-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
test_echo_quit_plugin
is flaky
#4976
Comments
iequidoo
added a commit
that referenced
this issue
Mar 9, 2024
A bot process is run asynchronously, so some messages can arrive before the bot is fully initialised.
This happened again recently: #5675 |
iequidoo
added a commit
that referenced
this issue
Jun 5, 2024
A bot process is run asynchronously, so some messages can arrive before the bot is fully initialised.
iequidoo
added a commit
that referenced
this issue
Jun 5, 2024
There was a comment in `fetch_existing_msgs()`: "Bots don't want those messages". If a bot doesn't want this setting, why enable it? It's disabled by default anyway.
iequidoo
added a commit
that referenced
this issue
Jun 6, 2024
There was a comment in `fetch_existing_msgs()`: "Bots don't want those messages". If a bot doesn't want this setting, why enable it? It's disabled by default anyway.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is a failure log:
The problem is that bot ignored the messages from the INBOX and DeltaChat folder as it set UIDVALIDITY/UIDNEXT when the message already arrived:
Normally for accounts we wait for IDLE
acc._evtracker.wait_idle_inbox_ready()
(should actually also wait for DeltaChat folder to go IDLE) as this means we have UIDNEXT set and will receive messages that arrive afterwards. But for the bot it is not done.The text was updated successfully, but these errors were encountered: