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

Error at storeChild.js:30:12 #246

Open
ExE-Boss opened this issue Jun 3, 2018 · 5 comments
Open

Error at storeChild.js:30:12 #246

ExE-Boss opened this issue Jun 3, 2018 · 5 comments
Labels

Comments

@ExE-Boss
Copy link

ExE-Boss commented Jun 3, 2018

The following error message is printed to the console whenever I interact with Mozilla Lightbeam since I upgraded to the WebExtension version:

17:47:36.447Error: UnknownError The operation failed for
reasons unrelated to the database itself and
not coveredby any other error code.
storeChild.js:30:12

This is likely coming from the call to the Dexie database library at store.js:179:

async getAll() {
const websites = await this.db.websites.filter((website) => {
return website.isVisible || website.firstParty;
}).toArray();
const output = {};
for (const website of websites) {
output[website.hostname]
= this.outputWebsite(website.hostname, website);
}
return output;
},

@princiya
Copy link
Collaborator

princiya commented Jun 3, 2018

@ExE-Boss Thank you for reporting the bug.

We had this error once, but was fixed. Looks like it is showing up again. I shall take a look when I have some time.

@Parikshit-Hooda
Copy link
Contributor

I want to work on this. But I can't replicate the said bug on my system. Please help me out.

@princiya
Copy link
Collaborator

@Parikshit-Hooda as mentioned in the above comment, this issue was seen in the beginning but was believed to have been solved.

However, you might be able to use some hints from this article to replicate the behaviour https://whotracks.me/blog/dexie_transaction_bug.html

@Parikshit-Hooda
Copy link
Contributor

So, maybe we can close this issue now.

@princiya
Copy link
Collaborator

Closing this issue isn't appropriate, until we know for sure this problem has been solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants