-
Notifications
You must be signed in to change notification settings - Fork 56
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
Have frontend proxy persist events when using redis #870
Conversation
438fa97
to
705d037
Compare
There have been quite a few changes here... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for taking a while to get to this. The new changes look great from a stability standpoint, and the additional logging is appreciated!
@@ -774,7 +774,7 @@ | |||
qw( can_sync ) ], | |||
|
|||
# sending 50 messages can take a while | |||
timeout => 20000, | |||
timeout => 20, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this made tests go faster or was this just an unnecessarily large number to begin with?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I forgot about these. I think there was a confusion for the units here, they're in seconds not milliseconds (a timeout of 6 hours seems excessive).
…insic-release-v1.15.x * 'release-v1.15.0' of github.com:matrix-org/sytest: Use the standardized form for SSO login via user interactive auth. (#884) Add tests for room version 6. (#869) Add a retry_until_success around room join (#882) Have frontend proxy persist events when using redis (#870) Squashed commit of the following: Fix link to Synapse's contributing docs. (#879)
Requires: matrix-org/synapse#7517
I chose to use frontend proxy rather than the event creator to ensure we test the HTTP replication routing. (We could use a new worker, but that is surprisingly faffy)