Update go-capnp package to fix build issue on Go 1.23

[kwilczynski]

What type of PR is this?

/kind dependency-change

What this PR does / why we need it:

When building the go-capnp using Go 1.23 or Go tip, the following build error will be reported (an example build failure from the CRI-O project):

# capnproto.org/go/capnp/v3
vendor/capnproto.org/go/capnp/v3/list.go:1087:10: invalid composite literal type T

Thus, upgrade the go-capnp version to v3.0.1-alpha.2, which would fix the build issue on a newer version of Go.

Related:

• Fix build error on go1.23rc1 capnproto/go-capnp#576
• Possible problem with go 1.23 (rc1) cri-o/cri-o#8373

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kwilczynski
Once this PR has been reviewed and has the lgtm label, please assign rphillips for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kwilczynski]

/assign kwilczynski

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.34%. Comparing base (4e0f474) to head (d9afa0d).
Report is 603 commits behind head on main.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2317      +/-   ##
==========================================
- Coverage   37.53%   37.34%   -0.20%     
==========================================
  Files          15       15              
  Lines        1268     1264       -4     
  Branches      414      421       +7     
==========================================
- Hits          476      472       -4     
+ Misses        526      524       -2     
- Partials      266      268       +2     

[saschagrunert]

Integration tests seems to fail, do you know why?

[kwilczynski]

/close

[openshift-ci]

@kwilczynski: Closed this PR.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

/reopen

[openshift-ci]

@kwilczynski: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

Integration tests seems to fail, do you know why?

@saschagrunert, I will look into it.

[kwilczynski]

Integration tests seems to fail, do you know why?

@saschagrunert, I will look into it.

@saschagrunert, I was able to narrow the failures down to the following change of the go-capnp package:

• Clean up Message.Reset capnproto/go-capnp#489

Part of the following release:

• https://github.com/capnproto/go-capnp/releases/tag/v3.0.0-alpha.26

Neet to look whether we need to do something or whether this is a regression.

[saschagrunert]

Yay, green CI! 🟢

[saschagrunert]

@kwilczynski is this still WIP?

[kwilczynski]

@kwilczynski is this still WIP?

@saschagrunert, should be ready for review, etc.

[saschagrunert]

Thanks!

[saschagrunert]

/approve

[kwilczynski]

@saschagrunert, do you think we could cut a new release?

[saschagrunert]

@saschagrunert, do you think we could cut a new release?

Yes, let me first check if we can / have to fix cri-o/cri-o#8411. I'm not even sure if that's a conmon-rs issue.

[kwilczynski]

@saschagrunert, do you think we could cut a new release?

Yes, let me first check if we can / have to fix cri-o/cri-o#8411. I'm not even sure if that's a conmon-rs issue.

@saschagrunert, the exit code and time out boolean value should be copied so the correct exit code should be reflected. We have a check in a test to verify this, per:

• https://github.com/containers/conmon-rs/blob/main/pkg/client/client_test.go#L389
• https://github.com/containers/conmon-rs/blob/main/pkg/client/client_test.go#L420

I also doubt that our change here resolved anything for the other issue.

[saschagrunert]

@kwilczynski see https://github.com/kubernetes-sigs/cri-tools/actions/runs/10195323313/job/28204264894?pr=1546