User context missing when using toUrl in some circumstances

I was experiencing the same error in my Drupal site, core ver. 9.1.0 after importing a database from one of my team member's localhost. That was occurring because of the same problem as is described in #28. However my fix was different. I opened the database file-I had received from my colleague and imported into my localhost-and observed that an insert statement for the anonymous user (uid, 0) was present in the SQL script. For some reason the uid of that row got changed to 186; I found this out by executing a select query with a where condition for the uuid column with the value copied and pasted from the database script. I just changed 186 to 0.

Closed 🐛 The 'entity:user' context is required and not present Closed: duplicate as duplicate of this issue.

I just experienced this in a kernel test in some custom code as well. I believe when we had code running Url::fromUri('internal:/taxonomy/term/1').

Cross-posting #3357354-16: The 'entity:user' context is required and not present → here.
The patch solves my issue on 2 projects caused by image styles as explained there. Few, what an absolute horror to debug. Thank you so much!

@Berdir from #12: Could the introduction of image lazy loading in core be directly related to the emergence of this issue?

Edit: I will reroll the patch for 10.1.x

Ok the assert is wrong there it seems.
Not exactly sure what to assert tbh, we mainly need to ensure that there are no exceptions thrown even though the current user context is NULL (because the anonymous user is used).

We could also do this but it's not really what we are trying to test:

$context_repository = $this->container->get('context.repository');
$contexts = $context_repository->getAvailableContexts();
$this->assertArrayHasKey('@user.current_user_context:current_user', $contexts);
$this->assertFalse($contexts['@user.current_user_context:current_user']->hasContextValue());

PS: Very interesting to see that such a simple URL causes the issue as anonymous. My case in #42 was hitting the same issue but from \Drupal\Core\Routing\AccessAwareRouter::match

FWIW, 🐛 Many calls to ContextRepository::getAvailableContexts() due to entity upcasting Needs review removes that whole chunk completely, I'd expect that fixes the issue as well.

Indeed it does, and I see no side effects. I'll use that instead then. Thanks for pointing it out.
I guess we could close this one then?
Cheers

I'm not sure, maybe wait until it's actually resolved. I'd love to get it done, but no idea how feasible it is to get it done soon. Hard to move it forward as it's related to several other language upcasting issues.

For those looking for a simple workaround to fix their kernel tests, the following additions to my kernel test class suppressed the exception.

I imported Drupal\Tests\user\Traits\UserCreationTrait and added that trait to my kernel test class with use UserCreationTest. Then I added $this->setUpCurrentUser() in my class's setUp method. In my case, I didn't need to call that method any optional arguments.

There are a lot of
"

Drupal\Component\Plugin\Exception\ContextException: The 'entity:user' context is required and not present. in Drupal\Core\Plugin\Context\Context->getContextValue()

" mentions across the versions.

For me the #44 🐛 User context missing when using toUrl in some circumstances Needs work is a life-saver. Thanks.

If you don't want to make a user current, this workaround creates the anon user in a kernel test:

use UserCreationTest

    $values = [
      'uid' => 0,
      'status' => 0,
      'name' => '',
    ];
    $this->createUser(values: $values);

Note that AFAICT the next call to createUser() will create user 1, so call it again if you don't want you actual test users to be that.

As per #45 this is probably no longer needed as per 🐛 Many calls to ContextRepository::getAvailableContexts() due to entity upcasting Needs review which has landed. Marking PMNMI for someone to verify if there is anything left to do here.