RFR: 1912: Show priority for bugs in pull request body

Zhao Song zsong at openjdk.org
Tue May 23 17:13:05 UTC 2023

On Tue, 23 May 2023 16:26:13 GMT, Erik Joelsson <erikj at openjdk.org> wrote:

>> The initial purpose of this issue is to show priority for bugs in the issue list in the pull request body. However, with current pr bot, if the user changes the type of the issue or the priority of the issue in the JBS, the changes will not be reflected in the PR body unless there is something could trigger the CheckWorkItem(like user edits the PR title and user issues some commands).
>> As Erik.J suggested, we could maintain a map(from JBS issue to the PRs related with this issue) in memory, so if the issue gets updated, we could know which pr needs to be updated.
>> To query updated issues and handle them, a new bot called `IssueBot` is introduced. This bot would query for updated issues(exclude CSR and JEP) in JBS, and it will read the in memory map to know whether there is any pr needs to be updated. If so, it will generate `CheckWorkItem` for that pr.
>> So currently, there are two ways to generate `CheckWorkItem`. Updated issues and updated pull requests. Previously, in the `CheckWorkItem`, we would check the metadata of the pull request and if the metadata is up to date, `jcheck` would not be triggered.  Now, we could check the metadata of the pull request and the issues related to this pr, but it would be too expensive because if only the pull request is updated, we also need to fetch all the issues from JBS to just generate the metadata. Therefore, in this patch, metadata is split to two parts, one part for pull request and one part for issues. If the `CheckWorkItem` is spawned from an updated pull request, we will only check pr metadata. On the other hand, if the `CheckWorkItem` is spawned from an updated issue, we will only check issues metadata.
>> Besides, since the map is in-memory, so if the bot restarts, the map needs to be initialized. When bot restarts, a `CheckWorkItem` would be generated for each pr, so the initialization is in `CheckWorkItem`.
> bots/pr/src/main/java/org/openjdk/skara/bots/pr/CheckWorkItem.java line 324:
>> 322: 
>> 323:     private void initializeIssuePRMap() {
>> 324:         // When bot restarts, the issuePRMap needs to get updated with this pr
> I'm not sure about this comment. This mapping needs to be updated every time there is a change to the associations, or if the map is currently missing associations for this PR. I don't think it makes sense to maintain an `initializedPRs` map, we should just always update the map.
> This update process needs to be synchronized. The map is a `ConcurrentHashMap`, which is good, but we need to synchronize on the list value before trying to manipulate it.

I make the bot maintaining the` initializedPRs` map because I think there is no need to always update the map here. We  only need to update the map here when the bot restarts and it's the first time for the bot to see this pr. Otherwise, the update is extra work. 

The real update for the map located in `CheckRun#getStatusMessage` from line 744 to 768. 

And yes, I need to synchronize on the list value before trying to manipulate it. Thanks for catching!

> bots/pr/src/main/java/org/openjdk/skara/bots/pr/IssueWorkItem.java line 82:
>> 80: 
>> 81:     @Override
>> 82:     public Collection<WorkItem> run(Path scratchPath) {
> I don't think we need a separate IssueWorkItem. The reason for the `CSRIssueWorkItem` is that we need to do potentially expensive work for each CSR issue found to translate them into `CheckWorkItem` (follow multiple issue links through queries). In this IssueWorkItem, all we need to do is look up the issue ID in an in-memory map, which is very cheap. That can easily be done in a loop in `bot.getPeriodicItems` without risking it taking too long.

Yes, it makes sense. Will fix it.


PR Review Comment: https://git.openjdk.org/skara/pull/1523#discussion_r1202729733
PR Review Comment: https://git.openjdk.org/skara/pull/1523#discussion_r1202732518

More information about the skara-dev mailing list