[FIX] mac-related changes

[isko-odoo]

Description

Briefly describe your changes and the reasoning behind them so that other contributors and reviewers can easily grasp the goal of your PR.

Makes odev compatible with Mac and avoids macOS bloating the repo with temp files

Linked Issues

Link the issues that this PR solves, if any:

• #[issue number or URL]
• ...

Compliance

the contribution guide and versioning guide are missing

• I have read the contribution guide
• I made sure the documentation is up-to-date both in doctrings and the docs directory
• I have added or modified unit tests where necessary
• I have added new libraries to the requirements.txt file, if any
• I have incremented the version number according the versioning guide
• The PR contains my changes only and no other external commit

[brinkflew]

Looking good, can you please target the beta branch instead of main? Thx!

[isko-odoo]

@brinkflew rebased on beta. Didn't tag you myself because the tests didn't run yet, and I have a problem running them on my system, as I can't compare the two, but the failing tests don't really point to my changes. I'll have a deeper look in a bit.

[Lok3rs]

I confirm it works, recently ran it on my mac and everything is setup well :)

[brinkflew]

@isko-odoo we can enable the tests to run on MacOS in the CI (.github/actions), this might be easier than running locally (I've had issues on linux as well, something isn't totally right in the cleanup I think...).

This may required a bit of work for the setup of the actions. The last time I tried I couldn't properly install postgres but I also couldn't really test it as I have no Mac. If we manage to do that we can enable MacOS in the test matrix.

[isko-odoo]

@brinkflew The issue I faced is probably related. The code created a db with a random id like test-jtjoae. I tried running the tests but they appeared stuck. Then I tried odev list, and I got an error saying the db test-whatever is corrupted. I did exit with cmd+C, so I can't say it's definitely caused by the code, but I don't think I exited prematurely the first times I tried the tests. And it might be because of the odev.sh changes, but I couldn't run the main/beta branch tests after running them on my own branch..

I'm happy to help you set up the github actions, maybe we can align next week.

[brinkflew]

Yeah, same kind of error here, I already noticed that exiting tests with ctrl+c tends to break it more, but I'm not convinced letting it run and exit cleanly is deterministic. That's something to work on. GitHub actions start from scratch everytime so that's less likely to be an issue.

I would love to work on that next week ;)

[isko-odoo]

@brinkflew needed to rebase