You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't been able to debug this completely, but I wanted to make a note (and a TODO for future me) that when running flumeview.rebuild() on this plugin it just remains at -1 until you restart ssb-server, at which point it indexes correctly. I've noticed this in the last view from ssb-db and the contacts2 view from ssb-friends.
The text was updated successfully, but these errors were encountered:
The only caveat is that two indexes, `last` and `contacts2`, depend on
flumeview-reduce, which seems to require a restart after
`flumeview.rebuild()` before indexing starts again.
See flumedb/flumeview-reduce#10
Also, this throws a handful of "errors" when the rebuild request is
started, but they seem to be harmless. I'll add the errors as a comment
in the PR (#4).
hmm, interesting. the thing we really need here is test coverage for this, and things like this.
every flumeview implements rebuild. I've been thinking about this again after setting up integration tests for the ssb stack. Nothing there tests the rebuild stuff though.
Started adding rebuild() tests to SSB-DB and I noticed that all but one view is finishing the rebuild process. After some investigation, I found this issue again -- woo! Gonna work on this a bit.
I haven't been able to debug this completely, but I wanted to make a note (and a TODO for future me) that when running
flumeview.rebuild()
on this plugin it just remains at-1
until you restart ssb-server, at which point it indexes correctly. I've noticed this in the last view from ssb-db and the contacts2 view from ssb-friends.The text was updated successfully, but these errors were encountered: