Bugzilla

I have switched 78.0 and found a few annoying things.

One is this.

I subscribe to a large number of mailing lists and also handles some paper submission to an annual conference/symposium in cooperation with a support of a society of IEEE.
society.
To classify all these and work/personal e-mails, I have a large number of filters.

Sometimes filters don't get executed for whatever the reason.: bugs, or I am locking a folder by doing something, etc. 
In those cases when I realized something went wrong,  I simply let the filters run on a folder, say, Inbox for a while to sort everything into the intended folders.

Well, it worked just fine before with 78.
Unfortunately, with 78, it seems that when no message matches a filter in the list of filters, TB asks the user "No match was found. Should I continue to apply the filters?" by a modal dialog. That is, the application of the filter stops right there WITHOUT the user interaction.

This is BAD.

I don't know the rationale for the introduction of the checking of the failure. Maybe a badly-constructed filter not matching any message as intended.

But as you can imagine, this interferes with my intention of cleaning up misfiltered message from a large folder.
It used to be able to simply run this on a large folder, say, have 30,000 messages and leave for lunch and come back. By the time I come back, hopefully the filtering was finished.
But with the MODAL dialog requesting to know if I want to continue, this scenario does not work any more.

Help. 

Either we get rid of this check or at least, 
we should ask at the time of invoking applying filters on a folder.
"- Should we stop and ask each time a filter fails to match any message (YES or NO)?" 
(No here means we apply filters till the end no matter what.)
and let someone like me to run filters without useless (to me) check till the last filter unbothered.

TIA


PS: This is VERY STRANGE THOUGH.
Just a few hours ago, I did something similar on a smallish folder and let the filters run on it. It worked without any such complaints. But the list of filters includes ones that would never fire on the messages in the small filter.
Whereas, now I am running filters on my large Inbox and this check appears now and then.

Worse, the filtering seems to take much longer in 78 than in the previous version. Something is wrong.

I have switched 78.0 and found a few annoying things.

One is this.

I subscribe to a large number of mailing lists and also handles some paper submission to an annual conference/symposium in cooperation with a support of a society of IEEE.
To classify all these and work/personal e-mails, I have a large number of filters.

Sometimes filters don't get executed for whatever the reason.: bugs, or I am locking a folder by doing something, etc. 
In those cases when I realized something went wrong,  I simply let the filters run on a folder, say, Inbox for a while to sort everything into the intended folders.

Well, it worked just fine before 78.
Unfortunately, with 78, it seems that when no message matches a filter in the list of filters, TB asks the user "No match was found. Should I continue to apply the filters?" by a modal dialog. (Sorry I am using a Japanese localized version on this Windows 10 PC and I have no idea what the English version shows there.)
That is, the application of the filter stops right there WITHOUT the user interaction.

This is BAD.

I don't know the rationale for the introduction of the checking of the failure. Maybe a badly-constructed filter not matching any message as intended.

But as you can imagine, this interferes with my intention of cleaning up misfiltered messages from a large folder unattended.
I used to be able to simply run this procedure on a large folder, say, have 30,000 messages and leave for lunch and come back. By the time I came  back, hopefully the filtering was finished.
But with the MODAL dialog requesting to know if I want to continue, this scenario does not work any more.

Help. 

Either we get rid of this check or at least, 
we should ask at the time of invoking applying filters on a folder,
"- Should we stop and ask each time a filter fails to match any message (YES or NO)?" 
(No here means we apply filters till the end no matter what.)
and let someone like me to run filters without useless (to me) check till the last filter unbothered if the user answers NO.

TIA


PS: This is VERY STRANGE THOUGH.
Just a few hours ago, I did something similar on a smallish folder and let the filters run on it. It worked without any such complaints if I am not mistaken. But the list of filters includes ones that would never fire on the messages in the small filter.
Whereas, now I am running filters on my large Inbox and this check appears now and then.

Worse, the filtering seems to take much longer in 78 than in the previous version. Something is wrong.

I have switched 78.0 and found a few annoying things.

One is this.

I subscribe to a large number of mailing lists and also handles some paper submission to an annual conference/symposium in cooperation with a support of a society of IEEE.
To classify all these and work/personal e-mails, I have a large number of filters.

Sometimes filters don't get executed for whatever the reason.: bugs, or I am locking a folder by doing something, etc. 
In those cases when I realized something went wrong,  I simply let the filters run on a folder, say, Inbox for a while to sort everything into the intended folders.

Well, it worked just fine before 78.
Unfortunately, with 78, it seems that when no message matches a filter in the list of filters, TB asks the user "No match was found. Should I continue to apply the filters?" by a modal dialog. (Sorry I am using a Japanese localized version on this Windows 10 PC and I have no idea what the English version shows there.)
That is, the application of the filter stops right there WITHOUT the user interaction.

This is BAD.

I don't know the rationale for the introduction of the checking of the failure. Maybe a badly-constructed filter not matching any message as intended.

But as you can imagine, this interferes with my intention of cleaning up misfiltered messages from a large folder unattended.
I used to be able to simply run this procedure on a large folder, say, have that 30,000 messages and leave for lunch and come back. By the time I came  back, hopefully the filtering was finished. I probably have close to 100 filters :-(
But with the MODAL dialog requesting to know if I want to continue, this scenario does not work any more.

Help. 

Either we get rid of this check or at least, 
we should ask at the time of invoking applying filters on a folder,
"- Should we stop and ask each time a filter fails to match any message (YES or NO)?" 
(No here means we apply filters till the end no matter what.)
and let someone like me to run filters without useless (to me) check till the last filter unbothered if the user answers NO.

TIA


PS: This is VERY STRANGE THOUGH.
Just a few hours ago, I did something similar on a smallish folder and let the filters run on it. It worked without any such complaints if I am not mistaken. But the list of filters includes ones that would never fire on the messages in the small filter.
Whereas, now I am running filters on my large Inbox and this check appears now and then.

Worse, the filtering seems to take much longer in 78 than in the previous version. Something is wrong.