-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
GET /values resulting in status code 500 #308
Comments
same error on circleci, very often in last time :((( |
Ugh, this is pretty horrible. Migrating to a different storage (shelf) is on my roadmap, haven't been able to get to it yet. |
@siddharthkp what's going on with the storage backend? Does 500 mean... we're overwhelming the firebase app? Or is it a serialization/deserialization issue? Could we try wiping the data for our repo and start from scratch? |
500 = It's unhandled. Could be either, honestly.
I don't think that will help. I will find some time to dig into this, soon-ish. |
Hi! |
@bolismauro Are you seeing this error too? (I'm working on a long term fix this month) |
Yes yesterday it didn't work but I just tried and It worked. No idea why |
bumped |
For what is worth, we too are seeing this on Bootstrap for quite some time now. |
Just installed bundlesize (0.18.0) and when I added BUNDLESIZE_GITHUB_TOKEN I got this error. I'm guessing it's a problem with the size difference calculation because the CI status check still works and we still get size details on the https://bundlesize-store.now.sh website. Our CI message: bundlesize — Total bundle size is 514.3KB/1.76MB (-null) |
Same here. It started 1 hour ago and restarting builds doesn't help: https://travis-ci.org/Redocly/redoc/builds/564951645 |
Me too on Travis
|
Still an issue for me as well. Anything we could contribute to get this fixed? |
If you have a similar issue can you please add a 👍 to the first post, people who are watching this thread for a response get notified so writing a comment that is the same as that isn't very useful |
Still an issue for me on this job. |
I just ran into this issue, too, unfortunately. |
I got this issue... |
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
For anyone bumping into this, https://github.com/bundlewatch/bundlewatch might be an alternative. |
Bundlesize is unmaintained and currently doesn't support reporting differences compared to master, see: siddharthkp/bundlesize#308 As mentioned here, Bundlewatch seems to be a working successor: GoogleChrome/lighthouse#10272 (comment)
We are getting this issue as well on our project. Looking at this thread should we still be using this tool? It looks like this has been an issue for a long time and no one has fixed it, solution seems to be removing the tool for most projects and use an alternative. @siddharthkp any chance this will be fixed? Is this tool still actively maintained? 🙂 |
going to be honest, barely 😓 I did a rewrite which is a lot more reliable - https://github.com/siddharthkp/bundlesize2, it's not 100% feature complete, but it's got the core features you probably need. Migration path:
|
Do you want to request a feature or report a bug?
Bug 🐛
What is the current behavior?
When our Travis CI build runs
yarn bundlesize
, the size check against master fails and we get some http logs indicating a 500 error.If the current behavior is a bug, please provide the steps to reproduce.
Here's the relevant section of the Travis CI build logs:
What is the expected behavior?
I expect the master branch values to be retrieved successfully, resulting in a handy comparison in the status notification on the pull request.
If this is a feature request, what is motivation or use case for changing the behavior?
N/A
Please mention other relevant information.
I'll pull these straight from the Travis CI logs
The text was updated successfully, but these errors were encountered: