bug: Erroneous warning messages when using nested folders ("Script not found at name f/... (scripts.rs:1576)")

[codersaur]

Describe the bug

I am seeing (seemingly erroneous) warning messages in my worker container logs with the format "Script not found at name f/folder/subfolder (scripts.rs:1576)". These occur whenever I run a python script which imports another script which is in a subfolder with depth of 2 or more.

E.g.

The actual import appears to work and scripts execute as expected.

To reproduce

1. Create a python script in a nested subfolder. E.g. f/folder/sub_folder/script_name
2. Import this script from a second python script:
   from f.folder.sub_folder.script_name import function_x
3. Execute the second script.
4. Observe warnings in worker container logs (scripts running ok).
   Not found: Script not found at name f/folder/sub_folder (scripts.rs:1576)

Expected behavior

These warning messages seem erroneus as the scripts are imported and run as expected, so they should not appear.

Screenshots

No response

Browser information

No response

Application version

Windmill CE v1.566.1

Additional Context

No response

[rubenfiszel]

It's somewhat normal, it's due to how imports overloading work in python, we have to check if the script exist at every subpath

[codersaur]

It's somewhat normal, it's due to how imports overloading work in python, we have to check if the script exist at every subpath

Ok, but why log it as a warning for every subpath, surely a warning message should only be needed if a script was not found on any path?