You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
On 5.3.0, when a module defines a require on itself, when this requirement is searched the module is omitted from result:
bar/1.0
should be returned bymodule 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.
The text was updated successfully, but these errors were encountered: