Instead it was being thrown in a Future that the master did not wait for:
the writing side failed with a closed pipe exception, and this meaningless error was thrown up.
Fixing by waiting for the reading side first, so any error there will be thrown up.
(If there was _also_ an error on the writing side, we would miss it, but typically this will just be the closed stream.)

[FIXED JENKINS-19332]

[FIXED JENKINS-19391] Trying to show the annotation on an Advanced block in newly inserted dynamic section failed since the span is not yet registered.
More generally, suppressing customizedField detection when attrs.field is null;
this prevents us from giving false positives for complex forms with Java-based defaults like CoberturaPublisher.

Fix for underlined trailing spaces on project links. Tried various solutions including the Jelly trim attribute, but in the end the only thing that would work was to remove the line break prior to the closing tag.

Optimize String appends in hudson.Functions

(Stapler 1.218 rejects it, I think correctly.)

Close JarFile resources in PluginWrapper and UpdateCenter

debian: Fill in gecos field for jenkins user

[JENKINS-17248] Be robust against exceptions in ItemListener.onLoaded, since this could interrupt Jenkins startup.

Thanks

The translation was too literal: the log is not full as in a cup of water (this is what "cheio" means), it is full because it is not a partial object.