Skip to content

Auto require not found by extra specifier search #494

Closed

Description

@xdelaruelle

On 5.3.0, when a module defines a require on itself, when this requirement is searched the module is omitted from result:

$ cat /path/to/modulefiles/bar/1.0
#%Module
module load bar/1.0
$ module use /path/to/modulefiles
$ module avail require:bar/1.0
$

bar/1.0 should be returned by module avail in the above example.

This is not a real world use case (a module should not require itself) but it demonstrates an issue in the extra specifier search mechanism.

Activity

  1. added this to the 5.3.1 milestone on May 31, 2023
  2. xdelaruelle commented on May 31, 2023

    @xdelaruelle
    CollaboratorAuthor

    bar/1.0 module is skipped as it corresponds to the requirement search query.

    This is a bug due to late state initialization: always_read_full_file is currently set after parsing of search query. As a result when bar/1.0 is resolved during search query parse it is not found (readModuleContent fails due to uninitialized state)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions