🐞 Service stops responding · Issue #112...

[snow steppe]

Hello! I am not familiar with playwright, here is what I get, how do I verify if it's failing or not?

[tawny zealot]

When clicking on each of the tests you should be seeing the visuals of the website being tested on that white square. Also if you click on the tabs below (Source, Log, etc) you should see their content. You can click those buttons and check the network errors in the developer console. Also the docker logs will report the health check “failed fatally”.

[tawny zealot]

I'd be happy to work on this issue myself if someone could give me some pointers.

[summer arrow]

Hey there! Sorry we weren't able to get back quickly here. The past week we were at the company offsite and we briefly looked at help requests. Ping me on Monday so we can help you out here 🙏

[tawny zealot]

@summer arrow ping 😉

[summer arrow]

pong. adding this to my list today

[tawny zealot]

Double ping 🙂

[summer arrow]

sorry, still catching up with things 🙏

[summer arrow]

@tawny zealot I can't seem to be able to repro. Seems to be working on here. I've made a recording about it

[tawny zealot]

I'm gonna try on a different machine.

[summer arrow]

what setup are you currently running this on?

[tawny zealot]

I have now reproduced in a MacStudio running OBS, a MacBook Air also running OBS and finally reproduced in a Linux machine running Ubuntu with vanilla Docker.

Your reproduction video is too short, you need to click around more and wait a minute for things to break.

Also, open the dev tools (F12) to check network errors and requests that stay pending forever

[summer arrow]

Gotcha. Will try again tomorrow

[summer arrow]

@tawny zealot by any chance are you using Chrome to test this? I can see the pending requests in Chrome but when I use firefox or just plain curl that doesn't seem to happen

[tawny zealot]

Yep, but that's so weird:

• Docker + Firefox ✅
• Dagger + Firefox ✅
• Docker + Chrome ✅
• Dagger + Chrome ❌

Thanks for finding a workaround though.

[snow steppe]

Maybe some interference between 1) dagger builtin healthcheck 2) chrome smarty-pants pre-fetching 3) one of the endpoints not being tolerant of multiple connections?