Conversation
Bump grpcio 1.83.0 → 1.83.1, grpcio-reflection 1.74.0 → 1.83.1, protobuf 6.31.1 → 7.36.1, googleapis-common-protos 1.70.0 → 1.75.3. Fix shell_test.py to pass grpc.aio.Metadata() instead of None for AioRpcError initial_metadata/trailing_metadata parameters. The constructor requires Metadata objects; passing None worked at runtime but fails stricter type checking.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe test now passes empty ChangesRPC test update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This PR updates dependencies and corrects test metadata construction without introducing an actionable production or test-path risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the RPC trail Comment |
- qdl/driver.py: fix import sorting (I001), reduce complexity of _prepare_cached_flash and _stream_to_tar by extracting helpers (_clear_cache, _try_cache_hit, _collect_source_metadata, _flush_tar_buffer) - qdl/schema.py: fix line too long in _parse_step (E501) - shell_test.py: pass grpc.aio.Metadata() instead of None for AioRpcError initial/trailing_metadata (same fix as PR #1087) - client/base.py: guard close() against missing 'stack' attribute to prevent PytestUnraisableExceptionWarning on Python 3.14 when objects are created via object.__new__() in tests Co-authored-by: Cursor <cursoragent@cursor.com>
- qdl/driver.py: fix import sorting (I001), reduce complexity of _prepare_cached_flash and _stream_to_tar by extracting helpers (_clear_cache, _try_cache_hit, _collect_source_metadata, _flush_tar_buffer) - qdl/schema.py: fix line too long in _parse_step (E501) - client/base.py: guard close() against missing 'stack' attribute to prevent PytestUnraisableExceptionWarning on Python 3.14 when objects are created via object.__new__() in tests Note: type-check-python failure (shell_test.py AioRpcError Metadata types) is a pre-existing issue caused by the ty type checker getting stricter -- not by library changes. PR #1087 addresses this properly. Co-authored-by: Cursor <cursoragent@cursor.com>
- qdl/driver.py: fix import sorting (I001), reduce complexity of _prepare_cached_flash and _stream_to_tar by extracting helpers (_clear_cache, _try_cache_hit, _collect_source_metadata, _flush_tar_buffer) - qdl/schema.py: fix line too long in _parse_step (E501) - client/base.py: guard close() against missing 'stack' attribute to prevent PytestUnraisableExceptionWarning on Python 3.14 when objects are created via object.__new__() in tests Note: type-check-python failure (shell_test.py AioRpcError Metadata types) is a pre-existing issue caused by the ty type checker getting stricter -- not by library changes. PR #1087 addresses this properly. Co-authored-by: Cursor <cursoragent@cursor.com>
|
thank you! |
Summary
Targeted dependency update for gRPC-related packages and a preventive type fix in
shell_test.py.Changes
Dependency updates (
uv.lock)grpcio1.83.0 → 1.83.1grpcio-reflection1.74.0 → 1.83.1protobuf6.31.1 → 7.36.1googleapis-common-protos1.70.0 → 1.75.3Type fix (
shell_test.py)grpc.aio.Metadata()instead ofNoneforAioRpcErrorinitial_metadata/trailing_metadataparameters.Metadataobjects;Noneworked at runtime but fails under stricter type checking (e.g. when the type checker or stubs are upgraded).Context
Discovered while rebasing #1080 — the
uv.lockconflict resolution triggered a full lock regeneration which upgraded transitive deps and surfaced this latent type issue. This PR applies the fix proactively so future lock refreshes don't break CI."