[pull] main from bytebase:main#612
Merged
pull[bot] merged 12 commits intoerickirt:mainfrom Feb 28, 2026
Merged
Conversation
* chore: upgrade parser and adapt snowflake integration * chore: tidy go module sums * fix(lint): remove unused receiver in snowflake helper
Bumps [go.opentelemetry.io/otel/sdk](https://github.com/open-telemetry/opentelemetry-go) from 1.39.0 to 1.40.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-go@v1.39.0...v1.40.0) --- updated-dependencies: - dependency-name: go.opentelemetry.io/otel/sdk dependency-version: 1.40.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Add AccessToken field to World struct - Add NewClientWithAccessToken() for OIDC/workload identity auth flow - Add --access-token flag to root command - Unify client creation via NewClientFromWorld() for check and rollout Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…ing (#19417) Use strconv.ParseInt with explicit bit size instead of strconv.Atoi to avoid unsafe int-to-int32 narrowing. Return uint32 directly from shouldSwitchUser to match syscall.Credential field types and eliminate redundant conversions. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
- elasticsearch/parser.go: change uffff to int32 and use bitmasked int32(hex&0xF) to eliminate uint64→int conversion - postgres.go: add explicit MaxInt32 bounds check before uint32→int conversion at os.Chown call site Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…9421) * docs: add implementation plan for Elasticsearch result table view Frontend-only feature to add a JSON/Table toggle for Elasticsearch _search results, flattening hits.hits[] documents into rows with _source fields as columns. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(sql-editor): add flattenElasticsearchSearchResult utility Add a utility function that transforms Elasticsearch _search query results into a tabular format by extracting hits.hits[] and flattening each hit's _source fields into columns. Unlike flattenNoSQLResult, this returns a new QueryResult without mutating the original, enabling JSON/Table view toggling. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(sql-editor): add storage key and i18n for ES table view toggle Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(sql-editor): add table/JSON toggle for Elasticsearch search results Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(sql-editor): improve code ordering and reset search state on ES view toggle Move activeResult and related computeds before columns/rows that depend on them for better readability. Reset search state alongside sort state when toggling between table and JSON views. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(sql-editor): enable JSON cell expand for Elasticsearch Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(i18n): add table-view translations for Elasticsearch result view Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(sql-editor): guard masking functions against ES table view column index mismatch Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(sql-editor): remove redundant _index from ES table view columns Users already know which index they're querying, so _index adds noise. Keep only _id and _score as meta columns before _source fields. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: remove plan document Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * refactor(sql-editor): reduce cognitive complexity of flattenElasticsearchSearchResult Extract parseESHitsArray, discoverESColumns, and buildESHitRow helpers to reduce cognitive complexity from 34 to within allowed limits. Also fix optional chaining, explicit sort comparator, and remove unnecessary type assertions flagged by SonarCloud. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…tions from SonarCloud (#19422) Add NOSONAR comments to parameterized query executions in the store layer that are incorrectly flagged as SQL injection. All queries use qb.Query which separates user values into $1/$2/... placeholders. Exclude backend/migrator/migration from SonarCloud analysis as these are schema migration files, not application source code. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…19423) Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…otspots (#19424) * fix(security): sanitize SQL identifiers and suppress false positive hotspots Fix 3 true positive SQL injection vulnerabilities where user-supplied schema names were interpolated into SQL without sanitization. Add NOSONAR annotations with justifications for false positives across database plugins, and update .sonarcloud.properties with test inclusions and ignore rules for known safe patterns. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(security): add NOSONAR to sanitized SQL lines SonarCloud cannot trace that safeSchemeName was sanitized via ReplaceAll — add NOSONAR annotations to the three fixed lines. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: exclude database plugins from copy-paste detection Database driver implementations (backend/plugin/db/*) naturally share patterns since they all implement the same Driver interface for different database engines. Exclude from CPD to avoid false positives. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )