ok Clippy you are drunk... running clippy locally I get directed one way .. running on github .. I am told to back it out...

dang it clippy! I'll see what's up with the ci, maybe some nightly vs. stable difference.

I would like to reopen this ... until we get consitency.
I tend to keep up setup upto date .. but that is just a naive way of saying "works on my machine"

cargo version -v

cargo 1.86.0 (adf9b6ad1 2025-02-28)
release: 1.86.0
commit-hash: adf9b6ad14cfa10ff680d5806741a144f7163698
commit-date: 2025-02-28
host: x86_64-unknown-linux-gnu
libgit2: 1.9.0 (sys:0.20.0 vendored)
libcurl: 8.12.0-DEV (sys:0.4.79+curl-8.12.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 24.4.0 (noble) [64-bit]

rustc --version
rustc 1.86.0 (05f9846f8 2025-03-31)

So it look like a sticky cache issue?

I generated 3 single issue PRs fixing 3 unrelated issues...

#184 #185 #186

Now all those test runs report a clippy failure which will be fixed by this PR.

"Something got clogged in the pipes."

it looks like there is another one here: src\io\scene.rs:179:22

Thanks, fixed