You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I believe the expectation is that dpm.replies() can be called to provide an async generator. I don't think this makes sense if the list isn't started. Right now, this function doesn't ensure that the list is started.
To Reproduce
Steps to reproduce the behavior:
#!/usr/bin/env python3importsysimportacsys.dpmasyncdefmy_app(con):
# Setup contextasyncwithacsys.dpm.DPMContext(con) asdpm:
# Add acquisition requestsawaitdpm.add_entry(0, "M:OUTTMP")
# This code doesn't work without this next line# dpm.start()# Process incoming dataasyncforevt_resindpm.replies():
ifevt_res.isReading:
print(evt_res)
else:
print(f"ERROR: {evt_res}")
acsys.run_client(my_app)
This runs but hangs because there are never messages, and we never start the list.
Expected behavior
See above
Environment (please complete the following information):
[Python]
The text was updated successfully, but these errors were encountered:
Describe the bug
I believe the expectation is that dpm.replies() can be called to provide an async generator. I don't think this makes sense if the list isn't started. Right now, this function doesn't ensure that the list is started.
To Reproduce
Steps to reproduce the behavior:
This runs but hangs because there are never messages, and we never start the list.
Expected behavior
See above
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: