-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump core 14.10.4 #1801
Bump core 14.10.4 #1801
Changes from all commits
26ccf57
61f45b0
2c61ee4
c860bed
6497b06
b7364d2
7283573
642ddc7
354b99d
e790f6f
c89bb1e
d4c9b5d
033d245
2dd78e1
1b07d2e
36ff361
e825ebf
42cc4f5
364999a
088eb86
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -168,7 +168,7 @@ internal open class SyncSessionImpl( | |
nativePointer, | ||
error, | ||
message, | ||
true | ||
false | ||
) | ||
} | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -438,12 +438,20 @@ class AppTests { | |
|
||
// Create a configuration pointing to the metadata Realm for that app | ||
val metadataDir = "${app.configuration.syncRootDirectory}/mongodb-realm/${app.configuration.appId}/server-utility/metadata/" | ||
|
||
// Workaround for https://github.com/realm/realm-core/issues/7876 | ||
// We cannot validate if the test app metadata realm is encrypted directly, as it is cached | ||
// and subsequent access wont validate the encryption key. Copying the Realm allows to bypass | ||
// the cache. | ||
PlatformUtils.copyFile(metadataDir + "sync_metadata.realm", metadataDir + "copy_sync_metadata.realm") | ||
|
||
val wrongKey = TestHelper.getRandomKey() | ||
val config = RealmConfiguration | ||
.Builder(setOf()) | ||
.name("sync_metadata.realm") | ||
.name("copy_sync_metadata.realm") | ||
.directory(metadataDir) | ||
.encryptionKey(wrongKey) | ||
.schemaVersion(7) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why do we need to specify the schema version? the test is validating the encryption key... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because the schema version that the client is using to write the metadata realm is greater than 0 which is used by default. If we don't set it we will get a migration error when trying to open the realm. |
||
.build() | ||
assertTrue(fileExists(config.path)) | ||
|
||
|
@@ -478,10 +486,18 @@ class AppTests { | |
|
||
// Create a configuration pointing to the metadata Realm for that app | ||
val metadataDir = "${app.configuration.syncRootDirectory}/mongodb-realm/${app.configuration.appId}/server-utility/metadata/" | ||
|
||
// Workaround for https://github.com/realm/realm-core/issues/7876 | ||
// We cannot validate if the test app metadata realm is encrypted directly, as it is cached | ||
// and subsequent access wont validate the encryption key. Copying the Realm allows to bypass | ||
// the cache. | ||
PlatformUtils.copyFile(metadataDir + "sync_metadata.realm", metadataDir + "copy_sync_metadata.realm") | ||
|
||
val config = RealmConfiguration | ||
.Builder(setOf()) | ||
.name("sync_metadata.realm") | ||
.name("copy_sync_metadata.realm") | ||
.directory(metadataDir) | ||
.schemaVersion(7) | ||
.build() | ||
assertTrue(fileExists(config.path)) | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -152,7 +152,7 @@ | |
realm.syncSession.progressAsFlow(Direction.UPLOAD, ProgressMode.CURRENT_CHANGES) | ||
.run { | ||
withTimeout(TIMEOUT) { | ||
last().let { | ||
Check failure on line 155 in packages/test-sync/src/commonTest/kotlin/io/realm/kotlin/test/mongodb/common/FLXProgressListenerTests.kt GitHub Actions / Unit Test Results - Sync JVM MacOS arm64io.realm.kotlin.test.mongodb.common.FLXProgressListenerTests ► uploadProgressListener_changesOnly[jvm]
Raw output
|
||
assertTrue(it.isTransferComplete) | ||
assertEquals(1.0, it.estimate) | ||
} | ||
|
@@ -239,7 +239,7 @@ | |
try { | ||
val flow = realm.syncSession.progressAsFlow(Direction.UPLOAD, ProgressMode.INDEFINITELY) | ||
val job = async { | ||
withTimeout(10.seconds) { | ||
withTimeout(30.seconds) { | ||
flow.collect { | ||
channel.trySend(true) | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should add this version into
Repository variables
This version is only needed for sdkmanager and we should not build with it the library
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is succeeded by #1779. But the explicit reference to Java 17 is maintained. This syntax will cause
actions/setup-java
to install both17
andvars.VERSION_JAVA
so this is exactly allowing us to run the sdkmanager with Java 17 while building the rest withvars.VERSION_JAVA
pointed to byJAVA_HOME
.