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

Test long running received record processing after task is complete #36

Open
ekigamba opened this issue Apr 5, 2019 · 1 comment
Open
Labels
bug Something isn't working Size: Small (≤1)

Comments

@ekigamba
Copy link
Contributor

ekigamba commented Apr 5, 2019

Check if the processing of received records is affected if it takes longer than after the sync complete command is sent by the sending device and received by the receiving device.

Or does the async task die?

@ekigamba ekigamba added bug Something isn't working Size: Small (≤1) labels Apr 5, 2019
@ekigamba
Copy link
Contributor Author

It also seems that the Async task dies if the connection breaks while it is not done processing, sometimes on the sample app, the last record id is logged but it is not saved in the DB. Other times it is logged but not saved in the DB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Size: Small (≤1)
Projects
None yet
Development

No branches or pull requests

1 participant