Extend the ability to skip geocoding when processing a large number of entity updates, like migrations or workspace publishing

The modern replacement for drupal_static() use-cases is a request attribute :)

Pushed a commit that uses the new request attribute during workspace publishing.

The MR looks good to me. One consideration here: As the presave hook is so expensive, it may be worth triggering a hook/an event that allows other modules to react when the hook is fired to skip further execution?

Looks good to me as well!

Looks good to me as well :)

Thanks for all this, but I had some difficulties to understand what exactly is going on here.
I particular how the attached #2 patch and the MR !60 are going to solve kind of same goals in a general way and in two different contexts of Migrate and Workspace modules.

It looks most of the folks here do belong to TAG1 and perfectly know what you are debating about and accomplishing within the Workspace module logics, isn't it?
Though it would also help some better description of what is going to be implemented here.
I mostly did and understood it myself ... digging in the the MR !60.
BUT it would be hard for a normal contributor to understand all the logics and its dependencies, also because the Workspace module is still missing basic documentation and help content.

So I feel to forward the following requests:

1. could you proper provide some better extended description of what (additional functional logics) is supposed to be achieved here, at once on both Migrate and Workspace sides? ...
2. and mostly could you properly let me know if both the #2 patch and the MR !60 should be deployed in parallel (as RTBC) or even better could / should the #2 patch be grouped / embedded in the MR !60 itself?

Thanks!

Ok I better inspected all this and all makes great sense to me also.
I just added a commit on better commenting.
Going to deploy this into new incoming 8.x-4.26 Geocoder release.

This needs to be re-open and implemented better - it doesn't account for non-browser context and breaks normal flow when a content entity is saved from the scheduled cron job or in a Drush call.

This is what I'm getting in logs:

   WARNING  Attempt to read property "attributes" on null in modules/contrib/geocoder/modules/geocoder_field/geocoder_field.module on line 179.
   Error  Call to a member function get() on null.

There is no request in set in this context.

Update: correction to the above statement - I was testing a piece of code with drush php which indeed doesn't have a request set, but drush php:script has it set.

Its being fixed in #3619252: Handle scenarios without request.