Skip to content

Sync upstream main through v3.2.5 - #5

Merged
VibeSWE merged 5 commits into
mainfrom
sync/upstream-main-v3.2.5
Oct 9, 2026
Merged

VibeSWE merged 5 commits into
mainfrom
sync/upstream-main-v3.2.5

Conversation

@VibeSWE

@VibeSWE VibeSWE commented Oct 9, 2026 •

Copy link
Copy Markdown

Description

Sync the fork with parseablehq/parseable:main through b8fb6ce (v3.2.5), preserving the fork's community PromQL, OIDC authorization, and /next frontend changes.

Includes four upstream commits:

  • 322e03c: restore the configured alert evaluation interval after a successful retry (upstream #1814).
  • f44c3af: add the external MCP tool executor API (upstream #1816).
  • 81e82ab: expose the read-only tool catalog (upstream #1817).
  • b8fb6ce: update the server and classic UI assets to v3.2.5 (upstream #1818).

The merge required one conflict resolution in src/sync.rs. Successful evaluations now restore the configured interval. PromQL alerts retain their configured retry cadence and continue retrying; other alert types retain upstream's one-minute retries and retry limit. The retry warning reports the actual delay.

Use a merge commit when merging this PR to retain upstream ancestry for future syncs.

Validation

  • cargo test --locked --lib: 584 passed, 1 ignored, 0 failed, with the /next frontend embedded.
  • node --test scripts/test-community-ui.mjs: 28 passed.
  • cargo fmt --all -- --check: passed.
  • cargo clippy --locked --lib -- -D warnings: passed.
  • git diff origin/main...HEAD --check: passed.
  • The build downloaded the v3.2.5 classic UI archive and verified its pinned SHA1. All 12 community overlay source SHA256 hashes match the new distribution, and the overlay build succeeded.
  • Both fork main and upstream main are ancestors of the sync branch; the branch has no remaining merge conflicts.

This PR has:

  • been tested to ensure live log ingestion and log query work (library ingestion and query tests passed; live integration checks were not run).
  • retained upstream documentation for the new tool API.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

nikhilsinhaparseable and others added 5 commits October 7, 2026 19:09
current: eval frequency continues to be 1m unless task is restarted
task restart only by -
1. alert disabled and then enabled again
2. server restart
3. alert edited

consecutive eval failures stop the task entirely
no automatic restart

fix: successful retry restores configured eval frequency
no task restart required
* tool executer api for external mcp server

* deepsource fix

* deepsource fix

* remove promql tool, remove confirmed from tool call request, coderabbit comment fix
* expose read only tools

* segregate read only tools for external use
Bring in the alert retry recovery fix, external MCP tool execution and read-only catalog, and the v3.2.5 release update. Resolve the alert scheduler conflict by preserving PromQL retry cadence and unlimited retries while restoring the configured interval after successful evaluation.
@VibeSWE
VibeSWE merged commit f082919 into main Oct 9, 2026
11 of 12 checks passed
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.

2 participants