You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When more than one proto files are provided to the gRPC Template Creation Utility, which both include the same imported file, the Utility is not being able to build the library and stops its execution with the following error.
LabVIEW: (Hex 0x425) Unable to create new object.
Is this a bug, or should I provide the imported files some other way, then mentioning them in the proto files?
The files are imported as follows:
import "common.proto";
import "error.proto";
All imported files are located in the same directory as main proto files, and the utility is able to read them.
AB#2626689
The text was updated successfully, but these errors were encountered:
Both the messenger.proto and greeter.proto use the Response message.
Using the gRPC Template Creation Utility :
I can script messenger.proto separately SUCCESFULLY.
I can script greeter.proto separately SUCCESFULLY.
I cannot script both the messenger.proto and greeter.proto together. could it be that the scripting is done sequentially and the Request TypeDef is made for the 1st proto file, and then when trying to make that same TypeDef (with same name) for the 2nd proto file, it cannot at it to the Library (because there already exists a TypeDef with the same name)?
These used-case (multiple proto files that use the same common.proto) is not uncommon when using gRPC in other lanuages like for example C#.
So hopefully this can be fixed in the future.
Could anyone tell me if this is on the roadmap to be fixed soon?
When more than one proto files are provided to the gRPC Template Creation Utility, which both include the same imported file, the Utility is not being able to build the library and stops its execution with the following error.
LabVIEW: (Hex 0x425) Unable to create new object.
Is this a bug, or should I provide the imported files some other way, then mentioning them in the proto files?
The files are imported as follows:
import "common.proto";
import "error.proto";
All imported files are located in the same directory as main proto files, and the utility is able to read them.
AB#2626689
The text was updated successfully, but these errors were encountered: