Task #10839 (closed)
Opened 11 years ago
Closed 11 years ago
Bug: MIF delete 'Constraint Violation'
Reported by: | wmoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 5.0.0-beta1 |
Component: | Services | Version: | n.a. |
Keywords: | FS | Cc: | fs@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | FS Demo 4.3 |
Description
Having imported zeiss-lsm-martin/051215-j-tf.mdb I get 2 images in one fileset. If I try to delete these (using current develop merged build (see below) I don't get an error, but only 1 image is deleted and printing: print handle.getResponse() I see:
object #0 (::omero::cmd::DoAllRsp) { responses = { [0] = object #1 (::omero::cmd::DeleteRsp) { warning = ConstraintViolation: fkfilter_transmittancerange_transmittancerange ...
merge branch:
* 199560c (develop-latest) Merge branch 'chgrp-java-tests' into develop-latest |\ | * 3083105 (joshmoore/chgrp-java-tests, chgrp-java-tests) Check delete after chgrp change | * 220da72 Restrict chgrp of filesets and return constraints (See #10776) * | 5f041c8 (snoopy/merge/develop/latest) merge develop -D org -I include -E exclude * | 778e54e merge develop -D org -I include -E exclude: PR 1132 (Repository API)
Change History (6)
comment:1 Changed 11 years ago by wmoore
- Priority changed from critical to minor
comment:2 Changed 11 years ago by jamoore
- Owner changed from jmoore to jamoore
- Sprint changed from FS demo 4.x to FS demo 4.1
comment:3 Changed 11 years ago by jamoore
- Owner jamoore deleted
- Priority changed from minor to major
- Sprint changed from FS demo 4.1 to FS demo 4.2
Open bug which needs to be looked at. Removing my name in case anyone else wants to pick it up.
comment:4 Changed 11 years ago by jburel
- Sprint changed from FS demo 4.2 to FS Demo 4.3
Moved from sprint FS demo 4.2
comment:5 Changed 11 years ago by bpindelski
Tested with build 297 of OMERO-merge-develop on gretzky. The two images from 051215-j-tf.mdb are indeed identified as a single MIF and put in the same fileset. Insight applies proper highlighting. With the current code, trying to delete just a single MIF element brings up a dialog stopping the user from doing so. Deleting both images from the fileset succeeds.
comment:6 Changed 11 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
Closing since Blazej is no longer seeing the error. We can re-test once #11017 is closed.
I now realise that the failure to delete the 2nd image is due to the 'delete by fileset' logic in the Blitz Gateway where we assume that it's only necessary to delete a fileset to delete all the images.
This has now been removed (PR coming soon).
So, this is now just a minor ticket (if the ConstraintViolation? is a concern, otherwise this can be closed.