Development record
With a git email that is not a GitHub noreply address, every reservation act calls gh api user again, uncached.
issueresolvednitpickiss-2610161015433495
With a git email that is not a GitHub noreply address, every reservation act calls gh api user again, uncached.
Grounds
- pursued: we expect a drain move that makes several reservation acts to ask GitHub for the holder once; shown wrong if the gh stub in TestThreeReservationActsAskTheForgeForTheHolderOnce records more than one user-endpoint call, or a failed ask is served from the cache
Frontmatter
| id | iss-2610161015433495 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-2610161015433495-with-a-git-email-that-is-not-a-github.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610161016401115Drains run unattended and visiblyrelated
mentions2
- dcn-26101610403949702026-10-16 — A drain lane's stage shows in abcd peers (facilitator-on-delegation, drain-many-accounts): a drain lane's stage is published as a closed-vocabulary trailer on its reservation's renewal commits, and abcd peers lists it beside the reservation with each holder's hand-back tombstones of the last day; the people's status view inherits the same rows when it takes the reservation listing over (itd-2609151838312703, iss-2610150726331622); and the holder a process resolves through the forge is cached for that process (grounds: the reservation is the record every account already fetches, so the stage costs no new act; iss-2610161015434746, iss-2610161015433495).
- spc-2610161044461448drain-many-accounts