"Error 502 bad gateway" when trying to view a specific package

[LaurentTreguier]

I've recently registered a new package on code.dlang.org, named dls at version 0.1.0. My dub.json file specified the package version manually, and going on the package page, I saw that this was considered obsolete. After a few changes to my package, removing the version from dub.json and tagging a new version (0.1.1), going to the package page gives me an almost blank page; and then code.dlang.org only gives "Error 502 bad gateway" when trying to see any other page for the next minute or so.

Maybe this is somehow linked to #294 as the problem started occuring after an update to the package ?
I don't think I've done any wrong change from the 0.1.0 version, but if it is of any relevance, here are the dub.json file and the changes from v0.1.0 to v0.1.1.
Apart from the code, the only changes are adding a REAME.md, and removing the version section (as it's obsolete) and configurations section of dub.json (as dub detects the configurations automatically).

[wilzbach]

There's some discussion on #dub at Slack about this.
In short:

• it's due to Tables with more columns than header segfault server vibe-d/vibe.d#2132
• the Vibe.d PR is here: fix #2132 vibe-d/vibe.d#2133

[WebFreak001]

you can wait until this patch is applied to dub (who knows when), or you can remove the subcolumns in the table in your readme which breaks it. (You have more columns than header columns somewhere)

[LaurentTreguier]

I'm using | in the contents of my table, inside backquotes... I guess that's what's breaking everything. I'll update my README and push an updated version in the next few days (it's not urgent anyway)

[LaurentTreguier]

Removing the pipes in my table indeed fixes it. I'm closing this since there is already an issue and a PR

[s-ludwig]

The quickfix for the crash has been deployed, but I'll open separate issue against vibe.d for the correct output.

[wilzbach]

I can still crash the registry when I open http://code.dlang.org/packages/dls

[LaurentTreguier]

That's weird... It doesn't seem to happen to me anymore, I can see the page just fine now

[wilzbach]

A sorry. Probably was a super-aggressive browser cache.