When someone connects to a MongoDB deployment with an invalid version (Ex: `4.2.18-`) Compass breaks on the parsing. This involves making Compass handle these without breaking.

V Old description below V

Problem Statement/Rationale

I have a mongoDB server running on an embedded Linux device, connected to a Windows laptop through a direct RNDIS/USB ethernet connection.

On the laptop, I'm running MongoDB Compass to connect to the database.

The data on the server is not protected (public), there is not any user defined nor any authentication.

• I can connect with MongoDB Compass.
• I can see the list of databases and the list of collections.
• But I cannot open any collection nor see any item in any collection from the UI.

Steps to Reproduce

• Start MongoDB Compass and connect to the mongoDB server with the following connection options:
  • Connect string: mongodb://192.168.XXX.XXX:27017 (where X is the real IP address)
  • Authentication: None
  • TLS/SSL: Default (Disabled)
  • Proxy/SSH: None
  • All the rest by default
• Wait for the list of databases to appear, and open one.
• Wait for the list of collections to appear, and try to open one (non-empty, obviously).

Expected Results

The collections can be opened and each individual entry can be read.

Actual Results

The collections cannot be opened (no arrow in the UI), nothing happens when clicking on a collection.

Additional Notes

• It used to work well with a previous version of MongoDB Compass from ~2 years ago (that I don't have anymore). Not sure though about the corresponding mongoDB server at that time.
• I can send commands from the terminal to Browse the database. I also tried Studio3T software and I can execute commands from the laptop, so it does not seem to be a configuration on the server nor a user permission issue.
• If I run the same database locally on the laptop (i.e. Windows version of the mongoDB server), it works and I can open the collections.