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

Check atom exists in graph when deciding to read from disk #1371

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

mblaney
Copy link
Contributor

@mblaney mblaney commented Apr 4, 2024

No description provided.

@amark
Copy link
Owner

amark commented Apr 4, 2024

oh GOSH why didn't I think about this? I have similar code in a branch in GUN core to fix, but was worried about side effects and wasn't confident about my coverage/tests on it. I didn't think to add it straight to here where the bugginess is which is much cleaner & safer to do.

The only edge case/problem this could cause is increased disk ops, but this is self-checking since it verifies against the graph so when it does get pulled in-memory so I 100% confidently ready to immediately pull this. 🎉 🔥 👏

@amark amark merged commit 1c095b1 into amark:master Apr 4, 2024
@amark
Copy link
Owner

amark commented Apr 4, 2024

@mblaney I'd like to do an emergency (sigh, year-ish late) NPM publish for this.

Some issues need to consider: GitHub main is on a major version change vs NPM has to stay pegged to a prior version branch, so to NPM publish I need to make a fork from old & patch your 1 change - willing to get on a call with me to do this? Cause I also want to run it thru your/ @Azarattum 's / Snoobeedoo gustavcorpas test, so can properly close them knowing they're isolated to just this (vs other) bug fix.

@mblaney
Copy link
Contributor Author

mblaney commented Apr 5, 2024

hi @amark yep happy to do that

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.

None yet

2 participants