Skip to content

Actions: Nitjsefnie/Overflow

Actions

claim

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
claim.yml
217 workflow runs
217 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Reconciliation refetches every issue every pass instead of asking what changed since the last one claim #217: Issue comment #196 (comment) created by Nitjsefnie
1s
1s
A fold that has lost its advisory lock can still overwrite a newer fold's result claim #216: Issue comment #210 (comment) created by Nitjsefnie
7s
7s
Issue comments are settlement evidence but no webhook subscribes to them claim #215: Issue comment #231 (comment) created by Nitjsefnie
11s
11s
The GraphQL reserve admits a pass but does not bound it, so one fold can still spend past zero claim #214: Issue comment #229 (comment) created by Nitjsefnie
1s
1s
Every deploy re-reads every repository, with no way to suppress the startup reconciliation pass claim #213: Issue comment #228 (comment) created by Nitjsefnie
8s
8s
Reconciliation refetches every issue every pass instead of asking what changed since the last one claim #212: Issue comment #196 (comment) created by Nitjsefnie
11s
11s
The GraphQL reserve admits a pass but does not bound it, so one fold can still spend past zero claim #211: Issue comment #229 (comment) created by Nitjsefnie
8s
8s
Every deploy re-reads every repository, with no way to suppress the startup reconciliation pass claim #210: Issue comment #228 (comment) created by Nitjsefnie
10s
10s
Nothing checks that a pull request follows the template or that an issue is assigned claim #209: Issue comment #55 (comment) created by Nitjsefnie
7s
7s
Reconciliation refetches every issue every pass instead of asking what changed since the last one claim #208: Issue comment #196 (comment) created by Nitjsefnie
1s
1s
Repairing a fold defect relies on re-reading everything, with no way to ask for a re-derivation claim #207: Issue comment #197 (comment) created by Nitjsefnie
1s
1s
Reconciliation refetches every issue every pass instead of asking what changed since the last one claim #206: Issue comment #196 (comment) created by Nitjsefnie
1s
1s
A query queued at shutdown never settles and the client keeps reconnecting after the shutdown resolved claim #205: Issue comment #223 (comment) created by Nitjsefnie
9s
9s
Closing the database clients never completes when a connection dies while it is still opening and reconnects are closed without an error claim #204: Issue comment #164 (comment) created by Nitjsefnie
11s
11s
Issue comments are settlement evidence but no webhook subscribes to them claim #203: Issue comment #231 (comment) created by Nitjsefnie
1s
1s
Repairing a fold defect relies on re-reading everything, with no way to ask for a re-derivation claim #202: Issue comment #197 (comment) created by Nitjsefnie
10s
10s
The GraphQL budget hold treats every sponsor's quota as one number, so one sponsor's reading decides another's reconciliation claim #201: Issue comment #225 (comment) created by Nitjsefnie
1s
1s
Reconciliation reads its remaining GraphQL budget on every query and discards it, so it spends to zero and stops claim #200: Issue comment #219 (comment) created by Nitjsefnie
1s
1s
The GraphQL budget hold treats every sponsor's quota as one number, so one sponsor's reading decides another's reconciliation claim #199: Issue comment #225 (comment) created by Nitjsefnie
9s
9s
Reconciliation refetches every issue every pass instead of asking what changed since the last one claim #198: Issue comment #196 (comment) created by Nitjsefnie
2s
2s
fix: round calibration deltas for display claim #197: Issue comment #67 (comment) created by Nitjsefnie
1s
1s
The GraphQL budget hold treats every sponsor's quota as one number, so one sponsor's reading decides another's reconciliation claim #196: Issue comment #225 (comment) created by Nitjsefnie
1s
1s
A query queued at shutdown never settles and the client keeps reconnecting after the shutdown resolved claim #195: Issue comment #223 (comment) created by Nitjsefnie
9s
9s
fix: use singular noun when count is 1 in four sites claim #194: Issue comment #188 (comment) created by Nitjsefnie
1s
1s
Closing the database clients never completes when a connection dies while it is still opening and reconnects are closed without an error claim #193: Issue comment #164 (comment) created by Nitjsefnie
11s
11s