Results 262 comments of Andrew M

With expo 50.0.6 and react-native 0.73.4 debugging hermes doesn't work at all. Breakpoints never bind. May not be this plugin's fault however, it seems there are a lot of bugs...

Trying to set a breakpoint with verbose logging shows this ``` [2024-2-6 20:06:53] [Reply From Debugger To Target] { "id": 1030, "method": "Debugger.setBreakpointByUrl", "params": { "urlRegex": "file:\\/\\/\\/Users\\/imagio\\/dev\\/TaskHero\\/apps\\/taskhero\\/build\\/src\\/components\\/hero\\/HeroAvatarImage\\.js($|\\?)|\\/Users\\/imagio\\/dev\\/TaskHero\\/apps\\/taskhero\\/build\\/src\\/components\\/hero\\/HeroAvatarImage\\.js($|\\?)", "lineNumber": 995, "columnNumber":...

Anybody managed to solve this one? I just tried to add eslint to my repo for the first time ever and ran into this. Linting a single file takes 3+...

I'm working on migrating from Firebase to Supabase and I was surprised to come across this issue! Lack of transaction support from the client will mean extra work for us...

Thanks! Ah I also didn't know about the limitation of updating jsonb columns. That will also make my transition from firebase more challenging as I relied upon being able to...

@GollyJer I manually patched it with pnpm's patchedPackages feature. Since then I've given up on this since it's unmaintained and the code is really inscrutable. Instead now I emit all...

I've uncovered a little bit more info. I got the android studio debugger attached and when the app is hung it _always_ pauses on ```java //in SkiaDomView.java:41 protected native void...

Further probing -- pausing the app native thread reveals it's frozen on the following stack. It appers there's a deadlock at `rnv8::V8PointerValue::invalidate()` ![image](https://github.com/Shopify/react-native-skia/assets/858965/70f19724-3936-4821-8bcb-52f20fe7f2f6)

`mqt_js` thread looks interesting too, it appears stuck at `RNSkia::RNSkJsiViewApi::getEnsuredViewInfo` ![image](https://github.com/Shopify/react-native-skia/assets/858965/b544e557-9695-47db-983f-a5719af3c3b6)

I'm at the end of my ability to debug this further I think. @chrfalch @wcandillon does anything obvious jump out at you as the cause of this deadlock?