fix(baileys): preserve sessions on transient disconnects#2612
Open
SmartNuvem wants to merge 1 commit into
Open
fix(baileys): preserve sessions on transient disconnects#2612SmartNuvem wants to merge 1 commit into
SmartNuvem wants to merge 1 commit into
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Sorry @SmartNuvem, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This fixes a regression introduced in 2.4.0-rc2 where transient disconnects
(e.g. DisconnectReason 408) were treated as permanent session closures.
Changes
closestate after transient failures.connection.updateandcreds.updateto avoid race conditions.Validation
Tested on a production-like environment:
Before this patch, instances disconnected within the same day or the following day and remained in
close.After applying this patch, the instance has remained connected beyond the period where the issue consistently occurred, without requiring QR reconnection.
No database schema, licensing, Redis, or authentication behavior was modified.