Open saibotma opened 6 days ago
Is it possible that you've upgraded drift without upgrading the drift worker? Generally that's something explicitly supported and tested, but IIRC we had a few bugs sending bigints over worker channels in older versions. These have been fixed, but required minor changes to the protocol when big ints are involved (I didn't consider this to be a breaking change because bigints were broken before).
It's possible that this can only be reproduced when a database operation actually returns a large value that can't be represented by JavaScript's number type, since IIRC we otherwise prefer to use normal numbers for efficiency.
The release is using the Drift worker of the 2.20.1 release: https://github.com/simolus3/drift/releases/tag/drift-2.20.1 Just double-checked, by overwriting it and then checking VCS.
Do you have access to the raw trace as reported by Firefox? There's no inferDeltaState
in the worker, so I think another tool might have applied a wrong source map here. The demangled trace when ignoring all entries that don't have drift_worker.js
appears to be:
org-dartlang-sdk:///lib/_internal/js_runtime/lib/string_helper.dart 164:8 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
org-dartlang-sdk:///lib/_internal/js_runtime/lib/string_helper.dart 164:8 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
org-dartlang-sdk:///lib/_internal/js_shared/lib/rti.dart 1225:1 dartProgram
That's not really helpful...
A customer reported, that his app was not working any more, after he switched to the newest version of the app which switched from Drift 2.15.0 to 2.20.2. He is running macOS 10.13 and Firefox 115.0. He also seems to have similar issues when running this app on Safari on his Mac, however I currently have no stack trace.
I tried to reproduce the issue by installing Firefox 115.0 on macOS 14.6.1 without success, unfortunately.
Just posting the stack trace here, in case someone has the same problem or maybe a solution to it.