updates to get everything working with go 1.18

[adamstruck]

Works for me - thought it could be useful given the ongoing compliance work I have seen.

[kellrott]

We've been working on getting up to TES 1.1 compliance. We'll need to review this against all the changes in #716

[lbeckman314]

This is great! We've just recently been getting past a possible logging concurrency bug* with MongoDB and Badger that has been blocking the PR in #716. I'll try rebasing that branch and this one to reconcile the changes into a mergeable PR and will update here for any review or recommendations!

---

*Specifically with the EventWriter attempting to write the last event to the database after the connection has been closed. fix/lint adds a WaitGroup to block the logging in Run() before closing.

[adamstruck]

Looks like this PR can probably just be closed in favor of #716.

You may want to use the ‘.golangci.yml’ file and compare the proto code generation command in the Makefile.

[lbeckman314]

Cleaning up PR's but making a note of this to revisit the Proto discussion and proto code generation as that could definitely be improved on now that compliance tests are happy.

Looks like this PR can probably just be closed in favor of #716.

You may want to use the ‘.golangci.yml’ file and compare the proto code generation command in the Makefile.

We're currently manually patching the tes.proto file with explicit views (minimal, basic, full) and using a custom marshaller (marshal.go) in order to get around the problem of protobuf not emitting empty slices (marshal_jsonpb.go).

This could be improved in a couple ways, including:

1. Updating the proto code generator to include the the views enum value
2. Replacing our marshal.go with an updated version of marshal_jsonpb.go that outputs empty slices

Updating the code generator would very likely be the simplest option with implementing the custom marshaler being a backup.