Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

Long running "waiting for dependency" steps should notify the user #18

Open
Torxed opened this issue Jul 22, 2020 · 0 comments
Open

Long running "waiting for dependency" steps should notify the user #18

Torxed opened this issue Jul 22, 2020 · 0 comments
Labels
feature Feature request / suggestion
Milestone

Comments

@Torxed
Copy link
Owner

Torxed commented Jul 22, 2020

Currently, users can skip a step manually by clicking around in the left hand menu.
required steps will ping pong back the user to the first required step by traversing through the dependency steps.

But optional steps doesn't really have any requirements.
But the chain of spawn() calls is in sequential order, meaning if a step is hard-skipped, the spawn() chain will fail. This is partially by design - but a step that hasn't been "chosen" or "skipped" via the panel, should notify the user about the current hold.

Example:

  1. Select a drive
  2. Skip encryption
  3. Skip mirrors (by using default)
  4. Manually skip Language by cliking on Profiles - not the save button in the language section
  5. Select a profile (for instance desktop.py) and wait for it to be queued.

This leaves Language unresolved forever, until the user goes back to language and presses skip or save. If all steps are in queued and doesn't release for ~5 seconds, the user should be notified of which step is hanging (in this case, Language) to make it more clear that user interaction is needed.

@Torxed Torxed added the feature Feature request / suggestion label Jul 22, 2020
@Torxed Torxed added this to the v1.0 milestone Jul 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Feature request / suggestion
Projects
None yet
Development

No branches or pull requests

1 participant