Skip to content
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

DATA LOADING ERROR #2

Closed
DaniChinwendu opened this issue Jan 16, 2025 · 10 comments
Closed

DATA LOADING ERROR #2

DaniChinwendu opened this issue Jan 16, 2025 · 10 comments

Comments

@DaniChinwendu
Copy link

025-01-16 01:22:45.411 | WARNING | polaris.dataset._base:zarr_root:179 - You're loading data from a remote location. If the dataset is small enough, consider caching the dataset first using CompetitionSpecification.cache() for more performant data access.

ClientError Traceback (most recent call last)
/usr/local/lib/python3.11/dist-packages/polaris/hub/storage.py in handle_s3_errors()
45 try:
---> 46 yield
47 except ClientError as e:

15 frames
ClientError: An error occurred (NotImplemented) when calling the GetObject operation: Header 'x-amz-checksum-mode' with value 'ENABLED' not implemented

The above exception was the direct cause of the following exception:

S3StoreException Traceback (most recent call last)
[... skipping hidden 1 frame]

/usr/local/lib/python3.11/dist-packages/polaris/hub/storage.py in handle_s3_errors()
50 raise S3StoreCredentialsExpiredException(f"Error in S3Store: Credentials expired: {e}") from e
51 else:
---> 52 raise S3StoreException(f"Error in S3Store: {e}") from e
53 except BotoCoreError as e:
54 raise S3StoreException(f"Error in S3Store: {e}") from e

S3StoreException: Error in S3Store: An error occurred (NotImplemented) when calling the GetObject operation: Header 'x-amz-checksum-mode' with value 'ENABLED' not implemented

@DaniChinwendu DaniChinwendu changed the title DATA lOADING ERROR DATA LOADING ERROR Jan 16, 2025
@cwognum
Copy link
Collaborator

cwognum commented Jan 16, 2025

Hi @DaniChinwendu , thanks for reaching out. This is related to Polaris and it would be best to open an issue in the Polaris repo.

In the meantime, I suspect you're not actually connecting to the Polaris Hub, but have configured your environment to connect to some other S3 compatible store.

To test this hypothesis, can you make sure you haven't set any of the following environment variables: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html#using-environment-variables

@DaniChinwendu
Copy link
Author

DaniChinwendu commented Jan 16, 2025 via email

@cwognum
Copy link
Collaborator

cwognum commented Jan 16, 2025

I understand! I meant to say that I think your environment is making you actually connect to a different S3 compatible store. We use boto3 under the hood, which is used by many projects. You therefore may have (unknowingly) configured those environment variables for another project before.

@DaniChinwendu
Copy link
Author

DaniChinwendu commented Jan 16, 2025 via email

@cwognum
Copy link
Collaborator

cwognum commented Jan 16, 2025

If that's not the case, I will ask you to create an issue in the Polaris repo. That will prompt you to fill put some additional info that will help the team investigate.

@DaniChinwendu
Copy link
Author

DaniChinwendu commented Jan 16, 2025 via email

@srdjanma
Copy link

Hi, I am experiencing the same error when trying to load competition data, its a bit annoying to have unnecessary hussle..Hope they help us sort out the issue! :)

@jhud
Copy link

jhud commented Jan 16, 2025

I'm also getting this error using CloudFlare object storage in a totally unrelated project, and I can't find this error anywhere else on the internet. Only change I have made is the upgrade from boto3 package version 1.35 to 1.36. It might be related to that.

@cwognum
Copy link
Collaborator

cwognum commented Jan 16, 2025

Hi @jhud and @srdjanma , thanks for sharing! We're looking into it. For now, I'll close this issue in favour of polaris-hub/polaris#246 .

@cwognum cwognum closed this as completed Jan 16, 2025
@cwognum
Copy link
Collaborator

cwognum commented Jan 16, 2025

FYI - It's due to a breaking change upstream from Polaris (in boto3, see boto/boto3#4392). The solution is to downgrade to boto3<1.36.0. We will release a fix shortly that pins the boto3 version (see polaris-hub/polaris#247).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants