Unrecognized pipeline stage name: '$planCacheStats' - database

Getting the below error when I run the following aggregate commands on MongoDB version 4.0.12. From what I read about the error, it looks like a syntax issue. But this was given to me by someone and they said it works. Can someone please tell me what I'm doing wrong?
db.bookings.aggregate( [ { $planCacheStats: { } } ] )
db.bookings.aggregate( [ { $planCacheStats: { } } , { $project: {createdFromQuery: 1, queryHash: 1 } } ] )
Output:
E QUERY [js] Error: command failed: {
"ok" : 0,
"errmsg" : "Unrecognized pipeline stage name: '$planCacheStats'",
"code" : 40324,
"codeName" : "Location40324"
} : aggregate failed :
_getErrorWithCode#src/mongo/shell/utils.js:25:13
doassert#src/mongo/shell/assert.js:18:14
_assertCommandWorked#src/mongo/shell/assert.js:536:17
assert.commandWorked#src/mongo/shell/assert.js:620:16
DB.prototype._runAggregate#src/mongo/shell/db.js:260:9
DBCollection.prototype.aggregate#src/mongo/shell/collection.js:1062:12
#(shell):1:1

As you are using version 4.0, it is not supported. So you are getting unrecognised pipeline error
$planCacheStats - New in version 4.2
Hence it is Supported from 4.2.
Reference

Related

three.js three-nodes showing 'Module not found' error

./node_modules/three/examples/jsm/renderers/webgpu/nodes/WebGPUNodeBuilder.js
Module not found: Can't resolve 'three-nodes/core/CodeNode.js'.
I am using react, import three from node_modules, It throws an error like this.
What can I do to solve it?
Why "three-nodes/": "./jsm/nodes/" ?
I think this GitHub Issue is relevant:
https://github.com/mrdoob/three.js/issues/24377
three-nodes is an alias of three/examples/jsm/nodes, therefore, if you have this issue you need to make your program recognize this alias. You can find way to do it in Vite from this reply, or in rollup from the following config (with support of #rollup/plugin-alias)
{
...,
plugins: [
...,
alias({
entries: [
{ find: 'three-nodes', replacement: 'three/examples/jsm/nodes' }
]
})
]
}

My mongodb service is crashed with the following error, and I am unable to find the root cause from the mongodb logs

Mongodb service crashed and this was the error I noticed in logs
2020-12-20T06:25:03.184+0000 I COMMAND [conn303] getmore local.oplog.rs query: { ts: { $gte: Timestamp 16084451500|5 } } cursorid: ntoreturn:0 keyUpdates:0 writeConflicts:0 exception: interrupted at shutdown code:1 numYields:0 nreturned:1 reslen:69 locks:{ Global: { acquireCount: { r: 8 } }, MMAPV1Journal: { acquireCount: { r: 4 } }, Database: { acquireCount: { r: 4 } }, oplog: { acquireCount: { R: 4 } } } 2052ms
I would like to know what causes mongodb service to crash like this? afterwards, mongodb service stopped and shutted down, Any reason for this?
Thanks
This is not a crash report. The server is saying that it was asked to shut down and it aborted a query that was being executed. This is normal behavior.

Internal error during creation of App Engine via deployment manager

I am trying to create an App Engine service via Deployment Manager.
My deployment-manager.yaml file looks like below
imports:
- path: create-app-engine-std.py
resources:
- name: create-app-engine-std-app
type: create-app-engine-std.py
properties:
name: app-engine-std-app
appsId: projectId
zip:
sourceUrl: https://storage.googleapis.com/some-bucket/xyz.zip
filesCount: 2
version: v1
runtime: nodejs8
My create-app-engine-std.py look like below
def GenerateConfig(cxt):
deployment = {}
if cxt.properties['zip']:
deployment = {
'zip': {
'sourceUrl': cxt.properties['zip']['sourceUrl'],
'filesCount': cxt.properties['zip']['filesCount']
}
}
resources = [{
'type': 'gcp-types/appengine-v1:apps.services.versions',
'name': 'app-engine-std-app',
'properties': {
'servicesId': 'app-engine-std-test-app',
'appsId': cxt.properties['appsId'],
'deployment': deployment,
'runtime': cxt.properties['runtime'],
'threadsafe': True,
'id': cxt.properties['version']
}
}]
return {'resources': resources}
When I execute the deployment command I get following error
message: '{"ResourceType":"gcp-types/appengine-v1:apps.services.versions","ResourceErrorCode":"500","ResourceErrorMessage":"An
internal error occurred."}'
I tried using the apps.services.versions.create API but I always get following error although I am owner of the project
{
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}
Can someone guide me why I am getting the internal error and why can't I use the API. Thanks...

DEPRECATION NOTICE while trying to launch selenium chrome driver using nightwatch

I use chromedriver with nightwatch for my web-ui testing. Things were working until i got this message. How do i get around this issue
DEPRECATION NOTICE: Property chrome_driver is deprecated since v0.5.
Please use the "cli_args" object on the "selenium" property to define
"webdriver.chrome.driver". E.g.:
{
"cli_args": {
"webdriver.chrome.driver":
"<VALUE>"
}
}
The answer is there in your own question, and in the example on the Nightwatch site:
"selenium" : {
"start_process" : false,
"server_path" : "",
"log_path" : "",
"host" : "127.0.0.1",
"port" : 4444,
"cli_args" : {
"webdriver.chrome.driver" : "<chromedriver path>"
}
},
[...]

problems running qooxdoo simulation-run job

I am trying to use the qooxdoo simulation-run job for this simple test (with changed class namespace of course):
qx.Class.define("twitter.simulation.Settings", {
extend : simulator.unit.TestCase,
members :
{
testChangeLanguage : function()
{
this.fail("Test not implemented!");
}
}
});
However, every time I try to run it, I get this very misterious error:
js: uncaught JavaScript runtime exception: TypeError: org.mozilla.javascript.Undefined#275b35 is not a function, it is org.mozilla.javascript.Undefined.
I am using Rhino 1.7R4 for the Javascript engine. The Selenium version is 2.25 and qooxdoo is at 2.0.2. Here is the simulation-run job config:
"simulation-run" :
{
"let" :
{
"SIMULATOR_CLASSPATH" :
[
"../selenium/selenium-java-2.25.0.jar",
"../selenium/libs/*",
"../rhino/js.jar"
]
},
"environment" :
{
"simulator.selServer" : "localhost",
"simulator.selPort" : 4444,
"simulator.testBrowser" : "*firefox",
"simulator.autHost" : "http://localhost:8080",
"simulator.autPath" : "/application/index.html"
}
}
You need to use the 1.x Selenium client drivers.

Resources