| 1 |
If you wonder why I stopped filing new stabilization request, the |
| 2 |
pybugz-based script that was filing those bugs started failing. |
| 3 |
|
| 4 |
I have added some debugging statements to see what's going on, and |
| 5 |
here's what https://bugs.gentoo.org says as a response to pybugz's |
| 6 |
request to create a new bug: |
| 7 |
|
| 8 |
<div class="throw_error"> |
| 9 |
It looks like you didn't come from the right page (you have no valid |
| 10 |
token for |
| 11 |
the <em>create_bug</em> action while processing the |
| 12 |
'post_bug.cgi' script). The reason could be one of:<br> |
| 13 |
<ul> |
| 14 |
<li>You clicked the "Back" button of your web browser after having |
| 15 |
successfully |
| 16 |
submitted changes, which is generally not a good idea (but |
| 17 |
harmless).</li> |
| 18 |
<li>You entered the URL in the address bar of your web browser |
| 19 |
directly, |
| 20 |
which should be safe.</li> |
| 21 |
<li>You clicked on a URL which redirected you here <b>without your |
| 22 |
consent</b>, |
| 23 |
in which case this action is much more critical.</li> |
| 24 |
</ul> |
| 25 |
Are you sure you want to commit these changes anyway? This may result in |
| 26 |
unexpected and undesired results. |
| 27 |
</div> |
| 28 |
|
| 29 |
And there is a form below etc. etc. Note that only filing new bugs is |
| 30 |
affected (updating existing ones works fine). |
| 31 |
|
| 32 |
It's possible to repro with the command-line bugz tool (bugz ... post). |
| 33 |
|
| 34 |
I'm using pybugz-0.9.3 and I'm connecting to https://bugs.gentoo.org |
| 35 |
|
| 36 |
I posted this issue here because it's not obvious what to do with it. |
| 37 |
That version of pybugz worked for me before (20 February 2012). |
| 38 |
|
| 39 |
Any ideas? |
Archives