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.

Sign up for GitHub

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

Jump to bottom

Hang in case of error when sweep thread is attaching to database - classic server case #7985

Closed
AlexPeshkoff opened this issue Jan 30, 2024 · 2 comments
Closed

Hang in case of error when sweep thread is attaching to database - classic server case #7985

AlexPeshkoff opened this issue Jan 30, 2024 · 2 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 3.0.11 affect-version: 4.0.4 affect-version: 5.0.0 fix-version: 3.0.12 fix-version: 4.0.5 fix-version: 5.0.1 qa: covered by another tests type: bug

Comments

@AlexPeshkoff
Copy link
Member

AlexPeshkoff commented Jan 30, 2024 •
edited
Loading

The only purpose of having this issue separate from #7917 is release of FB5.0.0 without fixed classic server case, for master branch that's postfix for initial case.
@AlexPeshkoff AlexPeshkoff self-assigned this Jan 30, 2024
AlexPeshkoff added a commit that referenced this issue Jan 30, 2024
@AlexPeshkoff
Fixed #7985: Hang in case of error when sweep thread is attaching to …
6f393ba 
…database - classic server case: i.e. backported fix for #7917
AlexPeshkoff added a commit that referenced this issue Jan 30, 2024
@AlexPeshkoff
Fixed #7985: Hang in case of error when sweep thread is attaching to …
4c21cae 
…database - classic server case: i.e. backported fix for #7917
AlexPeshkoff added a commit that referenced this issue Jan 30, 2024
@AlexPeshkoff
Fixed #7985: Hang in case of error when sweep thread is attaching to …
5fe6d92 
…database - classic server case: i.e. backported fix for #7917
@AlexPeshkoff AlexPeshkoff mentioned this issue Jan 30, 2024
Closed
@pavel-zotov
Copy link

QA issue: see test for #7917

@hvlad
Copy link
Member

hvlad commented Feb 1, 2024

Should it be marked as fixed in 3.0.12 too ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 3.0.11 affect-version: 4.0.4 affect-version: 5.0.0 fix-version: 3.0.12 fix-version: 4.0.5 fix-version: 5.0.1 qa: covered by another tests type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AlexPeshkoff @hvlad @pavel-zotov