-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Bug]: asyncio ERROR:Future exception was never retrieved #1012
Comments
That's a confusing set of issues you're getting there, and I have no idea where to start tbh. All the issues seem to be within playwright, and not directly related to code in lacus/lookyloo/playwrightcapture. The only context I sometimes see asyncio exceptions like that is when the app is killed with signals instead of running What do you mean by |
I mean submitting a request to a screen capture. |
lookyloo-background_processing logs has more but not really easy to interpret
doing the basic aka stupid extract, but it works
are there some global variables that could influence this function? lookyloo-async_capture_message.log just has the asyncio error future exception with the 30s timeout. cli I also tried aside where no proxy is required and
I also tried to disable the systemd restrictions that are included in my role, just in case, but that does not change anything. |
I'm running lookyloo, on anything from Ubuntu 22.04 to 24.10 and have absolutely no issue. The one you're having is pretty fondamental and I have no idea where it can come from. All the mentions of similar errors in the issues of playwright seem to be linked to somewhat broken virtual environments and I have no clue how ansible is doing all that. |
What happened?
I recently did a refresh of my ansible roles, among them one for lookyloo.
It was bumped to latest version (1.27.0, Ubuntu 24.04) but there is still some issue when asking for screenshot that I did not figure out for now.
System is behind a proxy which is configured in lookyloo generic.json (global_proxy).
Is there any other place that needs to be configured for proxy?
Where else can I check to debug this?
Without proxy, it fails elsewhere per github action:
https://github.com/juju4/ansible-lookyloo/actions/runs/12215830703/job/34078270688#step:15:344
Possibly related to microsoft/playwright-python#2276
If the issue is related to the web interface, what browsers are you seeing the problem on?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: