andygrove opened a new issue, #2420:
URL: https://github.com/apache/datafusion-ballista/issues/2420
## Describe the bug
The `msrv dependency check` job fails on every PR that touches a manifest:
```
error: cannot find macro `vec` in this scope
--> tinyvec-1.13.0/src/tinyvec.rs:710:21
|
710 | TinyVec::Heap(vec![A::Item::default(); len])
| ^^^
note: `vec` is imported here, but it is a module, not a macro
--> tinyvec-1.13.0/src/tinyvec.rs:3:18
|
3 | use alloc::vec::{self, Vec};
error: could not compile `tinyvec` (lib) due to 1 previous error
```
`tinyvec 1.13.0` shadows its own `vec!` macro with a module import, so it
does not build without `std`. It was published 2026-09-03T21:13:39Z; the same
branch was green at 16:10Z and started failing at 22:13Z.
## To Reproduce
```sh
cd dev/msrvcheck && cargo run
```
Or, minimally, any crate depending on `tinyvec = "=1.13.0"` with the `alloc`
feature. Reproduced on stable 1.97.0. `1.12.0` builds fine.
## Expected behavior
`msrv dependency check` passes.
## Additional context
Only that job is affected. `tinyvec` reaches it transitively through the
`cargo` crate, and `dev/msrvcheck/.gitignore` ignores `Cargo.lock`, so `cargo
run` re-resolves from crates.io on every CI run and picked up 1.13.0 as soon as
it was published. The workspace itself is unaffected: our checked-in
`Cargo.lock` pins `tinyvec 1.12.0`.
Fix is a pin in `dev/msrvcheck/Cargo.toml`, matching the one already there
for `time`. It can be dropped once upstream ships a fix.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
