chore: three cleanups around Postgres persistence#147
Open
FlyM1ss wants to merge 1 commit into
Open
Conversation
- Drop 2 leftover repro agents (owner-a-repro, intruder-b-repro) from the committed seed backtest.db external_agents table (inert test debris, same class #106 cleaned). - Document USERS_DATABASE_URL in render.yaml (sync: false), alongside the already-listed CONTENT_DATABASE_URL -- both are set on the service and equally load-bearing. - Fix the plan's Task 9 Step 5 verification: it piped uvicorn stdout to grep (block-buffered) and timeout's SIGTERM discarded the buffer, so it printed zero backend: lines on healthy code -- a false alarm. Add PYTHONUNBUFFERED=1 (what prod uses) so the four lines flush. Verified: 4 lines with it, 0 without. Closes #141 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Batch C of the agent-persistence follow-ups — three unrelated few-minute cleanups (grouped as filed in #141).
owner-a-repro,intruder-b-repro) frombacktest.dbexternal_agents(inert debris, same class chore: drop stray test data from seed backtest.db #106 removed). Removed via rawsqlite3+ WAL checkpoint: no tables added, no other rows touched,agent_versions/strategiesalready empty.USERS_DATABASE_URL(sync: false) next toCONTENT_DATABASE_URL. It's set on the service and equally load-bearing, but an operator reading the yaml wouldn't have known it exists. Documentation only — prod doesn't sync from this file (sync: false, so no secret committed).grepblock-buffers the factoryprint()s andtimeout's SIGTERM discards them, so it showed zerobackend:lines on healthy code — while "Application startup complete" still appeared, making the false alarm convincing. AddedPYTHONUNBUFFERED=1(whatrender.yamlsets in prod). Verified at source: 4 lines with it, 0 without.Closes #141. Suite unchanged: 1095 passed / 18 skipped.