You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github API has a bug in it's _request functionality which makes it impossible to catch some kinds of errors in the returned promise of Repository.getRelease call. In our case we could not catch the error thrown when the github api returned a 403 due to rate limiting. This then can prevent start up of the application.
Due to this we should remove usage of github-api as the underlying issue has not been resolved. see github-tools/github#439.
The text was updated successfully, but these errors were encountered:
fcaps
added a commit
to fcaps/website
that referenced
this issue
Nov 12, 2023
Github API has a bug in it's _request functionality which makes it impossible to catch some kinds of errors in the returned promise of Repository.getRelease call. In our case we could not catch the error thrown when the github api returned a 403 due to rate limiting. This then can prevent start up of the application.
Due to this we should remove usage of github-api as the underlying issue has not been resolved. see github-tools/github#439.
The text was updated successfully, but these errors were encountered: