Repository navigation
Conversation
Contributor
evalya-impact-summaryEvalya CI impact |
Contributor
❌ ErrorsYour PR has failed checks. Please review the issues below and take necessary action before merging. 🚦 40 Pipeline jobs failed
|
Contributor
Disk usage changeCommit Uncompressed
Details
Compressed
Details
|
Contributor
Validation Report
Run Passed validations (20)
|
This branch has not been deployed
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.
What does this PR do?
Adds session-backed remote queries to a loaded Postgres check: resolve/execute/cancel methods, isolated read-only connections, describe-before-COPY, typed descriptors, bounded CSV framing/pages, sequential intake uploads, retries/splitting, finalize/abort, tracing, and
remote_queries.timeout_ms.Reuses loaded connection settings, database identifiers, autodiscovery snapshots, and the framework's proxy bypass matching. No new dependency or base-check changes.
Local verification (all commands prefixed with
HATCH_DATA_DIR=/instance_storage/remote-queries-spec-ai/caches/hatch):Results: 109 passed; 1 opt-in median-of-five quality test skipped. Existing tests: 10 passed, 59 deselected. Lint passes; 2 configs valid; 5 model files synchronized. Quality thresholds and deployed-Agent behavior are not claimed.
Provisional choices:
503 unavailableis the capacity class; other retryable failures have five attempts. Cancellation by run ID cancels duplicate-ID calls together. Legacy libpq cancellation waits at most 5 s on a dedicated daemon; an abandoned cancel thread can outlive the run. Dedicated event loops do not wait for abandoned DNS resolver threads. Embedded Agent libpq is 18.3; local tests use 16.15.Blocking / unverified: this is scoped WIP, not a complete-spec or production-readiness claim. Libpq can receive an entire oversized COPY block before the framer rejects it, so strict early-read/memory bounds remain unresolved. AWS/Azure token fetching remains synchronous; deadline/cancel and independence on that path are unverified. Idle-machine quality measurements, deployed verification, and paired Agent/AP contract alignment remain outstanding.
Motivation
Fresh implementation of the session-backed Postgres specification, pinned at planning commit
1e3384369dc05ca2bec6e4eb7cd82d8ef0fe0b0e. Paired with the core-Agent change: DataDog/datadog-agent#60311.Checklist before requesting review