## Expected Behavior Feast should not crash. ## Current Behavior As commented in 028cc20a28118bd31deca8965782d5ad25f74300, Feast crashes with protobuf>=4.24.0. The most recent version of protobuf that Feast can use is 4.23 which stopped being supported in August of 2023 <https://protobuf.dev/support/version-support/> ## Steps to reproduce I see this on `feast apply`, the original report is unclear.
Activity
shuchu commentedon Feb 2, 2024
this one seems an urgent bug.
shuchu commentedon Feb 18, 2024
working on this. I do see segmentation errors.
shuchu commentedon Mar 8, 2024
I find this related issue from protobuf's Github repo: protocolbuffers/protobuf#13485 , especially, this comment: protocolbuffers/protobuf#13485 (comment)
cburroughs commentedon Mar 8, 2024
Nice find. That seems to suggest the Feast constraint should be something along the lines be <24, or >=25?
shuchu commentedon Mar 8, 2024
I have found the cause of this segment fault. Will have a PR to fix it today.
shuchu commentedon Mar 8, 2024
Here is a piece of example code that can repoduce the segmentation fault:
Please change the repo file path accordingly in your own computer.
jeremyary commentedon Mar 8, 2024
notable_trollis my new favoriteinitoutput 😆shuchu commentedon Mar 8, 2024
Right now, I use ">=4.24.0". I pass the test with 4.25.3