Repository navigation
waiting for customer response being incorrectly removed #129771
Description
Triagers have noticed that waiting for customer response is being seemingly randomly removed from issues. Examples:
- BottomNavigationBar and PageView click to switch item issues #129738 where it was removed almost immediately after being added.
- java.util.concurrent.RejectedExecutionException: #128945 where it was removed after about a week, but without any comments.
- Looking for new flutter package and exposing the SDK cryptographic/access primitive to Dart for secure usage #128921 where is was removed once with no triggering event, and then again either for a comment by someone other than the OP, or maybe randomly but coincidentally after the comment.
Having this label being randomly removed will make it much harder for us to keep un-actionable issues from accumulating in the issue systme.
Activity
godofredoc commentedon Jun 29, 2023
@stuartmorgan Is this still happening? we started the migration to the core action but it seems like we'll need to rollback to my fork because the processing in the core action does not scale well beyond a couple hundred open bugs + prs.
The errors linked to the bug were most likely during the transition period when we were adjusting the parameters.
stuartmorgan-g commentedon Jun 29, 2023
When was that transition period? The first one in the list happened 5 hours ago.
godofredoc commentedon Jun 29, 2023
My bad, I thought it was 5 days. Yeah we'll need to revert the changes, I'll send them in a minute.
iDarkQ commentedon Jun 29, 2023
it happened just as well with one of my issues #128935. (Although I already responded, I don't know if it matters).
godofredoc commentedon Jun 29, 2023
Hi @iDarkQ in your bug the label was removed correctly after the P2 label was added:
iDarkQ commentedon Jun 29, 2023
@godofredoc Hi, sorry yeah I haven't noticed it. Thanks
Revert no-response to fork. (#129775)
keyonghan commentedon Jul 5, 2023
@stuartmorgan Do you still happen to see the issue with the revert?
stuartmorgan-g commentedon Jul 5, 2023
@keyonghan I'd need to check with the triage team and get back to you. I'm fine with closing this as resolved given the revert, and I can re-open if it turns out to still be a problem, if that makes tracking easier.
keyonghan commentedon Jul 5, 2023
Thanks @stuartmorgan . Closing here, and feel free to reopen.
github-actions commentedon Jul 19, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.