QA » openQA Project

Motivation¶

See #92013#note-10 : The OBS rsync GUI and its interaction with Minion jobs can still be optimized. The GUI allows to trigger Minion jobs and shows their results - but when a job doesn't complete within a hard-coded time limit the only way to view the result is to trigger the Minion job again and to hope it now completes within that time limit.

The save button within the needle editor has the same interaction with Minion jobs. Here we delay the response until the Minion job has completed. Of course this is also not 100 % ideal because if the job takes very long to complete the HTTP request might timeout. However, this way we still have a much higher time limit and if the job completes fast this is also visible fast in the UI. So I'd say the UI should at least work like the needle editor's one (or we might even find a better way¹).

¹ As discussed in the chat, client-side polling might be preferable. Using a web socket connection and even introducing redis/rabbitmq (for pub/sub messaging from the job to get rid of polling completely) is possible but likely over-engineering.