1
Solved

Some pages still do not seem to be indexed

Right now, I looked for some words of this page:

Wikipedia, "Brutus of Troy".

Visited the page yesterday.

After not finding the content with memex, I visited again today. Refreshed it several times. Even moved it to another open session.

No sucess. Content not foundt by memex.

Not good. I intended to rely on this service.

5 replies

This problem should have been fixed with the new implementation of the search engine. 
Sorry for causing troubles. Really annoying if stuff like that happens :(

Hey Oliver, on my Windows machine, there's no error.

On my Mac, with the same Chrome configuration and extensions (synced), I get this error:

i {type: "ReadError", name: "ReadError", cause: Event, message: undefined, stack: "ReadError↵    at IDBRequest.<anonymous> (chrome-ex…hjpmblaafnpgjppbmioombali/background.js:1:345894)"}
cause
:
Event
bubbles
:
true
cancelBubble
:
false
cancelable
:
true
composed
:
false
currentTarget
:
null
defaultPrevented
:
false
eventPhase
:
0
isTrusted
:
true
path
:
[]
returnValue
:
true
srcElement
:
IDBRequest
error
:
DOMException: Failed to read large IndexedDB value
onerror
:
ƒ (t,n)
onsuccess
:
ƒ (e)
readyState
:
"done"
result
:
undefined
source
:
IDBObjectStore
autoIncrement
:
false
indexNames
:
DOMStringList {length: 0}
keyPath
:
null
name
:
"worldbrain-terms"
transaction
:
IDBTransaction {objectStoreNames: DOMStringList, mode: "readonly", db: IDBDatabase, error: DOMException: Failed to read large IndexedDB value, onabort: ƒ, …}
__proto__
:
IDBObjectStore
transaction
:
IDBTransaction {objectStoreNames: DOMStringList, mode: "readonly", db: IDBDatabase, error: DOMException: Failed to read large IndexedDB value, onabort: ƒ, …}
__proto__
:
IDBRequest
target
:
IDBRequest {result: undefined, error: DOMException: Failed to read large IndexedDB value, source: IDBObjectStore, transaction: IDBTransaction, readyState: "done", …}
timeStamp
:
467267.9000000001
type
:
"error"
__proto__
:
Event
message
:
undefined
name
:
"ReadError"
stack
:
"ReadError↵    at IDBRequest.<anonymous> (chrome-extension://abkfbakhjpmblaafnpgjppbmioombali/background.js:1:345894)"
type
:
"ReadError"
__proto__
:
Error

Promise.catch (async)
(anonymous) @ background.js:1
n @ background.js:1
(anonymous) @ background.js:1
e.(anonymous function) @ background.js:1
a @ background.js:1
(anonymous) @ background.js:1
Promise.then (async)
a @ background.js:1
(anonymous) @ background.js:1
t @ background.js:1
(anonymous) @ background.js:1
(anonymous) @ background.js:1
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
dispatchArgs @ extensions::event_bindings:260
dispatchEvent @ extensions::event_bindings:269

Ouch! This is a critical bug. We had it happening once but could not reproduce it. 
Unfortunate for you, but great that we have found this error again. 

It means that the indexedDB is locked and we can't store the content, only the title. 

With the next upgrade we change our storage approach and hopefully this will not happen anymore. Bear with us through this next transition :(

I will send this to our devs immediately. 

Sorry about all the hastle the extension causes for you and thanks for your constant constructive input. 

I'm also seeing this behavior on some pages, e.g. https://open.nytimes.com/building-a-text-editor-for-a-digital-first-newsroom-f1cb8367fc21

This page is showing up in my index (visited yesterday), but any search for text on the page shows 0 results.

That is weird, it works fine with me :(

Which other pages does this happen with?

Can you try and open the console to show what is there? That will help coming up with a solution. 
You need to go to chrome://extensions, open details of Memex and then search for the "background page". The window that opens, you need to open the tab "console" and share with me what it says when you visit websites, and especially the one you sent me. 

No, don´t know how to access the console logs.

Could you tell me? 

Before skyping - thanks for offering -, I would hope they might give you an idea where the issue stems from.

This understandably sucks. 

Can you share your system configuration with me?
Do you know how to access the console logs of the extension, so we can find out what the problem is?

If you are free, now or another time, we can have a short skype session and go through it together. 

This should not happen, and is super annoying i agree. 

You can add me here: realworldbrain

See you in a bit!