David Corking

@bsandrow that is a great workaround, thanks - foreground works perfectly for me on the same phone as when I posted the issue last year, and these versions: ``` simple-mtpfs...

I upgraded OSXFUSE and reinstalled simple-mtpfs from homebrew. The symptoms still occur without the foreground flag. ``` $ simple-mtpfs --version simple-mtpfs version 0.3.0 OSXFUSE 3.8.2 FUSE library version: 2.9.7 fuse:...

@lukelbd > The symptoms make me think the problem lies in the upstream fuse library. https://github.com/phatina/simple-mtpfs/issues/59#issuecomment-423975149

I have now upgraded OSXFUSE by 3 minor points, and macOS to 10.15.7, with same symptoms. Anyone dug into this deep enough to be able to give upstream a reproducible...

I have been able to reproduce this issue with the sample app mentioned by @zachbodek : https://github.com/jamesridgway/devise-otp-second-step (The sample session controller hook is here: https://github.com/jamesridgway/devise-otp-second-step/blob/master/app/controllers/concerns/authenticate_with_otp_two_factor.rb )

There is a solution that fixes this issue in the sample app at https://github.com/jamesridgway/devise-otp-second-step/issues/24 It doesn't seem to be specific to devise-two-factor, and rather is caused by the overall approach...

From experience, one workaround you _could_ consider documenting is simply to try again later. ### more info I tried again later in the day I wrote my report, and the...

For me, on macOS Ventura 13.6.4, there is no way for an ordinary user to stop mdnsresponder. It is protected by System Integrity Protection, and restarts automatically, so would require...

Thank you @Explosion-Scratch . Athough mDNSResponder still runs on my machine, and, according to netstat, is listening on tcp6 port 53, WARP today connected successfully. A few days ago I...

The WARP client is now showing a different error on IPv4 than this one, ( mDNSResponder is still listening on tcp6 but not 4) so I can no longer reproduce...