Composer GOS Websocket bundle symfony 2.8 dependency trouble / Exception - composer-php

Hi i want to use gos websocket bundle but keep getting this error
PHP Fatal error: Uncaught Symfony\Component\Debug\Exception\UndefinedMethodException:
Attempted to call an undefined method named "setArgument" of class
"Symfony\Component\DependencyInjection\Definition".
Did you mean to call e.g. "addArgument", "getArgument", "getArguments"
or "setArguments"? in /var/www/vhosts/foo/vendor/gos/web-
socket-bundle/DependencyInjection/CompilerPass/PingableDriverCompilerPass.php:37
so it seems the interface is not compatible with symfony 2.8 ? Here are the versions installed with composer
gos/pnctl-event-loop-emitter v0.1.7
gos/pubsub-router-bundle v0.3.4
gos/web-socket-bundle v1.8.13
gos/websocket-client v0.1.2
symfony/symfony v2.8.11
anybody any idea what is the problem and what i can do from here idea?

I am using Thruway library for websockets in my project running on PHP 5.4 (works well with PHP 7 too). if you are in early stage of setting up websocket in your project I would recommend you to switch to Thruway, which has clear documentation and support.

Related

Octobercms : Undefined Exception Symfony\Component\HttpKernel\Exception\NotFoundHttpException

I know there is a lot similar questions of this one. But non of them fixed my issue.
I run php artisan serve without any issue but when i try to load the page I get this error with no explicit message:
Undefined
Exception
Symfony\Component\HttpKernel\Exception\NotFoundHttpException
I've got the same project file + php version + laravel version that my teamate but he does not get the error.
Do you have any more ideas please ?

STR class error when deploying lumen to hosting

I was Deplyoying my lumen project to cpanel hosting , i did it as usual same as other person but i keep getting this error
'''
PHP Parse error: syntax error, unexpected '?' in /home/k5169896/public_html/apiFunderAsia/vendor/illuminate/support/Str.php on line 681
'''
This is usually caused by the version of PHP you are using, check the version on your new host, if it is < PHP 7.2 which is the minimum requirement for Lumen then it causes this issue.

Error while hosting CodeIgniter Framework to online server

I need to solve the below issue:
When I tried to hosting codeIgniter framework to my online server, this error occurred.
A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/lviscomp/public_html/system/core/Output.php:528)
Filename: core/Common.php
Line Number: 573
Backtrace:
A PHP Error was encountered
Severity: Error
Message: XCache: Cannot init
Filename: Unknown
Line Number: 0
Backtrace:
I had the same xcache issue in my Laravel application. I resolved it by upgrading the PHP version.
I think this might help you as well.
Go to your cPanel
Go to software section and click "select PHP version"
Change your PHP version from "native" to 5.4 or 5.5 (It will give you a list of drivers with checkboxes)
Select Xcache and enable it
Save your settings as well as PHP version
I hope it will work.
For Above Error header information already sent...
Click here!
XCache: Cannot init
Try Disable XCACHE from the Php configuration..
if this doesn't work ..
I think this is a question for your host.

Debugging a Laravel 5 artisan migrate unexpected T_VARIABLE FatalErrorException

When running artisan migrate on a Laravel 5 project, it is failing with the following FatalErrorException:
$ artisan migrate -vvv --force
[Symfony\Component\Debug\Exception\FatalErrorException] syntax
error, unexpected '$table' (T_VARIABLE)
How do I get the file and line that is causing the error?
If in anyway relevant, I'm on a Windows 7 x64 machine with WAMP - PHP 5.6 and Laravel Framework version 5.1.10 (LTS).
There might be a semicolon or bracket missing a line
Check all in your migration files.
Laravel is configured to create daily log files for your application
which are stored in the storage/logs directory.
http://laravel.com/docs/5.1/errors#logging
This class Symfony\Component\Debug\Exception\FatalErrorException has some differences compared with the other Exception classes and it is not properly presented by the "error renderers" or "error notifiers".
A New sentry "error notifier" ("getsentry/sentry-php" version >= "2.0") will give you a proper stack trace.
Here is issue where is reported : https://github.com/getsentry/sentry-php/issues/761
Here is the PR for fix : https://github.com/getsentry/sentry-php/pull/763

Magento Upgrade 1.3 1.4 Pear Error Invalid Argument foreach

Hello I am trying to upgrade Magento 1.3 to 1.4. using this guide http://astrio.net/blog/magento-upgrade-guide/
I tried the command ./pear upgrade -f magento-core/Mage_All_Latest-stable
I got the error
Notice: Array to string conversion in PEAR/REST/10.php on line 85
PHP Notice: Array to string conversion in /home/www/sss/staging.mysite.net/public/downloader/pearlib/php/PEAR/REST/10.php on line 85
So I tried Magento upgrade PEAR error ( specifically this command ./pear channel-update connect.magentocommerce.com/core ) .. but that gives me the error:
Updating channel "connect.magentocommerce.com/core"
Channel "connect.magentocommerce.com/core" is not responding over http://, failed with message: File http://connect.magentocommerce.com:80/core/channel.xml not valid (received: HTTP/1.1 404 Not Found
)
Trying channel "connect.magentocommerce.com/core" over https:// instead
Cannot retrieve channel.xml for channel "connect.magentocommerce.com/core" (File https://connect.magentocommerce.com:443/core/channel.xml not valid (received: HTTP/1.1 404 Not Found
))
Ideas?
You waited a bit too long to upgrade if you want to use Magento Connect to do it.
In order to upgrade 1.4 to a later version using Magento Connect requires you to upgrade to the 1.5 PEAR Connect package which switches from using ./pear to ./mage. There is no equivalent to doing this upgrade for 1.3 to use Connect to upgrade to 1.4.
You will need to manually download and apply the Magento 1.4 upgrade by downloading the full package from the Magento CE Download page under the Release Archives for the version of 1.4 you wish to upgrade to.
Of course, test it hard on a staging server as you will find that there will be template issues, database upgrade issues, etc.

Resources