Skip to content

Revert "feature #21038 [FrameworkBundle] deprecated cache:clear with warmup (fabpot)" #23825

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

Merged
merged 1 commit into from
Aug 18, 2017

Conversation

nicolas-grekas
Copy link
Member

This reverts commit 3495b35, reversing
changes made to 7f7b897.

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

Sibling to #23792: there is no need to trigger the deprecation in 3.3 if we un-deprecate in 3.4.

@nicolas-grekas nicolas-grekas added this to the 3.3 milestone Aug 8, 2017
@nicolas-grekas nicolas-grekas changed the base branch from master to 3.3 August 8, 2017 06:42
@@ -132,8 +126,6 @@ private function warmupCache(InputInterface $input, OutputInterface $output, $re
* @param string $warmupDir
* @param string $realCacheDir
* @param bool $enableOptionalWarmers
*
* @internal to be removed in 4.0
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note that in 3.4, the command class is @final so we can still make them private in 4.0. I'll take care of it when merging up.

@nicolas-grekas nicolas-grekas changed the title Revert "feature #21038 [FrameworkBundle] deprecated cache:clear with warmup (fabpot) Revert "feature #21038 [FrameworkBundle] deprecated cache:clear with warmup (fabpot)" Aug 8, 2017
…r with warmup (fabpot)"

This reverts commit 3495b35, reversing
changes made to 7f7b897.
@nicolas-grekas nicolas-grekas force-pushed the revert-no-warmup-deprec branch from 34369ad to 9009970 Compare August 8, 2017 06:44
@fabpot
Copy link
Member

fabpot commented Aug 18, 2017

I would not revert this in 3.3 as it helps with Flex. Here is the output right now when doing cache:clear on a Symfony 3.3 project using Flex:

image

As you can see, the warning helps explain the fatal error and provide a way to fix the issue. Instead, I would change the warning to explain that without the --no-warmup flag, the command does not work in 3.3 (but that it will work again in 3.4). Far from ideal, but at least, it provides a better experience for our users.

@fabpot
Copy link
Member

fabpot commented Aug 18, 2017

Investigating the issue a bit more, fixing the cache:clear in Flex is quite easy: see symfony/recipes#154.

So, let's remove the final keyword in Flex's Kernel and merge this one.

@fabpot
Copy link
Member

fabpot commented Aug 18, 2017

Thank you @nicolas-grekas.

@fabpot fabpot merged commit 9009970 into symfony:3.3 Aug 18, 2017
fabpot added a commit that referenced this pull request Aug 18, 2017
…clear with warmup (fabpot)" (nicolas-grekas)

This PR was merged into the 3.3 branch.

Discussion
----------

Revert "feature #21038 [FrameworkBundle] deprecated cache:clear with warmup (fabpot)"

This reverts commit 3495b35, reversing
changes made to 7f7b897.

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

Sibling to #23792: there is no need to trigger the deprecation in 3.3 if we un-deprecate in 3.4.

Commits
-------

9009970 Revert "feature #21038 [FrameworkBundle] deprecated cache:clear with warmup (fabpot)"
@nicolas-grekas nicolas-grekas deleted the revert-no-warmup-deprec branch August 18, 2017 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants