I have an issue, if I auto stake maturity, it updates my maturity balance normally, if I spawn maturity and then disburse it after 7 days I can add it to my neuron.
If I stake maturity it just disappears, neither balance gets updated (I’m aware only the maturity balance should be updated). It happened today and it’s not the first time. It’s there anywhere I can check where it went?
To recap, I got my maturity, it said 4.77 available, I hit stake, signed the transaction with my ledger, maturity number didn’t increase, now says available 0.
Should I raise a support ticket for this?
Just to be clear though.
When you stake all of your available maturity, it is supposed to say 0 Available afterwards.
It should only update the Staked Maturity balance.
Are you sure you’re not getting confused?
Could be a case of some sloppy joes:
committed 12:16PM - 13 Jan 26 UTC
What?
===
Add support for Claude Code for developing dfinity/ic.
Why?
====
We… should use AI tools more for developing dfinity/ic to increase our
productivity.
I had some initial success: using this PR `claude` was able to produce
https://github.com/dfinity/ic/pull/8287 with about 4 prompts and a bit
of manual work.
How?
===
~* Install the `claude` CLI in the dev container. It's important to have
`claude` run in the dev container such that it can easily call `cargo`
and `bazel` without wrapping all those commands in
`ci/container/container-run.sh` and such that the bazel server keeps
running.~ This has been reverted because we'll first split up the CI
from the dev-container and then add `claude` to the dev-container.
* ~Install the Claude Code VS Code extension. For me the extension is
not working correctly yet since I can't login for some reason. I need to
debug this further with IT.~ This has also been reverted and we'll
probably also do this later.
* Add a `.claude/README.md` with some preliminary notes on how to use
`claude`.
* Add a preliminary `.claude/CLAUDE.md` instructing Claude how to build
and test the ic repository.
This document is submitted with every prompt. We expect it to be
continuously tweaked by every team to optimise their prompting.
Future Work
===
Add [hooks](https://code.claude.com/docs/en/hooks-guide)
---
Consider moving some of the instructions from `.claude/CLAUDE.md` to
hooks like `cargo fmt` and `cargo clippy` after modifying .rs files.
This will keep the context as small as possible.
Add dfinity/ic specific [Agent
Skills](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview).
---
Examples:
* How to query Apache Superset (or ideally the PostgreSQL DB directly
via `psql`) for:
the most flaky tests,
the slowest tests on PRs,
previous failed / flaky tests runs of a given test,
failure rate of a given test over time,
run time of a given test over time.
* How to download a bazel test log from BuildBuddy.
* How to debug system-tests.
* How to download the IC node logs of a testnet / mainnet from
ElasticSearch.
* How to query Prometheus in testnets for relevant metrics.
Interesting Reads
===
Apart from the [Claude Code Docs](https://code.claude.com/docs) the
following are interesting Reads on how to optimize working with Claude
Code:
*
https://medium.com/@joe.njenga/17-best-claude-code-workflows-that-separate-amateurs-from-pros-instantly-level-up-5075680d4c49
* https://x.com/i/status/2007179832300581177
---------
Co-authored-by: IDX GitHub Automation <>
Co-authored-by: Nicolas Mattia <nicolas.mattia@dfinity.org>
Yeah, I’m being an idiot. The total balance doesn’t change because it’s maturity plus the available maturity.
I was looking at the available balance going to zero, and the total maturity not changing, but I wasn’t looking at the staked maturity (which actually did increase).
