Skip to content
quarry Today In History
Login

Today In History

This Day In History For 2027-09-07

1 Year Ago (more context)

2026-09-07
18:59 • Edit [37b806e848]: Add "ci-pass" with value "6a0fc66bc262007f6941337abb43ebfe". artifact: d3551fa04e user: quarry
18:57 • Edit [e20eea7dc2]: Add "ci-fail" with value "6acfffd1318303cd8958d5d3bf588981". artifact: 9d8fc4bfa3 user: quarry
18:57
land search-empty check-in: 37b806e848 user: dmestas tags: trunk
18:57 • Edit [37b806e848]: Add "landing" with value "02c8052b8846ac15fc10fe434987a91d155a8c480e48dd931179b2a8ec0aadf1". artifact: a0825a448f user: quarry
18:57 • Reply: Search pages get an empty state artifact: d7fb2648e4 user: dmestas
18:57 • Edit [d81c71e206]: Mark "Closed". artifact: e8e938bcae user: quarry
18:57 • Edit [593a47d4fa]: Add "ci-pass" with value "d68c5caf6a380bc49d29b22fbe401506". artifact: 1c8620194f user: quarry
18:57
land landing-live check-in: e20eea7dc2 user: dmestas tags: trunk
18:57 • Edit [e20eea7dc2]: Add "landing" with value "3bc7232c85442da35149acfe276b6afc4981e1ad6ea9f53d7c355623cdf9d605". artifact: f9dbd3f6fa user: quarry
18:57 • Reply: Landing page follows the record artifact: f168ef10c2 user: dmestas
18:57 • Edit [2f8cbedc64]: Mark "Closed". artifact: 7525302742 user: quarry
18:57
land ingest-fault-cause check-in: 593a47d4fa user: dmestas tags: trunk
18:57 • Edit [593a47d4fa]: Add "landing" with value "55d116eaa0a566d208338c73daba1f788bdcf546f0063b0a57fdd72e25d598ba". artifact: 0bf052a72e user: quarry
18:57 • Reply: zitcli: frames reports why the child stopped, not that the stream ended artifact: b3aa8cce63 user: dmestas
18:57 • Edit [f21812051f]: Mark "Closed". artifact: 04823973e1 user: quarry
17:06 • Edit [f21812051f]: Add "ci-pass" with value "edc808bb044f2b12dfe2b7f1e56be7ea". artifact: 11ec1846b6 user: quarry
17:05 • Post: zitcli: frames reports why the child stopped, not that the stream ended artifact: 55d116eaa0 user: dmestas
17:05 • Edit [90fb75f1e8]: Edit check-in comment. artifact: 34d9a3c337 user: dmestas
17:05 • Edit [90fb75f1e8]: Add "ci-fail" with value "fb5f0d658cd5f771301b11698b469ddc". artifact: 3db7646712 user: quarry
17:04
zitcli: frames reports why the child stopped, not that the stream ended closed check-in: f21812051f user: dmestas tags: ingest-fault-cause
17:04
zitcli: frames reports why the child stopped, not that the stream ended check-in: 90fb75f1e8 user: dmestas tags: ingest-fault-cause
17:02 • Edit [d81c71e206]: Add "ci-pass" with value "06828f002d69eb560eb7c2fd13a30d72". artifact: 9b075ce2b1 user: quarry
17:01 • Post: Search pages get an empty state artifact: 02c8052b88 user: zeitgeist
17:01
Search pages explain themselves when there is no query closed check-in: d81c71e206 user: dmestas tags: search-empty
17:01 • Edit [2f8cbedc64]: Add "ci-pass" with value "34ccfcacb9fa67f19ebc513e749373a9". artifact: 678bdfbff7 user: quarry
16:59 • Post: Landing page follows the record artifact: 3bc7232c85 user: zeitgeist
16:59
Landing page follows the record: accept, remarks and check-ins patch the body live closed check-in: 2f8cbedc64 user: dmestas tags: landing-live
16:53 • Edit [3ed6e6b891]: Add "ci-pass" with value "60251f9377b45e1ee53ab3ae56dd197c". artifact: 35909eb9e8 user: quarry
16:53
land landing-paragraph check-in: 3ed6e6b891 user: dmestas tags: trunk
16:53 • Edit [3ed6e6b891]: Add "landing" with value "f09ce84f027b50b2fd7b254d42667f895e229811599d94675c3fe2ac3e7392c5". artifact: 77ec4e93c3 user: quarry
16:53 • Reply: Paragraph-length landing titles render as prose artifact: 2cd47bcd2e user: dmestas
16:53 • Edit [5f4b40b254]: Mark "Closed". artifact: e0d1d39200 user: quarry
16:52 • Edit [5f4b40b254]: Add "ci-pass" with value "0dcc5f0dba639094aa1ab59cfda1b363". artifact: 737d0fac7d user: quarry
16:51 • Post: Paragraph-length landing titles render as prose artifact: f09ce84f02 user: zeitgeist
16:51
A paragraph-length landing title renders as prose, not an h1 closed check-in: 5f4b40b254 user: dmestas tags: landing-paragraph
16:45 • Edit [03ac9993bc]: Add "ci-pass" with value "09dbca59c0da999a62d4823adf62eb4e". artifact: c06ebd1b78 user: quarry
16:45
land ingest-stamp check-in: 03ac9993bc user: dmestas tags: trunk
16:45 • Edit [03ac9993bc]: Add "landing" with value "401906b55c67ca8f4a38572c7bb1257c77f6a1c141b0df523a4f0d0ac8aedad2". artifact: a5ea1e6259 user: quarry
16:45 • Reply: CI never ran on today's check-ins because quarry's own ingest was being shed: 19 stores each poll every 2s through a 3-wide ingest lane, and an unchanged store still cost a `zit frames` subprocess per round, so the lane sat saturated all day (shed ~8.6K) and quarry/zit polls lost the lottery. CI triggers, landing verdicts and the ci-pass tag all ride on ingest, which is also why a landing kept spinning after its run finished. artifact: a525973d6b user: dmestas
16:45 • Edit [f4cee0ea87]: Mark "Closed". artifact: f1fcd15069 user: quarry
16:44 • Post: CI never ran on today's check-ins because quarry's own ingest was being shed: 19 stores each poll every 2s through a 3-wide ingest lane, and an unchanged store still cost a `zit frames` subprocess per round, so the lane sat saturated all day (shed ~8.6K) and quarry/zit polls lost the lottery. CI triggers, landing verdicts and the ci-pass tag all ride on ingest, which is also why a landing kept spinning after its run finished. artifact: 401906b55c user: zeitgeist
16:41 • Edit [f4cee0ea87]: Add "ci-pass" with value "f92af57d1645ab3f818be596e38881b5". artifact: e094f0b593 user: quarry
16:41
Poll a store only when its file moved; idle stores no longer fill the ingest lane closed check-in: f4cee0ea87 user: dmestas tags: ingest-stamp
16:39 • Edit [9c5aae6530]: Add "ci-pass" with value "6adc08cb011f1a480a0940838bdd8252". artifact: 7301071316 user: quarry
16:39
Create new branch named "ingest-stamp" check-in: 9c5aae6530 user: dmestas tags: ingest-stamp
16:33 • Edit [b36e09fc2d]: Add "ci-pass" with value "5bdc580f5313be0e7769a8063dd409ff". artifact: 97333af6ed user: quarry
16:33 • Edit [3094f7065c]: Add "ci-pass" with value "eabd9a09f0118b2fc33d4d9398e39f2a". artifact: 5954740356 user: quarry
16:30
land ci-letter check-in: b36e09fc2d user: dmestas tags: trunk
16:30 • Edit [b36e09fc2d]: Add "landing" with value "b30af7afc8fb3e7ae8d3edd779f17c0f65ffdb37ba56a3ed05fa575bce2e0e2d". artifact: f60c9ebdf4 user: quarry
16:30 • Reply: An anonymous visitor could read the whole CI surface: the runs page with logs, gate findings, run pages and streams, the pass badges on timeline and check-in pages, and the run rows on every landing. RFC 0009 had put CI behind the repository read gate on the argument that CI is not more secret than the code; the forge's owner wants otherwise, so CI now takes a letter of its own. 8 is quarry's, since fossil has no CI and no fossil letter names it, and a digit fossil does not use cannot collide with an imported user table. Every role holds it (Reader, Developer, Maintainer; Admin has everything), the signed-in defaults of Public project and Members only hold it, the nobody category never does, and it is a fourth box under Anyone signed in may also. Two layers enforce it: ci.list and ci.gate.list declare the letter for the API, and the ops that carry CI facts beside other things (timeline rows, check-in pages, landing records and lists) blank the runs, logs and verdict badges for a caller without it rather than refuse the answer. Required-check policy stays visible on a landing, since it is why the accept is closed. The pages hide the CI tab and put the letter at the door of the runs page, the gate page, the run pages, the fragments and both streams: a visitor is sent to sign in, a signed-in reader without it is refused, and a forge with no capability plane keeps its doors as they were. On zeitforge.app quarry's CI is now visible to its admins and any account with a role, and to nobody else. RFC 0009's capability mapping needs a one-line amendment, left for you. artifact: 37e99f01e4 user: dmestas
16:30 • Edit [3094f7065c]: Mark "Closed". artifact: 366b878cd5 user: quarry
16:29 • Edit [3094f7065c]: Add "ci-pass" with value "648351817be504b9f1376cca5249d338". artifact: 7b4e9aa067 user: quarry
16:02 • Post: An anonymous visitor could read the whole CI surface: the runs page with logs, gate findings, run pages and streams, the pass badges on timeline and check-in pages, and the run rows on every landing. RFC 0009 had put CI behind the repository read gate on the argument that CI is not more secret than the code; the forge's owner wants otherwise, so CI now takes a letter of its own. 8 is quarry's, since fossil has no CI and no fossil letter names it, and a digit fossil does not use cannot collide with an imported user table. Every role holds it (Reader, Developer, Maintainer; Admin has everything), the signed-in defaults of Public project and Members only hold it, the nobody category never does, and it is a fourth box under Anyone signed in may also. Two layers enforce it: ci.list and ci.gate.list declare the letter for the API, and the ops that carry CI facts beside other things (timeline rows, check-in pages, landing records and lists) blank the runs, logs and verdict badges for a caller without it rather than refuse the answer. Required-check policy stays visible on a landing, since it is why the accept is closed. The pages hide the CI tab and put the letter at the door of the runs page, the gate page, the run pages, the fragments and both streams: a visitor is sent to sign in, a signed-in reader without it is refused, and a forge with no capability plane keeps its doors as they were. On zeitforge.app quarry's CI is now visible to its admins and any account with a role, and to nobody else. RFC 0009's capability mapping needs a one-line amendment, left for you. artifact: b30af7afc8 user: zeitgeist
16:02
CI takes a letter of its own: 8 in every role and the signed-in defaults, never in nobody; ops blank CI runs and pages close the CI doors without it closed check-in: 3094f7065c user: dmestas tags: ci-letter
04:14 • Edit [60b5664f24]: Add "ci-pass" with value "80e55d93b2159d4f261037cbcb5100a5". artifact: daa6e63193 user: quarry
04:14
land zit-0.3.7 check-in: 60b5664f24 user: dmestas tags: trunk
04:14 • Edit [60b5664f24]: Add "landing" with value "3d1a6e955f37b0a06b438ec8285dc102df294e425827dcc91967853217ecb19e". artifact: f0c766d5a9 user: quarry
04:14 • Reply: Pin zit 0.3.7. Four read verbs now cost what the image already paid for: grep over a file's history, timeline, info NAME, and reads on caches written by older builds; a forge rendering a page from many info calls sees each at the process-start floor. No artifact, tag or sync change. The 0.3.7 Linux tarball is staged on the host and verifies; the full suite is green locally against zit 0.3.7. artifact: 8cc2ff98ae user: dmestas
04:14 • Edit [0cd3610f2a]: Mark "Closed". artifact: 97fced94d1 user: quarry