Skip to content
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

Need a composer.lock file or a fix to work with current version of dependencies #18

Open
seba1rx opened this issue Jan 9, 2024 · 0 comments

Comments

@seba1rx
Copy link

seba1rx commented Jan 9, 2024

Hello, I just want to report that since there is no composer.lock file in this package, trying to use the RxThruwayClient with the current version of dependencies will raise an error:

PHP Fatal error:  Uncaught Exception: Please set a default scheduler factory in /mnt/c/DEV/RxThruwayClient/vendor/reactivex/rxphp/src/Scheduler.php:24
Stack trace:
#0 /mnt/c/DEV/RxThruwayClient/vendor/reactivex/rxphp/src/Subject/ReplaySubject.php(52): Rx\Scheduler::getDefault()
#1 /mnt/c/DEV/RxThruwayClient/src/Subject/WebSocketSubject.php(31): Rx\Subject\ReplaySubject->__construct()
#2 /mnt/c/DEV/RxThruwayClient/src/Client.php(40): Rx\Thruway\Subject\WebSocketSubject->__construct()
#3 /mnt/c/DEV/RxThruwayClient/examples/subscribe.php(8): Rx\Thruway\Client->__construct()
#4 {main}
  thrown in /mnt/c/DEV/RxThruwayClient/vendor/reactivex/rxphp/src/Scheduler.php on line 24

Today I updated my dependencies and noticed this problem, for now I am downgrading the dependencies to their previous version.

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 8 updates, 1 removal
  - Removing voryx/event-loop (3.0.2)
  - Upgrading react/dns (v1.11.0 => v1.12.0)
  - Upgrading react/promise (v2.10.0 => v2.11.0)
  - Upgrading react/promise-stream (v1.6.0 => v1.7.0)
  - Upgrading react/socket (v1.14.0 => v1.15.0)
  - Upgrading rx/websocket (2.1.8 => 2.2.0)
  - Upgrading seba1rx/sessionadmin (dev-main 8bdecda => dev-main 4e86497)
  - Upgrading symfony/http-foundation (v6.3.8 => v6.4.2)
  - Upgrading symfony/routing (v6.3.5 => v6.4.2)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 8 updates, 1 removal
  - Downloading symfony/routing (v6.4.2)
  - Downloading symfony/http-foundation (v6.4.2)
  - Downloading react/promise-stream (v1.7.0)
  - Downloading rx/websocket (2.2.0)
  - Downloading seba1rx/sessionadmin (dev-main 4e86497)
  - Removing voryx/event-loop (3.0.2)
  - Upgrading symfony/routing (v6.3.5 => v6.4.2): Extracting archive
  - Upgrading symfony/http-foundation (v6.3.8 => v6.4.2): Extracting archive
  - Upgrading react/promise (v2.10.0 => v2.11.0): Extracting archive
  - Upgrading react/dns (v1.11.0 => v1.12.0): Extracting archive
  - Upgrading react/socket (v1.14.0 => v1.15.0): Extracting archive
  - Upgrading react/promise-stream (v1.6.0 => v1.7.0): Extracting archive
  - Upgrading rx/websocket (2.1.8 => 2.2.0): Extracting archive
  - Upgrading seba1rx/sessionadmin (dev-main 8bdecda => dev-main 4e86497): Extracting archive

I used the following to downgrade the affected dependecies in order to make it work again:

 composer require voryx/event-loop 3.0.2
 composer require rect/dns 1.11.0
 composer require react/dns 1.11.0
 composer require react/promise 2.10.0
 composer require react/promise-stream 1.6.0
 composer require react/socket 1.14.0
 composer require rx/websocket 2.1.8
 composer require symfony/http-foundation 6.3.8
 composer require symfony/routing 6.3.5

Is it possible for you to provide a fix for this or a composer.lock file ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant