Tomoya Fujita

Pulls: ros2/rclcpp#2727 Gist: https://gist.githubusercontent.com/fujitatomoya/c0eb64b8725e475fdc01c47961b19ec7/raw/8dd8072602bdaaaf0b0391fff4bdd9e6d9b790ed/ros2.repos BUILD args: --packages-above-and-dependencies rclcpp TEST args: --packages-above rclcpp ROS Distro: rolling Job: ci_launcher ci_launcher ran: https://ci.ros2.org/job/ci_launcher/15290 * Linux [](http://ci.ros2.org/job/ci_linux/22639/) * Linux-aarch64 [](http://ci.ros2.org/job/ci_linux-aarch64/16881/) * Linux-rhel...

@bks-ol someone else needs to review this, we are pretty much occupied for next distro release for now.

@black-puppydog related issues and discussion, - https://github.com/colcon/colcon-core/issues/454 - https://discourse.ros.org/t/call-for-testing-standards-based-python-packaging-with-colcon/32008

@sxz1024 DCO is still missing, i think that you need to sign with `git commit --signoff`.

> KubeEdge cluster with 1 cloudcore and 2 edgecores. 1 of the edge nodes works fine the other one keeps changing its status between Ready and NotReady. seems like one...

either @XmchxUp @FengGaoCSC please chime in if you have something to share. @vofr did you resolve this error? any update?

@vofr just a quick question, those edge nodes are in the same network? if not, that would be problem to configure Cilium though. it expects all cilium nodes are accessible,...

@vofr can we see if your problem can be observed with k8s worker nodes only without kubeedge? if that happens, that is the generic issue between k8s and cilium, right?...