cached build files failing to update

[KadenAgrey]

Describe the bug
BUILD files are cached and not updated for subsequent runs of ./pants tailor :: even after edits have been made.

Pants version
2.14.0

OS
Linux (using WSL on windows machine)

Additional info
Steps in case above is unclear,

1. Introduce error to a BUILD file as example -> add line my_error
2. run ./pants tailor :: (will cause error)
   Name 'my_error' is not defined.
3. Remove offending line and rerun ./pants tailor :: (same error message, expected no error)
4. Disable or enable some backend package (e.g., pants.backend.build_files.fmt.black) and rerun ./pants tailor :: (now succeeds)

[KadenAgrey]

I've realized the issue occurs whether pants.backend.build_files.fmt.black is enabled or not. Simply enabling/disabling something in the backend_packages list forces pants to refresh the BUILD files, otherwise the files are not read in, even when I've made changes.

[jsirois]

Pants does not work on Windows generally, it only works when run completely from a WSL vm. The repo must reside inside the VM and not be accessed via /mnt/<Windows drive>. Does this describe your issue?

[KadenAgrey]

Yes this describes my problem, the bash is navigated through /mnt/... and commands run from there.

This is surprising. Should the Getting Started docs be updated with a disclaimer to avoid confusion around this? They imply pants should work in general through either WSL bash or power shell via the WSL command.

[jsirois]

Probably, yes. Are you willing to take a crack at that doc update?: https://github.com/pantsbuild/pants/blob/main/docs/markdown/Getting%20Started/getting-started/prerequisites.md

[KadenAgrey]

Sure, I'll take a look tonight.

Thanks for the help!

[KadenAgrey]

Hmm, do you prefer I use the "suggest edits" feature on the website directly or go through github?

[jsirois]

GitHub please.