covsight-core 0.1.2__tar.gz

covsight_core-0.1.2/.github/workflows/ci.yml

@@ -0,0 +1,102 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  python:
+    name: Python tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - name: Install
+        run: pip install -e ".[dev,validate]"
+      - name: Test
+        run: pytest
+
+  typescript:
+    name: TypeScript tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "20"
+          cache: npm
+          cache-dependency-path: ts/package-lock.json
+      - name: Install
+        run: cd ts && npm ci
+      - name: Lint
+        run: cd ts && npm run lint
+      - name: Build
+        run: cd ts && npm run build
+      - name: Test
+        run: cd ts && npm test
+
+  c:
+    name: C tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - name: Fetch C dependencies
+        run: pip install ivpm && ivpm update
+      - name: Build
+        run: cmake -S c -B c/build && cmake --build c/build
+      - name: Test
+        run: ctest --test-dir c/build --output-on-failure
+
+  docs:
+    # BUILD ONLY. This workflow does not publish docs, by design.
+    #
+    # Docs for every dvkit project are published by FORGEJO, not GitHub. The
+    # host-side poller (~/dvkit-docs/bin/docs-fetch) reads build artifacts from
+    # the Forgejo API, promotes them, and deploys with a Cloudflare token that
+    # never enters a job container. A Cloudflare Pages deployment replaces the
+    # WHOLE site, so dvkit.org is a single Pages space shared by every project
+    # -- there is exactly one publisher for it, and it is not here.
+    #
+    # What used to follow was a `docs-deploy` job. It was first converted from
+    # branch-driven to tag-driven (so a mirrored push could not republish as a
+    # side effect of a sync), and then removed outright: GitHub Pages would be
+    # a second, divergent copy of the docs, and the `docs-covsight-covsight-core`
+    # artifact this job used to upload for the poller was consumed by nothing,
+    # because the poller only ever looks at Forgejo.
+    #
+    # The Forgejo-side docs job that actually publishes lives in
+    # .forgejo/workflows/ and uploads `docs-covsight-covsight-core`.
+    #
+    # This job stays because a docs build that breaks should still fail a push.
+    name: Build docs
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "20"
+          cache: npm
+          cache-dependency-path: ts/package-lock.json
+      - name: Install TypeScript dependencies
+        run: cd ts && npm ci
+      - name: Install doc dependencies
+        run: pip install -r docs/requirements.txt
+      - name: Patch sphinx-js BigInt bug
+        run: |
+          SPHINX_JS_PATH=$(python -c "import sphinx_js, os; print(os.path.dirname(sphinx_js.__file__))")
+          patch "$SPHINX_JS_PATH/js/convertType.ts" docs/patches/sphinx-js-bigint.patch
+      - name: Build docs
+        run: cd docs && make html

covsight_core-0.1.2/.github/workflows/publish.yml

@@ -0,0 +1,156 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  gate:
+    # Release master switch. ONE file, above both platforms, decides who
+    # releases this repo:
+    #   https://dvkit.org/.well-known/release-authority.json
+    # Generated from /srv/forgejo/etc/sync-policy.toml by
+    # `git-sync emit-release-authority`, so GitHub and Forgejo cannot drift --
+    # there is only one copy for them to disagree about.
+    #
+    # The runner only READS it, over plain HTTPS with no credential: a workflow
+    # file is public and editable by anyone who can push, so nothing secret
+    # goes in one.
+    #
+    # `if:` on a job cannot reference a step in its own job, so the switch is
+    # resolved here and consumed via needs.gate.outputs.authority.
+    name: Release authority
+    runs-on: ubuntu-latest
+    outputs:
+      authority: ${{ steps.resolve.outputs.authority }}
+    steps:
+      - id: resolve
+        # The resolver is one line on purpose. A multi-line `python3 -c` script
+        # has to start at column 0, which terminates the YAML block scalar and
+        # silently corrupts the workflow.
+        run: |
+          url=https://dvkit.org/.well-known/release-authority.json
+          if ! body=$(curl -fsS --max-time 10 "$url"); then
+            # Fail CLOSED, but only make noise when a release was actually due:
+            # a missed release is recoverable, a wrong one is not.
+            case "$GITHUB_REF" in
+              refs/tags/v*)
+                echo "::error::release-authority switch unreachable; refusing to publish"
+                exit 1 ;;
+              *)
+                echo "authority=none" >> "$GITHUB_OUTPUT"
+                echo "switch unreachable on a non-tag ref; nothing to release"
+                exit 0 ;;
+            esac
+          fi
+          auth=$(printf '%s' "$body" | python3 -c 'import json,os,sys; d=json.load(sys.stdin); r=os.environ["GITHUB_REPOSITORY"]; print(d["repos"].get(r) or d["orgs"].get(r.split("/")[0]) or d["default"])')
+          echo "release authority for $GITHUB_REPOSITORY: $auth"
+          echo "authority=$auth" >> "$GITHUB_OUTPUT"
+
+  test-python:
+    name: Python tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - name: Install
+        # Must match ci.yml's extras exactly. This job used to install only
+        # ".[dev]" while ci.yml installed ".[dev,validate]", so the release
+        # path ran a suite that ci.yml never ran: 21 tests died with
+        # "ImportError: jsonschema is required for validation". It went
+        # unnoticed until the first tag, because until then this workflow had
+        # never run at all. The publish jobs `needs` this one, so the effect
+        # was a release that could never happen rather than a bad release --
+        # but the two extras lists must not drift again.
+        run: pip install -e ".[dev,validate]"
+      - name: Test
+        run: pytest
+
+  test-typescript:
+    name: TypeScript tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "20"
+          cache: npm
+          cache-dependency-path: ts/package-lock.json
+      - name: Install
+        run: cd ts && npm ci
+      - name: Lint
+        run: cd ts && npm run lint
+      - name: Build
+        run: cd ts && npm run build
+      - name: Test
+        run: cd ts && npm test
+
+  publish-pypi:
+    name: Publish to PyPI
+    # Skips -- does not fail -- when the switch names the other side. A red
+    # build on the dormant side every time anyone tags would train people to
+    # ignore the signal, which is worse than no signal.
+    if: startsWith(github.ref, 'refs/tags/v') && needs.gate.outputs.authority == 'github'
+    needs: [gate, test-python, test-typescript]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - name: Build
+        run: |
+          pip install build twine
+          python -m build
+          twine check dist/*
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}
+          # Idempotence net: with one switch and two possible publishers, a
+          # double-fire must be a no-op rather than a failure or a corruption.
+          skip-existing: true
+
+  publish-npm:
+    name: Publish to NPM
+    if: startsWith(github.ref, 'refs/tags/v') && needs.gate.outputs.authority == 'github'
+    needs: [gate, test-python, test-typescript]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "20"
+          registry-url: https://registry.npmjs.org
+          cache: npm
+          cache-dependency-path: ts/package-lock.json
+      - name: Install
+        run: cd ts && npm ci
+      - name: Set version
+        run: |
+          VERSION="${GITHUB_REF_NAME#v}"
+          cd ts && npm pkg set version="$VERSION"
+      - name: Build
+        run: cd ts && npm run build
+      - name: Dry run
+        run: cd ts && npm pack --dry-run
+      # npm has no --skip-existing, so the check is explicit. Same reasoning as
+      # the PyPI step: a re-run or a double-fire must be a no-op.
+      - name: Publish
+        run: |
+          cd ts
+          VERSION="${GITHUB_REF_NAME#v}"
+          if npm view "@covsight/core@$VERSION" version >/dev/null 2>&1; then
+            echo "@covsight/core@$VERSION is already published -- nothing to do"
+            exit 0
+          fi
+          npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

covsight_core-0.1.2/.gitignore

@@ -0,0 +1,18 @@
+__pycache__/
+*.py[cod]
+*.so
+*.o
+*.egg-info/
+dist/
+build/
+.eggs/
+.pytest_cache/
+*.cdb
+# Golden compat fixtures are committed (see tests/compat/golden/README.md);
+# the C migration tests read them and they cannot be regenerated in CI
+# because they intentionally carry the pre-3.0 JSON manifest format.
+!tests/compat/golden/*.cdb
+packages/
+node_modules/
+
+_build*/

covsight_core-0.1.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 [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.

covsight_core-0.1.2/PKG-INFO

@@ -0,0 +1,25 @@
+Metadata-Version: 2.4
+Name: covsight-core
+Version: 0.1.2
+Summary: Core UCIS data-model API and NCDB format for coverage data
+Author: CovSight Contributors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/covsight/covsight-core
+Project-URL: Repository, https://github.com/covsight/covsight-core
+Project-URL: Issues, https://github.com/covsight/covsight-core/issues
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pyyaml>=5.1
+Provides-Extra: accel
+Requires-Dist: cffi>=1.15; extra == "accel"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Provides-Extra: validate
+Requires-Dist: jsonschema>=4.0; extra == "validate"
+Provides-Extra: hjson
+Requires-Dist: hjson>=3.0; extra == "hjson"
+Dynamic: license-file
+
+# covsight-core

covsight_core-0.1.2/README.md

@@ -0,0 +1 @@
+# covsight-core

covsight_core-0.1.2/c/CMakeLists.txt

@@ -0,0 +1,58 @@
+cmake_minimum_required(VERSION 3.16)
+project(ncdb LANGUAGES C)
+
+set(CMAKE_C_STANDARD 99)
+set(CMAKE_C_STANDARD_REQUIRED ON)
+set(CMAKE_C_EXTENSIONS OFF)
+set(CMAKE_POSITION_INDEPENDENT_CODE ON)
+
+set(MZ_COMPAT    ON  CACHE BOOL "" FORCE)
+set(MZ_BZIP2     OFF CACHE BOOL "" FORCE)
+set(MZ_LZMA      OFF CACHE BOOL "" FORCE)
+set(MZ_PPMD      OFF CACHE BOOL "" FORCE)
+set(MZ_ZSTD      OFF CACHE BOOL "" FORCE)
+set(MZ_WZAES     OFF CACHE BOOL "" FORCE)
+set(MZ_OPENSSL   OFF CACHE BOOL "" FORCE)
+set(MZ_LIBBSD    OFF CACHE BOOL "" FORCE)
+set(MZ_BUILD_UNIT_TESTS OFF CACHE BOOL "" FORCE)
+set(MZ_BUILD_TESTS      OFF CACHE BOOL "" FORCE)
+
+add_subdirectory(${CMAKE_CURRENT_SOURCE_DIR}/../packages/minizip-ng ${CMAKE_CURRENT_BINARY_DIR}/minizip-ng)
+
+set(NCDB_SOURCES
+    src/ncdb_varint.c
+    src/ncdb_zip.c
+    src/ncdb_strings.c
+    src/ncdb_scope_tree.c
+    src/ncdb_counts.c
+    src/ncdb_manifest.c
+    src/ncdb_history.c
+    src/ncdb_sources.c
+    src/ncdb_attrs.c
+    src/ncdb_props.c
+    src/ncdb_unique_id.c
+    src/ncdb_tests_assoc.c
+    src/ncdb_formal.c
+    src/ncdb_metric.c
+    src/ncdb_toggle.c
+    src/ncdb_cross.c
+    src/ncdb_fsm.c
+    src/ncdb_tags.c
+    src/ncdb_issues.c
+    src/ncdb_db.c
+    ${CMAKE_CURRENT_SOURCE_DIR}/../packages/cjson/cJSON.c)
+
+add_library(ncdb SHARED ${NCDB_SOURCES})
+target_include_directories(ncdb
+    PUBLIC
+        ${CMAKE_CURRENT_SOURCE_DIR}/include
+    PRIVATE
+        ${CMAKE_CURRENT_SOURCE_DIR}/src
+        ${CMAKE_CURRENT_SOURCE_DIR}/../packages/cjson
+        ${CMAKE_CURRENT_SOURCE_DIR}/../packages/minizip-ng
+        ${CMAKE_CURRENT_BINARY_DIR}/minizip-ng)
+target_link_libraries(ncdb PUBLIC MINIZIP::minizip)
+
+enable_testing()
+add_subdirectory(tests)
+add_subdirectory(ucis)

covsight_core-0.1.2/c/README.md

@@ -0,0 +1,11 @@
+# NCDB C Library
+
+Native C99 reader/writer for the NCDB coverage database format.
+
+## Build
+
+```sh
+cmake -S c -B c/build
+cmake --build c/build
+ctest --test-dir c/build --output-on-failure
+```