Skip to content
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

Allow creating notifiers inside write transactions before the first change #8439

Merged
merged 1 commit into from
Dec 19, 2023

Allow creating notifiers inside write transactions before the first c…

535097a
Select commit
Loading
Failed to load commit list.
Merged

Allow creating notifiers inside write transactions before the first change #8439

Allow creating notifiers inside write transactions before the first c…
535097a
Select commit
Loading
Failed to load commit list.
Xcode Cloud / RealmSwift | osx-swift_15.1 | Test - macOS succeeded Dec 19, 2023 in 19m 21s

37 warnings

Report Summary
Errors 0
Test Failures 0
Analysis Issues 0
Warnings 37

Details

37 Warnings

Details

  RealmSwift/Tests/RealmTests.swift:1697
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Direct access in function 'realm::sync::InstructionApplier::operator()(realm::sync::instr::SetInsert const&)::SetInsertResolver::on_set(realm::SetBase&)' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(instruction_applier.o)' to global weak symbol 'typeinfo for realm::Set' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(set.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
  RealmSwift/Tests/ObjectTests.swift:21
      Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
  No App Category is set for target 'TestHost'. Set a category by using the General tab for your target, or by adding an appropriate LSApplicationCategory value to your Info.plist.
  RealmSwift/Impl/RealmCollectionImpl.swift:205
      Passing argument of non-sendable type 'Value' outside of actor-isolated context may introduce data races
  RealmSwift/Tests/RealmTests.swift:1708
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  not stripping binary because it is signed: /Volumes/workspace/DerivedData/Build/Products/Release/RealmSwift.framework/Versions/A/RealmSwift
  RealmSwift/Tests/RealmTests.swift:1527
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Realm/RLMAsyncTask_Private.h:21
      Double-quoted include "RLMRealm_Private.h" in framework header, expected angle-bracketed instead
  RealmSwift/Tests/RealmTests.swift:1683
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1722
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1846
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Direct access in function 'realm::sync::InstructionApplier::operator()(realm::sync::instr::SetErase const&)::SetEraseResolver::on_set(realm::SetBase&)' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(instruction_applier.o)' to global weak symbol 'typeinfo for realm::Set' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(set.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
  RealmSwift/Tests/RealmTests.swift:1823
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1518
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/ObjectTests.swift:1691
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1502
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/ObjectTests.swift:1590
      Non-sendable type 'RealmPublishers.Value.Output?' (aka 'Optional') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Impl/RealmCollectionImpl.swift:188
      Passing argument of non-sendable type 'Value' outside of actor-isolated context may introduce data races
  file:///Volumes/workspace/DerivedData/Build/Products/Release/include/external/json/json.hpp:24596
      No newline at end of file
  RealmSwift/Tests/RealmTests.swift:1818
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Direct access in function 'makeError(realm::SyncError&&)' from file '/Volumes/workspace/DerivedData/Build/Intermediates.noindex/Realm.build/Release/Realm.build/Objects-normal/arm64/Realm_lto.o/17.arm64.thinlto.o' to global weak symbol 'realm::SyncError::c_recovery_file_path_key' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(sync_session.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
  RealmSwift/Tests/RealmTests.swift:22
      Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
  RealmSwift/Tests/ObjectAccessorTests.swift:71
      '16777217' is not exactly representable as 'Float'; it becomes '16777216'
  RealmSwift/Tests/RealmTests.swift:1841
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/ObjectTests.swift:1617
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1734
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Realm/RLMResults_Private.h:21
      Double-quoted include "RLMRealm_Private.h" in framework header, expected angle-bracketed instead
  RealmSwift/Tests/ObjectTests.swift:1620
      Non-sendable type 'RealmPublishers.ObjectChangeset.Output?' (aka 'Optional>') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1752
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  Direct access in function 'makeError(realm::SyncError&&)' from file '/Volumes/workspace/DerivedData/Build/Intermediates.noindex/Realm.build/Release/Realm.build/Objects-normal/arm64/Realm_lto.o/17.arm64.thinlto.o' to global weak symbol 'realm::SyncError::c_original_file_path_key' from file '/Volumes/workspace/DerivedData/Build/Products/Release/librealm-monorepo.a(sync_session.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
  not stripping binary because it is signed: /Volumes/workspace/DerivedData/Build/Products/Release/Realm.framework/Versions/A/Realm
  RealmSwift/Tests/RealmTests.swift:1875
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1866
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmCollectionTypeTests.swift:22
      Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'
  RealmSwift/Tests/RealmCollectionTypeTests.swift:707
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary
  RealmSwift/Tests/RealmTests.swift:1769
      Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary

Annotations

Check notice on line 21 in RealmSwift/Tests/ObjectTests.swift

See this annotation in the file changed.

@xcode-cloud xcode-cloud / RealmSwift | osx-swift_15.1 | Test - macOS

RealmSwift/Tests/ObjectTests.swift#L21

Add '@preconcurrency' to suppress 'Sendable'-related warnings from module 'RealmSwift'

Check notice on line 1691 in RealmSwift/Tests/ObjectTests.swift

See this annotation in the file changed.

@xcode-cloud xcode-cloud / RealmSwift | osx-swift_15.1 | Test - macOS

RealmSwift/Tests/ObjectTests.swift#L1691

Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary

Check notice on line 1590 in RealmSwift/Tests/ObjectTests.swift

See this annotation in the file changed.

@xcode-cloud xcode-cloud / RealmSwift | osx-swift_15.1 | Test - macOS

RealmSwift/Tests/ObjectTests.swift#L1590

Non-sendable type 'RealmPublishers.Value<SwiftObject>.Output?' (aka 'Optional<SwiftObject>') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary

Check notice on line 1617 in RealmSwift/Tests/ObjectTests.swift

See this annotation in the file changed.

@xcode-cloud xcode-cloud / RealmSwift | osx-swift_15.1 | Test - macOS

RealmSwift/Tests/ObjectTests.swift#L1617

Non-sendable type 'Realm' returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary

Check notice on line 1620 in RealmSwift/Tests/ObjectTests.swift

See this annotation in the file changed.

@xcode-cloud xcode-cloud / RealmSwift | osx-swift_15.1 | Test - macOS

RealmSwift/Tests/ObjectTests.swift#L1620

Non-sendable type 'RealmPublishers.ObjectChangeset<SwiftObject>.Output?' (aka 'Optional<ObjectChange<SwiftObject>>') returned by implicitly asynchronous call to nonisolated function cannot cross actor boundary