tree e659d23dd92ffd5559f9c55b823b4469bb00e15d
parent 073699ea1342b90ed0ca28ab39c90bc71c223e9a
author Tyler French <66684063+tyler-french@users.noreply.github.com> 1702663968 -0500
committer GitHub <noreply@github.com> 1702663968 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlfJchCRBK7hj4Ov3rIwAAjfgIAFxsiCU3a4VFWih6gFhYH9OR
 vEoi1A339FBrQrBekc9uj444Du8gcUpuhJDovPeAuJkJbS4Zohdll2OoPeSxUeSW
 Gpr4/Rv+re151iiU3/Tc8mgzMSWSF1hE1j/Tycy0D/1Wq9jZiJUufrnU42Kwm3po
 K3d/WM5f+mJ8RG1EmQ68CAIry2ywLF78WX/ystvyQoy9bhNytLheat3M3/wSlZiR
 MPlVrrI5dr9tbYRsOtui15c0fUSc3yaT50adTQNvoynm5FOt21DCkNuade7v31gk
 Np0f2ohtr2jF6rcpzV1xQ3gXsHl1/KIRalNa8sWsjCRs9fC7sXDhKWn80ZnjHb8=
 =3sny
 -----END PGP SIGNATURE-----
 

feat(fix-update): allow user to profile commands with pprof (#1685)

This adds two flags to the `fix` and the `update` command, `-cpuprofile` and `-memprofile`, which allow users to create output CPU and memory `pprof` files to better understand the performance of Gazelle. This is very helpful in debugging issues like #1688, which show up in certain repository setups.

The implementation mostly followed the instructions on https://pkg.go.dev/runtime/pprof#hdr-Profiling_a_Go_program to set up profiling options for the command in the `cmd/gazelle`.

Tests were added to ensure that the `newProfile` would return a `profile{}` that wouldn't panic, even if either provider is empty.

Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>