-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Properly await for AddInclusionBounds
#47
Conversation
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Without this, the function call will never actually run. I'm not sure if this was working anyways because of some obscure implementation detail in grpcio, but in normal python a not awaited async function should never actually run. Besides this, for sure errors can't be really caught without the await either. This was detected while migrating to betterproto, as betterproto has correct type hints. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
All other calls have a timeout, so this one should probably too. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
This tests both that the timeout is set and that errors are properly handled after the `await` bug fix. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Btw, the SDK doesn't use the The previous version of the EV charger pool was using this implementation of The older version of the EV charger that was deployed in a demo installation was using an older streaming |
OK, I guess that explains why we didn't notice. |
Without this, the function call will never actually run. I'm not sure if this was working anyways because of some obscure implementation detail in grpcio, but in normal python a not awaited async function should never actually run.
Besides this, for sure errors can't be really caught without the await either.
This was detected while migrating to betterproto, as betterproto has correct type hints.