Skip to content

Conversation

MacKenzieHnC
Copy link

@MacKenzieHnC MacKenzieHnC commented Jan 1, 2023

Explanation

The issue stemmed from two separate places.

  1. .GetResults() seems to have been used as an attempted await, but does not function that way. Replaced with .get() which does.
  2. The original author considered it a failure state if the database already existed. They had set FailIfExists on the copy function, which is correct if you don't want to overwrite, but then they were returning without loading the database at all if that error fired. Replaced with a check for the error thrown by FailIfExists, which is ignored, while retaining error-checking for other types of failures (although I don't know what those would be).

Resolutions

resolves #519, resolves #491, resolves #487, resolves #451

mackenzie and others added 3 commits January 1, 2023 14:11
Include Windows pre-populated instructions
(If the db already exists, that's not a problem)
Works as suggested without change

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