Not 100% sure but throwing a guess out there I think this name is
being reset by scripts/set_metadata.py at the very end of the job
using files metadata files produced by metadata infrastructure. Job
runners take commands build up by tools and turn them into full
commands for executing using lib/galaxy/jobs/command_factory part of
this process appends metadata commands and building metadata files
used by the process. To accomplish this command_factory delegates off
to lib/galaxy/jobs:JobWrapper.set_external_metadata which in turn
delegates to lib/galaxy/datatypes/metadata:JobExternalOutputMetadataWrapper.

Hope this helps.

-John

On Thu, Apr 10, 2014 at 5:08 PM,  <neil.burd...@csiro.au> wrote:
> Thanks for the help John. I am using a slightly older version of Galaxy. 
> However, I was hoping that the change of colour may help me understand the 
> name change in the history.
>
> For example when you upload a file i.e. test.txt, "test.txt" appears in the 
> history. However, if you want the history text to say something like 
> "uploaded file test.txt", then you can modify the method "new_history_upload" 
> in ~/lib/galaxy/tools/actions/upload_common.py to update the text before 
> calling "trans.app.model.HistoryDatasetAssociation" . This works as you can 
> see this string when the file is being uploaded, however, when the file is 
> uploaded and the history turns to green the history test says "test.txt" 
> again. Do you have any idea where this may be set in the code?
>
> Thanks again
> Neil
> ________________________________________
> From: John Chilton [jmchil...@gmail.com]
> Sent: Thursday, April 10, 2014 11:39 PM
> To: Burdett, Neil (CCI, Herston - RBWH)
> Cc: galaxy-dev@lists.bx.psu.edu
> Subject: Re: [galaxy-dev] understanding change of colours in history
>
> This is tricky and has changed in the last few releases. If you have
> are developing against the latest revision of galaxy-central this is
> all handled via Backbone MVC code. In particular checkout the render
> method of static/scripts/mvc/dataset/hda-base.js about 100 lines down.
> The class of each of these HDA (history dataset) bodies is set based
> on the state fetched from the server:
>
>             this.$el.empty()
>                 .attr( 'class', view.className ).addClass( 'state-' +
> view.model.get( 'state' ) )
>                 .append( $newRender.children() );
>
> The visual properties of this class are described by CSS (in
> static/style/blue/base.css which I think is actually a derived file
> based on this LESS file static/style/src/less/history.less).
> https://wiki.galaxyproject.org/Develop/CSS.
>
> Hope this helps.
>
> -John
>
> On Wed, Apr 9, 2014 at 11:44 PM,  <neil.burd...@csiro.au> wrote:
>> Hi,
>>
>>     Can someone point me in the direction of where the code in Galaxy is
>> called to change the history background for example when a job changes from
>> Yellow to red on error,  or yellow to green on success. I've been going
>> around in circles now trying to figure out, how this is implemented and how
>> the labels are updated on the history.
>>
>>
>>
>> Also, If I change history_common.mako file and I restart the system my
>> changes aren't seen (i.e. add a new icon if the system goes into error)
>>
>>
>>
>> Thanks for any insight
>>
>>
>>
>> Neil
>>
>>
>>
>>
>> ___________________________________________________________
>> 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/
>>
>> To search Galaxy mailing lists use the unified search at:
>>   http://galaxyproject.org/search/mailinglists/

___________________________________________________________
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/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to