Repository navigation
Commit 7f41309
authored
feat: combined scheduler, web UI, parser and Verify delivery (#1382)
* fix: render SQL Server table functions as inline TVFs and list warehouse Recall relations portably
SQL Server's render_create_function stripped a table function's SELECT and
wrapped it in BEGIN RETURN (...) END, which the engine rejects. A TABLE return
now renders RETURNS TABLE AS RETURN (<query>).
sqb recall schema --backend warehouse matched state relations with
LIKE '\_sqlbuild\_%' ESCAPE '\', which ClickHouse cannot parse. A prefix
comparison with SUBSTRING needs no escape in any dialect.
* feat(lint): warn when SQL lint is unavailable for a dialect
A native lint response can report that the engine does not parse the project's
dialect yet. Each such file now gets one L007 warning carrying the engine's
reason, instead of looking lint-clean. A non-string reason is rejected as an
invalid response.
* fix(sqlserver): quote schema names in EXEC, end MERGE with a semicolon and refuse WITH source expressions
render_create_schema doubled quotes only in the sys.schemas lookup, so a schema
name with a quote broke the EXEC string. render_merge now ends with the
semicolon SQL Server requires. A source expression starting with WITH cannot
sit in a derived table on SQL Server, so it now fails with A715 and a rewrite
hint instead of a warehouse syntax error.
* refactor(analysis): read B101 spellings from a recorded table instead of SQL library probes
The unknown-function check (B101) asked the SQL library's parser which
built-in node each unaccepted call spelling becomes, and took DuckDB's
accepted names from the library's function catalogue. The check now reads
a table of the 41 rejected spellings, each with its argument count and the
spelling the dialect accepts. Every DuckDB row was confirmed unknown to
DuckDB 2.0.0. The call scan takes the analysis dialect name, so analysis
off the library can run it unchanged.
Findings are identical on every DuckDB and Snowflake query of the compiler
differential corpus and on every candidate spelling at 0 to 9 arguments.
The workspace no longer depends on the library's function-catalogue crate
directly; resolved features are unchanged.
* feat(lint): keep L007 out of every exit decision and show it in compile and rules run
compile and rules run kept only selected Rule codes, so an unavailable dialect
looked clean there. L007 now passes through as a warning-severity Rule
diagnostic in compile and is left out of rules run's failing-finding count.
counts_toward_exit owns the exemption.
* fix(lint): keep L007 out of rule exceptions and the plan rules gate
The plan and build rules gate failed on any finding, so an L007-only project
could not plan. Rule exceptions also validate every finding's code as a rule
code and rejected L007 with an invalid-lifecycle error. The gate now counts only
findings that count toward exit, and L007 passes through rule exceptions
unsuppressed. An end-to-end test replays a cached finding as L007 and as a rule
code through compile, rules run, plan and build.
* docs(rules): name plan and build, not format, in the L007 exit note
* test(orchestration): count the store statements a wide catalog listing issues
A same-run time ratio cannot see one store round trip per node: that cost is
linear. Tests now count the statements each task issues, and the wide listing
must read builds 100 nodes per statement: 17 statements for 1,000 nodes and 37
for 3,000 on SQLite and PostgreSQL, 1,008 with one node per statement. The
ratio check stays and now guards super-linear growth only.
* refactor(analysis): share diagnostic location and the catalog's options view
* feat(contracts): prove dynamic pivots from SQLQuack parse trees
The dynamic column contract proof parses pivot SQL with SQLQuack's shared
parser (DuckDB, MotherDuck, Snowflake) instead of Polyglot. DuckDB trees
match Polyglot's exactly; a Snowflake aggregate keeps its argument in a
call's argument list, which the proof now reads. Other dialects keep the
existing unsupported-dialect message.
* fix(contracts): refuse pivot SQL nested deeper than 512 levels before serialising it
* wip: read rule facts with SQLQuack
* wip: locate cast types and Snowflake date parts without a generator
* wip: report built-in rules unavailable for unparsed dialects
* wip: e2e for built-in rules on unparsed dialects
* chore(deps): bump sqlquack to a9dde6a0
* wip: docs and tests for built-in rules on unparsed dialects
* wip: format tests
* fix(rules): refuse rule facts for statements deeper than 512 levels
* fix(rules): anchor nested comparisons and Snowflake LAST_DAY date parts
* feat(scenario): map scenario column types with SQLQuack's type parsers
Local scenario capture no longer asks Polyglot to read warehouse column
types. Postgres types go through sqlquack-syntax-postgres's type parser,
and Snowflake and BigQuery types through their SQLQuack cast-target
parse, behind one native function (parse_warehouse_type). DuckDB and
MotherDuck spellings pass through unchanged. Databricks nested types map
recursively to DuckDB's LIST, MAP and STRUCT, and a nested spelling that
cannot be mapped is refused with a named message instead of falling back
to JSON. Other types keep their integer width or fall back to VARCHAR.
* fix(scenario): map SQL Server date, time, uuid and money types locally
SQL Server has no SQLQuack type parser, so its information_schema names
reached the generic fallback, which held datetime2, smalldatetime,
datetimeoffset and uniqueidentifier as VARCHAR. A SQL Server pre-mapper
now maps them to TIMESTAMP, TIMESTAMPTZ and UUID, bit to BOOLEAN, money
and smallmoney to exact decimals, and SQL Server's 8-byte float to
DOUBLE.
The fallback keeps 4-byte floats (FLOAT, FLOAT4, REAL) as FLOAT instead
of widening them to DOUBLE. A panic in the warehouse type parser now
surfaces as the ValueError capture already falls back on.
* chore(fensu): allow the cast-target walk next to the other JSON tree walks
* refactor(rules): name the date-part and unavailable-rule loops
* docs(analysis): keep the warehouse type binding's doc comment to one line
* feat(types): normalize adapter types without Polyglot
Read each type with SQLQuack's parser for the dialect, or SQLBuild's own
type reader where a dialect has none, and spell it the way the
Polyglot-based normalization did so the same aliases stay equal.
normalize_type now raises only ValueError, for an unknown dialect.
* fix(ui): stop a burst of control API requests on every live refresh
The person trigger listing now carries each trigger's newest tick, so the
jobs and triggers pages no longer read ticks once per trigger. Pages
coalesce change notices into one reload, and the HTTP client shares an
in-flight listing between pages that refresh together.
* fix(types): read only shipped dialects and ClickHouse nested parameters
MotherDuck now reads and spells types as DuckDB. MySQL and the other
SQL analysis dialects no adapter ships raise Unknown dialect instead of
reading as generic SQL. Under ClickHouse the type reader keeps nested
type arguments, enum members with values, and named tuple fields.
* refactor(rules): read the shared-parser dialect from one lookup
* chore(deps): bump sqlquack to 19c51fa2
sqlquack main 19c51fa2 carries the Postgres parser work and the train that
followed a9dde6a0. sqlquack-syntax-postgres now depends on stacker, which
re-resolves a few Windows-only windows-sys edges in the lock.
* build(deps): pin SQLQuack before its Snowflake grammar checks
SQLQuack's next commit refuses a bare call in a Snowflake FROM clause,
which rejects the __ref and __source placeholders that compiled model
SQL keeps, so custom-rule syntax trees fail on Snowflake models. This
rev keeps the BigQuery parser the warehouse type parsers need.
* fix(rules): read relation markers as tables in custom-rule syntax trees
Compiled query_sql keeps relation markers such as __ref("orders"). Snowflake
does not accept a bare function call in FROM, so newer SQLQuack parsers refuse
every Snowflake model that references another.
A shared helper in sqlbuild-analysis (relation_markers::markers_as_names) now
writes each marker call in code as a short indexed name, padded so all later
text keeps its line and column, and returns the calls by index. sql_tree reads
SQL through it for every dialect. The rules crate's dialect lexical syntax moves
to sqlbuild-sqltext so both use one mapping.
* build(deps): keep Windows windows-sys edges at main's resolution
Adding stacker through the SQLQuack crates re-resolved errno, rustix,
tempfile, junction, quinn-udp and winapi-util to older windows-sys
releases. On Windows the extension build then compiled windows-sys 0.52
with features the sqb build lacks. The lockfile keeps main's edges, so
both builds share one windows-sys again.
* docs(types): keep the ClickHouse type parameter doc comment to one line
* feat(ui): wire the lineage and changes pages to the live control API
Add a person read of a target's published snapshots with the subjects
each one changed, behind the same listing authorisation as jobs. The
Changes page reads it, and the Lineage page builds its graph and
inspector from the catalog listing, so neither page needs mock data.
* feat(server): page the security audit newest first with actor names
Person reads of the security audit accept an exclusive upper cursor that
returns the newest entries first, and name each principal actor. Exports
keep their payload unchanged.
* feat(ui): wire the audit log to the security audit read
The audit log reads the newest security facts first, lists a denial
under the action it refused with its decision ID and reason, and names
principal actors. Its actor and action filters come from the entries,
and links to the person page and access checker stay hidden until the
people read exists.
* feat(server): list people and role holdings for administrators
Add GET /api/admin/people, which needs user.manage everywhere, and GET
/api/admin/roles, which needs role.assign everywhere. People carry sign-in
facts only: password presence, SSO groups, live session count and last
sign-in. Role holdings list person assignments and SSO group mappings.
* feat(ui): wire the people page to the people and role reads
The people page lists everyone with their highest role, its source and
last sign-in. A person's sign-in source is shown only when the server
knows it. Links to the person page and access checker, and the risky
actions filter, stay hidden until their reads exist.
* fix(server): count no active sessions for a disabled person
Disabling a person blocks their sessions without revoking them, so the
people read no longer counts those sessions as active.
* fix(contracts): read relation markers as relations in dynamic pivot proofs
Newer SQLQuack Snowflake parsers refuse a bare __ref(...) or __source(...)
in FROM, so the proof parses the model SQL through the shared
markers_as_names helper and renames each dependency marker's table or column
node back to the relation its call names.
* refactor(analysis): share the statement depth guard between pivot proofs and rule facts
Both crates carried the same iterative deeper_than; sql_tree now owns it.
The deep pivot test asserts its expected outcome directly.
* fix(contracts): keep non-dependency markers out of pivot relations
A __dbt_ref passthrough named its internal placeholder in the failure
reason; it now fails as before. The marker scan reads comments and strings
with the dialect the proof parses, so MotherDuck scans as DuckDB.
* fix(types): spell ClickHouse Nullable and BINARY as the engine does
Under ClickHouse, Nullable(T) is read as a wrapper, so an alias inside
it is respelled: Nullable(INT) is Nullable(Int32), as bare INT is.
BINARY(n) spells as FixedString(n). Bare BINARY, and a Nullable that
wraps another Nullable or a nested type, are refused as the engine
refuses them.
* feat(server): let people read a target's location health
Add GET /api/control/locations/{location_id}/targets/{target}/health
behind the same listing gate as jobs. It returns the target's newest
health observations and instance check-ins, shared with the machine
read through one helper.
* feat(ui): show live location health on the Locations page
Health comes from each location's check-ins and observations: no check-in
for 90 seconds is broken, a failed compile at or after the connected
generation is falling back, and an unhealthy connection is degraded.
People without listing view see the health as unknown. Server status,
detail links and the deploy policy column appear only when supported.
* fix(server): limit a target's health read to its own observations
The person health read filtered by target only after the location's
newest 100 observations were taken across all targets, so a busier
target could push out another target's compile or connection reports.
The target filter now applies before each limit.
* feat(server): let people read live platform problems
Add GET /api/control/platform/problems for the UI's alert banner. It
derives problems at read time with the watchdog's thresholds: whether
the scheduler has a leader, location targets whose instances all missed
two check-ins, and running schedules more than 30 seconds late. Broken
locations and late ticks appear only for targets the person lists, and
access is checked per target before that target's ticks are read.
* feat(ui): show live platform problems in the alert banner
The banner reads the new problems endpoint every 30 seconds, because
missed check-ins and late ticks come from time passing, not change
notices. A stopped scheduler and each broken location are critical, and
late schedules are grouped per location. The read now names each
location and dates a stopped scheduler from its last lease. Links go to
the Locations list until location detail pages are supported.
* docs(ui): keep the locations doc comment on listLocations
* feat(server): let role administrators read a target's role definitions
Add GET /api/admin/locations/{location_id}/targets/{target}/roles behind
server-wide role.assign, like the role holdings read. It returns the
built-in roles with their actions, then the target's published custom
roles with their description, grants and the nodes each selector
matched, and how many active people hold each role there.
* feat(ui): show role definitions on the Roles pages
The Roles list and role pages read the new role definitions endpoint.
Built-in roles show their actions on every node, and custom roles show
their published grants, the nodes each selector matched, the published
definition and who holds them on this location. Holder counts include
SSO group members, counted once per person. The SSO mappings tab and the
base-role comparison stay hidden until the server provides them.
* feat(ui): show warehouse sync status in the top bar
The top bar reads the target's warehouse sync reports from the health
read: when a table last synced cleanly, and which tables' newest sync
failed and at what stage. It rereads every 30 seconds with the alert
banner, because sync reports send no change notice.
* fix(ui): stop rereading warehouse sync after a refused read
Every refused health read writes an audit denial, so a person who sees a
location but may not list all of its nodes would add one each poll. The
shell now asks once per target per page load and keeps the indicator at
its unknown state after a refusal.
* fix(rules): wrap Snowflake table functions in TABLE( ) before parsing
The rules engine stubs __table_fn calls before parsing a model. SQLQuack's
Snowflake grammar, like Snowflake, accepts a table function in FROM only
inside TABLE( ), which is how SQLBuild renders the call, so a bare stub made
every built-in Rule report the model unevaluated. Wrap the stub the same way
unless the model already wrote TABLE( ), and assert in the Snowflake
evaluation tests that the model was actually evaluated.
* fix(rules): read Snowflake table function markers inside TABLE( ) in rule trees
Custom Rules parse a model through the rule tree, which renames each
relation marker to a placeholder name first. SQLQuack's Snowflake grammar
refuses the bare table function call that leaves, so a custom Rule on a
Snowflake model with a table function failed to parse it. Wrap those calls
in TABLE( ) over the marker's own padding and a following space, so node
positions keep their line and column, and share the TABLE( ) detection with
the built-in Rules' stubbing.
* feat(ui): show catalog node detail from the control API and finish lineage labels
The catalog node page, the lineage inspector and node links across
Catalog, Checks, Changes and Lineage now load from the catalog listing,
node status, node SQL and check reads. SQL is read only where the
location grants view.sql, so viewers cause no refused, audited reads.
Graph cards show the node name without its kind prefix. Sections the
server does not report (run history, jobs, history, drift without built
SQL, ad-hoc runs) are hidden instead of claiming there are none.
* fix(ui): ask for refused node SQL once until reload
view.sql in a location's bootstrap actions may hold on only some nodes,
so the node SQL read can still be refused. Each refusal is audited and
node pages refetch on change signals, so remember the refused node and
skip its SQL read until the page reloads.
* fix(rules): keep columns after a wrapped table function in rule trees
When no space or tab follows a Snowflake table function call, the rule tree
inserts its closing parenthesis. Write the TABLE( ) wrapper over one more
padding space in that case, so text after the call keeps its column.
* fix(ui): wrap SQL previews and drop the kind prefix from SQL file labels
Preview lines scrolled sideways with no visible scrollbar, so long lines
looked cut off; previews now wrap and the full viewer still scrolls. SQL
file labels show the node name, like the graph cards.
* feat: publish column lineage and show it on catalog node pages
Location publication now adds a lineage snapshot document: the compiler's
FAST column lineage edges for every model, as source and target node keys,
columns and transform kind. A person read returns the edges reaching or
leaving one node, with each node's inferred columns, behind the same
view-on-every-node gate as the catalog listing. It carries no SQL or
expressions, which need view.sql.
The catalog node page's Column lineage tab maps the read onto the existing
column lineage view.
* fix(ui): show full names and transform kinds in column lineage
Traced identifiers and node names wrap instead of truncating, column types
stay on one line, and transformed edges name the compiler's transform
kind, such as Cast or Aggregation.
* refactor: move column lineage to its own change
Column lineage publication would push large projects past the publish
body limit, so it lands after the publish request is compressed. This
change keeps node detail, labels and the SQL preview fixes.
* feat: show per-node run history and selecting jobs on catalog node pages
A person read lists the scheduler runs that built one node in a target,
newest first, behind the same view-on-every-node gate as each run's node
list, and carries the same metadata. The catalog node page fills its Runs
tab, recent build strip and last duration from it, and lists the jobs and
groups whose selection includes the node from the existing jobs and
triggers reads.
The catalog list drops the kind prefix from node names, and the runs list
gives its Started column room for queued times.
* feat(orchestration): gzip location snapshot publishes
A location now sends its snapshot with Content-Encoding: gzip. The server
keeps the 64 MiB wire bound and, after authenticating the location token,
streams the body through a 512 MiB decompressed-size bound into the JSON
parser. Encodings other than gzip get 415, and a body over either bound gets
413. A server that refuses the encoded body with 400 or 415 gets the
snapshot again as plain JSON, so new locations still publish to older
servers.
* feat: show run events, statements, SQL and output to people
Person reads serve a run's Recall rows, scoped to its scheduler and
claimed worker invocations. Event and statement metadata need view on
every node of the target, as the run's node list does, and leave out
event payloads, which can carry SQL and error text. Statement SQL also
needs view.sql, and captured output with invocation and diagnostic error
text also needs view.evidence, on every node the run selected; both are
audited like node SQL and check evidence.
The run page's Statements, Events and Output tabs read them. The UI asks
for SQL and output only where the bootstrap grants them and stops asking
for a run after a refusal until reload, so viewers do not repeat audited
denials. SQL blocks wrap instead of clipping.
* feat: require run.prioritise for runs above priority 0
A run's priority decides which queued run is claimed first, and any person
allowed to run a job or rerun could set any priority. A person's job run
or rerun above priority 0 now also needs run.prioritise on the run's
nodes. Only Admin grants it among built-in roles, project roles may grant
it, and it has no default role. Priority 0 and below need nothing extra,
and trusted local launches are unchanged.
* fix(orchestration): report the server's refusal of a snapshot too large to resend plain
A snapshot whose plain JSON exceeds the wire bound can never be accepted
uncompressed, so a 400 for the gzip body is returned as is instead of
being masked by a second upload that ends in 413.
* fix(orchestration): bound decompressed publish bodies at 320 MiB
A parsed snapshot holds about 7.6 times its JSON size on the server, so
a body just under 512 MiB peaked at 3.8 GiB RSS. 320 MiB keeps four
times the headroom of a 10,000-model project with column lineage.
* fix: keep run cancellation independent of run.prioritise
Only queueing a job run or a rerun above priority 0 needs run.prioritise.
Cancelling an urgent run keeps needing only run.cancel.
* test: wait for every trigger to reach the latest due time after scheduler fault recovery
The scheduler ticks only the latest missed occurrence, so a trigger first
evaluated after the next minute begins ticks that minute and skips the
earlier one. When the final recovery drain crossed a minute boundary on a
slow runner, the fault test counted those triggers as missing their latest
tick, and its duplicate probe at that minute was accepted for the same
reason.
Recovery now cycles until every trigger has ticked at or after the latest
due time at settling, bounded by a five-minute deadline. Each trigger's
newest tick must reach that time, and the duplicate probe re-inserts a time
the trigger actually ticked. The duplicate, off-schedule, run, event and
fencing checks are unchanged.
* test: count ticks scheduled after their own evaluation as off schedule
Requiring each trigger's newest tick to be at or after the latest due time
has no upper bound, so a scheduler that ticked the next occurrence early
would pass. Each tick records the clock it was planned with, and no tick
may be for a later time.
* ci: run the full Verify matrix only on pull requests labelled full-verify
Every pull request push ran the whole matrix: wheels on five platforms,
Windows and macOS jobs, DuckDB end-to-end shards, warehouse, compiler
golden and timing jobs, for about two hours of the organisation's shared
job slots.
Pushes now run a fast Linux core: static checks, unit and integration
tests, native workspace checks and the UI checks. The rest runs when the
pull request is labelled full-verify and is not a draft, and always on
merge groups and manual runs. A run that leaves out suites its change
needs reports its aggregate as a fast-core check, so the required Verify
stays missing and blocks the merge; a full run fails Verify when any
selected suite was skipped. Changes confined to the web UI skip the
Python and native checks they cannot affect.
The aggregate now runs unless the run is cancelled, so a cancelled run
no longer queues it for a runner. A label other than full-verify starts
a run in its own concurrency group that verifies nothing and reports
under another name, so it cannot cancel or satisfy the real run.
* feat: run ad-hoc sqb commands from the web UI
People check and launch `sqb build` from the run panel. The server resolves
the selection against the current publication, authorises run.adhoc plus
run.warehouse, run.prioritise and history-rewriting flags, and refuses any
flag outside the ad-hoc allowlist by name. The dry run reads only and
records nothing. Workers refuse an ad-hoc run whose warehouse the location
does not configure for the target, before any statement runs; published
jobs keep their authored warehouse.
* ci: keep the Verify aggregate on always()
The release gate requires the aggregate to run with always(): a job
skipped when a run is cancelled would report Verify as skipped, which
satisfies a required check. Stale runs are force-cancelled instead.
* refactor(orchestration): page security audit facts beside the audit writes
Reading audit pages authorizes nothing; it reads the facts the credentials
audit module appends and prunes. Together the administrator role reads and
the ad-hoc scope decisions put 21 modules in authorization/main, one over
the container limit.
* test(ci): prove a fast-core or label-only Verify run cannot satisfy the merge gate
The release gate now names the aggregate with the label and fast-core
facts it reads, and requires that a pull request whose fast core passed
without the full matrix, or whose only run followed an unrelated label,
stays blocked. The aggregate tests cover full runs with a selected suite
skipped, fast-core runs and label-only runs.
* fix(ui): find an ad-hoc run launched while a runs listing is in flight
The ad-hoc launch looked up its new run through the shared runs listing
without clearing it, so a listing started before the launch could answer
without the run and report it missing while it was already queued. The
launch now clears shared listings after its write, as a job launch does.1 parent b8149cc commit 7f41309
316 files changed
Lines changed: 17245 additions & 8316 deletions
File tree
- .github/workflows
- benchmarks/duckshop/edge_cases/orchestration
- clients/typescript/src
- crates
- sqlbuild-analysis
- src
- assembly/analysis_session
- _helpers
- tests
- contracts/tests
- planner_strategy/main
- query_analysis/_helpers
- relation_markers
- _helpers
- main
- tests
- semantic_checks/tests
- semantic_validation
- _helpers
- main
- tests
- sql_tree
- _helpers
- main
- tests
- type_system
- _helpers
- main
- tests
- warehouse_types
- _helpers
- main
- sqlbuild-cli
- src
- adhoc
- _helpers
- main
- tests
- native_commands
- _helpers
- main
- sqlbuild-orchestration
- src
- api
- _helpers
- authentication
- resources
- main
- authorization
- _helpers
- main
- credentials
- main
- audit
- identities
- declarations
- _helpers
- main
- platform
- _helpers
- main
- runs
- _helpers/requests
- main
- snapshots/main
- store
- _helpers
- main
- warehouse_history
- _helpers
- main
- webhooks/_helpers
- tests
- api
- node_status
- person_sessions
- credentials
- platform
- runs
- scheduler/ticks
- sqlbuild-python/src/bindings/_helpers
- analysis
- command_runtime
- compile_driver
- compiled_project
- contracts
- debug_command
- location_command
- plan_command
- recall
- rules
- semantic_checks
- type_system
- sqlbuild-rules
- src
- engine
- _helpers
- tests
- lint_text
- _helpers
- main
- tests
- query_facts
- _helpers
- main
- rules/_helpers
- sqlbuild-sqltext/src/sql_scan
- main
- scripts/release_gate
- _helpers
- src/sqlbuild
- .agents/skills/sqlbuild/references/docs
- cli
- concepts
- adapters/sqlserver
- classes
- adapter/type_system
- main
- compiler/sql_analysis/main
- executor/scenario
- _helpers/capture
- tests
- e2e/src/sqlbuild/cli/commands/main/rules
- goldens/python_oracle
- integration/src/sqlbuild
- adapter/type_system
- cli
- commands/main
- recall
- compiler
- compiled_project/publication
- contracts
- semantic_checks
- executor/scenario
- unit
- scripts/release_gate/_helpers
- src/sqlbuild
- adapters/sqlserver
- executor/scenario
- _helpers
- main
- ui
- scripts
- src
- lib
- api
- mock
- types
- components
- code
- shell
- platform
- run
- state
- routes
- admin
- audit
- people
- [name]
- roles
- [name]
- catalog
- locations
- runs
- [id]
- utils
- website/src/content/docs/docs
- cli
- concepts
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| 5 | + | |
| 6 | + | |
5 | 7 | | |
6 | 8 | | |
7 | 9 | | |
8 | 10 | | |
9 | 11 | | |
10 | 12 | | |
11 | 13 | | |
12 | | - | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
13 | 17 | | |
14 | | - | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
15 | 22 | | |
16 | 23 | | |
17 | 24 | | |
18 | 25 | | |
19 | 26 | | |
| 27 | + | |
| 28 | + | |
20 | 29 | | |
21 | 30 | | |
| 31 | + | |
| 32 | + | |
22 | 33 | | |
23 | 34 | | |
24 | 35 | | |
| |||
138 | 149 | | |
139 | 150 | | |
140 | 151 | | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
141 | 155 | | |
142 | 156 | | |
143 | 157 | | |
| |||
147 | 161 | | |
148 | 162 | | |
149 | 163 | | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
150 | 171 | | |
151 | 172 | | |
152 | 173 | | |
| |||
232 | 253 | | |
233 | 254 | | |
234 | 255 | | |
235 | | - | |
| 256 | + | |
236 | 257 | | |
237 | 258 | | |
238 | 259 | | |
| |||
256 | 277 | | |
257 | 278 | | |
258 | 279 | | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
| 289 | + | |
| 290 | + | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
| 304 | + | |
| 305 | + | |
| 306 | + | |
259 | 307 | | |
260 | 308 | | |
| 309 | + | |
261 | 310 | | |
262 | 311 | | |
263 | 312 | | |
| |||
365 | 414 | | |
366 | 415 | | |
367 | 416 | | |
368 | | - | |
| 417 | + | |
369 | 418 | | |
370 | 419 | | |
371 | 420 | | |
| |||
442 | 491 | | |
443 | 492 | | |
444 | 493 | | |
445 | | - | |
| 494 | + | |
446 | 495 | | |
447 | 496 | | |
448 | 497 | | |
| |||
483 | 532 | | |
484 | 533 | | |
485 | 534 | | |
486 | | - | |
| 535 | + | |
487 | 536 | | |
488 | 537 | | |
489 | 538 | | |
| |||
523 | 572 | | |
524 | 573 | | |
525 | 574 | | |
526 | | - | |
| 575 | + | |
527 | 576 | | |
528 | 577 | | |
529 | 578 | | |
| |||
580 | 629 | | |
581 | 630 | | |
582 | 631 | | |
583 | | - | |
| 632 | + | |
584 | 633 | | |
585 | 634 | | |
586 | 635 | | |
| |||
632 | 681 | | |
633 | 682 | | |
634 | 683 | | |
635 | | - | |
| 684 | + | |
636 | 685 | | |
637 | 686 | | |
638 | 687 | | |
| |||
696 | 745 | | |
697 | 746 | | |
698 | 747 | | |
699 | | - | |
| 748 | + | |
700 | 749 | | |
701 | 750 | | |
702 | 751 | | |
| |||
747 | 796 | | |
748 | 797 | | |
749 | 798 | | |
750 | | - | |
| 799 | + | |
751 | 800 | | |
752 | 801 | | |
753 | 802 | | |
| |||
791 | 840 | | |
792 | 841 | | |
793 | 842 | | |
794 | | - | |
| 843 | + | |
795 | 844 | | |
796 | 845 | | |
797 | 846 | | |
| |||
894 | 943 | | |
895 | 944 | | |
896 | 945 | | |
897 | | - | |
| 946 | + | |
898 | 947 | | |
899 | 948 | | |
900 | 949 | | |
| |||
1019 | 1068 | | |
1020 | 1069 | | |
1021 | 1070 | | |
1022 | | - | |
| 1071 | + | |
1023 | 1072 | | |
1024 | 1073 | | |
1025 | 1074 | | |
| |||
1056 | 1105 | | |
1057 | 1106 | | |
1058 | 1107 | | |
1059 | | - | |
| 1108 | + | |
1060 | 1109 | | |
1061 | 1110 | | |
1062 | 1111 | | |
| |||
1093 | 1142 | | |
1094 | 1143 | | |
1095 | 1144 | | |
1096 | | - | |
| 1145 | + | |
1097 | 1146 | | |
1098 | 1147 | | |
1099 | 1148 | | |
| |||
1105 | 1154 | | |
1106 | 1155 | | |
1107 | 1156 | | |
1108 | | - | |
| 1157 | + | |
1109 | 1158 | | |
1110 | 1159 | | |
1111 | 1160 | | |
| |||
1158 | 1207 | | |
1159 | 1208 | | |
1160 | 1209 | | |
| 1210 | + | |
| 1211 | + | |
1161 | 1212 | | |
1162 | 1213 | | |
1163 | 1214 | | |
1164 | 1215 | | |
1165 | | - | |
| 1216 | + | |
| 1217 | + | |
| 1218 | + | |
| 1219 | + | |
1166 | 1220 | | |
1167 | 1221 | | |
1168 | 1222 | | |
| |||
1215 | 1269 | | |
1216 | 1270 | | |
1217 | 1271 | | |
| 1272 | + | |
| 1273 | + | |
| 1274 | + | |
| 1275 | + | |
| 1276 | + | |
| 1277 | + | |
| 1278 | + | |
| 1279 | + | |
| 1280 | + | |
| 1281 | + | |
1218 | 1282 | | |
| 1283 | + | |
| 1284 | + | |
| 1285 | + | |
| 1286 | + | |
1219 | 1287 | | |
1220 | 1288 | | |
1221 | 1289 | | |
| |||
1258 | 1326 | | |
1259 | 1327 | | |
1260 | 1328 | | |
| 1329 | + | |
| 1330 | + | |
| 1331 | + | |
| 1332 | + | |
| 1333 | + | |
| 1334 | + | |
| 1335 | + | |
| 1336 | + | |
| 1337 | + | |
| 1338 | + | |
| 1339 | + | |
| 1340 | + | |
| 1341 | + | |
| 1342 | + | |
| 1343 | + | |
| 1344 | + | |
| 1345 | + | |
| 1346 | + | |
| 1347 | + | |
| 1348 | + | |
| 1349 | + | |
| 1350 | + | |
| 1351 | + | |
| 1352 | + | |
| 1353 | + | |
| 1354 | + | |
1261 | 1355 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
94 | 94 | | |
95 | 95 | | |
96 | 96 | | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
97 | 105 | | |
98 | 106 | | |
99 | 107 | | |
| |||
0 commit comments