Skip to content

Commit dcb457b

Browse files
Say where a hand-set server-id counts, and when a count goes untagged (#46)
* Say where a hand-set server-id counts, and when a count goes untagged The README's "Resetting it" paragraph did not say that only a column-0 server-id: line outside the tags: block is read, nor that a quoted value is accepted, so an operator who indented the line would see a new ID appended. "The wire format" said a coalesced count always carries the coalesced tag, which withCount skips at 32 tags. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Say column 0 rather than "a line at the start of a line" Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 346c2c0 commit dcb457b

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

‎README.md‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,9 +81,11 @@ in memory for that run only — `build()` still never throws.
8181

8282
**Resetting it.** Delete the `server-id:` line; the next start writes a new
8383
one. Or set your own value (letters, digits, `_`, `.`, `-`, starting with a
84-
letter or digit; at most 255 characters). A `server-id:` line whose value is
85-
anything else is ignored, and the next start appends a new one to the end of
86-
the file.
84+
letter or digit; at most 255 characters; bare or quoted). Only a `server-id:`
85+
line that starts at column 0, outside the `tags:` block, counts, and the first
86+
valid one wins. A `server-id:` line that is indented, inside `tags:`, or whose
87+
value is anything else is ignored, and if no valid one is left, the next start
88+
appends a new one to the end of the file.
8789

8890
**Opting out.** Every [opt-out](#opting-out) below also stops the ID: a
8991
disabled client never generates one, never writes one, and sends nothing.
@@ -278,7 +280,8 @@ Shade it into a plugin jar; it is one class.
278280
is JSON); `tags` always holds at least `version`, and
279281
`install` whenever the client has an [installation ID](#every-event-carries-a-random-server-id) and the event is under
280282
32 tags, and the count of a
281-
[coalesced](#repeated-events-are-coalesced) event also carries `coalesced`. The server assigns the
283+
[coalesced](#repeated-events-are-coalesced) event also carries `coalesced`
284+
unless the event already carries 32 tags. The server assigns the
282285
timestamp. A `201` is success; anything else is logged at `FINE` and dropped.
283286

284287
Redirects are not followed. The body is streamed with a fixed length, so

0 commit comments

Comments
 (0)