Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto require not found by extra specifier search #494

Closed
xdelaruelle opened this issue May 31, 2023 · 1 comment
Closed

Auto require not found by extra specifier search #494

xdelaruelle opened this issue May 31, 2023 · 1 comment
Labels
Milestone

Comments

@xdelaruelle
Copy link
Member

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.

@xdelaruelle xdelaruelle added this to the 5.3.1 milestone May 31, 2023
@xdelaruelle
Copy link
Member Author

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
Labels
Projects
None yet
Development

No branches or pull requests

1 participant