Vicary A.
Vicary A.
@danawoodman I think your issue should be tracked separately, yours could be a documentation mismatch, or a genuine implementation mistake. This issue is about TypeScript types matching the current codebase...
Pinging @davidpatrick because this should not be stale.
As OP I don't want to drive this thread too much towards negativity, but I admit users do have their limits in patience. @EdNutting Adding to your point about resource...
The callback should be optional.
There are hidden restrictions on AWS side, but I believe my PR does the job. Please feel free to test it.
Gently ping @crowlKats from #7977, is the current array implementation intentional?
I built Deno from source using my fork in PR https://github.com/denoland/deno/pull/15853 and the backend check passes. I can do `await tf.ready();` and `tf.getBackend();` gives me `"webgpu"`. But when I tried...
@andykais Thanks for the hint. It turns out to be me prematurely disposing a tensor before the promise is resolved, we could definitely use a better error message but that's...
@rthadur See if this is enough to confirm my arch? 1. I use the terminal in VS Code, it natively supports M1 without Rosetta 2. 2. Running `node -p "process.arch"`...
*Last message was incorrect, I deleted it.* @rthadur 3.20.0 throws the same error, see the [build.log](https://github.com/tensorflow/tfjs/files/9421851/build.log). I went to https://storage.googleapis.com/tf-builds and search for `"napi-v8/3.20.0/CPU-darwin"`, nothing matches. In fact the closest...