nodkz / mongodb-memory-server Goto Github PK

NPM install is crashing due to incorrect MD5.

mongodb-memory-server: checking MongoDB binaries cache...
Downloading: https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-debian-latest.tgz
Downloading: https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-debian-latest.tgz.md5
(node:2047) UnhandledPromiseRejectionWarning: Error: MongoBinaryDownload: md5 check is failed
    at MongoBinaryDownload._callee3$ (/home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:217:23)
    at tryCatch (/home/circleci/app/node_modules/regenerator-runtime/runtime.js:62:40)
    at Generator.invoke [as _invoke] (/home/circleci/app/node_modules/regenerator-runtime/runtime.js:296:22)
    at Generator.prototype.(anonymous function) [as next] (/home/circleci/app/node_modules/regenerator-runtime/runtime.js:114:21)
    at step (/home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:52:191)
    at /home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:52:437
    at new Promise (<anonymous>)
    at MongoBinaryDownload.<anonymous> (/home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:52:99)
    at MongoBinaryDownload.checkMd5 (/home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:228:22)
    at MongoBinaryDownload._callee2$ (/home/circleci/app/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:179:29)
(node:2047) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

This causes

Error: EBUSY: resource busy or locked, unlink 'C:\Users\Gerard\AppData\Local\Temp\mongo-mem-13616GqtHuLWrpEBT\mongod.lock'

Solution would be to wait for the childProcess exit event before calling tmpDir.removeCallback()

Happy to provide a PR

I see that you've installed request-promise as dependency without its peer request. Now when you install the package, you'll run in the following warnings;

warning "mongodb-memory-server > [email protected]" has unmet peer dependency "request@^2.34".
warning "mongodb-memory-server > request-promise > [email protected]" has unmet peer dependency "request@^2.34".

As Yarn does not install peer dependencies automatically.

storageEngine option on replSet seems to be ignored:

new MongoMemoryReplSet({
  replSet: {
    storageEngine: 'wiredTiger'
  }
})

It falls back to the default memory storage.

Things work great when I'm running on my local machine, but I'm seeing problems getting things to run in my CI pipeline, which is running tests in a Docker containers.

The symptom is that my global.__MONGOD__ appears to be undefined by the time my mongo-environment.js is loaded by the test.

TypeError: Cannot read property 'getConnectionString' of undefined

Here's what my setup.js and my mongo-environment.js files look like:

// setup.js
const MongodbMemoryServer = require('mongodb-memory-server');

const MONGO_DB_NAME = 'jest';

const mongod = new MongodbMemoryServer.default({
  instance: {
    dbName: MONGO_DB_NAME,
  },
  binary: {
    version: '3.4.6',
  },
});

module.exports = () => {
  global.__MONGOD__ = mongod;
  global.__MONGO_DB_NAME__ = MONGO_DB_NAME;
};

// mongo-environment.js
const NodeEnvironment = require('jest-environment-node');

class MongoEnvironment extends NodeEnvironment {
  async setup() {
    // 👇 This line is throwing the error I mentioned above
    this.global.__MONGO_URI__ = await global.__MONGOD__.getConnectionString();
    this.global.__MONGO_DB_NAME__ = global.__MONGO_DB_NAME__;

    await super.setup();
  }

  async teardown() {
    await super.teardown();
  }

  runScript(script) {
    return super.runScript(script);
  }
}

module.exports = MongoEnvironment;

It looks like mongo doesn't get downloaded all the way before the code tries to run and reference the connection string? As I'm watching it run, I see this line about downloading Mongo and it starts showing percentages, but then tests start running and failing. (Note, the percent is gone in the screen grab).

it looks like fs-extra depends on graceful-fs that is causing jest to leak

check this jestjs/jest#6738
and isaacs/node-graceful-fs#102

can we avoid using fs-extra in this module?

I tried out the Jest example in the README and it does not work. When I ran some test, there are some error message saying "failed to connect on first connect".

The problem is at this line

mongoose.connect(mongoUri, opts, (err) => {
    if (err) console.error(err);
  });

Since mongoose.connect() returns a promise, we need to call it with await such that the call only returns when the connection is done.

So it should be something like

await mongoose.connect(mongoUri, opts, (err) => {
    if (err) console.error(err);
  });

Download of MongoDB version 3.6.2 does not work.
Here is the generated link from the package: https://downloads.mongodb.org/osx/mongodb-osx-x86_64-3.6.2.tgz
There is only a ssl version on downloads.mongodb.org, so the link is https://downloads.mongodb.org/osx/mongodb-osx-ssl-x86_64-3.6.2.tgz.

Should I make a PR which tests if the wanted version is > 3.6 and add -ssl- in name (https://github.com/nodkz/mongodb-memory-server/blob/master/src/util/MongoBinaryDownloadUrl.js#L39) ?

Our company's build servers do not have direct access to the internet. Instead, they request packages from an internal Artifactory that we host. Currently, MongoBinaryDownloadUrl hardcodes the download for mongodb binaries to fastdl.mongodb.org.

It would be very nice if we could override that with an environment variable to allow us to point this package at a mirror of the mongodb binaries that we could host. Other packages have a mechanism to do this (e.g. sass_binary_site, chromedriver_cdnurl).

https://github.com/nodkz/mongodb-memory-server/blob/3fb53263d50d64bb61f621075d9b9420843fe412/src/util/MongoBinaryDownloadUrl.js#L85

it worth to simply return empty string to fall back to 'legacy' distribution instead of throwing an error.

I can't get the connection string on Windows 10 use this function getConnectionString(). Everything work fine on Mac

Hi,

I have tried to run mongodb-memory-server ([email protected]) as a fresh npm install on Ubuntu 1804.

It is failing with an incorrect download location. Please see the following stack trace: -

Determining test suites to run... Mongo[40427] Starting MongoDB instance with following options: {"port":40427,"dbName":"jest","uri":"mongodb://127.0.0.1:40427/jest","storageEngine"
:"ephemeralForTest","dbPath":"/tmp/mongo-mem-15254m9v8farYN312"} +0ms
Mongo[40427] MongoBinary options: {"downloadDir":"/home/jenkins/.mongodb-binaries","platform":"linux","arch":"x64","version":"3.2.18"} +2ms
Mongo[40427] Downloading: https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz +27ms
Mongo[40427] renamed /home/jenkins/.mongodb-binaries/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz.downloading to /home/jenkins/.mongodb-binaries/mongodb-linux-x86_64-ubuntu1804-3.2.1
8.tgz +97ms
Mongo[40427] Downloading: https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz.md5 +1ms
Mongo[40427] renamed /home/jenkins/.mongodb-binaries/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz.md5.downloading to /home/jenkins/.mongodb-binaries/mongodb-linux-x86_64-ubuntu1804-3
.2.18.tgz.md5 +10ms
Mongo[40427] extract(): /home/jenkins/.mongodb-binaries/3.2.18 +1ms
Error: MongoBinaryDownload: missing mongod binary in /home/jenkins/.mongodb-binaries/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz
at /var/lib/jenkins/workspace/PrismIS/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:207:15
at Generator.next ()
at asyncGeneratorStep (/var/lib/jenkins/workspace/PrismIS/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:28:103)
at _next (/var/lib/jenkins/workspace/PrismIS/node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:30:194)
at

Trying this URL: https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1804-3.2.18.tgz gives a 'permission denied'.

Kind regards.

Peter

Hello,

Is it possible to run mongodb-memory-server as a standalone replica set, so that it could be used to test transactions?

I think it should be easy to add: https://docs.mongodb.com/manual/tutorial/convert-standalone-to-replica-set/

Regards,
Sebastian

There is interesting package: mongodb-download
What do you think about it?
It looks bit unattended, but may be it's still better to use it for mongo downloading?
Or reuse some code from it?

Hello, when we are executing our test with the real mongodb engine we use migrate-mongo to execute script to prepare tests database filling required data. Since It seems we are having issue with Jest and MongoDb related ton an openHandle, how could we run our migration on your in memory database?

Thanks

Won't download mongodb if started behind a proxy server even with env vars set.

I'm trying to use the module as described in docs.

const MongodbMemoryServer = require('mongodb-memory-server');
const mongoServer = new MongodbMemoryServer();

But I got the error TypeError: MongodbMemoryServer is not a constructor.

At this page I've found another piece of code

const mongoServer = new MongodbMemoryServer.MongoMemoryServer();

and that works. Is that an error in the documentation or in the code?

When I start my tests I see this:

DeprecationWarning: open() is deprecated in mongoose >= 4.11.0, use openUri() instead, or set the useMongoClient option if using connect() or createConnection(). See http://mongoosejs.com/docs/connections.html#use-mongo-client

Without this if the binary is corrupted there's never an error shown to the user.

I unfortunately found this out after using ctrl+c at the start of my tests 4 hours ago while it was still downloading.

PR 79 doesn't add auth to the command line arguments (prepareCommandArgs()) even when instance.auth is set to true.

This appears to be unused or never set, runningInstance must be checked instead

Freshly installed on a new machine
Windows10 x64

Autostarting MongoDB instance...
  Mongo[50146] Starting MongoDB instance with following options: {"port":50146,"dbName":"f63e96d0-2244-497d-a043-f608688a503d","uri":"mongodb://localhost:50146/f63e96d0-2244-497d-a043-f608688a503d","storageEngine":"ephemeralForTest","dbPath":"C:\\Users\\Username\\AppData\\Local\\Temp\\mongo-mem-6080BA3QCuF1h8UT"} +0ms
Downloading MongoDB: https://downloads.mongodb.org/win32/mongodb-win32-x86_64-3.4.4.zip
  Mongo[50146] renamed C:\Users\Username\.mongodb-binaries\mongodb-win32-x86_64-3.4.4.zip.downloading to C:\Users\Username\.mongodb-binaries\mongodb-win32-x86_64-3.4.4.zip +10s
  Mongo[50146] getDownloadMD5Hash content: 024a46524c856429d0fd9de0c7d04c5f  mongodb-win32-x86_64-3.4.4.zip
  Mongo[50146]  +557ms
  Mongo[50146] getDownloadMD5Hash extracted signature: 024a46524c856429d0fd9de0c7d04c5f +1ms
  Mongo[50146] extract(): C:\Users\Username\.mongodb-binaries\3.4.4 +581ms
(node:6080) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: MongoBinaryDownload: missing mongod binary in C:\Users\Username\.mongodb-binaries\mongodb-win32-x86_64-3.4.4.zip
(node:6080) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: MongoBinaryDownload: missing mongod binary in C:\Users\Username\.mongodb-binaries\mongodb-win32-x86_64-3.4.4.zip

Hi,

I got an issue that it is downloading binaries twice: after npm install and when instance is going to run.

I have a problem in this case:
In my CI/CD job I run inside docker container npm i and npm test commands and it always download binaries at least 1 time.
Please add checking that binaries have been already downloaded.

Hi,

I'm trying to configure jest to use this package but I've found that doesn't work with manjaro. This is the error I get when I activate the debugging:

Determining test suites to run...  Mongo[45603] Starting MongoDB instance with following options: {"port":45603,"dbName":"jest","uri":"mongodb://127.0.0.1:45603/jest","storageEngine":"ephemeralForTest","dbPath":"/tmp/mongo-mem-16705EyirF2mqsJ7s"} +0ms
  Mongo[45603] MongoBinary options: {"downloadDir":"/home/german/Proyectos/dyd/dyd-plus/node_modules/.cache/mongodb-memory-server/mongodb-binaries","platform":"linux","arch":"x64","version":"latest"} +1ms
  Mongo[45603] MongoBinary: Mongod binary path: /home/german/Proyectos/dyd/dyd-plus/node_modules/.cache/mongodb-memory-server/mongodb-binaries/latest/mongod +6ms
  Mongo[45603] MongoBinary: Download lock removed +6ms
  Mongo[45603] STDERR: /home/german/Proyectos/dyd/dyd-plus/node_modules/.cache/mongodb-memory-server/mongodb-binaries/latest/mongod: /usr/lib/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /home/german/Proyectos/dyd/dyd-plus/node_modules/.cache/mongodb-memory-server/mongodb-binaries/latest/mongod)
  Mongo[45603]  +1ms
  Mongo[45603] CLOSE: 1 +0ms
Done in 2.70s.

Seems like it is downloading the ubuntu's version which does not work with manjaro, I've tried manually downloading the generic one and it works well. Besides that I think whould be very useful to throw some exception in this case. I checked the code and maybe it can be changed around there https://github.com/nodkz/mongodb-memory-server/blob/master/src/util/MongoInstance.js#L148 to handle an exit codes different than 0, but I'm not realy sure.

Greetings.

First off, I totally love mongodb-memory-server - it makes testing models and GraphQL APIs a breeze!

If I log the errmsg prop of a MongoError like this:

try {
  await col.insertOne(doc);
} catch (error) {
  if (error typeof MongoError && error.code === 11000) {
    console.log(error.errmsg);
  }
}

I get this with mongodb-memory-server (Jest):

E11000 duplicate key error dup key: { : "YF2dqu11Z9mj", : "test" }

And this with a vanilla mongod process (Node):

E11000 duplicate key error collection: myDatabase.myCollection index: organizationId_1_name_1 dup key: { : "YF2dqu11Z9mj", : "test" }

I parse errmsg to figure out which index clashed so I can provide a more detailed error message to the client. But since the index part of errmsg is not available in the MongoError from mongodb-memory-server I can't write any tests for it.

Is there any way around this? Could it be that Jest is the reason for this?

So, I have the following code:

const mongoose = require('mongoose');
const { MongoMemoryServer } = require('mongodb-memory-server');
const mongoServer = new MongoMemoryServer();
mongoServer.getConnectionString().then((mongoUri) => {
  mongoose.connect(mongoUri);
});

const { Schema } = mongoose;
const userSchema = new Schema({ name: String });

const User = mongoose.model('User', userSchema);

and then I export the User model, and run my tests.

The surprising thing is that the tests run in 11 seconds or so when I run them on MongoDB normally. (5 seconds waiting on connection + 6 actually running).

While this takes 15 seconds (9 seconds to establish a connection + 6 actually running).

Am I doing something wrong?

I even tried with a more intensive test that queries a database collection a 1000 times, it takes 31 seconds to run on memory, and 28 seconds to run from disk. Is it possible that having the database hosted on an SSD make the difference negligible? AFAIK RAM should be at least 10 times faster than SSD.

@nodkz I was tryign to use your memory-server in my own project. Awesome idea. But I am running into a problem that may have something to do with your project tests you have set up. I attaching npm's log plus a copy of my own run log. Looks like maybe something needs an update. It is failing for a .toMatch method.
2018-06-24T20_08_22_039Z-debug.log
npmRunTest_consoleSnapshot.txt

I my own project, I chose to not use the es6 'import' and just stick with the older 'require' in my conn.js file within test folder. But that should not be causing any problems, should it? node is complaining of my constructor MongodbMemoryServer statement is not a constructor.
conn.txt

Hi and thanks for this module,

I use the downloadDir options in my code, so my home folder stays clean of .mongodb-binaries. However the postinstall script is not aware of that and downloads in my home folder. Shouldn't the downloading of binaries after npm install be optional ? (I mean opt-in instead of opt-out)

Am I missing something ?

Cheers

I'm getting the following error when trying to use this package on node 4.4.7.
From what I can see after googling around a bit, this may require babel-polyfill or similar. I'm not familiar with babel otherwise I'd attempt to put up a pull request.

  ● Test suite failed to run

    ReferenceError: regeneratorRuntime is not defined

      at node_modules/mongodb-memory-server/lib/MongoMemoryServer.js:10:32
      at Object.<anonymous> (node_modules/mongodb-memory-server/lib/MongoMemoryServer.js:44:2)
      at Object.<anonymous> (node_modules/mongodb-memory-server/lib/index.js:8:26)

in postInstall.js

if (isModuleExists('./lib/util/MongoBinary')) {
  const MongoBinary = require('./lib/util/MongoBinary').default;

  console.log('mongodb-memory-server: checking MongoDB binaries cache...');
  MongoBinary.getPath({
    version: 'latest',
  }).then(binPath => {
    console.log(`mongodb-memory-server: binary path is ${binPath}`);
  });
}

this will be download mongodb latest version to skip timeout setup jasmine.DEFAULT_TIMEOUT_INTERVAL = 60000;

but in /util/MongoBinary.js

export default class MongoBinary {
  static cache: MongoBinaryCache = {};

  static async getPath(opts?: MongoBinaryOpts = {}): Promise<string> {
    const {
      downloadDir = path.resolve(os.homedir(), '.mongodb-binaries'),
      platform = os.platform(),
      arch = os.arch(),
      version = '3.4.4',
} = opts;

the mongodb default version is 3.4.4

Therefore, it will always download mongodb-binaries version 3.4.4 if not define a version on the first run

If we make this 2 points (mongodb version) to the same version then this problem will solved?

Hi,

On Win10 x64, it's only extracting mongod.exe and throwing various dll errors related to open ssl.
If I manually download and extract all files from the archive link given in the console, it works fine.

I got the error:

Cannot determine version string for {"os":"linux","dist":"Alpine Linux","release":"3.4.6"}

That's what I get when running flow against my project:

yarn flow       
yarn run v1.10.1
$ flow
Error: node_modules/mongodb-memory-server/lib/util/MongoBinary.js.flow:27
 27:         process.env?.MONGOMS_DOWNLOAD_DIR || path.resolve(os.homedir(), '.mongodb-binaries'),
                         ^ Unexpected token .

Perhaps I can add node_modules/mongodb-memory-server to flow's ignore file but still.

Got a warning when using with Mongoose 4.11.0 and above:

(node:9265) DeprecationWarning: open() is deprecated in mongoose >= 4.11.0, use openUri() instead, or set the useMongoClient option if using connect() or createConnection(). See http://mongoosejs.com/docs/connections.html#use-mongo-client

https://github.com/nodkz/mongodb-memory-server/blob/bbf75b838f2e3a92a9f4c5e11d805e1c3c2d9c80/src/util/MongoBinary.js#L25-L30

Please define this options as follow

const {
  downloadDir = process.env.MONGOMS_DOWNLOAD || path.resolve(os.homedir(), '.mongodb-binaries'),
  platform = process.env.MONGOMS_PLATFORM || os.platform(),
  arch = process.env.MONGOMS_ARCH || os.arch(),
  version = process.env.MONGOMS_VERSION || 'latest',
} = opts;

otherwise how I can change it options on npm install from CI configurations for Gitlab? It can't cache files from project outside, for caching /root/.mongodb-binaries folder. Now I can only change my test files as

before(async () => {
  server = new MongoMemoryServer({ binary: { downloadDir: './.mongodb-binaries' } });
});

But this test will fail by timeout cause start download binaries. And this does not working because on postinstall script binaries anyway will downloads to os.homedir() + '/.monodb-binaries', than on test start binaries will downloads again to /path/to/project/.mongodb-binaries. Than Gitlab does not cache this binaries because job is fail.

In memory Mongo is instantiated like this:
const mongod = new MongodbMemoryServer.default({ instance: { dbName: 'my-test-db', port: 12345 } })

It's expected to have MongoDB running on port 12345, but that's not the case. Calling getConnectionString and getPort show that MongoDB is actually running on some default random port (e.g. mongodb://localhost:54271/my-test-db).

This started happening on version 1.9.3 and also happens on 2.0.0.

Thanks for the good work guys.

Asking for learning purposes -what is the added-value of this lib over Mongo built-in memory server?

Currently, the post-install script downloads the binaries to /node_modules/mongodb-memory-server/node_modules/.cache/mongodb-memory-server/mongodb-binaries/latest/mongod, which I believe is due to the cwd being set to /node_modules/mongodb-memory-server when post-install is run. At runtime, the binaries are downloaded anew to /node_modules/.cache/mongodb-memory-server/mongodb-binaries. Perhaps the easiest fix for this would be checking both directories in MongoBinary.js ?

To reproduce:

docker run -it --rm node:11 /bin/bash
root@444a1d59d65f:/# npm init --yes
Wrote to /package.json:

{
  "name": "",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "directories": {
    "lib": "lib"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}


root@444a1d59d65f:/# npm install --save-dev mongodb-memory-server

> [email protected] postinstall /node_modules/mongodb-memory-server
> node ./postinstall.js

mongodb-memory-server: checking MongoDB binaries cache...
mongodb-memory-server: binary path is /node_modules/mongodb-memory-server/node_modules/.cache/mongodb-memory-server/mongodb-binaries/latest/mongod
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] requires a peer of mongodb@>= 3.0 but none is installed. You must install peer dependencies yourself.
npm WARN @1.0.0 No description
npm WARN @1.0.0 No repository field.

+ [email protected]
added 81 packages from 48 contributors and audited 166 packages in 35.706s
found 0 vulnerabilities

root@444a1d59d65f:/# node
> const path = require('path');
undefined
> const findCacheDir = require('find-cache-dir');
undefined
> path.resolve(findCacheDir({ name: 'mongodb-memory-server' }), 'mongodb-binaries');
'/node_modules/.cache/mongodb-memory-server/mongodb-binaries'

It worth to remove 'use mongodb-prebuild' clause from readme. No one reads the docs thought =)

I've noticed substantial delay in e2e tests due to on-demand mongodb server download.
On the other hand, on-demand download makes testing without internet access almost impossible because we've to mock 3rd-party infrastructure.

It worth to provide a way to have mongodb server as a part of this npm package or add some optional npm dependency (separate package) to take server from.

Looks like the download url format may have changed and would need to be updated.

Recently when running tests I have been seeing the download fail for mongo binary, indeed if i follow the link (in my case 3.6.0) logged for the download I am seeing a standard s3 empty page like:

Log output is as follows using this package with { debug: true }:

Mongo[58989] Starting MongoDB instance with following options: {"port":58989,"dbName":"01d7602e-c235-4d6b-9009-db9f21c189f0","uri":"mongodb://localhost:58989/01d7602e-c235-4d6b-9009-db9f21c189f0","storageEngine":"ephemeralForTest","dbPath":"/var/folders/q2/5tmxbvwj6gs33d926p9_m45h0000gn/T/mongo-mem-51484gWf8ctpeqK84"} +0ms
  console.warn node_modules/node-uuid/uuid.js:48
    [SECURITY] node-uuid: crypto not usable, falling back to insecure Math.random()

  console.log node_modules/mongodb-memory-server/lib/MongoMemoryServer.js:99
    Autostarting MongoDB instance...

  console.log node_modules/mongodb-memory-server/lib/util/MongoBinaryDownload.js:172
    Downloading MongoDB: https://downloads.mongodb.org/osx/mongodb-osx-x86_64-3.6.0.tgz

  Mongo[58989] renamed ~/.mongodb-binaries/mongodb-osx-x86_64-3.6.0.tgz.downloading to ~/.mongodb-binaries/mongodb-osx-x86_64-3.6.0.tgz +8s
  Mongo[59099] Starting MongoDB instance with following options: {"port":59099,"dbName":"e10683f2-87ed-4816-9320-2843d1c6fe35","uri":"mongodb://localhost:59099/e10683f2-87ed-4816-9320-2843d1c6fe35","storageEngine":"ephemeralForTest","dbPath":"/var/folders/q2/5tmxbvwj6gs33d926p9_m45h0000gn/T/mongo-mem-514841O3FXUa6dBXX"} +0ms
  console.log node_modules/mongodb-memory-server/lib/MongoMemoryServer.js:99
    Autostarting MongoDB instance...

  console.error node_modules/jest-jasmine2/build/jasmine/Env.js:198
    Unhandled error

  console.error node_modules/jest-jasmine2/build/jasmine/Env.js:199
    StatusCodeError: 403 - "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>C341FADDCC53868E</RequestId><HostId>rOpZu2a1arUiUY5MRo2eFY3ZGLNWps9d6aYWhEtvTWYUUpJQLO3rdPRKc3s3Ny3jXoEUQA40+9Y=</HostId></Error>"
        at new StatusCodeError (~/myProject/node_modules/request-promise-core/lib/errors.js:32:15)
        at Request.plumbing.callback (~/myProject/node_modules/request-promise-core/lib/plumbing.js:104:33)
        at Request.RP$callback [as _callback] (~/myProject/node_modules/request-promise-core/lib/plumbing.js:46:31)
        at Request.self.callback (~/myProject/node_modules/request/request.js:186:22)
        at Request.emit (events.js:125:13)
        at Request.emit (domain.js:421:20)
        at Request.<anonymous> (~/myProject/node_modules/request/request.js:1163:10)
        at Request.emit (events.js:125:13)
        at Request.emit (domain.js:421:20)
        at IncomingMessage.<anonymous> (~/myProject/node_modules/request/request.js:1085:12)
        at Object.onceWrapper (events.js:217:13)
        at IncomingMessage.emit (events.js:130:15)
        at IncomingMessage.emit (domain.js:421:20)
        at endReadableNT (_stream_readable.js:1101:12)
        at process._tickCallback (internal/process/next_tick.js:152:19)

When I try MongoDB version 3.6.3 on Win 7 64 bit with or without SSL, It did not work.
Seems like dowload URL scheme has changed on server.

The same as #32 but for Linux Mint.

Was trying just to make like this

if (/ubuntu|mint/i.test(os.dist)) {
      return this.getUbuntuVersionString(os);
}

But tests are failing

Hi,
i have this schema-index:

profilesSchema.index(
	{
		type: 1,
		name: 1,
	},{
		unique: true,
	}
);

type and name is a combined index. This works live, but in the test i can add two documents with the same type and the same name.

I am using binary: {version: '4.0.3' } on both sides.

Are unique indexes are supported, yet?

Hi,

We're working here on testing best practices and focus now on performance optimization.

Did you perform any comparison between using this lib vs persisted Mongo? I'm curious what performance gain one might see

Thanks!

Yoni Goldberg

Code examples in README.md mentions MongodbMemoryServer everywhere instead of MongoMemoryServer. Due to this any new person trying to use this module for the first time faces using these examples would face errors.

Will be awesome if somebody adds TypeScript declarations for better DX.

Like it did @toverux for graphql-compose:

• graphql-compose/graphql-compose#81
• graphql-compose/graphql-compose#82

Thanks!

Latest working version of mongo I tried is 3.6.3
When I try latest or 4.0.0/1/2/3 - it downloads binaries and then silently exits the process

(K)Ubuntu 18.04
Node v10.7.0
mongodb-memory-server 2.4.3

After coping the code from the Readme, when trying to connect I get this error -

failed to connect to server [localhost:52141] on first connect [MongoNetworkError: getaddrinfo ENOTFOUND localhost localhost:52141]

The mongoUri returned from getConnectionString is
"mongodb://localhost:52141/62448dc5-37f7-4158-a47e-e8e3b3b4a2c9"

I'm using mongoose 5.2.9
What am I missing ?
Thanks