zhao-cli 0.5.6__py3-none-win_amd64.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
Binary file
|
|
@@ -0,0 +1,268 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: zhao-cli
|
|
3
|
+
Version: 0.5.6
|
|
4
|
+
Classifier: Development Status :: 4 - Beta
|
|
5
|
+
Classifier: Environment :: Console
|
|
6
|
+
Classifier: Intended Audience :: Developers
|
|
7
|
+
Classifier: Operating System :: OS Independent
|
|
8
|
+
Classifier: Programming Language :: Rust
|
|
9
|
+
Classifier: Topic :: Database
|
|
10
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
11
|
+
License-File: LICENSE
|
|
12
|
+
Summary: Deterministic, offline change-review and CI gate for data transformation projects.
|
|
13
|
+
Keywords: dbt,ci,data,lineage,sql
|
|
14
|
+
License-Expression: Apache-2.0
|
|
15
|
+
Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
|
|
16
|
+
Project-URL: Changelog, https://github.com/allenhori/zhao-cli/releases
|
|
17
|
+
Project-URL: Homepage, https://github.com/allenhori/zhao-cli
|
|
18
|
+
Project-URL: Repository, https://github.com/allenhori/zhao-cli
|
|
19
|
+
|
|
20
|
+
<p align="center">
|
|
21
|
+
<img src="https://raw.githubusercontent.com/allenhori/zhao-cli/master/docs/assets/logo.png" alt="zhao logo" width="128">
|
|
22
|
+
</p>
|
|
23
|
+
|
|
24
|
+
# zhao (曌)
|
|
25
|
+
|
|
26
|
+
[](https://crates.io/crates/zhao-cli)
|
|
27
|
+
[](LICENSE)
|
|
28
|
+
|
|
29
|
+
Named for the character Empress Wu Zetian invented for herself: 明 (sun and moon) over 空
|
|
30
|
+
(sky) — "illuminating everything below." **A free, deterministic breaking-change gate for
|
|
31
|
+
dbt.** zhao reads your dbt project's compiled SQL and tells a reviewer exactly what a pull
|
|
32
|
+
request changed and which downstream models it actually reaches — before anyone has to trace
|
|
33
|
+
the DAG by hand.
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
Changed:
|
|
37
|
+
model model.jaffle_shop.stg_customers:
|
|
38
|
+
- column removed: last_name
|
|
39
|
+
|
|
40
|
+
Downstream impact:
|
|
41
|
+
model model.jaffle_shop.dim_customers:
|
|
42
|
+
[BREAKING] last_name removed from model model.jaffle_shop.stg_customers breaks reference via last_name (column-removed-with-active-references)
|
|
43
|
+
|
|
44
|
+
Summary: 1 model(s) changed, 1 column(s) changed, 1 breaking, 0 warning
|
|
45
|
+
|
|
46
|
+
Impacted models: dim_customers
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Why
|
|
50
|
+
|
|
51
|
+
dbt's own `state:modified` comparison is syntactic: any compiled-SQL text change counts as
|
|
52
|
+
"modified," and everything downstream is assumed affected. Teams end up either rebuilding
|
|
53
|
+
their whole downstream cone on every PR (slow CI), or leaning on a human reviewer to catch a
|
|
54
|
+
removed column, a narrowed type, or a loosened join by reading SQL — something nobody
|
|
55
|
+
reliably does across a DAG of any real size.
|
|
56
|
+
|
|
57
|
+
zhao parses the SQL itself and computes *real* column-level lineage between two states of
|
|
58
|
+
your project, classifies each change against a fixed Rule catalog (column removed with an
|
|
59
|
+
active reference, a column's logic changed, type narrowed, join loosened, column added), and
|
|
60
|
+
reports the exact models each change actually reaches — never the whole DAG, never a guess.
|
|
61
|
+
Change one column's logic and only the models that read that column, directly or through a
|
|
62
|
+
column derived from it, are reported; a model that merely sits downstream of the same parent
|
|
63
|
+
but reads other columns is not. The analysis itself is
|
|
64
|
+
entirely local: no LLM, no account, and it never reads or sends your actual data — nothing
|
|
65
|
+
installed in your warehouse beyond what `dbt run` already needs. The one place a network call
|
|
66
|
+
happens is resolving a git-native Baseline (`dbt compile`/`dbt deps`, the same as running
|
|
67
|
+
`dbt` yourself) — skip that entirely by passing `--state` with an already-compiled manifest,
|
|
68
|
+
for a genuinely zero-network-call run.
|
|
69
|
+
|
|
70
|
+
## Install
|
|
71
|
+
|
|
72
|
+
**macOS / Linux** — [Homebrew](https://brew.sh):
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
brew install allenhori/zhao/zhao-cli
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
**Windows** — [Scoop](https://scoop.sh):
|
|
79
|
+
|
|
80
|
+
```powershell
|
|
81
|
+
scoop bucket add zhao https://github.com/allenhori/zhao-scoop
|
|
82
|
+
scoop install zhao-cli
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
**Python / dbt projects** — [PyPI](https://pypi.org/project/zhao-cli/), with
|
|
86
|
+
[uv](https://docs.astral.sh/uv/) or pip:
|
|
87
|
+
|
|
88
|
+
```bash
|
|
89
|
+
uv tool install zhao-cli # or: pip install zhao-cli
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
A pre-built binary in a wheel, no Rust toolchain needed. Handy for pinning zhao next to
|
|
93
|
+
`dbt-core` in your project's own dependencies (e.g. `zhao-cli==X.Y.Z`), so local dev and CI get
|
|
94
|
+
the same version.
|
|
95
|
+
|
|
96
|
+
**Any platform** — the install script:
|
|
97
|
+
|
|
98
|
+
```bash
|
|
99
|
+
curl -fsSL https://raw.githubusercontent.com/allenhori/zhao-cli/master/scripts/install.sh | sh
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
Downloads the right pre-built binary for your platform from the
|
|
103
|
+
[releases page](https://github.com/allenhori/zhao-cli/releases) — no Rust toolchain needed.
|
|
104
|
+
Windows without Scoop: grab `zhao-x86_64-pc-windows-msvc.zip` from the same page. Rust users:
|
|
105
|
+
`cargo install zhao-cli` (via [crates.io](https://crates.io/crates/zhao-cli)), or
|
|
106
|
+
`cargo install --git https://github.com/allenhori/zhao-cli` to build directly off `master`
|
|
107
|
+
instead of the last tagged release.
|
|
108
|
+
|
|
109
|
+
**Updating:** use the same tool you installed with — `brew upgrade zhao-cli`, `scoop update zhao-cli`,
|
|
110
|
+
`uv tool upgrade zhao-cli` / `pip install --upgrade zhao-cli`, or `zhao update` for the install
|
|
111
|
+
script / a manual download. `zhao update` detects a Homebrew-, Scoop- or pip/uv-managed install
|
|
112
|
+
and points you at the right command instead of touching the binary. Homebrew, Scoop and PyPI
|
|
113
|
+
only carry stable releases; the nightly build is install-script only.
|
|
114
|
+
|
|
115
|
+
Two release channels: a tagged **stable** release (`v0.1.0`, ...) for anything you depend
|
|
116
|
+
on, and a rolling **nightly** build off `master`, always available at the
|
|
117
|
+
[`nightly` tag](https://github.com/allenhori/zhao-cli/releases/tag/nightly) — set
|
|
118
|
+
`ZHAO_VERSION=nightly` before running the install script above to track it instead. See
|
|
119
|
+
[RELEASING.md](RELEASING.md) for how the two channels work and how releases are cut.
|
|
120
|
+
|
|
121
|
+
## Quickstart
|
|
122
|
+
|
|
123
|
+
```bash
|
|
124
|
+
cd your-dbt-project
|
|
125
|
+
dbt compile
|
|
126
|
+
zhao check --against main
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
`zhao check` finds the merge-base between your branch and `main`, compiles it with `dbt` to
|
|
130
|
+
get a Baseline, diffs it against your current state, and exits non-zero if anything breaking
|
|
131
|
+
fired. Full walkthrough: **[Getting started](docs/getting-started.md)**.
|
|
132
|
+
|
|
133
|
+
Rather have your coding agent wire it into your CI (GitHub Actions, Buildkite, Jenkins, GitLab,
|
|
134
|
+
...) and `zhao.yml`? Tell it: *"Read
|
|
135
|
+
https://raw.githubusercontent.com/allenhori/zhao-cli/master/docs/ai-setup.md and set up zhao for
|
|
136
|
+
this repository."* See **[Set up with an AI agent](docs/ai-setup.md)**.
|
|
137
|
+
|
|
138
|
+
## Commands
|
|
139
|
+
|
|
140
|
+
| Command | What it does |
|
|
141
|
+
|---|---|
|
|
142
|
+
| `zhao check` | The CI gate — diffs against a Baseline, fails on a breaking change. |
|
|
143
|
+
| `zhao diff` | Same engine, always exits `0` — for local inspection during development. |
|
|
144
|
+
| `zhao lineage` | What's upstream/downstream of a model or column, right now (no diff, no git). |
|
|
145
|
+
| `zhao update` | Replaces the current binary with a release from GitHub Releases (for Homebrew, Scoop and pip/uv installs it tells you to use that tool's upgrade command instead). The only command that reaches the network at all — and only to download the binary itself, never to send anything from your project. See [What it doesn't do](#what-it-doesnt-do). |
|
|
146
|
+
|
|
147
|
+
Full flag reference: **[docs/commands.md](docs/commands.md)**.
|
|
148
|
+
|
|
149
|
+
## Addons
|
|
150
|
+
|
|
151
|
+
`zhao <name>` falls through to a `zhao-<name>` binary on `PATH` when `<name>` isn't one of the
|
|
152
|
+
built-ins above — the same convention `git` uses for `git <custom-command>`. `zhao-cli` has no
|
|
153
|
+
compiled-in knowledge of any specific Addon; it only knows the naming convention and forwards
|
|
154
|
+
arguments, exit code, and output verbatim.
|
|
155
|
+
|
|
156
|
+
[`zhao-dbt-plan`](https://github.com/allenhori/zhao-dbt-plan) (a dbt microbatch cascading
|
|
157
|
+
time-window planner, AGPLv3, separate repo) is the first real Addon. See
|
|
158
|
+
[`examples/hello-zhao-addon/`](examples/hello-zhao-addon/) for a minimal reference
|
|
159
|
+
implementation of the Addon contract if you want to build your own — its `README.md` is a
|
|
160
|
+
walkthrough of the whole discovery/input/output contract.
|
|
161
|
+
|
|
162
|
+
## See it, don't just read about it
|
|
163
|
+
|
|
164
|
+
`zhao lineage` exports an interactive, self-contained lineage graph by default — click a model
|
|
165
|
+
or column to trace exactly what it depends on and what depends on it, search, filter, all
|
|
166
|
+
offline in one HTML file.
|
|
167
|
+
|
|
168
|
+
|
|
169
|
+
|
|
170
|
+
**[Open the live demo](https://htmlpreview.github.io/?https://github.com/allenhori/zhao-cli/blob/master/docs/assets/lineage-demo.html)**
|
|
171
|
+
to try it yourself (rendered via [htmlpreview.github.io](https://github.com/htmlpreview/htmlpreview.github.com),
|
|
172
|
+
since GitHub shows raw HTML as source rather than rendering it — the
|
|
173
|
+
[file itself](docs/assets/lineage-demo.html) is also there to download and open locally). More
|
|
174
|
+
in **[docs/lineage-html.md](docs/lineage-html.md)**.
|
|
175
|
+
|
|
176
|
+
## Configuration
|
|
177
|
+
|
|
178
|
+
An optional `zhao.yml` at your project root lets your team set its own severity policy —
|
|
179
|
+
versioned in the repo, not hidden in a CI script:
|
|
180
|
+
|
|
181
|
+
```yaml
|
|
182
|
+
preset: strict
|
|
183
|
+
rules:
|
|
184
|
+
column-added: pass
|
|
185
|
+
defer:
|
|
186
|
+
target: prod
|
|
187
|
+
state: artifacts/prod/manifest.json
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
Full reference, including monorepo cascading: **[docs/configuration.md](docs/configuration.md)**.
|
|
191
|
+
|
|
192
|
+
## CI integration
|
|
193
|
+
|
|
194
|
+
```yaml
|
|
195
|
+
- uses: actions/checkout@v7
|
|
196
|
+
with: { fetch-depth: 0 } # zhao's Baseline resolution needs full history
|
|
197
|
+
- run: dbt compile
|
|
198
|
+
- run: curl -fsSL https://raw.githubusercontent.com/allenhori/zhao-cli/master/scripts/install.sh | sh
|
|
199
|
+
- run: PATH="$HOME/.zhao/bin:$PATH" zhao check --against origin/${{ github.base_ref }}
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
Full example and notes: **[docs/ci-integration.md](docs/ci-integration.md)**.
|
|
203
|
+
|
|
204
|
+
## Documentation
|
|
205
|
+
|
|
206
|
+
- [Getting started](docs/getting-started.md)
|
|
207
|
+
- [Set up with an AI agent](docs/ai-setup.md) — hand your agent one URL to wire zhao into local dev and CI
|
|
208
|
+
- [Command reference](docs/commands.md)
|
|
209
|
+
- [Configuring `zhao.yml`](docs/configuration.md)
|
|
210
|
+
- [CI integration](docs/ci-integration.md)
|
|
211
|
+
- [Understanding lineage](docs/lineage-html.md)
|
|
212
|
+
- [Architecture](ARCHITECTURE.md) — how the code is organized, for contributors
|
|
213
|
+
- [Releasing](RELEASING.md) — how the stable/nightly channels work, for maintainers
|
|
214
|
+
|
|
215
|
+
## What it doesn't do
|
|
216
|
+
|
|
217
|
+
zhao never connects to, stores, or holds credentials for your warehouse or database. `zhao
|
|
218
|
+
check`/`zhao diff`/`zhao lineage` read only the compiled `manifest.json` dbt itself already
|
|
219
|
+
produced, entirely on your own machine or CI runner — no secret or token ever passes through
|
|
220
|
+
zhao to get there. The one place a live connection is genuinely useful (`--check-relations`,
|
|
221
|
+
fully optional) still doesn't change that: zhao never opens the connection itself, it hands
|
|
222
|
+
the check to `dbt run-operation` and borrows whatever connection your own dbt profile already
|
|
223
|
+
has.
|
|
224
|
+
|
|
225
|
+
zhao never reads, collects, or stores your actual data — no row values, nothing about what's
|
|
226
|
+
*in* your tables. It only derives structural metadata (schema, lineage, what changed), and
|
|
227
|
+
that metadata stays on your own filesystem, under `target/zhao/`, unless you decide otherwise.
|
|
228
|
+
Nothing is ever sent anywhere automatically: `zhao-cli` itself makes no network call of its
|
|
229
|
+
own except `zhao update`, which only downloads a release binary — it doesn't send anything
|
|
230
|
+
from your project. The one exception worth naming plainly: resolving a git-native Baseline
|
|
231
|
+
(the default `zhao check --against <ref>`, without `--state`) runs `dbt compile`/`dbt deps` as
|
|
232
|
+
a subprocess — the same commands you'd run yourself, and exactly as network-dependent as they
|
|
233
|
+
already are for you (package downloads, and often a live warehouse connection depending on
|
|
234
|
+
your adapter). Pass `--state` with an already-compiled manifest to skip that path entirely.
|
|
235
|
+
Nothing about your project is ever sent to zhao or any third party as a side effect of
|
|
236
|
+
`check`/`diff`/`lineage` — the metadata they write stays under `target/zhao/`, yours to do
|
|
237
|
+
whatever you want with, including nothing at all.
|
|
238
|
+
|
|
239
|
+
zhao also never generates or applies schema-evolution DDL for you: it detects that a change
|
|
240
|
+
needs manual evolution or a backfill; the decision and the mechanism stay entirely yours.
|
|
241
|
+
|
|
242
|
+
## Status
|
|
243
|
+
|
|
244
|
+
Early, real-world usable. dbt is the first supported project format, not the definition of
|
|
245
|
+
what zhao is — the core engine (`zhao-core`) has no dbt-specific vocabulary baked in, so a
|
|
246
|
+
second Transformation Tool Adapter is a matter of implementing a trait, not rewriting the
|
|
247
|
+
engine.
|
|
248
|
+
|
|
249
|
+
## Building from source
|
|
250
|
+
|
|
251
|
+
```bash
|
|
252
|
+
cargo build --workspace
|
|
253
|
+
cargo test --workspace
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
Requires a recent stable Rust toolchain (edition 2024). Before opening a PR, also run:
|
|
257
|
+
|
|
258
|
+
```bash
|
|
259
|
+
cargo fmt --all -- --check
|
|
260
|
+
cargo clippy --workspace --all-targets --all-features -- -D warnings
|
|
261
|
+
```
|
|
262
|
+
|
|
263
|
+
See [ARCHITECTURE.md](ARCHITECTURE.md) for how the code is organized.
|
|
264
|
+
|
|
265
|
+
## License
|
|
266
|
+
|
|
267
|
+
[Apache 2.0](LICENSE).
|
|
268
|
+
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
zhao_cli-0.5.6.data/scripts/zhao.exe,sha256=dxKksfvo4DFPZDxWGGgyUVYdB6FcjwtRbT56CFjpFOE,13633536
|
|
2
|
+
zhao_cli-0.5.6.dist-info/METADATA,sha256=F0lmzOqTcvLCAihazQu5prSKnFz6y1KyWNUJZCBhq7I,12692
|
|
3
|
+
zhao_cli-0.5.6.dist-info/WHEEL,sha256=8Aej0W0a6Cz6apA3IzJrTnxLRVLAt-w0Oh8SA3Con_c,94
|
|
4
|
+
zhao_cli-0.5.6.dist-info/licenses/LICENSE,sha256=Pd-b5cKP4n2tFDpdx27qJSIq0d1ok0oEcGTlbtL6QMU,11560
|
|
5
|
+
zhao_cli-0.5.6.dist-info/sboms/zhao-cli.cyclonedx.json,sha256=WDh6L9GSDOyZlIg3h0sFqUrQaFmaFW6thfLRpiRN5i4,181429
|
|
6
|
+
zhao_cli-0.5.6.dist-info/RECORD,,
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|