Re: [galaxy-dev] Current history via the REST API (or blend4j)

> On May 24, 2016, at 11:14 PM, Carl Eberhard wrote: > > most_recently_used *was* broken - thanks for finding that. Glad I could be of assistance! Just to clarify, the user has to actually *do* something with a history (i.e. add something to the history) for it to be

Re: [galaxy-dev] Current history via the REST API (or blend4j)

most_recently_used *was* broken - thanks for finding that. A pull request going back to the 16.01 release is here: https://github.com/galaxyproject/galaxy/pull/2407 A planning issue for a session API is here: https://github.com/galaxyproject/galaxy/issues/2404 On Tue, May 24, 2016 at 4:16 PM,

Re: [galaxy-dev] Current history via the REST API (or blend4j)

> On May 23, 2016, at 3:34 PM, Carl Eberhard wrote: > > There's a way to get the current history data through a non-api url: > /history/current_history_json That works, but to get the current history for a user I need to set the galaxysession cookie. So it is not

Re: [galaxy-dev] Current history via the REST API (or blend4j)

There's a way to get the current history data through a non-api url: /history/current_history_json ...but, I don't believe those are accessible through any of the bio/blend libraries. Failing the above, is there some way to get the history ID from the UI? You can click the information button