021-python-clients 0.1.0__tar.gz

021_python_clients-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+.venv*/
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.env*
+!.env.example
+dist/

021_python_clients-0.1.0/CHANGELOG.md

@@ -0,0 +1,41 @@
+# Changelog
+
+All notable changes are recorded here by release-please from Conventional Commits.
+
+## 0.1.0 (2026-10-21)
+
+
+### Features
+
+* add email (Resend, SES) and KMS clients ([0195195](https://github.com/from021-io/python-clients/commit/019519548c75e6d4bbc50ca564f5eb7dbb2a0ce2))
+* add observed clients for Redis, SQS, S3 and HTTP ([336e53b](https://github.com/from021-io/python-clients/commit/336e53b6a85ec1c84f76100bd5eef1c6cc1f0ba5))
+* **qstash:** add observed JSON publishing and client guide ([9ea3b86](https://github.com/from021-io/python-clients/commit/9ea3b866777d87046a1777ebfc05757d08e3aee9))
+* **qstash:** add observed publishing on top of email and KMS ([cea5d8a](https://github.com/from021-io/python-clients/commit/cea5d8a1a6923be86381a6ef13bd3498956fc909))
+* **queue:** add QStash and group queue providers ([970fbe4](https://github.com/from021-io/python-clients/commit/970fbe474f75866017a5981a66029599bb73964a))
+
+
+### Bug fixes
+
+* **clients:** enforce error and lifecycle contracts ([170d726](https://github.com/from021-io/python-clients/commit/170d72669d229a9802a1f1eebe41aca43425a4c7))
+
+
+### Refactors
+
+* **queue:** group SQS and QStash provider modules ([b71f8ba](https://github.com/from021-io/python-clients/commit/b71f8ba2a8ec4c6aadf217cdad83c1a181509964))
+
+## [Unreleased]
+
+### Added
+
+- **QStash**: observed JSON publishing with deduplication, delivery options, trace
+  propagation, bounded publication timeouts and sanitized provider errors.
+- **Client conventions**: contributor guidance for API design, retries, lifecycle,
+  telemetry, privacy and verification of new clients.
+
+### Changed
+
+- **Queue organization**: group SQS and QStash under `clients_021.queue.sqs` and
+  `clients_021.queue.qstash`, following the capability layout used by email. Provider APIs
+  and optional dependencies are unchanged; update imports from the initial draft paths.
+
+- **HTTP**: accept raw byte content for JSON `null` and reject conflicting body formats.

021_python_clients-0.1.0/CONTRACT.md

@@ -0,0 +1,163 @@
+# Contract
+
+What dashboards, alerts and services may rely on. Changing a name, a label or the error
+semantics below is a breaking change.
+
+## Imports and capability packages
+
+Queue providers live in `clients_021.queue.sqs` (`SqsClient`, `ReceivedMessage`) and
+`clients_021.queue.qstash` (`QStashClient`, `PublishedMessage`, `QStashResponseError`).
+Use these imports in place of the initial draft's root-level `clients_021.sqs` and
+`clients_021.qstash` paths. This organization is part of the first unreleased API.
+Importing `clients_021.queue` or its QStash module does not require the `aws` extra.
+
+The queue package groups providers by purpose. SQS owns polling, receipts and visibility;
+QStash owns HTTP delivery. Their public methods and observability contracts remain distinct.
+Shared email types and the interchangeable `EmailSender` protocol live in `clients_021.email`.
+
+## Metrics
+
+All on the service's `Observability` meter, so they carry its resource (service name,
+version, environment). Durations use 021-python-observability's buckets.
+
+| Instrument | Type / unit | Labels | Clients |
+| --- | --- | --- | --- |
+| `db.client.operation.count` | Counter / `{operation}` | dependency, operation, status, error.type | Redis (shared with SQL from 021-python-observability, which has no `operation`) |
+| `db.client.operation.duration` | Histogram / `s` | same | Redis |
+| `messaging.client.operation.count` | Counter / `{operation}` | dependency, operation, status, error.type | SQS, QStash, email (Resend, SES) |
+| `messaging.client.operation.duration` | Histogram / `s` | same | SQS, QStash, email (Resend, SES) |
+| `storage.client.operation.count` | Counter / `{operation}` | dependency, operation, status, error.type | S3 |
+| `storage.client.operation.duration` | Histogram / `s` | same | S3 |
+| `crypto.client.operation.count` | Counter / `{operation}` | dependency, operation, status, error.type | KMS |
+| `crypto.client.operation.duration` | Histogram / `s` | same | KMS |
+| `http.client.request.count` | Counter / `{request}` | dependency, http.request.method, http.response.status_code, error.type | HTTP, httpx2, QStash transport, Resend (its HTTP request) |
+| `http.client.request.duration` | Histogram / `s` | same | HTTP, httpx2, QStash transport, Resend (its HTTP request) |
+
+- `status`: `ok` or `error`. `error.type` only on errors.
+- `operation`: a fixed set per client. Redis: `get_json`, `set_json`, `take_json`,
+  `delete`, `incr_window`, `ping`. SQS: `send`, `receive`, `delete`, `change_visibility`.
+  S3: `put`, `get`, `head`, `delete`. QStash: `publish`. Email (Resend, SES): `send`. KMS:
+  `encrypt`, `decrypt`, `generate_data_key`; `seal` and `unseal` record the KMS call they make
+  (`generate_data_key`, `decrypt`), not the local AES work.
+- Redis/SQS/S3/QStash/email/KMS `error.type`: `timeout`, `connection_error`, `throttled`,
+  `status_<5xx>`, `cancelled`, or the exception class name for errors that are not outages
+  (`EmailRejected` for every email rejection; botocore's class, such as `ClientError` or
+  `NotFoundException`, for KMS).
+- Resend records two levels: the `send` operation (`messaging.client.operation.*`) and,
+  inside it, its HTTP request (`http.client.request.*`), both under the same `dependency`.
+- HTTP transport metrics inherit 021-python-observability's labels (`timeout`, `cancelled`,
+  `connection_error` or `internal_error`). These describe the transport exception, while
+  `DependencyUnavailable.reason` describes the failure returned to the caller.
+- httpx2 uses `timeout`, `connection_error`, `cancelled`, or the exception class name.
+  HTTP status errors set the span's ERROR status and status-code label, with no `error.type`.
+- A missing S3 object or Redis key is `status=ok`.
+- `dependency` is a static identifier, validated consistently with 021-python-observability.
+  User ids, tenant ids and request-derived values are forbidden even if they match its syntax.
+
+## Spans
+
+CLIENT spans named `<dependency> <operation>` (`HTTP <dependency>` for HTTP), with the
+metric labels plus `db.system.name=redis`, `messaging.system=aws_sqs`,
+`messaging.system=upstash_qstash`, `messaging.system=resend`, `messaging.system=aws_ses`, or
+`rpc.system=aws-api` + `rpc.service=S3` / `rpc.service=KMS`. Resend's `HTTP <dependency>`
+span is a child of its `<dependency> send` span. Status ERROR on failure (and on HTTP
+status ≥ 400).
+Cancellation propagates unchanged and records ERROR with `error.type=cancelled`.
+HTTP transports measure through response headers; they do not measure body consumption.
+
+QStash adds one logical `publish` operation around the HTTP transport request. The
+messaging duration includes reading and validating the acknowledgement; the nested HTTP
+span measures through response headers. Both use the configured static dependency name.
+Local input validation occurs before either operation is recorded.
+
+## Trace propagation
+
+- HTTP (`HttpClient`): `traceparent`, `tracestate` and `x-request-id` are sent (by
+  021-python-observability's transport).
+- httpx2 (`ObservedTransport`): nothing is sent unless `propagate=True`.
+  When enabled, both caller-supplied trace headers are replaced with the current context.
+- Resend: nothing is sent. The `traceparent`, `tracestate` and `x-request-id` headers that
+  021-python-observability's transport adds are removed before the request leaves.
+- SES and KMS: nothing is sent.
+- SQS: `traceparent` and `tracestate` are message attributes; `ReceivedMessage.trace_context()`
+  returns the producer's context. Caller-supplied values for both trace attributes are
+  replaced with the current context.
+- QStash: the `publish` span's context is sent as `Upstash-Forward-traceparent` and
+  `Upstash-Forward-tracestate` for delivery to the consumer. `propagate=False` removes
+  both forwarded trace headers. Caller values never override them. The request to QStash
+  itself still uses the HTTP transport's propagation policy.
+
+## Errors
+
+`DependencyUnavailable(dependency, operation, reason)` with `reason` one of `timeout`,
+`connection_error`, `throttled`, `status_<5xx>`. Raised only when retrying later may work.
+HTTP: only after the last attempt; HTTP statuses are returned, never raised.
+HTTP local protocol/unsupported protocol errors and Redis authentication
+or authorization errors retain their native type and are not treated as outages. httpx2
+transports always preserve the native exception for the owning SDK.
+
+QStash maps HTTP 429 to `throttled`, 5xx to `status_<code>`, and transport outages to
+`timeout` or `connection_error`, with operation `publish`. Other non-2xx responses raise
+`QStashResponseError(status_code, reason="rejected")`. A 2xx response must contain a
+non-empty `messageId` and, if present, a boolean `deduplicated`; otherwise it raises
+`QStashResponseError` with `reason="invalid_response"`. A missing deduplication flag
+is inferred from status 202. Neither error includes the provider response body.
+`PublishedMessage(message_id, deduplicated)` represents acceptance, not completed delivery.
+
+The exception's message and fields contain only the static dependency, operation and reason.
+The chained provider exception is preserved for debugging and is not sanitized.
+
+Email: `EmailRejected(dependency, status, code)` when the provider refused the message or
+the credentials, for both senders. `status` is the HTTP status; `code` is Resend's error
+`name` or the SES error code, reduced to `unknown` unless it is a short identifier. Its
+message is `<dependency> send: rejected (<status> <code>)`; never the provider's message.
+Resend: 429 is `throttled`, 5xx is `status_<5xx>`, transport timeouts and connection
+failures are `timeout` / `connection_error`; every other non-2xx is `EmailRejected` (409
+`concurrent_idempotent_requests` included: the first request is still running). SES: the
+shared AWS classification, and every other `ClientError` becomes `EmailRejected` chained to
+it. Resend's request is sent once; `idempotency_key` becomes its `Idempotency-Key` header
+(1–256 characters, kept by Resend for 24 hours). SES has no idempotency key: the argument is
+validated and ignored.
+
+KMS: throttling, 5xx (`KMSInternalException`, `DependencyTimeoutException`,
+`KeyUnavailableException`), timeouts and connection failures are `DependencyUnavailable`.
+Access denied, disabled or missing keys, invalid key state, a wrong encryption context or a
+tampered ciphertext (`InvalidCiphertextException`) and a ciphertext from another key
+(`IncorrectKeyException`) keep their botocore type. `decrypt` always names the client's key.
+Every call requires a non-empty encryption context. `unseal` raises `ValueError` for a
+malformed envelope and `cryptography.exceptions.InvalidTag` when the payload was altered.
+
+## Sealed envelope format
+
+`KmsClient.seal` output is stored data, so its layout is part of this contract: version
+byte `0x01`, wrapped data key length (2 bytes, big endian), the wrapped key (KMS
+`GenerateDataKey`, `AES_256`, same encryption context), a 12-byte random nonce, then the
+AES-256-GCM ciphertext and 16-byte tag. The GCM additional data is the header (version,
+length and wrapped key) followed by the encryption context as compact JSON with sorted keys.
+A new data key is generated for every envelope.
+
+## Lifecycle and retry limits
+
+HTTP, Redis, SQS, QStash, S3, Resend, SES and KMS expose `aclose()`. Close them after
+in-flight calls complete; the wrapper owns the underlying client, including one supplied
+through the constructor.
+AWS factories configure three total attempts; injected clients retain their own policy.
+Cancellation of an AWS await does not cancel its worker thread or undo a remote write.
+A transient failure does not guarantee that replaying a non-idempotent operation is safe.
+
+QStash publishes once, never automatically replays a POST, and preserves the required
+deduplication key exactly. Keys containing `:` fail locally, matching the provider
+restriction without lossy normalization. Delivery retries, delay and delivery timeout are separate
+provider options. The publication timeout is mandatory and finite. Consumers remain
+responsible for idempotency and signature verification. A closed QStash client cannot
+publish again.
+
+`HttpClient.request` accepts at most one of `json`, `form` or raw byte `content`. Passing
+more than one non-None body format raises `ValueError` before sending a request.
+
+## Never recorded
+
+Keys, URLs, query strings, bodies, message ids, receipts, object names, bucket or queue
+names, provider error messages. Email: sender, recipient and reply-to addresses, subjects,
+text and HTML bodies, tags, idempotency keys, API keys, configuration set names. KMS: key
+ids, ARNs and aliases, encryption contexts, plaintext, ciphertext and data keys.

021_python_clients-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,101 @@
+# Adding a client
+
+Add a client when services repeat provider communication or need a shared operational
+contract. Keep message envelopes, business validation, destination selection, tenant
+routing and deduplication-key generation in service adapters. A provider's full SDK does
+not need to be reimplemented here.
+
+## Layout and public API
+
+Group providers by capability when more than one serves the same purpose, with a module
+per provider inside that package. Keep standalone clients at the root until a second
+provider makes grouping useful. Tests stay in `tests/test_<provider>.py`.
+
+```text
+clients_021/
+  email/          # _message.py (shared protocol/types), resend.py, ses.py
+  queue/          # sqs.py, qstash.py
+  http.py
+  redis.py
+  s3.py
+  kms.py
+```
+
+Public result and exception types live beside their provider unless they are truly shared.
+A common protocol requires interchangeable operations and semantics: `EmailSender.send`
+qualifies. SQS polling/receipts and QStash HTTP delivery do not share a consumer API, so
+`queue/` groups them without inventing one. Provider imports are explicit, and importing
+the capability package must not load optional SDKs.
+
+Use private helpers for actual shared behavior: `_observe.py` owns instrumentation and
+`_aws.py` owns AWS configuration and error classification. Avoid a universal base class:
+a queue, cache and object store have different operations and failure semantics.
+
+Keep `__init__.py` small. Provider SDK imports belong inside their provider module, and
+new dependencies belong in an optional extra. An integration that uses the existing HTTP
+client, such as QStash, requires no extra. Installing the base wheel must not import AWS,
+Redis or an LLM SDK. Include `py.typed` and fully type the public interface.
+
+Accept the service's `Observability`, a static dependency name and explicit configuration.
+Do not read environment variables, initialize global clients, fetch credentials or start
+background work at import time. Factories may construct an SDK; constructors should allow
+an SDK or transport to be injected for tests and provider-specific configuration.
+
+## Operational contract
+
+Each implementation must make these decisions explicit in README.md and CONTRACT.md:
+
+| Concern | Required decision |
+| --- | --- |
+| Timeouts | Finite defaults or required finite configuration; distinguish connection, request and downstream delivery timeouts. |
+| Retries | Identify who retries and the maximum attempts. Do not add a retry loop around an SDK's own loop. A timeout may follow a successful remote write. |
+| Idempotency | Describe how callers safely retry writes. Preserve caller-supplied keys; do not normalize distinct keys into the same value. |
+| Errors | Classify only recoverable dependency failures as `DependencyUnavailable`. Preserve validation/auth/not-found distinctions. Sanitize custom protocol errors. |
+| Cancellation | Propagate cancellation and record it as failure. Document when cancelling an await cannot stop the underlying operation. |
+| Ownership | Reuse pools, expose `aclose()` for owned resources, and specify ownership of injected clients. Close only after in-flight work completes. |
+| Telemetry | Choose a metric family, fixed operations and system attribute. Never record URLs, credentials, bodies, object names or request-derived ids. |
+| Propagation | State the default and opt-out. Replace `traceparent` and `tracestate` together, including removing stale state. |
+
+Use `_observe.observed` for a logical cache, messaging, storage or crypto operation. HTTP-backed
+clients may also emit the transport's HTTP span/metrics: one logical operation and one
+network request are different measurements. Do not sum those counters as distinct
+business operations. Disable exception recording when provider errors can contain data.
+The safe wrapper message does not make a native chained exception safe to log.
+
+Expose small, stable results when the caller needs them. Validate acknowledgements before
+reporting success. Keep documented provider status codes accessible to callers without
+copying the response body into an exception. Invalid local configuration should fail
+before network I/O and should not be classified as an outage.
+
+## Verification and handoff
+
+Cover meaningful behavior, including:
+
+- A request/response round trip with non-default options and a useful result.
+- Transient failure versus invalid request, authentication or missing resources.
+- Actual attempt count, uncertain write outcomes and deduplication behavior.
+- Span/metric names and bounded labels on success, failure and cancellation.
+- Trace propagation, stale context removal and disabled propagation where supported.
+- Sensitive values absent from spans, metric attributes and structured logs.
+- Resource cleanup and installation of the built wheel with and without optional extras.
+
+Use a real local service or a supported emulator when available, and deterministic
+transports/stubs for failures. Keep live credentials and production writes out of tests.
+`tests/qstash_local.py` is an opt-in check against Upstash's development server; regular
+QStash tests use `httpx.MockTransport`.
+
+Run the repository's gates:
+
+```bash
+uv sync --all-extras
+uv lock --check
+make check
+uv build
+uvx twine check --strict dist/*
+# CI also runs tests/wheel_minimal.py and tests/wheel_smoke.py in isolated environments.
+```
+
+Update the README examples, public contract, minimal-wheel check and this guide when a new
+client changes shared conventions. Public contract changes require an appropriate version
+bump; release-please handles version and changelog updates after merge. Use Conventional
+Commits. See [AGENTS.md](AGENTS.md) for the repository's enforcement rules.

021_python_clients-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.