500 error trying to load snippets.

Issue #13372 resolved
Gary Sackett
staff created an issue

Receiving 500 errors, with codes when trying to load snippets.

Comments (20)

  1. Kaleb Elwert

    Missing snippet links sound like a separate issue. It would be great if you could contact support (support@bitbucket.org) with more information so we can try to get to the bottom of it.

  2. Kaleb Elwert
    • changed status to open

    Yep, looks like we only partially fixed this. If I had to guess, this happens when the creator of the snippet has been removed from the team. I've got a fix in review, so this should hopefully go out next week.

    Sorry for the inconvenience.

  3. dreamingrainbow

    500 Crossbones...

    Gotta love that...

    I knew I was hell on code.. ### didnt think it break the repo...

    HAHAHAHA No, but for really my code, aint crap... and I have plenty of repo's using the same account. Could it be because of the recent merge in accounts? Anyway... as long as I can still download the repo.. im cool, just hope you fix it!! Soon! I think you might want to look outside teams, as I am not a team player.. and code alone, don't use the team options very often. However, I use snippets for the special clips I deem keep-able, and last I checked staff can't even look at them via the web. So, maybe start with that, check .. for example that.. say my account has the correct permissions for each of the new snippets I created, then look at the older ones and see what is the difference. As I can access any of my old snippets, however the new ones .. well anyway.. you'll get it. I have faith!

  4. Kaleb Elwert

    I haven't been able to reproduce this locally. If anyone who is affected by this can give me the URL of a snippet which is not working, it would be a big help.

  5. Kaleb Elwert

    Alright, after digging into this a bit more, it appears to be related to files containing unicode characters over a certain size (Potentially 1M).

    You should still be able to clone these snippets and I'll be working on a fix which should go out in the next week or so.

    Thanks for your patience.

  6. Kaleb Elwert

    Looks like I was off by an order of magnitude. We fall back to a less expensive display when the file is over 100k. And there's a bug in the unicode handling for that.

    Edit: I have a fix ready against our staging branch, so my previous timeline is probably fairly accurate.

  7. Kaleb Elwert

    A fix for this was rolled out earlier in the week. I've confirmed this fixes the problem with the above hipchat snippets, so please let us know if you run into any other further issues.

  8. Log in to comment