pipefunc/pipefunc - CodSpeed

pipefunc

Blog Docs Changelog

Performance History

Latest Results

⬆️ Update ghcr.io/astral-sh/uv Docker tag to v0.9.5

renovate/ghcr.io-astral-sh-uv-0.x

21 hours ago

continue-on-errors2

1 day ago

fix: streamline continue map error scan

continue-on-errors2

1 day ago

refactor(pipefunc/map/_run.py): rename `_collect_error_info` to `_create_error_infos` - Renamed the function `_collect_error_info` to `_create_error_infos`. - Updated all references to the renamed function.

continue-on-errors2

1 day ago

refactor: Renamed functions for clarity Renamed the following functions in `pipefunc/_error_handling.py`: - `check_for_error_inputs` -> `scan_inputs_for_errors` - `handle_error_inputs` -> `propagate_input_errors` Additionally, updated all references to these functions in `pipefunc/map/_run.py` and test cases in `tests/map/test_error_handling_coverage.py`. The changes aim to make the function names more descriptive of their purpose.

continue-on-errors2

1 day ago

fix: use lightweight _ErrorMarker instead of full ErrorSnapshot with return_results=False When return_results=False, we discard heavy data to save memory. However, ErrorSnapshots were kept in full, defeating this optimization. ErrorSnapshots can be huge (they store full kwargs which may contain large arrays). Changes: - Add _ErrorMarker dataclass to track errors lightweight (just is_propagated flag) - Update _InternalShape.from_outputs() to replace ErrorSnapshots with _ErrorMarker - Update _entry_contains_error() to recognize _ErrorMarker for error counting - Add regression test verifying errors are saved to disk correctly This fix ensures return_results=False actually saves memory even when errors occur.

continue-on-errors2

2 days ago

continue-on-errors2

2 days ago

test: add regression test for non-mapspec callable resources Add test to verify that callable resources are evaluated for non-mapspec functions in _execute_single(). This test would have caught the bug where _maybe_eval_resources() was missing from _execute_single(). The test verifies that the resources callback is invoked for both error_handling modes (raise and continue) when using non-mapspec functions.

continue-on-errors2

2 days ago

Active Branches

⬆️ Update ghcr.io/astral-sh/uv Docker tag to v0.9.5

last run

21 hours ago

0%

ENH: `error_handling` options (`raise` and `continue`)

last run

1 day ago

-3%

[pre-commit.ci] pre-commit autoupdate

last run

2 days ago

-2%

© 2025 CodSpeed Technology

Home Terms Privacy Docs