Implement queue for run target requests

Open
#643 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

First review the control client’s activate_run_target path and the queue behavior documented for run target requests, after confirming that #489 has been merged. Trace how force = true is currently handled and identify the existing request or queue tests. Done means force = false requests are queued while the documented force behavior remains intact.

Written by the indexing model from the issue text.

Description

com enhancement

[!NOTE]

This is only relevant once #489 is merged.

What

Currently, the control client can only call activate_run_target with force = true.

We should support force = false, which is the default, and queue the requests as documented.

Acceptance Criteria (DoD)
  • Requests made through activate_run_target with force = false are queued
How

No response

Dominant language
C++
Stars
6
Forks
34
Avg merge
2d 6h
Merged PRs (30d)
91

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/lifecycle

All issues in eclipse-score/lifecycle

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.