fix(integ): bound credential scans and classify disabled TTL - #7860
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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
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.
Summary
Credential deletion exceeded the integ client's 30-second timeout while the paused-execution reference query reached a 46-second p99. Materialize workspace-scoped rows before searching JSON across blocks, deployments, paused executions, and checkpoints, preserving archived-workflow cleanup.
Also give disabled TTL column creation a stable
TABLE_ROW_TTL_DISABLEDdetail code so the integration probe can tolerate error wording changes without accepting unrelated 400s. Deploy this app change before the companion infra check.Related integration update: https://github.com/simstudioai/infra/pull/361
PostgreSQL CI also exposed a cross-file DDL deadlock: one suite replaced OAuth triggers while another deleted a user. Run the shared-schema suites sequentially; their internal concurrency tests remain concurrent.
Testing