bug(versioned): Fix tracking impls across multiple containers for the same version
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
The payload names no files, so start by searching the repository for ChangedValue and the per-version tracking impls that remove entries after an upgrade or downgrade. Check where JSON path matching panics on unmatched paths. Done means an entry is removed only once its list is empty, and unmatched paths are skipped. A test with two containers sharing one version should cover both cases.
Written by the indexing model from the issue text.
Description
Discovered in #1294.
- The tracking impls per each container assume they are the only container which need to access to
ChangedValues' upgrades and/or downgrades and currently removes the list ofChangedValuefor a particular version. The code must only remove the entire entry once the list inside is empty. Otherwise, other containers won't be able to access the tracked changes. - Each tracking impl only looks and removes the changes which matched to the expected JSON path. Unmatched JSON paths currently lead to a panic. They should instead be ignored.
I'm interested to work on this.
- Dominant language
- Rust
- Stars
- 169
- Forks
- 20
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from stackabletech/operator-rs
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stackabletech/operator-rs#1301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stackabletech/operator-rs#1273 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/operator-rs#1077 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/operator-rs#1063 ·
Maintainers usually reply within 1 day
-
stackable-versioned: Require inner module definitions to have the same visibility as the parentOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/operator-rs#1028 ·
Maintainers usually reply within 1 day
All issues in stackabletech/operator-rs
Similar issues
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day
-
bug documentation sev-0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1620 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100