Re: [Bug-wget] wget2 hanging, possible I/O issue

[Jeffrey Fetterman]

Few other notes: I am on the latest slow ring build, which is practically a
necessity if you're using WSL. The build I'm on is probably about to be
released publicly seeing as there's no version info on the desktop.

I did try this with Windows Firewall and my antivirus disabled.

I also tried this with openSUSE aside from learning that WSL openSUSE is a
mess, once I got it working I ran into the same issues as on WSL Debian &
WSL Ubuntu.

On Mon, Apr 2, 2018 at 3:59 PM, Jeffrey Fetterman <address@hidden>
wrote:

> oh, and the hang with HTTPS and repeating errors with HTTP is exactly the
> same issue I'm experiencing, yes.
>
> On Mon, Apr 2, 2018 at 3:59 PM, Jeffrey Fetterman <address@hidden>
> wrote:
>
>> Why'd you use your wife's laptop? You can have Debian and Ubuntu
>> installed on the same machine. Typing 'bash' in command prompt will go to
>> your primary (generally the first one you installed) and you just type the
>> OS name to get one specifically.
>>
>> I was thinking of trying to get it running on openSUSE but I'm worried
>> I'd just run into the same issue.
>>
>> On Mon, Apr 2, 2018 at 3:55 PM, Tim Rühsen <address@hidden> wrote:
>>
>>> Hi Jeffrey,
>>>
>>>
>>> back then I installed Ubuntu via WSL. A fresh build of Wget2 took
>>> ~30mins on my wife's laptop. Time-wasting.
>>>
>>> But I can reproduce a hang with HTTPS and (repeating) errors with HTTP.
>>>
>>>
>>> This might be an issue with Windows Sockets... maybe someone has a
>>> faster machine to do some testing !?
>>>
>>>
>>> Regards, Tim
>>>
>>> On 02.04.2018 19:30, Jeffrey Fetterman wrote:
>>> > I can tell you the exact steps I took from nothing to a fresh install,
>>> > I have the commands copied.
>>> >
>>> > install Debian from Windows Store, set up username/password
>>> >
>>> > $ sudo sh -c "echo kernel.yama.ptrace_scope = 0 >>
>>> > /etc/sysctl.d/10-ptrace.conf; sysctl --system -a -p | grep yama"
>>> > (this is a workaround for Valgrind and anything else that relies
>>> > on prctl(PR_SET_PTRACER) and the wget2 problem will occur either way)
>>> >
>>> > $ sudo apt-get update
>>> > $ sudo apt-get upgrade
>>> > $ sudo apt-get install autoconf autogen automake autopoint doxygen
>>> > flex gettext git gperf lcov libtool lzip make pandoc python3.5
>>> > pkg-config texinfo valgrind libbz2-dev libgnutls28-dev libgpgme11-dev
>>> > libiconv-hook-dev libidn2-0-dev liblzma-dev libnghttp2-dev
>>> > libmicrohttpd-dev libpcre3-dev libpsl-dev libunistring-dev zlib1g-dev
>>> > $ sudo update-alternatives --install /usr/bin/python python
>>> > /usr/bin/python3.5 1
>>> >
>>> > then the commands outlined as per the documentation. config.log
>>> attached.
>>> >
>>> > On Mon, Apr 2, 2018 at 11:53 AM, Tim Rühsen <address@hidden
>>> > <mailto:address@hidden>> wrote:
>>> >
>>> >     Hi Jeffrey,
>>> >
>>> >
>>> >     basically wget2 should work on WSL, I just tested it scarcely two
>>> >     weeks
>>> >     ago without issues.
>>> >
>>> >
>>> >     I suspect it might have to do with your dependencies (e.g. did you
>>> >     install libnghttp2-dev ?).
>>> >
>>> >     To find out, please send your config.log. That allows me to see
>>> your
>>> >     compiler, CFLAGS and the detected dependencies etc..
>>> >
>>> >     I will try to reproduce the issue then.
>>> >
>>> >
>>> >     Regards, Tim
>>> >
>>> >
>>> >     On 02.04.2018 17:42, Jeffrey Fetterman wrote:
>>> >     >  wget2 will not download any files, and I think there's some
>>> >     sort of disk
>>> >     > access issue.
>>> >     >
>>> >     > this is on Windows Subsystem for Linux Debian 9.3 Stretch.
>>> >     (Ubuntu 16.04
>>> >     > LTS had the same issue.)
>>> >     >
>>> >     > Here's the output of strace -o strace.txt -ff wget2
>>> >     https://www.google.com
>>> >     >
>>> >     > https://pastebin.com/4MEL88qs
>>> >     >
>>> >     > wget2 -d https://www.google.com just hangs after the line
>>> >     '02.103350.008
>>> >     > ALPN offering http/1.1'
>>> >     >
>>> >     > ultimately I might have to submit a bug to WSL but I wouldn't
>>> >     know what to
>>> >     > report, I don't know what's wrong. And it'd be great if there
>>> was a
>>> >     > workaround
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>
>