Repository navigation
Conversation
Every bug report from a machine nobody here owns starts with the same three questions: which version, against which engine, on what. --report answers all of them in one block, so a reporter pastes rather than remembers. The block comes from the kit's new report package, so the whole family answers in the same shape. What this tool adds is its own half: which engines this machine has and at which versions, or the reason a version could not be read. That line answers most reports here on its own — an action refused by a Podman below 5.0 and one refused by a bug look exactly the same from the outside. It reaches no engine socket and it runs before the backend is built. A user who cannot reach the socket, or a machine with neither engine installed, still produces a report. In --demo it says demo on the backend line, names the backend the fake imitates, and says plainly that nothing was probed. The block is written to be published: no hostname, no user name, no home path. The unit test asserts that, and the smoke test asserts it again on a real guest, next to the checks that the report agrees with the backend --check names and with the engines the guest really has. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MCypLQF5AD8JD831Ea9S9q
The report's privacy check greps its whole output for the host name, which a machine named after its distribution fails on a line it is entitled to: the distro line comes from /etc/os-release and the kernel line from uname's release and machine, never from the node name. Both are excluded from that search, and from that search only — every other line is still checked, which is where a host name would actually leak. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MCypLQF5AD8JD831Ea9S9q
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.
Every bug report from a machine nobody here owns starts with the same three
questions: which version, against which engine, on what.
--reportanswers allof them in one block, so a reporter pastes rather than remembers.
The block comes from tui-kit v0.2.9's
reportpackage, so the whole familyanswers in the same shape. What this tool adds is its own half: which engines
the machine has and at which versions, or the reason a version could not be
read — the line that answers most reports here on its own.
It reaches no engine socket and runs before the backend is built, so a user who
cannot reach the socket still produces one. In
--demoit says demo, names thebackend the fake imitates, and says plainly that nothing was probed.
The bug form is rendered from the kit template and asks for the block first.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MCypLQF5AD8JD831Ea9S9q