11761 2017-07-05 21:32:11 +0000 Broken pipe when paginating bitbake -e 2017-07-06 15:11:58 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.4 x86 Multiple RESOLVED NOTABUG Undecided minor --- 1 leonardo.sandoval.gonzalez richard.purdie poky.bs.watcher poky.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 74792 0 leonardo.sandoval.gonzalez 2017-07-05 21:32:11 +0000 If 'less' is quit ('q') in the first page where input comes from bitbake -e, the following error occurs: $ bitbake -e | less Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'> BrokenPipeError: [Errno 32] Broken pipe Seems that the errno.EPIPE should be caught somewhere instead of passing it to the console. 74819 1 richard.purdie 2017-07-06 15:11:58 +0000 If less quits, bitbake loses its stdout. Its reasonable it prints a pipe error at this point which is what a standard commandline utility would do. The alternative is to silently swallow an error when stdout has disappeared and we still have output which seems worse to me so I don't think we can improve this as described.