Update uv.lock to fix test environment#19
Update uv.lock to fix test environment#19google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
- Run `uv sync --extra dev` to generate/update `uv.lock`. - Verified that all 112 tests pass with the correct environment. - This ensures reproducible builds and working test collection.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
This change updates the
uv.lockfile to ensure all dependencies, including development dependencies likepytestandhypothesis, are correctly pinned and resolvable. This fixes the issue where tests were failing to collect due to missing modules. Verified the fix by running the full test suite, which passed successfully.PR created automatically by Jules for task 13134438090875513011 started by @rager306