Matthias
Matthias
I think PR #61 basically provides this capability to get restic log messages in real time, maybe this issue can be closed now?
Hi @flozz , just want to add that I face the same issue on [Solus](https://getsol.us/) which was just upgraded to Gnome 43.
Hi @andreasnuesslein , I think we should make the output parsing more robust against such changes by adding some exception handling. I have already tried this (see https://github.com/palto42/runrestic/blob/fix_output_parsing/runrestic/restic/output_parsing.py) and can...
Hi @gmag11 , I'm using restic 0.14.0 since 04. September with runrestic 0.5.26.1 and have no such issue, so not fully sure why it happens for you but not for...
Hi @gmag11 , I now found the reason why runrestic 0.5.26.1 works for me with restic 0.14 but not for you: I installed runrestic from git and not from PyPI....
Closing this, assuming it was fixed by #52
> debug_option = typer.Option( > "--debug", > "-d", > help="Enable debug mode.", > show_default=True, > default_factory=lambda: True, > ) I don't understand why this only forks with `default_factory=lambda: True`, which...
Not sure how much this is related to #11, I think it's a bit different. From my understanding this is asking for an option to share the fully rendered output...
I just tried it and don't get such error message, on my installation it shows the first part of the raw markdown text above the download button. Instead I get...
I faced the same issue and identified two issues which I fixed in the example code, see pull request #23 See also my #12 (comment)