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(gatsby): use lmdb.removeSync so getNode can't return deleted nodes (#33554) #33633

Merged
merged 1 commit into from
Oct 22, 2021

Conversation

vladar
Copy link
Contributor

@vladar vladar commented Oct 22, 2021

Backport #33554 to release/3.14 release branch.

(cherry picked from commit 98a843c)

# Conflicts:
#	packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts

#33554)

Co-authored-by: Ward Peeters <[email protected]>
(cherry picked from commit 98a843c)

# Conflicts:
#	packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Oct 22, 2021
@vladar vladar added type: cherry and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Oct 22, 2021
@vladar
Copy link
Contributor Author

vladar commented Oct 22, 2021

Oh well, gatsby-dev-cli now fails with Node12 in v3 test. Gonna ignore test failures as this backport only touches the experimental codepath in v3.

@vladar vladar merged commit d4cf891 into release/3.14 Oct 22, 2021
@vladar vladar deleted the backport-3.14-33554 branch October 22, 2021 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants