Helmut K. C. Tessarek
Helmut K. C. Tessarek
I found the issue, even though it is rather weird, since I made changes to this provided by you for an earlier issue. And it works on macOS, so that's...
Thanks for the info. Does this mean it's an upstream issue? e.g. I guess the bash completion on macOS is also different.
Interesting, so it seems that `ble-import integration/fzf-completion` does different things on macOS and Linux - or they behave differently. Weird though that I am the first one who encountered this....
Thanks for the info. I am still a bit confused why this only seemed to be triggering an issue on Linux. (Or maybe anything but macOS.)
Updated ble on macOS and Linux. macOS still works and Linux works now as well! 🎉 Thanks!
> Do you think it would be another issue? Should we identify the cause of this difference? Right now it makes no sense, since the bash init is identical except...
Just following-up... Shall we close this or do you want me to start the macOS VM?
No worries. In that case just let me know when you have time and I fire up the VM.
May I ask, why you want to do that? The token is still valid, so the application will still work. The user should know that the password has been changed....
@rullzer I don't understand. if a client uses a token, it can still connect and should work as normal. this was the entire point of keeping tokens valid when changing...