smoke-optimiser 0.3.0__tar.gz → 0.3.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/interactions.jsonl +5 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/issues.jsonl +40 -21
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.github/workflows/release-please.yml +4 -0
- smoke_optimiser-0.3.2/.release-please-manifest.json +3 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/CHANGELOG.md +25 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/PKG-INFO +18 -6
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/README.md +17 -5
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/pyproject.toml +1 -1
- smoke_optimiser-0.3.2/smoke_optimiser/__init__.py +1 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/cli.py +13 -8
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/config.py +23 -17
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/command.py +85 -59
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/maps.py +31 -13
- smoke_optimiser-0.3.2/smoke_optimiser/paths.py +95 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/coverage_db.py +9 -6
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/import_tracer.py +4 -4
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/models.py +64 -5
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/persistence.py +45 -9
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/read_tracer.py +2 -2
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/runner.py +82 -26
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/scope.py +11 -12
- smoke_optimiser-0.3.0/.release-please-manifest.json +0 -3
- smoke_optimiser-0.3.0/smoke_optimiser/__init__.py +0 -1
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.agents/skills/beads/SKILL.md +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.agents/skills/beads/agents/openai.yaml +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/.gitignore +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/README.md +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/config.yaml +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/hooks/post-checkout +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/hooks/post-merge +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/hooks/pre-commit +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/hooks/pre-push +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/hooks/prepare-commit-msg +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.beads/metadata.json +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.codex/config.toml +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.codex/hooks.json +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.githooks/pre-commit +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.github/workflows/ci.yml +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/.gitignore +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/AGENTS.md +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/Justfile +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/LICENSE +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/release-please-config.json +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/scripts/branch_summary.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/__main__.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/__init__.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/blind_spots.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/changes.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/environment_files.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/downwind/rules.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/environment.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/optimiser/__init__.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/optimiser/filters.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/optimiser/greedy.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/optimiser/models.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/plugin.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/profiler/__init__.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/py.typed +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/reports/__init__.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/reports/downwind_suite.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/reports/repro.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/reports/smoke_suite.py +0 -0
- {smoke_optimiser-0.3.0 → smoke_optimiser-0.3.2}/smoke_optimiser/reports/summary.py +0 -0
|
@@ -32,3 +32,8 @@
|
|
|
32
32
|
{"id":"int-cbad2e0b435fe44d03f4469b58c5efff","kind":"field_change","created_at":"2026-09-08T22:35:45.409768Z","actor":"lawther","issue_id":"so-n6b.46","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed by staging the write to a sibling .tmp and os.replace-ing it into position, so the target path is never absent or half-written and a killed write leaves the previous profile intact and readable.\n\nRegression test in tests/test_persistence.py (new module) simulates a failed write and asserts the previous profile survives it, both as bytes and through load_profile. Verified it fails against the previous code.\n\nOne consequence recorded on so-n6b.47: a hard kill now leaves a .smoke_profiling_data.json.tmp behind, since no cleanup can run. That is the right trade for not losing the profile, but it adds another untracked artefact to the set that issue is about."}}
|
|
33
33
|
{"id":"int-3915e7b580afd8d6136fad6580066262","kind":"field_change","created_at":"2026-09-09T03:24:23.011855Z","actor":"lawther","issue_id":"so-my1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed in 0210cbe. The three artefacts one iteration leaves behind -- outcomes, import graph, read map -- are counted before they are read, and disagreeing counts are fatal. The expected count is the largest of the three rather than the outcomes count as the issue proposed: the hook writes the graph before the outcomes, so a process killed inside pytest_unconfigure is likelier to leave a graph with no outcomes than an outcomes file with no graph, and anchoring on outcomes would have missed that direction entirely. Under xdist this catches one dead worker, not just a wholly absent graph.\n\nThe check runs after the exit code is inspected rather than inside the readers. run_profiling deliberately tolerates a later iteration that pytest reported as fatal -- it is dropped whole and the earlier iterations' coverage stands -- and failing on its missing files inside the reader would have removed that. A killed iteration's absent artefacts are explained by its exit code; only a clean pytest exit with artefacts missing is the silent case this issue is about.\n\nWider than the issue as written: the read map got the same treatment, since an empty map reads as 'no test opened this file' exactly as an empty graph reads as 'nothing imports this module'. Agreed with the user before implementing.\n\nThe mocked subprocess.run in the runner tests now writes what a finished pytest leaves behind and writes nothing when it is killed, which makes the existing later-iteration tolerance test exercise the ordering above rather than pass by accident."}}
|
|
34
34
|
{"id":"int-9ff921ab870e29c4cf124583da45fe9d","kind":"field_change","created_at":"2026-09-09T04:49:51.85054Z","actor":"lawther","issue_id":"so-jr5.3","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped, with two things the issue did not anticipate.\n\nThe issue assumed the fallback could simply call the profiling path. It could not: run_profiling exited the process on incomplete data and on a missing pytest-randomly, which would have meant declining to run the tests a developer was waiting on. Profiling failures are now typed -- ProfilingUnavailableError when nothing ran, ProfilingIncompleteError when a suite ran but produced untrustworthy data, the latter carrying pytest's exit code -- and the pytest-randomly check warns everywhere instead of exiting, since it costs a worse ranking rather than a wrong map. run_profiling returns ProfilingRun(data, returncode) and takes a ProfilingRunConfig, the four fields it actually reads, rather than a ResolvedConfig it mostly ignored.\n\nExit codes: pytest's own wherever the suite reached a verdict; 1 where the suite passed and left no usable profile, so a regeneration that quietly failed cannot pass for a green run.\n\nThe second, found while testing on enphase_curtailer, was a defect this change introduced. The fallback re-discovered its coverage target instead of reproducing the profile it was replacing. That project profiles with --src=app, a CLI flag persisted nowhere; discovery found no src/ and no package named after the project, and settled on '.'. The fallback replaced a profile recorded under coverage_roots ['app'] with one recorded under ['.'], which put every tracked .py file in the tree into scope -- including four .claude/hooks scripts coverage.py can never measure -- and so expired the profile it had just written, on every subsequent run. The feature built to end the staleness ratchet had created one.\n\nFixed on three fronts: discovery now reads [tool.coverage.run] source/source_pkgs ahead of every guess, which answers that project without any configuration at all; a fallback instruments the coverage root the profile it replaces was recorded under, so it reproduces rather than substitutes; and an undiscovered source refuses to profile rather than defaulting to the whole repository, with an error offering the exact command to set a source and the exact command to instrument everything deliberately. Every heuristic now announces what it chose and why, on both commands, because what a profile instruments decides what it can ever know.\n\nAlso: the xdist distribution flags (-n, --numprocesses, --dist, --maxprocesses) carry over from the downwind arguments into the instrumented run, since they change only how the same tests are spread and dropping them ran a parallel suite serially. Everything else in those arguments is still dropped -- an -x or -k would profile a fraction of the suite and pass every completeness check doing it.\n\nFollow-ups: so-n6b.49 (top up a profile's iterations rather than re-running every pass) and so-n6b.50 (the scope model counts files coverage.py never walks, which is why the '.' root was destructive rather than merely wide)."}}
|
|
35
|
+
{"id":"int-ad500a50f8750319e3865b8ffe767b3e","kind":"field_change","created_at":"2026-09-09T23:18:19.667426Z","actor":"lawther","issue_id":"so-n6b.54","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed by giving the Python rules the denominator the read map already had.\n\npresent_files is now every non-ignored file in the working tree when the run started -- Python\nincluded, untracked included -- rather than the tracked non-Python files. Both halves of the\nwidening were needed: the Python half so a module can be measured as unloaded, the untracked half\nbecause the changed set reports untracked files, which is precisely the reported case.\n\nOn that denominator, a changed Python path the maps deny knowing splits in two. Present means every\nrecorder watched it and none saw it take part, so it is inert by measurement and answers with the\ntests that LISTED its directory -- the one relation a file nothing imports can still appear in, and\nwhat keeps a tree-walking architecture test attached to it. Absent means it arrived after the run\nand still refuses with UNKNOWN_PATH. Expiry asks the same question, so an inert file in the tree no\nlonger expires the profile either; without that half the loop would simply have moved from the\nchanged-file rule to the expiry rule.\n\nVerified against the reporting project: with the denominator a re-profile would now write, an\nuntracked tests/foo.py selects nothing instead of the full suite. The under-selection this admits --\na script a test invokes through subprocess, invisible to every in-process recorder -- is so-n6b.55."}}
|
|
36
|
+
{"id":"int-8c876b20e431170c1a806fb1137db65b","kind":"field_change","created_at":"2026-09-09T23:43:12.048517Z","actor":"lawther","issue_id":"so-n6b.35","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Not a bug any more, and it was fixed by the read map rather than by anything aimed at it.\n\nThe body is written against NON_PYTHON_FILE, a reason that no longer exists. A .pyc now goes through _read_answer like any other non-Python path: nothing read it, nothing listed __pycache__, so it selects nothing instead of refusing. so-n6b.54's widening of the denominator reaches the same answer by the other branch when the .pyc predates the run.\n\nMeasured on a fixture repo with no .gitignore at all: an edit to src/app.py reported five changed files, four of them .pyc, and still selected '1 of 1 tests downwind' with no blind spot and no full suite. The failure this issue exists to describe cannot be reproduced.\n\nTwo adjacent things were noticed and deliberately not carried forward here, because neither is what this issue says: the changed-file list is mostly artefact noise a developer reads past, which so-n6b.47 now covers on its own terms, and read_tracer's EXCLUDED_PATH_PARTS is a second hand-rolled definition of 'not a project file' sitting beside git's, which is worth its own issue if it ever bites."}}
|
|
37
|
+
{"id":"int-ee37dbdf52a1c69ba2285c578528760e","kind":"field_change","created_at":"2026-09-09T23:43:48.81226Z","actor":"lawther","issue_id":"so-n6b.47","extra":{"field":"priority","new_value":"3","old_value":"2"}}
|
|
38
|
+
{"id":"int-d675556a4f9cf1a2520e475466fd48ea","kind":"field_change","created_at":"2026-09-10T00:06:08.104317Z","actor":"lawther","issue_id":"so-n6b.50","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Implemented per user decisions: (1) generalised to every coverage root, matching coverage.py's real behaviour rather than special-casing '.'; (2) rather than storing/replaying profile.measured_files (which would be stale for files created after the last profiling run), added ProfileScope.include_namespace_packages and derived package-ness live from __init__.py presence in the same tracked-file list files_in_scope already receives, keeping the module's pure-function design; (3) include_namespace_packages is read from the actual Coverage object inside the profiled pytest process rather than assumed False.\n\nChanged: smoke_optimiser/profiler/scope.py (_package_directories, _reachable_by_coverage_walk, _in_scope, ProfileScope, resolve_scope), smoke_optimiser/profiler/runner.py (pytest_unconfigure hook reads cov_controller.cov.config.include_namespace_packages; _merge_scopes), smoke_optimiser/profiler/models.py (ProfileScopeModel field, PROFILE_SCHEMA_VERSION 4->5). Tests added/updated in tests/test_scope.py and tests/test_runner.py; fixture dicts in tests/conftest.py, test_cli.py, test_downwind_command.py, test_profiler_models.py, test_runner.py updated for the new required field. Full suite (381 tests), ruff, and ty all pass."}}
|
|
39
|
+
{"id":"int-a9fab09b01785d4cb3ac0b35c9b47a99","kind":"field_change","created_at":"2026-09-10T00:12:07.901945Z","actor":"lawther","issue_id":"so-n6b.25","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Already fixed by df84630 (fix(profiler): save the profile on every run, not only --profile-only). cli.py now calls save_profile unconditionally in phase 1, and phase 2 only re-reads the file when phase 1 was skipped (--optimise-only), otherwise reuses the in-memory profiling_data — resolving the secondary question the issue raised."}}
|