conradoverta

Why should we do this right now? Let's leave cleaning the migrations to later as they should be pretty easy to do. We need to do at least one OSS...

@ad-47 should we close this to reduce the number of open PRs? We can remove later.

> Ready for review, but will do one optimization in separate PR: reduce calls to the database to get repositories, commits and blobs information That's fine. Optimizations can come later....

@ad-47 ~is this still in WIP?~ nevermind. I read 14 days instead of 14 hours!

> @conradoverta This is in WIP because the `resource_name` is not added in `GetResources` endpoint and also the UAC implementation is pending. Yeah, it's fine. I read "14 days" and...

We build in a different instance than we run, which might end up in a different instance type due to our mix. Is there an option to relax the compilation...

We created a wrapper around gcc/g++ to replace `march` to `mtune`. Just updating the `setup.py` in this repo wouldn't be enough for our case since we need to support existing...

I would recommend leaving mtune/march as an option if possible (maybe an environment flag?). I see value of locking with march in cases where you want to optimize for performance...

Oh! That is indeed a much better solution. Somehow I completely missed it when I skimmed the code.

Nice, thanks! I don't know if I should close or leave it open for tracking. Feel free to close if better for the team.