Has anyone else noticed that their Status Report always says "Composer security check is waiting to run on cron.", because it looks to me like it is not getting set to an empty array but I am not sure if it is my caching setup (Redis and Opcache) or something else.

Thanks in advance.

Comments

cmriley created an issue. See original summary.

arsmentis’s picture

arsmentis CreditAttribution: arsmentis commented

I'm seeing the exact same thing. My status report always says: "Composer security check is waiting to run on cron."

If I run the check manually, then everything looks good (e.g. drush composer-sa). However, if I then run cron manually from the browser, it goes back to "waiting to run on cron". I don't see anything in the logs to indicate there's a problem.

Does anyone have any insight to this?

Christopher Riley’s picture

Christopher Riley CreditAttribution: Christopher Riley commented

I have noticed that if I run the drush command ( drush composer-sa ) that the report works. I haven't dug into it yet but is it possible that this is buggy?

steveoriol’s picture

steveoriol
Location Grenoble 🇫🇷
CreditAttribution: steveoriol commented

Same issue here.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Version: 7.x-1.8 » 7.x-2.x-dev
Category: Support request » Bug report

This sounds like a possible bug.

Michael G’s picture

Michael G CreditAttribution: Michael G commented

I see tha same warning.
Composer library security updates 0 security advisories.
Composer security check is waiting to run on cron.