-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
On some systems, resolving Google Drive fails #135
Comments
+1 I believe it's related to this issue: Essentially, it seems dns resolution is affected. I was facing the same issue with another static library before moving to this one. My issue is the same as yours in that it fails in the docker environment, but passes locally on my mac. |
I shall update all the builds within the next day or 2 Let's hope that helps :) |
Guys, update to v1.2.0 with all new binaries and let's hope! |
No updates, closing. |
Lets hope? Wild. Its still an issue. |
We have encountered an issue with GoogleDrive on some of our developer systems.
We are using ffprobe @ 1.1.0, which depends on
"@ffprobe-installer/linux-x64": "4.1.0",
which installs this version:
And when I run this binary:
The key is in the penultimate line:
[tcp @ 0x7011dc0] Failed to resolve hostname doc-0k-30-docs.googleusercontent.com: System error
Note that simply running the ffprobe that I have on my own system, the same command runs without any errors.
So I guess it must be the ffprobe version in question, or one of the statically linked libraries.
The trick is that at another developer box, the same issue doesn't manifest... so it might be tricky to test this.
(I am willing to help.)
I guess we should move away from the ffprobe build from 2017?
Thanks.
The text was updated successfully, but these errors were encountered: