Laravel 7 Support

Thank you!

Problem installing this package on the Laravel 7
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for dirape/token ^2.2 -> satisfiable by dirape/token[V2.2].
- Conclusion: remove laravel/framework v7.4.0
- Conclusion: don't install laravel/framework v7.4.0
- dirape/token V2.2 requires illuminate/support 6.* || ~5.0 || ~4.0 -> satisfiable by
illuminate/support[4.0.x-dev, 4.1.x-dev, 4.2.x-dev, 5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x
-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, 6.x-d
ev, v4.0.0, v4.0.0-BETA2, v4.0.0-BETA3, v4.0.0-BETA4, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.
0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9, v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4
.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.
1.22, v4.1.23, v4.1.24, v4.1.25, v4.1.26, v4.1.27, v4.1.28, v4.1.29, v4.1.3, v4.1.30, v4.1
.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.0-BETA1, v4.2.1, v4.2.12, v4.2.16, v4.2.1
7, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9, v5.0.0, v5.0.22, v5.0.2
5, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22,
v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.
2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.
2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27,
v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5
.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6
.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.
21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.3
0, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4
, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.
2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5,
v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.
18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30
, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6
.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0
, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.2, v6.18.3, v6.2.0,
v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0].
- don't install illuminate/support 5.5.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.33|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.34|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.35|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.36|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.37|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.39|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.40|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.41|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.43|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.5.44|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.6.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.10|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.11|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.12|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.13|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.14|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.15|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.19|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.20|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.21|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.23|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.24|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.25|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.26|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.29|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.30|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.31|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.32|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.33|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.34|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.35|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.36|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.37|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.38|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.39|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.5|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.6.9|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.7.17|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.7.18|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.7.19|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.7.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.10|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.11|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.15|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.20|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.21|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.23|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.26|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.5|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.7.9|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.8.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.11|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.12|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.14|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.15|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.18|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.19|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.20|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.24|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.29|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.30|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.31|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.32|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.33|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.34|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.35|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.36|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.8.9|don't install laravel/framework v7.4.0
- don't install illuminate/support 6.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.0.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.0.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.0.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.0.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.0.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.1.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.10.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.11.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.12.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.13.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.13.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.14.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.15.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.15.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.16.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.17.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.17.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.18.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.18.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.18.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.18.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.2.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.3.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.4.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.5.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.5.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.5.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.6.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.6.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.6.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.7.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v6.8.0|don't install laravel/framework v7.4.0
- don't install illuminate/support 4.0.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 4.1.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 4.2.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.0.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.1.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.2.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.3.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support 5.4.x-dev|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.0-BETA2|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.0-BETA3|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.0-BETA4|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.10|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.5|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.0.9|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.10|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.11|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.12|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.13|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.14|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.15|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.18|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.19|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.20|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.21|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.23|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.24|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.25|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.26|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.29|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.30|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.5|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.1.9|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.0-BETA1|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.12|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.3|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.5|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v4.2.9|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.25|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.26|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.0.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.1|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.13|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.2|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.22|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.25|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.31|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.41|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.1.8|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.19|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.21|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.24|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.25|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.26|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.28|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.31|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.32|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.37|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.43|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.45|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.6|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.2.7|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.3.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.3.16|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.3.23|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.3.4|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.0|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.13|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.17|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.19|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.27|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.36|don't install laravel/framework v7.4.0
- don't install illuminate/support v5.4.9|don't install laravel/framework v7.4.0
- Installation request for laravel/framework (locked at v7.4.0, required as ^7.0) -> satisfiable by laravel/framework[v7.4.0].

Same issue

Thank you all , i have published new release 2.3 which support Laravel 7


New term request: prophylactic hormone treatment

Editor preferred term: prophylactic hormone treatment
Alternative term: adjuvant hormone treatment
Textual definition: A prophylactic treatment that has as occurrent part some administering of a drug product that either (1) contains some hormone as active ingredient, (2) negatively regulates the production of some hormone, or (3) negatively regulates some action of some hormone.
Definition source: https://www.cancer.gov/about-cancer/treatment/types/hormone-therapy#THT
Parent class: prophylactic treatment
Term editor: S. Clint Dowland
Contributor: William R. Hogan
Contributor: Matthew Diller
I'm also attaching a spreadsheet that displays the term request in a different format.
NTR - prophylactic hormone treatment.xlsx

Parts 2 & 3 of the definition may be too expansive. Possibly reduce to part 1 only?

A prophylactic treatment that has as occurrent part some administering of a drug product that either (1) contains some hormone as active ingredient, (2) regulates the production of some hormone, or (3) regulates some action of some hormone.
Split the term into 3. Alternative term: adjuvant hormone treatment not synonymous.


Update build.ps1

Update the variables for the pinned-toolchain usage to correctly specify the compilers.  Additionally use the new helpers to work with the new toolchain layout as well.

CC: @hjyamauchi

@swift-ci please test


Including openjdk-11 and its subpackage openjdk-11-jre causes errors

If I use wolfi-base to apk add: openjdk-11 and openjdk-11-jre everything seems to work hunky dory.
When I include both of those packages in a melange file as deps to gradle-8 in wolfi I see:
Apr 22 16:15:19.965 [INFO] [arch:x86_64] installing openjdk-11-jre (<IP_ADDRESS>-r2)
Apr 22 16:15:26.771 [INFO] [arch:x86_64] installing gradle-8 (8.0.2-r2)
Apr 22 16:15:28.658 [INFO] [arch:x86_64] installing openjdk-11 (<IP_ADDRESS>-r2)
2023/04/22 16:15:34 ERROR: failed to build package. the build environment has been preserved:
2023/04/22 16:15:34 melange (gradle-8/x86_64):   workspace dir: /tmp/melange-workspace-1754311826
2023/04/22 16:15:34 melange (gradle-8/x86_64):   guest dir: /tmp/melange-guest-3403006330
Error: failed to build package: unable to build guest: unable to generate image: installing apk packages: unable to install files for pkg openjdk-11: error creating file usr/lib/jvm/openjdk/legal/java.base/ADDITIONAL_LICENSE_INFO: open /tmp/melange-guest-3403006330/usr/lib/jvm/openjdk/legal/java.base/ADDITIONAL_LICENSE_INFO: permission denied
2023/04/22 16:15:34 error during command execution: failed to build package: unable to build guest: unable to generate image: installing apk packages: unable to install files for pkg openjdk-11: error creating file usr/lib/jvm/openjdk/legal/java.base/ADDITIONAL_LICENSE_INFO: open /tmp/melange-guest-3403006330/usr/lib/jvm/openjdk/legal/java.base/ADDITIONAL_LICENSE_INFO: permission denied
make: *** [Makefile:82: packages/x86_64/gradle-8-8.1.1-r0.apk] Error 1

Oh, permission denied! That is a new one! Always up for some unexpected entertainment. 😄
@patflynn can you put in here a minimal melange yaml that can reproduce it?

Here you go!

FYI the error changed after I installed melange from head.

Ah, good, I was able to reproduce it.

I wasn't sure about this myself but apk add doesn't seem to complain about adding both.

That is a fair point. I wonder why that is. Worth digging a little more deeply into the APKINDEX.
How did you do an apk add manually?

They have the same origin, but conflicting files. I am hoping @kaniini can provide some insight.

Packages with the same origin are allowed to override each other's files.

@kaniini and I chatted about this this morning. Sounds like apko should allow overwriting in this case, but ideally I'd also fix-up the packages so that the jdk package is additive to its JRE subpackage rather than overlapping.

Packages with the same origin are allowed to override each other's files.

Ah, ok. We can add that.

jdk package is additive to its JRE subpackage rather than overlapping

I assume you mean in wolfi-dev/os?

yep. seems less urgent once the overwriting is supported.

Actually this really is an apko issue.

Well, this is funny. Looking at apko logic, it actually allows overwriting existing files, without regard to origin. It just says, "ok, I will overwrite this." This needs to be constrained to only allow same origin, and then figure out why this particular case fails.


Weave ECS AMI: Update Weave Net to 2.3.0

Weave ECS AMI ships with Weave Net 2.0.4 which is ~9 months old.

Fixed by #140


don't pick up python2 from PYTHONPATH during selenium install

$ ./bootstrap.sh
...
Installing setuptools, pip, wheel...done.
Traceback (most recent call last):
File "/home/whatever/go/dist/selenium/bin/pip", line 7, in
from pip import main
File "/home/whatever/go/dist/grpc/usr/local/lib/python2.7/site-packages/pip/init.py", line 21, in
from pip._vendor.requests.packages.urllib3.exceptions import DependencyWarning
ImportError: No module named 'pip._vendor.requests'
Turned out to be because PYTHONPATH had go/dist/grpc/usr/local/lib/python2.7/site-packages before go/dist/selenium/lib/python3.5/site-packages (3.5 has the missing module).
Setting PYTHONPATH= for that pip install worked for me.
Slightly worried because Alex Charis made some commits about this in February ( f14c0586fc391c8677 , 3a5949bb9ca1440c3e ), so maybe I'm just undoing that.

@acharis can you take a look?

@acharis ping

@slanning can you add a comment before the line on why we're removing the PYTHONPATH? Essentially what you said on the PR.
This workaround is good enough for now. We could try to change things such that the selenium's PYTHONPATH comes before grpc, but that could very well break other things.

LGTM


[NEW CONTENT TYPE REQUEST] Godot Package

What type of file would you like magika to detect?
Godot Package (.pck)
What software can create/open these files?
Godot,
https://github.com/search?q=godot+pck&type=repositories.
Where can these files be found?
Many Godot games.
If possible, please provide a specification for this file type.
Additional context

Closing, see #152 for context. Thanks!


Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows.

Description

Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
(paste your output here)

Output of docker info:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

Thanks for reporting, this looks to be a duplicate of https://github.com/docker/docker/issues/31863, so let me close the issue here


Please join to us #standwithukraine

Please support Ukraine, more infos here: https://github.com/vshymanskyy/StandWithUkraine

@juergba Pls have a look on it

@id-dan I will have a look, I'm in doubt because of your own behaviour in other repos, see https://github.com/postmanlabs/newman/issues/2951#issue-1192634949.

 [...]
If it is not on the topic, then you are no different from the Nazi-Russian

Respecting other people's opinions without insulting them is one of the most basic rules of a democratic civilization.

@juergba I agree with you
it is very difficult to control emotions when peaceful people and innocent children are killed. Someone treats it lightly, and writes "it is off-topic"

@id-dan I'm against any political message in our package/docs/readme.
I propose to donate some of our OpenCollective funds (USD 10'000) to support The Ukrainian Red Cross, see https://opencollective.com/support-ukraine.
@mochajs/core thoughts?

ok, donation done.

@juergba thank you a lot.


dart-sass deprecation warning: Passing percentage units to the global abs() function is deprecated.

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
While using the latest bootstrap with dart-sass and including bootstrap via scss, the latest dart-sass is warning about a deprecation:
DEPRECATION WARNING: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent

the stacktrace they show is:
node_modules\bootstrap\scss\mixins\_grid.scss 59:12        row-cols()
node_modules\bootstrap\scss\mixins\_grid.scss 85:13        @content
node_modules\bootstrap\scss\mixins\_breakpoints.scss 68:5  media-breakpoint-up()
node_modules\bootstrap\scss\mixins\_grid.scss 72:5         make-grid-columns()
node_modules\bootstrap\scss\_grid.scss 38:3                @import
node_modules\bootstrap\scss\bootstrap.scss 20:9            @import

I hope this helps. Tks for your work.
Reduced test cases
@import '../../node_modules/bootstrap/scss/functions';
@import '../../node_modules/bootstrap/scss/_variables';
@import '../../node_modules/bootstrap/scss/bootstrap';
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
No response
What version of Bootstrap are you using?
5.3.1

mixins_grid.scss
the mixin row-cols need to be :
@mixin row-cols($count) {
  > * {
    flex: 0 0 auto;
    width: divide(100, $count);
  }
}

the divide function need an integer instead of a percentage

@rallets @Dreanad I created a PR https://github.com/twbs/bootstrap/pull/39030

From: https://sass-lang.com/documentation/breaking-changes/
Passing a percentage unit to the global abs() is   deprecated beginning in Dart Sass 1.65.0.
Temporary solution is to stay in v1.64.2

line 59 change to
width: math.div(100%, $count)

I will second this:
LOG from ./node_modules/sass-loader/dist/cjs.js sass-loader ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[2]!./node_modules/resolve-url-loader/index.js??ruleSet[1].rules[1].oneOf[7].use[3]!./node_modules/sass-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[4]!./src/components/Header/Header.scss
<w> Deprecation Passing percentage units to the global abs() function is deprecated.
<w> In the future, this will emit a CSS abs() function to be resolved by the browser.
<w> To preserve current behavior: math.abs(100%)
<w> To emit a CSS abs() now: abs(#{100%})
<w> More info: https://sass-lang.com/d/abs-percent
<w>
<w> src/components/Header/Header.scss 1:1                      divide()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 59:12        row-cols()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 85:13        @content
<w> node_modules/bootstrap/scss/mixins/_breakpoints.scss 68:5  media-breakpoint-up()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 72:5         make-grid-columns()
<w> node_modules/bootstrap/scss/_grid.scss 38:3                @import
<w> src/custom.scss 58:9                                       @import
<w> src/App.scss 2:9                                           @import
<w> src/components/Header/Header.scss 1:9                      root stylesheet
<w>

LOG from ./node_modules/sass-loader/dist/cjs.js sass-loader ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[2]!./node_modules/resolve-url-loader/index.js??ruleSet[1].rules[1].oneOf[7].use[3]!./node_modules/sass-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[7].use[4]!./src/App.scss
<w> Deprecation Passing percentage units to the global abs() function is deprecated.
<w> In the future, this will emit a CSS abs() function to be resolved by the browser.
<w> To preserve current behavior: math.abs(100%)
<w> To emit a CSS abs() now: abs(#{100%})
<w> More info: https://sass-lang.com/d/abs-percent
<w>
<w> src/App.scss 1:1                                           divide()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 59:12        row-cols()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 85:13        @content
<w> node_modules/bootstrap/scss/mixins/_breakpoints.scss 68:5  media-breakpoint-up()
<w> node_modules/bootstrap/scss/mixins/_grid.scss 72:5         make-grid-columns()
<w> node_modules/bootstrap/scss/_grid.scss 38:3                @import
<w> src/custom.scss 58:9                                       @import
<w> src/App.scss 2:9                                           root stylesheet
<w>

Could you have a fix ASAP, please?
Deprecation warning issued by SASS: https://sass-lang.com/d/abs-percent
Motivation and context
I just don't want LOGs and warnings like these when running yarn start.

[8:09:00 PM] Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent
╷
57 │   $dividend: abs($dividend);
│              ^^^^^^^^^^^^^^
╵
node_modules/bootstrap/scss/vendor/_rfs.scss 57:14         divide()
node_modules/bootstrap/scss/mixins/_grid.scss 59:12        row-cols()
node_modules/bootstrap/scss/mixins/_grid.scss 85:13        @content
node_modules/bootstrap/scss/mixins/_breakpoints.scss 68:5  media-breakpoint-up()
node_modules/bootstrap/scss/mixins/_grid.scss 72:5         make-grid-columns()
node_modules/bootstrap/scss/_grid.scss 38:3                @import
node_modules/bootstrap/scss/bootstrap.scss 20:9
NPM: "bootstrap": "^5.3.1",

Seems like problem is not solve fully, please fix this as well.

$dividend: abs($dividend);
NPM: "bootstrap": "^5.3.1",

Seems like problem is not solve fully, please fix this as well.

I have the same problem with bootstrap 5.3.1 in _rfs.scss, I hope it will be fixed fast. Proposed solutions:
math.abs(100%)
or
abs(#{100%})

getting the same warning

Hi there! I have the same warning with bootstrap 4.6.2.
Thank you!

@VictorQueiroz I'm not involved in this project, and I don't want to speak out for the maintainers, but I don't think so.
As this is a minor issue, it just logs a warning for a sass deprecated function, and it's not a breaking change, I think has a very low priority. You can keep an eye on the related issue, and see there is already some work in progress.

As this is a minor issue, it just logs a warning for a sass deprecated function, and it's not a breaking change

I agree with you that it's just a warning but still, it's a warning and the warning says :

In the future, this will emit a CSS abs() function to be resolved by the browser.

Since I'm not a CSS expert I don't know / can't measure the impact it will have on the app I'm maintaining : it could break something... or not 😄
That's why i'm asking to maintainers if a fix on BS 4.x could be planned.

vite HMR is spamming my terminal with this warning
can we get the PR pushed and released please

@jdion84 You can downgrade the sass dependency in your packages.json to remove the warnings:
    "sass": "~1.64.2",

My PR don't fix all warnings. This topic will take time.

what preventing you to resolve this issue.. its not any hard issue.  getting bored by fixing it manually all the time. please solve it.

what preventing you to resolve this issue.. its not any hard issue. getting bored by fixing it manually all the time. please solve it.

@HNazmul-IV, I understand that it can be frustrating when things aren't working as expected. It's worth noting that many of us who contribute to open source projects do so voluntarily in our spare time. We're committed to resolving issues, and your patience and understanding go a long way in fostering a positive and collaborative environment. If you have any suggestions or insights regarding the problem, that might be more helpful than your demanding attitude.

@epicserve By the same token, it's worth noting that a PR with a fix has been open and ready-to-commit for three weeks. (Although from reading above, that PR may not remove all instances of the warning.) The community has chipped in, which makes the approval bottleneck frustrating.

@bdkjones, I acknowledge how frustrating it is, but there is no reason to take a demanding and entitled attitude. To me, saying, "Please solve it," sounds demanding and entitled.

"Deprecation" does not mean that it doesn't work as intended.
"Deprecation" does not mean that it is a security issue.
"Deprecation" is only a warning for the near future that can get annoying to look at in the logs/console but, does no harm.
There is no reason to panic. Patience is a virtue.
They are aware of the issue, and have a PR and, a development process to go through.

its unusable with vite, you literally get spammed non stop when running the dev server. it makes proper debugging impossible. the only fix is to downgrade sass or use something 10x slower than vite.
i might just go all in on tailwind, i been 50/50 hanging on to bootstrap for some projects (probably cause of nostalgia / familiarity) but this type of thing seems to happen all the time. someone deprecates something for no reason and then its weeks before an update.

I am using Vite as well. I know that Vite can get blamed for anything and everything, including Google Chrome not working for fast refresh; not a Vite issue as it was also an issue in CRA, i.e. look at the code, i.e. an ESLint rule to help with that but, I digress. Vite isn't the bogeyman here (you would get the same warning using CRA). It is a SASS warning (i.e. you can downgrade SASS) that Bootstrap is using a deprecated function. I am using SASS (not dart-sass). Vite is a lot faster, currently minimalistic and, having more control of the cleaner configuration is better than CRA (Internet Explorer era). I have only briefly tried Tailwind.  If the warning SPAMS too much, I would spend a little bit of time looking for a way to temporarily suppress the warning, until it is patched by Bootstrap (up to a month or two).
https://stackoverflow.com/questions/68147471/how-to-set-sassoptions-in-vite
To hide the warnings, update your vite.config.js like this:

export default defineConfig({
  css: {
    preprocessorOptions: {
      scss: {
        quietDeps: true
      }
    }
  }
})

Immediate Solution:

Open the bootstrap/vendor/_rfd.scss file.
At the beginning of the file, insert the following line: @use "sass:math";
Locate instances of the abs() function within this file and replace them with math.abs().

From: https://sass-lang.com/documentation/breaking-changes/ Passing a percentage unit to the global abs() is deprecated beginning in Dart Sass 1.65.0. Temporary solution is to stay in v1.64.2

I applied the temp fix mentioned by @featuriz three weeks ago and pinned the sass package version to 1.16.2 by adding "sass": "~1.64.2", to my package.json.  It fixed the problem for my entire team with no manual node_module edits.  We will remove that one line when the new bootstrap version is released.

getting the same warning

rm -rf node_modules
"sass": "~1.64.2"
npm i

I don't even think we should be posting about this warning here. It's not about the framework. It's about the new and slow implementation of Sass in Dart. If you're willing to use bad software, that is ultimately up to you. It definitely has nothing to do with this project. Let's close this.

@VictorQueiroz it's painfully obvious that you don't know how to use your tools

It's very sad to see people complaining about an open source project, where you get everything for free, you have access to the source code, you have documentation, you can participate/contribute with a PR, and so on.
Nope, still someone think you are their slave and work for free and asap. It's a "cultural" problem that I hope it will change soon. It's true the most important skills for a developer are soft skills, and very difficult to find nowadays. 😶
And we are speaking about bootstrap, one of the most used and supported framework in the last 12 years.
I feel the pain of the maintainers. 😔
I understand why many choose to go closed source. Open source will not last long sadly...

To add @musaab-abdalla's fix to git (until a new version is released) use patch-package:

Immediate Solution:

Open the bootstrap/vendor/_rfd.scss file.
At the beginning of the file, insert the following line: @use "sass:math";
Locate instances of the abs() function within this file and replace them with math.abs().

npx patch-package bootstrap

@rallets I agree with you mostly however, "Open source will not last long" is wrong. Linus Torvald still argues for the "Open Source" concept with coding and the sciences (not necessarily politics and other "grey" areas). We use open-source resources to create and enhance private products and services. When code is no longer maintained, if there is no better alternative, being open-source, anyone with the qualified skills can pick up the project and continue it. https://www.youtube.com/watch?v=7XTHdcmjenI

I also encountered this issue. It's just a warning and I didn't notice any actual impact. But I'm still waiting for it to be fixed officially.
Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent

   ╷
57 │   $dividend: abs($dividend);
   │              ^^^^^^^^^^^^^^
   ╵
    D:\blog.runphp.net\node_modules\bootstrap\scss\vendor\_rfs.scss 57:14         divide()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 59:12        row-cols()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 85:13        @content
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_breakpoints.scss 68:5  media-breakpoint-up()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 72:5         make-grid-columns()
    bootstrap\scss\_grid.scss 38:3                                                @import
    _style.scss 47:9                                                              @import
    D:\blog.runphp.net\css\main.scss 2:9                                          root stylesheet
                    ...done in 29.6915673 seconds.

      Regenerating: 1 file(s) changed at 2023-09-05 11:14:29
                    _sass/_style.scss
       Jekyll Feed: Generating feed for posts

runphp
I also encountered this issue. It's just a warning and I didn't notice any actual impact. But I'm still waiting for it to be fixed officially.
Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent

   ╷
57 │   $dividend: abs($dividend);
   │              ^^^^^^^^^^^^^^
   ╵
    D:\blog.runphp.net\node_modules\bootstrap\scss\vendor\_rfs.scss 57:14         divide()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 59:12        row-cols()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 85:13        @content
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_breakpoints.scss 68:5  media-breakpoint-up()
    D:\blog.runphp.net\node_modules\bootstrap\scss\mixins\_grid.scss 72:5         make-grid-columns()
    bootstrap\scss\_grid.scss 38:3                                                @import
    _style.scss 47:9                                                              @import
    D:\blog.runphp.net\css\main.scss 2:9                                          root stylesheet
                    ...done in 29.6915673 seconds.

      Regenerating: 1 file(s) changed at 2023-09-05 11:14:29
                    _sass/_style.scss
       Jekyll Feed: Generating feed for posts

I using Nuxt v3.7.1 with bootstrap 5.3.1 and I fixed this error following the AvigdorB's tips:
1 - In node_modules/bootstrap/scss/vendor/_rfs.scss file, add to top:

@use 'sass:math';

2 - In line error, replace:

$dividend: abs($dividend);

to

$dividend: math.abs($dividend);

To add @musaab-abdalla's fix to git (until a new version is released) use patch-package:

Immediate Solution:

Open the bootstrap/vendor/_rfd.scss file.
At the beginning of the file, insert the following line: @use "sass:math";
Locate instances of the abs() function within this file and replace them with math.abs().

4. ```
   npx patch-package bootstrap
   ```

Be aware that this fix does not work under Libsass so the definitive fix for this issue will be something different.

This is mostly right the but the file is _rfs.scss.

@hashimaziz1 The fixed version of Bootstrap is 5.3.2 which is why this PR was closed.
After bumping Bootstrap to 5.3.2, if you still have the error, create a new PR?
"Passing a percentage unit to the global abs() is deprecated since Dart Sass v1.65.0. It resulted in a deprecation warning when compiling Bootstrap with Dart Sass. This has been fixed internally by changing the values passed to the divide() function. The divide() function has not been fixed itself so that we can keep supporting node-sass cross-compatibility. In v6, this won't be an issue as we plan to drop support for node-sass." https://github.com/twbs/bootstrap/releases/tag/v5.3.2

Hey there , i have the same problem
Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent
╷
54 │   $dividend: abs($dividend);
│              ^^^^^^^^^^^^^^
╵
node_modules\bootstrap\scss\vendor_rfs.scss 54:14             divide()
● Mix █████████████████████████ emitting (95%)
emit
Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent
╷
54 │   $dividend: abs($dividend);
│              ^^^^^^^^^^^^^^
╵
node_modules\bootstrap\scss\vendor_rfs.scss 54:14             divide()
× Mix
Compiled with some errors in 5.71s
Deprecation Warning: Passing percentage units to the global abs() function is deprecated.
In the future, this will emit a CSS abs() function to be resolved by the browser.
To preserve current behavior: math.abs(100%)
To emit a CSS abs() now: abs(#{100%})
More info: https://sass-lang.com/d/abs-percent
╷
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loade
rs

|
|
webpack compiled with 1 error

if u are with the same error just follow what the user musaab-abdalla says.

npm i -D patch-package

npx -yes sass-migrator division node_modules/bootstrap/scss/**/*.scss

npx -yes patch-package bootstrap

npm set-script postinstall patch-package

This will automatically change and update all deprecations (more info)[https://sass-lang.com/documentation/breaking-changes/slash-div/#automatic-migration]

This command will create a diff - what was changed

This script will apply that diff every time installing/updating node_modules

Yarn v1 users (more info)[]https://www.npmjs.com/package/patch-package#yarn-v1

yarn add -D patch-package postinstall-postinstall

For those using earlier versions of Bootstrap and encountering the warning related to the abs function, this solution addresses the issue in Bootstrap v4.5.0.
To resolve this warning, I implemented a custom SCSS solution that defines an abs function using sass:math and imports this custom file before the Bootstrap SCSS files. This approach ensures compatibility and resolves the warning without requiring an update to Bootstrap.
Here’s the detailed solution:

Create a Custom SCSS File with abs Function
File: src/styles/scss/_functions.scss
@use 'sass:math';

@function abs($value) {
  @return math.abs($value);
}

Import Custom SCSS File Before Bootstrap Imports
File: src/styles/scss/global.scss
@import './functions';
@import 'bootstrap/scss/functions';
@import 'bootstrap/scss/variables';
@import 'bootstrap/scss/mixins/breakpoints';
@import 'bootstrap/scss/mixins/grid-framework';
@import 'bootstrap/scss/mixins/grid';
@import 'bootstrap/scss/grid';
@import 'bootstrap/scss/utilities/display';
@import 'bootstrap/scss/utilities/flex';
@import 'animate.css/source/_vars.css';
@import 'animate.css/source/_base.css';
@import 'animate.css/source/sliding_entrances/slideInUp.css';

By defining the abs function in the custom _functions.scss file and importing it first, any calls to abs within Bootstrap’s SCSS will use this custom implementation. This approach effectively addresses the warning encountered in Bootstrap v4.5.0.


*: Fix multiple double panic on drop with the added safe_panic macro

What have you changed? (mandatory)
It is generally not safe to panic in a drop function because of the risk of double panic. As @siddontang suggested in #4548, this PR adds a new macro safe_panic, which logs the error instead of panicking if the thread is unwinding due to panic, to fix some known double panic risks. (See the related issues section below)
What are the type of the changes? (mandatory)
Bug fix.
How has this PR been tested? (mandatory)
Unit test.
Does this PR affect documentation (docs) update? (mandatory)
No.
Does this PR affect tidb-ansible update? (mandatory)
No.
Refer to a related PR or issue link (optional)
It should fix #4309, #4310, #4313. Then, PR #4548, #4549 are unnecessary and can be closed.
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

PTAL @overvenus

The only concern I would have with this approach is if it is untenable for the process to continue in these double-panic conditions - in those cases an explicit abort would probably be preferable in safe_panic.


Allow to show multiple panels at the same time (split pane)

VSCode Version: 1.5.1
OS Version: OS X El Capitan

While there's a double pane for files, an errors/terminal board can't be divided into two panes right now. This would be very helpful, since terminal and errors are usually needed together - you type some code and see compilation notes in terminal. Most of the time there's too much whitespace at the right side of the terminal/errors board, so we can add same double-pane toggle icon [ | ] at the right side of the board and make it work:

if double-pane mode is switched on and one side is empty, then, we would add a terminal/errors board right there
if double-pane mode is switched off, then, make visible only left board, right one should disappear
if one of the boards is switched off using hotkey, then, remove it and make a board single-pane (if there's one board in double-pane - remove both panes)

I think there should be a way to split terminal window independently of the amount of code windows.

@bpasero any progress on this issue?

No, this is something we are not working on currently or planning short term.

Duplicate of #10546
There's movement on this.

I'm bummed to see that this feature request has been closed, I would love the ability to see both the terminal and the problems pane at the same time.

This feature request is not closed.

Please make it happen!

Please make it happen!

I'd love to see Output / Terminal at the same time as well.
Really any combination of Output, Debug / Terminal as needed.

Also multiple Outputs, e.g. Output  and Output

In my use case I would love to see Problems and Terminal side by side in a split mode. This allows me to see lint errors and as well as see terminal output at the same time and constantly not to move away my hand from keyboard to mouse to switch between panels.

How to up-vote items in github?

Would love such a feature. Any news?

Great to see it's On Deck, still very interested in this one for me.

Critical feature for me, glad to see it's On Deck, will keep an eye out and switch from Sublime when it's out.

Indeed, having this feature would make things so much easier, especially when working with C++.

With work done this milestone, it is now possible in insiders to drop Terminal next to Problems to see them (or any set of views) at the same time. While we will continue to improve the look and feel of this feature, I believe this satisfies the original request.

Thanks @sbatten ! I'm finally ready to completely move over to VS Code due to this feature. Any video / documentation on how to use it? I'm running the latest VS Code version ( 1.45.0-insider), trying to follow the steps in your test (#93787)

Drag views into a single panel so that they are split horizontally.

I click and drag the Title "Problems" for example and try to drag it into terminal. It doesn't seem to do anything more than re-order the panels. I can't seem to get them into a split screen mode.

@JoshArdito, after dragging "Problems" over "Terminal", hover until the panel switches to "Terminal".  At this point, you can continue to drag the "Problems" inside the panel to side-by-side with "Terminal"


Removing machine specific reference

This line seems to be machine specific and not required.
"iso_path": "/Volumes/Storage/software/ubuntu",

as it leads to this error
virtualbox-iso: Error downloading: stat /Volumes/Storage/software/ubuntu/*.iso: no such file or directory

This is used on our official build machines. To make the builds faster, we have all the .ISO files downloaded. The error is benign, if it can't be found it will still download. We don't know of a better way to use pre-downloaded ISOs if they are present and not have this message displayed. Thankfully packer will still download the ISOs, so you should be seeing your desired behaviour.


Removing subtitle from Dub search links view

Description
Discussed with @quuu and it looks like the subtitle attribute is adding a bit of a visual clutter to the "Search Links" view for the Dub Extension. This PR removes it.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

sweet, more clear :D


Use equalizer with ROG Ally

Apply the equalizer settings tuned by discord user "tomoniutaou33" to ROG ally.
This can solve the problem of low volume in ChimeraOS.

This looks good. I will test it later when the sound patch is updated on unstable. Thank you!

tomoniutaou33 tuned the sink-eq.conf file to fix bass distortion.


Confusing hamming tests

    REM ------- Batch does not support empty string as a parameter. -------
    REM set "expected=left strand must not be empty"
    REM set "if_success=Test passed"
    REM set "if_failed=Test failed: disallow left empty strand."
    REM CALL :Assert "" "G"

    set "expected=right strand must not be empty"
    set "if_success=Test passed"
    set "if_failed=Test failed: disallow right empty strand."
    CALL :Assert "G" ""

If Batch doesn't support an empty string parameter, why is only the first test commented out and not the second one? Should these even be included if the tests can't be run in Batch?

In the first test, empty parameter not taken so first parameter will be like Assert G and second one too can't take empty parameter so second parameter will gone and just first parameter will stay so will be Assert G, when you look we have two same test at the end, second parameter does not have so it's empty in second.
:Assert "" "G" -> :Assert "G"
:Assert "G" "" -> :Assert "G"
:Assert "G" "A" -> :Assert "G" "A"

I don't understand why we need to keep the first test in the test suite if it's not even being run (since it's commented-out).
If we remove the left empty strand test since it can't be properly implemented, we should also remove the right empty strand test. It doesn't make sense to only validate if the right strand is empty when  :Assert "G" "" runs afoul of the rule that the strands need to be the same length. We already have tests in the suite for that.

If one test would be redundant, we can delete the other one, because it is unlikely to be otherwise.


fix: Audit Log records don't get created with threaded task processing

Closes #2949
Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes

Wrapped threaded task runs in transaction.on_commit by default, made it configurable
Added docs, functioning typing
Added debug logging for all webhook errors

How did you test this code?
Unit tests cover the new code paths.
IDE (VSCode + pylance) highlights the task handler "methods" and attributes correctly.

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (8eedf55) 95.64% compared to head (567dd3d) 95.63%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2958      +/-   ##
==========================================
- Coverage   95.64%   95.63%   -0.02%
==========================================
  Files        1012     1012
  Lines       29181    29227      +46
==========================================
+ Hits        27911    27952      +41
- Misses       1270     1275       +5

Files
Coverage Δ

api/app/settings/common.py
88.19% <ø> (ø)

api/webhooks/webhooks.py
95.45% <100.00%> (+0.33%)
:arrow_up:

...k_processor/test_unit_task_processor_decorators.py
93.45% <96.15%> (+0.51%)
:arrow_up:

api/task_processor/decorators.py
95.40% <85.18%> (-4.60%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Not able to control another app

I have a very simple script that just types a few characters after a timeout of like 5 seconds. I run the script and immediately switch to another app. The characters are always typed in the terminal. The app never receives any inputs.
Expected Behavior
The characters should be typed in the app if teh focus is on the app.
Current Behavior
The characters are typed in the terminal no matter where the focus is.
Any advices or workarounds?

Have you tried clicking on the new window? The window has to be in focus to receive the keystrokes.

Yes. I have tried that. It seems as if it is only limited to the console the script is executed in.

If the app is running in admin mode, windows locks up all automations, witch sucks

This issue has been closed because it has been inactive for > 180 days.
You may reopen this issue if it has been closed in error.


Test Data Issue - Invalid Certificate Algorithm

Issue Description
Test Data Issue - Invalid Certificate Algorithm
Ref: https://github.com/eu-digital-green-certificates/dgc-testdata/blob/main/common/2DCode/raw/CO28.json
DSC Certificate is having unsupported Certificate Signature Algorithm: <ObjectIdentifier(oid=1.2.840.10<IP_ADDRESS>, name=ecdsa-with-SHA512)>.
Proposed Solution
Valid values are RSA_WITH_SHA256 and ECDSA_WITH_SHA256

Thank you for clarifying. I would close this as per https://github.com/eu-digital-green-certificates/dgc-testdata/issues/155


[QUESTION] Chapter 4, how do I roll back model parameters? (Early Stopping)

Hi,
Please be patient, I am very new to machine learning. The Early Stopping section introduces an implementation. I ran the code and everything went smooth. My question is how I use the epoch and model that I just found. Here's the code:

from copy import deepcopy

#Creating the data
np.random.seed(42)
m = 100
X = 6 * np.random.rand(m, 1) - 3
y = 2 + X + 0.5 * X**2 + np.random.randn(m, 1)

X_train, X_val, y_train, y_val = train_test_split(X[:50], y[:50].ravel(), test_size=0.5, random_state=10)

# Preparing the data
poly_scaler = Pipeline([
        ("poly_features", PolynomialFeatures(degree=90, include_bias=False)),
        ("std_scaler", StandardScaler())
])
X_train_poly_scaled = poly_scaler.fit_transform(X_train)
X_val_poly_scaled = poly_scaler.transform(X_val)

sgd_reg = SGDRegressor(max_iter=1, tol=-np.infty, warm_start=True, penalty=None, learning_rate="constant", eta0=0.0005)

minimum_val_error = float("inf")
best_epoch = None
best_model = None
for epoch in range(1000):
    sgd_reg.fit(X_train_poly_scaled, y_train) #this continues where it left off
    y_val_predict = sgd_reg.predict(X_val_poly_scaled)
    val_error = mean_squared_error(y_val, y_val_predict)
    if val_error < minimum_val_error:
        minimum_val_error = val_error
        best_epoch = epoch
        best_model = deepcopy(sgd_reg)

Versions

OS: Windows 10.0.19044 Build 19044
Python: 3.9.7
Scikit-Learn: 0.24.2

The best epoch is around 230 ish. I just don't understand how I can use best_model to make predictions on X. Thank you so much in advance.

Hi @serchinnho ,
Thanks for your question, and my sincere apologies for the late response, I somehow missed your message.
The best_model object is a clone of the best SGDRegressor model, so it can be used completely normally, there's no need to roll back model parameters, since this object contains the best ones. So once early stopping is finished, just use best_model normally, for example:
y_pred = best_model.predict(X)

Hope this helps.

Hi Aurelien!
Don't worry about the late response, it happens. I forgot to update this entry, but I checked the exercises on this and other chapters and got my answer. I've tried online courses with videos and only text and your book is by far the tool that has worked the best for me! I'm already at Chapter 8 because I had to stop and learn some statistical methods but I plan on finishing reading. Really great work!

Thanks a lot for your very kind words, @serchinnho , and I'm really glad you found the solution!


etcdserver: fix TestTriggerSnap

Before checking, it needs to wait for snapshot goroutine to finish its
work.
fixes https://github.com/coreos/etcd/issues/2990

LGTM


Electron is leaking Xorg connections over time and on every desktop notification causing Xorg to stop accept clients

Last week I installed the Slack app for Linux and after a while my desktop stopped opening new windows. Trying from console Xorg complained that it reached its max number of clients, which I think by default is 255 (could be changed in Xorg code only):
Maximum number of clients reached
Can't open display.

After some digging turned out that Xorg indeed reached its max number of clients. Since the xrestop didn't report anything suspicious (beside the number of clients) I started killing apps to check which one was causing the issue. Turned it was the Slack app, which freed about 200 connections. Looks like its leaking Xorg connections over time. I suspect the opening and closing the app through the tray icon is doing this, but it was rather inconsistent. However every desktop notification did leak one Xorg connection on every call.
You can monitor the Xorg connections through:
lsof -p [Xorg PID] | grep /tmp/.X11-unix/X0 | wc -l

xrestop reports the new connections as unknown, for instance:
79 - <unknown> ( PID:  ?   ):
  res_base      : ox400000
  res_mask      : ox1fffff
  windows       : 0
  GCs           : 0
  fonts         : 0
  pixmaps       : 0
  pictures      : 0
  glyphsets     : 0
  colormaps     : 0
  passive grabs : 0
  cursors       : 0
  unknowns      : 0
  pixmap bytes  : 0
  other bytes   : ~0
  total bytes   : ~0

Closing the app frees them, but not before that.

Can confirm on Fedora 23. Running Slack alone results in Xorg eventually running out of client connections. Running Atom alone never resulted in the problem though which makes me think that either Atom leaks much slower, Atom does not hit the particular usage pattern that leads to a bug or the problem is specific to Slack and is not necessarily related to Electron.

After some testing I think it is not a bug of Notification, but from something else.
To verify that you can create a notification in Slack by sending slackbot a /remind me in 2s to notify, and then print the number of connections to Xorg with sudo lsof | grep /tmp/.X11-unix/X0 | wc -l. And you can find that the number doesn't change when the notification shows and disapears.

I've added Some Web Notifications to an empty app and they doesn't seem to spawn new connections. Must be something else. I see that Slack app also modifies the icon on notification, I'll try that too.

@bundyo As a workaround, I can suggest you to use the open souce Slack client: https://github.com/raelgc/scudcloud

Well, I didn't open the bug for that :) Still have to test the icons, but more pressing matters here due to a release.

Okay, after being unable to reproduce this, I've took a glimpse in Slack's code and it seems they create their own transparent notification windows and are not using Web Notifications.

Cool, I'm closing this until we can get a way to reproduce this in Electron.

Looks like Slack fixed the issue in the latest 1.2.4 version - a new notification doesn't spawn a ghost Xorg connection anymore. There are almost no changes in the notification scripts and the wrapper object, but they did upgrade to 0.33.6, so I guess the issue was in Electron, but fixed since 0.30.5.
So that's a wrap. :)

@bundyo It was also a bug in our code, https://github.com/paulcbetts/node-system-idle-time/compare/7909062001452523f85680d7035cd35282188605...1.0.4

:+1: Thank you all very much!


CCXT integration documentation (or tutorial) request

Dear Catalyst Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: *nix Mac
Python Version: python 3.6.1
Python Bitness: 64
How did you install Catalyst:  I haven't yet. 😬
Python packages:

altgraph==0.10.2
bdist-mpkg==0.5.0
bonjour-py==0.3
decorator==4.1.2
elasticsearch==5.4.0
elasticsearch-dsl==5.3.0
enum34==1.1.6
envtpl==0.5.3
functools32==3.2.3.post2
ipython-genutils==0.2.0
Jinja2==2.9.6
jsonschema==2.6.0
jupyter-core==4.3.0
macholib==1.5.1
MarkupSafe==1.0
matplotlib==1.3.1
modulegraph==0.10.4
nbformat==4.3.0
numpy==1.8.0rc1
plotly==2.0.8
py2app==0.7.3
pyobjc-core==2.5.1
pyobjc-framework-Accounts==2.5.1
pyobjc-framework-AddressBook==2.5.1
pyobjc-framework-AppleScriptKit==2.5.1
pyobjc-framework-AppleScriptObjC==2.5.1
pyobjc-framework-Automator==2.5.1
pyobjc-framework-CFNetwork==2.5.1
pyobjc-framework-Cocoa==2.5.1
pyobjc-framework-Collaboration==2.5.1
pyobjc-framework-CoreData==2.5.1
pyobjc-framework-CoreLocation==2.5.1
pyobjc-framework-CoreText==2.5.1
pyobjc-framework-DictionaryServices==2.5.1
pyobjc-framework-EventKit==2.5.1
pyobjc-framework-ExceptionHandling==2.5.1
pyobjc-framework-FSEvents==2.5.1
pyobjc-framework-InputMethodKit==2.5.1
pyobjc-framework-InstallerPlugins==2.5.1
pyobjc-framework-InstantMessage==2.5.1
pyobjc-framework-LatentSemanticMapping==2.5.1
pyobjc-framework-LaunchServices==2.5.1
pyobjc-framework-Message==2.5.1
pyobjc-framework-OpenDirectory==2.5.1
pyobjc-framework-PreferencePanes==2.5.1
pyobjc-framework-PubSub==2.5.1
pyobjc-framework-QTKit==2.5.1
pyobjc-framework-Quartz==2.5.1
pyobjc-framework-ScreenSaver==2.5.1
pyobjc-framework-ScriptingBridge==2.5.1
pyobjc-framework-SearchKit==2.5.1
pyobjc-framework-ServiceManagement==2.5.1
pyobjc-framework-Social==2.5.1
pyobjc-framework-SyncServices==2.5.1
pyobjc-framework-SystemConfiguration==2.5.1
pyobjc-framework-WebKit==2.5.1
pyOpenSSL==0.13.1
pyparsing==2.0.1
python-dateutil==1.5
pytz==2013.7
PyYAML==3.12
requests==2.13.0
scipy==0.13.0b1
six==1.4.1
traitlets==4.3.2
urllib3==1.22
xattr==0.6.4
zope.interface==4.1.1

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue
Congrats on the ccxt integration, that seems like a wonderful step forward in terms of interoperability of Catalyst with a larger number of exchanges, particularly for live-trading. I read that note about the integration in the Release Notes, but would love to know a little more.
In that regard, this issue is perhaps a docs issue. Specifically, here are some examples of the type of help I would hope for this issue to address:

Examples of how to use ccxt with Catalyst

Limitations of using ccxt

Recommendations for using ccxt

Short guide/tut/video to using ccxt with a straightforward example (such as adding data from two exchanges with ccxt)

What did you expect to happen?
Please see above

What happened instead?
Just a mention of ccxt integration.

Here is how you can reproduce this issue on your machine:
Reproduction Steps

...
What steps have you taken to resolve this already?
googling?
...
Anything else?
...
Sincerely,
$ whoami

+1


Enhance spec

Enhance spec to reflect swagger CLI usage for the yaml generation and avoid generating Go language extension

@casualjim did i need sign my commit again ?

No but I have to wait for the build to finish

O sorry I can only now see that it wants you to sign your commit. They always have to be signed :)

@casualjim done


Package list derived from "Imports" section of DESCRIPTION file

Coverage remained the same at 97.168% when pulling dfb030dcc81fcc98cc72560a1d588430a0b9919e on ashalper-usgs:AQCU-936 into 55f09bc0de6e484f0238a2148a2827cf3a2fa3a6 on USGS-R:master.

I'm not sure why we need the DOI cert? This is already installed on the servers by the SAs and we shouldn't necessarily have that here?
Otherwise I am interested to see how this works!

Coverage remained the same at 97.168% when pulling 298104ce16ba8e59bfdbd95e482dd48d8cdd0171 on ashalper-usgs:AQCU-936 into 55f09bc0de6e484f0238a2148a2827cf3a2fa3a6 on USGS-R:master.

Coverage remained the same at 97.168% when pulling 298104ce16ba8e59bfdbd95e482dd48d8cdd0171 on ashalper-usgs:AQCU-936 into 55f09bc0de6e484f0238a2148a2827cf3a2fa3a6 on USGS-R:master.


Refactor typography mixin; remove shorthand helpers

The shorthand helpers are being removed in favour of a new mixin govuk-font throughout - this decouples the codebase from the typography scale (allowing it to be overridden by consumers in the future), reduces the number of mixins in our public API and gives us greater control over being able to e.g. warn if points in the scale are going to be deprecated.
Rather than passing font maps around, pass the 'key' from the scale instead.
These changes have been made whilst running a Jest test that expects against against a known-good snapshot of both the default and IE8 stylesheets from master, so the output should be exactly the same.
https://trello.com/c/B8OCSU8R/759-agree-on-and-document-public-api-for-govuk-frontend

looks good. looking forward to the changelog entry :) 📓

looks good. looking forward to the changelog entry :) 📓

Changelog entries added!

Nice work using the snapshots while developing!

It worked really well – trying to think of a way we can turn it into a gulp task e.g. gulp refactor:start which would create a (non-committed) snapshot and run jest in watch mode. Maybe something for firebreak…


[BUG]: some metric doens't show up on Pivot table:panoramix.d.musta.ch/r/1042

Notice: this issue has been closed because it has been inactive for 549 days. Feel free to comment and request for this issue to be reopened.


Allow larger debounce values via UI

Currently the UI limits debounce values to 60,000 but if you edit the JSON it'll happily allow much larger numbers. Can the UI be unbounded (or some extremely high number eg: max_int)?
Use Case: The new Forestry events often involve spawning and despawning things over the span of multiple minutes. I would only like one alert for the very first time but since the UI only goes up to one minute, it ends up alerting in the middle of the event too.
Should be as easy as changing this value if this gets approved. :)
https://github.com/adamk33n3r/runelite-watchdog/blob/79010643136a5487a04cc8074e2a653096df5282/src/main/java/com/adamk33n3r/runelite/watchdog/ui/panels/AlertPanel.java#L281

For convenience, I created a PR ahead of time. Feel free to reject the PR if it goes against your vision.

I'm actually having the same issue with the same use case, on two of the three events I get the notification fired 2 or 3 times because 1m is not enough.

This was actually already suggested in #40. My stance was essentially "if I see a bigger need for it I'll think about it". The use case from #40 was just so weird, that it didn't seem that necessary. My only concern is supporting such large numbers from a visual standpoint since it's in milliseconds it'll kinda be ugly. That being said, I'm ok with the change 👍🏻


Convert to react

Convert it to a simple react app to make it easier to implement TMDB's API. You can omit all the fancy stuff like animation and all.

Hey @aditeyaS can I work on this issue?

Sure @imsherlocked . I will assign it to you

do you need me to provide a version using react for the current project?

Yes, that's what this issue was about. If we convert it to react it will be easier to integrate TMDB API


slow speed the first time write and every 128KB write

hello, I use littlefs on SD card, I have increased the block_size to 1MBytes, but I still found low speed write when I do the tests.

write several big file using littlefs-fuse on ubuntu. every file is about 20-80M big. total file size is about 240M
on my board mount littlefs, and create a new file and write 1KBytes data every loop till to 1MBytes. open/write/close the file every loop.
I found that the first time create/write needs about 80s to complete. What's worse, the fllowing 1KBytes write slows down to around 70s to complete after approx. 128KBytes data has been written.
here is my configurations:

    .read_size = 512,
    .prog_size = 512,
    .block_size = 512*2048,
    .block_count = 400,
    .cache_size = 1024,
    .lookahead_size = 64,
    .block_cycles = 500,

thank you if you can help me point out what's going on here.

I guess the result is this: each time you reopen the file and write 1KB, there will be a process of moving blocks, which will cause you to write 1KB for the first time, 2KB for the second time, ... 1024KB for the 1024th time, so Actually wrote about 512M of data. This is related to the wear leveling mechanism of littlefs.

@Johnxjj @geky here is the log file
1MBytes seppd test.txt

It looks like the superblock migration has happened. You should print out the specific write block (which block) and erase block (which block) so that you can analyze where the time is spent.

Hi @summer20100514, thanks for creating an issue.
This look related https://github.com/ARMmbed/littlefs/issues/75, but it looks like you've already gone for the workaround of increasing the block size, so I suspect you may now be running into https://github.com/ARMmbed/littlefs/issues/214? So it may be worth trying to scale the block size down a bit and see if it improves performance.
Though honestly, littlefs just doesn't scale to larger sizes well. It's an area I have some ideas on, but I can't make any promises about when I'll be able to make progress.

@geky hopefully one day the performance issue will be solved. what I am thinking about is that more RAM consumption is acceptable compared to the unacceptable longlonglong latency


doesn't seem to be working - global modules

In the node prompt I typed
require('resolve').sync('gulp')

Error: Cannot find module 'gulp' from '.'
    at Function.module.exports [as sync] (C:\Users\Administrator\AppData\Roaming\npm\node_modules\resolve\lib\sync.js:33:11)
    at repl:1:21
    at REPLServer.self.eval (repl.js:110:21)
    at Interface.<anonymous> (repl.js:239:12)
    at Interface.EventEmitter.emit (events.js:95:17)
    at Interface._onLine (readline.js:202:10)
    at Interface._line (readline.js:531:8)
    at Interface._ttyWrite (readline.js:760:14)
    at ReadStream.onkeypress (readline.js:99:10)
    at ReadStream.EventEmitter.emit (events.js:98:17)

But I am able to require gulp from node...This is a global module..

I'm experiencing the same issue.

+1

You can't require global modules, as such, resolve (just like require.resolve) shouldn't be able to find them.
@skandasoft do you have $NODE_PATH set to npm root -g? If so, that would enable node to require your global modules, but since that's a hugely deprecated bad practice, resolve wouldn't support that automatically.
However, you can pass a __basedir option to resolve set to process.env.NODE_PATH and it might be able to find it.


cache_promote plugin:  put a mutex-protected critical section into a Continuation.

This should hopefully reduce event thread blocking.
This PR is dependent on https://github.com/apache/trafficserver/pull/4848 .
The drawback is that this new version involves three dynamic memory allocations each time the critical section is entered.  So it depends on jemalloc whether there is a net benefit.  Whether jemalloc is good at avoiding the need to take a mutex for allocation, and at keeping the critical section short when taking a mutex is necessary.
If you fetch the branch for this PR and do a diff with 'meld', it shows more clearly what has really been changed.

I would very much prefer keeping the cppapi out of this plugin. Well, I’m -1 on it, try again.

Also help me understand which critical section is stalling the net thread? I find the idea of three allocations really discouraging on top of the cppapi shenanigans.

Ok, I see what section you are referring to, you are positive this is a bottleneck? You see that in traffic?

Note that Continuation.h/Continuation.cc is stand-alone from the rest of the cppapi.  So there is little reason to think that the dubiously-documented cppapi performance problems would be an issue with it.
If you looked at the change with a diff utility that was good at detect moved code allowing for white space changes, it would look much smaller.  I don't using try-lock and reentering cont_handle_policy() would be as simple as you're thinking.
I am just trying to explore ways we can align better with TS's event-driven core.  Maybe we need to conclude that it's generally better to create a new thread in some way to avoid blocking a core event-handling thread.
The core doesn't seem to have good facilities to handle prioritizing transactions that need to be low-latency.  Event threads would need priority queues for continuations.  An event thread would need to be able to bump up the priority of another thread that was holding a mutex it needed to take (priority inheritance).

Walt-- how much time has this cache promote change seen in production? It's a critical plugin for us, so need to ensure it has seen a lot of action before it is merged.

I don't know if we use this one in production, my changes have not been tested.  It's a WIP at best.

Hmm. Seems like we should abandon this change until it's seen some serious testing.

Our efforts to create a suite of automated regression tests should focus first on the features / plugins that are most used.  Do you all have any regression tests for this plugin that you could open source?

Replaced by https://github.com/apache/trafficserver/pull/5412 .


CSS Networking DNS private resolver limitation.md

Add limitation about Expressroute Fast Path and DNS private resolver

#sign-off

@duongau

After this validates, can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Viterbi decode issue

Hi all, I need to decode in Python a bit stream that has been encoded with Tail-biting Convolutional Code. The signal has been encoded with the following parameters:
K=8, m=3, G=(54,60)
For example, if the encoded bit stream is the following:
bits_array_id = [0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0]
I should get the following decoded output:
[0, 0, 1, 0, 0, 1, 1, 1]
In Matlab I get the correct result implementing the following code:
encoded_data = [0 1 0 0 0 1 0 1 1 0 0 1 1 0 0 0];
K = 8;
m = 3;
constraint_length = m + 1;
tblen = K;
generator_poly = {'x3+x1+1','x3+x2'};
trellis = poly2trellis(constraint_length, generator_poly);
y1  = 1 - 2 * encoded_data(:);
y2 = kron(ones(3,1),y1(:));
w = vitdec(y2, trellis, tblen,'trunc','unquant');
data = w(end-K+1:end);
In Python I have implemented the following code, but unfortunately I haven't been able to get the correct result:
bits_array = [0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0]
cc1 = fec_conv.FECConv(('1011', '1100'), Depth=8)
y1  = 1 - 2 * bits_array
y2 = np.kron(np.ones((3,), dtype=int),y1)
bits_array_decoded = cc1.viterbi_decoder(y2, metric_type='unquant')
bits_array_decoded = bits_array_decoded[4:12]
Do you have any hint on what I am doing wrong? Is it the Polys G1 and G2 that are not defined correctly?
Thank you in advance for your help.

Running in a notebook produced the following output:
from sk_dsp_comm.fec_conv import FECConv
import numpy as np

bits_array = np.array([0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0])
cc1 = FECConv(('1011', '1100'), Depth=8)

y1 = 1 - 2 * bits_array
y2 = np.kron(np.ones((3,), dtype=int),y1)

bits_array_decoded = cc1.viterbi_decoder(y2, metric_type='unquant')

bits_array_decoded

array([0., 1., 1., 1., 0., 0., 1., 0., 0., 1., 1., 1., 0., 0., 1., 0., 0.])

bits_array_decoded[4:12]

array([0., 0., 1., 0., 0., 1., 1., 1.])

Running in a notebook produced the following output:
from sk_dsp_comm.fec_conv import FECConv
import numpy as np

bits_array = np.array([0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0])
cc1 = FECConv(('1011', '1100'), Depth=8)

y1 = 1 - 2 * bits_array
y2 = np.kron(np.ones((3,), dtype=int),y1)

bits_array_decoded = cc1.viterbi_decoder(y2, metric_type='unquant')

bits_array_decoded

array([0., 1., 1., 1., 0., 0., 1., 0., 0., 1., 1., 1., 0., 0., 1., 0., 0.])

bits_array_decoded[4:12]

array([0., 0., 1., 0., 0., 1., 1., 1.])

Thanks for your reply. You are right, it works for the example data (which is the ID in a bit stream collected with an SDR) I provided but only if you choose the range [4:12] in "bits_array_decoded", while in Matlab I need to take the last 8 bits of "w". In addition, this array "w" has a different size than the array "bits_array_decoded" in Python. This confuses me.
But if I choose the following input encoded sequence (which is the payload of the same bit stream): --> bits_array = [1, 0, 0, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 0, 0, 0]
I should then get the following decoded output: --> [1, 0, 1, 0, 0, 1, 1, 1]
But instead in Python I get: --> [0,0,0,0,1,1,1,1,0,0,0,1,1,1,1,0,0] and the range [4:12] or other ranges will not give the expected output.
And if I consider the CRC data in the same bit stream, which is: --> bits_array = [1, 0, 1, 1, 0, 0, 0, 1, 0, 1, 1, 0, 1, 0, 1, 1]
I expect to get a decoded output of [1, 0, 0, 1, 0, 0, 0, 1], but also in this case I get a different result.
This is why I think there must be something wrong I am doing.

To get you some more examples please see my course Web Site for DIgital Communications 2 (https://ece.uccs.edu/~mwickert/ece5630/). The final exam from Fall 2021 has Problem 3 which indeed uses these functions. There is both a PDF exam document (https://ece.uccs.edu/~mwickert/ece5630/lecture_notes/solutions/5630fe_f2021.pdf) and a ZIP containing a Jupyter notebook (https://ece.uccs.edu/~mwickert/ece5630/lecture_notes/5630_Final_Project.zip), all under the Python Projects tab in the center column.
I am not sure of the K = 4 polynomials you are using, but I used them below and the output bits match the input bits.
Run this code:

EbN0 = 4
# cc2 = fec.FECConv(('101','111'),Depth=15) # decision depth is 10
cc3 = fec.FECConv(('1011', '1100'), Depth=15) # Depth of 5*(K-1) = 15 is better
# Encode with shift register starting state of '00'
state = '000'
# Create
N_bits = 50
# random 0/1 bits
x = randint(0,2,N_bits)
y,state = cc3.conv_encoder(x,state)
# Add channel noise to bits translated to +1/-1
yn = dc.cpx_awgn(2*y-1,EbN0-3,1) # Channel SNR is dB less
# Translate noisy +1/-1 bits to soft values on [0,7]
# yn = (yn.real+1)/2*7 # 3-bit soft 0 to 7 values with noise
# cc1.viterbi_decoder(x, metric_type='soft', quant_level=3)
# z = cc3.viterbi_decoder(yn,metric_type='soft',quant_level=3)
z = cc3.viterbi_decoder(yn.real,metric_type='unquant') # yn +/-1 values w/noise

Compare input and output bits in side-by-side columns

hstack((array([int16(x[:35])]).T,array([int16(z[:35])]).T))

array([[1, 1],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [0, 0],
       [0, 0],
       [0, 0],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1]], dtype=int16)

To get you some more examples please see my course Web Site for DIgital Communications 2 (https://ece.uccs.edu/~mwickert/ece5630/). The final exam from Fall 2021 has Problem 3 which indeed uses these functions. There is both a PDF exam document (https://ece.uccs.edu/~mwickert/ece5630/lecture_notes/solutions/5630fe_f2021.pdf) and a ZIP containing a Jupyter notebook (https://ece.uccs.edu/~mwickert/ece5630/lecture_notes/5630_Final_Project.zip), all under the Python Projects tab in the center column.

I am not sure of the K = 4 polynomials you are using, but I used them below and the output bits match the input bits.

Run this code:

EbN0 = 4
# cc2 = fec.FECConv(('101','111'),Depth=15) # decision depth is 10
cc3 = fec.FECConv(('1011', '1100'), Depth=15) # Depth of 5*(K-1) = 15 is better
# Encode with shift register starting state of '00'
state = '000'
# Create
N_bits = 50
# random 0/1 bits
x = randint(0,2,N_bits)
y,state = cc3.conv_encoder(x,state)
# Add channel noise to bits translated to +1/-1
yn = dc.cpx_awgn(2*y-1,EbN0-3,1) # Channel SNR is dB less
# Translate noisy +1/-1 bits to soft values on [0,7]
# yn = (yn.real+1)/2*7 # 3-bit soft 0 to 7 values with noise
# cc1.viterbi_decoder(x, metric_type='soft', quant_level=3)
# z = cc3.viterbi_decoder(yn,metric_type='soft',quant_level=3)
z = cc3.viterbi_decoder(yn.real,metric_type='unquant') # yn +/-1 values w/noise

* Compare input and output bits in side-by-side columns

hstack((array([int16(x[:35])]).T,array([int16(z[:35])]).T))

array([[1, 1],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [0, 0],
       [0, 0],
       [0, 0],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [0, 0],
       [0, 0],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1],
       [1, 1],
       [1, 1],
       [1, 1],
       [0, 0],
       [1, 1]], dtype=int16)

Thanks for your reply and links, I will have now a look at them.
The K value should be 8. The polynomials definition could definitively be something wrong I am doing. The polynomials I need to use are the following: {'x3+x1+1', 'x3+x2'}. In octal these polynomials are {54, 60}. My understanding is that I can represent them as '1011' and '1100'. Is this correct? If not, what would be the correct values?

From your two polynomials above there is a problem. Note from the screenshot taken from https://en.wikipedia.org/wiki/Convolutional_code that the ones and zeros define xor connections used to form the two encoder bit streams that are multiplexed together to form a stream of two output bits for every input bit.

Your polynomials start with one or more 1s but end in a string of multiple zeros. This breaks the code from a true K=6 code. Prepending the polynomials with zeros is also a problem. I think you need to figure out the proper polynomials to make your encoder work properly.

I see what you mean, the octal polynomials 54 and 60 have zeros at the end and this causes issues in the decoder. For this decoding the octal polynomials 13 and 14 also work in Matlab. I get the correct decoded data when running the following Matlab script:
encoded_data = [0 1 0 0 0 1 0 1 1 0 0 1 1 0 0 0];
K = 8;
m = 3;
constraint_length = m + 1;
tblen = K;
trellis = poly2trellis(constraint_length,[13 14]);
y  = 1 - 2 * encoded_data(:);
y = kron(ones(3,1),y(:));
w = vitdec(y, trellis, tblen,'trunc','unquant');
data = w(end-K+1:end);

This matlab code gives the output: [0 0 1 0 0 1 1 1]
But if I implement the same in python, using the same octal polynomials 13 and 14, which correspond to '1011' and '1100', I do not get the correct result. I post the python code below. Is it due to the fact that '1100' ends with two zeros?
bits_array = [0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0]
cc1 = fec_conv.FECConv(('1011', '1100'), Depth=8)
y1 = 1 - 2 * bits_array
y2 = np.kron(np.ones((3,), dtype=int),y1)
bits_array_decoded = cc1.viterbi_decoder(y2, metric_type='unquant')
bits_array_decoded = bits_array_decoded[4:12]

I just tried your polynomials and get this on my iPad running the Juno app:

The trace back also looks good:

Thanks, I have finally found the issue thanks to a colleague's help. I share it here as it may be useful for other as well. There is a difference in the analog to digital mapping between Matlab and Python:

Matlab uses: 1 -->0
Python uses: 1-->1

Therefore, the main adjustment to make is to replace:
y1 = 1 - 2 * bits_array
with:
y1  = 2 * bits_array - 1
I have also increased the Depth from 8 to 17. The code is below:
bits_array = [0, 1, 0, 0, 0, 1, 0, 1, 1, 0, 0, 1, 1, 0, 0, 0]
cc1 = fec_conv.FECConv(('1011', '1100'), Depth=17)
y1  = 2 * bits_array - 1
y2 = np.kron(np.ones((3,), dtype=int),y1)
bits_array_decoded = cc1.viterbi_decoder(y2, metric_type='unquant')

This now gives the expected output. Thanks a lot @mwickert for your help!

Glad you resolved the data bit polarity issue. I have not used the MATLAB convolution coding/decoding tools for quite some time. In all of scikit-dsp-comm I assume a simple level shifter approach, so (0,1) => (-1,1). Also from a digital comm book I see that for K=4 a better performing code is (bin(0o17),bin(0o15)).
Wishing you the best. Where are you located?

Thanks for the suggestion on better polynomials, however I cannot change the polynomials in the encoder side since the device transmitting the wireless data cannot be modified.
I wish you the best as well and thank you for your work in this great and very useful library. I am located in Sweden.

I want to also mention that a Rust language binding is also available: https://github.com/scikit-dsp-comm/rs_fec_conv


add all information_schema.innodb_* tables as empty tables

Great work! Would love test cases for all of these. Cc my pr

approving this. just take a second pass through  to make sure all added schemas are correct.


Statevector backend can't work well.

Statement
In recent blueqat updates, I guess that default backend is changed from a statevector to a sampler.
How can I use a statevector backend rather than a sampler in the latest blueqat?
Reproduce the problem
In old version of blueqat (probably, 2021),
import math
def print_Zbasis_expression(statevector):
    nqubit = int(math.log2(np.size(statevector)))
    for i in range(2**nqubit):
        print('+({:.2f})*|{number:0{width}b}>'.format(statevector[i],number=i,width=nqubit),end='')

State_out = Circuit(1).h[0].run()
print_Zbasis_expression(State_out)

returns,
+(0.71+0.00j)*|0>+(0.71+0.00j)*|1>

However, in the latest blueqat (version 2.0.3), the same code returns a different result.
+(0.00)*|0>

I guess that default backend is changed from a statevector to a sampler.
Expected
Circuit(1).h[0].run(backend="statevector")
or
Circuit(1).h[0].run_with_ibmq(backend="statevector")

[0.71+0.00j, 0.71+0.00j]

Thanks.

Sorry, the problem is self-resolved.
Circuit(1).h[0].run(backend="numpy")

returns the statevector.


Use mirrorlist generated by rankmirrors

Original mirrorlist only includes the "mirror-director" mirror, which in my experience ends up being super slow and at times ends up making pacman fail (since there are no other mirrors to fall back on).
This PR replaces it with one obtained by running rankmirrors on the latest mirrorlist provided by alarm's pacman-mirrorlist.
The main geo-ip mirror is still the first line, but the other mirrors are enabled too.

LGTM.