fix: do not constrain resources in remote jobs#87
Conversation
📝 WalkthroughWalkthroughThe change removes the inclusion of resource declarations from the command-line arguments generated for jobs in the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant RealExecutor
participant Job
User->>RealExecutor: get_job_args(Job)
RealExecutor->>Job: retrieve CLI arguments (without resource declarations)
RealExecutor-->>User: return job CLI arguments
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
💤 Files with no reviewable 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 mindful 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 (
|
Previously, the jobs resource usage was used to define global resource constraints for the remote job. This is (a) not necessary, since the remote job comes with its own resources anyway, and (b) can cause errors in case of pipe groups, where the consuming job does not yet have e.g. a defined memory usage if the memory is determined at runtime, such that it cannot be considered when calculating the resource constraints for the remote job.