forked from arition/torch-js
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
bugSomething isn't workingSomething isn't working
Description
I had fixed a similar issue for List[Tensor]
, but haven't find a way to fix this yet. Created this issue mainly as a reminder.
node:44) UnhandledPromiseRejectionWarning: Error: predict_batch() Expected a value of type 'List[List[Tensor]]' for argument 'list_bboxes' but instead found type 'List[List[Tensor]]'.
Position: 2
Declaration: predict_batch(__torch__.main.Liveness_mbv3 self, Tensor[] images, Tensor[][] list_bboxes, float r_padding=0.25, int max_batchsize=1024) -> (Tensor[])
Exception raised from checkArg at /pytorch/aten/src/ATen/core/function_schema_inl.h:162 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x42 (0x7f9bc8cd62f2 in /horus/node_modules/@lamhoangtung/torch-js/build/libtorch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::string const&) + 0x5b (0x7f9bc8cd367b in /horus/node_modules/@lamhoangtung/torch-js/build/libtorch/lib/libc10.so)
frame #2: <unknown function> + 0xd9668f (0x7f9bb6fb568f in /horus/node_modules/@lamhoangtung/torch-js/build/libtorch/lib/libtorch_cpu.so)
frame #3: torch::jit::GraphFunction::operator()(std::vector<c10::IValue, std::allocator<c10::IValue> >, std::unordered_map<std::string, c10::IValue, std::hash<std::string>, std::equal_to<std::string>, std::allocator<std::pair<std::string const, c10::IValue> > > const&) + 0x2d (0x7f9bb945b88d in /horus/node_modules/@lamhoangtung/torch-js/build/libtorch/lib/libtorch_cpu.so)
frame #4: torch::jit::Method::operator()(std::vector<c10::IValue, std::allocator<c10::IValue> >, std::unordered_map<std::string, c10::IValue, std::hash<std::string>, std::equal_to<std::string>, std::allocator<std::pair<std::string const, c10::IValue> > > const&) + 0x138 (0x7f9bb94691e8 in /horus/node_modules/@lamhoangtung/torch-js/build/libtorch/lib/libtorch_cpu.so)
frame #5: <unknown function> + 0x115f3 (0x7f9bc8f2a5f3 in /torch-js/build/Release/torch-js.node)
frame #6: Napi::AsyncWorker::OnAsyncWorkExecute(napi_env__*, void*) + 0x5e (0x7f9bc8f2e35e in /torch-js/build/Release/torch-js.node)
frame #7: /usr/local/bin/node() [0x132e72e]
frame #8: <unknown function> + 0x76db (0x7f9c073b26db in /lib/x86_64-linux-gnu/libpthread.so.0)
frame #9: clone + 0x3f (0x7f9c070dba3f in /lib/x86_64-linux-gnu/libc.so.6)
(node:44) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:44) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working