Closed aurreco-uga closed 2 years ago
this happens hen a user uses a sequence like below: (lots of dashes)
MS------------------------------------------------------------------------------ -------------------------------------------------------------------------------- -------------------------------------------------------------------------WR----- -------------------------------------------------------------------------------- --------ARFTPC------------------------------------------------------------------ -------------------------------------------------------------------------------- --------------------------------------------------------------VASLTVWL---------- -------------------------------NPK-D----------P----NC-FGVRNWW-----RN---NLPE-LQL- -LNPFC-----SFT-IQE---L--------SF------G-----EPH-----MYINY----------------------- ---------------T-----------------------------PT--------DQRMIRL-------A-------GAT -------------------------------------------------------------------------------- ---------------------------E-DE-CEDIMEACITYGMNHA----------------IIERPRTDD--GGDLI ----------------------------NQPAITSFGYTESFMSK-L---EVSPPADIGQRTPEG----
when executing this in the browser (uses a similar query): https://plasmodb.org/plasmo/app/workspace/blast/result/0771a5a0b24643e51742dd5ca8c6de61
the blast program fails execution , and the job is marked as .failed in the workspace (see below).
the client sends a request: https://plasmodb.org/multi-blast/jobs/72d4408d4fe0e69ad2bb0e0fe82762e3 that returns the job as "complete" but the workspace has it as .failed:
/ # ls -la /out/0771a5a0b24643e51742dd5ca8c6de61 total 268 drwxr-xr-x 3 root root 4096 Aug 16 17:57 . drwxr-xr-x 2014 root root 249856 Aug 16 18:10 .. -rw-r--r-- 1 root root 0 Aug 12 14:54 .failed drwxr-xr-x 2 root root 4096 Aug 12 14:55 7178a1ad66c92b19cb42f37068f5899b -rw-r--r-- 1 root root 143 Aug 12 14:54 error.txt -rw-r--r-- 1 root root 0 Aug 12 14:54 log.txt -rw-r--r-- 1 root root 1155 Aug 12 14:54 query.txt -rw-r--r-- 1 root root 320 Aug 12 14:54 report.asn1
tag 1.7.24, but it needs some client work to react to the new errored status
this happens hen a user uses a sequence like below: (lots of dashes)
when executing this in the browser (uses a similar query): https://plasmodb.org/plasmo/app/workspace/blast/result/0771a5a0b24643e51742dd5ca8c6de61
the blast program fails execution , and the job is marked as .failed in the workspace (see below).
the client sends a request: https://plasmodb.org/multi-blast/jobs/72d4408d4fe0e69ad2bb0e0fe82762e3 that returns the job as "complete" but the workspace has it as .failed:
/ # ls -la /out/0771a5a0b24643e51742dd5ca8c6de61 total 268 drwxr-xr-x 3 root root 4096 Aug 16 17:57 . drwxr-xr-x 2014 root root 249856 Aug 16 18:10 .. -rw-r--r-- 1 root root 0 Aug 12 14:54 .failed drwxr-xr-x 2 root root 4096 Aug 12 14:55 7178a1ad66c92b19cb42f37068f5899b -rw-r--r-- 1 root root 143 Aug 12 14:54 error.txt -rw-r--r-- 1 root root 0 Aug 12 14:54 log.txt -rw-r--r-- 1 root root 1155 Aug 12 14:54 query.txt -rw-r--r-- 1 root root 320 Aug 12 14:54 report.asn1