~bigbes/sr-ht-dolt · parade

main · last commit 6 hours ago · ti41arbu

← Back to the parade

sr-ht-dolt-9c6 The settings POST writes store paths into the response Past Stand

status: closed P3 bug
bd reopen sr-ht-dolt-9c6
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-08-13T07:19:41Z
Started2026-08-13T07:21:10Z
Updated2026-08-13T07:26:37Z
Closed2026-08-13T07:26:37Z
Description
web/handlers_settings.go:201,206 responds with "database record removed but store deletion failed: "+err.Error() and "store deleted but cache eviction failed: "+err.Error(). That is the same leak 11c622f removed from the overview, one path along: the browse/storage error text carries on-disk paths, and the owner is shown them. Found while fixing the overview.
Design
Same shape as 11c622f: a fixed sentence to the reader, the detail to slog with the database id. The distinction that matters to the owner — the record is gone but the store may not be — should survive in the sentence without the path.

Depends on

No outgoing dependencies.

Depended on by

Nothing depends on this issue.

No comments.

Close reason

Landed in 35875ff: two fixed sentences that keep the distinction the owner needs (record gone but store may remain / store gone but a cached handle may survive), detail to slog with the database id. The agent also checked handlers_keys.go and left its 'Invalid public key: <err>' alone — those errors describe the caller's own submitted string, not the storage layer, which is a different class.
  • Eugene Blikh created the issue · 2026-08-13T10:19:41Z
  • Eugene Blikh changed status to in_progress · 2026-08-13T10:21:10Z
  • Eugene Blikh closed the issue · 2026-08-13T10:26:36Z
    Landed in 35875ff: two fixed sentences that keep the distinction the owner needs (record gone but store may remain / store gone but a cached handle may survive), detail to slog with the database id. The agent also checked handlers_keys.go and left its 'Invalid public key: <err>' alone — those errors describe the caller's own submitted string, not the storage layer, which is a different class.
Stored rows — what this pane was built from, as read
issues 1 row
id sr-ht-dolt-9c6
content_hash 771e917e7a1f542d45b988a524089b9b8035acd0dbd0b2f57120017b67ed04ef
title The settings POST writes store paths into the response
description web/handlers_settings.go:201,206 responds with "database record removed but store deletion failed: "+err.Error() and "store deleted but cache eviction failed: "+err.Error(). That is the same leak 11c622f removed from the overview, one path along: the browse/storage error text carries on-disk paths, and the owner is shown them. Found while fixing the overview.
design Same shape as 11c622f: a fixed sentence to the reader, the detail to slog with the database id. The distinction that matters to the owner — the record is gone but the store may not be — should survive in the sentence without the path.
acceptance_criteria
notes
status closed
priority 3
issue_type bug
assignee NULL
estimated_minutes NULL
created_at 2026-08-13T07:19:41Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-08-13T07:26:37Z
closed_at 2026-08-13T07:26:37Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason Landed in 35875ff: two fixed sentences that keep the distinction the owner needs (record gone but store may remain / store gone but a cached handle may survive), detail to slog with the database id. The agent also checked handlers_keys.go and left its 'Invalid public key: <err>' alone — those errors describe the caller's own submitted string, not the storage layer, which is a different class.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at 2026-08-13T07:21:10Z
is_blocked 0
events 3 rows
id 019ff9fd-b333-755f-9cda-5d025cfc2eb5
issue_id sr-ht-dolt-9c6
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-08-13T10:19:41Z
id 019ff9ff-0eec-786c-800a-2b818a24fa24
issue_id sr-ht-dolt-9c6
event_type status_changed
actor Eugene Blikh
old_value {"id":"sr-ht-dolt-9c6","title":"The settings POST writes store paths into the response","description":"web/handlers_settings.go:201,206 responds with \"database record removed but store deletion failed: \"+err.Error() and \"store deleted but cache eviction failed: \"+err.Error(). That is the same leak 11c622f removed from the overview, one path along: the browse/storage error text carries on-disk paths, and the owner is shown them. Found while fixing the overview.","design":"Same shape as 11c622f: a fixed sentence to the reader, the detail to slog with the database id. The distinction that matters to the owner — the record is gone but the store may not be — should survive in the sentence without the path.","status":"open","priority":3,"issue_type":"bug","owner":"bigbes@gmail.com","created_at":"2026-08-13T07:19:41Z","created_by":"Eugene Blikh","updated_at":"2026-08-13T07:19:41Z"}
new_value {"status":"in_progress"}
comment NULL
created_at 2026-08-13T10:21:10Z
id 019ffa04-0b67-78c6-b149-cba5e73c9ccf
issue_id sr-ht-dolt-9c6
event_type closed
actor Eugene Blikh
old_value
new_value Landed in 35875ff: two fixed sentences that keep the distinction the owner needs (record gone but store may remain / store gone but a cached handle may survive), detail to slog with the database id. The agent also checked handlers_keys.go and left its 'Invalid public key: <err>' alone — those errors describe the caller's own submitted string, not the storage layer, which is a different class.
comment NULL
created_at 2026-08-13T10:26:36Z