-
Notifications
You must be signed in to change notification settings - Fork 602
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
virtual_can_demo.py changes #373
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #373 +/- ##
===========================================
- Coverage 58.85% 57.08% -1.77%
===========================================
Files 54 57 +3
Lines 4214 4348 +134
===========================================
+ Hits 2480 2482 +2
- Misses 1734 1866 +132
Continue to review full report at Codecov.
|
examples/virtual_can_demo.py
Outdated
|
||
# TODO Issue #3: Need to keep running to ensure the writing threads stay alive. ? | ||
time.sleep(2) | ||
with can.ThreadSafeBus(bustype='socketcan', channel='vcan0') as bus: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'm missing something @felixdivo - what are you trying to protect by introducing the thread safe bus here?
As I understand it each executor function call (several will be running concurrently in separate processes) is creating its own can.ThreadSafeBus
. If there are no threads sharing one ThreadSafeBus
is there any point using it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, I was apparently confused.
No description provided.