-
Notifications
You must be signed in to change notification settings - Fork 452
fix(extension/podman): ensure loop of monitoring can be started at activation of extension #13275
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
fix(extension/podman): ensure loop of monitoring can be started at activation of extension #13275
Conversation
…tivation of extension Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com>
📝 WalkthroughWalkthroughThe changes include setting the internal variable Possibly related PRs
Suggested labels
Suggested reviewers
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
extensions/podman/packages/extension/src/extension.spec.tsOops! Something went wrong! :( ESLint: 9.31.0 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'svelte-eslint-parser' imported from /eslint.config.mjs 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be min 8000 dful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
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.
Some tests are failing
I am investigating! It seems like there are side effects between tests in the extension.spec.ts file because they run individually. |
Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com>
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.
Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
…tivation of extension (podman-desktop#13275) * fix(extension/podman): ensure loop of monitoring can be started at activation of extension Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com> * test: fix instability Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com> * test: good practice to make sure called even failed test Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com> --------- Signed-off-by: Simon Rey <sfbrey+eqqe@gmail.com>
What does this PR do?
This PR is made to prepare another PR where the monitoring loop is tested. The stop loop is activated in the deactivate method, but it is not desactivated in the activate method. So the test cannot be run as the global stop loop can be modified from another test.
Screenshot / video of UI
What issues does this PR fix or reference?
https://github.com/podman-desktop/podman-desktop/pull/13153/files/ec5af1256af8c61821c3b277af26f5c553cba34d#r2215571950
How to test this PR?