Shuchu Han
Shuchu Han
do you mind to try "pip install `feast[aws, gcp]`. and define the feature_store.yaml accordingly as your current setup.
It was fixed and we are good to close it.:)
this one seems an urgent bug.
working on this. I do see segmentation errors.
I find this related issue from protobuf's Github repo: https://github.com/protocolbuffers/protobuf/issues/13485 , especially, this comment: https://github.com/protocolbuffers/protobuf/issues/13485#issuecomment-1686758403
I have found the cause of this segment fault. Will have a PR to fix it today.
Here is a piece of example code that can repoduce the segmentation fault: Please change the repo file path accordingly in your own computer. ```python from pathlib import Path from...
> Nice find. That seems to suggest the Feast constraint should be something along the lines be =25? Right now, I use ">=4.24.0". I pass the test with 4.25.3
hi @pmayd I assume you were following the tutorial and used FileSource (offline storage) as the DataSource. The "get_table_query_string()" function is not implemented as shown by the source code: https://rtd.feast.dev/en/latest/_modules/feast/infra/offline_stores/file_source.html#FileSource.get_table_query_string...
Feast uses the Python3.8/3.9 images as base images. The [Python3.10](https://hub.docker.com/layers/library/python/3.10/images/sha256-0a2e6600fb65626cb06681b3d289b59163063e76b2bfe373cceb33fc01d148d8?context=explore) does not seem to have high Vulnerabilities. I'll keep an eyeeye on this when we do the upgration. It will...