Skip to content

chore: update replica version to 17d483c6#4514

Merged
ggreif merged 6 commits intomasterfrom
chore-update-replica-17d483c60a09b393ad82a2091b68a242ac69c72d-master
Apr 17, 2026
Merged

chore: update replica version to 17d483c6#4514
ggreif merged 6 commits intomasterfrom
chore-update-replica-17d483c60a09b393ad82a2091b68a242ac69c72d-master

Conversation

@pr-automation-bot-public
Copy link
Copy Markdown
Contributor

@pr-automation-bot-public pr-automation-bot-public bot commented Mar 27, 2026

SHA 17d483c60a09b393ad82a2091b68a242ac69c72d (tag release-2026-03-26_04-51-base)

Suggested CHANGELOG.md changes

## Dependencies

### Replica

Updated replica to elected commit 17d483c60a09b393ad82a2091b68a242ac69c72d.
This incorporates the following executed proposals:


Previous replica version

``

@pr-automation-bot-public pr-automation-bot-public bot requested a review from a team as a code owner March 27, 2026 17:11
@ggreif ggreif self-assigned this Mar 27, 2026
@ggreif ggreif enabled auto-merge (squash) April 17, 2026 00:05
@ggreif
Copy link
Copy Markdown
Contributor

ggreif commented Apr 17, 2026

The set freezing threshold test fails with the new replica:

Canister uxrrr-q7777-77774-qaaaq-cai is out of cycles: please top up the canister with at least 24_653_335_286_234 additional cycles

The issue: after --freezing-threshold 100000000000 --confirm-very-long-freezing-threshold, the canister is frozen because the new replica requires more cycles to sustain that threshold. The fabricate-cycles call comes too late — it's after the status check that fails.

Suggested fix — move the fabricate-cycles call right after setting the high threshold:

   # with manual override it's ok
   assert_command dfx canister update-settings hello_backend --freezing-threshold 100000000000 --confirm-very-long-freezing-threshold

-  # to check if threshold is set correctly we have to un-freeze the canister by adding cycles. Fabricating 100T cycles onto it
-  assert_command dfx ledger fabricate-cycles --canister hello_backend --t 100
+  # un-freeze the canister by adding cycles before checking status. Fabricating 100T cycles onto it.
+  # (With the updated replica the canister needs more cycles to sustain this threshold.)
+  assert_command dfx ledger fabricate-cycles --canister hello_backend --t 100
+
   assert_command dfx canister status hello_backend
   assert_match "Freezing threshold: 100_000_000_000"

(The lines are the same, just ensuring fabricate-cycles happens before canister status.)

Actually looking again — they're already in that order. The issue might be that the update-settings call itself fails because the canister is already frozen and can't execute. In that case, fabricate-cycles should go before the update-settings call:

+  assert_command dfx ledger fabricate-cycles --canister hello_backend --t 100
   assert_command dfx canister update-settings hello_backend --freezing-threshold 100000000000 --confirm-very-long-freezing-threshold
-  # to check if threshold is set correctly we have to un-freeze the canister by adding cycles. Fabricating 100T cycles onto it
-  assert_command dfx ledger fabricate-cycles --canister hello_backend --t 100
   assert_command dfx canister status hello_backend

The new replica requires more cycles to sustain an extreme freezing
threshold (100B). Top up the canister before update-settings so it
doesn't freeze and reject subsequent calls.
@lwshang
Copy link
Copy Markdown
Contributor

lwshang commented Apr 17, 2026

We're sunsetting this project (see #4524). If the blocking test isn't trivial to fix, feel free to just remove or comment it out.

@ggreif
Copy link
Copy Markdown
Contributor

ggreif commented Apr 17, 2026

We're sunsetting this project (see #4524). If the blocking test isn't trivial to fix, feel free to just remove or comment it out.

Yeah, trying my best! But I'd really would like to have an acceptable moc with a decent ic.did, that is not ages-old.

@ggreif ggreif merged commit 73188cd into master Apr 17, 2026
113 checks passed
@ggreif ggreif deleted the chore-update-replica-17d483c60a09b393ad82a2091b68a242ac69c72d-master branch April 17, 2026 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants