Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to call Deepstack #175

Closed
Viksie opened this issue Jun 12, 2020 · 4 comments · Fixed by #179
Closed

Failed to call Deepstack #175

Viksie opened this issue Jun 12, 2020 · 4 comments · Fixed by #179
Assignees
Labels
bug Something isn't working

Comments

@Viksie
Copy link

Viksie commented Jun 12, 2020

First image analysed and triggers fired correctly.

Second attempt resulted in :

[Trigger Cat Cam] /aiinput/Cat_20200523-075000.jpg: Analyzing
[DeepStack] Failed to call DeepStack at http://deepstack:5000/: {"success":false,"error":"invalid image"}
(node:1) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'length' of undefined
at n (/home/node/app/bundle.js:9:83386)
at h (/home/node/app/bundle.js:9:89729)
at Module.b (/home/node/app/bundle.js:9:96406)
at Object. (/home/node/app/bundle.js:581:24268)
at /home/node/app/bundle.js:581:23561
at Object.next (/home/node/app/bundle.js:581:23666)
at o (/home/node/app/bundle.js:581:22380)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:1) 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:1) [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.

@Viksie
Copy link
Author

Viksie commented Jun 12, 2020

This happens with specific sample images.

Processes correctly

  • Cat_20200523-074700.jpg

Errors with

  • Cat_20200523-075100.jpg
  • Cat_20200523-075000.jpg

@Viksie
Copy link
Author

Viksie commented Jun 12, 2020

Please disregard. The images were downloaded with wget.

Upon downloaded via Windows and copying to Linux, all works 100%

@neilenns
Copy link
Owner

Thanks for the report, this is still a valid bug. I should be handling that exception cleanly.

@neilenns neilenns self-assigned this Jun 12, 2020
@neilenns neilenns added the bug Something isn't working label Jun 12, 2020
neilenns added a commit that referenced this issue Jun 12, 2020
neilenns added a commit that referenced this issue Jun 12, 2020
* Failed to call Deepstack
Fixes #175

* Update changelog
@neilenns
Copy link
Owner

Fixed. This will be available in the dev tagged image shortly, and in the latest tagged image on the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants