Ticket #159 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

drag and drop error

Reported by: Harald.Keller@desy.de Owned by: alamaison
Priority: critical (affects core workflow) Milestone: 0.9.x Bug sprint
Component: backend Version: 0.6.0
Keywords: Cc:

Description

I tried to copy a file between 2 Explorer windows from a Windows 7 to a Swish session on a Solaris host by drag and drop. Swish opens a new window with the error message: "An error occurred while transferring files: %1 could not be found".

Attachments

01_copy_drag_drop.png Download (609.2 KB) - added by Harald.Keller@desy.de 6 years ago.
drag & drop from W7 to Unix
02_copy_drag_drop_error.png Download (25.6 KB) - added by Harald.Keller@desy.de 6 years ago.
resulting error message

Change History

Changed 6 years ago by Harald.Keller@desy.de

drag & drop from W7 to Unix

Changed 6 years ago by Harald.Keller@desy.de

resulting error message

comment:1 Changed 6 years ago by alamaison

  • Priority changed from blocker (cannot release, e.g. data loss) to critical (affects core workflow)
  • Status changed from new to accepted
  • Component changed from authentication to backend
  • Milestone set to 0.6.1 Bug sprint

Yuk. What a completely useless error message. It gives us no information at all to start diagnosing the problem. I though we'd got rid of the last of these error dialogues but apparently not (also #107).

So finding a solution to this is going to have to happen in stages, the first of which is to track down the code that reports this error and get it to give more useful details.

Please bear with us. Our day jobs are taking up all our time at moment.

comment:2 Changed 5 years ago by alamaison

Finally we've made  a new release (v0.6.1). This one displays more detailed information when there's an error so should help us track down the source of this bug.

Please reply on this ticket with how you get on.

comment:3 Changed 5 years ago by alamaison

  • Milestone changed from 0.6.x Bug sprint to 0.7.x Bug sprint

Did the latest releases give you any more information when you encounter this error?

comment:4 Changed 5 years ago by alamaison

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.