Build from source v2.18.0 - countless warnings e.g. Do not pass an input_shape/input_dim argument to a layer.

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
v2.18.0
Custom code
No
OS platform and distribution
Linux Ubuntu 24.04
Mobile device
No response
Python version
13.2
Bazel version
bazilisk v1.22.1
GCC/compiler version
gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
CUDA/cuDNN version
12.6.1 / 9.4.0
GPU model and memory
NVIDIA GeForce RTX 4060 Ti
Current behavior?
I'm building from source, tag v2.18.0. Compilation succeeds with the configuration below. When used I get countless warnings. GPU seems to be used.
I'm running the basic example from the startpage of the web site and get the following output:
2024-10-29 13:56:32.470690: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:477] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1730206592.497706   98446 cuda_dnn.cc:8310] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
E0000 00:00:1730206592.505972   98446 cuda_blas.cc:1418] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-10-29 13:56:32.530518: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE3 SSE4.1 SSE4.2, in other operations, rebuild TensorFlow with the appropriate compiler flags.
/home/user/source/tf-test/venv/lib/python3.12/site-packages/keras/src/layers/reshaping/flatten.py:37: UserWarning: Do not pass an input_shape/input_dim argument to a layer. When using Sequential models, prefer using an Input(shape) object as the first layer in the model instead.
super().init(**kwargs)
I0000 00:00:1730206595.503757   98446 gpu_device.cc:2022] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 14163 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 4060 Ti, pci bus id: 0000:01:00.0, compute capability: 8.9
2024-10-29 13:56:36.992391: W external/local_xla/xla/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 188160000 exceeds 10% of free system memory.
2024-10-29 13:56:37.185922: W external/local_xla/xla/tsl/framework/cpu_allocator_impl.cc:83] Allocation of 188160000 exceeds 10% of free system memory.
Epoch 1/5
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1730206598.144274   98498 service.cc:148] XLA service 0x76ccf8002630 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
I0000 00:00:1730206598.144353   98498 service.cc:156]   StreamExecutor device (0): NVIDIA GeForce RTX 4060 Ti, Compute Capability 8.9
2024-10-29 13:56:38.176299: I tensorflow/compiler/mlir/tensorflow/utils/dump_mlir_util.cc:268] disabling MLIR crash reproducer, set env var MLIR_CRASH_REPRODUCER_DIRECTORY to enable.
I0000 00:00:1730206598.266340   98498 cuda_dnn.cc:529] Loaded cuDNN version 90400
I0000 00:00:1730206600.512484   98498 device_compiler.h:188] Compiled cluster using XLA!  This line is logged at most once for the lifetime of the process.
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 7s 2ms/step - accuracy: 0.8608 - loss: 0.4798
Epoch 2/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9552 - loss: 0.1478
Epoch 3/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9674 - loss: 0.1076
Epoch 4/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9746 - loss: 0.0843
Epoch 5/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9777 - loss: 0.0713
2024-10-29 13:56:59.770413: I external/local_xla/xla/stream_executor/cuda/cuda_asm_compiler.cc:397] ptxas warning : Registers are spilled to local memory in function 'gemm_fusion_dot_34', 4 bytes spill stores, 4 bytes spill loads
313/313 ━━━━━━━━━━━━━━━━━━━━ 3s 5ms/step - accuracy: 0.9724 - loss: 0.0882
Is my build corrupt or what did I do wrong? I'm very thankful for any hint and help. Thank you!
Standalone code to reproduce the issue
Compiling from code (checkout tag v2.18.0):

./configure
You have bazel 6.5.0 installed.
Please specify the location of python. [Default is /usr/bin/python3]:

Found possible Python library paths:
  /usr/lib/python3/dist-packages
  /usr/local/lib/python3.12/dist-packages
Please input the desired Python library path to use.  Default is [/usr/lib/python3/dist-packages]

Do you wish to build TensorFlow with ROCm support? [y/N]: N
No 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.

Please specify the hermetic CUDA version you want to use or leave empty to use the default version. 12.6.1

Please specify the hermetic cuDNN version you want to use or leave empty to use the default version. 9.4.0

Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus. Each capability can be specified as "x.y" or "compute_xy" to include both virtual and binary GPU code, or as "sm_xy" to only include the binary code.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 3.5,7.0]: 8.9

Please specify the local CUDA path you want to use or leave empty to use the default version. /usr/local/cuda-12.6/

Please specify the local CUDNN path you want to use or leave empty to use the default version. /usr/include/

Please specify the local NCCL path you want to use or leave empty to use the default version.

Do you want to use clang as CUDA compiler? [Y/n]: Y
Clang will be used as CUDA compiler.

Please specify clang path that to be used as host compiler. [Default is /usr/lib/llvm-17/bin/clang]:

You have Clang 17.0.6 installed.

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -Wno-sign-compare]:

Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]: N
Not configuring the WORKSPACE for Android builds.

Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
        --config=mkl            # Build with MKL support.
        --config=mkl_aarch64    # Build with oneDNN and Compute Library for the Arm Architecture (ACL).
        --config=monolithic     # Config for mostly static monolithic build.
        --config=numa           # Build with NUMA support.
        --config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.
        --config=v1             # Build with TensorFlow 1 API instead of TF 2 API.
Preconfigured Bazel build configs to DISABLE default on features:
        --config=nogcp          # Disable GCP support.
        --config=nonccl         # Disable NVIDIA NCCL support.
Configuration finished

host:~/source/tensorflow$ bazel build //tensorflow/tools/pip_package:wheel --repo_env=WHEEL_NAME=tensorflow --config=cuda --config=cuda_wheel --config=nogcp --config=nonccl
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
WARNING: The following configs were expanded more than once: [cuda_clang, cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Reading 'startup' options from /home/user/source/tensorflow/.bazelrc: --windows_enable_symlinks
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=181
INFO: Reading rc options for 'build' from /home/user/source/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/user/source/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --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 --features=-force_no_whole_archive --enable_platform_specific_config --defi    ine=with_xla_support=true --config=short_logs --config=v2 --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visib    bility
INFO: Reading rc options for 'build' from /home/user/source/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3 --action_env LD_LIBRARY_PATH=/usr/local/cuda-12.6/lib64:/usr/local/cuda-12.6/lib64 --config=cuda_clang --action_env CLANG_CUDA_COMPILER_PATH=/usr/lib/llvm-17/bin/clang --copt=-Wno-gnu-offsetof-extensions --    -config=cuda_clang
INFO: Found applicable config definition build:short_logs in file /home/user/source/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/user/source/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda_clang in file /home/user/source/tensorflow/.bazelrc: --config=cuda --@local_config_cuda//:cuda_compiler=clang --copt=-Qunused-arguments --repo_env=HERMETIC_CUDA_COMPUTE_CAPABILITIES=sm_60,sm_70,sm_80,sm_89,compute_90 --host_linkopt=-fuse-ld=lld --host_linkopt=-lm --linkopt=-fuse-ld=lld --linkopt=-lm
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda --repo_env=HERMETIC_CUDA_VERSION=12.5.1 --repo_env=HERMETIC_CUDNN_VERSION=9.3.0 --@local_config_cuda//cuda:include_cuda_libs=true
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.tf_configure.bazelrc: --repo_env HERMETIC_CUDA_VERSION=12.6.1 --repo_env HERMETIC_CUDNN_VERSION=9.4.0 --repo_env HERMETIC_CUDA_COMPUTE_CAPABILITIES=8.9 --repo_env LOCAL_CUDA_PATH=/usr/local/cuda-12.6/ --repo_env LOCAL_CUDNN_PATH=/usr/include/
INFO: Found applicable config definition build:cuda_clang in file /home/user/source/tensorflow/.bazelrc: --config=cuda --@local_config_cuda//:cuda_compiler=clang --copt=-Qunused-arguments --repo_env=HERMETIC_CUDA_COMPUTE_CAPABILITIES=sm_60,sm_70,sm_80,sm_89,compute_90 --host_linkopt=-fuse-ld=lld --host_linkopt=-lm --linkopt=-fuse-ld=lld --linkopt=-lm
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda --repo_env=HERMETIC_CUDA_VERSION=12.5.1 --repo_env=HERMETIC_CUDNN_VERSION=9.3.0 --@local_config_cuda//cuda:include_cuda_libs=true
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.tf_configure.bazelrc: --repo_env HERMETIC_CUDA_VERSION=12.6.1 --repo_env HERMETIC_CUDNN_VERSION=9.4.0 --repo_env HERMETIC_CUDA_COMPUTE_CAPABILITIES=8.9 --repo_env LOCAL_CUDA_PATH=/usr/local/cuda-12.6/ --repo_env LOCAL_CUDNN_PATH=/usr/include/
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda --repo_env=HERMETIC_CUDA_VERSION=12.5.1 --repo_env=HERMETIC_CUDNN_VERSION=9.3.0 --@local_config_cuda//cuda:include_cuda_libs=true
INFO: Found applicable config definition build:cuda in file /home/user/source/tensorflow/.tf_configure.bazelrc: --repo_env HERMETIC_CUDA_VERSION=12.6.1 --repo_env HERMETIC_CUDNN_VERSION=9.4.0 --repo_env HERMETIC_CUDA_COMPUTE_CAPABILITIES=8.9 --repo_env LOCAL_CUDA_PATH=/usr/local/cuda-12.6/ --repo_env LOCAL_CUDNN_PATH=/usr/include/
INFO: Found applicable config definition build:cuda_wheel in file /home/user/source/tensorflow/.bazelrc: --@local_config_cuda//cuda:include_cuda_libs=false
INFO: Found applicable config definition build:nogcp in file /home/user/source/tensorflow/.bazelrc: --define=no_gcp_support=true
INFO: Found applicable config definition build:nonccl in file /home/user/source/tensorflow/.bazelrc: --define=no_nccl_support=true
INFO: Found applicable config definition build:linux in file /home/user/source/tensorflow/.bazelrc: --host_copt=-w --copt=-Wno-all --copt=-Wno-extra --copt=-Wno-deprecated --copt=-Wno-deprecated-declarations --copt=-Wno-ignored-attributes --copt=-Wno-array-bounds --copt=-Wunused-result --copt=-Werror=unused-result --copt=-Wswitch --copt=-Werror=switch --copt    t=-Wno-error=unused-but-set-variable --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxop    pt=-std=c++17 --host_cxxopt=-std=c++17 --config=dynamic_kernels --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file /home/user/source/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
DEBUG: /home/user/.cache/bazel/_bazel_user/60b540d7b9200554d741de3bca139495/external/local_xla/third_party/py/python_repo.bzl:96:14:
HERMETIC_PYTHON_VERSION variable was not set correctly, using default version.
Python 3.12 will be used.
To select Python version, either set HERMETIC_PYTHON_VERSION env variable in
your shell:
  export HERMETIC_PYTHON_VERSION=3.12
OR pass it as an argument to bazel command directly or inside your .bazelrc
file:
  --repo_env=HERMETIC_PYTHON_VERSION=3.12
DEBUG: /home/user/.cache/bazel/_bazel_user/60b540d7b9200554d741de3bca139495/external/local_xla/third_party/py/python_repo.bzl:107:10: Using hermetic Python 3.12
WARNING: The following configs were expanded more than once: [cuda_clang, cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
DEBUG: /home/user/.cache/bazel/_bazel_user/60b540d7b9200554d741de3bca139495/external/local_tsl/third_party/nccl/hermetic/nccl_redist_init_repository.bzl:73:10: Downloading and extracting https://files.pythonhosted.org/packages/df/99/12cd266d6233f47d00daf3a72739872bdc10267d0383508b0b9c84a18bb6/nvidia_nccl_cu12-2.21.5-py3-none-manylinux2014_x86_64.whl
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/zlib.net/fossils/zlib-1.3.1.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed target //tensorflow/tools/pip_package:wheel (757 packages loaded, 55850 targets configured).
INFO: Found 1 target...

Relevant log output
No response

Hi @LeeABarron ,
Thank you for raising your issue here. I noticed there may be a version compatibility problem. Although everything compiled successfully, any compatibility issues could lead to performance problems. It is best to install compatible versions. I am providing the documentation here for your reference, please review it and check all compatibility versions. Let us know if the issue persists.
Thank you!

Hi @Venkat6871
Thank you for your response and your time.
I did 2.17 before and dealt with another issue that's why I went to 2.18.
At time of build this table was not updated yet for 2.18 - so I went with the max versions of third_party\xla\third_party\tsl\third_party\gpus\cuda\hermetic\cuda_redist_versions.bzl at the time of the tag v2.18.0
I guess this mean these max versions (12.6.1 and 9.4) are "experimental" or for development only. Did I miss another way to find the max recommended versions from the code, when the table is not updated yet?
I will happily give it a whirl with 2.5.1 and 9.3 and post my results. Thank you very much.

Unfortunately exactly the same - build successful (should I post configuration?) but warnings remain:
2024-11-01 19:16:54.296179: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:477] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1730485014.331975   26232 cuda_dnn.cc:8310] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
E0000 00:00:1730485014.342833   26232 cuda_blas.cc:1418] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-01 19:16:54.382102: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE3 SSE4.1 SSE4.2, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Downloading data from https://storage.googleapis.com/tensorflow/tf-keras-datasets/mnist.npz
11490434/11490434 ━━━━━━━━━━━━━━━━━━━━ 2s 0us/step
/home/user/source/tf-eval/venv/lib/python3.12/site-packages/keras/src/layers/reshaping/flatten.py:37: UserWarning: Do not pass an input_shape/input_dim argument to a layer. When using Sequential models, prefer using an Input(shape) object as the first layer in the model instead.
super().init(**kwargs)
I0000 00:00:1730485023.031375   26232 gpu_device.cc:2022] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 14242 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 4060 Ti, pci bus id: 0000:01:00.0, compute capability: 8.9
Epoch 1/5
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1730485027.010202   26313 service.cc:148] XLA service 0x7804e00083c0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
I0000 00:00:1730485027.010277   26313 service.cc:156]   StreamExecutor device (0): NVIDIA GeForce RTX 4060 Ti, Compute Capability 8.9
2024-11-01 19:17:07.141875: I tensorflow/compiler/mlir/tensorflow/utils/dump_mlir_util.cc:268] disabling MLIR crash reproducer, set env var MLIR_CRASH_REPRODUCER_DIRECTORY to enable.
I0000 00:00:1730485027.408144   26313 cuda_dnn.cc:529] Loaded cuDNN version 90300
I0000 00:00:1730485029.842869   26313 device_compiler.h:188] Compiled cluster using XLA!  This line is logged at most once for the lifetime of the process.
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 8s 2ms/step - accuracy: 0.8568 - loss: 0.4844
Epoch 2/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9567 - loss: 0.1485
Epoch 3/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9688 - loss: 0.1038
Epoch 4/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9734 - loss: 0.0850
Epoch 5/5
1875/1875 ━━━━━━━━━━━━━━━━━━━━ 4s 2ms/step - accuracy: 0.9755 - loss: 0.0749
2024-11-01 19:17:46.978835: I external/local_xla/xla/stream_executor/cuda/cuda_asm_compiler.cc:397] ptxas warning : Registers are spilled to local memory in function 'gemm_fusion_dot_34', 4 bytes spill stores, 4 bytes spill loads
313/313 ━━━━━━━━━━━━━━━━━━━━ 3s 5ms/step - accuracy: 0.9720 - loss: 0.0944
What could I try? Thank you very much.

The warning "To enable the following instructions: SSE3 SSE4.1 SSE4.2, in other operations, rebuild TensorFlow with the appropriate compiler flags" is CPU-related and has nothing to do with the CUDA and CUDNN versions. Using -march=native as a CPU flag when you use the configure.py would do the job. For the recommended CUDA and CUDNN versions, there are in the file .bazelrc of the repo, search for the line "build:cuda_clang_official --repo_env=HERMETIC_CUDA_VERSION" and "build:cuda_clang_official --repo_env=HERMETIC_CUDNN_VERSION" for your rc. The other warnings are just there and don't seem to impact training

Hi @LeeABarron ,
Apologies for the delay. For the similar issue one more issue was raised and still it is in open state.  please follow them for further updates. I am providing the link to that issue here for your reference.
Thank you!


export ObjectStore::set_schema_version()

export set_schema_version() for https://github.com/realm/realm-java/issues/3417

please review this @realm/java
There is one failing test case. I'm ignore it for now since the case is failing in other PRs (for example in #141 , https://ci.realm.io/job/ObjectStore Pull Request/314/)

Apart from a little comment 👍

:+1:


Type functions in builder

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[x] Documentation added for any new functionality
[ ] Entry added to UNRELEASED.md for any new functionality

Experimental builder:
Instead of using a schema-based approach, each (TNT) operator is associated with a type-computation function, that synthesizes a return type from input types (or, in rare cases, using value hints).

Work has been done to integrate this and I think it can be closed now.


Missing gfx/sprites.h

make: *** No rule to make target 'src/gfx/sprites.h', needed by 'obj/src/main.c.bc'.  Stop.

You need to run make gfx before make.


Error import dynamic module

I am compiling torchvision from source today. The installation seems fine but the following code gives me error. I am compiling in virtual env with python 3.6. The error is replicated across all of my devices. Also is there an estimation when torchvision_nightly will be back?
`import torch
from torchvision.models.detection import maskrcnn_resnet50_fpn
model = maskrcnn_resnet50_fpn(pretrained=True)
model.eval()
input_shape = (3, 300, 300)
x = torch.rand(input_shape)
model_input = [x]
out = model(model_input)`
The error is
  File "/home/boyuan/Projects/experiment/env/lib/python3.6/site-packages/torchvision/extension.py", line 12, in _lazy_import     from torchvision import _C as C ImportError: dynamic module does not define module export function (PyInit__C)

What version of PyTorch are you using?
Also, did you do python setup.py clean before rebuilding torchvision?

What version of PyTorch are you using?
Also, did you do python setup.py clean before rebuilding torchvision?

I am using pytorch 1.1 on the official website with cuda10. I tried setup.py clean and it did not work.

@buoyancy99 can you try switching to the v0.3 branch and compiling to see if it works for you?

@buoyancy99 can you try switching to the v0.3 branch and compiling to see if it works for you?

I tested the branch and it worked on the same piece of code

Ok, I think TorchVision master is not compatible with PyTorch 1.1 anymore, and you'd need a nightly version of PyTorch so that it works.


[Divider] - Vertical Dividers not working on Chrome Win8

Steps to Reproduce

Goto Divider section
Scroll to vertical divider section

Expected
The Divider should be placed between each section
Result
The vertical dividers all stack on top of each other on the far left

Running Windows 8, Chrome Version 54.0.2840.99 m

Known issue I'm afraid, #4342.
There's no workaround at the framework level for the the time being.
View Chrome Issue 633011
https://github.com/w3c/csswg-drafts/issues/401


Add support for 8BitDo SN30 Pro on Mac OS X.

Add support for the 8BitDo SN30 pro controller on Mac OS X.

good stuff


permit_actions/forbid_actions doesn't accept single item array

Is there a reason that the permit_actions and forbid_actions refuse an array of a single item?
I understand their is the singular case for each which accepts a value directly. However, it seems unnecessary to throw a validation error for a single item array. As long as they provided value is an array and is not empty, it seems like it should be accepted.
I'd like to see this validation taken out as I find it pointless to need to switch the method name when transitioning from a single to multiple (and vice versa) actions. It'd be great to simply use the plural method in all cases so I can easily add/remove arguments.
I'll happily get a PR in for a change. I wanted to make sure I understood the reasoning behind the current implementation before I went to change it.
Thanks!

It was done this way with the aim of making it easier for the reader to translate line into English in their head.
"The article policy is expected to permit the action: create" and "The article policy is expected to permit the actions: create and update" sound natural.
"The article policy is expected to permit the actions: create" sounds less natural.
Admittedly, this is a small problem for the reader, but it does help a little I think. Programmers often spend more time reading code than writing it. That being said, if you're still unconvinced, feel free to send a PR removing the restriction.

I think having both options makes a lot of sense from a readability perspective. It just seems unnecessary to enforce singularity on the plural action.
I'll look to submit a PR in the next couple of days.

PR merged and released as part of Pundit Matchers 1.4.0.

Wonderful!  Thank you very much!

I'll need to revisit this. It looks like merge of #13 had some conflicts that break this newly introduced functionality.
When a single item array is provided to a plural matcher, the matcher always fails. The singular version works as expected.

I see what happened there. The tests should have failed as well, but because of the JRuby Travis issue we didn't pick up on that. This is all fixed in version 1.4.1.

Sweet, thanks for taking care of that so quickly!


⚠ Bofrost.de has degraded performance

In 7e8d9ed, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1139 ms

Resolved: Bofrost.de performance has improved in 61a46ab after 6 minutes.


Static events don't play nice with -optimize

Static events need to be implemented on the factory to work reliably, but -optimize is all about forwarding the projection directly to the implementation class and bypassing the factory.

Moved to https://github.com/microsoft/cppwinrt/issues/364


[ENHANCEMENT] Make templating in values.yaml possible when setting host, replicas and pvc size (different settings for different environments with same values.yaml)

Which problem does the PR fix?
https://github.com/camunda/camunda-platform-helm/issues/1648
What's in this PR?
Treat the corresponding values as {{ tpl .Values.xxx . }} instead of simply {{ .Values.xxx }}
Example:
global.ingress.host: "{{ .Values.global.environment }}-camunda.your-domain.com"
global.identity.keycloak.url.host: "{{ .Values.global.environment }}-keycloak.your-domain.com"

connectors.replicas: "{{ if eq .Values.global.environment \"Dev\" }} 1 {{ else }} 2 {{ end }}"
zeebeGateway.replicas: "{{ if eq .Values.global.environment \"Dev\" }} 1 {{ else }} 2 {{ end }}"

zeebe.pvcSize: "{{ if eq .Values.global.environment \"Dev\")  }}5Gi{{ else }}32Gi{{ end }}"

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[x] There is no other open pull request for the same update/change.

After opening the PR:

[x] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[x] Did all checks/tests pass in the PR?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Рыбковский Игорь Владимирович seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I can't run make go.update-golden-only in my environment - please run it for me if needed


Workers are not getting deployed as part of the installation process

Hello,
We are trying to deployed the required AWS Resources for an UPI installation of CP4I solution in our environment.
Using the terraform code provided by this repo, we manage to execute a successful deployement (as far as terraform is concerned) and we getting a working bootstrap node and 3 masters nodes. Also the 3 loadbalancers are deployed as well.
But we do not see the 3 workers deployed.
Could you please help us understand the issue with our deployment?
Thank you

Can you please post your log files?

Of course, more than happy to provide any information needed.
Since there are multiple logs, could you please let me know which one would be more relevant for you?

.openshift-install.log would help me out to figure out.

Hello @Praveenmail2him ,
After going through the code once again, can I please verify that the workers nodes deployment is supposed to be initiated from the master nodes right?
I am trying to analyse the master.ign but I can't find this. Am I missing something ?

Also this might be helpful as well..
var allEvents = {
  "metadata": {

  },
  "items": [
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d3609d7794ddf5",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d3609d7794ddf5",
        "uid": "b33d83b6-72fe-4e59-84c6-66ff74f5b5ca",
        "resourceVersion": "771961",
        "creationTimestamp": "2022-02-13T15:01:58Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:37:49Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OAuthRouteCheck",
      "message": "route status does not have host address",
      "source": {
        "component": "cluster-authentication-operator"
      },
      "firstTimestamp": "2022-02-13T15:01:58Z",
      "lastTimestamp": "2022-02-15T10:37:49Z",
      "count": 19542,
      "type": "Warning",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d3609e15ff7692",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d3609e15ff7692",
        "uid": "ccadb97a-10fa-46b3-b6af-644e180a8147",
        "resourceVersion": "771556",
        "creationTimestamp": "2022-02-13T15:02:01Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:36:28Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:02:01Z",
      "lastTimestamp": "2022-02-15T10:36:28Z",
      "count": 273,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d3609e5bf12b8a",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d3609e5bf12b8a",
        "uid": "2ef6e13c-962b-45c3-bcc2-566294286fc4",
        "resourceVersion": "771568",
        "creationTimestamp": "2022-02-13T15:02:02Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:36:29Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:02:02Z",
      "lastTimestamp": "2022-02-15T10:36:29Z",
      "count": 182,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360b12fb274c3",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360b12fb274c3",
        "uid": "ad3c3fc8-407d-4f52-a6fe-35adb1478d1b",
        "resourceVersion": "771806",
        "creationTimestamp": "2022-02-13T15:03:23Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:37:23Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:03:23Z",
      "lastTimestamp": "2022-02-15T10:37:23Z",
      "count": 1758,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360b131526724",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360b131526724",
        "uid": "09c21c32-1e46-4852-a7f7-94e2e17c3d1e",
        "resourceVersion": "771810",
        "creationTimestamp": "2022-02-13T15:03:23Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:37:23Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:03:23Z",
      "lastTimestamp": "2022-02-15T10:37:23Z",
      "count": 1782,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360b29b2909d9",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360b29b2909d9",
        "uid": "d2f0c0f0-5d3a-4ab3-9a7c-a793aaf33a7a",
        "resourceVersion": "771851",
        "creationTimestamp": "2022-02-13T15:03:29Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:37:29Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:03:29Z",
      "lastTimestamp": "2022-02-15T10:37:29Z",
      "count": 1761,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360b29d198e8b",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360b29d198e8b",
        "uid": "b479362a-8e69-4809-aa35-cdc0de6ad006",
        "resourceVersion": "771855",
        "creationTimestamp": "2022-02-13T15:03:29Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:37:29Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:03:29Z",
      "lastTimestamp": "2022-02-15T10:37:29Z",
      "count": 1793,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360f7096c6932",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360f7096c6932",
        "uid": "e224f582-c5c5-431b-9112-c92b1e68e3eb",
        "resourceVersion": "769126",
        "creationTimestamp": "2022-02-13T15:08:23Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:27:53Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:08:23Z",
      "lastTimestamp": "2022-02-15T10:27:53Z",
      "count": 179,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360f70b0ca70d",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360f70b0ca70d",
        "uid": "e37b077e-ee69-4260-9474-3584460b39fb",
        "resourceVersion": "769130",
        "creationTimestamp": "2022-02-13T15:08:23Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:27:53Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:08:23Z",
      "lastTimestamp": "2022-02-15T10:27:53Z",
      "count": 184,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360f835bcd3f0",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360f835bcd3f0",
        "uid": "b93cc204-5db5-4900-af1a-e1ffd40108a3",
        "resourceVersion": "769625",
        "creationTimestamp": "2022-02-13T15:08:28Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:29:26Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:08:28Z",
      "lastTimestamp": "2022-02-15T10:29:26Z",
      "count": 273,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d360f8379d8fff",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d360f8379d8fff",
        "uid": "4833c4ad-b8a0-4897-a9e1-23aea40de8a7",
        "resourceVersion": "769629",
        "creationTimestamp": "2022-02-13T15:08:28Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:29:26Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:08:28Z",
      "lastTimestamp": "2022-02-15T10:29:26Z",
      "count": 277,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d3611428abd14b",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d3611428abd14b",
        "uid": "3e356ccf-fea2-47f5-b6f4-44d6b95ef6f0",
        "resourceVersion": "771560",
        "creationTimestamp": "2022-02-13T15:10:28Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:36:28Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:10:28Z",
      "lastTimestamp": "2022-02-15T10:36:28Z",
      "count": 280,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d36114688381cc",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d36114688381cc",
        "uid": "058729ef-e229-4ef9-9f4c-1c79ba3ce7de",
        "resourceVersion": "771571",
        "creationTimestamp": "2022-02-13T15:10:29Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:36:29Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T15:10:29Z",
      "lastTimestamp": "2022-02-15T10:36:29Z",
      "count": 181,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d366b1e1ec87c7",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d366b1e1ec87c7",
        "uid": "5a76bb7f-f575-4cbb-83bb-35d2d7a234cd",
        "resourceVersion": "747055",
        "creationTimestamp": "2022-02-15T06:22:28Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T09:11:23Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\",Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: i/o timeout (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\"",
      "source": {
        "component": "cluster-authentication-operator-status-controller-statussyncer_authentication"
      },
      "firstTimestamp": "2022-02-13T16:53:23Z",
      "lastTimestamp": "2022-02-15T09:11:23Z",
      "count": 12,
      "type": "Normal",
      "eventTime": null,
      "reportingComponent": "",
      "reportingInstance": ""
    },
    {
      "kind": "Event",
      "apiVersion": "v1",
      "metadata": {
        "name": "authentication-operator.16d37d4ad5a5e106",
        "namespace": "openshift-authentication-operator",
        "selfLink": "/api/v1/namespaces/openshift-authentication-operator/events/authentication-operator.16d37d4ad5a5e106",
        "uid": "456f0942-cb58-463d-a093-b97f45609fba",
        "resourceVersion": "767713",
        "creationTimestamp": "2022-02-15T10:22:59Z",
        "managedFields": [
          {
            "manager": "authentication-operator",
            "operation": "Update",
            "apiVersion": "v1",
            "time": "2022-02-15T10:22:59Z",
            "fieldsType": "FieldsV1",
            "fieldsV1": {"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{"f:apiVersion":{},"f:kind":{},"f:name":{},"f:namespace":{},"f:uid":{}},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{}},"f:type":{}}
          }
        ]
      },
      "involvedObject": {
        "kind": "Deployment",
        "namespace": "openshift-authentication-operator",
        "name": "authentication-operator",
        "uid": "d8fadf77-52e9-4bcc-b017-e87b1046b659",
        "apiVersion": "apps/v1"
      },
      "reason": "OperatorStatusChanged",
      "message": "Status for clusteroperator/authentication changed: Degraded message changed from \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\" to \"OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready\n+OAuthServiceCheckEndpointAccessibleControllerDegraded: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": dial tcp <IP_ADDRESS>:443: connect: connection refused\n+IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server\n+OAuthRouteCheckEndpointAccessibleControllerDegraded: route status does not have host address\n+OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps \\\"oauth-openshift\\\" not found\n+WellKnownReadyControllerDegraded: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\n+OAuthServerDeploymentDegraded: deployments.apps \\\"oauth-openshift\\\" not found\n+OAuthServerRouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\n+RouteDegraded: Route is not available at canonical host oauth-openshift.apps.ocp4.001.external.ocp.xxx.demos.aws.xxx.xxx: route status ingress is empty\",Available message changed from \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).\n+OAuthServiceEndpointsCheckEndpointAccessibleControllerAvailable: Failed to get oauth-openshift enpoints\n+OAuthServiceCheckEndpointAccessibleControllerAvailable: Get \\\"https://<IP_ADDRESS>:443/healthz\\\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\n+WellKnownAvailable: The well-known endpoint is not yet available: failed to get oauth metadata from openshift-config-managed/oauth-openshift ConfigMap: configmap \\\"oauth-openshift\\\" not found (check authentication operator, it is supposed to create this)\" to \"ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node.


ImportWarning when grabbing a FakeBackend

Environment

Qiskit Terra version: 0.22rc1
Python version:
Operating system:  Ubuntu 22.04

What is happening?
from qiskit.providers.fake_provider import FakeMumbai
backend = FakeMumbai()

gives
<frozen importlib._bootstrap>:671: ImportWarning: QiskitLoader.exec_module() not found; falling back to load_module()
How can we reproduce the issue?
Run the above
What should happen?
no warnings
Any suggestions?
No response

What version of Python?

It's interesting because that code hasn't changed since 0.21.x, and I've never seen the warning. But reading the python docs on Loader  the load_module() method I used to implement the import redirect for aer has been deprecated since 3.4 and exec_module() is the recommended path forward: https://docs.python.org/3/library/importlib.html#importlib.abc.Loader
I'll take a look into this and see if I can adapt how we're using load_module() to the newer interface.

3.10.5

Oddly enough it only happens if I first import mthree before grabbing the backend

But if I explicitly import AerSimulator before calling mthree there is no error again:
from qiskit_aer import AerSimulator

import mthree

fixes it

So it looks like it boils down to grabbing Cython extensions and then the FakeBackend.  Ie this causes it:

from qiskit.providers.fake_provider import FakeHanoi
from mthree.matrix import _reduced_cal_matrix
backend = FakeHanoi()

We do some trickery in Terra to make qiskit.providers.aer import paths work now that Aer doesn't inject itself into the namespace. If the first time a given module is seen is with the qiskit.providers.aer name it will trigger an import warning due to the deprecated code Matthew's accidentally used, as shown above. If the first time we see it is as qiskit_aer, then we we do see a qiskit.providers.aer name, the loader short-circuit returns the imported module without triggering the deprecated code.
The solution is what Matthew had above - we should be using load_module rather than exec_module, and it's fixable within Terra.


Fix mac popup special keys

What does the pull request do?
Special keys don't work in Popups on macOS. (Special key is anything written with modifier - even shift+1 for bang sign)
What is the current behavior?
InputManager is not initialized. But that's correct because the Window is still the key window and it receives the hotkeys.
What is the updated/expected behavior with this PR?
Keep the InputManager initialized to the parent window.
How was the solution implemented (if it's not obvious)?
I don't know if this is the correct solution in the scope of all platforms.
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes
test on other platforms
Fixed issues
https://github.com/AvaloniaUI/Avalonia/issues/14408

Popups under macOS currently don't implement any input method

@Gillibald but they can use the parent window one, can't they?

@Gillibald but they can use the parent window one, can't they?

No Popup itself needs to process the input context messages

@Gillibald I am not familiar that much with native mac code. Can you help me what I am missing here? (last commit here)
I believe the popup must be key window, right? And it must become firstResponder upon show too.
The problem is that when I click on the popup in this case it closes immediately. I can't figure out what is the problem.
This is a big problem for us because textboxes in popups do not work.

@Gillibald I am not sure how to do it properly though. I can override ShouldTakeFocusOnShow or I can make it first responder manually. In either case, the main window loses the focus and the flyout is hidden. This is the problem even now (if you click the popup it closes immediately). I couldn't find the connection between being a key window and closing on getting focus. Can you point me to the right direction here? Thanks!


Inputs shouldn't take input in canvas view

Clicking them or their labels should just select the component instead.
If they need a default pre-filled text, it should be done in the context menu.

[ ] text input
[ ] text area
[ ] search
[ ] number input

Hi @zvonimirfras @Akshat55 can i try this task ?
can you please assign to me ? aslo please add some details or screenshot for the reference

Sure, @vibh1103, go for it!
In our WYSIWG application, we don't want users to directly interact with the above elements. Meaning, we want the users to select the elements but NOT be able to select and type as you can see in the video I've posted.
https://github.com/IBM/carbon-ui-builder/assets/38994122/887803ed-4708-4e5f-a39b-ced448bbac3d
You will need to take a look at the fragment components for the components listed above.
e.g. a-text-input.tsx, a-text-area.tsx, etc.
You can most likely achieve this using css, see a-combobox.tsx.

Hi @Akshat55
I made some change in  a-text-input.tsx anda-text-area.tsx this component by making read-only property to true

is that right ?
how change looks like in the below image.

@vibh1103, that isn't ideal solution since we allow users to set the readOnly state. Enabling readOnly will also change the the component visually (Background color changes to white). To resolve this issue, do the following:

Create a css class as such:

const preventClickStyle = css`
	pointer-events: none;
`;

Pass it to the component

<TextInput className={cx(preventClickStyle, ...)} ... />

Test and make any specificity changes if needed.

Ok @Akshat55 let me try that


L4 sre

Adding in L4 SRE.
Updated Readme, bringing in feedback to cover operations in SRE space, and replace system engineer with Software Engineer naming to make it clearer. System Engineer role had been removed from the ladder

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Have some questions

I tried out this and find it very interesting, but I am not an experienced and I am confused about how to run it, when i eun the  $ GO111MODULE=on go run *.go
, It works nicely but if I were to close the console, the feed does not run.
Another question I have is, in the mutiview mode, how xan I display all the camera feeds without having to manually add them?

would you be able to help me with this? I need step-by-step guidance
On Wed, Jun 9, 2021 at 11:40 PM Andrey Semochkin @.***>
wrote:

go build *.go
create system.d script or run ./binaryname &

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/deepch/RTSPtoWeb/issues/38#issuecomment-857931003,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUNMU4EVSX55KGVOSKBGTRTTR6U7ZANCNFSM46MRG6IA
.

would you be able to help me with this? I need step-by-step guidance
…
On Wed, Jun 9, 2021 at 11:40 PM Andrey Semochkin @.***> wrote: 1. go build *.go 2. create system.d script or run ./binaryname & — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNMU4EVSX55KGVOSKBGTRTTR6U7ZANCNFSM46MRG6IA .
hi,
do these steps:

$ sudo git clone https://github.com/deepch/RTSPtoWeb
$ cd RTSPtoWeb/
if the golang-go package is not already installed:
$ sudo apt install golang-go
$ sudo go build *.go
$ ./apiHTTPChannel
open web browser http://<IP_ADDRESS>:8083

if you os Linux
go build -o RTSPtoWeb *.go
create dir's /usr/share/RTSPtoWeb/
cp RTSPtoWeb /usr/share/RTSPtoWeb/
create file /lib/system.d/system/youservicename.sercive
[Unit]
Description=RTSPtoWeb
After=network.target

[Service]
LimitNOFILE=500000
LimitNPROC=500000
Type=simple
WorkingDirectory=/usr/share/RTSPtoWeb/
ExecStart=/usr/share/RTSPtoWeb/RTSPtoWeb
Restart=always

[Install]
WantedBy=multi-user.target

service youservicename start


Misc. typos

Found via codespell -q 3 -L uint,lod,iff,pevent
(BTW, is ext/ considered 3rdparty libs ?)

yes, is ext/ considered 3rdparty libs


FileNotFoundError: [Errno 2] No such file or directory: 'datasets\LINUX\processed\LINUX_ged.pt'

Hello, is this LINUX_ged.pt downloaded in the code? How to solve it, thank you

The datasets should be automatically downloaded during loading GEDDataset. It seems that it's the issue of pyg. You can try a dry run of loading torch_geometric.datasets.GEDDataset.

在加载 GEDDataset 期间，应自动下载数据集。似乎是侏儒的问题。您可以尝试试运行加载 torch_geometric.datasets.GEDDataset。

Thank you very much for your answer, the dataset is downloaded automatically, but this file is not in it
FileNotFoundError: [Errno 2] No such file or directory: 'dataset\raw\LINUX\ged.pickle'

could you please paste the whole log of the error?

could you please paste the whole log of the error?

Traceback (most recent call last):
File "C:/Users/20825/Desktop/bioinformations/NA-GSL-main/main.py", line 211, in
trainer = GEDTrainer(args=parsed_args)
File "C:\Users\20825\Desktop\bioinformations\NA-GSL-main\trainer.py", line 34, in init
self.dataset = GraphSimDataset(args)
File "C:\Users\20825\Desktop\bioinformations\NA-GSL-main\data.py", line 25, in init
self.process_dataset()
File "C:\Users\20825\Desktop\bioinformations\NA-GSL-main\data.py", line 32, in process_dataset
self.training_graphs = GEDDataset(self.args.data_dir + self.args.dataset, self.args.dataset, train=True)
File "C:\anaconda\envs\bio_info\lib\site-packages\torch_geometric\datasets\ged_dataset.py", line 141, in init
self.ged = torch.load(path)
File "C:\anaconda\envs\bio_info\lib\site-packages\torch\serialization.py", line 771, in load
with _open_file_like(f, 'rb') as opened_file:
File "C:\anaconda\envs\bio_info\lib\site-packages\torch\serialization.py", line 270, in _open_file_like
return _open_file(name_or_buffer, mode)
File "C:\anaconda\envs\bio_info\lib\site-packages\torch\serialization.py", line 251, in init
super(_open_file, self).init(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: 'datasets\LINUX\processed\LINUX_ged.pt'

Hi, I know what's the issue.
There is a bug in the latest version of GEDDataset in pyg (file path mismatching). There is a walk-around to directly arrange the files like this and then run the code.

Hi, I know what's the issue. There is a bug in the latest version of GEDDataset in pyg (file path mismatching). There is a walk-around to directly arrange the files like this and then run the code.

This does not seem to be the problem. The required file in the error report does not exist in the file automatically downloaded by GEDDataset


problem about aen

Hi,
When I try to run aen model, I get the error "can't convert CUDA tensor to numpy. Use Tensor.cpu() to copy the tensor to host memory first." I don't know why and how to fix it. I will be grateful if I can get your reply.

fixed #37


Implement auto-assigned ticketing (#527)

Testing Netlify, mainly, but why not enjoy this nice commit. :)

Deploy preview processing.
Built with commit 80b3c2c4c1c990f0cabfccb033ae75700daaae99
https://app.netlify.com/sites/docker-docs-vnext-engine/deploys/58251d5471e20a5296e0daff

Deploy preview processing.
Built with commit 80b3c2c4c1c990f0cabfccb033ae75700daaae99
https://app.netlify.com/sites/docker-docs-vnext-engine/deploys/58251d546686745d4d54d8db

Cool, it works, closing. :)


Organize Extensions into folders

Request to be able to organize extensions into categories so they can be enabled and disabled per project. Examples of this being useful would include switching between different frameworks while still coding in JS, enabling/disabling formatters for work/personal use and theme/icon pairs that could be matched together.

/duplicate


If you block AdsBot-Google, google ads won't show your ads?

If you block AdsBot-Google, google ads won't show your ads?
Can anyone confirm this?
If so, maybe add some warning in docs?

Think you might need to clarify that slightly - google ads won't show your ads? Think you probably mean "show ads on your site." (Thats a assumption and I apologise if I have misread.)
Anyway, my understanding is that if Google AdsBot cannot crawl a site then it will not know what content is on there and I believe it needs to do that to understand what markets would be looking at that content so it can show ads on there that would be suitable for those markets.
So if you have Google Ads on your site I would be careful with any blocking as some advertisers are bound to be using AI to help them understand how their ads are performing.
Good call as there is probably a lot more nuance in this.

I mean if you want to display your ads (that link to your site) on Google's Search Engine Results Pages, then blocking AdsBot-Google is possibly not a good idea.
(This may also affect ads within your website, but I'm not sure, as I don't have any ads on my site.)

Ah yes - that makes sense!

I’d be ok to remove this agent if you’d like to issue a pull request. Google-Extended is the most important to block and explicitly AI related.

Updated here https://github.com/ai-robots-txt/ai.robots.txt/commit/af525789653bda55d80fb17dc3f51a720658d938 — also added some additional GoogleOther bots that are leveraged for internal use by Google.