Levi McCallum

Bumping the vram to 80GB appears to have resolved it for me. Possibly a OOM error?

@GoodBoyDigital I'll try your patch. Getting a sample repo together might take sometime on my end. Happy to screen share my project on discord if that is a helpful alternative...

I just found a ton of race conditions in my app because I implicitly assumed the items access in the store was thread safe. Moving to an actor would be...

@mergesort hi sorry just getting back into this now. The issue I saw is the `performInsert` method in the store snapshots the items via `currentItems`, mutates that set via the...

@mergesort I migrated to something like this in my own projects: ``` import Bodega import OrderedCollections import Foundation actor Store { private let storageEngine: StorageEngine private let cacheIdentifier: KeyPath //...

I've been iterating on my internal usage of Boutique. I've landed on a design that's similar to using a main and background context in CoreData. The UI can observe the...

The main actor approach of 3.0 does solve the original problem of write synchronization, but the tradeoff is a heavy amount of work on the main thread. I see your...

@aehlke yes i love it. It gives me the flexibility to write to main when I need to or write to background. So far, I haven't had issues with it...

Here's the base data controller in my app: ``` import Boutique import Foundation let sqliteDirectory = "sqlitecache" @MainActor protocol DataControllerProtocol: AnyObject { associatedtype Item: Identifiable & Codable & Sendable &...

Yes it also doesn't work super well if you do have access to @observable. I recommend the item stream.