Can someone tell me how to fix CI to pass?

The failing CI job is right to fail: it's indicating that pulling in the new library requires new vetting. One of the core team members will have to do acargo vet.

I'm tagged as reviewer here but I have some high-priority stuff on my plate at the moment so it may not be until sometime next week when I get to this, sorry!

Understand. Thank you!

@tamaroning I think this needs a Cargo.lock update as well (see the CI failures); would you mind doing that by doingcargo check orcargo build and then adding the updates as a new commit? (Please do not alter my vet commit;0da9d0b needs to remain on this branch.)

Hi, I rancargo update at your commit but nothing in Cargo.lock changed.
Do you meancargo update?

Hi, I rancargo update at your commit but nothing in Cargo.lock changed. Do you meancargo update?

No, I didn't meancargo update -- that pulls in new versions that require more vets. Would you mind force-pushing back to the prior commit to remove your latest one? (i.e., start from0da9d0b again)

Please see the CI job failurehere: that is showing that after running severalcargo check commands on different crates, the lockfile is modified. You'll need to reproduce that and then create a new, separate commit on top with those changes.

Hi, I reset my local branch to0da9d0b and ran allcargo check ...s and./ci/vendor-wit.sh in the Monolith checks CI, but could not reproduce the diff in Cargo.lock.
Am I missing something?

Hmm, I wasn't able to reproduce that either. I re-triggered the CI jobs to see if it was some transient version issue (e.g. maybe a release ofsmallvec happened partway through the run or something?).

OK, that didn't work, and the new failures don't seem reproducible either. I think at this point I need to ask our resident CI herder@alexcrichton (when he's back in office) for help...