Community
Participate
Working Groups
Sometimes I end up in a state when mini log still shows operations running even if the full view shows no running operations. I'm not sure what the steps are. The only related error in the console is: uncaught exception: No Matching OperationService for location:/../task/id/gB0m6307ABEQAagiAclxwQ http://localhost:8080/orion/operationsTable.js Line 122 which is my fault. Server restart does not help.
This is probably when error occurs while checking the operations status. In your case the operation location was incorrect and no operations service could be matched with it. What can we do about it? I think there are two possible answers: 1. remove the task from the list 2. change the task status to "unknown" Or maybe we should change status to unknown and after some timeout remove task from the list? This may be most reasonable way to do.
It occurred that while fixing another bug I also fixed this one. Now when there is a problem checking the operation status an error is displayed on the screen and also operation is marked as failed.
Created attachment 211312 [details] View of the main page This is how it looks like on the page.
Created attachment 211314 [details] Errors in minilog This is a screenshot of a minilog with failed operations.
I haven't seen the problem for a while. We can mark it fixed and refer the bug mentioned in comment 2.
The bug is Bug 367326. It was fixed in RC1. I'll mark this bug as fixed in RC1 as well.
