-
Couldn't load subscription status.
- Fork 6
chore(deps): Update to 5.0 pre-release of copier template #1214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Issues:
|
31887f4 to
e9fb90f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1214 +/- ##
=======================================
Coverage 94.73% 94.73%
=======================================
Files 41 41
Lines 2638 2638
=======================================
Hits 2499 2499
Misses 139 139 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
81abb40 to
2b35608
Compare
2b35608 to
78b9411
Compare
Uses uv for python management
835eaaa to
2f4b970
Compare
Re-using the user's local cache means invalid links get created
Once the uv cache has been set up, configuring the pre-commit hooks takes the most significant amount of time building the container. Using a shared volume for the pre-commit cache as well takes the devcontainer re-build time from ~1m10s to ~10s.
Convenience trumps consistency This reverts commit 95b8c2e.
2f4b970 to
5cf85d6
Compare
| // Keep a persistent cross container cache for uv, pre-commit, and the venvs | ||
| { | ||
| "source": "persistent-uv-cache", | ||
| "target": "/root/.cache/uv", | ||
| "type": "volume" | ||
| }, | ||
| // ...and for pre-commit | ||
| { | ||
| "source": "persistent-pre-commit-cache", | ||
| "target": "/root/.cache/pre-commit", | ||
| "type": "volume" | ||
| } | ||
| // Use a volume mount for the uv venv so it is local to the container | ||
| { | ||
| "target": "/workspaces/${localWorkspaceFolderBasename}/.venv", | ||
| "source": "devcontainer-shared-cache", | ||
| "type": "volume" | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been changed upstream to use a single cache for everything, do we want to keep in sync with that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, with the envvars set above this does need to change one way or the other
Uses uv for python management