Debdut Chakraborty
Debdut Chakraborty
cc @d-gubert
Hi, sorry to intrude, I was just going through some other pr and this caught my eye. @evanofslack - if you just return the models, you are misinforming the users...
I see, my misunderstanding then. Thanks
That's a different error than what is mentioned above. Please share the output of the restore action as that is more relatable to what is posted above.
this seems like the old apparmour issue
Will check out this patch ASAP. Still travelling :) should be done in a couple hours. Thanks.
I think in this case we're using *any* falsy value indication. If that's the case not sure whether this patch is necessary or not.
I see. Ok, for now, we don't have a standard for domain specific falsy values (i.e. for strings, '' instead of undefined, for boolean, false instead of undefined, and so...
Change the pr title to what you're fixing, not what you're doing code-wise, as that doesn't give us context as to why we need the patch.
Cannot reproduce onlatest develop.