Skip to content

Ensure error is propagated from rx queries correctly. #681

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

Merged
merged 3 commits into from
Apr 9, 2020

Conversation

zhenlineo
Copy link
Contributor

The rx queries should be semantically the same as the async queries.
Fixed a few wrong handling of finish future and error propergation used in rx queries.

@zhenlineo zhenlineo force-pushed the 4.0-fix-rx-stress-it branch from e818e55 to e1bf71c Compare March 12, 2020 15:58
Zhen Li added 2 commits April 8, 2020 17:24
The rx queries should be semantically the same as the async queries.
Fixed a few wrong handling of finish future and error propergation used in rx queries.
However this bookmark is not used for querying nodes count. It is only used to randomly generate queries waiting or not waiting for bookmark.
@zhenlineo zhenlineo force-pushed the 4.0-fix-rx-stress-it branch from e1bf71c to 0c4062d Compare April 8, 2020 17:43
@zhenlineo zhenlineo force-pushed the 4.0-fix-rx-stress-it branch from 0c4062d to e054ec5 Compare April 8, 2020 19:49
@zhenlineo zhenlineo merged commit a410b78 into neo4j:4.0 Apr 9, 2020
@zhenlineo zhenlineo deleted the 4.0-fix-rx-stress-it branch April 14, 2020 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants