chore: dont lock poetry
envgap__madpah__serializable-17
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
9bc4abccc9cabed5f9808101a8d25717b86f01b4- Manifest
pyproject.toml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
madpah/serializable #17 · read the original issue
this is a library, expected to be usable in various environments. therefore, it is needed to run the lib in various test envs, too. the poetry lock file is making this hard. therefore: lets remove the poetry lock file, if possible. for QA reasons, the ci/tests should run periodically, to check if all dependencies still match the dev-dependnecies should be pinned to exact versions, to make testing reliable, despite the absence if a lock file. ---- and for some reasons, the current lock file appears to cause problems on CI:
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]