"Contents" link broken for some packages

[crockeea]

When looking at the documentation for a specific package, (say here), the Contents link at the top left right usually links to hackage.haskell.org/package/packageName-version, like so.

However, for at least the the singletons package, the Contents link from a documentation page goes to /singletons-version/docs/index.html, which is a very different page.

I can't say which link is intended, only that the behavior is different between most packages and singletons. Both pages seem like a reasonable choice for a link labeled "Contents" but the one with version numbers does help change versions more easily. The only way I've been able to change the version of this package starting from a doc page is to manually chop the link.

[lambda-fairy]

For singletons-1.0, the list of build reports is empty. This (usually) means the documentation was not built by the build bot, but uploaded manually by the maintainer.

Perhaps @goldfirere knows something about this.

[crockeea]

@lfairy Could that affect the "Contents" link? That seems more like a Hackage issue.

Also, version 0.9.3 has a non-empty list of build reports, but the same problem occurs when viewing documentation for that version.

[lambda-fairy]

Could that affect the "Contents" link? That seems more like a Hackage issue.

The build bot sets the contents link via a Haddock flag. Though the bot does act up at times, I doubt it would mess up in this way, for only a single package.

On the other hand, with so many fiddly options to deal with, it's very possible for a human to get it wrong.

Also, version 0.9.3 has a non-empty list of build reports

Ah, but if you look very closely, you'll see docsOutcome = Failed right at the end!

(Before you ask: there is a better UI for these reports; but with the infrastructure team overworked as it is it'll be a while before it's merged in.)

[crockeea]

@lfairy Is @goldfirere notified by these tags, or should I make an issue with singletons?

[goldfirere]

I believe this is solely Hackage's issue. It's quite true that singletons pushes the boundaries of what Haddock can do, and I'll take responsibility for manually uploading the docs. But, unless I'm told otherwise, I don't think there's anything I can do on my end to fix that link.

[gbaz]

This happened because the docs were uploaded as built by a user with different settings than we'd like. Other tickets capture trying to get the right default settings into cabal's ability to auto-upload docs, etc. That workflow should resolve this.