Skip to content
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

F/OS-1224 Multisig approvers not appearing in past proposals #575

Merged
merged 6 commits into from
Apr 29, 2024

Conversation

josemarinas
Copy link
Contributor

@josemarinas josemarinas commented Apr 17, 2024

Description

Some approvers did not appear as approvers on past proposals after they've been removed from the multisig because the entity for the multisift members and approvers was related.

This fixes this issue using the solution discussed here: https://www.notion.so/aragonorg/Subgraph-Bug-Approvers-Query-Breaks-Multisig-Subgraph-d783e196ba464595974ba2a9d2dac80a#5ca1bd831bbd4dc191dd8fb0d4360e8f

Task ID: OS-1224

Playground: https://subgraph.satsuma-prod.com/aragon/osx-test-members-bug-mainnet/version/5/playground

Type of change

See the framework lifecycle in packages/contracts/docs/framework-lifecycle to decide what kind of change this pull request is.

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • My changes generate no new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I ran all tests with success and extended them if necessary.
  • I have updated the CHANGELOG.md file in the root folder.
  • I have updated the DEPLOYMENT_CHECKLIST file in the root folder.
  • I have updated the UPDATE_CHECKLIST file in the root folder.
  • I have updated the Subgraph and added a QA URL to the description of this PR.

Copy link
Contributor

@clauBv23 clauBv23 left a comment

Choose a reason for hiding this comment

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

let some comments

packages/subgraph/schema.graphql Show resolved Hide resolved
packages/subgraph/src/packages/multisig/multisig.ts Outdated Show resolved Hide resolved
@clauBv23
Copy link
Contributor

Since there is a branch for removing all plugins, multisig included, f/split-linting, not sure if this should be done only in this repo

@josemarinas
Copy link
Contributor Author

Since there is a branch for removing all plugins, multisig included, f/split-linting, not sure if this should be done only in this repo

Yes, this should also be done in the split repo, but i wanted to first get the fix reviewed and then aply it also to the other repo

packages/subgraph/schema.graphql Show resolved Hide resolved
packages/subgraph/schema.graphql Outdated Show resolved Hide resolved
packages/subgraph/src/packages/multisig/multisig.ts Outdated Show resolved Hide resolved
packages/subgraph/src/packages/multisig/multisig.ts Outdated Show resolved Hide resolved
packages/subgraph/tests/multisig/multisig.test.ts Outdated Show resolved Hide resolved
@josemarinas
Copy link
Contributor Author

@clauBv23 I fixed the lint missues that you mentioned, I also took the librety some others that popped up when I ran yarn lint. I also updated the description in the schema.graphql

@josemarinas josemarinas merged commit 9f18598 into develop Apr 29, 2024
16 checks passed
@josemarinas josemarinas deleted the f/OS-1224-fix-multisig-members-bug branch April 29, 2024 06:48
Rekard0 pushed a commit that referenced this pull request May 17, 2024
* fix: multisig members not appearing in past proposals

* wip

* chore: update schema and methods

* Update packages/subgraph/schema.graphql

Co-authored-by: Jordan <[email protected]>

* style: fix lint warnings

* docs: improve graphql schema comments

---------

Co-authored-by: Jordan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants