-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 IPFS local node in Brave Nightly 1.33.x on macOS 10.14 and 11.6, 1.33.34 on Windows 10 cycles power of network printer #19007
Comments
Also, please note that this does not happen with any version of Brave I tried in Windows - only macOS. I didn't test Linux per se, but I have a LinuxLite machine running Nightly and didn't notice the printer behavior. I'll do a quick test and post a followup comment if it affects the printer. |
Tested today on Linux Lite machine with no effect on printer:
Linux Lite: |
Either I had IPFS configured wrong or Nightly 1.33.34 just started doing this on Windows 10, so now it's a cross-platform issue. See https://community.brave.com/t/ipfs-cycles-network-printer-power-was-update-brave-nightly-cycles-network-printer-power/291260/16?u=hnktong I'll have to retest with Linux, too, to be sure. Sigh.
|
Still occurs with Nightly 1.33.37 on macOS and Windows 10.
|
Still occurs with Nightly 1.33.40 on macOS and Windows 10.
|
Still occurs with Nightly 1.33.40 on macOS and Windows 10.
|
Submitted ticket at IPFS project: |
Thank you. As this happens with IPFS Desktop as well, this is a problem with upstream go-ipfs, not Brave itself. |
@spylogsster Does Brave Nightly use go-ipfs v0.10.0, and do the other channels use go-ipfs v0.9.x or earlier? With IPFS Desktop, it appears to be go-ipfs v0.10.0 that triggers this printer reboot behavior; the earlier versions do not. |
v0.10 is used in all builds now |
UPDATE AFTER INITALLY POSTING THIS COMMENT: The printer was in some weird state where it responded to scan request, but when I went to it and checked it it cycled power and nagged me, and now Nightly and IPFS Desktop reboot the printer when launched with IPFS local node enabled, again.Well, @spylogsster, |
In the IPFS issue we determined that the issue is go-ipfs v0.10.0's mdns implementation in go-libp2p. Apparently, go-ipfs v0.11.0 will use random DNS labels that the devs think should solve this problem. |
@spylogsster i think this is solved since update to 0.11 (#20072) |
Description
Update 26 Oct. 16:13: Until about 10 minutes ago, I'd only experienced this on macOS, but either I had IPFS configured wrong or Nightly 1.33.34 just started doing this on Windows 10, so now it's a cross-platform issue. See https://community.brave.com/t/ipfs-cycles-network-printer-power-was-update-brave-nightly-cycles-network-printer-power/291260/16?u=hnktong I'll have to retest with Linux, too, to be sure. Sigh. end Update
Enabling IPFS local node cycles printer power only in Brave Nightly 1.33.x (at least as early as 1.33.7) as determined by testing current Dev, Beta, and Release somewhat extensively. Disabling and reenabling does it again. Disabling, relaunching Nightly, enabling IPFS local node does it again.
Also occurs when upgrading Nightly if IPFS is enabled local node when trigger upgrade.
Printer is Canon MX710 Series:
Initially I believed this to be power flickers, then noticed the behavior on updating Nightly, then tested with other Chromium-based browsers: none do this, and once IPFS was identified as primary suspect, abandoned testing of other browsers. Also see thread to which I posted in Community.
I used WireShark and PacketPeeper to record network activity during IPFS launch, which spikes quite a bit. Apart from recognizing acronyms and quantities of packets, the logs are fairly indecipherable to me, but I can share them if they would be helpful. I'd prefer to send them directly to a dev rather than post them here.
Steps to Reproduce
OR
With Nightly open with IPFS enabled local node and Upgrade notification appears:
Actual result:
Printer spontaneously reboots and nags that power was turned off improperly
Expected result:
Printer remains on and happy.
Reproduces how often:
Every time.
Brave version (brave://version info)
Please see Markdown log of experiments below.
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
In the log below, initially I tracked Brave Nightly on two machines, then when I expanded testing to Chromium (then-latest build via https://download-chromium.appspot.com/) and the different channels of Chrome and Opera, I focused on my daily workhorse, the 2012 MBP running macOS 10.14. Once IPFS was suspect and I learned that IPFS was in Dev, Beta, and Release, I abandoned the other browsers. This is why the log has empty spaces. That and I wanted to minimize time spent on this without slacking too much and I don't do this for a living, so please be gentle in any critique of the log.
Chromium-Based Browser Printer Log:
fbcf50401ae91125cef-refs/branch-heads/4638@{#816}
and 2015 13" MacBook Air
and WiFi
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
3e541cde5a91cb15b21f6e-refs/heads/main@{#933912}
0f49fffae22d2af419639e-refs/branch-heads/4677@{#1}
34ccdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
1671d219a59e29cf75e054-refs/branch-heads/4606@{#1320}
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
16269ed6dbf895ce5d3f-refs/heads/main@{#934186}
Yes - when enabled IPFS, which I subsequently disabled in prep for next update
Note that this is the same version of Chromium as 1.33.24 through 1.33.27
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
cdbaea45b4c86ce543e-refs/branch-heads/4638@{#871}
Note that this is the same version of JavaScript as 1.33.24 through 1.33.27
Yes - when then enabled IPFS (local node as before), which I subsequently disabled in prep for next update
After doing testing with Dev and Beta, relaunched Nightly, disabled IPFS, enabled to local node, printer reset.
No when enable
No when set Fallback to public gateway
No when add extension
fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU=
fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU=
fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU=
fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU=
MaximumInlineContentAdsPerHour=8/MaximumInlineContentAdsPerDay=40
MaximumInlineContentAdsPerHour=8/MaximumInlineContentAdsPerDay=40
MaximumInlineContentAdsPerHour=8/MaximumInlineContentAdsPerDay=40
The text was updated successfully, but these errors were encountered: