Error in vault task #30
Comments
|
The uncensored form of the amounts is obscure on XS relative to node because our xsnap console shim just uses cc @kriskowal |
Oo, this sounds like it needs an issue of its own. |
|
@mhofman Can you confirm that the Based on the error, it's this line erroring:
|
|
Admittedly I don't fully understand what the vault task does, but my cursory reading is that it should? // put 1% into the vault
const bldToLock = AmountMath.make(bldBrand, bldBalance.value / BigInt(100)); |
|
What's the environment in which this code is being run? Can you do a console log of the current amount of the purse? |
|
I switched the local solo to index 9c038d8..5162475 100644
--- a/loadgen/agent-create-vault.js
+++ b/loadgen/agent-create-vault.js
@@ -57,6 +57,10 @@ export default async function startAgent([key, home]) {
// (we close over 'bldToLock')
async function openVault() {
console.error('create-vault: openVault');
+ const currentBldBalance = await E(bldPurse).getCurrentAmount();
+ console.error(
+ `create-vault: openVault: start balance: ${disp(currentBldBalance)} BLD`,
+ );
const openInvitationP = E(treasuryPublicFacet).makeLoanInvitation();
const proposal = harden({
give: { |
|
Ok, thanks! Can you give me instructions for reproducing? |
|
With a ./runner/bin/loadgen-runner --stages=1 --no-stage.0.save-storage --stage.0.duration=10 --stage.0.loadgen |
|
Also, looking at the log again, it looks like the error goes through startInstance.js:167, which is the fee purse being charged for an offer. Are you sure the fee purse has enough RUN in it? |
|
This doesn't look like a bug in the Zoe or ERTP packages (or at least, we haven't found anything that would indicate that), so I need to reassign this back. I'm happy to give advice and discuss the debugging though. |
|
I do believe this used to work as expected, but it's possible the way a local solo is provisioned isn't compatible with the metering fees needed to run the loadgen tasks. I'll try to figure out when this broke. |
|
There has been other similar non fatal errors (e.g. Agoric/agoric-sdk#4114). I'm not sure if this one has occurred since then. Will close and open an issue to detect regressions in the loadgen. |
When running a
vaultloadgen task, some I believe Zoe originating error crops up.ammtasks run fine, both before and after, so it's probably not a metering issue.This is happening on Agoric/agoric-sdk@d48e6a7
The text was updated successfully, but these errors were encountered: