Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(jobs/emx2-pyclient): not possible to upload file from within a job #4219

Open
dtroelofsprins opened this issue Sep 13, 2024 · 0 comments · May be fixed by #4335
Open

fix(jobs/emx2-pyclient): not possible to upload file from within a job #4219

dtroelofsprins opened this issue Sep 13, 2024 · 0 comments · May be fixed by #4335
Assignees
Labels
priority Features/bugs that we should not let wait

Comments

@dtroelofsprins
Copy link
Contributor

dtroelofsprins commented Sep 13, 2024

What version of EMX2 are you using (see footer)
v11.8.0

Describe the bug
Running a script to upload files using the emx2-pyclient within the application is not possible, since the progress of file upload is being shown (version 10.109.0). This is due to the fact that the script that calls the upload file is running, and the upload file process is creating a new job/task which waits for the other job to be finished, which will not happen as long as the 'main' script is running which is the case as it waits for the file upload to be finished, so the two are blocking each other.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://emx2.dev.molgenis.org' and login
  2. Check if the ScriptWithFileUpload schema exists, if so delete it
  3. GoTo SYSTEM schema => scripts
  4. Start the scriptIssue4219 script
  5. GoTo the jobs overview and see that the scriptTask job is running and the PetStoreLoader is waiting.

Expected behavior
It should be possible to do a file upload from within a script using the existing functionalities => so actually run jobs in parallel.
Some thoughts on this:

  • Jobs could run regardless of the status of any of the other jobs
  • Mark jobs started from another job/task as sub-jobs and makes these run parallel with the main job

I think I would prefer something like 'subjobs', making jobs run independent of each other might be a bit 'too' much and can in some cases do unwanted things.

Screenshots
If applicable, add screenshots to help explain your problem.

@nakikkertumcg nakikkertumcg added the priority Features/bugs that we should not let wait label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority Features/bugs that we should not let wait
Projects
None yet
4 participants