Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[FrameworkBundler] Fix cache:clear with buildDir#39360

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
chalasr merged 1 commit intosymfony:5.2fromjderusse:fix-warmup
Dec 15, 2020

Conversation

@jderusse
Copy link
Member

QA
Branch?5.2
Bug fix?yes
New feature?no
Deprecations?no
TicketsFix#39232
LicenseMIT
Doc PR

Since#36515 there are 2 caches dircacheDir andbuildDir. For BC reason both points to the same folders, but when app don't use the same folder, many thing are broken:
This PR fixes several issues introduces by the above PR:

  • some files are persisted in the wrong folder (App_KernelDevDebugContainerDeprecations.log,App_KernelDevDebugContainer.xml)
  • LoggerDataCollector looks into cache_dir, whileCompiler.log is written in build_dir andDeprecations.log were written in cache_dir before this PR
  • the logic that mirror cacheDir into buildDir at the end of CacheClearCommand does not make sens whencache_dir andbuild_dir are not identical.
  • Files generated in cacheDir are trashed at the end of CacheWarming (initial issue)

Nyholm, dmaicher, Kocal, bertrandseurot, mbabker, xaviermarchegay, ogizanagi, alongosz, chalasr, rogierknoester, and spajxo reacted with thumbs up emojimnapoli and bobvandevijver reacted with heart emoji
@carsonbotcarsonbot added this to the5.2 milestoneDec 7, 2020
@jderussejderusseforce-pushed thefix-warmup branch 5 times, most recently from5b7dcc1 toe8e3aabCompareDecember 8, 2020 16:56
@jderusse
Copy link
MemberAuthor

FYI test in red because test in FWB requires fix Kernel form this same PR (that's why in changed composer.json to 5.2.1)

@nicolas-grekas
Copy link
Member

(the tests on Windows might need some love.)

@jderusse
Copy link
MemberAuthor

(the tests on Windows might need some love.)

Fixed with my must favorite trick. Doing nothing... ^^

In fact, previous failure were very strange: I guess appveyor had FS issue
Failed to remove non-empty directory: Fixtures/var
Permission denied: Fixtures/var/cache
Failed to create dir: var/cache/resetting

@nicolas-grekas
Copy link
Member

(rebase needed)

}
}

class NoBuildDirKernelextends TestAppKernel
Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Could you have a look@chalasr ? Previous code can't work, becausekernel.build_dir is now needed to build the container (and now needed to initialize thecache:clear command).
I refactored the code t build a container and then remove the parameter from the dumped container.

@alongosz
Copy link

Hey Guys, just wanted to let you know that this PR resolves ourblocker in Ibexa DXP preventing us from upgrading to Symfony 5.2. Thanks 👍

lserwatka, dmaicher, and adamwojs reacted with thumbs up emojilserwatka reacted with hooray emoji

@chalasr
Copy link
Member

Thanks for fixing this bug@jderusse.

massimilianobraglia and alongosz reacted with hooray emoji

@chalasrchalasr merged commita7fd98b intosymfony:5.2Dec 15, 2020
@Kocal
Copy link
Member

Thanks@jderusse ❤️ ❤️

jderusse reacted with heart emoji

@alongosz
Copy link

Thanks@jderusse 🎉
When can we expect a patch release / tag? :-)

jderusse reacted with heart emoji

@derrabus
Copy link
Member

By the end of the month, usually.

alongosz and jderusse reacted with thumbs up emoji

@lserwatka
Copy link

@derrabus we are launching new Ibexa DXP 3.3.0 on December 30th. We are eager to use Symfony 5.2 as all our tests are passing with this fix.

Could you make a Symfony 5.2.1 release before December 30th?

@derrabus
Copy link
Member

Could you make a Symfony 5.2.1 release before December 30th?

I'm pretty confident that 5.2.1 happens before Dec 30th. 😃 But please test against 5.2-dev in the meantime to make sure the changes work for you.

lserwatka and alongosz reacted with thumbs up emojilserwatka and alongosz reacted with heart emoji

@jderussejderusse deleted the fix-warmup branchDecember 15, 2020 11:49
@mnapoli
Copy link
Contributor

Thank you@jderusse!

@Wirone
Copy link
Contributor

First of all, thanks for the fix - I've encountered this problems in the project created with CLI binary few days ago and had to downgrade to 5.1 to continue working on it.

Personally I think that fixes like this one should be considered as hotfixes andreleased as soon as possible. Symfony 5.2.0 was released 16 days ago and is really unstable because of problems with cache (at least indev environment for development purposes). And now we hear that new version will be released at the end of the month which means for ~30 days straight really broken version will be installed by default bysymfony new ... and possibly upgraded to in already existing apps. That's... quite interesting 🤔

derrabus reacted with confused emoji

@jderusse
Copy link
MemberAuthor

keep calm and runrm -rf var/cache/*

Wirone and alpha1917 reacted with confused emojibobvandevijver reacted with rocket emoji

@Wirone
Copy link
Contributor

Thank you@fabpot for earlier release 👍

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@chalasrchalasrchalasr approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

5.2

Development

Successfully merging this pull request may close these issues.

10 participants

@jderusse@nicolas-grekas@alongosz@chalasr@Kocal@derrabus@lserwatka@mnapoli@Wirone@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp