add API endpoint to create TS repository

Develop

Updates to take advantage of galaxyproject#229 infrastructure

Add a library_data input test case and small fix.

add some trello card links to release notes

update

Tweak a few indentations to avoid kicking toplevel parameters into se…

Merge Reports_homepage against latest dev.

Collect error messages (which fixes the current travis build), some other cleanup for sanity.

Remove trailing whitespace

Remove deprecated datatype stuff

Adjustments to sanitize_whitelist reloading.

Minor tweaks to i18n work

More general safe_walk function, handles symlinks loops

Conditional galaxycloudrunner

Release 19.01 updates

Fix test tool label and tool xsd

Use a base URI set in config for Custos Authnz backend.

get latest from dev

Release 19.09

fix crash when no input selected

1. Remove `item` instance attribute: it's not used and is meaningless.
2. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
3. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
4. Simplify mapping test: just use the constructor.

1. Remove `item` instance attribute: it's not used and is meaningless.
2. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
3. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
4. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

1. Remove id parameter from constructor (this is created by the db).
2. Remove `item` instance attribute: it's not used and is meaningless.
3. Make user and item parameters in the constructor required: a rating
   cannot exist without a rater or the item being rated.
4. For the same reason as in #2, make the `set_item()` method private
   and only call it from the constructor.
5. Simplify mapping test: just use the constructor.

Reason: late evaluation of arguments causes errors in mypy;
also this seems to be the more common (as per SA docs) and more readable
method compared to lambdas.

Downside #1: a typo in the string value won't be caught by lint tools.
Downside #2: if there's a sufficiently complex statement, it will be
hard to read if it's all on one line;

primaryjoin = "and_(HistoryDatasetAssociation.history_id == History.id, not_(HistoryDatasetAssociation.deleted), HistoryDatasetAssociation.visible)"

splitting across lines will require surrounding each line with quotes:

primaryjoin = (
   "and_("
   "HistoryDatasetAssociation.history_id == History.id,"
   "not_(HistoryDatasetAssociation.deleted),"
   "HistoryDatasetAssociation.visible,"
    ")"
)

Still, I think it's better than the alternative (lambda + multiple type-ignores
after each line:

primaryjoin = lambda(
   and_(
        HistoryDatasetAssociation.history_id == History.id,  # type:ignore[has-type, arg-type]
        not_(HistoryDatasetAssociation.deleted),  # type:ignore[has-type, arg-type]
        HistoryDatasetAssociation.visible,  # type:ignore[has-type, arg-type]
    )
)

…s-in-map.html

Use CORS proxies for map view