Cache ignores HTML vs. Drush [#314821]

0. Install and configure Drush.
1. TRUNCATE cache_coder.
2. Run a review via the browser.
3. Run the same review via Drush.

Results: Drush results contain HTML, from the cache created in step 2. The opposite is also true:

1. TRUNCATE cache_coder.
2. Run a review via Drush.
3. Run the same review via the browser.

Results: Browser results contain plain text results from Drush.

Comments

Comment #1

danepowell commented 16 December 2011 at 16:40

I wonder if this is the same root cause for my problem?

For Mailhandler, I have mailhandler.coder_ignores.txt, and if I change any of the lines in this file, the changes do not get picked up by Coder- it seems that something is being cached.

To reproduce:

Create an ignores file, and add one ignore line.
Run code review- Coder will properly report "1 warning flagged to be ignored".
Add one more ignore line to the ignores file. You can even clear caches via the GUI at this point, it doesn't matter.
Run code review again- Coder still reports "1 warning flagged to be ignored".
Edit coder.module and insert dsm($ignores); after $ignores = coder_get_ignores(); - this somehow forces coder to pick up the changes...
Run coder review again- now Coder properly reports "2 warnings flagged to be ignored".

This is very consistent and reproducible. Does it sound the same, or should I open a new issue?

Comment #2

danepowell commented 4 January 2012 at 17:36

Re: #1: I have confirmed that clearing all caches via admin toolbar does not clear the coder_cache table. If I manually empty this table, then new ignore lines get picked up. ~~Oddly, however, only changes to 'core' ignores (style, sql) get picked up. 'Plug-in' ignores (coder_tough_love) still seem to be getting cached.~~ #1394024: Ignored lines not respected for rules with callbacks