Robo 3t 1.2 Download Mac Updated

Robo 3t 1.2 Download Mac

We are very happy to denote the release of Robo 3T 1.ii! In this release we have focused more often than not on solving some popular issues. However, we nevertheless have some improvements. One major comeback is Qt version upgrade from 5.7.0 to v.9.iii for better program stability, UI feel and Hi-DPI back up. All of the changes can exist seen below in "Table of Contents":

Table of Contents

Issues Fixes
1. Big double numbers are showing incorrectly (#1447)
2. Aggregate query results are not pagaeble (#1058)
3. Editing a projected certificate causes data override/loss (#881)
four. Error when starting up SSH session (#1189)
5. Robo 3T i.ane fails to offset on Ubuntu 17.Twenty (#1385)
6. Robo 3T is non opening on MacOS High Sierra (#1412)
7. Cannot load list of indexes (#1454)

Improvements:
one. Qt version upgraded from Qt v.vii.0 to Qt 5.9.iii
2. Auto switch from HTTPS to HTTP feature
3. Robo 3T is not buildable on latest MacOS Loftier Sierra


Bug Fixes

i. Big double numbers are showing incorrectly (#1447)

Wit this version, nosotros accept some fixes for some representation bug of big double numbers and some enhancements for better usability of them.

Let'south get-go with a quick presentation of one of the problematic case and how it was fixed, then keep with more examples and details.

Beneath, we come across the trouble where users were unable to save the document due to trailing '.0' characters in scientific notation of big double numbers.

In general, our goal was to stand for and behave exactly like mongo shell does. With this in mind, nosotros tried to achieve this goal equally much as possible with the following changes:

  • Fix: Disabled trailing zeros for scientific format
  • Enhancement: For better usability, frequently used e+xv and e+sixteen values are shown in non-scientific format. (Note: Similarly, in mongo crush, from east+fifteen to e+twenty values are shown not-scientific format, we wanted to bear exactly this way but could not due to some conversion issues)
  • Fix: '-inf' was shown incorrectly equally 'Infinity' in text fashion
  • Fix: 'Infinity/-Infinity' are now always shown as 'Infinity/-Infinity'. (The trouble earlier was 'Infinity' was shown 'inf' in table way and 'Infinity' in text way.)

A brusk comparing of problematic (on the left) and fixed (on the right) cases with examples:

          Robo 3T 1.i (before)                Robo 3T 1.ii (afterward)  -----------------------------       ------------------------- "e14": 150512101156575.0,           "e14": 150512101156575.0,     "e15": 1.50512101156575e+xv.0,      "e15": 1505121011565750.0, "e16": one.50512101156575e+sixteen.0,      "e16": 15051210115657500.0, "e17": 1.50512101156575e+17.0       "e17": 1.50512101156575e+17 "e18": 1.50512101156575e+18.0       "e17": i.50512101156575e+18 "inf": inf                          "inf": Infinity "inf_": -inf                        "inf_": -Infinity                  

Finally, let's run into how these values are shown in mongo shell:

          > db.getCollection('double').find({}).pretty() {         "e14" : 150512101156575,         "e15" : 1505121011565750,         "e16" : 15051210115657500,         "e17" : 150512101156575000,         "e18" : 1505121011565750000,         "inf" : Infinity,         "inf_" : -Infinity, }                  

two. Aggregate query results are not pagaeble (#1058)

The problem here was that aggregate query results were shown without paging bar (skip and batch fields). As a result information technology was not possible to folio through the results.

The problematic case and the fix are shown below:


iii. Editing a projected document causes information override/loss (#881)

4. SSH: Error when starting up SSH session (#1189)

This problem has kept us busy for a long fourth dimension. The biggest challenge here was, we tried many different setups and configurations, simply still we were unable to reproduce this consequence in our systems.

We attempted to fix this problem with a small code change and decided to include this change in a Beta to allow the users exam. Fortunately, we have 'by and large' positive results. (See results: issues/1189#issuecomment-353354032)

Users who take this trouble, mostly study errors in the format Error: Resources temporarily unavailable ..., 2 examples seen beneath:

          Error: Resources temporarily unavailable. No supported hallmark methods found. (Error #35)                  
          Error: Resource temporarily unavailable. Error when starting upward SSH session: -viii. (Error #35)                  

Details
Also, this fix seems to be fixing SSH errors for systems which accept this error in their SSH server logs:
kex protocol fault: blazon 30 seq 1 [preauth]

Alternative Solution
In the link below, an alternative workaround solution can exist seen submitted past one of our users:
issues/1125#issuecomment-323303611


v. Robo 3T 1.1 fails to first on Ubuntu 17.20 (#1385)

          ~/robo3t$ bin/robo3t  This awarding failed to start because it could non detect or load the Qt platform plugin "xcb" in "". Bachelor platform plugins are: xcb. ...                  

Users have started to have this problem generally on Ubuntu 17.04 which was an Ubuntu development release at the time of Robo 3T i.1 release.
(Annotation: Later on, Ubuntu 17.xx release download link has been removed on official Ubuntu download folio due to some security bug. Currently, the download links seems to exist back again.)

With Robo 3T 1.two (after Qt version upgrade to 5.9.iii), this issue seems to be fixed.

Workaround Solution:
Luckily, we too had a relatively unproblematic workaround solution which was to delete (or movement) robo3t-1.1.1-linux-x86_64-c93c6b0/lib/libstdc++* file:

          rm robo3t-1.1.1-linux-x86_64-c93c6b0/lib/libstdc++*                  

Details:
issues/1385#issuecomment-310014331

Note: Nosotros were unable to reproduce this issue, that's why we released an unofficial Robo 3T 1.2 Beta in order to brand sure this upshot is fixed. (Run across results: bug/1385#issuecomment-353275110)


6. Robo 3T is not opening on MacOS High Sierra (#1412)

This issue was started be seen on MacOS High Sierra where users were unable to open up/starting time Robo 3T program.

In order to solve this problem, we have upgraded our Qt version from 5.7.0 to Qt v.9.3 and included a crash prevention change in our code with Robo 3T ane.2.

These changes were likewise included in version one.2 Beta since nosotros were unable to reproduce these crashes in our systems. For this issue also, we take more often than not positive results. (See results: issues/1412#issuecomment-353276002)


seven. Cannot load list of indexes trouble (#1454)

This problem was seen when the index options document has unexpected values, such as "groundwork" : 1 or "thin" : 0 instead of correct values "background" : truthful or "thin" : false.

Index document every bit an case beneath:

                      {         "v" : ane,         "unique" : true,         "fundamental" : {             "services.OS.id" : i         },         "name" : "services.OS.id_1",         "ns" : "OS.users",         "thin" : 1 // should be 'true' not i     }                  

In this case, Robo 3T was unable to bear witness/load indexes. Subsequently this fix, indexes were visible.

Both the problem and the solution can seen beneath:

Reference:
db.collection.createIndex:
https://docs.mongodb.com/manual/reference/method/db.drove.createIndex


Improvements:

1. Qt version upgraded from Qt 5.7.0 to Qt v.9.3

We have upgraded Qt version from 5.vii.0 (15-Jun-2016) to 5.9.3 (21-Nov-2017). Master reasons for this upgrade were to set up crashes and build problems for MacOS High Sierra.


2. Motorcar switch from HTTPS to HTTP feature

The reason to add this feature was some low level HTTPS related crashes mostly seen on Linux systems. With this characteristic, Robo 3T switches to HTTP in the next plan start, after it detects HTTPS caused program abnormal exit/crash.

This characteristic is designed to be used for Welcome Tab where the information being exchanged is not user/critical data.

Note:
It is likewise possible to manually enable/disable this flag in config file.

robo-3t.json:

          ...  "useHttps" : false, ...                  

iii. Robo 3T is not buildable on latest MacOS High Sierra

In order to solve this problem, we had to upgrade Qt version from 5.7.0 to .5.9.3 and also apply a QScintilla patch (QScintilla-2.9.iii-xcode8.patch).

Subsequently these changes, Robo 3T could exist built on MacOS Loftier Sierra.

Download

Download Robo 3T 1.2, our best version of Robo 3T.

Savor!

Follow us on Twitter (@robomongo) to be notified about future releases. Please submit any found issues to our GitHub.

Robo 3t 1.2 Download Mac

Posted by: drummondcanetur.blogspot.com

Post a Comment

0 Comments