Bastien Abadie

The bot code only iterate on all issues path and query the [list_repo_issues](https://github.com/mozilla/code-review/blob/master/backend/code_review_backend/issues/api.py#L374) endpoint. We could look into performance and even if the whole output is needed (the bot only...

I just started a manual backup on heroku so we can test locally for performance issues.

I was able to restore the backup, and test API queries. The list issue endpoint is indeed super-slow (taking several seconds per hit...) I noticed a few immediate issues: -...

To start working on this, the code review bot needs to pick up the default task format first; otherwise old tasks will be used instead.

Most common issues are currently: - in events, [missing `m-c` repo on Phabricator](https://mozilla.sentry.io/issues/4996743258/?project=6273982&query=&referrer=issue-stream&sort=freq&statsPeriod=14d&stream_index=0) with 1700 events & ongoing - in bot [missing clang-format](https://mozilla.sentry.io/issues/?limit=5&project=6273985&query=missing+clang-format&referrer=issue-list&sort=freq&statsPeriod=14d) has 2k+ events - in bot, a...

I filed 2 issues for @vrigal on the bot, and removed the MC repo from testing secret, then restarted code-review events testing o, heroku. This [sentry issue](https://mozilla.sentry.io/issues/5668518104/?project=6273982&query=&referrer=issue-stream&sort=freq&statsPeriod=14d&stream_index=0) is now marked...

I just noticed another config problem (on this [task](https://firefox-ci-tc.services.mozilla.com/tasks/DE0vXqX8TN-Gr_BJK84Drg/runs/0/logs/public/logs/live.log)): ``` 2024-08-29 12:17:48.000824 [WARNING ] [warning ] Backend rejected the payload: b'{"base_repository":["Object with url=https://hg.mozilla.org/comm-unified does not exist."]}' ``` I do not...

I merged a few of them (easy ones). The big items are: - Django from 4.2 => 5.0 - Vue js major bump (2 => 3) - Python version in...

Next big work is to migrate from Vue 2 to Vue 3. I'll file a dedicated issue with analysis of steps to do

The vue.js migration will be tracked in #2392 as it's a larger effort