timermiddleware:db/8333 (will need release published, req.txt updates) and a few more commits to allura:db/8333
--- ** [tickets:#8333] Forgehg: upgrade mercurial** **Status:** review **Milestone:** unreleased **Created:** Thu Sep 12, 2019 09:47 PM UTC by Dave Brondsema **Last Updated:** Tue Sep 17, 2019 07:48 PM UTC **Owner:** Dave Brondsema Currently at 3.2.2 forgehg/setup.py pins the version lower https://www.mercurial-scm.org/wiki/Python3 says we should target Mercurial 5.0+ Changelogs: https://www.mercurial-scm.org/wiki/UpgradeNotes https://www.mercurial-scm.org/wiki/WhatsNew/Archive https://www.mercurial-scm.org/wiki/ApiChanges Test coverage is good 89% but some cases would be good to cover, for this and upcoming python3 work * 3.2.3 tests pass, but need to check on reproing `hfsignoreclean` errors - OSX only? * 3.4+ has UnicodeWarning although tests pass * 3.5.0+ has weird "`linking [ <=> ...`" output * 3.7.0+ `forgehg.tests.model.test_repository:TestHgRepo.test_merge_request_commits` fails * 4.6.0+ lots like f`orgehg.tests.functional.test_controllers:TestLogPagination.test_log_messages ProgrammingError: revset statement must be bytes, got u'0debe4adbedc5d711d2e379027cc3c6cca26f89a:0'` * 4.8.0+ lots during repo init: `TypeError: type() argument 1 must be string, not unicode` Should test with older repos --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
