Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Dec 19, 2025

It's possible for Windows to be so stubborn that the file can't be opened after open_eventually has given up, which causes a crash and force the queue to be restarted, then trying to open that same file during recovery still errors out.

Using open_eventually there may or may not help.

Also use open_eventually in queue store's get_read_fd as a crash log has shown it can happen there as well.

#15134

Note that this isn't a "real fix" but just more workarounds for some annoying Windows behavior.


This is an automatic backport of pull request #15136 done by Mergify.

It's possible for Windows to be so stubborn that the file can't
be opened after open_eventually has given up, which causes a
crash and force the queue to be restarted, then trying to open
that same file during recovery still errors out.

Using open_eventually there may or may not help.

Also use open_eventually in queue store's get_read_fd as a crash
log has shown it can happen there as well.

(cherry picked from commit ba71e66)
@michaelklishin michaelklishin added this to the 4.2.3 milestone Dec 19, 2025
@michaelklishin michaelklishin merged commit 9aab44b into v4.2.x Dec 19, 2025
291 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.2.x/pr-15136 branch December 19, 2025 17:18
@michaelklishin
Copy link
Collaborator

@Mergifyio backport v4.1.x

@mergify
Copy link
Author

mergify bot commented Dec 19, 2025

backport v4.1.x

✅ Backports have been created

Details

michaelklishin added a commit that referenced this pull request Dec 19, 2025
CQ: Use open_eventually in recovery (backport #15136) (backport #15167)
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.

3 participants