Follow-up from #1194136: Re-organise core cache bins. I may have opened an issue for this already and lost it, apologies if so.
We can rename the default 'cache' bin to 'cache_default'
Looks like this:
- arguments: ['@container.namespaces', '@cache.cache', '@language_manager', '@module_handler', '@string_translation']
+ arguments: ['@container.namespaces', '@cache.default', '@language_manager', '@module_handler', '@string_translation']
Also that bin is currently special-cased in storage implementations to avoid the table being cache_cache, that could be removed.
Comments
Comment #1
damiankloip commentedHere is an initial patch, let's see what fails.
The main issue with trying to rename this is that in conflicts with our current directive of using 'default' under the cache settings in settings.php to change the default backend for all bins. Spoke to catch briefly about this. We could nest the per bin stuff one level deeper. So
Would become:
Comment #3
damiankloip commented1: 2221065.patch queued for re-testing.
Comment #5
berdirConflicted in migration.services.yml.
Comment #7
berdir5: 2221065-5.patch queued for re-testing.
Comment #9
damiankloip commented5: 2221065-5.patch queued for re-testing.
We know this will fail - just re-testing so we can see/debug this on the bot servers.
Comment #11
berdirRe-roll.
Comment #13
damiankloip commentedHopefully this will fix those...
Comment #15
damiankloip commentedReroll.
Comment #16
damiankloip commented15: 2221065-15.patch queued for re-testing.
Comment #18
damiankloip commentedRerolled after cache bins re-organisation.
Comment #20
damiankloip commentedReroll fun.
Comment #22
wim leersThis should at least allow Drupal to be installed again :)
Comment #23
damiankloip commentedHAHA, yes. That will indeed help.
Comment #25
wim leersComment #27
damiankloip commentedApologies, the reroll in @#20 was completely wrong (see the size) and the subsequent rerolls were based on that, which is just trying to redo work already done.
Another reroll based on #18.
Comment #28
wim leersHah :)
Comment #29
sunFixing issue title to prevent confusion.
That said, I'm a bit terrified by the amount of instances of "default" in the D8 code base, all having different meanings... And for a cache bin, I wonder whether "default" really is an appropriate term, given that each bin has a clear use-case, and the "default" bin should only be the last resort...?
I don't want to start a bikeshed, but how about naming it "misc" instead of "default"?
"misc" == Dumping ground for miscellaneous stuff that doesn't fit into any of the other bins for any reason.
Comment #30
damiankloip commentedSeems like that is that start of a bikeshed to me .... :)
Seems a bit extreme? Did you just grep for 'default' or something?!
Default is a popular word. This seems like a logical use of 'default', plus this is the default cache bin, so the name is apt IMO. I'm sorry but misc is not a good name.
Comment #31
damiankloip commentedRerolled.
Comment #32
wim leersI agree with #30 completely. "default" is clear, it's just used in many different contexts, not in different meanings.
Comment #33
catchYes agreed on the naming as well. Default is very clear and just a common word, it's not like 'module' or 'entity' where our usage is specific.
Patch no longer applies unfortunately though.
Comment #34
berdirOnly context changes, so back to RTBC.
Comment #36
jibran34: 2221065-34.patch queued for re-testing.
Comment #38
damiankloip commentedComment #39
damiankloip commentedJust a rerolled with above change for the library discovery patch. I think this can still be RTBC.
Comment #41
catchCommitted/pushed to 8.x, thanks!