[HttpKernel] unserialize() conflicts with extended constructor

[kingcrunch]

Kernel::unserialize() prevents one from extending the constructor. Even when I overwrite serialize() and unserialize() something tries unserialize my custom AppKernel-class with some inappropiate during cache creation.

[Koc]

relates to #8500

[linaori]

I'm running against this issue too (see hostnet/hnDependencyInjectionPlugin#1). We've had to (more or less) implement the constructor with a custom argument but loading it from the cache is a bit buggy in some cases: Hostnet\HnDependencyInjectionPlugin\Symfony1Kernel::__construct(). I don't think this is an easy fix though.

[linaori]

@kingcrunch this issue isn't present for me anymore and I don't think this will be fixed. Is the issue still something you consider should be fixed?

[kingcrunch]

I am a little bit confused of this phrase

this issue isn't present for me anymore and I don't think this will be fixed.

If it isn't present anymore, it is fixed, right?

However, back in the days I used a different approach, thus for me it is not relevant anymore, what doesn't mean, it doesn't exists, or that it can affect other people.

[linaori]

This issue was for our custom kernel implementation for symfony1 migration, but most of our apps have been migrated to a point where we no longer need it.

[javiereguiluz]

Let's close this issue because @kingcrunch and @iltar no longer consider it relevant. We'll reopen it if we get more reports about this. Thanks!