This repository was archived by the owner on Nov 8, 2021. It is now read-only.
Releases: realm/realm-object-server
Releases · realm/realm-object-server
Release 3.9.6
Bugs fixed
- None
Enhancements
- None
Release 3.9.5
Bugs fixed
- Updated to Sync 3.8.5
- Fixed a bug that would result in the server crashing with
std::bad_alloc
in the error message.
- Fixed a bug that would result in the server crashing with
Enhancements
- None
Release 3.9.4
Bugs fixed
- None
Enhancements
- ROS can now be started with an option (--realm-size-reporting when started on the CLI and
enableRealmSizeReporting
when starting the server programatically) to periodically (currently every 30 minutes) emit stats about the size of
the data of realms stored on the server. These can be read by admin users via a new/stats/{metricName}
HTTP
endpoint. - Update to Sync 3.8.4.
- Improved the average memory usage during merge.
- Fixed another memory bug related to stray iterators while iterating in the merge algorithm, which could lead to memory corruption, changeset corruption, and crash the server/client.
- Optimized ChangesetIndex when merging changesets that mention a large number of objects.
Release 3.9.3
Bugs fixed
- ROS will no longer initialize new projects with the latest version of ROS by default.
Instead, it will use the version of the globally installed package. If you want to initialize
a project with the latest version of ROS, you can useros init my-project --latest
.
Enhancements
- Allow
ros init
to be run without an argument from an empty folder. In this case, it will
initialize the project in the current folder.
Release 3.9.2
Bugs fixed
- None
Enhancements
- Added two parameters -
shouldCompactRealmsAtStart
andshouldPerformPartialSyncAtStart
that control whether the server will compact the Realms and do a complete partial sync
during initialization. Compacting the Realms may reduce the disk space they use, while
performing partial sync will detect inconsistencies in the partial Realms and correct them
at the cost of incurring a client reset for the clients that used to synchronize against
an inconsistent Realm. It is recommended that they are set tofalse
(or left undefined)
unless you are experiencing Bad Changeset errors or excessive disk usage.
Release 3.6.5-2
Bugs fixed
- None
Enhancements
- None
Release 3.6.5-1
Bugs fixed
RealmDirectoryService
will initialize the Default Realm only once. This prevents extensively long ROS startup times
when the default Realm contains a lot of data.
Enhancements
- None
Release 3.9.1
Bugs fixed
- None
Enhancements
- None
Release 3.9.0
Enhancements
-
Added an optional
allowAnonymous
argument to route decorators. If not specified on the route level,
the service-level value will be used. To specify it for individual route, use the following syntax:@Get("/some-path", /* allowAnonymous */ true) public unauthorizedFunction() {}
The route-level value, if specified, will override the service-level value. To specify it at the service level,
use the following syntax:@BaseRoute("/my-service", /* allowAnonymous */ false) export class MyUnauthorizedService {}
The default value for the service decorator is
true
, meaning ROS will not enforce authorization requirements by
default.
Release 3.8.5
Bugs fixed
- None
Enhancements
- None