Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error reference: 5bce264b7e014802a20244e4cd230a74 #2

Open
bgoonz opened this issue Sep 12, 2021 · 2 comments
Open

Error reference: 5bce264b7e014802a20244e4cd230a74 #2

bgoonz opened this issue Sep 12, 2021 · 2 comments

Comments

@bgoonz
Copy link

bgoonz commented Sep 12, 2021

This is not an issue with the stackbit CLI but instead the GUI.

I wasn't sure where to submit the issue and this seemed like the most official repository for this GitHub organization. I am not sure exactly what is causing the issue but it feels like an authentication issue. For a few minutes it abated but then returned to an error code minutes later.

I will attach a screenshot of the error popup... as I was writing this the issue seems to have self resolved once again but based on my prior experiences tonight I expect it won't last long. Unless I have accidentally revoked some sort of permission or token on GitHub I expect this issue belongs to the server. Love the product... not complaining, just figured this is the kind of thing you guys might want brought to your attention.

stackbit-error

@bgoonz
Copy link
Author

bgoonz commented Sep 12, 2021

Fyi... the image may look very low resolution... and it is, but if you click on it it will focus to the extant necessary to read the individual characters if necessary. At least it does for me. Let me know if you need any further information.

@bgoonz
Copy link
Author

bgoonz commented Sep 12, 2021

One last detail, it just occurred to me that I have about 2000 commits in the last 24 hours (gitbook merge button will do that if you're not conscious of how often you're merging), and it's remotely possible that the issue may have something to do with me running up against the GitHub API rate limit... (to me that's the most plausible explanation for why the issue seems to resolve it's self only after a period of inactivity on GitHub), however, I have not received any notification from GitHub that this is the case yet. I submitted an inquiry with the GitHub team and if they respond in the affirmative, I will reach out to make sure that you guys aren't chasing a bug that does not exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant