Wiredrag
Menu

Answers

What one question returns: every place, counted, beside the files it skipped

POST /v1/snapshots returns the quote; POST /v1/questions asks, two at a time per account. GET /v1/answers/{id} returns the JSON, also a readable document, as Markdown or PDF.

The answer opens on the question, the commit and three counts. Then each place by service, with its file, its line and why it was listed.

The figures are from the order-id scenario, not from a customer.

  • 31 found - by service, each saying why it was listed
  • 7 unconfirmed - each with the boundary where it stopped
  • 214 not read - and why, file by file
A whole answer: the question, three counts (found, unconfirmed, not read), the places as sentences grouped by service.
The coverage line of an answer: files read, files skipped, and the reason for each skip.

An answer is also a map: the repository's directories by size, and the order id's path lit across them.

Each top-level directory is a block sized by its tokens. Every lit hop is a place on the list.

Six hops a type checker cannot cross, and why each is a place of its own

Each one is its own change, owned by a different team and shipped on a different day.

Protobuf fields

an int32 field is a contract with every reader, in every language generated from the .proto

A Python pipeline's schema

pa.int32() sits in the declaration, and nothing fails until the first row past the limit is written

CSV exports

the 32 bits live in a loader's type map, or in a partner's importer outside the repository

Ints in older Java services

compiled against their own copy of the DTO, out of sight of the next service's checker

Cache keys

cast to int and formatted into a string, where no type system follows

A reporting job

CAST(order_id AS INT) in a warehouse where INT is 32 bits, failing only when it runs

The same question asked after fixes: now 64-bit, still 32-bit, and one place new since the last answer.

Each re-ask reads the new commit in full. If the reader's version changed in between, the answer says so.

Ask again once the fixes land, and the list closes instead of being read twice

See what a re-ask costs

Send the new commit with reask_of set. Every place comes back changed, unchanged, new or gone since the last answer.

Six weeks in - 24 now 64-bit, 7 still 32-bit, 1 new

Eleven weeks in - 31 changed, 1 still 32-bit, none new

Marked not this value - off the list until its line changes

Your request has been received.

Expect a message from Wiredrag. It goes to the address you gave.