Skip to content
Discussion options

You must be logged in to vote

yeah, this matches the already-fixed v0.14.0 installer bug in #1179 / #1194.

I reproduced it with the v0.14.0 release wheel in a clean Python 3.12 venv: ANOMALY_AVAILABLE is false, but WorkflowsRunner.all() still tries to create AnomalyTrainerWorkflow, so it raises the same NameError. Running the same call against current main at 99e47bd returns tasks successfully.

So dqx@latest is still picking up the May 5 release asset. Until a release after #1194 is cut, I'd use the workaround from #1179: apply that patch locally and install offline, or use a build from current main if that's available in your setup.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@mwojtyczka
Comment options

Answer selected by ghanse
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants