One non-object JSON record makes the session catalog exit
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
The payload names no files, so start from the code path behind corecoder --list-sessions and find where each saved .json entry is read and .get is called on it. Reproduce with a temporary home containing one valid session and one file whose contents are [], then make the catalog skip any record that does not decode to a JSON object. The load-by-ID path should route the same non-object case into the existing invalid-session/not-found result rather than raising TypeError. Done when both commands leave the files untouched, the valid session still lists, and resuming the bad entry returns the not-found result.
Written by the indexing model from the issue text.
Description
In the published 0.14.0 wheel, corecoder --list-sessions lists a valid saved session as expected. If the same directory also contains a .json file whose contents are [], the command exits with AttributeError: 'list' object has no attribute 'get' and never shows the valid session. Loading the non-object record by ID raises TypeError instead of returning the existing not-found result.
Both checks were done with a fresh temporary home and fixture files, with no provider key. The catalog should skip records that are not JSON objects, and resuming one should follow the existing invalid-session path. Neither command should rewrite the entries.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 453
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 he-yufeng/CoreCoder
-
Difficulty 1/5 Under an hour Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-3 hours Newbie friendliness 25/100
he-yufeng/CoreCoder#62 · 1 comment ·
Maintainers usually reply within 1 day
-
学完之后的实践Open
Difficulty 1/5 Under an hour Newbie friendliness 25/100
he-yufeng/CoreCoder#49 · 2 comments ·
Maintainers usually reply within 1 day
-
Roadmap: where CoreCoder goes after v0.8.0Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
he-yufeng/CoreCoder#40 · 2 comments ·
Maintainers usually reply within 1 day
All issues in he-yufeng/CoreCoder
Similar issues
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
gke-labs/kube-agents#6620 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#34719 · 2 comments ·
Maintainers usually reply within 1 day
-
cognition
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
collabnix/awesome-mcp-lists#433 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day