Datasets:
Release [run release-20261111T133413Z]
#19
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
- CHANGELOG.md +18 -0
- README.md +26 -26
- README.zh.md +26 -26
- campaign_files/2026-10-a-spreadsheets-with-answers-2/kstate-agmanager-decision-tools/README.md +0 -2
- campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-gerber/README.md +0 -6
- campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-pcb/README.md +0 -10
- campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-sch/README.md +0 -6
- campaign_files/2026-10-gt-browser-tests-2/laminas-mail-mbox-inbox/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/king-county-metro-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/konectbus-passenger-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/ku-lawrence-transit-combined-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/la-metro-bus-gtfs/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/komascript-uni-titlepage-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/kozea-weasyprint-tests-draw/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/kramdown-asciidoc-scenario-table-alignment/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex-package-repositories-oberdiek-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-fontspec-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-graphics-def-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-hyperref-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-l3build-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-latex2e-latex-lab-testfiles/README.md +0 -6
- campaign_files/2026-10-md-media-and-documents/latex3-latex3-l3kernel-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-luamml-testfiles-lua/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-luaotfload-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-unicode-math-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latex3-xcolor-testfiles/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/latexml-t-alignment-halign/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/kios-research-leakdb/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kics-infrastructure-as-code-query-library/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kics-query-tests/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kics-query-with-positive-and-negative-tests/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kube-linter-checks-with-per-check-yaml-fixtures-and-bats-end-to-end-tests/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kube-linter-end-to-end-tests/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kubeaudit-auditor-fixtures/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kubelinter-check-fixtures-with-bats-end-to-end-expectations/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/kubescape-regolibrary/README.md +0 -18
- campaign_files/2026-10-s-security-detection-2/kyverno-policies-library-with-kyverno-cli-and-chainsaw-tests/README.md +0 -22
- campaign_files/2026-10-sc-science-reference-data-2/lammps-force-style-tests/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data-2/lastz-test-data/README.md +0 -6
- campaign_files/2026-10-sc-science-reference-data/lammps-unittest-force-styles/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises/kotlin-codegen-box/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises/kotlin-koans-edu/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises/learn-go-with-tests/README.md +0 -4
- cards/0xdea-semgrep-rules.md +2 -2
- cards/1brc-test-samples.md +2 -2
- cards/2dpacklib.md +2 -2
- cards/abacus-integrate-tests.md +2 -2
- cards/abhishekumarr00-supply-chain-mastery.md +2 -2
- cards/academy-bus-nj-gtfs.md +2 -2
- cards/accordproject-cicero-template-library.md +2 -2
CHANGELOG.md
CHANGED
|
@@ -3141,3 +3141,21 @@ Changes to the content of this index, oldest first. There is one entry for each
|
|
| 3141 |
- hf-training-records: refused
|
| 3142 |
- npm: refused
|
| 3143 |
- stackexchange-api-posts: refused
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 3141 |
- hf-training-records: refused
|
| 3142 |
- npm: refused
|
| 3143 |
- stackexchange-api-posts: refused
|
| 3144 |
+
|
| 3145 |
+
## 2026-11-11: sources held back
|
| 3146 |
+
|
| 3147 |
+
- Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
|
| 3148 |
+
- borealis-dataverse-workbooks-cc-by: changed pointer group file data/borealis-dataverse-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc-by after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3149 |
+
- borealis-dataverse-workbooks-cc0: changed pointer group file data/borealis-dataverse-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3150 |
+
- cfpb-complaints: refused
|
| 3151 |
+
- data-gov-uk-workbooks: changed pointer group file data/data-gov-uk-workbooks/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 4 key(s) of the old version are in no data file of source data-gov-uk-workbooks after the commit (row 5 from batch 2026-10-a-spreadsheets-with-answers, row 6 from batch 2026-10-a-spreadsheets-with-answers, row 12 from batch 2026-10-a-spreadsheets-with-answers, 1 more); the removal record holds none of them, and none fails a publish check now
|
| 3152 |
+
- data-gov-uk-workbooks-noassertion: changed pointer group file data/data-gov-uk-workbooks-noassertion/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source data-gov-uk-workbooks-noassertion after the commit (row 6 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3153 |
+
- dataversenl-workbooks-cc-by: changed pointer group file data/dataversenl-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source dataversenl-workbooks-cc-by after the commit (row 17 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3154 |
+
- dataversenl-workbooks-cc0: changed pointer group file data/dataversenl-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source dataversenl-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers, row 13 from batch 2026-10-a-spreadsheets-with-answers, row 16 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3155 |
+
- dvn-fvhlgg-repro: changed pointer group file data/dvn-fvhlgg-repro/2026-10-c-repros/part-00000.parquet: 3 key(s) of the old version are in no data file of source dvn-fvhlgg-repro after the commit (row 5 from batch 2026-10-c-repros, row 7 from batch 2026-10-c-repros, row 16 from batch 2026-10-c-repros); the removal record holds none of them, and none fails a publish check now
|
| 3156 |
+
- eu-institution-workbooks-cc-by: changed pointer group file data/eu-institution-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source eu-institution-workbooks-cc-by after the commit (row 2 from batch 2026-10-a-spreadsheets-with-answers, row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3157 |
+
- hdx-workbooks-cc0: changed pointer group file data/hdx-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source hdx-workbooks-cc0 after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3158 |
+
- hdx-workbooks-odbl: changed pointer group file data/hdx-workbooks-odbl/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source hdx-workbooks-odbl after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3159 |
+
- hf-training-records: refused
|
| 3160 |
+
- npm: refused
|
| 3161 |
+
- stackexchange-api-posts: refused
|
README.md
CHANGED
|
@@ -24,25 +24,25 @@ configs:
|
|
| 24 |
<!-- artifact-pointer-layout: v2 -->
|
| 25 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 26 |
|
| 27 |
-
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 28 |
|
| 29 |
This dataset is the public index of the **Training Data Foundation**: find public files to build agent tasks and environments from, and fetch them with one command.
|
| 30 |
|
| 31 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 35 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 36 |
</picture>
|
| 37 |
<picture class="not-prose">
|
| 38 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 39 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 40 |
</picture>
|
| 41 |
|
| 42 |
## Get data in one command
|
| 43 |
|
| 44 |
```sh
|
| 45 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 46 |
```
|
| 47 |
|
| 48 |
This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
@@ -52,7 +52,7 @@ the same command takes the same units of this release.
|
|
| 52 |
<details>
|
| 53 |
<summary>What the command takes, and in which order</summary>
|
| 54 |
|
| 55 |
-
The command and the queries below are pinned to the release tag `release-2026-11-11.
|
| 56 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 57 |
|
| 58 |
The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
@@ -79,7 +79,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
|
|
| 79 |
|
| 80 |
```sql
|
| 81 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 82 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 83 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 84 |
ORDER BY collection, units DESC;
|
| 85 |
```
|
|
@@ -90,7 +90,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
|
|
| 90 |
Choose files in one corpus:
|
| 91 |
|
| 92 |
```sql
|
| 93 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 94 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 95 |
FROM read_parquet(getvariable('files'))
|
| 96 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -112,12 +112,12 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 112 |
### Task material: units by collection
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 116 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 120 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,801 material sets with 4,186 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
@@ -150,12 +150,12 @@ Upstreams are the upstream works the material sets of a collection come from.
|
|
| 150 |
### Corpora: rows by main domain
|
| 151 |
|
| 152 |
<picture class="not-prose">
|
| 153 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 154 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 155 |
</picture>
|
| 156 |
<picture class="not-prose">
|
| 157 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 158 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 159 |
</picture>
|
| 160 |
|
| 161 |
139 corpora with 1,216,362,128 rows.
|
|
@@ -188,12 +188,12 @@ Every material set and every corpus, with its counts, size, license tier and log
|
|
| 188 |
## How it is made
|
| 189 |
|
| 190 |
<picture class="not-prose">
|
| 191 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 192 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 196 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 197 |
</picture>
|
| 198 |
|
| 199 |
The terms, each step and how every number is made are folded below.
|
|
@@ -247,9 +247,9 @@ only their sizes add up to the size of the whole index.
|
|
| 247 |
|
| 248 |
| Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
|
| 249 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 250 |
-
| Whole index | 4.45 PB | 4.11 PB | 36,
|
| 251 |
| Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 252 |
-
| Task material | 2.90 GB | 2.82 GB | 4,
|
| 253 |
|
| 254 |
Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
|
| 255 |
a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
|
|
@@ -444,9 +444,9 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
|
|
| 444 |
<details>
|
| 445 |
<summary>Releases</summary>
|
| 446 |
|
| 447 |
-
- Latest release: `release-2026-11-11.
|
| 448 |
- Releases are listed in [CHANGELOG.md](CHANGELOG.md);
|
| 449 |
-
each one is a commit with its own release tag (this one is [`release-2026-11-11.
|
| 450 |
so any earlier state stays readable at its tag.
|
| 451 |
- `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
|
| 452 |
- Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
@@ -479,7 +479,7 @@ A removal covers the current version of this repository (the main branch) and th
|
|
| 479 |
@misc{training_data_foundation,
|
| 480 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 482 |
-
note = {Release release-2026-11-11.
|
| 483 |
year = {2026}
|
| 484 |
}
|
| 485 |
```
|
|
|
|
| 24 |
<!-- artifact-pointer-layout: v2 -->
|
| 25 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 26 |
|
| 27 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/banner.svg" alt="Public web, in two layers (task material in collections; corpora), one row per file (address, size, SHA-256, license), your selection, fetched and verified">
|
| 28 |
|
| 29 |
This dataset is the public index of the **Training Data Foundation**: find public files to build agent tasks and environments from, and fetch them with one command.
|
| 30 |
|
| 31 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-narrow-light.svg">
|
| 35 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-wide-light.svg" alt="1,801 material sets with 4,186 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 35,277 rows compared match their recorded size.">
|
| 36 |
</picture>
|
| 37 |
<picture class="not-prose">
|
| 38 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-narrow-dark.svg">
|
| 39 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-wide-dark.svg" alt="1,801 material sets with 4,186 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 35,277 rows compared match their recorded size.">
|
| 40 |
</picture>
|
| 41 |
|
| 42 |
## Get data in one command
|
| 43 |
|
| 44 |
```sh
|
| 45 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/tools/fetch.py --form spreadsheets --sample 3 --out ./data
|
| 46 |
```
|
| 47 |
|
| 48 |
This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
|
|
| 52 |
<details>
|
| 53 |
<summary>What the command takes, and in which order</summary>
|
| 54 |
|
| 55 |
+
The command and the queries below are pinned to the release tag `release-2026-11-11.12`.
|
| 56 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 57 |
|
| 58 |
The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
|
|
| 79 |
|
| 80 |
```sql
|
| 81 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 82 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet'
|
| 83 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 84 |
ORDER BY collection, units DESC;
|
| 85 |
```
|
|
|
|
| 90 |
Choose files in one corpus:
|
| 91 |
|
| 92 |
```sql
|
| 93 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'if-archive'));
|
| 94 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 95 |
FROM read_parquet(getvariable('files'))
|
| 96 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 112 |
### Task material: units by collection
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-narrow-light.svg">
|
| 116 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-wide-light.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 189; Disk images 179; Reproduction packages and runs 106; In no collection 9; SEC filing reviews 0.">
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-narrow-dark.svg">
|
| 120 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-wide-dark.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 189; Disk images 179; Reproduction packages and runs 106; In no collection 9; SEC filing reviews 0.">
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,801 material sets with 4,186 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
|
|
| 150 |
### Corpora: rows by main domain
|
| 151 |
|
| 152 |
<picture class="not-prose">
|
| 153 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-narrow-light.svg">
|
| 154 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-wide-light.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
|
| 155 |
</picture>
|
| 156 |
<picture class="not-prose">
|
| 157 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-narrow-dark.svg">
|
| 158 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-wide-dark.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
|
| 159 |
</picture>
|
| 160 |
|
| 161 |
139 corpora with 1,216,362,128 rows.
|
|
|
|
| 188 |
## How it is made
|
| 189 |
|
| 190 |
<picture class="not-prose">
|
| 191 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-narrow-light.svg">
|
| 192 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-11.12.">
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-narrow-dark.svg">
|
| 196 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-11.12.">
|
| 197 |
</picture>
|
| 198 |
|
| 199 |
The terms, each step and how every number is made are folded below.
|
|
|
|
| 247 |
|
| 248 |
| Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
|
| 249 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 250 |
+
| Whole index | 4.45 PB | 4.11 PB | 36,158 | 35,277 | 35,147 (99.6%) | 881: address unreachable 449, file gone 80, login needed 330, no size from the server 19, other error 3 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 251 |
| Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 252 |
+
| Task material | 2.90 GB | 2.82 GB | 4,564 | 4,554 | 4,537 (99.6%) | 10: login needed 8, other error 2 | 0 | none |
|
| 253 |
|
| 254 |
Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
|
| 255 |
a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
|
|
|
|
| 444 |
<details>
|
| 445 |
<summary>Releases</summary>
|
| 446 |
|
| 447 |
+
- Latest release: `release-2026-11-11.12` (its newest CHANGELOG entry is dated 2026-11-11).
|
| 448 |
- Releases are listed in [CHANGELOG.md](CHANGELOG.md);
|
| 449 |
+
each one is a commit with its own release tag (this one is [`release-2026-11-11.12`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.12)),
|
| 450 |
so any earlier state stays readable at its tag.
|
| 451 |
- `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
|
| 452 |
- Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
|
|
| 479 |
@misc{training_data_foundation,
|
| 480 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 482 |
+
note = {Release release-2026-11-11.12},
|
| 483 |
year = {2026}
|
| 484 |
}
|
| 485 |
```
|
README.zh.md
CHANGED
|
@@ -11,25 +11,25 @@ tags:
|
|
| 11 |
---
|
| 12 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 13 |
|
| 14 |
-
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 15 |
|
| 16 |
本数据集是**数据基座**的公开索引:在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 22 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 26 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 33 |
```
|
| 34 |
|
| 35 |
这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
@@ -39,7 +39,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 39 |
<details>
|
| 40 |
<summary>命令取什么、按什么顺序取</summary>
|
| 41 |
|
| 42 |
-
这条命令和下面的查询都固定在发布标签 `release-2026-11-11.
|
| 43 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 44 |
|
| 45 |
命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
@@ -66,7 +66,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 66 |
|
| 67 |
```sql
|
| 68 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 69 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 70 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 71 |
ORDER BY collection, units DESC;
|
| 72 |
```
|
|
@@ -77,7 +77,7 @@ ORDER BY collection, units DESC;
|
|
| 77 |
在一个语料库里挑选文件:
|
| 78 |
|
| 79 |
```sql
|
| 80 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 81 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 82 |
FROM read_parquet(getvariable('files'))
|
| 83 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -99,12 +99,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 99 |
### 任务材料:按合集的单元数
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 103 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 107 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,801 个材料集,共 4,186 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
@@ -137,12 +137,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 137 |
### 语料库:按主要领域的行数
|
| 138 |
|
| 139 |
<picture class="not-prose">
|
| 140 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 141 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 142 |
</picture>
|
| 143 |
<picture class="not-prose">
|
| 144 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 145 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 146 |
</picture>
|
| 147 |
|
| 148 |
139 个语料库,共 1,216,362,128 行。
|
|
@@ -175,12 +175,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 175 |
## 怎样做成
|
| 176 |
|
| 177 |
<picture class="not-prose">
|
| 178 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 179 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 183 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
@@ -234,9 +234,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
-
| 整个索引 | 4.45 PB | 4.11 PB | 36,
|
| 238 |
| 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 239 |
-
| 任务材料 | 2.90 GB | 2.82 GB | 4,
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
@@ -433,9 +433,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
-
- 最新发布:`release-2026-11-11.
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
-
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
@@ -476,7 +476,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 476 |
@misc{training_data_foundation,
|
| 477 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 479 |
-
note = {Release release-2026-11-11.
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
|
|
|
| 11 |
---
|
| 12 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 13 |
|
| 14 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/banner.zh.svg" alt="公开网络,分两层(按合集的任务材料;语料库),每个文件一行(地址、大小、SHA-256、许可证),你的选择,下载并校验">
|
| 15 |
|
| 16 |
本数据集是**数据基座**的公开索引:在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-narrow-light.zh.svg">
|
| 22 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-wide-light.zh.svg" alt="1,801 个材料集,共 4,186 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 35,277 行中,99.6% 与记录的大小一致。">
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-narrow-dark.zh.svg">
|
| 26 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/numbers-wide-dark.zh.svg" alt="1,801 个材料集,共 4,186 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 35,277 行中,99.6% 与记录的大小一致。">
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/tools/fetch.py --form spreadsheets --sample 3 --out ./data
|
| 33 |
```
|
| 34 |
|
| 35 |
这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
|
|
| 39 |
<details>
|
| 40 |
<summary>命令取什么、按什么顺序取</summary>
|
| 41 |
|
| 42 |
+
这条命令和下面的查询都固定在发布标签 `release-2026-11-11.12` 上。
|
| 43 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 44 |
|
| 45 |
命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
|
|
| 66 |
|
| 67 |
```sql
|
| 68 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 69 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet'
|
| 70 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 71 |
ORDER BY collection, units DESC;
|
| 72 |
```
|
|
|
|
| 77 |
在一个语料库里挑选文件:
|
| 78 |
|
| 79 |
```sql
|
| 80 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'if-archive'));
|
| 81 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 82 |
FROM read_parquet(getvariable('files'))
|
| 83 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 99 |
### 任务材料:按合集的单元数
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-narrow-light.zh.svg">
|
| 103 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 189;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-narrow-dark.zh.svg">
|
| 107 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 189;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,801 个材料集,共 4,186 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
|
|
| 137 |
### 语料库:按主要领域的行数
|
| 138 |
|
| 139 |
<picture class="not-prose">
|
| 140 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-narrow-light.zh.svg">
|
| 141 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-wide-light.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
|
| 142 |
</picture>
|
| 143 |
<picture class="not-prose">
|
| 144 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-narrow-dark.zh.svg">
|
| 145 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/corpora-wide-dark.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
|
| 146 |
</picture>
|
| 147 |
|
| 148 |
139 个语料库,共 1,216,362,128 行。
|
|
|
|
| 175 |
## 怎样做成
|
| 176 |
|
| 177 |
<picture class="not-prose">
|
| 178 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-narrow-light.zh.svg">
|
| 179 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.12。">
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-narrow-dark.zh.svg">
|
| 183 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.12/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.12。">
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
+
| 整个索引 | 4.45 PB | 4.11 PB | 36,158 | 35,277 | 35,147(99.6%) | 881:地址无法访问 449 行、文件已不存在 80 行、需要登录 330 行、服务器未给出大小 19 行、其他错误 3 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 238 |
| 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 239 |
+
| 任务材料 | 2.90 GB | 2.82 GB | 4,564 | 4,554 | 4,537(99.6%) | 10:需要登录 8 行、其他错误 2 行 | 0 | 无 |
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
+
- 最新发布:`release-2026-11-11.12`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
+
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.12`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.12)),
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
|
|
| 476 |
@misc{training_data_foundation,
|
| 477 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 479 |
+
note = {Release release-2026-11-11.12},
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
campaign_files/2026-10-a-spreadsheets-with-answers-2/kstate-agmanager-decision-tools/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
| 11 |
-
**Answers:** Each file with an answer has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: key_formula_values.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-gerber/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: golden_image. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png ApertureMacroPngTransform.gbr (headless GerbView); kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png MalformedEmptyIJArcComponents.gbr (headless GerbView)
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `qa/data/cli/artwork_generation_regressions/ApertureMacroPngTransform.gbr`: KiCad GerbView: render a Gerber with a transformed aperture macro to a 64 px PNG matching the golden.
|
| 22 |
Format: RS-274X Gerber file as input; golden PNG render as answer
|
| 23 |
Origin: KiCad Gerber-viewer regression fixture (tool_fixture)
|
| 24 |
-
Reference result: golden_image
|
| 25 |
-
Reference source: qa/data/cli/artwork_generation_regressions/ApertureMacroPngTransform.png (test_gerber.py lines 38-41 name the pair; the test runs at lines 436-452)
|
| 26 |
Check: Can only be judged as a picture: the result must first be rendered to an image (the agent's PNG, or its Gerber rendered by kicad-cli gerber convert png --width 64 --no-antialias), then compared with the golden PNG by utils.images_are_equal: same size and mode, and the pixel difference must vanish after a 1-pixel erosion (test_gerber.py line 450; utils.py lines 157-189)
|
| 27 |
Tools: kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png ApertureMacroPngTransform.gbr (headless GerbView)
|
| 28 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ApertureMacroPngTransform.png (golden 64 px wide render; the answer, hide); qa/tests/cli/test_gerber.py; qa/tests/cli/utils.py (images_are_equal); qa/tests/cli/conftest.py; LICENSE.README
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `qa/data/cli/artwork_generation_regressions/MalformedEmptyIJArcComponents.gbr`: KiCad GerbView: render a Gerber whose arcs have empty I/J fields to a 64 px PNG matching the golden.
|
| 31 |
Format: RS-274X Gerber file as input; golden PNG render as answer
|
| 32 |
Origin: KiCad Gerber-viewer regression fixture (tool_fixture)
|
| 33 |
-
Reference result: golden_image
|
| 34 |
-
Reference source: qa/data/cli/artwork_generation_regressions/MalformedEmptyIJArcComponents.png (test_gerber.py lines 38-41 name the pair; the test runs at lines 454-469)
|
| 35 |
Check: Can only be judged as a picture: the result must first be rendered to an image (the agent's PNG, or its Gerber rendered by kicad-cli gerber convert png --width 64 --no-antialias), then compared with the golden PNG by utils.images_are_equal: same size and mode, and the pixel difference must vanish after a 1-pixel erosion (test_gerber.py line 467; utils.py lines 157-189)
|
| 36 |
Tools: kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png MalformedEmptyIJArcComponents.gbr (headless GerbView)
|
| 37 |
Companions (not included): qa/data/cli/artwork_generation_regressions/MalformedEmptyIJArcComponents.png (golden 64 px wide render; the answer, hide); qa/tests/cli/test_gerber.py; qa/tests/cli/utils.py (images_are_equal); qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png ApertureMacroPngTransform.gbr (headless GerbView); kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png MalformedEmptyIJArcComponents.gbr (headless GerbView)
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
|
|
| 19 |
- `qa/data/cli/artwork_generation_regressions/ApertureMacroPngTransform.gbr`: KiCad GerbView: render a Gerber with a transformed aperture macro to a 64 px PNG matching the golden.
|
| 20 |
Format: RS-274X Gerber file as input; golden PNG render as answer
|
| 21 |
Origin: KiCad Gerber-viewer regression fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Can only be judged as a picture: the result must first be rendered to an image (the agent's PNG, or its Gerber rendered by kicad-cli gerber convert png --width 64 --no-antialias), then compared with the golden PNG by utils.images_are_equal: same size and mode, and the pixel difference must vanish after a 1-pixel erosion (test_gerber.py line 450; utils.py lines 157-189)
|
| 23 |
Tools: kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png ApertureMacroPngTransform.gbr (headless GerbView)
|
| 24 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ApertureMacroPngTransform.png (golden 64 px wide render; the answer, hide); qa/tests/cli/test_gerber.py; qa/tests/cli/utils.py (images_are_equal); qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 26 |
- `qa/data/cli/artwork_generation_regressions/MalformedEmptyIJArcComponents.gbr`: KiCad GerbView: render a Gerber whose arcs have empty I/J fields to a 64 px PNG matching the golden.
|
| 27 |
Format: RS-274X Gerber file as input; golden PNG render as answer
|
| 28 |
Origin: KiCad Gerber-viewer regression fixture (tool_fixture)
|
|
|
|
|
|
|
| 29 |
Check: Can only be judged as a picture: the result must first be rendered to an image (the agent's PNG, or its Gerber rendered by kicad-cli gerber convert png --width 64 --no-antialias), then compared with the golden PNG by utils.images_are_equal: same size and mode, and the pixel difference must vanish after a 1-pixel erosion (test_gerber.py line 467; utils.py lines 157-189)
|
| 30 |
Tools: kicad-cli gerber convert png --width 64 --no-antialias -o OUT.png MalformedEmptyIJArcComponents.gbr (headless GerbView)
|
| 31 |
Companions (not included): qa/data/cli/artwork_generation_regressions/MalformedEmptyIJArcComponents.png (golden 64 px wide render; the answer, hide); qa/tests/cli/test_gerber.py; qa/tests/cli/utils.py (images_are_equal); qa/tests/cli/conftest.py; LICENSE.README
|
campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-pcb/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: golden_output_files. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** kicad-cli pcb export drill --format excellon [-u in | --excellon-mirror-y] -o DIR/ basic_test.kicad_pcb, and --format gerber for the PTH drill map; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb; the judge uses kicad-cli gerber diff --format json --no-align; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd; the judge uses kicad-cli gerber diff --format json --no-align; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu -o DIR/ Issue24143.kicad_pcb; judged with kicad-cli gerber diff --format json --no-align
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `qa/data/cli/basic_test/basic_test.kicad_pcb`: KiCad board basic_test: export Excellon drill files (mm, inches, mirrored) and a Gerber drill file.
|
| 22 |
Format: KiCad 10 board (.kicad_pcb S-expression) as input; golden Excellon .drl and Gerber X2 drill files as answers
|
| 23 |
Origin: KiCad command-line test fixture (tool_fixture)
|
| 24 |
-
Reference result: golden_output_files
|
| 25 |
-
Reference source: qa/data/cli/basic_test/basic_test_excellon_{default,inches,mirror}.drl and basic_test-PTH-drl.gbr (test_pcb.py lines 238-267)
|
| 26 |
Check: Final file state: compare each drill file the agent writes with its golden by utils.textdiff_files after dropping the header lines (5 for Excellon, 9 for Gerber), test_pcb.py line 302. Text diff, no screenshot
|
| 27 |
Tools: kicad-cli pcb export drill --format excellon [-u in | --excellon-mirror-y] -o DIR/ basic_test.kicad_pcb, and --format gerber for the PTH drill map
|
| 28 |
Companions (not included): qa/data/cli/basic_test/basic_test.kicad_pro (project file); qa/data/cli/basic_test/basic_test_excellon_default.drl, basic_test_excellon_inches.drl, basic_test_excellon_mirror.drl, basic_test-PTH-drl.gbr (golden drill files; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_drill); qa/tests/cli/utils.py; qa/tests/cli/conftest.py; LICENSE.README
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7.kicad_pcb`: KiCad zone-fill regression board from 4.0.7: plot F.Cu and B.Cu to Gerber and SVG matching the golden artwork.
|
| 31 |
Format: KiCad board (KiCad 4.0.7 era .kicad_pcb) with filled copper zones as input; golden RS-274X Gerbers and SVG plots of F.Cu and B.Cu as answers
|
| 32 |
Origin: KiCad artwork-generation regression fixture (tool_fixture)
|
| 33 |
-
Reference result: golden_output_files
|
| 34 |
-
Reference source: qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-{F,B}_Cu.gbr (test_pcb.py lines 174-186) and qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-{F,B}_Cu.svg (test_pcb.py lines 82-90)
|
| 35 |
Check: Final file state, two judges. Gerber: kicad-cli gerber diff --format json --no-align between the agent's Gerber and the golden; total_diff_percent must be at most 0.5 (utils.py lines 253-276, test_pcb.py lines 177-183). SVG: this one can only be judged as a picture: render both SVGs to PNG at 850 DPI with cairosvg and compare the images with utils.images_are_equal, which passes when the pixel difference vanishes after a 1-pixel erosion (utils.py lines 157-189 and 238-248, test_pcb.py lines 116-117: 1 px is 30 um, so about 90 um of allowed error)
|
| 36 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb; the judge uses kicad-cli gerber diff --format json --no-align
|
| 37 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-F_Cu.gbr and ZoneFill-4.0.7-B_Cu.gbr (golden Gerbers; the answer, hide); qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-F_Cu.svg and ZoneFill-4.0.7-B_Cu.svg (golden SVG plots; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_svg and test_pcb_export_gerber); qa/tests/cli/utils.py (svgs_are_equivalent, images_are_equal, gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
|
@@ -39,8 +33,6 @@ Files:
|
|
| 39 |
- `qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy.brd`: KiCad legacy .brd zone-fill board: plot F.Cu and B.Cu to Gerber and SVG matching the golden artwork.
|
| 40 |
Format: KiCad board (legacy .brd) with filled copper zones as input; golden RS-274X Gerbers and SVG plots of F.Cu and B.Cu as answers
|
| 41 |
Origin: KiCad artwork-generation regression fixture (tool_fixture)
|
| 42 |
-
Reference result: golden_output_files
|
| 43 |
-
Reference source: qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-{F,B}_Cu.gbr (test_pcb.py lines 174-186) and qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-{F,B}_Cu.svg (test_pcb.py lines 82-90)
|
| 44 |
Check: Final file state, two judges. Gerber: kicad-cli gerber diff --format json --no-align between the agent's Gerber and the golden; total_diff_percent must be at most 0.5 (utils.py lines 253-276, test_pcb.py lines 177-183). SVG: this one can only be judged as a picture: render both SVGs to PNG at 850 DPI with cairosvg and compare the images with utils.images_are_equal, which passes when the pixel difference vanishes after a 1-pixel erosion (utils.py lines 157-189 and 238-248, test_pcb.py lines 116-117: 1 px is 30 um, so about 90 um of allowed error)
|
| 45 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd; the judge uses kicad-cli gerber diff --format json --no-align
|
| 46 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-F_Cu.gbr and ZoneFill-Legacy-B_Cu.gbr (golden Gerbers; the answer, hide); qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-F_Cu.svg and ZoneFill-Legacy-B_Cu.svg (golden SVG plots; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_svg and test_pcb_export_gerber); qa/tests/cli/utils.py (svgs_are_equivalent, images_are_equal, gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
|
@@ -48,8 +40,6 @@ Files:
|
|
| 48 |
- `qa/data/cli/artwork_generation_regressions/Issue24143.kicad_pcb`: KiCad board with a degenerate polygon spike: plot F.Cu to Gerber with zero area difference from the golden.
|
| 49 |
Format: KiCad 10 board (.kicad_pcb) as input; golden RS-274X Gerber as answer
|
| 50 |
Origin: KiCad regression fixture for issue 24143 (tool_fixture)
|
| 51 |
-
Reference result: golden_output_files
|
| 52 |
-
Reference source: qa/data/cli/artwork_generation_regressions/Issue24143-F_Cu.gbr (test_pcb.py lines 192-194)
|
| 53 |
Check: Final file state: kicad-cli gerber diff --format json --no-align between the agent's F.Cu Gerber and the golden; total_diff_percent must be 0.0 (utils.py lines 253-276). No screenshot
|
| 54 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu -o DIR/ Issue24143.kicad_pcb; judged with kicad-cli gerber diff --format json --no-align
|
| 55 |
Companions (not included): qa/data/cli/artwork_generation_regressions/Issue24143-F_Cu.gbr (golden Gerber; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_gerber); qa/tests/cli/utils.py (gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** kicad-cli pcb export drill --format excellon [-u in | --excellon-mirror-y] -o DIR/ basic_test.kicad_pcb, and --format gerber for the PTH drill map; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb; the judge uses kicad-cli gerber diff --format json --no-align; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd; the judge uses kicad-cli gerber diff --format json --no-align; kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu -o DIR/ Issue24143.kicad_pcb; judged with kicad-cli gerber diff --format json --no-align
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
|
|
| 19 |
- `qa/data/cli/basic_test/basic_test.kicad_pcb`: KiCad board basic_test: export Excellon drill files (mm, inches, mirrored) and a Gerber drill file.
|
| 20 |
Format: KiCad 10 board (.kicad_pcb S-expression) as input; golden Excellon .drl and Gerber X2 drill files as answers
|
| 21 |
Origin: KiCad command-line test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: compare each drill file the agent writes with its golden by utils.textdiff_files after dropping the header lines (5 for Excellon, 9 for Gerber), test_pcb.py line 302. Text diff, no screenshot
|
| 23 |
Tools: kicad-cli pcb export drill --format excellon [-u in | --excellon-mirror-y] -o DIR/ basic_test.kicad_pcb, and --format gerber for the PTH drill map
|
| 24 |
Companions (not included): qa/data/cli/basic_test/basic_test.kicad_pro (project file); qa/data/cli/basic_test/basic_test_excellon_default.drl, basic_test_excellon_inches.drl, basic_test_excellon_mirror.drl, basic_test-PTH-drl.gbr (golden drill files; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_drill); qa/tests/cli/utils.py; qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 26 |
- `qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7.kicad_pcb`: KiCad zone-fill regression board from 4.0.7: plot F.Cu and B.Cu to Gerber and SVG matching the golden artwork.
|
| 27 |
Format: KiCad board (KiCad 4.0.7 era .kicad_pcb) with filled copper zones as input; golden RS-274X Gerbers and SVG plots of F.Cu and B.Cu as answers
|
| 28 |
Origin: KiCad artwork-generation regression fixture (tool_fixture)
|
|
|
|
|
|
|
| 29 |
Check: Final file state, two judges. Gerber: kicad-cli gerber diff --format json --no-align between the agent's Gerber and the golden; total_diff_percent must be at most 0.5 (utils.py lines 253-276, test_pcb.py lines 177-183). SVG: this one can only be judged as a picture: render both SVGs to PNG at 850 DPI with cairosvg and compare the images with utils.images_are_equal, which passes when the pixel difference vanishes after a 1-pixel erosion (utils.py lines 157-189 and 238-248, test_pcb.py lines 116-117: 1 px is 30 um, so about 90 um of allowed error)
|
| 30 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-4.0.7.kicad_pcb; the judge uses kicad-cli gerber diff --format json --no-align
|
| 31 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-F_Cu.gbr and ZoneFill-4.0.7-B_Cu.gbr (golden Gerbers; the answer, hide); qa/data/cli/artwork_generation_regressions/ZoneFill-4.0.7-F_Cu.svg and ZoneFill-4.0.7-B_Cu.svg (golden SVG plots; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_svg and test_pcb_export_gerber); qa/tests/cli/utils.py (svgs_are_equivalent, images_are_equal, gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 33 |
- `qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy.brd`: KiCad legacy .brd zone-fill board: plot F.Cu and B.Cu to Gerber and SVG matching the golden artwork.
|
| 34 |
Format: KiCad board (legacy .brd) with filled copper zones as input; golden RS-274X Gerbers and SVG plots of F.Cu and B.Cu as answers
|
| 35 |
Origin: KiCad artwork-generation regression fixture (tool_fixture)
|
|
|
|
|
|
|
| 36 |
Check: Final file state, two judges. Gerber: kicad-cli gerber diff --format json --no-align between the agent's Gerber and the golden; total_diff_percent must be at most 0.5 (utils.py lines 253-276, test_pcb.py lines 177-183). SVG: this one can only be judged as a picture: render both SVGs to PNG at 850 DPI with cairosvg and compare the images with utils.images_are_equal, which passes when the pixel difference vanishes after a 1-pixel erosion (utils.py lines 157-189 and 238-248, test_pcb.py lines 116-117: 1 px is 30 um, so about 90 um of allowed error)
|
| 37 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd, and kicad-cli pcb export svg --page-size-mode 1 --exclude-drawing-sheet --black-and-white --layers F.Cu|B.Cu -o DIR/ ZoneFill-Legacy.brd; the judge uses kicad-cli gerber diff --format json --no-align
|
| 38 |
Companions (not included): qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-F_Cu.gbr and ZoneFill-Legacy-B_Cu.gbr (golden Gerbers; the answer, hide); qa/data/cli/artwork_generation_regressions/ZoneFill-Legacy-F_Cu.svg and ZoneFill-Legacy-B_Cu.svg (golden SVG plots; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_svg and test_pcb_export_gerber); qa/tests/cli/utils.py (svgs_are_equivalent, images_are_equal, gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 40 |
- `qa/data/cli/artwork_generation_regressions/Issue24143.kicad_pcb`: KiCad board with a degenerate polygon spike: plot F.Cu to Gerber with zero area difference from the golden.
|
| 41 |
Format: KiCad 10 board (.kicad_pcb) as input; golden RS-274X Gerber as answer
|
| 42 |
Origin: KiCad regression fixture for issue 24143 (tool_fixture)
|
|
|
|
|
|
|
| 43 |
Check: Final file state: kicad-cli gerber diff --format json --no-align between the agent's F.Cu Gerber and the golden; total_diff_percent must be 0.0 (utils.py lines 253-276). No screenshot
|
| 44 |
Tools: kicad-cli pcb export gerbers --no-x2 --use-drill-file-origin --layers F.Cu -o DIR/ Issue24143.kicad_pcb; judged with kicad-cli gerber diff --format json --no-align
|
| 45 |
Companions (not included): qa/data/cli/artwork_generation_regressions/Issue24143-F_Cu.gbr (golden Gerber; the answer, hide); qa/tests/cli/test_pcb.py (test_pcb_export_gerber); qa/tests/cli/utils.py (gerbers_are_equivalent); qa/tests/cli/conftest.py; LICENSE.README
|
campaign_files/2026-10-gt-browser-tests-2/kicad-cli-qa-sch/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: golden_output_files. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** kicad-cli sch export netlist --format cadstar|orcadpcb2|pads|allegro -o OUT basic_test.kicad_sch, and kicad-cli sch erc --format report|json [--units in] -o OUT basic_test.kicad_sch (headless KiCad command line); kicad-cli sch export bom [--variant "Variant 1"|Variant2] --exclude-dnp --fields Reference,Value --labels Refs,Value [--include-byte-order-mark | --format-preset "UTF-8 BOM"] -o OUT.csv variants.kicad_sch
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `qa/data/cli/basic_test/basic_test.kicad_sch`: KiCad schematic basic_test: export netlists in four third-party formats and run ERC to a report.
|
| 22 |
Format: KiCad 10 schematic (.kicad_sch S-expression) plus project file as input; golden netlists (CADSTAR, OrCAD PCB2, PADS, Allegro) and ERC reports (text and JSON) as answers
|
| 23 |
Origin: KiCad command-line test fixture written by the KiCad developers (tool_fixture)
|
| 24 |
-
Reference result: golden_output_files
|
| 25 |
-
Reference source: qa/data/cli/basic_test/basic_test.netlist.{cadstar,orcadpcb2,pads,allegro} (test_sch.py lines 126-133) and basic_test.erc.rpt, .erc.json, .erc.unitsin.rpt (test_sch.py lines 320-324); the kicadsexpr and kicadxml netlists are not compared upstream (skip_compare True, lines 127-129) and are left out
|
| 26 |
Check: Final file state: run the agent's netlist or ERC command (or take its output files) and compare each with the golden by utils.textdiff_files after dropping the first N header lines (dates and tool version); the ERC compare also drops lines matching ^\s*"kicad_version": (test_sch.py lines 350-351); the ERC exit code must be 0 (expected_exit_code column, lines 321-324). Text diff, no screenshot
|
| 27 |
Tools: kicad-cli sch export netlist --format cadstar|orcadpcb2|pads|allegro -o OUT basic_test.kicad_sch, and kicad-cli sch erc --format report|json [--units in] -o OUT basic_test.kicad_sch (headless KiCad command line)
|
| 28 |
Companions (not included): qa/data/cli/basic_test/basic_test.kicad_pro (project file the schematic loads with; ERC settings); qa/data/cli/basic_test/basic_test.netlist.cadstar, .netlist.orcadpcb2, .netlist.pads, .netlist.allegro (golden netlists; the answer, hide from the agent); qa/data/cli/basic_test/basic_test.erc.rpt, .erc.json, .erc.unitsin.rpt (golden ERC reports; the answer, hide); qa/tests/cli/test_sch.py (test_sch_export_netlist and test_sch_export_erc: cli arguments and skip counts); qa/tests/cli/utils.py (textdiff_files); qa/tests/cli/conftest.py (pytest fixture that locates data files); LICENSE.README (licence)
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `qa/data/cli/variants/variants.kicad_sch`: KiCad schematic with design variants: export a DNP-filtered BOM per variant, with and without a UTF-8 byte order mark.
|
| 31 |
Format: KiCad 10 hierarchical schematic with design variants (.kicad_sch, .kicad_pro, .kicad_sym) as input; golden CSV BOMs as answers
|
| 32 |
Origin: KiCad command-line test fixture (tool_fixture)
|
| 33 |
-
Reference result: golden_output_files
|
| 34 |
-
Reference source: qa/data/cli/variants/variants_default.bom.csv, variants_v1.bom.csv, variants_v2.bom.csv (test_sch.py lines 191-201: five cases, the last two reuse the default golden with a byte order mark)
|
| 35 |
Check: Final file state: compare the agent's CSV with the golden by utils.textdiff_files with 0 skipped lines; for the two byte-order-mark cases the output bytes must equal b"\xef\xbb\xbf" plus the golden bytes exactly (test_sch.py lines 227-231). No screenshot
|
| 36 |
Tools: kicad-cli sch export bom [--variant "Variant 1"|Variant2] --exclude-dnp --fields Reference,Value --labels Refs,Value [--include-byte-order-mark | --format-preset "UTF-8 BOM"] -o OUT.csv variants.kicad_sch
|
| 37 |
Companions (not included): qa/data/cli/variants/variants.kicad_pro (project file; defines the variants); qa/data/cli/variants/pic_sockets.kicad_sch (sub-sheet); qa/data/cli/variants/pic_programmer.kicad_sym and sym-lib-table (symbol library the sheets use); qa/data/cli/variants/variants_default.bom.csv, variants_v1.bom.csv, variants_v2.bom.csv (golden BOMs; the answer, hide); qa/tests/cli/test_sch.py (test_sch_export_bom_variants); qa/tests/cli/utils.py; qa/tests/cli/conftest.py; LICENSE.README
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** kicad-cli sch export netlist --format cadstar|orcadpcb2|pads|allegro -o OUT basic_test.kicad_sch, and kicad-cli sch erc --format report|json [--units in] -o OUT basic_test.kicad_sch (headless KiCad command line); kicad-cli sch export bom [--variant "Variant 1"|Variant2] --exclude-dnp --fields Reference,Value --labels Refs,Value [--include-byte-order-mark | --format-preset "UTF-8 BOM"] -o OUT.csv variants.kicad_sch
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-or-later AND GPL-2.0-or-later
|
|
|
|
| 19 |
- `qa/data/cli/basic_test/basic_test.kicad_sch`: KiCad schematic basic_test: export netlists in four third-party formats and run ERC to a report.
|
| 20 |
Format: KiCad 10 schematic (.kicad_sch S-expression) plus project file as input; golden netlists (CADSTAR, OrCAD PCB2, PADS, Allegro) and ERC reports (text and JSON) as answers
|
| 21 |
Origin: KiCad command-line test fixture written by the KiCad developers (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: run the agent's netlist or ERC command (or take its output files) and compare each with the golden by utils.textdiff_files after dropping the first N header lines (dates and tool version); the ERC compare also drops lines matching ^\s*"kicad_version": (test_sch.py lines 350-351); the ERC exit code must be 0 (expected_exit_code column, lines 321-324). Text diff, no screenshot
|
| 23 |
Tools: kicad-cli sch export netlist --format cadstar|orcadpcb2|pads|allegro -o OUT basic_test.kicad_sch, and kicad-cli sch erc --format report|json [--units in] -o OUT basic_test.kicad_sch (headless KiCad command line)
|
| 24 |
Companions (not included): qa/data/cli/basic_test/basic_test.kicad_pro (project file the schematic loads with; ERC settings); qa/data/cli/basic_test/basic_test.netlist.cadstar, .netlist.orcadpcb2, .netlist.pads, .netlist.allegro (golden netlists; the answer, hide from the agent); qa/data/cli/basic_test/basic_test.erc.rpt, .erc.json, .erc.unitsin.rpt (golden ERC reports; the answer, hide); qa/tests/cli/test_sch.py (test_sch_export_netlist and test_sch_export_erc: cli arguments and skip counts); qa/tests/cli/utils.py (textdiff_files); qa/tests/cli/conftest.py (pytest fixture that locates data files); LICENSE.README (licence)
|
|
|
|
| 26 |
- `qa/data/cli/variants/variants.kicad_sch`: KiCad schematic with design variants: export a DNP-filtered BOM per variant, with and without a UTF-8 byte order mark.
|
| 27 |
Format: KiCad 10 hierarchical schematic with design variants (.kicad_sch, .kicad_pro, .kicad_sym) as input; golden CSV BOMs as answers
|
| 28 |
Origin: KiCad command-line test fixture (tool_fixture)
|
|
|
|
|
|
|
| 29 |
Check: Final file state: compare the agent's CSV with the golden by utils.textdiff_files with 0 skipped lines; for the two byte-order-mark cases the output bytes must equal b"\xef\xbb\xbf" plus the golden bytes exactly (test_sch.py lines 227-231). No screenshot
|
| 30 |
Tools: kicad-cli sch export bom [--variant "Variant 1"|Variant2] --exclude-dnp --fields Reference,Value --labels Refs,Value [--include-byte-order-mark | --format-preset "UTF-8 BOM"] -o OUT.csv variants.kicad_sch
|
| 31 |
Companions (not included): qa/data/cli/variants/variants.kicad_pro (project file; defines the variants); qa/data/cli/variants/pic_sockets.kicad_sch (sub-sheet); qa/data/cli/variants/pic_programmer.kicad_sym and sym-lib-table (symbol library the sheets use); qa/data/cli/variants/variants_default.bom.csv, variants_v1.bom.csv, variants_v2.bom.csv (golden BOMs; the answer, hide); qa/tests/cli/test_sch.py (test_sch_export_bom_variants); qa/tests/cli/utils.py; qa/tests/cli/conftest.py; LICENSE.README
|
campaign_files/2026-10-gt-browser-tests-2/laminas-mail-mbox-inbox/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** PHP laminas-mail Storage\Mbox, Python mailbox.mbox or formail; a script counts the messages of the mbox and writes each message's subject and first body line to a file
|
| 14 |
|
| 15 |
**Licence (SPDX):** BSD-3-Clause
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `test/_files/test.mbox/INBOX`: Count the messages of an mbox folder and read a subject and a body line.
|
| 22 |
Format: mbox file (7 messages); expected values in a PHPUnit file
|
| 23 |
Origin: laminas-mail mbox storage fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: test/Storage/MboxTest.php: line 150 the mbox holds 7 messages; line 175 the subject of message 1 is 'Simple Message'; line 213 the first body line of message 3 is 'Fair river! in thy bright, clear flow'
|
| 26 |
Check: Final file state: the agent writes the message count, the subject of message 1 and the trimmed first body line of message 3 to a file; all three must equal the expected values exactly. Byte sizes per message are left out because they depend on the reader. No screenshot
|
| 27 |
Tools: PHP laminas-mail Storage\Mbox, Python mailbox.mbox or formail; a script counts the messages of the mbox and writes each message's subject and first body line to a file
|
| 28 |
Companions (not included): test/Storage/MboxTest.php
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** PHP laminas-mail Storage\Mbox, Python mailbox.mbox or formail; a script counts the messages of the mbox and writes each message's subject and first body line to a file
|
| 12 |
|
| 13 |
**Licence (SPDX):** BSD-3-Clause
|
|
|
|
| 19 |
- `test/_files/test.mbox/INBOX`: Count the messages of an mbox folder and read a subject and a body line.
|
| 20 |
Format: mbox file (7 messages); expected values in a PHPUnit file
|
| 21 |
Origin: laminas-mail mbox storage fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: the agent writes the message count, the subject of message 1 and the trimmed first body line of message 3 to a file; all three must equal the expected values exactly. Byte sizes per message are left out because they depend on the reader. No screenshot
|
| 23 |
Tools: PHP laminas-mail Storage\Mbox, Python mailbox.mbox or formail; a script counts the messages of the mbox and writes each message's subject and first body line to a file
|
| 24 |
Companions (not included): test/Storage/MboxTest.php
|
campaign_files/2026-10-m-issue-trackers-2/king-county-metro-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-KingCounty-Transit-Data-Terms
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://metro.kingcounty.gov/GTFS/google_transit.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 24 |
Origin: Live static GTFS feed published by King County Metro Transit at https://metro.kingcounty.gov/GTFS/google_transit.zip. The licence allows redistribution, so calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member) and kept as a snapshot pinned by sha256; the full zip was not downloaded.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-KingCounty-Transit-Data-Terms
|
|
|
|
| 20 |
Read out of the archive: https://metro.kingcounty.gov/GTFS/google_transit.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 22 |
Origin: Live static GTFS feed published by King County Metro Transit at https://metro.kingcounty.gov/GTFS/google_transit.zip. The licence allows redistribution, so calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member) and kept as a snapshot pinned by sha256; the full zip was not downloaded.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
campaign_files/2026-10-m-issue-trackers-2/konectbus-passenger-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/konectbus/gtfs/konectbus_1782738102.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by konectbus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/konectbus/gtfs/konectbus_1782738102.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 20 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/konectbus/gtfs/konectbus_1782738102.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by konectbus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/konectbus/gtfs/konectbus_1782738102.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt
|
campaign_files/2026-10-m-issue-trackers-2/ku-lawrence-transit-combined-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://assets.lawrenceks.org/transit/KU-LTS_GTFS.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 24 |
Origin: Live static GTFS feed published by City of Lawrence, Kansas (Lawrence Transit with KU on Wheels) at https://assets.lawrenceks.org/transit/KU-LTS_GTFS.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 20 |
Read out of the archive: https://assets.lawrenceks.org/transit/KU-LTS_GTFS.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 22 |
Origin: Live static GTFS feed published by City of Lawrence, Kansas (Lawrence Transit with KU on Wheels) at https://assets.lawrenceks.org/transit/KU-LTS_GTFS.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
campaign_files/2026-10-m-issue-trackers-2/la-metro-bus-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://gitlab.com/LACMTA/gtfs_bus/-/raw/master/gtfs_bus.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 24 |
Origin: Live static GTFS feed published by Los Angeles County Metropolitan Transportation Authority (LA Metro) at https://gitlab.com/LACMTA/gtfs_bus/-/raw/master/gtfs_bus.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 20 |
Read out of the archive: https://gitlab.com/LACMTA/gtfs_bus/-/raw/master/gtfs_bus.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 22 |
Origin: Live static GTFS feed published by Los Angeles County Metropolitan Transportation Authority (LA Metro) at https://gitlab.com/LACMTA/gtfs_bus/-/raw/master/gtfs_bus.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
campaign_files/2026-10-md-media-and-documents/komascript-uni-titlepage-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX log (.tlg). Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check ordinals (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/ordinals.lvt`: Uni-titlepage l3build test ordinals: German title page (style UKoLa) whose referee list mixes male and female ordinal names, checked through the log.
|
| 22 |
Format: LaTeX test file (.lvt) plus expected log (.tlg)
|
| 23 |
Origin: regression test of the package author; the .tlg is the accepted normalised log
|
| 24 |
-
Reference result: expected normalised TeX log (.tlg)
|
| 25 |
-
Reference source: testfiles/ordinals.tlg, saved by the author from checked runs (one file for all engines)
|
| 26 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 27 |
Tools: l3build check ordinals (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 28 |
Companions (not included): testfiles/ordinals.tlg; build.lua; LICENSE.md
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check ordinals (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `testfiles/ordinals.lvt`: Uni-titlepage l3build test ordinals: German title page (style UKoLa) whose referee list mixes male and female ordinal names, checked through the log.
|
| 20 |
Format: LaTeX test file (.lvt) plus expected log (.tlg)
|
| 21 |
Origin: regression test of the package author; the .tlg is the accepted normalised log
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 23 |
Tools: l3build check ordinals (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 24 |
Companions (not included): testfiles/ordinals.tlg; build.lua; LICENSE.md
|
campaign_files/2026-10-md-media-and-documents/kozea-weasyprint-tests-draw/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected raster per test as a character grid mapped to RGB values. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** weasyprint input.html out.pdf (command line), then gs -sDEVICE=png16m to rasterise; in the source tree pytest tests/draw/test_column.py does both
|
| 14 |
|
| 15 |
**Licence (SPDX):** BSD-3-Clause
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/draw/test_column.py`: WeasyPrint draw tests test_column.py: CSS column rules rendered to pixels, expected pixels written as character grids.
|
| 22 |
Format: Python pytest file holding HTML and expected pixel grids
|
| 23 |
Origin: drawing tests of WeasyPrint (HTML/CSS to PDF), written by its developers; each test gives HTML and the expected tiny raster as a character grid
|
| 24 |
-
Reference result: expected raster per test as a character grid mapped to RGB values
|
| 25 |
-
Reference source: the first argument of each assert_pixels call in test_column.py, with the character to colour table in tests/draw/__init__.py
|
| 26 |
Check: render each HTML snippet to PDF with WeasyPrint, rasterise with Ghostscript at 96 dpi (zoom 4/30), and compare every pixel with the grid exactly (tolerance 0); hide the grids when posing the task
|
| 27 |
Tools: weasyprint input.html out.pdf (command line), then gs -sDEVICE=png16m to rasterise; in the source tree pytest tests/draw/test_column.py does both
|
| 28 |
Companions (not included): tests/draw/__init__.py; tests/resources/blue.jpg; tests/testing_utils.py
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** weasyprint input.html out.pdf (command line), then gs -sDEVICE=png16m to rasterise; in the source tree pytest tests/draw/test_column.py does both
|
| 12 |
|
| 13 |
**Licence (SPDX):** BSD-3-Clause
|
|
|
|
| 19 |
- `tests/draw/test_column.py`: WeasyPrint draw tests test_column.py: CSS column rules rendered to pixels, expected pixels written as character grids.
|
| 20 |
Format: Python pytest file holding HTML and expected pixel grids
|
| 21 |
Origin: drawing tests of WeasyPrint (HTML/CSS to PDF), written by its developers; each test gives HTML and the expected tiny raster as a character grid
|
|
|
|
|
|
|
| 22 |
Check: render each HTML snippet to PDF with WeasyPrint, rasterise with Ghostscript at 96 dpi (zoom 4/30), and compare every pixel with the grid exactly (tolerance 0); hide the grids when posing the task
|
| 23 |
Tools: weasyprint input.html out.pdf (command line), then gs -sDEVICE=png16m to rasterise; in the source tree pytest tests/draw/test_column.py does both
|
| 24 |
Companions (not included): tests/draw/__init__.py; tests/resources/blue.jpg; tests/testing_utils.py
|
campaign_files/2026-10-md-media-and-documents/kramdown-asciidoc-scenario-table-alignment/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected AsciiDoc for a Markdown document with aligned tables. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** kramdoc command line (kramdoc -o alignment.adoc alignment.md) or the Ruby API Kramdown::Document.new(input, Kramdown::AsciiDoc::DEFAULT_PARSER_OPTS).to_asciidoc
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `spec/scenarios/table/alignment.md`: Kramdown-asciidoc scenario "table/alignment": Markdown tables with column alignment converted to AsciiDoc tables.
|
| 22 |
Format: scenario pair: alignment.md (input) and alignment.adoc (expected output); no .opts file exists for this scenario, so only the default parser options apply
|
| 23 |
Origin: scenario written by the Asciidoctor project for kramdown-asciidoc (kramdoc), the Markdown to AsciiDoc converter
|
| 24 |
-
Reference result: expected AsciiDoc for a Markdown document with aligned tables
|
| 25 |
-
Reference source: alignment.adoc
|
| 26 |
Check: show the agent alignment.md (hide alignment.adoc); read the input with universal newlines; read alignment.adoc with universal newlines and remove one trailing newline (chomp); pass when the agent's AsciiDoc equals that string exactly (eql)
|
| 27 |
Tools: kramdoc command line (kramdoc -o alignment.adoc alignment.md) or the Ruby API Kramdown::Document.new(input, Kramdown::AsciiDoc::DEFAULT_PARSER_OPTS).to_asciidoc
|
| 28 |
Companions (not included): spec/scenarios/table/alignment.adoc; spec/scenario_spec.rb; spec/spec_helper.rb
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** kramdoc command line (kramdoc -o alignment.adoc alignment.md) or the Ruby API Kramdown::Document.new(input, Kramdown::AsciiDoc::DEFAULT_PARSER_OPTS).to_asciidoc
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `spec/scenarios/table/alignment.md`: Kramdown-asciidoc scenario "table/alignment": Markdown tables with column alignment converted to AsciiDoc tables.
|
| 20 |
Format: scenario pair: alignment.md (input) and alignment.adoc (expected output); no .opts file exists for this scenario, so only the default parser options apply
|
| 21 |
Origin: scenario written by the Asciidoctor project for kramdown-asciidoc (kramdoc), the Markdown to AsciiDoc converter
|
|
|
|
|
|
|
| 22 |
Check: show the agent alignment.md (hide alignment.adoc); read the input with universal newlines; read alignment.adoc with universal newlines and remove one trailing newline (chomp); pass when the agent's AsciiDoc equals that string exactly (eql)
|
| 23 |
Tools: kramdoc command line (kramdoc -o alignment.adoc alignment.md) or the Ruby API Kramdown::Document.new(input, Kramdown::AsciiDoc::DEFAULT_PARSER_OPTS).to_asciidoc
|
| 24 |
Companions (not included): spec/scenarios/table/alignment.adoc; spec/scenario_spec.rb; spec/spec_helper.rb
|
campaign_files/2026-10-md-media-and-documents/latex-package-repositories-oberdiek-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX log with box dumps (.tlg), one per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -e pdftex setouterhbox-test2 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/setouterhbox-test2.lvt`: Oberdiek setouterhbox l3build test 2: box contents set in an outer hbox, checked by box dumps on pdfTeX, XeTeX and LuaTeX.
|
| 22 |
Format: LaTeX test file (.lvt) plus expected logs (.tlg)
|
| 23 |
Origin: regression test of the LaTeX Project maintainers; the .tlg files are the accepted normalised logs (box dumps from \showoutput) for each engine
|
| 24 |
-
Reference result: expected normalised TeX log with box dumps (.tlg), one per engine
|
| 25 |
-
Reference source: testfiles/setouterhbox-test2.tlg, .luatex.tlg and .xetex.tlg, saved by the maintainers from checked runs
|
| 26 |
Check: unpack setouterhbox.sty from setouterhbox.dtx, run the .lvt with l3build on each engine and configuration and compare the normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 27 |
Tools: l3build check -e pdftex setouterhbox-test2 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 28 |
Companions (not included): build.lua; testfiles/setouterhbox-test2.tlg; testfiles/setouterhbox-test2.luatex.tlg; testfiles/setouterhbox-test2.xetex.tlg; setouterhbox.dtx; oberdiek.ins; LICENSE.md
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -e pdftex setouterhbox-test2 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `testfiles/setouterhbox-test2.lvt`: Oberdiek setouterhbox l3build test 2: box contents set in an outer hbox, checked by box dumps on pdfTeX, XeTeX and LuaTeX.
|
| 20 |
Format: LaTeX test file (.lvt) plus expected logs (.tlg)
|
| 21 |
Origin: regression test of the LaTeX Project maintainers; the .tlg files are the accepted normalised logs (box dumps from \showoutput) for each engine
|
|
|
|
|
|
|
| 22 |
Check: unpack setouterhbox.sty from setouterhbox.dtx, run the .lvt with l3build on each engine and configuration and compare the normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 23 |
Tools: l3build check -e pdftex setouterhbox-test2 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 24 |
Companions (not included): build.lua; testfiles/setouterhbox-test2.tlg; testfiles/setouterhbox-test2.luatex.tlg; testfiles/setouterhbox-test2.xetex.tlg; setouterhbox.dtx; oberdiek.ins; LICENSE.md
|
campaign_files/2026-10-md-media-and-documents/latex3-fontspec-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected font selection and feature log (\CURRNFSS) per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check aff-numbers (xelatex and lualatex runs headless; fontspec needs a Unicode engine)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/aff-numbers.lvt`: Fontspec test aff-numbers: switching OpenType number features on TeX Gyre Adventor, with reference logs for XeTeX and LuaTeX.
|
| 22 |
Format: LaTeX source (.lvt, 14 lines) plus expected logs (.tlg, .luatex.tlg) and the suite setup files (fontspec-testsetup.tex, luaotfload.conf, regression-test.cfg)
|
| 23 |
Origin: l3build regression test of fontspec OpenType number features (proportional, old-style, monospaced, lining) written by the fontspec maintainers
|
| 24 |
-
Reference result: expected font selection and feature log (\CURRNFSS) per engine
|
| 25 |
-
Reference source: testfiles/aff-numbers.tlg and aff-numbers.luatex.tlg: the font shape and feature string reported by \CURRNFSS after each \fontspec / \addfontfeatures call
|
| 26 |
Check: hide the .tlg files; the agent writes the fontspec calls or predicts the selected font features; run l3build check aff-numbers per engine; pass when the normalised log equals the .tlg
|
| 27 |
Tools: l3build check aff-numbers (xelatex and lualatex runs headless; fontspec needs a Unicode engine)
|
| 28 |
Companions (not included): testfiles/aff-numbers.tlg; testfiles/aff-numbers.luatex.tlg; testfiles/support/fontspec-testsetup.tex; testfiles/support/luaotfload.conf; testfiles/support/regression-test.cfg
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check aff-numbers (xelatex and lualatex runs headless; fontspec needs a Unicode engine)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles/aff-numbers.lvt`: Fontspec test aff-numbers: switching OpenType number features on TeX Gyre Adventor, with reference logs for XeTeX and LuaTeX.
|
| 20 |
Format: LaTeX source (.lvt, 14 lines) plus expected logs (.tlg, .luatex.tlg) and the suite setup files (fontspec-testsetup.tex, luaotfload.conf, regression-test.cfg)
|
| 21 |
Origin: l3build regression test of fontspec OpenType number features (proportional, old-style, monospaced, lining) written by the fontspec maintainers
|
|
|
|
|
|
|
| 22 |
Check: hide the .tlg files; the agent writes the fontspec calls or predicts the selected font features; run l3build check aff-numbers per engine; pass when the normalised log equals the .tlg
|
| 23 |
Tools: l3build check aff-numbers (xelatex and lualatex runs headless; fontspec needs a Unicode engine)
|
| 24 |
Companions (not included): testfiles/aff-numbers.tlg; testfiles/aff-numbers.luatex.tlg; testfiles/support/fontspec-testsetup.tex; testfiles/support/luaotfload.conf; testfiles/support/regression-test.cfg
|
campaign_files/2026-10-md-media-and-documents/latex3-graphics-def-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX box log (\showoutput) per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check pdftex001 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/pdftex001.lvt`: Graphics-def l3build test pdftex001: \includegraphics of PDF, JPEG and PNG with page, pagebox, bb, clip and interpolate keys, with expected box logs per engine.
|
| 22 |
Format: LaTeX test (.lvt) plus expected log (.tlg) per engine
|
| 23 |
Origin: regression test written by the LaTeX Project team; the .tlg files are the accepted \showoutput box logs
|
| 24 |
-
Reference result: expected normalised TeX box log (\showoutput) per engine
|
| 25 |
-
Reference source: testfiles/pdftex001.tlg (pdfTeX), .luatex.tlg and .xetex.tlg, written by the maintainers from a checked run
|
| 26 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 27 |
Tools: l3build check pdftex001 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 28 |
Companions (not included): testfiles/pdftex001.tlg; testfiles/pdftex001.luatex.tlg; testfiles/pdftex001.xetex.tlg; build.lua; pdftex.def; luatex.def; xetex.def; testfiles/support/graphics001.tex; testfiles/support/az2.pdf; testfiles/support/example-image-a.pdf; testfiles/support/clip-1-2.jpg; testfiles/support/clip-1-2.png
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check pdftex001 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles/pdftex001.lvt`: Graphics-def l3build test pdftex001: \includegraphics of PDF, JPEG and PNG with page, pagebox, bb, clip and interpolate keys, with expected box logs per engine.
|
| 20 |
Format: LaTeX test (.lvt) plus expected log (.tlg) per engine
|
| 21 |
Origin: regression test written by the LaTeX Project team; the .tlg files are the accepted \showoutput box logs
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 23 |
Tools: l3build check pdftex001 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 24 |
Companions (not included): testfiles/pdftex001.tlg; testfiles/pdftex001.luatex.tlg; testfiles/pdftex001.xetex.tlg; build.lua; pdftex.def; luatex.def; xetex.def; testfiles/support/graphics001.tex; testfiles/support/az2.pdf; testfiles/support/example-image-a.pdf; testfiles/support/clip-1-2.jpg; testfiles/support/clip-1-2.png
|
campaign_files/2026-10-md-media-and-documents/latex3-hyperref-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected \showoutput page box dump per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check gh187-whatsits-break (pdflatex, etex and lualatex runs headless); compare the \showoutput box dump
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/gh187-whatsits-break.lvt`: Hyperref test gh187-whatsits-break: section heading after a color whatsit must not get an extra breakpoint, with reference box dumps.
|
| 22 |
Format: LaTeX source (.lvt, 15 lines) plus three expected logs (.tlg, .etex.tlg, .luatex.tlg)
|
| 23 |
Origin: l3build regression test for hyperref GitHub issue 187 (a color whatsit creating an unwanted page breakpoint after \section), written by the hyperref maintainers
|
| 24 |
-
Reference result: expected \showoutput page box dump per engine
|
| 25 |
-
Reference source: the three .tlg files: the expected page box dump (\showoutput) after the \START line
|
| 26 |
Check: hide the .tlg files; the agent predicts or fixes the layout; run l3build check per engine with a .tlg; pass when the normalised log equals the .tlg; the property under test is that the two section headings stay on the page as in the .tlg (no break introduced by the \color whatsit)
|
| 27 |
Tools: l3build check gh187-whatsits-break (pdflatex, etex and lualatex runs headless); compare the \showoutput box dump
|
| 28 |
Companions (not included): testfiles/gh187-whatsits-break.tlg; testfiles/gh187-whatsits-break.etex.tlg; testfiles/gh187-whatsits-break.luatex.tlg
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check gh187-whatsits-break (pdflatex, etex and lualatex runs headless); compare the \showoutput box dump
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles/gh187-whatsits-break.lvt`: Hyperref test gh187-whatsits-break: section heading after a color whatsit must not get an extra breakpoint, with reference box dumps.
|
| 20 |
Format: LaTeX source (.lvt, 15 lines) plus three expected logs (.tlg, .etex.tlg, .luatex.tlg)
|
| 21 |
Origin: l3build regression test for hyperref GitHub issue 187 (a color whatsit creating an unwanted page breakpoint after \section), written by the hyperref maintainers
|
|
|
|
|
|
|
| 22 |
Check: hide the .tlg files; the agent predicts or fixes the layout; run l3build check per engine with a .tlg; pass when the normalised log equals the .tlg; the property under test is that the two section headings stay on the page as in the .tlg (no break introduced by the \color whatsit)
|
| 23 |
Tools: l3build check gh187-whatsits-break (pdflatex, etex and lualatex runs headless); compare the \showoutput box dump
|
| 24 |
Companions (not included): testfiles/gh187-whatsits-break.tlg; testfiles/gh187-whatsits-break.etex.tlg; testfiles/gh187-whatsits-break.luatex.tlg
|
campaign_files/2026-10-md-media-and-documents/latex3-l3build-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised log. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check 02-OMIT
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/02-OMIT.lvt`: l3build self-test 02-OMIT: \OMIT and \TIMO markers of the test harness.
|
| 22 |
Format: LaTeX source plus expected log
|
| 23 |
Origin: self-test of the l3build harness
|
| 24 |
-
Reference result: expected normalised log
|
| 25 |
-
Reference source: testfiles/02-OMIT.tlg
|
| 26 |
Check: l3build exact diff of normalised log against .tlg
|
| 27 |
Tools: l3build check 02-OMIT
|
| 28 |
Companions (not included): testfiles/02-OMIT.tlg; build.lua
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check 02-OMIT
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `testfiles/02-OMIT.lvt`: l3build self-test 02-OMIT: \OMIT and \TIMO markers of the test harness.
|
| 20 |
Format: LaTeX source plus expected log
|
| 21 |
Origin: self-test of the l3build harness
|
|
|
|
|
|
|
| 22 |
Check: l3build exact diff of normalised log against .tlg
|
| 23 |
Tools: l3build check 02-OMIT
|
| 24 |
Companions (not included): testfiles/02-OMIT.tlg; build.lua
|
campaign_files/2026-10-md-media-and-documents/latex3-latex2e-latex-lab-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised PDF (structure tree, tags, marked content). Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -c config-table-pdftex table-001-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf); l3build check -c config-table-pdftex table-009-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `required/latex-lab/testfiles-table-pdftex/table-001-pdf.pvt`: LaTeX tagged-PDF table test table-001-pdf: structure tree of a simple tabular, with the expected normalised PDF.
|
| 22 |
Format: LaTeX source (.pvt) plus the expected normalised PDF (.tpf, text) and the repository support/regression-test.cfg
|
| 23 |
Origin: l3build PDF-based regression test of the LaTeX tagging project (latex-lab table module): a minimal tabular in a tagged PDF (tagging=on); written by the LaTeX Project
|
| 24 |
-
Reference result: expected normalised PDF (structure tree, tags, marked content)
|
| 25 |
-
Reference source: required/latex-lab/testfiles-table-pdftex/table-001-pdf.tpf: the PDF l3build expects after normalisation (structure elements /Table, /TR, /TH, /TD and their attributes)
|
| 26 |
Check: hide the .tpf; the agent writes the tagged table markup (or predicts the structure tree); run l3build check on the .pvt; l3build normalises the produced PDF (l3build.dtx lines 1370 to 1393) and the check passes when it equals the .tpf
|
| 27 |
Tools: l3build check -c config-table-pdftex table-001-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 28 |
Companions (not included): required/latex-lab/testfiles-table-pdftex/table-001-pdf.tpf; support/regression-test.cfg
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `required/latex-lab/testfiles-table-pdftex/table-009-pdf.pvt`: LaTeX tagged-PDF table test table-009-pdf: header rows and a spanning header cell in the PDF structure tree, with the expected normalised PDF.
|
| 31 |
Format: LaTeX source (.pvt) plus the expected normalised PDF (.tpf, text) and the repository support/regression-test.cfg
|
| 32 |
Origin: l3build PDF-based regression test of the LaTeX tagging project (latex-lab table module): a tabular with header rows set by table/header-rows={1,2,-1} and a spanning \multicolumn header in a tagged PDF; written by the LaTeX Project
|
| 33 |
-
Reference result: expected normalised PDF (structure tree, tags, marked content)
|
| 34 |
-
Reference source: required/latex-lab/testfiles-table-pdftex/table-009-pdf.tpf: the PDF l3build expects after normalisation (structure elements /Table, /TR, /TH, /TD and their attributes)
|
| 35 |
Check: hide the .tpf; the agent writes the tagged table markup (or predicts the structure tree); run l3build check on the .pvt; l3build normalises the produced PDF (l3build.dtx lines 1370 to 1393) and the check passes when it equals the .tpf
|
| 36 |
Tools: l3build check -c config-table-pdftex table-009-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 37 |
Companions (not included): required/latex-lab/testfiles-table-pdftex/table-009-pdf.tpf; support/regression-test.cfg
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -c config-table-pdftex table-001-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf); l3build check -c config-table-pdftex table-009-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `required/latex-lab/testfiles-table-pdftex/table-001-pdf.pvt`: LaTeX tagged-PDF table test table-001-pdf: structure tree of a simple tabular, with the expected normalised PDF.
|
| 20 |
Format: LaTeX source (.pvt) plus the expected normalised PDF (.tpf, text) and the repository support/regression-test.cfg
|
| 21 |
Origin: l3build PDF-based regression test of the LaTeX tagging project (latex-lab table module): a minimal tabular in a tagged PDF (tagging=on); written by the LaTeX Project
|
|
|
|
|
|
|
| 22 |
Check: hide the .tpf; the agent writes the tagged table markup (or predicts the structure tree); run l3build check on the .pvt; l3build normalises the produced PDF (l3build.dtx lines 1370 to 1393) and the check passes when it equals the .tpf
|
| 23 |
Tools: l3build check -c config-table-pdftex table-001-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 24 |
Companions (not included): required/latex-lab/testfiles-table-pdftex/table-001-pdf.tpf; support/regression-test.cfg
|
|
|
|
| 26 |
- `required/latex-lab/testfiles-table-pdftex/table-009-pdf.pvt`: LaTeX tagged-PDF table test table-009-pdf: header rows and a spanning header cell in the PDF structure tree, with the expected normalised PDF.
|
| 27 |
Format: LaTeX source (.pvt) plus the expected normalised PDF (.tpf, text) and the repository support/regression-test.cfg
|
| 28 |
Origin: l3build PDF-based regression test of the LaTeX tagging project (latex-lab table module): a tabular with header rows set by table/header-rows={1,2,-1} and a spanning \multicolumn header in a tagged PDF; written by the LaTeX Project
|
|
|
|
|
|
|
| 29 |
Check: hide the .tpf; the agent writes the tagged table markup (or predicts the structure tree); run l3build check on the .pvt; l3build normalises the produced PDF (l3build.dtx lines 1370 to 1393) and the check passes when it equals the .tpf
|
| 30 |
Tools: l3build check -c config-table-pdftex table-009-pdf in required/latex-lab (pdflatex and lualatex headless; l3build normalises the PDF and compares it with the .tpf)
|
| 31 |
Companions (not included): required/latex-lab/testfiles-table-pdftex/table-009-pdf.tpf; support/regression-test.cfg
|
campaign_files/2026-10-md-media-and-documents/latex3-latex3-l3kernel-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX log (box and coffin dumps) per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -e<engine> m3coffins001 in the l3kernel directory (pdftex, luatex, xetex, ptex, uptex engines); the engine runs headless and writes the .log that l3build normalises
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `l3kernel/testfiles/m3coffins001.lvt`: LaTeX3 kernel coffins test m3coffins001: build, join, rotate and typeset coffins, with reference logs for five TeX engines.
|
| 22 |
Format: TeX source (.lvt, 395 lines, 12 \TEST blocks) plus five expected logs (.tlg for pdftex and engine-specific .luatex/.ptex/.uptex/.xetex.tlg) and the repository regression-test.cfg
|
| 23 |
Origin: l3build regression test of the LaTeX3 kernel (expl3) coffin layout boxes, written by the LaTeX Project for its own test suite
|
| 24 |
-
Reference result: expected normalised TeX log (box and coffin dumps) per engine
|
| 25 |
-
Reference source: l3kernel/testfiles/m3coffins001.tlg (pdftex) and the engine-specific .tlg files: the expected log l3build produces from the .lvt
|
| 26 |
Check: hide the .tlg files; the agent writes or edits the .lvt (or predicts the log); run l3build check for each engine with a .tlg (l3build picks <name>.<engine>.tlg when present, else <name>.tlg, l3build.dtx lines 592 to 595); pass when the normalised log equals the .tlg (l3build normalises line numbers, dates, register numbers and drops text outside \START/\END and inside \OMIT/\TIMO, l3build.dtx lines 876 to 926)
|
| 27 |
Tools: l3build check -e<engine> m3coffins001 in the l3kernel directory (pdftex, luatex, xetex, ptex, uptex engines); the engine runs headless and writes the .log that l3build normalises
|
| 28 |
Companions (not included): l3kernel/testfiles/m3coffins001.tlg; l3kernel/testfiles/m3coffins001.luatex.tlg; l3kernel/testfiles/m3coffins001.ptex.tlg; l3kernel/testfiles/m3coffins001.uptex.tlg; l3kernel/testfiles/m3coffins001.xetex.tlg; support/regression-test.cfg
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -e<engine> m3coffins001 in the l3kernel directory (pdftex, luatex, xetex, ptex, uptex engines); the engine runs headless and writes the .log that l3build normalises
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `l3kernel/testfiles/m3coffins001.lvt`: LaTeX3 kernel coffins test m3coffins001: build, join, rotate and typeset coffins, with reference logs for five TeX engines.
|
| 20 |
Format: TeX source (.lvt, 395 lines, 12 \TEST blocks) plus five expected logs (.tlg for pdftex and engine-specific .luatex/.ptex/.uptex/.xetex.tlg) and the repository regression-test.cfg
|
| 21 |
Origin: l3build regression test of the LaTeX3 kernel (expl3) coffin layout boxes, written by the LaTeX Project for its own test suite
|
|
|
|
|
|
|
| 22 |
Check: hide the .tlg files; the agent writes or edits the .lvt (or predicts the log); run l3build check for each engine with a .tlg (l3build picks <name>.<engine>.tlg when present, else <name>.tlg, l3build.dtx lines 592 to 595); pass when the normalised log equals the .tlg (l3build normalises line numbers, dates, register numbers and drops text outside \START/\END and inside \OMIT/\TIMO, l3build.dtx lines 876 to 926)
|
| 23 |
Tools: l3build check -e<engine> m3coffins001 in the l3kernel directory (pdftex, luatex, xetex, ptex, uptex engines); the engine runs headless and writes the .log that l3build normalises
|
| 24 |
Companions (not included): l3kernel/testfiles/m3coffins001.tlg; l3kernel/testfiles/m3coffins001.luatex.tlg; l3kernel/testfiles/m3coffins001.ptex.tlg; l3kernel/testfiles/m3coffins001.uptex.tlg; l3kernel/testfiles/m3coffins001.xetex.tlg; support/regression-test.cfg
|
campaign_files/2026-10-md-media-and-documents/latex3-luamml-testfiles-lua/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected MathML (XML), compared after tidy. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -c config-lua test_sqrt-xml (headless LuaLaTeX run; MathML output tidied and diffed against the .mlr)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles-lua/test_sqrt-xml.mlt`: Luamml l3build test test_sqrt-xml: LuaLaTeX math with square roots and nth roots converted to MathML, with expected MathML.
|
| 22 |
Format: LaTeX test (.mlt) plus expected MathML (.mlr)
|
| 23 |
Origin: regression test written by the luamml authors; the .mlr file is the accepted MathML
|
| 24 |
-
Reference result: expected MathML (XML), compared after tidy
|
| 25 |
-
Reference source: testfiles-lua/test_sqrt-xml.mlr, written by the authors from a checked run
|
| 26 |
Check: run the .mlt with l3build config-lua on LuaTeX (three runs), tidy the generated .mml and compare it with the .mlr line by line; hide the .mlr when posing the task
|
| 27 |
Tools: l3build check -c config-lua test_sqrt-xml (headless LuaLaTeX run; MathML output tidied and diffed against the .mlr)
|
| 28 |
Companions (not included): testfiles-lua/test_sqrt-xml.mlr; build.lua; config-lua.lua
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -c config-lua test_sqrt-xml (headless LuaLaTeX run; MathML output tidied and diffed against the .mlr)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles-lua/test_sqrt-xml.mlt`: Luamml l3build test test_sqrt-xml: LuaLaTeX math with square roots and nth roots converted to MathML, with expected MathML.
|
| 20 |
Format: LaTeX test (.mlt) plus expected MathML (.mlr)
|
| 21 |
Origin: regression test written by the luamml authors; the .mlr file is the accepted MathML
|
|
|
|
|
|
|
| 22 |
Check: run the .mlt with l3build config-lua on LuaTeX (three runs), tidy the generated .mml and compare it with the .mlr line by line; hide the .mlr when posing the task
|
| 23 |
Tools: l3build check -c config-lua test_sqrt-xml (headless LuaLaTeX run; MathML output tidied and diffed against the .mlr)
|
| 24 |
Companions (not included): testfiles-lua/test_sqrt-xml.mlr; build.lua; config-lua.lua
|
campaign_files/2026-10-md-media-and-documents/latex3-luaotfload-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX box log (\showoutput) for LuaTeX. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -e luatex letterspace1 in the repository root; LuaTeX runs headless and writes the .log that l3build normalises
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-2.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/letterspace1.lvt`: Luaotfload regression test letterspace1: OpenType letter spacing with fontspec and microtype under LuaTeX.
|
| 22 |
Format: LaTeX source (.lvt) plus expected log (.tlg)
|
| 23 |
Origin: l3build regression test of luaotfload, the LuaTeX OpenType font loader, written by its maintainers
|
| 24 |
-
Reference result: expected normalised TeX box log (\showoutput) for LuaTeX
|
| 25 |
-
Reference source: testfiles/letterspace1.tlg, written by the maintainers from a checked run
|
| 26 |
Check: run the .lvt with l3build on LuaTeX and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 27 |
Tools: l3build check -e luatex letterspace1 in the repository root; LuaTeX runs headless and writes the .log that l3build normalises
|
| 28 |
Companions (not included): testfiles/letterspace1.tlg; build.lua
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -e luatex letterspace1 in the repository root; LuaTeX runs headless and writes the .log that l3build normalises
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-2.0-only
|
|
|
|
| 19 |
- `testfiles/letterspace1.lvt`: Luaotfload regression test letterspace1: OpenType letter spacing with fontspec and microtype under LuaTeX.
|
| 20 |
Format: LaTeX source (.lvt) plus expected log (.tlg)
|
| 21 |
Origin: l3build regression test of luaotfload, the LuaTeX OpenType font loader, written by its maintainers
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on LuaTeX and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 23 |
Tools: l3build check -e luatex letterspace1 in the repository root; LuaTeX runs headless and writes the .log that l3build normalises
|
| 24 |
Companions (not included): testfiles/letterspace1.tlg; build.lua
|
campaign_files/2026-10-md-media-and-documents/latex3-unicode-math-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX box log (\SHIPOUT box dump) per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check -e xetex cramped-style (or -e luatex) in the repository root; the engine runs headless and writes the .log that l3build normalises
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/cramped-style.lvt`: Unicode-math regression test cramped-style: cramped text style math under XeTeX and LuaTeX.
|
| 22 |
Format: LaTeX source (.lvt) plus expected log (.tlg)
|
| 23 |
Origin: l3build regression test of the unicode-math package, written by its maintainers for their own test suite
|
| 24 |
-
Reference result: expected normalised TeX box log (\SHIPOUT box dump) per engine
|
| 25 |
-
Reference source: testfiles/cramped-style.tlg (XeTeX) and testfiles/cramped-style.luatex.tlg, written by the maintainers from a run they checked
|
| 26 |
Check: run the .lvt with l3build on the named engine and compare its normalised .log line by line with the .tlg; hide the .tlg files when posing the task
|
| 27 |
Tools: l3build check -e xetex cramped-style (or -e luatex) in the repository root; the engine runs headless and writes the .log that l3build normalises
|
| 28 |
Companions (not included): testfiles/cramped-style.tlg; testfiles/cramped-style.luatex.tlg; build.lua; testfiles/support/umtest-preamble.tex
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check -e xetex cramped-style (or -e luatex) in the repository root; the engine runs headless and writes the .log that l3build normalises
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles/cramped-style.lvt`: Unicode-math regression test cramped-style: cramped text style math under XeTeX and LuaTeX.
|
| 20 |
Format: LaTeX source (.lvt) plus expected log (.tlg)
|
| 21 |
Origin: l3build regression test of the unicode-math package, written by its maintainers for their own test suite
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on the named engine and compare its normalised .log line by line with the .tlg; hide the .tlg files when posing the task
|
| 23 |
Tools: l3build check -e xetex cramped-style (or -e luatex) in the repository root; the engine runs headless and writes the .log that l3build normalises
|
| 24 |
Companions (not included): testfiles/cramped-style.tlg; testfiles/cramped-style.luatex.tlg; build.lua; testfiles/support/umtest-preamble.tex
|
campaign_files/2026-10-md-media-and-documents/latex3-xcolor-testfiles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected normalised TeX box log (\showoutput) per engine. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** l3build check mathcolor-01 (pdftex, xetex, luatex) in the repository root; the engines run headless and write the .log that l3build normalises
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c+
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/mathcolor-01.lvt`: Xcolor regression test mathcolor-01: \mathcolor on math operators and integrals, box log per engine.
|
| 22 |
Format: LaTeX source (.lvt) plus expected logs (.tlg)
|
| 23 |
Origin: l3build regression test of the xcolor package, written by the LaTeX Project
|
| 24 |
-
Reference result: expected normalised TeX box log (\showoutput) per engine
|
| 25 |
-
Reference source: testfiles/mathcolor-01.tlg, .luatex.tlg and .xetex.tlg, written by the maintainers
|
| 26 |
Check: run the .lvt with l3build on each engine and compare its normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 27 |
Tools: l3build check mathcolor-01 (pdftex, xetex, luatex) in the repository root; the engines run headless and write the .log that l3build normalises
|
| 28 |
Companions (not included): testfiles/mathcolor-01.tlg; testfiles/mathcolor-01.luatex.tlg; testfiles/mathcolor-01.xetex.tlg; build.lua
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** l3build check mathcolor-01 (pdftex, xetex, luatex) in the repository root; the engines run headless and write the .log that l3build normalises
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c+
|
|
|
|
| 19 |
- `testfiles/mathcolor-01.lvt`: Xcolor regression test mathcolor-01: \mathcolor on math operators and integrals, box log per engine.
|
| 20 |
Format: LaTeX source (.lvt) plus expected logs (.tlg)
|
| 21 |
Origin: l3build regression test of the xcolor package, written by the LaTeX Project
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on each engine and compare its normalised .log with the matching .tlg line by line; hide the .tlg files when posing the task
|
| 23 |
Tools: l3build check mathcolor-01 (pdftex, xetex, luatex) in the repository root; the engines run headless and write the .log that l3build normalises
|
| 24 |
Companions (not included): testfiles/mathcolor-01.tlg; testfiles/mathcolor-01.luatex.tlg; testfiles/mathcolor-01.xetex.tlg; build.lua
|
campaign_files/2026-10-md-media-and-documents/latexml-t-alignment-halign/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected LaTeXML XML document. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** latexml --dest=halign.xml halign.tex (the LaTeXML command line converter); latexmlpost turns the XML into HTML
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-NIST-PD
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `t/alignment/halign.tex`: LaTeXML test "halign": plain TeX \halign alignments converted to LaTeXML XML.
|
| 22 |
Format: TeX source halign.tex (2479 bytes) with the expected LaTeXML XML halign.xml (16413 bytes)
|
| 23 |
Origin: test written by the LaTeXML developers at NIST for \halign templates, spans and \noalign; the neighbouring tabular.tex was not taken because it reproduces an example from a copyrighted LaTeX manual
|
| 24 |
-
Reference result: expected LaTeXML XML document
|
| 25 |
-
Reference source: t/alignment/halign.xml
|
| 26 |
Check: give the agent halign.tex; hide halign.xml; convert to LaTeXML XML; pass when the serialised XML equals halign.xml line by line after chomp (Test.pm is_strings); no requirement or extra package is declared for this file in t/53_alignment.t
|
| 27 |
Tools: latexml --dest=halign.xml halign.tex (the LaTeXML command line converter); latexmlpost turns the XML into HTML
|
| 28 |
Companions (not included): t/alignment/halign.xml
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** latexml --dest=halign.xml halign.tex (the LaTeXML command line converter); latexmlpost turns the XML into HTML
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-NIST-PD
|
|
|
|
| 19 |
- `t/alignment/halign.tex`: LaTeXML test "halign": plain TeX \halign alignments converted to LaTeXML XML.
|
| 20 |
Format: TeX source halign.tex (2479 bytes) with the expected LaTeXML XML halign.xml (16413 bytes)
|
| 21 |
Origin: test written by the LaTeXML developers at NIST for \halign templates, spans and \noalign; the neighbouring tabular.tex was not taken because it reproduces an example from a copyrighted LaTeX manual
|
|
|
|
|
|
|
| 22 |
Check: give the agent halign.tex; hide halign.xml; convert to LaTeXML XML; pass when the serialised XML equals halign.xml line by line after chomp (Test.pm is_strings); no requirement or extra package is declared for this file in t/53_alignment.t
|
| 23 |
Tools: latexml --dest=halign.xml halign.tex (the LaTeXML command line converter); latexmlpost turns the XML into HTML
|
| 24 |
Companions (not included): t/alignment/halign.xml
|
campaign_files/2026-10-ml-serving-configs-2/kios-research-leakdb/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_leak_time_series. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Each scenario is one task. Hide its Labels.csv and Leaks/. The agent reads the 32 pressure series and outputs a 0/1 leak label per time step. Score with the repository's scoring function CCWI-WDSA2018/Scoring Function/scoring_algorithm.m (MATLAB, runs in GNU Octave, open source; or the same formulas reimplemented): confusion matrix, F1, true positive rate, true negative rate and the early detection score SED with the parameters below. an exact match of the label sequence is the full score.
|
| 14 |
|
| 15 |
**Licence (SPDX):** EUPL-1.2
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `CCWI-WDSA2018/Benchmarks/Hanoi_CMH/` (110 files): LeakDB Hanoi_CMH Scenarios 3, 5 and 7: each one simulated year of half-hourly pressures at the 32 nodes of the Hanoi water network, with a 0/1 leak label per time step (Scenario-3: leak at node 26, incipient, 2017-03-05 01:00:00 to 2017-06-13 03:30:00, leak at node 19, abrupt, 2017-09-22 14:00:00 to 2017-10-28 10:30:00; Scenario-5: leak at node 21, incipient, 2017-03-15 23:00:00 to 2017-07-17 11:30:00; Scenario-7: leak at node 14, abrupt, 2017-12-22 10:00:00 to 2017-12-29 00:00:00).
|
| 22 |
Format: per scenario 32 CSV files, each 17,520 half-hourly rows for 2017 with columns Timestamp,Value (pressure); Labels.csv has Timestamp,Label with 17,520 rows; each Leaks/Leak_<node>_info.csv gives node, area, diameter, type (abrupt or incipient), start, end and peak time
|
| 23 |
Origin: benchmark scenario simulated with EPANET by the LeakDB authors (README.md: 'artificially created but realistic leakage scenarios'), published as a benchmark.
|
| 24 |
-
Reference result: labelled_leak_time_series
|
| 25 |
-
Reference source: each scenario's Scenario-<n>/Labels.csv, its own 0/1 leak label per half-hour step (Scenario-3: 6527 steps labelled 1, 1 step(s) differ; Scenario-5: 5930 steps labelled 1, 0 step(s) differ; Scenario-7: 316 steps labelled 1, 1 step(s) differ).
|
| 26 |
Check: Each scenario is one task. Hide its Labels.csv and Leaks/. The agent reads the 32 pressure series and outputs a 0/1 leak label per time step. Score with the repository's scoring function CCWI-WDSA2018/Scoring Function/scoring_algorithm.m (MATLAB, runs in GNU Octave, open source; or the same formulas reimplemented): confusion matrix, F1, true positive rate, true negative rate and the early detection score SED with the parameters below. an exact match of the label sequence is the full score
|
| 27 |
Companions (not included): CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Scenario-3_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_19_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_19_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_26_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_26_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Scenario-5_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Leaks/Leak_21_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Leaks/Leak_21_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Scenario-7_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Leaks/Leak_14_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Leaks/Leak_14_info.csv; LICENSE.md; README.md
|
| 28 |
Dependencies: none to read the data (comma-separated text, columns Timestamp,Value).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Each scenario is one task. Hide its Labels.csv and Leaks/. The agent reads the 32 pressure series and outputs a 0/1 leak label per time step. Score with the repository's scoring function CCWI-WDSA2018/Scoring Function/scoring_algorithm.m (MATLAB, runs in GNU Octave, open source; or the same formulas reimplemented): confusion matrix, F1, true positive rate, true negative rate and the early detection score SED with the parameters below. an exact match of the label sequence is the full score.
|
| 12 |
|
| 13 |
**Licence (SPDX):** EUPL-1.2
|
|
|
|
| 19 |
- `CCWI-WDSA2018/Benchmarks/Hanoi_CMH/` (110 files): LeakDB Hanoi_CMH Scenarios 3, 5 and 7: each one simulated year of half-hourly pressures at the 32 nodes of the Hanoi water network, with a 0/1 leak label per time step (Scenario-3: leak at node 26, incipient, 2017-03-05 01:00:00 to 2017-06-13 03:30:00, leak at node 19, abrupt, 2017-09-22 14:00:00 to 2017-10-28 10:30:00; Scenario-5: leak at node 21, incipient, 2017-03-15 23:00:00 to 2017-07-17 11:30:00; Scenario-7: leak at node 14, abrupt, 2017-12-22 10:00:00 to 2017-12-29 00:00:00).
|
| 20 |
Format: per scenario 32 CSV files, each 17,520 half-hourly rows for 2017 with columns Timestamp,Value (pressure); Labels.csv has Timestamp,Label with 17,520 rows; each Leaks/Leak_<node>_info.csv gives node, area, diameter, type (abrupt or incipient), start, end and peak time
|
| 21 |
Origin: benchmark scenario simulated with EPANET by the LeakDB authors (README.md: 'artificially created but realistic leakage scenarios'), published as a benchmark.
|
|
|
|
|
|
|
| 22 |
Check: Each scenario is one task. Hide its Labels.csv and Leaks/. The agent reads the 32 pressure series and outputs a 0/1 leak label per time step. Score with the repository's scoring function CCWI-WDSA2018/Scoring Function/scoring_algorithm.m (MATLAB, runs in GNU Octave, open source; or the same formulas reimplemented): confusion matrix, F1, true positive rate, true negative rate and the early detection score SED with the parameters below. an exact match of the label sequence is the full score
|
| 23 |
Companions (not included): CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Scenario-3_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_19_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_19_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_26_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-3/Leaks/Leak_26_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Scenario-5_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Leaks/Leak_21_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-5/Leaks/Leak_21_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Labels.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Scenario-7_info.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Leaks/Leak_14_demand.csv; CCWI-WDSA2018/Benchmarks/Hanoi_CMH/Scenario-7/Leaks/Leak_14_info.csv; LICENSE.md; README.md
|
| 24 |
Dependencies: none to read the data (comma-separated text, columns Timestamp,Value).
|
campaign_files/2026-10-s-security-detection-2/kics-infrastructure-as-code-query-library/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: finding_lines. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: for the 8 playbooks (positive and negative names hidden) list the file and line of every IMDSv1 finding. Score: exact set match of (file, line) pairs against positive_expected_result.json.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `assets/queries/ansible/aws/instance_uses_metadata_service_IMDSv1/` (11 files): KICS instance_uses_metadata_service_IMDSv1 (Ansible AWS): find the lines in 8 playbooks where an EC2 instance allows IMDSv1.
|
| 22 |
Format: Rego query (query.rego), metadata.json, 5 positive and 3 negative Ansible playbooks under test/, and positive_expected_result.json listing file and line of every expected finding
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: finding_lines
|
| 25 |
-
Reference source: test/positive_expected_result.json (20 entries): positive1.yaml lines 10, 20, 32, 42; positive2.yaml lines 2, 11, 20, 29; positive3.yaml lines 11, 23, 35, 47; positive4.yaml lines 9, 20, 31, 42; positive5.yaml lines 9, 20, 31, 42; negative1 to 3 give none
|
| 26 |
Check: Task: for the 8 playbooks (positive and negative names hidden) list the file and line of every IMDSv1 finding. Score: exact set match of (file, line) pairs against positive_expected_result.json
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: kics at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: for the 8 playbooks (positive and negative names hidden) list the file and line of every IMDSv1 finding. Score: exact set match of (file, line) pairs against positive_expected_result.json.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `assets/queries/ansible/aws/instance_uses_metadata_service_IMDSv1/` (11 files): KICS instance_uses_metadata_service_IMDSv1 (Ansible AWS): find the lines in 8 playbooks where an EC2 instance allows IMDSv1.
|
| 20 |
Format: Rego query (query.rego), metadata.json, 5 positive and 3 negative Ansible playbooks under test/, and positive_expected_result.json listing file and line of every expected finding
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: for the 8 playbooks (positive and negative names hidden) list the file and line of every IMDSv1 finding. Score: exact set match of (file, line) pairs against positive_expected_result.json
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: kics at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kics-query-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_findings_by_file_and_line. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: for each template report the line of the unencrypted table. Score: exact match of (file, line) pairs against positive_expected_result.json; any finding on negative1.yaml is a false positive.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `assets/queries/cloudFormation/aws/dynamodb_table_not_encrypted/` (7 files): KICS DynamoDB Table Not Encrypted: find the CloudFormation tables without server side encryption.
|
| 22 |
Format: query directory: metadata.json, query.rego, 4 CloudFormation YAML templates, positive_expected_result.json
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: expected_findings_by_file_and_line
|
| 25 |
-
Reference source: test/positive_expected_result.json: positive1.yaml line 18, positive2.yaml line 17, positive3.yaml line 8, severity HIGH; negative1.yaml expects no finding
|
| 26 |
Check: Task: for each template report the line of the unencrypted table. Score: exact match of (file, line) pairs against positive_expected_result.json; any finding on negative1.yaml is a false positive
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: KICS engine at this commit (Apache-2.0) and the KICS Rego libraries: needed only to rerun the query; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: for each template report the line of the unencrypted table. Score: exact match of (file, line) pairs against positive_expected_result.json; any finding on negative1.yaml is a false positive.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `assets/queries/cloudFormation/aws/dynamodb_table_not_encrypted/` (7 files): KICS DynamoDB Table Not Encrypted: find the CloudFormation tables without server side encryption.
|
| 20 |
Format: query directory: metadata.json, query.rego, 4 CloudFormation YAML templates, positive_expected_result.json
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: for each template report the line of the unencrypted table. Score: exact match of (file, line) pairs against positive_expected_result.json; any finding on negative1.yaml is a false positive
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: KICS engine at this commit (Apache-2.0) and the KICS Rego libraries: needed only to rerun the query; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kics-query-with-positive-and-negative-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_file_line_pairs. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: with the file names renamed neutrally, list (file, line) of each misconfiguration. Score: exact set equality with the 4 expected pairs and no finding on the 5 negatives.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `assets/queries/k8s/kubelet_read_only_port_is_not_set_to_zero/` (12 files): KICS kubelet_read_only_port_is_not_set_to_zero: find the lines in 9 kubelet configurations that leave the read-only port open.
|
| 22 |
Format: KICS query directory: metadata.json, query.rego, 9 test configurations (YAML and JSON), positive_expected_result.json
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: expected_file_line_pairs
|
| 25 |
-
Reference source: test/positive_expected_result.json: positive1.yaml line 11, positive2.yaml line 11, positive3.yaml line 8, positive4.json line 5; negative1 to negative5 have no finding
|
| 26 |
Check: Task: with the file names renamed neutrally, list (file, line) of each misconfiguration. Score: exact set equality with the 4 expected pairs and no finding on the 5 negatives
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: KICS at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: with the file names renamed neutrally, list (file, line) of each misconfiguration. Score: exact set equality with the 4 expected pairs and no finding on the 5 negatives.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `assets/queries/k8s/kubelet_read_only_port_is_not_set_to_zero/` (12 files): KICS kubelet_read_only_port_is_not_set_to_zero: find the lines in 9 kubelet configurations that leave the read-only port open.
|
| 20 |
Format: KICS query directory: metadata.json, query.rego, 9 test configurations (YAML and JSON), positive_expected_result.json
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: with the file names renamed neutrally, list (file, line) of each misconfiguration. Score: exact set equality with the 4 expected pairs and no finding on the 5 negatives
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: KICS at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kube-linter-checks-with-per-check-yaml-fixtures-and-bats-end-to-end-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: per_resource_verdict. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: given the 4 objects (names replaced by neutral ids), say which ones the host-network check reports. Score: exact match of the reported set against the bats expectations; accuracy over 4.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/checks/host-network.yml`: Kube-linter host-network: decide which of 4 Deployments and DeploymentConfigs share the host network namespace.
|
| 22 |
Format: multi-document Kubernetes YAML fixture (4 objects); the companion bats-tests.sh holds the @test block with the expected report count and messages
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: per_resource_verdict
|
| 25 |
-
Reference source: bats-tests.sh @test "host-network" (line 389): exit status 1, exactly 2 reports, for the Deployment and the DeploymentConfig named app with message "resource shares host's network namespace (via hostNetwork=true)."; the two objects named dont-fire give none
|
| 26 |
Check: Task: given the 4 objects (names replaced by neutral ids), say which ones the host-network check reports. Score: exact match of the reported set against the bats expectations; accuracy over 4
|
| 27 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 28 |
Dependencies: kube-linter and bats at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: given the 4 objects (names replaced by neutral ids), say which ones the host-network check reports. Score: exact match of the reported set against the bats expectations; accuracy over 4.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `tests/checks/host-network.yml`: Kube-linter host-network: decide which of 4 Deployments and DeploymentConfigs share the host network namespace.
|
| 20 |
Format: multi-document Kubernetes YAML fixture (4 objects); the companion bats-tests.sh holds the @test block with the expected report count and messages
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: given the 4 objects (names replaced by neutral ids), say which ones the host-network check reports. Score: exact match of the reported set against the bats expectations; accuracy over 4
|
| 23 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 24 |
Dependencies: kube-linter and bats at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kube-linter-end-to-end-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_reports. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: list the workloads and variables that leak a secret. Score: exact match of the report set (kind, variable, container) and of the report count 2.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/checks/env-var-secret.yml`: Kube-linter env-var-secret: find the workloads that put a secret in a plain environment variable.
|
| 22 |
Format: multi document Kubernetes YAML (1,082 B, 5 workloads); expected reports in a bats test
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: expected_reports
|
| 25 |
-
Reference source: e2etests/bats-tests.sh lines 340 to 355: exit status 1, exactly 2 reports, Deployment: environment variable SECRET_BLAH in container "app" found and the same for the DeploymentConfig; the other 3 workloads must not fire
|
| 26 |
Check: Task: list the workloads and variables that leak a secret. Score: exact match of the report set (kind, variable, container) and of the report count 2
|
| 27 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 28 |
Dependencies: kube-linter at this commit (Apache-2.0), bats and jq: needed only to rerun the e2e test; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: list the workloads and variables that leak a secret. Score: exact match of the report set (kind, variable, container) and of the report count 2.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `tests/checks/env-var-secret.yml`: Kube-linter env-var-secret: find the workloads that put a secret in a plain environment variable.
|
| 20 |
Format: multi document Kubernetes YAML (1,082 B, 5 workloads); expected reports in a bats test
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: list the workloads and variables that leak a secret. Score: exact match of the report set (kind, variable, container) and of the report count 2
|
| 23 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 24 |
Dependencies: kube-linter at this commit (Apache-2.0), bats and jq: needed only to rerun the e2e test; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kubeaudit-auditor-fixtures/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: per_file_finding_set. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: for each manifest list the capability findings (from the closed set of kubeaudit codes, including the overridden variant when an allow label is present). Score: per-file set equality with the expected list; accuracy over 10 files.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `auditors/capabilities/fixtures/` (10 files): Kubeaudit capabilities: list the Linux capability findings for 10 Kubernetes manifests (added capabilities, drop ALL missing, override labels).
|
| 22 |
Format: 10 Kubernetes manifests in YAML (298 to 1,814 B); expected error codes per file in the companion Go test
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: per_file_finding_set
|
| 25 |
-
Reference source: auditors/capabilities/capabilities_test.go lines 19 to 43: expected error list per fixture, e.g. capabilities-nil.yml gives CapabilityOrSecurityContextMissing, capabilities-added-not-dropped.yml gives CapabilityAdded and CapabilityShouldDropAll, capabilities-dropped-all.yml gives none
|
| 26 |
Check: Task: for each manifest list the capability findings (from the closed set of kubeaudit codes, including the overridden variant when an allow label is present). Score: per-file set equality with the expected list; accuracy over 10 files
|
| 27 |
Companions (not included): auditors/capabilities/capabilities_test.go; LICENSE
|
| 28 |
Dependencies: kubeaudit at this commit (MIT): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: for each manifest list the capability findings (from the closed set of kubeaudit codes, including the overridden variant when an allow label is present). Score: per-file set equality with the expected list; accuracy over 10 files.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `auditors/capabilities/fixtures/` (10 files): Kubeaudit capabilities: list the Linux capability findings for 10 Kubernetes manifests (added capabilities, drop ALL missing, override labels).
|
| 20 |
Format: 10 Kubernetes manifests in YAML (298 to 1,814 B); expected error codes per file in the companion Go test
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: for each manifest list the capability findings (from the closed set of kubeaudit codes, including the overridden variant when an allow label is present). Score: per-file set equality with the expected list; accuracy over 10 files
|
| 23 |
Companions (not included): auditors/capabilities/capabilities_test.go; LICENSE
|
| 24 |
Dependencies: kubeaudit at this commit (MIT): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kubelinter-check-fixtures-with-bats-end-to-end-expectations/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: per_resource_verdict. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Task: say which of the 4 objects (names hidden) the check reports. Score: exact set match against the 2 reported objects of bats-tests.sh.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/checks/privilege-escalation-container.yml`: KubeLinter privilege-escalation-container: find which of 4 Deployments and DeploymentConfigs allow privilege escalation.
|
| 22 |
Format: one multi-document Kubernetes YAML (52 lines, 4 objects); expected reports in e2etests/bats-tests.sh
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: per_resource_verdict
|
| 25 |
-
Reference source: e2etests/bats-tests.sh lines 767 to 782: exit status 1, 2 reports: Deployment app1 and DeploymentConfig app2 (messages lines 779 and 780: container "app" has AllowPrivilegeEscalation set to true), count 2 (line 781); the two dont-fire objects give none
|
| 26 |
Check: Task: say which of the 4 objects (names hidden) the check reports. Score: exact set match against the 2 reported objects of bats-tests.sh
|
| 27 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 28 |
Dependencies: kube-linter at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Task: say which of the 4 objects (names hidden) the check reports. Score: exact set match against the 2 reported objects of bats-tests.sh.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `tests/checks/privilege-escalation-container.yml`: KubeLinter privilege-escalation-container: find which of 4 Deployments and DeploymentConfigs allow privilege escalation.
|
| 20 |
Format: one multi-document Kubernetes YAML (52 lines, 4 objects); expected reports in e2etests/bats-tests.sh
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: say which of the 4 objects (names hidden) the check reports. Score: exact set match against the 2 reported objects of bats-tests.sh
|
| 23 |
Companions (not included): e2etests/bats-tests.sh; LICENSE
|
| 24 |
Dependencies: kube-linter at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kubescape-regolibrary/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Each unit is self-contained. 8 of 8 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: per_case_verdict_with_path; per_case_alert_set. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Tools are named in the check written per unit in the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,64 +19,48 @@ Units:
|
|
| 21 |
- `rules/kubelet-strong-cryptography-ciphers/` (14 files): Kubescape kubelet-strong-cryptography-ciphers: decide for 6 kubelet command lines and configs whether the kubelet uses only strong TLS ciphers.
|
| 22 |
Format: Rego rule (raw.rego), rule.metadata.json, and 6 test cases each with input/kubeletcmd.json and expected.json (empty list = pass)
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: per_case_verdict_with_path
|
| 25 |
-
Reference source: test/<case>/expected.json: non-empty for fail-cli-and-config-not-set, fail-cli and fail-config-not-supported-value (alertMessage "Kubelet is not configured to only use strong cryptographic ciphers", raw.rego lines 21 and 47; failedPaths TLSCipherSuites, line 50); [] for pass-cli, pass-config-not-set and pass-config-supported-value
|
| 26 |
Check: Task: for each of the 6 inputs (case names hidden) say whether the kubelet is configured with only strong ciphers, and for failing configs name the offending config path. Score: exact match of the verdict against expected.json (empty or not); failedPaths compared as an exact set where expected.json gives one
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 29 |
- `rules/etcd-tls-enabled/` (13 files): Kubescape etcd-tls-enabled: decide for 5 etcd Pod manifests whether etcd serves TLS with a certificate and key file, and give the fix path.
|
| 30 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 5 test cases each with an input etcd Pod YAML and expected.json (empty list = pass, else alert with fixPaths)
|
| 31 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 32 |
-
Reference result: per_case_verdict_with_path
|
| 33 |
-
Reference source: test/<case>/expected.json: alert for fail-missing-cert-argument (fixPaths spec.containers[0].command[17] = --cert-file=...), fail-missing-key-argument (--key-file) and rke2-args-fail (spec.containers[0].args[16]); [] for rke2-args and test-passed
|
| 34 |
Check: Task: for each of the 5 etcd Pods (case names hidden) say whether TLS is enabled and, if not, which flag is missing. Score: exact match of the verdict against expected.json; missing flag compared against the fixPaths value of expected.json
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 37 |
- `rules/ensure-that-the-api-server-anonymous-auth-argument-is-set-to-false/` (12 files): Kubescape regolibrary: find the kube-apiserver Pods that allow anonymous requests and give the failed and fix paths, 5 inputs in 4 test cases.
|
| 38 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and test/<case>/input/*.yaml with test/<case>/expected.json (expected alerts with failedPaths and fixPaths)
|
| 39 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 40 |
-
Reference result: per_case_alert_set
|
| 41 |
-
Reference source: test/failed/expected.json: 2 alerts (input 1.yaml with no flag: failedPaths [], fixPaths spec.containers[0].command[26] value --anonymous-auth=false; input 2.yaml with --anonymous-auth=true at command[26]: failedPaths and fixPaths command[26]); test/rke2-args-fail/expected.json: 1 alert, failedPaths and fixPaths spec.containers[0].args[1]; test/passed/expected.json and test/rke2-args/expected.json: [] (no alert)
|
| 42 |
Check: Task: given the rule and the input Pods of each test case, list the alerts with failedPaths and fixPaths. Score: per test case, exact match of the alert set (alertMessage, failedPaths, fixPaths) against expected.json; accuracy over 4 cases
|
| 43 |
Companions (not included): LICENSE
|
| 44 |
Dependencies: OPA (Rego evaluator) with the regolibrary test runner at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 45 |
- `rules/ensure-that-the-api-server-token-auth-file-parameter-is-not-set/` (12 files): Kubescape regolibrary: find the kube-apiserver Pods that set a static token auth file and give the failed and fix paths, 5 inputs in 4 test cases.
|
| 46 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and test/<case>/input/*.yaml with test/<case>/expected.json (expected alerts with failedPaths and fixPaths)
|
| 47 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 48 |
-
Reference result: per_case_alert_set
|
| 49 |
-
Reference source: test/failed/expected.json: 2 alerts (input with --token-auth-file inside command[25] together with --tls-private-key-file: failedPaths command[25], fix value --tls-private-key-file=/var/lib/minikube/certs/apiserver.key; input with --token-auth-file alone at command[26]: failedPaths command[26], fixPaths []); test/rke2-args-fail/expected.json: 1 alert, failedPaths spec.containers[0].args[1]; test/passed/expected.json and test/rke2-args/expected.json: [] (no alert)
|
| 50 |
Check: Task: given the rule and the input Pods of each test case, list the alerts with failedPaths and fixPaths. Score: per test case, exact match of the alert set (alertMessage, failedPaths, fixPaths) against expected.json; accuracy over 4 cases
|
| 51 |
Companions (not included): LICENSE
|
| 52 |
Dependencies: OPA (Rego evaluator) with the regolibrary test runner at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 53 |
- `rules/kubelet-rotate-certificates/` (12 files): Kubescape kubelet-rotate-certificates: decide for 5 kubelet command lines and configs whether client certificate rotation is disabled, and name the alert.
|
| 54 |
Format: Rego rule (raw.rego), rule.metadata.json, and 5 test cases each with input/kubelet-info.json and expected.json (empty list = pass)
|
| 55 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 56 |
-
Reference result: per_case_verdict_with_path
|
| 57 |
-
Reference source: test/<case>/expected.json: fail-cli-argument-set-false and fail-set-false-via-config-file give "Kubelet client certificates rotation is disabled" (raw.rego lines 20 and 44; the config case has failedPaths rotateCertificates, line 47); fail-sensor-failed gives "Failed to analyze config file" (line 72); pass-cli-argument-not-set and pass-not-present-in-config-file give []
|
| 58 |
Check: Task: for each of the 5 inputs (case names hidden) say whether rotation is disabled, could not be analysed, or is fine, and for config-file failures name the config path. Score: exact match of the verdict and alertMessage against expected.json (empty or not); failedPaths compared as an exact set where expected.json gives one; accuracy over 5
|
| 59 |
Companions (not included): LICENSE
|
| 60 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 61 |
- `rules/ensure-that-the-api-server-encryption-provider-config-argument-is-set-as-appropriate/` (13 files): Kubescape api-server encryption-provider-config: decide for 4 control-plane test cases whether Secrets are encrypted at rest, and give the fix path.
|
| 62 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 4 test cases with kube-apiserver Pod YAML and ControlPlaneInfo JSON inputs and expected.json (empty list = pass)
|
| 63 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 64 |
-
Reference result: per_case_verdict_with_path
|
| 65 |
-
Reference source: test/failed/expected.json: 2 alerts, "Encryption provider config file not set" with fixPaths spec.containers[0].command[26] (raw.rego line 15) and "Encryption provider config is not covering secrets" (line 46) for the ControlPlaneInfo config; test/rke2-args-fail/expected.json: 1 alert with fixPaths spec.containers[0].args[2] (flags in args, RKE2 layout); test/passed and test/rke2-args give []
|
| 66 |
Check: Task: for each of the 4 cases (names hidden, inputs given) list the alerts the rule raises and the fix path. Score: per case, the set of alertMessage values must equal expected.json and each fixPaths path must match exactly; accuracy over 4 cases
|
| 67 |
Companions (not included): LICENSE
|
| 68 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 69 |
- `rules/kubelet-protect-kernel-defaults/` (10 files): Kubescape kubelet-protect-kernel-defaults: decide for 4 kubelet command lines and configs whether the kubelet protects kernel defaults, and name the alert.
|
| 70 |
Format: Rego rule (raw.rego), rule.metadata.json, and 4 test cases each with input/kubelet-info.json and expected.json (empty list = pass)
|
| 71 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 72 |
-
Reference result: per_case_verdict_with_path
|
| 73 |
-
Reference source: test/<case>/expected.json: deny-config-file-false gives "Property protectKernelDefaults is not set to true" with failedPaths protectKernelDefaults (raw.rego lines 44 and 47); fail-no-config-and-cli and fail-set-via-cli give "Argument --protect-kernel-defaults is not set to true." (lines 20 and 71); pass-set-via-cli gives []
|
| 74 |
Check: Task: for each of the 4 inputs (case names hidden) say whether kernel defaults are protected, and for failures give the alert and, for config-file failures, the config path. Score: exact match of the verdict and alertMessage against expected.json; failedPaths compared as an exact set where expected.json gives one; accuracy over 4
|
| 75 |
Companions (not included): LICENSE
|
| 76 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 77 |
- `rules/ensure-that-the-api-server-profiling-argument-is-set-to-false/` (12 files): Kubescape api-server profiling: decide for 4 control-plane test cases whether kube-apiserver profiling is on, and give the failed and fix paths.
|
| 78 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 4 test cases with kube-apiserver Pod YAML inputs (kubeadm command layout and RKE2 args layout) and expected.json (empty list = pass)
|
| 79 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 80 |
-
Reference result: per_case_verdict_with_path
|
| 81 |
-
Reference source: test/failed/expected.json: 2 alerts, one for the Pod without the flag (fixPaths spec.containers[0].command[26] value --profiling=false, raw.rego lines 42 to 53) and one for --profiling=true (failedPaths and fixPaths spec.containers[0].command[3], lines 31 to 40); test/rke2-args-fail/expected.json: failedPaths and fixPaths spec.containers[0].args[1]; test/passed and test/rke2-args give []
|
| 82 |
Check: Task: for each input Pod of the 4 cases (names hidden) say whether profiling is on and give the failed path and fix path. Score: per case, the set of (failedPaths, fixPaths path, fixPaths value) triples must equal expected.json exactly; accuracy over 4 cases
|
| 83 |
Companions (not included): LICENSE
|
| 84 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Each unit is self-contained. 8 of 8 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Tools are named in the check written per unit in the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `rules/kubelet-strong-cryptography-ciphers/` (14 files): Kubescape kubelet-strong-cryptography-ciphers: decide for 6 kubelet command lines and configs whether the kubelet uses only strong TLS ciphers.
|
| 20 |
Format: Rego rule (raw.rego), rule.metadata.json, and 6 test cases each with input/kubeletcmd.json and expected.json (empty list = pass)
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: for each of the 6 inputs (case names hidden) say whether the kubelet is configured with only strong ciphers, and for failing configs name the offending config path. Score: exact match of the verdict against expected.json (empty or not); failedPaths compared as an exact set where expected.json gives one
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 25 |
- `rules/etcd-tls-enabled/` (13 files): Kubescape etcd-tls-enabled: decide for 5 etcd Pod manifests whether etcd serves TLS with a certificate and key file, and give the fix path.
|
| 26 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 5 test cases each with an input etcd Pod YAML and expected.json (empty list = pass, else alert with fixPaths)
|
| 27 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 28 |
Check: Task: for each of the 5 etcd Pods (case names hidden) say whether TLS is enabled and, if not, which flag is missing. Score: exact match of the verdict against expected.json; missing flag compared against the fixPaths value of expected.json
|
| 29 |
Companions (not included): LICENSE
|
| 30 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 31 |
- `rules/ensure-that-the-api-server-anonymous-auth-argument-is-set-to-false/` (12 files): Kubescape regolibrary: find the kube-apiserver Pods that allow anonymous requests and give the failed and fix paths, 5 inputs in 4 test cases.
|
| 32 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and test/<case>/input/*.yaml with test/<case>/expected.json (expected alerts with failedPaths and fixPaths)
|
| 33 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 34 |
Check: Task: given the rule and the input Pods of each test case, list the alerts with failedPaths and fixPaths. Score: per test case, exact match of the alert set (alertMessage, failedPaths, fixPaths) against expected.json; accuracy over 4 cases
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: OPA (Rego evaluator) with the regolibrary test runner at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 37 |
- `rules/ensure-that-the-api-server-token-auth-file-parameter-is-not-set/` (12 files): Kubescape regolibrary: find the kube-apiserver Pods that set a static token auth file and give the failed and fix paths, 5 inputs in 4 test cases.
|
| 38 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and test/<case>/input/*.yaml with test/<case>/expected.json (expected alerts with failedPaths and fixPaths)
|
| 39 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 40 |
Check: Task: given the rule and the input Pods of each test case, list the alerts with failedPaths and fixPaths. Score: per test case, exact match of the alert set (alertMessage, failedPaths, fixPaths) against expected.json; accuracy over 4 cases
|
| 41 |
Companions (not included): LICENSE
|
| 42 |
Dependencies: OPA (Rego evaluator) with the regolibrary test runner at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 43 |
- `rules/kubelet-rotate-certificates/` (12 files): Kubescape kubelet-rotate-certificates: decide for 5 kubelet command lines and configs whether client certificate rotation is disabled, and name the alert.
|
| 44 |
Format: Rego rule (raw.rego), rule.metadata.json, and 5 test cases each with input/kubelet-info.json and expected.json (empty list = pass)
|
| 45 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 46 |
Check: Task: for each of the 5 inputs (case names hidden) say whether rotation is disabled, could not be analysed, or is fine, and for config-file failures name the config path. Score: exact match of the verdict and alertMessage against expected.json (empty or not); failedPaths compared as an exact set where expected.json gives one; accuracy over 5
|
| 47 |
Companions (not included): LICENSE
|
| 48 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 49 |
- `rules/ensure-that-the-api-server-encryption-provider-config-argument-is-set-as-appropriate/` (13 files): Kubescape api-server encryption-provider-config: decide for 4 control-plane test cases whether Secrets are encrypted at rest, and give the fix path.
|
| 50 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 4 test cases with kube-apiserver Pod YAML and ControlPlaneInfo JSON inputs and expected.json (empty list = pass)
|
| 51 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 52 |
Check: Task: for each of the 4 cases (names hidden, inputs given) list the alerts the rule raises and the fix path. Score: per case, the set of alertMessage values must equal expected.json and each fixPaths path must match exactly; accuracy over 4 cases
|
| 53 |
Companions (not included): LICENSE
|
| 54 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 55 |
- `rules/kubelet-protect-kernel-defaults/` (10 files): Kubescape kubelet-protect-kernel-defaults: decide for 4 kubelet command lines and configs whether the kubelet protects kernel defaults, and name the alert.
|
| 56 |
Format: Rego rule (raw.rego), rule.metadata.json, and 4 test cases each with input/kubelet-info.json and expected.json (empty list = pass)
|
| 57 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 58 |
Check: Task: for each of the 4 inputs (case names hidden) say whether kernel defaults are protected, and for failures give the alert and, for config-file failures, the config path. Score: exact match of the verdict and alertMessage against expected.json; failedPaths compared as an exact set where expected.json gives one; accuracy over 4
|
| 59 |
Companions (not included): LICENSE
|
| 60 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 61 |
- `rules/ensure-that-the-api-server-profiling-argument-is-set-to-false/` (12 files): Kubescape api-server profiling: decide for 4 control-plane test cases whether kube-apiserver profiling is on, and give the failed and fix paths.
|
| 62 |
Format: Rego rule (raw.rego, filter.rego), rule.metadata.json, and 4 test cases with kube-apiserver Pod YAML inputs (kubeadm command layout and RKE2 args layout) and expected.json (empty list = pass)
|
| 63 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 64 |
Check: Task: for each input Pod of the 4 cases (names hidden) say whether profiling is on and give the failed path and fix path. Score: per case, the set of (failedPaths, fixPaths path, fixPaths value) triples must equal expected.json exactly; accuracy over 4 cases
|
| 65 |
Companions (not included): LICENSE
|
| 66 |
Dependencies: opa (Open Policy Agent) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-s-security-detection-2/kyverno-policies-library-with-kyverno-cli-and-chainsaw-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Each unit is self-contained. 10 of 10 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: per_resource_verdict; patched_resource. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Tools are named in the check written per unit in the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,80 +19,60 @@ Units:
|
|
| 21 |
- `pod-security-vpol/baseline/restrict-sysctls/` (10 files): Kyverno restrict-sysctls: decide for 27 Pods, Deployments and CronJobs whether the Pod Security baseline sysctl policy rejects them.
|
| 22 |
Format: Kyverno ValidatingPolicy YAML plus .kyverno-test/kyverno-test.yaml (expected result per resource) and resource.yaml (27 resources), plus chainsaw end-to-end test manifests
|
| 23 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 24 |
-
Reference result: per_resource_verdict
|
| 25 |
-
Reference source: .kyverno-test/kyverno-test.yaml lines 9 to 66: result fail for badpod01, badpod02, baddeployment01, baddeployment02, badcronjob01, badcronjob02 (lines 16, 23, 30); result pass for goodpod01 to 07, gooddeployment01 to 07, goodcronjob01 to 07 (lines 42, 54, 66)
|
| 26 |
Check: Task: given the policy and the 27 resources of resource.yaml (names replaced by neutral ids), say which ones the policy rejects. Score: exact match of the per-resource pass or fail verdict against kyverno-test.yaml; accuracy over 27
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 29 |
- `other-vpol/disallow-secrets-from-env-vars/` (10 files): Kyverno disallow-secrets-from-env-vars: decide for 3 Pods whether the policy rejects Secrets passed as environment variables.
|
| 30 |
Format: Kyverno ValidatingPolicy YAML, .kyverno-test/kyverno-test.yaml with the expected result per Pod and resource.yaml (3 Pods), plus chainsaw end-to-end manifests
|
| 31 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 32 |
-
Reference result: per_resource_verdict
|
| 33 |
-
Reference source: .kyverno-test/kyverno-test.yaml: result fail for default/secret-env-pod and default/secret-ref-pod (line 16), result pass for default/good-pod (line 22)
|
| 34 |
Check: Task: say which of the 3 Pods (names hidden) the policy rejects and which rule message applies. Score: exact match of the verdict per Pod against kyverno-test.yaml; accuracy over 3; chainsaw pods-bad and pods-good give a second check set
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 37 |
- `other-mpol/remove-hostpath-volumes/` (15 files): Kyverno remove-hostpath-volumes: rewrite 5 Pods so that every hostPath volume and its volumeMounts are removed, matching the expected patched Pods.
|
| 38 |
Format: Kyverno MutatingPolicy YAML (CEL JSONPatch), .kyverno-test/kyverno-test.yaml with resource.yaml (1 Pod) and patchedResource.yaml, plus chainsaw manifests pods.yaml (4 Pods) with pod-patched.yaml to pod-patched04.yaml (assert) and not-pod-patched04.yaml, not-pod-patched05.yaml (error, must not match)
|
| 39 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 40 |
-
Reference result: patched_resource
|
| 41 |
-
Reference source: .kyverno-test/patchedResource.yaml for Pod busybox (kyverno-test.yaml lines 10 to 16, result pass, isMutatingPolicy true); .chainsaw-test/pod-patched.yaml to pod-patched04.yaml are the expected Pods after mutation (chainsaw-test.yaml lines 23 to 30), not-pod-patched04.yaml and not-pod-patched05.yaml must not match (lines 31 to 34)
|
| 42 |
Check: Task: given the 5 input Pods (resource.yaml and chainsaw pods.yaml) and the hardening goal in words (policy hidden), write each Pod with hostPath volumes and their mounts removed. Score: parse YAML and compare the spec of each Pod with the expected patched Pod as a structural subset match (the chainsaw assert semantics: every field of the expected file must be present with the same value), plus the 2 error files must not match; per-Pod pass or fail over 5
|
| 43 |
Companions (not included): LICENSE
|
| 44 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 45 |
- `other-mpol/disable-automountserviceaccounttoken/` (11 files): Kyverno disable-automountserviceaccounttoken: decide which of 3 ServiceAccounts must be patched and write the patched default ServiceAccount with token automount disabled.
|
| 46 |
Format: Kyverno MutatingPolicy YAML (ApplyConfiguration), .kyverno-test/kyverno-test.yaml with resource.yaml (ServiceAccounts default and demo-sa) and patchedResource.yaml, plus chainsaw manifests sa.yaml (foo-sa), sa-patched.yaml (assert) and sa-not-patched.yaml (error)
|
| 47 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 48 |
-
Reference result: patched_resource
|
| 49 |
-
Reference source: .kyverno-test/patchedResource.yaml: ServiceAccount default with automountServiceAccountToken false (kyverno-test.yaml lines 10 to 16, only resource default listed); policy matches resourceNames default only (policy line 22), so demo-sa and chainsaw foo-sa stay unpatched (sa-not-patched.yaml is an error assertion, chainsaw-test.yaml line 25)
|
| 50 |
Check: Task: given the 3 ServiceAccounts and the hardening goal in words, say which must be patched and write the patched object. Score: per ServiceAccount, patched or not must match (default yes, demo-sa no, foo-sa no) and the patched default must equal patchedResource.yaml after YAML parsing; accuracy over 3. Small unit: use as a short item or pool with other mutating policies
|
| 51 |
Companions (not included): LICENSE
|
| 52 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 53 |
- `pod-security-vpol/restricted/restrict-seccomp-strict/` (10 files): Kyverno restrict-seccomp-strict: decide for 51 Pods, Deployments and CronJobs whether the Pod Security restricted seccomp policy rejects them.
|
| 54 |
Format: Kyverno ValidatingPolicy YAML (CEL) plus .kyverno-test/kyverno-test.yaml (expected result per resource) and resource.yaml (51 resources), plus chainsaw end-to-end test manifests
|
| 55 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 56 |
-
Reference result: per_resource_verdict
|
| 57 |
-
Reference source: .kyverno-test/kyverno-test.yaml: result fail for badcronjob01 to 07, baddeployment01 to 07, badpod01 to 07 (lines 21, 33, 45); result pass for goodcronjob01 to 10, gooddeployment01 to 10, goodpod01 to 10 (lines 60, 75, 90); chainsaw-test.yaml lines 36 and 43 expect an admission error for pod-bad.yaml and podcontroller-bad.yaml
|
| 58 |
Check: Task: given the policy and the 51 resources of resource.yaml (names replaced by neutral ids), say which ones the policy rejects. Score: exact match of the per-resource pass or fail verdict against kyverno-test.yaml; accuracy over 51
|
| 59 |
Companions (not included): LICENSE
|
| 60 |
Dependencies: kyverno CLI and chainsaw at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 61 |
- `other-mpol/add-default-securitycontext/` (11 files): Kyverno add-default-securitycontext: write the patched Pods, Deployment and CronJob with default runAsNonRoot, runAsUser, runAsGroup and fsGroup, keeping values already set.
|
| 62 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (Pod myapp-pod) and patchedResource.yaml, plus chainsaw manifests pod-resources.yaml (pod01, pod02), podcontroller-resources.yaml (deployment01, cronjob01) and their *-patched.yaml assertions
|
| 63 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 64 |
-
Reference result: patched_resource
|
| 65 |
-
Reference source: .kyverno-test/patchedResource.yaml: myapp-pod gains securityContext runAsNonRoot true, runAsUser 1000, runAsGroup 3000, fsGroup 2000 (kyverno-test.yaml lines 10 to 16); .chainsaw-test/pod-resources-patched.yaml: pod01 gains all four fields, pod02 keeps its own runAsNonRoot false and gains only runAsUser, runAsGroup and fsGroup; podcontroller-patched.yaml: the same defaults in the Deployment and CronJob pod templates (chainsaw-test.yaml lines 15 to 26)
|
| 66 |
Check: Task: given the 5 input objects and the hardening goal in words (add the defaults, never overwrite a field already set), write each patched object. Score: per object, the myapp-pod answer must equal patchedResource.yaml after YAML parsing; for the 4 chainsaw objects every field in the *-patched.yaml assertion must be present with that value (chainsaw assert is a partial match), and pod02 must keep runAsNonRoot false; accuracy over 5
|
| 67 |
Companions (not included): LICENSE
|
| 68 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 69 |
- `other-mpol/always-pull-images/` (14 files)
|
| 70 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (myapp-pod-1, myapp-pod-2) and patchedResource1.yaml, patchedResource2.yaml, plus chainsaw manifests pods.yaml (pod01 to pod03), podcontrollers.yaml and their patched assertions
|
| 71 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 72 |
-
Reference result: patched_resource
|
| 73 |
-
Reference source: kyverno-test.yaml lines 10 to 16 (myapp-pod-1 against patchedResource1.yaml) and 17 to 23 (myapp-pod-2 with 2 containers against patchedResource2.yaml): every container gets imagePullPolicy Always; chainsaw patched-pod01.yaml to patched-pod03.yaml and podcontrollers-patched.yaml assert the same for pod01 to pod03, deployment01 and cronjob01
|
| 74 |
Check: Task: given the 7 input objects and the hardening goal in words, write each patched object. Score: per object, the 2 kyverno CLI answers must equal their patchedResource file after YAML parsing; for the 5 chainsaw objects every field in the patched assertion must be present with that value (chainsaw assert is a partial match); accuracy over 7
|
| 75 |
Companions (not included): LICENSE
|
| 76 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 77 |
- `other-mpol/mitigate-log4shell/` (15 files)
|
| 78 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (demo-pod01, demo-pod02) and patched resource files, plus chainsaw manifests pod.yaml (pod01 to pod03), podcontroller.yaml and the per-object patched assertions
|
| 79 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 80 |
-
Reference result: patched_resource
|
| 81 |
-
Reference source: kyverno-test.yaml lines 10 to 16 (demo-pod01 with an initContainer and a container) and 17 to 23 (demo-pod02): the variable is added to every container and initContainer; chainsaw pod-patched01.yaml to pod-patched03.yaml, deploy-patched.yaml and cronjob-patched.yaml assert the same for pod01 to pod03, deployment01 and cronjob01
|
| 82 |
Check: Task: given the 7 input objects and the mitigation in words, write each patched object. Score: per object, the 2 kyverno CLI answers must equal their patched resource file after YAML parsing; for the 5 chainsaw objects every field in the patched assertion must be present with that value (chainsaw assert is a partial match), initContainers included; accuracy over 7
|
| 83 |
Companions (not included): LICENSE
|
| 84 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 85 |
- `psa-mpol/add-psa-labels/` (13 files): Kyverno add-psa-labels: write the patched Namespaces with Pod Security Admission labels enforce=baseline and warn=restricted, keeping labels already set.
|
| 86 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (Namespace test), patchedResource.yaml (pass) and patchedResourcefail.yaml (fail case), plus chainsaw ns.yaml (4 Namespaces) and patched-ns01.yaml to patched-ns03.yaml
|
| 87 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 88 |
-
Reference result: patched_resource
|
| 89 |
-
Reference source: kyverno-test.yaml lines 18 to 24: Namespace test gains pod-security.kubernetes.io/enforce baseline and warn restricted (patchedResource.yaml, result pass); lines 11 to 17: patchedResourcefail.yaml is a wrong patch (result fail); chainsaw: ns01 gains both labels, ns02 keeps enforce privileged and gains warn restricted, ns03 keeps warn baseline and gains enforce baseline, ns04 already carries both labels and stays unchanged
|
| 90 |
Check: Task: given the 5 input Namespaces and the goal in words (add each label only where it is missing), write each patched Namespace; patchedResourcefail.yaml is hidden or offered as a distractor to reject. Score: Namespace test must equal patchedResource.yaml after YAML parsing; ns01 to ns03 must carry every label of their patched assertion (chainsaw partial match); ns04 must be unchanged; accuracy over 5
|
| 91 |
Companions (not included): LICENSE
|
| 92 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 93 |
- `psp-migration-mpol/add-apparmor/` (10 files): Kyverno add-apparmor: write the patched Pods with a runtime/default AppArmor annotation for every container.
|
| 94 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (pod01, pod02) and the patched resource files, plus chainsaw resource-mutated.yaml
|
| 95 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
| 96 |
-
Reference result: patched_resource
|
| 97 |
-
Reference source: kyverno-test.yaml lines 10 to 16 (pod01) and 17 to 23 (pod02): one annotation container.apparmor.security.beta.kubernetes.io/<container name>: runtime/default per container; chainsaw-test.yaml lines 15 to 24 apply the same resource.yaml and assert resource-mutated.yaml
|
| 98 |
Check: Task: given the 2 Pods and the goal in words, write each patched Pod. Score: per Pod, the answer must equal its patched resource file after YAML parsing (annotation keys must name each container exactly); accuracy over 2. Small unit: use as a short item or pool with other mutating policies
|
| 99 |
Companions (not included): LICENSE
|
| 100 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Each unit is self-contained. 10 of 10 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Tools are named in the check written per unit in the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `pod-security-vpol/baseline/restrict-sysctls/` (10 files): Kyverno restrict-sysctls: decide for 27 Pods, Deployments and CronJobs whether the Pod Security baseline sysctl policy rejects them.
|
| 20 |
Format: Kyverno ValidatingPolicy YAML plus .kyverno-test/kyverno-test.yaml (expected result per resource) and resource.yaml (27 resources), plus chainsaw end-to-end test manifests
|
| 21 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 22 |
Check: Task: given the policy and the 27 resources of resource.yaml (names replaced by neutral ids), say which ones the policy rejects. Score: exact match of the per-resource pass or fail verdict against kyverno-test.yaml; accuracy over 27
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 25 |
- `other-vpol/disallow-secrets-from-env-vars/` (10 files): Kyverno disallow-secrets-from-env-vars: decide for 3 Pods whether the policy rejects Secrets passed as environment variables.
|
| 26 |
Format: Kyverno ValidatingPolicy YAML, .kyverno-test/kyverno-test.yaml with the expected result per Pod and resource.yaml (3 Pods), plus chainsaw end-to-end manifests
|
| 27 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 28 |
Check: Task: say which of the 3 Pods (names hidden) the policy rejects and which rule message applies. Score: exact match of the verdict per Pod against kyverno-test.yaml; accuracy over 3; chainsaw pods-bad and pods-good give a second check set
|
| 29 |
Companions (not included): LICENSE
|
| 30 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 31 |
- `other-mpol/remove-hostpath-volumes/` (15 files): Kyverno remove-hostpath-volumes: rewrite 5 Pods so that every hostPath volume and its volumeMounts are removed, matching the expected patched Pods.
|
| 32 |
Format: Kyverno MutatingPolicy YAML (CEL JSONPatch), .kyverno-test/kyverno-test.yaml with resource.yaml (1 Pod) and patchedResource.yaml, plus chainsaw manifests pods.yaml (4 Pods) with pod-patched.yaml to pod-patched04.yaml (assert) and not-pod-patched04.yaml, not-pod-patched05.yaml (error, must not match)
|
| 33 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 34 |
Check: Task: given the 5 input Pods (resource.yaml and chainsaw pods.yaml) and the hardening goal in words (policy hidden), write each Pod with hostPath volumes and their mounts removed. Score: parse YAML and compare the spec of each Pod with the expected patched Pod as a structural subset match (the chainsaw assert semantics: every field of the expected file must be present with the same value), plus the 2 error files must not match; per-Pod pass or fail over 5
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 37 |
- `other-mpol/disable-automountserviceaccounttoken/` (11 files): Kyverno disable-automountserviceaccounttoken: decide which of 3 ServiceAccounts must be patched and write the patched default ServiceAccount with token automount disabled.
|
| 38 |
Format: Kyverno MutatingPolicy YAML (ApplyConfiguration), .kyverno-test/kyverno-test.yaml with resource.yaml (ServiceAccounts default and demo-sa) and patchedResource.yaml, plus chainsaw manifests sa.yaml (foo-sa), sa-patched.yaml (assert) and sa-not-patched.yaml (error)
|
| 39 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 40 |
Check: Task: given the 3 ServiceAccounts and the hardening goal in words, say which must be patched and write the patched object. Score: per ServiceAccount, patched or not must match (default yes, demo-sa no, foo-sa no) and the patched default must equal patchedResource.yaml after YAML parsing; accuracy over 3. Small unit: use as a short item or pool with other mutating policies
|
| 41 |
Companions (not included): LICENSE
|
| 42 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 43 |
- `pod-security-vpol/restricted/restrict-seccomp-strict/` (10 files): Kyverno restrict-seccomp-strict: decide for 51 Pods, Deployments and CronJobs whether the Pod Security restricted seccomp policy rejects them.
|
| 44 |
Format: Kyverno ValidatingPolicy YAML (CEL) plus .kyverno-test/kyverno-test.yaml (expected result per resource) and resource.yaml (51 resources), plus chainsaw end-to-end test manifests
|
| 45 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 46 |
Check: Task: given the policy and the 51 resources of resource.yaml (names replaced by neutral ids), say which ones the policy rejects. Score: exact match of the per-resource pass or fail verdict against kyverno-test.yaml; accuracy over 51
|
| 47 |
Companions (not included): LICENSE
|
| 48 |
Dependencies: kyverno CLI and chainsaw at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 49 |
- `other-mpol/add-default-securitycontext/` (11 files): Kyverno add-default-securitycontext: write the patched Pods, Deployment and CronJob with default runAsNonRoot, runAsUser, runAsGroup and fsGroup, keeping values already set.
|
| 50 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (Pod myapp-pod) and patchedResource.yaml, plus chainsaw manifests pod-resources.yaml (pod01, pod02), podcontroller-resources.yaml (deployment01, cronjob01) and their *-patched.yaml assertions
|
| 51 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 52 |
Check: Task: given the 5 input objects and the hardening goal in words (add the defaults, never overwrite a field already set), write each patched object. Score: per object, the myapp-pod answer must equal patchedResource.yaml after YAML parsing; for the 4 chainsaw objects every field in the *-patched.yaml assertion must be present with that value (chainsaw assert is a partial match), and pod02 must keep runAsNonRoot false; accuracy over 5
|
| 53 |
Companions (not included): LICENSE
|
| 54 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 55 |
- `other-mpol/always-pull-images/` (14 files)
|
| 56 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (myapp-pod-1, myapp-pod-2) and patchedResource1.yaml, patchedResource2.yaml, plus chainsaw manifests pods.yaml (pod01 to pod03), podcontrollers.yaml and their patched assertions
|
| 57 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 58 |
Check: Task: given the 7 input objects and the hardening goal in words, write each patched object. Score: per object, the 2 kyverno CLI answers must equal their patchedResource file after YAML parsing; for the 5 chainsaw objects every field in the patched assertion must be present with that value (chainsaw assert is a partial match); accuracy over 7
|
| 59 |
Companions (not included): LICENSE
|
| 60 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 61 |
- `other-mpol/mitigate-log4shell/` (15 files)
|
| 62 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (demo-pod01, demo-pod02) and patched resource files, plus chainsaw manifests pod.yaml (pod01 to pod03), podcontroller.yaml and the per-object patched assertions
|
| 63 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 64 |
Check: Task: given the 7 input objects and the mitigation in words, write each patched object. Score: per object, the 2 kyverno CLI answers must equal their patched resource file after YAML parsing; for the 5 chainsaw objects every field in the patched assertion must be present with that value (chainsaw assert is a partial match), initContainers included; accuracy over 7
|
| 65 |
Companions (not included): LICENSE
|
| 66 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 67 |
- `psa-mpol/add-psa-labels/` (13 files): Kyverno add-psa-labels: write the patched Namespaces with Pod Security Admission labels enforce=baseline and warn=restricted, keeping labels already set.
|
| 68 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (Namespace test), patchedResource.yaml (pass) and patchedResourcefail.yaml (fail case), plus chainsaw ns.yaml (4 Namespaces) and patched-ns01.yaml to patched-ns03.yaml
|
| 69 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 70 |
Check: Task: given the 5 input Namespaces and the goal in words (add each label only where it is missing), write each patched Namespace; patchedResourcefail.yaml is hidden or offered as a distractor to reject. Score: Namespace test must equal patchedResource.yaml after YAML parsing; ns01 to ns03 must carry every label of their patched assertion (chainsaw partial match); ns04 must be unchanged; accuracy over 5
|
| 71 |
Companions (not included): LICENSE
|
| 72 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
| 73 |
- `psp-migration-mpol/add-apparmor/` (10 files): Kyverno add-apparmor: write the patched Pods with a runtime/default AppArmor annotation for every container.
|
| 74 |
Format: Kyverno MutatingPolicy YAML, .kyverno-test/kyverno-test.yaml with resource.yaml (pod01, pod02) and the patched resource files, plus chainsaw resource-mutated.yaml
|
| 75 |
Origin: test fixture written by the rule maintainers to pin the expected findings of their own rule (synthetic, not recorded production code or telemetry)
|
|
|
|
|
|
|
| 76 |
Check: Task: given the 2 Pods and the goal in words, write each patched Pod. Score: per Pod, the answer must equal its patched resource file after YAML parsing (annotation keys must name each container exactly); accuracy over 2. Small unit: use as a short item or pool with other mutating policies
|
| 77 |
Companions (not included): LICENSE
|
| 78 |
Dependencies: kyverno CLI at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed; chainsaw (Kyverno) at this commit (Apache-2.0): needed only to rerun the scan; not used by the judge; version pinned when the pool is built; not packed
|
campaign_files/2026-10-sc-science-reference-data-2/lammps-force-style-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: reference_numbers_with_tolerance. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Give the agent data.metal, in.metal and CuNi.eam.alloy with pair_style eam/alloy and ask for the initial energy, forces and stress and those after the short run; compare each value with the YAML by the relative-error rule EXPECT_FP_LE_WITH_EPS (test_main.h lines 37 to 44) with epsilon 5e-12 from the YAML line 4 (read at test_pair_style.cpp line 429), init values with epsilon (lines 437, 440, 444), run forces with 5*epsilon (line 452), run stress and energy with epsilon (lines 455, 460); the single() check is skipped per the YAML line 5.
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-2.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `unittest/force-styles/tests/atomic-pair-eam_alloy.yaml`: LAMMPS force-style test atomic-pair-eam_alloy: energy, forces and stress of a 32-atom Cu-Ni system with the Onat-Durukanoglu EAM alloy potential, before and after a short MD run.
|
| 22 |
Format: YAML reference (epsilon at line 4, init_vdwl at line 16, run_vdwl at line 53, plus per-atom forces and stress)
|
| 23 |
Origin: force-style unit test of LAMMPS (tool_fixture): reference values generated by LAMMPS and committed as YAML
|
| 24 |
-
Reference result: reference_numbers_with_tolerance
|
| 25 |
-
Reference source: unittest/force-styles/tests/atomic-pair-eam_alloy.yaml (init_vdwl -118.71751329207396 at line 16, run_vdwl -118.72184582083834 at line 53, init and run forces and stress)
|
| 26 |
Check: give the agent data.metal, in.metal and CuNi.eam.alloy with pair_style eam/alloy and ask for the initial energy, forces and stress and those after the short run; compare each value with the YAML by the relative-error rule EXPECT_FP_LE_WITH_EPS (test_main.h lines 37 to 44) with epsilon 5e-12 from the YAML line 4 (read at test_pair_style.cpp line 429), init values with epsilon (lines 437, 440, 444), run forces with 5*epsilon (line 452), run stress and energy with epsilon (lines 455, 460); the single() check is skipped per the YAML line 5
|
| 27 |
Companions (not included): LICENSE; potentials/CuNi.eam.alloy; unittest/force-styles/test_main.h; unittest/force-styles/test_pair_style.cpp; unittest/force-styles/tests/data.metal; unittest/force-styles/tests/in.metal
|
| 28 |
Dependencies: LAMMPS at 4a9f5dfe465386e380d8907e6e1d386a755ba80c built with the MANYBODY package and its unittest harness
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Give the agent data.metal, in.metal and CuNi.eam.alloy with pair_style eam/alloy and ask for the initial energy, forces and stress and those after the short run; compare each value with the YAML by the relative-error rule EXPECT_FP_LE_WITH_EPS (test_main.h lines 37 to 44) with epsilon 5e-12 from the YAML line 4 (read at test_pair_style.cpp line 429), init values with epsilon (lines 437, 440, 444), run forces with 5*epsilon (line 452), run stress and energy with epsilon (lines 455, 460); the single() check is skipped per the YAML line 5.
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-2.0-only
|
|
|
|
| 19 |
- `unittest/force-styles/tests/atomic-pair-eam_alloy.yaml`: LAMMPS force-style test atomic-pair-eam_alloy: energy, forces and stress of a 32-atom Cu-Ni system with the Onat-Durukanoglu EAM alloy potential, before and after a short MD run.
|
| 20 |
Format: YAML reference (epsilon at line 4, init_vdwl at line 16, run_vdwl at line 53, plus per-atom forces and stress)
|
| 21 |
Origin: force-style unit test of LAMMPS (tool_fixture): reference values generated by LAMMPS and committed as YAML
|
|
|
|
|
|
|
| 22 |
Check: give the agent data.metal, in.metal and CuNi.eam.alloy with pair_style eam/alloy and ask for the initial energy, forces and stress and those after the short run; compare each value with the YAML by the relative-error rule EXPECT_FP_LE_WITH_EPS (test_main.h lines 37 to 44) with epsilon 5e-12 from the YAML line 4 (read at test_pair_style.cpp line 429), init values with epsilon (lines 437, 440, 444), run forces with 5*epsilon (line 452), run stress and energy with epsilon (lines 455, 460); the single() check is skipped per the YAML line 5
|
| 23 |
Companions (not included): LICENSE; potentials/CuNi.eam.alloy; unittest/force-styles/test_main.h; unittest/force-styles/test_pair_style.cpp; unittest/force-styles/tests/data.metal; unittest/force-styles/tests/in.metal
|
| 24 |
Dependencies: LAMMPS at 4a9f5dfe465386e380d8907e6e1d386a755ba80c built with the MANYBODY package and its unittest harness
|
campaign_files/2026-10-sc-science-reference-data-2/lastz-test-data/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_output_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa from src/ with default settings, strip the version token with the test's sed, and diff with the expected LAV; for an agent task, ask for the default LASTZ alignment of the two files and check the a { } blocks (scores and aligned segment coordinates) against the expected file; the file paths in the d { } and s { } stanzas are those of the test layout; run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa --format=axt and compare with the expected file the way axt_compare.py does: same number of blocks, blocks in the same order, each block's header fields (split on whitespace) and both aligned text lines equal; comment and blank lines ignored; the comparison script is read here as the rule and may be reimplemented, it is not run.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,16 +19,12 @@ Files:
|
|
| 21 |
- `test_data/base_test.default.lav`: LASTZ default pairwise alignment of two DNA sequences, LAV output.
|
| 22 |
Format: expected LAV file, 521 lines (12875 bytes) with 14 gapped alignment blocks and the default scoring matrix; inputs pseudocat.fa 19186 bytes and pseudopig.fa 69498 bytes
|
| 23 |
Origin: test data of LASTZ (tool_fixture): synthetic cat and pig like sequences with alignments produced by LASTZ and committed as references
|
| 24 |
-
Reference result: expected_output_file
|
| 25 |
-
Reference source: test_data/base_test.default.lav, which the make test target of src/Makefile (lines 208 to 217) diffs against
|
| 26 |
Check: run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa from src/ with default settings, strip the version token with the test's sed, and diff with the expected LAV; for an agent task, ask for the default LASTZ alignment of the two files and check the a { } blocks (scores and aligned segment coordinates) against the expected file; the file paths in the d { } and s { } stanzas are those of the test layout
|
| 27 |
Companions (not included): test_data/pseudocat.fa; test_data/pseudopig.fa; src/Makefile; LICENSE
|
| 28 |
Dependencies: LASTZ at 1ac92247a02c8eed85ced64d1c2d38feb7f1c6f7
|
| 29 |
- `test_data/base_test.default.axt`: LASTZ default pairwise alignment of two DNA sequences, AXT output.
|
| 30 |
Format: expected AXT file, 69 lines (43863 bytes) with 14 alignment blocks; inputs pseudocat.fa and pseudopig.fa
|
| 31 |
Origin: test data of LASTZ (tool_fixture)
|
| 32 |
-
Reference result: expected_output_file
|
| 33 |
-
Reference source: test_data/base_test.default.axt, which the base_test_axt target of src/Makefile (lines 340 to 349) compares with tools/axt_compare.py
|
| 34 |
Check: run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa --format=axt and compare with the expected file the way axt_compare.py does: same number of blocks, blocks in the same order, each block's header fields (split on whitespace) and both aligned text lines equal; comment and blank lines ignored; the comparison script is read here as the rule and may be reimplemented, it is not run
|
| 35 |
Companions (not included): test_data/pseudocat.fa; test_data/pseudopig.fa; src/Makefile; tools/axt_compare.py; LICENSE
|
| 36 |
Dependencies: LASTZ at 1ac92247a02c8eed85ced64d1c2d38feb7f1c6f7
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa from src/ with default settings, strip the version token with the test's sed, and diff with the expected LAV; for an agent task, ask for the default LASTZ alignment of the two files and check the a { } blocks (scores and aligned segment coordinates) against the expected file; the file paths in the d { } and s { } stanzas are those of the test layout; run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa --format=axt and compare with the expected file the way axt_compare.py does: same number of blocks, blocks in the same order, each block's header fields (split on whitespace) and both aligned text lines equal; comment and blank lines ignored; the comparison script is read here as the rule and may be reimplemented, it is not run.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `test_data/base_test.default.lav`: LASTZ default pairwise alignment of two DNA sequences, LAV output.
|
| 20 |
Format: expected LAV file, 521 lines (12875 bytes) with 14 gapped alignment blocks and the default scoring matrix; inputs pseudocat.fa 19186 bytes and pseudopig.fa 69498 bytes
|
| 21 |
Origin: test data of LASTZ (tool_fixture): synthetic cat and pig like sequences with alignments produced by LASTZ and committed as references
|
|
|
|
|
|
|
| 22 |
Check: run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa from src/ with default settings, strip the version token with the test's sed, and diff with the expected LAV; for an agent task, ask for the default LASTZ alignment of the two files and check the a { } blocks (scores and aligned segment coordinates) against the expected file; the file paths in the d { } and s { } stanzas are those of the test layout
|
| 23 |
Companions (not included): test_data/pseudocat.fa; test_data/pseudopig.fa; src/Makefile; LICENSE
|
| 24 |
Dependencies: LASTZ at 1ac92247a02c8eed85ced64d1c2d38feb7f1c6f7
|
| 25 |
- `test_data/base_test.default.axt`: LASTZ default pairwise alignment of two DNA sequences, AXT output.
|
| 26 |
Format: expected AXT file, 69 lines (43863 bytes) with 14 alignment blocks; inputs pseudocat.fa and pseudopig.fa
|
| 27 |
Origin: test data of LASTZ (tool_fixture)
|
|
|
|
|
|
|
| 28 |
Check: run lastz ../test_data/pseudocat.fa ../test_data/pseudopig.fa --format=axt and compare with the expected file the way axt_compare.py does: same number of blocks, blocks in the same order, each block's header fields (split on whitespace) and both aligned text lines equal; comment and blank lines ignored; the comparison script is read here as the rule and may be reimplemented, it is not run
|
| 29 |
Companions (not included): test_data/pseudocat.fa; test_data/pseudopig.fa; src/Makefile; tools/axt_compare.py; LICENSE
|
| 30 |
Dependencies: LASTZ at 1ac92247a02c8eed85ced64d1c2d38feb7f1c6f7
|
campaign_files/2026-10-sc-science-reference-data/lammps-unittest-force-styles/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: reference_values_in_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Agent sets up pair_style tersoff with SiC.tersoff on data.manybody and reports energy/forces; compare per component with the unit test's own setting, manybody-pair-tersoff.yaml line 4 'epsilon: 2e-11'; no relaxed tolerance.
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-2.0-only
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `unittest/force-styles/tests/manybody-pair-tersoff.yaml`: LAMMPS force-style unit test manybody-pair-tersoff: SiC Tersoff energy, stress and per-atom forces before and after a short run.
|
| 22 |
Format: YAML test spec with reference values + LAMMPS input + data file + potential file
|
| 23 |
Origin: upstream unit test fixture with reference values generated by LAMMPS (upstream regression-test input with the reference values the project's own test harness checks against)
|
| 24 |
-
Reference result: reference_values_in_file
|
| 25 |
-
Reference source: manybody-pair-tersoff.yaml: init_vdwl -163.15057331304786, init_stress, init_forces, run_vdwl -163.2266634102495, run_forces; epsilon 2e-11
|
| 26 |
Check: agent sets up pair_style tersoff with SiC.tersoff on data.manybody and reports energy/forces; compare per component with the unit test's own setting, manybody-pair-tersoff.yaml line 4 'epsilon: 2e-11'; no relaxed tolerance
|
| 27 |
Companions (not included): unittest/force-styles/tests/in.manybody; unittest/force-styles/tests/data.manybody (64-atom structure); potentials/SiC.tersoff
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Agent sets up pair_style tersoff with SiC.tersoff on data.manybody and reports energy/forces; compare per component with the unit test's own setting, manybody-pair-tersoff.yaml line 4 'epsilon: 2e-11'; no relaxed tolerance.
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-2.0-only
|
|
|
|
| 19 |
- `unittest/force-styles/tests/manybody-pair-tersoff.yaml`: LAMMPS force-style unit test manybody-pair-tersoff: SiC Tersoff energy, stress and per-atom forces before and after a short run.
|
| 20 |
Format: YAML test spec with reference values + LAMMPS input + data file + potential file
|
| 21 |
Origin: upstream unit test fixture with reference values generated by LAMMPS (upstream regression-test input with the reference values the project's own test harness checks against)
|
|
|
|
|
|
|
| 22 |
Check: agent sets up pair_style tersoff with SiC.tersoff on data.manybody and reports energy/forces; compare per component with the unit test's own setting, manybody-pair-tersoff.yaml line 4 'epsilon: 2e-11'; no relaxed tolerance
|
| 23 |
Companions (not included): unittest/force-styles/tests/in.manybody; unittest/force-styles/tests/data.manybody (64-atom structure); potentials/SiC.tersoff
|
campaign_files/2026-10-sw-tests-and-exercises/kotlin-codegen-box/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is marked self-contained upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: return_value_OK. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Compile edgeCases.kt, call box(); pass = it returns "OK" (any other string names the failed check).
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `compiler/testData/codegen/box/when/edgeCases.kt`: Kotlin compiler codegen box test when/edgeCases: compile the file and call box(), which must return the string OK (when on Int.MAX_VALUE and Int.MIN_VALUE).
|
| 22 |
Format: Kotlin source with a fun box(): String entry point
|
| 23 |
Origin: tool_fixture: Kotlin compiler backend regression test
|
| 24 |
-
Reference result: return_value_OK
|
| 25 |
-
Reference source: the box() convention of the Kotlin codegen tests: a test passes when box() returns "OK"
|
| 26 |
Check: compile edgeCases.kt, call box(); pass = it returns "OK" (any other string names the failed check)
|
| 27 |
Companions (not included): license/LICENSE.txt; license/README.md
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is marked self-contained upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Compile edgeCases.kt, call box(); pass = it returns "OK" (any other string names the failed check).
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `compiler/testData/codegen/box/when/edgeCases.kt`: Kotlin compiler codegen box test when/edgeCases: compile the file and call box(), which must return the string OK (when on Int.MAX_VALUE and Int.MIN_VALUE).
|
| 20 |
Format: Kotlin source with a fun box(): String entry point
|
| 21 |
Origin: tool_fixture: Kotlin compiler backend regression test
|
|
|
|
|
|
|
| 22 |
Check: compile edgeCases.kt, call box(); pass = it returns "OK" (any other string names the failed check)
|
| 23 |
Companions (not included): license/LICENSE.txt; license/README.md
|
campaign_files/2026-10-sw-tests-and-exercises/kotlin-koans-edu/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: junit_assertions_plus_answer_span. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Replace the span with /* TODO */ to make the task, then compile with kotlinc plus JUnit 4 and run TestComparison; pass means all 3 tests pass.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `Conventions/Comparison/` (4 files): Kotlin Koans (JetBrains Academy course): Conventions / Comparison (implement compareTo for MyDate, JUnit tests).
|
| 22 |
Format: JetBrains EduTools task: task.md, src/Task.kt, test/tests.kt (JUnit), task-info.yaml with placeholder offset and length marking the answer span in Task.kt
|
| 23 |
Origin: programming exercise or course assignment shipped with its tests and expected results (was course_exercise_with_tests)
|
| 24 |
-
Reference result: junit_assertions_plus_answer_span
|
| 25 |
-
Reference source: src/Task.kt in the repo holds the solved code; task-info.yaml marks offset 97, length 198 as the placeholder (/* TODO */) shown to learners, so the span is the reference answer; tests.kt has 3 JUnit tests (before, after, same); the span is lines 2 to 6 of Task.kt (402 B at the pinned commit): the compareTo override from 'override fun' through the closing brace of the when block; when making the task, replace those lines with /* TODO */
|
| 26 |
Check: Replace the span with /* TODO */ to make the task, then compile with kotlinc plus JUnit 4 and run TestComparison; pass means all 3 tests pass.
|
| 27 |
Companions (not included): util/src/koansTestUtil.kt
|
| 28 |
Dependencies: not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Replace the span with /* TODO */ to make the task, then compile with kotlinc plus JUnit 4 and run TestComparison; pass means all 3 tests pass.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `Conventions/Comparison/` (4 files): Kotlin Koans (JetBrains Academy course): Conventions / Comparison (implement compareTo for MyDate, JUnit tests).
|
| 20 |
Format: JetBrains EduTools task: task.md, src/Task.kt, test/tests.kt (JUnit), task-info.yaml with placeholder offset and length marking the answer span in Task.kt
|
| 21 |
Origin: programming exercise or course assignment shipped with its tests and expected results (was course_exercise_with_tests)
|
|
|
|
|
|
|
| 22 |
Check: Replace the span with /* TODO */ to make the task, then compile with kotlinc plus JUnit 4 and run TestComparison; pass means all 3 tests pass.
|
| 23 |
Companions (not included): util/src/koansTestUtil.kt
|
| 24 |
Dependencies: not packed
|
campaign_files/2026-10-sw-tests-and-exercises/learn-go-with-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_map_plus_benchmark. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Go test ./... and go test -race in the package; pass means the test passes with no race; go test -bench . compares runtime of v1 and v3 (the chapter reports 2249228637 ns/op before and 23406615 ns/op after).
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `concurrency/` (8 files): Learn Go with Tests: concurrency chapter (make a sequential website checker concurrent while tests and a benchmark guard it).
|
| 22 |
Format: Go package: starting version v1/check_websites.go, target version v3/check_websites.go, unit test with a mock checker and expected map, benchmark test with a slow stub, chapter Markdown
|
| 23 |
Origin: programming exercise or course assignment shipped with its tests and expected results (was course_exercise_with_tests)
|
| 24 |
-
Reference result: expected_map_plus_benchmark
|
| 25 |
-
Reference source: TestCheckWebsites compares CheckWebsites output with an expected map via reflect.DeepEqual; v3/check_websites.go is the upstream concurrent solution; the benchmark uses a 20 ms stub checker over 100 URLs; concurrency/v2 and v3 hold the upstream concurrent versions; when making the task, give only v1 and withhold v2 and v3
|
| 26 |
Check: go test ./... and go test -race in the package; pass means the test passes with no race; go test -bench . compares runtime of v1 and v3 (the chapter reports 2249228637 ns/op before and 23406615 ns/op after).
|
| 27 |
Companions (not included): concurrency.md (chapter text); go.mod (module root; go test needs it)
|
| 28 |
Dependencies: Go >= 1.25: go.mod at the pinned commit says go 1.25; the concurrency package imports only the standard library (reflect, testing, time), so the three modules go.mod requires (go-approval-tests, gomarkdown, gorilla/websocket) are not needed; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Go test ./... and go test -race in the package; pass means the test passes with no race; go test -bench . compares runtime of v1 and v3 (the chapter reports 2249228637 ns/op before and 23406615 ns/op after).
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `concurrency/` (8 files): Learn Go with Tests: concurrency chapter (make a sequential website checker concurrent while tests and a benchmark guard it).
|
| 20 |
Format: Go package: starting version v1/check_websites.go, target version v3/check_websites.go, unit test with a mock checker and expected map, benchmark test with a slow stub, chapter Markdown
|
| 21 |
Origin: programming exercise or course assignment shipped with its tests and expected results (was course_exercise_with_tests)
|
|
|
|
|
|
|
| 22 |
Check: go test ./... and go test -race in the package; pass means the test passes with no race; go test -bench . compares runtime of v1 and v3 (the chapter reports 2249228637 ns/op before and 23406615 ns/op after).
|
| 23 |
Companions (not included): concurrency.md (chapter text); go.mod (module root; go test needs it)
|
| 24 |
Dependencies: Go >= 1.25: go.mod at the pinned commit says go 1.25; the concurrency package imports only the standard library (reflect, testing, time), so the three modules go.mod requires (go-approval-tests, gomarkdown, gorilla/websocket) are not needed; not packed
|
cards/0xdea-semgrep-rules.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '0xdea-semgrep-rules'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = '0xdea-semgrep-rules'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '0xdea-semgrep-rules'
|
cards/1brc-test-samples.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '1brc-test-samples'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = '1brc-test-samples'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '1brc-test-samples'
|
cards/2dpacklib.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '2dpacklib'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = '2dpacklib'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = '2dpacklib'
|
cards/abacus-integrate-tests.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'abacus-integrate-tests'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'abacus-integrate-tests'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'abacus-integrate-tests'
|
cards/abhishekumarr00-supply-chain-mastery.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'abhishekumarr00-supply-chain-mastery'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'abhishekumarr00-supply-chain-mastery'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'abhishekumarr00-supply-chain-mastery'
|
cards/academy-bus-nj-gtfs.md
CHANGED
|
@@ -50,10 +50,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
-
Pinned to the release tag `release-2026-11-11.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'academy-bus-nj-gtfs'
|
|
|
|
| 50 |
|
| 51 |
## Query this source at a fixed release
|
| 52 |
|
| 53 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 54 |
|
| 55 |
```sql
|
| 56 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'academy-bus-nj-gtfs'));
|
| 57 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 58 |
FROM read_parquet(getvariable('files'))
|
| 59 |
WHERE source = 'academy-bus-nj-gtfs'
|
cards/accordproject-cicero-template-library.md
CHANGED
|
@@ -52,10 +52,10 @@ Size quantiles: unknown (no size distribution recorded for this source).
|
|
| 52 |
|
| 53 |
## Query this source at a fixed release
|
| 54 |
|
| 55 |
-
Pinned to the release tag `release-2026-11-11.
|
| 56 |
|
| 57 |
```sql
|
| 58 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 59 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 60 |
FROM read_parquet(getvariable('files'))
|
| 61 |
WHERE source = 'accordproject-cicero-template-library'
|
|
|
|
| 52 |
|
| 53 |
## Query this source at a fixed release
|
| 54 |
|
| 55 |
+
Pinned to the release tag `release-2026-11-11.12`.
|
| 56 |
|
| 57 |
```sql
|
| 58 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.12/meta/catalog.parquet' WHERE source = 'accordproject-cicero-template-library'));
|
| 59 |
SELECT uri, ext, size_bytes, lower(hex(sha256)) AS sha256
|
| 60 |
FROM read_parquet(getvariable('files'))
|
| 61 |
WHERE source = 'accordproject-cicero-template-library'
|