Closed TonyBagnall closed 2 days ago
aeon
I have added the following labels to this PR based on the title: [ $\color{#d73a4a}{\textsf{bug}}$ ]. I would have added the following labels to this PR based on the changes made: [ $\color{#41A8F6}{\textsf{transformations}}$ ], however some package labels are already present.
The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.
If our pre-commit
code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.
Don't hesitate to ask questions on the aeon
Slack channel if you have any.
These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.
pre-commit
checks for all filespytest
tests and configurationscodecov
testspre-commit
fixes (always disabled for drafts)The metadata update should not really be happening in the first place. See https://github.com/aeon-toolkit/aeon/pull/1479 which disables it.
The metadata update should not really be happening in the first place. See #1479 which disables it.
dont actually agree with this, meta data storage should be possible when passed as kwargs to save time, useful with very large datasets, but Im ok to go with #1479 instead of this
fixes #1750 with simplest solution