Voting for a new IC release - ca5e50528

Governance
,
1

Hello there!

We are happy to announce that voting is now open for a new IC release and the retirement of old replica versions 43c85184884cf0a23ecee4c28177b359579d0fea and d353989b94e5862692ea2887637dcacace4e244c.
The NNS proposal is here: IC NNS Proposal 124857 .

Here is a summary of the changes since the last release:

  • [28b8773cb] Crypto: perf: add crypto basic sig benchmarks with remote vault
  • [be6ab0121] Crypto: refactor: Use RustCrypto for all hashing
  • [09d6aa3d4] Execution: chore: Add critical error for missing install code call
  • [46bd5ac61] Execution: chore: Observe metric for stop canister request
  • [906467d69] Execution: chore: Remove deprecated set_controller management api
  • [6529a74ee] Execution: chore: Add limit to a single HTTP header in headers to comply with the spec
  • [96184d423] Execution: feat: Add support for Bitcoin canister query endpoints to the query handler
  • [660899bd2] Execution: feat: Expose subnet metrics through the http api
  • [c7d2f8b39] Message Routing: feat: Hardlink immutable files
  • [236743769] Networking: build: update quinn
  • [c365dc51c] Networking: chore: remove redundant/unused code
  • [f11d7a0b4] Networking: chore: remove the unused RemoveFromValidated from the set of ChangeActions
  • [64ca887dd] Networking: chore: use the global workspace for deriving the prost version
  • [27d80069d] Networking: chore: use the global workspace for the version of the futures crate
  • [05bd2099d] Networking: docs: add the initial version of the transport design readme
  • [323022cc6] Networking: feat: purge artifacts from the unvalidated pool
  • [712910160] Networking: feat(p2p-consensus): Add watcher for the priority function.
  • [729f65d78] Networking: feat: compress state sync chunks
  • [a7a927a67] Networking: fix(p2p-consensus): Fix formatting of endpoints.
  • [5e02dc012] Networking: fix: introduce a dedicated tokio runtime for P2P
  • [8435b3e94] Node: HostOS VSOCK fixes
  • [40ea9bec9] Node: Support concurrent vsock commands
  • [4918bb79b] Node: Tidy up some SetupOS drive handling
  • [56800b234] Runtime: Re-added scaled up performance numbers to dashboard
  • Various tech-debt management: code refactoring, docs, bug fixes, test updates

IC-OS Verification

To build and verify the IC-OS disk image, run:

# From https://github.com/dfinity/ic#verifying-releases
sudo apt-get install -y curl && curl --proto '=https' --tlsv1.2 -sSLO https://raw.githubusercontent.com/dfinity/ic/ca5e5052886de781021506814d2c6502e375da48/gitlab-ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c ca5e5052886de781021506814d2c6502e375da48

The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.

2 Likes
2

And there is another “feature build” that enables QUIC protocol for state sync. We would like to deploy it to a subset of subnets again.

1 Like
3

Reviewers for the CodeGov project have completed our review of these replica updates.

Proposal ID: 124857
Vote: ADOPT
Full report: CodeGov portal on DSCVR

Proposal ID: 124858
Vote: ADOPT
Full report: CodeGov portal on DSCVR

Neuron: CodeGov
NeuronID: 2649066124191664356
Voting history: Dashboard
Website: codegov.org

At the time of this comment on the forum there are still 2 days left in the voting period, which means there is still plenty of time for others to review the proposal and vote independently.

We had several very good reviews of the Release Notes on these proposals by @Zane, @cyberowl, @ZackDS, @massimoalbarello, and @ilbert. The IC-OS Verification was also performed by @Gekctek and @tiago89. I recommend folks talk a look and see the excellent work that was performed on these reviews by the entire CodeGov team. Feel free to comment here if you have any questions or suggestions.

4

Hey @sat would you please let the change owners for 124857 know that @cyberowl had a few comments and questions about some of the details in commits [09d6aa3d4], [660899bd2], and [56800b234] that they might want to review. He provided more details in his review posted in the CodeGov portal in DSCVR. Here are the relevant screen shots…

image
image864Ă—166 20.2 KB

image
image861Ă—494 69.6 KB

image
image865Ă—212 26.9 KB

2 Likes
5

re [56800b234]

You are correct, queries and update calls are mixed up on our dashboard. Thanks for spotting this. I will fix this soon.

3 Likes
6

Re [[09d6aa3d4]] and [660899bd2]

Thanks for catching some of the typos, indeed these were missed.

The change to principal id was made because with the introduction of the new endpoint (/api/v2/subnet/) we have cases where the id passed in such api calls to the replica does not always represent a canister anymore. So, the switch was made to principal id and wherever it’s applicable we additionally check whether this is really supposed to be a canister id to proceed with further processing (e.g. in query or update calls or the existing canister state read but for example not in the new one). In hindsight, it should have probably been mentioned as I realise now that it might not have been super clear without more context.

The last part around the message for the two condition is something that was simply moved around in the commit, so kept the message intact. I can bring it up with the code owners to make a change if they agree.

3 Likes
7

Hey @stefan-kaestle and @dsarlis thank you so much for the feedback and interaction! Keep up the good work.

3 Likes