One of my CI tests deals with an edge case, in which a HTTPMovedPermanently is raised in deeply nested code. This almost never gets raised in Production - rules on the loadbalancer/gateway typically catch it.
With the debugtoolbar off, Pyramid serves the redirect. With the debugtoolbar enabled, it's caught by toolbar.py as an Exception and never makes it to the block of code dealing with `intercept_redirects`. Has anyone encountered this before and developed a good workaround? I feel like this test used to pass, but I can't find anything on our change history or Pyramid/Debugtoolbar's that would cause this change. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/ea13f955-007b-403f-a009-1a4e7ac5d288n%40googlegroups.com.
