Failed to build on Cuda-11.1

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: related to servers
TensorFlow installed from (source or binary): source
TensorFlow version: commit: a0b68d1ecc46f9bbc8fad4f18c68f25c6bd5ae48
Python version: 3.6
Installed using virtualenv? pip? conda?: none
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 7.5.0-3ubuntu1
CUDA/cuDNN version: CUDA-11.1, CuDNN 8.0.3 for CUDA-11.0
GPU model and memory: RTX 3090, 24GB, RTX Titan, 24GB, RTX 2080Ti, 11GB (total three GPUs)

Describe the problem
Hello,
failed to compile Tensorflow.
Please check the log messages then give me an advice.
Thanks!
Provide the exact sequence of commands / steps that you executed before running into the problem
(Including logging messages)
bazel build --config=mkl //tensorflow/tools/pip_package:build_pip_package
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
tensorflow$ deactivate
sephiroce@bike:~/open_source/tensorflow$ bazel build --config=mkl //tensorflow/tools/pip_package:build_pip_package
WARNING: Ignoring JAVA_HOME, because it must point to a JDK, not a JRE.
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=228
INFO: Reading rc options for 'build' from /home/sephiroce/open_source/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/sephiroce/open_source/tensorflow/.bazelrc:
  'build' options: --apple_platform_type=macos --define framework_shared_object=true --define open_source_build=true --java_toolchain=//third_party/toolchains/java:tf_java_toolchain --host_java_toolchain=//third_party/toolchains/java:tf_java_toolchain --define=tensorflow_enable_mlir_generated_gpu_kernels=0 --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /home/sephiroce/open_source/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/home/sephiroce/virtualenv/py3-tf2-gpu/bin/python3 --action_env PYTHON_LIB_PATH=/home/sephiroce/virtualenv/py3-tf2-gpu/lib/python3.6/site-packages --python_path=/home/sephiroce/virtualenv/py3-tf2-gpu/bin/python3 --config=xla --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.1 --action_env TF_CUDA_COMPUTE_CAPABILITIES=8.6 --action_env LD_LIBRARY_PATH=/home/sephiroce/open_source/rdkit/build/lib:/usr/local/cuda/lib64:/usr/local/lib:/usr/local/lib/openmpi:/home/sephiroce/local/lib:/usr/lib/x86_64-linux-gnu:/usr/lib: --action_env GCC_HOST_COMPILER_PATH=/usr/bin/x86_64-linux-gnu-gcc-7 --config=cuda --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:short_logs in file /home/sephiroce/open_source/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/sephiroce/open_source/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:xla in file /home/sephiroce/open_source/tensorflow/.bazelrc: --define=with_xla_support=true
INFO: Found applicable config definition build:cuda in file /home/sephiroce/open_source/tensorflow/.bazelrc: --config=using_cuda --define=using_cuda_nvcc=true
INFO: Found applicable config definition build:using_cuda in file /home/sephiroce/open_source/tensorflow/.bazelrc: --define=using_cuda=true --action_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --define=tensorflow_enable_mlir_generated_gpu_kernels=1
INFO: Found applicable config definition build:mkl in file /home/sephiroce/open_source/tensorflow/.bazelrc: --define=build_with_mkl=true --define=enable_mkl=true --define=tensorflow_mkldnn_contraction_kernel=0 -c opt
INFO: Found applicable config definition build:linux in file /home/sephiroce/open_source/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels
INFO: Found applicable config definition build:dynamic_kernels in file /home/sephiroce/open_source/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
INFO: Repository local_config_cuda instantiated at:
  no stack (--record_rule_instantiation_callstack not enabled)
Repository rule cuda_configure defined at:
  /home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl:1407:18: in <toplevel>
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
   Traceback (most recent call last):
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
                _create_local_cuda_repository(<1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
                _find_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
                _check_cuda_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
                execute(repository_ctx, <1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/remote_config/common.bzl", line 208, in execute
                fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': no such package '@local_config_cuda//cuda': Traceback (most recent call last):
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
                _create_local_cuda_repository(<1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
                _find_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
                _check_cuda_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
                execute(repository_ctx, <1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/remote_config/common.bzl", line 208, in execute
                fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
WARNING: Target pattern parsing failed.
ERROR: no such package '@local_config_cuda//cuda': Traceback (most recent call last):
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1377
                _create_local_cuda_repository(<1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 1054, in _create_local_cuda_repository
                _find_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 599, in _find_libs
                _check_cuda_libs(repository_ctx, <2 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/gpus/cuda_configure.bzl", line 501, in _check_cuda_libs
                execute(repository_ctx, <1 more arguments>)
        File "/home/sephiroce/open_source/tensorflow/third_party/remote_config/common.bzl", line 208, in execute
                fail(<1 more arguments>)
Repository command failed
No library found under: /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1
INFO: Elapsed time: 1.183s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
    currently loading: tensorflow/tools/pip_package

My graphics card: 3080
Cuda 11.1, ubuntu 20.04, cudnn 8.0.3 (the very recent one), python 3.8
I installed cuda 11.1 using the .deb file (to create all the symlinks automatically)
I think the problem is that CUDA11.1 installs symlink libcudart 11.0 but it does not create symlink for libcudart11.1.
However, tensorflow tries to find libcudart 11.1, because cuda version is 11.1
I tried to make a symlink libcudart11.1 -> libcudart11.1.74 as suggested in here : https://github.com/tensorflow/tensorflow/issues/26150#issuecomment-469058265
However, then the error showed that SONAME did not match.
Next, I tried this method : https://github.com/tensorflow/tensorflow/issues/26289#issuecomment-477848947
I opened third_party/gpus/cuda_configure.bzl and searched for 'cudart'
Changed  cuda_config.cuda_version to "11.0"
For me, changing cuda_config.cuda_version of only cudart and cudart_static worked and I am currently building tensorflow.
My CPU is too slow (never expected to build tensorflow myself), so it will take a long time to see if it successfully builds, but until now, it is building without any errors.
I will update if anything happens.

Thanks!
It worked 👍  (I'm not sure the RTX 3090 is fully utilized or not though.)

It worked 👍 (I'm not sure the RTX 3090 is fully utilized or not though.)

sm_86 doesnt seem to be implemented in nvcc yet, at least not in the copy i have (same cuda/cudnn configuration) so there's probably still room for performance improvement

It worked 👍 (I'm not sure the RTX 3090 is fully utilized or not though.)

sm_86 doesnt seem to be implemented in nvcc yet, at least not in the copy i have (same cuda/cudnn configuration) so there's probably still room for performance improvement

I ran a simple test training, and Conv2D operation was about 2~3 times faster than 2070super. The tensorboard profiling showed that 3080 did not use tensorcores, and the speed was actually a bit faster with fp32 than mixed precision. Considering some issues saying that using tensorcores does not speed up much, I think the performance is within the range of expectation.
Oh, and by the way, profiling fails in CUDA11.1. It worked with CUDA11.0, but after I upgraded to CUDA11.1, segmentation fault happens.

I ran a simple test training, and Conv2D operation was about 2~3 times faster than 2070super. The tensorboard profiling showed that 3080 did not use tensorcores, and the speed was actually a bit faster with fp32 than mixed precision. Considering some issues saying that using tensorcores does not speed up much, I think the performance is within the range of expectation.
Oh, and by the way, profiling fails in CUDA11.1. It worked with CUDA11.0, but after I upgraded to CUDA11.1, segmentation fault happens with profile_batch turned on.

Please tell me what versions of CUDA and cuDNN did you use? And also a listing of a test training, if not difficult.

Please tell me what versions of CUDA and cuDNN did you use, and the parameters at which the build was successful? And also a listing of a test training, if not difficult.
My platform:
OS: Windows 10 x64, Graphics Card: Palit RTX 3080
My REQUIRED_PACKAGES were working for me:
python 3.6 absl-py==0.7.0 astunparse==1.6.3 gast==0.3.3 google_pasta==0.1.8 h5py==2.10.0 keras_preprocessing==1.1.1 opt_einsum==2.3.2 protobuf==3.9.2 tensorboard==2.3.0 tensorflow_estimator==2.3.0 termcolor==1.1.0 wrapt==1.11.1 wheel==0.26 six==1.12.0 numpy==1.18.5
My build options that where working:
bazel build --config=opt --config=avx2_win --config=short_logs --define=no_tensorflow_py_deps=true --copt=-DTHRUST_IGNORE_CUB_VERSION_CHECK --copt=-nvcc_options=disable-warnings //tensorflow/tools/pip_package:build_pip_package
I used cuDNN v8.0.3 (August 26th, 2020), for CUDA 11.0 and Latest Release CUDA Toolkit 11.1 (Sept 2020), but this required renaming cudart64_110.dll to cudart64_111.dll and cufftw64_10.dll to cufftw64_11.dll for the test vgg16 model to work
With CUDA Toolkit 11.0 Update1 (Aug 2020) and cuDNN v8.0.3 (August 26th, 2020), for CUDA 11.0 i got:
nvcc fatal : Unsupported gpu architecture 'compute_86'

OK, here's all I have tried since installing 3080
Ubuntu 20.04
cuDNN v8.0.3

CUDA 11.0 Update1

As you mentioned, building from the source with compute compatibility 8.6 failed.
I think it's because CUDA 11.0 does not support 30 series geforce graphics card.
They added 30 series in CUDA 11.1
However, installing with pip tf-nightly works.
The problem with pypi installation is that it does not recognize sm_86, and spits out
ptxas fatal : Value 'sm_86' is not defined for option 'gpu-name' and compiles ptxas every single time it launches.
Tensorboard profiling worked in this case.

CUDA 11.1

pip tf-nightly
It still works.
Tensorflow does fail to find libcudart.so.11.1 (as CUDA 11.1 does not make libcudart.so.11.1 nor libcudart.so.11 symlink), but because Tensorflow then searches for libcudart.so file, it managed to load libcudart.so anyway.
However, it still does not recognize sm_86 and compiles ptxas everytime it starts.
Moreover, Tensorboard profiling does not work. (segmentation fault)

Build from source
This is the case I mentioned above.
In my case, making symlink for libcudart.so.11.1 did not work.
I had to edit third_party/gpus/cuda_configure.bzl file.
With this build, it now recognizes sm_86 and does not compile ptxas anymore.
However, tensorboard profiling error consists.

In both CUDA 11.0 Update1 and CUDA 11.1

They both have to set set_memory_growth=True, or they spit out errors when predict and/or fit a model with Conv layers.
This problem does not care how big the model is. Even with a single Conv layer, it just fails.
About testing, I used customized HRNet. It has batchnorm, Conv2D, Conv2D Transpose, Global pooling average and Dense layers.
It is the only log I have left with profiling turned on using 2070super, so I only compared with this model.
I think I can get my profiling function back if I downgrade to CUDA 11.0, but I really do not want to change anything anymore, until new versions come out.

Why is this closed ?

Why is this closed ?

Because the chief complaint of this issue is failing to build on CUDA-11.1, and at least building tensorflow is successful.

How to change the value of cuda_config.cuda_version to 11.0
cudart": _check_cuda_lib_params(
"cudart",
cpu_value,
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version,    <-------------------- here
static = False,
),
"cudart_static": _check_cuda_lib_params(
"cudart_static",
cpu_value,
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version,               <--------------------------- and here
static = True,
),
Please, I am not too good at python...

How to change the value of cuda_config.cuda_version to 11.0
cudart": _check_cuda_lib_params(
"cudart",
cpu_value,
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version, <-------------------- here
static = False,
),
"cudart_static": _check_cuda_lib_params(
"cudart_static",
cpu_value,
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version, <--------------------------- and here
static = True,
),
Please, I am not too good at python...

I meant literally changing it to "11.0"

Before :
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version,
static = False,

After:
cuda_config.config["cuda_library_dir"],
"11.0",
static = False,

Thank you very much for the so swift help. I am not being able to build tensorflow with bazel. Somebody wrote that the soultion is to change the version to  11.0, since I use cuda11.1 and cudnn8... I changed the version as you kindly suggested, but I still can not build it. After changing I still get these errors:
ERROR: An error occurred during the fetch of repository 'local_config_cuda':ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': no such package '@local_config_cuda//cuda': Traceback (most recent call last):
WARNING: Target pattern parsing failed.
ERROR: no such package '@local_config_cuda//cuda': Traceback (most recent call last):
I feel so sorry but some help would be very much appreciated.

Thank you very much for the so swift help. I am not being able to build tensorflow with bazel. Somebody wrote that the soultion is to change the version to 11.0, since I use cuda11.1 and cudnn8... I changed the version as you kindly suggested, but I still can not build it. After changing I still get these errors:
ERROR: An error occurred during the fetch of repository 'local_config_cuda':ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': no such package '@local_config_cuda//cuda': Traceback (most recent call last):
WARNING: Target pattern parsing failed.
ERROR: no such package '@local_config_cuda//cuda': Traceback (most recent call last):
I feel so sorry but some help would be very much appreciated.

What specific CUDA version/CUDNN version/ OS are you using?

Thank you very much for your answer.
I am using  cuda-11.1 and libcudnn8-<IP_ADDRESS>-1, and I my system is linux_suse_x86-64.

Ok. things to try:

Install cudnn 8.0.4 or 8.0.3
8.0.4 is the cudnn which supports cuda 11.1.
I had no problem building with cudnn 8.0.3, and am currently building with cudnn 8.0.4 without any errors right now.
(My cpu is not so good. It takes ages to complete building)
Honestly, I do not think this is the problem, but give it a try.

Check your cuda path.
When executing configure file before building with bazel, does that properly recognize your cuda and cudnn?
If not so, check LD_LIBRARY_PATH and PATH.

Thousand thanks for your reply. I will try. Yeah, something strange happened. Actually, I have installed cuda10.2 in my system, and when running the .configure of tensor flow, it asks for the cuda version and so on, and the program would go to limbo, it would ask for the cudnn version, and also for the RT support and so on. Then I thought that the problem would be not having "cupy" installed, because I want to use GPU's, and the card I got is a GeForce GTX 1060 6GB.  It was also kind of cumbersome to install cupy, but finally I did. Suddenly .configure would ask all these questions again, but now the default cuda, was the cuda11.1, and the defalut cudnn would be cudnn7.1. But the cudnn installed was the cudnn8.0.0. So I input that, and then .configure finished, indicating the options to run bazel. I thought I succeeded, but now I am facing this problem for more than a week. My LD_LIBRARY_PATH and PATH are pointing to my cuda-10.2 installation, and it seems that .configure doesn't care. It automatically goes to thecuda11.1 installation.

If you are using gtx 1060, I really suggest using cuda 10.1 or  10.2, not 11.x.
For me, I have 3080 which does not work with cuda 10 so I have to use cuda 11.
However, right now, there is absolutely no benefit for using cuda 11.
Whether or not you still want to use cuda 11, I recommend uninstalling CUDA completely and reinstalling CUDA.
Something seems to be messed up.

I have no words to thank you for your time. You got almost the best GPU card in the market. Does it maintain a low temperature? Well, comparatively I mean. Let me then re-install cuda-10.2 and the libcuddnn corresponding is
Then I will have to uninstall cuda11.1 that suddenly appeared when I installed "cupy", and then re-install cuda. In fact I got cuda and cuda10.2 which are the same. My CUDA_HOME points to /usr/local/cuda. And I will proceed with cudnn-8.0.4

Now, in Linux SUSE-15.1  cuda 10.2 and libcudnn<IP_ADDRESS>.180.1 come pre installed.

I looked up cupy installation document briefly. It seems like it does not require CUDA 11.1.
If you do not need 11.1 for any other reason, I recommand you to go for cuda 10.1 and cudnn 7.6.5
(Compatibility matrix : https://docs.nvidia.com/deeplearning/cudnn/support-matrix/index.html)
I haven't used SUSE, so I am not sure whether installing cuda 10.1 will be successful, but if possible, it is the most stable configure for tensorflow.
As you said, remove all cuda related things first, and then install cuda 10.1 with corresponding cudnn (recommend 7.6.5).
If CUDA11.1 was installed when installing cupy, try installing cupy-cuda101 (or cupy-cuda102 if you want to use 10.2)

OK, I will follow your advice. Thank you very much. Hope this time around I can install tensorflow with the GPU's. Because I installed one, indeed, but pycharm keeps warning that even though it detects the GPU, it can't use it... So I need this bazel installation.

Hello, how are you? I am still fighting with the installation of TF, and when I thought I did, the monitor suddenly went off, and after 10 or 12 minutes it came back and this is the state. Do you think the installation is going well? Because for some time it doesn´t continue.
Thank you for your comments.

差出人: jaentrouble<EMAIL_ADDRESS>送信日時: 2020年10月7日 5:24
宛先: tensorflow/tensorflow<EMAIL_ADDRESS>CC: minsky-1<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>件名: Re: [tensorflow/tensorflow] Failed to build on Cuda-11.1 (#43588)
I looked up cupy installation document briefly. It seems like it does not require CUDA 11.1.
If you do not need 11.1 for any other reason, I recommand you to go for cuda 10.1 and cudnn 7.6.5
(Compatibility matrix : https://docs.nvidia.com/deeplearning/cudnn/support-matrix/index.html)
I haven't used SUSE, so I am not sure whether installing cuda 10.1 will be successful, but if possible, it is the most stable configure for tensorflow.
As you said, remove all cuda related things first, and then install cuda 10.1 with corresponding cudnn (recommend 7.6.5).
If CUDA11.1 was installed when installing cupy, try installing cupy-cuda101 (or cupy-cuda102 if you want to use 10.2)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/tensorflow/tensorflow/issues/43588#issuecomment-704699886, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARE5YSNJB7MEZEPCV2EQ7V3SJP3RBANCNFSM4R3AYDJQ.

Hello,
I am still struggling with the TF installation, and thought everything was going OK, when suddenly the computer has stopped. This happened last time, after I changed as you advised me. But the computer was back after 3 hours or so. But this time, its more than 12 hours and it doesn´t come back.
Do you think I should force shutdown and retry? It has stopped as I show in the photo. How far am I from installing it?  Thank you for your time.

差出人: jaentrouble<EMAIL_ADDRESS>送信日時: 2020年10月6日 8:02
宛先: tensorflow/tensorflow<EMAIL_ADDRESS>CC: minsky-1<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>件名: Re: [tensorflow/tensorflow] Failed to build on Cuda-11.1 (#43588)
Ok. things to try:

Install cudnn 8.0.4 or 8.0.3
8.0.4 is the cudnn which supports cuda 11.1.
I had no problem building with cudnn 8.0.3, and am currently building with cudnn 8.0.4 without any errors right now.
(My cpu is not so good. It takes ages to complete building)
Honestly, I do not think this is the problem, but give it a try.

Check your cuda path.
When executing configure file before building with bazel, does that properly recognize your cuda and cudnn?
If not so, check LD_LIBRARY_PATH and PATH.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/tensorflow/tensorflow/issues/43588#issuecomment-704102087, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARE5YSJBLEDAXEAU2TJKSVLSJLFJHANCNFSM4R3AYDJQ.

Hi,
I'm having issues with building TF 2.3.
OS: Ubuntu 18.04
GPU: RTX2080
CUDA: 11.1
cudNN: 8.0.4
TensorRT: 7.2
I already tried :
changing it to "11.0"
Before :
cuda_config.config["cuda_library_dir"],
cuda_config.cuda_version,
static = False,
After:
cuda_config.config["cuda_library_dir"],
"11.0",
static = False,
Please see the following to see what happened and let me know what else I should do.
root:~/tensorflow# ./configure
You have bazel 3.1.0 installed.
Please specify the location of python. [Default is /usr/bin/python3]: /usr/bin/python3
Found possible Python library paths:
/usr/lib/python3/dist-packages
/usr/local/lib/python3.7/dist-packages
Please input the desired Python library path to use.  Default is [/usr/lib/python3/dist-packages]
/usr/lib/python3/dist-packages
Do you wish to build TensorFlow with OpenCL SYCL support? [y/N]: n
No OpenCL SYCL support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]: y
ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.
Do you wish to build TensorFlow with TensorRT support? [y/N]: y
TensorRT support will be enabled for TensorFlow.
Traceback (most recent call last):
File "third_party/gpus/find_cuda_config.py", line 649, in
main()
File "third_party/gpus/find_cuda_config.py", line 641, in main
for key, value in sorted(find_cuda_config().items()):
File "third_party/gpus/find_cuda_config.py", line 579, in find_cuda_config
result.update(_find_cuda_config(cuda_paths, cuda_version))
File "third_party/gpus/find_cuda_config.py", line 255, in _find_cuda_config
get_header_version)
File "third_party/gpus/find_cuda_config.py", line 241, in _find_header
required_version, get_version)
File "third_party/gpus/find_cuda_config.py", line 230, in _find_versioned_file
actual_version = get_version(file)
File "third_party/gpus/find_cuda_config.py", line 247, in get_header_version
version = int(_get_header_version(path, "CUDA_VERSION"))
ValueError: invalid literal for int() with base 10: ''
Asking for detailed CUDA configuration...
Please specify the CUDA SDK version you want to use. [Leave empty to default to CUDA 10]: 11.1
Please specify the cuDNN version you want to use. [Leave empty to default to cuDNN 7]: 8.0.4
Please specify the TensorRT version you want to use. [Leave empty to default to TensorRT 6]: 7.2
Please specify the locally installed NCCL version you want to use. [Leave empty to use http://github.com/nvidia/nccl]:
Please specify the comma-separated list of base paths to look for CUDA libraries and headers. [Leave empty to use the default]: /lib,/lib/x86_64-linux-gnu,/usr,/usr/lib/x86_64-linux gnu/libfakeroot,/usr/local/cuda,/usr/local/cuda-11.1,/usr/local/cuda-11.1/targets/x86_64-linux/lib,/TensorRT-<IP_ADDRESS>
Traceback (most recent call last):
File "third_party/gpus/find_cuda_config.py", line 649, in
main()
File "third_party/gpus/find_cuda_config.py", line 641, in main
for key, value in sorted(find_cuda_config().items()):
File "third_party/gpus/find_cuda_config.py", line 579, in find_cuda_config
result.update(_find_cuda_config(cuda_paths, cuda_version))
File "third_party/gpus/find_cuda_config.py", line 255, in _find_cuda_config
get_header_version)
File "third_party/gpus/find_cuda_config.py", line 241, in _find_header
required_version, get_version)
File "third_party/gpus/find_cuda_config.py", line 230, in _find_versioned_file
actual_version = get_version(file)
File "third_party/gpus/find_cuda_config.py", line 247, in get_header_version
version = int(_get_header_version(path, "CUDA_VERSION"))
ValueError: invalid literal for int() with base 10: ''
Asking for detailed CUDA configuration...

Hello my friend.
I succeeded with the installation, it recognizes the card, and all the cublas libraries...!!!
And it is working in tandem with pycharm...
Thank you very much for your replies. It took me half the month to do so.
I installed python3.7, then I had to reinstall python3.6, because cuda was running with python3.6.
I have neve had a problem like this. But it is done. Thank you for your help...

差出人: jaentrouble<EMAIL_ADDRESS>送信日時: 2020年10月7日 5:24
宛先: tensorflow/tensorflow<EMAIL_ADDRESS>CC: minsky-1<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>件名: Re: [tensorflow/tensorflow] Failed to build on Cuda-11.1 (#43588)
I looked up cupy installation document briefly. It seems like it does not require CUDA 11.1.
If you do not need 11.1 for any other reason, I recommand you to go for cuda 10.1 and cudnn 7.6.5
(Compatibility matrix : https://docs.nvidia.com/deeplearning/cudnn/support-matrix/index.html)
I haven't used SUSE, so I am not sure whether installing cuda 10.1 will be successful, but if possible, it is the most stable configure for tensorflow.
As you said, remove all cuda related things first, and then install cuda 10.1 with corresponding cudnn (recommend 7.6.5).
If CUDA11.1 was installed when installing cupy, try installing cupy-cuda101 (or cupy-cuda102 if you want to use 10.2)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/tensorflow/tensorflow/issues/43588#issuecomment-704699886, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARE5YSNJB7MEZEPCV2EQ7V3SJP3RBANCNFSM4R3AYDJQ.

Another RTX 3080 user here, trying to make CUDA 11.1 with cuDNN and tensorflow works (using conda to make my environment) but fail to do so, I get that I have to use latest cuda as it supports my card, but there seems to be so many conflicts upon trying to make the environment, if someone got a solution would really help~

Can verify that I was able to start compiling from this answer above!

Another resolution is to modify soname in libcudart.so.
sudo patchelf --set-soname libcudart.so.11.1 /usr/local/cuda-11.1/targets/x86_64-linux/lib/libcudart.so.11.1.74
But the system will show the file was truncated.


Schemas can't load in Windows

I found the problem, it's on this line https://github.com/tamago324/nlsp-settings.nvim/blob/main/lua/nlspsettings/jsonls.lua#L29, it can be fixed by replacing file:// with file:/// or just /.
res[server_name] = string.format('/%s/%s', path, name) -- jsonls.lua L29

this works fine for me.

PR is welcome!

Alright, also I tried in Linux and doesn't seems to work, so I'll do the PR without Windows distinction


Adding breadcrumbs to all resources.

Hi!
It's not an issue, but I could not create request.
My question: Why we can not add breadcrumbs globally in Resource file, or Nova Service Provider file as a tool?
If we have plenty of resources and in any future this package will have any kind of not compatibility with any part of Nova, it will be very painful to remove code from all resources. Normally, commonly breadcrumbs are for all pages in the app, not only selected.
It is my point of view of course and fell free to give any kind of feedback to this question :-)

It's built as a card because its the easiest way to add something to the top of all of the required pages.
Sure I could have wrapped the pages again in the style of my Resource Cards package and used a Tool or some such to add the Breadcrumbs to every page, but as I had already wrapped the pages for my resource cards this seemed like over-engineering.
Theres nothing stopping you from overriding resolveCards on your App/Nova/Resource.php file which all of your Resources extend by default and doing the following:
    public function resolveCards(NovaRequest $request)
    {
        array_unshift($this->cards($request), Breadcrumbs::make($request, $this));
        return collect(array_values($this->filter($this->cards($request))));
    }

Thanx for comment. It makes sense. I will try to apply b. for all resources following your tip.

:-) I had the same. Implementing breadcrumbs to one of the resource shows me the issue I was not going to discover with it. Thanks 🙏

Awesome, closing this for now but if you need anything else feel free to open a new issue (or just reply here again if its related)


Couldn't read Frameset in a page using Puppeteer

Steps to reproduce
Tell us about your environment:

Puppeteer version: v1.1.1
Platform / OS version: Windows10
URLs (if applicable):
Node.js version: 8.10

What steps will reproduce the problem?
Please include code that reproduces the issue.
The page i'm trying to access using puppeteer, has a main frameset, and it has multiple frames attached to it.
I need to get a particular frame to access a link, The functions i tried are listed below,
await page.frames(); -- returns only one result, i.e the main page itself, no child frames in it
page.mainFrame();  -- returns the main page
What is the expected result?
Expected at least the main frame set as result
What happens instead?
Could not get frameset and the nested frames in a page.
Any help will be highly appreciated.

Page frames get loaded when i added a forceful delay.


Node v18 "fetch" causes exception on LSP startup

[ERROR][2022-07-11 17:08:08] .../vim/lsp/rpc.lua:420	"rpc"	"m68k-lsp-server"	"stderr"	"(node:43562) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time\n(Use `node --trace-warnings ...` to show where the warning was created)\n"
[ERROR][2022-07-11 17:08:08] .../vim/lsp/rpc.lua:420	"rpc"	"m68k-lsp-server"	"stderr"	"node:internal/deps/undici/undici:4832\n            throw new TypeError(\"Failed to parse URL from \" + input, { cause: err });\n                  ^\n\nTypeError: Failed to parse URL from /opt/homebrew/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.wasm\n    at new Request (node:internal/deps/undici/undici:4832:19)\n    at Agent.fetch2 (node:internal/deps/undici/undici:5524:29)\n    ... 4 lines matching cause stack trace ...\n    at new Promise (<anonymous>)\n    at Parser.init (/opt/homebrew/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:332)\n    at $l (/opt/homebrew/lib/node_modules/m68k-lsp-server/out/server.js:300:2915)\n    at /opt/homebrew/lib/node_modules/m68k-lsp-server/out/server.js:300:3197 {\n  [cause]: TypeError [ERR_INVALID_URL]: Invalid URL\n      at new NodeError (node:internal/errors:388:5)\n      at URL.onParseError (node:internal/url:564:9)\n      at new URL (node:internal/url:644:5)\n      at new Request (node:internal/deps/undici/undici:4830:25)\n      at Agent.fetch2 (node:internal/deps/undici/undici:5524:29)\n      at Object.fetch (node:internal/deps/undici/undici:6351:20)\n      at fetch (node:internal/bootstrap/pre_execution:197:25)\n      at /opt/homebrew/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:15192\n      at /opt/homebrew/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:15413\n      at new Promise (<anonymous>) {\n    input: '/opt/homebrew/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.wasm',\n    code: 'ERR_INVALID_URL'\n  }\n}\n\nNode.js v18.5.0\n"

Seems to be the same issue as referenced here: https://github.com/emscripten-core/emscripten/issues/16913
I was able to workaround by adjusting the first line of m68k-lsp-server (the npm package) to include the --no-experimental-fetch argument:
#!/usr/bin/env node --no-experimental-fetch
require("./out/server");

Maybe building with an updated emscripten would fix this (it seems like the issue was addressed on their side), but otherwise it seems my workaround works perfectly fine as well.

Annoyingly that quick fix results in an error on node <=15: node: bad option: --no-experimental-fetch. We really need to support node 14 given in's still in LTS.
I'll try the updated emscripten.

Apologies for chiming in on something that's already marked as closed.
I started looking into this language server yesterday and had the exact same problem as described here. In my case, something similar to what has been suggested above worked:
#!/usr/bin/env -S node --no-experimental-fetch

I am on node v18.7.0 and since I've only installed this yesterday should be running v0.8.0. I've also compared that my local vasmm68k_mot has the changes from the commit above.

Ok that's strange, it looked to me like the new emscripten version fixed it. I'll have another look.

Just trying to get to the bottom of this. Proir to v0.8.0, the wasm build of vasm would fail like this when executed with node 18:
$ git checkout v0.7.0
Previous HEAD position was 8eb65c2 v0.8.0
HEAD is now at f6b1bca v0.7.0
$ node server/wasm/vasmm68k_mot ~/example.s
(node:19651) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot:143
      throw ex;
      ^

TypeError: Failed to parse URL from /Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot.wasm
    at new Request (node:internal/deps/undici/undici:5446:19)
    at Agent.fetch2 (node:internal/deps/undici/undici:6242:25)
    ... 4 lines matching cause stack trace ...
    at Object.<anonymous> (/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot:5043:11)
    at Module._compile (node:internal/modules/cjs/loader:1120:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
    at Module.load (node:internal/modules/cjs/loader:998:32) {
  [cause]: TypeError [ERR_INVALID_URL]: Invalid URL
      at new NodeError (node:internal/errors:387:5)
      at URL.onParseError (node:internal/url:564:9)
      at new URL (node:internal/url:644:5)
      at new Request (node:internal/deps/undici/undici:5444:25)
      at Agent.fetch2 (node:internal/deps/undici/undici:6242:25)
      at Object.fetch (node:internal/deps/undici/undici:7076:20)
      at fetch (node:internal/bootstrap/pre_execution:199:25)
      at instantiateAsync (/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot:1593:14)
      at createWasm (/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot:1630:3)
      at Object.<anonymous> (/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot:5043:11) {
    input: '/Users/batesgw1/m68k-lsp/server/wasm/vasmm68k_mot.wasm',
    code: 'ERR_INVALID_URL'
  }
}

Node.js v18.7.0

After the fix this no longer happens and it successfully assembles a source file (the warning at the end is unrelated):
$ git checkout v0.8.0
HEAD is now at 8eb65c2 v0.8.0
$ node server/wasm/vasmm68k_mot ~/example.s
vasm 1.9 (c) in 2002-2022 Volker Barthelmann
vasm M68k/CPU32/ColdFire cpu backend 2.5 (c) 2002-2021 Frank Wille
vasm motorola syntax module 3.15d (c) 2002-2022 Frank Wille
vasm test output module 1.0 (c) 2002 Volker Barthelmann

CODE(acrx2):	          2 bytes
program exited (with status: 0), but EXIT_RUNTIME is not set, so halting execution but not exiting the runtime or preventing further async execution (build with EXIT_RUNTIME=1, if you want a true shutdown)

@docbobo do you see something different if you try to reproduce it this way?

I've tried the exact same steps are you and I am also seeing the exact same result. Weird.
So I disable the workaround and tried again. Here's what the lsp.log says:
[START][2022-08-05 14:06:52] LSP logging initiated
[ERROR][2022-08-05 14:06:52] .../vim/lsp/rpc.lua:420    "rpc"   "m68k-lsp-server"       "stderr"        "(node:612466) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time\n(Use `node --trace-warnings ...` to show where the warning was created)\n"
[ERROR][2022-08-05 14:06:52] .../vim/lsp/rpc.lua:420    "rpc"   "m68k-lsp-server"       "stderr"        "node:internal/deps/undici/undici:5446\n            throw new TypeError(\"Failed to parse URL from \" + input, { cause: err });\n                  ^\n\nTypeError: Failed to parse URL from /usr/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.wasm\n    at new Request (node:internal/deps/undici/undici:5446:19)\n    at Agent.fetch2 (node:internal/deps/undici/undici:6242:25)\n    ... 4 lines matching cause stack trace ...\n    at new Promise (<anonymous>)\n    at Parser.init (/usr/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:332)\n    at Kl (/usr/lib/node_modules/m68k-lsp-server/out/server.js:302:2915)\n    at /usr/lib/node_modules/m68k-lsp-server/out/server.js:302:3197 {\n  [cause]: TypeError [ERR_INVALID_URL]: Invalid URL\n      at new NodeError (node:internal/errors:387:5)\n      at URL.onParseError (node:internal/url:564:9)\n      at new URL (node:internal/url:644:5)\n      at new Request (node:internal/deps/undici/undici:5444:25)\n      at Agent.fetch2 (node:internal/deps/undici/undici:6242:25)\n      at Object.fetch (node:internal/deps/undici/undici:7076:20)\n      at fetch (node:internal/bootstrap/pre_execution:199:25)\n      at /usr/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:15192\n      at /usr/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.js:1:15413\n      at new Promise (<anonymous>) {\n    input: '/usr/lib/node_modules/m68k-lsp-server/node_modules/web-tree-sitter/tree-sitter.wasm',\n    code: 'ERR_INVALID_URL'\n  }\n}\n\nNode.js v18.7.0\n"

So something must be different when started through that shell script...

One thing I just noticed in the stack, not sure if it's relevant: this seems to be complaining about the tree-sitter.wasm. I suspect that's not involved in the test scenario above - or is it?

Ah ok it looks like the same problem in this file too. This comes from upstream in the tree-sitter package so I'd imagine updating to the latest version should sort it.

Looks like that was wishful thinking - there's no fix released upstream as yet:
https://github.com/tree-sitter/tree-sitter/issues/1765
I should be able to build it myself and bundle it. Failing that we could go with the --no-experimental-fetch fix, but I didn't really want to break compatibity with older node versions.

No worries then - I have a workaround right now. Can we a few days for the real fix ;)
Thanks!


Missing access to simulation history

nsims
https://jira.jpl.nasa.gov/browse/AERIEQS-364
Moderate
No evidence of past simulation runs.

addressed along with temporal subset sim design


Yatin: Watch fukatsoft.com

Yatin requests the watch of the watch_keyword fukatsoft\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

fukatsoft\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


DMTF validator Tools for CI

Using https://github.com/DMTF tools

[x] Redfish-Service-Validator
[ ] Redfish-Service-Conformance-Check
[ ] Redfish-JsonSchema-ResponseValidator
[ ]  Redfish-Reference-Checker

Help plug in to CI once openBMC is fully complaint.

Redfish Service validator  https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/18652/


Support read from file when persistent memory cache allocation failed for parquet file format

What changes were proposed in this pull request?
It can transfer data that read from file to column batch when cache allocation failed. It can ensure the executor won't be killed when exception happen.
Design Doc:
https://docs.google.com/document/d/10ju6ik2lTU-bxATpkVYHZplh2wzve3ZFLsGy6Efbwv8/edit?usp=sharing
This is relate to #1068
How was this patch tested?
ET

@LuciferYang
How about merging  these stability  patches to Master Branch?
#1076 #1077 #1097 #1098


Keep version path for old versions

Fixes #3069
Description
Fixes the fix by using document.URL instead of window.location
How was this change tested?

Running locally

Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@rothgar please feel free to reopen if you disagree.


It failed to search by using the filter with GB18030 characters in Services and Applications view.

Stratos Version

4.4.0
Frontend Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] npm run start
[ ] Other (please specify below)

Backend (Jet Stream) Deployment type

[ ] Cloud Foundry Application (cf push)
[x] Kubernetes, using a helm chart
[ ] Docker, single container deploying all components
[ ] Other (please specify below)

Expected behaviour
Can use the filter with GB18030 characters to search in Service.
Actual behaviour
It failed to search by using the filter with GB18030 characters in Service.
Steps to reproduce the behavior

Create a User Provided Servce and input the name with GB18030 characters, for example: 'TrafficServive€酮خد㐁ᠡꀈ༑㘚郂'

In Search by name, type 'traffic' to search
Got an entry, so this service can be found successfully.
In Search by name, copy GB18030 characters  '€酮خد㐁ᠡꀈ༑㘚郂' to search,

Cannot locate the correct service.

Log output covering before error and any error statements
Insert log hereCopy

In step3, use English characters to search, it can get the returned entry.

Note:
After the step4,  English characters will be also failed to search. You need to refresh the web page to continue English characters search.

Detailed Description

Context

Possible Implementation

<EMAIL_ADDRESS><EMAIL_ADDRESS>Could you help to assign it to the related developer for fixing？ Thanks！

The issue is also reproduced in Applications view. Please help to fix together. Thanks!

Created an internal git issue: https://github.ibm.com/CFMigrationRuntime/todo_issues/issues/215 to help devs track the issue


Midi Context Error

https://github.com/nlaha/godot-midi-4.0/blob/f61646b7f6ca09e78d5801e82d45e1c84a6c7153/game/addons/godot_midi/midi_import_plugin.gd#L51
This line keeps bringing up a midi context error that impedes the importing process. There isn't a gdscript version of the MIDI.cs file.

Sorry for the late response, I'm just now getting around to working on this project again. I think this might be for the C# version of godot-midi which is now deprecated. You can use this version with C# as the core content is all built in C++ with GDExtension.


Regression: some other things are broken at startup with syntax on

Description
I noticed some things such as treesitter syntax highlighting and .editorconfig weren't applying at startup (when passing files as arguments to nvim).
I tracked the culprit down to this plugin and bisected the issue. The problematic commit is https://github.com/nvim-treesitter/nvim-treesitter-context/commit/2484f58384be24da375558c88402f2998193eff6. It seems reverting the function M.get() in that file fixes it.
Neovim version
0.9.5 and 0.10.0
Expected behavior
No response
Actual behavior
Things break on first read from command line.
Minimal config
local plugins = {
  ts         = 'https://github.com/nvim-treesitter/nvim-treesitter',
  ts_context = 'https://github.com/nvim-treesitter/nvim-treesitter-context',
  -- ADD ADDITIONAL PLUGINS THAT ARE _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.o.runtimepath = install_path..','..vim.o.runtimepath
end

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

vim.cmd [[syntax on]]
require("treesitter-context").setup {
}

Steps to reproduce
An easy way to repro is to have a .editorconfig file like this:
root = true

[*]
max_line_length = 99

Open a file like nvim foo.c, and run :set tw?. With ts-context enabled, this returns 0, while without it returns 99 as expected.
This doesn't repro when reading files with :e.

Figured it out.
Call chain:
https://github.com/nvim-treesitter/nvim-treesitter-context/blob/5efba33af0f39942e426340da7bc15d7dec16474/lua/treesitter-context.lua#L205
https://github.com/nvim-treesitter/nvim-treesitter-context/blob/5efba33af0f39942e426340da7bc15d7dec16474/lua/treesitter-context.lua#L161
https://github.com/nvim-treesitter/nvim-treesitter-context/blob/5efba33af0f39942e426340da7bc15d7dec16474/lua/treesitter-context.lua#L101
https://github.com/nvim-treesitter/nvim-treesitter-context/blob/5efba33af0f39942e426340da7bc15d7dec16474/lua/treesitter-context.lua#L57
https://github.com/nvim-treesitter/nvim-treesitter-context/blob/5efba33af0f39942e426340da7bc15d7dec16474/lua/treesitter-context/context.lua#L256
into neovim code:
https://github.com/neovim/neovim/blob/6c3f7e7e27a0ffcf6d58dc1f5ad2fce7e59a2d88/runtime/lua/vim/treesitter.lua#L108
https://github.com/neovim/neovim/blob/6c3f7e7e27a0ffcf6d58dc1f5ad2fce7e59a2d88/runtime/lua/vim/treesitter.lua#L39
Indeed, minimal repro with no plugins:
bufnr = vim.api.nvim_get_current_buf()
vim.fn.bufload(bufnr)
local group = vim.api.nvim_create_augroup('testgroup', {})
vim.api.nvim_create_autocmd({ 'BufNewFile', 'BufRead', 'BufFilePost' }, {
  group = group,
  callback = function(args)
    print("hello world")
  end,
})

The autocmd never fires, because it was registered after bufload() was called!
The reason why this doesn't happen with syntax off is because vim.treesitter.get_parser() can't figure out the file's language in that case, and errors out.
Solution:
diff --git a/lua/treesitter-context/context.lua b/lua/treesitter-context/context.lua
index 5339c80..aaf5ae6 100644
--- a/lua/treesitter-context/context.lua
+++ b/lua/treesitter-context/context.lua
@@ -253,6 +253,14 @@ end
 --- @param winid integer
 --- @return Range4[]?, string[]?
 function M.get(bufnr, winid)
+  -- vim.treesitter.get_parser() calls bufload(), but we don't actually want to load the buffer:
+  -- this method is called during plugin init, before other plugins or the user's config
+  -- have a chance to initialize.
+  -- They may want to register autocmds, and this would prevent them from firing.
+  if vim.fn.bufloaded(bufnr) == 0 then
+    return
+  end
+
   if not pcall(vim.treesitter.get_parser, bufnr) then
     return
   end

I'll open a PR.


enable validate fluentd ssl ca

problem:
not validate ca and hostname for fluentd test function is not the same
logic as fluentd
Solution:
enable validate ca and hostname
Issue:
https://github.com/rancher/rancher/issues/18332

LGTM

LGTM


synclet: add polling/retries to synclet client creation, get container id [ch373]

i'm not positive that the client_adaptor is the right place to put this polling code... but sometimes we are able to connect to the synclet but it's not yet up and running in such a way that it can actually accept calls to ContainerIdForPod.

just went and checked, and if we have polling in place for connecting to the client but NOT for synclet.ContainerIdForPod, we fail with:

failed to get deployInfo: syncletClient.GetContainerIdForPod (pod = fortune-857c595d7d-f9qdf): error returned from synclet.GetContainerIdForPod: rpc error: code = Unavailable desc = transport is closing


Issue 153

can you take a look at the conflicts, im not familiar with the changes that are conflicting. Otherwise everything looks good and functions fine, just gotta resolve those before github lets you merge


react native maps showsUserLocation not displayed when development apk is built , but running fine in expo go

Summary
when using the development build in the simulator the showsUserLocation feature is not working. but when i use expo go showsUserLocation works just fine.  has anyone ran into this issue?
Reproducible sample code
import { View } from "@/components/Themed";
import { Ionicons } from "@expo/vector-icons";
import React, { useState, useEffect } from "react";
import {
  StyleSheet,
  FlatList,
  TextInput,
  Button,
  TouchableOpacity,
} from "react-native";
import MapView, { PROVIDER_GOOGLE } from "react-native-maps";
import { YStack, Text } from "tamagui";
import { router } from "expo-router";
import { Link } from "expo-router";

export default function HomeScreen() {
  // State for search query
  const [searchQuery, setSearchQuery] = useState("");

  // Example function to handle search - adjust based on your data fetching logic
  const handleSearch = () => {
    console.log("Search for:", searchQuery);
    // Implement search functionality here
  };

  const INITIAL_REGION = {
    latitude: 43.038902,
    longitude: -87.906471,
    latitudeDelta: 44,
    longitudeDelta: 44,
  };

  return (
    <YStack flex={1}>
      <View style={styles.searchContainer}>
        <TextInput
          style={styles.searchInput}
          onChangeText={setSearchQuery}
          value={searchQuery}
          placeholder="Search for wings..."
        />
        <TouchableOpacity style={styles.searchButton} onPress={handleSearch}>
          <Ionicons name="search" size={24} color="white" />
        </TouchableOpacity>
      </View>
      <View style={styles.container}>
        <MapView
          showsMyLocationButton
          showsUserLocation={true}
          initialRegion={INITIAL_REGION}
          provider={PROVIDER_GOOGLE}
          style={StyleSheet.absoluteFill}
        />
      </View>
      <TouchableOpacity
        style={styles.addButton}
        onPress={() => router.navigate("/add-review")} // Adjust the navigation path as needed
      >
        <Ionicons name="add-circle" size={64} color="blue" />
      </TouchableOpacity>
    </YStack>
  );
}

const styles = StyleSheet.create({
  header: {
    fontSize: 30,
    fontWeight: "bold",
    marginBottom: 20,
    textAlign: "center",
    color: "#333",
  },
  searchContainer: {
    flexDirection: "row",
    alignItems: "center",
    // marginHorizontal: 10,
    // marginBottom: 10,
    // backgroundColor: "#fff",
    borderRadius: 20,
    // paddingHorizontal: 10,
    // shadowColor: "#000",
    shadowOffset: { width: 0, height: 2 },
    shadowOpacity: 0.2,
    shadowRadius: 2,
    elevation: 2,
  },
  searchInput: {
    flex: 1,
    height: 40,
    fontSize: 16,
  },
  searchButton: {
    padding: 10,
    backgroundColor: "#007BFF",
    borderRadius: 20,
    marginLeft: 5,
  },
  container: {
    flex: 1,
    paddingHorizontal: 10,
  },
  addButton: {
    position: "absolute",
    right: 7,
    bottom: 70,
    // backgroundColor: "#fff",
    // borderRadius: 30,
    // padding: 10,
    elevation: 5,
  },
});

Steps to reproduce
run npx expo run:ios
Expected result
to see the users location on the maps
Actual result
no user location. works fine in expo go
React Native Maps Version
1.10.0
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.73.6
What version of Expo are you using?
SDK 48
Device(s)
iphone 15 pro ios 17.2
Additional information
No response

Any news?

Yes!. turns out i was using a react native bare firebase sdk when i should have been using the web based sdk

Still relevant


Dockerfile currently does not build correctly due to missing isolated-vm dependency

What do you want to improve?
After upgrading to backstage 1.15.0, the required isolated-vim native dependency is not currently installed in the Dockerfile. This results in the built image not running properly.
What is the current behavior?
When the built image is run in a container, the following error occurs:
node:internal/modules/cjs/loader:1078
  throw err;
  ^

Error: Cannot find module './out/isolated_vm'
Require stack:
- /opt/app-root/src/node_modules/isolated-vm/isolated-vm.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /opt/app-root/src/packages/backend/dist/index.cjs.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/opt/app-root/src/node_modules/isolated-vm/isolated-vm.js:1:18)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/opt/app-root/src/node_modules/@backstage/plugin-scaffolder-backend/dist/cjs/ScaffolderEntitiesProcessor-d9bc7a90.cjs.js:20:18)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/opt/app-root/src/node_modules/isolated-vm/isolated-vm.js',
<EMAIL_ADDRESS><EMAIL_ADDRESS>    '/opt/app-root/src/packages/backend/dist/index.cjs.js'
  ]
}

Node.js v18.14.2

What is the new behavior?
The built image will run properly.
:warning: Is this a breaking change?
Put an x in the boxes that apply

[ ] Yes
[ ] No
[x] Don't know

It appears the upstream has just updated the documentation regarding Dockerfiles for this issue.
https://github.com/backstage/backstage/pull/18612#discussion_r1257392564

Reopening since https://github.com/janus-idp/backstage-showcase/pull/371 hasn't been tested in the downstream.

Closing in favor of https://github.com/janus-idp/backstage-showcase/issues/373


chore: new fluid tokens

Description
POC for new fluid tokens

/ok-to-test

/ok-to-test

/ok-to-test


Allow !HostSNI in TCP routers

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
 For those custom domains, my backend does SSL termination by itself.
So I wanted to have a dynamic config like this:
http:
  services: ...
  routers:
    app:
      rule: 'Host(`product.com`)'
      service: 'frontend'
      tls:
        certResolver: 'lets-encrypt'

tcp:
  services: ...
  routers:
    customDomains:
      rule: '!HostSNI(`product.com`)'
      service: 'backend'
      tls:
        passthrough: true

However, I get told that !HostSNI is not a valid rule.
How can I achieve this in Traefik?

keywords: negate sni, negate hostsni

Nevermind, I see this is implemented in https://github.com/traefik/traefik/pull/8182.


Update CHANGELOG

Added a statement to let folks know they shouldn't build Hypre in GPU mode yet.

I'll incorporate this directly in memory-dev


Remove last logs to ensure flakiness is now corrected #3584

The pr is no more flaky since almost 4 weeks. Let's remove the last logs to ensure flakiness is fixed.


build_examples.py need to support mdns option

Problem
scripts/build/build_examples.py does not have an option to specify which mDNS option the example app should be build with. Currently builds default to use minmdns.
For certification we need to build apps with platform option to use avahi on the linux platform.
https://github.com/CHIP-Specifications/chip-certification-tool/issues/507

I took a brief look, it seems like HostBuilder in host.py has a use_platform_mdns option, it just needs to be exposed as a Variant in targets.py.

@andy31415


DefaultCssErrorHandler class logged to stdout

I couldn't yet figure out where but at some place there must be some sort of debug logging left, I see a couple of
com.gargoylesoftware.htmlunit.DefaultCssErrorHandler@54478411

in my console output. Looks like some System.out.println(someObject).
HtmlUnit 2.43.0 - hmtlunit-driver 2.43.1.
/edit: even with SilentCssErrorHandler in place

https://github.com/HtmlUnit/htmlunit/pull/215 :)

https://oss.sonatype.org/content/repositories/snapshots/net/sourceforge/htmlunit/htmlunit/2.44.0-SNAPSHOT/ from Sep 6th fixes this indeed - thanks!


Fixes bytes issue in get_condor_version

This PR fixes a bug in get_condor_version() where bytes strings weren't handled properly.
Closes #117

@jrbourbeau when do you plan to issue a new release on pypi? I'm writing some documentation for a project that relies on this, but requires this bug fix and would prefer to avoid instructing people to clone from the source. Thanks.

Thanks for asking @GregoryAshton :) I can do a new release of PyCondor on pypi and conda-forge sometime tomorrow

@GregoryAshton  just did a new release. Should be available on PyPI now


Add tests for ronin-install.sh using docker

Add tests that run ronin-install.sh inside a docker image.

This can be closed now that we have GitHub Actions using containers.


FFM-11212 Upgrade FF Go SDK Code table

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
Adds new SDK Code to FF Golang SDK

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6622562fb03528c5a84b8807--harness-developer.netlify.app


Supermodel generator should set Type.connection

Generator should be updated to be like: https://github.com/donejs/bitcentive/blob/staging/public/models/os-project.js#L18.

Closed by https://github.com/donejs/generator-donejs/pull/197.


Collection method for associative, but not commutative, reductions

Not sure how possible this is, but I'd like to be able to use parallel iterators with non-commutative reduction functions (e.g., collecting error messages in a deterministic order).
Maybe best to use .enumerate() and .sort() a Vec populated by the parallel iterator?

I don't know if it's promised, but the current implementation should actually preserve order in the reductions, just with associative differences as you note.  This is a natural implication of the way the jobs are split recursively and then joined as it returns.

I believe that in https://github.com/nikomatsakis/rayon/pull/120 I went ahead and promised that the order would be deterministic when doing reduce or fold.

Hmm, the new reduce says just associative, but reduce_with still says commutative too.  Then sum, mul, min, and max all mention commutative operators.

@cuviper well-- consistency is a lot to ask =)
In any case, I feel all right about just requiring associativity.

Are there tests for just-associative reduction functions (String::push?) already?

Using collect into any of the ordered collections will exercise associative non-commutative reduce.  Look at their FromParallelIterator implementations.
Any further question about this?  Otherwise, I think we can close this issue.

Ok, I don't think we have any plain mathematical tests of this, but all of the collection and string stuff mandates that it works this way.  Also, find_first et al. would make no sense if we didn't maintain order.


Bump mypy version

This is an attempt to fix the CI failures.

Yikes, I didn't realize it was that far behind. Thanks for the PR!


Add UBI token

Token Address : 0xdd1ad9a21ce722c151a836373babe42c868ce9a4
Token Name: Universal Basic Income
Token Decimals: 18
Token Symbol: UBI
Website: https://www.proofofhumanity.id/
Telegram: https://t.me/proofhumanity
Twitter: https://twitter.com/proofofhumanity & https://twitter.com/Kleros_io & https://twitter.com/DemocracyEarth
Etherscan: https://etherscan.io/token/0xdd1ad9a21ce722c151a836373babe42c868ce9a4
Github: https://github.com/Proof-Of-Humanity & https://github.com/DemocracyEarth/ubi

+1 to this pull.


Time Limit Exceeded (Level 6)

Anyone faced a similar issue? Thanks!

it means somewhere in your code there is a infinite loop,  i would suggest having System.out.println to see exactly where the error is repeating

Can consider keeping a lookout for your waiting queue implementation (ie. adding to queue when you shouldn't have), as that was the source of my infinite loop issue.

Can consider keeping a lookout for your waiting queue implementation (ie. adding to queue when you shouldn't have), as that was the source of my infinite loop issue.

May I ask how did you solve the problem? Do you add the queue in Arrive event class?

I also keep meeting this. Take a few steps back and recode. It worked for me

Hi Brian, did you manage to solve this? I'm getting the same error as well :')

Hi! you can check whether your server state is updated properly in each event class. instead of using this.server to get the server try using the shop to get that particular server that you want instead. I had this problem too and i used the shop's server instead of using this.server and it worked for me.


[Addition]: Gamer with hotspots that only witness each other

Hotspot b58 Addresses
11e3TpC82t6D9HDh4QfGL1aBoAYf9p4wm1KGDfpbtaRYqMXq4Qk
11ibXvuvDq7jXTRjUmXHtARNUJyYeX28rTB8y6P4s4EfDLX3Rug
112eLWoxYyHohJG6oJ6Uemntcq77WWs9FXmdSPogB81YDEJiKn2c
11ojaHUDEkhn5ZvnjiwehLWn7qS37pUd1zhXXaqhbxhR7qYYgf3
11YRUMm3XmRzeyqhXUVn9H64zAXKMiDZVJG4ZnYawo5W6RBcJ5i
11uY5GSzYUemqb551Q7H8sbrgG9t4k5fd2dQUwzrbx2gbN2XA2
11FU3TuLjWyc2D3Arg9tXL2g1okRT9enKougyKFGpQmL5oAHpV3
11FyeBewvyFp87taBvk8LRzhGYSEgCDqucEfiMshUgVbwX4xc3x
Discord Handle
Fritsels#9999
Reason(s)
99% of all the hotspots above only witness each other with similar RSSI and SNR

Indeed the values are too good (better than -100dbm RSSI and +5db SNR) for the supposed distances (>5km). And they only beacon and witness other hotspots in the wallet. They are very likely all in the same room with some signal dampening on the antennas.


Connecting to Amazon MQ RabbitMQ Instance

I'm looking for any information that will help me connect to my Amazon MQ RabbitMQ instance. You have to use TLS to connect to these instances. I plan on deploying my app via a docker image, and in other apps I've had to use the rustls TLS crate in order to get them to compile, so I'm trying to use the rustls feature of lapin in order to connect. This is where I'm at so far:
let uri = AMQPUri {
            scheme: AMQPScheme::AMQP,
            authority: AMQPAuthority {
                userinfo: AMQPUserInfo {
                    username: "my_username".into(),
                    password: "my_password".into(),
                },
                host: "{my-rabbitmq-hostname}.mq.us-east-2.amazonaws.com".into(),
                port: 5671,
            },
            vhost: "/".into(),
            query: AMQPQueryString::default(),
        };

I'm not sure what the query field is for, so I just tried the default one. When I try to connect using this uri, I get the following error:
IOError(Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) })
If I try to follow along with the TLS example and parse a url to get a uri:
let url = "ampq:://{my_broker_id}.mq.us-east-2.amazonaws.com:5671";
let uri = url.parse::<AMQPUri>().unwrap();

I get the following error:
Invalid URL: 'ampq:://{my_broker_id}.mq.us-east-2.amazonaws.com:5671'"
Has anyone had success in using lapin to connect to AmazonMQ based RabbitMQ instances? Is it something with the query that I need to configure? I've gotten a python script to connect to my RabbitMQ instance and I didn't need to provide any certificates or anything, so I'm pretty sure that's not necessary. The only TLS options I see on the amqprs library require you to provide certificates, so I don't think I can use that crate. I'd like to use lapin if at all possible, since I prefer its API.

I also tried copying the TLS example exactly. I get this error when using native-tls:
IOError(Custom { kind: AlreadyExists, error: "already a TLS stream" })
I'm copying the example from here: https://github.com/amqp-rs/lapin/blob/main/examples/custom_tls_connection.rs
This happens when I manually build the uri. I cannot use the parse() function with an amazon url for some reason.

Problem solved. Heres the updated code:

Problem solved. Here's the updated code:
let connect = move |uri: &AMQPUri| {
        let conn = uri.connect().and_then(|stream| {
            let connector = RustlsConnector::new_with_native_certs().unwrap();
            // Perform here your custom TLS setup, with tls_builder.identity or whatever else you need
            stream.into_rustls(&connector, &uri.authority.host)
        });
        conn
    };

I had to use RustlsConnector::new_with_native_certs() instead of ::default. I also had to use scheme: AMQPScheme::AMQP in the uri. Trying to use AMQPScheme::AMQPS as the scheme did not work, even though the amazon host starts with ampqs://

Note that enabling the rustls-native-tls feature should be the same as this

(Context for the AMQP VS AMQPS: if you use amqps, lapin does the tls itself, if you use amqp it doesn't. Since you're doing the TLS yourself here, that's why you have to use amqp


Cannot read property "seed" of null

@mendsalbert can you give some context of the error? Which example are you using? Can you also write the steps to reproduce the error?

Closing as i cannot reproduce it. I'll reopen if more info is provided.


wip: new(ci): add a release-body CI for drivers releases.

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area CI
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR adds a new pipeline to generate github release body for driver tags.
The release-body is autogenerated from latest tag diff; moreover, kernel testing matrixes are prepended, so that each driver release is quickly linked to its kernel testing matrix results.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @LucaGuerra

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This needs to be fully tested, of course, but should work just fine (and, after all, it is not a release blocking CI, therefore none of value would be lost if it breaks!)

/milestone next-driver

Ok master CI is passed and release-body worfklow did not trigger: https://github.com/falcosecurity/libs/actions/workflows/release-body.yml

/milestone 5.1.0+driver


Verification

Sorry, I'm hoping someone can point me in the right direction.
I want to verify a users email and then redirect to my app.
Is it possible to verify with stormpath directly then redirect to my login page? The Workflows and emails page in the stormpath ui only has Link Base URL which I guess means I have to provide the route for verification myself?
How do I do this using the JSON API stateless version of the server. Do I need to use the nodejs sdk?
Is the client object and tenant object from that sdk available in express-stormpath. It seems the verifyEmail function is only available on the tenant object.
I think I'm missing something.
Cheers,
Adam

Hey @Adam-Burke! If you're using express-stormpath, all you need to do is set the link base URL to http://localhost:3000/verify, and then enable that route in the Stormpath config section in your server file:
app.use(stormpath.init(app, {
  ....
  web: {
    verifyEmail: {
      enabled: true,
      nextUri: "/login"
    }
  }
});

For future reference, you can configure a whole mess of things in app.use(stormpath.init...). This is a good place to start: https://docs.stormpath.com/nodejs/express/latest/configuration.html. It also links to 'Web Configuration Defaults' which contains a full list of the things you can customize: https://github.com/stormpath/express-stormpath/blob/master/lib/config.yml.
LMK if this helps or if you have any follow-up q's!

Yeah I placed that config in but it is just is a missing route on the server. Doesn't that only work if you are using express-stormpath as traditional web app or spa? I'm only using it for auth and to dispense json.
The localhost:3001 server is just my localhost dev ur where my app is being servedl. I'm serving the html seperately from the express-stormpath server. They're on different ports but cors is enabled.
expand: {
  customData: true,
  groups: true,
  groupMemberships: true,
  providerData: true
},
web: {
 produces: ['application/json'],
 verifyEmail: {
    enabled: true,
    nextUri: 'http://localhost:3001/login'
 }
}

@Adam-Burke One thing to note is that the email verification workflow also requires the whole thing to be enabled in the Directory used by your application. You can do this in the dashboard in api.stormpath, under Directory/Workflows & Emails. Just ran into this myself and figured it might help.


Update to latest<EMAIL_ADDRESS>blueprint.

Note: this includes updating to Node 4+, which will require a 0.6.0.

Tracking the caching failure that required 8ffa49f in https://github.com/ember-cli/ember-cli-htmlbars-inline-precompile/issues/95.

Turns out that we were already using ember-cli-babel@6 (since version 0.5.3) so this won't need to be a breaking change release at all...


Packet provider: project-id required

In the Packet provider, if you omit the --project-id flag, you get
a 404 error when you attempt to create the machine instead of
a working machine.
https://github.com/inlets/inletsctl/issues/5#issuecomment-582791212
I think but am not 100% sure that this is also true for GCE.
Expected Behaviour
If the --project-id flag is omitted, a message should appear
stating that it's required.
Current Behaviour
Command to create a server is accepted without the --project-id flag,
and the response looks like this:
ed@iyengar:~$ inletsctl create --provider packet --access-token VBGBq525BcpXXXXXXXXXXX
Using provider: packet
Requesting host: charming-brown5 in ams1, from packet
POST https://api.packet.net/projects//devices: 404 Not found

Possible Solution
At https://github.com/inlets/inletsctl/blob/master/cmd/create.go#L156 where --project-id is parsed, introduce a check to see that it's of non-zero length if it's required for the provider.
Context
This came up in the course of a first-time test to get inletsctl running and was easy to remedy.
Your Environment

inletsctl version 0.4.4
Windows on Arm + WSL Ubuntu for arm64

Thanks for fixing this!

You're welcome. Hope it's useful to the community. I'd love to see it used more


Add short flag for workspace

I have no idea what the feature roadmap is, so adding a short flag might conflict with future plans. If it doesn't though, it'd be nice to have.

How frequent this flag is used and people are tired of typing it out.

In my workspaces, basically always since I'm running cargo t --workspace constantly.

What the most common shorthand flag is for workspace-like operation from other package manager.

I don't think pip or bundler have workspaces, but npm does and uses the -w flag:
$ npm run --help
Run arbitrary package scripts

Usage:
npm run-script <command> [-- <args>]

Options:
[-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
[-ws|--workspaces] [--include-workspace-root] [--if-present] [--ignore-scripts]
[--foreground-scripts] [--script-shell <script-shell>]

aliases: run, rum, urn

Run "npm help run-script" for more info

How -w is used for in other command line tools. This is to avoid future conflicts for a well-recognized meaning over -w.

Honestly I don't think random tool X's flag naming is relevant as they're different domains.

First off, this is a lot of requirements / design discussion in a PR when typically we ask for this to happen in an Issue before a PR  is ever created, see

https://doc.crates.io/contrib/process/index.html
https://github.com/rust-lang/cargo/blob/master/CONTRIBUTING.md

I don't think pip or bundler have workspaces, but npm does and uses the -w flag:

For an example list of other tools we sometimes consider for prior art, see cargo-add's PR

Honestly I don't think random tool X's flag naming is relevant as they're different domains.

Its very relevant on two fronts

There are common conventions that could confuse people if we appropriated one.  -f is nearly synonymous with --force that if we used it for something else, it would cause confusion.
We have a lot of overlap in functionality with various domains, so looking to other commands for flags they use could be useful to give ideas for potential flags in cargo.   For example, say this was before cargo install -f was added, we would want to look at flags and consider "would we ever have a --force flag?  Maybe we should follow conventions for it?

One resource I commonly look to is https://www.gnu.org/prep/standards/html_node/Option-Table.html#Option-Table
Some other questions

Do we use the -w short flag in any existing command such that a new command using both would run into conflicts?
Are there any other existing flags that a -w short flag would be useful for?  This is both an extension of the above question and it is important because a user might confuse the two as well.

Regarding the implementation of this, it'd be worth checking the PR of the last major short flag we added (sadly, most of the research for what we considered when adding it was not captured in that PR or the one it references).

Maybe we should follow conventions for it?

I don't recall using a -w flag in recent memory and the gnu resource you shared uses -w for a bunch of esoteric options I'd never heard of, so I'm fairly confident in saying it's not a common flag name.

Do we use the -w short flag in any existing command such that a new command using both would run into conflicts?

Is there a command reference somewhere? Otherwise I can grep help pages.

Are there any other existing flags that a -w short flag would be useful for?

 Highly doubtful since workspaces are a core feature of cargo.

Is there a command reference somewhere? Otherwise I can grep help pages.

https://doc.rust-lang.org/cargo/commands/index.html

Are there any other existing flags that a -w short flag would be useful for?

 Highly doubtful since workspaces are a core feature of cargo.

I did not say "more useful" but "useful".  Like I said, if -w would be meaningful enough in another context, then it could be confusing as to what -w means.

How -w is used for in other command line tools. This is to avoid future conflicts for a well-recognized meaning over -w.

Honestly I don't think random tool X's flag naming is relevant as they're different domains.

Not exactly. -w is often a shorthand of --watch. Here is a summary of tools with -w in JavaScript land (and many more for newer tools). Outside of that, kubectl has -w as a shorthand of --watch. dune, a build system for OCaml, also got the same -w for watch mode. So does tsc, or TypeScript Compiler.
Just try providing some data points. Some of them are relevant tools I feel like, though that doesn't imply Cargo is going to use -w as watch mode.

Is there a command reference somewhere? Otherwise I can grep help pages.

doc.rust-lang.org/cargo/commands/index.html

Boom: https://doc.rust-lang.org/cargo/commands/cargo-update.html. We're already using -w for --workspace, so making -w universal gets extra points for consistency.

I did not say "more useful" but "useful". Like I said, if -w would be meaningful enough in another context, then it could be confusing as to what -w means.

Sure, but I can't predict the future and don't know the roadmap. That's on you guys.

-w is often a shorthand of --watch

Great point, that's a good possible future direction. So then it's up to you guys: do you think cargo will ever have a watch feature? I personally don't see much value for Rust and we already have https://crates.io/crates/cargo-watch.

Boom: https://doc.rust-lang.org/cargo/commands/cargo-update.html. We're already using -w for --workspace, so making -w universal gets extra points for consistency.

Huh, never noticed that had a --workspace flag.
However, I will not that text communication can be hard and starting with "boom" like this can come across as trying to "win an argument" when there is no argument here but trying to gather the relevant information for making the best decision for cargo (as we can't change this due to compatibility).

-w is often a shorthand of --watch

Great point, that's a good possible future direction. So then it's up to you guys: do you think cargo will ever have a watch feature? I personally don't see much value for Rust and we already have https://crates.io/crates/cargo-watch.

Watch support is being discussed at https://github.com/rust-lang/cargo/issues/9339
Again, to be clear, this doesn't mean that this will necessarily be rejected or that it is that one is more important than the other but that we need to weigh in potential ambiguity.

when there is no argument here but trying to gather the relevant information for making the best decision

Right, and the fact that a -w flag already exists is a huge seller. There's a precedent.

potential ambiguity

I think this is the key question then: if watch were to become a thing, would it be a flag or a command (like cargo-watch)? If it would be a flag, then this PR has to wait for https://github.com/rust-lang/cargo/issues/9339 to be resolved. If it'd be added as a command, then I think -w can coexist just fine. I took a look at the other linked --watch tools, and they all appear to use booleans which suggests watch as a command is fine.

the fact that a -w flag already exists is a huge seller

Actually, thinking about this a bit more, it's not unreasonable to think someone would want to run update automatically as they're editing the Cargo.toml. This further suggests that watch should be a command since otherwise it would be confusing to add to cargo update as a flag. Though I don't know the downsides of making it command.

I think this is the key question then: if watch were to become a thing, would it be a flag or a command (like cargo-watch)? If it would be a flag, then this PR has to wait for https://github.com/rust-lang/cargo/issues/9339 to be resolved. If it'd be added as a command, then I think -w can coexist just fine. I took a look at the other linked --watch tools, and they all appear to use booleans which suggests watch as a command is fine.

imo I would see watch support being a flag on select commands, like cargo check.

Actually, thinking about this a bit more, it's not unreasonable to think someone would want to run update automatically as they're editing the Cargo.toml. This further suggests that watch should be a command since otherwise it would be confusing to add to cargo update as a flag. Though I don't know the downsides of making it command.

Generally, watch mode is used during long-running tasks, like as part of an edit-build-test cycle.  I can't quite picture a long running Cargo.toml workflow for a cargo update --watch flag.

For anyone curious -w was added at the same time as --workspace to `cargo update as part of #8725.

Generally, watch mode is used during long-running tasks, like as part of an edit-build-test cycle. I can't quite picture a long running Cargo.toml workflow for a cargo update --watch flag.

Fair enough, so I think this is blocked on #9339.

Filed https://github.com/rust-lang/cargo/issues/11554


add docker-compose for a easy startup with ngrok

Thank you for this great app. I found it just before I started building one myself. But this works perfectly and fits exactly my needs.
I also made a Helm chart to deploy it on a Kubernetes cluster.
https://github.com/mms-gianni/github-action-dashboard-helm

Requested changes not made.  Closing for now...


Investigate embedded certs

See https://github.com/mitchellh/vagrant/issues/5391

Updated the ca bundle and curl!


Gracelessly handles client crash

I've been able to make this pin a cpu core to 100% and rapidly eat all RAM in the system.
I believe I'm running the latest versions of neovim-nightly and idris2-lsp, and copy-pasted the setup suggestions from the wiki.
To reproduce

Crash the client

using neovim, edit a file with "content" (case insensitive) in the filepath, and trigger the built in lsp

Close the editor
Don't kill scheme .../idris2-lsp.so

System will quickly become nonresponsive.

The "content" crash happens because in neovim/runtime/lua/vim/lsp/rpc.lua:160, they assume that messages may start with garbage, and the true message starts with a header like Content-Length: 168.
I can't find why it gets this, but at some point in the loop, the lua function parse_headers is trying to read (using i.e. src/Foo/Content/Bar.idr):
Content.Bar (/absolute/path/to/project/src/Foo/Content/Bar.idr)
Content-Length: 168

as though it were only the second line.


Failed to import wasm, even after enabling zoneless

Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
As doc guided, app.module.ts modified:
import { NgModule, provideExperimentalZonelessChangeDetection } from "@angular/core";

@NgModule({
  providers: [CurrencyPipe, provideExperimentalZonelessChangeDetection()],
  bootstrap: [AppComponent],
})
export class AppModule {}

But the error with zoneless reminding still thrown.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
✘ [ERROR] WASM/ES module integration imports are not supported with Zone.js applications [plugin angular-wasm]
apps/demo/src/pack/wasm.ts:2:22:
  2 │ ... wasm from "wasmfile.w...
    ╵               ~~~~~~~~~~~~~~

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 18.2.11
Node: 20.17.0
Package Manager: npm 10.8.2
OS: darwin arm64
Angular: 18.2.10
... animations, cdk, common, compiler, compiler-cli, core
... elements, forms, platform-browser, platform-browser-dynamic
... router
Package                         Version
@angular-devkit/architect       0.1802.11
@angular-devkit/build-angular   18.2.11
@angular-devkit/core            16.2.14
@angular-devkit/schematics      16.2.14
@angular/cli                    18.2.11
@schematics/angular             16.2.14
rxjs                            7.8.1
typescript                      5.5.4
Anything else?
No response

This appears to be an issue with the underlying package.  Direct WASM usage must use ESM imports due to the need for top-level await.  The package argon2-browser is using a CommonJS require call.  A similar issue where Vite also fails to build with the package can be found here: https://github.com/antelle/argon2-browser/issues/92.  There appears to be a potential workaround/solution mentioned in the issue that may also apply here.

This appears to be an issue with the underlying package. Direct WASM usage must use ESM imports due to the need for top-level await. The package argon2-browser is using a CommonJS require call. A similar issue where Vite also fails to build with the package can be found here: antelle/argon2-browser#92. There appears to be a potential workaround/solution mentioned in the issue that may also apply here.

@clydin Thanks!
Great information!

Closing as there does not appear to be anything actionable for the Angular CLI.


x/crypto: AcceptSecContext always given first outputToken from InitSecContext

What version of Go are you using (go version)?

go version go1.15.7 windows/amd64

Does this issue reproduce with the latest release?
I believe 1.15.7 to be the latest release, so yes?
What operating system and processor architecture are you using (go env)?
go env Output
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\jpenn\AppData\Local\go-build
set GOENV=C:\Users\jpenn\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\jpenn\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\jpenn\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\jpenn\AppData\Local\Temp\go-build470606270=/tmp/go-build -gno-record-gcc-switches

What did you do?
See this program.
This is a dumb and broken implementation of GSSAPIServer and GSSAPIClient for use with crypto/ssh, but it exposes what I think is a bug. As I understand it, InitSecContext and AcceptSecContext should be called back-and-forth, each being given the outputToken of the other. This does not appear to be what is happening. Instead it looks like AcceptSecContext is always given the first outputToken returned by InitSecContext.
What did you expect to see?

CLIENT: InitSecContext(host@HostnameSuppliedByClient, [], false): [100] true
SERVER: AcceptSecContext([100]): [50 1], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 1], false): [101] true
SERVER: AcceptSecContext([101]): [51 2], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [51 2], false): [102] true
SERVER: AcceptSecContext([102]): [52 3], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [52 3], false): [103] true
SERVER: AcceptSecContext([103]): [53 4], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [53 4], false): [104] true
SERVER: AcceptSecContext([104]): [54 5], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [54 5], false): [105] true
SERVER: AcceptSecContext([105]): [55 6], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [55 6], false): [106] true
SERVER: AcceptSecContext([106]): [56 7], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [56 7], false): [107] true
SERVER: AcceptSecContext([107]): [57 8], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [57 8], false): [108] true
SERVER: AcceptSecContext([108]): [58 9], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [58 9], false): [109] true
SERVER: AcceptSecContext([109]): [59 10], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [59 10], false): [] false
...

What did you see instead?

CLIENT: InitSecContext(host@HostnameSuppliedByClient, [], false): [100] true
SERVER: AcceptSecContext([100]): [50 1], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 1], false): [101] true
SERVER: AcceptSecContext([100]): [50 2], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 2], false): [102] true
SERVER: AcceptSecContext([100]): [50 3], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 3], false): [103] true
SERVER: AcceptSecContext([100]): [50 4], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 4], false): [104] true
SERVER: AcceptSecContext([100]): [50 5], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 5], false): [105] true
SERVER: AcceptSecContext([100]): [50 6], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 6], false): [106] true
SERVER: AcceptSecContext([100]): [50 7], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 7], false): [107] true
SERVER: AcceptSecContext([100]): [50 8], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 8], false): [108] true
SERVER: AcceptSecContext([100]): [50 9], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 9], false): [109] true
SERVER: AcceptSecContext([100]): [50 10], UsernameDeterminedByServer, true,
CLIENT: InitSecContext(host@HostnameSuppliedByClient, [50 10], false): [] false
...

apparently nothing is done with the packet received from the client
https://github.com/golang/crypto/blob/eec23a3978adcfd26c29f4153eaa3e3d9b2cc53a/ssh/server.go#L329-L356

apparently nothing is done with the packet received from the client
https://github.com/golang/crypto/blob/eec23a3978adcfd26c29f4153eaa3e3d9b2cc53a/ssh/server.go#L329-L356

Could someone take a look at bodgit's PR? The issue continues to be present in the most recent release of go & x/crypto.

Hello @9072997, @bodgit
thanks for the patch and sorry for all the time it took to respond.
The patch in principle looks correct.
However I have tried a real GSSAPI implementation and have never had more than one token exchange, the continue flag returned from AcceptSecContext is always false in my basic test case.
Can you please provide a way to test this patch in a real usage scenario so we can double check it? Thank you!

I have just open-sourced a portion of the internal project which was the motivation for the bug report in the first place (link)
Running the example program currently looks like this:
CLIENT g63Q: New Session
CLIENT: SPN: "HOST/0506TZ9SZ2"
CLIENT g63Q: InitSecContext("host@0506TZ9SZ2", [0], false): [129] true <nil>
SERVER JYUn: New Session
SERVER JYUn: SPN: "HOST/0506TZ9SZ2"
SERVER JYUn: AcceptSecContext([129]): [339] "" true <nil>
CLIENT g63Q: InitSecContext("host@0506TZ9SZ2", [339], false): [121] true <nil>
SERVER JYUn: AcceptSecContext([129]): [0] "" false negotiate.ServerContext.Update: The token supplied to the function is invalid
SERVER JYUn: DeleteSecContext(): <nil>
CLIENT g63Q: DeleteSecContext(): <nil>
panic: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none gssapi-with-mic], no supported methods remain

goroutine 1 [running]:
main.client({0xc000018630, 0x13}, {0xc00000eae0, 0xa})
        C:/Users/jpenn/Downloads/chocolatey-management-master/sshsso/examples/main.go:141 +0x336
main.main()
        C:/Users/jpenn/Downloads/chocolatey-management-master/sshsso/examples/main.go:193 +0x125
exit status 2

after updating go.mod to include the line
replace golang.org/x/crypto => github.com/bodgit/crypto v0.0.0-20210125101325-0d58e4d50014
running the program looks like this
CLIENT Ar7Z: New Session
CLIENT: SPN: "HOST/0506TZ9SZ2"
CLIENT Ar7Z: InitSecContext("host@0506TZ9SZ2", [0], false): [129] true <nil>
SERVER 7KHT: New Session
SERVER 7KHT: SPN: "HOST/0506TZ9SZ2"
SERVER 7KHT: AcceptSecContext([129]): [339] "" true <nil>
CLIENT Ar7Z: InitSecContext("host@0506TZ9SZ2", [339], false): [121] true <nil>
SERVER 7KHT: GetUsername Error: negotiate.ServerContext.GetUsername: The function requested is not supported
SERVER 7KHT: Falling back to ImpersonateUser
SERVER 7KHT: Username(): "SYSTEM" <nil>
SERVER 7KHT: AcceptSecContext([121]): [29] "SYSTEM" false <nil>
CLIENT Ar7Z: InitSecContext("host@0506TZ9SZ2", [29], false): [0] false <nil>
CLIENT Ar7Z: GetMIC([97]): [16] <nil>
SERVER 7KHT: VerifyMIC([97], [16]): <nil>
AllowLogin(__, "SYSTEM")
&{transport:0xc00033c000 sshConn:{conn:0xc0000a2030 user:NT AUTHORITY\SYSTEM sessionID:[16 80 26 100 49 60 27 198 137 76 127 46 25 55 245 195 243 178 135 17 120 143 98 105 24 155 160 87 44 116 192 125] clientVersion:[83 83 72 45 50 46 48 45 71 111] serverVersion:[83 83 72 45 50 46 48 45 71 111]} mux:<nil>}
TrueUsername: "SYSTEM"  ClaimedUsername: "SYSTEM"
SERVER 7KHT: DeleteSecContext(): <nil>
SERVER: New connection from "[fe80::2c45:f331:c01d:f57c%Ethernet]:30845"
CLIENT Ar7Z: DeleteSecContext(): <nil>
Hello NT AUTHORITY\SYSTEM

@9072997 thank you!

From what I've seen when using Kerberos, the Acceptor always creates just the one response token, even with mutual auth, so it's more theoretical that this issue could arise.
@9072997 I noticed your example code is using the negotiate SSPI package; I'm fairly sure if you try and use that against something like OpenSSH it won't interoperate, (I think RFC 4462 section 7.3 applies here), which is why I ended up sending the SSPI maintainer a PR to add support for the additional Kerberos SSP package. I guess it's fine if you control both ends of the SSH connection though, and obviously it's helpful here to illustrate the bug. Just thought I'd mention it as an FYI!


UrlBuilder Class

Created UrlBuilder to easily build URLs

The pytest passed on my machine...I guess this is why we're learning about configurations :sweat_smile:


OS#10665027 Stop using FrameDisplay in Asm.js + Cleanup

Stop using the FrameDisplay to store the ModuleEnvironment, it is available on the function itself instead
Add new WasmScriptFunction for WebAssembly to ease how we check if it's a WasmFunction or AsmJsFunction
Cleanup how we get the WebAssemblyMemory and/or JavascriptArrayBuffer.
Since Asm.js function can't detach the buffer anymore, keep a pointer to the ArrayBuffer in the interpreter instead of an address in the Module Environment
Some renaming to be more conform with how we call things

This change is

@MikeHolman @digitalinfinity Should I target master for this change ?

Either master or 1.7 seems fine.

Ping

@MikeHolman @agarwal-sandeep Could one of you review this please ?

            entryPoint = Js::AsmJsExternalEntryPoint;

still need this

Refers to: lib/Runtime/Base/CrossSite.cpp:339 in 53d43dc. [](commit_id = 53d43dcf72962182237979d8074d8cdb22739320, deletion_comment = False)

            entryPoint = Js::AsmJsExternalEntryPoint;

I haven't removed this...

In reply to: 327677959 [](ancestors = 327677959)

Refers to: lib/Runtime/Base/CrossSite.cpp:339 in 53d43dc. [](commit_id = 53d43dcf72962182237979d8074d8cdb22739320, deletion_comment = False)

            entryPoint = Js::AsmJsExternalEntryPoint;

Sorry, I meant you need it for asm.js, now it is only for wasm functions

In reply to: 327880657 [](ancestors = 327880657,327677959)

Refers to: lib/Runtime/Base/CrossSite.cpp:339 in 53d43dc. [](commit_id = 53d43dcf72962182237979d8074d8cdb22739320, deletion_comment = False)