v2.5.0

What's Changed

• Fix tests by @nuwang in #138
• Add lint warning for tools with cores and no mem by @natefoo in #140

Full Changelog: v2.4.0...v2.5.0

v2.4.0

What's Changed

• Update shared db short link by @nuwang in #128
• Improved docs by @nuwang in #126
• Add optional slow tests by @nuwang in #66

Full Changelog: v2.3.3...v2.4.0

v2.3.3

What's Changed

• Fix get_dataset_size for datasets with null file_size column by @mvdbeek in #116
• Add contributing doc and update readme by @afgane in #122
• Add readthedocs configuration by @nuwang in #121
• Add to to_dict functions to Destination and TagSetManager classes by @pauldg in #119
• Add a helper to get the object store ids and the datasets size for every dataset in a job by @sanjaysrikakulam in #125

New Contributors

• @afgane made their first contribution in #122
• @pauldg made their first contribution in #119

Full Changelog: v2.3.2...v2.3.3

v2.3.2

What's Changed

• Fix E721 for type comparison by @mvdbeek in #113
• Fix legacy version parsing by using Galaxy's version parsing if available by @bgruening in #112

New Contributors

• @mvdbeek made their first contribution in #113

Full Changelog: v2.3.1...v2.3.2

v2.3.1

What's Changed

• Add two tests around destination inheritance (one fails) + fix by @cat-bro, @nuwang in #110

Full Changelog: v2.3.0...v2.3.1

v2.3.0

Highlights

Two significant bugs with how TPV handles default inheritance and destination clamping were reported by @cat-bro. Both of these bugs have been fixed in this release.

In the first case, if the TPV shared database (or other remote file) defined a default, and a local default was also defined, the local default would apply even if the remote tool explicitly overrides the relevant values. Local defaults should only apply if the remote tool does not define any values, and therefore, this could result in unexpected behaviour or improper overriding. You may need to check your config for cases where the remote defines a value, and a local default also affects that same value.

In the second issue, if resources are clamped at a destination, the natural expectation would be that the cores/mem/gpu values defined at the destination will affect all expressions. However, this was not the case, and only expressions defined at the destination were affected by clamping. This has now been fixed. See issue #106 for more details.

What's Changed

• fix resubmission tests by @bernt-matthias in #78
• Fix issue with how default inheritance is applied to multiple files by @nuwang in #105
• Fix evaluation to support resource clamping by @nuwang in #107

Full Changelog: v2.2.4...v2.3.0

v2.2.4

What's Changed

• When regex compilation fails, log what was attempting to be compiled by @natefoo in #97
• add helper for tool version equality comparison by @sanjaysrikakulam in #98
• Match cores, mem and gpus whenever they are defined by @kysrpex in #99
• Modify linter to flag regex errors by @nuwang in #102
• Create dependabot.yml by @nuwang in #103

New Contributors

• @sanjaysrikakulam made their first contribution in #98

Full Changelog: v2.2.3...v2.2.4

v2.2.3

What's Changed

• Add id to mock_galaxy.User by @kysrpex in #96
• Fix dry run tool version by @cat-bro in #94

New Contributors

• @kysrpex made their first contribution in #96

Full Changelog: v2.2.2...v2.2.3

v2.2.2

What's Changed

• Fix formatter ordering of inherits field by @nuwang in #90
• Add helpers for tool version comparison by @cat-bro in #91
• Fix dry run user by @cat-bro in #92
• Failing test for pulsar user scenario by @cat-bro and @nuwang in #93

Full Changelog: v2.2.1...v2.2.2

v2.2.1

What's Changed

• If a tool has file size rules, a role rule has no access to a tool's scheduling tags by @cat-bro in #89

Full Changelog: v2.2.0...v2.2.1