Skip to content

Extract OmegaConf resolver registration into shared utility#47

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/fix-randbits-resolver-issue
Draft

Extract OmegaConf resolver registration into shared utility#47
Copilot wants to merge 2 commits intomainfrom
copilot/fix-randbits-resolver-issue

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 15, 2026

predict.py fails with an unknown resolver error when loading saved configs containing ${randbits:...} or ${slug:...} interpolations, because only train.py registered those resolvers.

  • Extract slug, len, and randbits resolver registration from train.py into src/muonly/utils/resolvers.py as a shared register_resolvers() function
  • Call register_resolvers() at module level in both train.py and predict.py
  • Use replace=True on all resolvers so repeated calls are safe

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • astral.sh
    • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Move custom resolver registration (slug, len, randbits) from train.py
into src/muonly/utils/resolvers.py and call it from both train.py and
predict.py to fix unknown resolver errors when loading saved configs.

Agent-Logs-Url: https://github.com/cms-kr/DeepMuonReco/sessions/e352cbc8-c6f4-404a-9a7c-179355774a13

Co-authored-by: slowmoyang <20718100+slowmoyang@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix unknown resolver error in predict.py for randbits resolver Extract OmegaConf resolver registration into shared utility Apr 15, 2026
Copilot AI requested a review from slowmoyang April 15, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

any better way of handling resolvers across different scripts?

2 participants