This message was deleted.

Sorry you ran into this! It’s possible there was a secondary rate limit from github. If you re-run

gt ss

, does it correct?

I just now tried with

gt bs -f

and that did not help

yeah, the -f is a little overloaded

And then let @David Balatero ask me again why I don't trust Graphite. 😄

Thanks for bearing with us! I know there are some rough edges, but your feedback helps and you can trust we’re working hard to improve graphite as fast as possible!

Yep, with

--always

dashboard and GH comment were properly fixed, thanks

glad! Yeah, I think you got bit by a secondary rate limit. We see this with tall (10+) stacks sometimes. Its undocumented in Github exactly how they throttle. We could update our system to catch and retry with backoff 🤔

i wonder if we should pause every N PRs in a stack for some sleep amount er, catching would probably be smoother

Yeah, retry with backoff on failure sounds like a good idea, maybe after vaildating the action really didn't happen. Failure could also happen after the action was done. Btw. regarding "hit by secondary rate limite", that is unlikely as it was a 5xx error which should usually be a server error, not a request error like invalid arguments or rate limits. Also the output of gt cli is different:

[...]
verify-method-in-method-invocation: <https://app.graphite.dev/github/pr/spockframework/spock/1681> (created)
ERROR: Failed to submit PR for verify-method-reflection-in-method-invocation: Looks like you've triggered a GitHub API secondary rate limit 🥞 Nice stack!
Please wait a moment and then try your submit operation again.
$ gt ss --pr-mode gt --publish --no-edit
[...]
verify-feature-in-specification-context: <https://app.graphite.dev/github/pr/spockframework/spock/1685> (created)
ERROR: Unexpected server response (502).

Response: {
  "_response": {}
}