8000 RuntimeException after clearing cache · Issue #23977 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

RuntimeException after clearing cache #23977

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.

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

Closed
gharlan opened this issue Aug 24, 2017 · 7 comments
Closed

RuntimeException after clearing cache #23977

gharlan opened this issue Aug 24, 2017 · 7 comments

Comments

@gharlan
Copy link
Contributor
gharlan commented Aug 24, 2017
Q A
Bug report? yes
Feature request? no
BC Break report? no
RFC? no
Symfony version 3.3@dev

I'm using symfony/flex with sf 3.3.6 with symfony/config ^3.3@dev (because of #23753)

After clearing cache (without warmup) I get this exception:

screenshot 2017-08-24 15 03 10

After reloading everything is fine.

@chalasr
Copy link
Member
chalasr commented Aug 24, 2017

Already fixed in #23755, will be part of v3.3.7. Thanks for reporting.

@chalasr chalasr closed this as completed Aug 24, 2017
@gharlan
Copy link
Contributor Author
gharlan commented Aug 24, 2017

@chalasr #23755 fixed my other issue. This issue is not fixed, it is another exception!

@chalasr
Copy link
Member
chalasr commented Aug 24, 2017

Strange, it looks the same. Can you give the steps to reproduce (including the creation of your flex app and the packages you add into)? Are you sure that symfony/config is installed in its 3.3-dev version? (composer show symfony/config should help)

@chalasr chalasr reopened this Aug 24, 2017
@chalasr
Copy link
Member
chalasr commented Aug 24, 2017

You said "with sf 3.3.6", does that mean you require symfony/symfony? That would replace any symfony/config requirement by the 3.3.6 version of the component.

@gharlan
Copy link
Contributor Author
gharlan commented Aug 24, 2017

does that mean you require symfony/symfony?

No, I'm using these symfony packages (composer show):

screenshot 2017-08-24 23 59 35

Can you give the steps to reproduce (including the creation of your flex app and the packages you add into)?

I'm trying to create a reproducer package. After some more tests I found out that the exception only happens in a very special sequence:

  1. make cache-clear (no warmup!)
  2. Don't do a hard reload! Click on a link that triggers an ajax call. In my case it is a pjax call. The call needs some time to build the container, so the pjax timeout is reached.
  3. Pjax forces a non-ajax call because of the timeout. This call throws the exception.

Again: I will try to provide a reproducer package.

@gharlan
Copy link
Contributor Author
gharlan commented Aug 25, 2017

Now I got the same exception with another stacktrace:

screenshot 2017-08-25 14 46 47

This time a reload didn't help. Also cache:clear wasn't possible, had to hard delete the cache dir.

Don't know how to reproduce this one. But I try to create the reproducer package for the other exception stacktrace from above at this weekend.

@nicolas-grekas
Copy link
Member

@gharlan can you please confirm that #23989 fixes the issue?

fabpot added a commit that referenced this issue Aug 27, 2017
…icolas-grekas)

This PR was merged into the 2.7 branch.

Discussion
----------

[Debug] Remove false-positive check in DebugClassLoader

| Q             | A
| ------------- | ---
| Branch?       | 2.7
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #23977
| License       | MIT
| Doc PR        | -

In some edge case situations, DebugClassLoader generates false-positives (see linked issue, ping @gharlan).

Commits
-------

466da3f [Debug] Remove false-positive check in DebugClassLoader
@fabpot fabpot closed this as completed Aug 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
0