Repository navigation
Commit da952c1
chore: upgrade
* chore: upgrade `@altimateai/altimate-core` to 0.7.0 and sync consumer contracts
Engine upgrade 0.5.1 → 0.7.0 (through 0.6.0). Both releases are correctness
releases whose output differs where the old output was wrong: more lineage
edges (derived tables, CTE chains, CTAS/INSERT…SELECT), more PII exposures,
stricter migration verdicts, a new `unbalanced_quote` safety rule, and
validate/transpile/equivalence fixes. One type-surface addition:
`PiiColumnAccess.query_targets`.
Contract sync (consumers still read legacy pre-native-core shapes):
- `altimate-core-migration` tool: read `findings`/`safe`/`overall_risk`
(engine `MigrationResult`) instead of nonexistent `risks` — previously ANY
migration, including `DROP COLUMN`, rendered "Migration: SAFE"; never render
SAFE when the engine call errored; count only non-"safe" findings as risks.
- `altimate_core.migration` handler: coerce empty dialect `"" → undefined`
(`|| undefined`, same as the equivalence handler) so `Schema.fromDdl` does
not throw on the default empty-string dialect.
- `check --checks safety`: read engine `threats[]` (`rule`/`message`/`detail`)
so real threats (e.g. `unbalanced_quote`) render with rule and message
instead of a generic warning.
- `normalizeSeverity`: map engine severities `high → error`, `medium →
warning` — previously both degraded to `info`, so `--fail-on`/`--severity`
silently passed high-risk injections.
- `check --checks pii`: map engine `PiiColumnAccess` (`table`/`column`/
`classification`/`query_targets`/`suggested_masking`); stop assigning the
column NAME to the numeric column-position field; report the exposing alias;
stringify `{ Custom: string }` classifications (also in the query-pii tool
renderer, which printed `[object Object]`).
- `altimate-core-track-lineage` tool: collect edges from `queries[].edges`
(engine `LineageResult`) instead of flat `edges` — previously always
"0 edges"; render `impact_map`; format `{table, column}` refs; render ERROR
instead of "0 edges" when the engine call fails.
- `altimate-core-query-pii` tool: surface new 0.7.0 `query_targets` field as
"Exposed via: …".
- `altimate-core-check` tool: safety renderer and telemetry read
`rule`/`message` with legacy fallback.
Test updates for 0.7.0 behavior:
- Dialect-forwarding fixture: `payload:f` now parses in the default dialect,
so it no longer discriminates; switched to Snowflake time-travel
`AT(OFFSET => -60)` which still does.
- Grade comparison made apples-to-apples (same table, projection-only diff).
- New real-engine tests: `query_targets` contract + rendering, migration
destructive/safe/empty-dialect/error + tool-title regression, track-lineage
edge surfacing + error rendering, check CLI safety `ThreatFinding` (incl.
`high → error` normalization) and PII `PiiColumnAccess` shapes (incl.
`{ Custom }` classification).
- Strengthened previously vacuous migration e2e assertions.
Verification: typecheck clean; test/altimate + test/cli fully green (4750
pass / 0 fail); full-suite failures (MCP/TUI-sound/subprocess) reproduced
identically on 0.5.1 or shown run-to-run flaky with no engine coupling —
pre-existing. Marker check: no upstream-shared files modified. Codex reviewed
twice (found the legacy-shape consumers; verified all fixes non-tautological).
Closes #1089
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: never emit `null` suggestion from `suggested_masking` in PII check
`f.suggestion ?? f.suggested_masking` leaked `null` into the `suggestion`
field when the engine emits `suggested_masking: null`. Coerce to `undefined`
and lock with a test. (Kilo review follow-up on #1090.)
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: sync remaining engine-output consumers flagged by consensus review
Round-2 contract sync for PR #1090, fixing every Critical/Major finding from
the 4-model consensus review (all verified against the live 0.7.0 binary; all
latent since the Python-engine elimination, not 0.7.0 breakage):
Dead gates (silent false-passes):
- `check --checks validate`: gated on envelope `success`, which the handler
sets even for invalid SQL — every file passed. Now gates on `data.valid`,
maps `ValidationError` (`location.line/column`, `suggestions`) and fails
closed on engine failure.
- `check --checks semantic` + `altimate_core_semantics` tool: engine returns
`valid:true` WITH `findings` (cartesian product) — `valid` means
"plannable", not "clean". Both consumers now read `findings` and never gate
on `valid`; tool formatter/title/telemetry follow the findings list.
- `check --checks grade`: read `grade`/`score`/`recommendations`, none of
which `evaluate()` returns — no grade or finding ever surfaced. Now reads
`overall_grade`/`scores.overall`/`lint.findings` and fails closed on the
failure envelope. The check-e2e mock enshrined the fictional shape — fixed.
- `schema.detect_pii` (pii-detector): read `piiData.findings`; engine
`PiiReport` is `{ columns, pii_count, … }` — schema PII scanning returned
zero findings for every scan. Shared `piiColumnsFromReport` now filters
`classification !== "None"` on both the cache and live paths.
Wrong shapes / crashes:
- `altimate-core-compare` tool: read `differences` (engine: `identical`/
`diff_count`/`diffs`, `DiffEntry.change_type`) — different queries rendered
"Compare: IDENTICAL". Error-gated title added.
- `altimate-core-policy` tool: titled on `pass` (engine: `allowed`) — clean
SQL always rendered "VIOLATIONS FOUND"; `metadata.success` now reflects the
envelope and error output no longer contradicts the ERROR title.
- Empty-dialect coercion centralized: new `dialectHint()` in
`native/engine-coerce.ts` applied to all 7 dialect-forwarding handlers
(columnLineage, formatSql, extractMetadata, compareQueries, importDdl +
the two already fixed) — the compare/column-lineage/extract-metadata/
import-ddl tools crashed with `unknown dialect ''` whenever `dialect` was
omitted (the common invocation path).
- `{ Custom: string }` PII classifications rendered `[object Object]` in
classify-pii, the composite check renderer, and the review runner's signed
verdict — shared `classificationToString()` used everywhere; classify-pii
also no longer counts `classification: "None"` rows and error-gates its
title/output; query-pii treats engine `parse_error` as an abstention
(previously rendered CLEAN for unparseable SQL).
- Composite `altimate_core.check` now computes query PII (fail-safe) — the
tool's "=== PII ===" section previously always printed "No PII detected"
because the handler never populated it.
- `ThreatFinding.location` is `[byteOffset, byteLength]` — surfaced as a
`(chars a-b)` range in `check --checks safety` (was dropped entirely).
Tests: real-engine "consumer contract sync (round 2)" block (semantics
valid-gate, compare, policy pass/violation, classify-pii None-filter,
no-dialect tool invocations, query-pii/classify-pii/policy error gating,
composite-check PII, grade contract); CLI-shape tests for validate/semantic/
grade incl. fail-closed cases; pii-detector unit tests against the live
engine + a DuckDB-gated e2e; legacy formatter tests updated to real shapes.
Also filed upstream: stale `SafetyRule` union in the engine's index.d.ts
(altimate-core-internal#764). Codex-verified twice: all shape corrections
match the installed 0.7.0 engine; its five review findings (parse_error
abstention, grade fail-closed, byte-length location, contradictory failure
outputs, untracked files) are addressed in this commit.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: address cubic round-2 review — runner PII extraction + consumer polish
- `review/runner.ts`: the composite check's `data.pii` is now the engine
`PiiQueryResult` object — extract columns from `pii_columns` (legacy array
shape kept as fallback) so check-derived PII columns reach the signed
review verdict.
- Composite check renderer: surface `query_targets` ("exposed via: …") and
honor the engine's `parse_error` abstention ("PII check skipped: …")
instead of rendering "No PII detected" for unparseable SQL.
- `pii-detector`: band numeric engine confidence (0..1) to
`high`/`medium`/`low` via shared `bandConfidence` — `PiiFinding.confidence`
is a string field.
- `check --checks validate`: normalize string-shaped `suggestions` entries as
well as `Suggestion` objects.
- Safety location label: `bytes a-b` (engine offsets are byte-based and
diverge from char indexes on multibyte SQL).
- Semantics tool metadata reports `result.success` instead of hardcoding
true (consistent with the policy/compare tools).
- `classify-pii` tool reuses `piiColumnsFromReport` instead of a second
None-filter implementation.
- Tests: classify-pii error case made deterministic (malformed schema file —
previously guarded by an `if`, so it could pass vacuously); composite-check
alias + parse-error abstention assertions added; bytes label updated.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: cubic round-3 polish — no eager NAPI load from tool imports
- Move `piiColumnsFromReport` into `native/engine-coerce.ts` (re-exported from
`pii-detector` for compatibility) so `altimate-core-classify-pii` no longer
pulls the native NAPI binding eagerly at tool-registry load time.
- `bandConfidence`: missing confidence maps to "medium" (unknown), restoring
the previous default instead of degrading to "low".
- classify-pii error test: temp dir created outside `try` but cleaned in
`finally` regardless of setup failure.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: address round-4 review comments (Codex connector, CodeRabbit, Kilo)
Abstention and fail-closed hardening:
- `check --checks pii`: engine `parse_error` abstentions now produce an
error finding ("PII analysis skipped: …") instead of an empty pass —
`--fail-on` no longer PASSes files whose PII analysis never ran.
- Composite `altimate_core.check`: a thrown `checkQueryPii` now marks the
PII section as an abstention (`parse_error`) instead of leaving `{}`,
which rendered a false-clean "No PII detected"; `formatCheckTitle`
reports "PII check skipped" instead of PASS for abstained-but-clean runs.
- `schema.detect_pii`: per-column classify failures are counted and flip
`success` to false (fail closed) instead of being silently swallowed;
`piiColumnsFromReport` now throws on malformed reports (missing/non-array
`columns`) rather than yielding zero findings.
- `altimate_core_query_pii` tool: abstentions set `metadata.success: false`
so telemetry's soft-failure classification records them.
Correctness:
- `check --checks grade`: per-file grades (`results.grade.grades`) — the
shared `gradeValue`/`gradeScore` raced across concurrent batch promises,
keeping whichever file finished last; flat `grade`/`score` retained for
single-file runs only.
Module shape / dedup:
- `engine-coerce.ts` gets the AGENTS.md-prescribed `EngineCoerce`
self-reexport; all consumers import the namespace projection.
- `review/runner.ts` drops its local `bandConfidence` for the shared one;
shared version now bands missing/non-numeric confidence as "medium"
(matching the runner's previous behavior).
Tests: CLI PII-abstention and multi-file grade regression tests;
"PII check skipped" title test; strict malformed-PiiReport assertions;
classify-pii e2e asserts a positive `pii_count` lower bound; DuckDB e2e
closes its connector and restores the telemetry env var on teardown.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-5 review follow-through — failed scans and warnings must surface
- `schema_detect_pii` tool: honor `success: false` from `detectPii` — a scan
that failed for any column now renders "PII Scan: ERROR" (with any partial
findings attached) instead of a clean "no findings" verdict. The previous
round made the detector fail closed but left its only user-facing consumer
branching on `finding_count` alone. (cursor High / cubic P1 / Codex P2)
- `check --checks grade`: flat `grade`/`score` gated on the invocation file
count, not surviving-grade count — with several files where all but one
grade call failed, the flat fields would have misattributed the survivor.
(CodeRabbit Major)
- `altimate_core_policy` tool: `allowed: true` with non-empty `warnings` now
renders the warnings with the pass instead of hiding them behind the early
"passes all policy checks" return. (Codex P2)
- `review/runner.ts`: PII column extraction includes `query_targets` output
aliases (e.g. `SELECT email AS contact` exposes `contact`), not just source
columns. (Codex P2)
- Tests: fail-closed detect-pii tool cases (zero and partial findings),
policy warnings-on-pass case.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-6 review polish — alias preference + grade nested findings
- `review/runner.ts`: when a PII column has `query_targets`, report ONLY the
output aliases — the source column name is not present in the model output,
so including it flagged a column that isn't there (`SELECT email AS contact`
now reports `contact`, not `email` + `contact`).
- `check --checks grade`: findings now come from all nested EvalResult
sections (lint.findings + validation.errors + safety.threats) — a failing
grade with clean lint no longer yields an empty, passing finding list.
- Regression test for the nested-findings case.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: preserve locations/suggestions in nested grade findings
`runGrade`'s nested `validation.errors`/`safety.threats` went through the
shared flat mapper, dropping the line numbers and fixes that `runValidate`/
`runSafety` already surface. Normalize each shape first: `ValidationError`
hoists `location.{line,column}` and the first `suggestions[]` entry;
`ThreatFinding` renders its `[byteOffset, byteLength]` range into the message
and maps `detail` to the suggestion. Regression assertions added.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: address post-approval review follow-ups
All items from the approving human review, except where noted in the PR reply:
Introduced by this PR:
- `classificationToString` default fallback unified to "UNKNOWN" across all
call sites (was "PII"/"UNKNOWN"/"" depending on caller — an unrecognized
classification no longer renders as a positive PII assertion).
- `pii-detector-e2e.test.ts` gets the same NAPI-availability guard as
`altimate-core-e2e.test.ts` (skip, not crash, when the binary is absent).
- The `unbalanced_quote` check-e2e fixture SQL is now engine-faithful (a
dangling quote, which the live 0.7.0 runtime genuinely flags with that
rule — only the stale `SafetyRule` union omits it; upstream issue #764).
Adjacent pre-existing:
- `check --checks policy`: violations map `remediation` into the suggestion.
- `sql.format` / `sql.column_lineage` handlers: last two raw dialect
forwards coerced via `EngineCoerce.dialectHint`.
- Review runner: composite `validation.errors` and `safety.threats` now
flow into review issues alongside lint findings.
- `runSafety` dispatcher-failure fallback fails closed (error severity via
`dispatcherErrorFinding`, matching every other check).
- Runner grade reads `overall_grade` before the legacy `grade`.
Nits:
- `runSemantic`'s valid:false fallback surfaces `validation_errors` detail.
- Dead `line`/`column`/`code` reads dropped from the threats mapper.
- Byte ranges render the INCLUSIVE end (`[37,7]` → `bytes 37-43`) in both
places; tests updated.
- `normalizeSeverity` documents the intentional low→info mapping.
- PII findings carry a machine-readable `columnName` field.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-7 review polish — threat normalization in review lane + fail-closed partials
- Review runner: composite `safety.threats` are normalized before joining
review issues — engine severities (`critical`/`high` → error, `medium` →
warning, `low` → info) and the byte-tuple `location` dropped, so the
quality lane classifies threats as errors instead of suggestions.
- `check --checks safety`: a `success:false` envelope now appends the
fail-closed error finding even when partial sub-error threats were
returned — `--fail-on error` can no longer pass a crashed scanner.
- Semantics tool: abstentions (`validation_errors`) set
`metadata.success: false` so telemetry records the soft failure
(consistent with query-pii); contract test updated accordingly.
- Shared `byteRange()` helper replaces the duplicated inclusive-range
formula in `runSafety`/`runGrade`.
- `pii-detector-e2e.test.ts` defers the pii-detector import until after the
NAPI-availability guard (static import defeated the guard).
- Fixture cleanup: stale `matched_pattern`/comment from the old OR 1=1
payload removed; new fail-closed partial-threats test.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-8 review polish — lint-only validation gating, diff-scoped safety, CLI policy warnings
- Review runner: validation errors from the composite check are surfaced
ONLY when a real schema exists — in lint-only mode the throwaway
`_altimate_lint_` schema marks every real table unknown and would flood
the review (restores the documented intent of that mode).
- Composite `altimate_core.check`: safety threats are diff-scoped like lint
when `base_sql` is supplied — threats already present in the base
(matched by rule + matched_pattern) are pre-existing, not introduced by
the change. Real-engine regression test added.
- `check --checks policy`: advisory `warnings[]` on an allowed result now
surface as info findings (they do not fail the check). Test added.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-9 review polish — sound diff-scoping + composite lintDiff schema bug
- Safety diff-scoping is now a MULTISET subtraction (one base occurrence
consumes one head occurrence of the same rule + matched_pattern) — a PR
that adds a second identical injection still reports it; `safe` and
`risk_score` are recomputed when every threat is pre-existing so the
verdict doesn't stay stale-unsafe.
- PII exposures are diff-scoped the same way: (table, column) pairs already
exposed by the base are not reported as introduced.
- Validation is deliberately NOT diff-scoped: the engine validates fail-fast
(only the first error is reported), so base subtraction can hide genuinely
new breakage behind a pre-existing error — proven by test; re-reporting a
pre-existing error is the safe mode, documented inline.
- Pre-existing bug found while testing: the composite check with `base_sql`
+ a flat agent schema_context crashed with "missing field tables" — lintDiff
takes SchemaDefinition JSON; now normalized via `normalizeSchemaContext`
(exported from schema-resolver). This made every diff-scoped composite call
with a flat schema fail closed since the lintDiff wiring landed.
- Semantic CLI abstention severity: error when a schema was provided (the
analysis should have run), warning schema-less (abstains routinely).
- Policy tool telemetry includes advisory warnings (`policy_warning`).
- `pii-detector` gets the AGENTS.md namespace self-reexport.
Co-Authored-By: Claude Fable 5 <[email protected]>
* fix: round-10 review polish — alias-aware PII scoping + scoped scores
- PII diff-scoping identity now includes the sorted `query_targets` — adding
or renaming a SELECT-list alias for an already-exposed column is a NEW
output exposure and surfaces; identical exposures stay filtered. Regression
test covers rename vs identical.
- `risk_score` is recomputed (documented severity-based approximation) when
only SOME threats are pre-existing, instead of keeping the full head
scan's score; `risk_level` resets to "None" when every PII exposure was
pre-existing.
- `schema-resolver` gets the AGENTS.md `SchemaResolver` self-reexport; the
new `normalizeSchemaContext` consumer uses the namespace projection.
Co-Authored-By: Claude Fable 5 <[email protected]>
---------
Co-authored-by: Claude Fable 5 <[email protected]>@altimateai/altimate-core to 0.7.0 and sync consumer contracts (#1090)1 parent e0a1232 commit da952c1
26 files changed
Lines changed: 1641 additions & 210 deletions
File tree
- packages/opencode
- src
- altimate
- native
- schema
- sql
- review
- tools
- cli/cmd
- test
- altimate
- cli
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
78 | 78 | | |
79 | 79 | | |
80 | 80 | | |
81 | | - | |
| 81 | + | |
82 | 82 | | |
83 | 83 | | |
84 | 84 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| 12 | + | |
12 | 13 | | |
13 | | - | |
| 14 | + | |
14 | 15 | | |
15 | 16 | | |
16 | 17 | | |
| |||
168 | 169 | | |
169 | 170 | | |
170 | 171 | | |
171 | | - | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
172 | 177 | | |
173 | 178 | | |
174 | 179 | | |
| |||
177 | 182 | | |
178 | 183 | | |
179 | 184 | | |
180 | | - | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
181 | 188 | | |
182 | 189 | | |
183 | | - | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
| 260 | + | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
184 | 265 | | |
185 | | - | |
| 266 | + | |
186 | 267 | | |
187 | 268 | | |
| 269 | + | |
188 | 270 | | |
189 | 271 | | |
190 | 272 | | |
| |||
323 | 405 | | |
324 | 406 | | |
325 | 407 | | |
326 | | - | |
327 | | - | |
328 | | - | |
329 | | - | |
| 408 | + | |
| 409 | + | |
| 410 | + | |
| 411 | + | |
330 | 412 | | |
331 | 413 | | |
332 | 414 | | |
| |||
337 | 419 | | |
338 | 420 | | |
339 | 421 | | |
340 | | - | |
341 | | - | |
| 422 | + | |
| 423 | + | |
| 424 | + | |
342 | 425 | | |
343 | 426 | | |
344 | 427 | | |
| |||
432 | 515 | | |
433 | 516 | | |
434 | 517 | | |
435 | | - | |
| 518 | + | |
436 | 519 | | |
437 | 520 | | |
438 | 521 | | |
| |||
453 | 536 | | |
454 | 537 | | |
455 | 538 | | |
456 | | - | |
| 539 | + | |
457 | 540 | | |
458 | 541 | | |
459 | 542 | | |
| |||
464 | 547 | | |
465 | 548 | | |
466 | 549 | | |
467 | | - | |
| 550 | + | |
468 | 551 | | |
469 | 552 | | |
470 | 553 | | |
| |||
474 | 557 | | |
475 | 558 | | |
476 | 559 | | |
477 | | - | |
| 560 | + | |
478 | 561 | | |
479 | 562 | | |
480 | 563 | | |
| |||
528 | 611 | | |
529 | 612 | | |
530 | 613 | | |
531 | | - | |
| 614 | + | |
532 | 615 | | |
533 | 616 | | |
534 | 617 | | |
| |||
| 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 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
87 | | - | |
| 87 | + | |
88 | 88 | | |
89 | 89 | | |
90 | 90 | | |
| |||
120 | 120 | | |
121 | 121 | | |
122 | 122 | | |
| 123 | + | |
| 124 | + | |
0 commit comments