libutil: Fix invalid boost format string in infinite symlink recursion error #13086
Conversation
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
…n error Found while working on an automated migration to `std::format`.
Mic92
added
backport 2.24-maintenance
backport 2.28-maintenance
mergify bot
added a commit
that referenced
this pull request
Apr 25, 2025
…3086 libutil: Fix invalid boost format string in infinite symlink recursion error (backport #13086)
mergify bot
added a commit
that referenced
this pull request
Apr 25, 2025
…3086 libutil: Fix invalid boost format string in infinite symlink recursion error (backport #13086)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
Found while working on an automated migration to
std::format#10294Boost throws a
boost::bad_format_string: format-string is ill-formedexception when creating a format string from this.Context
cc @Ericson2314, as git blame points me to your commit
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.