veny 0.2.2__tar.gz

veny-0.2.2/.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+
+updates:
+  # Keeps the SHA-pinned third-party action in release.yml current without
+  # anybody having to remember it exists. Dependabot rewrites the pin and
+  # updates the trailing version comment in the same PR.
+  - package-ecosystem: github-actions
+    directory: "/"
+    schedule:
+      interval: weekly

veny-0.2.2/.github/workflows/release.yml

@@ -0,0 +1,79 @@
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.13"
+
+      - name: Install build tooling
+        run: |
+          python -m pip install --disable-pip-version-check --upgrade pip
+          python -m pip install --disable-pip-version-check build twine
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      # veny's version is a static string in src/veny/__init__.py, not derived
+      # from the tag, so the two can disagree: tag v0.2.3 while __init__.py
+      # still reads 0.2.2 and the build cheerfully produces veny-0.2.2. PyPI
+      # filenames are immutable, so publishing the wrong one burns that
+      # version number permanently. Fail here instead, before the publish job
+      # can run.
+      - name: Assert the tag matches __version__
+        run: |
+          set -euo pipefail
+          tag="${GITHUB_REF_NAME}"
+          version="$(python -c 'import sys; sys.path.insert(0, "src"); import veny; print(veny.__version__)')"
+          echo "tag=${tag}  __version__=${version}"
+          if [ "${tag}" != "v${version}" ]; then
+            echo "::error::tag ${tag} does not match veny.__version__ ${version} (expected v${version})"
+            exit 1
+          fi
+          test -f "dist/veny-${version}.tar.gz"
+          test -f "dist/veny-${version}-py3-none-any.whl"
+
+      # veny is pure Python. A platform-tagged wheel here would mean something
+      # went wrong in the build, and would publish an artifact most users
+      # could not install.
+      - name: Assert the wheel is pure Python
+        run: |
+          set -euo pipefail
+          ls dist/
+          test -n "$(ls dist/*-py3-none-any.whl)"
+
+      - name: twine check
+        run: python -m twine check --strict dist/*
+
+      - uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      # Required for PyPI Trusted Publishing (OIDC). No API token exists.
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

veny-0.2.2/.github/workflows/test.yml

@@ -0,0 +1,79 @@
+name: test
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: test-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.13"
+
+      # Pinned rather than floating. A new ruff minor can add rules that were
+      # not in the ruleset when main last went green, which would turn the
+      # default branch red without anybody changing any code. Bump this
+      # deliberately, alongside the pixi environment.
+      - name: Install ruff
+        run: python -m pip install --disable-pip-version-check ruff==0.16.1
+
+      - name: ruff check
+        run: ruff check .
+
+      - name: ruff format --check
+        run: ruff format --check .
+
+  # mypy is deliberately absent from this workflow. It does not currently pass
+  # on this tree, so gating CI on it would leave main permanently red and make
+  # every genuine failure invisible. Reinstate it as a job here once the
+  # outstanding errors are cleared.
+
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        # Every supported minor on Linux; the ceiling only on macOS.
+        #
+        # windows-latest is not in this matrix. environment.py resolves
+        # Scripts/python.exe correctly, but state.py builds its venv
+        # interpreter path as `bin/python` unconditionally, so the suite would
+        # not pass there. Adding Windows is a one-line change here once that
+        # is fixed -- leaving it out is honest, leaving it in would be red.
+        os: [ubuntu-latest]
+        python-version: ["3.12", "3.13"]
+        include:
+          - os: macos-latest
+            python-version: "3.13"
+
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      # Installing the project (rather than only putting src/ on the path)
+      # brings in emmykit and uv, which the suite needs: the environment and
+      # verify tests drive a real uv, and cli.py's import-time guard reads
+      # emmykit.__version__.
+      - name: Install veny and pytest
+        run: |
+          python -m pip install --disable-pip-version-check --upgrade pip
+          python -m pip install --disable-pip-version-check -e .
+          python -m pip install --disable-pip-version-check pytest
+
+      - name: Run the test suite
+        run: python -m pytest

veny-0.2.2/.gitignore

@@ -0,0 +1,35 @@
+.claude-project-id
+
+.sandbox_settings.json
+
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*.egg-info/
+
+# Tool caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# pixi environment (recreate with `pixi install`; pixi.lock is the record)
+.pixi/
+
+# veny run byproducts: the custom-module cache it pickles into the working
+# directory, and the log directory it creates. Both are per-run state.
+.veny_custom_modules_*.pkl
+logs/
+
+# superpowers subagent-driven-development scratch workspace
+.superpowers/
+
+# Packaging build outputs
+dist/
+build/
+
+# Local Claude Code harness config -- session hooks and settings for whoever
+# happens to be driving the agent, not something this project ships. CLAUDE.md
+# at the repo root IS tracked: it is the project's own instructions.
+.claude/

veny-0.2.2/.gitleaksignore

@@ -0,0 +1,28 @@
+# gitleaks allowlist.
+#
+# Every entry below is a confirmed false positive, affirmed individually
+# during the repository's publication audit on 2026-08-23 (gitleaks 8.30.1).
+#
+# The first three are all the same string: a Python standard-library module
+# name (the `pygram` submodule of `lib2to3`) appearing inside a hard-coded
+# list of stdlib module names, next to its `pgen2.tokenize` sibling.
+# gitleaks' generic-api-key rule flags it on Shannon entropy alone (3.807),
+# with no credential-shaped context anywhere near it. It is not a secret and
+# there is nothing to rotate.
+#
+# The fingerprints are commit-scoped, so they were generated after the
+# git-filter-repo mailmap pass that rewrote every commit SHA. If history is
+# ever rewritten again, re-run gitleaks and refresh these lines.
+
+8e2b34fb1095b8c11c25835772746d069bbb3e69:veny.py:generic-api-key:486
+29b95077d93d63f5db4d430801e0fb5b80d39d27:mypy.py:generic-api-key:476
+380df7d401ceb83b77e9458329a80970ed6af02f:mypy.py:generic-api-key:447
+
+# The fourth entry is this file flagging itself. The first version of this
+# allowlist (commit 5722027) quoted the offending module names verbatim while
+# explaining them, which gitleaks then detected as a fourth leak -- in the
+# very file written to silence the first three. The comment above no longer
+# spells the pair out, so nothing new triggers it, but that first commit's
+# blob is immutable and a history scan still reaches it.
+
+5722027ccf6ffb07f8c784af41fe19f57c94a2b3:.gitleaksignore:generic-api-key:9

veny-0.2.2/.pre-commit-config.yaml

@@ -0,0 +1,47 @@
+repos:
+  - repo: local
+    hooks:  # On macOS, pixi-installed tools (pytest, ruff, mypy) can fail due to shebang path resolution issues. Using python -m <tool> bypasses this reliably.
+      - id: ruff
+        name: ruff
+        entry: pixi run python -m ruff check --fix
+        language: system
+        types: [python]
+      - id: ruff-format
+        name: ruff-format
+        entry: pixi run python -m ruff format
+        language: system
+        types: [python]
+      - id: mypy
+        name: mypy
+        entry: pixi run python -m mypy .
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      # Built-in pygrep — no remote pre-commit-hooks dep, no network.
+      # Real conflict markers: `<<<<<<< <ref>` and `>>>>>>> <ref>` (with
+      # trailing space) and `=======` *alone on a line*. The bare-`=======`
+      # form would otherwise false-positive on pytest's `======== … ========`
+      # header lines (>7 equals followed by text), so we anchor it $.
+      - id: check-merge-conflict
+        name: check-merge-conflict
+        entry: '^(<<<<<<< |>>>>>>> |={7}$)'
+        language: pygrep
+
+      # Local reimplementation of pre-commit-hooks' check-added-large-files
+      # (default maxkb=500 → 500000 bytes). System bash + wc only; bash's
+      # arithmetic context strips BSD-wc's leading whitespace so no tr needed.
+      - id: check-added-large-files
+        name: check-added-large-files (limit 500 KB)
+        entry: 'bash -c ''max=500000; rc=0; for f in "$@"; do sz=$(wc -c < "$f"); if (( sz > max )); then echo "$f: $sz bytes exceeds limit of $max" >&2; rc=1; fi; done; exit $rc'' --'
+        language: system
+
+      # Local reimplementation of pre-commit-hooks' check-toml. tomllib is
+      # stdlib in 3.11+; this template requires 3.12+. Routed through
+      # `pixi run python` so the env (and its Python) is the same one the
+      # other hooks use.
+      - id: check-toml
+        name: check-toml
+        entry: 'pixi run python -c ''import sys,tomllib;[tomllib.load(open(f,"rb")) for f in sys.argv[1:]]'''
+        language: system
+        types: [toml]

veny-0.2.2/CLAUDE.md

@@ -0,0 +1,126 @@
+# Project: veny
+
+## Session resume protocol (read this first, every session)
+This project may be built across multiple sessions, and a session can die
+mid-run. On **every** new or resumed session, before doing anything else:
+
+1. Read `PROGRESS.md` at the repo root. It carries the index of the current
+   active work AND the project's running notebook of deferred items,
+   cross-cutting decisions, gotchas, and open questions. Read all of it.
+2. Open the design doc and implementation plan that `PROGRESS.md` points to.
+3. Run `git log --oneline -20` to see what is already committed.
+4. Resume from the first unchecked task in the plan. **Do not** redo work
+   that is already committed.
+
+If `PROGRESS.md` does not exist yet, you are at the very start of the
+project; create it (with the headings described in the Durability rules
+below, sections initially empty) as soon as a design or plan exists.
+
+If Superpowers is installed and this project uses it, prefer its native
+resume mechanism (`/superpowers-extended-cc:executing-plans <plan-path>`)
+over reading `PROGRESS.md`'s **Current work** section by hand — that
+command reads the plan's `.tasks.json` and picks up exactly where the
+last session stopped. The other PROGRESS.md sections (deferred items,
+decisions, gotchas, open questions) are NOT covered by Superpowers, so
+read them either way.
+
+## Durability rules (always)
+- **Git is the source of truth, not the conversation.** Commit after every
+  completed task, with a clear message. Never end a step with completed
+  work left uncommitted.
+- **Keep `PROGRESS.md` current.** The **Current work** block is an index
+  — point at the design doc, plan, and task tracker; do NOT duplicate the
+  task checklist into PROGRESS.md (link to the plan instead, so there's
+  one place to update task state). The other sections (deferred items,
+  cross-cutting decisions, gotchas, open questions) hold canonical content
+  that lives nowhere else; add to them as the project teaches you things
+  worth not forgetting. Refresh the "next action" line and commit
+  PROGRESS.md after each task.
+- **Persist the brainstorm as it forms.** During brainstorming, append
+  each validated design section to the design doc and commit it — never
+  leave the agreed design only in the conversation.
+- **Migrate, don't duplicate.** When a deferred item or open question
+  becomes active work, move it out of PROGRESS.md into the new design/plan
+  rather than leaving a copy behind.
+
+## Environment & tools
+
+- Use `rg` instead of `grep`, `fd` instead of `find`.
+
+## Workspace scaffolding
+
+This project has already been scaffolded. The following files
+already exist and should NOT be recreated:
+
+- `pyproject.toml` — project metadata + ruff/mypy/pytest/coverage config
+- `pixi.toml` — pixi workspace with dev dependencies (ruff, mypy, pytest, pytest-cov, pre-commit)
+- `.pre-commit-config.yaml` — pre-commit hooks (ruff, ruff-format, mypy, trailing-whitespace, end-of-file-fixer, etc.)
+- `.gitignore` — standard Python ignores
+
+**Do NOT run `pixi init` or `pre-commit sample-config`.**
+
+## Project layout
+
+Use a `src/` layout:
+
+```
+src/
+  <package_name>/
+    __init__.py
+    __main__.py
+    ...
+tests/
+  __init__.py
+  test_*.py
+```
+
+The package name should be the project name normalized to a valid Python identifier
+(lowercase, spaces/hyphens replaced with underscores).
+
+## Running tools
+
+All dev tools are installed via pixi. Use `pixi run` to invoke them:
+
+- `pixi run test` — run tests (pytest)
+- `pixi run lint` — lint (ruff check .)
+- `pixi run format` — format (ruff format .)
+- `pixi run typecheck` — type check (mypy .)
+- `pixi run pre-commit run` — run pre-commit on staged files
+- `pixi run pre-commit run --files <path>` — run pre-commit on specific files
+- `pixi run pre-commit run --all-files` — run pre-commit on every file
+- `pixi run pre-commit install` — install the git pre-commit hook
+  (`pre-commit` is only available via `pixi run` — no system binary)
+
+To add a new dependency: `pixi add <package>`
+To add a PyPI-only dependency: `pixi add --pypi <package>`
+
+## Cross-platform conda gotchas
+
+This project's `pixi.toml` lists `platforms = ["linux-64", "linux-aarch64", "osx-arm64", "osx-64"]`,
+so `pixi install` must solve cleanly on macOS even when the actual run happens in
+the Linux container. Some conda-forge packages have no `osx-arm64` build and will
+fail resolution on macOS with `No candidates were found`. Move them into
+`[target.linux-64.dependencies]` (already scaffolded into your `pixi.toml`)
+instead of `[dependencies]`.
+
+Symptom: `pixi add <pkg>` (or `pixi install`) fails with
+`No candidates were found for <pkg>` while the package clearly exists on
+conda-forge for linux-64.
+
+Fix: edit `pixi.toml` to add the package under `[target.linux-64.dependencies]`,
+then `pixi install`. Or use `pixi add --platform linux-64 <pkg>`.
+
+Known offenders (non-exhaustive):
+
+- `pngquant` — pulled in by `ocrmypdf`; together they force linux-64-only.
+- `pytorch-cuda` — CUDA runtime, linux-only by design.
+
+If you can swap to a lighter cross-platform alternative, prefer that
+(e.g. `tesseract` + `pytesseract` + `pypdfium2` instead of `ocrmypdf`).
+
+## First-time setup
+
+Already done by the container entrypoint — git repo
+initialized, git identity configured, dependencies
+installed, pre-commit hooks active, initial scaffold
+committed.

veny-0.2.2/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2024 Emmy Killett
+
+   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.