On Fri, Oct 13, 2017 at 12:02:43AM +0000, John Rouillard wrote:
> 
> Ralf, I am not seeing this with a working checkout of
> 5017c3422334 which is the tip.
> 
> I created an auditor that checks the title of the issue class.
> If the word rejectme is in the title, it raises Reject.
> 
> I see the rejection in the web interface and I get the
> bad title (with rejectme) redisplayed like I expect.
> 
> If I use the goto box to reload the same issue, I see the
> original title and no history changes in the history.
> 
> Also I have an auditor for msg that check for more than 2 links in the 
> body of the message. If I put in three, I get the reject and I do not 
> have the message saved nor do I find the body of the message in the db 
> directory.
> 
> How are you seeing the committed data that should be rejected?
> I agree 100% what you describe is a critical failure.

I have an application that has a "sign&send" button that calls a custom
web action. This does a commit(). Then several auditors are called which
should prevent the commit from going through. I will have to check the
exact path where this happens, I think I'm doing some actions on other
classes in the process.
The effect is that on the next sign&send I'm getting an assertion
violation because one change that shouldn't have made it through the
Reject was made.

I need to investigate this further, I've created the issue so that it
doesn't get lost. I feared it would not be reproduceable with a standard
setup...

I've already investigated to the point I'm sure this is a change in the
database (not just browser state). To get back to the expected state I
had to change a flag in the DB using psql...

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com