HelloZeroNet / HelloZeroNet/ZeroNet
OperationalError: cannot commit - no transaction is active in core/src/Db/Db.py line 169 (reason: Interval)
- Dominant language
- JavaScript
- Stars
- 18.8k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
### Step 1: Please describe your environment
* ZeroNet version: r4404
* Operating system: W10
* Web browser: FF beta
* Tor status: error
* Opened port: no
### Step 2: Describe the problem:
debug.log shows:
ERROR Db#0:Chart Commit error: OperationalError: cannot commit - no transaction is active in core/src/Db/Db.py line 169 (reason: Interval)
on restart it not appeared, then i quit and start again and appeared again.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading core/src/Db/Db.py around line 169 and inspect the debug.log entry for the Chart commit error. Reproduce the reported quit-and-restart sequence if possible, then determine whether the interval-related path still attempts a commit without an active transaction. Done means the reported error no longer appears during the described restart flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100