-
Notifications
You must be signed in to change notification settings - Fork 69
Description
I just opened patchbay after a year of not using it and the UI has been quite unresponsive (although not completely) for several hours. It would be great if there was some sort of progress bar or something that informs the user that heavy processing is taking place and perhaps how long it will approximately take. It would be even better if the UI was responsive while creating the indexes and all that.
Should I have pressed the initial sync button in ahoy? Since I did the initial sync about 2 years ago, I thought I should press the other button.
I'm getting the following two types of errors in the console.
server error, from net:::ffff:127.0.0.1:34932~shs:
Error: stream ended with:64 but wanted:112
at drain (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/pull-reader/index.js:43:26)
at /tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/pull-reader/index.js:63:18
at /tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/pull-reader/index.js:20:7
at drain (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/stream-to-pull-stream/index.js:126:18)
at Socket.<anonymous> (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/stream-to-pull-stream/index.js:143:5)
at Socket.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1092:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
and
Error replicating with @tXroIBgvpO//CNS4od08GiPHQJQ7fX4ZxDQasuKIeww=.ed25519:
Error: parent stream is closing
at PacketStream.stream (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/packet-stream/index.js:46:28)
at Object.ws.remoteCall (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/muxrpc/stream.js:116:17)
at /tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/muxrpc/index.js:46:15
at remoteCall (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/muxrpc/api.js:40:19)
at EventEmitter.obj.(anonymous function) [as createHistoryStream] (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-server/node_modules/muxrpc/api.js:25:18)
at replicate (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-replicate/legacy.js:291:13)
at EventEmitter.fallback (/tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-replicate/legacy.js:351:7)
at Object.onceWrapper (events.js:273:13)
at EventEmitter.emit (events.js:182:13)
at /tmp/.mount_patchbhQXx7k/resources/app.asar/node_modules/ssb-ebt/index.js:129:15
However, the former is much more frequent than the latter. In fact, the latter has only happened once so far.
Maybe this is related to #343? I'm using archlinux and the last version of patchbay which I downloaded today (patchbay-Linux-8.1.0-x86_64.AppImage from releases).
Thanks for the great work on patchbay :)