SPB Git
spboucher.ai

spb/wp30_uqo

Public

WP30: harness scaffold, cache adapters, datasets, literature audit

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Simon-Pierre Boucher committed (Oct 30, 2026) Browse files

808 changed files +20,001 −0

808 changed files
Load all 808 files Unified Split
added .gitignore +35 −0
@@ -0,0 +1,35 @@
1+# Raw & processed data — never committed (see data/raw/README.md for provenance)
2+data/raw/*
3+!data/raw/README.md
4+data/processed/*
5+!data/processed/.gitkeep
6+
7+# Python
8+__pycache__/
9+*.pyc
10+.pytest_cache/
11+.venv/
12+*.egg-info/
13+
14+# LaTeX build artifacts (paper/main.pdf IS committed)
15+paper/*.aux
16+paper/*.log
17+paper/*.out
18+paper/*.toc
19+paper/*.lof
20+paper/*.lot
21+paper/*.fls
22+paper/*.fdb_latexmk
23+paper/*.bbl
24+paper/*.blg
25+paper/*.spl
26+paper/*.synctex.gz
27+paper/*.run.xml
28+paper/*.bcf
29+
30+# Logs
31+logs/
32+*.log
33+
34+# macOS
35+.DS_Store
added DECISIONS.md +15 −0
@@ -0,0 +1,15 @@
1+# DECISIONS.md — WP30 dated implementation and scope decisions
2+
3+All times America/Toronto unless noted.
4+
5+## 2026-10-29
6+
7+- **D-001 Project location.** `Recherche-UQO/` had only `immobilier/` and `finance/` categories and no WP29/WP30 directory. WP30 is an AI-systems paper, so a new category `ia/` was created: `Recherche-UQO/ia/cache-compression-knowledge-transfer/` (git repo `wp30_uqo`, to be pushed to spbgit `gitsrv:srv/git/wp30_uqo.git`). WP28 (`finance/distributed-mle-synchronization`) is untouched; no WP29 exists in the tree (the Russell 3000 database paper is numbered FIRC 0001).
8+- **D-002 Local backend.** Laptop = Apple M5 Max, 18 cores, 48 GiB unified memory, macOS 27.0, Python 3.12.13 (uv available), mlx 0.32.2 + mlx_lm 0.31.3, torch 2.12 (MPS), transformers 5.8.1. mlx_lm exposes real KV tensors (`KVCache.state` = post-RoPE keys/values `[B, H_kv, T, d_h]`), packed `QuantizedKVCache` (uint32 packing + scales + biases, bits ∈ {2,3,4,6,8}, used by `quantized_scaled_dot_product_attention` → genuine quantized execution), `save_prompt_cache`/`load_prompt_cache` (safetensors). This is the Track B/C white-box backend. The `cache.make_mask` hook permits sparse-retention caches with preserved logical offsets.
9+- **D-003 Models (pending probe).** Candidate checkpoints, all ungated on HF `mlx-community`, bf16 weights so weight quantization is not a confound: `Qwen2.5-3B-Instruct-bf16` (Qwen family), `Llama-3.2-3B-Instruct-bf16` (Llama family), `Qwen2.5-1.5B-Instruct-bf16` (same-family size ladder), `Qwen2.5-7B-Instruct-bf16` (larger receiver, if memory allows). Final choice after `models probe`.
10+- **D-004 Hosted track budget.** No API key is in the shell environment; `.env` files of WP26/WP27 (same research folder, same author) hold Anthropic/OpenAI keys used for prior UQO papers. Track D will run only after a live probe succeeds, under a hard cap written in `configs/resources.yaml` (initially 25 USD total), and only on public/synthetic data. Local experiments never depend on it.
11+- **D-005 Cluster.** MacLustr nodes are used only through the existing SSH configuration (`~/.ssh/config` aliases) for genuine two-node cache transfer (E2/E6). No network scanning.
12+- **D-006 Numerical tolerance for cache equivalence.** Measured on Qwen2.5-1.5B cast to float32 (all 338 parameter tensors fp32): max |Δlogit| between a one-chunk prefill and a token-by-token prefill is ≈ 0.10 (logit scale ≈ 30), max |Δprob| ≈ 7e-7, KL ≈ 3e-8. MLX kernels are therefore not bitwise deterministic across chunkings even in fp32. Registered criterion for "equivalent": KL(ref‖test) < 1e-5 and max |Δprob| < 1e-4 and identical greedy top-1 in fp32; KL < 1e-3, max |Δprob| < 1e-2, identical top-1 in bf16. Identity round trip and 100 % retention must be exactly 0 (they are).
13+- **D-007 Qwen2.5 4-bit KV finding (smoke, not a result).** Both the native mlx_lm path (`generate(..., kv_bits=4)`) and the WP30 adapter produce garbage at 4-bit/group-64 for Qwen2.5-1.5B while Llama-3.2-3B survives even 2-bit/group-32 on the smoke memo. The adapter is therefore not the cause; this is the per-token affine quantization of outlier-heavy Qwen keys (the KIVI motivation). Registered as hypothesis H2; a KIVI-inspired per-channel key quantization is scheduled as a *transport-only* variant (B2b) and labelled "inspired".
14+- **D-008 Task families.** (i) Synthetic private-fact ledgers (generator `wp30.data.synthetic`, 15 question types per document incl. unanswerable; evaluator-only keys); (ii) public LongBench v1 subsets qasper and 2wikimqa (all 200 items each; hotpotqa reserved as a 16K-extension subset), raw jsonl from THUDM/LongBench `data.zip` because the HF loading script is no longer supported by `datasets` 5.x; (iii) executable tasks (`wp30.data.exec_tasks`, hidden tests in a `python -I` subprocess). Family (ii) is likely in pretraining corpora; family (i) is not.
15+- **D-009 Remote node.** M3U96b (Mac Studio M3 Ultra, 96 GB) is the second node for genuine two-node transfer: `~/wp30-worker/.venv` with the same mlx/mlx-lm pins; both 3B checkpoints downloaded there. iperf3 available on both ends for link measurement.
added STATUS.md +7 −0
@@ -0,0 +1,7 @@
1+# STATUS.md — WP30
2+
3+**Phase:** 0 (environment + scope) — in progress
4+**Completed gates:** none yet
5+**Current task:** environment inspection, literature audit launch, model download
6+**Blockers:** none
7+**Next command:** `python -m wp30 doctor --output evidence/environment.json` (after package scaffold)
added configs/data.yaml +21 −0
@@ -0,0 +1,21 @@
1+# Dataset construction (deterministic). Seeds define split membership; keys are written to data/generated/keys (evaluator-only).
2+synthetic:
3+ n_projects: 6
4+ lengths_tokens: [2000, 8000, 16000]
5+ # seed ranges by split (disjoint; template families identical, entities/numbers differ)
6+ splits:
7+ train: {start: 1000, count: 40} # mapper/calibration/prompt tuning
8+ dev: {start: 2000, count: 30} # method selection, router fitting
9+ test: {start: 3000, count: 40} # locked; first evaluated at Phase 8
10+ length_assignment: round_robin # each seed gets one length: 2000, 8000, 16000, 2000, ...
11+exec:
12+ splits:
13+ train: {start: 1, count: 20}
14+ dev: {start: 101, count: 30}
15+ test: {start: 201, count: 40}
16+ target_tokens: 2000
17+public:
18+ subsets: [qasper, 2wikimqa]
19+ extension_subsets: [hotpotqa]
20+ split_rule: "sha256(document text) last hex digit: 0-3 -> dev, 4-f -> test (dev ~25%, test ~75%)"
21+ max_context_tokens: 16384
added configs/models.yaml +8 −0
@@ -0,0 +1,8 @@
1+models:
2+ qwen3b: {repo: mlx-community/Qwen2.5-3B-Instruct-bf16, family: qwen2, role: [sender, receiver]}
3+ llama3b: {repo: mlx-community/Llama-3.2-3B-Instruct-bf16, family: llama, role: [sender, receiver]}
4+ qwen1b5: {repo: mlx-community/Qwen2.5-1.5B-Instruct-bf16, family: qwen2, role: [receiver_small, smoke]}
5+probe:
6+ prompt: "Project Varkolith-7 has supplier identifier ZR-77Q-0931."
7+ question: "What is the supplier identifier? Answer with the identifier only."
8+ context_lengths: [2048, 8192, 16384]
added configs/resources.yaml +23 −0
@@ -0,0 +1,23 @@
1+# WP30 resource guardrails (enforced by the runner; a trial must not silently expand a cap)
2+hardware:
3+ local_node: laptop-m5max # Apple M5 Max, 18 cores, 48 GiB unified memory, macOS 27.0
4+ remote_nodes: [M3U96b] # MacLustr, LAN 192.168.2.85, mlx available; used only for E2/E6 transfer
5+limits:
6+ trial_timeout_s: 600 # one attempt; timeout recorded as censoring bound
7+ batch_timeout_s: 14400
8+ max_concurrent_workers: 1 # single-model execution per process; Metal is not time-shared for timing trials
9+ memory_guard_bytes: 40000000000 # abort a trial if mlx active memory would exceed 40 GB
10+ disk_allowance_bytes: 150000000000 # runs/ + data/ + models
11+ max_context_tokens: 16384
12+budgets:
13+ api:
14+ enabled: true # keys found in sibling WP .env files (same author); probed live 2026-10-29
15+ hard_cap_usd: 25.0 # total for Track D; runner stops scheduling hosted trials beyond this
16+ providers:
17+ anthropic: {model: claude-haiku-4-5, max_output_tokens: 256}
18+ openai: {model: gpt-5-nano, max_output_tokens: 256}
19+ training:
20+ mapper_max_device_hours: 6.0 # Phase 6 learned mapper (if run); checkpoints saved every epoch
21+retry:
22+ max_attempts: 2 # first attempt + one retry on implementation_error/timeout; both kept
23+ retry_on: [timeout, implementation_error]
added configs/smoke.yaml +30 −0
@@ -0,0 +1,30 @@
1+experiment_id: E0_smoke
2+splits: [dev]
3+families: [synthetic, exec, public_qasper]
4+lengths: [2000]
5+limit_docs_per_family: 1
6+max_questions_per_doc: 4
7+model_pairs:
8+ - {sender: qwen3b, receiver: qwen3b}
9+generation: {max_tokens: 48}
10+seeds: [0]
11+conditions:
12+ - {method: A0}
13+ - {method: A1}
14+ - {method: A2, budget_tokens: 512}
15+ - {method: A3, budget_tokens: 512, access: blind}
16+ - {method: A3, budget_tokens: 512, access: aware}
17+ - {method: A4, budget_tokens: 512, access: blind}
18+ - {method: A5, budget_tokens: 512, access: blind}
19+ - {method: A6, budget_tokens: 512, access: blind, max_fetch_bytes: 2000, max_lookups: 6}
20+ - {method: A7, codec: zstd}
21+ - {method: B0}
22+ - {method: B1}
23+ - {method: B2, bits: 8}
24+ - {method: B2, bits: 4}
25+ - {method: B3, keep_frac: 0.25}
26+ - {method: B4, keep_frac: 0.25}
27+ - {method: B5, keep_frac: 0.25, access: aware}
28+ - {method: B5, keep_frac: 0.25, access: blind}
29+ - {method: B6, keep_frac: 0.25, access: aware}
30+ - {method: B9, keep_frac: 0.5, bits: 8}
added data/generated/docs/exec/exec_00001_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00001_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7019: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 47.53, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 4.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 25, \"unit_price\": 71.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 9.99, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 50.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 26.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8073,
7+ "document_hash": "ddfe7fcc3baca3e97144b66188f285a0e8a83018d1ca41b7f37cb80dede62dcc",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00002_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00002_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6302: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 5.2, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 14.07, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 51.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 37.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 67.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8001,
7+ "document_hash": "7918e3cdcab2a8bfae77558b7b523f4cea70cdc52435393d98d0c7b36de29e60",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00003_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00003_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6542: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 35.12, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 47.96, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 27.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 8.05, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 37.32, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7972,
7+ "document_hash": "8ab845867bddfdcb5cf63b1319a6f29794cc9dddea45cd92bca3bc94fe023da7",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00004_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00004_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4473: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 66.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 75.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 70.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 56.79, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 16, \"unit_price\": 23.1, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 64.58, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8037,
7+ "document_hash": "08c5cdfaa7a0742a094ee4726d97a32a89395c354270406bbcf78eff4fdbe8b2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00005_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00005_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1004: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 9.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 9.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 26.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 12.59, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 4, \"unit_price\": 49.06, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 38.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8031,
7+ "document_hash": "f885d791d02ed1adb010c9c27804b5c38facf8fd2a09b9b1b6f9cacb7b0acc81",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00006_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00006_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2483: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 51.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 16.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 75.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 55.85, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 45.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 32.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8049,
7+ "document_hash": "2a1bb6d86c77861b166e281bb1deac9a658ed4383a7ade93e9698e33861de0e5",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00007_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00007_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6853: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 15.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 21.54, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 27.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 48.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 59.99, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 79.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 9}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 7826,
7+ "document_hash": "fb0150ce17a4b0ade1601cf6082b82e83f67db83a57c177064777d028b33d97c",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00008_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00008_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9591: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 27.18, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 55.08, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 28.44, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 59.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 79.85, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 26.43, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8052,
7+ "document_hash": "04f896fa681f3ae7cbfc7efa30fd96c43be9d9b703dab76457ee8043483b3612",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00009_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00009_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4251: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 10.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 5.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 46.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 44.75, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 42.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8097,
7+ "document_hash": "db44cbab6b33239dddaa205976960167be792c1b1025bd39a4c4d6cf0f6ab7d7",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00010_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00010_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7892: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 25.77, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 67.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 78.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 47.19, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 61.6, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 64.37, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8004,
7+ "document_hash": "232fe52471a905a3ae14b591781c17dfa57a2d115258bfc1f8a1fce231b705ad",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00011_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00011_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1386: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 66.05, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 28.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 44.45, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 7, \"unit_price\": 66.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 6.84, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 64.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8135,
7+ "document_hash": "f046c8292307adf97cae067d41f5a7bcce9d2a48bc8dd143e0f11e89a1c3a4c2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00012_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00012_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3390: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 45.84, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 28.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 22.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 52.18, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 46.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 7906,
7+ "document_hash": "2befcba5bfd5b509a9a6ec5d9334e2e384a05b6733ac02d80222302d3ca6e6ef",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00013_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00013_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8332: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 19.02, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 31.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 6.76, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 50.8, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 70.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 29.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8051,
7+ "document_hash": "d006207e385cff8703be29071faf5845de84d05d8a677e40dda4983739115d29",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00014_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00014_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7580: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 20.49, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 61.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 28.29, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 53.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 5.5, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 60.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8089,
7+ "document_hash": "e6ac9234df3fc7dcec86770e041bf75b576d1c65cf6fe32717891429f5461066",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00015_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00015_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7400: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 44.28, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 77.11, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 37.27, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 24.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 49.63, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8041,
7+ "document_hash": "7bd733e903db470812271aa82f1cd9c7111ace0dcd257ace35b07e660d045be7",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00016_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00016_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8263: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 16.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 13.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 31.16, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 76.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 43.73, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 41.2, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8045,
7+ "document_hash": "b232fee620440e55facf033b892741387c97661b269dc2371313fb0f5934ff69",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00017_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00017_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-5234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 71.87, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 57.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 63.43, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 39, \"unit_price\": 73.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 41.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 17, \"unit_price\": 36.3, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8053,
7+ "document_hash": "bce532bd3702b32e6eb3620ef3ea7d860a695f22bb90b8e995836a7937c77f52",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00018_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00018_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3864: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 62.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 68.54, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 63.9, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 71.94, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 9.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 26.85, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8169,
7+ "document_hash": "6f0951d7af338593059efbe431f0b7ce5bf9ae652e3dfb9eedafa7e192b80c01",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00019_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00019_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4945: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 55.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 5.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 35.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 18.49, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 38.49, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 40, \"unit_price\": 46.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8031,
7+ "document_hash": "733853d52a559dfc67d0cdab02de9e21c2aa09e0b25702d2cadfb38c20ab2159",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00020_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00020_2000",
3+ "family": "exec",
4+ "split": "train",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8600: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 77.87, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 51.72, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 67.82, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 22.1, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 49.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 8080,
7+ "document_hash": "1a7bfffc3347254640c8b76b9b5f0ff368a758543995fa06006e28ea43d8eb71",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00101_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00101_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 53.66, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 17.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 66.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 33.18, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 47.37, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 22.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8125,
7+ "document_hash": "932bac511f2c5ee3faf8c1f37b853fcd2be373db29c6a84b2d7f8c3ab71ee6f9",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00102_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00102_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4681: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 68.35, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 65.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 17, \"unit_price\": 8.56, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 36, \"unit_price\": 48.5, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 22, \"unit_price\": 76.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 51.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8089,
7+ "document_hash": "5535ac3109616f7d46dff5417535ca232754aee2c0759e072d552e465f004d46",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00103_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00103_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1178: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 24.8, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 13.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 26.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 10.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 34.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 17.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8038,
7+ "document_hash": "a7875d1e95742c6246c4ec3862b9797a4269a2b607e47869f5014d7dc29139e0",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00104_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00104_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6532: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 26.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 59.29, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 50.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 74.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 40.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8014,
7+ "document_hash": "bce3091895fc315bf981ac1272a7da1f00b0f64819f1ecfa2a6dd8a3d23f2207",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00105_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00105_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2817: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 44.66, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 12.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 71.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 69.08, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 71.78, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 17.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8046,
7+ "document_hash": "fe4b8857bf1774be1123bec85a5743da5c3551d53125ddf128efde401f3990c2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00106_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00106_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8363: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 66.67, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 69.05, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 67.57, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 49.2, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 40.78, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 31, \"unit_price\": 40.56, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 7943,
7+ "document_hash": "c3652bfa1632f0cc62d6512131ef519100143881225c8b4ee572c1876e7c6c7f",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00107_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00107_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7434: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.74, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 4.67, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 67.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 10.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 61.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 16.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7930,
7+ "document_hash": "983dbcacdfae2acf0316690a7fe50cfa2523ae41beffd9de42356f2ebd3d1e79",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00108_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00108_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-5898: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 59.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 47.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 24.32, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 53.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 33.13, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 58.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 8038,
7+ "document_hash": "7ebb05d3714e237d074dfc9a69c5b83e99932f9041b5d4fe15c8fc7224ba7078",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00109_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00109_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1880: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 14 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 16.34, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 77.14, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 21.7, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 65.34, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 36.24, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.17, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8073,
7+ "document_hash": "680dab47e67683cb351941eea647197cb2b2ea472ff116582019ace0c543d461",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00110_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00110_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 48.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.65, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 52.8, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 30.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 18.59, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 26.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 8019,
7+ "document_hash": "f1699da28903736ad58ec0640a277bb2eac030c80c49c22c027c273374df86fa",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00111_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00111_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8832: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 74.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 62.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 46.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 49.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 62.57, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 38.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7942,
7+ "document_hash": "e65e9534b60b15cdaadf465396c6385868f5a0ed4be5ba04c458937c2eff43ae",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00112_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00112_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1935: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"gamma\", \"units\": 4, \"unit_price\": 38.52, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 13, \"unit_price\": 23.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 18.69, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 55.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 19.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 61.42, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 7996,
7+ "document_hash": "4a8db801f5e7f6b2108618514f90c37fbdbb61e902c4441c0d68548a5792da05",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00113_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00113_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7037: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 39.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 5.13, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 20.94, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 3.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 42.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 3, \"unit_price\": 57.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8055,
7+ "document_hash": "7535b4d324a3e28b457e40fe41d18d52e75a9ed0271b411285e522c6c8c8200e",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00114_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00114_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7391: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 39.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 65.95, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 38, \"unit_price\": 38.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.5, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.46, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 10.31, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 6}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8042,
7+ "document_hash": "e1faab8175075b8cf98d2e5e16181db3f5a8f103ed89d35efee7ba4684968699",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00115_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00115_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4157: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 62.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 35, \"unit_price\": 64.7, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 29.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 17.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 53.93, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6+ "char_len": 8127,
7+ "document_hash": "4d6a9aa137c992493ef42f6758dbb35b873a4a392b00eae7152d6e45b68a3c1b",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00116_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00116_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8712: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 40.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 3, \"unit_price\": 67.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 21.59, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 21.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 30.51, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 66.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 7941,
7+ "document_hash": "2b6100ff4b04865ebf622b9749757f3b32215faa2e32f12d63be71b0c18fc7be",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00117_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00117_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8902: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 34.17, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 39.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 37.26, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 13.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 4.12, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 1, \"unit_price\": 4.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 8064,
7+ "document_hash": "6e53d886a35d8e51c98908f1e40e9314353c62a19e3197603509fd2a59c6bbf3",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00118_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00118_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8999: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 68.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 35.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 65.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 2, \"unit_price\": 53.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 48.57, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 8050,
7+ "document_hash": "5353584056feb451c43bd2199aa87e2f7064bbfb9485b6eb1f6a1387dddac0f6",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00119_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00119_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6430: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.28, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 28.27, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 56.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 58.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 21, \"unit_price\": 7.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 10.91, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 7901,
7+ "document_hash": "f62c9b5ecd91caa0cf95af49bf6d40dd2bc3885255008434f482e56b7a2a2fae",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00120_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00120_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6138: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 26, \"unit_price\": 76.39, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.78, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 55.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 48.6, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 31.92, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 33.32, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7992,
7+ "document_hash": "5b1b1089a793b0953579b8ce004efe99282ffd8a6eb17b16c3ce50273c121aad",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00121_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00121_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6726: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 48.97, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 58.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 78.34, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 65.31, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 52.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 37, \"unit_price\": 9.99, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 8033,
7+ "document_hash": "9064e893e331010c27db6e1229c2af7da83ed7fb3680e079fc5c1a9ee7b2d73a",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00122_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00122_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 43.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 74.34, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 31.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 12.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 24.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 38, \"unit_price\": 69.36, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8139,
7+ "document_hash": "8641f3a09b033f2a216948ea197682c280cda7a9559b7102473da5f152a73eb3",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00123_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00123_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6186: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 44.11, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 43.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 27.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 15, \"unit_price\": 68.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 49.94, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 57.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8069,
7+ "document_hash": "3a8a85801b1200bb0a18063e20eb67097e3e9c34d009894a5a61963f7145608b",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00124_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00124_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4820: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 15.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 16.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 32.63, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 22.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 53.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 66.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7919,
7+ "document_hash": "adfa94aa242540ae900f58c2db73dace6e0bb6ec243a71137685b2d527e54fdb",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00125_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00125_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8156: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 74.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 79.31, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 24.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 61.06, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 48.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 73.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 7915,
7+ "document_hash": "144a4af055228fc4045ad15b1ca9ba8229c8e5563cc4c4cf9ad94203a0072dd9",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00126_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00126_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1488: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 14.21, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 40.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 66.39, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 5, \"unit_price\": 58.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 35.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 51.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 7944,
7+ "document_hash": "a6bed1ca1c6bee001ded092712010d4dc8d3ec10d0d1f85432e8844be28b9359",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00127_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00127_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4907: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 4.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 57.56, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 48.4, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 7.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 49.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.89, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7953,
7+ "document_hash": "01e9b8b715cbfdd0d66c26d571044c18f9a6d9d2c5146b834291716879cf02d2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00128_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00128_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7370: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 33.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 74.94, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 71.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 69.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 38.14, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 7945,
7+ "document_hash": "e702731f232f4b91d0513add4b301fd1ef0382eee35df22a98cef7eb727fafca",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00129_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00129_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2059: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 2 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 31.69, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 44.06, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 28.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 18.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 32.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 10.85, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 7973,
7+ "document_hash": "e508132470ec83c8745c1899d6c954b865130cad33382718fa48d35d6bea0ec8",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00130_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00130_2000",
3+ "family": "exec",
4+ "split": "dev",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7512: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 4.14, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 3.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 18.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 23.95, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 17.39, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 71.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8072,
7+ "document_hash": "c65f14fbcb1d4d0049a6e641be2826817637866851032f95c4cc1943f87ff809",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00201_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00201_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8684: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 5.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 15.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 54.9, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 7.38, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 33, \"unit_price\": 19.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 43.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8073,
7+ "document_hash": "876f090ca1801217ec4295964e7d9ce5b46b9fc96b04db7ca463d6cc8ed74978",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00202_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00202_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1160: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 68.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 71.74, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 31.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 43.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 5, \"unit_price\": 75.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 76.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 7844,
7+ "document_hash": "660fc77600d7958889cef9b34f9c9a1a8c2d96ef38db054d180f225ebe3d4a42",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00203_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00203_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-7417: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 73.68, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 40.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 27.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 78.27, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 49.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 53.29, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 7967,
7+ "document_hash": "f26e049133c3f806d2045fa255ba4e6c2594f5ecbe872414b75faaf52ceb5033",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00204_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00204_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2345: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 22.64, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 40, \"unit_price\": 49.16, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 47.27, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 36, \"unit_price\": 38.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 29.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 22.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8100,
7+ "document_hash": "7cc296695d97fdf8fb07de5772744af9c3a79a52f20ee1e3410187cac4dd94b2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00205_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00205_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9090: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 21.72, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 33.96, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 7, \"unit_price\": 20.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 24.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 29.74, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 1, \"unit_price\": 9.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8061,
7+ "document_hash": "1f9b534774ca095126415c70bc29f4400d55f083ec020a658e6ee1263a76072f",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00206_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00206_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 41.55, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 10.75, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 79.56, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 44.39, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 12.61, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 35.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 7908,
7+ "document_hash": "71e5bf98eb246c53babd99cdd8ec1212e594a1af3ddd2a6da69bac721ad65ddd",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00207_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00207_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3534: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 61.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 57.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 30.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 25.39, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 54.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 66.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6+ "char_len": 8035,
7+ "document_hash": "2273befa734c54f0d780db1126ec3ce69ce8f9f829e57586a614786258681ba3",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00208_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00208_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9673: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 34.08, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 10, \"unit_price\": 62.88, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 63.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 23.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 78.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 32, \"unit_price\": 71.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 8036,
7+ "document_hash": "e22e990c3c20d7feee2f70e993961e465ac68d3a867c3547dc0566739847c2d8",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00209_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00209_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2760: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 42.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 72.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 23.31, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 63.77, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 32.46, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 52.71, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8044,
7+ "document_hash": "bd895760d266f605848302775beaceb129633108ddc74dcbe83a8642eecb0ea3",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00210_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00210_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6939: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 64.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 76.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 77.13, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 33.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 77.57, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 19.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7990,
7+ "document_hash": "2678fb8184c3c22ce8bfa861af1a68ef2704dd84cb88718d63c1b668adaf1f69",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00211_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00211_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6353: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 44.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 18.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 19.62, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 61.32, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 64.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 15.18, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 8091,
7+ "document_hash": "5ad4fd06e4149025eddafab6fbf5c707e06c1f7e47f3cbaec839f52cd6744e38",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00212_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00212_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8815: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 38.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 5.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 68.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 31.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 68.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 17.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8061,
7+ "document_hash": "8a171bf76e4dc9c8921e9b2a4370fc5385ceb9695d62d19fc693110c84df06f0",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00213_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00213_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9971: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 6.93, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 72.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 79.31, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 20.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 16.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 59.43, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 7876,
7+ "document_hash": "55fc33fe81ccfe25e3ebdcdb70ee135b990fcf94d02bfb56e0116982ffd6df6f",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00214_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00214_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6115: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 62.71, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 20, \"unit_price\": 4.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 37.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 54.43, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 24.23, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 14, \"unit_price\": 46.97, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 7997,
7+ "document_hash": "0be81f6d80f5eb03ba862cbc94c8bf20b6ab1196483c947401585e7178fd458d",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00215_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00215_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9778: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 33.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 2.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 34.09, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 66.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 32.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 39.54, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6+ "char_len": 8073,
7+ "document_hash": "37b95a047621c2a78beaff095b27647064c994bf6ede6ef6b3e91f8296b70eff",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00216_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00216_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-5343: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 19.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 57.35, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 56.48, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 70.24, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 66.63, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 33.67, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8017,
7+ "document_hash": "1deddf301b0b2291cb9bdc4213848eceb17ece12032a2e454bcceb4ca4174397",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00217_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00217_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1928: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 71.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 23.77, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 22, \"unit_price\": 39.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 40.72, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 36.45, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 51.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 7946,
7+ "document_hash": "7f71cb12d994e6fe2646a0f7b337c441f923868ec6b21c29533122fda4d87a73",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00218_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00218_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6421: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 69.57, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 11, \"unit_price\": 53.59, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 77.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 24, \"unit_price\": 22.35, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 79.4, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 20.83, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6+ "char_len": 7955,
7+ "document_hash": "2a77fd38142317b7e8868dfcaebb42248ddd462e9339268378a26e4b587eab3d",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00219_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00219_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-1173: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 79.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 39, \"unit_price\": 77.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 27.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 6.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 50.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 13.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8119,
7+ "document_hash": "501d502ac1cd6920ddaeccbc4f0c925ddf4ca966cfb601ffd9d0547d97a741ed",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00220_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00220_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6509: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 67.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 37.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 44.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 27.9, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 7.8, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 61.13, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7931,
7+ "document_hash": "a7487c2eb12039fcc44c64460641febdd19eaf0e13d8b6b8f00d018ca564a8b6",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00221_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00221_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8588: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 1 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 12, \"unit_price\": 67.75, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 38.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 52.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 29.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 7.64, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 39, \"unit_price\": 27.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 7820,
7+ "document_hash": "a986eec8e76aa658fd694272657b8e201d940be0671e7769a934ffe76ca4748a",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00222_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00222_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4818: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 13.55, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 25.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 19.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 79.51, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 42.07, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 57.83, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 9}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8057,
7+ "document_hash": "fa31c738b8b80170524adedf048965eb739a7ebf7de9fcd4f4192d331dcc3346",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00223_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00223_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4982: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 19.44, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 15.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 51.74, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 11.86, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 33.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 44.89, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7992,
7+ "document_hash": "9b2d718a88e7b451a6e6d433e81fa6c3862777588f40791fe888b2d7a44efa42",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00224_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00224_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2924: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 40.1, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 74.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 67.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 44.81, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 79.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 60.0, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7921,
7+ "document_hash": "526a53c484a99dde8d83b8fc83d103060128d6331659920d7688b8836de1ec53",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00225_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00225_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3204: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 5.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 25.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 22.38, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 3, \"unit_price\": 5.01, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 70.26, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 5.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 7998,
7+ "document_hash": "0d5d08bcef45a939605c15cb0d0b5b1ac3c2304c8358dae05fa7da75db07621f",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00226_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00226_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9781: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 13.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 77.55, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 40.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 65.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 43.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 50.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7972,
7+ "document_hash": "32ca9297d301e1956917680ad370eda2add0304f9742c49a2023cfa3f2a82bd2",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00227_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00227_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4863: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 60.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 16, \"unit_price\": 74.12, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 66.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 49.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 14.6, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 54.41, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6+ "char_len": 8074,
7+ "document_hash": "0297d0253d8ecb7ba91156d4221aff1d54ba5efaed7fe7664734e63d44d31bd0",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00228_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00228_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3241: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 76.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 29, \"unit_price\": 33.94, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 14, \"unit_price\": 14.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 4.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 52.45, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 77.48, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7994,
7+ "document_hash": "7bd8eb7ac7409f89d5f44f1f5001fd0660aece03d12d92588e821c86e0d1f69b",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00229_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00229_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2051: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 76.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 78.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 41.6, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 3.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 31.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 7905,
7+ "document_hash": "488c5efd60f8e64b88269226071b8befe058a5e2442b99934157b38f5fc41a19",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00230_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00230_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-9897: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 34.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 36.88, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 42.84, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 25.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 20.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 69.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6+ "char_len": 8012,
7+ "document_hash": "2e09e5c09991cb1b7c5c288b9a49bb058042a17dc7fd32cde98e2b705477598c",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00231_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00231_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8917: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 34, \"unit_price\": 42.27, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 66.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 77.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 28, \"unit_price\": 73.35, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 48.71, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 4.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8077,
7+ "document_hash": "9071b939e284c02834a84c70b2af1783b2a26d6217aa2184b3224f0c27400eaf",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00232_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00232_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-8049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 25.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 75.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 65.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 7, \"unit_price\": 59.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 11, \"unit_price\": 48.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 30.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6+ "char_len": 7990,
7+ "document_hash": "6bb55261f58b559a6304971baddf54cabc7de9843d30afe350a659e21fa02b73",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00233_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00233_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-6605: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 40.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 16, \"unit_price\": 13.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 1, \"unit_price\": 30.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 77.63, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 21.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 7.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6+ "char_len": 7909,
7+ "document_hash": "f88eb8610ee0ae9a0cc4c953e6f302bceb7e6a9f131c2e5f775a4026d048e997",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00234_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00234_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-3367: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 64.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 43.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 31.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 28, \"unit_price\": 16.65, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 40.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 33.7, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8006,
7+ "document_hash": "89b49129e4581b4b424c4986c040ee62a62ff6f482d53151d96cbcf944c97e02",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00235_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00235_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-2404: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 16 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 21, \"unit_price\": 57.5, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 43.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 70.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 13, \"unit_price\": 4.78, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 3.2, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 1, \"unit_price\": 74.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6+ "char_len": 8079,
7+ "document_hash": "7870795b3e6c98bee59eb42d0e036ccc1d88fe696a6e7c94016c77fb0f3cefe4",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00236_2000.json +15 −0
@@ -0,0 +1,15 @@
1+{
2+ "document_id": "exec_00236_2000",
3+ "family": "exec",
4+ "split": "test",
5+ "text": "ENGINEERING TICKET\n\nBug report BR-4238: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 35.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 13.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 55.74, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 26.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 20.92, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 33.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6+ "char_len": 8048,
7+ "document_hash": "dabe94079fad1aa1fef7653ff5583522be249aa0c33c58334ae1d261091d83f9",
8+ "questions": [
9+ {
10+ "question_id": "q00_exec",
11+ "qtype": "exec",
12+ "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences."
13+ }
14+ ]
15+}
\ No newline at end of file
added data/generated/docs/exec/exec_00237_2000.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/exec/exec_00238_2000.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/exec/exec_00239_2000.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/exec/exec_00240_2000.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_018c9c2d781ea2c9d57a31bd2e0ff30b55e77017a319484a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_025911ff0afd34976b0a800c198c4117f95edfcd7b64bb24.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_048e82b64b5651b74d452db7151c2110a718128dfd12a774.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_059802de84ebd63ee99284c9cb2b7db2d45ca66c55e68ee1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0a64d8873482d91efc595a508218c6ce881c13c95028039e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0bcff697444354703dd1e8987a709b8ed2f44bf9d6b2d320.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0c15fb826ac59bbde9df698db9c277def2bc72fa5b7b497d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0c35123885c26fc474a7cd8e7c03fe75bfff4fc15845d3b9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0c43156b7d6bc17425a89dc6c6d48fc8c2c72ac9eba55a87.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0c4dd15b43d1061d372c11946aa71630926e2570f333f538.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0c8d9e57340d06b13e75f1dd42ddb5f08c1203fb62632353.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0cf27c68148c99571860af561ce5f64c4524fde278defc63.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0d02726cbaab0fbd2e84b7537550154e8aa96f81abb2864b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0ef1c3ac6b07212a6d5a91bfab2c12f2823412f10f667616.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_0f629fbc7a6c3689ee9771af3aa81400674e673f11d47f2d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_1038dcf795ffefdb5d947e54a7e2d3b04d73895e482fd324.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_10dc2bd4f7fb1b834c7f563ae3d7af5d269d84b3dfc0b056.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_13c4f5388b670f6c20b168e782f7478616fa3ba2edca3081.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_13dde588b81d1de4a9984418bf3d6791de7d1b1edf21d61b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_184929a3ff00c41a966da9d53444da794af70ce90d624205.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_188123e1b35a7de33fc44a40b55ab9ff0b59d29dc30f9148.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_1d38c4b905f131417ce218eb86f68305a10160f9757cbeca.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_1d554e7ae21ed7b5d142b57bcdab110cf6cea6f5256a58ee.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_1edc61803f35344a5a4b6d273e6eb0f643fefcec0fa0a22a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_1ff4dc6c1f7c02445945ced1b35a08544d7ba76089675883.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_236eb4a8c2ba63d96ed3b6aec9ff7b00fa5e4df1173dd01c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_24591a37ff748fb849a62e6a4f4095f7089d7ced43595d01.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_24a43c1b071d8bb99f51fec368dbc438cf7aea1f549ea195.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_24e27e943be014d4549674d581cdc20fdae92fa3d9cd256c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_259c17d6e4a5e4c74669836fec3c6de0730bf65e67e6d988.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_259e029da053a54f862f2455f3b92fb5f1b810647f1c1825.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_25b5c6893c13f6e52ddd541c03f5bd6bb7b17cfeb15d9f16.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_29ec971fbdf0df2d0c41c497de945024db6159c0c30be307.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2a0554b724822b6c611539e39b44381f752acdecce4868ad.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2a398d925d3607c94ffb2d0cf9fe2fe6da6e9970ce95578a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2c605656720054b6c9e6e0f15f99c1b4675db67e6e098cee.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2c952e3e1ca394df975103b3135b3c38e0ee16e25d860258.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2ce836524b90befee94e944e77ce3420878e75b5a1e14c26.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2d1951b62f317038d28f6ac6a2b21e9d2e7f921ea528948b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2df722c08f52cbf987c84019f7f2e5455cd29992738441cc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_2e86241a9d27925aa52e039067fa83e27e305301188daef7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_300ccba91f776e583d418d6d9ecc5e1bdca7bd80580cd36e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_314e76591d11d30d2bd59b2f12b671e873b786656f19956d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_32092cc7b80094b9c8914c1f70000295aefc4a985747b0ed.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3292d2bcbbf8fc4816d168bcb7f81c13341198da1e88b903.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_33e3bc2dc011e79c047553153b1ab176c6a08f923af245ec.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_34896de8d6a2c70e09b6dc3d113475a58899961d2aa356b3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_35cbcb102aa5b4f9188011190e0f30456df5673fcddacf49.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_35ffcf04ff64965decfcd3d34ff37b35da2a92f0b64346cd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_37022dee1597491021c2aa7522276a600eb0dd316f12cbb6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3723ec96e3b1af88c73edaa0a5e87f20194d9d212a67b615.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3816f7d8e90a5497a1c0e415bf25218037c690e8e4d0d016.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3924e4ac5039ce3fadda49604bfcb0f5238af81774616e53.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3cff7074281c58717aa65021d875cc1e6a6321f71cd77742.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_3ee59c959e64a29c8a30263816ad47b76ffab36e5b8859ee.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_40de6f6c353c080845a8ea644039e9ba83cd481d3745395b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_41ac2a4beb0af8f58d01863a62b90692f7c7d74b5e3a58d9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_435fae9b23d8b22e85a57cfd8ceb8541dea5b0c551acc3a9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_43cf26663f3b4cec7a8ea68d56909201a2d1b1ad82512190.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_4413705182b57f12dc553e0919b50fd3c3b111cb4d82d12f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_44864cf7bbca78294d1b24c5acfa035f30849d802356aad4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_44b7f326c7b3c430968c237ee4017425d03eef586d5d6cb7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_47ed89f40cae521df8767b1b7077fe9c547c10fd8bf1c6b2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_49035ecce6e78a355307dd6a1ddb11a87cab76090d655d2f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_4b28d517ce1c1e3cfec9282ca7b212c1cb87c254781d7c86.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_4db5bcd1d49fce674507d9128850eb71b808b7dc4246e882.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_517da14d56782303ccf8ec057b86bf43169b6f2edcd6d0f1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_538d0eac8ec082e93d6f273237fafd1f23fb405e35bad84e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_53f6acc70a61443a93c25c91ca7dc7f8780046d02e28c94a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_5421c1e591296d64636a7e99fbfe98dddfed0f83d2053380.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_544828db02efd1313bfc0a1bdeb8c3df5985c299254b0222.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_550f734c7ef908fcfe6b1b7e761826340f00abaa5eb305a0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_55acb15a501d22031778ff4ccb655e787668b617d911daa9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_56db201f810a3d01b7d14e8e9e6dd94820ecaf2f4a86b2b9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_57543e0892f90733bf97dc270cdb36eb9bf8e2230940bcb9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_57db7adad0b62b8a396fd45937030d876ecd02153b8a931e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_58301315eaee3256c8f5ddefb03de59d55a75d3a37aab88a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_5844352bd3fe5898756970abec3099ec694be6ad15c498db.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_59e42b2cab6da2436fae05e25c49f6f4b4893b07bb48e3c1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_5a867841d94c9f88f3bc0c333e93484486b09341db474bd6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_5c3829f10f9daf565e9b5b52ca19f5c044550e916479da74.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_5ff6349ea0b2ecb882f535ff3cec2f9c012d3468fb7b912e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_60735709da9cbdd65bab0a11d1a0991ec842fe74d1ab583b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_6110cb2d4156df8d180fdd01e5f340c4731f7d1f4583fc5a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_62453a76a4867b6d09ac435581e1a327ec5b55cf231c79f9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_62616c28af945825f87a95c47c1783dc284b06ec2d447402.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_6275ba9fee197d2fab82671a4497b4764a461c2c7c33ac0b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_633204c891118a6f3d1ae62d7b444c2ee02ad0cbae4876cc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_63df7238a0005c6bffc122ca97570a95eb1d3711abaee205.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_64d6357ab735a8542112f87893a6e7c89b1b307bdb0e24c7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_655c0c4e465b47d7fd829d3a487705991f4c059cee3c9aed.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_67705e148a6e0540819f466bb4fdc73ed2e5cbcd64d80930.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_6a60fa19187345478a447b63d8f52a1cb5341e964cda29db.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_6e7c0185fda0b6211274db748205994ee1468cfb30e2023d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_6e7d2d0700c8ec6fc15dc188c42d8104b89935219254fdaf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_70923ff731dcad518ecdcdc8b53e165e8515a96ecf8f23c7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_7140432f1c424674d04ea819fa63f85aa4f154d72ab66285.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_72132e87102859b583fb69a8a2a6a8b026be4fec5a1437e0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_7218faa7d718853f8df4329a7242806cf70e63ece56f8cdb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_76a7a3db55c966560ad3e8d34037602d4d12714980898b78.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_77a79ad1902a4732e8030d79380395b7e614d65de3cdd038.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_78227cb74e7b2401070e50abff8069510f5e5ccec0a2479f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_78436f55ae9c254da5a54558ddd196c94850ba7a2b6fa637.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_78d3bf98f7b05622b428940d273b8c493f24a4468d1998dd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_7940c60a5ff2d81b62d118253577d1d891057ca45695e91a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_7a35ba110f4c26f7eb9d4dcc2e8c1baac383c777f0904976.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_7c0b13a81d9d58791b71c2d8e46d2d063de3b9e89c75335f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_814dddaa4a997380fc80cc1c72d48cb20545411924a0603f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_81c8cd41355e5f0489dad4010b5fd414b817f7a9134affc2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_81cd47ec621f2228d8bb4ec351ffd6b23d23107e5b287ffb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_85d2e8c38cc3b6f464eae6d84ef2df5f41807c9f8bf3aac8.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_860a0ad0039969cc7f01d512df2b0ea283d8f7d0c08886e5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8720ebfc91b6860392a2b7b0ba954b0cd16ffd8c360a1f2b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_884614fa7d0fe723587d2f2677d3f2143cd13ab74391bea6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8848d4bd1425f8bef31b6c279ec378bcbca14f10b702c4ea.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_88e4806d6c6553000e3c1ff8be5c90f5309342954ce4acae.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_89530e21fb2f36eb499cea025efa9c80b10049f72945bfb6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8af3f07b73fabc0cc4ef4e6928818d1ff08ead9f41a5085a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8d3cf7916a2f8a2762de13a9520b6350e46464fbf7f63dd5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8daefc2a4f66b3614a6934857c8c8f9cfdeb3ca23d16e172.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8dedfb4f00b873379cb4457d81113516b8db6c4017a1c912.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_8f6c8de1c1518b5bdcbc4ff1cdfe035b9207971a6362574f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_90f7f51f0c27f041e730cf8893f79f3f40fcb0aab1820a4d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_919cc6b1e482c475dc93740aae3549bc6012d644fb29562c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_93ef40c0bfa088c2a2dd3302976a950cba3e8d97767f65ce.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_93ff7c9369b6ff2f37896b54f6e4d8ff91c125f78ae8bf9a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_96500ef697df70106798988a9065594622cdeff67156cd20.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_977f59ef09f7cc4ad6c71fc18d8b60e818e07a43cd7bee92.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_98ead8987446388d37301c03d7d9f24e2f511a9e0c10bcdf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9a0ab728b48d43221f196b43d2816a4dff4142fd0054a4eb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9b0b29e391c61c570b20fae813486bc757c1fb7d25d83049.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9b0dc01a1388db020e5c5c428a002d099f8a35544e9b6261.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9c5350cca5afdd1a7254dbc26b3642401551473f4b071ce6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9ce10c5072e04cbd0d81d7e721fba8cf8062cc665fd32314.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_9ef1c9e836fb3844fe16369a346088af89b8da29e24aab1f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a14e739445167b1be10d3a125f958a244c4b378261598a57.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a3c88e70534d79b432d32c0b53d0d181c957b353f658dc95.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a49e29926d7019e6cbaf6b0610453eda22fa1ce9043f5829.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a7b5c5d84d974a849b0d042c435bbb3fe90ff50fd5d73f79.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a7d0cfa55dce1e96490d1e6c0188398864724e96a44e4b79.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_a88430cef36a0222c3c30780328ff266b16325a7ec723a97.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_acb93469117282f2d0131e19f6210e007d681bc7a78e7b64.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_aec83da1f2faf6ec8badfd53d632f525c9ef2090d99d1c6c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_b1034d8bbeeba5f9001f48311c182d2a20782462f0c2ed65.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_b126cad8f81aed3c5cc29c20c25b1adc7d1f33e1c4e264c3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_b3845fcad97309850a76e3720cd829a45d2bb12ee29a9cfb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_b8ffb375e75ee2976b8825d05d48c34638c7ffeb6d67baff.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_b9a9b860c0f0430853d1db2756095da274d522beed2acbeb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bbaa4eb6b32bad24fc2b8639d03be8c16d1140ec8454b16a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bc40752faddd32264f8402321411881736ab5a4733eee758.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bc596d2ebcd25e79ca9cd689e50746e42e9a6fc579afc683.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bcd3d700ef14d9a1f6b766c5d185b43ac8f3b7feffd4732f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bdb42f1c30e16bbcdf6f0ab7c1f76765ddaa5817ee5e674b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_be0651d84c04af5de43e28cf89e78d7e87490e637167632e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_be97290f663a83ba27007dd262ca2a6072c9156f775a24ad.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_bf2899717e8d7d3d83d865ca5ff59e26d7f647e6025e2d52.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c1b46a5458b15fdbfcd264b7e26e42d2cbaafb0e6dc5f48d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c1d354f1d1855b21eb3c3cd204d5030080ef9e3c7e4b0195.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c7347f362602f3a0be4b051c0b68219e0648afa64772bd30.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c8fd8db4d295aef41a9434299a8eeffb9af5e2bbcde4f13a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c94e0220a7c5dadee3094df576df766b6d1a15b6c6e21011.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c997d53083dff6918a3f066cc76c824e43eb4ea21de33c51.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_c9e8d02824dfbdf95fe9f90c45dc13bc12f45b6969b1467b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ca72ce55dc8f774617c794681dd7062eadfd14e679418cfa.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_cab5465c3f7663e5d72c15a32bc04c8a917dac3c03828814.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_cc32d31bbeb3e0d8787e963cf0843ae6b22f33817eb5a587.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_cdf0b77af7d55cc9a3424613604e8dbabe7a01e4869ad502.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ce6a3aae400b3f5f028504fec37d7be8b447bd0cb1a0cff5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_cf5321576ab8cc1b8453991abac66aa5d46155d8ffa7ee17.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_cf56ec8180c3c7622a439e68704fc1ff73770f2e8ee2926e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d04cc75917c9ef6b7a78b82491229023013ef3cea72bfba4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d0b11838d26195f89d1568431f88a02b4f4d8c9cdf99e04a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d0ebddd00bfc9c5747021ae27c0ea5cdf21355bc86b83753.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d267c5682ee42c1a570524a4b129fa908997a0ecfe07f8f6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d65eba4a41497416d108c17f366636efb4cbda4c215c8818.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_d7f6203bfe33e28a517ed4214f515fb80671c48edd4720a6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_da746ca10a31021be62e267f4e1407178b3f4a2d340672d3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ddd046530f4979511397f82fe5391d0a646c0aa18225a98e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_de14d0bf7b2c73f7a21875677eed84a1ef270d2f29dc5b99.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_e026b7c57d2d759c12652fae6421931fe4f8cf8745ff9bdb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_e15605da0c5b6f02c85aff9f1f683d3f85d211c083792ecb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_e5eb5e5215ff4d3f7a036fa1a20699d85cdfb68a7908f086.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_e8c2e5c8d393b186e21c75788f7e93efeaef12a9c44880d9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ead67129fee9b0024c9c3f53041469d74cf8a0281e39febb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_eb1478ef3d4926564e153e99fd139c87e59cfaee49caac88.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ec4ba162decfc8dd03ccbca7832f3cecf985a5542e70dec1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ececb22cb4bba60194702771c0d4de89658a4798d7efa1a1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ee29eb2556135405fa19a48b0abdff0aceddef7594169c33.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_ef73e58876b94a997d928ee13b7ac7cdb8b8aa0bac856a92.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_efea9c05de081efb7ef76741d3f24da2e993d54d99677b72.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f0523a41000b43996413780968b611c3f4d28b87f4acc859.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f11ac580e22d7d0e3da7cf1c725c8def8aef4aa891baa07a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f5cf6d94b9e4e7adfc30d262396bc29e201d9e07ead1d088.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f67db35cb225c73bb753006bd14fab03942bbe0157a74979.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f73db1873c311b2a38f27a52c5e05b021da0c2fe9590dac3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f77d9c5f3892f245b951dfd32e935473f63a4c6b565e31a9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_f7abcc33c22de53769935182a278a199e9f263a12e56673e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_fac1e789f954097c329b2709c591f0b35841438b14d08784.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_fcc4a49fbe72f1b8ffef144e2e9d85bfc8897ba2864fd521.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_2wikimqa/lb_2wikimqa_fefa6cc344f63fdceda9662af921fdcdf645abb8fe87ea73.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_0118217cf85bd94f6a5f65952212eb05e7176fd3b18c694a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_019dbd177ddcff6752aaabc8c0e459f3ae4003f718bd672b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_01aff89f9ce55470c12450b595c268a225a638582dac204f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_02c6e6b95d2a200df20bea7495469c79b1d89ed560890ee3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_034b6ac41cd902b7fbde6b304eb2930d8eea616924ba461f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_07f505d321fd7a7c04e158059cb69ac3ac7ecdebfb03037d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_0879d3f078165bdc1aabca26c8526e66d3959e8ab2c6d903.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_0a44085d7963681015a69416470b86da02135ac722d6301b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_0aaabfd136117761896b5931d7b468ff8c61909e00140470.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_0d6a7aae6f7e00180107c47a73dedda18caf3949666c4d55.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_105e7f4d337799315ddf870acc4ff2a62a1e6cdf489086cd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_11a7ad9d646184c16480376226d58f1b2754b095563c8344.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_11b4c60bf00735e20ae817b940d86aa8922e2fcdaa3a0b47.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_139d2fcf8763003414ebd0187eb30b94930de13c4ab754a0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1650b91e6fb722111b6461fc9524295246c3bd3b1a342267.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1a71b5a73ffb21cb52d41e09b1f861748b60f1e59273a080.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1ceb1c91662d241b3421853112a91b5868d1b81fe3b88ce4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1d81e1f410acc77f1d9a844f811045c2cecb0fdc9e717d41.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1df269c3eca341348a837f39c628f59aa40d663c07875d24.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_1fd7df3ba224e985f87e976c7a4a67ddc1012a249a542bea.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_203709148e7052e14bf493f95037458b606b42f2fff54c79.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_207efa55e96afdf705e48bc57b58fc8232bb972a47073d50.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_21849142d27a4c8410bf8e8042f016054a0a0493e0e8b6e6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_21bc398556b5612bf0437043cd2800e943bab5929c4bccc5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_220230ff5154e6f0ccad63965d06ce69a9226bd72cc32fa4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_228572a285ddcbb4947f362c07531238d1eec58e0fe0cfc6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_22a4122731366b93dd7495f9cb64b9312537fbe85797efbc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_232c2ba7b8bb5f22b77e5c55961d0cd0fe673d26870e157b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_26a5366c80c3a569c474a3990f3383beb125d34149e8ed3e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_27190bb50ab7e97f74e2feec7dc3ef037f1a1c74d335ecb1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_2903a54db35e788f31a967bdfa021d64ac18ed7e1aed919a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_2bf8384417cec2f1a2d43a2602326d90a97622d87898b1cc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_2bfda75e23447ca7e3213d01331c31816f30190a2ff6df71.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_302ee593ca790dfb2dcbfd4341817fc64f8d106f65f61867.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3056e292ff1583fe84207873be57c6ec28c28b425087ca84.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_31386c51d334a83befff8c1264657e197fad8b2885906939.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3518c800877d0b8cc48ca575de745502b472a139564ffa46.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_38bd41e515abf2a44d29c593748db043ba2276d93938fdad.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3a75aba6bc2496016339474aef28ffdc9dbebdc00ccc166b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3acb0cc0a04a3f71078ee120e1b7ca4f089548b7cc8a8056.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3dc3db870ea907282d3160c597c4d618ae6ba2a6bdd712bb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3dd1ade26fd583844dd2af051d61eb20856ccc8e23abae59.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3df75e9b85781f83af8d3011cedb0c5fc6725f3489e48e54.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3e4cce5082e968aec7f0c008b1acbd111f505d0579d1c9ee.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3ece2c87c1ddea4a504fd1c67fe75d34ca8f818bd9ea15d0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3f17f12cfde4c677f3af81362ce1df42f949bee1ceae40f4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_3faa54c1f192293c709684aa60c6e2e8cfe34ff55c8b6248.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_40b5d54934bcf22bb9267e605c49d46509f3bd41b1a34c31.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4567b6935bf5c64a1974b1089d67d176d9acac6b29836cb7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4636487a1855382398fe1e54284cb7dd3d7b8d178ac4a476.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4670f2a542ac06d27e47a74a042cf57f743fba34722a7dc5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_47b3fb2eb0b90839a7887fa2138662a58c0170c96479190a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_480b33cc38878ea4fe81b796d09ba2d10cca554611e323ec.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4aee23759e842807b156492356b920a11236c7ea3da20732.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4b0f3138abafd9fe2f3a16c3b2ffd55199bc3771070b5cd9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4b1df711ec0557b9df23de534c1ce99b7f37528f643b8c29.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4b753aee2d76b79f12f1b8708dd61bde51405af6fe602520.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4b83e873a551cd83a2e409d2b4467f74dd332326fcbca843.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4c34b33d7a545c4eba3848d54fc4568fdf186e849897aa6e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4cdf613f05eaa834f5867ee486ec94d47587f09b5a7bb6db.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_4d6aafffd109cb61fd543f44bda770fda0cf1e1c3798548b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_54d1487358089d52613d8e6970c3efdd5c56d112159d2810.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_561c378ca284bab34f735f05e21dae8653ca251f6480d6e4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_56dbceaf2e826fbb177035f03d7a263d62365856f21f39da.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5748ce1eca37fc55596e58fcff71e45363396002d28e0af9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5affd6b287c8ce97502760e33a71598e8eee24b78c3dd95c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5da42038bb9d29bb30e4094504ad06dc2d43afa373568686.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5e3362de0244d2b96c83958c4d3229151999292c369b0197.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5e7675388334946fc508c4c8ac4ab0c491910fcc0e048bfd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5fc84dadeb648a27c3aaa64698a5bec5d2ef23eb32e22e44.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_5ff08452b84748458e71d82a6d387599969311fd61cd8fd1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_60ec93a22fbcb65eeadd9f1d2b3c8e4ed44d3a2c4285b168.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6320310adc4a826b1bb240c63ac1735b7b29e93a59782364.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_666b2401378aceb59c9a4d6cc75b006f7c6af8a00c7d6f19.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_670498f9d7fd2582c5791cad2fe212f580d316fa49a8a984.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_690c31a6d6263dacd649fefc5b5cfa94210205fdcdb43905.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6c64a81fa526cb96d0a191d9cbd85a7e917b5d4f03b316d7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6d8f9be94b67277442c42aa9b437edaf901efec0d0959bda.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6e541b3b8fc7e59da0da6548a17932b403b2e865d4036982.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6eafb48c7a974b5097cb4752eb3853dbac8f622173d24e44.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_6eca7d7affce3375ec084f6356c6fc8ddf75eda0f6a4382f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_72a769d6d0fd1c5c90974e60ab97e88e6853b9115a7fb85e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_72feb2a8e5b92548a357bfc11e94050464f93f1ce286418c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_73d978e7e37a9c7475daa9151f9ead2bd3042e72988cafdd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_74ae5bfc8bdac7b560ec92b71604e86654f87b8f7fcbb30a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_7528b0be35e8e6007f07c98b9f2d45ee1c854298134aba5c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_75439ed8609c12817aaee0fa4f749aebb3e4a36dfa72390e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_75d66ce7bb5fbcea2d942895c0b10144ba9a94282e2e9f15.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_75f3798af3596cffefe8b932a00b1976f3f25fa0f42089fc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_76096cce081ab5b9ef72be19076ee0a79d9e9239474e8b73.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_77439b0a62b6de3a022b1d7a5678c1c00fa8d9af42fea1bf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_77a3188a3b97619e1661cc289bb1a951308223219592696b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_780b1664552881f2c14a0d943e746855f83709a5399bb4aa.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_781060824875cb0343a110f5e6f83d46e638cbb89e2ad7c6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_78e73e15102e688a5b5f43155b11658907db8caa30fdb16e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_795ed5382ff9378f90123aedc2b638c049411295c5678466.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_7bb5645d62fc946b46910757e007f59e87f52bbf8535da58.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_7d3bc2e36b406094cb586b4eeb07f13a7f1ac9dfbdce7d1f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_7e525340152c2f4b26d7fba85c680dde7b75af77356a7c22.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_81d43196cac0effe1645b207f826a30550efc3126c35371e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_826474c90684b1813df9324f779959a5e060d1cfc893a85f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_83df22880fee9f761464404ca2ff6ab21954e6b0827b4142.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_861e7d3ba836f6a816d0265dc1c9f5566ef4d22b8de223ca.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_87fd3f0590498461d595ff1823632c79b66cf313cf55fbb3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_887be3f3f2080532b3c0f1dc4d26be4f8a06030bf2e68a1a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_88b095fb93df1d962625daa1796a46ce4721c316b0ab819b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_8a5d7c131d291d2c7cf2c20ea36a629f969402e0c50a8a8a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_8bcda9c521bb7cb5dcd9a8d4987bd5bcf4ec455a84c62f81.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_8e9e0bac1908657b2f48452fe70dd4f7ab765b9633b75627.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_8fddd32ef1d88a5f8fde49152fc015eb80b3d60d1108d073.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_90caafc7fe51eee4143874971f67bb3e0107d26179c437f7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9303f959145f198df63d2d7ec604a9d6efcb3e8daca89e91.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9336554e511e88766228ffa1acd1c6f82c9a41046514c253.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_93d2774c99edbde88789a9f989642ff160871ca09e66e46a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_963e90eba94bba5bf5cf56755032d7bd4a3e4e225d3b8d14.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9729ff4cf6a13382c88896cf5a5b176d082cc1137c66b38b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_97b31d6d7a9137c220726ad51a6dca3e957e2c94ce5e65b8.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_98bf7e9946e86278d6d2b938d751861981c5fe14c356ea68.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_99635fd2d7a227cb3360253cf0f5759ed87bbac33593d830.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9a19f9594aa73716dd38bcbd5ff1c04e57a6649800570f80.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9dc6d234e2406aef691ea02ddc2064f343fc30cbc534c937.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_9fe92e20febe504670266d638939a94fc57c3cf8fe9cf948.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a16ac581bde4459861c8681858b07f82363f66142beed4c2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a18c0ece7c2ae88d2f9f3ffc5eaa13297a1b5d0125a172ad.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a1cce86489841f2514678029dbe95b7289b9d47f52f44939.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a2bb6c8de2a57c51b35e9d5c005cf46e1c0457f4086ef77d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a30caa5dafcc37835bfe4093f129017adf4c814e9016e10d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a3859ad1c8ffbce9bb2952f83cb463cc7051072c38eb8d70.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a7c311f9f6423063e02c8236bdd83cc8059fcb9fe78b4fff.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_a93aa642fb8802a99b36cd62febe1c4e995096a9320b00c5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ab016faac478c4acc6e9ed3ed87f9e29dbed47fd946be244.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ad26b1fdaa97e8ef1c290a41a9151cc6b453756cb2715176.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_afa4eccc7b711ace3270c9cbcd784c971a4f0f8d22629ebf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b3647c02310a89ccb2822c163da3bead1ad3cd21948d4769.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b4dfcf1c4f152ba5684531d0eaa43f33ec5b185b92a36884.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b524574cca42824f963480aae00867719108113389d087d3.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b6352c61b4a748448ce38882861cd5ae5f7f2869a81e92a1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b785963089bd7f81ee294751c688af85bfe2863dba623373.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b7af427ee230063a2aabb35691c7a81670c0b7e85ac3b7b2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_b84411acb9b2e39a68f92ed9e164eb053d3dd9ba4160f0af.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_bb5fb55b76b2e47a59f48907aca9db96fafabd5b874e83cf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_bcd98af30c2eb7ce1233459715d27f428b111d12fea529b4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_bf8ee342564ae21a17b169023f83a20220a63198827a0232.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c16a3dd0b5b97180359715cab5c41d528cf2a99e2744f037.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c1cfe7334235bf4a9ef11293d8be2d4055a70ac89334be2c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c261ca6aeaf366815232e91db1ef4dc8408cec3750c38ee9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c274ce731f680eb107c70386e2e341615378165ecc22799e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c47c8d3b1917f017cafaecbb4cddd6b92171854247957c08.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c5d6aa8cb0ad17a88eb66d578e86f783e3ac1f3684df9425.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c5f1f53de09eb82eae93ae68a9581141a8cc8f3df6851926.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c6c1401ec6e635eac28b985621cf59bde9e416cac2b30080.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c9ee71b5dc7f5a4538d7727c95f80c174d3c9819dfbeac5a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_c9f8b2166f7c44bf2e0843b2c77fb9fa5738af275555ca73.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_cae319fad2385d30d79efac0fb61e58518fbdc0703be3b0f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_cb677158d6f710ab0cb440b2024cc61c942a1ea4a963087d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_cb9214532284b8202912b1b75592832daef0b109593185a0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ce14f5dd15a5819d08a11f04e015e35a6f3640119973f806.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_cf16ba255ad4b7b0fdae56093ac7d5fb58487dc24f2659e2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d136a5063f8e7f5594182b51b05d626ca0671aea2ba22226.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d18fde9d0b8da2a2febb67a679847ee4ee3259e85a9565f4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d3249d0550c7105bdd4ed60c9ca9d955db08d362574c2086.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d3b197d5b4da1198fc9c232524faced0f528b89f919b8061.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d3b2acfdec13f925424cd7d96b689557edfd08e6dd6177b7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d542fcd45bbf5112eee9127f04ae060a887c8ef2050aa160.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d6fe5bc54941b566b3c88598bbc459ee4d7098d6c6f22c4d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d7d92c85b8becc33e60fc03507933f8eaf53b5e1067286de.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_d9f5437fa85841cb12798def39a30721d3d2d140b4982854.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_dc14a859291c1d678432626f6f7974f8ecca536f4b7bdd6c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_de202b6e76dc82831c7f14a6d4346d84b0c0e5e3783356cf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_de85aaa5c535ba20bdcad5fbabfe13a03687374265a57b44.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_de89026c970fbb6dff04176107b9cf20407d155bc1ae2eec.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e0873e8c51c3e473d614f6ff9705557ec2f37972ec4be718.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e0998dbc2db68c7b18adff7fcc67081acc865c974b721312.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e0a5da9581af9a4a573423cbdcf207c5436dc35ff8a9d380.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e4df9576e5cd102024e81baf94a43325335d0ba2d8892041.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e54d1e07a1fc2ce2afdf7e75f79561d8fe0abd22f4d8bd53.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e5e18488f0e900206332a857f70da66dc59829937c913ff0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e7875d33cdf7138818681e7bb2a13310bba28ea94550d64f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e8ba4badc3c5d30cc0942ede8df86a72257c492c07025dab.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e9348ea3d217789522ba17d5dd2c69c01bacc9d677c614a4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_e9b828ee7169d1978f3bcb6de5bbb0f54f9ee3bfc0ffdb8b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ea58013717bdbe9f0bad1991ed03d1afe3208bf514d9a2cd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_eac05e5d0936f802e28b0c5081a2c2a1a94fe4f2c20cb2df.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ec3b5bcfa070b047c769413b99a2f32e4f5d2f803cf81a43.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ed6c85899d2a29f6dc8e02ba62bc8f1b1043a8c135fdd132.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ee07a420f322205e992788e25c0b256cadcd99abd359ff0f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ef245cc27251f559f3cd900c11c7bf9f303eec3c4b346802.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_efc793ac73a0341a7cc35ea6872a89be3d4fed5f64c1e043.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f039fe9cc81a0a312f9899beca2fe26b710bf8c3aa23a4d9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f1c0b9a9ec47ccda8ba4b1be0ca7083b961ba0f06b2a4df7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f1ea70c4e2c13d2fda1feda75a72a345c0e91f083220e95a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f2da37b927d3f8ce752b69d7149a6eb31aa738d123f8fdb6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f327fe18cfe320df9685d7195f33d41745a432e769476dd0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f536646dd72a8a4f5ebddec61a67b8319dc9187d47bb7fc6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_f5ca9a0360773900f848072d3d7c63034922bdd0e6925e64.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_fbd2e6218ec7c8fc1a90b05bf6858a15d376704a278fa79f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_fc6267db9ba02bbb251960231bc87251c581110e4e2b5f3f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_fda38e0c47dcd2b4f1de4adefeb00ab431221c0ef9adeb31.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_fddb2049ab13cf002eb07f658ae13d9f99d83538ed881e9b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_hotpotqa/lb_hotpotqa_ff048b34a9405c880ccf710acdf1a53244e6039cb76c793a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_0012658ce252037bf12bb47de21ea785b1ee2731e5bd809f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_021d8b537118d33026257c7aa79d0405d126e2d35962d221.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_036bfbdbfff8294f59afd5860663bbb4349924c9853b2151.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_03ac54754b9162f6632212ca481920db17fc953e73af3a1f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_03e03cd498cae30eb47667209de54bfe6545647ddfe4457d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_04174ea6c9849bfa946452cdbc20fc0c4ff9d27596099dcc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_04af9dc96013a1bc7faecbc589f7ea5c207e92c7d9a3495e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_06baf6c4ae0f97a3131aa06bfa2b4878bd99ef96659cbf9c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_06feabc1e5ca23dbfd79cbb2ea42b436c85bf6ac6a8d4b14.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_072d3de1a7122730a13a31db3eede4113af2d920814f0aaa.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_07484380079dcec47eb573ab62eaff39a1a44b32006ec74e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_08034d93200eb0b2207fc07921f81e95f4a801c0961f3724.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_091b4028a3b5e9d8248c58f17a62fd16c878da69693cfbfb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_0b90a0a4b2cdceda62a9e2b165f0cfa1a34d34d800a46086.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_0ce1ee7ab0f1557704a9d7f937e6f5182c665687a3e2b0d9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_0d39f8e4a71796ad340444ae3e5fe23b51beb9f47247d8a1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_0e83a6f7ee840931e1851402cc87bd34f52fe8bfa4dc1cab.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_10f50fd914b227d12f503b3ef4ac5fe772e70f44557c17b5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_11be2f14f540e957e9797cc962203b8186ca10561228f81f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_14e88916523197e066dbb743339685621db47c4beb503abb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_159a474e0a7155a2d0b984cbb5215cdc853d721605b90154.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_160075b535e7b0c17c873ce4ffc5bfc9735ba43fcff32757.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_1614ea21f8d039debfc655015f8133d0ef220837804ddf62.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_168484fbdc83fc2e0c374e1d92ed08edca0c33669cd88a33.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_17a2b96e126ab914e1179b4794d18513627ade82d5c35554.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_18576b9ee9994a46dc0c7d916a009ff6d0964991541010ee.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_188fe9331293312465b4564e11ab36dfbcb37191e62a969c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_1a1daeb5809cde7c7131d972f42ee43654a378c78d5182c8.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_1b96562949f4722fed7766bb0be032ca10cb98c89192068f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_1fc62062641bf85a160d7465aefb91870235e6c815b392cf.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_2561836b391d69be52ba4d97583238407f2fa80afef9a15b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_2589b46ee58a7600e17fa89a0d4fffd9a0faf1df49b3c035.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_26eccf323630722b689e91abd27fbbae0da4097e74865c33.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_2ecd2808617740f222a4e2f3b2df546da046d876b1580952.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_2f457d7ab54cb1afc5be7e5171425354617f49b8f75d90fa.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3278efeb1fb7f569dfd6ef8627cdefb5955b93b612fe2902.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_32e71ab83380bf828bc42ff6e76f4e8ae42d356a6988a79c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_34e4bb298d4e2c19c2fce8670a00196cddd9f361eeb09a9a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3598040772b4950e6241b50125f7ab7038a8149060e3c381.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_36dd6c4714fb80bd70d4dc3805324eb2055fe272b85fa5c0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_37555b3a43b9c65a02a522310fe737913a5863a33bf81c32.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_37f06d3a413beef1661730ae1049e7adccd6308032ae1fc5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_388c857ed1b4175e114a0ce9f3489766797a32cd183f10ff.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_39352d304bd452de69fcc492ad458b72614e329b4509eb48.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3ac3eef636db11635a21a61804cb28e92c546a5686dd1e12.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3b069a546d5417be546f57d02981cf5ac68b4d3d6c55624a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3b3fcd0ee773501a21c5eb6159746fa29bdc3498329525e5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3b83a9c5c4dc7fa170724ce8378a276b8cbef90a62b13603.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3bb91d7f22ae15ff9fc6475233052ad0981ad7e812f7eaa7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3c1ef39c9ae5336afa8c7d3501bd8d24dc655c17ebf6c75f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3ca65b23b3cb316653709b469b4a9b42b790e0350c76ae1a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3dd2d62c046f3b559c34003f570ed35211000500b8f0145f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_3f3d64d45cd4761fa7a9da94fbc4c41b27f3a7b856117638.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_43279ddf85ada1b163aa1b316a4df1418957058206501c26.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_43ffd7775c3b4a541e227c120bffcc7c7b31fb184ba94d69.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_443d051a54d96c296d9135dad3794d09f89ff91d6433d092.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_466bd29bcab1cdfdef327777808236bd2677e2a54414a32a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4a244628cbffa02d2240d412aeeed45c53fec95e66595a00.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4b9e15e7e39589f3a953e9e6637e00c28269be034f93c00b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4c9552eec5c238657f8ed5237bf66067d3fdda2409a903b6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4eb3ad14a5fbb16b03f54ef42febd2f167f8b2a9f5a26343.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4f1d5a7b6c42269c845959f8a8d7ef95cb7e0c122c9a721c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_4f6f6dfa672ed697a94d1d1ee528e50645f01f568707b0b5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_51b9066a5f2845e2fdf0d1dcde6833f70ae49ed01aa306db.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_51cd01004f7bc29798a9671b991c5223ada1d40ccb8141e0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_547c0b203cd3f5e26ebf4709ca03599db12e8d1bb08bc1ba.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_5663b4bd81cbb6b052e49e8df64f91f4fa3146f4067b2f94.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_57de270868df43af983000c70076588676aaf9bfb5fbfca5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_591249c5522d87dcf4eeb6e1fc35bbf56a2290d23c83544d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_5acdda9ea1342cee04400bab5f4e3d23f394c14fa42f784d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_5f00d4f6e62f4b99484eb78491f803f8143cc1b13ad33816.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_5f7af98db66df4388108e26cde4781423ca2580bb48de4fa.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_65e11f98300887fc3b0d3912db406f8d8825d3f61c7a12a2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_65f7bdb541fd6f01fe866dcf694891f92533186085fcba20.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_677dad703988e8f26b322211803fad38ffe9e58d1725f51a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_679cbfcf05ceb304bfbc0f4ea24597aeff90611a76a374a2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_680ef767fe2a990615d0bc1cb1bf5f7d23c8766209138826.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6a78dbe4f8e30d35c13ea1f80e52df286f9e1f664f9c3d98.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6ab7a0f094ebc681c85b0bdbf251970c5fc6bc638da5e3b5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6b9d0c1e63714067fc0b54c024dc065e63f64cbaf44ab4d0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6ceab4edd1d0e37d217958e7e962697124ccb6a4f449f4af.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6eec5b0ef38f64f6a545677f730b4ea1c980db6d380de966.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_6f949074854fa472b5be66cc1c3cf9d2c3dfe301bd437515.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_710f7452388fe5d22e2329697dbc4fa17d2c9a53daedafa6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_715229da03cdd7077f0ea02c5b4f67489abe24d42e4ece22.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_72bf7a9599ea8ea1cf309f0dfe07f16f2e05d59ff82f4a37.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_757c3e92861be1ad45a06d157bb10fe162bd2163bc3baa6c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_76f663a13234c9da9f1d78c72b52d73ab37da0977e0001d8.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_78224546bfb859e5412a0d5ef1b030ea0b3844c9987c79ff.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_78ec3790de7582388e6f9f2e428ddd2f6cccef851a8fcd57.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_7e2663bb13493e18205f6aab469fee8b2a9df281a0ba0e2a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_7e339da53449dbd58a1e815d55e440e712af6a1950f342b7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_7fb2af0c4759875dc623bdfa5024e13f06a9288f1930470a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_7fc2e4d78ed71fd9cb767560f9f8f69124754bf212e2e3dc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_806667777a33e5aede1bd3a62cbb5562f99b2223f68b98fe.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_8595332098adaabcfd8ae199f754a9b06cdde08cdd4cc64a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_85a7083bae278e83df0fea37003937a9294638f488a18a83.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_86c75d2a9157cb601a49f8424fa1e6e90fcd724132490bbd.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_8861331a4438449d0fd62132eff72f24413fab1daf990780.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_88d89e5b02c860bd1fdac17796e2b6048a6d2b86950c4c12.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_894a0e08b526f2093c854d91c680190c898ae6acbc1ba131.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_89a4fd3fce6114c3401790c6f9b5243fda094597657f348a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_8b6bf313950a892cbda035f2c7b3d8b01472ff34749f028d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_8f650cd8021e553a4106d292af9908f29595f88fc39385b2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_8fa5af6a36dd0b6b73900b2ec6f6e43a652a3e7d2b827a58.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_901f735b1582acacb606002ab77c6c7a3fe6017d38349aa2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_90b2dc5aba0e95b2f541da4efa36c414b93bb33d56f2c31e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_914ecea04fa73d3a61afe04a4dabd1dc5b80a0aa66784a9b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_91dd7b7a6ead4025763812d70dc51c6674b0acf31bd5a5f0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_92da01e7242f30f5266e431b4269fee1b0ca5fcc23aee095.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_93004cdb0e6d24f5de0568ed952fd50655e42900dc9dbfdb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9694f6b846301d401e87c4d0456a400913361db16c05503c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_981e544c9c90888f266707622e41e2c06b1b9b8ce6af525f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9c060535b14310dff1d863489d6ecd52f7ecffda0dcc9fcb.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9c415874c0c9fba5d1111bf3d9cb379fcbeff17fcccb560a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9c46084d667b60a92a3cebfb8fa56436fa1497668ce2af56.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9de7829de79f59d8deeb2d8ecc1652d081394c258cbce691.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_9fb085a1f47673d1907f2378c90843b4b6e8622a14fe1fa9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_a3aadf47eb153a70559416ba375c57883aec1538a2b17fb5.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_a49d38fea6e6ffd631d227f17753ce20624d17bd8a04ee03.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_a65a814bec0bd2085660d75fc5eeb39935a7cea44abab2b1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_a80067307d72e349f14a1f6765d914acf0b43764afe77ab7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_a8f155f6d0b86040e21fdb913b07c5fa675b82dbacc0674e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_aaaf5a6e22afc0f84ee63ab9e8dfe9484462ef105aa44ec6.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_aad6558e94d7056e2b8acd03fbdac6448c16b0bf28d1f033.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ac6538e9c173ba7b453d6bf62480d56eb3761b5f6f73c328.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_acb71edfecd0645219cfd258956141fe666557f8debad399.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b3d9af44008c13b316e929ad00b8eeea477fdbf5aa50eab7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b5481f9dfee2d9dd2154b3396a702c72f00b86508b001651.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b5f62b7acf975c5454df077adf727c1bcc62985be5e5a660.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b69e327bf637183397c7d975df8e1c45fa1ad9866b71e6d1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b72f9154e71c03d0403e06e50063325961ea2ad27c245763.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b805e336d2e8cce895100cfde3a536e632ddd5296ddece21.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b80ef6cf65d0728f2a3a6c812d50121f97dc555c71d8871d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_b96a5e2e8d4b32aff5401e97c66942bf33f6c3c62a43609d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_bae15e10e0f414a92fb0e943871ed25c3fc16183a3028012.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_bd9de91e4f20f4d0e8cbd1d442c97022e5410cc9a814aa0e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_be6e56c9310a931e883d529da75b125058563bcf4d8d16d0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_bee3efb92996570d990ab04bfdf054835ef720b9dd1c6f5a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_bfc5d4d72997fdcc0107cd5cab9b9718777c43b86be45eb2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c09598fc924dab440fb92fcd82dff116759ed11f5947b3c0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c109a25d23a8c5c95af8697ef1ac51cd3bee93c67521af6d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c276162e5903240b254238163922fb0ef59df8b8c706790f.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c2df5ec4b6b7dd1c56e05d6b3c0e244d0c44d68f117caf0e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c3dc6e575eeee19145547b339ae1c7af914dfde59a652000.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c47ca982b6c4681c4741d4708801fa79a3e1cab17d0a2c4a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c509e3bda123ac08967781ad78a55a157b876e9d0aa97adc.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c624b6d8a5c2cbf6ad3c24de6e42d7b1b6504fe608ee3733.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c6464e3b2dbf1c8412496fdef56cafcccd0ccb9dd1937886.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c6aff9577f2b48117cc4b4d11e8acfc1ffb55ec48717b69b.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c6bf18dbbe6ad2c777f3b2db9f35a1b23c9e3ec2d138b186.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c8ddf1d2e1192893ee5bf9e0ffdeb6762a7a2f719d299c28.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c92d96ed55bc5dcd92f963d3c5d26e52661b74e71090f24a.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_c9d48df129798d2aed0161fa805a289e5f75306af3e22336.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ca91b274c44baec976e7acbd926d7d823fd5a81e34dfcce1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d022dfe02fb2a55b4baa40fe436f616aecd3f3ced1a58d7c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d0c52dceef7d3b347e2f4543e601576d4d68324e7c543a6d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d17f6335089f3dd922f3d5400e3fc2ad1ca15202f4ac6467.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d1d93cefe6e2c643ecf128643f9362e3fa137ff54253a3ec.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d230ce079b2e4ecf5d9a987fb750dcbc319a537bdcfcc3d4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d25cf05e9fda9bdadb01c26a57122079766a565269fac749.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d3dac3676da5685f20bae39814f760368752f5bd8db93500.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d426a2d42f3dffc8771498ba64ed0e383b91939398e83dce.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d5280384a4496ef3358dc45dc0199b9198bd0d927be302ef.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d696cd0b146419d53d72071d8b8949fc562ea4addb87eb96.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d7fcca67f5487a55282f8217e4f05bc54ee67e2ddb578e73.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_d999910bed46747299b4c315cc345dc978d979252f65d39e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_db4afd55783aaf6d069c5228152492cf0804e9cf310cb238.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_db6c4d611b78c840972b57ee0b245003566b982feaff1084.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_dd771b6e98a15ceb55e41e4c6e948e1ab1248d51111fb5c1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_debdd11c3c5802df0fbef5055ef8d57888c833e2a230e0b9.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_df3b5e07ec132472a8fc5b7f30b6ce3d942c8488a3d8ff7c.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e0a92574e7c31adb9146851dcc95729b585305d15cf491d4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e419f2bff9d2ab7c3b60b3250caccd2d9ae1285ec3e8e818.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e48405471fa8e3af3ddf67e7e9deb109523dfab05dc9d659.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e57ea6390f796b88ab34da666c6576609db900eb9d0d9b24.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e73ea6012e4dfc66d353142915ef35e7ea2c315e1566adfe.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e7860b94e9aedb1f9b1e5a8839cb1424486c3f2dd69ee124.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_e7efd3969adf95459805233e580d6e0c7539a4de09b4441e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ea4db579b5224fe0fa413ee436a5f4f56777dfa3e25d99d7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ea58638e132307bb3f2c24abeb0e2d07eaf162e3e1d12b57.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_eb64a6b64d9837a23cd1824be1986861b0b23d98ff1c52b1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ebd4ae480fe1596841b2132e96f40eac8437c800db8ef59e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ec83bdfec205fe7374404faa05fe5420a2a7922e251c573d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ecb62b0ffa918a2faef02edcbcab0090da78c2c6e92612d1.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ecf37304ab84334d46491b0bd3d8bdc7cda33d54a15870f0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ed98266f89745750cb92ebc16c941888f1b0291d405d14e2.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_ede810c7fa069014dc1b6fe66c54079ce1fe81903c684600.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_eeab2b9167f294f68d3058752acc01e1145eb7d89437d5c4.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f028740d1aa46f5337578cc37bb55f6c8ac0864856b26096.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f0f715a6867aa0e4b6ef1eab6827162fba00296faa55114e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f27a64d129091a6c8973c001ff789b8f68955b8ff0ae70af.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f3aba3579b9e3373ce708f10b33510d6a198c3bae58c5ad7.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f3b5a2a6642523c5347d7612ee64a3378c6592ea58a0857e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f4aa62dcbb2bac20bc9ef1361ad811d6822f66df83f0930d.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f545e80cf01375e891406755e35019032cb4b7621338b707.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f55efaaee938369fc4be8a430e531c164168be643b3cfe57.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f755dcbd288905ec07a63f18ddee7ed22103c45e887a091e.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_f7c52845824592155b90b879209bfaf82e6a8598c9cb9db0.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/public_qasper/lb_qasper_fe6e5087f91071369646d9d868d784a290d0d13013292b61.json +15 −0
Large diff (16 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01000_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01001_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01002_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01003_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01004_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01005_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01006_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01007_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01008_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01009_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01010_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01011_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01012_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01013_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01014_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01015_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01016_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01017_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01018_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01019_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01020_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01021_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01022_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01023_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01024_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01025_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01026_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01027_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01028_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01029_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01030_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01031_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01032_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01033_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01034_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01035_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01036_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01037_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01038_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_01039_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02000_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02001_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02002_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02003_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02004_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02005_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02006_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02007_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02008_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02009_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02010_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02011_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02012_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02013_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02014_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02015_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02016_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02017_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02018_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02019_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02020_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02021_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02022_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02023_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02024_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02025_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02026_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02027_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02028_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_02029_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03000_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03001_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03002_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03003_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03004_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03005_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03006_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03007_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03008_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03009_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03010_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03011_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03012_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03013_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03014_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03015_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03016_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03017_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03018_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03019_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03020_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03021_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03022_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03023_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03024_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03025_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03026_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03027_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03028_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03029_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03030_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03031_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03032_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03033_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03034_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03035_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03036_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03037_8000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03038_16000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/docs/synthetic/syn_03039_2000.json +85 −0
Large diff (86 lines) is not loaded by default to keep the page fast.Load diff
added data/generated/keys/exec/exec_00001_2000.json +162 −0
Large diff (162 lines) is not loaded by default to keep the page fast.Load diff

Diff truncated — file too large.

Menu

Theme
↑↓ navigate ↵ open esc close / or ⌘K anywhere