Repository navigation
Commit a661e43
authored
feat(limrun): serve iOS alert get/wait/accept/dismiss from tree capture (#3699)
* feat(limrun): serve iOS alert get/wait/accept/dismiss from tree capture
Limrun iOS direct sessions refused all four alert legs with
unsupported-provider-mode even though the session's element-tree capture
already shows the system alert and its touch seam can press its buttons.
Issue #3349.
Detect the alert from the capture: a system alert arrives as its own
blank-label AXApplication root hosting text and pressable buttons, while
the app's own UIAlertController rides the app's named root, so app-owned
dialogs stay app UI. Accept and dismiss press exactly the button whose
label states the asked-for choice and confirm the alert is gone; an
ambiguous choice is reported, never guessed, and dismiss never
authorizes tracking. The four legs bind through the same catalog and
facts the Android tree-based legs already use.
* fix(limrun): harden iOS alert detection against ambiguous sheets
Review follow-up on the alert legs: a sheet must offer at least two
pressable choices, launch-icon buttons never qualify, a capture whose
host sheets disagree is refused instead of shadowing one with the
other, and an action fires only when exactly one button states its
choice. The legs' poll/confirm budgets now spend through an injected
sleep seam so their tests drive the clock, a malformed timeout fails as
a bounded default instead of an unbound loop, and the grant vocabulary
covers the iOS variants (Allow Once / While Using App / All the Time)
and Close App. User docs and CHANGELOG updated.
* refactor(alert): drive every tree-based alert backend through one shared driver
PR #3699 review: the Limrun iOS alert legs duplicated the Android tree-alert
driver (poll, confirm, same-alert, response building) and its label
vocabulary. Both backends now reach those steps through one backend-neutral
driver, runTreeAlertAction in platform-android (exported via the mechanics
facet provider-limrun already depends on), and classify button roles
through one English vocabulary that lives in contracts/alert-contract with
the alert budgets and typed reasons (contracts owns vocabulary only; the
driver loop owns the AppError/timer mechanics R18 keeps out of contracts).
Each backend supplies only its own seams: Android wraps its dump reader
and keeps its platform-id roles, neutral/Back fallbacks, and tap/Back
presses; Limrun supplies the blank-root process-exclusive host reader,
the label-strict chooser, and client.tap. The confirm-on-ambiguous-capture
and duplicate-label threads settle once in the shared code: the three-way
alert|none|undecided observation gates confirmation in the driver, and
selectUniqueAlertButtonByRole refuses duplicated roles at the shared
choice boundary. The deadline order resolves to read-first: over a
positive window both predecessor loops already observed before waiting.
The alert-not-found and undecided refusals now carry the same typed
details.reason and dispatched: 'no' on both backends.
* refactor(alert): ride main's deadline primitive with no sleep seam
origin/main migrated the Android alert loops to pollUntilSettled/Deadline
and moved timing into fake timers at the test edge. The shared driver
adopts the same shape: poll/confirm run on the deadline primitive, so the
driver-owned sleep seam is dead weight and goes — Limrun's tests now drive
the clock the way the migrated Android tests do.
* test(limrun): pin the accept-once/second-get-none timeline and satisfy catch-name lint
Adds the maintainer's live-validated sequence at the unit seam: accept
taps exactly once, and a following get on the same seam reports no alert.
Renames catch params to satisfy oxlint's catch-error-name (three
findings the affected gate reported).
* fix(alerts): resolve multi-grant sheets by a declared preference table
The unique-role choice boundary refused exactly the sheets the fix is
for: Android 11+'s permission_allow_foreground_only_button and
permission_allow_one_time_button both classify accept, and iOS's
'Allow Once'/'Allow While Using App' sheet refused the same way. The
shared vocabulary is now a per-role preference table: distinct grants
resolve by declared rank (a lasting grant before a one-time grant), and
the acting legs refuse only when the capture names no single physical
button — the same label at two points, or vocabulary-free multiplicity.
Android keeps its neutral-button/Back fallback, Limrun keeps none.
* fix(alerts): type the undecided state and bound the seams each budget owns
Three review findings on the shared tree-alert driver, plus the test
that masked a polling loop:
- alert get on a tree backend answered undecided exactly like absence
(alert: null, message-only difference). The result now carries a typed
status (visible/none/undecided) so clients switch on states, not text.
- The budgets bounded only the poll sleeps: a capture or press that hung
could outrun the leg. Each leg now builds a window (deadline clock plus
the joined window/caller signal) that reaches the capture and press
seams; the Android legs hand it to the snapshot capture and the adb
input sends, which kill their child on abort. A capture that lands
once its window closed is refused on a typed alert-window-expired
reason and never consumed or pressed; a press cut off mid-flight says
dispatched: unknown, one refused before dispatch says no.
- Limrun's WebSocket transport exposes no abort on elementTree/tap
(checked against the shipped typings), so the consumption rule is what
keeps it honest, and the SDK gap is stated rather than papered over.
- The awaitAlert first-capture test now asserts the capture count; its
same-alert fixture had made it vacuous.
* fix(alerts): close the window holes the review found and cap the budget
The shared tree-alert driver consumed an answer from a poll that started
after its window closed (the loop tests settled before remaining, and an
expired-at-start probe rode unguarded), and its first probe paid the
Android helper cold start inside the action budget, aborting the very
read that leg was about to press on — the executed smoke failure. The
first observation is now read-first, unarmed, consumed once, and arms
the window behind it; a later probe starting past the deadline never
captures at all, and the press rides the armed window.
- contracts: a mix of ranked and unranked role candidates refuses
instead of letting the one known label win (selectRankedAlertButton-
ByRole); MAX_ALERT_WINDOW_MS names the timer ceiling the daemon
refuses above (INVALID_ARGS) and the driver defaults above.
- android: same-label dedup keys on the physical center, so nested
nodes collapse and two distinct OKs reach the shared refusal; the
input dispatch option type owns cancellation only, and the tap
forward picks fields so allowFailure cannot reach the transport.
- docs: alert-window-expired/none/undecided reasons stated exactly per
phase, Limrun's non-abortable transport described as post-capture and
pre-press guards with the hung-request limit named.
Prose at the driver trims to invariants.
* fix(alerts): scope alert captures to the warm helper and split the unconfirmed press
The executed Android smoke failure at 5b1e1c1: the session's alert probes
ran without the app-backed helper session scope, so each probe cold-started
the snapshot helper inside the window that bounds it — the request log shows
the post-press confirm capture aborted at 2.3s ("operation was aborted due
to timeout") while the canary proves the dialog was in fact dismissed. Alert
reads now carry the same helperSessionScope as every other app-backed read.
The failure also proved the wording lied: with no confirm capture ever
answering, "did not dismiss the visible alert"/"dialog is still visible"
accused a dialog that was already gone. Only a re-read naming the same alert
earns the still-visible failure; an unconfirmed press now says exactly that,
on both the cut-off and the spent-budget exits, with a hint to run alert get
before retrying. The same-alert stuck-alert failure keeps its message.
Pinned: interactor scoping regression (fail-before against 5b1e1c1) and
the three Limrun confirm-phase tests moved to the truthful split; the
Android still-visible pin keeps its message via the same-alert path.
* fix(alerts): let only the latest answered capture claim a visible dialog
Two review findings on the confirm split, one batch:
- The spent-budget exits of confirmTreeAlertDismissed omitted
details.reason, while commands.md promises every post-press failure
branches on alert-window-expired. Both unconfirmed and still-visible
failures now carry the typed reason, pinned in the Android and Limrun
suites.
- The same-alert flag latched on the first matching capture, so a later
undecided re-read still reported the dialog as currently visible.
Each probe now replaces the verdict with its own observation: the
still-visible failure requires the latest capture that answered to
name the same alert, and a fresher undecided read exits as an
unconfirmed press. A probe whose capture never answered is not a
completed observation, so the thrown cutoff keeps saying only that
the press went unconfirmed, at any earlier match.
Pinned fail-before at the pre-fix alert.ts: same-alert then undecided
to budget-end, and same-alert then a hung capture, both expect the
unconfirmed message and the typed reason. The helper-scope comment is
trimmed to the non-obvious constraint per AGENTS.
* fix(alerts): a deadline-straddling confirm capture cannot erase an answered sighting
The Coverage run at f584e8a (38924441176) failed the maintainer-owned
provider-integration scenario 'Android alert accept fails when the dialog
stays visible' — a suite the affected gate's related-test selection does
not reach, so the local exact-head receipt never ran it. The driver, not
the oracle, was wrong: f584's confirm catch downgraded every thrown cutoff
to unconfirmed, discarding the captures that had answered before it. On CI
the final confirm capture starts inside the 2s window and lands past it
(the thrown path); locally it starts after the deadline (the sentinel
path), which is why the same commit passed one and failed the other. The
dialog had been re-named by answered reads; the error claimed the check
never answered.
The latest-completed-observation rule from review thread r4296070770 and
from commands.md is: the latest capture that ANSWERED carries the claim.
A hung probe is not an observation, so the cutoff now reports
still-visible when an answered capture named the alert, and unconfirmed
only when none did — the 2482e24 smoke case, with no answer at all. The
undecided-overrules-match case is unchanged: undecided is an answered
observation. Pin flipped to the CI timeline (fail-before at f584's catch);
all 128 alert-family tests and the 197-test provider-integration project
pass at this working tree.
* test(alerts): pin the press cutoff's dispatched disclosure; review nits
The independent review of f584e8a returned merge-ready with three
follow-up-scale findings, batched here:
- The documented `dispatched: 'unknown'` press-cutoff failure had no test.
Pinned in the Android suite with the real transport shape: the adb fake
hangs the tap until the 2s action window closes and dies with the
signal; the failure must disclose unknown, never 'no'. Mutation-checked:
flipping the disclosure to 'no' fails the pin.
- The `[timeout]` positional is honored by `alert wait` only — the Apple
acting legs pass fixed runner budgets and the tree legs run their own
lookup/confirm windows; commands.md now says the argument is wait-only
per backend instead of leaving the silence to surprise callers.
- `void device;` in limrunAlertOperationFacts follows the `_device`
convention; the two byte-identical visible-after-press exits collapse
into one helper, keeping the two hints that genuinely differ (latest
read hung vs budget ended unresolved).
No behavior change for any message, reason, or tap.
* fix(alerts): let started probes finish, rank Android grants by id
The maintainer review at be48a28 named two defects and a design
simplification; this applies all three.
Budget rule (whole): the alert budget now bounds only how long a leg
polls. pollUntilSettled awaits every probe it starts, the deadline ends
the loop, and only the caller's cancellation stops a capture or press in
flight. A quiet screen answers alert-not-found with dispatched:no on
every backend, never a reason that depends on which capture crossed the
deadline; the late positive that used to be refused is consumed and
pressed, per the rule the maintainer asked for and this supersedes the
earlier late-answer-refusal contract.
Grant ranking: the shared choice boundary takes a backend rank first and
the label vocabulary only where the backend declares nothing. Android
declares the permissioncontroller grant ids (foreground-only, always,
one-time), so a Spanish Android 11+ sheet and the Android 10 foreground
copy resolve to the lasting grant instead of refusing; equal ranks and
candidates no rank reaches keep refusing.
Design: the driver moved to capture-kit/alert-tree-driver (Limrun no
longer depends on platform-android), treeAlertWindow/arm/start, the
delegating clock, the window-closed sentinel, lastCaptureNamesAlert, and
the exception paths are gone; net production diff vs be48a28 is -161
lines. Docs and CHANGELOG state the chosen behavior.
* fix(alerts): keep the mechanics façade lazy, honor cancel at every post-press seam, rank only on one scale
Follow-up to the review at 5cfe029:
- platform-android: load the shared tree-alert driver behind the alert
entry's function-scoped import (types stay static), so mechanics.ts keeps
its merge-base eager closure (177->176, the gate's owning-edge rule).
- capture-kit driver: a caller cancel is typed dispatched:'unknown' from
the press onward even when a non-abortable transport RESOLVES after the
cancel or the cancel lands in the confirm window, and a cancel that rode
a straddling lookup probe refuses cleanly (dispatched:'no', no press).
- contracts: selectRankedAlertButtonByRole refuses pairs mixing backend
id-ranks with label-table positions — different scales are not
comparable; same-source conflicts still let the owning backend win.
- tests: deterministic started-gated cancel pins (no unreachable mock
branches), Limrun no-abort capability pins, backend-rank-override and
mixed-scale pins at the contract seam, faithful vendor-id fixture.
- docs: correct the CHANGELOG/commands/driver claims about Limrun
cancellation (started calls run to their answer; the leg ends at the
next seam cancel can reach), scope the quiet-screen guarantee to
accept/dismiss, and limit the details.reason promise to driver
refusals; fix the stale platform-android module comment.
* docs(alerts): state the real lazy-load constraint, cancel truth, and confirm-never-started pin
- platform-android/alert.ts: drop the false comparison to how the Limrun
provider loads its own alert file; the comment now states only the real
constraint — a static driver import would grow the mechanics facade past
its merge-base eager-closure budget (ADR-0019).
- commands.md: replace 'the next seam cancellation can reach' with what
the reader observes: a Limrun request already sent is not stoppable;
cancellation lands once that request answers; restarting the instance
session clears a stall. Human-rule facts unchanged.
- alert.test.ts: the resolves-after-cancel pin also asserts the leg ended
before any confirm read started (elementTree exactly once).
* fix(alerts): type the transport-death cancel as pre-press, and make the stall docs exhaustive
R6-review P3 follow-ups (report /tmp/3349-r6-review-report-3e1e.md):
- capture-kit driver: a capture whose transport died with the caller's
cancellation exits through observeTreeAlert, which is always pre-press
(acting legs never press before the lookup returns) — it now carries the
clean dispatched:'no' like the other pre-press exit instead of omitting
the key; both backend pins assert it. Pins fail without the key.
- capture-kit driver: correct the seam comment's attribution — the caller
learns of its cancellation from its own client transport; the daemon's
answer lands once the leg settles on the started probe's answer.
- commands.md: the Limrun stall sentence enumerates the SDK's own ~30 s
request timeout (verified against @limrun/[email protected] sendRequest) as a
route the unanswered request resolves on, instead of reading exhaustive.
* docs(capture-kit): scope the transport-death cancel comment to the routes that end here
R7 P3 / inline r4300817984: 'always a pre-press exit' overstated the
catch's reach — confirmTreeAlertGone polls through the same
observeTreeAlert, so a cancel mid-confirm-probe reaches it post-press
(harmless: the actOnTreeAlert press/confirm catch re-types it to
dispatched:'unknown', which owns that invariant). The comment now states
where each typed answer is owned instead of asserting a false
reachability fact. No behavior change.
* fix(alerts): state each permissioncontroller grant's role and rank in one table
The maintainer's rule for the Android media sheet: every id the Android
classifier maps to a role must carry a rank in the same declaration, so
an accept-by-id with no rank cannot exist. The partial-media sheet's
permission_allow_all_button and permission_allow_selected_button both
classified accept by id with no backend rank, and on the English sheet
the mixed-source pair refused where main pressed "Allow all".
- PERMISSION_GRANT_ID_SLOTS is now the one declaration: one slot per
rank, role and rank read together. Full access, then foreground-only,
then plain/always, then the picker-limited selection, then one-time;
the deny ids rank on the same scale (plain deny before its
don't-ask-again variants). An unknown controller id keeps the
prefix-only role with no rank, so it can only ever refuse.
- Tests pin the AOSP media-sheet ids at the choice boundary and at the
tap seam, a cohesion sweep over every declared id, and the two-deny
scale.
- commands.md names the media-sheet order; the limrun test's stale
platform-android driver comment and the driver header's narration are
corrected to the invariants.
* fix(alerts): refuse every undeclared permission grant instead of pressing it
The maintainer's rule admits no exception: an id the Android classifier
maps to a role must carry its rank in the same declaration. A grant-shaped
id outside PERMISSION_GRANT_ID_SLOTS no longer earns a role from its
prefix, so no path can accept-by-id without a rank: not the single
candidate at the shared boundary, not the single-button or neutral
fallbacks (the sheet-level refusal stops both actions), and not the label
vocabulary. An undeclared grant keeps the sheet represented and makes it
unactionable; dismiss answers with Back, the cancel that grants nothing.1 parent 56618ac commit a661e43
29 files changed
Lines changed: 3539 additions & 244 deletions
File tree
- packages
- capture-kit
- src
- contracts/src
- daemon/src/execution/handlers
- __tests__
- platform-android/src
- __tests__
- provider-limrun/src
- scripts/layering
- src/core/interactors
- website/docs/docs
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
21 | 25 | | |
22 | 26 | | |
23 | 27 | | |
| |||
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
5 | 14 | | |
6 | 15 | | |
7 | 16 | | |
8 | 17 | | |
9 | | - | |
10 | | - | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
11 | 22 | | |
12 | 23 | | |
13 | 24 | | |
| |||
20 | 31 | | |
21 | 32 | | |
22 | 33 | | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
23 | 180 | | |
24 | 181 | | |
25 | 182 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
61 | 64 | | |
62 | 65 | | |
63 | 66 | | |
| |||
76 | 79 | | |
77 | 80 | | |
78 | 81 | | |
79 | | - | |
| 82 | + | |
| 83 | + | |
80 | 84 | | |
81 | 85 | | |
82 | 86 | | |
83 | | - | |
84 | | - | |
| 87 | + | |
| 88 | + | |
85 | 89 | | |
86 | 90 | | |
87 | 91 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
94 | 94 | | |
95 | 95 | | |
96 | 96 | | |
97 | | - | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
98 | 101 | | |
99 | 102 | | |
100 | 103 | | |
101 | 104 | | |
| 105 | + | |
102 | 106 | | |
103 | 107 | | |
104 | 108 | | |
| |||
124 | 128 | | |
125 | 129 | | |
126 | 130 | | |
127 | | - | |
| 131 | + | |
128 | 132 | | |
129 | 133 | | |
130 | 134 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
474 | 474 | | |
475 | 475 | | |
476 | 476 | | |
| 477 | + | |
| 478 | + | |
477 | 479 | | |
478 | 480 | | |
479 | 481 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
140 | 140 | | |
141 | 141 | | |
142 | 142 | | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
0 commit comments