You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to download ARM binary when running tests using the package
Output
Starting the instance failed, please enable debug for more infomation
1) "before all" hook in "{root}"
0 passing (425ms)
1 failing
1) "before all" hook in "{root}":
Error: Status Code is 403 (MongoDB's 404)
This means that the requested version-platform combination doesn't exist
Used Url: "https://fastdl.mongodb.org/osx/mongodb-osx-ssl-arm64-4.0.14.tgz"
Try to use different version 'new MongoMemoryServer({ binary: { version: 'X.Y.Z' } })'
List of available versions can be found here:
https://www.mongodb.org/dl/linux for Linux
https://www.mongodb.org/dl/osx for OSX
https://www.mongodb.org/dl/win32 for Windows
at ClientRequest.<anonymous> (node_modules/mongodb-memory-server-core/src/util/MongoBinaryDownload.ts:341:17)
at ClientRequest.EventEmitter.emit (domain.js:483:12)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:601:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:122:17)
at TLSSocket.socketOnData (_http_client.js:474:22)
at TLSSocket.EventEmitter.emit (domain.js:483:12)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (_stream_readable.js:272:9)
at TLSSocket.Readable.push (_stream_readable.js:213:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
Do you know why it happenes?
There is a 403 from the mirror, not sure if this is the cause or not.
The text was updated successfully, but these errors were encountered:
OSX ARM is not supported by default in 6.x, but since 7.x it is automatically translated to use what @jeffrey-dugas-neo said (to use x64, because mongodb does not provide any native builds yet)
Versions
package: mongo-memory-server
What is the Problem?
Unable to download ARM binary when running tests using the package
Output
Do you know why it happenes?
There is a 403 from the mirror, not sure if this is the cause or not.
The text was updated successfully, but these errors were encountered: