Tool: pr list --mine paginates every contributor PR #501
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
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
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#501
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?
forge.py pr list --minefetches every contributor's pull requests and filters by the signed-in login locally. On this repository, the traced command read325 PRs over7 pages (plus GET/user) to find our own handful. A successful rerun took about22s; the preceding attempt hit the client's30s read timeout, although that original run did not log which request stalled.The existing API supports server-side author filtering on the same pull-request endpoint:
poster=<username>. A normal authenticated metadata probe with poster=monsterlag returned exactly our5 PRs in0.368s, with full PR fields. The parameter takes the username, not the numeric user ID. No timeout, authentication or access-control change is needed.Claimed for a focused
--mineoptimization: URL-escape the current login into poster on every requested page, preserve the local ownership check defensively, preserve state/merged output and normal unfiltered listing, and cover pagination/encoding/read-only boundaries. Existing PR/claim overlap will be checked before implementation. Matrix broadcast is queued for the next permitted hourly slot; no force post.Priority: S3 contributor-tool latency/reliability defect, confidence1.0 for the bulk-fetch behavior and working author-filter probe. Reader/player reach is unmeasured; no player-impact score. This does not establish the exact cause of the earlier transient timeout or guarantee that all future network calls avoid a timeout.
Closing this as fixed: #877 is merged and addresses it. If that's wrong, or it still happens on a current build, feel free to re-open it.