Right now, running locally, every action from the Meteor CLI in OSX throws this exception:
> /Users/mallorym/.meteor/packages/meteor-tool/.1.1.3.1d614zp++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245 throw(ex);
> Error: SQLITE_CORRUPT: database disk image is malformed
> at Object.Future.wait (/Users/mallorym/.meteor/packages/meteor-tool/.1.1.3.1d614zp++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:395:18)
> at runOnce (/Users/mallorym/.meteor/packages/meteor-tool/.1.1.3.1d614zp++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/tools/catalog-remote.js:237:21)
If I understand, this means that the package manager uses SQLite, but mine is broken somehow
You can see where Meteor package manager / CLI uses SQLite here.
How to fix? Can I use the SQLite CLI to reset somehow?
Not that this isn’t nice and all but I’m always wondering
a) how you guys are finding these threads from years back and
b) why you bother replying to them?
Google search turns it up.
why bother replying? It is still an issue that still happens in some circumstances.
It just happened to me and I found this less intrusive solution that maybe others would benefit from.