Skip to content
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

assert from write_ready #77

Open
billpriest opened this issue Jan 5, 2022 · 0 comments
Open

assert from write_ready #77

billpriest opened this issue Jan 5, 2022 · 0 comments

Comments

@billpriest
Copy link

I have a low bandwidth serial read/write (read ~16 bytes at 0.5 Hz/~16 bytes at 1.0 Hz). I've confirmed that I only have one transport.write and that the amount of data being written is always > 0. Periodically, I see a stack trace where an is raised
assert data, 'Write buffer should not be empty'
I added if len(data) == 0: print("len = 0") and set a breakpoint on it. The callstack showed the following
_run, events.py:80
_run_once, base_events.py:1890
run_forever, base_events.py:596

I set breakpoints on connection lost and didn't hit that and I don't believe that the transport was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant