tapio-py 0.1.0__tar.gz

tapio_py-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,40 @@
+<!--
+Keep this short. The diff says what changed; this says why, and what a
+reviewer should look at hardest. Delete any section that does not apply.
+-->
+
+## What and why
+
+<!-- One or two sentences. If it closes an issue: Closes #NNN. -->
+
+## Design notes
+
+<!--
+Anything a reviewer would otherwise have to reverse-engineer: a tradeoff you
+made, an alternative you rejected and the reason, a semantic that is
+observable and therefore load-bearing. If a decision here contradicts the
+design doc, say so explicitly. That is a decision, not an oversight.
+-->
+
+## Verification
+
+<!--
+How you know it works, beyond "CI is green". Name the tests that would fail
+if this regressed.
+-->
+
+- [ ] `make check` passes locally (lint, mypy strict, tests)
+- [ ] New behaviour has a test that fails without the change
+- [ ] Public API changes are reflected in the docs
+
+## Risk
+
+<!--
+Breaking changes, new failure modes, anything that only shows up under
+concurrency or shutdown. "None" is a fine answer, so say it rather than
+leaving this blank.
+-->
+
+## Not in this PR
+
+<!-- Deliberate follow-ups, so they read as scoping rather than omissions. -->

tapio_py-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,179 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  # The pipeline never re-spells the commands: it calls `make ci`, which is the
+  # same gate developers run locally.
+  ci:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Pin Python ${{ matrix.python-version }}
+        run: uv python pin ${{ matrix.python-version }}
+
+      - name: make ci
+        run: make ci
+
+      # The badge is written from one leg of the matrix only: three legs racing
+      # a PATCH against the same gist would publish whichever finished last.
+      #
+      # Dormant until the repository variable COVERAGE_GIST_ID is set, in the
+      # same spirit as PUBLISH_DOCS below. It also needs a GIST_TOKEN secret: a
+      # personal access token with the `gist` scope, because the built-in
+      # GITHUB_TOKEN is scoped to the repository and cannot write gists.
+      - name: Publish the coverage badge
+        if: >-
+          matrix.python-version == '3.12'
+          && github.ref == 'refs/heads/main'
+          && github.event_name == 'push'
+          && vars.COVERAGE_GIST_ID != ''
+        env:
+          GH_TOKEN: ${{ secrets.GIST_TOKEN }}
+          GIST_ID: ${{ vars.COVERAGE_GIST_ID }}
+        run: |
+          # The secrets context is not readable from a step `if`, so the token
+          # is checked here: a repository without GIST_TOKEN yet should skip
+          # the badge, not fail the gate.
+          if [ -z "${GH_TOKEN:-}" ]; then
+            echo "GIST_TOKEN is not set, skipping the coverage badge."
+            exit 0
+          fi
+          total=$(uv run coverage report --format=total)
+          if   [ "$total" -ge 90 ]; then color=brightgreen
+          elif [ "$total" -ge 80 ]; then color=green
+          elif [ "$total" -ge 70 ]; then color=yellowgreen
+          elif [ "$total" -ge 60 ]; then color=yellow
+          else                           color=red
+          fi
+          jq -n --arg message "$total%" --arg color "$color" \
+            '{files: {"tapio-coverage.json": {content: (
+                {schemaVersion: 1, label: "coverage", message: $message, color: $color}
+                | tojson)}}}' \
+            | gh api -X PATCH "/gists/$GIST_ID" --input -
+
+  # Publishing is a step of the same pipeline, not a workflow of its own: the
+  # site only goes out if the gate above passed, on main, and it is built by
+  # the same `make docs-build` that runs locally.
+  #
+  # Dormant until the repository variable PUBLISH_DOCS is set to "true", which
+  # is the switch to flip once Pages is enabled for this repository. Pages on a
+  # private repository needs a paid plan, so a job that always ran would fail
+  # every push to main until then.
+  docs:
+    needs: ci
+    if: >-
+      github.ref == 'refs/heads/main'
+      && github.event_name == 'push'
+      && vars.PUBLISH_DOCS == 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deploy.outputs.page_url }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: make docs-build
+        run: make docs-build
+
+      - uses: actions/configure-pages@v5
+
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+      - id: deploy
+        uses: actions/deploy-pages@v4
+
+  # Versions come from the commits. `feat:` moves the minor, `fix:` the patch,
+  # and the job tags what it bumped, so nobody edits two files by hand and
+  # nobody has to remember which release a change went out in.
+  #
+  # This is only safe because a link is pinned to PROTOCOL_VERSION rather than
+  # to the release: bumping the version no longer refuses a peer, so a rolling
+  # deploy survives a patch release and a bot may do the bumping.
+  #
+  # Dormant until the repository variable AUTORELEASE is set to "true", in the
+  # same spirit as PUBLISH_DOCS above. Publishing to PyPI is deliberately not
+  # here: this job tags, builds and attaches the artifacts to a GitHub release,
+  # and `uv publish` stays a decision somebody makes.
+  release:
+    needs: ci
+    if: >-
+      github.ref == 'refs/heads/main'
+      && github.event_name == 'push'
+      && vars.AUTORELEASE == 'true'
+    runs-on: ubuntu-latest
+    # Its own group, and never cancelled: the workflow-level concurrency
+    # cancels in progress, and a release interrupted between tagging and
+    # publishing leaves a tag nobody built.
+    concurrency:
+      group: release
+      cancel-in-progress: false
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # The whole history, because the next version is a function of every
+          # commit since the last tag.
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      # The bump commit and the tag are pushed with the built-in token, and a
+      # push made with that token does not trigger workflows. That is what
+      # stops the release from starting this pipeline again.
+      - name: make release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: make release
+
+      # Separate from the tag on purpose. Tagging is reversible and an upload
+      # is not: PyPI never lets a version be re-used, even after a deletion,
+      # so this waits on its own variable rather than riding on AUTORELEASE.
+      #
+      # The alternative to a token is trusted publishing, where PyPI accepts an
+      # OIDC identity from this workflow and no secret exists to leak. Worth
+      # moving to once the project exists on PyPI.
+      - name: make publish
+        if: vars.PUBLISH_PYPI == 'true'
+        env:
+          UV_PUBLISH_TOKEN: ${{ secrets.UV_PUBLISH_TOKEN }}
+        run: |
+          # Checked here rather than in the step `if`, because the secrets
+          # context is not readable from one. A repository with the variable
+          # set and no token should say so, not upload nothing quietly.
+          if [ -z "${UV_PUBLISH_TOKEN:-}" ]; then
+            echo "PUBLISH_PYPI is true but UV_PUBLISH_TOKEN is not set."
+            exit 1
+          fi
+          make publish

tapio_py-0.1.0/.gitignore

@@ -0,0 +1,36 @@
+# Python
+__pycache__/
+*.py[cod]
+*.so
+
+# Packaging / build
+dist/
+build/
+*.egg-info/
+
+# Environments — uv.lock IS committed; .venv is not
+.venv/
+.python-version
+
+# Tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.benchmarks/
+
+# Coverage
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Docs build output
+site/
+
+# Local working docs (not versioned by choice)
+PLAN.md
+
+# Editors / OS
+.idea/
+.vscode/
+.DS_Store

tapio_py-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,28 @@
+default_install_hook_types: [pre-commit]
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: check-toml
+      - id: check-yaml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.5.7
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy --strict
+        entry: uv run mypy --strict src/tapio examples/tapio_examples
+        language: system
+        pass_filenames: false
+        types: [python]

tapio_py-0.1.0/AGENTS.md

@@ -0,0 +1,175 @@
+# Working in this repository
+
+tapio is a Pekko-inspired actor toolkit for Python: local, typed,
+asyncio-native actors with supervision, and Pydantic models throughout.
+
+## Commands
+
+`make` with no target lists everything. The Makefile is the single source of
+truth for what CI runs, so use it rather than re-spelling commands.
+
+```bash
+make install    # create the venv, install deps
+make check      # pre-push gate: lint + types + tests
+make test       # pytest
+make examples   # run and assert every example
+make ci         # exactly what GitHub Actions runs
+```
+
+Never invoke `python` or `pytest` directly: everything goes through `uv run`,
+so there is no ambiguity about which interpreter ran.
+
+CI calls `make ci` and nothing else, then publishes the built site to GitHub
+Pages from `main`. That publish step waits on the repository variable
+`PUBLISH_DOCS` being `"true"`, since Pages has to be enabled on the repository
+first.
+
+## Layout
+
+| Path | What lives there |
+|---|---|
+| `src/tapio/` | the library, shipped in the wheel |
+| `src/tapio/actor/` | paths, refs, behaviors, cell, mailbox, system |
+| `src/tapio/remote/` | addressing, the wire format, the link and the associations over it |
+| `src/tapio/dispatch/` | the event loop a system's tasks run on |
+| `src/tapio/testkit/` | helpers for testing actor code, shipped |
+| `tests/` | unit tests, mirroring the source packages, plus `tests/examples/` and `tests/benchmarks/` |
+| `examples/tapio_examples/` | runnable examples, dev-only, never shipped |
+| `docs/` | mkdocs-material, code included from `examples/` |
+
+## Style
+
+These are settled preferences. Follow them in new code and fix them in code
+you are already editing.
+
+- **No em dashes.** Not in prose, docstrings, comments, commit messages, or PR
+  bodies. Use a comma, a colon, parentheses, or a full stop.
+- **No references to internal planning documents.** No section numbers, no
+  milestone labels, no "see the plan". Write the reasoning out in place. A
+  reader of this repository cannot follow those pointers.
+- **Absolute imports only**, enforced by ruff. `from tapio.actor.path import
+  ActorPath`, never a relative import, including in tests.
+- **Single backticks in docstrings.** Markdown, not RST: no double backticks
+  and no roles. Cross-reference with mkdocstrings syntax,
+  `[Name][tapio.module.Name]`.
+- **No blanket `from __future__ import annotations`.** The floor is Python
+  3.11. Quote the few genuinely forward references instead.
+- **Plain English, everywhere.** Docstrings, comments, `docs/`, the README,
+  commit messages and pull request bodies. Subject, verb, object. One idea per
+  sentence. No inverted clauses, no aphorisms, no sentence written for its
+  cadence, nothing a reader has to decode before they can use it. Say the fact
+  and stop. Keep the reasons: *why* a decision was made is worth a sentence,
+  it just has to be a plain one. In tests this is strictest, since a test is
+  usually read while it is failing: a one-line module docstring, and a comment
+  only where the code is genuinely surprising.
+- Google-style docstrings on every public module, class, and function. Ruff
+  enforces the convention; mypy runs `--strict` over `src` and `examples`.
+- Explain *why* in comments, not *what*. The code says what it does.
+
+## Commit messages and pull requests
+
+- **The commit type decides the version.** python-semantic-release reads the
+  history on `main`, so `feat:` moves the minor, `fix:` moves the patch, and
+  anything else moves nothing. Write the type you mean: a `fix:` that is
+  really a feature ships under a version number that lies about it. A
+  `BREAKING CHANGE:` footer moves the minor too while this is 0.x, since
+  going to 1.0.0 is a decision rather than a side effect. Nobody edits a
+  version by hand, and `make next-version` says what the current history
+  would produce.
+- **Nothing in the repository holds a version number.** It is derived from the
+  git tag at build time, so a release is a tag and nothing else. Do not add a
+  literal version to `pyproject.toml` or `version.py`: the second copy is the
+  one that goes stale, and writing one would put the release job back to
+  pushing commits at a protected branch.
+- **Wrap commit messages at 72 columns.** `git log` does not reflow, so an
+  unwrapped paragraph becomes one very long line in a terminal.
+- **Do not wrap pull request bodies.** One line per paragraph and one per list
+  item, however long. GitHub renders Markdown, so a hard-wrapped body and an
+  unwrapped one look identical in the browser, and the wrapping only shows in
+  the raw editor. What it costs is in the permanent history: GitHub generates a
+  squash merge's message from the pull request body and wraps it at 72, so a
+  body already wrapped at 79 gets wrapped a second time and lands ragged, with
+  stray two-word lines. Wrapping once, at merge time, is the point. PR #3's
+  merge commit has the artifact, with "and a / shutdown / that drains the tree"
+  split across three lines.
+- **Let the merge generate its own message.** `gh pr merge --squash` with no
+  `--body-file` uses the pull request body and applies the wrapping above.
+  Passing a body explicitly sends it verbatim and skips the wrapping entirely,
+  so an unwrapped body becomes an unwrapped commit: one paragraph, one
+  several-hundred-character line, unreadable in `git log`. PR #4's merge commit
+  has *that* artifact, which is how this rule got its second half. If a merge
+  message really has to be supplied by hand, wrap it at 72 first.
+- **End the pull request body with the `Co-Authored-By` trailer**, not just the
+  branch commits. The squash message is built from the body and the branch
+  commits' trailers are discarded with their messages, so a trailer on every
+  commit of the branch still does not reach `main`. PR #4's merge commit has
+  none, while all four of its branch commits did.
+- Say what changed and why, and where a decision contradicts the design notes,
+  say so explicitly. That is a decision, not an oversight.
+- Name the tests that would fail if the change regressed. "CI is green" is not
+  verification, it is a precondition.
+
+## Testing
+
+- **The test tree mirrors the source tree.** A test for `tapio.remote.codec`
+  lives in `tests/remote/test_codec.py`. Shared fixtures and fakes stay at
+  `tests/`, since they are shared by every package.
+- `pytest-asyncio` runs in auto mode, so an `async def test_...` needs no
+  marker. Warnings are errors.
+- **Stop an actor through its behavior, not with `cell.abort()`.** Abort
+  cancels the cell's task, and the `CancelledError` that follows lands in the
+  test rather than in the runtime. Send a message the behavior answers with
+  `Behaviors.stopped()` and wait for the effect with `eventually`.
+- Anything that starts a system wraps itself in
+  `tapio.testkit.assert_no_leaked_tasks()`. The runtime deliberately does not
+  use `TaskGroup`, so "no orphaned tasks" is an invariant this suite has to
+  keep honest.
+- Tests use the `system` fixture from `tests/conftest.py` when they need a live
+  tree; it terminates whatever the test leaves behind. A fixture only one
+  package needs lives in that package's own `conftest.py`, with its helpers
+  beside it: `tests/remote/conftest.py` holds the two systems every remoting
+  test starts, and `tests/remote/peers.py` the messages, behaviors and
+  misbehaving peer they share.
+- **A test that listens binds port 0.** The OS picks, the canonical address
+  follows what it picked, and no two tests argue over a number somebody chose.
+- Examples are tests. Every module in `examples/tapio_examples/` has an
+  assertion in `tests/examples/test_suite.py`, and a new example with no
+  assertion fails the suite on purpose.
+
+## Design invariants worth knowing before changing the runtime
+
+- **A message's identity never depends on a setting.** Delivery-time validation
+  discards its result; the recipient always gets the object the sender passed.
+  The guarantee is local: a message that crossed a link was rebuilt from JSON,
+  so it is `==` to what was sent and never `is` it. Say which side of that line
+  a test is on.
+- **`tell` never blocks and never raises about the recipient.** Errors about
+  the message belong to the sender. Errors about the recipient become dead
+  letters.
+- **The mailbox has one consumer and one waiter.** Signals drain before user
+  messages, and the system lane is always unbounded so a stop cannot be
+  refused.
+- **Shutdown races one deadline for the whole tree**, not one per actor, so
+  worst-case shutdown does not multiply by depth.
+- **Every task belongs to a cell and is cancelled in its termination
+  sequence.** If you add a task, say which cell owns it. Remoting adds no
+  exception: an association is an actor whose reader is its own task, and the
+  endpoint actor owns the listener and any connection still mid-handshake.
+- **The handshake pins the protocol version, not the package version.**
+  `PROTOCOL_VERSION` in `remote/protocol.py` describes the wire contract and
+  is what both ends must agree on. `__version__` travels in the hello as a
+  diagnostic and is never compared, so two nodes on different releases
+  interoperate and a rolling deploy is possible. Raising the protocol version
+  is a deployment event and belongs in the pull request body.
+- **A type key on a frame is a registry key, never an import path.** Resolving
+  a dotted name that arrived on a socket into an importable object is remote
+  code execution. An unregistered key is a dead letter naming the key, and
+  nothing is imported to find out what it might have meant.
+- **Remoting is off unless it is configured**, and when it is, the port is
+  bound while the system is being constructed. That is what settles the
+  canonical address before any ref can write itself down, and what makes a
+  configuration that would listen to the world fail to start rather than fail
+  to be secure.
+- **Delivery across a link is at-most-once, FIFO per association**, the same
+  guarantee as a local send. No acks and no retries: upgrading that belongs to
+  the user's protocol, where they know what is safe to repeat.

tapio_py-0.1.0/CLAUDE.md

@@ -0,0 +1,5 @@
+# CLAUDE.md
+
+The conventions for this repository live in one file, shared by every agent:
+
+@AGENTS.md

tapio_py-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.