-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: get sqlite working on edge #2099
Closed
NathanFlurry
wants to merge
1
commit into
03-03-fix_get_sqlite_working_on_edge
from
chore_wf_snapshot
Closed
fix: get sqlite working on edge #2099
NathanFlurry
wants to merge
1
commit into
03-03-fix_get_sqlite_working_on_edge
from
chore_wf_snapshot
+1,099
−1,028
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Mar 4, 2025
Closed
Closed
Closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This PR introduces concerning changes to SQLite database management in the Rivet system, primarily affecting temporary file handling and connection cleanup.
- Disabled garbage collection loop in
manager_gc_loop
with early return, preventing cleanup of expired connections - Commented out temporary SQLite file removal code in
SqliteConn
drop handler - Added debug log message "foo" instead of proper file cleanup, indicating incomplete implementation
- These changes will cause temporary SQLite files to accumulate in the data directory over time
- Potential memory leak risk from disabled connection cleanup in
manager_gc_loop
1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
de2b0f9
to
204281c
Compare
Closed
d558db1
to
4c778c2
Compare
204281c
to
2e186c6
Compare
4c778c2
to
d558db1
Compare
2e186c6
to
204281c
Compare
d558db1
to
4c778c2
Compare
204281c
to
2e186c6
Compare
This was referenced Mar 6, 2025
4c778c2
to
d558db1
Compare
2e186c6
to
204281c
Compare
d558db1
to
4c778c2
Compare
204281c
to
2e186c6
Compare
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
Mar 6, 2025
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
This was referenced Mar 6, 2025
This was referenced Mar 6, 2025
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes