Skip to content

Commit 544f6d0

Browse files
LucaFgrThomasClausnitzer
LucaFgr
authored and
ThomasClausnitzer
committed
created JLS-54 to JLS-60
1 parent 693adb1 commit 544f6d0

7 files changed

Lines changed: 44 additions & 3 deletions

File tree

‎.dotstop.dot‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,13 @@ digraph G {
8282
"JLS-51" [sha="190e17d59795c9ed3b25a0a8bf57497de1e0d06ab90b3f6ba47b543c95edea43"];
8383
"JLS-52" [sha="8539f924c31974a2722615d2410a25336a5d6a9f399f16dc485be83f7f87a5ff"];
8484
"JLS-53" [sha="d9f7e732e34b0ec79305dde4c5b3d60906559ef1d90bc3ce2906e28a90293844"];
85+
"JLS-54" [sha="e1d713fcbd323526a04ea0c7f963a4425bab1567cc7d701546d29cb05f8ac92f"];
86+
"JLS-55" [sha="321c775e2acf0267ac1753eb772fedf1bcca18029714071c6e55d999f6dd008a"];
87+
"JLS-56" [sha="6fdd3ab1172c1df5658f140d104d51559080aa32389a5a842b93cfbd394593b3"];
8588
"JLS-57" [sha="6261b6cf44be2e742af1e1d687f1233161ab7cdaf6f1c0a6e31e671a7451adc5"];
8689
"JLS-58" [sha="dbdb83427fd82fd3be5e90ab761945a0346b33740b9ea80fd37122dfa6baaa60"];
90+
"JLS-59" [sha="2ac670fb73ace2f582d7351baf2ea3bbd16a00dbe01cc56997ff86b564d69840"];
91+
"JLS-60" [sha="035303bc28dfc2e2a80d5b4b9de3a45406508a0c5c27d511e676159db227d9b9"];
8792
"JLS-61" [sha="151f1cda2384ae4935d29d300c3424bca710378fa3689bbcff69b06dc86bb692"];
8893
"JLS-62" [sha="60848232c2989d0282b64792d7da7a57c04ff368d2ac9deae09c3743251dfc79"];
8994
"JLS-63" [sha="2b50e79c3b43c6815b5dc15c7909ce5fb513e98fadb28ddfa40938f20f5d0427"];
@@ -448,6 +453,11 @@ digraph G {
448453
"TA-FIXES" -> "JLS-28" [sha="0adb7ec9c6cc4338fa810442d22c8e4ca2a39cf33f0efaf859457ab32946991d"];
449454
"TA-FIXES" -> "JLS-33" [sha="56b526e261afa2da0793ec172850d227e4ed1d8c8a06e616c680c3db29648d45"];
450455
"TA-FIXES" -> "JLS-57" [sha="ada11447792ac70d2f87b81253379dd31d73eefa57554c9f0b1e067bf995812c"];
456+
"TA-INDICATORS" -> "JLS-54" [sha="b8d659e9fa897e4f13ceace28a2c71e38d41be22a52ca34162ca907c82e160fc"];
457+
"TA-INDICATORS" -> "JLS-55" [sha="0d048eab93d9d675bf346fb93b80a5af1b7752352b28e1b80b4b9e8b85e5fc3d"];
458+
"TA-INDICATORS" -> "JLS-56" [sha="a27def8655040fb7b0feb8c88ce79962442cd8f7fab0e64ec7a7ff576ff1b7e6"];
459+
"TA-INDICATORS" -> "JLS-59" [sha="cb6fadb815da01e8cf5624d69ddcb9d6dd0b6e9d9df2cc2f0c40810741cffe46"];
460+
"TA-INDICATORS" -> "JLS-60" [sha="fe0fdac1036e4ff8557ae5151f1516b4127644b03c778e8fff95e00b7aa6381c"];
451461
"TA-INPUTS" -> "JLS-04" [sha="262db6d430e99ef3a23645c93a1cc5bda1270ceba90b4d8cccb40b1eb85e9860"];
452462
"TA-INPUTS" -> "JLS-47" [sha="b2da62290125ecc680f953dde166bb5f22e7f8c6e7e53a73136102e01dd013a7"];
453463
"TA-INPUTS" -> "JLS-34" [sha="b39b1a808b02bfcd5450ffea835179c862c19f7759de0508bac9249c02db58c1"];

‎TSF/trustable/assertions/TA-CONSTRAINTS_CONTEXT.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -78,15 +78,15 @@ contradictions and obvious pitfalls within the defined Statements.
7878
- **Answer**: The existing set of AOUs provides effective guidance for consumers.
7979
- Do they provide clear guidance for upstreams on reusing components with
8080
well-defined claims?
81-
- **Answer**:
81+
- **Answer**: # currently unclear how to interpret this question
8282
- Are any Statements explicitly designated as not reusable or adaptable?
83-
- **Answer**:
83+
- **Answer**: No, all statements could theoretically be adapted or reused.
8484
- Are there worked examples from downstream or upstream users demonstrating
8585
these constraints in practice?
8686
- **Answer**:
8787
- Have there been any documented misunderstandings from users, and are these
8888
visibly resolved?
89-
- **Answer**:
89+
- **Answer**: Yes, it is documented that the [brace initialisation](https://json.nlohmann.me/home/faq/) (cf. AOU-06) regularly leads to confusion, cf. [here](https://github.com/nlohmann/json/issues/4898).
9090
- Do external users actively keep up with updates, and are they properly
9191
notified of any changes?
9292
- **Answer**: External users of the library are not necessarily automatically notified of an update, and are neither assumed nor required to keep up to date. If the external user forks the github repository, however, then github shows automatically whenever the upstream changes.

‎TSF/trustable/statements/JLS-54.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
level: '1.1'
3+
normative: true
4+
---
5+
6+
In eclipse-score/inc_nlohmann_json, a GitHub workflow continuously monitors the fraction of failing unit and integration tests on protected branches (e.g., main, release branches). If the failure rate exceeds a defined threshold over a configurable number of consecutive runs, the workflow blocks further merges to the affected branch, and restores the last known-good commit (last fully passing pipeline) as the default basis for integration and release.

‎TSF/trustable/statements/JLS-55.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
level: 1.1
3+
normative: true
4+
---
5+
6+
In eclipse-score/inc_nlohmann_json, a GitHub workflow tracks CI pipeline duration (build + tests) over time. If the median runtime increases beyond a defined relative threshold compared to a rolling baseline, the workflow flags the regression, blocks releases from the affected commit(s), and
7+
opens or updates an issue to investigate performance-related misbehaviours.

‎TSF/trustable/statements/JLS-56.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
level: 1.1
3+
normative: true
4+
---
5+
6+
In eclipse-score/inc_nlohmann_json, code coverage for unit and integration tests is measured on each CI run. If coverage for any protected branch decreases by more than a defined threshold relative to the previous release baseline, the workflow blocks merges that introduce the regression, and requires either a compensating test update or a documented justification approved by a Subject Matter Expert.

‎TSF/trustable/statements/JLS-59.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
level: 1.1
3+
normative: true
4+
---
5+
6+
In eclipse-score/inc_nlohmann_json, dependency and CVE status (including GitHub security alerts and Dependabot alerts) is monitored continuously. The presence of any unresolved critical or high-severity vulnerability relevant to nlohmann/json usage blocks new releases and integration of new changes triggers an issue or misbehaviour entry with mitigation actions (update, patch, or justified dismissal), and is tracked until mitigation is implemented and verified.

‎TSF/trustable/statements/JLS-60.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
level: 1.1
3+
normative: true
4+
---
5+
6+
In eclipse-score/inc_nlohmann_json, the rate of newly reported misbehaviours or bugs attributable to nlohmann/json (within S-CORE’s use cases) is tracked for each new version integrated. If the rate over a defined observation window exceeds a specified threshold compared to previous versions the affected version is no longer considered a known-good state integration is rolled back to the last known-good version.

0 commit comments

Comments
 (0)