-
Notifications
You must be signed in to change notification settings - Fork 135
fix(pegboard): fix manager tests #2286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
d967870 to
5852e82
Compare
e9a7eb9 to
5852e82
Compare
Merge activity
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This PR fixes manager tests by updating actor handling with a new (Uuid, u32) key and streamlining Dockerfile and test configurations.
• In packages/edge/infra/client/manager/src/ctx.rs, actors are now stored using (Uuid, u32), converting i64 to u32, so ensure generation values are within range.
• In packages/edge/infra/client/echo/Dockerfile, the cache mount path is updated and the directory change removed—verify correct Cargo.toml detection.
• In packages/edge/infra/client/manager/tests/common.rs, tests now include an explicit generation (0) and remove the owner field, aligning with updated client configuration.
• In packages/edge/infra/client/manager/tests/container_lifecycle.rs, actor state tests now expect a tuple key; check the Exited state assertion for consistency in error messaging.
4 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->

Changes