[COMPASS-6709] MONGOSH | Getting unimplemented error on running exit or quit command Created: 07/Apr/23  Updated: 18/May/23

Status: Open
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Vijay Kumar Assignee: Ben Radcliffe
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Windows 10

Additional info:
MongoDB Compass version: 6.0.5

Error Code: [COMMON-90002]


Attachments: JPEG File Shell_1.JPG     JPEG File Shell_2.JPG     PNG File image-2023-04-07-23-40-19-619.png    

 Description   

Problem Statement/Rationale

As a user, when i'm trying to quit the Mongo DB  shell  Console using the 'exit/quit' command(s) and observing that 'MongoshUnimplementedError'. but the above commands and the corresponding action(s) has been mentioned in the help. 

Please find the attached screenshot(s) for ref.

Steps to Reproduce

  1. Open Mongo DB Compass and connect to any database
  2. Open Compass Shell and run any of the command i.e. exit / quit

Expected Results

The corresponding action for Mongo DB Compass Shell should be performed on running exit or quit command. No error should be displayed.

Actual Results

Getting the error as below: 

[MongoshUnimplementedError:|#]

[COMMON-90002] the exit/quit commands are not supported for current platform: Compass

Additional Notes

It would be an appropriate error message should be thrown since the two commands i.e quit / exit and the corresponding action has been mentioned in the Shell help screen. (Please refer the screenshot for ref)



 Comments   
Comment by Vijay Kumar [ 18/May/23 ]

ben.radcliffe@mongodb.com does any update on this ticket ?

Comment by Vijay Kumar [ 07/Apr/23 ]

Mongo DB Compass Version : 1.36.2

 

Comment by PM Bot [ 07/Apr/23 ]

Hello vijaykumarsinthu@gmail.com, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible.

Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again!

Generated at Wed Feb 07 22:44:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.