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

Enabling IPNS pubsub via daemon flags #1828

Closed
jakasi2 opened this issue Jun 2, 2021 · 5 comments
Closed

Enabling IPNS pubsub via daemon flags #1828

jakasi2 opened this issue Jun 2, 2021 · 5 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@jakasi2
Copy link

jakasi2 commented Jun 2, 2021

OS: Windows 10 Home 21H1 - build 19043.985
IPFS Desktop 0.15.0

  • agent: go-ipfs v0.8.0
  • UI: v2.12.2

Bug description
Cannot enable IPNS pubsub with --enable-namesys-pubsub daemon flag. Flag is added as noted in Which flags does IPFS Desktop boot with? .

The GUI (cube) flashes 2-3 times and then continues as nothing happened. Desired feature is still disabled - using ipfs name pubsub state . File config.json automatically resets to default configuration.

To Reproduce
The flag --enable-namesys-pubsub is added to a file C:\Users\<user>\AppData\Roaming\IPFS Desktop\config.json .
It doesn't matter in which position it is added. It only causes a more severe logdump if it is added directly after flag --routing .

Command failed with exit code 1: C:\Users\<user>\AppData\Local\Programs\IPFS Desktop\resources\app.asar.unpacked\node_modules\go-ipfs\go-ipfs\ipfs.exe daemon --migrate --enable-gc --routing --enable-namesys-pubsub dhtclient
Error: expected 0 argument(s), got 1

Expected behavior
I am not sure what the expected behavior is, probablly the feature being enabled. I am trying to get familiar with IPNS PubSub atm.

Logs
Faulty log

2021-06-02T19:31:46.657Z info: [meta] logs can be found on C:\Users\<user>\AppData\Roaming\IPFS Desktop
2021-06-02T19:31:48.226Z info: [web ui] window ready
2021-06-02T19:31:48.226Z info: [web ui] navigate to /
2021-06-02T19:31:48.242Z info: [tray] starting
2021-06-02T19:31:48.459Z info: [tray] started
2021-06-02T19:31:48.460Z info: [ipfsd] start daemon STARTED
2021-06-02T19:31:48.947Z info: [daemon] removing api file
2021-06-02T19:31:49.899Z info: [ipfsd] start daemon FINISHED 1.4393155000004918s
2021-06-02T19:31:50.047Z info: [automatic gc] enabled
2021-06-02T19:31:50.048Z info: [pubsub] disabled
2021-06-02T19:31:50.060Z info: [ipfsd] stop daemon STARTED
2021-06-02T19:31:50.120Z info: [ipns over pubsub] disabled
2021-06-02T19:31:50.126Z info: [ipfs on path] no action taken
2021-06-02T19:31:50.126Z info: [launch on startup] disabled
2021-06-02T19:31:50.149Z info: [ipfsd] stop daemon FINISHED 0.08913480000011623s
2021-06-02T19:31:50.215Z info: [ipfsd] start daemon STARTED
2021-06-02T19:31:50.350Z info: [daemon] removing api file
2021-06-02T19:31:51.239Z info: [ipfsd] start daemon FINISHED 1.0239555999990553s
2021-06-02T19:31:52.582Z info: [updater] update not available
2021-06-02T19:33:42.005Z info: [ipfsd] stop daemon STARTED

Additional context
I am exploring a distributed app idea. Users would periodically upload/make available some data via IPFS. Service would use IPNS to log/retrieve the latest submission. IPNS PubSub would be used to notify the service of new IPNS mapping. For now, users would use IPFS Desktop as their gateway, since it provides a nice GUI, makes IPFS more familiar to them. Later go-ipfs daemon could be included in a seperate executable. As noted in the documentation both the users and the service provider need to have the IPNS PubSub enabled in order for it to work as intended.

@jakasi2 jakasi2 added the need/triage Needs initial labeling and prioritization label Jun 2, 2021
@welcome
Copy link

welcome bot commented Jun 2, 2021

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@andrasfuchs
Copy link

I might be misunderstand your request, but isn't this option available in the Tray Icon / Settings / Experiments menu?

image

@jakasi2
Copy link
Author

jakasi2 commented Jun 9, 2021

Thank you for the reply. I wasn't aware of the tray option. I found only CLI flag way of doing it.

Since there are some issues with Electron tray and Linux distros it might not work on Linux. Is there any filtering of options/flag when the daemon is launched with IPFS Desktop. I tried the flags from the command line and it worked, it was just when the daemon was started via IPFS Desktop there was issues.

@andrasfuchs
Copy link

I'm just a regular user and I'm not too familiar with CLI flags or IPFS on Linux, sorry!

@lidel
Copy link
Member

lidel commented Jun 18, 2021

I'm closing this because the error was caused by manually changing config.json and introducing bug that way.

Note that ipfs.exe daemon --migrate --enable-gc --routing --enable-namesys-pubsub dhtclient has dhtclient which is not a valid parameter, should be --routing dhtclient

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

3 participants