-
Notifications
You must be signed in to change notification settings - Fork 42
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
ssb.friends.get Error #718
Comments
I'm seeing the exact same problem (and for the same reason) |
I forgot to include that this was with Node v14.17.1 on MacOS v11.2.3. I tried reinstalling Node completely, rolling it back to v12, and neither could get the instructions from the README to result in a working install. However, I was able to get Oasis running by using npm build and npm start on the source tree for v2.17.0. I would not count this as a solution though, because the listed instructions still do not work, even after I was able to get a successful install by building from source. |
Mine was Node v14.7.1 on MacOS v11.4 - i just saw there were a lot of errors in the oasis console - looks easy to replicate. |
Ran into this issue today as well. |
Did any of you find a way around this ? |
ugg - Anyone got suggestions for an alternative to Oasis that works with old patchwork database :-( (on current Node and OSX?) |
I'm getting the same error in a fresh |
Also getting it here with Node 15.5.0, Ubuntu 20.04.2. Unlike @analoglesbian I was not able to run the app from source (latest @ time of writing Looking at it now, node is still maxing out 4 CPUs with the erroring page in question open. It may just be that there is more data for Oasis yet to process. This would seem to be confirmed by a second error message being printed some time later (several minutes)-
I occasionally get |
Did you figure this out @pospi ? |
Yeah. The amusing workaround is to just run Patchwork in another window
*first*, then run Oasis, then open your browser. It needs to piggyback off
the Patchwork backend server 'cos its one appears to have problems.
…On Tue, 17 Aug 2021 at 10:44, Mitra Ardron ***@***.***> wrote:
Did you figure this out @pospi <https://github.com/pospi> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#718 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADK2JEEOZQF6YLXBHP2EGDT5GWG3ANCNFSM47RPKR7Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
--
writings <http://pospi.spadgos.com/> | twitter
<https://twitter.com/pospigos> | github <https://github.com/pospi> ← where
to find me
ValueFlows <https://www.valueflo.ws/> | Holo-REA
<https://github.com/holo-rea/> ← things I'm working on
|
That's hilarious @pospi - especially since the whole point is to get off of Patchwork because (according to the patchwork repo) its got problems and shouldn't be used. From the silence in this repo, I'm guessing Oasis's server isn't under active dev either, any suggestions for an alternative. |
I'm running into the same issue by following the instructions for building Oasis with Docker. |
This is caused by #715. In |
@nickwynja after running npm install [email protected], the next error I get is:
|
@nickwynja thanks. I was on node 16, and I just now tried switching to 14 and now its working 🌵 |
Even with this |
Any luck @nickwynja ? |
@mitra42 I wasn't able to solve the dependency issues but locally reverted back to the last commit hash that wasn't a dependabot automated merge. That was 4e8f742. You can check out this version doing |
Thanks Nick - I'll give that a go. I don't what the dev culture in this group is, but I'd have thought that maybe the package owner should revert out those dependabot merges for the "stable" version until someone has time to figure out the issues - I had to do that for one of the packages I'm admin for. |
That worked, and it looks like it picked up my id and follows etc from the old Patchwork DB I copied over.
Would you agree - and if so I wonder if I should do a Pull request on the README as, currently the install instructions (from npm) are incorrect for Mac users, and judging by the age of this bug it doesn't look like there is anyone with the skills and time to fix it? |
@christianbundy, can the breaking change be reverted? |
👍 I'd imagine either I or @nickwynja would merge a PR to revert this change. |
I can confirm that this error isn't related to patchwork. I was using oasis about a year ago and it was working without issues. I haven't used patchwork since then, yet I get this same error on most pages when running oasis now. I'm on node version
on a local git clone I can re-install oasis globally and re-start the oasis server. As others said before, this new build doesn't give the |
I got a solution in the code for using ssb-friends 5.0.0 (the one currently installed in the master branch)
I'll try to open a PR with it |
This is now fixed in the master branch. |
I just installed Oasis, since Patchwork is being sunsetted, and when I first launched it said it was processing my database, but once that finished, it gave me the following error message:
I've tried installing both the stable and unstable versions, and get this same error either way. Do I need to do anything special to import my Patchwork ssb database?
The text was updated successfully, but these errors were encountered: