8000 You have requested a non-existent service "debug.error_handler_configurator". · Issue #50504 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content
/ symfony Public

You have requested a non-existent service "debug.error_handler_configurator". #50504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
TheNerka opened this issue May 31, 2023 · 4 comments
Closed

You have requested a non-existent service "debug.error_handler_configurator". #50504

TheNerka opened this issue May 31, 2023 · 4 comments
Labels
Bug Status: Needs Review

Comments

@TheNerka
Copy link

Symfony version(s) affected

6.3.0

Description

after upgrade symfony from 6.2 to 6.3 calls cache clear got error:

You have requested a non-existent service "debug.error_handler_configurator".

How to reproduce

upgrade from 6.2 to 6.3

Possible Solution

No response

Additional Context

No response
@TheNerka TheNerka added the Bug label May 31, 2023
@xabbuh
Copy link
Member
xabbuh commented May 31, 2023

Does #50498 fix this?

@nicolas-grekas nicolas-grekas mentioned this issue May 31, 2023
Merged
@symfony symfony deleted a comment from stloyd May 31, 2023
nicolas-grekas added a commit that referenced this issue May 31, 2023
@nicolas-grekas
bug #50498 [FrameworkBundle] ease migration to symfony 6.3 (lyrixx)
14b1088 
This PR was merged into the 6.3 branch.

Discussion
----------

[FrameworkBundle] ease migration to symfony 6.3

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | kind of
| New feature?  | no
| Deprecations? | no
| Tickets       | #50504
| License       | MIT
| Doc PR        | -

Commits
-------

06ab7ec [FrameworkBundle] ease migration to symfony 6.3
@OleksiiBulba
Copy link
Contributor

Hello! Is there any possible workaround to fix this error message before the fix will be released?

@stof
Copy link
Member
stof commented Jun 14, 2023

@OleksiiBulba you can use the dev version of the package.

Alternatively, you could remove the old cache (the one generated by the old version of Symfony) with rm -rf var/cache/prod/*

@OleksiiBulba
Copy link
Contributor

Thanks @stof, updating to the dev package and downgrading back to release helped (I did it before seeing your answer) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Status: Needs Review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@nicolas-grekas @stof @xabbuh @TheNerka @carsonbot @OleksiiBulba
0