Package install release-age cutoffs breaking installs on mirrors and plugins
NousResearch/hermes-agent · cluster 119704 · gateway
Data as of
Nothing open on GitHub. Fix merged in #137110. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #137110. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Members all concern dependency installation in Hermes being affected by a release-age/exclude-newer cutoff, including Tornado for Telegram lazy install, mirrors without upload times, and plugin dependency handling. Some titles reference a regression from #137110 and a change in where release age is checked, but the exact relationships between items are not fully established by the titles alone.
Open issues0
Open PRs0
Fixes on record
-
#137110 Plugin installs work on any package mirror: release age is checked when Hermes locks (3 days), not on users' machines (#135589)
files:
plugin-catalog/README.md,pm/AGENTS.md,pm/environment.py,pm/workspace.py,pyproject.toml,tests/pm/test_workspace.py,tests/pm/test_workspace_build_inputs.py,tests/test_packaging_metadata.py,website/docs/developer-guide/plugins/catalog-submission.md,website/docs/developer-guide/plugins/index.md,website/docs/reference/package-management.md -
#137159 Core-only installs and hermes update work again on mirrors without upload times (regression from #137110)
files:
pm/workspace.py,tests/pm/test_workspace.py -
#137405 Five catalog plugins install again: plugins may move Hermes's non-pinned dependencies (regression from #137110)
files:
plugin-catalog/README.md,pm/AGENTS.md,pm/workspace.py,tests/pm/test_workspace.py,tests/pm/test_workspace_build_inputs.py,website/docs/developer-guide/plugins/catalog-submission.md,website/docs/developer-guide/plugins/index.md,website/docs/reference/package-management.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#119711 fix: exempt Tornado from Telegram lazy install cutoff · done elsewhere →
#137110,#137159,#137405,#119704
Closed issues · 1
- Closed#119704[Bug]: Lazy install of platform.telegram hard-fails on pip.conf-mirrored indexes — exclude-newer quarantines every tornado release ("there are no versions of tornado")
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab