build(deps): bump github.com/jackc/pgx/v5 from 5.9.1 to 5.9.2 in the go_modules group across 1 directory - #1
Merged
Conversation
Bumps the go_modules group with 1 update in the / directory: [github.com/jackc/pgx/v5](https://github.com/jackc/pgx). Updates `github.com/jackc/pgx/v5` from 5.9.1 to 5.9.2 - [Changelog](https://github.com/jackc/pgx/blob/master/CHANGELOG.md) - [Commits](jackc/pgx@v5.9.1...v5.9.2) --- updated-dependencies: - dependency-name: github.com/jackc/pgx/v5 dependency-version: 5.9.2 dependency-type: direct:production dependency-group: go_modules ... Signed-off-by: dependabot[bot] <support@github.com>
cursor
Bot
force-pushed
the
dependabot/go_modules/go_modules-dc1255629f
branch
from
May 24, 2026 07:51
eccfff7 to
a558443
Compare
diazMelgarejo
pushed a commit
that referenced
this pull request
May 27, 2026
## Summary - Update GitHub Actions: checkout v6.0.2, upload-artifact v6.0.0, download-artifact v7.0.0 - Update npm deps: svelte 5.53.2 (SSR vulnerability fix), vite-plugin-svelte 6.2.4, vite 6.4.1, typescript 5.9.3, svelte-check 4.4.1, @tsconfig/svelte 5.0.8, @tanstack/virtual-core 3.13.18 - Add engines.node constraint for vite-plugin-svelte 6.x minimum - Fix search.test.ts timing for Svelte 5.53.2 reactive system changes Closes #1, closes #2, closes #3, closes #4, closes #5, closes #6, closes #7, closes #8 ## Test plan - [ ] CI passes: Go tests, frontend unit tests, E2E tests, lint, type check - [ ] `npm audit` shows 0 vulnerabilities - [ ] Frontend builds cleanly with vite 6.4.1 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
cursor Bot
pushed a commit
that referenced
this pull request
Jun 1, 2026
## Summary - Update GitHub Actions: checkout v6.0.2, upload-artifact v6.0.0, download-artifact v7.0.0 - Update npm deps: svelte 5.53.2 (SSR vulnerability fix), vite-plugin-svelte 6.2.4, vite 6.4.1, typescript 5.9.3, svelte-check 4.4.1, @tsconfig/svelte 5.0.8, @tanstack/virtual-core 3.13.18 - Add engines.node constraint for vite-plugin-svelte 6.x minimum - Fix search.test.ts timing for Svelte 5.53.2 reactive system changes Closes #1, closes #2, closes #3, closes #4, closes #5, closes #6, closes #7, closes #8 ## Test plan - [ ] CI passes: Go tests, frontend unit tests, E2E tests, lint, type check - [ ] `npm audit` shows 0 vulnerabilities - [ ] Frontend builds cleanly with vite 6.4.1 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
cursor Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
## What
Adds a `--write-timeout` duration flag to `serve` and `pg serve`, making the API
write deadline configurable. The default is unchanged at 30s. A non-positive value
disables the deadline.
## Why
The write deadline was hardcoded at 30s. On large shared datasets the full-history
analytics aggregates (heatmap, activity, usage summary) can exceed it and return
`503` with `{"error":"request timed out"}`, which surfaces as blank "request timed
out" dashboard panels. Operators had no way to raise it. Relates to kenn-io#1147.
## Where to look
- `internal/config/config.go` — the flag is registered on both the `flag` and
`pflag` serve flag sets (so `serve` and `pg serve` both accept it) and mapped to
`Config.WriteTimeout` in `applyFlagValue`, mirroring `events-coalesce-interval`.
- `internal/server/middleware.go` — the standard-handler timeout wrapper now
bypasses `http.TimeoutHandler` when the timeout is non-positive, so `0` disables
the deadline instead of firing immediately. The typed (Huma) API path already
had this guard; this brings the two paths into agreement.
- `docs/remote-access.md` — documents raising the timeout for slow aggregates and
the flag reference row.
## Tradeoffs and limitations
- Raising the timeout treats the symptom. When aggregates are slow enough to need a
large value, the underlying database-side cost is usually the real fix — for a
multi-tenant read role, a set-based row-level-security predicate rather than a
per-row function call. The docs note points there; #1 has the detail.
- Flag only; no new config-file or environment key was added, consistent with the
neighboring serve duration flags.
Co-authored-by: TechnoPhobe01 <Technophobe01@users.noreply.github.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.
Bumps the go_modules group with 1 update in the / directory: github.com/jackc/pgx/v5.
Updates
github.com/jackc/pgx/v5from 5.9.1 to 5.9.2Changelog
Sourced from github.com/jackc/pgx/v5's changelog.
Commits
0aeabbcRelease v5.9.260644f8Fix SQL sanitizer bugs with dollar-quoted strings and placeholder overflowa5680bcMerge pull request #2531 from dolmen-go/godoc-add-linkse34e452doc: Add godoc links08c9bb1Fix Stringer types encoded as text instead of numeric value in composite fields96b4dbdRemove unstable testacf88e0Merge pull request #2526 from abrightwell/abrightwell-min-proto2f81f1fUpdatemax_protocol_versionandmin_protocol_versiondefaultsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.