Trackster: update jQuery selector so that all tool inputs are updated on change rather only <input> elements. Pack script.
Automated merge of next-stable to default
Metrics: allow time to be passed into fluent_log.py, log
Remove debugging statements
merge next-stable
When submiting bug reports disable submit buttons while form is being submitted. When submiting bug report to Biostar, have user confirm that they are posting to a public forum.
merge next-stable
fix tab spaces in javascript
merge next-stable
The basis of this change set is to provide some fixes to certain Tool Shed functions for supporting changing HTTP protocols over time (ie.e, https <-> http).  In doing this, I've refactored several functions and moved most of the Tool Shed <-> Galaxy URL munging functions to the Tool Shed's common_util.py module.  Ive renamed the munging functions to clarify what each of them does.  Several duplicate functions have been eliminated from the code as well.
Genome data provider: (a) handle regions with no mapped reads and (b) clean up trailing whitespace.
SAM/BAM data provider: fix bug and streamline code to support both genomes with reference data and those without.
Automated merge of next-stable to default.
Metrics API: allow posting of metrics sending to app.trace_logger.log if available
Improve handling of invalid/expired GenomeSpace tokens in GenomeSpace export tool.
Charts: Allow switching chart types without reset, fix resizing
Fix in the tool shed install and test framework for a recently relocated function.
Record history content type with output of history contents API.

Downstream in dataset collections branch this isn't just dataset, including this will allow clients to distinguish between different kinds of content.
Refactor backbone models to allow different kinds of history contents.

In particular, add a new backbone parent model (HistoryContent) refactored out of HistoryDatasetAssociation. This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API.

There are likely better ways to share common functionality between a dataset and a dataset collection contents - more JS savy developers should feel free to refactor into smaller mixins for instance. For now HistoryContent is just composed of the overlap in functionality between dataset and collection representations downstream and is an quick and dirty way to share said functionality.
Refactor backbone views to allow different kinds of history contents.

This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API. Same comment as previous changeset applies - this is a potentially crude way to share duplicated functionality and a better design would be most welcome.