Skip to content

Conversation

jmberg
Copy link
Member

@jmberg jmberg commented Apr 23, 2025

It's much easier since events get a timestamp from the server, not from the email. It should also be cheaper for the server since we can limit to the last event we saw before.

RFC because I'm not sure how you'd want to to handle the switch-over ... the state is re-initialized. For myself I just decided to do it manually and not worry about seen series etc.

@kuba-moo
Copy link
Contributor

Manual reinit is fine, I reckon. We could try to maintain the seen series for a bit to discard the 2h overlap after first restart, but seems like an overkill. I'll redeploy our instances on the weekend when traffic is low.
Could you rebase tho, I fixed the lint stuff that's failing yesterday.

It's much easier since events get a timestamp from the server,
not from the email. It should also be cheaper for the server
since we can limit to the last event we saw before.

Signed-off-by: Johannes Berg <[email protected]>
@jmberg
Copy link
Member Author

jmberg commented Apr 24, 2025

Sure, done. FWIW I've been running it for wireless since I pushed it, and happy with it - reacts much faster.

@kuba-moo kuba-moo merged commit db9c2da into linux-netdev:main Apr 24, 2025
1 check passed
@kuba-moo
Copy link
Contributor

Thanks! :)

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