Error starting timeout

[Mte90]

I am getting this error maybe is connected to #403?

The log when this error is happening: https://pastebin.com/qwGYmnFu

Anyway this error block the opening of the various buffers with the informations.

[dave2309]

After upgrading vdebug , I have the same error showing up during debug... when an ajax takes some times (difficult to measure that)

[BlackIkeEagle]

Could you create simple steps to reproduce? I have tried to reproduce but not yet encountered this socket.timeout issue

[BlackIkeEagle]

@Mte90 I don't think the timeout is related to the empty stacktrace

[Mte90]

when I tested I changed the code to get more seconds, as I can remember the error was still there.

[dave2309]

It is difficult to make steps to reproduce. But for me I can reproduce each time I have a process on backend that takes more than 30s to process. eg. series of ajax calls (short ones) are perfectly fine. Then one request needs to wait for a backend task to finish like an upload to some server, big file, upload times is more than 30s. then the error message appear on vim.
I have tested two versions of vim: (on ubuntu)
version: 2:8.1.2269-1ubuntu5
and version: 2:8.2.1767-0york0~20.04
same result

[dave2309]

Something I did which endup losing the connection.
Put a breakpoint at a first line method.
next is sleep(30);
then another breakpoint next line.

When running. Vim breaks at the first breakpoint. Then when pressing F5 then display a connection closed after around 5s.

actually sleep(4); passes, sleep(5); would break
Connection to the debugger has been closed

[dave2309]

So Error starting Vdebug: <class 'socket.timeout'> appears when performing an xhr call.
Otherwise the message is Connection to the debugger has been closed.
But both occur if the "task" takes more than 4s. until 4s everything is fine. 5s then errors shows up.

[BlackIkeEagle]

@dave2309 thanks, I'll look into it further

[dave2309]

I may have found something.
.vim/bundle/vdebug/python3/vdebug/connection.py
line 195
client.settimeout(5)

if change to
client.settimeout(5000)

error is gone. can you confirm @Mte90 ?

If it is the "culprit" maybe a configuration value would be interesting to define here connection.timeout or so... @BlackIkeEagle ?

[BlackIkeEagle]

@dave2309 the client should not set the timeout there, I overlooked that

[BlackIkeEagle]

Thanks for the additional input, this helped finding the issue

[dave2309]

nm
I use vdebug quite intensively. I would have love to PR but I don't have enough knowledge of vdebug internal to propose yet.
Glad I could help