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
S3 filesystem pure virtual method called; terminate called without an active exception #1912
Comments
Can we please verify why the latest so exhibiting this issue. Thank you |
I had the same issue and it was driving me insane. I have some unrelated custom c++ ops and wasted a day digging into those. I am using s3 and going back to 0.34.0 fixed it. |
Facing the same issue but for I've also faced the same error with |
As an update, I followed the build instructions for tensorflow-io (Ubuntu 22.04 and then Python Wheels), and discovered that this particular Note: The link in the docker build instructions is broken - https://github.com/tensorflow/io/blob/master/docs/development.md#docker - and the latest image in tfsigio/tfio is about 2 years old. |
@saimi Is there any chance you can please post the steps you took to build? I tried to build but was thwarted by the issues you mentioned. |
@rivershah I pulled the
and installed all the packages and bazel as instructed in https://github.com/tensorflow/io/blob/master/docs/development.md#ubuntu-2204 (without the
I then followed the instructions at https://github.com/tensorflow/io/blob/master/docs/development.md#python-wheels:
Then, within the same container, I was able to validate tf-io's S3 filesystem functionality by trying to checkpoint a model to S3. I'll need to do some additional work to reproduce the failure I got when copying the generated tf-io wheel out into a different container, since I've terminated all of that setup now. |
Bumping this issue. Needs looking at to ensure build process handling correctly |
This problem persists in |
I am getting a core dump during interpreter teardown, when using the s3 filesystem. Can I please be given guidance how to handle this issue. Please see script to reproduce inside docker:
FROM tensorflow/tensorflow:2.14.0-gpu
The following environment variables are set
The text was updated successfully, but these errors were encountered: