Skip to content

Conversation

darosior
Copy link
Member

v26 introduced a regression in that starting a bitcoind twice may have the second instance delete the cookie file of the first, making it impossible to communicate with it.

Not a big deal but it's annoying, only an issue for 26.0, and the patch is trivial.

@DrahtBot
Copy link
Contributor

DrahtBot commented Feb 28, 2024

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage

For detailed information about the code coverage, see the test coverage report.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK glozow

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

@maflcko
Copy link
Member

maflcko commented Feb 28, 2024

The backport should include the metadata:

Github-Pull: #num
Rebased-From: commit_id

You may use a script to do it for you: https://github.com/bitcoin-core/bitcoin-maintainer-tools#backport

@maflcko maflcko added this to the 26.1 milestone Feb 28, 2024
Otherwise, starting bitcoind twice may cause the `.cookie`
file generated by the first instance to be deleted by the
second instance shutdown (after failing to obtain a lock).

Github-Pull: bitcoin#28784
Rebased-From: 7cb9367
@darosior
Copy link
Member Author

Thanks, done using backport.py.

Copy link
Member

@glozow glozow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm ACK 1e95643

@glozow glozow merged commit a718bfa into bitcoin:26.x Feb 28, 2024
@bitcoin bitcoin locked and limited conversation to collaborators Feb 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants