Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ytreister
Copy link
Contributor

I was curious to see the asyncio in action and the debug logging did not make it clear which WorkerPlugin completed it's scan. I added this in this PR.

Here is what the log looks like now (red underline for what I added):
image

I am not sure the asyncio is behaving as I expected it to. I always see something like this:

Starting scan...A
Completed scan...A
Starting scan...B
Completed scan...B
Starting scan...C
Completed scan...C
Starting scan... D
Completed scan...D

I would have expected something more like:

Starting scan...A
Starting scan...B
Starting scan...C
Completed scan...B
Starting scan... D
Completed scan...A
Completed scan...C
Completed scan...D

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.44% when pulling 9eb9498 on ytreister:worker_debug_logging into bc51d67 on PUNCH-Cyber:master.

@mlaferrera mlaferrera self-assigned this Apr 9, 2020
@mlaferrera mlaferrera merged commit 674408f into PUNCH-Cyber:master Apr 9, 2020
@mlaferrera
Copy link
Contributor

Looks good, thanks again!

@ytreister
Copy link
Contributor Author

@mlaferrera Thanks, can you please answer my question in this PR? I just want to make sure that there is not a bug with the framework...

@ytreister ytreister deleted the worker_debug_logging branch December 12, 2021 00:30
fyodorr pushed a commit to fyodorr/stoq that referenced this pull request Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants