ChimeraTK / ChimeraTK/ControlSystemAdapter
Persistency Layer: backup file before updating
Open
Nobody has claimed this yet.
redmine
- Dominant language
- C++
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The output file of the persistency layer should be renamed before it is written again, so there is a backup in case the new file is corrupted (e.g. because the process is killed in the process of writing).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test path is named. Start by locating the persistency layer and its output-file update path, then determine how interrupted writes are currently handled. Done means an existing output file has a backup before it is rewritten and the behavior is covered by the relevant persistence tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100