https://pantsbuild.org/ logo
Join Slack
Powered by
Is it recommended to run `./pants fmt ::` or to br...
# general
h
Is it recommended to run 
./pants fmt ::
or to break up formatters? e.g. 
isort
+ 
yapf
seem to cause a bunch of logs like this
Copy code
12:02:16.98 [INFO] Filesystem changed during run: retrying `Fmt` in 500ms...
12:02:17.50 [INFO] Filesystem changed during run: retrying `Fmt` in 500ms...
12:02:18.01 [INFO] Filesystem changed during run: retrying `Fmt` in 500ms...
12:02:18.52 [INFO] Filesystem changed during run: retrying `Fmt` in 500ms...
12:02:19.04 [INFO] Filesystem changed during run: retrying `Fmt` in 500ms...
w
those are expected, although annoying… it just means that it took longer for the 
fmt
rule to finish than for the engine to notice that the files on disk had changed. i think that we have a ticket about quieting it down, but it is harmless.
it has no impact on correctness.
h
Right, learning a lot by adding another formatter to the mix.
We currently only have 
yapf
and I want 
isort
. Having trouble getting them happy together since isort wants to format some import lines a different way than yapf does.
w
yea, what gets written to disk has no impact on the actual behavior of the 
fmt
goal, because it executes all formatters sequentially in sandboxes before commiting the result to disk
4 Views
Open in Slack
PreviousNext
Powered by