Closed Necr0x0Der closed 1 week ago
Dear @Necr0x0Der, Thank you for reporting this issue. We appreciate your feedback and apologize for any inconvenience caused. After thorough investigation, we have resolved this issue in the v3.3.0 of our app. The config now supports optional force_update key. If set to False (default) it will not re-download the proto file and re-generate the gRPC stubs if they already present in the .snet directory. Please update to the most recent release, and if you encounter any further problems, feel free to reopen this issue or create a new one. Best regards, Paul, SingularityNET
Thanks. It seems to work. The only question is what is the parameter for forcing proto files to be reloaded and recompiled? I'm not sure if this parameter should be True
or False
by default, but we may need control over it in any case
@Necr0x0Der if force_update is set to True, the SDK will always reload and recompile the proto files
Thanks! I see that it is in README, so I'm closing the issue.
It seems that the service information is requested each time from the platform, and protobuf compilation is done each time. Running the same script two times in a row produces the following messages each time:
This process requires several seconds. It should not be done each time. This can be achieved in different ways:
force_update
(or with another name) can be introduced to redo this.