Unreliable Followups/Unassignment

[0x4007]

The bot seems to be inconsistent on who it follows up with and then unassigns when dealing with bounties that are assigned but have no updates happening. This is an important feature that should be functional, or else we will have many bounties being reserved and neglected.

I have a feeling that this stopped being reliable after implementing the capability for the bot to monitor linked pull requests for updates. But this feeling may be unfounded cause I haven't done the research to confirm it.

          Thanks @pavlovcik. will complete this asap

Originally posted by @sweetapplepumpkinpie in #176 (comment)

---

I will compile examples as I find them.

• prettier in package.json calling forge fmt ubiquity-dollar#516
• Bot Deploys Comment Should Include Commit Hashes ubiquity-dollar#663

[wannacfuture]

/start

[ubiquibot]

@wannacfuture The time limit for this bounty is on Sat, 17 Jun 2023 04:35:24 GMT

Your currently set address is:
0x9e4EF4353C928cD3eb473E8f12aeCF58C208ef40
please use /wallet 0x4FDE...BA18 if you want to update it.

[wannacfuture]

@pavlovcik , could you provide more information in detail? So, what the bot should do about the bounties with no update?

[0x4007]

The bot should follow up as it does on some bounties (I am assuming it is only working on bounties with an open pull request right now. Before it worked on any assigned bounty with no activity!)

The thing is, in the linked example above, the bounty hunter never even started the task. It already has been a full week so they should have already been unassigned by now.

This bounty requires that you figure out the root cause of the issue, as well as provide a fix.

This is an important feature because at any given moment there may be many bounties assigned and then the bounty hunters stop working on them which means that our organization's development throughput will decrease.

[wannacfuture]

The thing is, in the linked example above, the bounty hunter never even started the task. It already has been a full week so they should have already been unassigned by now.

The reason of not unassigning is there is a comment of that bounty hunter which is created less than a week before.
It seems the bot identifies it as it has activity.

So, let's clarify.

• We should identify issue with only pull request on it even it has comments of the hunter.
• If there is no opened pr on it and it has passed over followup time, the bot should follow up that issue.
• And also, even if the issue has opened pr, we should calculate how many time has passed since that pr is created, then if it is over the followup time, the bot also should follow up that issue.

What do you think, @pavlovcik ?

[wannacfuture]

@pavlovcik , Can you check my thoughts above?

[0x4007]

The reason of not unassigning is there is a comment of that bounty hunter which is created less than a week before.
It seems the bot identifies it as it has activity.

There are two "checkpoints"

1. the follow up, where the bot comments "do you have any updates?" this is in about 4 days.
2. the unassign, where the bot will unassign if there is no reply to that question.

---

The bot should be following up when activity is not visible from the bounty hunter. "Activity" includes:

1. comments on the issue from the bounty hunter.
2. commits on the linked pull request from the bounty hunter.
3. comments on the linked pull request from the bounty hunter.

Any of those actions should reset the clock for the bot to follow up AND for unassign. This means that if the bot asks for an update, and the bounty hunter adds a new commit, the bot should wait another four days until it asks for updates again.

[ubiquibot]

[ CLAIM 450 WXDAI ]

0x9e4EF435...8C208ef40