MerginMaps / MerginMaps/geodiff
rebase: "Failed to release savepoint" when applying base2their
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
Seen in the logs - in some very rare cases, when there are no "our" changes, but there are some "their" changes, rebase fails when applying base2their changeset at the last step, when committing the changes (in sqlite3 speak, releasing savepoint). In logs, this shows as Failed to release savepoint, but with no further information.
In Sqlite3SavepointTransaction, we could add more detailed error reporting, to better understand possible source of the problem.
Contributor 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.
Research direction
Start by reading Sqlite3SavepointTransaction and tracing the base2their rebase path where the savepoint is released. Reproduce or inspect the rare no-our-changes case, then improve the Failed to release savepoint reporting so it includes the underlying error details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100