Nicholas D Steeves

Hi @gfederix > Hi @sten0. I was going to do some more code this weekend and probably do a pull request next weekend (February 6th). > I also found that...

Ah, this is the problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977931 For anyone else encountering this issue, it appears Jedi 0.17 requires Parso 0.7, and Parso 0.8 requires Jedi 0.18. Merry Christmas!

Oh no... Parso 0.8 + Jedi 0.18 doesn't solve pytest failures. There are obvious actionable bugs like: ``` E AssertionError: Tuples differ: (PosixPath('/tmp/elpy-teste5ye5srh/test.py'), 0) != ('/tmp/elpy-teste5ye5srh/test.py', 0) E E First...

Oh, and this is a regression relative to 4248dcce

Hi @gopar, thank you for reviewing! By the way, do you know why `elpy-shell-add-to-shell-history` is disabled by default? If you or @galaunay aren't planning to document that in a follow-up...

Pierre Curto ***@***.***> writes: > I need to investigate as I dont recall. I might need to remove some of the other files (the Linux kernels) as they were provided...

> I'm fine with removing this line. Didn't notice any issues for normal use cases. > > Showing a warning mit more details and giving the option to continue would...

Agreed, but that's more work! I'm just talking about a simple if fail, then present a generic ssh debug command notification, using variables in the string that Vorta already knows...

ah, I missed one thing. It's borg that would fail with non-zero at this point...ahhh, now I see what you mean. Sorry :-)

> I think we should keep `StrictHostKeyChecking=no` for the `borg init` and `borg info` operations, which are used to add a new repo, but remove them from everything else. That...