Skip to content
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

appengine_api: always consider push to properties interfaces succesful #438

Merged

Conversation

rbino
Copy link
Collaborator

@rbino rbino commented Jul 10, 2020

A push can fail only if the device doesn't have a session on the broker. But if
it this happen, then the device will ask for all properties at the next
reconnection. This allows to push properties to devices before their first
connection, making sure they're saved to the database.

Signed-off-by: Riccardo Binetti riccardo.binetti@ispirata.com

A push can fail only if the device doesn't have a session on the broker. But if
it this happen, then the device will ask for all properties at the next
reconnection. This allows to push properties to devices before their first
connection, making sure they're saved to the database.

Signed-off-by: Riccardo Binetti <riccardo.binetti@ispirata.com>
@rbino rbino added bug Something isn't working app:appengine_api This issue or pull request is about astarte_appengine_api application labels Jul 10, 2020
@rbino rbino requested a review from bettio July 10, 2020 16:28
@bettio bettio merged commit d1abf31 into astarte-platform:release-1.0 Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app:appengine_api This issue or pull request is about astarte_appengine_api application bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants