Tool: forge.py issue view hides attached diagnostic logs #289
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#289
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
python -I scripts/forge.py issue view N --commentsomits the issue's attached files. For bug triage this makes a report appear to have no log even when it does.Reproduction
At Longshot main
514591a3(also present atd906c8f4), view issues 278, 261, 275 or 271 with that command. The body says the log is attached, but no attachment names or URLs are printed. The same issue GET that cmd_issue already performs returns anassetsarray: issue 278 has two text logs, issue 261 has a small diagnostic ZIP, and issues 275/271 also have log files.cmd_issueprints only title/state/body and optional comments, so it discards this metadata.Expected behavior
Show the attachment names, sizes and
browser_download_urllinks in issue view, without automatically downloading or executing anything. Keep ordinary issues with no assets working. Links remain subject to their normal access controls; showing a link must not try to bypass them.Evidence and priority
Reproduced from the existing authenticated issue API response and the local CLI output; no game files were read or shared. This is a contributor-triage defect, not a demonstrated player crash. Confidence 1.0; affected-reader reach is unmeasured, so no player-impact score is assigned.
PR 254 adds uploading pictures to comments and PR 120 handles UTF-8 output; neither supplies issue-attachment listing. No implementation is claimed here yet.
Claimed for a focused CLI fix after checking current PRs and team claims. I will display existing API attachment metadata only, add no-attachment/comments/network-boundary regressions, and verify native Windows before/after output. Attachment access controls remain in place; no content download is part of this fix.
Implemented in #300, now ready for review. Two native regression pairs reduce four non-passing cases to zero, and two live metadata-only pairs show both attached logs instead of zero rows. Full suite:497 passed,3 failures also reproduced on untouched main,33 skipped; details and limits are in the PR. No attachment content request was introduced.