FelixFBecker keeps initializing #159

Activity

1. boogiefromzk commented on Jan 11, 2021

   

   boogiefromzk

   on Jan 11, 2021

   Last edited by boogiefromzk

   More actions

   Same on OpenSUSE Leap 15.3 & PHP 7.4.6, Atom 1.52.0 x64.

   I've found out that maximum PHP version supported is 7.3.9.
2. Jamie-Vandenbalck commented on Jan 11, 2021

   

   Jamie-Vandenbalck

   on Jan 11, 2021

   Author

   More actions

   When using older PHP version it works indeed. I couldn't find anywhere details about the supported php versions, they should mention it.
3. Jamie-Vandenbalck

   closed this as completedon Jan 11, 2021
4. boogiefromzk commented on Jan 11, 2021

   

   boogiefromzk

   on Jan 11, 2021

   More actions

   You shouldn't have closed it :) it's PHP 8 released already :)
5. Jamie-Vandenbalck commented on Jan 11, 2021

   

   Jamie-Vandenbalck

   on Jan 11, 2021

   Author

   More actions

   Ah yes :)
6. Jamie-Vandenbalck

   reopened this on Jan 11, 2021
7. redcuillin commented on Mar 13, 2021

   

   redcuillin

   on Mar 13, 2021

   More actions

   I haven't tested with PHP8, but for PHP7.4 the quickest/easiest solution for this problem is to ensure php.ini for the CLI is set to NOT output errors for use of deprecated functions.

   In other words, users with this problem probably have error_reporting set to E_ALL in php.ini. Changing it to :
   error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
   and restarting Atom should resolve the problem (it did for me). Preferable to downgrading PHP to 7.3.

   I believe a permanent fix is being sought here in the upstream code: https://github.com/felixfbecker/php-advanced-json-rpc/issues. It's probably a trivial change, but beyond my abilities.

   👍React with 👍5Reacted by Jens Svalgaard Kohrt, esttsujita, Jamie Vandenbalck, Peytoria and IgorVertikov
8. Peytoria commented on Jun 22, 2021

   

   Peytoria

   on Jun 22, 2021

   More actions

   I haven't tested with PHP8, but for PHP7.4 the quickest/easiest solution for this problem is to ensure php.ini for the CLI is set to NOT output errors for use of deprecated functions.

   In other words, users with this problem probably have error_reporting set to E_ALL in php.ini. Changing it to :
   error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
   and restarting Atom should resolve the problem (it did for me). Preferable to downgrading PHP to 7.3.

   I believe a permanent fix is being sought here in the upstream code: https://github.com/felixfbecker/php-advanced-json-rpc/issues. It's probably a trivial change, but beyond my abilities.

   This fix worked for me, ditched PHP 8 to go back to PHP 7.4. I am hopeful about a fix and this language server being updated for 8, but nothing for 2 years from Felix.
9. fredden commented on Jul 12, 2021

   

   fredden

   on Jul 12, 2021

   More actions

   I've been able to reliably reproduce this.

   1. With a fresh Atom profile (mv ~/.atom ~/.atom-backup)
   2. Install these packages: apm install atom-ide-ui ide-php linter
   3. Start Atom. (This will install busy-signal, intentions, linter-ui-default.)
   4. Choose "Disable Linter" in the prompt
      Screen-shot

      
   5. From now on, every PHP file opened will result in a new PHP Language Server being started.

   The following error can be seen on the JavaScript console within Atom:

   ~/.atom/packages/ide-php/node_modules/atom-languageclient/build/lib/server-manager.js:5 Uncaught (in promise) Error: Emitter has been disposed
       at Emitter.on (/usr/share/atom/resources/app/static/<embedded>:11)
       at yt.onDidDestroy (~/.atom/packages/linter/dist/index.js:1)
       at LinterPushV2Adapter.attach (~/.atom/packages/ide-php/node_modules/atom-languageclient/build/lib/adapters/linter-push-v2-adapter.js:28)
       at PHPLanguageClient.startExclusiveAdapters (~/.atom/packages/ide-php/node_modules/atom-languageclient/build/lib/auto-languageclient.js:362)
       at PHPLanguageClient.<anonymous> (~/.atom/packages/ide-php/node_modules/atom-languageclient/build/lib/auto-languageclient.js:298)
       at Generator.next (<anonymous>)
       at fulfilled (~/.atom/packages/ide-php/node_modules/atom-languageclient/build/lib/auto-languageclient.js:4)
   

   I've worked around this by disabling the "Diagnostics" feature within atom-ide-ui.
10. LoganTann commented on Jul 18, 2021

    

    LoganTann

    on Jul 18, 2021

    More actions

    I haven't tested with PHP8, but for PHP7.4 the quickest/easiest solution for this problem is to ensure php.ini for the CLI is set to NOT output errors for use of deprecated functions.

    In other words, users with this problem probably have error_reporting set to E_ALL in php.ini. Changing it to :
    error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
    and restarting Atom should resolve the problem (it did for me). Preferable to downgrading PHP to 7.3.

    Tried using php8.0, I can confirm this workaround don't work.
    It's sad to see that I'm not able to try this plugin just because it uses deprecated functions...

    👍React with 👍3Reacted by Rahul Saini, Marcel Steinger and Joonas