robotruth 0.1.6__tar.gz
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.
- robotruth-0.1.6/.gitignore +18 -0
- robotruth-0.1.6/CHANGELOG.md +58 -0
- robotruth-0.1.6/LICENSE +201 -0
- robotruth-0.1.6/PKG-INFO +531 -0
- robotruth-0.1.6/README.md +492 -0
- robotruth-0.1.6/examples/validation/2026-09-20/README.md +180 -0
- robotruth-0.1.6/policyci/README.md +22 -0
- robotruth-0.1.6/policyci/pyproject.toml +34 -0
- robotruth-0.1.6/policyci/tests/test_policyci.py +441 -0
- robotruth-0.1.6/pyproject.toml +54 -0
- robotruth-0.1.6/src/robotruth/__init__.py +12 -0
- robotruth-0.1.6/src/robotruth/_env.py +35 -0
- robotruth-0.1.6/src/robotruth/audit.py +84 -0
- robotruth-0.1.6/src/robotruth/cli.py +272 -0
- robotruth-0.1.6/src/robotruth/compare.py +105 -0
- robotruth-0.1.6/src/robotruth/contract/__init__.py +39 -0
- robotruth-0.1.6/src/robotruth/contract/check.py +165 -0
- robotruth-0.1.6/src/robotruth/contract/extract.py +462 -0
- robotruth-0.1.6/src/robotruth/contract/spec.py +149 -0
- robotruth-0.1.6/src/robotruth/fingerprint/__init__.py +36 -0
- robotruth-0.1.6/src/robotruth/fingerprint/cell.py +194 -0
- robotruth-0.1.6/src/robotruth/fingerprint/common.py +64 -0
- robotruth-0.1.6/src/robotruth/fingerprint/drift.py +163 -0
- robotruth-0.1.6/src/robotruth/fingerprint/unit.py +183 -0
- robotruth-0.1.6/src/robotruth/guard/__init__.py +93 -0
- robotruth-0.1.6/src/robotruth/guard/adapters.py +179 -0
- robotruth-0.1.6/src/robotruth/guard/cli.py +100 -0
- robotruth-0.1.6/src/robotruth/guard/conformal.py +261 -0
- robotruth-0.1.6/src/robotruth/guard/metrics.py +173 -0
- robotruth-0.1.6/src/robotruth/guard/monitor.py +540 -0
- robotruth-0.1.6/src/robotruth/guard/scores.py +612 -0
- robotruth-0.1.6/src/robotruth/judge/__init__.py +69 -0
- robotruth-0.1.6/src/robotruth/judge/calibrate.py +367 -0
- robotruth-0.1.6/src/robotruth/judge/cli.py +158 -0
- robotruth-0.1.6/src/robotruth/judge/failbench.py +91 -0
- robotruth-0.1.6/src/robotruth/judge/features.py +255 -0
- robotruth-0.1.6/src/robotruth/judge/judge.py +371 -0
- robotruth-0.1.6/src/robotruth/judge/open_vlm.py +107 -0
- robotruth-0.1.6/src/robotruth/judge/vlm.py +329 -0
- robotruth-0.1.6/src/robotruth/report.py +207 -0
- robotruth-0.1.6/src/robotruth/results.py +86 -0
- robotruth-0.1.6/src/robotruth/schema/__init__.py +41 -0
- robotruth-0.1.6/src/robotruth/schema/episode.py +177 -0
- robotruth-0.1.6/src/robotruth/schema/lerobot_ingest.py +240 -0
- robotruth-0.1.6/src/robotruth/schema/log.py +109 -0
- robotruth-0.1.6/src/robotruth/schema/metrics.py +95 -0
- robotruth-0.1.6/src/robotruth/stats/__init__.py +44 -0
- robotruth-0.1.6/src/robotruth/stats/intervals.py +94 -0
- robotruth-0.1.6/src/robotruth/stats/pairwise.py +84 -0
- robotruth-0.1.6/src/robotruth/stats/planning.py +56 -0
- robotruth-0.1.6/src/robotruth/stats/schedule.py +59 -0
- robotruth-0.1.6/src/robotruth/stats/sequential.py +136 -0
- robotruth-0.1.6/src/robotruth/stats/timing.py +108 -0
- robotruth-0.1.6/tests/__init__.py +0 -0
- robotruth-0.1.6/tests/test_audit.py +32 -0
- robotruth-0.1.6/tests/test_compare_cli.py +69 -0
- robotruth-0.1.6/tests/test_contract.py +102 -0
- robotruth-0.1.6/tests/test_fingerprint.py +151 -0
- robotruth-0.1.6/tests/test_guard.py +413 -0
- robotruth-0.1.6/tests/test_judge.py +518 -0
- robotruth-0.1.6/tests/test_lerobot_ingest.py +78 -0
- robotruth-0.1.6/tests/test_schema.py +98 -0
- robotruth-0.1.6/tests/test_stats.py +140 -0
- robotruth-0.1.6/tests/test_validate_real_runner.py +54 -0
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
## 0.1.6 (2026-09-21)
|
|
4
|
+
|
|
5
|
+
- First release published to PyPI, so `pip install robotruth` works. Publishing goes through PyPI trusted publishing from GitHub Actions, which means no API token exists in this repository or its secrets.
|
|
6
|
+
- **Baseline study.** Our monitor being at chance on real task failures turned out to be a fact about the signal rather than about our scorers. Nine other detectors covering the families used in recent work, the chunk consistency of VLA-FAIL, the distance, density and action-variance signals of FAIL-Detect, random network distillation, a GRU sequence model, and isolation forest, one-class SVM and PCA reconstruction, were each fitted on successful episodes only and scored on the same held-out episodes. All ten catch injected execution faults. All ten are at chance on the failures the robots actually had, with AUROC from 0.31 to 0.57 across BotFails and DROID.
|
|
7
|
+
- Nine of the twenty detector and corpus pairs land below 0.5, which is not the same as no signal: the score runs backwards. On DROID a failed episode runs 188 steps against 239 and covers 5.2 units of total motion against 7.6, so a policy that fails does less and any score built on movement reads failure as quiet and quiet as normal. A monitor tuned on that data would spend its alarm budget on the successes.
|
|
8
|
+
- `ops/baseline_comparison.py` runs the comparison and `ops/why_below_chance.py` measures the mechanism; full output is in `examples/validation/2026-09-20-paper`.
|
|
9
|
+
|
|
10
|
+
## 0.1.5 (2026-09-20)
|
|
11
|
+
|
|
12
|
+
- **The guard's scope is corrected, and the correction is measured.** Replayed against real robot logs it caught 5/145 of BotFails' own failures and 0/58 of DROID's. A threshold-free AUROC per scorer head came out at 0.50 to 0.51 and 0.33 to 0.44, so there is no signal to recover: a robot that fails a task keeps moving normally, and the action stream does not show it. The guard detects execution faults, where the robot stops behaving like itself, and the README no longer implies otherwise.
|
|
13
|
+
- **That capability does transfer to real robots.** Stalls and erratic control were detected in 153/153, 72/72 and 136/137 real episodes across three physical-robot corpora within 0.1 to 0.2 s, with false alarms inside the 0.05 bound. Constant offsets need about two standard deviations, and on one corpus were missed at every magnitude tried.
|
|
14
|
+
- **False alarms measured on a pool that can carry the claim**: 0/338 held-out successes, interval [0.000, 0.011]. The 0.1.4 bound rested on 18 episodes and its interval reached 0.176, wide enough to hide a 17 percent true rate.
|
|
15
|
+
- **Gradual faults are detected too.** Every previous number used a step change. Faults ramping to full strength over 0.5 to 4 s are still detected 100% of the time, and the delay tracks how long the fault takes to leave the nominal envelope rather than being a fixed lag.
|
|
16
|
+
- **`robotruth.fingerprint.DriftDetector`**: a calibrated drift alarm for when you have a population of fingerprints instead of a known tolerance. Median and scaled MAD for the centre and spread, so one already-drifted unit cannot mask the drift it represents, and a split-conformal threshold on the worst standardised per-joint deviation. On eight real datasets and 270 held-out clean episodes it gives 3/270 false alarms against 23/270 for a three-sigma rule, with detection of a 0.25 sd offset unchanged at 268/270. It reports itself saturated rather than claiming a rate too few fingerprints can certify.
|
|
17
|
+
- The policy loader reads min/max scaling and the newer lerobot layout that keeps statistics in separate preprocessor files, taking the scheme from the policy's own config instead of guessing.
|
|
18
|
+
- Known limit, unchanged and now stated plainly: every live guard number comes from one policy on one task. Three attempts at a second combination failed, one of them because `lerobot/diffusion_pusht` raises an uncorrectable ECC error on an A10 and poisons the GPU for other processes.
|
|
19
|
+
|
|
20
|
+
## 0.1.4 (2026-09-19)
|
|
21
|
+
|
|
22
|
+
- **The stall blind spot is closed.** A `StagnationScorer` watches windowed motion of the action stream, and `calibrate_guard` now gives it its own conformal threshold in a `MultiHeadScorer` instead of averaging it into the composite, alarming on the union of the two heads with alpha split between them. Measured on the same live policy and fault protocol as 0.1.3, on a 150-episode calibration pool: stall, offset and noise faults all detected 10/10, pooled 30/30 = 1.000 [0.886, 1.000], median latency 0.04 s, 0/18 false alarms on held-out successes.
|
|
23
|
+
- The dedicated head is the reason it works. With the stagnation score averaged into the composite, freeze detection was only 1/10: a frozen action stream is self-consistent and in-distribution, so three of the four component scores report nominal and dilute the one that sees the stall. Both runs are published side by side in `examples/validation/2026-09-19/guard_detection_v2/`.
|
|
24
|
+
- The stall head reports itself as saturated below roughly 40 calibration episodes rather than claiming an uncertifiable guarantee.
|
|
25
|
+
- **Cross-dataset benchmark**: `ops/benchmark_fetch.py`, `ops/benchmark_report.py` and `ops/botfails_bench.py` fetch public LeRobot datasets (metadata and parquet only), run every module over them and render one HTML report. First run covers 54 datasets from RoboMIND and AgiBotWorld task ports, OpenX conversions, DROID, BotFails and DAgger logs, with zero ingest failures.
|
|
26
|
+
- **HTML reports redesigned**: markdown in report sections now renders as HTML instead of being dumped as raw text, with a document header, table of contents, numbered sections, sentence-cased headings and column headers, and print styles.
|
|
27
|
+
- `ops/guard_detection.py` saves every rollout as npz, so threshold changes can be replayed offline instead of costing GPU hours.
|
|
28
|
+
|
|
29
|
+
## 0.1.3 (2026-09-19)
|
|
30
|
+
|
|
31
|
+
- Guard detection measured with policy-breaking faults injected into executed actions on a live policy (all 30 fault episodes failed the task). On a 164-episode calibration pool: offset (miscalibration) faults 10/10 detected, noise (erratic policy) faults 10/10 with max thresholds, median detection latency 0.04 s, 0/17 false alarms on held-out successes. Stall (freeze) faults 0/10: a frozen action stream is self-consistent and in-distribution, so the current scorers cannot see it; a stagnation scorer is the planned fix and the blind spot is documented in Known limits.
|
|
32
|
+
- Calibration-size guidance is now measured: 45-episode pools leaked up to 3/17 false alarms in the same experiment while the 164-episode pool leaked none. Calibrate on 150 or more nominal episodes.
|
|
33
|
+
|
|
34
|
+
## 0.1.2 (2026-09-19)
|
|
35
|
+
|
|
36
|
+
- Fused judge validated on real labeled data: on 323 BotFails episodes the fused and calibrated judge reaches 0.921 [0.617, 0.972] balanced accuracy at 25.8 percent coverage with 2.73 false alarms per hour, against 0.614 and 11.13 for the uncalibrated vision channel alone. The action channel alone abstains on everything, which is why fusion is the shipped default.
|
|
37
|
+
- Guard conformal methods measured across three independent calibration draws on a live policy. The bonferroni method alarmed on about 20 percent of held-out successes at 44 to 49 calibration episodes because every time bin was saturated, so its alpha did not hold; `max` remains the default and the caveat is documented in `guard/conformal.py`. Detection remains unmeasured because the perturbation broke the policy in only 1 of 12 episodes.
|
|
38
|
+
- Memory-safe frame sampling in the evaluation scripts: sampling frames from a decoded video kept the whole video alive through numpy views, which grew to 140 GB across a dataset. Frames are now streamed and copied.
|
|
39
|
+
- Em dashes removed from all documentation.
|
|
40
|
+
|
|
41
|
+
## 0.1.1 (2026-09-18)
|
|
42
|
+
|
|
43
|
+
- Open-weight VLM backend for the judge (`robotruth.judge.open_vlm.OpenVLMBackend`, Qwen-VL class via transformers): the vision channel runs on your own GPU with no API key. Benchmarked zero-shot on 140 labeled real UR5 episodes: balanced accuracy 0.555 [0.442, 0.663] at 3.5 s per episode on one A10 (frontier ceiling on FailBench: 0.77). The Claude backend remains available behind the `vlm` extra.
|
|
44
|
+
- Live policy-loop validation: a real ACT policy in gym-aloha with the guard attached to every step and the judge scored against simulator truth. Judge balanced accuracy 0.929 [0.651, 0.987] over 24 live episodes with zero false alarms; guard false-alarm bound held in both runs; run-to-run threshold variance at small calibration sizes documented.
|
|
45
|
+
- openpi extractor validated against the real pi0_base orbax checkpoint (12 GB hashed; norm_stats for nine robot assets detected and flagged as part of the executable policy).
|
|
46
|
+
- The live test reproduced the contract failure class in the wild: lerobot 0.6.1 silently drops this checkpoint's normalization buffers, taking an 83 percent policy to 0 percent with only a log warning.
|
|
47
|
+
|
|
48
|
+
## 0.1.0 (2026-09-18)
|
|
49
|
+
|
|
50
|
+
First public release.
|
|
51
|
+
|
|
52
|
+
- Contract checker: ExecSpec manifests for LeRobot (old and new preprocessor formats), GR00T, openpi and custom checkpoints; probe-directory source so weights never move; fail-closed comparison. Validated against five public checkpoints (ACT, SmolVLA, pi0, pi05, GR00T N1.5).
|
|
53
|
+
- Statistics: Wilson and Clopper-Pearson intervals, paired and bootstrap differences, anytime-valid empirical Bernstein confidence sequences, sequential paired test, sample-size planner, Kaplan-Meier and log-rank on censored time to success, Bradley-Terry with bootstrap errors, blinded interleaved schedules, claims audit (Newcombe intervals and Fisher tests over reported counts).
|
|
54
|
+
- Episode records: schema with 12 failure classes and 60 subclasses, interventions with source, provenance hashes; JSONL log; MCAP bridge; fleet metrics with intervals (success, autonomous fraction, interventions per hour, MTBI, failure Pareto); LeRobot dataset ingest (v2 and v3, success and intervention columns, DROID column aliases).
|
|
55
|
+
- Fingerprints: robot unit fingerprint from an excitation log (joint lag and backlash by regression, RMSE, offset, gain) and workspace cell fingerprint from a camera frame (ArUco markers, exposure, sharpness, colour balance) with drift tolerances.
|
|
56
|
+
- Judge: action-stream features, VLM backend protocol with a Claude backend, logistic fusion, split-conformal calibration with abstain, evaluation with balanced accuracy and false alarms per hour, FailBench-style loader.
|
|
57
|
+
- Guard: Mahalanobis (Ledoit-Wolf, optional CUDA), chunk-consistency and action-stat scorers, time-uniform conformal thresholds (max and Bonferroni), contrast-set calibration, hysteresis and hard limits, offline replay, metrics.
|
|
58
|
+
- Ops: GPU-box scripts for checkpoint probing, dataset fetching, sync-and-test, and end-to-end validation on public LeRobot datasets.
|
robotruth-0.1.6/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|