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

No option to reindex in Settings #702

Open
SpencerDub opened this issue Jun 3, 2021 · 2 comments
Open

No option to reindex in Settings #702

SpencerDub opened this issue Jun 3, 2021 · 2 comments

Comments

@SpencerDub
Copy link

What's the problem you want solved?

Most immediately, many of my contacts appear in my feed with black squares as avatars, and for some, their display name is just the first few characters of their unique hash:

Oasis - No profile deets

To extend this into a slightly bigger issue, other users have suggested I fix this by reindexing, which they say I can do by going to Settings. Unfortunately, this doesn't work for me—I see no option to reindex under Settings:

Oasis - No reindex

System details

  • Oasis version: 2.17.0
  • Browser: Firefox 88.0.1
  • Running Oasis independently (not starting Patchwork first)
  • OS: Ubuntu 20.04.2 LTS
@rmdes
Copy link

rmdes commented Jun 20, 2021

It seems to be related to the Node version being used, with NVM you can switch from 16 to 15 to 14 and with each of these versions, the oasis UI behave differently, I'm having much better results running oasis on v15.

@wildthyme
Copy link

i’m having the same issue (no avis/names/etc., no index rebuild button), but for my case have found a quasi-workaround.

in all cases, i’m using oasis 2.17.0, node.js 14 on nixos, and running it independently from patchwork. the issue appears when i try to build it as a node2nix derivation and does not when i install it from npm directly—at which point i was able to rebuild the index. that settings region goes back to looking like the above screenshot if i switch back, though. i don’t expect this to be a solution for you, but only say it as additional information, and as evidence that it isn’t merely a matter of which node version is in use. is there some unavailable dependency it’s failing to announce? of course, i don’t want to keep using it directly from npm.

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

No branches or pull requests

3 participants