Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 Pre-existing: runs replication ClickHouse clients also missing
secureparam strippingWhile this PR correctly fixes the missing
secureparam deletion for the query ClickHouse client, two other call sites have the same pre-existing issue:apps/webapp/app/services/runsReplicationInstance.server.ts:25-26passesenv.RUN_REPLICATION_CLICKHOUSE_URLdirectly tonew ClickHouse()without strippingsecure.apps/webapp/app/routes/admin.api.v1.runs-replication.create.ts:80-81does the same.These use a different env var (
RUN_REPLICATION_CLICKHOUSE_URL) which may or may not contain thesecurequery parameter depending on the deployment. If it does, these clients would also hit the same startup crash described in this PR's changelog. Worth a follow-up fix for consistency.Was this helpful? React with 👍 or 👎 to provide feedback.