Jonas Bernoulli

I am on a mental health break (because all those little requests took a toll on me), but because I contacted you elsewhere, I'll make an exception and respond here....

Is this when trying to fetch a huge repository? I'm actually a bit surprised this happened. I had some debug statements that printed the relevant information and it never got...

I don't consider that a huge repository and it is indeed at the same magnitude as Magit. It's weird that you hit the rate limit. While neither `ghub` nor `forge`...

We should consider the rate limiting headers and report when we get close. Most of that probably has to be implemented in `ghub`.

> "Could not resolve to an Issue with the number of 151." Could be that that issue was deleted just as you were fetching. Use this code to determine the...

This won't happen more than once in a blue moon and so won't attempt to come up with a work-around. Notification fetching is already very complicated because of limitations of...

Please post the error message. Use the above code-snippet to determine which issue from which repository this is about. Is there anything special about that issue?

In the short-run the only workaround is to not fetch notifications (by setting `forge-pull-notifications` to `nil`) until Github forgets about the offending notification.

I am unable to reproduce this. For me the list of notifications does not appear to include any entries about topics that no longer exist. (I created two issue using...

Can you provide more information about the issue "that is not there"? Do you know that the issue by that number existed at one point? Did you delete it or...