Skip to content

Conversation

@troygilman
Copy link
Contributor

This PR is a bugfix for issue #173.

We must check if the ring-buffer has messages after transitioning the procStatus to "idle". If there are messages, then we should schedule again.

I added a test that can somewhat reliably reproduce the issue. However, the test takes about 2 seconds to run on my machine.

@troygilman
Copy link
Contributor Author

FYI the cluster tests are very flakey. I needed to trigger the build a few times to get them to pass.

@anthdm
Copy link
Owner

anthdm commented Dec 27, 2024

@troygilman0 The test are indeed scuffed, do to the "async" nature and probably the skill issue on my end as well. Been thinking about it for a long time to rewrite those.

@anthdm
Copy link
Owner

anthdm commented Jan 3, 2025

Nice found my man! Thank you a lot for your time.

@anthdm anthdm merged commit 02bbf30 into anthdm:master Jan 3, 2025
1 check passed
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