Hey @ernie1901
Well spotted. This is "by design", the reason is the way how ffastrans manages watchfolders. It is about like that: the watchfolder code does not use the same que as api jobs, it carries it's own queue because it could be that the file dissapears before enough resources are free to give up the job.
So i cannot display the jobs in the same way than other queued jobs, it would need it's own status type e.g. "file found" or "pending".
However, i am well aware about this and want to deal with it but it is a big piece of work because there is no jobid in that case and everything depends on the jobid in the webinterface's code.
Webinterface
Re: Webinterface
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
No worries and thanks emcodem. I went to lunch with only in progress jobs showing and came back and all my queued API jobs had appeared in the UI!
Weirdly this included already completed jobs still sat in a queued state.
Refreshing the page took me back to in progress jobs only removing the queued.
Thought it was worth mentioning in case it helps a fix.
Weirdly this included already completed jobs still sat in a queued state.
Refreshing the page took me back to in progress jobs only removing the queued.
Thought it was worth mentioning in case it helps a fix.
Re: Webinterface
Hey @ernie1901
ahh ok, that last thing should be a bug on the frontend, i'll check if i can reproduce and fix accordingly.
thanks mate!
ahh ok, that last thing should be a bug on the frontend, i'll check if i can reproduce and fix accordingly.
thanks mate!
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Hey @emcodem,
I upgraded to FFAStrans 1.1.0 and now I get "Error retrieveing queued jobs, lost connection to FFAStrans server. Is the FFAStrans API online? Error read: ECONNRESET" message every minute or so. The UI does actually update as expected though so functionality does not seem to be affected.
Is this the best place to post this? I dont mind using the bugs sub forum instead
I upgraded to FFAStrans 1.1.0 and now I get "Error retrieveing queued jobs, lost connection to FFAStrans server. Is the FFAStrans API online? Error read: ECONNRESET" message every minute or so. The UI does actually update as expected though so functionality does not seem to be affected.
Is this the best place to post this? I dont mind using the bugs sub forum instead
Re: Webinterface
Hey @ernie1901
sorry but i cannot reproduce easily. There is one bug in ffastrans 1.1 that prevents starting the REST API service in case you did not "upgrade" an existing installation but just run a fresh and clean new installation. But in that case, it should not work at all i guess.
Maybe you can stop the windows service for webinterface, start the server.exe by doubleclick and copy a bunch of error lines for me so i have more insight whats going on for you?
For the best place, i am happy when you post a message for me, no matter where
the only difference when posting in a new thread is that you get notified automatically and i dont have to write the @ernie stuff when i want the forum to notify you
sorry but i cannot reproduce easily. There is one bug in ffastrans 1.1 that prevents starting the REST API service in case you did not "upgrade" an existing installation but just run a fresh and clean new installation. But in that case, it should not work at all i guess.
Maybe you can stop the windows service for webinterface, start the server.exe by doubleclick and copy a bunch of error lines for me so i have more insight whats going on for you?
For the best place, i am happy when you post a message for me, no matter where
the only difference when posting in a new thread is that you get notified automatically and i dont have to write the @ernie stuff when i want the forum to notify youemcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Maybe I was a little too hasty apologies, a restart of the two windows services does appear to have fixed it.emcodem wrote: ↑Wed Sep 30, 2020 11:04 am Hey @ernie1901
sorry but i cannot reproduce easily. There is one bug in ffastrans 1.1 that prevents starting the REST API service in case you did not "upgrade" an existing installation but just run a fresh and clean new installation. But in that case, it should not work at all i guess.
Maybe you can stop the windows service for webinterface, start the server.exe by doubleclick and copy a bunch of error lines for me so i have more insight whats going on for you?
For the best place, i am happy when you post a message for me, no matter where
A little self investigation first is required next time I think!
Re: Webinterface
Ah i see... well there is room for improvement in how ffastrans cooperates with the webinterface, actually it would be best if the webint was always restarted along with the ffastrans application (or the rest service) to make sure everything works (e.g. after moving an installation). I am sure we will discuss this internally at some point in time!
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Hi Emcodem,
where could I set the column "Node" on Finished job under Job Status View?
Status View - Finished:
Job details view:
br,
Jerrysub
where could I set the column "Node" on Finished job under Job Status View?
Status View - Finished:
- ffastrans_view1.jpg (55.94 KiB) Viewed 8209 times
- ffastrans_view2.jpg (76.49 KiB) Viewed 8209 times
Jerrysub
Re: Webinterface
Hey @jerrysub,
Not sure if i understand correctly but if i did understand the answer is more kind of an explaination.
On the Finished job view, what you see is all the branches that a job did generate, grouped together.
On the Job details view, you see one more level down, all branches of the job and all nodes of each branch.
Now, the Job details view is basically parsing the job log in order to get this information while the finished job view gets it's informations from API calls. As the job log is not guaranteed to exist, i need to stick with showing the reliable information on the Job Details view.
If i would plan to show the nodes on the job history page, i would most likely introduce one more level of depth, e.g. you can expand one job to see its branches and then you can expand each branch to see the nodes it did execute.
Would this be what you imagined?
Not sure if i understand correctly but if i did understand the answer is more kind of an explaination.
On the Finished job view, what you see is all the branches that a job did generate, grouped together.
On the Job details view, you see one more level down, all branches of the job and all nodes of each branch.
Now, the Job details view is basically parsing the job log in order to get this information while the finished job view gets it's informations from API calls. As the job log is not guaranteed to exist, i need to stick with showing the reliable information on the Job Details view.
If i would plan to show the nodes on the job history page, i would most likely introduce one more level of depth, e.g. you can expand one job to see its branches and then you can expand each branch to see the nodes it did execute.
Would this be what you imagined?
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Hey @emcodem,
Where in the API do you pull queued jobs from? I can get the in progress and history great via the API but when I queue a load of jobs I cannot see them in any of the documented API calls. Is it in a secret non documented API?
Where in the API do you pull queued jobs from? I can get the in progress and history great via the API but when I queue a load of jobs I cannot see them in any of the documented API calls. Is it in a secret non documented API?