GP Saggese
GP Saggese
The code has pretty much no standard so everybody mocks in different ways. 1) I don't like decorators, the context manager approach makes the code too nested 2) Clear rules...
Sg. Let's wait for CmampTask10710 fix (which is on me)
I've been rewriting all that logic and I can't test on all the external devices. IIUC, my take is that either one can run `docker` without `sudo` or if it...
Ok to put a hack to unblock, but let's clearly mark with a `TODO(gp): Remove this as per HelpersTask578`. 1) What is your set up exactly? 2) What does it...
> Current [setup](https://github.com/causify-ai/helpers/blob/master/docs/onboarding/intern.set_up_development_on_laptop.how_to_guide.md) does not ask users to add themselves to sudoers. I could update the document. Yes pls The new approach I've been working on is about checking what...
You can file an issue for this. It's a bit weird that there is a problem, since we use ubuntu on the server and everything is fine. Maybe the ubuntu...
1) @aangelo9 If you created files with the "wrong" user, then only your root can delete them 2) Adding the user to `etc_sudoers` is the right approach > # Linux...
1) Yes, system-wide is the way to go (since there is also no alternative). The virtual env is only for Python packages and GH cli is not one of that....
All good. 3) I believe `sudo` is inevitable in this case for Linux.
It seems a bug in the library itself... Not sure how to fix it, besides not using verbose = 0. Any other idea?