-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
thread 'tokio-runtime-worker' panicked #1508
Comments
Couldn't reproduce with:
Works as expected. You have to provide more detail about your environment, or error details. |
It usually happens after running tests for my job. I'll try to narrow it down, but I cannot share the exact setup |
Do you have debuginfod url for it? I could get a stacktrace from the coredump |
The release build may have already stripped all symbols, please try to build from source and run a debug build. But I don't think stacktrace is useful, because the key issue is not where it panic (which is very obvious in logs), but why the timer is not initialized in your case. Which system are you running on? Linux? Which kernel version? |
yes, it's {
"server": "::",
"server_port": 443,
"method": "aes-256-gcm",
"password": "redacted",
"plugin_opts": "mode=quic;host=github.com",
"plugin_args": [
"--verbose"
],
"plugin_mode": "tcp_and_udp",
"timeout": 7200
} |
Couldn't reproduce on my laptop. Maybe you could try to upgrade/downgrade your ArchLinux version. |
config:
logs:
The text was updated successfully, but these errors were encountered: