fix(deps): raise the scitex-dev floor to a version whose store actually works (0.20.1) - #158
Merged
Merged
Conversation
…ly works (0.20.1) 0.20.0 declared `scitex-dev>=0.17.8` while every store resolves through `scitex_dev.store.host_store()`. A consumer on an older scitex-dev resolved CLEANLY and then failed at use. Measured on scitex-python, which pins `scitex-dev==0.28.0`: the install succeeded, then `ModuleNotFoundError: No module named 'scitex_dev.store'` and three clew integration tests failed on all three Python legs. The floor is measured, and IMPORTING IS NOT THE TEST. 0.43.1 is the first release carrying the module and `host_store`, and it imports every symbol clew imports — yet a real write-then-read raises `TypeError: tuple indices must be integers or slices, not str` inside `Store.rows()`. Running an actual record-and-read-back against PostgreSQL with the published 0.20.0 wheel: 0.28.0 FAIL (no module), 0.43.1 FAIL, 0.46.0 FAIL, 0.48.0 FAIL, 0.49.0 FAIL, 0.49.2 OK, 0.49.3 OK, 0.50.0 OK, 0.57.0 OK. Applied to both the runtime and `dev` sets, so the bad combination is refused at resolve time. No code change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The bug
0.20.0 declared
scitex-dev>=0.17.8while every store resolves throughscitex_dev.store.host_store(). A consumer holding an older scitex-dev therefore resolves cleanly and then fails at use — the exact silent-failure shape the ecosystem rules forbid.Measured on scitex-python (PR scitex-ai/scitex-python#375), which pins
scitex-dev==0.28.0:uv pip installsucceeded, thenand
TestClewIntegration::test_status,::test_hash_fileandTestCrossModuleWorkflow::test_io_save_then_clew_hashfailed on all three Python legs.The floor is measured, and importing is NOT the test
scitex_dev.storeandhost_storefirst appear in scitex-dev 0.43.1, and that version imports every symbol clew imports — a symbol-presence check would have stopped there and been wrong. A real write-then-read raises:So the probe is an actual record-and-read-back against PostgreSQL, using the published 0.20.0 wheel from PyPI in a fresh venv per version:
scitex_dev.storeat allrows()TypeErrorsThe change
scitex-dev>=0.49.2in both the runtime dependency set anddev, so the bad combination is refused at resolve time instead of failing later. Version 0.20.1. No code change — this is 0.20.0 with honest metadata.