~bigbes/tarantool-etcd · parade

main · last commit 1 month ago · 2npkec0r

← Back to the parade

tarantool-etcd-uud WatchProgressRequest not stream-synchronised; wrong response shape (per-watcher ids instead of watch_id=-1) Lined Up

status: open P2 bug etcd-changelog-sweep
bd update tarantool-etcd-uud --claim bd close tarantool-etcd-uud
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-07-17T13:20:15Z
Updated2026-07-17T13:20:15Z
Description
etcd sends ONE broadcast WatchResponse with watch_id=-1, deferred until every watcher on the stream is synced (watchable_store.go:510-539).

We send one empty response PER WATCHER carrying its real watch id, emitted immediately from the recv-loop fiber while event fibers are still delivering asynchronously (app/etcd/grpc.lua:522-533 vs grpc.lua:336-427).

Impact: clients keying on watch_id=-1 to recognise a progress broadcast do not see it; the 'all watchers caught up' guarantee is not provided.

Race-shaped: argued from code structure, not from an observed failure — needs a reproducer first.
Acceptance criteria
RequestProgress emits a single watch_id=-1 response gated on all stream watchers being caught up; reproducer test exists.

Depends on

No outgoing dependencies.

Depended on by

Nothing depends on this issue.

No comments.

  • Eugene Blikh created the issue · 2026-07-17T16:20:15Z
  • Eugene Blikh added label etcd-changelog-sweep · 2026-07-17T16:20:15Z
Stored rows — what this pane was built from, as read
issues 1 row
id tarantool-etcd-uud
content_hash fd643145ab1fb8229578bc7680a265a12fc602153dfd6682b33c3090c46b73d7
title WatchProgressRequest not stream-synchronised; wrong response shape (per-watcher ids instead of watch_id=-1)
description etcd sends ONE broadcast WatchResponse with watch_id=-1, deferred until every watcher on the stream is synced (watchable_store.go:510-539). We send one empty response PER WATCHER carrying its real watch id, emitted immediately from the recv-loop fiber while event fibers are still delivering asynchronously (app/etcd/grpc.lua:522-533 vs grpc.lua:336-427). Impact: clients keying on watch_id=-1 to recognise a progress broadcast do not see it; the 'all watchers caught up' guarantee is not provided. Race-shaped: argued from code structure, not from an observed failure — needs a reproducer first.
design
acceptance_criteria RequestProgress emits a single watch_id=-1 response gated on all stream watchers being caught up; reproducer test exists.
notes
status open
priority 2
issue_type bug
assignee NULL
estimated_minutes NULL
created_at 2026-07-17T13:20:15Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-07-17T13:20:15Z
closed_at NULL
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 <binary>
source_repo
close_reason
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 NULL
is_blocked 0
labels 1 row
issue_id tarantool-etcd-uud
label etcd-changelog-sweep
events 2 rows
id 019f703c-1ab3-7ecd-8c09-6e8cc9db8d3a
issue_id tarantool-etcd-uud
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-07-17T16:20:15Z
id 019f703c-1ab4-77e3-8de6-83819ccd7907
issue_id tarantool-etcd-uud
event_type label_added
actor Eugene Blikh
old_value NULL
new_value NULL
comment Added label: etcd-changelog-sweep
created_at 2026-07-17T16:20:15Z