Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
2013.02.17. 11:36, "Stas Malyshev" smalyshev@sugarcrm.com ezt írta:
Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
I found the script (scripts/cron/no-feedback or something like that) but I
have to figure out how it should be called (maybe via curl/wget) because it
expects a post variable and stuff and execution from cli errors out.
if somebody remembers the setup feel free to beat me with the restoration.
2013.02.17. 11:36, "Stas Malyshev" smalyshev@sugarcrm.com ezt írta:
Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
I found the script (scripts/cron/no-feedback or something like that) but I
have to figure out how it should be called (maybe via curl/wget) because it
expects a post variable and stuff and execution from cli errors out.
if somebody remembers the setup feel free to beat me with the restoration.
I've fixed up that script, executed so all bugs should be in the No
feedback status and added it to the crontab on the bugsweb machine.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
2013.02.17. 11:36, "Stas Malyshev" smalyshev@sugarcrm.com ezt írta:
Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
I found the script (scripts/cron/no-feedback or something like that) but
I have to figure out how it should be called (maybe via curl/wget) because
it expects a post variable and stuff and execution from cli errors out.
if somebody remembers the setup feel free to beat me with the restoration.I've fixed up that script, executed so all bugs should be in the No
feedback status and added it to the crontab on the bugsweb machine.--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
and it seems that somebody commented out the script in the crontab on feb
17 so it hasn't run since.
could the one who did that ellaborate why did was it needed and it is still
the case or can I re-activate it again?
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
2013.02.17. 11:36, "Stas Malyshev" smalyshev@sugarcrm.com ezt írta:
Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
I found the script (scripts/cron/no-feedback or something like that) but
I have to figure out how it should be called (maybe via curl/wget) because
it expects a post variable and stuff and execution from cli errors out.
if somebody remembers the setup feel free to beat me with the
restoration.I've fixed up that script, executed so all bugs should be in the No
feedback status and added it to the crontab on the bugsweb machine.--
Ferenc Kovács
@Tyr43l - http://tyrael.huand it seems that somebody commented out the script in the crontab on feb
17 so it hasn't run since.
could the one who did that ellaborate why did was it needed and it is
still the case or can I re-activate it again?--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
on a related not /local/systems/update-systems is also commented out in the
crontab, and it seems that it hasn't run since marc 8.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
2013.02.17. 11:36, "Stas Malyshev" smalyshev@sugarcrm.com ezt írta:
Hi!
I remember we used to have a script that goes over bugs DB and closes
bugs that are in "Feedback" status for too long. Does it still happen?
Because we have bugs that are in feedback status for a long time: like
this one: https://bugs.php.net/bug.php?id=52961 - in Feedback for 2+
years. If the script is not run for some reason, I think we should
restore it.Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
I found the script (scripts/cron/no-feedback or something like that) but
I have to figure out how it should be called (maybe via curl/wget) because
it expects a post variable and stuff and execution from cli errors out.
if somebody remembers the setup feel free to beat me with the
restoration.I've fixed up that script, executed so all bugs should be in the No
feedback status and added it to the crontab on the bugsweb machine.--
Ferenc Kovács
@Tyr43l - http://tyrael.huand it seems that somebody commented out the script in the crontab on feb
17 so it hasn't run since.
could the one who did that ellaborate why did was it needed and it is
still the case or can I re-activate it again?--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
I forgot to re-enable this after I got no response from you, so I've run it
manually and put it back to the cronjob so it should be running
periodically.
Expect a bunch of emails to the list about bugs being closed with
no-feedback was provided.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu