fix(third-party): cap lints on vendored wait-timeout #36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "patman/wait-timeout-cap-lints"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What this does
Adds a reindeer fixup capping lints (
--cap-lints=allow) on the vendoredwait-timeout 0.2.1crate.wait-timeoutcarries#![deny(warnings)]; rustc 1.96 introduced thefunction_casts_as_integerlint (implied bydeny(warnings)), which turns asigchld_handler as usizecast in itsunix.rsinto a hard error. This broke everybuck2 testtarget, sinceproptestpullswait-timeoutin transitively via itsfork/timeoutfeatures. The library (//common:common) was unaffected.Capping lints on the vendored crate is the standard fix — we should not enforce our lint policy on third-party code.
Stack position
PR 1 of 2. Next:
feat(units): back unit newtypes with uom, which depends on this so its tests can run.Review focus
The one-line fixup; regenerated
BUCKaddsrustc_flags = ["--cap-lints=allow"]to the wait-timeout target.