Sudden 404: Not Found error

[denkristoffer]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Bundlesize returns "Could not add github status. 404: Not Found"

Please mention other relevant information.
We've been using bundlesize with Circle CI for months with no issues, but during the night between the 18th and the 19th of September something has broken. We're now getting the above error. I've tried updating and replacing the token ENV var to no avail.

[siddharthkp]

The usual suspects are:

• https://bundlesize-store.now.sh is down (it isn't)
• your GitHub token expired (you replaced it)
• your new token does not have access to add status (?)
• bundlesize hit rate limit for GitHub (i don't think it has enough users yet :P)

GitHub error messages usually give a 404 instead of 401 in cases like this

I'd suggest checking if the token has access, and running bundlesize with --debug flag to see if spots one of the common problems

[denkristoffer]

Running bundlesize with --debug gives me output ending with the following (after displaying all the chunk sizes:

 WARN  token exists: true 

 WARN  repo: "Onlaw/onlaw.dk" 

 WARN  sha: "f1c43040e6b8ad10122bfb7a22a4b44a2d10d958" 

 WARN  api enabled: true 

 WARN  fetching values: "..." 

 ERROR  Could not add github status.
        404: Not Found 

Doesn't tell me much. Any ideas?

[cihati]

I have the exact same issue as @denkristoffer, any ideas @siddharthkp ? Using CircleCI.

Regarding

your new token does not have access to add status (?)

How do I check it? @siddharthkp

When I tried to generate the token, although I am being asked my GitHub credentials, I do not see another intermediate screen until https://bundlesize-store.now.sh/auth?code=XYZ site

[siddharthkp]

Does anyone know if this means that the token doesn't have permission to update the status?

Yep, GitHub sends down a 404 if you don't have permission

[landvibe]

Same here with Circle CI

[denkristoffer]

@siddharthkp I don't think this issue should be closed, missing access was never the problem in my case.

[siddharthkp]

Oops, sorry. There was another sub-thread in between.

[grumpyoldman-io]

I just fixed this on our pipeline. The BUNDLESIZE_GITHUB_TOKEN can expire. Github will reply with a 404. Follow the steps here to reset your token: https://github.com/siddharthkp/bundlesize#build-status-for-github

1. go here: https://github.com/login/oauth/authorize?scope=repo%3Astatus&client_id=6756cb03a8d6528aca5a
2. replace the token in your build tool with the supplied token.
3. restart build.

[PaulKujawa]

What is the lifetime of this token? A token can not just expire without being automatically refreshed when this is supposed to be embedded into corporate CI workflows.