-
-
Notifications
You must be signed in to change notification settings - Fork 291
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
PHP Fatal error: LocalLockFactory #585
Comments
Thanks for reporting! I will investigate and try to get a fix as soon as possible. |
@SirFlip I'm having some problems reproducing this bug. I have tried a few combinations, but I see you reported the PHP version as What's exactly the version you used? Or did you try the three of them? |
The main one is 7.4 but because of other stuff on the server I have the other ones as well and tried them out. |
I was asking because shlink is not yet compatible with PHP 7.4, and that's probably the reason it fails with that version. However, it should work with the other two versions. I will try to reproduce it with 7.4, just to make sure.
|
Ok, I just reproduced it with all three versions. It seems the problem is on the dist file somehow, since it works with the official docker image 🤔 I will try to get it fixed. |
@SirFlip I found the root cause for this issue. While a fix is provided, you can workaround it by doing this: Open the }
// Build container
+class_alias(\Symfony\Component\Lock\Factory::class, 'Shlinkio\Shlink\LocalLockFactory');
$config = require __DIR__ . '/config.php';
$container = new ServiceManager($config['dependencies']);
$container->setService('config', $config); After that, the error should be gone. |
Yes that works thank you very much for all your work. Merry Christmas and a happy new year |
I have just released Shlink 1.20.3, which includes this fix https://github.com/shlinkio/shlink/releases/tag/v1.20.3 |
How Shlink is set-up
Summary
when using the cli I get a PHP fatal error. Discovered, because the "visit:locate" didn't work. The web api and the link resolving works fine as far as I know.
Current behavior
How to reproduce
I don't know on other machines. For me its presistent on every command I tried.
The text was updated successfully, but these errors were encountered: