Message6038
I've investigated a little further. In the working version calling the
db.close in main (around line 386 in cgi/client.py) will *not* commit
the wrong value that was set before a Reject occurs, while the latest
tip will commit the erroneous value at that point.
So it looks like this *only* occurs in the web-interface. I guess we
don't have too much test coverage in that area ;-)
Ralf |
|
| Date |
User |
Action |
Args |
| 2017-10-19 09:57:11 | schlatterbeck | set | messageid: <1508407031.59.0.213398074469.issue2550955@psf.upfronthosting.co.za> |
| 2017-10-19 09:57:11 | schlatterbeck | set | recipients:
+ schlatterbeck, rouilj |
| 2017-10-19 09:57:11 | schlatterbeck | link | issue2550955 messages |
| 2017-10-19 09:57:10 | schlatterbeck | create | |
|