Igor Mytyuk

Results 10 comments of Igor Mytyuk

I have the same issue, any solution for it?

@dfang having the same issue: ![image](https://github.com/supabase/supabase/assets/30237552/c69e04da-f4a1-479a-b9bb-1d44b1552ccc) I've just updated the docker-compose with studio version v0.23.09 but still having those console log errors.

I'm having still those errors in console.log() but at functional level all seems to work correctly: ![image](https://github.com/supabase/supabase/assets/30237552/5c38211a-d33c-40e6-b9ef-7cc383df6943)

@ivasilov it would be cool to be able to remove the subscriptions module for self-hosted so to prevent all those errors.

I'm trying to use Base64QRCode in .NET 8 and having the same issue, how could that be resolved?

The only workaround I've found for now with the latest supabase-js version is: `"overrides": { "@supabase/supabase-js": { "@supabase/auth-js": "2.61.0" } }`

I've resolve the issue by returning a .maybeSingle() without .limit(1)

What about adding a note that will remember about setting the custom context type on both `Bot` and `Commands` when they are used together? For instance, if `MyContext` is set...

Any update on it? I have "@supabase/supabase-js": "^2.43.4" and auth-js is 2.64.2 and still having that issue: ![image](https://github.com/supabase/supabase-js/assets/30237552/f6776f48-2e0f-49ad-bb70-c454088ab627)

Hi @encima, the issue happens exactly when I have some existing data that has been created or imported with a different naming convention on FKs. Btw I've "resolve" it be...