This message was deleted.

I am also getting 500 on create:

📨 Pushing to remote and creating/updating PRs...
ERROR: Unexpected server response (500).

Headers:
  x-graphite-request-id: <uuid>

Response: {
  "_response": {}
}

thanks both for flagging! I've flagged to the team and they'll look into this.

Hi all! Looks like there was a Github outage at this time. Are you still seeing 500's or is this resolved? https://www.githubstatus.com/incidents/smdz34v7j8q0

I am still seeing 500s. There’s no current GitHub incident https://www.githubstatus.com/

$ gt ss -nd                                       
🥞 Validating that this Graphite stack is ready to submit...

✏️  Preparing to submit PRs for the following branches...
▸ nick09-07-add_backtest_to_ci (Create)

📨 Pushing to remote and creating/updating PRs...
ERROR: Unexpected server response (500).

Headers:
  x-graphite-request-id: 53f9d57a-105c-4ee4-9a5d-797855633962

Response: {
  "_response": {}
}

Hi @Nick, apologies for the delay here. I’m looking now!

No, i have been able to access https://github.com/BitBuilder-ai/bitbuilder consistently. I can also Pull

gt rs -r

just fine, and also if i try pushing

gt ss -nd

it similarly updates the branch, it simply doesn’t update the PR state (draft or not) correctly. is there a way i can reset the Graphite state for that repository easily to see if that fixes it?

Hi @Nick, after digging in further, here’s the issue: • When submitting changes from the CLI, we push to the repository (using your auth key, e.g. SSH key) and then try to open/update a PR on your behalf for the corresponding changes (this requires a GitHub API key). • In the case where the latter is failing (this case), it’s because the GitHub API doesn’t think we have access to the repository (either because the repo has been renamed and the repo the CLI has inferred/is looking for is now incorrect or because the GitHub API key can’t access the repo). • Given that the repo hasn’t been renamed in this case (and after inspecting your API key), I think the issue is the latter; I can’t seem to see your membership in the BitBuilder-ai org at all using your API key. In terms of solutions, there’s 2: • Your current GitHub auth method on Graphite (that generates your API key) is our default, OAuth. When authenticating via OAuth, you won’t be able to see any information about an organization if the organization has “OAuth app access restrictions” on. The solution here (if you’re an org admin/know who your org admin is) is to navigate to the page (https://github.com/organizations/BitBuilder-ai/settings/oauth_application_policy) and then approve the Graphite OAuth app. • Alternatively, as an escape hatch, you can also switch your GitHub auth method to “Personal access token” which doesn’t require approval to access your org resources.

cool, working now

Awesome, glad to hear!