Replies: 2 comments
-
Hi @Karreg, thanks for reaching out. I'm against doing this at the moment as filtering the output risks us removing context that might have value. What we might want to do instead is buffer output from the draw.io sub processes and only print it on a failed export (e.g. non-zero exit status or successful exit without the expected output file being written). I'm afraid I'm unlikely to do this work in the foreseeable future as I'd prefer to move away from shelling out to the CLI (see #16). |
Beta Was this translation helpful? Give feedback.
-
The idea was to propose options to filter out, not filter out by default :) But I get the other part. I have seen this issue, I was thinking of a more tactical change. However, for the record, as it might help other people , I have fixed the issue by filtering the In case the original repository disappears, here if the command:
It can still be disabled in case of error to get the full logs... Thanks for your work, this is awesome! I need to check if my company can donate... |
Beta Was this translation helpful? Give feedback.
-
Hello,
I know the chromium headless dbus dependency is a long running issue, but a quick hack could be to filter related logs.
The warnings pollute the terminal output, and with devcontainer getting more traction, this use case will be more and more frequent.
I have created such an image here: https://gitlab.com/karreg/docker-mkdocs
And I was wondering if it could/should be possible to implement a (long running?) temporary solution to filter out such logs, like this.
Initial:
Hack:
Of course the list is not exhaustive. My idea was to not hard code these lines, but make them configurable.
I have tried different things, but I was not able to find a way to do this currently between xvfb-run and drawio options...
What do you think?
Regards.
Beta Was this translation helpful? Give feedback.
All reactions