See issue at https://jira.mongodb.org/browse/SERVER-4785 and https://jira.mongodb.org/browse/SERVER-18946

Here is the test result.

[email protected]:~/github/mongo$ ./mongo

db.getProfilingStatus() { "was" : 0, "slowms" : 100, "sampleRate" : 1 } db.setProfilingLevel(0, 1) { "was" : 0, "slowms" : 100, "sampleRate" : 1, "ok" : 1 } db.getProfilingStatus() { "was" : 0, "slowms" : 1, "sampleRate" : 1 } for(var i =0; i<10000; i++) {db.test.save({'i': i})} WriteResult({ "nInserted" : 1 }) use test2 switched to db test2 db.getProfilingStatus() { "was" : 0, "slowms" : 100, "sampleRate" : 1 } . -- test 2: still 100 for(var i =0; i<10000; i++) {db.test.save({'i': i})} WriteResult({ "nInserted" : 1 })

as a result: we capture the slow queries from test database but not for test2 database.

` 2017-12-26T13:38:32.678+0800 I COMMAND [conn1] command test.test appName: "MongoDB Shell" command: insert { insert: "test", ordered: true, $db: "test" } ninserted:1 keysInserted:1 numYields:0 reslen:29 locks:{ Global: { acquireCount: { r: 3, w: 1 } }, Database: { acquireCount: { w: 1, R: 1 } }, Collection: { acquireCount: { w: 1 } } } protocol:op_msg 3ms

`

The first two commits are of particularly low risk: they should not regress anything, since the new gcc atomic builtins are only used on new architectures not previously supported. In the IA-32 and x86_64 cases, the inline assembly continues to be used.

The benefit of these first two commits is that a build and smoke test on ARM (specifically Ubuntu armhf) now succeeds, provided that you use --use-system-v8 as the in-tree v8 does not support ARM.

The third commit switches IA-32 and x86_64 to also use the gcc atomic builtins instead of the previous inline assembly, as requested by Andy Schwerin in SERVER-12064. The inline assembly remains and covers the case of a build with an older gcc that does not support atomic builtins. This commit is higher risk, since I change the code path on IA-32 and x86_64, and I think warrants a close review to make sure that my understanding of the required semantics is correct.

For my purposes, I'm fine if you take just the first two commits, since I'll have enabled ARM and hopefully AArch64, too.

However, taking the third commit also is probably a good long term plan for the project.

I wanted to resolve SERVER-2459, so I patched /src/mongo/tools/dump.cpp to add a new command line option, --excludeCollection. I also updated the man file debian/mongodump.1 to reflect this. I think I have made these changes following the style of the existing code. This is my first contribution to Mongo and if you see issues with my code, I would appreciate any feedback. Thanks for considering my patch.

Hi: This pull request is about https://jira.mongodb.org/browse/SERVER-9306 and https://jira.mongodb.org/browse/SERVER-26589

The user story of this feature is something like this:

1. DBA want to drop an index
2. DBA is not confident enough to know if the index is not need at all.
3. The table is huge so recreating the index after drop will take a long time.

In this situation, we can make the index invisible for the following few days, which means mongodb will still maintain index for the following data change but the optimizer will not use it any more. If we found the index is still needed, we can simple rollback our change quickly by making it visible again. If we found the index is not needed for the following N days, we can drop it safely.

The reason why “indexStats” command in MongoDB 3.2 is not perfect for this user case is that the optimizer may choose a wrong index, so it will still show the index is in use but in fact it can be and should be dropped.

Here is an overview for this feature:

> for(var i = 0; i<10000; i++) { db.i.save({a: i})}
> db.i.createIndex({a: 1})
{
               "createdCollectionAutomatically" : false,
               "numIndexesBefore" : 1,
               "numIndexesAfter" : 2,
               "ok" : 1
}

> db.i.getIndices()
[
               {
                               "v" : 2,
                               "key" : {
                                               "_id" : 1
                               },
                               "name" : "_id_",
                               "ns" : "zhifan.i",
                               "invisible" : false
               },
               {
                               "v" : 2,
                               "key" : {
                                               "a" : 1
                               },
                               "name" : "a_1",
                               "ns" : "zhifan.i",
                               "invisible" : false
               }
]

> db.i.find({a: 100}).explain()
{
               "queryPlanner" : {
                               "plannerVersion" : 1,
                               "namespace" : "zhifan.i",
                               "indexFilterSet" : false,
                               "parsedQuery" : {
                                               "a" : {
                                                               "$eq" : 100
                                               }
                               },
                               "winningPlan" : {
                                               "stage" : "FETCH",
                                               "inputStage" : {
                                                               "stage" : "IXSCAN",
                                                               "keyPattern" : {
                                                                               "a" : 1
                                                               },
                                                               "indexName" : "a_1",
                                                               "isMultiKey" : false,
                                                               "multiKeyPaths" : {
                                                                               "a" : [ ]
                                                               },
                                                               "isUnique" : false,
                                                               "isSparse" : false,
                                                               "isPartial" : false,
                                                               "indexVersion" : 2,
                                                               "direction" : "forward",
                                                               "indexBounds" : {
                                                                               "a" : [
                                                                                               "[100.0, 100.0]"
                                                                               ]
                                                               }
                                               }
                               },
                               "rejectedPlans" : [ ]
               },
               "serverInfo" : {
                               "host" : "zhifan-dev16",
                               "port" : 27017,
                               "version" : "3.7.0-353-g2307b7a",
                               "gitVersion" : "2307b7ae2495b4b1c0caa0a83d7be1323b975fe4"
               },
               "ok" : 1
}

> db.runCommand({"collMod": "i", "index": {"name": "a_1", "invisible": true}})
{ "invisible_old" : false, "invisible_new" : true, "ok" : 1 }
> db.i.find({a: 100}).explain()
{
               "queryPlanner" : {
                               "plannerVersion" : 1,
                               "namespace" : "zhifan.i",
                               "indexFilterSet" : false,
                               "parsedQuery" : {
                                               "a" : {
                                                               "$eq" : 100
                                               }
                               },
                               "winningPlan" : {
                                               "stage" : "COLLSCAN",
                                               "filter" : {
                                                               "a" : {
                                                                               "$eq" : 100
                                                               }
                                               },
                                               "direction" : "forward"
                               },
                               "rejectedPlans" : [ ]
               },
               "serverInfo" : {
                               "host" : "zhifan-dev16",
                               "port" : 27017,
                               "version" : "3.7.0-353-g2307b7a",
                               "gitVersion" : "2307b7ae2495b4b1c0caa0a83d7be1323b975fe4"
               },
               "ok" : 1
}
> db.runCommand({"collMod": "i", "index": {"name": "a_1", "invisible": false}})
{ "invisible_old" : true, "invisible_new" : false, "ok" : 1 }
> db.i.find({a: 100}).explain()
{
               "queryPlanner" : {
                               "plannerVersion" : 1,
                               "namespace" : "zhifan.i",
                               "indexFilterSet" : false,
                               "parsedQuery" : {
                                               "a" : {
                                                               "$eq" : 100
                                               }
                               },
                               "winningPlan" : {
                                               "stage" : "FETCH",
                                               "inputStage" : {
                                                               "stage" : "IXSCAN",
                                                               "keyPattern" : {
                                                                               "a" : 1
                                                               },
                                                               "indexName" : "a_1",
                                                               "isMultiKey" : false,
                                                               "multiKeyPaths" : {
                                                                               "a" : [ ]
                                                               },
                                                               "isUnique" : false,
                                                               "isSparse" : false,
                                                               "isPartial" : false,
                                                               "indexVersion" : 2,
                                                               "direction" : "forward",
                                                               "indexBounds" : {
                                                                               "a" : [
                                                                                               "[100.0, 100.0]"
                                                                               ]
                                                               }
                                               }
                               },
                               "rejectedPlans" : [ ]
               },
               "serverInfo" : {
                               "host" : "zhifan-dev16",
                               "port" : 27017,
                               "version" : "3.7.0-353-g2307b7a",
                               "gitVersion" : "2307b7ae2495b4b1c0caa0a83d7be1323b975fe4"
               },
               "ok" : 1
}

all the existing test case are passed with python buildscripts/resmoke.py jstests/core/*.js and code is formated with python buildscripts/clang_format.py format

The $trim operator will limit the length of the arrays to which it is applied. A positive number indicates how many items to keep starting counting from the beginning of the array whereas a negative number keeps items from the end of the array.

array: [1 2 3 4 5 6 7 8] trim(5) -> keep 1 2 3 4 5, drop 6 7 8 -> [1, 2, 3, 4, 5] trim(-5) -> drop 1 2 3, keep 4 5 6 7 8 -> [4, 5, 6, 7, 8]

$trim is special as it is allowed (and required) to reference the same field as another update modifier. It can not be used by itself, but the same effect can be used by doing a $pushAll: [](pushing an empty list) at the same time as using $trim.

$trim is always performed after updating the field with any other modifier.

Test cases have been added.

Support Connection String URI Format for mongo auth.

Example usage: mongo mongodb://username:[email protected]:port/database

Jira Reference: https://jira.mongodb.org/browse/SERVER-6233

All sleepmillis() calls with values lesser than timer resolution will sleep AT LEAST the timer resolution value, making Mongo be really slow on certain use cases. Like when implementing consumer/producer patterns using capped collections to stream objects back and forth

Previously, exit was being implemented as a code in the DB shell, while quit was being implemented as a shell function. This meant that both were doing different things, and were called differently--i.e., exit could be run as is, whereas quit() had to be called as a function.

This PR allows building mongo with use of latest (3.0.1) scons which now uses python3 by default. There are still a lot of rough edges but on the end it allows building binary mongod

python version:

[email protected]:~/rpmbuild/BUILD/mongo-patched> python3 --version
Python 3.6.3
[email protected]:~/rpmbuild/BUILD/mongo-patched> 

scons version:

[email protected]:~/rpmbuild/BUILD/mongo-patched> scons -v
SCons by Steven Knight et al.:
        script: v3.0.1.74b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:16:53, by bdbaddog on hpmicrodog
        engine: v3.0.1.74b2c53bc42290e911b334a6b44f187da698a668, 2017/11/14 13:16:53, by bdbaddog on hpmicrodog
        engine path: ['/usr/lib/scons-3.0.1/SCons']
Copyright (c) 2001 - 2017 The SCons Foundation
[email protected]:~/rpmbuild/BUILD/mongo-patched>

and finally running scons on my machine

[email protected]:~/rpmbuild/BUILD/mongo-patched> scons -j 8 MONGO_VERSION=3.6.0  --disable-warnings-as-errors  --ssl
scons: Reading SConscript files ...
Mkdir("build/scons")
scons version: 3.0.1
python version: 3 6 3 final 0
Checking whether the C compiler works... yes
Checking whether the C++ compiler works... yes
...
...
...
ranlib build/blah/mongo/db/query/libquery_common.a
Generating library build/blah/mongo/db/libmongod_options.a
ranlib build/blah/mongo/db/libmongod_options.a
Linking build/blah/mongo/mongod
Install file: "build/blah/mongo/mongod" as "mongod"
scons: done building targets.
[email protected]:~/rpmbuild/BUILD/mongo-patched> 

and of course running built binary

[email protected]:~/rpmbuild/BUILD/mongo-patched> ./mongod --dbpath /tmp/ --bind_ip 127.0.0.1
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] MongoDB starting : pid=2937 port=27017 dbpath=/tmp/ 64-bit host=pc
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] db version v3.6.0
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] git version: 9038d0a67ee578aa68ef8482b1fc98750d1007a6
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.0g-fips  2 Nov 2017
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] modules: none
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] build environment:
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-12-22T18:52:02.566+0000 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1" }, storage: { dbPath: "/tmp/" } }
2017-12-22T18:52:02.566+0000 I STORAGE  [initandlisten] Detected data files in /tmp/ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-12-22T18:52:02.566+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=15542M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2017-12-22T18:52:02.637+0000 I STORAGE  [initandlisten] WiredTiger message [1513968722:637511][2937:0x7f87663729c0], txn-recover: Main recovery loop: starting at 6/4736
2017-12-22T18:52:02.679+0000 I STORAGE  [initandlisten] WiredTiger message [1513968722:679111][2937:0x7f87663729c0], txn-recover: Recovering log 6 through 7
2017-12-22T18:52:02.706+0000 I STORAGE  [initandlisten] WiredTiger message [1513968722:706386][2937:0x7f87663729c0], txn-recover: Recovering log 7 through 7
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] 
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] 
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] 
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] 
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] ** WARNING: soft rlimits too low. rlimits set to 4096 processes, 64000 files. Number of processes should be at least 32000 : 0.5 times number of files.
2017-12-22T18:52:02.730+0000 I CONTROL  [initandlisten] 
2017-12-22T18:52:02.736+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/tmp/diagnostic.data'
2017-12-22T18:52:02.737+0000 I NETWORK  [initandlisten] waiting for connections on port 27017

see https://github.com/marcello3d/node-buffalo/pull/11, please. Then could u check the following shell scripts:

var timespan = new ObjectId(Date.now() - 10*60*60*1000);
db.myColl.find({_id: {'$gt': timespan}}).count();

I would get the latest 10 hours records from their insertion date, It's useful.

Right now S2 library just writes any debugging output and errors to std::cerr. This patch changes S2's logger to use Mongo's LOG macros.

That way it is much easier to find errors in geometry primitives.

Patching CVE-2007-4559

Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.

If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

In recent releases of MongoDB, there’s a couple optimization been made around Refreshing incremental Routing Info, however the performance issue caused by it wasn’t rooted out for good that big sharded clusters would still suffer slow queries due to it.

Tencent cloud MongoDB team have (or hope so) come up with an optimization solution to solve the problem by utilizing Two-Dimensional Sorting & Search. With the optimization, there’d be no latency caused by refreshing routing info, that the refreshing time cost would remain at around 2ms regardless of the data size of the shreded cluster.

In the official release, refreshing routing info requires iterating full ChunkInfo in the ChunkMap twice, plus iterating ChunkVector once to free shared pointers – This could be very time- & resource-consuming if the chunk size exceeds certain threshold.

The updated _chunkMap and algorithm in the proposed method requires only one iteration on a very small portion of ChunkInfo based on the changed Chunks to update routing info: _chunkMap, _collectionVersion & _shardVersions.

Snyk has created this PR to upgrade http-server from 0.12.3 to 0.13.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 1 version ahead of your current version.
• The recommended version was released a year ago, on 2021-08-07.

The recommended version fixes:

Severity | Issue | PriorityScore (*) | Exploit Maturity | :-------------------------:|:-------------------------|-------------------------|:------------------------- | Denial of Service (DoS)
SNYK-JS-ECSTATIC-540354 | 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5 | Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade bezier-js from 4.0.3 to 4.1.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

• The recommended version is 2 versions ahead of your current version.
• The recommended version was released a year ago, on 2021-04-30.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs