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
I'm running a script that watches for file changes, and then executes go run main.go
watchexec -r -e go -- go run main.go serve --http 0.0.0.0:8090
Obviously since this builds and runs multiple times, go seems to create a new folder under /tmp/go-buildxxxxx storing the built executable, which in my case has 32MB
What did you see happen?
This results in an accumulation of unnecessary go-buildxxxx folders overfilling tmpfs volume on Fedora 40.
$: df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 16G 16G 0G 100% /tmp
Deleting all go-build* folders from /tmp brings /tmp down to 1% in my case.
What did you expect to see?
go run should not create multiple /tmp/go-buildxxxx folders when executing the build command multiple times within the same project. Or it should at least clean them up when the process is terminated.
The text was updated successfully, but these errors were encountered:
Go version
go version go1.22.4 linux/amd64
Output of
go env
in your module/workspace:What did you do?
I'm running a script that watches for file changes, and then executes
go run main.go
Obviously since this builds and runs multiple times, go seems to create a new folder under /tmp/go-buildxxxxx storing the built executable, which in my case has 32MB
What did you see happen?
This results in an accumulation of unnecessary
go-buildxxxx
folders overfilling tmpfs volume on Fedora 40.Deleting all
go-build*
folders from /tmp brings /tmp down to 1% in my case.What did you expect to see?
go run
should not create multiple /tmp/go-buildxxxx folders when executing the build command multiple times within the same project. Or it should at least clean them up when the process is terminated.The text was updated successfully, but these errors were encountered: