Skip to content
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.

Rune abort infinite loop #1032

Closed
Tracked by #724
ryanleecode opened this issue May 25, 2023 · 2 comments · Fixed by #1100
Closed
Tracked by #724

Rune abort infinite loop #1032

ryanleecode opened this issue May 25, 2023 · 2 comments · Fixed by #1100
Assignees
Labels
bug Something is broken

Comments

@ryanleecode
Copy link
Contributor

ryanleecode commented May 25, 2023

Capi version: 0.40

Rune.ts:211 Uncaught RangeError: Maximum call stack size exceeded.
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
    at AbortSignal.<anonymous> (Rune.ts:211:30)
(

image

@robocapi robocapi added this to Capi May 25, 2023
@peetzweg
Copy link
Member

peetzweg commented May 30, 2023

paritytech/capi-multisig-app#186 (comment)

This is quite the urgent issue. It's blocking ratifying multisig calls in the capi-multisig-app.

Impossible to debug from the frontend code. Not sure if this can be even reproduced in a node/deno environment or if it only occurs in browser.

cc @harrysolovay

This function is resulting in the described error:
https://github.com/paritytech/capi-multisig-app/blob/7737a7848fcbbc47a46737f0ee24c9650a00278a/www/src/components/wizards/transaction/Sign.tsx#L18-L49

@peetzweg peetzweg added the bug Something is broken label May 30, 2023
@statictype
Copy link

Was able to successfully ratify a multisig call by adding .finalized() to the Rune like so:

    const ratifyCall = multisig.ratify(user, call)
      .signed(signature({ sender }))
      .sent()
      .dbgStatus("Ratify")
      .finalized()

The max call stack size error remains, but the call is successfully dispatched to the chain and shows up on Subscan
https://westend.subscan.io/block/0xcb2d19a6796cec9fea4e301dec004043a5b239ea1b1592469d80a8773b716625

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something is broken
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants