Rework of component requirements related to snapshots

[tizava]

• Snapshots are now explicit (Driven by the users)
• Snapshots are created from live data (Not from data flushed to disk)
• New API to acquire status of the snapshot slot (Occupied/Free)
• General rework and cleanup

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 84e7b4c7-ab48-493b-a5e6-25f71e6113b9
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 3 packages loaded
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)

Analyzing: target //:license-check (36 packages loaded, 10 targets configured)

Analyzing: target //:license-check (80 packages loaded, 10 targets configured)

Analyzing: target //:license-check (138 packages loaded, 1378 targets configured)

Analyzing: target //:license-check (139 packages loaded, 2712 targets configured)

Analyzing: target //:license-check (139 packages loaded, 2712 targets configured)

Analyzing: target //:license-check (139 packages loaded, 2712 targets configured)

Analyzing: target //:license-check (153 packages loaded, 6160 targets configured)

Analyzing: target //:license-check (156 packages loaded, 8084 targets configured)

Analyzing: target //:license-check (156 packages loaded, 8084 targets configured)

Analyzing: target //:license-check (156 packages loaded, 8084 targets configured)

Analyzing: target //:license-check (161 packages loaded, 8133 targets configured)

Analyzing: target //:license-check (161 packages loaded, 8133 targets configured)

Analyzing: target //:license-check (164 packages loaded, 10021 targets configured)

Analyzing: target //:license-check (164 packages loaded, 10021 targets configured)

Analyzing: target //:license-check (164 packages loaded, 10021 targets configured)

Analyzing: target //:license-check (165 packages loaded, 10145 targets configured)

INFO: Analyzed target //:license-check (166 packages loaded, 10271 targets configured).
[14 / 17] Generating Dash formatted dependency file ...; 0s disk-cache, processwrapper-sandbox ... (2 actions, 1 running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 66 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[16 / 17] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 41.507s, Critical Path: 2.08s
INFO: 17 processes: 12 internal, 4 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 17 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[PandaeDo]

Please have a look again on the requirements. It seems to me that they are not fully atomic. You can use https://eclipse-score.github.io/process_description//main/process_areas/requirements_engineering/guidance/requirements_templates.html#gd_temp__req_formulation and also the question if the requirement is testable. Understandable they are.

[anmittag]

@tizava there are checks failing, please adapt and review comments. please care

[umaucher]

Suggested change

	The component shall create a new snapshot in the selected snapshot slot when the slot is empty.
	The component shall create a new snapshot in the selected snapshot slot when the slot is empty or return an error.

this should be defined for all API's handling snapshots

[tizava]

Fixed with last commit

[PandaeDo]

My findings are solved

[umaucher]

changed / new requirements needs to be tagged as valid

[tizava]

Fixed with last commit