Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

profile command failing on .find() operation #195

Closed
Chinney opened this issue Sep 10, 2018 · 1 comment
Closed

profile command failing on .find() operation #195

Chinney opened this issue Sep 10, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@Chinney
Copy link

Chinney commented Sep 10, 2018

I am currently getting this error message whenever I use the find() command:

Error: profile command failed: {
  "_t": "OKMongoResponse",
  "ok": 0,
  "code": 115,
  "errmsg": "Command is not supported",
  "$err": "Command is not supported"
}

However everything still will be outputted. The message appears like 1 second after the shell has listed all results. I am not sure how to debug this. It does not appear on other operations like findOne() or if I concatenate with the count() command.

@stennie stennie added this to the 0.1.0 milestone Aug 24, 2019
@stennie stennie added the bug label Aug 24, 2019
@stennie
Copy link
Collaborator

stennie commented Aug 24, 2019

The original error message is from CosmosDB, which does not fully implement the MongoDB API.

Mongo Hacker uses the profile command to determine the current slowms value for comparison with the last query execution. I've changed this to assume the default (100ms) if the profile command is not supported (or authorised).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants