Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Indexes on master aren't being saved #935

Closed
christianbundy opened this issue Feb 5, 2019 · 9 comments
Closed

Indexes on master aren't being saved #935

christianbundy opened this issue Feb 5, 2019 · 9 comments
Assignees
Labels

Comments

@christianbundy
Copy link
Contributor

I'm not sure what's going on, but it basically goes like this:

  1. Open Patchwork and see that it's "indexing database..."
  2. Run ssb-server status and see that Patchwork-specific views are behind
  3. Wait
  4. Run ssb-server status and see that views are almost up-to-date
  5. Wait a bit more
  6. Run ssb-server status and see that it can't connect to ssb-server
  7. Look at Patchwork and see that it still says "indexing database..."
  8. Close out of Patchwork
  9. GOTO 1 (indexes are somehow back to where they started)
$ ssb-server status
{
  "progress": {
    "indexes": {
      "start": 371470125,
      "current": 495540217,
      "target": 533459552
    },
    "ebt": {
      "start": 0,
      "current": 52,
      "target": 52
    }
  },
  "sync": {
    "since": 533459552,
    "plugins": {
      "last": 533459552,
      "keys": 533459552,
      "clock": 533459552,
      "time": 533459552,
      "feed": 533459552,
      "backlinks--oaWWDs8g": 533459552,
      "private--oaWWDs8g": 533459552,
      "query": 533459552,
      "search": 533459552,
      "tags": 410253896,
      "patchwork-subscriptions": 410253896,
      "patchwork-channels": 410253896,
      "patchwork-contacts": 410253896
    },
    "sync": false
  },
  "rest of the output": "removed :)"
}

screenshot from 2019-02-05 14-47-39

$ ssb-server status
Error: Could not connect to ssb-server :::8008
Use the "start" command to start it.
Use --verbose option to see full error
@christianbundy
Copy link
Contributor Author

The workaround seems to be "open and close Patchwork about 10 times, very quickly, and eventually when you open it'll have all of the indexes done". WTF. I'm suspicious that a view is returning a bad since somewhere.

@christianbundy
Copy link
Contributor Author

🤷‍♂️

@christianbundy
Copy link
Contributor Author

I found it!

👨‍🔬

flumedb/flumeview-reduce#11

@christianbundy christianbundy removed their assignment Oct 26, 2019
@stale
Copy link

stale bot commented Jan 24, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Jan 24, 2020
@black-puppydog
Copy link
Contributor

hasn't been fixed upstream and still annoying. yeah, relevant to me.

@stale stale bot removed the stale label Jan 24, 2020
@stale
Copy link

stale bot commented Apr 23, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Apr 23, 2020
@christianbundy
Copy link
Contributor Author

My stab at the solution is here: flumedb/flumeview-reduce#12

Unfortunately I don't have energy to continue on it. :/

@stale
Copy link

stale bot commented Jul 23, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@stale stale bot added the stale label Jul 23, 2020
@christianbundy christianbundy self-assigned this Jul 23, 2020
@stale stale bot removed the stale label Jul 23, 2020
@black-puppydog
Copy link
Contributor

By now flumedb/flumeview-reduce#16 is merged, allowing any flumeview-reduce index to make periodic writes. Now "all" that is left for patchwork is to find all the relevant views, and initialize them with periodic writes! Easy as pie! :)

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

No branches or pull requests

2 participants