Newline in error message breaks intake

[rebecca-palmer]

Describe the issue:

Since #9677, some dask error messages (e.g. file not found) have included a newline.

intake forwards error messages in a way that doesn't allow newlines, and hence fails its tests: failure log.

This could be fixed in dask by removing the newline (but keeping the rest of the new wording). I don't know if it could reasonably instead be fixed in intake: @martindurant

Environment:

• Dask version: 2022.12
• Python version: fails in both 3.10 and 3.11
• Operating System: Ubuntu

[martindurant]

Would be happy to fix it in intake. We can transfer the issue or perhaps close this one. Do you think you make a simple non-dask reproducer?

[jrbourbeau]

Thanks for the issue @rebecca-palmer and for handling things in intake @martindurant

[rebecca-palmer]

It's something I ran across in a "what breaks if we update dask" mass-rebuild: I don't actually use intake. The obvious starting point would be the code for the test that failed.

[ncclementi]

From the logs, it seems the ValueError due to the new line is raised in tornado more specifically, here https://github.com/tornadoweb/tornado/blob/b726f6d66133189a1cf25a695e4e1c96d70c713b/tornado/http1connection.py#L455-L457