Colors with gulp-util.colors

Hello,
I was trying this package and it works just fine, however I was trying to add some colors to the output of my gulp tasks and it doesn't print them.
I'm using the gulp-util module to color my output, and it works perfectly on the terminal but not under the sublime result window. Why? Can it be fixed?
Thank you.

Hello!
The output you see on Sublime Text it's just the text gulp writes to STDOUT being added to a regular tab. Sadly there's no way to actually see the output formatted as like you do in the Terminal.
The color you see while using the package is defined here, the solution would be creating your own Syntax Definition and then using it by overriding the syntax option of this package.
It's annoying, I know :(

@NicoSantangelo thanks for confirming my fears, I had run with this "issue" with build systems in the past. Frankly if the way to create a Syntax Definition it's not worth it. You can close this!


[tool_crash] FileSystemException: Cannot open file, OS Error: The file or directory is corrupted and unreadable., errno = 1392

Command
flutter doctor

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot open file, OS Error: The file or directory is corrupted and unreadable.
, errno = 1392
#0      _File.throwIfError (dart:io/file_impl.dart:635:7)
#1      _File.openSync (dart:io/file_impl.dart:479:5)
#2      _File.writeAsBytesSync (dart:io/file_impl.dart:604:31)
#3      _File.writeAsStringSync (dart:io/file_impl.dart:628:5)
#4      ForwardingFile.writeAsStringSync (package:file/src/forwarding/forwarding_file.dart:147:16)
#5      ErrorHandlingFile.writeAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:259:22)
#6      _runSync (package:flutter_tools/src/base/error_handling_io.dart:560:14)
#7      ErrorHandlingFile.writeAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:258:5)
#8      Cache.setStampFor (package:flutter_tools/src/cache.dart:529:35)
#9      VersionCheckStamp.store (package:flutter_tools/src/version.dart:587:19)
#10     FlutterVersion._getLatestAvailableFlutterDate (package:flutter_tools/src/version.dart:494:31)
<asynchronous suspension>
#11     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart:399:46)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:257:11)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:152:19)
<asynchronous suspension>
#14     AppContext.run (package:flutter_tools/src/base/context.dart:151:12)
<asynchronous suspension>
#15     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:239:5)
<asynchronous suspension>
#16     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#17     run.<anonymous closure> (package:flutter_tools/runner.dart:60:12)

[✓] Flutter (Channel dev, 1.27.0-8.0.pre, on Microsoft Windows [Version
    10.0.19042.867], locale en-US)
    • Flutter version 1.27.0-8.0.pre at D:\AbdulsWork\flutter
    • Framework revision b7d4806243 (7 weeks ago), 2021-02-19 09:22:45 -0800
    • Engine revision 6993cb229b
    • Dart version 2.13.0 (build 2.13.0-30.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\Sony\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.55.1)
    • VS Code at C:\Users\Sony\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0

[✓] Connected device (3 available)
    • Redmi Note 8 (mobile) • 1701f8c7 • android-arm64  • Android 9 (API 28)
    • Chrome (web)          • chrome   • web-javascript • Google Chrome
      89.0.4389.114
    • Edge (web)            • edge     • web-javascript • Microsoft Edge
      89.0.774.57

• No issues found!

Flutter Application Metadata
No pubspec in working directory.

@abdul-basit-dev
the issue might be caused by a corrupted installation https://github.com/flutter/flutter/issues/60107#issuecomment-695061619
please try this fix

@abdul-basit-dev
Check above link and solution to see if it resolves your issue.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


BadgeUp init provides no feedback on error

Like the title says currently /badgeup init provides no feedback to the player that ran the command. I had to look in the console to see what happened when I ran the command.

Resolved in e6fcb172d55b8647ff4bc869771b87769485ccd6


Can't ccompile

-- USE_CPU_XENONCAT DEFINED
-- USE_CUDA_DJEZO DEFINED
-- Boost version: 1.61.0
-- Found the following Boost libraries:
--   system
--   log_setup
--   log
--   date_time
--   filesystem
--   thread
--   regex
--   chrono
--   atomic
-- CXXFLAGS:  -std=c++11 -m64 -msse2
-- LIBS: /usr/lib/x86_64-linux-gnu/libboost_system.a;/usr/lib/x86_64-linux-gnu/libboost_log_setup.a;/usr/lib/x86_64-linux-gnu/libboost_log.a;/usr/lib/x86_64-linux-gnu/libboost_date_time.a;/usr/lib/x86_64-linux-gnu/libboost_filesystem.a;/usr/lib/x86_64-linux-gnu/libboost_thread.a;/usr/lib/x86_64-linux-gnu/libboost_regex.a;/usr/lib/x86_64-linux-gnu/libboost_chrono.a;/usr/lib/x86_64-linux-gnu/libboost_atomic.a;/usr/lib/x86_64-linux-gnu/libpthread.a
CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find CUDA (missing: CUDA_CUDART_LIBRARY) (found version "8.0")
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.5/Modules/FindCUDA.cmake:949 (find_package_handle_standard_args)
cuda_djezo/CMakeLists.txt:20 (FIND_PACKAGE)
-- Configuring incomplete, errors occurred!
See also "/root/nheqminer/CMakeFiles/CMakeOutput.log".
See also "/root/nheqminer/CMakeFiles/CMakeError.log".
this is the error
help me plz ?

I am also seeing this identical error, but with boost 1.63 installed.
root@a5518a5e71c4:~/build# lsb_release -dcr
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial
root@a5518a5e71c4:~/build# echo $LD_LIBRARY_PATH
:/usr/local/cuda-8.0/lib64:/usr/local/cuda-8.0/lib64/stubs
root@a5518a5e71c4:~/build# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/cuda-8.0/:/usr/local/cuda-8.0/bin
root@a5518a5e71c4:~/build# pwd
/root/build
root@a5518a5e71c4:~/build# ls ../
boost  boost_1_63_0  boost_1_63_0.tar  build  nheqminer

root@a5518a5e71c4:~/build# cmake ../nheqminer/
...
...
...
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.63.0
-- Found the following Boost libraries:
--   system
--   log_setup
--   log
--   date_time
--   filesystem
--   thread
-- CXXFLAGS:  -std=c++11 -m64 -msse2
-- LIBS: /root/boost_1_63_0/stage/lib/libboost_system.a;/root/boost_1_63_0/stage/lib/libboost_log_setup.a;/root/boost_1_63_0/stage/lib/libboost_log.a;/root/boost_1_63_0/stage/lib/libboost_date_time.a;/root/boost_1_63_0/stage/lib/libboost_filesystem.a;/root/boost_1_63_0/stage/lib/libboost_thread.a;/usr/lib/x86_64-linux-gnu/libpthread.a
CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
  Could NOT find CUDA (missing: CUDA_CUDART_LIBRARY) (found version "8.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.5/Modules/FindCUDA.cmake:949 (find_package_handle_standard_args)
  cuda_djezo/CMakeLists.txt:20 (FIND_PACKAGE)

yeaaa i think there is a problem with CUDA. maybe we need 7.5 install and not 8.... haven't found anything similar.
my setup is the same as yours except libboost

I have same problem. It's cmake3 bug http://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=16096&graph=dependency&orientation=horizontal . Solution is to update cmake3 or comment out string CUDA_CUDART_LIBRARY in file FindCUDA.cmake

Have a simpler solution, though yes upgrading cmake works, adding a flag works as well.
export CUDA_CUDART_LIBRARY="/usr/local/cuda/lib64/libcudart.so"

cd nheqminer/cpu_xenoncat/asm_linux \
  && sh assemble.sh \
  && cd /home/nheqminer \
  && mkdir build/ \
  && cd build/ \
  && cmake -DCUDA_CUDART_LIBRARY=CUDA_CUDART_LIBRARY ../nheqminer  \
  && make -j $(nproc)

I put together a docker image that seems to do the job on ubuntu, and it runs CUDA --- covers most of the above issues.
https://hub.docker.com/r/unsalted/nheqminer/

@unsalted I have the same problem. Setting a flag seems to be not working for me. And, by setting up the docker container, the nheqminer fails in benchmark:
$ sudo docker exec nheqminer bash -c "nheqminer -b"

		==================== www.nicehash.com ====================
			Equihash CPU&GPU Miner for NiceHash v0.5c
		Thanks to Zcash developers for providing base of the code.
	    	Special thanks to tromp, xenoncat and djeZo for providing
	      	optimized CPU and CUDA equihash solvers.
		==================== www.nicehash.com ====================

	Setting log level to 2
	[14:19:21][0x00007f5eee4b5740] Using SSE2: YES
	[14:19:21][0x00007f5eee4b5740] Using AVX: YES
	[14:19:21][0x00007f5eee4b5740] Using AVX2: YES
	[14:19:22][0x00007f5eee4b5740] Benchmark starting... this may take several minutes, please wait...
	[14:19:22][0x00007f5eee4b5740] Benchmark done!
	[14:19:22][0x00007f5eee4b5740] Total time : 0 ms
	[14:19:22][0x00007f5eee4b5740] Total iterations: 0
	[14:19:22][0x00007f5eee4b5740] Total solutions found: 0
	[14:19:22][0x00007f5eee4b5740] Speed: -nan I/s
	[14:19:22][0x00007f5eee4b5740] Speed: -nan Sols/s

My CMake log message after setting the CUDA_CUDART_LIBRARY flag is:
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- USE_CPU_XENONCAT DEFINED
-- USE_CUDA_DJEZO DEFINED
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Error at /usr/share/cmake-3.5/Modules/FindBoost.cmake:1677 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.58.0

  Boost include path: /usr/include

  Could not find the following static Boost libraries:

          boost_system
          boost_log_setup
          boost_log
          boost_date_time
          boost_filesystem
          boost_thread

  Some (but not all) of the required Boost libraries were found.  You may
  need to install these additional Boost libraries.  Alternatively, set
  BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT
  to the location of Boost.
Call Stack (most recent call first):
  CMakeLists.txt:60 (find_package)

Boost_FOUND NOT FOUND
-- CXXFLAGS:  -std=c++11 -m64 -msse2
-- LIBS:
-- Found CUDA: /usr/local/cuda (found version "8.0")
CUDA FOUND
-- CUDA_NVCC_FLAGS: -gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_52,code=sm_52;-gencode;arch=compute_60,code=sm_60
-- Configuring incomplete, errors occurred!
See also "/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeOutput.log".
See also "/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeError.log".

Then I referred to nheqminer/build/CMakeFiles/CMakeError.log which looks like:
Determining if the pthread_create exist failed with the following output:
Change Dir: /home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_59f96/fast"
/usr/bin/make -f CMakeFiles/cmTC_59f96.dir/build.make CMakeFiles/cmTC_59f96.dir/build
make[1]: Entering directory '/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_59f96.dir/CheckSymbolExists.c.o
/usr/bin/cc    -m64 -msse2    -o CMakeFiles/cmTC_59f96.dir/CheckSymbolExists.c.o   -c /home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTC_59f96
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_59f96.dir/link.txt --verbose=1
/usr/bin/cc   -m64 -msse2     CMakeFiles/cmTC_59f96.dir/CheckSymbolExists.c.o  -o cmTC_59f96
CMakeFiles/cmTC_59f96.dir/CheckSymbolExists.c.o: In function `main':
CheckSymbolExists.c:(.text+0x16): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_59f96.dir/build.make:97: recipe for target 'cmTC_59f96' failed
make[1]: *** [cmTC_59f96] Error 1
make[1]: Leaving directory '/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_59f96/fast' failed
make: *** [cmTC_59f96/fast] Error 2

File /home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include <pthread.h>

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(&pthread_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with the following output:
Change Dir: /home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_cf457/fast"
/usr/bin/make -f CMakeFiles/cmTC_cf457.dir/build.make CMakeFiles/cmTC_cf457.dir/build
make[1]: Entering directory '/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_cf457.dir/CheckFunctionExists.c.o
/usr/bin/cc    -m64 -msse2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o CMakeFiles/cmTC_cf457.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.5/Modules/CheckFunctionExists.c
Linking C executable cmTC_cf457
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_cf457.dir/link.txt --verbose=1
/usr/bin/cc   -m64 -msse2 -DCHECK_FUNCTION_EXISTS=pthread_create    CMakeFiles/cmTC_cf457.dir/CheckFunctionExists.c.o  -o cmTC_cf457 -lpthreads
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_cf457.dir/build.make:97: recipe for target 'cmTC_cf457' failed
make[1]: *** [cmTC_cf457] Error 1
make[1]: Leaving directory '/home/xinye/Desktop/nheqminer/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_cf457/fast' failed
make: *** [cmTC_cf457/fast] Error 2

make[2]: *** No rule to make target '../../cpu_xenoncat/Linux/asm/equihash_avx1.o', needed by 'nheqminer_cpu'.  Stop.
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nheqminer_cpu.dir/all' failed
make[1]: *** [CMakeFiles/nheqminer_cpu.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
error everywhere !!!

Check your cmake version.
On Apr 12, 2017, at 2:36 PM, napoleon2121<EMAIL_ADDRESS>wrote:
make[2]: *** No rule to make target '../../cpu_xenoncat/Linux/asm/equihash_avx1.o', needed by 'nheqminer_cpu'. Stop.
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nheqminer_cpu.dir/all' failed
make[1]: *** [CMakeFiles/nheqminer_cpu.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
error everywhere !!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

cmake version 3.5.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).

cmake version 3.5.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
what version should i hav to correct this  ?

That looks correct -- here is my dockerfile, make sure boost is the right version as well.
https://github.com/unsalted/docker-nheqminer-cuda/blob/master/Dockerfile
On Apr 12, 2017, at 6:58 PM, napoleon2121<EMAIL_ADDRESS>wrote:
cmake version 3.5.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
what version should i hav to correct this ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@unsalted Thank you SO MUCH!

I have also been at this for some time now and cannot get it right. Please, if someone knows what is going on here:
oliver@Ollie-NZXT-Ubuntu:~/Downloads/build$ make -j $(nproc)
[  4%] Building NVCC (Device) object cuda_djezo/CMakeFiles/cuda_djezo.dir/cuda_djezo_generated_equi_miner.cu.o
[ 13%] Built target cpu_xenoncat
CMake Error at cuda_djezo_generated_equi_miner.cu.o.cmake:222 (message):
  Error generating
  /home/oliver/Downloads/build/cuda_djezo/CMakeFiles/cuda_djezo.dir//./cuda_djezo_generated_equi_miner.cu.o

cuda_djezo/CMakeFiles/cuda_djezo.dir/build.make:63: recipe for target 'cuda_djezo/CMakeFiles/cuda_djezo.dir/cuda_djezo_generated_equi_miner.cu.o' failed
make[2]: *** [cuda_djezo/CMakeFiles/cuda_djezo.dir/cuda_djezo_generated_equi_miner.cu.o] Error 1
CMakeFiles/Makefile2:178: recipe for target 'cuda_djezo/CMakeFiles/cuda_djezo.dir/all' failed
make[1]: *** [cuda_djezo/CMakeFiles/cuda_djezo.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

And my versions are:

oliver@Ollie-NZXT-Ubuntu:~/Downloads/build$ cmake --version
cmake version 3.9.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).
oliver@Ollie-NZXT-Ubuntu:~/Downloads/build$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Tue_Jan_10_13:22:03_CST_2017
Cuda compilation tools, release 8.0, V8.0.61

Along with Boost 1.65
Any help would be greatly appreciated.

@napoleon2121 Where did you placed your /build directory? Unlike other applications, it should be placed outside /nheqminer directory.

I am having same error now. I did exact install few days ago with no error.
*** No rule to make target '../../cpu_xenoncat/Linux/asm/equihash_avx1.o', needed by 'nheqminer_cpu'. Stop.

Same error here.

I have the same error
$ sudo cmake . && make
-- Boost version: 1.62.0
-- Found the following Boost libraries:
--   system
--   log_setup
--   log
--   date_time
--   filesystem
--   thread
--   regex
--   chrono
--   atomic
-- Configuring done
-- Generating done
-- Build files have been written to: /home/zcash/nheqminer/Linux_cmake/nheqminer_cpu
make[2]: *** No rule to make target '../../cpu_xenoncat/Linux/asm/equihash_avx1.o', needed by 'nheqminer_cpu'.  Stop.
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nheqminer_cpu.dir/all' failed
make[1]: *** [CMakeFiles/nheqminer_cpu.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
I am using cmake version 3.7.2
any solution?

@joseortiz3  - most probably cuda folder just a simlink to a current version of cuda installation directory. I suggest it pointing to your cuda-9.1

When Dealing with the former  to compile consistency one must  run:
while replacing the actual location to  libscuart.so to one relevant to your system.
cmake -DCUDA_CUDART_LIBRARY="/usr/local/cuda-9.1/lib64/libcudart.so" ../nheqminer
When Dealing with the lather, to at least get past this issue one must rename the unpackaged source code's directory to match  the make target which should be _nheqminer.  When we've acquired  the code from a release or so the packaged directory name may mismatch with whats baked in the target rules.
[ 22%] Built target cpu_xenoncat
make[2]: *** No rule to make target '../nheqminer/cpu_xenoncat/asm_linux/equihash_avx1.o', needed by 'nheqminer'.  Stop.
CMakeFiles/Makefile2:68: recipe for target 'CMakeFiles/nheqminer.dir/all' failed
make[1]: *** [CMakeFiles/nheqminer.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2


Many superficial fixes to the contributor book

I did an extensive review of the contributor book. I think once this is merged it will be ready to be hosted

@antimora Thanks for the review. Fixed the unrelated candle stuff and also the run-checks command which was wrong.


Unable to update

Microsoft PowerToys version
0.53.3
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce
Trying to update directly via app crashes the updater, trying to update by installing the new .exe from releases produces "Another version of this product is already installed"
I have tried uninstalling current version from control panel and running installer again but same error occurs.
Here are the logs:

[4564:5B54][2022-02-23T01:55:12]i001: Burn v<IP_ADDRESS>16, Windows v10.0 (Build 22000: Service Pack 0), path: C:\Users\geast\AppData\Local\Temp{5CE4AD8A-85A0-4D85-AE83-3F4F80E221F5}.cr\PowerToysSetup-0.55.1-x64.exe
[4564:5B54][2022-02-23T01:55:12]i000: Initializing string variable 'InstallFolder' to value '[ProgramFiles64Folder]PowerToys'
[4564:5B54][2022-02-23T01:55:12]i000: Initializing version variable 'DetectedPowerToysVersion' to value '<IP_ADDRESS>'
[4564:5B54][2022-02-23T01:55:12]i000: Initializing version variable 'TargetPowerToysVersion' to value '0.55.1'
[4564:5B54][2022-02-23T01:55:12]i000: Initializing version variable 'DetectedWindowsBuildNumber' to value '0'
[4564:5B54][2022-02-23T01:55:12]i009: Command Line: '-burn.clean.room=C:\Users\geast\Downloads\PowerToysSetup-0.55.1-x64.exe -burn.filehandle.attached=572 -burn.filehandle.self=628'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\geast\Downloads\PowerToysSetup-0.55.1-x64.exe'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\geast\Downloads'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\geast\AppData\Local\Temp\PowerToys_(Preview)x64_20220223015512.log'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'WixBundleName' to value 'PowerToys (Preview) x64'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'
[4564:377C][2022-02-23T01:55:12]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[4564:377C][2022-02-23T01:55:12]i000: Setting version variable 'WixBundleFileVersion' to value '<IP_ADDRESS>'
[4564:5B54][2022-02-23T01:55:12]i100: Detect begin, 4 packages
[4564:5B54][2022-02-23T01:55:12]i000: Setting version variable 'DetectedPowerToysVersion' to value '<IP_ADDRESS>'
[4564:5B54][2022-02-23T01:55:12]i000: Setting string variable 'DetectedWindowsBuildNumber' to value '22000'
[4564:5B54][2022-02-23T01:55:12]i000: File search: wfs787C47E874A1A76AD0DF461B72DB8F90, did not find path: C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\5.0.13\System.Xaml.dll
[4564:5B54][2022-02-23T01:55:12]i000: Setting numeric variable 'HasDotnet5013' to value 0
[4564:5B54][2022-02-23T01:55:12]i000: Setting numeric variable 'HasDotnet3122' to value 1
[4564:5B54][2022-02-23T01:55:12]i000: Registry key not found. Key = 'Software\Microsoft\EdgeUpdate\Clients{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}'
[4564:5B54][2022-02-23T01:55:12]i000: Setting numeric variable 'HasWebView2PerUser' to value 0
[4564:5B54][2022-02-23T01:55:12]i000: Setting numeric variable 'HasWebView2PerMachine' to value 1
[4564:5B54][2022-02-23T01:55:12]i102: Detected related bundle: {74fe7fce-0af1-46f9-b084-314c7770c151}, type: Upgrade, scope: PerMachine, version: <IP_ADDRESS>, operation: MajorUpgrade
[4564:5B54][2022-02-23T01:55:12]i052: Condition 'HasDotnet3122' evaluates to true.
[4564:5B54][2022-02-23T01:55:12]i052: Condition 'HasDotnet5013' evaluates to false.
[4564:5B54][2022-02-23T01:55:12]i052: Condition 'HasWebView2PerMachine OR HasWebView2PerUser' evaluates to true.
[4564:5B54][2022-02-23T01:55:12]i103: Detected related package: {1EEAC01B-68E4-41E8-AE8C-33A2D149637C}, scope: PerMachine, version: <IP_ADDRESS>, language: 0 operation: MajorUpgrade
[4564:5B54][2022-02-23T01:55:12]i103: Detected related package: {1EEAC01B-68E4-41E8-AE8C-33A2D149637C}, scope: PerMachine, version: <IP_ADDRESS>, language: 0 operation: MajorUpgrade
[4564:5B54][2022-02-23T01:55:12]i101: Detected package: DotnetRuntime, state: Present, cached: None
[4564:5B54][2022-02-23T01:55:12]i101: Detected package: DotnetRuntime5, state: Absent, cached: None
[4564:5B54][2022-02-23T01:55:12]i101: Detected package: WebView2, state: Present, cached: None
[4564:5B54][2022-02-23T01:55:12]i101: Detected package: PowerToysSetup_0.55.1_x64.msi, state: Absent, cached: Complete
[4564:5B54][2022-02-23T01:55:12]i052: Condition 'TargetPowerToysVersion >= DetectedPowerToysVersion OR WixBundleInstalled' evaluates to true.
[4564:5B54][2022-02-23T01:55:12]i052: Condition 'DetectedWindowsBuildNumber >= 18362 OR WixBundleInstalled' evaluates to true.
[4564:5B54][2022-02-23T01:55:12]i199: Detect complete, result: 0x0
[4564:377C][2022-02-23T01:55:14]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[4564:5B54][2022-02-23T01:55:14]i200: Plan begin, 4 packages, action: Install
[4564:5B54][2022-02-23T01:55:14]w321: Skipping dependency registration on package with no dependency providers: DotnetRuntime
[4564:5B54][2022-02-23T01:55:14]w321: Skipping dependency registration on package with no dependency providers: DotnetRuntime5
[4564:5B54][2022-02-23T01:55:14]i000: Setting string variable 'WixBundleLog_DotnetRuntime5' to value 'C:\Users\geast\AppData\Local\Temp\PowerToys(Preview)x64_20220223015512_000_DotnetRuntime5.log'
[4564:5B54][2022-02-23T01:55:14]w321: Skipping dependency registration on package with no dependency providers: WebView2
[4564:5B54][2022-02-23T01:55:14]i000: Setting string variable 'WixBundleRollbackLog_PowerToysSetup_0.55.1_x64.msi' to value 'C:\Users\geast\AppData\Local\Temp\PowerToys(Preview)x64_20220223015512_001_PowerToysSetup_0.55.1_x64.msi_rollback.log'
[4564:5B54][2022-02-23T01:55:14]i000: Setting string variable 'WixBundleLog_PowerToysSetup_0.55.1_x64.msi' to value 'C:\Users\geast\AppData\Local\Temp\PowerToys(Preview)_x64_20220223015512_001_PowerToysSetup_0.55.1_x64.msi.log'
[4564:5B54][2022-02-23T01:55:14]i201: Planned package: DotnetRuntime, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[4564:5B54][2022-02-23T01:55:14]i201: Planned package: DotnetRuntime5, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: Yes, uncache: No, dependency: None
[4564:5B54][2022-02-23T01:55:14]i201: Planned package: WebView2, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[4564:5B54][2022-02-23T01:55:14]i201: Planned package: PowerToysSetup_0.55.1_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: No, uncache: No, dependency: Register
[4564:5B54][2022-02-23T01:55:14]i207: Planned related bundle: {74fe7fce-0af1-46f9-b084-314c7770c151}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[4564:5B54][2022-02-23T01:55:14]i299: Plan complete, result: 0x0
[4564:5B54][2022-02-23T01:55:14]i300: Apply begin
[4564:5B54][2022-02-23T01:55:14]i010: Launching elevated engine process.
[4564:5B54][2022-02-23T01:55:16]i011: Launched elevated engine process.
[4564:5B54][2022-02-23T01:55:16]i012: Connected to elevated engine.
[1258:2DA4][2022-02-23T01:55:16]i358: Pausing automatic updates.
[1258:2DA4][2022-02-23T01:55:16]i359: Paused automatic updates.
[1258:2DA4][2022-02-23T01:55:16]i360: Creating a system restore point.
[1258:2DA4][2022-02-23T01:55:16]i361: Created a system restore point.
[1258:2DA4][2022-02-23T01:55:16]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, options: 0x7, disable resume: No
[1258:2DA4][2022-02-23T01:55:16]i000: Caching bundle from: 'C:\Users\geast\AppData\Local\Temp{7304F4FA-42D2-49F3-BE60-E548540E1BC8}.be\PowerToysSetup-0.55.1-x64.exe' to: 'C:\ProgramData\Package Cache{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}\PowerToysSetup-0.55.1-x64.exe'
[1258:2DA4][2022-02-23T01:55:16]i320: Registering bundle dependency provider: {a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, version: <IP_ADDRESS>
[1258:2DA4][2022-02-23T01:55:16]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, resume: Active, restart initiated: No, disable resume: No
[4564:1240][2022-02-23T01:55:16]w343: Prompt for source of package: DotnetRuntime5, payload: DotnetRuntime5, path: C:\Users\geast\Downloads\windowsdesktop-runtime-5.0.13-win-x64.exe
[4564:1240][2022-02-23T01:55:16]i338: Acquiring package: DotnetRuntime5, payload: DotnetRuntime5, download from: https://download.visualstudio.microsoft.com/download/pr/2bfb80f2-b8f2-44b0-90c1-d3c8c1c8eac8/409dd3d3367feeeda048f4ff34b32e82/windowsdesktop-runtime-5.0.13-win-x64.exe
[1258:5BA0][2022-02-23T01:55:17]i305: Verified acquired payload: DotnetRuntime5 at path: C:\ProgramData\Package Cache.unverified\DotnetRuntime5, moving to: C:\ProgramData\Package Cache\EB5506CEBB3DD1CEC78F7F8131F87A2C5F665B40\windowsdesktop-runtime-5.0.13-win-x64.exe.
[1258:5BA0][2022-02-23T01:55:17]i304: Verified existing payload: PowerToysSetup_0.55.1_x64.msi at path: C:\ProgramData\Package Cache{F8E2F1CF-E4EE-498B-BC46-43943A71C86C}v0.55.1\PowerToysSetup-0.55.1-x64.msi.
[1258:2DA4][2022-02-23T01:55:17]i301: Applying execute package: DotnetRuntime5, action: Install, path: C:\ProgramData\Package Cache\EB5506CEBB3DD1CEC78F7F8131F87A2C5F665B40\windowsdesktop-runtime-5.0.13-win-x64.exe, arguments: '"C:\ProgramData\Package Cache\EB5506CEBB3DD1CEC78F7F8131F87A2C5F665B40\windowsdesktop-runtime-5.0.13-win-x64.exe" /install /quiet'
[1258:2DA4][2022-02-23T01:55:18]e000: Error 0x80070666: Process returned error: 0x666
[1258:2DA4][2022-02-23T01:55:18]e000: Error 0x80070666: Failed to execute EXE package.
[4564:5B54][2022-02-23T01:55:18]e000: Error 0x80070666: Failed to configure per-machine EXE package.
[4564:5B54][2022-02-23T01:55:18]i319: Applied execute package: DotnetRuntime5, result: 0x80070666, restart: None
[4564:5B54][2022-02-23T01:55:18]e000: Error 0x80070666: Failed to execute EXE package.
[1258:2DA4][2022-02-23T01:55:18]i351: Removing cached package: DotnetRuntime5, from path: C:\ProgramData\Package Cache\EB5506CEBB3DD1CEC78F7F8131F87A2C5F665B40
[1258:2DA4][2022-02-23T01:55:18]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, resume: None, restart: None, disable resume: No
[1258:2DA4][2022-02-23T01:55:18]i330: Removed bundle dependency provider: {a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}
[1258:2DA4][2022-02-23T01:55:18]i352: Removing cached bundle: {a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, from path: C:\ProgramData\Package Cache{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}
[1258:2DA4][2022-02-23T01:55:18]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{a92e2f2f-f4e7-4ce9-b3ba-2c56acefde95}, resume: None, restart initiated: No, disable resume: No
[4564:5B54][2022-02-23T01:55:18]i399: Apply complete, result: 0x80070666, restart: None, ba requested restart:  No

✔ Expected Behavior
Complete update procedure successfully
❌ Actual Behavior
App is stuck and no longer able to update to newer versions
Other Software
No response

I managed to fix it, "Another version of this product is already installed" refers to the Windows Desktop Runtime, not PowerToys which is what confused me. A recent windows update updated the Windows Desktop Runtime to version 5.0.14, Powertoys was trying to install 5.0.13. After uninstalling the 5.0.14 version, the update goes through as expected. @16520

Fixed with 0.55.2


Import module error

After installing the kan_gpt using pip install kan_gpt on colab.
I got this error when I try to import the library and the model. I copied it from the GitHub readme.

I have the same issue.

I have the same issue.

Have you been able to solve it??
I think it's suppose to be from kan_gpt.kan_gpt.effificent_kan.model import GPT .
Change it to this and try it

Hi all, thank you for reporting this! I have made the fix and pushed it on the new 0.4.0 release


Detect the format of the config and try loading it

<!-- Make sure you have read http://napalm.readthedocs.io/en/latest/contributing/index.html --!>

@dbarrosop @ktbyers I made some tests, this seems to work fine. Please let me know your suggestions / improvements etc.

Coverage decreased (-1.4%) to 83.883% when pulling a563339ff289c393d66acd8e5dccdfda60b71984 on mirceaulinic:cfg-fmt into 26c628b0ab7ed7d7636a0697ea6f0f626e428565 on napalm-automation:develop.

Could you add tests? I think this is one of those methods that deserves it :) Other than that LGTM!


[SPARK-43013][PYTHON] Migrate ValueError from DataFrame into PySparkValueError.

What changes were proposed in this pull request?
This PR proposes to migrate ValueError from python/pyspark/sql/dataframe.py into error classes.
Why are the changes needed?
To leverage the PySpark error framework.
Does this PR introduce any user-facing change?
No, it's about the error message improvement. No API changes.
How was this patch tested?
The existing CI should pass.

Merged to master.


Add isFile function

I think we need to have a difference between file_exists and is_file

Colsed by sending PR to main Symfony directory as requested https://github.com/symfony/symfony/pull/21622


build(snap): Upgrade kong, redis, consul, vault

Signed-off-by: Mengyi Wang<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Using Redis 7.0.5 and 7.0.0 both result in the following error:
Oct 24 14:47:13 fv-az96-423 edgexfoundry.redis[4141]: *** FATAL CONFIG FILE ERROR (Redis 7.0.5) ***

This needs further investigation; maybe there are new config files that the snap isn't packing.
For now, we can proceed with v6.2.7 as it has the latest CVE fixes that aren't affecting v7 features.

Codecov Report

Merging #4210 (865dd42) into main (2325198) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #4210   +/-   ##
=======================================
  Coverage   43.28%   43.28%
=======================================
  Files         125      125
  Lines       11106    11106
=======================================
  Hits         4807     4807
  Misses       5887     5887
  Partials      412      412

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Execute a simple echo rust test program.

This builds any tests/bin/*.rs found, which can be used for
integration tests.
A simple echo.rs test writing every stdin to stdout is added.
Because this uses poll, the poll syscall was also implemented for
the sgx and sev shims.
Signed-off-by: Harald Hoyer<EMAIL_ADDRESS>

IIRC the reason why we compile C binaries for the integration tests is because it is easy to avoid linking with crt0; the goal is to ensure the scope of the test is not accidentally widened by whatever crt0 may or may not call. From my initial read of this, it doesn't look like the builds for the Rust binaries exclude crt0.
I like the idea of testing real programs, and have no strong opinion as to whether those are included in the integration tests or if we organize them collectively in a different repository. However, this may be a good place to break some ground with another kind of end-to-end testing.
I have been thinking it'd be useful to have some kind of repo/CI setup that is able to clone the relevant repos, build the Enarx stack, and feed in WebAssembly binaries. This setup would be associated with each component that builds up our end-to-end run of a Wasm workload. This way, any time we change any component in the runtime stack, they're all tested together.
For example, a pull request made to the enarx-keepldr repo would trigger the following:

The PR would be checked out
The CI would clone the missing components (in this case, enarx-wasmldr & the enarx-test-progs repo; if the PR was originally made to enarx-wasmldr, then the missing components would be enarx-keepldr & enarx-test-progs, etc.)
The CI would build each program in the enarx-test-progs designation as a Wasm binary.
The CI would use enarx-keepldr to exec the enarx-wasmldr for each build test program.

This would also the side effect of serving as a demonstration of the gradually more complicated workloads Enarx is able to deploy.
Thoughts?

Thoughts?

Yeah, I like the end-to-end integration test. We should definitely have that.
This test serves more of a quick and lean end-to-end rust test and would show regressions with cargo test earlier in the devel cycle.


Add models for Members and Projects

Add Member and Project Schemas, and model

mongo schema

@darthvader2 Please review and then merge


Timezone error

Using office 365 in a single timezone (office runs in french on my desktop). I get An error occurred getting calendar timezone information. Error authenticating with resource.
I check my timezone settings, and they dont look out of the ordinary. Any help on this issues?

I have what i suspect is a timezone issue in Australia.  If in the morning at say 7.30am (GMT+10) i ask for "todays" appointments it tells me it cannot provide information for past appointments.  If I say the name of today ie wednesday, it reads my appointments out.


Border

Would be excellent if we had options to add a border

A border with a background/transparency level would be nice.
If the portrait is an image with no background, it can it lost amongst the UI elements.

I might take a look at this as I'd like a border as well. Will update if I have time over this weekend & next.


gzdoom: 3.3.0 -> 3.3.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/gzdoom/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 3.3.2 with grep in /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2
directory tree listing: https://gist.github.com/66372cbd8e865e89ab9749a99b308ea7

cc @Lassulus for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: gzdoom
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: gzdoom
Partial log (click to expand)
/build/source/build/gzdoom.pk3 contains 684 files (updated 684)
[100%] Built target gzdoom_pk3
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2
shrinking /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2/lib/gzdoom/gzdoom
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2/lib  /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2/bin
patching script interpreter paths in /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2
checking for references to /build in /nix/store/zv856axqy6bna0vpgramgaglz02nb8rh-gzdoom-3.3.2...

Success on aarch64-linux (full log)
Attempted: gzdoom
Partial log (click to expand)
/build/source/build/gzdoom.pk3 contains 684 files (updated 684)
[100%] Built target gzdoom_pk3
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2
shrinking /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2/lib/gzdoom/gzdoom
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2/lib  /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2/bin
patching script interpreter paths in /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2
checking for references to /build in /nix/store/vwaqc5kk5rfjq6qckwfpl02xz63d86cn-gzdoom-3.3.2...


Fix #1083 Factory supports indices

Looks good but was there a request to add this feature? Just trying to be mindful about new features.
Also, updating the documentation would be nice.

The request doesn't exist like that. But the feature was fun to add and, in fact, pretty simple to add.
The idea is to use indices to be able to provide a way to run tests on only failed instances.
But the current PR is just a first step in that objective.
Something should be added later in the suite description but an annotation listener will do the job quickly.
For sure, l'm agree about the missing documentation but it is already missing for the data provider feature.
I'm propose we create an issue in order to add the doc on indices for both elements.

Sounds good, thanks for the clarifications.


[cs] Adjust responses to follow style guide

This is rather a big change - it adjusts all responses to follow the official response style guide. For English this was done in #1040 - this PR aligns (or tries to) the Czech language with that.
Although it seems detrimental by making the assistant less chatty, it improves maintainability and removes the need for adjusting for clumsy responses (with bad grammatical cases/tenses), such as those that can be seen in the removed test cases.

@halecivo I resolved the conflicts after the two previous PRs have been merged. PTAL when convenient and let me know if there's anything to discuss or if it is okay now.

Sorry for the delay, I was on vacation and dared to review only simple PRs from phone :)
Thanks for the job done.


Page request for just video views of a room

I forked the example app accompanied by flutter  and i did get it to work on my end , however remote users can see published room tracks using the example app, I would like to request for that feature request.

You can use components to quickly implement a video views page
https://github.com/livekit/components-flutter


Consider putting plugins in a different location

At present, all the plugins live in the same directory as the irods_s3_api binary. We should consider changing how plugins are loaded so that they can live in a separate directory. This will allow us to put plugins somewhere like ${LIBDIR}/irods/clients/s3_api and the main executable in ${BINDIR}.

Just a note:  I temporarily removed the plugin architecture from the project while we are transitioning away from coroutines.  This will be restored later.


Harden replication tests

@mambocab to review

Sorry about the sleep, but nothing I could do about it. There is no programmatic way to check for trace completion effectively.

LGTM. Can you file a PYTHON ticket for the sleep you need?

...No? There is no way to know how long to sleep. So it's not something the driver can add.

buh, sorry -- I meant adding information about when traces were completed. Adam explained over on the PYTHON Jira that that would require a server change and why, though. :+1:


How does StrumNote.hx work?

What is your question?
I was wondering how does StrumNote.hx work. Pretty self explain.

it's the source file that manages the strum notes animations and movements

it's the source file that manages the strum notes animations and movements

and directions too

it's the source file that manages the strum notes animations and movements

and directions too

Thx


Improve clone

In this PR we implement the Clone::clone_from method, this way it is faster to clone a RoaringBit/Treemap by reusing a previous map if possible.

bors merge


nixos/zapret: extra features

Added some of the requested by users features:

[x] "Full" http processing mode.

[x] Tested.

[x] Udp support.

[x] Tested.

[x] ipv6 support.

[x] Tested ipv4 only.

They need proper testing by users as I can't get myself a consistent results either because of incomplete changes or network specifics.
@Nishimara I'd like to hear your thoughts on this.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I added examples to new options. It is ready for now. I'll try to implement the requested ipv6 support as soon as I get access to it.

I'm really interested in ipv6 feature. How can I help to test this? In case of implementation I think we can do something like this:
(lib.mkIf cfg.configureFirewall {
  networking.firewall.extraCommands =
    let
      httpParams = lib.optionalString (
        cfg.httpMode == "first"
      ) "-m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:6";

      udpPorts = lib.concatStringsSep "," cfg.udpPorts;
      iptablesCommands = [ "iptables" ] ++ lib.optional (cfg.ipv6) "ip6tables";
      mkIptablesRules =
        command:
        ''
          ${command} -t mangle -I POSTROUTING -p tcp --dport 443 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:6 -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        ''
        + lib.optionalString (cfg.httpSupport) ''
          ${command} -t mangle -I POSTROUTING -p tcp --dport 80 ${httpParams} -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        ''
        + lib.optionalString (cfg.udpSupport) ''
          ${command} -t mangle -A POSTROUTING -p udp -m multiport --dports ${udpPorts} -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        '';
    in
    lib.concatMapStrings mkIptablesRules iptablesCommands;
})

I'm really interested in ipv6 feature. How can I help to test this? In case of implementation I think we can do something like this:
(lib.mkIf cfg.configureFirewall {
  networking.firewall.extraCommands =
    let
      httpParams = lib.optionalString (
        cfg.httpMode == "first"
      ) "-m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:6";

      udpPorts = lib.concatStringsSep "," cfg.udpPorts;
      iptablesCommands = [ "iptables" ] ++ lib.optional (cfg.ipv6) "ip6tables";
      mkIptablesRules =
        command:
        ''
          ${command} -t mangle -I POSTROUTING -p tcp --dport 443 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:6 -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        ''
        + lib.optionalString (cfg.httpSupport) ''
          ${command} -t mangle -I POSTROUTING -p tcp --dport 80 ${httpParams} -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        ''
        + lib.optionalString (cfg.udpSupport) ''
          ${command} -t mangle -A POSTROUTING -p udp -m multiport --dports ${udpPorts} -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass
        '';
    in
    lib.concatMapStrings mkIptablesRules iptablesCommands;
})

Is replacing iptables with ip6tables is the only requirement for zapret? If so, this should be easy. I'll try to draft it within a day, could you test it, please? I'll ping you on GH.

Try looking into ip46tables. Firewall have this hack to execute commands with both iptables and ip6tables.

Is replacing iptables with ip6tables is the only requirement for zapret? If so, this should be easy. I'll try to draft it within a day, could you test it, please? I'll ping you on GH.
Not a replacement, but an addition of exactly the same rule using ip6tables. Sure I can test this, but do not know exactly how) Any guides are welcome here

@voronind-com
Maybe something like this?
let
  ...
  tables = if cfg.ipv6Support then "ip46tables" else "iptables";
in
  ...
  networking.firewall.extraCommands = "${tables} -t mangle -I POSTROUTING -p tcp --dport 443 -m connbytes --connbytes-dir=original --connbytes-mode=packets --connbytes 1:6 -m mark ! --mark 0x40000000/0x40000000 -j NFQUEUE --queue-num ${qnum} --queue-bypass";

Thanks. I'm uber tired today, I'll update this pr tomorrow morning. Also will help roman3pm with testing.

Sadly I have no ip46tables in my system, so I guess it is not included by default. Referencing another pkg also might not be a good idea. I'm gonna do additional rule with ip6tables now.

@roman3pm It's ready for testing. Actually super easy. All you need to do is add this to your nixos config:
disabledModules = [ "services/networking/zapret.nix" ];

Then copy-paste https://github.com/NixOS/nixpkgs/blob/2cde9592dfba6ea3a95d6cece22a328927908864/nixos/modules/services/networking/zapret.nix and import it as a regular module. Switch and test.

Fixed a typo. Works fine with ip46tables on ipv4 network. Marking as ready.

Hello @Nishimara, @voronind-com . I wanted to add --ipset option. I created https://github.com/NixOS/nixpkgs/pull/358168, could you please check it out

Hello @Nishimara, @voronind-com . I wanted to add --ipset option. I created #358168, could you please review it

Hello! I see. I'll research that option a bit and sure will add it in this PR, okay? Or do you want to author on it?

sure, add it to this pr, i don`t need to author on it. Did you think about how a QUIC parameters could be added?

Not yet. I still want to iteratively add small features.

As for --ipset option there's also--ipset-exclude. We already occupied the whitelist and blacklist option names. So we have a few options:

Theoretically we could detect IP addresses in them and move to a different list. Tho I have no idea how to implement that, but I could try.
Create filterMode option with values domain and ip. But this disallows using both. I'm unsure whether Zapret even supports using both at the same time.
Straightforward creation of a new pair: ipwhitelist and ipblacklist or something like that. This would theoretically allow the usage of both filters.
???

@Nishimara what do you think?

I think it's better to move it into next PR, as soon as this merged. Otherwise we block well-tested features implemented here from going to unstable.


Cache some api calls

We might want to cache for a given amount of time calls to certain APIs, to prevent our request limits.

Brilliant idea


story for pulling in remote origin topic branch that already exists into local repo

VSCode Version: 0.10.11
OS Version: win10 10586.164

Steps to Reproduce:

open folder containing clone of remote origin master

click on git branch status area in bottom left corner, or enter ctrl+p or f1+>Git: Checkout, and enter name of remote origin branch you want to local copy to reference.  the git ouput window shows "git checkout -q -b someTopicBranch" and "git fetch" were executed.

folder doesn't contain copy of remote origin topic branch so from command line enter "git.exe config -l --local" where you'll see that branch.someTopicBranch.remote/.merge entries are not present

from command line enter "git branch -u origin/someTopicBranch" or "git branch --set-upstream-to=someTopicBranch" to update local config to contain branch.someTopicBranch.remote/.merge entries

from vscode you can now use git | ... | pull == "git pull" to retrieve the contents of the remote origin someTopicBranch that already existed

My thinking is that steps 3 thru 5 should be automated for you in case where you are not looking to create new topic branch and optionally later push it into remote origin but rather create local repo topic branch into which you sync the details of remote origin copy of topic branch that already exists.

Duplicate of #3385


Bumped smart_auth plugin version to 2.0.0:

This update fixes two important issues:

Fixed RECEIVER_EXPORTED exception in android SDK 34
Fix "Namespace not specified" error when upgrading to AGP 8.0

I have raised an issue for the same https://github.com/Tkko/Flutter_Pinput/issues/166
@Tkko please review


Pdf content(text and image) is blurred in generated pdf document using jsPDF

I have a div that should be converted to PDF using jsPDF. Problem is that text and image in the generated PDF document is blurry. Is there a way to fix this ?
HTML
<button type="button" (click)="downloadPdf()">Convert to PDF

This text will be converted to canvas, then to image and then to PDF

    This text will not be included

Typescript
public downloadPdf() {
const elementToPrint = document.getElementById('div1'); //The html element to become a pdf
const pdf = new jspdf('p', 'pt', 'a4');
pdf.addHTML(elementToPrint, () => {
pdf.save('certificate.pdf');
});
}

certificate (68).pdf

Please find the attached pdf document

addHTML is deprecated. Use html instead.


Getting started with JavaScript Events

Proposed title of article
Getting started with JavaScript Events
Introduction paragraph (2-3 paragraphs):
A JavaScript events are operations that run when a user interacts with a given webpage. Events can be used to used to provide a dynamic interaction with a webpage by making the interaction  seamless and enjoyable. Alerts, form validation, window pop ups are all forms of events that facilitate user interaction with a webpage.
When an event occurs, we can use JavaScript event handler to detect the event and preform a specific task specified by the event. Events can be classified into Mouse events, keyboard events and events that are triggered by loading a webpage. Conventionally, most events are named according to their classifications.
In this article, the reader will understand how to JavaScript listen to events, pass them to event handlers and specify tasks to be performed depending on specific events.
Key takeaways:

How to listen to JavaScript events
Handling JavaScript events.
Types of JavaScript events

References:
Please list links to any published content/research that you intend to use to support/guide this article.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Hi, @bastian-zab.
Great topic suggestion. I'm sure our readers will find your guide to JavaScript Events very useful.
Make sure to cover mouse and load events in detail to differentiate your article from our existing Keyboard Events in JavaScript article.
Topic approved ✔

@bastian-zab
Just pinging you on this topic form - as were trying to make some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date.

@bastian-zab
Just pinging you on this topic form - as I'm making some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date.


set workingdirectory instead of environment

Environment=PYTHONPATH=/opt/oulib/islandoraq-worker

should be
WorkingDirectory=/opt/oulib/islandoraq-worker

closed by commit e0e70ce


RFC CycloneDX IANA media type registration

Suggest we register official media types with IANA.
Use cases include API end points that can return SBOMs.
This could either be just to communicate to consumers the format provided. Or allow specifying which SBOM format is desired during the request.
Suggested media types are application/cyclonedx+xml and application/cyclonedx+json.
Although I need to re-read the relevant RFCs for any gotchas/requirements.

Related to OPSAWG thread that references registering mime types for CycloneDX (and other formats) for use with .well-known.
<EMAIL_ADDRESS>

Related to OPSAWG thread that references registering mime types for CycloneDX (and other formats) for use with .well-known.
<EMAIL_ADDRESS>

I think the media types will need to be something like application/vnd.cyclonedx+xml and application/vnd.cyclonedx+json.
To avoid the vnd prefix the standard needs to be published as an IETF RFC. And IMHO that would just cause too much friction.

I think the media types will need to be something like application/vnd.cyclonedx+xml and application/vnd.cyclonedx+json.
To avoid the vnd prefix the standard needs to be published as an IETF RFC. And IMHO that would just cause too much friction.

IANA registrations have been submitted for application/vnd.cyclonedx+xml and application/vnd.cyclonedx+json

IANA registrations have been submitted for application/vnd.cyclonedx+xml and application/vnd.cyclonedx+json

IANA media types have been assigned.
https://www.iana.org/assignments/media-types/application/vnd.cyclonedx+xml
https://www.iana.org/assignments/media-types/application/vnd.cyclonedx+json

IANA media types have been assigned.
https://www.iana.org/assignments/media-types/application/vnd.cyclonedx+xml
https://www.iana.org/assignments/media-types/application/vnd.cyclonedx+json

Absolutely fantastic Patrick.

Absolutely fantastic Patrick.


bootstrap_pex_env not fully bootstrapping

Hello friends,
I have a weird issue that I'm trying to track down. I'm fiddling with uwsgi and pex, and thus the bootstrapping functions and I've run into something I can't quite figure out.
Hoping @kwlzn can help out, since I borrowed a lot from his pyuwsgi stuff.
Here's the gist: I've got a flask app that I'm decorating with some attributes (mostly for configs). When I enter the pex interpreter alone, I can access all of the attributes I set, but when I bootstrap the pex environment I am missing the attributes that I add to the app object.
Here's an example:
linux /export/content/lid/apps/cosmos/i001/bin ❯❯❯ ./cosmos.pex
Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from cosmos.core import app
>>> app.secret_key
'foo'
>>> app
<Flask 'cosmos.core'>

Whereas, if I bootstrap the pex environment, I get nothing:
linux /export/content/lid/apps/cosmos/i001/bin ❯❯❯ python2.6
Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path.insert(0, '/export/content/lid/apps/cosmos/i001/bin/cosmos.pex')
>>> sys.path.insert(0, '/export/content/lid/apps/cosmos/i001/bin/cosmos.pex/.bootstrap')
>>> from _pex.pex_bootstrapper import bootstrap_pex_env
>>> bootstrap_pex_env('/export/content/lid/apps/cosmos/i001/bin/cosmos.pex')
>>> from cosmos.core import app
>>> app.secret_key
>>> app
<Flask 'cosmos.core'>

Note the lack of a secret_key attribute in the second example.
So, I think that there's something that is not happening during bootstrap that is happening during regular interpreter initialization, though I have no idea what, since the .bootstrap code is practically identical (__main__.py just calls the same bootstrap function that I call directly).
I'm using uwsgi with --import bootstrap.py, co-opted from @kwlzn's project, but as you can see above, it's reproducible in a regular interpreter as well. Tested on python2.6 and python2.7.
Any ideas?

P.S.
It should be noted that this only affects attributes set by side effect, anything I explicitly set shows up fine.
For example:
my_app = Flask(__name__)

def side_effect(app):
    app.foo = 'bar'

side_effect(my_app)

app = my_app

^ does not work, but
my_app = Flask(__name__)
my_app.foo = 'bar'
app = my_app

^ does work

So, it would appear from my digging around that bootstrapping pex environments ignores entry_points
Check it out:
linux /export/content/lid/apps/cosmos/i001/bin ❯❯❯ ./cosmos.pex
Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> import pkg_resources
>>> [entry_point for entry_point in pkg_resources.iter_entry_points('app_def.plugins')]
[EntryPoint.parse('flask-v10 = linkedin.web.cfg2:FlaskV10'), EntryPoint.parse('flask-v9 = linkedin.web.cfg2:FlaskV9'), EntryPoint.parse('flask-v2 = linkedin.web.cfg2:FlaskV2'), EntryPoint.parse('flask-v8 = linkedin.web.cfg2:FlaskV8'), EntryPoint.parse('flask-debugtoolbar = linkedin.web.cfg2:FlaskDebugToolbar'), EntryPoint.parse('gunicorn = linkedin.web.cfg2:Gunicorn'), EntryPoint.parse('flask-sqlalchemy = linkedin.flask_sqlalchemy.cfg2:FlaskSQLAlchemy')]
>>>

vs.
linux /export/content/lid/apps/cosmos/i001/bin ❯❯❯ python2.6
Python 2.6.6 (r266:84292, Oct 12 2012, 14:23:48)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path.insert(0, '/export/content/lid/apps/cosmos/i001/bin/cosmos.pex')
>>> sys.path.insert(0, '/export/content/lid/apps/cosmos/i001/bin/cosmos.pex/.bootstrap')
>>> from _pex.pex_bootstrapper import bootstrap_pex_env
>>> bootstrap_pex_env('/export/content/lid/apps/cosmos/i001/bin/cosmos.pex')
>>> import pkg_resources
>>> [entry_point for entry_point in pkg_resources.iter_entry_points('app_def.plugins')]
[]
>>>```

Hah. So after digging around in pkg_resources guts for the evening I managed to find an odd fix:
reload(pkg_resources)
Cheers :beers:


size_tuple vs extents

Back already(!)
My second trivial program is
#include <linear_algebra.hpp>
#include <iostream>
#include <tuple>

int main()
{
        STD_LA::fs_matrix<double, 3, 3> R{{1, 2, 3}, {4, 5, 6}, {7, 8, 9}};
        STD_LA::fs_vector<double, 3> v{{1, 2, 3}};
        auto x = R * v;
        std::cout << R(1,2) << '\n';
        std::cout << x(2) << '\n';
        std::cout << std::get<0>(R.size()) << '\n';
}

The aim is simply, given a matrix R, how do I find out the number of columns / rows.
According to P1385R7.md
    using size_tuple      = tuple<size_type, size_type>;
    constexpr size_tuple    size() const noexcept;

so I would expect R.size() to return a tuple<size_type,size_type>, and get<0> to return the first size_type.
This fails to compile with g++ 10.3.0:
c++  -O2 -fPIE -g -Werror -std=c++20     -I/usr/src/local/mdspan/include -I/usr/src/local/wg21/include  -c    wg21test.cc
wg21test.cc: In function ‘int main()’:
wg21test.cc:12:35: error: no matching function for call to ‘get<0>(std::math::matrix<std::math::fs_matrix_engine<double, 3, 3>, std::math::matrix_operation_traits>::index_tuple)’
   12 |  std::cout << std::get<0>(R.size()) << '\n';
      |                                   ^
...
/usr/src/local/mdspan/include/experimental/__p0009_bits/extents.hpp:206:3: note: candidate: ‘template<class IndexType>  requires  is_convertible_v<IndexType, std::experimental::extents<Extents ...>::index_type> constexpr std::experimental::extents<Extents>::extents(const std::array<IndexType, std::experimental::extents<Extents>::rank_dynamic()>&) [with IndexType = IndexType; long int ...Extents = {3, 3}]’
  206 |   extents(std::array<IndexType, rank_dynamic()> const& dyn) noexcept
      |   ^~~~~~~

As per #68, this is head wg21, and now 51b291a1265bf mdspan.
Have I maybe hit the R5 Feedback to do item
+ Use `extents` instead of `size_tuple`.

or am I missing something?

Yes, I think you will find that is out of date.  Most of the recent development has been taking places on the r7y branch with a view to being in line with the changes in the upcoming revision 7 of the specification: https://github.com/BobSteagall/wg21/tree/r7y
Please try against that branch and see if that improves things, just note that this branch is under development until the next paper revision is released.

Thanks again!
cd /usr/src/local/wg21
git checkout r7y

did the trick, with the updated trivial program
#include <matrix.hpp>
#include <iostream>

int main()
{
        STD_LA::fixed_size_matrix<double, 3, 3> R{{1, 2, 3}, {4, 5, 6}, {7, 8, 9}};
        STD_LA::fixed_size_column_vector<double, 3> v{1, 2, 3};
        auto x = R * v;
        std::cout << R(1,2) << '\n';
        std::cout << x(2) << '\n';
        std::cout << R.rows() << 'x' << R.columns() << '\n';
}

Might it be worth a note say in README.md to say that to try this out, one needs the r7y branch of this project, and the 9d1acac54305 commit of mdspan?

Yes, I can certainly update the readme to point to the r7y branch.  As for the 9d1acac54305 commit of mdspan, that is the revision hardcoded in the FetchContent call here on master: https://github.com/BobSteagall/wg21/blob/4b39067496f3a6401f6c76e965703de20c6622d7/CMakeLists.txt#L24
When you encountered the error with MDSpan were you attempting to build the r7 branch?  I see that required change to the CMakeList.txt has not been back merged onto that branch...  I've opened the following issue to fix this properly on master and back merge the changes and should be able to look at this in the next day or so: https://github.com/BobSteagall/wg21/issues/70

As explained in #68, I just checked out the 2 git repositories, and compiled the tiny program. Since then you have told me which branch and commit I should have checked out. These are header-only libraries, so no running of cmake needed. I just used -I to point the compiler to the relevant include directories. (For your amusement, as you asked for operating system / architecture, this is NetBSD/amd64 (!))

Oh wow, you are the first person to my knowledge to have built this on NetBSD/amd64 :)
Ah right, I had not taken in that you manually fetched both repositories.  If you had built the wg21 repo via CMake it would have fetched the correct MDSpan in the build directory, and then if you and ran the install step then it would have installed the correct MDspan and WG21 side by side.  This could have been achieve as such:
git clone git@github.com:BobSteagall/wg21.git
cd wg21
mkdir build
cd build

cmake ../ [-G <generator>] [configuration options] -DCMAKE_INSTALL_PREFIX=/usr/src/local/
cmake --build . --target install

Ok thanks, that's helpful for my understanding.

Closing for now as I think this is resolved, please reopen if you have further queries.


Fix/Add CABundle handling for flatcar

How to categorize this PR?

/area os
/kind bug
What this PR does / why we need it:
The CABundle from cloudprofile.spec.caBundle and shoot.spec.provider.workers.caBundle is currently not working for flatcar linux.
This PR adds the handling for flatcar to update-local-ca-certificates.sh (Based on the description of flatcar: https://www.flatcar.org/docs/latest/setup/security/adding-certificate-authorities/)
I decided against putting the cert file directly to /etc/ssl/certs/ROOTcerts.pem via OperatingSystemConfig, as this is already present in /var/lib/ca-certificates-local/ROOTcerts.crt. In my opinion, the same applies to  /etc/pki/trust/anchors/ROOTcerts.pem which contains also the same and could be copied within the shell script.
I dont understeand the reason for mkdir -p "{{ .pathLocalSSLCerts }}", as this is should be always there because of the files from OperatingSystemConfig. I cant check with the linked Issue (https://github.com/gardenlinux/gardenlinux/issues/1490) as this is not public accessible.
https://github.com/gardener/gardener/blob/b4042f7fcf05978d2d81920e5d54c4044156c3a9/pkg/component/extensions/operatingsystemconfig/original/components/rootcertificates/templates/scripts/update-local-ca-certificates.tpl.sh#L10
Special notes for your reviewer:
I tested it on our environmet with flatcar version 3815.2.3.
Release note:

Fix CABundle from `cloudprofile.spec.caBundle` and `shoot.spec.provider.workers.caBundle` handling for flatcar

I was not expecting to see OS specific code in gardener main repo, but seems to have been already introduced with the /etc/debian_version file.
Code wise looks good to me, currently I do not have flat car environment at hand, so I have not tested the change.
/lgtm

I was not expecting to see OS specific code in gardener main repo, but seems to have been already introduced with the /etc/debian_version file.

I agree, I was wondering about the same and then found the Debian snippet. I think we should move this into OS extensions eventually, but for now it seems to be more pragmatic to just fix it here. We don't have a good way for OS extensions to modify this other than registering a webhook on the reconcile OperatingSystemConfig. This requires more work since OS extensions don't have webhooks today.

This requires more work since OS extensions don't have webhooks today.

But it is in the making, at least for the Garden Linux extension...

Okay @MrBatschner, that's cool. Would you still be fine to proceed with the proposed changes here and go down the webhook path later in the other OS extensions (Flatcar, etc.) as well?

/cc @MrBatschner
@dergeberl Should we cherry-pick this?

Okay @MrBatschner, that's cool. Would you still be fine to proceed with the proposed changes here and go down the webhook path later in the other OS extensions (Flatcar, etc.) as well?

I am not having a strong opinion here. The webhook thingy I linked depeneds on PR #10167 so before that got merged, nothing will change for the Garden Linux extension. However, I believe we will eventually need it in all OS extensions [1] so if you already want to pave the road for the FlatCar extension, that would be cool.
[1]: To get rid of scripts like these (1, 2) - with the recent advent of SLES15 SP6, the last of the operating systems Gardener currently supports finally comes with cgroup v2 and that stuff should be streamlined.

Okay, thanks @MrBatschner sounds good and makes sense.
@dergeberl please fix the typo so that we can get this thing merged :)

@dergeberl Should we cherry-pick this?

This would be nice!

@dergeberl please fix the typo so that we can get this thing merged :)

Fixed.

/lgtm
/approve

/cherry-pick release-v1.101

/cherry-pick release-v1.100

/cherry-pick release-v1.99


Trying to make it work with babel-preset-env

Babel-env let you determine the plugins and polyfills you need based on your targeted browser, which is really cool
https://github.com/babel/babel/tree/master/experimental/babel-preset-env
But I'm having a hard time trying to make it work with universal-import.
If I use a conventional .babelrc file like this, it works perfectly:
{
  "presets": ["es2015", "react", "stage-2"],
  "plugins": [["emotion", { "inline": true }], "universal-import"],
  "env": {
    "development": {
      "plugins": ["react-hot-loader/babel"]
    }
  }
}

But when I switch to babel-env, universal-import fails to transpile the imports:

This is my current .babelrc:
{
  "env": {
    "devClient": {
      "presets": [
        ["env", {
          "targets": { "browsers": ["android >= 4.4", "ios_saf > 9", "and_chr >= 56"] },
          "useBuiltIns": "usage"
        }],
        "react"
      ],
      "plugins": [["emotion", { "inline": true }], "universal-import", "react-hot-loader/babel"],
    },
    "devServer": {
      "presets": [
        ["env", {
          "targets": { "node": "current" }
        }],
        "react"
      ],
      "plugins": [["emotion", { "inline": true }], "universal-import"],
    }
  }
}

Any idea?

also, I see you're using emotion--have you tried their extractStatic feature? Would love to see an article about using extracStatic and this setup's capability to split stylesheets.
I assume the reason you're not using it is because you still want dynamic styles. The future I'd like to see is a glamorous all-JS api with the ability to both generate static styles (and their sheets) AND dynamic styles. And what's more, the "static styles" would in fact be based on javascript evaluated at build time--so essentially they are only semi-static in that they can't take advantage of renderTime/runTime information, but they let you combine styles via standard javascript techniques like merging objects.

When you use super presets, they do many things, which can break other plugins. In this case, they already do something for dynamic imports, and break our plugin:

The thing is... babel-env should not be using the syntax-dynamic-import plugin. That plugin is currently on stage-2 and babel-env shouldn't include any stage-x plugin. Only es2017, es2016 and es2015 presets.
I'll investigate this further tomorrow. Maybe I can use the babel-env exclude option to exclude syntax-dynamic-import (if it's really there) or switch to individual plugins until I find which one is breaking universal-import.

also, I see you're using emotion--have you tried their extractStatic feature? Would love to see an article about using extracStatic and this setup's capability to split stylesheets.

Yes. I am migrating a project from nextjs and styled-components to react-universal and emotion :)
My first step is to use emotion in inline mode and once everything is working try the switch to extractStatic to see if there's an improvement in performance. As you can see in our babel-env conf, we are not worried about IE11, although I dislike having to use css variables for dynamic styles, instead of javascript variables.

I took another look at this today.
Our babel-preset-env configuration (the one I pasted on the OP) is using these babel plugins:
Using plugins:
  check-es2015-constants {"android":"4.4","ios":"9.3"}
  transform-es2015-arrow-functions {"android":"4.4","ios":"9.3"}
  transform-es2015-block-scoped-functions {"android":"4.4","ios":"9.3"}
  transform-es2015-block-scoping {"android":"4.4","ios":"9.3"}
  transform-es2015-classes {"android":"4.4","ios":"9.3"}
  transform-es2015-computed-properties {"android":"4.4"}
  transform-es2015-destructuring {"android":"4.4","ios":"9.3"}
  transform-es2015-duplicate-keys {"android":"4.4"}
  transform-es2015-for-of {"android":"4.4","ios":"9.3"}
  transform-es2015-function-name {"android":"4.4","ios":"9.3"}
  transform-es2015-literals {"android":"4.4"}
  transform-es2015-object-super {"android":"4.4","ios":"9.3"}
  transform-es2015-parameters {"android":"4.4","ios":"9.3"}
  transform-es2015-shorthand-properties {"android":"4.4"}
  transform-es2015-spread {"android":"4.4","ios":"9.3"}
  transform-es2015-sticky-regex {"android":"4.4","ios":"9.3"}
  transform-es2015-template-literals {"android":"4.4"}
  transform-es2015-typeof-symbol {"android":"4.4"}
  transform-es2015-unicode-regex {"android":"4.4","ios":"9.3"}
  transform-regenerator {"android":"4.4","ios":"9.3"}
  transform-exponentiation-operator {"android":"4.4","ios":"9.3"}
  transform-async-to-generator {"android":"4.4","ios":"9.3"}
  syntax-trailing-function-commas {"android":"4.4","ios":"9.3"}

So there's no syntax-dynamic-import here.
After that, I realized it doesn't conflict with syntax-dynamic-import. Instead, it needs it. So adding it back with the stage-2 preset or the syntax-dynamic-import plugin did the trick.
{
  "env": {
    "devClient": {
      "presets": [
        ["env", {
          "targets": { "browsers": ["android >= 4.4", "ios_saf > 9", "and_chr >= 56"] },
          "useBuiltIns": "usage"
        }],
        "react"
      ],
      "plugins": [["emotion", { "inline": true }], "syntax-dynamic-import", "universal-import", "react-hot-loader/babel"],
    }
  }
}
// or...
{
  "env": {
    "devClient": {
      "presets": [
        ["env", {
          "targets": { "browsers": ["android >= 4.4", "ios_saf > 9", "and_chr >= 56"] },
          "useBuiltIns": "usage"
        }],
        "react",
        "stage-2"
      ],
      "plugins": [["emotion", { "inline": true }], "universal-import", "react-hot-loader/babel"],
    }
  }
}

Maybe this should be mentioned in the README?

the thing is it doesn't need it:
https://github.com/faceyspacey/universal-demo/blob/master/.babelrc#L3
Webpack 3 will automatically handle it. I think your setup may have undone it somehow. I really don't know.
At some point, I'm gonna do a PR to webpack that removes the need for as much of this stuff as possible. I have some ideas.

syntax-dynamic-import is part of stage-2:
https://babeljs.io/docs/plugins/preset-stage-2/
I've cloned the universal-demo repo and if you remove the stage-2 preset from your .babelrc, the same problem appears:

Maybe stage-2 was always there?

it was. but you can't really develop these modern babel-based apps without at least stage 2.


Create Bluehelix Cross Chain Bridge

RFP Proposal: Bluehelix
RFP Category: Cross-chain Bridge（infrastructure）
Name of Project: Bluehelix
Link to RFP: https://www.bhexchain.com/
Proposer: Dori.Zhu
Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT and APACHE2 licenses?: "YES"
Project Description
Bluehelix is the next-generation cross-chain DeFi infrastructure for decentralized assets. It is based on MPC distributed key technology, comprehensively using cryptography and blockchain technology, and completely decentralized to realize heterogeneous chain cross-chain services. Bluehelix Bridge is a decentralized cross-chain bridge based on MPC rather than smart contract deployment, encapsulation or issuance of any new assets. It supports the cross-chain circulation of arbitrary assets through cryptographically secure decentralized private key management tailored specifically for high-performance asset cross-chain financial scenarios, and fully guarantees the security of assets on the chain.
Deliverables
Please describe in details what your final deliverable for this project will be.
Bluehelix has been the largest MPC-based decentralized cross-chain bridge for supporting arbitrary assets. Bluehelix can already bridge these 7 public chains and its ecosystem assets. Bluehelix will support more popular chains. It is completely decentralized.
For better user's experience, Bluehelix has launched Bluehelix cross-chain Bridge, Bluehelix wallet(a decentralized wallet) and Hdex( a cross-chain decentralized exchange). These products will keep promoting our ecology.
In the future, Bluehelix Bridge will support more public chains and fully decentralized and securely realize asset cross-chain transactions, and provide better infrastructure services for blockchain /DeFi project ecology construction.
Development Roadmap
Please break up your development work into a clear set of milestones. You can use the milestones suggested in the RFP or create your own. This section needs to be very detailed (will vary on the project, but aim for around 2 pages for this section).
First, Bluehelix is based on MPC, a decentralized cryptography technology. It is patented in Europe and United States. Any user has a completely independent decentralized signatory address on the corresponding chain. The Bluehelix cross-chain process does not involve the exchange of any intermediate assets, nor does it issue any new/wrapped assets. We are running by consensus nodes, and core nodes are all supported by authority institutions, including SlowMist and Peck hield.
And the completion of any transaction (deposit/withdrawal) requires the generation of distributed signature and multi-party confirmation, and the processes are fully transparent and can be verified on the Chain.
Second, Bluehelix has been the largest MPC-based decentralized cross-chain bridge for supporting any assets cross chain. Bluehelix Bridge has integrated asset transactions on seven public chains, including Bitcoin, Ethereum, HECO, BSC, DOGE, TRON, Polygon, and more public chains will be connected in the future.
Moreover, for better user's experience, Bluehelix has launched Bluehelix cross-chain Bridge, Bluehelix wallet(a decentralized wallet) and Hdex. HDEX is a decentralized trading platform that supports safe cross-chain deposit and trading of any asset. Based on the Bluehelix OpenDEX protocol, HDEX supports the fast exchange transaction mode of AMM and Orderbook order books, and is committed to providing users around the world with a decentralized trading experience with the ultimate performance.
In short, Bluehelix will supports more public chains and assets and improving our products.
Total Budget Requested
50,000 U for improving our products and doing some market activities to encourage users cross-chain transaction integrated Bluehelix bridge.
Maintenance and Upgrade Plans
1,We have a Security-vulnerabilities and Threat-intelligence Bounty Programme with cooperated with SlowMist which is open for community. Reports could get reward from $10-$10000 equivalent funds according to the findings.
Details could be check:
https://slowmist.io/hdex/
https://slowmist.io/en/bug-bounty.html
Within one working day, the SlowMist Security Team will confirm the threat intelligence report from the "SlowMist Zone", follow up, evaluate the problem, and feed the intelligence back to the BlueHelix contact person in the meantime (status: under review). Within three working days, the Bluehelix technical team will deal with the problem, draw conclusions and record points (status: confirmed / ignored). They will communicate with the reporter if necessary, and ask the reporter for assistance.
2, Bluehelix will keep doing marketing and supporting more assets and public chain.
Team
Contact Info
<EMAIL_ADDRESS>Tele:@Dori2008
Team Members
James JU
Cody Jiang
Team Member LinkedIn Profiles
https://www.linkedin.com/in/james-ju-65a89366/
https://www.linkedin.com/in/cody-jiang-38b31490/
Team Website
https://github.com/bluehelix-chain
Relevant Experience
Mr. Ju is a senior blockchain expert and a serial entrepreneur. As a former Huobi CTO, he led the operation of upgrading and reconstructing Huobi's cryptocurrency trading system, which oversees 20 billions (CNY) of cashflow on a daily basis. Mr. Ju also recruited Huobi's core technology developing team, one of which Huobi is still dependent on nowadays. Mr. Ju led the team and finished development and management of some of Huobi's most innovative technical operations, including but not limited to: USD business, futures market, Caimao securities, and Huobi Pro. After Mr. Ju left Huobi, he joined Xiaoying Technology Inc.（NYSE: XYF) as Vice President of technology and was responsible for platform maintenance, product development, and blockchain system innovation. In 2018, Mr. Ju founded Blue Helix with a purpose to create a brand-new crypto asset custody and clearing trading system. Mr. Ju is also an active member of various technical communities. He has contributed great contents in elite forums like QCon/ArchSummit /GTLC/CSDN. He was also a two-time co-chairman during the annual joint ArchSummit conference.
Team code repositories
https://github.com/bluehelix-chain
https://bhexchain.gitbook.io/bhex-chain/v/english/audit-report
Additional Information
The grant will be used for introducing iotex ecology, encouraging users cross-chain transaction and bringing more assets.

Hi there! We are officially moving all Halo Grant proposals to our new community forum page and will no longer be accepting proposals on GitHub. If you are still interested in pursuing this project, please resubmit your proposal to the community page here according to the provided template: https://community.iotex.io/c/halo-grants/61
Thank you!


[Task]: Implement logic for handling partially casted state

Task description
It is likely that users will receive funds on the same address that they staked with. To handle this situation, we need to guide them so that they can vote with all funds on their address.
Requirements
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Closing as the user will technically always be in a partially state with our chosen voting mechanism.


Issue about "extrinsic": [4, 4] -- camera extrinsic matrix

We know that the external parameter is the transformation relationship between the camera and the ground coordinate system.
When annotating data, how are extrinsic matrix annotated?
extrinsic matrix = [[cos(cam_pitch),  0,    -sin(cam_pitch), 0],
[0,                       1,    0,                        0],
[sin(cam_pitch),  0,    cos(cam_pitch),  h],
[0,                       0,    0,                        1]]
Is that how I understand it?

i think that the original cam_extrinsics in JSON file transforms camera coordinate system to vehicle coordinate system

i think that the original cam_extrinsics in JSON file transforms camera coordinate system to vehicle coordinate system

Thank you for your answers. They have been very helpful to me. However, I am confused about how you arrived at that conclusion. Could you please tell me where you found that information? Is it in Waymo's documents?

It's in waymo github issue24.


Systemd service issue

Not sure if this is the best approach, but as it stands the binary the current hubble.service file is looking for (via /opt/hubble/hubble) doesn't exist.  It was suggested to use a symlink in a prior PR, but the binary itself is non-existent in this case. ,

Ah, right, the existing service file wouldn't work for source installs.
This is probably a fine solution for the moment. I can't remember if all the packages stick the binary in /usr/bin/hubble or if maybe one or two hits /usr/local/bin/hubble or something. We should evaluate those packages and get everything in the same file (or two).


Fix unit tests in mnist.rs, cifar10.rs and imagenet_v2.rs

They are commented out right now since more work is needed here to get it right. I added some tests that I think is a good start. This is a good started issue or low hanging fruit IMO.

Hello @mjovanc , I am willing to complete those tasks, is the issue still available or assigned to someone

Hello @mjovanc , I am willing to complete those tasks, is the issue still available or assigned to someone

It's yours if you can do it! 👌🏻


Support Actionable Diagnostics from Scala 2.13.12+

Scala 2.13.12 added actionable diagnostics to the compiler and and info/warning/error messages.
We needed to change our tests in #789 to accommodate that change.
In future versions of Scapegoat, we could also support the actionable diagnostics in a way that we suggest a fix for rules where it makes sense.
An example: AvoidToMinusOne inspection would automatically suggest to rewrite x to n-1 to x until n.
Discuss: This would not work for older Scala versions. So we either only support Scapegoat for newer Scala versions or somehow create an internal intermediate model that maps to the Scala version's info message.

is this required to get an initial release for scala 2.13.12 ?

No.

from what I got from this ticket, this is additional functionality?

Yes.


Docs: Broken link for structure of a TaskResponse

The section for CompletionCallbackUrl contains a link describing what the response body for a TaskResponse looks like (currently pointing to https://github.com/cloudfoundry/bbs/blob/master/doc/defining-tasks.md#retrieving-tasks). This link seems broken.

Bunch of other links were broken as well, such as the one found in the EgressRules section.

Thanks, @aashah, we'll take a pass through the links in the BBS API docs and make sure they all resolve correctly. If you see any obvious corrections in the meantime, we'd welcome a PR!
Best,
Eric

Closing with https://github.com/cloudfoundry/diego-release/commit/c924d3e46484ae5b025178f5aa87ccb19959f0a3.


As an author, posts I create be private to only friends on my host

6cd40895ae284afa0961f776764c86c05debc383

For submission: verified. (With the assumption that this is the SERVERONLY visibility, which doesn't really imply anything about my friends. Do we think this needs to be friends on my server only or just anyone on my server only?)

This isn't serveronly, it's server only friends, we can't prove this work until we have connections.


[gdal] Update to 3.6.2

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static


NO-ISSUE: Remove workflow plugin dependency on knative/client int…

…erface
(cherry picked from commit dc7a3ecbcf65c835b0963e273c8a2308581e73d1)

@tomasdavidorg fyi, want to check?

@treblereel The CI on Windows has failed. Could you please check?

hmm,
packages/kogito-serverless-operator build:dev: ./hack/goimports.sh
packages/kogito-serverless-operator build:dev: Windows Subsystem for Linux has no installed distributions.
packages/kogito-serverless-operator build:dev: Distributions can be installed by visiting the Microsoft Store:
packages/kogito-serverless-operator build:dev: https://aka.ms/wslstore

not sure it's related to this pr, but lets take a look

It looks like CI is broke, https://github.com/apache/incubator-kie-tools/pull/2339

@tiagobento yeap, let me do a separate PR for this.


[BUG] Difference in URI handling behavior of % for Blob Storage between V8 and V12

Describe the bug
When trying to upgrade between V8 and V12 I have discovered differing behavior when handling % in a file path in blob storage.
On v8 the code looks like this:
  CloudBlobContainer container = getOrCreateCloudBlobContainer(containerName); // create a CloudBlobContainer
  try (FileInputStream stream = new FileInputStream(file)) {
    container.getBlockBlobReference(blobPath).upload(stream, file.length());
  }

On v12 the code looks like this:
    BlobContainerClient blobContainerClient = getOrCreateBlobContainerClient(containerName);

    try (FileInputStream stream = new FileInputStream(file)) {
      // By default this creates a Block blob, no need to use a specific Block blob client.
      blobContainerClient.getBlobClient(blobPath).upload(stream, file.length());
    }

Where blobPath is "ab2a7d5f-b973-4222-83ba-d0581817a819 %Россия 한국 中国!?/file" (anything with a % works to trigger this issue)
The public docs say that the client should automatically handle url encoding (% is not in the reserved characters list) (https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata).
But when I upload a file with a unencoded special character name directly via the azure UI it seems to work okay.
The V8 client seems to follow this logic, as it will accept a unencoded special character name.
But the V12 client will throw an exception.
Exception or Stack Trace
[2023-11-08T16:46:06.435Z] Caused by: java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 0 in: "Ро"
[2023-11-08T16:46:06.435Z] 	at java.base/java.net.URLDecoder.decode(URLDecoder.java:232)
[2023-11-08T16:46:06.435Z] 	at java.base/java.net.URLDecoder.decode(URLDecoder.java:142)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.common.Utility.decode(Utility.java:88)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.common.Utility.urlDecode(Utility.java:55)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.specialized.BlobAsyncClientBase.<init>(BlobAsyncClientBase.java:242)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.specialized.BlobAsyncClientBase.<init>(BlobAsyncClientBase.java:206)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.BlobAsyncClient.<init>(BlobAsyncClient.java:154)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:194)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:172)
[2023-11-08T16:46:06.435Z] 	at com.azure.storage.blob.BlobContainerClient.getBlobClient(BlobContainerClient.java:98)

To Reproduce
Try using the Java V12 blob client to upload a file with blobPath: "asdf%asdf"
Code Snippet
Linked these in the description
Expected behavior
I would expect the new client's behavior to be similar to both the docs and the UI, but right now the docs and the UI have different behavior.
Screenshots
N/A
Setup (please complete the following information):

OS: Ubuntu
IDE: N/A
Library/Libraries: azure-storage-blob:12.24.0
Java version: 8,11,17
App Server/Environment: N/A
Frameworks: N/A

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

Hi @georgew5656
Thank you for reaching out with this issue! This indeed is an issue on the Java side, we are currently working on a fix and hope to have it out soon. Will update on this thread when the fix is out!


Glitched video in headset for every game (tested with Superhot VR)

Description
All games have glitched/corrupted video in the Quest 2 (ALVR installed via Quest store) as shown in the included screenshot.
SteamVR Home, and the waiting area are not glitched, but the steam menu brought up by the menu button is also glitched.
Tracking works fine though.
I should mention I switched to Fedora from Arch to fix this exact issue. In Arch, I was using mesa-tkg-git (which I installed a long time ago and forgot about), and reinstalling upstream mesa, vulkan-radeon and va-api drivers fixed the issue mostly. The menu was still glitched, which is what prompted me to try a "more stable" OS, which ended up having the same exact issue.
Till now I have only tried using the freeworld alternatives of the va-api drivers, but I read somewhere that va-api is not even supported by Quest 2, so that's probably not the problem. I feel there's something wrong with video drivers, but as this is a fresh Fedora install, and a fresh everything install basically, I think the issue is beyond the OS.

The Waiting Area screen looks fine

The Menu is glitched

The game loading heads up looks fine as well

Once I enter the game (SuperHot VR in this case), everything is corrupted beyond recognition.

When in game, the main screen of the menu is fine but the rest is glitched.
General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR GitHub Wiki

Environment
Hardware
Note: https://linux-hardware.org/?probe=fd9d1ea7b8
CPU: AMD Ryzen 9 5900HX
GPU: AMD Radeon 6800M
GPU Driver Version: mesa-vulkan-drivers 24.1.5-2.fc40, mesa-va-drivers-freeworld 24.1.5-1.fc40
Audio: Pipewire
Installation
ALVR Version: 20.9.1
ALVR Settings File: All the settings are at default.
SteamVR Version: 2.7
Install Type:

[ ] Packaged (exe, deb, rpm, etc)
[x] Portable (zip)
[ ] Source

OS Name and Version: Fedora Linux 40 (Workstation Edition)

Do other games have that rendering issue? Specifically a game that would be running in vulkan, like VRChat? I find that OpenGL games tend to not render correctly in the steamvr runtime, and give me the aforementioned glitchiness in game. As for the menu afaik that hasn’t been rendering correctly for most people

@Macjja

PC view of the VRChat Login Screen

Quest 2 View.
All games seem to have this issue.
Could you link me some comments about other people's menus being glitched like this?
Also, the whole alvr portable binary thing seems to be very finicky. I heard that the appimage is discontinued, the flatpak takes time to build instead of just installing it from flathub, and I don't see anything other than the binary in the releases. Is alvr in any distro's main repo?

Could you link me some comments about other people's menus being glitched like this?

This was anecdotal, and related to this image you sent

@Macjja  DRI_PRIME=1 fixed the glitching in-game, which now feels like a silly mistake on my part.
There's still the issue of the glitchy menus, which are obviously unusable. Running Steam with DRI_PRIME has its own issues (the window doesn't wanna render at all, for me) so I can't try that as a fix.
Also, is there a way to permanently add the ALVR add-on to SteamVR? It seems like every time I launch SteamVR without going through ALVR, I get a "Headset not Detected" error.

@vibudh007

DRI_PRIME=1 fixed the glitching in-game, which now feels like a silly mistake on my part.

Didn’t notice you had a mobile config, should’ve mentioned that as well since I also have a mobile config😅

Also, is there a way to permanently add the ALVR add-on to SteamVR? It seems like every time I launch SteamVR without going through ALVR, I get a "Headset not Detected" error.

Not as far as I’m aware, you have to launch steamVR through ALVR every time you want to use ALVR with it; but since the ALVR server needs to be running anyways it shouldn’t be too much of a hassle