You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded the latest version today and upgraded from 1.71. Problem is, when running as a service, it runs fine for a bit and then gives me the following errors. I edited the time and the incremental number off the end for clarity. I thought it night have had something to do with too many cameras active at once, but running it as a non-service application I can trigger all of my cameras and it doesn't have an issue. Hopefully, this is something known and there's a fix rather than this being a serious issue. Version 1.71 doesn't suffer from this from what I can see...
Debug|AITOOLS.EXE|DetectObjects|192.168.0.4:5000|garage|Garage.20201124_184023831.jpg| (1/6) Uploading a 2305361 byte image to DeepQuestAI Server at http://192.168.0.4:5000/v1/vision/detection
Info|AITOOLS.EXE|WaitForNextURL|192.168.0.4:5000|garage|None| ---- All URL's are in use or disabled, waiting...
Error|AITOOLS.EXE|DetectObjects|192.168.0.4:5000|garage|Garage.20201124_184023831.jpg| Got http status code 'BadRequest' (400) in 341ms: Bad Request
The text was updated successfully, but these errors were encountered:
Try the beta version of deepstack referenced closer to the bottom of this thread, a few versions were published and they seem to work better than the windows version, and I think the 400 error was fixed. VorlonCD#65
Otherwise I cant think why running as a service would matter.
I downloaded the latest version today and upgraded from 1.71. Problem is, when running as a service, it runs fine for a bit and then gives me the following errors. I edited the time and the incremental number off the end for clarity. I thought it night have had something to do with too many cameras active at once, but running it as a non-service application I can trigger all of my cameras and it doesn't have an issue. Hopefully, this is something known and there's a fix rather than this being a serious issue. Version 1.71 doesn't suffer from this from what I can see...
The text was updated successfully, but these errors were encountered: