Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11045 (closed)

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

Bug: can't move plates

Reported by: mtbcarroll Owned by: jamoore
Priority: blocker Milestone: 5.0.0-beta1
Component: OmeroFs Version: n.a.
Keywords: n.a. Cc: ux@…, fs@…,
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: FS demo 4.4

Description (last modified by mtbcarroll)

In testing develop merge build 297 on adhoc-test-02 as user-3, in Insight I picked a couple of plates I'd imported into read-only-1 and tried moving them into read-annotate-1 and got "Unable to transfer data".

Attachments (3)

Unable to transfer data in Insight mssg.png (14.9 KB) - added by pwalczysko 11 years ago.
double-jstack during failed move.txt (36.6 KB) - added by pwalczysko 11 years ago.
from the blitz log on Gretzky.txt (10.2 KB) - added by pwalczysko 11 years ago.

Download all attachments as: .zip

Change History (14)

comment:1 Changed 11 years ago by mtbcarroll

  • Description modified (diff)
  • Priority changed from major to blocker

comment:2 Changed 11 years ago by mtbcarroll

  • Description modified (diff)

(bah, restoring description, confused by it being below comment field)

comment:3 Changed 11 years ago by pwalczysko

  • Sprint set to FS demo 4.4

comment:4 Changed 11 years ago by pwalczysko

This still does not work. Today's build on Gretzky, OMERO.insight-5.0.0-alpha4-366-ec8585a-dirty-ice33-b302-mac.
Workflow:

  • user-6, private-1 on Gretzky
  • Import data_repo/public/images/HCS/incell/ -> the first plate in the folder
  • try to Move it to read-annotate-1
  • Move starts okay, got a first window encouraging me to create a screen in the target group - did not do so
  • went on with the move
  • within 30 sec, the activities entry changes from spinner to red cross - unable to transfer the data (see screenshot below)
  • after refresh, the plate is there intact in the original group
  • absolutely no entries found in Insight log, neither is there any error produced by Insight
  • will try to do a jstack when the move is running

Changed 11 years ago by pwalczysko

comment:5 Changed 11 years ago by pwalczysko

  • Cc fs@… jrswedlow added

Changed 11 years ago by pwalczysko

comment:6 Changed 11 years ago by pwalczysko

  • Cc jrswedlow removed

comment:7 Changed 11 years ago by pwalczysko

Attached a jstack of Insight - ran it twice while the Move was in progress (it ended up failing again, as before).

comment:8 Changed 11 years ago by pwalczysko

Adding lines from the Blitz.log on Gretzky as well - don't know whether this is interesting.

Changed 11 years ago by pwalczysko

comment:9 Changed 11 years ago by jamoore

  • Resolution set to fixed
  • Status changed from new to closed

Commit added to https://github.com/openmicroscopy/openmicroscopy/pull/1256 Please re-open if this re-appears.

comment:10 Changed 11 years ago by jmoore <josh@…>

  • Remaining Time set to 0

(In [99865a91fc892e01fbb9850a4e742e6c13e69e34/ome.git] on branch develop) Order filesets last (Fix #11045, See #11054)

Rather than inject filesets at the first possible location
in the DoAll? requests list, place them after all related
requests.

comment:11 Changed 11 years ago by jmoore <josh@…>

(In [92b69fe02b0a709f5fdd5aa34974ac4132cdd833/ome.git] on branch develop) Add finish() phase to IRequest (See #11045, #11054, etc)

Now that Fileset handling is happening after containers and
images, it's necessary to have a phase hook which checks that
all filesets have been deleted along with the related images.

This amounts to a trigger pre-commit, but that's not provided
by postgresql. Instead, we collect all of the fileset IDs in
the DeleteStep? instances and then check that they have been
removed afterwards. The primary drawback is that this no longer
provides a GraphConstraintERR but rather just a regular ERR.

See #10846

Note: if this requirement is ever removed, the entire finish()
phase could be rolled back. Alternatively, this could replace
the ChgrpValidation? steps.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.71070 sec.)

We're Hiring!