Gwf

Latest version: v1.7.2

Safety actively analyzes 621688 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

1.7.2

=============

Fixed
-----

* Trying to cancel a target that is not running or completed will now *not* fail.
* Documented the Slurm target options ``mail_user`` and ``mail_type``.

Added
-----

* Slurm backend now accepts a ``gres`` target option that maps directly to
Slurm's ``--gres`` flag.

1.7.1

=============

Changed
-------

* The ``clean`` command now asks for confirmation when no targets are
specified. This can be avoided by using the ``--force`` flag.
* The Slurm backend will now get all jobs from ``squeue`` and not only jobs
belonging to the current user. This used to be the default behaviour, but was
unintentionally changed when refactoring the Slurm backend.

Fixed
-----

* The output of the ``cancel`` command is now correct.

1.7.0

=============

This release is the first version of *gwf* to support Python 3.8. We're now
testing on nightly version of Python so that future Python releases should be
supported as soon as they're available.

Added
-----

* Automatically checks for updates on a regular basis. A warning will be shown
when a new version is available. This feature can be disabled with
``gwf config set check_updates no``.
* The Slurm backend will now retry failed operations, e.g. if it fails to get
the state of the queue from Slurm or if submitting a job failed.
* Support for Python 3.8.

Changed
-------

* When running `gwf cancel` without specifying targets, only
submitted/running targets will be cancelled.

Fixed
-----

* Fixed a deadlock in the local backend which caused the workers to freeze.
* Links to examples and ReadTheDocs (we're now hosting the docs ourselves).

1.6.0

=============

This release contains a few large features such as named inputs and outputs
and the introduction of the :class:`Workflow.map` method for easily generating
multiple targets from a template and improving readability.

There are also several minor improvements that contribute to the overall
user experience ranging from speed improvements for the ``logs`` command to
improved debugging output.

The documentation has also been restructured and improved.

Added
-----

* Named inputs and outputs. The ``inputs`` and ``outputs`` arguments to
``Workflow.target`` can now be either a string, list or dictionary. See the
documentation for more details.
* Tutorial now explains what happens if a target fails.
* Documentation now has an official list of *gwf* plugins.
* The ``status`` command now has a ``--summary`` option the summarizes the
status of an entire workflow.
* All input and output paths are now checked for non-printable characters such
as newlines and tabs. This can cause problems that are very hard to find and
fix (e.g. *gwf* reporting that a file is missing even though it seems to be
there). Paths containing such characters now result in an error.

Changed
-------

* The ``logs`` command is now much faster since it no longer builds the entire
graph.
* The target in the ``status`` output is now sorted in creation order, instead
of alphabetically.
* Cleaner output formatting, especially when running with ``-v debug``.
* Improved log messages from scheduler when running with ``-v debug``. The
messages are now more specific and helpful.
* Documentation has been restructured to be more readable and have less
redundant information.

Fixed
-----

* Crash when running ``gwf init`` without an existing configuration file.
* The ``--force`` flag for the ``cancel`` command now actually forces cancellation.
* We now respect the ``--no-color`` flag completely and implement the ``NO_COLOR``
environment variable standard described `here <https://no-color.org/>`_.

1.5.1

=============

Fixed
-----

* Crash when Slurm returns unknown job state (244).

1.5.0

=============

Added
-----

* Users can now run ``gwf init`` to bootstrap a new *gwf* project (c78193).
* Add option to protect output files in a target from being removed when
``gwf clean`` is being run (2f51ed).

Fixed
-----

* Ensure job script end with a newline (239).
* Ignore missing log files when cleaning on run (237).

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.