Describe the bug
While running yarn dlx @yarnpkg/doctor . an assertion failed warning will be printed for git dependencies.
➤ YN0000: │ Resolving jest-date-mock@andreialecu/jest-date-mock#build errored with Assertion failed: This resolver cannot be used unless a fetcher is configured
To Reproduce
```js repro
await packageJsonAndInstall({
devDependencies: {
"jest-date-mock": "https://github.com/andreialecu/jest-date-mock.git#build",
}
});
const output = await yarn(dlx, @yarnpkg/doctor, .);
expect(output).not.toMatch('errored with Assertion failed')
```
The reproduction case in your issue seems broken (ie it neither pass nor fail due to throwing an unmanaged exception):
Error: Command failed: /usr/bin/node /github/workspace/scripts/actions/../run-yarn.js install
/github/workspace/.yarn/cache/yoga-layout-prebuilt-npm-1.9.3-b527507fd5-1.zip/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
throw ex;
^
Error: spawn git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn git',
path: 'git',
spawnargs: [
'ls-remote',
'--refs',
'https://github.com/andreialecu/jest-date-mock.git'
]
}
[94m➤[39m [90mYN0000[39m: ┌ Resolution step
at ChildProcess.exithandler (child_process.js:295:12)
at ChildProcess.emit (events.js:210:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Remember: any non-Jest exceptions will cause the test to be reported as broken. If you expect something to pass without throwing, you must wrap it into something like await expect(...).resolves.toBeTruthy(). If you instead expect something to throw, you need to wrap it into await expect(...).rejects.toThrow().
Looks like there's no git available to sherlock either. Not sure how to add a repro for this.
Interestingly though, I would assume this would work via the github plugin and use http instead of git. Not clear why it's attempting to use the git binary here.
In order to load git dependencies it needs to download them (fetch) and store them into the cache. The doctor is configured to only do the most basic resolutions.
This limitation was set back when we didn't have the cache mirror to speed things up, and when git dependencies were inefficiently packaged. It isn't the case anymore, so we can revisit this 🙂
Great! Any idea why sherlock isn't using github-plugin here though in the repro run?
Edit: I think this is a separate bug: https://github.com/yarnpkg/berry/blob/45c24de98db932cc0bccd82a273107d5799503f8/packages/plugin-github/sources/githubUtils.ts#L8-L18
The github plugin isn't properly detecting dependencies like githubusername/repo as github deps, they need to be https://... based on the regex above. Possible patterns that are also valid are: github:githubusername/repo and git+https://github.com/... and maybe others.
The reproduction case in your issue seems broken (ie it neither pass nor fail due to throwing an unmanaged exception):
Error: Command failed: /usr/bin/node /github/workspace/scripts/actions/../run-yarn.js install
/github/workspace/.yarn/cache/yoga-layout-prebuilt-npm-1.9.3-b527507fd5-1.zip/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
throw ex;
^
Error: spawn git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn git',
path: 'git',
spawnargs: [
'ls-remote',
'--refs',
'https://github.com/andreialecu/jest-date-mock.git'
]
}
[94m➤[39m [90mYN0000[39m: ┌ Resolution step
at ChildProcess.exithandler (child_process.js:295:12)
at ChildProcess.emit (events.js:210:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Remember: any non-Jest exceptions will cause the test to be reported as broken. If you expect something to pass without throwing, you must wrap it into something like await expect(...).resolves.toBeTruthy(). If you instead expect something to throw, you need to wrap it into await expect(...).rejects.toThrow().
@andreialecu I think the problem is that the regex here doesn't match .:
https://github.com/yarnpkg/berry/blob/master/packages/plugin-git/sources/gitUtils.ts#L17
Will fix that!
This issue reproduces on master:
Error: expect(received).toBeFalsy()
Received: true
at module.exports (evalmachine.<anonymous>:9:58)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async /github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:56:13
at async executeInTempDirectory (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:17:16)
at async Object.executeRepro (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:24:12)
at async ExecCommand.execute (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/commands/exec.js:25:38)
at async ExecCommand.validateAndExecute (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Command.js:161:26)
at async Cli.run (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Cli.js:74:24)
at async Cli.runExit (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Cli.js:83:28)
This issue reproduces on master:
Error: expect(received).not.toMatch(expected)
Expected substring: not "errored with Assertion failed"
Received string: "➤ YN0000: ┌ Resolution step
➤ YN0002: │ @yarnpkg/plugin-version@npm:2.0.0-rc.20 [10f20] doesn't provide @types/react@>=16.8.0 requested by ink@npm:2.6.0
➤ YN0000: └ Completed in 6.85s
➤ YN0000: ┌ Fetch step
➤ YN0013: │ @babel/runtime@npm:7.8.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @sindresorhus/is@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @szmarczak/http-timer@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/cacheable-request@npm:6.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/color-name@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/events@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/glob@npm:7.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/http-cache-semantics@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/keyv@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/minimatch@npm:3.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/node@npm:13.5.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/responselike@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/semver@npm:6.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/cli@npm:2.0.0-rc.28 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/core@npm:2.0.0-rc.22 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/doctor@npm:2.0.0-rc.14 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/fslib@npm:2.0.0-rc.15 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/json-proxy@npm:2.0.0-rc.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/libui@npm:2.0.0-rc.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/libzip@npm:2.0.0-rc.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/parsers@npm:2.0.0-rc.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-compat@npm:2.0.0-rc.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-constraints@npm:2.0.0-rc.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-dlx@npm:2.0.0-rc.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-essentials@npm:2.0.0-rc.22 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-file@npm:2.0.0-rc.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-git@npm:2.0.0-rc.16 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-github@npm:2.0.0-rc.13 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-http@npm:2.0.0-rc.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-init@npm:2.0.0-rc.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-link@npm:2.0.0-rc.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-node-modules@npm:2.0.0-rc.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-npm-cli@npm:2.0.0-rc.14 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-npm@npm:2.0.0-rc.15 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-pack@npm:2.0.0-rc.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-patch@npm:2.0.0-rc.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-pnp@npm:2.0.0-rc.16 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-stage@npm:2.0.0-rc.15 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/plugin-version@npm:2.0.0-rc.20 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/pnp@npm:2.0.0-rc.16 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/pnpify@npm:2.0.0-rc.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @yarnpkg/shell@npm:2.0.0-rc.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-escapes@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-escapes@npm:4.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-regex@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-regex@npm:4.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-regex@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-styles@npm:3.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ansi-styles@npm:4.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ any-promise@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ argparse@npm:1.0.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ array-union@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ arrify@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ asap@npm:2.0.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ astral-regex@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ astral-regex@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ auto-bind@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ balanced-match@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ bl@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ brace-expansion@npm:1.1.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ braces@npm:3.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cacheable-lookup@npm:0.2.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cacheable-request@npm:7.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ camelcase@npm:5.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ chalk@npm:2.4.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ chalk@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ chardet@npm:0.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ chownr@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ci-info@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cli-cursor@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cli-cursor@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cli-truncate@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cli-width@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ clipanion@npm:2.1.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ clone-response@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ color-convert@npm:1.9.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ color-convert@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ color-name@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ color-name@npm:1.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ commander@npm:2.12.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ comment-json@npm:2.4.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ concat-map@npm:0.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ core-util-is@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ cross-spawn@npm:6.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ decompress-response@npm:5.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ defer-to-connect@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ define-properties@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ diff@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ dir-glob@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ duplexer3@npm:0.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ emoji-regex@npm:7.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ emoji-regex@npm:8.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ end-of-stream@npm:1.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ end-of-stream@npm:1.4.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ es-abstract@npm:1.17.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ es-to-primitive@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ escape-string-regexp@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ esprima@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ external-editor@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fast-glob@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fastq@npm:1.6.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ figgy-pudding@npm:3.5.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ figures@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fill-range@npm:7.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fn-name@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fs-constants@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fs-minipass@npm:1.2.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ fs.realpath@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ function-bind@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ get-stream@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ git-up@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ git-url-parse@npm:11.1.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ glob-parent@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ glob@npm:7.1.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ globby@npm:10.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ got@npm:10.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ has-flag@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ has-flag@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ has-own-prop@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ has-symbols@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ has@npm:1.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ http-cache-semantics@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ iconv-lite@npm:0.4.24 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ignore@npm:5.1.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ inflight@npm:1.0.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ inherits@npm:2.0.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ink@npm:2.6.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ inquirer@npm:6.5.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-callable@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-ci@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-date-object@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-extglob@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-fullwidth-code-point@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-fullwidth-code-point@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-glob@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-number@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-promise@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-regex@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-ssh@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is-symbol@npm:1.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ is@npm:3.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ isexe@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ js-reporters@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ js-tokens@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ js-yaml@npm:3.13.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ json-buffer@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ json-file-plus@npm:3.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ keyv@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ lodash.throttle@npm:4.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ lodash.toarray@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ lodash@npm:4.17.15 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ log-update@npm:3.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ logic-solver@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ loose-envify@npm:1.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ lowercase-keys@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ merge2@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ micromatch@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mimic-fn@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mimic-fn@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mimic-response@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mimic-response@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ minimatch@npm:3.0.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ minimist@npm:0.0.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ minipass@npm:2.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ minizlib@npm:1.3.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mkdirp@npm:0.5.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ mute-stream@npm:0.0.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ nice-try@npm:1.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ node-emoji@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ node-watch@npm:0.6.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ node.extend@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ normalize-url@npm:3.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ normalize-url@npm:4.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ object-assign@npm:4.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ object-inspect@npm:1.7.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ object-keys@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ object.assign@npm:4.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ once@npm:1.3.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ once@npm:1.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ onetime@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ onetime@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ os-tmpdir@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ p-cancelable@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ p-limit@npm:2.2.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ p-try@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ parse-path@npm:4.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ parse-url@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ path-is-absolute@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ path-key@npm:2.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ path-parse@npm:1.0.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ path-type@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ picomatch@npm:2.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ pluralize@npm:7.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ pretty-bytes@npm:5.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ promise-deferred@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ promise.prototype.finally@npm:3.1.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ promise@npm:7.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ promiseback@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ prop-types@npm:15.7.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ property-expr@npm:1.5.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ protocols@npm:1.4.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ pump@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ qunit@npm:2.9.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ react-is@npm:16.12.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ react-reconciler@npm:0.24.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ react@npm:16.12.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ readable-stream@npm:3.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ readline-sync@npm:1.4.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ redux@npm:4.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ regenerator-runtime@npm:0.13.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ repeat-string@npm:1.6.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ resolve@npm:1.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ resolve@patch:resolve@npm%3A1.9.0#builtin<compat/resolve>::version=1.9.0&hash=8fccd0 can't be found in the cache and will be fetched from the disk
➤ YN0013: │ responselike@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ restore-cursor@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ restore-cursor@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ reusify@npm:1.0.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ rimraf@npm:2.7.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ run-async@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ run-parallel@npm:1.1.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ rxjs@npm:6.5.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ safe-buffer@npm:5.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ safer-buffer@npm:2.1.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ scheduler@npm:0.18.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ semver@npm:5.7.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ shebang-command@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ shebang-regex@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ signal-exit@npm:3.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ slash@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ slice-ansi@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ sprintf-js@npm:1.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ssri@npm:6.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ stream-buffers@npm:3.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ stream-to-array@npm:2.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ stream-to-promise@npm:2.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string-length@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string-width@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string-width@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string-width@npm:4.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string.prototype.trimleft@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string.prototype.trimright@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ string_decoder@npm:1.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ strip-ansi@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ strip-ansi@npm:5.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ strip-ansi@npm:6.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ supports-color@npm:5.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ supports-color@npm:7.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ symbol-observable@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ synchronous-promise@npm:2.0.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tar-stream@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tar@npm:4.4.13 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tau-prolog@npm:0.2.80 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ through@npm:2.3.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tmp@npm:0.0.33 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tmp@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ to-readable-stream@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ to-regex-range@npm:5.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ toposort@npm:2.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ treeify@npm:1.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tslib@npm:1.10.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ tunnel@npm:0.0.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ type-fest@npm:0.8.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ type-fest@npm:0.9.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ typescript@npm:3.7.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ typescript@patch:typescript@npm%3A3.7.5#builtin<compat/typescript>::version=3.7.5&hash=226bd1 can't be found in the cache and will be fetched from the disk
➤ YN0013: │ underscore@npm:1.9.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ util-deprecate@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ which@npm:1.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ widest-line@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrap-ansi@npm:6.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yoga-layout-prebuilt@npm:1.9.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yup@npm:0.27.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 46.65s
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0.74s
➤ YN0000: Done with warnings in 54.27s
➤ YN0000: Found 1 package(s) to process
➤ YN0000: For a grand total of 1 file(s) to validate
➤ YN0000: ┌ /tmp/tmp-27zCAUqMV44K0i/package.json
➤ YN0000: │ Resolving jest-date-mock@https://github.com/andreialecu/jest-date-mock.git#build errored with Assertion failed: This resolver cannot be used unless a fetcher is configured
➤ YN0000: └ Completed in 0.13s
➤ YN0000: Done with warnings in 0.13s
"
at module.exports (evalmachine.<anonymous>:9:20)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async /github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:56:13
at async executeInTempDirectory (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:17:16)
at async Object.executeRepro (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/executeRepro.js:24:12)
at async ExecCommand.execute (/github/workspace/.yarn/cache/@arcanis-sherlock-npm-1.0.38-d4f5e2dbf3-1.zip/node_modules/@arcanis/sherlock/lib/commands/exec.js:25:38)
at async ExecCommand.validateAndExecute (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Command.js:161:26)
at async Cli.run (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Cli.js:74:24)
at async Cli.runExit (/github/workspace/.yarn/cache/clipanion-npm-2.0.0-rc.16-b9444aaf89-1.zip/node_modules/clipanion/lib/advanced/Cli.js:83:28)