leongross
leongross
@jensdrenhaus should we get this in or is it sufficient to keep this as an open PR for now?
@aykevl I will add some basic tests. Since I already did some testing (I hope) it should be fairly easy to integrate this here.
@robertmin1 what do you mean by > it is unable to trace What did you expect to happen / how did you expect it to work and what happened instead?...
@archie2x sorry for being late with the review. I added a new batch of suggestions (also many unimportant nits). When this is fixed we can get this merged.
Up until now it only fixes the index out-of-range issue. When I build it on my system, the panic in the interface conversion still exists for said command ``` $...
Example application I use to test out simple network support on x86_64 linux systems: https://gist.github.com/leongross/ed23eafe85105ead0a63c88e4964657b
@nquarton Just to clarify the terminology here: with "max measurements" you mean that we should measure and validate the maximum possible **size** for a x509 certificate that we can create?...
Closing this for now. Reworking the error strategies in u-root should follow a systematic approach that we define (e.g. when we use nolint directives etc). We should define an easy-to-follow...
We should revive this PR in favor of #3238. I looked at @archie2x's work on the CI part, and it looks very promising.
There are some bugs in my multi-go-routine implementation that I currently don't have time to address. I close this PR for now and will create a more streamlined CI utility...