Skip to content

Conversation

@p-r-a-v-i-n
Copy link

Summary

  • Completed the logic where TODO comments were present in PlanScheduler.
  • Added handling for mechanism types (singleton and multi) based on mechanism name.
  • Updated the scheduling process to discard duplicate or invalid plans.

Question

I added this mapping for mechanism types:
MECHANISM_TYPE = { "cpu_freq": "singleton", "component_placement": "multi" }

Are these mechanism names and their types correct, or do we need to update/add more?

@netlify
Copy link

netlify bot commented Jul 27, 2025

Deploy Preview for mlsysops ready!

Name Link
🔨 Latest commit c85e2d5
🔍 Latest deploy log https://app.netlify.com/projects/mlsysops/deploys/68870e403b38c1000819ef52
😎 Deploy Preview https://deploy-preview-42--mlsysops.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

…iscard logic

- Added MECHANISM_TYPE mapping for singleton vs multi-instance mechanisms
- Implemented discard logic for conflicting mechanisms and inactive applications
- Replaced TODOs in PlanScheduler with concrete logic
- Added is_plan_app_active() helper in MLSState
- Improved logging clarity for scheduled and discarded plans

Signed-off-by: Pravin Kamble <iampbkamble@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant