Describe the bug
As long as Anytype is opened, my HDD seems constantly to be writing and my logging system is spammed with some messages of type “logger:netqueue, caller:queue/ff.go, msg : …a service-key is required to request logs”
Here is an extract :
janv. 26 23:49:57 ubuntu-i5 systemd[4725]: gnome-launched-google-chrome.desktop-26475.scope: Succeeded.
janv. 26 23:51:19 ubuntu-i5 dbus-daemon[4736]: [session uid=1000 pid=4736] Activating service name='org.gnome.Nautilus' requested by ':1.38' (uid=1000 pid=4986 comm="/usr/bin/gnome-shell " label="unconfined")
janv. 26 23:51:19 ubuntu-i5 dbus-daemon[4736]: [session uid=1000 pid=4736] Successfully activated service 'org.gnome.Nautilus'
janv. 26 23:51:20 ubuntu-i5 nautilus[26644]: Called "net usershare info" but it failed: L’exécution du processus fils « net » a échoué (No such file or directory)
janv. 26 23:51:31 ubuntu-i5 org.gnome.Nautilus[26669]: 23:51:31.519 › Config: {
janv. 26 23:51:31 ubuntu-i5 org.gnome.Nautilus[26669]: "channel": "latest",
janv. 26 23:51:31 ubuntu-i5 org.gnome.Nautilus[26669]: "theme": ""
janv. 26 23:51:31 ubuntu-i5 org.gnome.Nautilus[26669]: }
janv. 26 23:51:32 ubuntu-i5 org.gnome.Nautilus[26669]: Channel: latest
janv. 26 23:51:35 ubuntu-i5 org.gnome.Nautilus[26746]: mw jsaddon:
janv. 26 23:51:36 ubuntu-i5 org.gnome.Nautilus[26669]: (node:26669) UnhandledPromiseRejectionWarning: Error: An object could not be cloned.
janv. 26 23:51:36 ubuntu-i5 org.gnome.Nautilus[26669]: at EventEmitter.t.ipcRendererInternal.send (node:electron/js2c/renderer_init:85:328)
janv. 26 23:51:36 ubuntu-i5 org.gnome.Nautilus[26669]: at EventEmitter.<anonymous> (node:electron/js2c/renderer_init:81:357)
janv. 26 23:51:36 ubuntu-i5 org.gnome.Nautilus[26669]: (Use `anytype2 --trace-warnings ...` to show where the warning was created)
janv. 26 23:51:36 ubuntu-i5 org.gnome.Nautilus[26669]: (node:26669) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
janv. 26 23:51:42 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:51:42.342+0400","logger":"anytype-mw-api","caller":"core/account.go:491","msg":"AccountSelect app start takes 3176ms: map[anytype:459 blockService:0 builtinobjects:0 builtintemplate:12 configfetcher:47 datastore:2240 docService:0 filepin:0 filestore:0 fts:137 gateway:0 indexer:5 ipfs:206 objectstore:0 process:0 status:0 subscription:0 threads:70]"}
janv. 26 23:51:42 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:51:42.706+0400","logger":"anytype-mw-configfetcher","caller":"configfetcher/configfetcher.go:104","msg":"failed to update simultaneous requests: number of simultaneous requests is too small: 0"}
janv. 26 23:51:43 ubuntu-i5 org.gnome.Nautilus[26746]: failed to write to gelf: bad write (0/611)
janv. 26 23:52:37 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:52:37.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybaqiyh7gb3lingdwdowgf2jlcjwuxadvzhe3hbxrveps2x5mse4vt] failed: getting offsets for thread bafybaqiyh7gb3lingdwdowgf2jlcjwuxadvzhe3hbxrveps2x5mse4vt failed: thread not found"}
janv. 26 23:52:38 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:52:38.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybaqiyh7gb3lingdwdowgf2jlcjwuxadvzhe3hbxrveps2x5mse4vt] failed: a service-key is required to request logs"}
janv. 26 23:54:04 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:54:04.424+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybatcw3oz67fw72aucdozcqo4hwcxhyahs5h7qivbncqrnl5s2w5qk] failed: a service-key is required to request logs"}
janv. 26 23:54:04 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:54:04.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybatcw3oz67fw72aucdozcqo4hwcxhyahs5h7qivbncqrnl5s2w5qk] failed: getting offsets for thread bafybatcw3oz67fw72aucdozcqo4hwcxhyahs5h7qivbncqrnl5s2w5qk failed: thread not found"}
janv. 26 23:55:50 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:55:50.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybakl7urr353tmd72ouuadjo7s5sctuk4tz5jo6es24iqcwwlbdxxw] failed: a service-key is required to request logs"}
janv. 26 23:55:50 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:55:50.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybakl7urr353tmd72ouuadjo7s5sctuk4tz5jo6es24iqcwwlbdxxw] failed: getting offsets for thread bafybakl7urr353tmd72ouuadjo7s5sctuk4tz5jo6es24iqcwwlbdxxw failed: thread not found"}
janv. 26 23:55:51 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:55:51.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafyeckxdsm3flzkivspw2knzkrtzmgf3uasshs7l7bihelotpzspf5kx] failed: a service-key is required to request logs"}
janv. 26 23:55:51 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:55:51.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafyeckxdsm3flzkivspw2knzkrtzmgf3uasshs7l7bihelotpzspf5kx] failed: getting offsets for thread bafyeckxdsm3flzkivspw2knzkrtzmgf3uasshs7l7bihelotpzspf5kx failed: thread not found"}
janv. 26 23:57:37 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:57:37.789+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybb3kohmh4prten77gm4iulawbqtylbv6rkka3wxdqzu52bbvbskgd] failed: getting offsets for thread bafybb3kohmh4prten77gm4iulawbqtylbv6rkka3wxdqzu52bbvbskgd failed: thread not found"}
janv. 26 23:57:38 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:57:38.424+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybb3kohmh4prten77gm4iulawbqtylbv6rkka3wxdqzu52bbvbskgd] failed: a service-key is required to request logs"}
janv. 26 23:58:52 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:52.789+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafygbuv33auls6z6w6wfwht36qhi7mhl5qlwafltzqhuzao34ppzlboj] failed: getting offsets for thread bafygbuv33auls6z6w6wfwht36qhi7mhl5qlwafltzqhuzao34ppzlboj failed: thread not found"}
janv. 26 23:58:53 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:53.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafygbuv33auls6z6w6wfwht36qhi7mhl5qlwafltzqhuzao34ppzlboj] failed: a service-key is required to request logs"}
janv. 26 23:58:53 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:53.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybaaiwryhk743fxaj47z2nskej2yd2wej3pdunzodozq7qzqkcfdzu] failed: getting offsets for thread bafybaaiwryhk743fxaj47z2nskej2yd2wej3pdunzodozq7qzqkcfdzu failed: thread not found"}
janv. 26 23:58:54 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:54.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybaaiwryhk743fxaj47z2nskej2yd2wej3pdunzodozq7qzqkcfdzu] failed: a service-key is required to request logs"}
janv. 26 23:58:54 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:54.788+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybb6bx64egv3h435zky3jmj7brmwckcc6d45mfci2m6zwpcvkvhttt] failed: getting offsets for thread bafybb6bx64egv3h435zky3jmj7brmwckcc6d45mfci2m6zwpcvkvhttt failed: thread not found"}
janv. 26 23:58:55 ubuntu-i5 org.gnome.Nautilus[26746]: {"level":"error","ts":"2022-01-26T23:58:55.425+0400","logger":"netqueue","caller":"queue/ff.go:232","msg":"call to [12D3KooWKwPC165PptjnzYzGrEs7NSjsF5vvMmxmuqpA2VfaBbLw/bafybb6bx64egv3h435zky3jmj7brmwckcc6d45mfci2m6zwpcvkvhttt] failed: a service-key is required to request logs"}
To Reproduce
Steps to reproduce the behavior:
- In a terminal, type journalctl -e -f --user
- Open Anytype-0.23.5.AppImage, but do nothing in it
- Watch all “queue/ff.go:232” messages appear in the terminal
- Close Anytype-0.23.5.AppImage
- No New “queue/ff.go:232” messages appear in the terminal
Expected behavior
When Anytype is opened but we do nothing in it, logging system should not be constantly spammed by such messages and hdd should not be constantly writing something.
System Information:
- OS: Ubuntu 20.04
- Device Manufacturer/Model: Custom PC
- Anytype Version: e.g. 0.23.5
