#pouchdb

/

      • slackbot has quit
      • slackbot joined the channel
      • NOTICE: [pouchdb] nolanlawson opened pull request #6368: (#6366) - fix $or/$nor without explicit $eq (master...6366) https://git.io/vSUei
      • NOTICE: [pouchdb] nolanlawson opened pull request #6369: (#6369) - pouchdb-find debugs correctly (master...pouchdb-find-debug) https://git.io/vSUe7
      • NOTICE: [pouchdb] nolanlawson opened pull request #6370: (#6370) - fix building of plugins in dev mode (master...fix-dev-mode-build) https://git.io/vSUfI
      • slackbot
        <jnax> I found this project helped me wrap my head around pouchdb along with nolan's todo youtube video where he gives me vertigo with the zoom feature
      • <jnax> id want to do a video of my project once i can get it working but i'm pretty n00b so it may take me a few weeks
      • wendall9111 joined the channel
      • wendall911 has quit
      • <jnax> Also, what do you guys think of GunDB?
      • m-i has quit
      • <mikeymckay> Hi Pouchers - I am getting a document update conflict when I try and destroy() a database. Any advice? I am stuck because this error seems to block the database from being removed: message: "Document update conflict", name: "conflict", status: 409
      • <jan> something is off there. a db delete can’t issue a document update.
      • <jan> either the wrong error message bubbles up, or you are doing a doc update somewhere
      • <mikeymckay> I am just destroying from the command line:
      • <mikeymckay> I should say, from the javascript console.
      • <garrensmith> @mikeymckay what are you doing after your destroy?
      • <mikeymckay> Nothing. I immediately see a Promise printed, and then the error message.
      • <garrensmith> And is your app doing anything while you trying to delete?
      • <mikeymckay> I don't think so.
      • <mikeymckay> I am using crypto-pouch - but even if I comment out the require to load crypto-pouch I get the same error message upon deletion
      • m-i joined the channel
      • <jan> maybe crypto-pouch overloads destroy()?
      • m-i has quit
      • robfraz joined the channel
      • NOTICE: [pouchdb] blahah opened pull request #6372: Update to leveldown@1.5.1 (master...master) https://git.io/vSU2G
      • <jan> Doesn't look like it
      • <jan> @mikeymckay maybe enable DEBUG logging and see what's going on
      • <mikeymckay> How do I enable DEBUG loggig?>
      • <mikeymckay> Got it: PouchDB.debug.enable('*');
      • <mikeymckay> Ahh - I got it
      • <mikeymckay> I am also using the pouchdb-all-dbs plugin
      • <mikeymckay> When I remove that, then the problem goes away
      • <mikeymckay> DEBUG logging FTW. Thanks!
      • basiclaser joined the channel
      • <jan> ;)
      • robfraz has quit
      • robfraz joined the channel
      • robfraz has quit
      • robfraz joined the channel
      • robfraz has quit
      • robfraz joined the channel
      • RangerRick has quit
      • m-i joined the channel
      • RangerRick joined the channel
      • NOTICE: [pouchdb] nolanlawson closed pull request #6372: Update to leveldown@1.5.1 (master...master) https://git.io/vSU2G
      • m-i has quit
      • m-i joined the channel
      • <nolanlawson> just so everyone knows, IE10 is our most “fail-y” test in Travis by far. Safari and coverage also occasionally fail, but not nearly as much as IE 10
      • m-i_ joined the channel
      • <nolanlawson> unfortunately travis_retry only helps a little, so it still requires restarting. I’ve been using: https://gist.github.com/nolanlawson/7b7961b49b7...
      • <nolanlawson> I’ve also looked into other MS browsers but they all fail for various reasons. I tried to get Edge 14 running but it failed consistently, and I couldn’t reproduce the failure locally
      • <nolanlawson> I’ll try again when Edge 15 is out but it may be some issue with SauceLabs’ Windows support. not sure
      • m-i has quit
      • m-i_ has quit
      • m-i joined the channel
      • m-i has quit
      • wendall9111 has quit