Skip to content

builder-next: call stopprogress on download error#39211

Merged
1 commit merged intomoby:masterfrom
tonistiigi:pull-progress-fix
May 20, 2019
Merged

builder-next: call stopprogress on download error#39211
1 commit merged intomoby:masterfrom
tonistiigi:pull-progress-fix

Conversation

@tonistiigi
Copy link
Copy Markdown
Member

Progress needs to be stopped on download error as well to avoid defer from hanging.

@tiborvass @AkihiroSuda

Signed-off-by: Tonis Tiigi tonistiigi@gmail.com

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
Copy link
Copy Markdown
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codecov
Copy link
Copy Markdown

codecov bot commented May 19, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@3042254). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #39211   +/-   ##
=========================================
  Coverage          ?   37.02%           
=========================================
  Files             ?      612           
  Lines             ?    45488           
  Branches          ?        0           
=========================================
  Hits              ?    16843           
  Misses            ?    26351           
  Partials          ?     2294

@olljanat
Copy link
Copy Markdown
Contributor

CI green. Ready for merge 👍

@thaJeztah thaJeztah closed this May 20, 2019
@thaJeztah
Copy link
Copy Markdown
Member

Thx @olljanat

@thaJeztah
Copy link
Copy Markdown
Member

thaJeztah commented May 20, 2019

Wait; this is odd; I clicked the merge button, but GitHub shows the PR as still being open, and as if I closed the PR?

Screenshot 2019-05-20 at 15 03 08

Screenshot 2019-05-20 at 15 03 13

Screenshot 2019-05-20 at 15 03 22

Looks like it's really merged into master though

Screenshot 2019-05-20 at 15 05 46

@thaJeztah
Copy link
Copy Markdown
Member

I contacted GitHub support, just in case 👍

@tiborvass
Copy link
Copy Markdown
Contributor

@thaJeztah no response?

@thaJeztah
Copy link
Copy Markdown
Member

Nope, don't think so 😔

@AkihiroSuda
Copy link
Copy Markdown
Member

can we retry to close this?

@thaJeztah thaJeztah closed this Jun 7, 2019
@thaJeztah
Copy link
Copy Markdown
Member

interesting; tried that earlier and didn't work; now looks like it did

(I did reach out to hem again today, perhaps they fixed something?)

@thaJeztah thaJeztah added this to the 20.03.0 milestone Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants