Yarn tasks fails due to DNS issue? getaddrinfo ENOTFOUND publicblobs.geeklearning.io publicblobs.geeklearning.io:443

[dotansimha]

Since a few hours ago, it seems like publicblobs.geeklearning.io is down, leading to a failure when using the VSTS task:

Starting: Use Yarn (1.x)
==============================================================================
Task         : Yarn Tool Installer
Description  : Installs a version of Yarn
Version      : 3.0.1999
Author       : Geek Learning
Help         : [More Information](https://github.com/geeklearningio/gl-vsts-tasks-yarn/wiki/Yarn) (Version 3.0.1999)
==============================================================================
##[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.
##[error]getaddrinfo ENOTFOUND publicblobs.geeklearning.io publicblobs.geeklearning.io:443
Finishing: Use Yarn (1.x)

[dotansimha]

@sandorfr any idea how this can be resolved?

[shayb-datumate]

Having the same issue as well

[mike-eo]

From a WHOIS search, it looks like the domain name has expired today (November 23, 2021). That's why the fetch is failing...

[dotansimha]

Seems like latest ubuntu image of Azure DevOps supports Yarn as built-in so I'm not sure if this task is needed...

[tx-tim]

Confirmed comment by @dotansimha - Just ran my build task without the installer and subsequent tasks using yarn were able to execute

[sgaloux]

Having exactly the same issue, my devops task fails :

[norlandoPDDS]

Seems like latest ubuntu image of Azure DevOps supports Yarn as built-in so I'm not sure if this task is needed...

Yarn 1.22.17 is also built-in on windows-2016, windows-2019 and windows-2022 build agents as well.

[RPbarfield]

I unchecked the "Always download the latest matching version" in my Use Yarn task and the builds are working again. Once this is fixed, I'll go back to downloading Yarn.

[dthomason]

confirmed @norlandoPDDS was correct. Just pulled out task: YarnInstaller@3 and everything built fine.

[alangdcdevop]

Confirmed, just uncheck "Always download the lastest matchig version" and its works like charm.
Thanks @RPbarfield

[sandorfr]

Hello, Just fixed the dns problem, sorry about that.

…

On Wed, 24 Nov 2021 at 6:24 am, aduartebdsol ***@***.***> wrote: Confirmed, just uncheck "Always download the lastest matchig version" and its works like charm. Thanks @RPbarfield <https://github.com/RPbarfield> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUJPJRECQWUYMBXSA7XG2LUNPS6VANCNFSM5ITZENAA> .

[kenlyon]

The value of this tasks was in being able to stay up to date with the latest version, though. Seems a more robust way would be for it to check https://registry.npmjs.org/yarn.

[sandorfr]

Yes I agree, especially considering the agents have a version of yarn by default these days. The npm registry manifest is a great idea, I’ll investigate that.

…

On Wed, 24 Nov 2021 at 6:49 am, Ken Lyon ***@***.***> wrote: The value of this tasks was in being able to stay up to date with the latest version, though. Seems a more robust way would be for it to check https://registry.npmjs.org/yarn. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUJPJXXAKDTPV5VWEJIWDLUNPV6JANCNFSM5ITZENAA> .

[jlopez-technisys]

The error has already been solved?

[sandorfr]

I'm actually wondering if there is any value to this tool installer task anymore since yarn no supports installs via npm, and azure pipelines now supports chocolatey. This give two builtin way to install yarn without relying on this 3rd party (as neither official yarn or azur pipelines).

Since I have the attention of some fellow users of this, what are your thoughts?

[sandorfr]

To clarify my thoughts, yarn 1.x is available in the standard agent image. When it comes to yarn 2.x and ulterior, they can be enabled directly via corepack.

The following would be a an example that does everything without this extension.

  - task: NodeTool@0
    inputs:
      versionSpec: '16.13.x'
  - task: Bash@3
    displayName: Yarn enable
    inputs:
      targetType: 'inline'
      script: |
        corepack enable
        corepack prepare yarn@3.1.1 --activate
  - task: Cache@2
    inputs:
      key: '"yarn" | "$(Agent.OS)" | yarn.lock'
      restoreKeys: |
        yarn | "$(Agent.OS)"
        yarn
      path: $(YARN_CACHE_FOLDER)
    displayName: Cache Yarn packages
  - task: Bash@3
    displayName: Yarn
    inputs:
      targetType: 'inline'
      script: |
        yarn --frozen-lockfile
  - task: Bash@3
    displayName: Yarn build
    inputs:
      targetType: 'inline'
      script: |
        yarn build

If package feed authentication is needed, npm authenticate should do the job.