Hehe, again great debugging, you found the new API Prototype thats running on port 3003
I believe you cannot do anything about it, it could be about the packaging, the conversion from .js to .exe using the nexe module.
Let me finish the queued jobs stuff, then i need to make a new package anyway and i''ll have a close look on the mediainfo stuff after packaging. I believe i just messed up with the latest package.
Just out of curiosity, when downloading the source code, did you go for the most current Version1 branch or for the source code attached to the release version 1.0.0.3?
Thats ok, the log prints the url to the new API (http://localhost:3003) anyway but it will take some time until we replace the included API with the new one. Until this time, i deliver the new API along with the webinterface. When it is finished, the 2 software modules will be splitted into separate .exe and windows services.
However, if you use 1.0.3 source and package then it is about a mistake at the packaging for sure. I'll post an update next week.
Thanks for all your debug work, thats really helpful
Is anyone using the dropdown option for job submissions? I create the variable with 'webui' prefix.
But no matter what formatting I use for the JSON key value pairs in the web UI I get:
'Workflow config error, user variables with "webui" in their names must have a valid JSON description. Actual description was:
"undefined"'.
hahhaahaha i was waiting for someone to encounter this handy feature Thank you for using this feature!
as nobody really seems to use it, the bug you found was not detected earlier. I just found and fixed it, new version is uploaded in a few minutes.
emcodem wrote: ↑Mon Aug 24, 2020 12:06 pm
Hi @ernie1901,
hahhaahaha i was waiting for someone to encounter this handy feature Thank you for using this feature!
as nobody really seems to use it, the bug you found was not detected earlier. I just found and fixed it, new version is uploaded in a few minutes.
I am seeing a bug whereby queued jobs dont appear in the web interface UI or locally in the Status Monitor.
The jobs are queued, because when previous ones finish the new ones appear and start.
Is this a known bug? They arent timing out, as this happens right away when I send jobs via the API.
My PC is set to only do 2 jobs at a time, the first two start but the other 8 dont appear until they start.
It's not a deal breaker by any means just seems strange.
