Skip to content

Commit

Permalink
doc: desc. in NEWS report and conflict mngt changes
Browse files Browse the repository at this point in the history
  • Loading branch information
xdelaruelle committed Jan 21, 2024
1 parent e6d830c commit 835df2e
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 3 deletions.
1 change: 1 addition & 0 deletions .hunspell.en.dic
Original file line number Diff line number Diff line change
Expand Up @@ -567,6 +567,7 @@ mksh
mlprof
mlstatus
mmap
mngt
modEq
modEqStatic
modStartNb
Expand Down
17 changes: 14 additions & 3 deletions NEWS.rst
Original file line number Diff line number Diff line change
Expand Up @@ -125,11 +125,22 @@ Modules 5.4.0 (not yet released)
from a modulefile.
* No *Switching* block message report when :mfcmd:`module switch<module>`
command is run from a modulefile.
* Report all error messages locally under *Loading* or *Unloading* block
message rather reporting some of them under the block message of the main
action.
* Report all error and warning messages locally under *Loading* or *Unloading*
block message rather reporting some of them under the block message of the
main action. These errors and warnings are thus reported where they occur.
* Report switched-on load failure as error rather warning.
* Report switched-on module locating or access issues only once.
* Report conflict error message when it occurs rather than after modulefile
evaluation.
* Update conflict error message to report all conflicting modules name and
version rather conflict module specification.
* Fix conflict error check to avoid reporting both *unloading conflict failed*
and *conflict is loading* messages.
* Raise an error and stop modulefile evaluation when :mfcmd:`module
switch<module>` command fails unless if :option:`--force` option is set.
* When a *useless requirement unload* fails, do not increase error count as
this failure is reported as a warning and main unload process is not
affected.


.. _5.3 release notes:
Expand Down

0 comments on commit 835df2e

Please sign in to comment.