-
Notifications
You must be signed in to change notification settings - Fork 865
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
TypeError: ctx.manualCheckForUpdates is not a function #1705
Comments
Thanks, @tonuonu - we'll look into this in our next weekly triage. |
Hi @tonuonu -- quick question. What were you doing when this error happened? Do you mind attaching your logs? |
Hi @tonuonu -- just checking in about previous question, thanks! |
Hi! Sorry about delay. Was overworking and then missed flight and now have jet lag.
I been thinking long how to help you because I do not remember much about what I was exactly doing. And such accurate input is crucial. So my best as I remember:
1. This is brand new Mac, IPFS daemon was possibly installed separately before IPFS Desktop.
2. Everything was stock setup and my aim was to command over port 5001 API which by default listens 127.0.0.1 only
3. If anything, then I possibly changed 5001 ACL to 0.0.0.0 or external IP because I might wanted to access it from other laptop. I might screwed up something, I am not sure anymore.
4. IPFS Desktop kept complaining and offered “restart IPFS desktop” as a way to resolve. When pressed “restart” I got the error I submitted. It was reputable, I submitted just one example.
5. Things went back to normal after I deleted config file from .ipfs directory.
If I somehow find any factual tracks, I tell you. Right now this is all I remember.
Tõnu
… On Nov 2, 2020, at 18:10, Jessica Schilling ***@***.***> wrote:
Hi @tonuonu <https://github.com/tonuonu> -- just checking in about previous question, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1705 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAF5QKNAHY6CKB7M7UQ4MNLSN3KYFANCNFSM4S662WQA>.
|
@tonuonu - that's a great start, thanks! @lidel and @rafaelramalho19 - any ideas? |
Hi @tonuonu - we're unfortunately unable to reproduce this and can't get much further without the config that it sounds like you've deleted. Closing for now, but please be in touch if you experience any similar problems. In case anyone reading this runs across this issue again - please reply and attach/excerpt your config file. |
Thank You! I try to report if I know something.
…On Mon, 2020-11-09 at 08:18 -0800, Jessica Schilling wrote:
Hi @tonuonu - we're unfortunately unable to reproduce this and can't
get much further without the config that it sounds like you've
deleted. Closing for now, but please be in touch if you experience
any similar problems.
In case anyone reading this runs across this issue again - please
reply and attach/excerpt your config file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Please describe what you were doing when this error happened.
Specifications
Error
The text was updated successfully, but these errors were encountered: