masc
masc
@thrau yes, it covers "only" the most common and relevant use case, as preserving executability is a key feature of eg tar archives. there's not really many changes here, but...
everything to make it work is essentially in specialized `TarAchiver`
why not render asynchronously in stages, like eg. postman does. it works well and there's barely any need for switches or limits.
btw this issue got much worse in recent versions, presumably due to pretty-print / color enhancements which make rendering even more expensive.
> What's the purpose of showing/render a response larger than 2MB? your argument makes no sense to me. if there's no purpose (in showing the content), why would you download...
if it makes sense to download it (very often) makes even more sense to view the content right in place. just for quick checking a subset of a larger result,...
> This issue is more around bad practices on API design, responses should not be large, highly depends on the use case. anyway it's not implemented that way in postman...
> Remember the project is open source, if this is a big issue to you the code is there for you to fix it it's not an issue at all...
current "design" is that a backup volume can be identified by subvolume path only, that's why path convention is that "static". I would accept this kind of PR, but only...
yes, there could be some more explicit checks and feedback in quite a few places. I avoided this initially as every single command executed remotely initiates a new ssh connection,...