Re: [galaxy-dev] Conditional parameters regression: KeyError: '__current_case__'
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.c...@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 d...@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 ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Conditional parameters regression: KeyError: '__current_case__'
On Thu, Jun 16, 2011 at 2:23 PM, Daniel Blankenberg d...@bx.psu.edu wrote: Hi Peter, If you were curious it was fixed about 7 hours later in 5681:0886ed0a8c9f Thanks for using Galaxy, Dan Thanks - I know this kind of unexpected breakage is inevitable sometimes, but would recommend tool developers in general run with galaxy-dist or galaxy-central? Peter ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Conditional parameters regression: KeyError: '__current_case__'
Hi Peter, Production servers, or any server where you have users, should always track Galaxy-dist. Galaxy-central is a development repo (you get access to the latest and greatest, but also should Expect more bugs to pop up at any given time), from the Galaxy-central header on bitbucket: Main development repository for Galaxy. Active development happens here, and this repository is thus intended for those working on Galaxy development. See http://bitbucket.org/galaxy/galaxy-dist/ for a more stable repository intended for end-users. Its really a personal choice that each (tool) developer will have to make based upon whether they consider themselves to be a pure end-user (just adding tools or running a Galaxy server) who only wants to work on a stable branch; or if they want to contribute to Core development or gain early access to development features (and bugs). I would say that finalized tools and e.g. tools submitted to the tool shed should be vetted against galaxy-dist. Thanks for using Galaxy, Dan On Jun 16, 2011, at 9:26 AM, Peter Cock wrote: On Thu, Jun 16, 2011 at 2:23 PM, Daniel Blankenberg d...@bx.psu.edu wrote: Hi Peter, If you were curious it was fixed about 7 hours later in 5681:0886ed0a8c9f Thanks for using Galaxy, Dan Thanks - I know this kind of unexpected breakage is inevitable sometimes, but would recommend tool developers in general run with galaxy-dist or galaxy-central? Peter ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Conditional parameters regression: KeyError: '__current_case__'
On Thu, Jun 16, 2011 at 3:01 PM, Daniel Blankenberg d...@bx.psu.edu wrote: Hi Peter, Production servers, or any server where you have users, should always track Galaxy-dist. Yes, that's very clear. Galaxy-central is a development repo (you get access to the latest and greatest, but also should Expect more bugs to pop up at any given time), from the Galaxy-central header on bitbucket: Main development repository for Galaxy. Active development happens here, and this repository is thus intended for those working on Galaxy development. See http://bitbucket.org/galaxy/galaxy-dist/ for a more stable repository intended for end-users. Its really a personal choice that each (tool) developer will have to make based upon whether they consider themselves to be a pure end-user (just adding tools or running a Galaxy server) who only wants to work on a stable branch; or if they want to contribute to Core development or gain early access to development features (and bugs). I would say that finalized tools and e.g. tools submitted to the tool shed should be vetted against galaxy-dist. OK, that's basically how I've been working - quite often during tool development I've hit bugs in Galaxy and wanted to make branches with fixes etc, or needed new functionality for a tool that isn't yet in galaxy-dist. Peter ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
