You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
ffprobe version N-48944-g9b069eb14e-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2007-2019 the FFmpeg developers
built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
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:
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.
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: