You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unified QA run passed all executed tests (7/7, 0 failures, with one additional check-only segment reporting no confirmed defects), indicating no verified production logic defects in scope. Key validations showed first-boot auto-creation of the default database, correct authentication behavior (valid SCRAM login succeeds and out-of-order SCRAM frames are rejected without residual session auth), correct COPY FROM STDIN commit and post-error recovery behavior, and correct SERIAL/sequence wiring plus boundary enforcement, while noting these results were obtained after local environment remediation with temporary role/auth bypasses (and SCRAM disabled in the SERIAL-focused run) to stabilize test setup.
✅ Passed (7)
Category
Summary
Screenshot
Authentication
After restoring the stopped nested container and starting Doltgres, postgres/password successfully authenticated to sqllogictest on 127.0.0.1:5432 and SELECT current_user returned postgres@127.0.0.1.
Authentication
Raw wire-protocol probe sent an out-of-order SASLResponse before SASLInitialResponse; server closed the connection (EOF), subsequent query on same socket was unusable, and a fresh connection authenticated normally.
Copy
Using psql against sqllogictest, COPY FROM STDIN accepted multi-row text input and returned COPY 3; subsequent SELECT confirmed rows persisted after CopyDone.
Copy
Injected invalid COPY data chunk to force failure; COPY returned type-conversion error, no partial rows remained, and normal SQL executed immediately afterward in the same session.
Sequence
CREATE TABLE serial_t(id SERIAL...) produced a nextval-backed default and insert without id generated id=1 via public.serial_t_id_seq.
Sequence
Using smallserial/serial/bigserial tables, inserts at each subtype max succeeded after setting sequence to max-1, and one-beyond inserts consistently failed with sequence maximum errors.
Startup
Startup flow successfully created and selected getting_started on first boot via the normal CLI path.
These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩
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
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.
☕ An Automated Dependency Version Bump PR 👑
Initial Changes
The changes contained in this PR were produced by `go get`ing the dependency.
```bash
go get github.com/dolthub/[dependency]/go@[commit]
```