maint(windows-agent): Investigate skipping distros

[CarlosNihelton]

time=2024-07-24T12:17:10-07:00 level=error msg=Landscape:  skipping distro "Ubuntu-24.04" from landscape info: could not get distro "Ubuntu-24.04"'s state: could not get states of distros: exit status 1. Stdout: . Stderr:

That happens during construction of the status message sent to Landscape. If we skip a distro, Landscape understands it doesn't exist anymore and removes it from the dashboard. But that happens sometimes when an existing distro. It seems a WSL internal error.

ubuntu/GoWSL#120 should prevent the stdout and stderr messages to come empty as shown above.
Thus I'm updating GoWSL here.

That doesn't prevent the issue itself.

I couldn’t reproduce this outside of UP4W. I attempted building a small binary in Go doing the same steps as GoWSL does and put it to run during system startup in loop, rebooted the OS many times but no success. The few times I’ve seen this happening in the logs were early during app startup, so I suspect it may happen because some WSL internal component is not yet ready. Thus this PR: adding one-time retry if an error happens when attempting to retrieve a distro state.

Either that will prevent the issue once for all or at least give us more context about what causes that error.

---

UDENG-3722

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.35%. Comparing base (b4a5f0d) to head (fdb3d8b).
Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #902      +/-   ##
==========================================
+ Coverage   89.28%   89.35%   +0.07%     
==========================================
  Files         110      110              
  Lines        7520     7533      +13     
==========================================
+ Hits         6714     6731      +17     
+ Misses        627      625       -2     
+ Partials      179      177       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[CarlosNihelton]

Now we have to upgrade the Go. I'm unsure if we should Go with the toolchain to 1.22.7 or migrate straight into 1.23.1. 1.23.0 is affected by the same vulnerability reported in ´go/parser`.

[jibel]

Now we have to upgrade the Go. I'm unsure if we should Go with the toolchain to 1.22.7 or migrate straight into 1.23.1. 1.23.0 is affected by the same vulnerability reported in ´go/parser`.

The version of Go has been bumped to 1.23, so you'd just need to rebase this PR

[didrocks]

Tell me what you think about my comment or if you think this is unecessary.

As a aside, you will to rebase again due to conflicts :)

[CarlosNihelton]

Rebased over the latest main, updated GoWSL dependency and implemented the looping.

[didrocks]

Looking all good from my side!