Skip to content
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

Yarn package layout unexpected while github is down #69

Open
4 of 9 tasks
kachkaev opened this issue Jul 22, 2019 · 1 comment
Open
4 of 9 tasks

Yarn package layout unexpected while github is down #69

kachkaev opened this issue Jul 22, 2019 · 1 comment

Comments

@kachkaev
Copy link

kachkaev commented Jul 22, 2019

Before opening an issue please read this.

Are you reporting a bug or a feature request ?

  • Bug
  • Feature request

Description

During a recent GitHub incident our Azure Devops Pipelines were failing with the following message: Yarn package layout unexpected.

Screenshot 2019-07-22 at 17 32 25

Screenshot 2019-07-22 at 17 31 40

This was confusing given that it was not clear that Yarn was fetched from GitHub releases. Ironically, when I googled for "yarn package layout unexpected", the only result was the source of this repo, which was.... returning 500 😁

Expected behavior

I would expect a different error message, which would make it clear that a specified Yarn release failed to download because of a remote server error. Perhaps, it could even include links to https://www.githubstatus.com and https://twitter.com/githubstatus?

Reproduction

It's hard to break GitHub on demand, but it may be possible to reproduce the error in tests by replacing a real GitHub releases URL with https://httpstat.us/500.

System information

VSTS or TFS:

  • VSTS (azure devops)
  • TFS

Agent:

  • Hosted
  • Custom

OS:

  • Windows
  • Mac
  • Linux

Yarn version:
1.17.3 (desired), 1.16.0 (already existing on the machine)

Node version:
12

@SlashmanX
Copy link

Just a note that this error message is still occurring when Github has operational issues as has been the case the past few days. This issue was the only way I was able to track down the source of the problem in my build step so thanks @kachkaev !

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

No branches or pull requests

3 participants