May 20 2020
Jan 8 2020
Sep 11 2019
Sep 10 2019
The error I mentioned looks like this:
Sep 9 2019
Sep 6 2019
Nov 2 2018
Either way, we'll be deploying this to Mozilla's hg servers in the next few months and testing it out. Perhaps after it's been in production for some time we will have a stronger case for inclusion in core. :)
Oct 30 2018
Is this useful enough to others that it should live in the hg core repo? It doesn't seem like it to me, but maybe I'm wrong.
Oct 26 2018
Throwing this up for review now, but there are a few things that could be done to improve this. A cache expiration policy might be useful, but is difficult to test with the S3 bucket expiration rules. It may also be desirable to be able to specify more than one S3 bucket/region/account in the future.
Oct 14 2018
Aug 20 2018
This seems like a strict improvement.
But the proper way to register web commands from extensions would be to go through the registrar API and have the extension loader look for a well-named symbol in each extension module that is loaded and hgweb would consult the registrar for active commands. In theory, this will only activate web commands on repositories that have an extension loaded.
Search for templatefilter in mercurial/extensions.py for an example of how all this works.
Would you be willing to try that approach? It doesn't have to be perfect. But we are moving to the registrar for extensions wishing to install well-defined things. And web commands fit that bill.
Aug 15 2018
Mar 31 2018
Abandoning, this was landed as another differential.