Skip to content

[Bug]: Opening a pull request fails while its host is rate-limited #27579

Closed

Description

@PolarBearEs

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. Get a source control host rate-limited so SourceControlRateLimit pauses it, for example Bitbucket with several linked pull requests ([Bug]: PR sync reads pull requests GitHub cannot find on every sweep, even on settled threads #17799).
  2. While it is paused, open one of that host's pull requests in the pull request panel.

Expected behavior

The pull request loads. #23889 says reads a user is waiting on still go out while background reads wait for the pause to end.

Actual behavior

The panel fails with paused until the rate limit resets. withRateLimitBackoff wraps getChangeRequest, getChangeRequestActivity and the other reads with allowPaused = false and provides Interactive as false. So ws.rpc.pullRequests.detail is treated as a background read and fails before any request goes out. I saw this on Bitbucket; the wrapper is shared, so other providers are likely affected too.

Impact

Major degradation or frequent failure

Version or commit

0.1.6-nightly.20261030.3917

Environment

Linux x64, desktop AppImage, Bitbucket Cloud

Logs or stack traces

PullRequestProviderError: bitbucket failed in getChangeRequest: bitbucket requests to bitbucket.org are paused until the rate limit resets.
    at PullRequestService.withRoutingCredential
    at ws.rpc.pullRequests.detail

Workaround

Wait for the pause to end.

Activity

  1. pyhrus commented on Nov 6, 2026

    @pyhrus

    Also seen on stable 0.1.6 (desktop, macOS arm64, Bitbucket Cloud). Between 09:48 and 10:30 UTC on 2026-11-05, the server traces show these calls failing with bitbucket requests to bitbucket.org are paused until the rate limit resets.:

    • ws.rpc.pullRequests.detail: 21
    • ws.rpc.pullRequests.activity: 10
    • ws.rpc.pullRequests.reviewGuide: 10

    None of these failures appear after the app moved to 0.1.7 at about 11:20 UTC. The traces don't show whether a pull request was opened during a pause after that, so this doesn't tell us whether 0.1.7 is affected.

    Posted by Claude Code (claude-opus-5-5) via t3 triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions