Module stalling 

What a screen says when a profile’s image build has said nothing for long enough to look hung.

A build has no time limit of its own: a big image takes twenty minutes, and that is normal. What the person cannot read off a log that has stopped moving is whether to keep waiting, so both screens that show a build — the workspace tab that is building a missing image and the wizard’s image page — judge the same silence the same way and say the same one line beside it.

Nothing here stops a build, and nothing asks the engine whether it is stuck: the engine does not say, and a build QCode gave up on is a half-made image and a person who wanted their profile. The person’s own Stop is the only way a build ends, and this rule only tells them it is time to consider it.

The silence is judged by Lengths, which a screen holds and a test shortens: the product uses the measured QUIET and LOOK, and the number in the sentence is the first of them in whole minutes rather than a measured silence, which a person cannot be shown.

Structs

Lengths

The two lengths a build’s silence is judged by. The product’s are QUIET and LOOK; a test shortens both, since a test cannot wait five minutes for a warning and cannot ask the engine for a build that really takes that long.

Constants

LOOK

How often a build that is running is looked at.

QUIET

How long a build may say nothing before it is said to be quiet.

Functions

follow

The next look at the builds running on a screen, timed once: a task that sleeps Lengths::look and hands woke the moment it woke at, so what is judged is the screen as it is then and not as it was when the look was asked for.

quiet_for

Whether a build that last said something at said has been quiet for longer than quiet as of now, which is what the warning beside it is raised and taken down by.