"The lock count should never be negative" after Clean Sum of Bests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
No source file, test, or entry point is named in the report. Reproduce the Clean Sum of Bests flow with a re-routed run, then trace the edit-screen transition and verify that the splits file and displayed Sum of Bests reflect the accepted cleanup without a negative lock count.
Written by the indexing model from the issue text.
Description
I am trying to use "Clean Sum of Bests" on a splits file for a run that recently had a re-route. Whether or not I accept the suggested cleanups, the splits file is not correctly updated and I see "The lock count should never be negative" when going back from the edit screen to the main screen.
The splits file does show in the UI as edited but afaik nothing has actually changed and the cleanups are not reflected in the Sum of Bests displayed on my splits.
- Dominant language
- TypeScript
- Stars
- 302
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
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 LiveSplit/LiveSplitOne
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
LiveSplit/LiveSplitOne#1165 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
LiveSplit/LiveSplitOne#1162 ·
-
enhancement suitable for contributions UI
Difficulty 5/5 Over a week Newbie friendliness 35/100
LiveSplit/LiveSplitOne#1139 ·
-
enhancement suitable for contributions UI
Difficulty 4/5 3-5 days Newbie friendliness 45/100
LiveSplit/LiveSplitOne#1138 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
LiveSplit/LiveSplitOne#1129 · 12 comments ·
All issues in LiveSplit/LiveSplitOne
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day