You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If agd is configured with telemetry enabled, and runs a fairly typical workload (e.g. with a chainStorage set or delete that decrease the size of the stored key), it panics the Golang side, causing an exception on the JS side.
sizeDelta may very well be negative, which is invalid for telemetry.IncrCounter*. For the metric to go up and down over time, use telemetry.SetGauge* instead. More detail than only the current number may need to be implemented with multiple Counters and/or Gauges using different metric keys.
The text was updated successfully, but these errors were encountered:
michaelfig
changed the title
agd with telemetry throws panic: counter cannot decrease in valueagd throws panic: counter cannot decrease in valueFeb 27, 2025
Describe the bug
If
agd
is configured with telemetry enabled, and runs a fairly typical workload (e.g. with a chainStorage set or delete that decrease the size of the stored key), it panics the Golang side, causing an exception on the JS side.To Reproduce
Steps to reproduce the behavior:
git checkout mfig-devnet-config-steps
(the PR fix(vm-config):vats/init-core.js
relies on econCommittee #11056 branch)cd agoric-sdk/packages/cosmic-swingset
make scenario2-setup scenario2-run-chain
to start a new chain with Golang telemetry enabledmake fund-provision-pool
(which triggers the SwingSet provisionPool vat to interact with the Cosmos bridge)make provision-acct ACCT_ADDR=$(cat t1/8000/ag-cosmos-helper-address)
panic: counter cannot decrease in value
errors logged by the running chain, as below2025-02-27T03:09:04.893Z SwingSet: ls: v10: Error#1: panic: counter cannot decrease in value
Expected behavior
No panics.
Platform Environment
vats/init-core.js
relies on econCommittee #11056 , currentlygit describe --tags --always
yields fast-usdc-beta-1-137-gef30b2a883Additional context
#10997 introduced an idiom that looks like:
sizeDelta
may very well be negative, which is invalid fortelemetry.IncrCounter*
. For the metric to go up and down over time, usetelemetry.SetGauge*
instead. More detail than only the current number may need to be implemented with multiple Counters and/or Gauges using different metric keys.The text was updated successfully, but these errors were encountered: