starting from systemBinary does not work as documented

Versions

• NodeJS: v14.16.1
• mongodb-memory-server-*: 7.2.1
• mongodb(the binary version): 4.4.5
• system: Manjaro Linux

package: mongo-memory-server

What is the Problem?

Starting the mongo memory server with

{
  instance: { port: 27017, dbPath: undefined },
  binary: { version: '4.4.7', systemBinary: '/usr/bin/mongod' }
}

or

{
  instance: { port: 27017, dbPath: undefined },
  binary: { systemBinary: '/usr/bin/mongod' }
}

leads the memory server to download and use the downloaded binary (4.4.7, 4.0.25 respectively), while it should use the specified one.

if im setting the environment variable MONGOMS_SYSTEM_BINARY=/usr/bin/mongod, the system binary is being used, but the output is:

getPath: MongoMemoryServer: Possible version conflict
  SystemBinary version: "4.4.5"
  Requested version:    "4.0.25"

  Using SystemBinary!

which in my eyes means that the start works as expected, but the output is kinda awkward because explicitly did not want to start 4.0.25, but the system binary. The output is a minor issue I don’t really care about - the ‘systemBinary’ having no effect is problematic.

[hasezoey]

this issue may be fixed with 7.3.1, which should be published in some minutes

most likely commit bc89da33a4cddaa3b4dda8480a2ba480d3cd3051 fixed this

Edit: version 7.3.1 is now published (if its not fixed, please update to that version and provide new logs)

[boredland]

tyvm, works like a charm now!