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

Tests fail with [email protected] #78

Open
gr2m opened this issue Sep 15, 2015 · 8 comments
Open

Tests fail with [email protected] #78

gr2m opened this issue Sep 15, 2015 · 8 comments

Comments

@gr2m
Copy link
Member

gr2m commented Sep 15, 2015

follow up for #75 (comment)

Just checked it locally and could reproduce it with [email protected], but not with 4.0.1. @NickColley are you looking into this already? It must have be something with the db.destroy() call here: https://github.com/hoodiehq/pouchdb-hoodie-api/blob/master/clear.js#L11

@gr2m
Copy link
Member Author

gr2m commented Sep 15, 2015

fyi: pouchdb/pouchdb#4339

@NickColley
Copy link
Contributor

@gr2m think it's todo with the stateless constructor but yeah I ran into the same thing.

@gr2m
Copy link
Member Author

gr2m commented Sep 16, 2015

Okay, so a way around this would be to re-initialize the db instance on destroy. In the hoodie API, we don't have the option to manually re-initialize the hoodie.store API, so it must happen auto-magically ™️

No idea how though

@gr2m
Copy link
Member Author

gr2m commented Sep 16, 2015

Is there a an alternative to db.destroy without performance issues in PouchDB?

@NickColley
Copy link
Contributor

We have:

Unless we can implement purge I'd think we'd have to re instantiate the database ourselves.

@NickColley NickColley self-assigned this Feb 1, 2016
@NickColley
Copy link
Contributor

Okay, we throw an error in PouchDB now, so this will mean this test wont hang any more.

@gr2m
Copy link
Member Author

gr2m commented Feb 24, 2016

could you check locally? Is the new PouchDB version out yet?

@nolanlawson
Copy link
Member

No, it's not released yet. But 5.3.0 should have the fix.

@NickColley NickColley removed their assignment Sep 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants