controllers: don’t pass start=0 to BaseRepository.get_changesets() MercurialRepository.get_changesets() can fail if passing start=0 if the revision 0 is not in self.revisions. That can happen if revision 0 is not in the visible subset of the revisions in the repository. Before Kallithea changeset 7c43e15fb8bc7a73f17f577e59a4698589b6809d, it was working by chance because start=0 was treated like start=None in the relevant places (GitRepository.get_changesets still does that). The intention of passing start=0 was seemingly to not limit the start. Therefore passing start=None (or nothing, as it’s the default value) should be correct. I got the following traceback before this change: Traceback (most recent call last): File "~/vcs/kallithea/kallithea/controllers/changelog.py", line 117, in index collection = c.db_repo_scm_instance.get_changesets(start=0, end=revision, File "~/vcs/kallithea/kallithea/lib/vcs/backends/hg/repository.py", line 529, in get_changesets start_pos = None if start is None else self.revisions.index(start_raw_id) ValueError: '4257f758b3eaacaebb6956d1aefc019afab956b8' is not in list

setup: support Mercurial 6.1 for continuously improved Python 3 support

hg: support Mercurial 6.1 without util.url

setup: support Mercurial 5.9 for continuously improved Python 3 support

hg: use mercurial.node.nullid directly - needed for 5.9 mercurial.commands.nullid was removed in d55b71393907.

webutils: monkeypatch to make webhelpers2 work with Python 3.10 Webhelpers2 is apparently a dead project and is using collections.Sequence directly.

setup: support Pytest 6.2 for Python 3.10 support https://github.com/pytest-dev/pytest/issues/8539

setup: support Bleach 4.2 for Python 3.10 support Changelog shows no significant API changes. Bleach 3.2 and later are however even more unreasonably paranoid than 3.1, and the test thus has to be updated and we stop supporting 3.1 .

setup: support FormEncode 2.0.0 for Python 3.10 support Changelog shows no problematic changes.

front-end: update package-lock.json Running "kallithea-cli front-end-build" with npm 7.21.1 gave: npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... and modified this file. Let's hope that change is stable.