Mark Bryars

I've seen this issue too, its when you've called .close on a reader when its not fully initialized yet. Its not easy to work around this, maybe add your own...

EM.run { EM.error_handler do |e| puts " **** ERROR #{e.message}" puts e.backtrace.join "\n" end started=0 (1..30).each do EM::Ssh::Shell.new("localhost", "emtest", "emdemo") do |shell| started+=1 shell.on(:error) do |e| puts "Shell error :(...

I found the reason for the 10 limit is the sshd_config default for MaxStartups is 10 but it doesn't explain the lack of errors.

Maybe you need to refresh the oauth credentials in the filestack website: https://www.filestack.com/docs/tutorials/google-drive-oauth/

As the copyright holder you're entitled to contact his hosting company and get it taken down for copyright violation. DMCA is pretty shitty, but maybe try and use it for...

The RPI bootloader now has as a tryboot config.txt replacement oneshot feature that might help a bit with this. https://github.com/raspberrypi/linux/commit/757666748ebf69dc161a262faa3717a14d68e5aa

It doesn't seem to be in the tooling yet... but. echo hdd.hdd2 > /sys/fs/bcachefs/$BLKID/dev-$DEVID/label if you're not sure on these values but know the linux block device name, you can...

I don't have any nocow data, but I did try enabling compression attribute on a folder with replicas=1 and then upping replicas to 2, I don't know if that plays...

I see there is a reconnector struct, I was wondering if perhaps the EOF on closing an already closed connection was masking the error and blocking the retry.

This seems fixed, I tested it with v1.25.2-29-g3139850c ``` $ bcachefs set-fs-option --nohorse-enabled /dev/loop12 bachefs: unrecognized option '--nohorse-enabled' Using encoding defined by superblock: utf8-12.1.0 ```