QueueWorker Error after updating to 4.1.9

I may be wrong but your deployment might have been at fault - state was indeed replaced by the key/value store and the error you are getting may be due to a partially old code base or some cache. Please retry the update, run `drush updb -y && drush cr` afterwards and let me know if the modules works.

If you change services, you need to reset the container.

The typical pattern is by implementing an empty postupdate hook. For example `user_post_update_sort_permissions` / `layout_builder_operation_link_post_update_remove_destination_form_link`.

I've hit this on a handful of projects so far, its annoying that it breaks CI requiring a manual CR beforehand. Especially if you dont have another module implementing an update that happens to do it for you.

A postupdate should be implemented.

A postupdate should be implemented.

Yeah maybe that's what we should be doing - feel free to create an MR. Alternatively adjust your deployment so it cleans the cache which has been the recommended approach since I can remember. I'm surprised your site doesn't break after every update.

Also please open up bug reports against the dev version of the module and only support requests against the stable version.

Just as follow up our deployment CI is pretty typical, its an Acquia Cloud Next hook as follows and it was clearing cache after deployment. Again too this white screen of death only happened to use ~5min after deployment when our Cypress Testing was about half way through testing, and we have about 509 cypress tests that test various routes of the CMS and features.

drush cr
drush updb -y
drush cim -y
drush cr
drush sset environment_indicator.current_release $deployed_tag

Update: So today I tried another migration again and its seemed to not be a problem, so could have just been a deployment hiccup? I guess well see if it happens to others or not to see if its an issue, and I guess worst case it can be solved with a cache clear I assume.

Once you clear the cache its solved.

Its only disruptive for the deployments running after the upgrade.

Linking cause 📌 simple_sitemap.queue_stashed_results should be in keyvalue instead of state Fixed

MR @ https://git.drupalcode.org/project/simple_sitemap/-/merge_requests/93

Thanks.

I have seen this same issue after deployment with the latest version of the module.

Looking at the code in the commit above, it seems that there's only an empty function, is that intentional? Or did we need something like

  drupal_flush_all_caches();

in there to actually clear the cache?

See 4

oh, sorry I missed it :-)

(strangely the problem still happened in my deployment even with that piece of code...)

dpi → closed merge request !93

Automatically closed - issue fixed for 2 weeks with no activity.