Luka Secerovic

I agree, there's no need for ToTensorCustom then. I'll create a PR with these changes and link the issue.

I'm having the same issue as @Prasad-Techlead mentions. I'm able to script and trace Torchvision models and get correct predictions, but when converting to CoreML, I get the error `images.7...

Sadly, I forgot to make this change long time ago... I see now that GaussianBlur has been changed to use `radius`, which is incompatible with torchvision version of GaussianBlur, so...

I'm also having issues with `FormData is not defined`. I'm using version `1.109.0`. I've mitigated the error by using `1.106.0` version... But it would be great if there was a...

Hey @pauldambra, here's some info on how we're using it. I hope it helps: - it was defined in `packages.json` initially like this: `"posthog-js": "^1.105.9",` and that worked for a...

@pauldambra I was using `node 16` and `npm 8.X`. After updating npm to 10.5.0 and node to 21.x, it works! So the solution was updating node and npm versions.

That's an interesting observation! I think it's not a problem in a real scenario: - even in the case that (1,1) gets picked first, (1,2) would be picked after it....

Thank you Toby for making the code more readable!

Echoing this, my team also has a usecase for native support from searching across multiple tenants in a single query!

Bumping the visibility of this :) Is there a recommended way of doing this?