NoSuchFlowExecutionException

Dan McLaughlin dmclaughlin at tech-consortium.com
Thu Oct 20 15:40:45 UTC 2022


Good point.  We are using CSRF.  I'll try disabling that to see if
that might narrow it down to that portion of the code.  That's easy
for me to test.

--

Thanks,

Dan

On Thu, Oct 20, 2022 at 10:36 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> Back to dev...
>
> The CSRF stuff would seem like the most connected code that was impacted by the change, if it's enabled anyway.
>
> Otherwise there's really no reason why our tests would be passing (*), but I haven't run the testbed in a while and I can give it a quick test to make sure it's still functional.
>
> The exception is likely due to the flow terminating in some way that your code is not expecting, it's not specifically connected to anything that's wrong. But it could be terminating with an error of course.
>
> * Are you on Windows? We're digging into a sporadic issue with the CAS tests on Windows that I am fearing may be related to bugs in Java in their handling of SecureRandom. We moved to what is supposed to be the modern way to instantiate all that. And that JDK code has a history of being so insane and subject to constant churn in patches that you wouldn't believe professional Java programmers could have built it.
>
> -- Scott
>
>


More information about the dev mailing list