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

Delete nifti not working properly #2502

Open
jcomedouteau opened this issue Nov 15, 2024 · 1 comment · May be fixed by #2534
Open

Delete nifti not working properly #2502

jcomedouteau opened this issue Nov 15, 2024 · 1 comment · May be fixed by #2534
Assignees

Comments

@jcomedouteau
Copy link
Collaborator

Two things:

  • When deleting all nifti of a very big study, the request takes too much time. We should do it asynchroneously. (see with @pierrehenri-dauvergne on how to do it)
  • We sometimes encounter the following error:
    "Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [org.shanoir.ng.dataset.model.DatasetExpression#1790168]",
    (example for study id 23 on ofsep quailf)

This may be linked to the fact that we are working with a List and not a Set<>, but I'm not quite sure. Ne need to test it further.

DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 6, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 6, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 6, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 6, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 9, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 9, 2024
DuckflipXYZ added a commit to DuckflipXYZ/shanoir-ng that referenced this issue Dec 9, 2024
@DuckflipXYZ DuckflipXYZ linked a pull request Dec 16, 2024 that will close this issue
@DuckflipXYZ
Copy link
Collaborator

Seems good but keep in mind that I had to talk to Anthony about the server memory issue, after what he gave more resources to the database container (or something like, I'm not sure), it gonna be required on prod too (probably).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants