-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: changed threadpool -> malebolgia #88
base: main
Are you sure you want to change the base?
Conversation
@YamatoSecurity
|
I have opened the following issue. |
It's already fixed in the development branch(not released yet)😁 I'm starting to think it's okay to merge...😅 Anyway, I'll test it first! |
Environment
TEST(macOS)I confirmed that all VT commands are successful as shown below. vt-domain-lookup
vt-ip-lookup
vt-hash-lookup
|
Environment
TEST(Linux)I confirmed that all VT commands are successful as shown below. vt-domain-lookup
vt-ip-lookup
vt-hash-lookup
|
Environment
TEST(Windows)I confirmed that all VT commands are successful as shown below. vt-domain-lookup
vt-ip-lookup
vt-hash-lookup
|
I have confirmed normal operation on Windows, Ubuntu, and macOS! |
@fukusuket |
@YamatoSecurity |
I tried v2.0.4 but the warning issue was not resolved :( |
@fukusuket That's too bad. Since this seems to be a nim issue, can you raise an issue in the nim repository and include error logs for them to look at? |
@YamatoSecurity issue: |
I tried v2.0.6 but the warning issue was not resolved :( |
@fukusuket Humm. I tried with the latest 2.0.8 but it is still not resolved. Maybe we should notify them again? |
What Changed
spawn
in VT lookup commands #81threadpool
tomalebolgia