Hi Peter, If you were curious it was fixed about 7 hours later in 5681:0886ed0a8c9f Thanks for using Galaxy, Dan On Jun 16, 2011, at 4:32 AM, Peter Cock wrote:
On Wed, Jun 15, 2011 at 4:56 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Dan,
I just started work on updating my MIRA wrapper, and fell over a regression present of 6079:5e6254f2b9e3, steps to reproduce on Linux:-
1. Install latest Galaxy 2. Install my MIRA wrapper v0.0.1 from the tool shed (don't need MIRA for this) 3. Run Galaxy 4. Select the MIRA tool 5. Change "Backbones/reference chromosomes?" or "Sanger/Capillary reads?" or "454 reads?" or "Solexa/Illumina reads?" to yes 6. Instead of new file parameter appearing, get a KeyError: '__current_case__' exception (details below).
Shorter example without a 3rd party tool:
1. Install latest Galaxy 2. Run Galaxy 3. Select the "Convert SOLiD output to fastq" tool 4. Change "Is this a mate-pair run?" to yes 5. Instead of new file parameters appearing, get a KeyError: '__current_case__' exception.
By going through recent commits and retesting, I found the commit which caused this regression:
changeset: 6078:894112e0b9d5 user: Daniel Blankenberg <dan@bx.psu.edu> date: Thu Jun 09 11:26:41 2011 -0400 summary: Some fixes for interplay between DataToolParameter, implicit datatype conversion and dynamic select lists. Closes #491.
I guess there are downsides to running my development environment off galaxy-central rather than galaxy-dist ...
Peter
This has been fixed as of 6116:124f8bcea0ff but I didn't bother to work out which change solved it.
Regards,
Peter