-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use cycles ledger in deposit-cycles #3626
Conversation
|
call_sender = &proxy_sender; | ||
} | ||
Err(err) => { | ||
if CYCLES_LEDGER_ENABLED && matches!(err, crate::lib::identity::wallet::GetOrCreateWalletCanisterError::NoWalletConfigured { .. }) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does the error handling of the get_or_create_wallet_canister
depend on the flag CYCLES_LEDGER_ENABLED
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because until we enable the cycles ledger functionality we want to preserve the previous behavior of erroring out because no cycles wallet is configured. Once the cycles ledger is enabled we will just try to use the cycles in the cycles ledger
Description
dfx canister deposit-cycles
now is also capable of using cycles on the cycles ledger to top up a canister.The test
dfx/cycles-ledger/top-up and deposit-cycles
passed when the feature flag was turned on, see e.g. this run: macos, ubuntu. It is now disabled until the feature flag gets enabled (ETA ~1 month)Fixes SDK-1371
How Has This Been Tested?
added e2e
Checklist: