Skip to content

Add comment about feed instability due to deb/rpm package publish in "Troubleshoot the package manager" #16670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dagood opened this issue Jan 14, 2020 · 3 comments · Fixed by #16857
Assignees

Comments

@dagood
Copy link
Member

dagood commented Jan 14, 2020

We should mention that the feed becomes unstable when packages get published: what are the symptoms and how long are you expected to have to wait for it to resolve itself? (At which point you should file an issue on dotnet/core.)

Example on Ubuntu:

  File has unexpected size (72463 != 72485). Mirror sync in progress? [IP: 13.91.48.226 443]

I think this notice should be added to all Deb and RPM pages. I believe the delay is different between Deb and RPM.

Idea from @drk-mtr over at dotnet/core#4116 (comment).

@leecow @vivmishra @dleeapho


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@Thraka
Copy link
Contributor

Thraka commented Jan 16, 2020

@dagood Are they fixing the issue behind the scenes? Is this going to keep happening? As someone pointed out in those threads, it really should just work, the repos shouldn't be suddenly crippled for days when a new release comes up. It completely breaks CI and automation.

cc @rbhanda

@dagood
Copy link
Member Author

dagood commented Jan 16, 2020

Are they fixing the issue behind the scenes?

No, it's considered a normal aspect of the service. Yes, it seems pretty absurd.

@dagood
Copy link
Member Author

dagood commented Jan 16, 2020

@dleeapho has been trying to work with the team, especially regarding the aftermath of the way more impactful 2019 Dec issues. dotnet/core#3995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants