Skip to content

Releases: galaxyproject/total-perspective-vortex

v3.2.1

Choose a tag to compare

@nuwang nuwang released this 13 Apr 14:57
5000291

What's Changed

  • Replace deprecated pydantic class Config with ConfigDict by @mvdbeek in #191

Full Changelog: v3.2.0...v3.2.1

v3.2.0

Choose a tag to compare

@nuwang nuwang released this 14 Mar 09:16
07ac684

Release Highlights

  • When using multiple configs, you can now dump your merged config using the tpv dump command. docs
  • The tpv dry-run command now has a --explain flag that provides a detailed trace of how TPV arrived at a particular scheduling decision. docs
  • Special tool_type tags are automatically injected to make it easier to schedule tools. For example, user-defined tools are automatically rejected from all destinations unless specifically allowed. docs

What's Changed

New Contributors

Full Changelog: v3.1.3...v3.2.0

v3.1.3

Choose a tag to compare

@nuwang nuwang released this 05 Dec 05:29

What's Changed

  • Bump setuptools minimum version to 77.0.0 by @nsoranzo in #178
  • Fix how inheritance chains are handled between multiple config files by @nuwang in #180

New Contributors

Full Changelog: v3.1.2...v3.1.3

v3.1.2

Choose a tag to compare

@nuwang nuwang released this 23 Oct 17:04

What's Changed

Full Changelog: v3.1.1...v3.1.2

v3.1.1

Choose a tag to compare

@nuwang nuwang released this 07 Oct 04:51

What's Changed

  • Match TPVConfig model, return list, not set of strings by @mvdbeek in #170
  • Allow floats in GPU related fields by @mvdbeek in #173
  • Fix comments under tools: key by @mvdbeek in #171

Full Changelog: v3.1.0...v3.1.1

v3.1.0

Choose a tag to compare

@nuwang nuwang released this 30 Sep 14:18

Release Highlights

  • TPV now automatically injects resource requirements specified in the tool's resource requirements section. This applies to all tools, including user-defined tools.

What's Changed

  • Remove the duplicated docs section by @martenson in #164
  • Remove pipe synthax only available from py3.10 by @nagoue in #165
  • Implement basic version of resource requirements by @mvdbeek in #166

New Contributors

Full Changelog: v3.0.1...v3.1.0

v3.0.1

Choose a tag to compare

@nuwang nuwang released this 07 Aug 12:17

What's Changed

  • Fix jinja template missed in packaging step by @nuwang in #162

Full Changelog: v3.0.0...v3.0.1

v3.0.0

Choose a tag to compare

@nuwang nuwang released this 24 Jul 15:42

Breaking Changes

  • A new version of the TPV shared database has been released. Therefore, please update your links to point to https://gxy.io/tpv/db-latest.yml if you want to preserve the older behaviour of using the latest version. Otherwise, https://gxy.io/tpv/db.yml is now an alias for https://gxy.io/tpv/db-v1.yml, and will no longer be updated. Alternatively, you can use https://gxy.io/tpv/db-v2.yml, if you want to pin to the latest major version. We recommend this latter option for most users, as you can control the major version upgrade cycle. Refer to release notes in the TPV shared database for more information.
  • TPV v3.0.0 also has some breaking changes for edge cases, although most users will be unaffected.
  • If you programmatically access TPV tags in python code, some breaking changes were made. Specifically, the TagSetManager class has been deprecated and the Tag class - simplified. Users using only yaml scheduling tags are unaffected. To create a a new Tag instance programmatically, a name is no longer required. Simply use pulsar_tag = Tag("mytag", TagType.REQUIRE). The TagSetManager class has been replaced with the SchedulingTags class. Use SchedulingTags(require=[pulsar_tag] to replace. See here for additional context.
  • These changes can be caught with mypy based type-checking support in the upgraded linter. Type-check failures are treated as linter warnings, not errors, and therefore, you must use the tpv -vv lint flag to view type-checking issues. The type-checker will warn you if you attempt to use any non-existent classes.

Release highlights

  • The TPV linter now supports type-checking of Python code embedded in your yaml files, so that potential errors can be detected prior to deployment. Type-check failures are treated as linter warnings, not errors, and therefore, you must use the tpv -vv lint flag to view type-checking issues. Internally, TPV uses mypy with strict type-checking support, and we recommend linting all your existing files and correcting any type related errors prior to deploying TPV 3.0.0 in production.
  • The TPV linter also warns you if any unrecognised fields are seen in your yaml config. Use tpv -vv lint to display these warnings. You can also individually silence these errors by adding the comment noqa: T104.
  • TPV now has a well-defined Pydantic schema and uses this schema internally for parsing yaml config files. A future release will add support for displaying this YAML schema.
  • The dryrun command has been enhanced with support for specifying roles and history-tags.
  • Numerous bug fixes and internal enhancements.

What's Changed

New Contributors

Full Changelog: v2.5.0...v3.0.0

v2.5.0

Choose a tag to compare

@nuwang nuwang released this 17 Dec 16:13

What's Changed

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

v2.4.0

Choose a tag to compare

@nuwang nuwang released this 29 Apr 06:33

What's Changed

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