Release 3.10.6

Breaking changes

• The function loadFeatureToken has been removed. It has had no effect and has been deprecated since version 3.0.

Bugs fixed

• 3.10.0 introduced a change that forced ROS components to communicate over HTTPS when ROS itself was configured for HTTPS.
  However, on single-node deployments this caused communication to fail with hostname validation errors when the used SSL
  certificate was not valid over the loopback interface or listenAddress did not match the DNS name in the certificate.
  The fix is to not enable HTTPS communication between components by default. This feature is now enabled by setting the
  httpsForInternalComponents configuration option to true instead.
• Fixed a crash with sync client HTTP requests with a malformed Content-Length header. Such will now correctly result in
  responses with status code 400.

Enhancements

• None

Installation & rollback instructions

Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• None

Release 3.10.3

Breaking changes

• None

Bugs fixed

• None

Enhancements

• The server can now encrypt its realms with an encryption key passed in the realmsEncryptionKey configuration property.

Installation & rollback instructions

WARNING: A server with encrypted realms cannot be rolled back to an older version!
Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• Encrypting existing realm files is not possible. Only fresh deployments with zero state can use realms encryption. We're working on a migration path for existing deployments.

Release 3.10.2

Breaking changes

• None

Bugs fixed

• Fixed the consistency checker such that it does not crash on empty partial Realms.

Enhancements

• None

Installation & rollback instructions

Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• None

Release 3.10.1

Breaking changes

• None

Bugs fixed

• Adding a table and creating a subscription for it without having permissions to create the table could result in a CrossTableLinkTarget exception being thrown by Core.
• Outward partial sync was fixed to handle the case where temporary link targets have been previously deleted in the reference Realm. This bug could lead to crashes and error messages of type index out of range or an assertion of the form ndx < m_size. This bug could explain many of the index out of range crashes that have been seen. This bug has not led to bad changesets being generated, which means that there should be no remnants of the bug in existing Realms.

Enhancements

• None

Installation & rollback instructions

Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• None

Release 3.10.0-alpha.3

Breaking changes

• None

Bugs fixed

• None

Enhancements

• Refactored the internals of KubernetesSyncWorker to be a bit more
  straightforward. Each evaulation of the endpoints object will result
  in a new sync server configuration. This configuration is compared to the
  current one in order to determine if the server should be restarted.
• Configuration options can be read from the endpoints object's annotations
  when they are not overridden by the constructor. These options are:
  • sync.realm.io/log-level (string)
  • sync.realm.io/enable-download-log-compaction (boolean)
  • sync.realm.io/max-download-size (integer)
  • sync.realm.io/enable-debug-mode (boolean)
  • sync.realm.io/history-ttl (integer)
  • sync.realm.io/history-compaction-interval (integer)

Installation & rollback instructions

Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• None

Release 3.10.0

Breaking changes

• None

Bugs fixed

• None

Enhancements

• The sync worker has been upgraded to a multithreaded architecture. It now has two major internal threads, a networking event loop thread, and one worker thread for performing potentially long-running tasks. This improves the responsiveness of the server while executing larger queries.
• The sync worker now uses an adaptive scheme for caching and reusing query results, which improves query time and decreases load on the server.

Installation & rollback instructions

Please see https://docs.realm.io/platform/self-hosted/installation for installation, upgrade and rollback instructions.

Notable known issues

• None

Release 3.10.0-alpha.2

Bugs fixed

• None

Enhancements

• When the server is configured for HTTPS, its internal components will communicate over HTTPS in both single-node and multi-node deployments.

Release 3.9.17

Bugs fixed

• Fixed a bug that could occasionally cause the PermissionService to take longer than 30 seconds to start, resulting in the server terminating with a timeout error.
• Fixed a bug that would prevent the error details to be logged when a permission-related error occurs. Previously, we would log just An error occurred while executing GN callback, whereas now the full error details will be logged as well.

Release 3.10.0-alpha.1

Bugs fixed

• None

Enhancements

• None

Release 3.10.0-alpha

Bugs fixed

• None

Enhancements

• Uses sync 3.9.1, which introduces mulithreaded networking