Richard Purdie 759a3eb9b5 bitbake: server/process: Fix logging issues where only the first message was displayed ... I realised only the first logging message was being displayed in a given parsing process. The reason turned out to be the UI handler failing with a "pop from empty list". The default handler was then lost and no further messages were processed. Fix this by catching the exception correctly in the connection writer code. (Bitbake rev: b8fd6f5d9959d27176ea016c249cf6d35ac8ba03) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d3e64f64525187f1409531a0bd99df576e627f7f) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2022-06-26 22:55:39 +01:00
..
__init__.py	bitbake: bitbake: Drop duplicate license boilerplace text	2019-05-04 10:44:10 +01:00
process.py	bitbake: server/process: Fix logging issues where only the first message was displayed	2022-06-26 22:55:39 +01:00
xmlrpcclient.py	bitbake: lib: remove unused imports	2020-01-19 13:31:05 +00:00
xmlrpcserver.py	bitbake: server/xmlrpcserver: Add missing xmlrpcclient import	2022-03-08 09:45:57 +00:00