🌮 Mood: Looking forward to some tacos tonight.

🎵 Soundtrack: Big Red Machine Mix

🦁 More Parsing

I fixed my bash script and I finished parsing the rest of the top 1000 golang repos on github by stars. Once removing duplicates due to vendoring, I found 5 additional examples of the bug. I opened issues for the ones I found. I shared this research on the issue and got two ❤️s. Yayyyyy.

Project Name Links
golang/go buggy test, github issue
golang/text buggy test, github issue
miekg/dns buggy test, github issue
m3db/m3 buggy test, github issue
cuelang/cue -> cue-lang/cue buggy test, github issue
zalando/skipper buggy test, github issue
smartcontractkit/chainlink buggy test, github issue

Two of these examples were hiding failing tests, including skipper, which someone has investigated and submitted a PR for already!

a github comment on issue for skipper that says thanks

I would’ve done PRs for the trival ones, but to do that I have to wrangle employer stuff and that will take days. I’ll check next week and see if any of them are not done yet and then I will go through that hassle. Next step is adding it as a go vet check!

🐈‍⬛ Go Vet

🎥 I watched this video to learn more: “GopherCon UK 2019: Michael Matloob - Using and Writing Go Analyses”.

Then I started poking around CheckExample like one of the maintainers suggested.

I ended the day by having a failing test (yay TDD).

📚 Reading Github Issues

Skipped it again because I was too focused on parsing!