Closed andrewjstone closed 1 year ago
I believe the right thing to do here is indeed to move the hubris code to syn@2
before pulling in MGS updates. However, it's unclear to me right now how hard this may be. We may end wanting to back out the dependabot update of zerocopy depending upon urgency/priorities.
I ran into this while trying to pull #121 into hubris and I expect @mkeeter to run into the same thing when he tries to integrate #116 into hubris.
The issue actually already existed with 9b39c775a3530d5b58cd208606c6e508216a60f1, which we also haven't pulled into hubris yet. To move along with my testing for #121, I temporarily reverted back to zerocopy@0.6.1
for now.
hubris
can stay on syn@1
(moving to syn@2
is still probably right at some point, but it doesn't have to be forced by this issue). The error you're running into is because derive-idol-err
needs the extra-traits
syn1 feature but didn't enable it; this previously worked because zerocopy-derive 0.3.1 enabled the feature for us.
https://github.com/oxidecomputer/hubris/pull/1524 fixes the missing feature and bumps to the latest main
MGS branch.
Thank you @jgallagher
Dependabot just pulled in
0.6.4
ofzerocopy
, which indeed is useful and fixes a soundness hole.Hubris has
zerocopy@0.6.1
. Bumping the hubris version to0.6.4
results in the newerzerocopy
pulling inzerocopy-derive@0.6.4
instead ofzerocopy-derive@0.3.1
that is pulled in withzerocopy@0.6.1
. Now, this wouldn't be much of a problem, except thatzerocopy-derive@0.6.4
pulls insyn@2
instead ofsyn@1
which is a major change, withsyn@1
being used by a number of hubris crates. We using workspace dependencies for everything and so at the end of doing a simple version bump forzerocopy
in hubrisCargo.toml
I get the fun error:If I try to also bump
syn
tov2
I get the following errors: