Skip to content

Comments

prepare release 0.9.0#2293

Merged
sylvestre merged 1 commit intomozilla:mainfrom
sylvestre:new-upstream-release
Dec 9, 2024
Merged

prepare release 0.9.0#2293
sylvestre merged 1 commit intomozilla:mainfrom
sylvestre:new-upstream-release

Conversation

@sylvestre
Copy link
Collaborator

No description provided.

@sylvestre sylvestre requested a review from lissyx December 9, 2024 09:05
Copy link
Collaborator

@lissyx lissyx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@Xuanwo Xuanwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you @sylvestre for working on this!

@sylvestre sylvestre merged commit ac3bff7 into mozilla:main Dec 9, 2024
@sylvestre
Copy link
Collaborator Author

my pleasure :)

@sylvestre sylvestre deleted the new-upstream-release branch December 9, 2024 10:52
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (0cc0c62) to head (21bcf00).
Report is 119 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #2293       +/-   ##
==========================================
- Coverage   30.91%       0   -30.92%     
==========================================
  Files          53       0       -53     
  Lines       20112       0    -20112     
  Branches     9755       0     -9755     
==========================================
- Hits         6217       0     -6217     
+ Misses       7922       0     -7922     
+ Partials     5973       0     -5973     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

tottoto pushed a commit to tottoto/sccache that referenced this pull request Feb 6, 2026
The boxed `Decoder` inside `Streaming` need not be `Sync` since
hyperium/tonic#804.  Unfortunately, that makes
`Streaming` non-`Sync`, meaning that all the generated `tonic` futures
cannot be awaited in `Sync` futures.

In fact, the only times we use the `Decoder`, we have a `&mut` unique
reference to it, so we are guaranteed not to require synchronization.

The `sync_wrapper` crate encodes this reasoning, allowing us to safely
make the `Streaming` type `Sync` regardless of whether the contained
`Decoder` is `Sync` or not.
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.

4 participants