Tracy shows error page with out of date error after code has been fixed!

[artfulrobot]

I've noticed this a couple of times. I load a page and it crashes, Tracy gives me a big red page with helpful info on it.

I then fix the problem, and reload the page - but the error won't go away.

For example the screenshot below shows and error saying "Call to undefined function ProcessWore\pappub_inlay_request()", and then highlights a line in my code that (now because it's been fixed) doesn't show the code from the error message! One part of the page is lying to me, and it doesn't go away until some timeout. I'm guessing a cache timeout? But I've tried adding a ?something=123 var and that didn't fix anything either: still received the old error that no longer correlates to the actual code; Tracy seems to be intercepting my actual code to show me the old error!

 

Anyone else had this?

 

[adrian]

Have you tried a hard reload in the browser? I know it sounds strange, but I have seen PW return cached results before. Please let me know if that works.

[artfulrobot]

@adrian oh yeah, I'm all about the hard reload. I have basically stuck tape over my Ctrl key.

But sadly it didn''t help.

It's so weird how it exhibits the error, yet quotes the corrected code!

[adrian]

@artfulrobot - sorry, I really don't know. I haven't ever seen this or had anyone else mention it. Is it specific to one server / machine, or can you reproduce on others?

[artfulrobot]

I only have one pw site at the mo, and I can't reproduce it reliably. It's just happened a few times and I wondered if anyone else had the problem.

The main bother of it is that, typically I'm in a hurry to debug the crash, not debug the debugger at the time of the crash!