Add Laravel 8.x support

Currently getting errors when upgrading to Laravel 8.x
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

    - Can only install one of: laravel/framework[8.x-dev, v7.25.0].
    - don't install illuminate/support 5.5.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.6.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.7.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.7.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.7.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.8.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 6.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.40|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.41|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.43|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.5.44|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.38|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.6.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.7.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.8.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.13.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.15.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.38|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.18.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.4.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v6.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.0.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.1.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.1.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.1.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.10.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.10.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.10.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.14.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.16.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.17.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.19.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.19.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.2.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.2.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.20.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.21.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.22.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.22.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.22.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.22.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.22.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.23.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.23.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.23.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.24.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.25.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.26.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.26.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.27.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.28.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.4.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.8.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.9.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.9.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v7.9.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.5.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.40|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.41|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.43|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.5.44|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.6.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.38|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.6.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.7.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.7.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.7.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.7.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.8.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.8.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 6.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.13.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.15.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.10|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.11|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.12|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.14|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.15|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.18|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.29|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.33|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.34|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.35|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.38|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.39|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.18.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.4.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v6.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 7.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.5|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.0.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.1.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.1.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.1.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.1.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.10.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.10.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.10.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.10.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.11.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.12.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.13.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.14.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.14.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.15.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.16.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.16.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.17.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.17.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.17.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.18.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.19.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.19.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.2.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.2.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.20.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.21.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.22.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.22.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.22.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.22.3|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.22.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.23.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.23.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.23.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.24.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.25.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.26.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.26.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.27.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.28.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.4.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.5.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.5.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.5.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.6.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.6.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.6.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.7.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.7.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.8.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.8.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.9.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.9.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v7.9.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.1.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.2.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.3.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support 5.4.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.41|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.1.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.43|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.45|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.2.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.3.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.3.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.3.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/support v5.4.9|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.1.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.2.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.3.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem 5.4.x-dev|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.1|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.2|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.20|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.22|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.30|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.41|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.1.8|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.21|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.24|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.25|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.26|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.28|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.31|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.32|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.37|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.43|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.45|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.6|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.2.7|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.3.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.3.16|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.3.23|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.3.4|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.0|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.13|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.17|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.19|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.27|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.36|don't install laravel/framework 8.x-dev
    - don't install illuminate/filesystem v5.4.9|don't install laravel/framework 8.x-dev
    - Installation request for laravel/framework ^8.0 -> satisfiable by laravel/framework[8.x-dev, v8.0.0].
    - Installation request for superbalist/laravel-google-cloud-storage ^2.2 -> satisfiable by superbalist/laravel-google-cloud-storage[2.2.0, 2.2.1, 2.2.2, 2.2.3].

Can we please get support for Laravel 8.x?

PR raised to resolve this.


There are no releases to install from.

ReadME.me suggests to go to GH releases page in order to install the paclet. Yet the list is empty.

@arnoudbuzing It does otoh I am confused because this paclet already is included in Mathematica v12+
 PacletFind["MongoLink"][[1]]["Location"]

"C:\Program Files\Wolfram Research\Mathematica\12.1\SystemFiles\Links\MongoLink"

If that is expected then information about which Mathematica version contains which MongoLink version could be included in the ReadMe.


AudioStreamPlayer keyframe is silent if the AudioClip starts at an negative time position

Godot version
v4.2.rc1.mono.official [ad72de508]
System information
Godot v4.2.rc1.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated GeForce GTX 1070 () - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)
Issue description
4.1 Behaviour: If an AudioClip is positioned at an negative number inside the animation player. The Audio plays Exact at the 0 position.

4.2 Behaviour: The clip is silence if played. Also if played by the play button of the animation player
This bug is not critical because it can be worarround by cutting the animation clip inside the player so it does not need to be positioned at an negative number. But on large projects it requirest many refactors.
Steps to reproduce
Create an Scene with an AnimationPlayer Node and an AudioStreamPlayer Node.
Create a new Animation.
Drag and Drop an Audio File inside the animation player and place its start below zero.
In my Case the Audio file was mp3
Minimal reproduction project
NA, Because i did not know how to upload it. But it is easy to reproduce

To be precise, since 4.2, if the current position is in the middle of an audio track key, there is no longer the ability to playback the key currently on it during playback. Probably this was the case with AnimationTree prior to 4.2.
BTW, The behavior of AudioTrack and AnimationPlaybackTrack is very similar; They are basically based on the "firing playback at the beginning of the key" feature.
Since before 4.2, AnimationPlaybackTrack does not handle playback from the middle of a playback but the playback-in-progress functionality was hard-coded into AnimationPlayer only for audio, but now AudioTrack has followed AnimationPlaybackTrack and this problem has occurred.
In order to handle playback from the middle of the tracks correctly, the algorithm for retrieving those keys will need to be reworked, which will take a bit of time.
What could be implemented immediately would be a trimming shortcut "[": set start offset / "]": set end offset to set the offset immediately. This would provide a workaround to allow the user to easily set the offset by selecting a key with a negative position and trimming it with the current position set to 0.

Well this was very annoying. Happened to be working on a project that relied heavily on being able to play certain sections of AudioTracks at certain keyframes, and now it seems like I will be unable to continue my project because I have made progress in the 4.2 version and the 4.2 project is not backwards compatible with the 4.1.3 version.
And it apparently hasn't been fixed within weeks of the stable being released.

For those like me who are impatient and require a workaround, editor tool script is here to save the day!
Below is a quick and dirty work around which utilizes the power of @tool and another scene to get an AudioStreamPlayer to run at the position of where your keyframes are in an animationplayer! All you must do is simply choose your animation player node and your audio stream player node, set enabled to true, attach the script to a scene or a node and voila.
Until this gets fixed, this is good enough for me, this is my Hopeful Tool, because I was hopeful that it would work and it did.
@tool
extends Node

@export var animationplayer : NodePath
@export var audiostreamer : NodePath
@export var enabled = true

var animationplayernode
var audiostreamernode

var check = false # this is unneccesary but for some reason i feel like its not good to have AudioStreamPlayer.stop()
# run every single frame

func _notification(what):
	match what:
		NOTIFICATION_EDITOR_POST_SAVE:
			if get_node_or_null(animationplayer) != null:
				if get_node_or_null(audiostreamer) != null:
					animationplayernode = get_node(animationplayer)
					audiostreamernode = get_node(audiostreamer)
					# Just to make sure that im not overconnecting it
					for i in animationplayernode.get_signal_connection_list("animation_started"):
						animationplayernode.disconnect("animation_started",i.callable)
						print("Hopeful Tool Signal Info: " + str(i))
					animationplayernode.connect("animation_started",

					func started(animation):
						if enabled:
							check = true
							audiostreamernode.play()
							audiostreamernode.seek(animationplayernode.get_current_animation_position())
							print("Hopeful Tool: Starting Audio Test Track"))

					print("Hopeful Tool has been updated.")

func _process(delta):
	if enabled:
		if animationplayernode != null:
			if !animationplayernode.is_playing():
				if check:
					audiostreamernode.stop()
					print("Hopeful Tool: Audio test track has been stopped.")
					check = false
			pass

Perhaps in 4.2.1 playback from the middle is temporarily allowed, but that is causing problems and I am not sure what will become of it in 4.2.2.
In conclusion, playback from the middle should be allowed, but negative time keys should not be obtained. I think #86661 should provide the fine workaround possible at this time for this problem.


UMA RPT introspection should be allowed for a PAT without verifying further permissions

In WSO2 Identity Server the introspection endpoint is default protected with '/permission/admin/manage/identity/applicationmgt/view' permission.
Thus, the introspection request can be initiated only with an access token issued for a user with above permission level.
This complicates the UMA story as the PAT issued for the resource owner is used to access the introspection endpoint to introspect the RPT.
Thus, the resource owner needs to have the above permission level, in order to successfully use PAT to introspect RPT.
But, that should not be the case, ideally if the bearer token coming to introspect endpoint is a PAT (A token issued for the resource owner for uma_protection scope) introspection of the RPT should be allowed.
Moreover RPT should have been issued for a resource of the resource owner for whom the PAT is issued

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Refactor utils/http.go

Fixes: #11899
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

done @LK4D4

LGTM

LGTM


Check if .env file exists / provide feedback if login fails

Is your feature request related to a problem? Please describe.

SaltyBot does not currently check to see if .env file is in the project directory. If the .env file is not provided, the program will continue with the email and password environment variables set as 'None'. The program will fail to login, but does not communicate this to the end user.
Currently, the only hint to the user that the program isn't functioning is the following alert: Either winstreaks or tier didn't retrieve from Twitch.  This match wasn't recorded which comes from the record_match function in SaltyDatabase.py.
Adding a check for the .env file would be beneficial as it is necessary for the program to save matches and would it clearer to the end user why the program might be failing to retrieve info from Twitch.

Describe the solution you'd like
Use conditional statement that checks if dotenv's find_dotenv function returns True to verify .env file exists in project directory.
Other Considerations
Given that the functionality of the program to save matches is critical for it to make any bets, and the lack of an .env file renders it unable to do this, we may want it throw an exception / stop the program if .env file is not detected. In my PR I will add below, the program doesn't stop or throw an exception if the .env file is not found, rather it will just print to the console that it was not detected and to read README for instructions.

Closed with pull.  Thanks for the work!  (PS:  let me know if the JSON error is still happening for you)


ci: run on all tags

Run on all tags, check files only for PRs.
Should resolve #12753.

This looks like guessing to me.
We don't want this to be run on pull_request. I do understand that I added that line at some point (and removed), but that was a mistake.
So, the intention of the current setup is right:
Build image if either

Docker file or image.yml changed
A v* tag is created.

What's missing is 2. I could probably force a build by changing the image.yml file, but I doubt it would pick up the tag...
To conclude., we need someone who knows.

And a double note: This isn't me pointing fingers at anyone; I have spent too may hours in the mysteries of GitHub actions to blame anyone of not understanding it to the point ...

Maybe this?
on:
  push:
    paths:
      - Dockerfile
      - .github/workflows/image.yml

I have spent too may hours in the mysteries of GitHub actions to blame anyone of not understanding it to the point ...

I FEEL THIS IN MY BONES.

@bep so for 1, you want to build it on every push that changes the files, even to master?

@bep so for 1, you want to build it on every push that changes the files, even to master?

I don't mind doing that. My take on this is:

I don't want to build this on every PR because that will be a waste of bot time and storage
These 2 files changes very infrequently, so I would not mind building then to verify that it "still works"
But the most important part is release tags on the master branch.

I will do a little investigation on my own on this. I'm doing a patch release later today.

I agree with that take.
With the current changes, it should build:

on every tag
For every PR that changes the two files

That is as you described it in https://github.com/gohugoio/hugo/pull/12754#issuecomment-2284920836.
The on.pull_request is restricted by the on.pull_request.paths to only run on PRs that change these paths.
The issue now might be - and I don't have any experience with that so far - that this PR here is coming from my fork, which does not have push access to the registry for the gohugoio organization, and rightly so.
I think that might make it impossible to use the matrix workflow (I adapted it from https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners) to speed up builds.
Maybe a better way is to instead:

not use matrix builds
use the docker/build-push-action and set push to true only for tags

With that, the build itself would be tested, but the image only pushed for tags.
Sorry that this change is causing so many difficulties right now, this is not what I intended.

The issue now might be - and I don't have any experience with that so far - that this PR here is coming from my fork, which does not have push access to the registry for the gohugoio organization, and rightly so.

The GITHUB_TOKEN with write access is not available to forks, which is a good thing! I tested this in a PR in a branch in the Hugo repo, and that works.
We will never get a setup that tests this in PRs, and that is fine; as long as we get it to work on the master branch, I'm fine.
Let's move this discussion to https://github.com/gohugoio/hugo/pull/12758


[test_rom] enable address translation

This commit:

enables address translation in the test ROM,
align test ROM manifest symbols with ROM's, and
makes the virtual slot the default OTTF slot used.

This partially addresses #10712.
Signed-off-by: Timothy Trippel<EMAIL_ADDRESS>

This addresses a comment on a previous PR  (#14521).


[INTEGRATION][AIRFLOW] Introduce a new extractor for SFTPOperator

Signed-off-by: Kengo Seki<EMAIL_ADDRESS>
Problem
Currently, OL doesn't have an extractor for tracing file transfer between local file systems.
Solution
This PR introduces a new extractor for SFTPOperator for the purpose described above.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[x] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[x] You've updated any relevant documentation (if relevant)
[ ] You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

Thank you for reviewing and addressing the mypy issue, @JDarDagran! I left some replies.
The latest CI failures are caused by timeout and the Spark IT, so it seems to be irrelevant to this PR.

Thank you for the response @JDarDagran, just updated the PR. Let's see how CI goes.

On secound thought I think we should change convention to use IP instead of host name. Generally speaking we should aim into making dataset namespace + name unique. Use of IP makes it possible in most cases.

Regarding this, I fixed the latest PR as follows, considering a case using dummy hostname (e.g., unit test):

If hostname can be resolved to IP address, use it
If not, still use hostname but leave a warning in log

Oh, I've just noticed I forgot to fix the integration test. It will fail since I didn't change requests/sftp.json at all.
I've also realized that it may be difficult to fix IP addresses for integration test in the CI environment which is built with docker-compose. Anyway I'll try it.

I fixed the IP issue in the latest PR. The following document helped me.
https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address
The most recent CI run failed due to timeout in the previous step in question (it seems to frequently happen), but I ensured the latest PR passed the integration test locally.
$ git show --shortstat
commit 9543ad723a1f644fcc3d7e9aafd27cfd691caa5f (HEAD -> feature/sftp-extractor, origin/feature/sftp-extractor)
Author: Kengo Seki<EMAIL_ADDRESS>Date:   Mon Nov 14 08:51:09 2022 +0900

    Fix IP address of worker and SSH server for integration test

    Signed-off-by: Kengo Seki<EMAIL_ADDRESS>
 2 files changed, 37 insertions(+), 6 deletions(-)
$ AIRFLOW_IMAGE=apache/airflow:2.4.2-python3.7 ./tests/integration/docker/up.sh

...

test_integration.py::test_integration[sftp_dag-requests/sftp.json]
------------------------------------------------------------------------------- live log call -------------------------------------------------------------------------------
2022-11-14 01:19:32 INFO Checking dag sftp_dag
2022-11-14 01:19:32 INFO Waiting for DAG 'sftp_dag'...
2022-11-14 01:19:32 INFO DAG 'sftp_dag' state set to 'success'.
2022-11-14 01:19:37 DEBUG Starting new HTTP connection (1): backend:5000
2022-11-14 01:19:37 DEBUG http://backend:5000 "GET /api/v1/lineage HTTP/1.1" 200 208350
2022-11-14 01:19:37 INFO failed to compare events for dag sftp_dag!
2022-11-14 01:19:37 INFO Events for dag sftp_dag verified!
PASSED                                                                                [ 82%]

...

================================================================= 13 passed, 4 skipped in 89.63s (0:01:29) ==================================================================

@JDarDagran Would you take a look?

@sekikn I've made some improvements in the CI process. Please rebase once again so that tests should run successfully.
The one thing that I made notice previously and it actually just happens. As a result of a broader discussion - {host}:{port} should be the only choice without having port optional. In case of local files we do not know remote port let's default to paramiko.config.SSH_PORT value. Besides it looks good! Thank you!

Thanks a lot for addressing the CI issue, @JDarDagran! I'll update the PR in accordance with your comment.
There's one more thing I've just noticed, the current implementation doesn't pass the integration test on CI because of the dependency version. Airflow's dependencies are installed using the constraint file, and it installs apache-airflow-providers-sftp 2.1.1 for Airflow 2.1.4, sftp 2.4.1 for Airflow 2.2.4, and sftp 4.0.0 for Airflow 2.3.4 respectively, while this extractor requires sftp 4.1.0+. We can add a new test condition for addressing this, but I'd rather loosen the version requirement by accepting both str and list as local_filepath and remote_filepath so that wider range of users can leverage this extractor.

Let's loosen the requierements.

Oh, sorry for my misunderstanding. Now I got what you meant, thank you for the elaboration!


[Investigation] Reducing allocations in HttpClient

We believe there are some gains to be found in reducing allocations in HttpClient, particularly for proxy scenarios where it may be reasonable to bypass header validation and other HttpClient features designed for more general-purpose use cases.

@stephentoub I created this to track the work you're looking at. Feel free to edit/adjust as desired to appropriately match what you're looking at!

Duplicate of https://github.com/dotnet/runtime/issues/35126


Make tile entity replacement configurable

Made it possible to disable the WorldEventTick that replaces tiles
entites with upgraded versions to make Et Futurum play nice with
Mystcraft.

Found that you already made a build, awesome :)

I'd be interested in the build. The problem is, @ganymedes01 has been inactive for almost a year.

Just check the "Releases" section in the OP's fork, it has -spec appended to the end.
On Mar 29, 2017, EzerArch<EMAIL_ADDRESS>wrote:

Found that you already made a build, awesome :)

I'd be interested in the build. The problem is, @ganymedes01 has been
inactive for almost a year.

--
Sent with K-@ Mail - the evolution of emailing.

Found it. Thanks. :)

Just found our server was using a huge amount of CPU and ~85% of it was from this tick method.

@cosmicdan sorry for necro this old pull request, but i had the doubt: the issue fixed on this Pull Request should not affect anyone that is not using Mystcraft or should i use it? (the release on wmrojer's fork)

Just found our server was using a huge amount of CPU and ~85% of it was from this tick method.

@cosmicdan sorry for necro this old pull request, but i had the doubt: the issue fixed on this Pull Request should not affect anyone that is not using Mystcraft or should i use it? (the release on wmrojer's fork)

Whew it's been a while haha but I think Mystcraft was one specific combination where this caused an issue, because Mystcraft dimensions do something with TE's and it causes a bad interaction with Et Futurism.
Basically I found high CPU usage with both the mods, I used Java profiler and found this to be the cause; its not so much a fix but a work around.

oh ok, many thanks for the aclaration, it's just that i wanted to try the old 1.7 experience (which sadly i never tried before with a well-played survival game, i jumped directly from 1.6 to 1.10)

oh yeah, i started to use Et Futurum Requiem since i found it (some months after my comment on this issue), thanks anyways


Retraining the inception model to remove objects

Hello I have been trying for a while now to find an answer to this question
is there is anyway to retrain the inception model in a way that I remove objects from it (without doing the training from the scratch) and to be possible to integrate in the android demo

This question is better suited for StackOverflow as it's not a TF bug itself. They also monitor there under TensorFlow tag and it would get a wider exposure.


support copies in find-getter and other things

❗ Problem:
I have a UI-table for data manipulation. I use this table somehow like the FeathersVuexFormWrapper but for multiple items at once. I implemented a cancel/save mechanism for the whole table and all displayed items.
So I create clones for existing items and show the clones in the table for manipulation. When I add a temp record I also concat them to the table. I implemented it by querying the original and temp records and replace the resulting items with existing clones afterwards
✔ Solution:
An additional copies property in params for getters would make this shorter. I think this could become useful for someone else so here is the change for this with tests and docs. Just pass { query: {}, copies: true } to activate this behaviour. By this the original and temp items get queried normally and then get replaced with the according clones. ✔
Other things:
While programming this I came accross some other issues:

values = values.concat(_.values()) in the find-getter is slow. values.push(..._.values() is much more performant. See https://dev.to/uilicious/javascript-array-push-is-945x-faster-than-array-concat-1oki. This optimization is only relevant for temps: true but since the find getter is used anywhere small performance changes can make a difference ✔
The clearCopy mutation was not working with Model.copiesById. ✔
The createCopy mutation was not working properly for state.copiesById when cloning an item twice. ✔
I added mutation-tests for the copy mutations for Model.copiesById / keepCopiesById: false . But there was a problem with the getter / setter which got undefined with mergeWithAccessor. I could not solve this problem. 😕
I wrote tests for it.skip('instance.remove removes cloned records from the store', function () {}) and it.skip('instance.remove removes cloned records from the Model.copiesById', function () {}) but kept them as it.skip because I don't know whether you want to implement this, or not @marshallswain. See the discussion below: ❓

❓ Discussion:
There are some things I'm not sure how it should be. At the moment copiesById can get poluted because it never releases items (just by clearCopy which never gets called):
a. removeItem / Model.remove should delete the item from copiesById, as it is suggested in the tests? 💯
b. resetCopy / Model.reset should delete the item from copiesById, shouldn't it? 💯
c. ``commitCopy/Model.commitshould also delete the item fromcopiesById, right? I'm not that sure about this one. 😕  d. clearAllmutation should also clearcopiesById`, shouldn't it? 💯
@marshallswain For the last four questions I need your thoughts, please. As always I'm happy to contribute. Just a 'yes' or 'no' would be enough and I will implement them. 👍

Just my 2 cents:
a. Yes
b. Not sure, would it mean that we need to re-clone the item ?
c. Yes
c bis. Yes
I noticed this behavior when I re-implemented the VuexFormWrapper for a specific need and manually added the copy deletion.
About the copies param, in fact, it already exist, it's there
// Set params.temps to true to include the tempsById records
params.temps = params.hasOwnProperty('temps') ? params.temps : false

but it's called temps and is mentioned in the docs here but maybe you already saw it.
What I'm not sure there is why the original items are concatenated with the copies ?
Shouldn't they replace the original ones ?

Thanks for your thoughts 👍
How did you add the custom copy deletion? If you don't mind sharing maybe we can bake that into FeathersVuex to make it even better? I thought of calling the clearCopy mutation in a beforeDestroy / beforeUnmount hook of the renderless data component.
I think you misunderstood the temps param:

temps -> state.tempsById store new records that have not been send to the server and therefore don't have an id
copies or also clones -> state.copiesById / Model.copiesById store records cloned from original records (keyedById or tempsById)

So they basically are two seperate things. Temps for complete new records. Copies for a tempory discard/save mechanism.

Ah yes, definitely, now that you say it I remember that I was confused at first and then understood the difference.
I just forgot it in the meantime... ^^
So yes it totally make sense.
For the copy deletion, I did it manually by deleting the id in copiesById on the item constructor like this
deleteCopy() {
  const { idField, copiesById } = this.item.constructor;
  const id = this.clone[idField];
  Reflect.deleteProperty(copiesById, id);
},

@fratzinger, I'm going to start by answering the last four questions, then I'll go back and review the rest.

a. removeItem / Model.remove should delete the item from copiesById, as it is suggested in the tests? 💯

Yes

b. resetCopy / Model.reset should delete the item from copiesById, shouldn't it? 💯

No  Reset copy should basically do the same thing as re-cloning.  It resets the copy back to match the original record.

c. ``commitCopy/Model.commitshould also delete the item fromcopiesById`, right? I'm not that sure about this one.

No  My most common pattern is to work from a copy and send commits/saves back to the original/API server.  This would break literally every form I've ever written.  :)

d. clearAll mutation should also clear copiesById, shouldn't it? 💯

Yes

@fratzinger this is an excellent idea.  I'm curious to try it out and compare it to my current workflow, which uses a new handleClones utility that wrote a couple of months ago.  I think it's time to bring it into feathers-vuex and share it.
#4 is interesting.  mergeWithAccessors is quite a pain to work with, so I'm not surprised.  Please at least leave a skipped test in place for that.
Overall it sounds great.  Let me know when you'd like it merged and I'll do a release.

Wow, this was more to do than I expected.
What was added to this PR since the last discussion?

clearAll also clears the copiesById
Model.remove also removes the corresponding copy
mutation removeItem also removes the corresponding copy
mutation removeItems also removes the corresponding copies
added tests for these

But wait, why are there unrelated changes in the tests?
Handling the state/Model.copiesById thing in the tests was more difficult than I expected. It said Cannot get 'copiesById' of undefined. After digging and digging deeper I found out it has to do with the 1on1 relation between service-path and service/Model. Since most of the services are called todos in the several tests-files it's not hardly debugable. The tests in model.methods.tests.js called states from make-service-plugin.test.js and so on. So I tried to straighten that out:

custom server-alias per file
custom service-path per file
I recommand doing this from now on, even if it was not a problem before.

It's ready from my perspective. Let me know @marshallswain if anything is missing or incorrect.

@fratzinger would you mind fixing the conflicts.  I'm not sure why it won't let me do it right here in the Github UI.

Oh, also I forgot to say that this pull request is beautiful and I really appreciate how thorough you've been.  The changes to the tests look great.

conflicts resolved.
Bizarrely there were new errors in the debounce events tests, that drive me nuts. I guess the performance.now() provides not the best developing experience.
I don't know how the Uncaught Unavailable: connect ECONNREFUSED <IP_ADDRESS>:3030 can be resolved.
Just one last thing came into my mind regarding the initial intention of this PR: The copies: true param just adds copies from keyedById but no copies from tempsById by now. What do you think @marshallswain? Should I change this to also include copies of temp records? I'm confused about cloning a temp anyway.

@fratzinger. Thank you for this entire thing!  I'll create an issue to support copies from tempsById, too.  This is a valid use case.

@fratzinger here's the issue.  It's low priority for right now, since temps are less commonly used: https://github.com/feathersjs-ecosystem/feathers-vuex/issues/554

perfect. Thanks :)

Released as<EMAIL_ADDRESS> Thank you!


Websocket data connectivity issue with Chrome headless?

Component
Version

Operating system
macOS 10.15.7

Node.js
-

Chrome/Chromium/...
87.0.4280.88

chrome-remote-interface
-

Is Chrome running in a container? YES / NO
Hi Cyrus, Good Day to you!
I'm maintaining 2 digital automation tools (TagUI, and RPA for Python, a Python wrapper of the former). Recently I found that TagUI is not able to receive response back from Chrome websocket connection if it is run in headless mode. But the same code works fine with visible mode. Nothing changed from my side, so I suspect something changed with Chrome.
Did some troubleshooting but not getting any clues (https://github.com/kelaberetiv/TagUI/issues/890) and have not found anything from the internet. Thought to raise an issue here to see if you or your users have run into problems with Chrome headless as well.
The gist is after a websocket message is sent, it can take more than 10 seconds for the headless Chrome process to send back the response. Running the same code with Chrome visible gets instant response.
Best Regards,
Ken

Hi Ken! Is there a way I can easily reproduce what you're saying using chrome-remote-interface or plain WebSocket interaction?
For example running the example from the README in headless mode works as intended.

Thanks Cyrus for your quick reply!
It seems like a situation unique with my implementation for TagUI. What happens is in headless mode, when I provide --user-data-dir= with a relative path it no longer works, when it used to work in the past 2 years. When I tweak the relative path provided into a full path, it works in headless mode. For visible mode, it works whether relative or absolute path is provided.
Something probably has changed with how headless Chrome behaves when the path provided is a relative path. I'll close this issue because I don't think it happens outside of the TagUI implementation. I tried replicating the issue using Python websocket but it can't be replicated. So the fix has to be an updated implementation for TagUI headless Chrome.

Thanks Cyrus! Have fixed it to work for TagUI. I did by changing the user profile directory value to absolute path, and also enclose that string as follows to handle cases where the path name has spaces. Otherwise, it will break Chrome. Fyi in case your users run into this strange issue in future. The updated implementation tested to work on Windows and macOS/Linux.
--user-data-dir="some_variable_that_maps_to_absolute_path_of_user_profile_directory"

So --user-data-dir must be an absolute path, good to know! The fact that the behaviour is different between headless and not it means that this is probably a bug in Chrome though...

Yep, for some reason for my implementation that seems to break Chrome. Took some trial and error to figure that out, because the websocket connection is still working but response only comes back after more than 10 seconds after a send. And the issue happens for both Windows and macOS, so it couldn't have been some mac-specific OS changes.

That's super weird, you should file an issue to Chrome.

That's true... But I can't seem to replicate outside of the way I implement it for the TagUI project (invoke via shell script and use a PHP websocket library to do the communications), so I didn't raise.
When I tried testing it using Python websocket the issue isn't replicable. So, something must have changed but only affecting specific usage scenarios. Btw, Happy 2021 to you Cyrus!

That's true... But I can't seem to replicate outside of the way I implement it for the TagUI project (invoke via shell script and use a PHP websocket library to do the communications), so I didn't raise.
When I tried testing it using Python websocket the issue isn't replicable. So, something must have changed but only affecting specific usage scenarios. Btw, Happy 2021 to you Cyrus!

I see, hopefully people running in the same problem will find this issue.
Happy 2021 to you too! ^_^

I see, hopefully people running in the same problem will find this issue.
Happy 2021 to you too! ^_^

Thanks Cyrus! And thanks for accepting my LinkedIn invite :)

Thanks Cyrus! And thanks for accepting my LinkedIn invite :)


Path3D has editor performance issues when points are added over a long distance

Godot version
v4.2.dev.custom_build [da81ca62a]
System information
Godot v4.2.dev (da81ca62a) - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>99) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)
Issue description
I noticed that when I loaded up one of my game's levels that uses a long Path3D, the editor was slow to respond when I initially selected the Path3D node, and then when I was panning around with the camera, there were intermittent hiccups in the performance and the editor would freeze for a second.
If you create a Path3D with a bunch of points while zoomed right in, the performance is okay, but if you zoom all the way out and start adding points, it takes longer and longer to process as you add each new point. I also found that after I'd added the points, if I panned the camera around I'd get random stutters/freezes like something is being re-calculated as the view changes.
Steps to reproduce
Create a Path3D node
Zoom all the way out and start adding a bunch of points
Notice the editor become less responsive as more points are added (not that many are needed to cause this, maybe 15 or so)
With the Path3D node still selected, pan the camera around continuously and you may notice some stutters (how long it takes to happen for me is a bit inconsistent, but usually after a few seconds it starts happening)
Minimal reproduction project
I don't think a minimal reproduction project is really needed

Can you try with a recent version of 4.2? Your build is about two months old

Can you try with a recent version of 4.2? Your build is about two months old

Sorry, I should have mentioned I've also tried it with a build from master that I built today

Can you reproduce this in 4.1.1? I wonder if this is a regression from https://github.com/godotengine/godot/pull/80329.

Can you reproduce this in 4.1.1? I wonder if this is a regression from #80329.

Yep, still happens in 4.1.1
I've just tried it in 3.3 (which is what I was using before moving to 4.x) and I can keep adding points while fully zoomed out and there's no drop in performance at all

Can you reproduce this in 3.5.2? If not, can you test 4.0 alphas and betas? This would help pinpoint the regression more accurately, as there are a lot of commits to cover before we should start bisecting.

Okay, I've just gone through some of the betas and I've found that it started with Beta 8, everything before that (including 3.5.2) is fine

@sketchyfun Seems working on my computer. Could you provide a minimal reproduction project? I'd like to investigate if it is somehow caused by my curve baking code refactor.

@sketchyfun Seems working on my computer. Could you provide a minimal reproduction project? I'd like to investigate if it is somehow caused by my curve baking code refactor.

I didn't add a minimal project because part of the issue appears when actually adding the points, after several points have been added, it starts to get slower and slower to add new points. If I made a project, it would just be a path with some points already added, there's really nothing else to it. Maybe it's system specific, but I'm not sure why that would be..

I can confirm that happens in the master version, i also bisected between beta 7 and beta 9 and this started to happen after #68860
I did some test and what i found was:

In both master and #68860 the freeze happens when you move the camera with Path3D selected, if you deselect the node, the freeze stops
The freeze also happens if you change for another scene and click to go back for the scene with Path3D, even if Path3D node wasn't selected and to close the engine too
The zoom per-se doesn't seems be the problem, but have points too far from each other is
In #68860 you can easily trigger the freeze even with points close each other, also the console spams the error: "The target vector can't be zero."

I compiled both master and #68860 with scons default options
My specs:
Godot v4.2.dev unknown - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 2048SP (Advanced Micro Devices, Inc.; 31.0.21029.1006) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)
Demonstrating the bug in master: https://www.youtube.com/watch?v=YouQkKOZaWY
Demonstrating the bug in #68860: https://www.youtube.com/watch?v=E48LaOw4_ps

I've done a bit of testing, and it's definitely the fish bones that are slowing it down. The issue is that there's just too many of them being drawn unnecessarily. You only have to be zoomed out slightly and they're barely visible, and yet with two points only 4 units apart, there's 100 fish bones being drawn. I checked how many were drawn when I was fully zoomed out (thus adding points large distances apart) and after I'd added around 45 points, there were almost 300,000 fish bones being drawn.
I think the code needs to be changed so that the amount of fish bones drawn takes the zoom level into account or the on-screen distance between each point, so that there isn't an excessive amount of them drawn. I'll look into this myself, but I can't promise anything.

Further investigate this problem a bit, find something interesting. I reported in previous comment that I cannot reproduce this problem . It turns out that's because I was rotating the camera with the "ball gizmo" at the upper-right corner of the viewport. If I rotate with middle mouse button, then there is the stutter.
So my hypothesis is that the stutter is not related with drawing at all, but with the mouse event handling, which somehow trigger the collision detection code path. Then I checked the code of EditorNode3DGizmo::intersect_ray, which strengthened the suspicion, as this method does a linear search for all line segment one-by-one.

@xiongyaohua This reminds me, someone else recently reported a stutter with mouse camera rotating....

I'm not getting any stutters myself when rotating the camera, but dragging points over large distances is awfully laggy. Adding points over long distances can also cause hitches. Definitely related to how long the spline is in world-space.

Setting the interval value higher here helps to alleviate the issue, but only temporarily. You'll end up hitting a threshold where it starts to chug. The simplest solution is probably to match Blender's functionality. A resolution value that defines a fixed number of intervals between two spline points.
https://github.com/godotengine/godot/blob/e5b4ef8e9522e950033cbece39a31a4a76da19c1/editor/plugins/path_3d_editor_plugin.cpp#L291-L355


Fixed bubbling of click event in sl-menu-item-show-all

Closes softlayer/sl-ember-components#1486

addon/components/sl-menu-item-show-all.js, line 28 [r1] (raw file):
erroneous indention.

Comments from the review on Reviewable.io

@juwara0 is there no testing required for this change set?

Comments from the review on Reviewable.io

https://github.com/softlayer/sl-ember-components/blob/7e6c655b485cdcfbd92014d80654a455a2acd675/tests/integration/components/sl-menu-test.js#L370

Comments from the review on Reviewable.io

Review status: 0 of 2 files reviewed at latest revision, 2 unresolved discussions.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r1] (raw file):
I don't see a reason to prevent the event from bubbling/propagating here. As much as possible, we should not stop the event
from propagating unless absolutely necessary. One concrete reason is that we do not know what events the consuming application, or
end users who are extending our components want to wire up to.
E.g If when tracking all clicks on the page using a global event handler, or there's a third party script tracking clicks, with
code such as this:
	$(document).click(function( e ){
		console.log( 'Element was clicked', e.target );

		//ajax request to log click on page and what element was clicked
	});

In this case the click on the "Show All" link will not propagate and not get captured.
The specific usecase for preventing event propagation is if clicking the element has unwanted side effects, such as the scenario below outlined in the docs:
{{#link-to 'post'}}
  Post
  <button {{action 'close' bubbles=false}}>✗</button>
{{/link-to}}

In this scenario clicking on the button would also navigate to the post route, which is an unintended side effect, hence
using bubbles=false here is necessary.
If we still think we need bubbles=false please share code and scenarios that I may not have accounted for.

Comments from the review on Reviewable.io

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from the review on Reviewable.io

Review status: 1 of 2 files reviewed at latest revision, 2 unresolved discussions.

addon/components/sl-menu-item-show-all.js, line 28 [r1] (raw file):
Done.

Comments from the review on Reviewable.io

Until https://github.com/softlayer/sl-ember-components/issues/1488 is resolved this PR cannot be fully tested, as does this approach also capture selection of the link via enter press?

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r1] (raw file):
I understand what you are saying @azizpunjani but the other menu item's click event are already being suppressed because of {{action}} syntax, as well the only target information this link would provide is #.
If you have another way to resolve this we're open to suggestions.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r2] (raw file):
Use double quotes around "click"

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 3 unresolved discussions.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r1] (raw file):
The way to resolve it is simply do
Show All`

that should prevent the link from navigating to /# when clicked, there's not a need for bubbles=false.

"the other menu item's click event are already being suppressed because of {{action}} syntax"

Yes, whenever you use the {{action}} helper preventDefault=true is implied, hence clicking the link will not navigate to the href on the link. This is exactly what we want, we shouldn't need the additional bubbles=false. If you notice we don't use it on sl-menu-item  links either.
If we are advocating for bubbles=false whenever using links within our components, why are we not putting it on all links we use an action helper on? Why only this one?
Again, a very subtle point I'm trying to get across, event.preventDefault() vs event.stopPropagation(). We need event.preventDefault() in our case which is already true whenever we use the {{action}} helper, that's not my issue. My issue is bubbles=false which is event.stopPropagation(), we don't need that in this particular case.
Please read https://css-tricks.com/dangers-stopping-event-propagation/ for further clarification on the differences and why we should not prevent the event form bubbling i.e event.stopPropagation(), unless absolutely necessary.

Comments from the review on Reviewable.io

I tested this fix against the enter press as well.

Review status: 1 of 2 files reviewed at latest revision, 3 unresolved discussions.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r1] (raw file):
Done.

addon/templates/components/sl-menu-item-show-all.hbs, line 1 [r2] (raw file):
Done.

Comments from the review on Reviewable.io

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from the review on Reviewable.io

Reviewed 1 of 2 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from the review on Reviewable.io


Broadlink switch

--> My broadlink switches have not  worked since 0.67 version.
Now, I am using Hass.io 068.

Component/platform:

Description of problem:
I don't receive error massage but I dont have switches entitys enabled.

I too have the same problem:

platform: broadlink
name: TV Sala Comando
host: <IP_ADDRESS>
mac: 'xx:xxx:xx:xx'
ircodes_ini: 'packages/broadlink_media_codes/samsung.ini'
ping_host: <IP_ADDRESS>

Unlike oescafandrista I have an error:
2018-04-29 21:52:43 ERROR (SyncWorker_16) [homeassistant.util.package] Unable to install package broadlink==0.8.0: Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-6n7dlixd/pycryptodome/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-7aknopjn-record/install-record.txt --single-version-externally-managed --prefix  --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-6n7dlixd/pycryptodome/
2018-04-29 21:52:43 ERROR (MainThread) [homeassistant.requirements] Not initializing media_player.broadlink because could not install requirement broadlink==0.8.0
2018-04-29 21:52:43 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform media_player.broadlink: Could not install all requirements.
2018-04-29 21:55:55 ERROR (SyncWorker_6) [homeassistant.util.package] Unable to install package broadlink==0.8.0: Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-build-cr626u5l/pycryptodome/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-sqgbetmt-record/install-record.txt --single-version-externally-managed --prefix  --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-cr626u5l/pycryptodome/
2018-04-29 21:55:55 ERROR (MainThread) [homeassistant.requirements] Not initializing media_player.broadlink because could not install requirement broadlink==0.8.0
2018-04-29 21:55:55 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform media_player.broadlink: Could not install all requirements.

I'm closing this as the OP hasn't filled in the issue template so there's too little info to move forward.
@oescafandrista please open a new issue with the issue template properly filled out.
@JPM-git please open a separate issue for your error with issue template filled in.


Hera 4.0.0

Adds:

[ ] #88 - workflow of workflows and patching support
[ ] #177 - fan out over multiple task implementations through InputFrom
[ ] #218 - pod patch spec via parameterization

Breaking changes:

[x] #201 - expose namespace configuration on workflow services only rather than workflows
[ ] #202 215 - support for arbitrary script submissions via source rather than func
[ ] #205 - make Resource more aligned with the usage and specifications in Kubernetes
[ ] #220 - dynamic allocation and exposure of task and workflow output fields

Discussion topic:

[ ] #204 - should we rename some objects so that they are more in line with Argo specifications and allow control over dynamic field reference via {{...}} syntax? CC: @trollgeir

Closing in favor of #253 @Trollgeir


Update examples with latest changes to extensions

See: https://github.com/cloudevents/sdk-javascript/pull/246#pullrequestreview-448367574

closed via #282