Description
dtvem doctor tells me I need to reshim, but when I do, dtvem doctor keeps telling me I need to reshim.
Steps to Reproduce
- Have a user install on 0.5.3, upgrade to 0.6.1 (don't know if this is necessary, but it's what I was doing)
- Run
dtvem doctor
- Run
dtvem reshim
- See message about still needing to reshim.
Expected Behavior
I expect that after the reshim command, dtvem doctor would report all green.
Actual Behavior
See above
Operating System
Windows
dtvem Version
0.6.1
Go Version (if building from source)
No response
Which runtime is affected?
Not runtime-specific
Error Messages / Logs
dtvem doctor
⚠ Shim-map cache is out of sync with disk [fixable]
On disk, missing from cache: pytest, python3, ruff, virtualenv
Run `dtvem reshim` to rebuild the cache from the installed runtimes.
✓ All configured runtimes are installed
✓ Shims directory matches installed runtimes
✓ All installed runtime versions have their executable
✓ dtvem-shim binary is present
✓ dtvem shims directory is on PATH
✓ No stale dtvem shims entries in PATH
✓ No system runtimes ahead of dtvem on PATH
✓ Only one dtvem install location holds data
⚠ 1 non-error problem(s) found across 9 check(s)
Configuration
{
"node": "24.14.0",
"python": "3.13.11"
}
Additional Context
I ran some dtvem which and where.exe commands that may be useful
🕙 11:06:59 ❯ dtvem which ruff
✗ Unknown command: ruff
→ This command is not managed by dtvem
~
🕙 11:07:44 ❯ where.exe ruff
C:\Users\Brad\.local\share\dtvem\shims\ruff.cmd
C:\Users\Brad\.local\share\dtvem\shims\ruff.exe
~
🕙 11:07:47 ❯ ruff --help
dtvem shim error: runtime provider not found: runtime provider 'ruff' not found
~
🕙 11:07:57 ❯ dtvem which virtualenv
✗ Unknown command: virtualenv
→ This command is not managed by dtvem
~
🕙 11:08:17 ❯ virtualenv --version
dtvem shim error: runtime provider not found: runtime provider 'virtualenv' not found
~
🕙 11:08:24 ❯ where.exe virtualenv
C:\Users\Brad\.local\share\dtvem\shims\virtualenv.exe
Code of Conduct
Description
dtvem doctortells me I need to reshim, but when I do,dtvem doctorkeeps telling me I need to reshim.Steps to Reproduce
dtvem doctordtvem reshimExpected Behavior
I expect that after the
reshimcommand,dtvem doctorwould report all green.Actual Behavior
See above
Operating System
Windows
dtvem Version
0.6.1
Go Version (if building from source)
No response
Which runtime is affected?
Not runtime-specific
Error Messages / Logs
Configuration
{ "node": "24.14.0", "python": "3.13.11" }Additional Context
I ran some
dtvem whichandwhere.execommands that may be usefulCode of Conduct