Oleg Pudeyev
Oleg Pudeyev
Thanks for the report, what do you mean by "loading prior to testing" though? Paraspec is meant to start in a pristine environment with none of the application loaded in...
OK, can you then set `export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES` in your environment for all projects? Any reason not to do that?
I made an effort to minimize open network connections during forks but perhaps this can be improved further. Is the stack trace posted accurate with respect to where the issue...
paraspec hanging is a bug in any event, that shouldn't be happening.
https://github.com/mongo-express/mongo-express/pull/615 seems to do with query execution, this issue as far as I can tell is with m-e configuration processing and I don't think it has anything to do with...
That seems like it could be the fix although I am not 100% confident given the diff.
To clarify the requirements expressed in https://github.com/mongodb/bson-ruby/pull/284: the request is for rubocop to be configured to check a specific subdirectory of the project only (in this case `lib`) even though...
Also ran into this issue, is this project maintained?
If the goal of mlaunch is to encapsulate cluster provisioning logic, then having --setParameterMongod and setParameterMongos makes a lot of sense. With adminCommand, from https://docs.mongodb.com/manual/reference/command/setParameter/ it is not clear which...
Yes, if the user needs to do that many manual invocations, having mlaunch assist will definitely be appreciated.