Skip to content

Fix sns demo proposals creation #6722

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

mstrasinskis
Copy link
Contributor

Motivation

Currently, creating dummy SNS proposals throws an error due to multiple failing calls.
This PR addresses a few related issues to make the flow work — except for executeNSFunctionProposal, which is still failing.

Changes

  • Add new required field: topic.
  • Comment out executeNSFunctionProposal — solution still pending.
  • Make proposal execution sequential to improve robustness. This feature isn't used in the e2e tests.

Tests

  • Verified locally that it creates proposals w/o errors.

Todos

  • Add entry to changelog (if necessary).
    Not necessary.

@mstrasinskis mstrasinskis changed the title Fix sns demo proposals Fix sns demo proposals creation Apr 22, 2025
@mstrasinskis mstrasinskis marked this pull request as ready for review April 22, 2025 08:45
@mstrasinskis mstrasinskis requested a review from a team as a code owner April 22, 2025 08:45
},
] as [SnsAction],
};
// const executeNSFunctionProposal = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this block of code commented out because of the linter? What if we add a linter exception for the unused variable instead of commenting it?

// The following proposals require specific state to be set up first.
executeNSFunctionProposal,

// Fails with error: 1 defects in Proposal: There is no NervousSystemFunction with id: 1002
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know why we get this error now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants