-
Notifications
You must be signed in to change notification settings - Fork 184
Query doesn't complete #292
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
Comments
I can confirm this happening; this fix should be part of |
Thanks a lot for the reproducer. I'm going to investigate what's going on. |
As it looks now, the emission gets stuck after |
We now make sure to call demandMore() regardless of the drain loop to ensure that demand is propagated upstream even if the drain conditions are not met. Previously, concurrent consumption lead to an empty buffer without demand propagation and so emission got eventually stuck. [resolves #292]
0.8.4 snapshots are available from repo.spring.io. Feel free to test against the new snapshots. |
@mp911de Thanks, i will check it. |
Not yet. Roughly, we aimed for shipping releases every two months. Mid-July seems a good target. |
Is it part of |
@mp911de I have been trying to pull the SNAPSHOT build I am getting:
Gradle seems to be getting 403 here. |
repo.spring.io was impacted last night by an incident, see https://status.jfrog.io/incidents/cjx2djy9xzb2 for further details. The incident is resolved now. |
Thanks it works now. |
i can confirm as well this issue is fixed now. |
We now make sure to call demandMore() regardless of the drain loop to ensure that demand is propagated upstream even if the drain conditions are not met. Previously, concurrent consumption lead to an empty buffer without demand propagation and so emission got eventually stuck. [resolves pgjdbc#292]
Reorder methods. Add Javadoc. [pgjdbc#292]
We now make sure to call demandMore() regardless of the drain loop to ensure that demand is propagated upstream even if the drain conditions are not met. Previously, concurrent consumption lead to an empty buffer without demand propagation and so emission got eventually stuck. [resolves pgjdbc#292]
Reorder methods. Add Javadoc. [pgjdbc#292]
Bug Report
Versions
Current Behavior
query doesn't complete and doesn't emit all of the rows.
Steps to reproduce
i forked
r2dbc-postgresql
and added a new test that reproduce this issue.take a look at this commit: mosherobinov@a679e8e
seems to be some kind of a race between the
onNext()
andrequest()
when they are happening on different threads,therefore i had to
publish
on a different scheduler andlimitRate
to 1 so theonNext()
andrequest()
will interleave.the test times out after the query doesn't complete.
The text was updated successfully, but these errors were encountered: