Skip to content

Make observed_value_field optional in TFTInstanceSplitter #3259

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

Merged
merged 4 commits into from
Jun 27, 2025

Conversation

abdulfatir
Copy link
Contributor

@abdulfatir abdulfatir commented Jun 24, 2025

Issue #, if available: N/A

Description of changes: Previously, TFTInstanceSplitter assumed that the observed_value_field is always present in the entry. This PR fixes that.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

@abdulfatir abdulfatir changed the title Make observed_values field optional in TFT Make observed_values field optional in TFTInstanceSplitter Jun 24, 2025
@abdulfatir abdulfatir changed the title Make observed_values field optional in TFTInstanceSplitter Make observed_value_field optional in TFTInstanceSplitter Jun 24, 2025
@abdulfatir abdulfatir requested a review from shchur June 24, 2025 22:08
shchur
shchur previously approved these changes Jun 25, 2025
Copy link
Contributor

@shchur shchur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@abdulfatir abdulfatir enabled auto-merge (squash) June 26, 2025 20:40
@abdulfatir abdulfatir requested a review from lostella June 26, 2025 21:05
@abdulfatir abdulfatir disabled auto-merge June 26, 2025 21:05
@abdulfatir
Copy link
Contributor Author

@shchur @lostella there's an issue with statsmodels accessing private API of scipy which is breaking our CI. Do the version caps look reasonable to you? See: statsmodels/statsmodels#9584

@@ -1 +1,4 @@
# scipy cap can be removed once this is resolved: https://github.com/statsmodels/statsmodels/issues/9584
scipy<1.16.0; python_version > "3.7.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version cap looks reasonable to me

@@ -1 +1,4 @@
# scipy cap can be removed once this is resolved: https://github.com/statsmodels/statsmodels/issues/9584
scipy<1.16.0; python_version > "3.7.0"
scipy~=1.7.3; python_version <= "3.7.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just skip this completely: Python 3.8 is already EOL for a while so we don't need to worry about it

Copy link
Contributor

@lostella lostella Jun 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's just a bit redundant, but since there may be EOL versions of Python running and doing stuff 🤖 doesn't hurt to leave it like this

@lostella lostella added the new feature (one of pr required labels) label Jun 27, 2025
@abdulfatir abdulfatir merged commit 8a1bc0f into awslabs:dev Jun 27, 2025
18 checks passed
@lostella lostella added bug fix (one of pr required labels) pending v0.16.x backport This contains a fix to be backported to the v0.16.x branch and removed new feature (one of pr required labels) labels Jun 27, 2025
lostella pushed a commit to lostella/gluonts that referenced this pull request Jun 27, 2025
*Issue #, if available:* N/A

*Description of changes:* Previously, `TFTInstanceSplitter` assumed that
the `observed_value_field` is always present in the entry. This PR fixes
that.


By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.


**Please tag this pr with at least one of these labels to make our
release process faster:** BREAKING, new feature, bug fix, other change,
dev setup
@lostella lostella mentioned this pull request Jun 27, 2025
lostella added a commit that referenced this pull request Jun 27, 2025
*Description of changes:* backport changes
- #3259 
- #3261

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.


**Please tag this pr with at least one of these labels to make our
release process faster:** BREAKING, new feature, bug fix, other change,
dev setup

---------

Co-authored-by: Abdul Fatir <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix (one of pr required labels) pending v0.16.x backport This contains a fix to be backported to the v0.16.x branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants