-
Notifications
You must be signed in to change notification settings - Fork 3
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
*.db file is empty, tables empty #5
Comments
I will look into this; perhaps an internal of Gun change. |
Hmm, I had some issues getting visual studio 17 to work again (I had uninstalled it end of last year); finally was able to update to the latest gun (2020.301) and, it seems the writes are stalled for some reason; so actually nothing ends up getting any data back in either. |
Ok, thanks for looking into this. Glad you replicated the issue. Will be
on standby..
…On Mon, Mar 23, 2020 at 8:42 AM Jim B ***@***.***> wrote:
Hmm, I had some issues getting visual studio 17 to work again (I had
uninstalled it end of last year); finally was able to update to the latest
gun (2020.301) and, it seems the writes are stalled for some reason; so
actually nothing ends up getting any data back in either.
Will look into this in a bit; have a few other projects that are going to
distract me first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHANR2BBUWH2OQVOVRKARCTRI57MPANCNFSM4LQ7WLKQ>
.
|
Hi. I'm getting an empty SQLite file and empty tables when running default config and/or sack.vfs. Appears the data is in memory, but not writing to SQLite file.. the
*.db
file doesn't appear to write to disk after put events. When should this persist to disk?Example:
Env:
The text was updated successfully, but these errors were encountered: