det/CICS: fileKey folds every ZC##FILE onto one store; ZECS003 under ZC02 deletes records the COBOL leaves alone
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
Start in fileKey(), where the ZC.+FILE pattern maps every ZC##FILE name onto one store, and read test_template_file_lineage_4771.py, which pins that regex. Reproduce with the transid-zc02 scenario: with only ZC01FILE present, the COBOL READ should return FILENOTFOUND and delete nothing. Done means ZC02 no longer reaches the ZC01 store, and READ responses are included in the event comparison. This touches the #4771 design, so check with maintainers before changing the regex.
Written by the indexing model from the issue text.
Description
ZECS003 as transaction ZC02, with only ZC01FILE in the region: the COBOL gets READ FILENOTFOUND (resp 12, resp2 1) and deletes nothing. The port's fileKey() matches ZC.+FILE, reaches the ZC01 store and deletes the expired records. Reproduced twice, scenario transid-zc02. test_template_file_lineage_4771.py pins the regex, so this is a limit of the #4771 design.
Reading, not run: every instance collapses onto one store, so one instance's expiry would delete another's records. Also, the report says 6 of 6 events equal although READ answered differently: a READ's response may not be in the event comparison.
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
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 squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
strawberry-graphql/strawberry#4794 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dataforgoodfr/cetolog#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btclib-org/btclib#2932 ·
Maintainers usually reply within 1 day