[Bug] Concerns about data quality: Very serious inconsistencies between graphics and text.

I have already raised an issue and expressed that there are serious image and text inconsistencies in data_engine data. The author's reply is that cambrian only provides method reference.
But my concern is that the seriousness of the inconsistency between the pictures and texts in the data_engine part is not just whether the details of the text and pictures correspond, but that the text and pictures are not the same topic at all. I think such data cannot prove that cambrian has proposed a valuable data production tool.

Or is it that the corresponding relationship between annotation and image was recorded incorrectly when the data was uploaded? I hope the author can pay attention to this issue and double check the data quality.

Hi, thank you for raising this concern. We are looking into it


Create a command line interface for the Manage GitHub Enterprise Server API

Summary
We want to improve the experience for GitHub Enterprise Server administrators by offering a command line interface (CLI) for the Manage GitHub Enterprise Server API. This gives administrators control over their Enterprise Server instance without requiring SSH access.
Intended Outcome
Enterprise Server administrators will be able to manage their instance/s using the CLI, either from on the instance or from an external host.
How will it work?
We will extend the existing gh CLI to include commands for all of the endpoints currently in the Manage GitHub Enterprise Server API.

🚢 This shipped with GHES 3.11<EMAIL_ADDRESS>


Runtime Segfault

Hi developers,
I've successfully installed the driver but I get a segmentation fault error when running kinect2_bridge.
The output is:
$rosrun kinect2_bridge kinect2_bridge
parameter:
base_name: kinect2
sensor:
fps_limit: -1
calib_path: /home/hbadino/catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opengl
depth_device: -1
reg_method: default
reg_devive: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
Segmentation fault (core dumped)
gdb shows this:
Program received signal SIGSEGV, Segmentation fault.
glfwGetWindowAttrib (handle=handle@entry=0x0, attrib=attrib@entry=139266) at /home/hbadino/ros/libfreenect2/depends/glfw_src/src/window.c:560
560	/home/hbadino/ros/libfreenect2/depends/glfw_src/src/window.c: No such file or directory.
(gdb) bt
#0  glfwGetWindowAttrib (handle=handle@entry=0x0, attrib=attrib@entry=139266) at /home/hbadino/ros/libfreenect2/depends/glfw_src/src/window.c:560
#1  0x00007ffff56cd894 in flextInit (window=0x0, bindings=0x72bd00) at /home/hbadino/ros/libfreenect2/examples/protonect/src/flextGL.c:20
#2  0x00007ffff56d0ef0 in libfreenect2::OpenGLDepthPacketProcessorImpl::initialize (this=this@entry=0x728e10)
at /home/hbadino/ros/libfreenect2/examples/protonect/src/opengl_depth_packet_processor.cpp:472
#3  0x00007ffff56cef59 in libfreenect2::OpenGLDepthPacketProcessor::OpenGLDepthPacketProcessor (this=0x6b2780, parent_opengl_context_ptr=,
debug=) at /home/hbadino/ros/libfreenect2/examples/protonect/src/opengl_depth_packet_processor.cpp:786
#4  0x00007ffff56bce66 in libfreenect2::OpenGLPacketPipeline::createDepthPacketProcessor (this=0x6ae870)
at /home/hbadino/ros/libfreenect2/examples/protonect/src/packet_pipeline.cpp:109
#5  0x00007ffff56bcf15 in libfreenect2::BasePacketPipeline::initialize (this=this@entry=0x6ae870)
at /home/hbadino/ros/libfreenect2/examples/protonect/src/packet_pipeline.cpp:43
#6  0x00007ffff56bd383 in libfreenect2::OpenGLPacketPipeline::OpenGLPacketPipeline (this=0x6ae870, parent_opengl_context=, debug=)
at /home/hbadino/ros/libfreenect2/examples/protonect/src/packet_pipeline.cpp:102
#7  0x000000000041efaf in Kinect2Bridge::initialize() ()
#8  0x000000000041f3e9 in Kinect2Bridge::run() ()
#9  0x000000000040af09 in main ()
Upon connection of the Kinect, the kernel buffer shows:
[  328.473633] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[  328.492429] usb 4-1: New USB device found, idVendor=045e, idProduct=02c4
[  328.492434] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[  328.492437] usb 4-1: Product: Xbox NUI Sensor
[  328.492439] usb 4-1: Manufacturer: Microsoft
[  328.492441] usb 4-1: SerialNumber:<PHONE_NUMBER>47
[  328.547135] usbcore: registered new interface driver snd-usb-audio
And when I get the segfault:
[  343.564198] kinect2_bridge[10450]: segfault at 1c0 ip 00007f90a8d784f8 sp 00007fffac3357e0 error 4 in libglfw.so.3.0[7f90a8d71000+12000]
Your help would be greatly appreciated.
Hernan

The OpenGL processor from libfreenect2 requires OpenGL 3.3. Could it be that your driver only supports 3.0?
You could try to use the OpenCL processor instead.

Hi Thiemo,
thanks for replying.
How do I install/enabled/configure the OpenCL processor?
Hernan

You need to install OpenCL. When running cmake for libfreenect2 it should enable the OpenCL depth processor when it finds the OpenCL libraries.
Installation of OpenCL depends on the graphics card you are using. For Intel you need beignet, there are some instructions in the readme. For AMD and Nvidia you just need to install their newest drivers and opencl-headers.

Any updates or can we close this one?

You can close it. Thanks.
On Wed, Jun 3, 2015 at 6:51 AM, Thiemo Wiedemeyer<EMAIL_ADDRESS>wrote:

Any updates or can we close this one?
—
Reply to this email directly or view it on GitHub
https://github.com/code-iai/iai_kinect2/issues/94#issuecomment-108296495
.

--

Hernan

I am able to run ./Protonect and can view color, ir and depth images with out any error.
When I am trying to run kinect2_bridge from the root, it asks for clients. If I provide kinect2/sd/image_color_rect, it produces the messages but if I provide other topics like kinect2/qhd/image_color, the following error genetares
root@tegra-ubuntu:~/catkin_ws/devel# rosrun kinect2_bridge kinect2_bridge
parameter:
base_name: kinect2
sensor:
fps_limit: -1
calib_path: /home/ubuntu/catkin_ws/src/iai_kinect2/kinect2_bridge/data/
use_png: false
jpeg_quality: 90
png_level: 1
depth_method: opengl
depth_device: -1
reg_method: default
reg_devive: -1
max_depth: 12
min_depth: 0.1
queue_size: 2
bilateral_filter: true
edge_aware_filter: true
publish_tf: false
base_name_tf: kinect2
worker_threads: 4
[Freenect2Impl] enumerating devices...
[Freenect2Impl] 10 usb devices connected
[Freenect2Impl] found valid Kinect v2 @2:5 with serial<PHONE_NUMBER>47
[Freenect2Impl] found 1 devices
Kinect2 devices found:
0:<PHONE_NUMBER>47 (selected)
[Freenect2DeviceImpl] opening...
[Freenect2DeviceImpl] opened
starting kinect2
[Freenect2DeviceImpl] starting...
[Freenect2DeviceImpl] ReadData0x14 response
92 bytes of raw data
0x0000: 00 00 12 00 00 00 00 00 01 00 00 00 43 c1 1f 41 ............C..A
0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x0020: 0a 21 33 55 c2 00 17 20 00 08 00 00 10 00 00 00 .!3U... ........
0x0030: 00 01 00 00 00 10 00 00 00 00 80 00 01 00 00 00 .......... .....
0x0040: 31 33 00 00 00 04 0a 0d 47 4d 42 30 31 33 2e 31 13......GMB013.1
0x0050: 58 00 00 00 00 00 00 00 07 00 00 00 X...........
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 23 26 00 00 #&..
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 23 26 00 00 #&..
[Freenect2DeviceImpl] enabling usb transfer submission...
[Freenect2DeviceImpl] submitting usb transfers...
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[Freenect2DeviceImpl] started
device serial:<PHONE_NUMBER>47
device firmware: 2.3.3913.0.7
[Freenect2DeviceImpl] stopping...
[Freenect2DeviceImpl] disabling usb transfer submission...
[Freenect2DeviceImpl] canceling usb transfers...
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[TransferPool::submit] transfer submission disabled!
[Freenect2DeviceImpl] stopped
default ir camera parameters:
fx 367.573, fy 367.573, cx 256.171, cy 209.483
k1 0.0850694, k2 -0.273469, p1 0, p2 0, k3 0.100644
default color camera parameters:
fx 1081.37, fy 1081.37, cx 959.5, cy 539.5
using sensor defaults for color intrinsic parameters.
using sensor defaults for ir intrinsic parameters.
using defaults for rotation and translation.
using defaults for depth shift.
camera parameters used:
camera matrix color:
[1081.3720703125, 0, 959.5;
0, 1081.3720703125, 539.5;
0, 0, 1]
distortion coefficients color:
[0, 0, 0, 0, 0]
camera matrix ir:
[367.572998046875, 0,<PHONE_NUMBER>617188;
0,<PHONE_NUMBER>46875,<PHONE_NUMBER>617188;
0, 0, 1]
distortion coefficients ir:
[0.08506941795349121, -0.2734693884849548, 0, 0, 0.1006444990634918]
camera matrix depth:
[367.572998046875, 0,<PHONE_NUMBER>617188;
0,<PHONE_NUMBER>46875,<PHONE_NUMBER>617188;
0, 0, 1]
distortion coefficients depth:
[0.08506941795349121, -0.2734693884849548, 0, 0, 0.1006444990634918]
rotation:
[1, 0, 0;
0, 1, 0;
0, 0, 1]
translation:
[0; 0; 0]
depth shift:
0
[DepthRegistration::New] Using CPU registration method!
[DepthRegistration::New] Using CPU registration method!
[kinect2_bridge] waiting for clients to connect
[kinect2_bridge] client connected. starting device...
[Freenect2DeviceImpl] starting...
[Freenect2DeviceImpl] ReadData0x14 response
92 bytes of raw data
0x0000: 00 00 12 00 00 00 00 00 01 00 00 00 43 c1 1f 41 ............C..A
0x0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x0020: 0a 21 33 55 c2 00 17 20 00 08 00 00 10 00 00 00 .!3U... ........
0x0030: 00 01 00 00 00 10 00 00 00 00 80 00 01 00 00 00 .......... .....
0x0040: 31 33 00 00 00 04 0a 0d 47 4d 42 30 31 33 2e 31 13......GMB013.1
0x0050: 58 00 00 00 00 00 00 00 07 00 00 00 X...........
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 01 26 00 00 .&..
[Freenect2DeviceImpl] ReadStatus0x090000 response
4 bytes of raw data
0x0000: 03 26 00 00 .&..
[Freenect2DeviceImpl] enabling usb transfer submission...
[Freenect2DeviceImpl] submitting usb transfers...
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[TransferPool::submit] failed to submit transfer
[Freenect2DeviceImpl] started
[RgbPacketStreamParser::handleNewData] packetsize or sequence doesn't match!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~-nanHz (-nanms) publishing rate: ~10.3149Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~112.666Hz (8.87577ms) publishing rate: ~13.6632Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[TurboJpegRgbPacketProcessor] avg. time: 58.6753ms -> ~17.043Hz
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[RgbPacketStreamParser::handleNewData] skipping rgb packet!
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
[kinect2_bridge] color processing: ~127.059Hz (7.87038ms) publishing rate: ~14.6242Hz
Segmentation fault
I am using Jetson TK1 board .
cpu ang gpu performance were altered with maximum efficiency
Why lots of "skipping rgb packet!" and " [TransferPool::submit] failed to submit transfer " ?
why not providing depth data?
[kinect2_bridge] depth processing: ~nanHz (nanms) publishing rate: ~0Hz
Why segmentation fault after producing one message to the topics?


resolve MAC address of XXX timeout

Expected Behavior
after install kubeovn coredns in running status
Actual Behavior
after install kubeovn coredns in ContainerCreatingstatus
use NETWORK_TYPE="vlan" in vmware vsphere vm environment.

Steps to Reproduce the Problem
1、change install.sh config
#!/usr/bin/env bash
set -euo pipefail

IPV6=${IPV6:-false}
DUAL_STACK=${DUAL_STACK:-false}
ENABLE_SSL=${ENABLE_SSL:-false}
ENABLE_VLAN=${ENABLE_VLAN:-false}
CHECK_GATEWAY=${CHECK_GATEWAY:-true}
LOGICAL_GATEWAY=${LOGICAL_GATEWAY:-false}
U2O_INTERCONNECTION=${U2O_INTERCONNECTION:-false}
ENABLE_MIRROR=${ENABLE_MIRROR:-false}
VLAN_NIC=${VLAN_NIC:-}
HW_OFFLOAD=${HW_OFFLOAD:-false}
ENABLE_LB=${ENABLE_LB:-true}
ENABLE_NP=${ENABLE_NP:-true}
ENABLE_EIP_SNAT=${ENABLE_EIP_SNAT:-true}
LS_DNAT_MOD_DL_DST=${LS_DNAT_MOD_DL_DST:-true}
ENABLE_EXTERNAL_VPC=${ENABLE_EXTERNAL_VPC:-true}
CNI_CONFIG_PRIORITY=${CNI_CONFIG_PRIORITY:-01}
ENABLE_LB_SVC=${ENABLE_LB_SVC:-false}
ENABLE_KEEP_VM_IP=${ENABLE_KEEP_VM_IP:-true}
# exchange link names of OVS bridge and the provider nic
# in the default provider-network
EXCHANGE_LINK_NAME=true
EXCHANGE_LINK_NAME=${EXCHANGE_LINK_NAME:-false}
# The nic to support container network can be a nic name or a group of regex
# separated by comma, if empty will use the nic that the default route use
IFACE=ens160
IFACE=${IFACE:-}
# Specifies the name of the dpdk tunnel iface.
# Note that the dpdk tunnel iface and tunnel ip cidr should be diffierent with Kubernetes api cidr,otherwise the route will be a problem.
DPDK_TUNNEL_IFACE=${DPDK_TUNNEL_IFACE:-br-phy}
ENABLE_BIND_LOCAL_IP=${ENABLE_BIND_LOCAL_IP:-true}

CNI_CONF_DIR="/etc/cni/net.d"
CNI_BIN_DIR="/opt/cni/bin"

REGISTRY="kubeovn"
VERSION="v1.11.1"
IMAGE_PULL_POLICY="IfNotPresent"
POD_CIDR="<IP_ADDRESS>/24"                # Do NOT overlap with NODE/SVC/JOIN CIDR
POD_GATEWAY="<IP_ADDRESS>"
SVC_CIDR="<IP_ADDRESS>/22"                # Do NOT overlap with NODE/POD/JOIN CIDR
JOIN_CIDR="<IP_ADDRESS>/16"              # Do NOT overlap with NODE/POD/SVC CIDR
PINGER_EXTERNAL_ADDRESS="<IP_ADDRESS>"  # Pinger check external ip probe
PINGER_EXTERNAL_DOMAIN="alauda.cn"         # Pinger check external domain probe
SVC_YAML_IPFAMILYPOLICY=""
if [ "$IPV6" = "true" ]; then
  POD_CIDR="fd00:10:16::/64"                # Do NOT overlap with NODE/SVC/JOIN CIDR
  POD_GATEWAY="fd00:10:16::1"
  SVC_CIDR="fd00:10:96::/112"               # Do NOT overlap with NODE/POD/JOIN CIDR
  JOIN_CIDR="fd00:100:64::/64"              # Do NOT overlap with NODE/POD/SVC CIDR
  PINGER_EXTERNAL_ADDRESS="2400:3200::1"
  PINGER_EXTERNAL_DOMAIN="google.com"
fi
if [ "$DUAL_STACK" = "true" ]; then
  POD_CIDR="<IP_ADDRESS>/16,fd00:10:16::/64"                # Do NOT overlap with NODE/SVC/JOIN CIDR
  POD_GATEWAY="<IP_ADDRESS>,fd00:10:16::1"
  SVC_CIDR="<IP_ADDRESS>/12,fd00:10:96::/112"               # Do NOT overlap with NODE/POD/JOIN CIDR
  JOIN_CIDR="<IP_ADDRESS>/16,fd00:100:64::/64"             # Do NOT overlap with NODE/POD/SVC CIDR
  PINGER_EXTERNAL_ADDRESS="<IP_ADDRESS>,2400:3200::1"
  PINGER_EXTERNAL_DOMAIN="google.com"
  SVC_YAML_IPFAMILYPOLICY="ipFamilyPolicy: PreferDualStack"
fi

EXCLUDE_IPS="<IP_ADDRESS>..<IP_ADDRESS>"                                    # EXCLUDE_IPS for default subnet
LABEL="node-role.kubernetes.io/control-plane"     # The node label to deploy OVN DB
DEPRECATED_LABEL="node-role.kubernetes.io/master" # The node label to deploy OVN DB in earlier versions
NETWORK_TYPE="vlan"                             # geneve or vlan
TUNNEL_TYPE="geneve"                              # geneve, vxlan or stt. ATTENTION: some networkpolicy cannot take effect when using vxlan and stt need custom compile ovs kernel mod
ule
POD_NIC_TYPE="veth-pair"                          # veth-pair or internal-port
POD_DEFAULT_FIP_TYPE=""                           # iptables, pod can set iptables fip automatically by enable fip annotation

# VLAN Config only take effect when NETWORK_TYPE is vlan
PROVIDER_NAME="provider"
VLAN_INTERFACE_NAME="ens160"
VLAN_NAME="ovn-vlan"
VLAN_ID="0"

if [ "$ENABLE_VLAN" = "true" ]; then
  NETWORK_TYPE="vlan"
  if [ "$VLAN_NIC" != "" ]; then
    VLAN_INTERFACE_NAME="$VLAN_NIC"
  fi
fi

2、run install.bash
bash install.sh

3、install logs
root@ubuntu:~/kube-ovn# bash install.sh
-------------------------------
Kube-OVN Version:     v1.11.1
Default Network Mode: vlan
Default Vlan Nic:     ens160
Default Vlan ID:      0
Default Subnet CIDR:  <IP_ADDRESS>/24
Join Subnet CIDR:     <IP_ADDRESS>/16
Enable SVC LB:        true
Enable Networkpolicy: true
Enable EIP and SNAT:  true
Enable Mirror:        false
-------------------------------
[Step 1/6] Label kube-ovn-master node and label datapath type
node/ubuntu labeled
-------------------------------

[Step 2/6] Install OVN components
Install OVN DB in <IP_ADDRESS>,
customresourcedefinition.apiextensions.k8s.io/vpc-dnses.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/switch-lb-rules.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/vpc-nat-gateways.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/iptables-eips.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/iptables-fip-rules.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/iptables-dnat-rules.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/iptables-snat-rules.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/ovn-eips.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/ovn-fips.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/ovn-snat-rules.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/vpcs.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/ips.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/vips.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/subnets.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/vlans.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/provider-networks.kubeovn.io created
customresourcedefinition.apiextensions.k8s.io/security-groups.kubeovn.io created
serviceaccount/ovn created
clusterrole.rbac.authorization.k8s.io/system:ovn created
clusterrolebinding.rbac.authorization.k8s.io/ovn created
service/ovn-nb created
service/ovn-sb created
service/ovn-northd created
deployment.apps/ovn-central created
daemonset.apps/ovs-ovn created
Waiting for deployment "ovn-central" rollout to finish: 0 out of 1 new replicas have been updated...
Waiting for deployment "ovn-central" rollout to finish: 0 of 1 updated replicas are available...
deployment "ovn-central" successfully rolled out
-------------------------------

[Step 3/6] Install Kube-OVN
deployment.apps/kube-ovn-controller created
daemonset.apps/kube-ovn-cni created
daemonset.apps/kube-ovn-pinger created
deployment.apps/kube-ovn-monitor created
service/kube-ovn-monitor created
service/kube-ovn-pinger created
service/kube-ovn-controller created
service/kube-ovn-cni created
Waiting for deployment "kube-ovn-controller" rollout to finish: 0 of 1 updated replicas are available...
deployment "kube-ovn-controller" successfully rolled out
Waiting for daemon set "kube-ovn-cni" rollout to finish: 0 of 1 updated pods are available...
daemon set "kube-ovn-cni" successfully rolled out
-------------------------------

[Step 4/6] Delete pod that not in host network mode
pod "coredns-565d847f94-gb695" deleted
pod "coredns-565d847f94-pdzqz" deleted
daemon set "kube-ovn-pinger" successfully rolled out
Waiting for deployment "coredns" rollout to finish: 0 of 2 updated replicas are available...
error: deployment "coredns" exceeded its progress deadline
root@ubuntu:~/kube-ovn# kubectl get pods
No resources found in default namespace.
root@ubuntu:~/kube-ovn# kubectl get pods  -A
NAMESPACE     NAME                                   READY   STATUS              RESTARTS      AGE
kube-system   coredns-565d847f94-96fl4               0/1     ContainerCreating   0             17m
kube-system   coredns-565d847f94-j78sv               0/1     ContainerCreating   0             21m
kube-system   etcd-ubuntu                            1/1     Running             2 (24m ago)   51m
kube-system   kube-apiserver-ubuntu                  1/1     Running             2 (24m ago)   51m
kube-system   kube-controller-manager-ubuntu         1/1     Running             2 (24m ago)   51m
kube-system   kube-ovn-cni-lggm7                     1/1     Running             0             21m
kube-system   kube-ovn-controller-5966b7f576-8knjm   1/1     Running             0             21m
kube-system   kube-ovn-monitor-9754c455c-88bl5       1/1     Running             0             21m
kube-system   kube-ovn-pinger-m6x9l                  0/1     ContainerCreating   0             12m
kube-system   kube-proxy-gwdkn                       1/1     Running             2 (24m ago)   51m
kube-system   kube-scheduler-ubuntu                  1/1     Running             2 (24m ago)   51m
kube-system   ovn-central-6877744858-l5mqk           1/1     Running             0             22m
kube-system   ovs-ovn-747kg                          1/1     Running             0             22m

4、coredns logs
root@ubuntu:~/kube-ovn# kubectl -n kube-system describe pods coredns-565d847f94-96fl4
Name:                 coredns-565d847f94-96fl4
Namespace:            kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Service Account:      coredns
Node:                 ubuntu/<IP_ADDRESS>
Start Time:           Thu, 13 Apr 2023 00:42:26 +0800
Labels:               k8s-app=kube-dns
                      pod-template-hash=565d847f94
Annotations:          ovn.kubernetes.io/allocated: true
                      ovn.kubernetes.io/cidr: <IP_ADDRESS>/24
                      ovn.kubernetes.io/gateway: <IP_ADDRESS>
                      ovn.kubernetes.io/ip_address: <IP_ADDRESS>
                      ovn.kubernetes.io/logical_switch: ovn-default
                      ovn.kubernetes.io/mac_address: 00:00:00:39:7E:CC
                      ovn.kubernetes.io/pod_nic_type: veth-pair
                      ovn.kubernetes.io/provider_network: provider
                      ovn.kubernetes.io/routed: true
                      ovn.kubernetes.io/vlan_id: 0
Status:               Pending
IP:
IPs:                  <none>
Controlled By:        ReplicaSet/coredns-565d847f94
Containers:
  coredns:
    Container ID:
    Image:         registry.k8s.io/coredns/coredns:v1.9.3
    Image ID:
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-t7prz (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  kube-api-access-t7prz:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 CriticalAddonsOnly op=Exists
                             node-role.kubernetes.io/control-plane:NoSchedule
                             node-role.kubernetes.io/master:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age    From               Message
  ----     ------                  ----   ----               -------
  Normal   Scheduled               21m    default-scheduler  Successfully assigned kube-system/coredns-565d847f94-96fl4 to ubuntu
  Warning  FailedCreatePodSandBox  18m    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d9f5b6d3cb9bd121403632c3c42b5a3600b1084b60f1e840a63dfcb10df84b47": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout
  Warning  FailedCreatePodSandBox  14m    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "720457a14038737419b34a2dc92ae677b68270c9d3d91dfe472c00f8923f4565": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout
  Warning  FailedCreatePodSandBox  11m    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "31cf59eb23ab5e44e538226f1ac954a9216753ca9ff5f832bbbf6f590f68e9bc": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout
  Warning  FailedCreatePodSandBox  7m51s  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e9c3a87a801a2d7337c015942ef3ef695a4093bddd87e748ca63f40fcacb2112": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout
  Warning  FailedCreatePodSandBox  4m26s  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "742bf1b4f5420ab94716e7dee2a45115e8edcfb4258e07cb665c74de9cab2764": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout
  Warning  FailedCreatePodSandBox  60s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7d4ddd9d4c9fa9482e6df170a82cb83ef1ecb5417cf41f472baee441fafd70a7": plugin type="kube-ovn" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout

4、kubelet logs
Apr 13 00:48:13 ubuntu kubelet[1180]: I0413 00:48:13.002578    1180 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"host-config-openvswitch\" (UniqueName: \"kubernetes.io/host-path/32362817-8066-4b67-8c75-c2a59d2f0379-host-config-openvswitch\") pod \"kube-ovn-pinger-m6x9l\" (UID: \"32362817-8066-4b67-8c75-c2a59d2f0379\") " pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:48:13 ubuntu kubelet[1180]: I0413 00:48:13.002633    1180 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"kube-ovn-log\" (UniqueName: \"kubernetes.io/host-path/32362817-8066-4b67-8c75-c2a59d2f0379-kube-ovn-log\") pod \"kube-ovn-pinger-m6x9l\" (UID: \"32362817-8066-4b67-8c75-c2a59d2f0379\") " pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:48:13 ubuntu kubelet[1180]: I0413 00:48:13.002683    1180 reconciler.go:357] "operationExecutor.VerifyControllerAttachedVolume started for volume \"host-modules\" (UniqueName: \"kubernetes.io/host-path/32362817-8066-4b67-8c75-c2a59d2f0379-host-modules\") pod \"kube-ovn-pinger-m6x9l\" (UID: \"32362817-8066-4b67-8c75-c2a59d2f0379\") " pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:49:18 ubuntu kubelet[1180]: E0413 00:49:18.180994    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"720457a14038737419b34a2dc92ae677b68270c9d3d91dfe472c00f8923f4565\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout"
Apr 13 00:49:18 ubuntu kubelet[1180]: E0413 00:49:18.181044    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"720457a14038737419b34a2dc92ae677b68270c9d3d91dfe472c00f8923f4565\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:49:18 ubuntu kubelet[1180]: E0413 00:49:18.181071    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"720457a14038737419b34a2dc92ae677b68270c9d3d91dfe472c00f8923f4565\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:49:18 ubuntu kubelet[1180]: E0413 00:49:18.181126    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"720457a14038737419b34a2dc92ae677b68270c9d3d91dfe472c00f8923f4565\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout\"" pod="kube-system/coredns-565d847f94-96fl4" podUID=e6432e5f-c196-4695-ac2c-8f3802fd8cd0
Apr 13 00:49:34 ubuntu kubelet[1180]: E0413 00:49:34.730508    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"7148a21b2f843ac0ad3d9204df237780dc3080dd4cad3c418671393517331e26\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout"
Apr 13 00:49:34 ubuntu kubelet[1180]: E0413 00:49:34.730580    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"7148a21b2f843ac0ad3d9204df237780dc3080dd4cad3c418671393517331e26\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:49:34 ubuntu kubelet[1180]: E0413 00:49:34.730607    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"7148a21b2f843ac0ad3d9204df237780dc3080dd4cad3c418671393517331e26\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:49:34 ubuntu kubelet[1180]: E0413 00:49:34.730675    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"7148a21b2f843ac0ad3d9204df237780dc3080dd4cad3c418671393517331e26\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout\"" pod="kube-system/coredns-565d847f94-j78sv" podUID=6732bb83-9823-4a89-bfd8-e3c93ee5d0db
Apr 13 00:50:06 ubuntu kubelet[1180]: W0413 00:50:06.141833    1180 watcher.go:93] Error while processing event ("/sys/fs/cgroup/system.slice/systemd-tmpfiles-clean.service": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /sys/fs/cgroup/system.slice/systemd-tmpfiles-clean.service: no such file or directory
Apr 13 00:51:39 ubuntu kubelet[1180]: E0413 00:51:39.534548    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"421aba4d0b6838b1cff940180e445ebe08835d7fc169add53941181eb9194f1b\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout"
Apr 13 00:51:39 ubuntu kubelet[1180]: E0413 00:51:39.534683    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"421aba4d0b6838b1cff940180e445ebe08835d7fc169add53941181eb9194f1b\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout" pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:51:39 ubuntu kubelet[1180]: E0413 00:51:39.534764    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"421aba4d0b6838b1cff940180e445ebe08835d7fc169add53941181eb9194f1b\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout" pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:51:39 ubuntu kubelet[1180]: E0413 00:51:39.534894    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"kube-ovn-pinger-m6x9l_kube-system(32362817-8066-4b67-8c75-c2a59d2f0379)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"kube-ovn-pinger-m6x9l_kube-system(32362817-8066-4b67-8c75-c2a59d2f0379)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"421aba4d0b6838b1cff940180e445ebe08835d7fc169add53941181eb9194f1b\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout\"" pod="kube-system/kube-ovn-pinger-m6x9l" podUID=32362817-8066-4b67-8c75-c2a59d2f0379
Apr 13 00:52:44 ubuntu kubelet[1180]: E0413 00:52:44.930636    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"31cf59eb23ab5e44e538226f1ac954a9216753ca9ff5f832bbbf6f590f68e9bc\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout"
Apr 13 00:52:44 ubuntu kubelet[1180]: E0413 00:52:44.930694    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"31cf59eb23ab5e44e538226f1ac954a9216753ca9ff5f832bbbf6f590f68e9bc\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:52:44 ubuntu kubelet[1180]: E0413 00:52:44.930727    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"31cf59eb23ab5e44e538226f1ac954a9216753ca9ff5f832bbbf6f590f68e9bc\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:52:44 ubuntu kubelet[1180]: E0413 00:52:44.930805    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"31cf59eb23ab5e44e538226f1ac954a9216753ca9ff5f832bbbf6f590f68e9bc\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout\"" pod="kube-system/coredns-565d847f94-96fl4" podUID=e6432e5f-c196-4695-ac2c-8f3802fd8cd0
Apr 13 00:53:01 ubuntu kubelet[1180]: E0413 00:53:01.706025    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"c521a39f522965686dc7b97bd8bfa51af325ea0beade31bed001065964e72099\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout"
Apr 13 00:53:01 ubuntu kubelet[1180]: E0413 00:53:01.706094    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"c521a39f522965686dc7b97bd8bfa51af325ea0beade31bed001065964e72099\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:53:01 ubuntu kubelet[1180]: E0413 00:53:01.706130    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"c521a39f522965686dc7b97bd8bfa51af325ea0beade31bed001065964e72099\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:53:01 ubuntu kubelet[1180]: E0413 00:53:01.706506    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"c521a39f522965686dc7b97bd8bfa51af325ea0beade31bed001065964e72099\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout\"" pod="kube-system/coredns-565d847f94-j78sv" podUID=6732bb83-9823-4a89-bfd8-e3c93ee5d0db
Apr 13 00:55:07 ubuntu kubelet[1180]: E0413 00:55:07.314743    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"b2079d584775504f2a878c1786063a95167076e37eeb3b1c4d0557e6c83bab76\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout"
Apr 13 00:55:07 ubuntu kubelet[1180]: E0413 00:55:07.314820    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"b2079d584775504f2a878c1786063a95167076e37eeb3b1c4d0557e6c83bab76\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout" pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:55:07 ubuntu kubelet[1180]: E0413 00:55:07.314857    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"b2079d584775504f2a878c1786063a95167076e37eeb3b1c4d0557e6c83bab76\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout" pod="kube-system/kube-ovn-pinger-m6x9l"
Apr 13 00:55:07 ubuntu kubelet[1180]: E0413 00:55:07.314937    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"kube-ovn-pinger-m6x9l_kube-system(32362817-8066-4b67-8c75-c2a59d2f0379)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"kube-ovn-pinger-m6x9l_kube-system(32362817-8066-4b67-8c75-c2a59d2f0379)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"b2079d584775504f2a878c1786063a95167076e37eeb3b1c4d0557e6c83bab76\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:a5:96:7e: i/o timeout\"" pod="kube-system/kube-ovn-pinger-m6x9l" podUID=32362817-8066-4b67-8c75-c2a59d2f0379
Apr 13 00:56:12 ubuntu kubelet[1180]: E0413 00:56:12.015033    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"e9c3a87a801a2d7337c015942ef3ef695a4093bddd87e748ca63f40fcacb2112\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout"
Apr 13 00:56:12 ubuntu kubelet[1180]: E0413 00:56:12.015125    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"e9c3a87a801a2d7337c015942ef3ef695a4093bddd87e748ca63f40fcacb2112\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:56:12 ubuntu kubelet[1180]: E0413 00:56:12.015166    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"e9c3a87a801a2d7337c015942ef3ef695a4093bddd87e748ca63f40fcacb2112\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout" pod="kube-system/coredns-565d847f94-96fl4"
Apr 13 00:56:12 ubuntu kubelet[1180]: E0413 00:56:12.015237    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-96fl4_kube-system(e6432e5f-c196-4695-ac2c-8f3802fd8cd0)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"e9c3a87a801a2d7337c015942ef3ef695a4093bddd87e748ca63f40fcacb2112\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:39:7e:cc: i/o timeout\"" pod="kube-system/coredns-565d847f94-96fl4" podUID=e6432e5f-c196-4695-ac2c-8f3802fd8cd0
Apr 13 00:56:26 ubuntu kubelet[1180]: E0413 00:56:26.796226    1180 remote_runtime.go:222] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"446bf1a35997c40dcd7ebec2f57421dd66ee55445f14e957ebe7cc825aad20c9\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout"
Apr 13 00:56:26 ubuntu kubelet[1180]: E0413 00:56:26.796298    1180 kuberuntime_sandbox.go:71] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"446bf1a35997c40dcd7ebec2f57421dd66ee55445f14e957ebe7cc825aad20c9\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:56:26 ubuntu kubelet[1180]: E0413 00:56:26.796334    1180 kuberuntime_manager.go:772] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to setup network for sandbox \"446bf1a35997c40dcd7ebec2f57421dd66ee55445f14e957ebe7cc825aad20c9\": plugin type=\"kube-ovn\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout" pod="kube-system/coredns-565d847f94-j78sv"
Apr 13 00:56:26 ubuntu kubelet[1180]: E0413 00:56:26.796407    1180 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"coredns-565d847f94-j78sv_kube-system(6732bb83-9823-4a89-bfd8-e3c93ee5d0db)\\\": rpc error: code = Unknown desc = failed to setup network for sandbox \\\"446bf1a35997c40dcd7ebec2f57421dd66ee55445f14e957ebe7cc825aad20c9\\\": plugin type=\\\"kube-ovn\\\" failed (add): RPC failed; request ip return 500 configure nic failed network <IP_ADDRESS>/24 with gateway <IP_ADDRESS> is not ready for interface eth0 after 200 checks: resolve MAC address of <IP_ADDRESS> timeout: read packet 00:00:00:67:95:54: i/o timeout\"" pod="kube-system/coredns-565d847f94-j78sv" podUID=6732bb83-9823-4a89-bfd8-e3c93ee5d0db
root@ubuntu:~#

Additional Info

Kubernetes version:
v1.25.6

kube-ovn version:
v1.11.3
wget https://github.com/kubeovn/kube-ovn/archive/refs/tags/v1.11.3.tar.gz

operation-system/kernel version:
Output of awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release:
Output of uname -r:
root@ubuntu:~/kube-ovn# awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release
"Ubuntu 22.04 LTS"

root@ubuntu:~/kube-ovn# uname -r
5.15.0-27-generic

Please check your network configuration.
You can also check access to the external network using macvlan.


RAML 1.0 to Swagger conversion fails with multi file RAML specification

A RAML 1.0 specification composed of multiple files does not properly convert to Swagger.
Example:
spec.raml (top level spec file)
types.raml (a RAML 1.0 library used by spec.raml)
Executing the converter on spec.raml does not convert the types in types.raml to Swagger definitions.

+1

+1

+1


signInWithEmailAndPassword throws error

Description
Attempting to use signInWithEmailAndPassword throws and exception
Expected outcome
method should be found and executed.
Actual outcome
market-edge-app.html:51 Uncaught TypeError: this.$.auth.signInWithEmailAndPassword is not a function
signIn	@	market-edge-app.html:51
handler	@	polymer.html:518
fire	@	polymer.html:1277
signIn	@	me-login.html:70
handler	@	polymer.html:518
fire	@	polymer.html:1277
fire	@	polymer.html:854
forward	@	polymer.html:1149
click	@	polymer.html:1134
handleNative	@	polymer.html:744
Not sure if I  have something configured wrong or what but I started with a basic polymer app built using the polymer-cli, I then added polymerfire using bower I have setup the firebase-app with the correct setting from my firebase-console.
Below is a snippet of the code.
<firebase-auth
      id="auth"
      app-name="market-edge"
      signed-in="{{signedIn}}"
      user="{{user}}">
  </firebase-auth>

</template>

<script>
  Polymer({

    is: 'market-edge-app',

    properties: {
    },
    signIn: function() {
      console.log(this.$.auth.user);
      this.$.auth.signInWithEmailAndPassword(this.user, this.password)
        .then(function(response) {
          console.log(response);
        })
        .catch(function(error) {
          console.log(error);
        });
    }
  });
</script>

I changed my code as follows and now the signIn function works. This should really work either way and I'm not sure why it works one way and not the other.
<firebase-auth
        id="auth"
        app-name="market-edge"
        signed-in="{{signedIn}}"
        user="{{user}}">
    </firebase-auth>

  </template>

  <script>
  (() => {
    'use strict'

    Polymer({

      is: 'market-edge-app',

      properties: {
      },
      signIn() {
        console.log(this.$.auth.user);
        this.$.auth.signInWithEmailAndPassword(this.user, this.password)
          .then(function(response) {
            console.log(response);
          })
          .catch(function(error) {
            console.log(error);
          });
      }
    });
  })();
  </script>

Since signInWithEmailAndPassword is definitely defined on the auth element, I'm guessing this may have been some kind of initialization or timing error in your app code somewhere...I'm unable to repro and am closing barring a concrete repro. Thanks!


Annotate app structure and design as a wiki page

documented your different post's reply here https://github.com/jedireza/aqua/wiki/Page-Structure-&-How-to-add-new-page   as start point later can be groomed, atleast this will provide users a start point. Hope this helps.

Thanks for starting that page @nitingautam


[Gssoc'21] Back to top button

Is your feature request related to a problem? Please describe.
There is no back to top button in website
Describe the solution you'd like
I would like to add the back to top button on every page

can I do this?

@CodesbyUnnati can I start working on this??

@arpit456jain Go for it


fix: update readme

This PR adds some syntax highlighting on some bash commands to improve readability.

Thanks!


treeModel.filterNodes behaves weird when compiled with AOT

Hi,
The tree component works perfectly when compiled as JIT , but when compiled the same code with AOT it started behaving weird when you do the tree.treeModel.filterNodes(text, true);
When you enter any data on the search input , it JIT it display the Parent and Filtered Child Node properly , but on AOT it Opens up all the Parent Nodes and overlap with each Other like the Attached ScreenShot.
It only happens on the AOT compilation, not sure why the same thing never happened on JIT compilation.

Thank you

in jit as well, I am able to see issue. Along with it, the nodes which don't match the search term are no more hidden although hidden attribute is set

If I put useVirtualScroll: true in options, then the issue goes away for me. But again scroll bar comes for even small tree.

Will be fixed in the coming version
--

Adam Klein http://il.linkedin.com/in/adamklein500
CTO @ 500Tech.com http://500tech.com/
AngularJS, ReactJS, NodeJS
Development, consulting, training and public speaking
(+972) 52 747 5633

On Tue, Mar 14, 2017 at 8:49 AM, debslab<EMAIL_ADDRESS>wrote:

If I put useVirtualScroll: true in options, then the issue goes away for
me. But again scroll bar comes for even small tree.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/500tech/angular-tree-component/issues/218#issuecomment-286336726,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2SSkwhZZyAHpclB6vkFLwUx6BnGaInks5rljhggaJpZM4MbA80
.

Hi @debslab , @snehasis  fixed in 3.2.4, can you verify?


Auto Remove Download if two way sync is done

Describe your suggested feature
if two way sync is enabled & u refresh the library & u previously read or sync some chapters already. e.g
i read manga A & sync it to anilist from any other client it its latest chapter which is = 84
& on komikku last updated chapter was 83
now i refresh the library it shows chapter 84 & 85.
when i open that manga two way sync will sync it to 84 but autodownload will still go on.
maybe remove that chapter from downloading when it synced and marked it as read?
i guess i explained it properly
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.10.5.
[X] I will fill out all of the requested information in this form.

Have you tried the "Delete after manually marked as read"?

Have you tried the "Delete after manually marked as read"?

on but still same


Description

Description
A sidebar that is fixed to the side and is collapsible using a resizable panel
Example
No response
Originally posted by @teenkevo in https://github.com/shadcn-ui/ui/discussions/3658

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Cannot open include file: 'libpq-fe. h'

Hi Vadim and all-
C:\soci-4.0.2\include\soci/postgresql/soci-postgresql.h(22,10): is the place where the error is thrown.
The kind of line it is on looks like this
#include<libpq-fe.h>
No such file or directory [C:\soci-4.0.2\src\backends\postgresql\soci_postgresql_static.vcxproj]
I put this line in my cmake script variable that you provided:
-DPOSTGRESQL_INCLUDE_DIR="C:/Progra2/PostgreSQL/14/include"
I'm trying to build with windows. Here is my entire script.
cmake -G "Visual Studio 17" -DWITH_BOOST=ON -DBOOST_INCLUDE_DIR="C:/local/boost_1_76_0/boost" -DBOOST_LIBRARIES="C:/local/boost_1_76_0/lib64-msvc-14.1" -DWITH_ORACLE=OFF -DSOCI_CXX11=ON -DWITH_DB2=OFF -DWITH_FIREBIRD=OFF -DWITH_MYSQL=OFF -DWITH_ODBC=OFF -DWITH_POSTGRESQL=ON -DPOSTGRESQL_VERSION=14 -DPOSTGRESQL_INCLUDE_DIR="C:/Progra2/PostgreSQL/14/include" -DPOSTGRESQL_LIBRARY="C:/Progra2/PostgreSQL/14/lib" -DPOSTGRESQL_LIBRARIES="C:/Progra2/PostgreSQL/14/lib/libpq.lib"  -DWITH_SQLITE3=OFF C:/soci-4.0.2
Please assist!
I just had my computer destroyed because of a leaking soda in my backpack~
I am back putting all the tools on my new PC.
Thanks for any cool help-
roboloki

HI Vadim and other cool people-
I got past the error.
I noticed that c:/progra2/PostgreSql isn't preferred to "c:/Program Files/PostgreSQl...".
Also, I added an entry to cmakelist.txt.
in the backend section I added a absolute file path to lipq-fe.h.
I hope that helps someone. Now I only have 3 warnings left with 0 errors.
I am sure I can fix the last one. Here is my cmake script you all provided for getting it to work.
cmake -G "Visual Studio 17" -DWITH_BOOST=ON -DBOOST_INCLUDE_DIR="C:/local/boost_1_76_0/boost" -DBOOST_LIBRARIES="C:/local/boost_1_76_0/lib64-msvc-14.1" -DWITH_ORACLE=OFF -DSOCI_CXX11=ON -DWITH_DB2=OFF -DWITH_FIREBIRD=OFF -DWITH_MYSQL=OFF -DWITH_ODBC=OFF -DWITH_POSTGRESQL=ON -DPOSTGRESQL_VERSION=14 -DPOSTGRESQL_INCLUDE_DIR="C:/Program Files/PostgreSQL/14/include" -DPOSTGRESQL_LIBRARY="C:/Program Files/PostgreSQL/14/lib/libpq.lib" -DPOSTGRESQL_LIBRARIES="C:/Program Files/PostgreSQL/14/lib/libpq.lib"  -DWITH_SQLITE3=OFF C:/soci-4.0.2
Thanks much.
Have a cool weekend :-)

HI all-
I just built postgresql with soci and boost. It worked on Visual Studio Community 17 and postgres 14.
thanks


Added nofollow to the blacklist

Not sure if this was left out because of its potential legitimacy, but I've found it to be used only by spammers.
Thanks!
Ryan

Hi Ryan.
Spammers generally do not add nofollow to their links, as that would defeat much of the purpose of including links in spammy comments to begin with. The nofollow attribute is designed to stop search engines and indexing spiders from following those links.
I’ve left nofollow out of the blacklist because WordPress automatically adds the rel="nofollow" attribute1 to fully qualified links (eg: Apple) that are found in comment text. It does this prior to checking that text against the blacklist. Since every fully qualified link contains the nofollow string, every comment containing links formatted in this way would be flagged as spam.
However, if you include a bare link in your comment (eg: www.apple.com), the rel="nofollow" attribute is added after the comment text is checked against the blacklist.
1 http://codex.wordpress.org/Nofollow

Hey Grant!
Thanks for the response... Yeah, I get that it has its legitimate usages. I just recently went through a blog of mine that gets boatloads of spam and found that they were using nofollows in their links (I have no idea why -- doesn't make sense for SEO). A few weeks of my own little exploration in spam honey-potting left me with this:
mysql> update wp_comments set comment_approved='spam' where comment_approved='0' AND comment_content LIKE "%nofollow%";
Query OK, 412 rows affected (0.09 sec)
Rows matched: 412  Changed: 412  Warnings: 0

I didn't go through each of these by hand, but I can verify that the vast majority of these were from a DC in the Ukraine (195.211.154 and 155), but not all:
mysql> select count(*) from wp_comments where comment_author_IP like "195.211.15%" and comment_content like "%nofollow%";
+----------+
| count(*) |
+----------+
|     2306 |
+----------+
1 row in set (0.16 sec)

mysql> select count(*) from wp_comments where comment_author_IP not like "195.211.15%" and comment_content like "%nofollow%";
+----------+
| count(*) |
+----------+
|      550 |
+----------+
1 row in set (0.03 sec)

Browsing through the content of those comments (focusing on ones not from the Ukraine DC), I have yet to find one legitimate comment D=
Full disclosure, the site these numbers are from only has technical posts about mysql, *nix cli usage, and WordPress... I was also able to eliminate a bunch of spam by doing the same to "China" and "obama" (verbatim -- "china" or "Obama" were empty) as well -- probably not good suggestions for this list though xD
Feel free to close this as it might not be a good fit for most blogs, just thought I'd share my experience with a project that might be able to use it.
Thanks and take care,
Ryan

I appreciate the sleuthing, but I will not be including nofollow in the blacklist.
However, as I explained above all URLs contained in anchor elements automatically get the nofollow attribute added to them by WordPress.
I’ve tested this using valid (not spammy) URLs and link text on my own blogs. If nofollow is included in the blacklist, every single URL contained in an anchor element with get flagged as spam, regardless of its source or author.
You can certainly add your own terms to the blacklist manually. Just be aware that if you do include nofollow, you’ll likely be marking valid comments as spam.


Fixed #35226 -- Reallowed executing queries for dynamically created connections.

Regression in 8fb0be3500cc7519a56985b1b6f415d75ac6fedb.
Thanks Florian Apolloner for the report.

@David-Wobrock Thanks for checking :+1:


Self update

Add a feature to project keeper to update itself to the latest available version.

This will probably require an additional dependency to
<dependency>
    <groupId>org.kohsuke</groupId>
    <artifactId>github-api</artifactId>
    <version>1.307</version>
</dependency>

The last comment was based on wrong assumptions -- please ignore.


[$250] IOU – Disabled distance rate is present in the rate list in confirmation page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.74-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to https://staging.new.expensify.com/
Log in and go to Collect workspace settings
Go to Distance rates
Click Add rate
Add a new rate
Disable existing rate
Go to workspace chat
Start submit distance flow
In confirmation page, click Rate

Expected Result:
Disabled distance rate is not present in the rate list in confirmation page
Actual Result:
Disabled distance rate is present in the rate list in confirmation page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/609ccf1c-abbd-48aa-8e87-f20ec3781f3e

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c1179d796babea5c
Upwork Job ID:<PHONE_NUMBER>329356800
Last Price Increase: 2024-05-22
Automatic offers:

ikevin127 | Reviewer | 102499784
cretadn22 | Contributor | 102499787

Issue OwnerCurrent Issue Owner: @ikevin127

We think this issue might be related to the #collect project.

Opening this up to the community.

♻ Reviewing proposals.

@Krishna2323 Your proposal's RCA is incomplete as only filtering out the disabled distance rates from the Rate option selector is not enough to fix this issue. See cretadn22's proposal RCA for more details.
Your main solution is not detailed enough for me to assess whether or not it would fix the issue. Even if it would be, since the RCA is not complete, it would most likely not tackle the issue fully.
Regarding your alternative solution, I think it adds too much overhead and new code when not necessary - besides this, I'm reserved when it comes to adding 2 additional arguments to a function that already has 23 arguments. I checked out your test branch and the same thing mentioned above applies:

only filtering out the disabled distance rates from the Rate option selector is not enough to fix this issue

Besides not fixing the issue completely, due to the changes from your test branch -> now there's no more difference in the UI when it comes to canUseAllBetas being true or false -> the Rate field is always visible as if canUseAllBetas is always true.

canUseAllBetas -> false on current main
canUseAllBetas -> false / true (your test branch)

@GandalfGwaihir Your proposal's RCA is incomplete as only filtering out the disabled distance rates from the Rate option selector is not enough to fix this issue. See cretadn22's proposal RCA for more details.
Your proposed solution only filters out the disabled distance rates from the Rates selector but if you follow the OP video carefully, once the new distance rate was added, the existing (default) one was disabled -> when reaching the confirmation page even though the existing (default) distance rate is disabled -> it still shows up as the default selected rate in the Rate option for both canUseAllBetas true and false UI variations, even though the rate is disabled.

@cretadn22 Your proposal's RCA is correct. Your solution is problematic since you don't clearly mention which part of the issue the suggested change is targeting. Additionally, your test branch does not help me in assessing whether your solution is working because of the following reasons:

It only implements 2 of the suggested bullet-point changes from your solution, the first bullet-point does not seem to be accounted for.
It uses getMileageRates before the function is defined.
I'm reserved when it comes to implementing the logic which includes the includeDisableRate argument as I think there's better and simpler ways of tackling this, avoiding the addition of unnecessary arguments.

Notes for contributors
Some pointers regarding issue complexity
This issue has 2 sides to it, see cretadn22's proposal RCA for more details. To get a better sense of the root cause I'd advise following these steps:

[!tip]

Log in and go to Collect workspace settings.
Go to Distance rates.
Click [+ Add rate].
Add a new rate.
Disable previously existing rate (0.67) such that only the newly added rate is Enabled.

Now before following the rest of the steps from OP, know that there are 2 different ways the UI can look when arriving on the Distance request confirmation page, and this differs based on whether your account canUseAllBetas.

canUseAllBetas -> false
canUseAllBetas -> true (OP)

Note: This can be enabled / disabled from src/libs/Permissions.ts by hardcode returning true / false for the canUseAllBetas function.
Some RCA & Solution pointers (from a reviewer's POV)
✅ Have a clear RCA that accounts for the entirety of the issue.
✅ Have a clear and technically detailed implementation of the solution, instead of a vague sentence.
✅ We need a solution which tackless the root cause for both canUseAllBetas UI scenarios, including consideration for offline pattern (if any).
✅ We need a clear and detailed technical implementation of the solution which I'm able to test OR a test branch which aligns with your proposal's solution. The test branch should reflect the final implementation as close as possible.
❌ Avoid adding extra parameters to existing functions which already have too many parameters.
❌ Avoid creating a test branch which does not entirely match everything mentioned in the proposed solution changes. Additionally, don't use variable / function names like abc as the test branch should reflect the final implementation as close as possible.

[!important]
The first contributor to update / post a new proposal considering all of the above will be selected on a first come, first served basis.

cc @Krishna2323 @GandalfGwaihir @cretadn22

Proposal
Please re-state the problem that we are trying to solve in this issue.
Disabled distance rate is present in the rate list in confirmation page
What is the root cause of that problem?

We don't clear lastSelectedDistanceRates of the policy when the rate is disable

We don't filter out the disabled rate here so the disabled rates still present in distance rate step page

https://github.com/Expensify/App/blob/aa9bbcfb9b5a1ae0dd8050efad11eeabd9f65c58/src/pages/iou/request/step/IOURequestStepDistanceRate.tsx#L55
What changes do you think we should make in order to solve the problem?

We should clear lastSelectedDistanceRates of a policy when the rate is disable. To do that we can handle the same way we handle report change here. It's something like this in Policy actions

const allPolicies: OnyxCollection<Policy> = {};
Onyx.connect({
    key: ONYXKEYS.COLLECTION.POLICY,
    callback: (val, key) => {
        ...
        handlePolicyChange(val);

        allPolicies[key] = val;
    },
});
let lastSelectedDistanceRates: OnyxEntry<LastSelectedDistanceRates> = {};
Onyx.connect({
    key: ONYXKEYS.NVP_LAST_SELECTED_DISTANCE_RATES,
    callback: (value) => {
        lastSelectedDistanceRates = value;
    },
});

function handlePolicyChange(policy: OnyxEntry<Policy>) {
    if (!policy || !lastSelectedDistanceRates?.[policy?.id ?? '']) {
        return;
    }

    const rateID = lastSelectedDistanceRates?.[policy?.id ?? ''];
    const distanceUnit = Object.values(policy?.customUnits ?? {}).find((unit) => unit.name === CONST.CUSTOM_UNITS.NAME_DISTANCE);
    const distanceRate = distanceUnit?.rates?.[rateID];

    if (!distanceRate?.enabled) {
        Onyx.merge(ONYXKEYS.NVP_LAST_SELECTED_DISTANCE_RATES, {[policy.id] : null});
    }
}

In getDefaultMileageRate, we should return an extra field enabled: rate.enabled to know a rate is disabled or not

https://github.com/Expensify/App/blob/aa9bbcfb9b5a1ae0dd8050efad11eeabd9f65c58/src/libs/DistanceRequestUtils.ts#L51

To make distance rate step has the same behavior with other steps like tag, category, we will filter out that disabled rate that isn't the selected rate and return an extra field isDisabled: !rate.enable. So if the selected rate is disabled, it can be displayed with grey out

const sections = Object.values(rates).filter((rate) => rate.enabled || rate.customUnitRateID === lastSelectedRateID).map((rate) => {
    const rateForDisplay = DistanceRequestUtils.getRateForDisplay(rate.unit, rate.rate, rate.currency, translate, toLocaleDigit);

    return {
        ...
        isDisabled: !rate.enabled,
    };
});

https://github.com/Expensify/App/blob/aa9bbcfb9b5a1ae0dd8050efad11eeabd9f65c58/src/pages/iou/request/step/IOURequestStepDistanceRate.tsx#L55
What alternative solutions did you explore? (Optional)
NA

♻ Reviewing proposals once again.

@nkdengineer Thank you for your proposal. Your proposal's RCA is correct and complete since it was already pointed out previously. As far as your solution goes, though it would fix the issue, due to the different route you approached when it comes to disabling the Rate list options -> this does not match with the expected result which states:

Disabled distance rate is not present in the rate list in confirmation page

If the assigned CME decides that we want to involve design and adjust the expected result to match your proposed solution, then I would be willing to reconsider assignment.

@cretadn22's updated proposal looks good to me! They were first to identify the root cause correctly and completely and first to update their proposal after initial review. Their updated main solution / test branch fixes the issue accordingly as per issue's expected result by:

Defaulting distance rate to the first enabled when the Rate field is not shown (users with betas disabled).
(1.) + Not displaying the disabled distance rates in the Rate field list (users with betas enabled).

Video / Screenshot of Fix

canUseAllBetas -> true
canUseAllBetas -> false

🎀👀🎀 C+ reviewed

@cretadn22's updated proposal looks good to me! They were first to identify the root cause correctly and completely and first to update their proposal after initial review. Their updated main solution / test branch fixes the issue accordingly as per issue's expected result by:

Defaulting distance rate to the first enabled when the Rate field is not shown (users with betas disabled).
(1.) + Not displaying the disabled distance rates in the Rate field list (users with betas enabled).

Video / Screenshot of Fix
🎀👀🎀 C+ reviewed

@cretadn22's updated proposal looks good to me! They were first to identify the root cause correctly and completely and first to update their proposal after initial review. Their updated main solution / test branch fixes the issue accordingly as per issue's expected result by:

Defaulting distance rate to the first enabled when the Rate field is not shown (users with betas disabled).
(1.) + Not displaying the disabled distance rates in the Rate field list (users with betas enabled).

Video / Screenshot of Fix
🎀👀🎀 C+ reviewed

Cool thanks, looks good to me to. I guess we forgot about handling this during the initial implementation.

Awaiting for PR to be open!

The PR was reverted because it had regressions and no follow-up fix was provided in a timely manner, therefore a revert was performed.
What's next ?

@cretadn22 Can let us know if they want to re-work the solution in a new PR, making sure to test it better this time (both author and reviewer), accounting for the regression issues encountered after initial PR was merged (#43197 and #43171).
If initial contributor does not want to re-work the solution in a new PR, we would re-open the issue to proposals.

@cretadn22 Sorry, my bad - I just noticed the revert PR being closed and the issue being fixed somewhere else.
So the regression was indeed caused by our PR, or it was another PR / unrelated ?
cc @neil-marcellini

[x]  [@ikevin127] The PR that introduced the bug has been identified. Link to the PR: #38543.
[x]  [@ikevin127] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: #38543 (comment).
[x]  [@ikevin127] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x]  [@ikevin127] Determine if we should create a regression test for this bug.
[x]  [@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal
Test 1
Precondition: User does NOT have betas enabled, hence no Rate field will be displayed in Distance confirmation page.

Log in and go to a new Collect workspace settings page.
Enable Distance rates and go to Distance rates page.
Click [+ Add rate].
Add a new rate and make sure it's Enabled.
Disable previously existing distance rate (the default $0.670 / mile rate).
Go to the workspace chat.
Click composer [+] and proceed to Submit expense > Distance request.
On Distance confirmation page, verify that the enabled rate is set as default in the Distance field (see below).

Test 2
Precondition: User does have betas enabled, hence the Rate field will be displayed in Distance confirmation page.

Log in and go to a new Collect workspace settings page.
Enable Distance rates and go to Distance rates page.
Click [+ Add rate].
Add a new rate and make sure it's Enabled.
Disable previously existing distance rate (the default $0.670 / mile rate).
Go to the workspace chat.
Click composer [+] and proceed to Submit expense > Distance request.
On Distance confirmation page, verify that the enabled rate is set as default in the Rate field (see [1.]).
On Distance confirmation page, click on the Rate field and verify that the disabled rate is not displayed (see [2.]).

1
2

Do we agree 👍 or 👎.

⚠ Not sure why the automation added the second HOLD date her, since the PR was deployed 4 days ago according to https://github.com/Expensify/App/pull/42330#issuecomment-2161772275 -> therefore the [HOLD for payment 2024-06-18] is the correct payment date.
Summary:

PR was merged 2 weeks ago according to automation #42330 (comment) but wasn't deployed to staging / production
PR was deployed to production 4 days ago -> compensation due for contributor / reviewer on 2024-06-18

Note: Some regressions were associated with this PR, which if confirmed -> the compensation will be reduced. I asked @neil-marcellini to confirm this above in https://github.com/Expensify/App/issues/42284#issuecomment-2156123530 so that everything is clear and ready for payment when due.
cc @JmillsExpensify

Yes there was a regression caused by https://github.com/Expensify/App/pull/42330

Payment issued to @ikevin127 and @cretadn22 factoring in regression 👍

done


BUG 2115507: rbd: consider mirror deamon state for ResyncVolume

During ResyncVolume, we check if the image is in an error state, and we resync. After resync, the image will move to either the Error or the Resyncing state. And if the image is in the above two conditions, we will return a successful response and Ready=false so that the consumer can wait until the volume is ready to use. If the image is in any other state we return an error message to indicate the syncing is not going on. The whole resync and image state change depends on the rbd mirror daemon. If the mirror daemon is not running, the image can be in Resyncing or Unknown state. The Ramen marks the volume replication as secondary, and once the resync starts, it will delete the volume replication CR as a cleanup process.
As we dont have a check for the rbd mirror daemon, we are returning a resync success response and Ready=false. Due to this false response, Ramen is assuming the resync started and deleted the volume replication CR. Because of this, the cluster goes into a bad state and needs manual intervention.
upstream PR https://github.com/ceph/ceph-csi/pull/3290
downstream devel branch sync PR https://github.com/red-hat-storage/ceph-csi/pull/118
/assign @agarwal-mudit

/assign @nixpanic

/lgtm
/approved


Nullpointer while inserting cache values above 6mb

I've configured memcached 1.4.22 and could see that every attempt to insert data sized more than ~6MB is giving me the following error:
2018-01-30 22:17:00.645 INFO net.spy.memcached.MemcachedConnection:  Reconnecting due to exception on {QA sa=/<IP_ADDRESS>.5:11211, #Rops=0, #Wops=1, #iq=0, topRop=null, topWop=Cmd: 1 O
paque: 505 Key: app:cceabea9aaeb58418912fb56762dc0c7c927e150:cceabea9aaeb58418912fb56762dc0c7c927e150 Cas: 0 Exp: 2592000 Flags: 2050 Data Length: 1902195, toWrite=0, interested=4}
java.lang.NullPointerException
        at net.spy.memcached.protocol.TCPMemcachedNodeImpl.fillWriteBuffer(TCPMemcachedNodeImpl.java:206)

The size value configured for memcached is 10000
Any comments on what could be the issue here?

Btw, I received similar issue to @a2l007 but simply increasing the maxSize didnt work for me. I am inserting data of size ~12MB into memcached.
Issue: https://github.com/monix/shade/issues/64

@rohantandon96 please don't necro random old issues :(
It looks like you're setting the maxSize for spymemcached but probably not increasing the max item size for memcached itself, so the server would reject you.

@dormando sorry about that.
I did increase the max item size on memcached itself and not for spyMemcached.

@anthonyryan1 you didn't show anything about what you changed with memcached, what version it's running/etc.

Ah, we can't really support the AWS version. You could try opening a raw connection to the instance and SET a value of the size you want and see what happens. it's trivial to generate a raw text protocol request.
If you get an error it's something you'll have to take up with AWS, sorry.

ah thanks for that @dormando. What version of memcached do you support? Maybe I can bump up/down the version based on your support and then try.

None of them. We can give some support but if you're using their tooling (and it's unclear if they've made modifications to the daemon like they have in the past) you're stuck with them. I support the actual project; the latest versions. If something's wrong you can't exactly upgrade to deal with it :)
What we can do: if you supply output of stats and stats settings and do what I suggested by writing a SET command to an instance and seeing what happens, we can troubleshoot a little bit. AWS's control panel means nothing to me though.
Also this is still the wrong venue; please open a new issue or try the mailing list/discord for support.


Request 100 periods before start time and throw them away

Blocktap's indicators begin at the first requested timeseries data. This leads to the chart displaying the SMA50 and SMA20 as the same line for a period of time. To get around this issue, cryptolist should request n periods before the start time (where n is the max indicator period, currently 100), then throw them away.

This doesn't apply since we are using tradingview's TA tools


Forge 1.20.1 Crash Just after start

Caused by: java.lang.UnsupportedOperationException: A mod tried to access the state neighbor table directly. Please report this at https://github.com/malte0811/FerriteCore/issues. As a temporary workaround you can enable "populateNeighborTable" in the FerriteCore config
Logs.txt

Here's my start.log.


Mc burn

Added a burn in optional keyword argument to mc_simulate_path and various other testing fixes

Coverage decreased (-18.27%) to 52.92% when pulling 99ef91666fa3a20a38ea158685fd4adb1d84a854 on mc_burn into 3ed25fc05de2920e57fa8be59355ca2d2a67902c on master.


pull request for e2e test at 11/10/2016 23:15:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Security improvements

Here is a list of things we might want to do to improve security. Refer to the OWASP cheat sheets for details.

[x] Strict Transport Security - enforce HTTPS. This should be for the whole site, not the API. It needs to be done carefully with a check for mixed content first. See this blog post for useful details.
Impact: High 🔴
Effort: Medium 🟠
[ ] Content Security Policy (+ MDN) - For prevention of XSS. Should be tested with report-only first. Supersedes X-XSS-Protection.
Impact: High 🔴
Effort: Medium 🟠
[x] Disable all admin-related endpoints, validations and authorisations - these are no longer required.
Impact: High 🔴
Effort: Medium 🟠
[x] Review all user input validation and rendering of user input (ie injection and XSS attacks)
Impact: Medium 🟠
Effort: Medium 🟠
[x] Other minor security headers. Eg X-Frame-Options, X-Content-Type-Options.
Impact: Low 🟢
Effort: Low 🟢
[x] Explicit SameSite: Lax for session cookie - this is the default in recent browsers but should be explicit
Impact: Low 🟢
Effort: Low 🟢
[x] Make the identity API authorizer deny-by-default - currently the fallthrough case in the authorizer is to allow access. This should be refactored to be deny-by-default.
Impact: Low 🟢
Effort: Low 🟢

Closing for now as CSP is difficult and we have no evidence that we really require it right now