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

fix(manifest): resolve node persistence after removal #4819

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

asabya
Copy link

@asabya asabya commented Sep 13, 2024

Checklist

  • I have read the coding guide.
  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

This PR fixes #4808. Where loading a manifest then removing forks from it would not persist in the next load.

Copy link
Member

@zelig zelig left a comment

Choose a reason for hiding this comment

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

very neat find. please simplify by just nil-ing the ref field

pkg/manifest/mantaray/persist.go Outdated Show resolved Hide resolved
pkg/manifest/mantaray/node.go Show resolved Hide resolved
@gacevicljubisa gacevicljubisa changed the title Mantaray manifest remove fork fix(manifest): resolve node persistence after removal Nov 25, 2024
@gacevicljubisa
Copy link
Contributor

@asabya this is the guide for commit msgs, linter will not allow merge if msgs are not in correct format. Currenltly this commit msg is not in correct format

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.

Mantaray removed entry still persists
3 participants