-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
Add an intrinsic for capturing Snapshots from absolute paths #10842
Comments
#10870 describes a method for making mutable caches remote-friendly. In that issue, it currently describes placing a I think that using polling (or the In summary, I think that you've described a capability which could be extended to make the existing mutable cache feature remote-friendly without upstream support, and is I think better more generally useful than #10870. I would also possibly add #10864 to the list of issues this could fix then -- while parenting the MyPy daemon would solve the local execution case, we could also keep track of the MyPy cache directory to make it remote-friendly. |
Both our existing pyenv scraping and the upcoming ASDF integration at #12028 should be using this API, but aren't. |
This is likely related to #16800, in service of #13682. In the context of the work on #13682, the intrinsic described on this ticket would be environment-specific: i.e., when in a |
There are a few usecases for "absolute" file watching+capturing: #10769, #10360, #10837, etc. A likely end-user API would be to add
PathGlobsAndRoot->(Paths|Digest)
intrinsics.Currently Pants' file watching+capturing intrinsics (
PathGlobs->(Paths|Digest)
) operate relative to the buildroot, for two reasons:The second point is now somewhat historical: since we switched to the
notify
crate, we can more easily watch more locations. But OSX still places bounds on how many locations you might reasonably watch (see), and so it's possible that:The paths that would be explored via #10769 in particular will generally involve chains of symlinks:
PathGlobs
expansion is aware of those symlinks (and additionally tries to traverse their parents...), and the result would be watches installed in various places throughout/etc
,/usr
, and ... etc. It's possible that the total number of watches would be small enough that this would be a non-issue though.The text was updated successfully, but these errors were encountered: