Skip to content

returns 400 on validator-faucets api when no validator_ids are sent#6131

Open
JYC11 wants to merge 2 commits into
canton-network:mainfrom
JYC11:jaeyoon/fix-scan-validator-faucets-empty-output
Open

returns 400 on validator-faucets api when no validator_ids are sent#6131
JYC11 wants to merge 2 commits into
canton-network:mainfrom
JYC11:jaeyoon/fix-scan-validator-faucets-empty-output

Conversation

@JYC11

@JYC11 JYC11 commented Jun 26, 2026

Copy link
Copy Markdown

fixes: #1964

The SQL syntax crash does not seem to occur as an empty array produces = ANY ('{}') which is valid SQL. A test asserting store returns Seq.empty for an empty input was added as a regression test in case inClause semantics change.

This PR instead addresses the user-facing concern: calling /v0/validators/validator-faucets with no validator_ids (or a misspelled key like validator=) used to return 200 + empty list, masking the typo. It now returns HTTP 400 with a clear error.

@JYC11 JYC11 changed the title fix scan validator faucets empty output returns 400 on validator-faucets api when no validator_ids are sent Jun 29, 2026
JYC11 added 2 commits June 30, 2026 01:34
Signed-off-by: JYC11 <jaeyoon.c@gmail.com>
Signed-off-by: JYC11 <jaeyoon.c@gmail.com>
@JYC11 JYC11 force-pushed the jaeyoon/fix-scan-validator-faucets-empty-output branch from 0d14bb2 to c2d6a03 Compare June 30, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

scan /v0/validators/validator-faucets should 400 or empty-result on no validators

5 participants