seek icon indicating copy to clipboard operation
seek copied to clipboard

Batch submission fails on extraction and breaks file

Open Jake3784 opened this issue 1 year ago • 8 comments

Describe the bug Recently when creating samples using the "new batch submission" feature, the data file gets stuck in queue for extracting the samples indefinitely. Besides not creating the samples, this also leads to an inability to manage or edit the data file as opening its page when signed in redirects to an error message (the data file page can be viewed when not signed in & the file may be downloaded).

To Reproduce ** I have not been able to recognize a difference between the instances where this error occurs and the instances where the submission works perfectly as intended ***

Steps to reproduce the behavior:

  1. Go to 'Create'
  2. Click on 'Sample'
  3. Scroll down to the specific sample type
  4. Click on 'New Batch Submission'
  5. Click on 'Data file uploader' (Step 3)
  6. Chose the file to be uploaded (have been using local)
  7. Finish uploading the file
  8. Open the page of the data file
  9. Click on 'Extract Samples'
  10. If the error occurs, the file will indefinitely be in queue for extraction

Expected behavior After a period of time there should be an option to review samples to be extracted and then to finalize extraction.

Screenshots Data file stuck in queue: fairdomQueue

Error page that is thrown when trying to access data file [only for the uploader when signed in (previous page can no longer be seen)] fairdomErrorPage

Data File Page for someone not signed in fairdomPublicPage

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser Microsoft Edge
  • Version 106.0.1370.47

Additional context There have been instances of batch submission working after this problem was first found.

Jake3784 avatar Oct 18 '22 17:10 Jake3784

this also leads to an inability to manage or edit the data file as opening its page when signed in redirects to an error message

I've corrected this now. Can you try extracting the samples again?

fbacall avatar Oct 18 '22 17:10 fbacall

Sure, I'm trying to extract the samples now. Currently, I'm getting the message 'Sample extraction: Active'. It has been running for a couple minutes now. I'll send an update if it doesn't complete soon.

Jake3784 avatar Oct 18 '22 17:10 Jake3784

Yeah, it seems it is stuck on 'Sample extraction: Active'. For reference, there are 32 samples in the batch submission which in my experience is usually quite fast to extract.

Jake3784 avatar Oct 18 '22 18:10 Jake3784

Hi @Jake3784 I've been looking into this problem. I'm still not quite sure what went wrong. The extracted samples get put into a temporary file, but in this case it ended up as a blank file. I'm still trying to track down why that might have happened and prevent it leaving a blank file in the future if things go wrong.

However, whilst investigating I reproduced the steps the job performs that runs, and it created the file of the correct size. So you should be able to proceed with the next steps of Reviewing and Storing the extracted samples.

In the meantime I will try and figure out what happened. From above it sounds like it happened twice and wasn't down to some freak event.

stuzart avatar Oct 19 '22 14:10 stuzart

Thank you so much for your help. I was able to go ahead and finish extracting samples for two of the three instances where this problem arose. The final instance still doesn't work but the problem looks a little different. I'm able to select 'Extract Samples' and there is a message that 'Sample Extraction: Queued' but the page no longer gets stuck on this message. Instead, the message disappears after a few seconds and the process is seemingly terminated.

Jake3784 avatar Oct 19 '22 17:10 Jake3784

It sounds like the last case is encountering the same problem as before. I deployed a very small partial fix, to avoid it creating the blank file that led to page crashing and prevents the ability to retry. This was just a quick fix, and I'm making more changes to report that something went wrong and also record the exception and report it to us. If it is urgent I can force the 3rd datafile onto the next step, otherwise I will use it to try and reproduce the problem. I'd strange because I've so far not been able to reproduce.

stuzart avatar Oct 20 '22 09:10 stuzart

Nope, it's not particularly urgent. Feel free to continue using it as a test case.

Jake3784 avatar Oct 20 '22 13:10 Jake3784

The underlying problem should be fixed now, so you should be able to extract your other samples.

I'm leaving the issue open, as I still want to add some further changes that improves the error reporting both to us and the user

stuzart avatar Oct 21 '22 16:10 stuzart