-
Notifications
You must be signed in to change notification settings - Fork 20
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
OSError: Cannot call rmtree on a symbolic link #224
Comments
@ThierryDeruyttere - Thanks very much for logging, and I'm sorry you have been running into this. Can you tell me which OS you are using (windows or mac)? And do you have information on which directory is trying to be deleted? Any information about what runtime you are using could also be helpful. This error implies that symlinks are being provided and trying to be deleted. |
@aaronsteers Sorry for my late reply! This is on a linux machine. It's trying to delete a temporary directory.
This is not 100% related to airbyte i think because it comes from tempfile.py but I can't provide my own tempfile through airbyte so I can't fix this problem... |
@ThierryDeruyttere - Thanks for providing the more complete stack trace. I see here this is stemming from inside the source-facebook-marketing connector, and specifically within a piece of code managed by the CDK. As a next step, we can check if that connector is using the latest version of the CDK, and if so, we can try to reproduce the issue either in the CDK itself or with that connector running in another Linux environment. If you see the same error with any other source connectors, please let us know. That would help us determine if it is more strongly correlated with the connector itself or with the runtime environment. |
Confirmed the Facebook Marketing source is using CDK version So, still no obvious explanation comes to mind for why this would cause an issue... 🤔 |
I think this might be because of the serverless compute provider that I'm using (modal). But also not 100% sure. |
@ThierryDeruyttere - Thanks for the additional context... I think your theory is correct regarding this being related to the Temp directory context managers are particularly problematic to implement in a cross-platform and cross-runtime manner. We've previously found implementation differences between Windows and Linux but I don't think we've specifically experienced this symlink-related issue before. It is likely correct that a 'create temp directory' request in |
I sometimes receive the following error.
I have no idea what causes it and when it's triggered but this is pretty annoying to suddenly have after your job ran for 1h.
The text was updated successfully, but these errors were encountered: