Project

General

Profile

Actions

action #45278

closed

Improve developer mode for re-needling use case

Added by mkittler over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2018-12-18
Due date:
% Done:

0%

Estimated time:

Description

After a re-needling session with @okurz we noticed that there's room for improvement:

  • Remove the "job cancel" button. It can be clicked accidentally and people are wondering about the difference to the regular job cancel button (there is no difference).
  • Ensure tool-tips are disappearing when hiding a button.
  • Confirming the dialog for match level should work by pressing return.
  • Triggering a restart from the needle editor should open the right job.
  • The needle editor should not show wrong notifications about newly added needles.
    • After a short investigation it seems there's nothing wrong with the code displaying those notifications. However, the t_updated flag of the entries in the needle database is updated unexpectedly.
  • Show the current command in the developer mode panel.
  • Add button to stop as soon as possible.
  • Wrap long lines in the live log.
  • Ensure the live log does not get too long. Otherwise the browser tab freezes at a certain length.
  • Resume directly from the needle editor.
  • (Re)start a job to open the developer mode directly and pause it as soon as possible.

Maybe it makes sense to create tickets for some of them and maybe we already have some tickets.

Striked-out points are already implemented in the PRs mentioned in the comment.


Related issues 1 (0 open1 closed)

Related to openQA Project - action #44969: Wrong 'new needle with matching tags has been created since the job started' warning messageResolvedmkittler2018-12-10

Actions
Actions #1

Updated by mkittler over 5 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
Actions #2

Updated by mkittler over 5 years ago

  • Description updated (diff)
Actions #3

Updated by mkittler over 5 years ago

  • Related to action #44969: Wrong 'new needle with matching tags has been created since the job started' warning message added
Actions #4

Updated by mkittler over 5 years ago

  • Description updated (diff)
Actions #5

Updated by mkittler over 5 years ago

  • Description updated (diff)
Actions #6

Updated by mkittler over 5 years ago

  • Description updated (diff)
Actions #7

Updated by mkittler over 5 years ago

  • Description updated (diff)
Actions #8

Updated by mkittler about 5 years ago

  • Status changed from In Progress to Resolved

The PRs have been merged.

The 2 remaining points wouldn't be that easy to implement. It also wouldn't gain us much (from my point of view) so likely not worth the effort.

Actions

Also available in: Atom PDF