spatie / laravel-ray Goto Github PK

View Code? Open in Web Editor NEW

280.0 20.0 58.0 535 KB

Debug with Ray to fix problems faster in Laravel apps

Home Page: https://myray.app

License: MIT License

PHP 99.99% Blade 0.01%

php laravel debug

laravel-ray's Introduction

Debug with Ray to fix problems faster

This package can be installed in any PHP application to send messages to the Ray app.

The desktop app:

can be used in WordPress, Laravel, PHP, JavaScript function
shows you models, mails, queries, ... IN Laravel
helps you to debug locally or via SSH
lets you measure performance & set breakpoints

Documentation

You can find the full documentation on our documentation site.

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.

laravel-ray's People

Stargazers

Watchers

Forkers

leemcd56 bullenb srwiez palazari19 patinthehat harris21 jstoone timrspratt filipac markvesterskov crynobone esseremmerik pieczarkazsolt thecaliskan sinnbeck dheia icarojobs simbiant lukeraymonddowning shuvroroy abenerd niektenhoopen basduchambre xndbogdan janpantel iuriimattos2 tonning rubinred defstudio bogdankharchenko ahmedhelalahmed sergiy-petrov vesper8 simonjnsson keithbrink idiegonl juanrangel dead23angel adam-digemy stein-j ohmygodvt95 summercms squatto fullstackfool byt3sage ayoobmh php-ltd lentex mohamedsabil83 elsayed85 kornalaravel grantholle peter279k lloricode marksalmon gromnan roqianjas

laravel-ray's Issues

Windows: Ray seems not be running at http://localhost:23517

I've followed the instructions. but when I run my app with a ray call it gives this error:Ray seems not be running at http://localhost:23517

I'm using Winds 10 and using wsl2 to run my app using php artisan serve.

Laravel package support

While attempting to use ray() in a laravel package test suite:

"require-dev": {
    "orchestra/testbench": "~5.0",
     "phpunit/phpunit": "^9.2",
    "spatie/laravel-ray": "^1.0"
},

Illuminate\Contracts\Container\BindingResolutionException: Unresolvable dependency resolving [Parameter #0 [ <required> array $settings ]] in class Spatie\Ray\Settings\Settings

Ray installation failure

Describe the bug

Unable to try out Ray because of installation failure. Here is the error from the composer require spatie/laravel-ray command

composer require  spatie/laravel-ray
Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is now
available and you should upgrade. See https://getcomposer.org/2
Using version ^1.3 for spatie/laravel-ray
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2.0 is now
available and you should upgrade. See https://getcomposer.org/2
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install laravel/framework v8.21.0
    - Conclusion: don't install laravel/framework v8.20.1
    - Conclusion: don't install laravel/framework v8.20.0
    - Conclusion: don't install laravel/framework v8.19.0
    - Conclusion: don't install laravel/framework v8.18.1
    - Conclusion: don't install laravel/framework v8.18.0
    - Conclusion: don't install laravel/framework v8.17.2
    - Conclusion: don't install laravel/framework v8.17.1
    - Conclusion: don't install laravel/framework v8.17.0
    - Conclusion: don't install laravel/framework v8.16.1
    - Conclusion: don't install laravel/framework v8.16.0
    - Conclusion: don't install laravel/framework v8.15.0
    - Conclusion: don't install laravel/framework v8.14.0
    - Conclusion: don't install laravel/framework v8.13.0
    - Conclusion: remove laravel/framework v8.10.0
    - Conclusion: don't install laravel/framework v8.10.0
    - spatie/laravel-ray 1.3.0 requires illuminate/database ^7.0|^8.13 -> satisfiable by laravel/framework[8
.x-dev, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v
8.20.0, v8.20.1, v8.21.0], illuminate/database[7.x-dev, 8.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.
0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7
.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7
.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23
.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29
.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.
6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8
.17.0, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.20.0, v8.20.1, v8.21.0].
    - spatie/laravel-ray 1.3.1 requires illuminate/database ^7.0|^8.13 -> satisfiable by laravel/framework[8
.x-dev, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v
8.20.0, v8.20.1, v8.21.0], illuminate/database[7.x-dev, 8.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.
0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7
.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7
.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23
.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29
.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.
6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8
.17.0, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.20.0, v8.20.1, v8.21.0].
    - spatie/laravel-ray 1.3.2 requires illuminate/database ^7.0|^8.13 -> satisfiable by laravel/framework[8
.x-dev, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v
8.20.0, v8.20.1, v8.21.0], illuminate/database[7.x-dev, 8.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.
0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7
.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7
.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23
.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29
.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.
6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8
.17.0, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.20.0, v8.20.1, v8.21.0].
    - spatie/laravel-ray 1.3.3 requires illuminate/database ^7.0|^8.13 -> satisfiable by laravel/framework[8
.x-dev, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v
8.20.0, v8.20.1, v8.21.0], illuminate/database[7.x-dev, 8.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.
0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7
.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7
.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23
.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29
.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.
6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8
.17.0, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.20.0, v8.20.1, v8.21.0].
    - spatie/laravel-ray 1.3.4 requires illuminate/database ^7.0|^8.13 -> satisfiable by laravel/framework[8
.x-dev, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8.17.0, v8.17.1, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v
8.20.0, v8.20.1, v8.21.0], illuminate/database[7.x-dev, 8.x-dev, v7.0.0, v7.0.1, v7.0.2, v7.0.3, v7.0.4, v7.
0.5, v7.0.6, v7.0.7, v7.0.8, v7.1.0, v7.1.1, v7.1.2, v7.1.3, v7.10.0, v7.10.1, v7.10.2, v7.10.3, v7.11.0, v7
.12.0, v7.13.0, v7.14.0, v7.14.1, v7.15.0, v7.16.0, v7.16.1, v7.17.0, v7.17.1, v7.17.2, v7.18.0, v7.19.0, v7
.19.1, v7.2.0, v7.2.1, v7.2.2, v7.20.0, v7.21.0, v7.22.0, v7.22.1, v7.22.2, v7.22.3, v7.22.4, v7.23.0, v7.23
.1, v7.23.2, v7.24.0, v7.25.0, v7.26.0, v7.26.1, v7.27.0, v7.28.0, v7.28.1, v7.28.2, v7.28.3, v7.28.4, v7.29
.0, v7.29.1, v7.29.2, v7.29.3, v7.3.0, v7.30.0, v7.30.1, v7.4.0, v7.5.0, v7.5.1, v7.5.2, v7.6.0, v7.6.1, v7.
6.2, v7.7.0, v7.7.1, v7.8.0, v7.8.1, v7.9.0, v7.9.1, v7.9.2, v8.13.0, v8.14.0, v8.15.0, v8.16.0, v8.16.1, v8
.17.0, v8.17.2, v8.18.0, v8.18.1, v8.19.0, v8.20.0, v8.20.1, v8.21.0].
    - Can only install one of: laravel/framework[8.x-dev, v8.10.0].
    - don't install illuminate/database 7.x-dev|don't install laravel/framework v8.10.0
    - don't install illuminate/database 8.x-dev|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.4|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.5|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.6|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.7|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.0.8|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.1.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.1.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.1.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.1.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.10.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.10.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.10.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.10.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.11.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.12.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.13.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.14.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.14.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.15.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.16.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.16.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.17.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.17.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.17.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.18.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.19.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.19.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.2.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.2.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.2.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.20.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.21.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.22.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.22.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.22.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.22.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.22.4|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.23.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.23.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.23.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.24.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.25.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.26.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.26.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.27.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.28.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.28.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.28.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.28.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.28.4|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.29.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.29.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.29.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.29.3|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.3.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.30.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.30.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.4.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.5.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.5.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.5.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.6.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.6.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.6.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.7.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.7.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.8.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.8.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.9.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.9.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v7.9.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.13.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.14.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.15.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.16.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.16.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.17.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.17.2|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.18.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.18.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.19.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.20.0|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.20.1|don't install laravel/framework v8.10.0
    - don't install illuminate/database v8.21.0|don't install laravel/framework v8.10.0
    - Installation request for laravel/framework (locked at v8.10.0, required as ^8.0) -> satisfiable by lar
avel/framework[v8.10.0].
    - Installation request for spatie/laravel-ray ^1.3 -> satisfiable by spatie/laravel-ray[1.3.0, 1.3.1, 1.
3.2, 1.3.3, 1.3.4].

Based on my understanding, this has to do with the version of Laravel. However, on the Ray website, it is mentioned that Laravel 7 is supported. Not certain what is wrong. Issue #45 suggests that it is the composer v 1.x that is leading to the issue. However, in this case, does not seem to be so.

Versions
Unable to set up yet

You can use composer show to get the version numbers of:

spatie/ray package version:
spatie/laravel-ray package version (if applicable):

Unable to setup yet.

PHP version: 7.4.6

PHP 7.4.6 (cli) (built: May 12 2020 11:38:54) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Xdebug v2.9.6, Copyright (c) 2002-2020, by Derick Rethans

Laravel version: Laravel Framework 8.10.0

To Reproduce
Steps to reproduce the behavior:

Install the software on Windows 10, and then set it up in the laravel application.
During setup require fails. Composer o/p added already.

Expected behavior

Ray to be set up completely and be ready for debugging.

Desktop (please complete the following information):

OS: Windows 10
Version: 10.0.19041 Build 19041

Laravel 6 support

Hi guys, great package. My question is, would you consider merging a PR that adds Laravel 6 support?

I know you like to keep things current, hence, why I'm checking before I spend the time on updating the composer versions, git hub action yml etc.

The reason for Laravel 6 support is the projects my company work on require the LTS version (client requirements to have the longer support window).

I don't feel there is anything in the illuminate packages that is "breaking", but you will know more than me I'm sure.

Thanks

Exception when running tests in Github Actions

Hey guys and thanks for the product!

I required Laravel Ray as an dev dependency and now my test's are failing when they are running in Github Actions. It seems like Ray is still trying to send logs to it's Client. Whichi think should'nt be the case when running in Github Actions.

Exception: Ray seems not be running at http://localhost:23517

Do i miss something in my configuration?

"composer install" cannot find "../ray" repository

In composer.json, spatie/ray is a local repository using a path so it can be found. Since it is now both published, this can be removed so Composer can pull the package.

Fix displaying model relations

Configured host reverted to localhost

Due to an error in the brackets in the service provider, the host setting is not passed to the client.

I've submitted a pull request (#14) to address this

Ray doesn't show file that executed ray helper

Windows 10, IIS

Laravel v8.21.0

Controller:

class MyController extends Controller
{
    ...
    public function index()
    {
        ray()->showQueries();

        ray('Hello world');

        return $this->repository->allCarWashes();
    }
    ...
}

Document how to open ray window

How can we display the ray output?
Should it be opened in a separate window like Telescope ? I tried http://localhost:23517/ but that does not work.
Should it be visible together with the loaded page? I looked at the page source, but nothing is added.

Dead Page and Question

This is a dead page -- https://github.com/spatie/laravel-ray/discussions/new?category=q-a

Further, to my question, if ray is not running, I am thinking that code should continue and not throw an error? Is this not the case?

Package "spatie/laravel-ray" is not installed

Hello I have a mistake that tells me that I didn't install spatie/laravel-ray when it's a good installation can you help me? Thanks (I'm on windows 10)
https://flareapp.io/share/17Dn1GXm#F12

Composer dependencies

This is very likely to be an issue my end, running PHP 7.4.11 and Laravel 7.22.4, when running compser require I get:

Using version ^1.0 for spatie/laravel-ray
./composer.json has been updated
Running composer update spatie/laravel-ray
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - spatie/laravel-ray 1.0.0 requires spatie/ray dev-master -> satisfiable by spatie/ray[dev-master].
    - spatie/laravel-ray[1.0.1, ..., 1.0.2] require spatie/ray ^1.0 -> satisfiable by spatie/ray[1.0.0, 1.0.1].
    - spatie/ray[dev-master, 1.0.0, ..., 1.0.1] require symfony/console ^4.2|^5.2 -> found symfony/console[v4.2.0-BETA1, ..., 4.4.x-dev, v5.2.0-BETA1, ..., 5.x-dev] but the package is fixed to v5.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires spatie/laravel-ray ^1.0 -> satisfiable by spatie/laravel-ray[1.0.0, 1.0.1, 1.0.2].

If I run with -W for all dependencies I get even more errors. I've had successful composer updates today so don't want to go changing too many things.

Thanks

WSL 2 + Docker + VSCode - file references open in new VSCode window instead of in existing one

Describe the bug
I'm trying to make it possible to click on a file link in Ray and have VSCode open it. I'm running it using Windows 10, WSL 2 + the official Docker integration as well as the official VSCode "Remote WSL" extension.

This means that VSCode runs inside the WSL distro (in my case Ubuntu 20.04) and then sends all data to the VSCode GUI remote which is running on Windows 10.

I understand that it sounds a bit confusing, but I almost got it to work.

The path rewrites work correctly, however, every time I click on a file name in Ray, it opens a new VSCode window instead of opening the file in the already opened one. This might be a VSCode/WSL2 limitation but it does make using Ray a bit of a pain, so I'm hoping someone could look into this or if there is any approach that would make this work as expected.

My configuration is as follows:

<?php
return [
    'host' => 'host.docker.internal',
    'port' => 23517,
    /* This is the root path inside the Docker container */
    'remote_path' => '/var/www/html/',
    /* This is the WSL NFS path that corresponds to the root of the Docker container */
    'local_path' => '\\wsl$\\Ubuntu-20.04\\home\\k\\GitHub\\php8\\src-compose\\',
];

Versions
Ray version (you can see this in "About Ray"): 1.2.2.0

You can use composer show to get the version numbers of:
WP plugin version:

PHP version: 8.0
Laravel version: N/A

To Reproduce
Steps to reproduce the behavior:

Install Docker, VSCode, WSL 2 and a WSL 2 distro & the Windows version of Ray on Windows 10.
Install the WSL Remote extension in VSCode.
Activate the Docker WSL2 support in Docker options.
Run a PHP application that has Ray installed inside Docker (I'm using this image)
Configure the project in a similar way to my ray.php (paths will have to be adjusted)
Try to log something and then open the file definition under the log entry.
The file opens in a new VSCode instance.

Expected behavior
See earlier text.

Screenshots
N/A

Desktop (please complete the following information):

OS: Windows 10

Additional context
N/A

Fix location of @ray blade directive

Better support for logged mailables

See this discussion: spatie/ray#77 (reply in thread)

path mapping needed + phpstorm not found

most projects believe, there exists only mac or Linux and virtualization is - sadly - never an issue.
windows users often use virtualization to let code run 100% within Linux, like in my case.
so code is running on a Linux host within docker. so of course, paths on Linux or inside docker
has nothing todo with the paths my windows-phpstorm is using. so when ray('hello word') send
the file and path to the desktop app, the path needs to be mapped to the local windows path
to make it working with phpstorm. ray on windows shows me of course the path that is used
inside docker (in my Linux host), so for instance /home/blabla/something.php and on windows
the real path is C:\blabla\something.php 😏

clicking on the file link within windows says (translated) something like: you need to install a new app to open this phpstorm link.

what if the ray desktop app is not running

hi, I would like to ask: in some projects, it´s not uncommon to use some debug outputs in the code and don´t remove them. because they provide some interesting info. so let's say you work in a small team within one project, some people are using ray, some not. so when you add "ray()" in some situations and let this in, even in production, is there an option to tell ray that there is no app running so instead of trying to connect the app, that will end in a timeout (i guess) because the app is not running, it should behave more like a "print_r" and shouldn´t search for the app in the first place? so for example, the ray config inside code would have a switch like "env=debug" or "env=produktion" and only if "env=debug" ray will try to connect to the app and in all other cases it wouldn´t even try because it knows, there is no app running?

Open With VSCODE prompt

Hi there
Whenever I click the ray link to open it in VSCODE, it always shows me this prompt.
I know it's vscode related, but is there a way to ALWAYS accept ?

Using Ray with Docker can't open files

I realize this is new but great work! I am running a Docker container and have Ray setup and working. However, my path in the container is /app/public and the Ray app defaults to the path from the container, not the host machine which makes sense.

Perhaps a config option to set the "file path/root" to the project would resolve this issue?

Ray processes keep running after closing

Can't install the package

Description

Hello, I just purchased the app and tried to install the package in my Laravel 8 but got an error requirements could not be resolved to an installable set of packages

composer require spatie/laravel-ray

Using version ^1.3 for spatie/laravel-ray
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - spatie/ray 1.3.2 requires composer-runtime-api ^2.0 -> no matching package found.
    - spatie/ray 1.3.1 requires composer-runtime-api ^2.0 -> no matching package found.
    - spatie/ray 1.3.0 requires composer-runtime-api ^2.0 -> no matching package found.
    - Installation request for spatie/laravel-ray ^1.3 -> satisfiable by spatie/laravel-ray[1.3.0].
    - Conclusion: remove symfony/console v5.1.7
    - Conclusion: don't install symfony/console v5.1.7
    - spatie/laravel-ray 1.3.0 requires spatie/ray ^1.3 -> satisfiable by spatie/ray[1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.3.4].
    - spatie/ray 1.3.3 requires symfony/console ^4.2|^5.2 -> satisfiable by symfony/console[4.2.x-dev, 4.3.x-dev, 4.4.x-dev, 5.2.x-dev, 5.x-dev, v4.2.0, v4.2.0-BETA1, v4.2.0-BETA2, v4.2.0-RC1, v4.2.1, v4.2.10, v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9, v4.3.0, v4.3.0-BETA1, v4.3.0-BETA2, v4.3.0-RC1, v4.3.1, v4.3.10, v4.3.11, v4.3.2, v4.3.3, v4.3.4, v4.3.5, v4.3.6, v4.3.7, v4.3.8, v4.3.9, v4.4.0, v4.4.0-BETA1, v4.4.0-BETA2, v4.4.0-RC1, v4.4.1, v4.4.10, v4.4.11, v4.4.12, v4.4.13, v4.4.14, v4.4.15, v4.4.16, v4.4.17, v4.4.18, v4.4.2, v4.4.3, v4.4.4, v4.4.5, v4.4.6, v4.4.7, v4.4.8, v4.4.9, v5.2.0, v5.2.0-BETA1, v5.2.0-BETA2, v5.2.0-BETA3, v5.2.0-RC1, v5.2.0-RC2, v5.2.1].
    - spatie/ray 1.3.4 requires symfony/console ^4.2|^5.2 -> satisfiable by symfony/console[4.2.x-dev, 4.3.x-dev, 4.4.x-dev, 5.2.x-dev, 5.x-dev, v4.2.0, v4.2.0-BETA1, v4.2.0-BETA2, v4.2.0-RC1, v4.2.1, v4.2.10, v4.2.11, v4.2.12, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9, v4.3.0, v4.3.0-BETA1, v4.3.0-BETA2, v4.3.0-RC1, v4.3.1, v4.3.10, v4.3.11, v4.3.2, v4.3.3, v4.3.4, v4.3.5, v4.3.6, v4.3.7, v4.3.8, v4.3.9, v4.4.0, v4.4.0-BETA1, v4.4.0-BETA2, v4.4.0-RC1, v4.4.1, v4.4.10, v4.4.11, v4.4.12, v4.4.13, v4.4.14, v4.4.15, v4.4.16, v4.4.17, v4.4.18, v4.4.2, v4.4.3, v4.4.4, v4.4.5, v4.4.6, v4.4.7, v4.4.8, v4.4.9, v5.2.0, v5.2.0-BETA1, v5.2.0-BETA2, v5.2.0-BETA3, v5.2.0-RC1, v5.2.0-RC2, v5.2.1].
    - Can only install one of: symfony/console[4.3.x-dev, v5.1.7].
    - Can only install one of: symfony/console[4.4.x-dev, v5.1.7].
    - Can only install one of: symfony/console[v4.3.10, v5.1.7].
    - Can only install one of: symfony/console[v4.3.11, v5.1.7].
    - Can only install one of: symfony/console[v4.3.4, v5.1.7].
    - Can only install one of: symfony/console[v4.3.5, v5.1.7].
    - Can only install one of: symfony/console[v4.3.6, v5.1.7].
    - Can only install one of: symfony/console[v4.3.7, v5.1.7].
    - Can only install one of: symfony/console[v4.3.8, v5.1.7].
    - Can only install one of: symfony/console[v4.3.9, v5.1.7].
    - Can only install one of: symfony/console[v4.4.0, v5.1.7].
    - Can only install one of: symfony/console[v4.4.0-BETA1, v5.1.7].
    - Can only install one of: symfony/console[v4.4.0-BETA2, v5.1.7].
    - Can only install one of: symfony/console[v4.4.0-RC1, v5.1.7].
    - Can only install one of: symfony/console[v4.4.1, v5.1.7].
    - Can only install one of: symfony/console[v4.4.10, v5.1.7].
    - Can only install one of: symfony/console[v4.4.11, v5.1.7].
    - Can only install one of: symfony/console[v4.4.12, v5.1.7].
    - Can only install one of: symfony/console[v4.4.13, v5.1.7].
    - Can only install one of: symfony/console[v4.4.14, v5.1.7].
    - Can only install one of: symfony/console[v4.4.15, v5.1.7].
    - Can only install one of: symfony/console[v4.4.16, v5.1.7].
    - Can only install one of: symfony/console[v4.4.17, v5.1.7].
    - Can only install one of: symfony/console[v4.4.18, v5.1.7].
    - Can only install one of: symfony/console[v4.4.2, v5.1.7].
    - Can only install one of: symfony/console[v4.4.3, v5.1.7].
    - Can only install one of: symfony/console[v4.4.4, v5.1.7].
    - Can only install one of: symfony/console[v4.4.5, v5.1.7].
    - Can only install one of: symfony/console[v4.4.6, v5.1.7].
    - Can only install one of: symfony/console[v4.4.7, v5.1.7].
    - Can only install one of: symfony/console[v4.4.8, v5.1.7].
    - Can only install one of: symfony/console[v4.4.9, v5.1.7].
    - Can only install one of: symfony/console[5.2.x-dev, v5.1.7].
    - Can only install one of: symfony/console[5.x-dev, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0-BETA1, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0-BETA2, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0-BETA3, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0-RC1, v5.1.7].
    - Can only install one of: symfony/console[v5.2.0-RC2, v5.1.7].
    - Can only install one of: symfony/console[v5.2.1, v5.1.7].
    - Can only install one of: symfony/console[4.2.x-dev, v5.1.7].
    - Can only install one of: symfony/console[v4.2.0, v5.1.7].
    - Can only install one of: symfony/console[v4.2.0-BETA1, v5.1.7].
    - Can only install one of: symfony/console[v4.2.0-BETA2, v5.1.7].
    - Can only install one of: symfony/console[v4.2.0-RC1, v5.1.7].
    - Can only install one of: symfony/console[v4.2.1, v5.1.7].
    - Can only install one of: symfony/console[v4.2.10, v5.1.7].
    - Can only install one of: symfony/console[v4.2.11, v5.1.7].
    - Can only install one of: symfony/console[v4.2.12, v5.1.7].
    - Can only install one of: symfony/console[v4.2.2, v5.1.7].
    - Can only install one of: symfony/console[v4.2.3, v5.1.7].
    - Can only install one of: symfony/console[v4.2.4, v5.1.7].
    - Can only install one of: symfony/console[v4.2.5, v5.1.7].
    - Can only install one of: symfony/console[v4.2.6, v5.1.7].
    - Can only install one of: symfony/console[v4.2.7, v5.1.7].
    - Can only install one of: symfony/console[v4.2.8, v5.1.7].
    - Can only install one of: symfony/console[v4.2.9, v5.1.7].
    - Can only install one of: symfony/console[v4.3.0, v5.1.7].
    - Can only install one of: symfony/console[v4.3.0-BETA1, v5.1.7].
    - Can only install one of: symfony/console[v4.3.0-BETA2, v5.1.7].
    - Can only install one of: symfony/console[v4.3.0-RC1, v5.1.7].
    - Can only install one of: symfony/console[v4.3.1, v5.1.7].
    - Can only install one of: symfony/console[v4.3.2, v5.1.7].
    - Can only install one of: symfony/console[v4.3.3, v5.1.7].
    - Installation request for symfony/console (locked at v5.1.7) -> satisfiable by symfony/console[v5.1.7].

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.

Versions
Ray version (you can see this in "About Ray"): 1.0.7

spatie/laravel-ray package (trying to install): 1.3

PHP version: 7.4 (Docker image: php:7.4-fpm-alpine)
Laravel version: 8.18.1

To Reproduce
Steps to reproduce the behavior:

In a Laravel 8 application
try to install the laravel package by executing compose require spatie/laravel-ray
See an error

Expected behavior
The laravel-ray package to be installed

Screenshots

Desktop (please complete the following information):

OS: macOS
Version: Catalina 10.15.7
Docker: 19.03.13

Additional context

Ray seems not be running at http://localhost:23517

Hi, nice looking package!

I'm having trouble getting it up and running. When calling ray() I'm receiving the error Ray seems not be running at http://localhost:23517.

Any reason why I'd be getting this error?

Thanks!

ExecutedQueryPayload time should display as milliseconds

Describe the bug
The queries that are logged show the Time as μs when it should be milliseconds.

https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Events/QueryExecuted.php#L22

    /**
     * The number of milliseconds it took to execute the query.
     *
     * @var float
     */
    public $time;

Versions
Ray version (you can see this in "About Ray"): 1.2.0

You can use composer show to get the version numbers of:

spatie/ray package version:
spatie/laravel-ray package version (if applicable):

PHP version: 7.4
Laravel version: 8.21.0

To Reproduce
Steps to reproduce the behavior:

log a query

Expected behavior
time is shown with 'ms' suffix

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. macOS] macOS
Version [e.g. 22] 10.15.7

Additional context
Add any other context about the problem here.

Unable to receive calls in Homestead

First of all, love the name!

I'm unable to receive any messages using Ray from Homestead, I wish I had more details but unfortunately the welcome never disappears and no errors appear.

Returns string but nothing ever appears in the Ray client.

Route::get('test', function () {
    ray('Hello');

    return 'done!';
});

macOS Cataline Version 10.15.7
Laravel 7.30.1
Vagrant 2.2.14
Homestead 10.17.0
PHP 7.4.13

500 with openbasedir

Hi
Locally it works perfect. But when the code was sent to the server, the site crashes.
I was trying with:
composer require spatie/laravel-ray
first, and then with:
composer require spatie/laravel-ray --dev
with env set to production. Same issue:

[2021-01-07 22:12:30] production.ERROR: is_dir(): open_basedir restriction in effect. File(/usr/home/myaccount) is not within the allowed path(s): (/usr/home/myaccount/domains/mydoma.in/public_html:/tmp:/usr/share:/usr/local/share:/dev:/usr/home/myaccount/domains/mydoma.in/public:/tmp:/usr/share:/usr/local/share:/dev:/usr/local/share/pear:/usr/home/myaccount/domains/mydoma.in:/usr/home/myaccount/domains) {"exception":"[object] (ErrorException(code: 0): is_dir(): open_basedir restriction in effect. File(/usr/home/myaccount) is not within the allowed path(s): (/usr/home/myaccount/domains/mydoma.in/public_html:/tmp:/usr/share:/usr/local/share:/dev:/usr/home/myaccount/domains/mydoma.in/public:/tmp:/usr/share:/usr/local/share:/dev:/usr/local/share/pear:/usr/home/myaccount/domains/mydoma.in:/usr/home/myaccount/domains) at /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php:35)
[stacktrace]
0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'is_dir(): open_...', '/usr/home/ekome...', 35, Array)
1 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(35): is_dir('/usr/home/ekome...')
2 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(16): Spatie\Ray\Settings\SettingsFactory->searchConfigFiles('/usr/home/ekome...')
3 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/ray/src/Settings/SettingsFactory.php(9): Spatie\Ray\Settings\SettingsFactory->getSettingsFromConfigFile('/usr/home/ekome...')
4 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(37): Spatie\Ray\Settings\SettingsFactory::createFromConfigFile('/usr/home/ekome...')
5 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(826): Spatie\LaravelRay\RayServiceProvider->Spatie\LaravelRay{closure}(Object(Illuminate\Foundation\Application), Array)
6 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(712): Illuminate\Container\Container->build(Object(Closure))
7 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(796): Illuminate\Container\Container->resolve('Spatie\Ray\Sett...', Array, true)
8 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Container/Container.php(651): Illuminate\Foundation\Application->resolve('Spatie\Ray\Sett...', Array)
9 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(781): Illuminate\Container\Container->make('Spatie\Ray\Sett...', Array)
10 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(119): Illuminate\Foundation\Application->make('Spatie\Ray\Sett...', Array)
11 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(51): app('Spatie\Ray\Sett...')
12 /usr/home/myaccount/domains/mydoma.in/vendor/spatie/laravel-ray/src/RayServiceProvider.php(25): Spatie\LaravelRay\RayServiceProvider->registerBindings()
13 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(627): Spatie\LaravelRay\RayServiceProvider->register()
14 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php(75): Illuminate\Foundation\Application->register(Object(Spatie\LaravelRay\RayServiceProvider))
15 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(604): Illuminate\Foundation\ProviderRepository->load(Array)
16 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterProviders.php(17): Illuminate\Foundation\Application->registerConfiguredProviders()
17 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(230): Illuminate\Foundation\Bootstrap\RegisterProviders->bootstrap(Object(Illuminate\Foundation\Application))
18 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(152): Illuminate\Foundation\Application->bootstrapWith(Array)
19 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(136): Illuminate\Foundation\Http\Kernel->bootstrap()
20 /usr/home/myaccount/domains/mydoma.in/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(110): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
21 /usr/home/myaccount/domains/mydoma.in/public/index.php(59): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
22 {main}
"}

select all + delete does not work

Describe the bug

Inside the Ray Electron app:
Menu: Edit -> Select all (STRG+A) then, Menu: Edit -> Delete, does nothing
"Select All" does not select the individual dumps, it only selects the whole text on that electron-page.
the whole menu item "Edit" seems to be useless here, because it looks like that "Copy" is the only item
that has a useful function here. but we all know the hotkey for "copy" so maybe the menu item "Edit"
can be removed in that app?

anyway... I would like to know how I am able to delete the entries ;)

Versions
1.0.5.0

Expected behavior
delete all dumps on the current page

Desktop (please complete the following information):

OS: Windows 10

Ray doesn't show the proper file where ray() was called.

I have added ray('my test') to my index.php file, but it's showing "helpers.php:21" from the ray package as file where it was called.

The same happens if I call ray('my test from ' . __CLASS__ ); from several different files.

My environment: OSX with MAMP Pro 5.7

Lumen Support

Hey guys,

congrats on the release of ray! It would be nice if the Laravel integration could also support Lumen. I have tried it locally and the only blockers should be the following:

Spatie\LaravelRay\DumpRecorder\DumpRecorder requires the Application Contract which Lumen does not support, but it could be replaced by Illuminate\Container\Container instead
The RayServiceProvider registers a blade listener which is not supported by Lumen. A check if it is loaded could resolve this

If I have enough time later on I will create a pull request to resolve this, but it would be nice to hear your opinion regarding Lumen support within this package.

is_dir(): open_basedir restriction in effect. File(/data/sites/web) is not within the allowed path(s):

Versions
spatie/ray (1.3.2)
spatie/laravel-ray (1.3.0)

You can use composer show to get the version numbers of:

spatie/ray package version:
spatie/laravel-ray package version (if applicable):

PHP version:
7.4

Steps to reproduce the behavior:

nstall spatie/laravel-ray (locally)
Test locally -> works perfect
git add , git commit, git push
On staging server, git pull
Reload website: is_dir(): open_basedir restriction in effect. File(/data/sites/web) is not within the allowed path(s):

I use a shared hosting.

OS: macOS Catalina
Version: version 10.15.7

Documentation Error

On the

Usage -> In Laravel

page, there is a reference to a function called stopLoggingQueries . In the example following, it is shown as ** stopShowingQueries**. My guess is the name of this function changed during development.

Thanks for the super cool tool!!

issue #35 is not yet solved

please reopen a not solved issue or at least help to understand what your customer is doing wrong

Exception if Ray not open

Environment: Windows using Homestead

If the Ray app is not open and the project has spatie/laravel-ray as a dependency, if you hit any exception the following exception will be displayed instead of the actual Exception.

Ray seems not be running at http://10.0.2.2:23517

This can be changed by setting 'send_log_calls_to_ray' => false

But I'm wondering if it would be better to see if it is a log and if so don't throw the not running exception?

OutOfBoundsException Package "spatie/laravel-ray" is not installed

I installed Version 1.0.8 (1.0.8) of Ray.

I required it with composer using composer require spatie/laravel-ray and ran the "My first ray call" -- no problems and worked beautifully.

I pushed the commit to production.

I ran an artisan command in production and received this error:

OutOfBoundsException

  Package "spatie/laravel-ray" is not installed

  at vendor/composer/composer/src/Composer/InstalledVersions.php:110
    106▕      */
    107▕     public static function getVersion($packageName)
    108▕     {
    109▕         if (!isset(self::$installed['versions'][$packageName])) {
  ➜ 110▕             throw new \OutOfBoundsException('Package "' . $packageName . '" is not installed');
    111▕         }
    112▕
    113▕         if (!isset(self::$installed['versions'][$packageName]['version'])) {
    114▕             return null;

      +11 vendor frames
  12  [internal]:0
      Illuminate\Foundation\Bootstrap\HandleExceptions::handleException()
forge@production-uam:~/avtechnix.com$  OutOfBoundsException
OutOfBoundsException: command not found

I ran dump-autoload in production and error re-appeared.

I ran COMPOSER_MEMORY_LIMIT=-1 composer require spatie/laravel-ray in production, dumped auto-load and had same error.

What else can I do to silence this stoppage and error ... i need to run this artisan command.

InstalledVersion does not detect spatie/laravel-ray as being installed

Running the latest version of Laravel Ray, Laravel 8.21.0 on a MacBook Pro, any attempt so far has given me the same response. The package is installed, exists within the vendor/spatie folder and is listed in the composer.json and composer.lock file.

Below I included the exception and first trace

{
  "message": "Package \"spatie/laravel-ray\" is not installed",
  "exception": "OutOfBoundsException",
  "file": "/Users/christian/Code/project/vendor/composer/composer/src/Composer/InstalledVersions.php",
  "line": 110,
  "trace": [
    {
      "file": "/Users/christian/Code/project/vendor/spatie/laravel-ray/src/Ray.php",
      "line": 149,
      "function": "getVersion",
      "class": "Composer\\InstalledVersions",
      "type": "::"
    },
}

ray()->queries() BadMethodCallException

Describe the bug
ray()->queries() and ray()->showQueries() both throw BadMethodCallException exceptions.

Versions
Ray 1.04
Laravel Ray 1.20

PHP version: 7.4.11
Laravel version: 8.21.0

To Reproduce
Steps to reproduce the behavior:
Add ray()->queries() or ray()->showQueries()

Expected behavior
Expect queries to be output to the Ray app.

Screenshots

Desktop (please complete the following information):

OS: macOS
Version 11.1

Additional context

Stack trace:

BadMethodCallException Method queries does not exist. 
    vendor/spatie/macroable/src/Macroable.php:66 Spatie\Ray\Ray::__call
    routes/web.php:7 require
    vendor/laravel/framework/src/Illuminate/Routing/RouteFileRegistrar.php:35 Illuminate\Routing\RouteFileRegistrar::register
    vendor/laravel/framework/src/Illuminate/Routing/Router.php:424 Illuminate\Routing\Router::loadRoutes
    vendor/laravel/framework/src/Illuminate/Routing/Router.php:381 Illuminate\Routing\Router::group
    vendor/laravel/framework/src/Illuminate/Routing/RouteRegistrar.php:135 Illuminate\Routing\RouteRegistrar::group
    app/Providers/RouteServiceProvider.php:48 App\Providers\RouteServiceProvider::App\Providers\{closure}
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36 Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
    vendor/laravel/framework/src/Illuminate/Container/Util.php:40 Illuminate\Container\Util::unwrapIfClosure
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:81 Illuminate\Container\BoundMethod::callBoundMethod
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:37 Illuminate\Container\BoundMethod::call
    vendor/laravel/framework/src/Illuminate/Container/Container.php:610 Illuminate\Container\Container::call
    vendor/laravel/framework/src/Illuminate/Foundation/Support/Providers/RouteServiceProvider.php:120 Illuminate\Foundation\Support\Providers\RouteServiceProvider::loadRoutes
    vendor/laravel/framework/src/Illuminate/Foundation/Support/Providers/RouteServiceProvider.php:45 Illuminate\Foundation\Support\Providers\RouteServiceProvider::Illuminate\Foundation\Support\Providers\{closure}
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36 Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
    vendor/laravel/framework/src/Illuminate/Container/Util.php:40 Illuminate\Container\Util::unwrapIfClosure
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:81 Illuminate\Container\BoundMethod::callBoundMethod
    vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:37 Illuminate\Container\BoundMethod::call
    vendor/laravel/framework/src/Illuminate/Container/Container.php:610 Illuminate\Container\Container::call
    vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php:113 Illuminate\Support\ServiceProvider::callBootedCallbacks
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:872 Illuminate\Foundation\Application::bootProvider
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:850 Illuminate\Foundation\Application::Illuminate\Foundation\{closure}
    [internal] array_walk
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:851 Illuminate\Foundation\Application::boot
    vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php:17 Illuminate\Foundation\Bootstrap\BootProviders::bootstrap
    vendor/laravel/framework/src/Illuminate/Foundation/Application.php:230 Illuminate\Foundation\Application::bootstrapWith
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:152 Illuminate\Foundation\Http\Kernel::bootstrap
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:136 Illuminate\Foundation\Http\Kernel::sendRequestThroughRouter
    vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:110 Illuminate\Foundation\Http\Kernel::handle
    public/index.php:52 require
    /Users/wdavis/.composer/vendor/laravel/valet/server.php:214 [main]

PHPStorm (2020.3.1) does not recognize the methods either.

Invalidating the PHPStorm caches had no effect on discovering the methods.

Parse Error in Ray.php line 15

Installed ray v1.1.1 and laravel-ray v1.1.0

The app is open and I have placed a simple call, ray('hello world'), in one of my controllers. It fails and the following is dumped in my log file.

[2021-01-08 08:15:07] local.ERROR: syntax error, unexpected 'bool' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) {"userId":21094,"exception":"[object] (ParseError(code: 0): syntax error, unexpected 'bool' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) at C:\...\vendor\spatie\laravel-ray\src\Ray.php:15)
[stacktrace]
#0 C:\...\vendor\composer\ClassLoader.php(322): Composer\Autoload\includeFile('C:\\...')
#1 [internal function]: Composer\Autoload\ClassLoader->loadClass('Spatie\\LaravelR...')
#2 [internal function]: spl_autoload_call('Spatie\\LaravelR...')
#3 C:\...\vendor\spatie
ay\src\helpers.php(15): class_exists('Spatie\\LaravelR...')
#4 C:\...\app\Http\Controllers\MasterDataController.php(53): ray('hello world')

Windows and PHPstorm compatability?

Sorry to be dense and have to raise an issue...

Instant purchase for me, looks great but after installing with composer require... and saving ray.php to project root what actually gets ray running? Nothing obvious to get a process started. Have put a simple ray('Hello') but nothing happens.

Windows 10, PHPstorm, Laragon

Package "spatie/laravel-ray" is not installed

I have installed spatie/laravel-ray but when I called ray('test") it keeps saying "Package "spatie/laravel-ray" is not installed".

Ray doesn't work in Lumen

Describe the bug
Ray doesn't work in Lumen the calls do not appear in the desktop app.

Versions
1.2.2.0

spatie/ray package version: 1.5.5
spatie/laravel-ray package version (if applicable): 1.3.4

PHP version: 8.0
Lumen version: 8

To Reproduce

Create a new lumen project
Register Ray service provide in app.php:
$app->register(\Spatie\LaravelRay\RayServiceProvider::class);
Add a ray log in web.php

$router->get('/', function () use ($router) {
    ray('My first ray call');

    return $router->app->version();
});

Expected behavior
A message in the ray desktop app.

OS: Windows with Docker
I've also published ray.php in the root of the project (using rays publish command).
And changed the host to: host.docker.internal

Clicking on the filename under a debug message isn't sending me to the file in Sublime

Thanks for the great app guys. Just reporting this bug, hope it's helpful feedback.

Describe the bug
In my ray preferences, I have specified that my IDE is Sublime.
When I am clicking the filename under a debug message within my trial version of Ray, I am expecting to be taken back to Sublime and be taken to the line of code where I added the debug message.

Versions
Ray version (you can see this in "About Ray"): 1.2.2 (Trial)

To Reproduce
Steps to reproduce the behavior:

Open ray
Set my IDE in ray to 'Sublime'
Open sublime text
Add a ray() debug message to my code
See the error within Ray
Click on the filename

Expected behavior
I'm expecting to sent back to sublime, at the right file and line number.

Screenshots

Desktop (please complete the following information):

OS: [e.g. macOS] macOS
Version [e.g. 22] 10.15.7

Additional context
Sublime Text Version 3.2.2 Build 3211

Not launching Sublimetext

Hey @freekmurze thank you for this tool. It was an instant buy.

I'm on Mac (latest) and using the latest version of the app.

I selected my editor as Sublime but nothing seems to happen when i click a line number.

Is this the intended functionality ?

Or do i have to install something else to get this working ?

Allow `model` to accept a `collection` of models

Also add a models method.

I'd accept a PR with tests for this.

If none such a PR comes in, I'll implement this myself soon.

Laravel Vapor Issues

Hello and thank you for an awesome product.

It is mentioned here that it is preferred to add Laravel Ray as a normal dependency rather than a --dev one: https://spatie.be/docs/ray/v1/getting-started/installation-in-laravel

This makes total sense, but this won't my experience is that some things fail there and ray actually does start.
https://sentry.io/share/issue/181f7a8d1e28440b85956d6a7bc76ea2/

Does not open Links to Files in Sublime

When clicking in Ray on a Link to a File and Line, the File is not Opened in Sublime Text.
In Rays Settings, "Editor" is set to "Sublime"

Versions
Ray version:1.0.5
Sublime: 3.2.2, 3211
Mac Os: 10.15.7

After your latest log of your trail, you can't re-watch your 10 results

Describe the bug
As mentioned in the application you'll get 10 free logs. The issue is that you can't re-watch your logs that you made because of the popup model that asks to activate your license.

Versions
Ray version 1.2.3.0:

Composer: spatie/laravel-ray 1.3.5 Easily debug Laravel apps

PHP version: PHP 8.0.1 (cli)
Laravel version: v8.21.0

Steps to reproduce the behavior:

start a trail
Execute 9 ray logs
The 10th log is a JSON
See error

Expected behavior
A smaller popup alert in the top corners that warns you that you need to activate your license or otherwise you can't use ray in the further progress of your project.

Screenshots

Desktop (please complete the following information):

OS: Windows 10 Home 64-bit
Version: Build 19041

local_path option is not recognized with WSL2 & Laravel Sail

Describe the bug
The local_path option is not recognized on WSL 2 using Laravel Sail. The path returned is from the Docker container, not my local path.

I asked the question in the discussion, but decided to move it here to report it as an issue.

Versions
Ray version: 1.3.4
PHP version: 8.0.0
Laravel version: 8.21.0

Expected behavior
A click on the Goto Line in the desktop ray app should show the line in my editor

Desktop (please complete the following information):

OS: Windows 10 with WSL 2

Additional context
Although the guy who reported this first had questionable manners, he seems to have a valid point. It's not a breaking bug though, I'm still happy with ray.

Queries with long single-values are cut off

Describe the bug
I have a query that inserts into a logging table that has 3 json columns. When using showQueries(), the query is cut off and I'm unable to horizontally scroll to see it all.

Versions
Ray version (you can see this in "About Ray"): 1.2.3

You can use composer show to get the version numbers of:

spatie/ray package version: 1.5.0
spatie/laravel-ray package version (if applicable): 1.3.4

PHP version: 7.4.14
Laravel version: 8.21.0

To Reproduce
Steps to reproduce the behavior:

Enable showQueries()
Insert into a model that has a json field, and use a large array for the value

Expected behavior
I'd like to be able to see the entire query, either by scrolling left or - more preferably - by wrapping the value.

Screenshots

Desktop (please complete the following information):

OS: macOS
Version: Big Sur 11.1 (20C69)

Additional context
N/A

Windows: Subsequent launching of Ray not working if 'On system tray' is chosen

Ray works fine as long as I don't set in preferences Show App -> On system tray.
By setting this it'll work for the current launch but whenever I tried to open the program again it didn't work.

Had to completely remove all files related to Ray manually because Reinstalling didn't help either (From \AppData\Local\ray-updater and \AppData\Roaming\Ray) and installing fresh again, but letting you know! I'll just use it with the app in task bar, no big deal.

Note: I'm using Windows 10 Home - 64 bits, in case it helps

Queries with values that contain question marks are incorrectly logged

Describe the bug
When using showQueries(), if a query has a value that contains a question mark ?, the query is incorrectly logged because the question mark is replaced with the next bound value. This query is a great example: (I trimmed the actual values, so the JSON isn't valid...)

update
  `sba_api_request_logs`
set
  `was_successful` = "true",
  `response_code` = "200",
  `response_reason_phrase` = "OK",
  `response_headers` = "{"Content-Type":["application\/json"],...}",
  `response_data` = "{"count":1057,"next":"https:\/\/sandbox.forgiveness.sba.gov\/api\/naics\/"false"page=2","previous":null,"results":[...]}",
  `was_server_error` = "false",
  `was_client_error` = "2021-01-12 22:22:31",
  `sba_api_request_logs`.`updated_at` = "46"
where
  `id` = ?

The bound values are correct until the response_data value. There is a URL in that value that includes the string ?page=2. The ? is being replaced by the next bound value in the query - "false" - which should be bound to was_server_error. This causes each subsequent bound value to be shifted up, and the last bound value - id - remains ?. There aren't any more bound values at that point, but it should be "46", which was shifted up and bound instead to updated_at.

Let me know if that made any sense 😂 The first image below hopefully makes it more clear what I'm trying to say.

Versions
Ray version (you can see this in "About Ray"): 1.2.3

You can use composer show to get the version numbers of:

spatie/ray package version: 1.5.0
spatie/laravel-ray package version (if applicable): 1.3.4

PHP version: 7.4.14
Laravel version: 8.21.0

To Reproduce
Steps to reproduce the behavior:

Enable showQueries()
Execute a query with a value that contains a question mark ?

Expected behavior
Question marks ? within field values should not be replaced with bound values

Screenshots
This shows the bound values and the field they should be bound to:

This is a different query that shows what is happening:

Desktop (please complete the following information):

OS: macOS
Version: Big Sur 11.1 (20C69)

Additional context
N/A

spatie / laravel-ray Goto Github PK

laravel-ray's Introduction

Debug with Ray to fix problems faster

Documentation

Testing

Changelog

Contributing

Security Vulnerabilities

Credits

License

laravel-ray's People

Stargazers

Watchers

Forkers

laravel-ray's Issues

Recommend Projects

Recommend Topics

Recommend Org