Repository navigation
test(fuzz): three warehouse routes are reachable since #2053 - #2068
Merged
Merged
Conversation
The scheduled fuzz.yml run 44544139061 on main at 373744b (seed 20261006) was red in the superuser pass: 7 operations answered 5xx, all 7 known, and 3 operations that tests/fuzz/unreached.toml lists as unreached were reached. The viewer and sdk passes were green. #2053 enabled Amazon Redshift. A Redshift source takes a role, not a secret, so the superuser pass now saves one when it creates a warehouse analysis source (201, five times at this seed) where it answered 422 connector_disabled before, and the ids Schemathesis reuses from those answers name stored sources. The pass then reaches the get (200), update (200) and delete (204) routes for one stored source. Between #2010's green dispatch (run 44438135568 on 87f87ac, main at 0b7e3cc) and 373744b the only application change is that enable line. The three superuser entries are removed and the header gains the paragraph that says why; the superuser list is 117, the viewer and sdk lists (191, 9) do not change. Read from fuzz_check's evaluation of a local run of the superuser pass at seed 20261006 on 373744b (uvicorn on 127.0.0.1, scratch PostgreSQL 14, the workflow's bootstrap, demo seed, api_env and Schemathesis invocation), whose count line equals run 44544139061's: 264 selected, 7 5xx (0 not listed), reached 147, unreached 117 (0 not listed, 3 listed but reached). With this file the same run evaluates GREEN: listed but reached 0, and every other count unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NpxPyav9uBxNuiXsDvD8qn Signed-off-by: amarkanday <a.markanday@gmail.com>
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 and why
The scheduled fuzz.yml run 44544139061 on main at 373744b (seed 20261006) was red in the superuser pass. Seven operations answered 5xx, all seven already known. Three operations that
tests/fuzz/unreached.tomllists as unreached were reached. The viewer and sdk passes were green.#2053 enabled Amazon Redshift. A Redshift source takes a role, not a secret. So when the superuser pass creates a warehouse analysis source, it now saves one (201, five times at this seed), where before it answered 422
connector_disabled. Schemathesis then reuses the ids from those answers, and they name stored sources. That is how the pass reaches the get (200), update (200) and delete (204) routes for one stored source. Between #2010's green dispatch (run 44438135568 on 87f87ac, main at 0b7e3cc) and 373744b, the only application change is that enable line.This change removes the three superuser entries and adds a paragraph to the file's header that says why. The superuser list is now 117. The viewer and sdk lists (191 and 9) do not change.
Part of #2064
Verification
The numbers come from fuzz_check's evaluation of a local run of the superuser pass at seed 20261006 on 373744b. That run used uvicorn on 127.0.0.1, a scratch PostgreSQL 14, and the workflow's own bootstrap, demo seed, api_env and Schemathesis invocation. Its count line equals run 44544139061's: 264 selected, 7 5xx (0 not listed), reached 147, unreached 117 (0 not listed, 3 listed but reached). With this file, the same run evaluates GREEN: listed but reached 0, and every other count unchanged.
backend/tests/unit/scripts/test_fuzz_{check,workflow,report}.py: 193 passed.tests/fuzz/unreached.toml(13 insertions, 15 deletions).NOT VERIFIED
🤖 Generated with Claude Code
https://claude.ai/code/session_01NpxPyav9uBxNuiXsDvD8qn