LateInitializationError from _connectedDb when querying from isolate #1570
-
|
I am here again to ask for some assistance: In my app, I use When I launch the app, in my DatabaseConnection connection = DatabaseConnection.delayed(isolate.connect());Which I then use in my (multi) provider s.t. I can access it throughout my app: Provider<MyDatabase>(
create: (context) => MyDatabase.connect(connection),
dispose: (context, db) => db.close(),
)So far, so good. However, when I first access the database, I do so from another isolate (which is responsible for fetching data from the server), and in doing so, I get a After messing around for a bit, I found out I could prevent it by performing a query from the main isolate, which seems to force everything to initialize. That is, before I start the isolate that fetches and stores the data, I run MyDatabase db = Provider.of<MyDatabase>(context, listen: false);
// query the items table (empty at this time) and just ignore the result
await db.allItems().get();
startDataLoadingIsolate();The question is, is this expected behaviour? Am I doing something wrong, or is this a bug? Not sure if this is better fitted as a discussion topic or as an issue, it depends on what causes the problem for me, I suppose ;) Stack trace for the error |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
I feel like this is a drift issue. If this turns out to be you doing something wrong, we should at least report a much more actionable error message ;) If you can consistently reproduce this, could you enable |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! The debug log was actually very helpful already. Looking at it, I think 34d0ed5 may fix this problem? So far I've been unable to reproduce this outside of Flutter (and setting up a Flutter project is always a bit of additional hassle :D). If you have time to try the commit it would really help. Otherwise I'll try to reproduce this scenario with Flutter and |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Sorry for leaving you in the dark for a few days. I just replaced the moor_flutter:
path: ./localpackages/moor/moor_flutterwhere I checked out the commit you mentioned. Unfortunately, the same error still occurs for me: [OUT]: Request (id = 0): EnsureOpen(25, null)
[IN]: Request (id = 0): RunBeforeOpen(Instance of 'OpeningDetails', 0)
[OUT]: ErrorResponse (id = 0): LateInitializationError: Field '_connectedDb@255214145' has not been initialized. at #0 DriftClient._connectedDb (package:drift/src/remote/client_impl.dart)
[IN]: ErrorResponse (id = 0): LateInitializationError: Field '_connectedDb@255214145' has not been initialized. at #0 DriftClient._connectedDb (package:drift/src/remote/client_impl.dart)Complete stack traceIf I find the time I'll try to set up a more minimal app to reproduce this error tomorrow, which I can share with you |
Beta Was this translation helpful? Give feedback.
-
|
You probably won't get the updated implementation if you only override dependency_overrides:
drift:
path: ./localpackages/moor/driftBut if you have a minimal repro to share that would be amazing, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
With the depedency override it works as expected now, so your commit did indeed resolve my issue! [OUT]: Request (id = 0): EnsureOpen(26, null)
[IN]: Request (id = 0): RunBeforeOpen(Instance of 'OpeningDetails', 0)
[OUT]: Request (id = 1): EnsureOpen(26, 0)
[OUT]: SuccessResponse (id = 0): null
[IN]: SuccessResponse (id = 1): trueAs a note, the |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this can happen when only overriding some of the drift packages. Glad to hear that this fixes the issue! By the way, |
Beta Was this translation helpful? Give feedback.
I feel like this is a drift issue. If this turns out to be you doing something wrong, we should at least report a much more actionable error message ;)
If you can consistently reproduce this, could you enable
debugLog: truewhen callingDriftIsolate.connect? It would be interesting to see the messages being sent across isolates before this happens. If you share a bit more details on how you start the second isolate (where the error happens, I can also try to reproduce this myself). But maybe seeing the debug log will be enough.