-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TSML: Error in timeseries-anomaly-detection.ipynb
#426
Comments
Observationsscikit-learn 1.4.2 was released on Apr 9, 2024. Is it related? -- https://pypi.org/project/scikit-learn/1.4.2/#history ThoughtsIf it is, the reason why the corresponding CI job did not fail before more prominently, on the nightly runs to validate functionality, is most probably because dependencies are configured to be cached when the local In this case, the nightly CI jobs do not catch updates to transitive dependencies not enumerated locally, and thus, do not hold up to their promise to give you a constant piece of mind in "on stage" situations. In this spirit, what is reflected on the Build Status page, might not convey the whole truth, and I am sad about it. |
I am able to confirm this error on my workstation, using Python 3.11.
ValueError: Found array with 0 sample(s) (shape=(0, 1)) while a minimum of 1 is required by SimpleImputer. However, I am also seeing this one, where the second one might actually be a follow-up error. ProgrammingError: (crate.client.exceptions.ProgrammingError) RelationAlreadyExists[Relation 'notebook.machine_data' already exists.]
[SQL: CREATE TABLE machine_data ("timestamp" TIMESTAMP, "value" DOUBLE PRECISION)] |
On behalf of GH-425, the -- https://github.com/crate/cratedb-examples/actions/runs/8744363838/job/23997048918?pr=425#step:6:951 |
Taking a closer look, |
Problem
The
timeseries-anomaly-detection.ipynb
notebook errors out, both on Python 3.10 and 3.11 12.Observations
Because it happens on both versions of Python, it is most probably unrelated to the change per se where it started tripping.
Thoughts
Most probably another dependency flaw?
Footnotes
https://github.com/crate/cratedb-examples/actions/runs/8743815972/job/23995257165?pr=425#step:6:1505 ↩
https://github.com/crate/cratedb-examples/actions/runs/8743815972/job/23995257591?pr=425#step:6:1350 ↩
The text was updated successfully, but these errors were encountered: