search

probot / no-response

a GitHub App that closes issues where the author hasn't responded to a request for more information
ISC License
107 stars 22 forks source link

Bot didn't close issue? #25

Open Hixie opened 6 years ago

Hixie commented 6 years ago

These issues have been marked appropriately (as far as I can tell) for longer than the configured close period (as far as I can tell) but didn't get closed:

https://github.com/flutter/flutter/issues/9384 https://github.com/flutter/flutter/issues/9385

RussH commented 6 years ago

@Hixie I have the same issue. Did you find a fix at-all?

Hixie commented 6 years ago

Nope. :-(

gixid192 commented 5 years ago

Same here :(

AlexSkorkin commented 5 years ago

same here...

gixid192 commented 5 years ago

It is working for me now. My problem is I didn't assign the label for the issue. no-res-result

RussH commented 5 years ago

so just to check - is this working now? I've just flagged some issues, I won't find out until the 14 day timer expires

AlexSkorkin commented 5 years ago

It works fine on my side.

Hixie commented 5 years ago

Seems to not work again. For example: https://github.com/flutter/flutter/issues/20912

kf6gpe commented 4 years ago

It's still not working for flutter/flutter reliably --- any update here? Thanks!

cc @helinanever

mairaw commented 4 years ago

I also recently installed the bot on a new repo and I yet have to see the bot close any issues. I've seen it remove the label when a customer responded, so I know that the bot seems to be configured for my repo. Or does this only apply to labels applied after you configure the bot? If so, I might start seeing issues closed after an additional week or so.

helinanever commented 4 years ago

The behaviour of the bot in https://github.com/flutter/flutter/issues is still unreliable. The most common issue is that it fails to close issues at the right time (21 days), e.g. https://github.com/flutter/flutter/issues/10593, or closes them later (after 26 days), e.g. https://github.com/flutter/flutter/issues/47619.

Sometimes it also closes when it shouldn't, e.g. https://github.com/flutter/flutter/issues/38976, or doesn't remove the "waiting for.." label after the author replies, e.g. https://github.com/flutter/flutter/issues/53790.

GitHub
flutter/flutter
Flutter makes it easy and fast to build beautiful apps for mobile and beyond. - flutter/flutter
PrivatePuffin commented 4 years ago

@helinanever and @Hixie You guys do notice you didn't use the recommended syntax in the config file do you? closeComment: >- Where the recommended syntax is: closeComment: >

Hixie commented 4 years ago

We did not notice at all, good to know.

Hixie commented 4 years ago

(Though... why would it sometimes work in that case?)

PrivatePuffin commented 4 years ago

(Though... why would it sometimes work in that case?)

Thats a very good question! For which i've no answer... Don't expect this to magically fix your problem, but at least we might be able to exclude this... :)

mairaw commented 4 years ago

Just FYI, since I posted, the bot started working for my repo. After a couple of weeks waiting to see if the bot would kick off (I had the period set to 14 days), I changed it to 10 and then it started working all of the sudden.