Skip to content

RLIMIT support - part 3 - #868

Open
NicolasFussberger wants to merge 6 commits into
eclipse-score:mainfrom
etas-contrib:rlimit_part3
Open

NicolasFussberger wants to merge 6 commits into
eclipse-score:mainfrom
etas-contrib:rlimit_part3

Conversation

@NicolasFussberger

@NicolasFussberger NicolasFussberger commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

This is the last PR for adding rlimit support.
It makes the rlimits configurable via json and adds a component/feature-integration test for all rlimits.

See previous PRs:
#847
#845

@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-868: https://eclipse-score.github.io/lifecycle/pr-868/

Comment thread tests/integration/sandbox_options/BUILD Resolved
// Scheduling priority for the component's initial thread.
scheduling_priority:int32 = null; // required

// to be removed - only here for compatibility but values will be ignored

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think this removal should be mentioned in a release note? I guess it's not really a breaking changes since it wasn't used but a users build could fail if they did set this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it would also be good to increase the schema version due to this change?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah think we should maybe start honoring that. Might also be good to keep git tags for the config? so that external tools can reference the raw schema file?

e.g. something like cfg-schema-vX
so then a link like this would never change:
https://raw.githubusercontent.com/eclipse-score/lifecycle/refs/tags/cfg-schema-v1/score/launch_manager/src/daemon/src/configuration/config_schema/launch_manager.schema.json

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could be an idea. I guess at the current stage it might be enough to use the release tag?
I assume we will keep changing the schema for each upcoming release

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that would work too.

Comment thread tests/integration/sandbox_options/BUILD Resolved

This branch was successfully deployed

1 active deployment
workflow-approval — 85de26ba Deployed Oct 30, 2026 by NicolasFussberger via Build and test unit-tests-arm64-qnx / approval #1984
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants