You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clippy doesn't like the highest_priority_action_first and equal_priority_earliest_first tests in cas/scheduler/tests/action_messages_test.rs. I'm not sure what these tests are trying to test. Is this about Ord? Would testing something like assert!(first_action < current_action) or similar also work?
Removes needless overoptimization of strings for DigestInfo #174 The GetFinishedResult in cas/worker/tests/utils/mock_running_actions_manager.rs pointed out that the largest GetFinishedResult variant contains at least 496 bytes. It's talking about ActionResult here. I'd expect this to be fairly large but should it really be this large at all times?
We "hold a RefCell reference across an await point" in cas/store/tests/filesystem_store_test.rs L731. Seems like something is wrong there.
We "hold a RefCell reference across an await point" in cas/store/tests/filesystem_store_test.rs L731. Seems like something is wrong there.
I ended up disabling this warning. I tried to turn it into a mutex but it didn't help, it just gave another clippy error. In this case the reason it's complaining is because we "might" deadlock because we are calling an async function while we hold a lock (for mutex). The RefCell is complaining because technically multiple people can mutate the object in random places in the code without a clear code path of where all has mutable references. Granted this would all happen on the same thread (because Rc is not Send). All it's trying to do is make sure that the promise is still pending and the way it does this is by wrapping the future in another future temporary and calling pretty much calling await on it... This allows the outer future to get a context and then it calls .poll() on the inner future, and returns the Polling results. In this case it's a test and I don't see a direct way to fix this without turning off the warning.
The GetFinishedResult in cas/worker/tests/utils/mock_running_actions_manager.rs pointed out that the largest GetFinishedResult variant contains at least 496 bytes. It's talking about ActionResult here. I'd expect this to be fairly large but should it really be this large at all times?
FYI #174 almost certainly is going to trigger many places where we call .clone() but it's trivial copyable now, so we'll need to re-run clippy on many directories that were already fixed.
Activity
allada commentedon Jul 12, 2023
Try and hold off on the scheduler stuff until @chrisstaite-menlo has landed his changes.
allada commentedon Jul 12, 2023
I ended up disabling this warning. I tried to turn it into a mutex but it didn't help, it just gave another clippy error. In this case the reason it's complaining is because we "might" deadlock because we are calling an async function while we hold a lock (for mutex). The
RefCellis complaining because technically multiple people can mutate the object in random places in the code without a clear code path of where all has mutable references. Granted this would all happen on the same thread (becauseRcis notSend). All it's trying to do is make sure that the promise is still pending and the way it does this is by wrapping the future in another future temporary and calling pretty much calling await on it... This allows the outer future to get a context and then it calls.poll()on the inner future, and returns thePollingresults. In this case it's a test and I don't see a direct way to fix this without turning off the warning.allada commentedon Jul 12, 2023
Hmmm, I can do some simple math on this:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=29c3e096a14d764a417e3197f19c6801
Sums to 460, so yeah, my math is probably off a little because of
DigestInfo'sLazyTransform.allada commentedon Jul 12, 2023
FYI #174 almost certainly is going to trigger many places where we call
.clone()but it's trivial copyable now, so we'll need to re-run clippy on many directories that were already fixed.aaronmondal commentedon Jul 15, 2023
Closed by #182 Onwards to pedantic 🤣 🎉 🥳 🎈 🍰
small_blob_dispatcher: drainer + register_worker + TLA+ spec
task TraceMachina#168: SmallBlobDispatcher integration plumbing (part…
small_blob_dispatcher_test: TDD failing tests for unpin_on_disconnect…
small_blob_dispatcher: delete pin_ttl + add unpin_on_disconnect (Trac…