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

eliot.testing.check_for_errors leaves logger.messages in an unpredictable state. #469

Open
tomprince opened this issue Jun 8, 2021 · 3 comments
Labels

Comments

@tomprince
Copy link
Contributor

It appears that it will serialize all messages, until the first one that does not validate, or none, if there are unflushed tracebacks.

@itamarst itamarst added the bug label Jun 8, 2021
@itamarst
Copy link
Owner

itamarst commented Jun 8, 2021

Thanks for the bug report!

Seems like it should always serialize all messages and just report multiple errors if it finds them, given what it does. Any interest in submitting a PR?

And out of curiosity, what are you using Eliot for?

@tomprince
Copy link
Contributor Author

Seems like it should always serialize all messages and just report multiple errors if it finds them, given what it does.

That seems sensible.

Any interest in submitting a PR?

I'm probably not going to do so soon, as I've worked around it locally, and am stuck on a python 2 version at the moment.

And out of curiosity, what are you using Eliot for?

I ran into this working on https://github.com/LeastAuthority/magic-folder

@itamarst
Copy link
Owner

Cool, I'm actually finishing up the port of Tahoe-LAFS to Python 3 at the moment.

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

No branches or pull requests

2 participants