deps(hub): bump github.com/go-chi/chi/v5 from 5.1.0 to 5.2.5 in /hub#8
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(hub): bump github.com/go-chi/chi/v5 from 5.1.0 to 5.2.5 in /hub#8dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [github.com/go-chi/chi/v5](https://github.com/go-chi/chi) from 5.1.0 to 5.2.5. - [Release notes](https://github.com/go-chi/chi/releases) - [Changelog](https://github.com/go-chi/chi/blob/master/CHANGELOG.md) - [Commits](go-chi/chi@v5.1.0...v5.2.5) --- updated-dependencies: - dependency-name: github.com/go-chi/chi/v5 dependency-version: 5.2.5 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
physercoe
pushed a commit
that referenced
this pull request
May 23, 2026
… log spam + agy tool_action surfacing (v1.0.650-alpha) ADR-035 W11 fix-up #8. Three findings from the post-v1.0.649 review. ## Q1: attention_reply unsupported Host-runner WARN: `input dispatch failed agent=… seq=377 kind=attention_reply err="antigravity adapter: unsupported input kind \"attention_reply\""`. The hub fans out the principal's /decide on request_approval / select / help_request as `input.attention_reply` to the owning agent. Pre-fix the antigravity adapter rejected it (only text/cancel/escape/pick_option/action_bar were handled), the input router posted a system event with the failure, and the agent never saw the decision. Fix: new `attention_reply` case in HandleInput that renders the structured payload through an inlined `formatAttentionReplyText` (mirror of the hostrunner-package canonical in driver_stdio.go) and feeds it through `inputText` as a normal text turn. The ACP/exec_resume/stdio/ appserver drivers already do this — antigravity was the gap. Duplicated the formatter inline because the hostrunner package already imports this one (would be a cycle); future `internal/drivers/attentionreply` refactor flagged in the changelog. ## Q2: overview_widget warning storm The user's hub-server log had multi-line-per-minute spam: WARN unknown overview_widget ... template=ablation-sweep widget=sweep_compare WARN unknown overview_widget ... template=benchmark-comparison widget=sweep_compare Cause: the template walker re-runs on every list-projects / list-templates / project-detail call (cheap, but each walk re-validated overview_widget and re-logged). Two on-disk overlay templates in <dataRoot>/team/templates/projects/ reference `sweep_compare`, a widget retired in v1.0.506. The bundled FS no longer ships it; the operator's overlay still does. Fix: new `warnOverviewWidgetOnce(template, widget)` helper that de-duplicates by (template, widget) pair. First stale value still surfaces (operator awareness preserved); subsequent walks stay quiet. Two lock tests. ## Q3: agy local-log review — surface humanised intent strings Every agy PLANNER_RESPONSE.tool_calls[].args carries `toolAction` ("Querying matching attentions from database") and `toolSummary` ("Grep search") strings. Pre-fix mobile saw only the raw tool name + arg blob; now the mapper lifts both to top-level payload fields (tool_action, tool_summary) so mobile's tool_call card can render them as a subtitle. Additive — non-agy engines stay unchanged. Two more findings noted as out-of-scope follow-ups (Bash vs run_command duplicate naming, list_dir vs list_directory mismatch, file-write tool prominence). Plus the previously-noted is_error propagation (v1.0.649) and turn.result emission (v1.0.647) — both verified still working in this run's event stream. ## Verified - All 20 hub packages green; go vet clean. - 6 new lock tests across the changes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
physercoe
pushed a commit
that referenced
this pull request
May 23, 2026
v1.0.650-alpha Android workflow hit the same transient `Bad credentials` GitHub-API flake as v1.0.649-alpha during the "Create Release" step. APK + 8 server tarballs all built and signed cleanly; only the upload to the GitHub release page failed. The PAT in this session can't re-run individual jobs via the API, and the Android workflow only fires on tag push, so a fresh tag is the cleanest re-trigger. No code change vs v1.0.650-alpha — same binaries, same fixes (ADR-035 W11 fix-up wedge #8: attention_reply routing + overview_widget once-per-key + agy tool_action surfacing). Use v1.0.651 on the GitHub release page if you need the APK; v1.0.650 has only the iOS .ipa. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
physercoe
pushed a commit
that referenced
this pull request
May 24, 2026
…eadcrumb (v1.0.664-alpha) ADR-027 W11 fix-up wedge #8 — diagnostic-only. On-host smoke of v1.0.663 reproduced "mobile shows nothing for this agent": no agent text, cancel button stuck on (no turn.result received), session.init / token / context chips blank. JSONL has the assistant text + Stop hook attachment; running mapper.MapLine() locally against the file confirms kind=text + kind=usage are correctly produced. So the events ARE being generated — they're vanishing between the mapper and the hub's agent_events row, silently. Diagnostic logging was at Debug (the default level), so the on-host smoke had no signal. This wedge raises it to Warn + adds one INFO breadcrumb when the tailer produces its first line. After deploy + re-smoke, host-runner stderr will tell us which leg fails: - "claude-code adapter: post failed" + err → Poster path broken - "claude-code adapter: hook-emit post failed" → hookStop path broken - No "first JSONL line received" → tailer never started - All three appear + agent still empty → mobile filter (session_id / subscription) is the bug No behaviour change. Tests unchanged + green. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Author
|
Superseded by #16. |
dependabot
Bot
deleted the
dependabot/go_modules/hub/github.com/go-chi/chi/v5-5.2.5
branch
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 github.com/go-chi/chi/v5 from 5.1.0 to 5.2.5.
Release notes
Sourced from github.com/go-chi/chi/v5's releases.
... (truncated)
Commits
05f1ef7fix(middleware): add missing return in RouteHeaders empty check (#1045)6eb3588middleware: harden RedirectSlashes handler (#1044)de0d16eUpdate comment about min Go version (#1023)9fb4a15update reverseMethodMap in RegisterMethod (#1022)51c977cRefactor to use atomic type (#1019)563ab11Refactor graceful shutdown example (#994)a52c582Bump minimum Go and use new features (#1017)9b9fb55Replace methodTypString func with reverseMethodMap (#1018)0265fcdrefactor: iterative wildcard collapsing and add test for consecutive wildcard...cf537d4Optimize throttle middleware by avoiding unnecessary timer creation (#1011)Dependabot 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)