Thomas Coldwell

Would love to see this merged - pretty important for the bare workflow IMO :)

Good point - I've got it sending it's JWT over now and decoding using `supabase.auth.api.getUser()` in the `createContext` function. Setting up some middleware to check the `user` in the ctx...

Does the `viewerRouter` have sub routers as well then e.g. ``` viewerRouter() .middleware(authorizationFunction) .merge("user.", userRouter) .merge("feed.", feedRouter); ``` or are the endpoints added onto the `viewerRouter` directly: ``` viewerRouter() .middleware(authorizationFunction)...

I will have a look at this, probably worth mentioning about row-level security (RLS) rules that can be written on Supabase for this too so you don't have access from...

@wjx0820 This issue should now be resolved by #7 - just had to tell Prisma to use the non connection pooling URL when performing migrations - let me know you...

> Hi @jaewoolim, The aar builder is only designed to support a single aar file per application. Workarounds: 1)Build all into one AAR (issue has a relegated issue suggesting this)....

Had to work out a few memory management issues with the `Frame` in those last few commits 😅 A few key fixes they addressed: - ARC didn't count the `Frame`...

Just thinking how we want to handle the frame processor callback in cases where we want to draw on the frame or just perform some inference. In the first case...

The latest changes add a separate `useSyncFrameProcessor` to handle any synchronous work we might want to do on the frame e.g. drawing and is the only type of frame processor...

I've edited a bunch of stuff just to test out the depth data in frame processors that I'll remove in a new commit as well as linting + formatting btw....