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

Add serialize_writes option to ensure lines are sent in-order (resolves #361) #362

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

edfletcher
Copy link

@edfletcher edfletcher commented Jun 17, 2023

Resolves #361

Includes an integration test that exercises both option values, demonstrating that - without serialized_writes - lines that are purposefully reversed in order from that which the caller emitted them will be sent in that reverse order undesirably. When enabling serialized_writes, those writes are emitted in the order the caller intended.

I'll squash all commits in this PR down into one before merging.

@edfletcher
Copy link
Author

For E2E testing, I am using this fix-fork already with my personal DRC instance(s), and it's working like a charm. Can't really think of a better way to E2E test it except for putting together a significant bot-and-mock-server-based test harness, which honestly I just don't have the time for.

edfletcher added a commit to discord-relay-chat/drc that referenced this pull request Jun 22, 2023
Until kiwiirc/irc-framework#362 can be merged upstream.

Also includes the following fixes/updates:
* fix bug in log search consumed by irc-responseWhois-full.js
* fix join flood when isReconnect is true even though it should not be
* improve os image initial setup for base image in Dockerfile
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.

Lines can be sent out-of-order
2 participants