gbaz
I like this proposal -- I've run into this issue before, and I can't think of a case where this would be problematic. It might be worth printing a notification...
Is this still pending a test?
This seems the right place, as the cache control for both the json files and the index tarball is set in the server code. I agree it would be better...
I'm confused. That 300 that I'm proposing is the max-age for the json files. We could also cut the max-age from 300 to 60 for the 01-index if you prefer....
On that fix, we can change the uses of `maxAgeMinutes` in this file https://github.com/haskell/hackage-server/blob/8815bc9e27ec25506952f6e41b38d5293d5d31d6/src/Distribution/Server/Features/Core.hs#L666
bump on the above question -- i would like to approve and merge but this should be resolved.
This feature was introduced by @414owen in https://github.com/haskell/hackage-server/pull/1279 -- maybe they'd be open to a followup PR? Patches from others also welcome.
That error comes from ghc -- the build brings autoexporter into scope, but for some reason ghc fails on executing it? Don't see why offhand
The first issue is a good call! I believe the plan was to add a ui to give access to the test build reports, but I can't find an issue...
if its an issue with how the server parses newlines in headers, then likely the non-cabal fix will have to be not in hackage itself, but upstream in happstack.