Show a slack target's retry setting in the target list (closes #395) #475

Merged
clawbot merged 1 commits from issue-395-slack-retries into next 2026-10-03 00:19:13 +02:00
Collaborator

In the target list on the webhook page, a slack target now shows its retry setting next to its masked webhook URL: "Max Retries" with the number, or "0 (fire-and-forget)" for zero. The line is built by the same code an http target uses, so the label and wording cannot drift apart. Before this, a slack target showed only its masked webhook URL, though its edit page saves retries and delivery honours them.

slackConfigFields now takes the target row instead of its configuration text, because the retry setting is stored on the row. A slack target shows no queue size even when one is stored, since delivery never reads it; an http target still shows one as before.

Every slack target in the list now has a "Max Retries" line, including those left at zero.

Judgement call: the deleted-target test now checks that a deleted slack target's fields equal a live one's, instead of repeating the literal list a third time.

Model: opus-5-5

In the target list on the webhook page, a `slack` target now shows its retry setting next to its masked webhook URL: "Max Retries" with the number, or "0 (fire-and-forget)" for zero. The line is built by the same code an `http` target uses, so the label and wording cannot drift apart. Before this, a `slack` target showed only its masked webhook URL, though its edit page saves retries and delivery honours them. `slackConfigFields` now takes the target row instead of its configuration text, because the retry setting is stored on the row. A `slack` target shows no queue size even when one is stored, since delivery never reads it; an `http` target still shows one as before. Every `slack` target in the list now has a "Max Retries" line, including those left at zero. Judgement call: the deleted-target test now checks that a deleted `slack` target's fields equal a live one's, instead of repeating the literal list a third time. Model: opus-5-5
clawbot added the needs-review label 2026-10-02 23:14:22 +02:00
clawbot self-assigned this 2026-10-02 23:14:22 +02:00
Author
Collaborator

Review: FAIL (needs-rework)

  1. internal/delivery/target_config_view.go, slackConfigFields: it appends the whole of retryFields, so a slack target with a queue size stored shows a "Max Queue Size" line. The delivery engine never reads a target's queue size (the README's max_queue_size row says so too), so the line shows a setting that does nothing for a slack target. The new test TestNewTargetViews_SlackRetries asserts that line, and the PR body says the list shows it. Acceptable: a slack target shows "Webhook URL" and "Max Retries" only. The "Max Retries" line comes from the same code the http target uses, so the label and the "0 (fire-and-forget)" wording cannot drift apart. The test stores a queue size on the slack target and checks that no "Max Queue Size" line appears. The PR body drops the queue-size claim.

Model: opus-5-5

Review: FAIL (needs-rework) 1. `internal/delivery/target_config_view.go`, `slackConfigFields`: it appends the whole of `retryFields`, so a `slack` target with a queue size stored shows a "Max Queue Size" line. The delivery engine never reads a target's queue size (the README's `max_queue_size` row says so too), so the line shows a setting that does nothing for a `slack` target. The new test `TestNewTargetViews_SlackRetries` asserts that line, and the PR body says the list shows it. Acceptable: a `slack` target shows "Webhook URL" and "Max Retries" only. The "Max Retries" line comes from the same code the `http` target uses, so the label and the "0 (fire-and-forget)" wording cannot drift apart. The test stores a queue size on the `slack` target and checks that no "Max Queue Size" line appears. The PR body drops the queue-size claim. Model: opus-5-5
clawbot added needs-rework and removed needs-review labels 2026-10-02 23:55:48 +02:00
clawbot added 1 commit 2026-10-03 00:09:14 +02:00
The target list showed only the masked webhook URL for a slack
target, though its edit page saves a retry setting and delivery
honours it. It now shows the "Max Retries" line, built by the same
code as an http target's. It shows no queue size: delivery never
reads one.

Model: opus-5-5
clawbot force-pushed issue-395-slack-retries from d0fe433d31 to 67410ec9f8 2026-10-03 00:09:14 +02:00 Compare
clawbot added needs-review and removed needs-rework labels 2026-10-03 00:09:22 +02:00
Author
Collaborator

A slack target now shows only "Webhook URL" and "Max Retries". The "Max Retries" line comes from one function that the http target also uses, so its label and the "0 (fire-and-forget)" wording are shared. The queue-size line is now added only by the http target. The test now stores a queue size on the slack target and checks that no "Max Queue Size" line appears. The PR body no longer claims that a queue size is shown.

Model: opus-5-5

A `slack` target now shows only "Webhook URL" and "Max Retries". The "Max Retries" line comes from one function that the `http` target also uses, so its label and the "0 (fire-and-forget)" wording are shared. The queue-size line is now added only by the `http` target. The test now stores a queue size on the `slack` target and checks that no "Max Queue Size" line appears. The PR body no longer claims that a queue size is shown. Model: opus-5-5
Author
Collaborator

Review: PASS.

Model: opus-5-5

Review: PASS. Model: opus-5-5
clawbot merged commit 93911f28f9 into next 2026-10-03 00:19:13 +02:00
clawbot deleted branch issue-395-slack-retries 2026-10-03 00:19:13 +02:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/webhooker#475