2020-10-28T15:17:59+02:00 - �[31merror�[39m: �[31mUnhandled-exception:  { Error: listen EACCES 127.0.0.1:7001
    at Object.exports._errnoException (util.js:1024:11)
    at exports._exceptionWithHostPort (util.js:1047:20)
    at Server.setupListenHandle [as _listen2] (net.js:1302:19)
    at listenInCluster (net.js:1367:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1493:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:10)
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 7001 }�[39m

Netstat does not show anything listening on the port.

On my Windows 10 2004,

netsh interface ipv4 show excludedportrange protocol=tcp

includes this line in its output:

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      6953        7052

I'm not sure what those entries are for or whether they are the same on all PCs...

Ideally, a different port should be used if the error is encountered.

First of all ❤️ thanks for this great product.

Is there a way to export schema of a collection?

Affected Version: dbKoda 1.0.1
Operating System: Windows 10 Pro 1803, Build 17134.165

Steps to Reproduce

1. Open dbKoda
2. Enable "Password Store" on the Home Screen
3. Click the "+" Button on the "Connection Profiles" sidebar
4. Create a profile with: "Use SSL for all connections" and "Allow invalid certificates"
5. Connect to this profile
6. Right-Click the "Databases" field in the sidebar
7. Choose "Restore Databases"
8. Choose a Folder to restore from and a Database name
9. Execute

Expected Behaviour

• The database is restored
• The shell should contain the --sslAllowInvalidCertificates switch

Actual Behavior

• The database is not restored, failing with the following error:
  2018-07-24T18:18:27.080+0200 error dialing localhost:10250: SSL errors: 14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed
• The switch --sslAllowInvalidCertificates is not present in the shell, leading to above error

Workaround

Manually insert the --sslAllowInvalidCertificates switch before executing

I have a collection user with 4M data. However, when I execute the command db.user.find({});, i'm only getting only 20 in the view. db.user.count({}); does show 4M data;

I cant find Protocol option in Basic Connection tab . Can you help me?

Thanks

Hello, I need to connect via SSH through port 10900. How do I do?

system: osx
version: v1.0.0

i had set mongo binary path.

however it still error. why?

mongo is no problem from the command.

i need you help, thanks very much.

This is the icon that shows pinned in the taskbar:

While this is the icon that shows up in the start menu:

At https://dbkoda.useresponse.com/knowledge-base/article/how-do-i-connect-to-a-replica-set

I actually would prefer that one if it could come back from the dead versions :)

Environment

Operating system : osx (version 10.15.3)
dbkoda version : v1.1.0

config.yml

use Docker and do not create new container

Error Information

it is no problem from the command

I need you help , thank you very much. (･ェ･。)

Amazing UI. Does this support kerberos authentication or is it planned in road map?. Please advise.

Or at least have a warning regarding what information is dumped into stateStore.json

Running windows version 1.1.0:
and testing explain for aggregate queries:
I have this query:
db.test.aggregate([
{
"$match":
{
"$or": [
{
"variables.reportedBy.code": "CRM-00000625"
},
{
"variables.contactPerson.code": "CRM-00000625"
},
{
"variables.claimant.code": "CRM-00000625"
},
{
"variables.claimant.contactRef.code": "CRM-00000625"
},
{
"variables.claimants.code": "CRM-00000625"
},
{
"variables.claimants.contactRef.code": "CRM-00000625"
},
{
"variables.reportedBy.id": "7801184523"
},
{
"variables.contactPerson.id": "7801184523"
},
{
"variables.claimant.id": "7801184523"
},
{
"variables.claimant.contactRef.id": "7801184523"
},
{
"variables.claimants.id": "7801184523"
},
{
"variables.claimants.contactRef.id": "7801184523"
}]
}
},
{
"$project":
{
"lossNotificationNumber": 1,
"status": 1,
"policyNumber": 1,
"variables.reportedBy": 1,
"variables.contactPerson": 1,
"variables.claimant": 1,
"variables.claimants": 1
}
},
{
"$addFields":
{
"_match":
{
"$cond":
{
"if":
{
"$or": [
{
"$eq": ["$variables.reportedBy.code", "CRM-00000625"]
},
{
"$eq": ["$variables.contactPerson.code", "CRM-00000625"]
},
{
"$eq": ["$variables.claimant.code", "CRM-00000625"]
},
{
"$eq": ["$variables.claimant.contactRef.code", "CRM-00000625"]
},
{
"$eq": ["$variables.claimants.code", "CRM-00000625"]
},
{
"$eq": ["$variables.claimants.contactRef.code", "CRM-00000625"]
}]
},
"then": "code",
"else": "lax"
}
}
}
}])

when clicking explain, it generates correct query (explain() before aggregate) but fails with message: Failed to parse explain output, make sure to highlight entire statement.

db.common.formtemplate.localizeddocumentform.explain().aggregate([
{
$match: {
$or: [
{ "variables.reportedBy.code": "CRM-00000625" },
{ "variables.contactPerson.code": "CRM-00000625" },
{ "variables.claimant.code": "CRM-00000625" },
{ "variables.claimant.contactRef.code": "CRM-00000625" },
{ "variables.claimants.code": "CRM-00000625" },
{ "variables.claimants.contactRef.code": "CRM-00000625" },
{ "variables.reportedBy.id": "7801184523" },
{ "variables.contactPerson.id": "7801184523" },
{ "variables.claimant.id": "7801184523" },
{ "variables.claimant.contactRef.id": "7801184523" },
{ "variables.claimants.id": "7801184523" },
{ "variables.claimants.contactRef.id": "7801184523" }
]
}
},
{
$project: {
lossNotificationNumber: 1,
status: 1,
policyNumber: 1,
"variables.reportedBy": 1,
"variables.contactPerson": 1,
"variables.claimant": 1,
"variables.claimants": 1
}
},
{
$addFields: {
_match: {
$cond: {
if: {
$or: [
{
$eq: ["$variables.reportedBy.code", "CRM-00000625"]
},
{
$eq: ["$variables.contactPerson.code", "CRM-00000625"]
},
{
$eq: ["$variables.claimant.code", "CRM-00000625"]
},
{
$eq: ["$variables.claimant.contactRef.code", "CRM-00000625"]
},
{
$eq: ["$variables.claimants.code", "CRM-00000625"]
},
{
$eq: ["$variables.claimants.contactRef.code", "CRM-00000625"]
}
]
},
then: "code",
else: "lax"
}
}
}
}
]);

when running from cli, this query retyrns:
/* 1 */
{
"stages" : [
{
"$cursor" : {
"query" : {
"$or" : [
{
"variables.reportedBy.code" : "CRM-00000625"
},
{
"variables.contactPerson.code" : "CRM-00000625"
},
{
"variables.claimant.code" : "CRM-00000625"
},
{
"variables.claimant.contactRef.code" : "CRM-00000625"
},
{
"variables.claimants.code" : "CRM-00000625"
},
{
"variables.claimants.contactRef.code" : "CRM-00000625"
},
{
"variables.reportedBy.id" : "7801184523"
},
{
"variables.contactPerson.id" : "7801184523"
},
{
"variables.claimant.id" : "7801184523"
},
{
"variables.claimant.contactRef.id" : "7801184523"
},
{
"variables.claimants.id" : "7801184523"
},
{
"variables.claimants.contactRef.id" : "7801184523"
}
]
},
"fields" : {
"lossNotificationNumber" : 1,
"policyNumber" : 1,
"status" : 1,
"variables.claimant" : 1,
"variables.claimants" : 1,
"variables.contactPerson" : 1,
"variables.reportedBy" : 1,
"_id" : 1
},
"queryPlanner" : {
"plannerVersion" : 1,
"namespace" : "test",
"indexFilterSet" : false,
"parsedQuery" : {
"$or" : [
{
"variables.claimant.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimant.contactRef.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimant.contactRef.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimant.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimants.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimants.contactRef.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimants.contactRef.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimants.id" : {
"$eq" : "7801184523"
}
},
{
"variables.contactPerson.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.contactPerson.id" : {
"$eq" : "7801184523"
}
},
{
"variables.reportedBy.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.reportedBy.id" : {
"$eq" : "7801184523"
}
}
]
},
"winningPlan" : {
"stage" : "SUBPLAN",
"inputStage" : {
"stage" : "COLLSCAN",
"filter" : {
"$or" : [
{
"variables.claimant.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimant.contactRef.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimant.contactRef.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimant.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimants.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimants.contactRef.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.claimants.contactRef.id" : {
"$eq" : "7801184523"
}
},
{
"variables.claimants.id" : {
"$eq" : "7801184523"
}
},
{
"variables.contactPerson.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.contactPerson.id" : {
"$eq" : "7801184523"
}
},
{
"variables.reportedBy.code" : {
"$eq" : "CRM-00000625"
}
},
{
"variables.reportedBy.id" : {
"$eq" : "7801184523"
}
}
]
},
"direction" : "forward"
}
},
"rejectedPlans" : []
}
}
},
{
"$project" : {
"_id" : true,
"policyNumber" : true,
"status" : true,
"lossNotificationNumber" : true,
"variables" : {
"claimants" : true,
"claimant" : true,
"contactPerson" : true,
"reportedBy" : true
}
}
},
{
"$addFields" : {
"_match" : {
"$cond" : [
{
"$or" : [
{
"$eq" : [
"$variables.reportedBy.code",
{
"$const" : "CRM-00000625"
}
]
},
{
"$eq" : [
"$variables.contactPerson.code",
{
"$const" : "CRM-00000625"
}
]
},
{
"$eq" : [
"$variables.claimant.code",
{
"$const" : "CRM-00000625"
}
]
},
{
"$eq" : [
"$variables.claimant.contactRef.code",
{
"$const" : "CRM-00000625"
}
]
},
{
"$eq" : [
"$variables.claimants.code",
{
"$const" : "CRM-00000625"
}
]
},
{
"$eq" : [
"$variables.claimants.contactRef.code",
{
"$const" : "CRM-00000625"
}
]
}
]
},
{
"$const" : "code"
},
{
"$const" : "lax"
}
]
}
}
}
],
"ok" : 1.0
} whic you fail to parse. Thanx for help

What I did: close (Ctrl+W) the Performance Lab window. Ubuntu 18.04. Reproduced 2/2 after restarting dbKoda.

Looks like SSH access is needed to run a command? The controller log shows

1mError happened during initialisation of observable SSH Stats of profile

The app log shows

: Error: { code: 'SSH_NOT_ENABLED' }

I use mLab and don't have SSH access.

I'm trying to submit debug logs by clicking the "i" button in the bottom right corner, but after the spinner completes spinning, I see again the same prompt that was displayed initally:

Affected Version: dbKoda 1.0.1
Operating System: Windows 10 Pro 1803, Build 17134.165

Steps to Reproduce

1. Open dbKoda
2. Enable "Password Store" on the Home Screen
3. Click the "+" Button on the "Connection Profiles" sidebar
4. Check the checkbox "SCRAM-SHA-1(username/password)"
5. Fill out the connection profile data, including username and password
6. Click the "Save" Button

Expected Behaviour

• Profile will be saved, including the Password in the "Password Store"
• When trying to connect, and the connection parameters are valid, dbKoda should connect to the specified server/db

Actual Behavior

• dbKoda does not connect, reporting that there is no password stored

Workaround

Press the "Test" Button before saving

use version with 'dbKoda-1.0.1.29-01-2019.dmg' . alert 'Failed to find an available port for controller ranging from 7001 to 8000' when launch the dbkoda.app

Hi, I try to use this great tool but I'm faced with the following problem.

• dbKoda installed on Windows 10
• docker on Windows 10
• container launched on WSL (Ubuntu on Windows)

Docker config:

Basic config:

I try to connect to a MongoDB in docker, and test connection is a success:

But when I click on Connection button I get an error:

Can you help me plz?
thx

Right clicking in the "Please enter your password..." dialog produces the "New Local Terminal" pop-up menu:

A lot of developers who will use this app probably use 3030 for their apps, and it took me a while to figure out that running my app in the background broke dbKoda, in production it might be worth looking into using a random high port, or give the user to change this somehow :)

When we use aggregate builder ,the script start with
use databasename;

dbk_agg.sampleSize = 100;
dbk_agg.useLimitSample= true;
...

then run the script,show the result

but the results count limit by mongo shell DBQuery.shellBatchSize

can you add a new set at start stage ,just like sampleSize to set the mongoshell limit ?

some times we know the result count like $group...and we can use export csv to save the result.

Pressing OK does, predictably, nothing :)

One-click access to MongoDB administration on commands.

This is an env path issue in macOS's production build. Read the support docs for the below workaround. Please fix this in the production build.

Workaround:
• replace all docker run with the full path to docker, e.g. /usr/local/bin/docker run, in the config.yml

Hello,

If you use the import collection from csv and choose the headerLine check box the corresponding command is '--headerLine'. This lead to an error for me and I needed to change to '--headerline'. Not sure if this is just a problem with mongo versions. Also needed to add '--type csv'.

Thanks,

Tim

When the following query is run:

db.[redacted].update(
    { "name" : "[redacted]" },
    {
      $set: { "email": "[redacted]" }
    }
)

The taskbar shows these icons:

but the query never finishes.
Also worth mentioning that the connection is done through an ssh tunnel.

Current form of restore database functionality does not support archives. To support it we need to be able to choose archive files instead of a folder(from ui). Also --archive should be enabled if the selection is a file.

This URI works in mongochef, but I'm getting Authentication error in dbKoda. Of the form:

mongodb://username:[email protected]:port/dbname

(w/ user/pass replaced w/ actual values)

While connecting to a mongoDB instance i get this error:

Error: Create shell connection failed. Mongo binary might be corrupted.

Please check your mongo binary path, or define your own mongoCmd in ~/.dbKoda/config.yml (Refer to this doc for details)

connection is to localhost:27017

I'm trying to connect using cluster configuration. The test connection is successful. But the connection fails,

I turned on SSL connection. Allow invalid certificates. And, username/password configuration. Which should be one. I'm also using Robo 3T. The configuration I made in Robo 3T is successful.

Error message:
Error: Timeout of 60000ms exceeded calling mongo-connection::create

wondering if this works with mongodb 4.0

1. Run a query that produces a document with nested fields.
2. Manually expand one of the subfields by clicking on it.
3. Click one of the 1, 2, 3, or All buttons.

Nothing happens. The buttons only work until the user clicks a field to expand.

For those using adequate OS/machine-level security practices, the dbKoda's password options may be overkill. As another data point, no other MongoDB admin tool I've used forced me to go through the password setup process. On the contrary, in Studio3T you can simply paste a connection URL, and off you go. Some other tools get the string from the clipboard already.

EDIT: this is actually more annoying than I thought. With the Password Store enabled, I've been unable to save a profile's password. I paste the connection string in the URI field, click Test ("Connection Success!"), Save, then Open Connection says "Error: Authentication failed.". Going back to the profile shows the password has been erased.

I don't need or want this level of security at the expense of convenience. I'm using other security measures that have worked very well for me for the past ~15 years.

https://github.com/SouthbankSoftware/dbkoda/releases/download/12-10-2017/dbKoda-0.8.0-beta.1.12-10-2017.dmg

Only shows start screen with moving logo, but doesn't get to main screen

For example if I add a new field in a projection the aggregation builder is not aware of that manual change.

Love it so far. Good work.

Issue: When I find my collection, I can scroll horizontally in the raw view, but in a table view I have no horizontal scroll.
example code:db.getSiblingDB("testDB").getCollection("testCollection").find( { }, { });
Expected result: I expect to be able to scroll horizontally.

Version 0.8.1 on Linux

1. Connect to a profile
2. Double click a connection .dbKoda helpfull shows a number of records in a table. Note,
   • the JSON toolbar icon is disabled - is this intended?
   • no query is shown in Query Input tab. It's blank. Seems like the query that produced the table results should be pre-filled.
3. Click the "View Raw output" icon.

Now "View JSON Tree output" becomes enabled, but clicking it leads to a JSON parsing error.

It would be nice to have something like my mock in which you can see numeric and graphic performance of a pipeline. Even more it would be better if I can make comparisons between pipelines.

A naive implementation would be to execute several iterations of the pipeline stages adding 1 stage in the next iteration:

• match -> get results
• match + unwind -> get results
• match + unwind + lookup -> get results

Thanks for sharing this nice tool!

As a new user, I had some trouble following this prompt:

Tip: To avoid seeing this prompt every time you connect, you can setup a password store in Preferences

File -> Preferences toggles the left sidebar. The prompt could say, "Config -> General"

Request from useResponse

Hi dbKoda team,

this is not an issue but an request for future enhancements.

It would be cool to have code completion in the editor window while using the Javascript engine of MongoDB.

Thanks for building this amazing application which got even better with the recent release of version 1.0. Congratulations on that.

Best regards,

Tobias

MongoDB atlass provides with following link: mongodb+srv://lympo-io-xxx.mongodb.net/test

While dbKoda says that mongodb+srv schema is not supported. Well for 3.6 mongo version is totally valid. So what's the problem?

In the generated code collections with spaces have problem as the generated code just uses collection name with . syntax

db.Example With Space.aggregate(...);

The correct form should be like, at least to my knowledge.

db["Example With Space"].aggregate(...);

Nice work on this @southbanksoftwaredeveloper ! I've just spent my first couple hours working with this tool. Am I overlooking a color scheme / theme option. I'm having some difficulty seeing the text in the editor with the dark background and the muted text colors.

After successfully login(confirmed from Query console), I got the error as blow:

TypeError: this.text.toLowerCase is not a function
    at e.value (app.803ff66….js:140)
    at e.value (app.803ff66….js:140)
    at e.value (app.803ff66….js:66)
    at C (app.803ff66….js:20)
    at e.n (app.803ff66….js:20)
    at e.value (app.803ff66….js:66)
    at C (app.803ff66….js:20)
    at e.n (app.803ff66….js:20)
    at app.803ff66….js:140
    at C (app.803ff66….js:20)

In the mean while, Topology Window shows "Loading topology..."

dbkoda version: Version 0.8.0 (0.8.0.80)
macOS version: 10.12.6

Thanks for your hard working, best wishes!

The above is an example. Look at all that whitespace it is wasting! WHY???

This app should support multiple layout styles for the data. There should a raw json version, a table-like version, and any extra ways to visualize that we can think of.

For whatever reason, this app has a very large amount of UI lag, when clicking/loading things. Not sure what's up with that. If I have time, i'll try to create a PR for some fixes for the UI stuff.

I have a read-only connection to reporting DB, and trying to show .find() results as JSON fails, probably because the output includes the profile command failing:

Error: profile command failed: {
  "operationTime": Timestamp(1561102597, 1),
  "ok": 0,
  "errmsg": "not authorized ... to execute command { profile: -1.0, ... }",
  "code": 13,
  "codeName": "Unauthorized",
  ...
}

I have cloned dbkoda, dbkoda-controller and dbkoda-ui into the same directory
afterwards I installed yarn, as it was needed, according to the instructions here

Then I ran yarn link:dev as described in the README, but it failed.

> yarn dev:link
yarn run v1.19.1
$ yarn run dev:link:controller && yarn run dev:link:controller:ui && yarn run dev:link:uiDefinitions
$ rimraf assets/controller && ln -s "$(cd ../dbkoda-controller && pwd)" assets/controller && (cd assets/controller && (yarn unlink > /dev/null 2>&1; exit 0) && yarn link) && yarn link "@southbanksoftware/dbkoda-controller"
success Registered "@southbanksoftware/dbkoda-controller".
info You can now run `yarn link "@southbanksoftware/dbkoda-controller"` in the projects where you want to use this package and it will be used instead.
success Using linked package for "@southbanksoftware/dbkoda-controller".
$ cd ../dbkoda-controller && rimraf public/ui && ln -s "$(cd ../dbkoda-ui/dist/ui && pwd)" public/ui
/bin/sh: 1: cd: can't cd to ../dbkoda-ui/dist/ui
ln: failed to create symbolic link 'public/ui' -> '': No such file or directory
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I continued on with the installation anyway, and I got some missing/invalid dependency warnings for example:

> yarn install
yarn install v1.19.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > [email protected]" has unmet peer dependency "request@^2.34".
warning "request-promise-native > [email protected]" has unmet peer dependency "request@^2.34".
warning " > [email protected]" has incorrect peer dependency "winston@^2 <= 3.0.0-rc9 || ^3".
warning " > [email protected]" has incorrect peer dependency "[email protected] || 20.x".
[5/5] Building fresh packages...
$ yarn run cbuild
yarn run v1.19.1
$ yarn run clean && yarn run build
$ rimraf lib
$ babel --ignore tests -d lib/ src/
src/app.js -> lib/app.js
src/components/drill.js -> lib/components/drill.js
src/components/performance.js -> lib/components/performance.js
src/helpers/identifyWorkingMode.js -> lib/helpers/identifyWorkingMode.js
src/helpers/index.js -> lib/helpers/index.js
src/helpers/invokeApi.js -> lib/helpers/invokeApi.js
src/helpers/pkginfo.js -> lib/helpers/pkginfo.js
src/helpers/raygun.js -> lib/helpers/raygun.js
src/helpers/raygun.offline.js -> lib/helpers/raygun.offline.js
src/helpers/winston.js -> lib/helpers/winston.js
src/index.js -> lib/index.js
src/touchbar.js -> lib/touchbar.js
Done in 5.14s.
Done in 42.72s.

or

> yarn run pack
yarn run v1.19.1
$ yarn run cbuild && ELECTRON_BUILDER_ALLOW_UNRESOLVED_DEPENDENCIES=true build --dir --config.extraMetadata.mode=prod
$ yarn run clean && yarn run build
$ rimraf lib
$ babel --ignore tests -d lib/ src/
src/app.js -> lib/app.js
src/components/drill.js -> lib/components/drill.js
src/components/performance.js -> lib/components/performance.js
src/helpers/identifyWorkingMode.js -> lib/helpers/identifyWorkingMode.js
src/helpers/index.js -> lib/helpers/index.js
src/helpers/invokeApi.js -> lib/helpers/invokeApi.js
src/helpers/pkginfo.js -> lib/helpers/pkginfo.js
src/helpers/raygun.js -> lib/helpers/raygun.js
src/helpers/raygun.offline.js -> lib/helpers/raygun.offline.js
src/helpers/winston.js -> lib/helpers/winston.js
src/index.js -> lib/index.js
src/touchbar.js -> lib/touchbar.js
  • electron-builder version=20.2.0
  • loaded configuration file=/home/paul/bin/dbkoda/electron-builder.json
  • writing effective config file=dist/electron-builder.yaml
  • Unresolved node modules: webpack
  • rebuilding native production dependencies platform=linux arch=x64
  • rebuilding native dependency name=bcrypt
  • rebuilding native dependency name=node-pty
  • rebuilding native dependency name=uws
  • rebuilding native dependency name=ws
  • rebuilding native dependency name=ws
  • packaging       platform=linux arch=x64 electron=1.8.6 appOutDir=dist/linux-unpacked
Downloading tmp-30012-1-SHASUMS256.txt-1.8.6
[============================================>] 100.0% of 5.74 kB (5.74 kB/s)
Done in 94.45s.

Then in the end I got a bunch of exceptions.

> yarn dist
yarn run v1.19.1
$ ELECTRON_BUILDER_ALLOW_UNRESOLVED_DEPENDENCIES=true yarn run dist:basic --publish never
$ yarn run cbuild && build --config.extraMetadata.mode=prod --publish never
$ yarn run clean && yarn run build
$ rimraf lib
$ babel --ignore tests -d lib/ src/
src/app.js -> lib/app.js
src/components/drill.js -> lib/components/drill.js
src/components/performance.js -> lib/components/performance.js
src/helpers/identifyWorkingMode.js -> lib/helpers/identifyWorkingMode.js
src/helpers/index.js -> lib/helpers/index.js
src/helpers/invokeApi.js -> lib/helpers/invokeApi.js
src/helpers/pkginfo.js -> lib/helpers/pkginfo.js
src/helpers/raygun.js -> lib/helpers/raygun.js
src/helpers/raygun.offline.js -> lib/helpers/raygun.offline.js
src/helpers/winston.js -> lib/helpers/winston.js
src/index.js -> lib/index.js
src/touchbar.js -> lib/touchbar.js
  • electron-builder version=20.2.0
  • loaded configuration file=/home/paul/bin/dbkoda/electron-builder.json
  • writing effective config file=dist/electron-builder.yaml
  • Unresolved node modules: webpack
  • rebuilding native production dependencies platform=linux arch=x64
  • rebuilding native dependency name=bcrypt
  • rebuilding native dependency name=node-pty
  • rebuilding native dependency name=uws
  • rebuilding native dependency name=ws
  • rebuilding native dependency name=ws
  • packaging       platform=linux arch=x64 electron=1.8.6 appOutDir=dist/linux-unpacked
  • building        target=AppImage arch=x64 file=dist/@southbanksoftware/dbkoda-1.1.0-x86_64.AppImage
  • downloading               path=/home/paul/.cache/electron-builder/appimage/appimage-9.0.7 url=https://github.com/electron-userland/electron-builder-binaries/releases/download/appimage-9.0.7/appimage-9.0.7.7z
  ⨯ exit status 1
output: WARNING: zsyncmake is missing, please install it if you want to use binary delta updates
Using architecture x86_64
Deleting pre-existing .DirIcon
Creating .DirIcon symlink based on information from desktop file
Generating squashfs...
Could not create destination file: No such file or directory
Embedding ELF...
Not able to open the AppImage for writing, aborting
/home/paul/bin/dbkoda/dist/__appImage-x64 should be packaged as /home/paul/bin/dbkoda/dist/@southbanksoftware/dbkoda-1.1.0-x86_64.AppImage

Hi, I'm working on windows and have my mongodb database in a virtual box container.
DBKoda is asking me for a path to mongodb but the thing is that I have not installed mongodb in my host system but only in the virtual box.

How can I connect to my box?

Host: 127.0.0.1
Port: 2222
User: vagrant
Pass: *****

And in settings:

Mongo binary path: /usr/bin/mongo

but it tries to find that path probably on the host system and not in the container so that's not working

I get this error:

Error: Creation of shell connection failed. Unable to detect your mongo binary.

Please make sure the Mongo shell is in your path, or define path to mongo shell in the Preferences Panel.(Refer to this doc for details)

I have no problem with Robo 3T. Setting up a SSH Tunnel and everything works fine.

running explain() on this query returns the following error:
"Failed to parse explain output, make sure to highlight entire statement"

db.mydb
  .explain("queryPlanner")
  .find({
    data: {
      $in: [
        "38029B",
        "3807FA",
        "3808FA",
        "380EBA",
        "3815BA",
        "382A9A",
        "394A62",
        "394A63",
        "3C1215",
        "3C127A"
      ]
    },
    ts: { $gte: ISODate("2017-11-24T16:12:38Z") }
  });

it works when removing the filter ts: { $gte: ISODate("2017-11-24T16:12:38Z") }.

mongodb version is 3.4