Voting for a new IC release - 2023-12-13_23-01

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 version 69e1408347723dbaa7a6cd2faa9b65c42abbe861.
The NNS proposal is here: IC NNS Proposal 126729 .

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

Features:

  • [c602b21] Boundary Nodes,Node: remove unused fields from logs
  • [03338f5] Execution: allow Start api type for ic0.in_replicated_execution
  • [40d18f8] Execution: Track time, balance and call System APIs
  • [8d89fa0] Execution,Runtime: Avoid cache invalidations
  • [5b10198] Execution,Runtime: Increase Query Cache capacity to 200MiB
  • [a9fc954] Execution,Runtime: Implement max expiry for cache entries
  • [bc6ce9b] Execution,Runtime: QueryStats PayloadBuilder validation
  • [d8fb391] Message Routing: Split ResetTipTo functionality from TipToCheckpoint
  • [d726cac] Message Routing,Runtime: merge LSMT overlays
  • [b934613] Node: ic-os/guestos: mount filesystem with the label CONFIG
  • [5014ae8] Runtime,Execution: implement ic0.in_replicated_execution system API method

Bugfixes:

  • [fd396ab] Boundary Nodes,Node(custom-domains): removed canister id header
  • [586cd9e] Message Routing: Load WASM chunk store correctly with LSMT
  • [935c001] Networking(http_outcalls_adapter): Only use socks proxy as fallback
  • [c36fa97] Networking(consensus-manager): Don’t hold lock on artifact pool during response serialization in rpc endpoint
  • [9c3c37f] Networking(consensus_manager): verify that downloaded artifact matches advertised Id
  • [af56c7b] Node: proper input format in help text

Chores:

  • [bc75916] Boundary Nodes,Node: upgrade vector & node_exporter
  • [a24e15e] Boundary Nodes,Node: set the CONFIG label for the boundary-node config image
  • [cf2296b] Consensus(http_utils): Remove unused error types
  • [13d2e53] Consensus(http_utils): Remove manual redirect logic
  • [185add8] Consensus: sync rocksdb annotation
  • [ef5166b] Crypto: Change NiDkgTranscript to ThresholdSigPublicKey conversions to TryFrom and remove internal panics
  • [b85b99e] Crypto: Add script to estimate NIDKG costs
  • [1ede681] Execution: Introduce System API call IDs
  • [6bfb53b] Networking(consensus-manager): Fix typos and update stale comments
  • [99fcf43] Networking(quic-transport): Add packets sent/lost metrics
  • [383bf33] Node: Add documentation for how to add a new dependency to ICOS images.
  • [359ad72] Node: put slog dependency into proper section

Refactoring:

  • [b3adfe5] Networking: don’t use the ArtifactChunk type in the old P2P; remove the UnitChunk variant as well.
  • [33c63fb] Networking,Message Routing: Don’t use the Artifact aggregation type for the new state sync.
  • [ea368f6] Networking,Message Routing: remove the ArtifactChunkData type

Tests:

  • [ced121d] Consensus(http_utils): Add unit tests for FileDownloader
  • [9b1e237] Crypto: Add unit tests for FS key update
  • [ca1bdc5] Crypto: update public key in dummy_transcript_for_tests_with_params
  • [f45daff] Execution,Runtime: Move query cache tests into a separate module
  • [f53527b] Message Routing: Make state manager tests pass with LSMT

Other changes:

  • [a592071] Boundary Nodes,Crypto,NNS,T&V: Move rcgen to the workspace to keep the same version
  • [1bbb7e2] NNS,Execution,Message Routing: upgrade some crate versions and remove unused ones
  • [ce506d8] Node: Updating container base images refs [2023-12-13-1429]
  • [7fd682d] Node: Updating container base images refs [2023-12-12-0722]
  • [3d97902] Node: Node exporter SSL certificate used for metrics-proxy.
  • [d0230a5] Node: Add node network receive and send metrics for the network cards.
  • [d01c559] Node: Updating container base images refs [2023-12-08-0925]
  • [739c35a] Node: Updating container base images refs [2023-12-07-0925]

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/91d71f050805e37a1e7294b282dd15591954e0b1/gitlab-ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c 91d71f050805e37a1e7294b282dd15591954e0b1

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 build with the new P2P protocol used for http(s) outcalls:

  • [206a50f] Networking: enable new p2p protocol for https outcalls

https://dashboard.internetcomputer.org/proposal/126730

1 Like
3

Reviewers for the CodeGov project have completed our review of this replica update.

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

Proposal ID: 126730
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 @jwiegley, @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.

RECRUITING NOTE:
The CodeGov Project is offering attractive bounty payments to experienced Rust developers who are interested in spending a few hours each week reviewing Replica Version Management proposals, which are code changes that are submitted to the Internet Computer Protocol (ICP) governance system for adoption or rejection. We do this through IC-OS Verification and by performing a sanity check on the Release Notes. Our votes are cast according to the findings of our reviewers. Proposals are usually submitted on a Friday and we complete our reviews within 48 hours. Each reviewer posts a summary of their findings in the CodeGov portal on DSCVR.one and the bounty payment is made using the tipping feature of DSCVR with ckBTC equivalent to USD. The bounty is always announced in this bounty payment post on the portal and the deliverables for each review can be found on the codegov.org website. It is a requirement to Apply on the codegov.org website and to complete either Form W-9 or Form W-8BEN in order to get paid the bounty. Please send me a DM or an email at codegov.org@gmail.com if you would like to discuss this opportunity further.

4 Likes