SR300: /camera/driver - Error calling rs_wait_for_frames

Required Info

Camera Model
SR300

Operating System & Version
Ubuntu 14.04

Kernel Version (Linux Only)
4.4.0

Issue Description
<Describe your issue / question / feature request / etc..>
I installed the librealsense following the instruction in https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md#Troubleshooting
When I run
roslaunch realsense_camera sr300_nodelet_default.launch
I have the following errors.
... logging to /home/fetch/.ros/log/48698a5a-03d0-11e9-9c86-d8cb8a5dca62/roslaunch-fetch6-4200.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fetch6:35116/
SUMMARY
PARAMETERS

/camera/driver/base_frame_id: camera_link
/camera/driver/camera_type: SR300
/camera/driver/color_fps: 30
/camera/driver/color_frame_id: camera_rgb_frame
/camera/driver/color_optical_frame_id: camera_rgb_optica...
/camera/driver/depth_frame_id: camera_depth_frame
/camera/driver/depth_height: 480
/camera/driver/depth_optical_frame_id: camera_depth_opti...
/camera/driver/depth_width: 640
/camera/driver/fisheye_frame_id: camera_fisheye_frame
/camera/driver/fisheye_optical_frame_id: camera_fisheye_op...
/camera/driver/imu_frame_id: camera_imu_frame
/camera/driver/imu_optical_frame_id: camera_imu_optica...
/camera/driver/ir2_frame_id: camera_ir2_frame
/camera/driver/ir2_optical_frame_id: camera_ir2_optica...
/camera/driver/ir_frame_id: camera_ir_frame
/camera/driver/ir_optical_frame_id: camera_ir_optical...
/camera/driver/mode: manual
/camera/driver/serial_no:
/camera/driver/usb_port_id:
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/camera/
driver (nodelet/nodelet)
nodelet_manager (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[camera/nodelet_manager-1]: started with pid [4222]
process[camera/driver-2]: started with pid [4223]
[ INFO] [1545256733.842314026]: Initializing nodelet with 4 worker threads.
[ INFO] [1545256734.206235227]: /camera/driver - Detected the following camera:
- Serial No:<PHONE_NUMBER>98, USB Port ID: 7-1-1, Name: Intel RealSense SR300, Camera FW: <IP_ADDRESS>
[ WARN] [1545256734.206276330]: /camera/driver - Detected unvalidated firmware:
-<PHONE_NUMBER>98's current camera firmware is <IP_ADDRESS>, Validated camera firmware is <IP_ADDRESS>
[ INFO] [1545256734.206292011]: /camera/driver - Connecting to camera with Serial No:<PHONE_NUMBER>98, USB Port ID: 7-1-1
[ INFO] [1545256735.584291085]: /camera/driver - Setting static camera options
[ INFO] [1545256735.585747249]: /camera/driver - Enabling Depth in manual mode
[ INFO] [1545256735.586014152]: /camera/driver - Enabling Color in manual mode
[ INFO] [1545256735.586315444]: /camera/driver - Starting camera
[ INFO] [1545256735.592578755]: /camera/driver - Publishing camera transforms (/tf_static)
[ INFO] [1545256735.592727578]: /camera/driver - Setting dynamic camera options
[ERROR] [1545256742.069283310]: /camera/driver - Error calling rs_wait_for_frames ( device:0x109b908 ):
Timeout waiting for frames.
[camera/nodelet_manager-1] process has died [pid 4222, exit code -11, cmd /opt/ros/indigo/lib/nodelet/nodelet manager __name:=nodelet_manager __log:=/home/fetch/.ros/log/48698a5a-03d0-11e9-9c86-d8cb8a5dca62/camera-nodelet_manager-1.log].
log file: /home/fetch/.ros/log/48698a5a-03d0-11e9-9c86-d8cb8a5dca62/camera-nodelet_manager-1.log*
[camera/driver-2] process has finished cleanly
log file: /home/fetch/.ros/log/48698a5a-03d0-11e9-9c86-d8cb8a5dca62/camera-driver-2*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
Don't know how to fix it. Can anyone helps me with this? Thank you so much!

[Realsense Customer Engineering Team Comment]
Hi @pl95,
Please use below ROS wrapper and SR300 latest firmware <IP_ADDRESS>.
https://github.com/intel-ros/realsense

Hi @RealSense-Customer-Engineering
I follow the instruction and have an make fail when I run
catkin_make -DCATKIN_ENABLE_TESTING=False -DCMAKE_BUILD_TYPE=Release
Base path: /home/fetch/catkin_ws
Source space: /home/fetch/catkin_ws/src
Build space: /home/fetch/catkin_ws/build
Devel space: /home/fetch/catkin_ws/devel
Install space: /home/fetch/catkin_ws/install

Running command: "cmake /home/fetch/catkin_ws/src -DCATKIN_ENABLE_TESTING=False -DCATKIN_DEVEL_PREFIX=/home/fetch/catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/home/fetch/catkin_ws/install -G Unix Makefiles" in "/home/fetch/catkin_ws/build"

-- Using CATKIN_DEVEL_PREFIX: /home/fetch/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/fetch/catkin_ws/devel;/opt/ros/indigo
-- This workspace overlays: /home/fetch/catkin_ws/devel;/opt/ros/indigo
-- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: False
-- catkin 0.6.19
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 1 packages in topological order:
-- ~~  - realsense2_camera
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin package: 'realsense2_camera'
-- ==> add_subdirectory(realsense-2.0.3/realsense2_camera)
-- Using these message generators: gencpp;genlisp;genpy
-- Create Debug Build.
-- realsense2_camera: 2 messages, 0 services
-- Configuring done
-- Generating done
-- Build files have been written to: /home/fetch/catkin_ws/build

Running command: "make -j4 -l4" in "/home/fetch/catkin_ws/build"

[  0%] Built target tf2_msgs_generate_messages_py
[  0%] [  0%] Built target roscpp_generate_messages_cpp
Built target dynamic_reconfigure_generate_messages_cpp
[  0%] [  0%] Built target sensor_msgs_generate_messages_cpp
Built target std_msgs_generate_messages_cpp
[  0%] Built target _realsense2_camera_generate_messages_check_deps_Extrinsics
[  0%] Built target std_msgs_generate_messages_lisp
[  0%] [  0%] Built target geometry_msgs_generate_messages_py
Built target sensor_msgs_generate_messages_lisp
[  0%] [ 25%] Built target _realsense2_camera_generate_messages_check_deps_IMUInfo
Built target realsense2_camera_gencfg
[ 25%] Built target nodelet_generate_messages_py
[ 25%] [ 25%] Built target geometry_msgs_generate_messages_lisp
Built target tf_generate_messages_py
[ 25%] Built target sensor_msgs_generate_messages_py
[ 25%] Built target _catkin_empty_exported_target
[ 25%] [ 25%] [ 25%] Built target roscpp_generate_messages_py
Built target bond_generate_messages_py
Built target roscpp_generate_messages_lisp
[ 25%] Built target rosgraph_msgs_generate_messages_py
[ 25%] [ 25%] Built target nodelet_generate_messages_cpp
Built target rosgraph_msgs_generate_messages_lisp
[ 25%] Built target bond_generate_messages_cpp
[ 25%] [ 25%] Built target std_msgs_generate_messages_py
Built target bond_generate_messages_lisp
[ 25%] [ 25%] Built target rosgraph_msgs_generate_messages_cpp
Built target tf_generate_messages_lisp
[ 25%] [ 25%] [ 25%] Built target diagnostic_msgs_generate_messages_lisp
Built target tf_generate_messages_cpp
Built target nodelet_generate_messages_lisp
[ 25%] Built target geometry_msgs_generate_messages_cpp
[ 25%] [ 25%] Built target tf2_msgs_generate_messages_cpp
Built target diagnostic_msgs_generate_messages_cpp
[ 25%] [ 25%] Built target actionlib_msgs_generate_messages_cpp
Built target actionlib_generate_messages_cpp
[ 25%] [ 25%] Built target actionlib_generate_messages_py
Built target actionlib_generate_messages_lisp
[ 25%] Built target diagnostic_msgs_generate_messages_py
[ 25%] Built target dynamic_reconfigure_generate_messages_py
[ 25%] Built target actionlib_msgs_generate_messages_py
[ 25%] Built target actionlib_msgs_generate_messages_lisp
[ 25%] Built target dynamic_reconfigure_generate_messages_lisp
[ 25%] Built target dynamic_reconfigure_gencfg
[ 25%] [ 43%] Built target tf2_msgs_generate_messages_lisp
Built target realsense2_camera_generate_messages_py
[ 56%] Built target realsense2_camera_generate_messages_lisp
[ 68%] Built target realsense2_camera_generate_messages_cpp
[ 68%] Built target realsense2_camera_generate_messages
[ 75%] Building CXX object realsense-2.0.3/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o
/home/fetch/catkin_ws/src/realsense-2.0.3/realsense2_camera/src/base_realsense_node.cpp:384:0: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
#pragma omp parallel for schedule(dynamic)
^
In file included from /usr/local/include/librealsense2/hpp/rs_device.hpp:8:0,
from /usr/local/include/librealsense2/hpp/rs_record_playback.hpp:8,
from /usr/local/include/librealsense2/hpp/rs_context.hpp:8,
from /usr/local/include/librealsense2/rs.hpp:9,
from /home/fetch/catkin_ws/src/realsense-2.0.3/realsense2_camera/src/../include/../include/realsense_node_factory.h:11,
from /home/fetch/catkin_ws/src/realsense-2.0.3/realsense2_camera/src/../include/base_realsense_node.h:6,
from /home/fetch/catkin_ws/src/realsense-2.0.3/realsense2_camera/src/base_realsense_node.cpp:1:
/usr/local/include/librealsense2/hpp/rs_sensor.hpp: In instantiation of ‘void rs2::frame_callback::on_frame(rs2_frame*) [with T = rs2::asynchronous_syncer; rs2_frame = rs2_frame]’:
/home/fetch/catkin_ws/src/realsense-2.0.3/realsense2_camera/src/base_realsense_node.cpp:1394:1:   required from here
/usr/local/include/librealsense2/hpp/rs_sensor.hpp:109:13: error: no match for call to ‘(rs2::asynchronous_syncer) (rs2::frame)’
on_frame_function(frame{ fref });
^
make[2]: *** [realsense-2.0.3/realsense2_camera/CMakeFiles/realsense2_camera.dir/src/base_realsense_node.cpp.o] Error 1
make[1]: *** [realsense-2.0.3/realsense2_camera/CMakeFiles/realsense2_camera.dir/all] Error 2
make: *** [all] Error 2
Invoking "make -j4 -l4" failed
I am using the 2.0.3 release. Also, how can I get the firmware version and how to update to the latest version?

[Realsense Customer Engineering Team Comment]
Hi @pl95,
Which librealsense version did you install? Please try to build and install LibRealSense v2.10.2. The latest librealsense version is not compatible with ros wrapper 2.0.3.
You can install SR300 DCM and it will upgrade your firmware automatically.
https://downloadcenter.intel.com/download/25044/Intel-RealSense-Depth-Camera-Manager?product=92329

Hi @pl95,
Did you try the latest ROS wrapper on ROS Kinetic? If no additional support required, will close this.

Hi,
I didn't try the ROS wrapper on ROS Kinetic. Because I have ROS indigo
instead of ROS Kinetic, and everything else on the computer is build for
Indigo.  I don't think I can upgrade the ROS version to Kinetic. I do need
additional support. When I run the rgbd launch file, it sometimes gives me
the following error.
... logging to
/home/fetch/.ros/log/09768c8e-3aa4-11e9-aa0b-d8cb8a5dca62/roslaunch-fetch6-27004.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fetch6:40598/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: 1000
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: True
/camera/realsense2_camera/camera_aligned_depth_to_color_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_fisheye_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra1_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra2_frame_id:
camera_aligned_de...
/camera/realsense2_camera/color_fps: 30
/camera/realsense2_camera/color_height: 480
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: 640
/camera/realsense2_camera/depth_fps: 30
/camera/realsense2_camera/depth_height: 480
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: 640
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye: True
/camera/realsense2_camera/enable_imu: True
/camera/realsense2_camera/enable_infra1: True
/camera/realsense2_camera/enable_infra2: True
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_sync: True
/camera/realsense2_camera/fisheye_fps: 30
/camera/realsense2_camera/fisheye_height: 480
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: 640
/camera/realsense2_camera/gyro_fps: 1000
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/infra1_fps: 30
/camera/realsense2_camera/infra1_height: 480
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra1_width: 640
/camera/realsense2_camera/infra2_fps: 30
/camera/realsense2_camera/infra2_height: 480
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra2_width: 640
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/serial_no:
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/camera/
color_rectify_color (nodelet/nodelet)
points_xyzrgb_hw_registered (nodelet/nodelet)
points_xyzrgb_sw_registered (nodelet/nodelet)
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
register_depth (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[camera/realsense2_camera_manager-1]: started with pid [27022]
process[camera/realsense2_camera-2]: started with pid [27023]
process[camera/color_rectify_color-3]: started with pid [27029]
process[camera/register_depth-4]: started with pid [27034]
process[camera/points_xyzrgb_sw_registered-5]: started with pid [27036]
process[camera/points_xyzrgb_hw_registered-6]: started with pid [27039]
[ INFO] [1551298797.817294736]: Initializing nodelet with 4 worker threads.
[ INFO] [1551298797.855250530]: RealSense ROS v2.0.3
[ INFO] [1551298797.855337152]: Running with LibRealSense v2.10.2
[ INFO] [1551298798.035325506]: getParameters...
[ INFO] [1551298798.069852915]: setupDevice...
[ INFO] [1551298798.069888008]: JSON file is not provided
[ INFO] [1551298798.069908264]: ROS Node Namespace: camera
[ INFO] [1551298798.069926606]: Device Name: Intel RealSense SR300
[ INFO] [1551298798.069940006]: Device Serial No:<PHONE_NUMBER>98
[ INFO] [1551298798.069951032]: Device FW version: <IP_ADDRESS>
[ INFO] [1551298798.069961308]: Device Product ID: 0x0AA5
[ INFO] [1551298798.069974564]: Enable PointCloud: Off
[ INFO] [1551298798.069983016]: Align Depth: On
[ INFO] [1551298798.069991538]: Sync Mode: On
[ INFO] [1551298798.070016186]: Device Sensors:
[ INFO] [1551298798.070043105]: Coded-Light Depth Sensor was found.
[ INFO] [1551298798.070054765]: RGB Camera was found.
[ INFO] [1551298798.070082161]: (Infrared, 2) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551298798.070096865]: (Fisheye, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551298798.070109340]: (Gyro, 0) sensor isn't supported by current
device! -- Skipping...
[ INFO] [1551298798.070118883]: (Accel, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551298798.070131148]: setupPublishers...
[ INFO] [1551298798.073014407]: Expected frequency for depth = 30.00000
[ INFO] [1551298798.202256525]: Expected frequency for infra1 = 30.00000
[ INFO] [1551298798.225239333]: Expected frequency for
aligned_depth_to_infra1 = 30.00000
[ INFO] [1551298798.251012841]: Expected frequency for color = 30.00000
[ INFO] [1551298798.272607788]: Expected frequency for
aligned_depth_to_color = 30.00000
[ INFO] [1551298798.294500488]: setupStreams...
27/02 15:19:58,294 WARNING [140095634999232] (sensor.cpp:313) Unregistered
Media formats : [ INZC PAIR YUYV ]; Supported: [ ]
[ INFO] [1551298798.295241903]: depth stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551298798.295538761]: infra1 stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551298798.296678607]: color stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551298798.301602210]: publishStaticTransforms...
[ INFO] [1551298798.301751608]: RealSense Node Is Up!
27/02 15:19:58,305 WARNING [140094721324800] (backend-v4l2.cpp:808) Empty
frame has arrived.
27/02 15:19:58,305 WARNING [140094721324800] (backend-v4l2.cpp:808) Empty
frame has arrived.
27/02 15:19:58,305 WARNING [140094721324800] (backend-v4l2.cpp:808) Empty
frame has arrived.
27/02 15:19:58,305 WARNING [140094721324800] (backend-v4l2.cpp:808) Empty
frame has arrived.
 But it still won't have any image.
Following is the log.
... logging to
/home/fetch/.ros/log/09ec9f3a-3ace-11e9-9358-d8cb8a5dca62/roslaunch-fetch6-4710.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fetch6:42654/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: 1000
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: True
/camera/realsense2_camera/camera_aligned_depth_to_color_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_fisheye_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra1_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra2_frame_id:
camera_aligned_de...
/camera/realsense2_camera/color_fps: 30
/camera/realsense2_camera/color_height: 480
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: 640
/camera/realsense2_camera/depth_fps: 30
/camera/realsense2_camera/depth_height: 480
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: 640
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye: True
/camera/realsense2_camera/enable_imu: True
/camera/realsense2_camera/enable_infra1: True
/camera/realsense2_camera/enable_infra2: True
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_sync: True
/camera/realsense2_camera/fisheye_fps: 30
/camera/realsense2_camera/fisheye_height: 480
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: 640
/camera/realsense2_camera/gyro_fps: 1000
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/infra1_fps: 30
/camera/realsense2_camera/infra1_height: 480
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra1_width: 640
/camera/realsense2_camera/infra2_fps: 30
/camera/realsense2_camera/infra2_height: 480
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra2_width: 640
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/serial_no:
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/camera/
color_rectify_color (nodelet/nodelet)
points_xyzrgb_hw_registered (nodelet/nodelet)
points_xyzrgb_sw_registered (nodelet/nodelet)
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
register_depth (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[camera/realsense2_camera_manager-1]: started with pid [4728]
process[camera/realsense2_camera-2]: started with pid [4729]
process[camera/color_rectify_color-3]: started with pid [4730]
process[camera/register_depth-4]: started with pid [4740]
process[camera/points_xyzrgb_sw_registered-5]: started with pid [4749]
process[camera/points_xyzrgb_hw_registered-6]: started with pid [4751]
[ INFO] [1551299271.647355610]: Initializing nodelet with 4 worker threads.
I will need the pointcloud data later. Could you help me figure out what is
wrong with this?
Thank you so much!
On Wed, Feb 27, 2019 at 9:37 AM RealSense Customer Support <
<EMAIL_ADDRESS>wrote:

Hi @pl95 https://github.com/pl95,
Did you try the latest ROS wrapper on ROS Kinetic? If no additional
support required, will close this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/2935#issuecomment-467885368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aif031eA_d5_etcWNa0B0SfeGMFVXOR4ks5vRpglgaJpZM4ZbGcU
.

Hi @pl95,

From "top" log, it looks the overall cpu consumption/loading is quite heavy when you run "demo_pointcloud".  Please run also "lscpu" to show the info.
Try below command to see how it works.
$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
Indeed, above DCM exe command is used for Windows to upgrade your SR300 firmware.
So far, I don't have Ubuntu 14.04 + Indigo environment. Will try to setup to see how it goes.

HI,

The "lscpu" log when "demo_pointclould" is running:
$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 60
Stepping:              3
CPU MHz:               3226.816
BogoMIPS:              5799.92
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3

"lscpu" log when "demo_pointcloud" NOT running:
$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 60
Stepping:              3
CPU MHz:               3306.453
BogoMIPS:              5799.92
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3
2. $ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
... logging to
/home/fetch/.ros/log/c5bee004-410b-11e9-b06f-d8cb8a5dca62/roslaunch-fetch6-16790.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fetch6:40161/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: 1000
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: False
/camera/realsense2_camera/camera_aligned_depth_to_color_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_fisheye_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra1_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra2_frame_id:
camera_aligned_de...
/camera/realsense2_camera/color_fps: 30
/camera/realsense2_camera/color_height: 480
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: 640
/camera/realsense2_camera/depth_fps: 30
/camera/realsense2_camera/depth_height: 480
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: 640
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye: True
/camera/realsense2_camera/enable_imu: True
/camera/realsense2_camera/enable_infra1: True
/camera/realsense2_camera/enable_infra2: True
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/fisheye_fps: 30
/camera/realsense2_camera/fisheye_height: 480
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: 640
/camera/realsense2_camera/gyro_fps: 1000
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/infra1_fps: 30
/camera/realsense2_camera/infra1_height: 480
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra1_width: 640
/camera/realsense2_camera/infra2_fps: 30
/camera/realsense2_camera/infra2_height: 480
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra2_width: 640
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/serial_no:
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[camera/realsense2_camera_manager-1]: started with pid [16808]
process[camera/realsense2_camera-2]: started with pid [16809]
[ INFO] [1551988395.758642023]: Initializing nodelet with 4 worker threads.
[ INFO] [1551988395.795874419]: RealSense ROS v2.0.3
[ INFO] [1551988395.795911935]: Running with LibRealSense v2.10.2
[ INFO] [1551988395.971667137]: getParameters...
[ INFO] [1551988396.002472106]: setupDevice...
[ INFO] [1551988396.002507340]: JSON file is not provided
[ INFO] [1551988396.002535316]: ROS Node Namespace: camera
[ INFO] [1551988396.002557651]: Device Name: Intel RealSense SR300
[ INFO] [1551988396.002573471]: Device Serial No:<PHONE_NUMBER>98
[ INFO] [1551988396.002587263]: Device FW version: <IP_ADDRESS>
[ INFO] [1551988396.002599760]: Device Product ID: 0x0AA5
[ INFO] [1551988396.002610195]: Enable PointCloud: Off
[ INFO] [1551988396.002622229]: Align Depth: Off
[ INFO] [1551988396.002640664]: Sync Mode: Off
[ INFO] [1551988396.002677609]: Device Sensors:
[ INFO] [1551988396.002709250]: Coded-Light Depth Sensor was found.
[ INFO] [1551988396.002724746]: RGB Camera was found.
[ INFO] [1551988396.002760196]: (Infrared, 2) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002773979]: (Fisheye, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002802157]: (Gyro, 0) sensor isn't supported by current
device! -- Skipping...
[ INFO] [1551988396.002816048]: (Accel, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002836535]: setupPublishers...
[ INFO] [1551988396.006296502]: Expected frequency for depth = 30.00000
[ INFO] [1551988396.126424813]: Expected frequency for infra1 = 30.00000
[ INFO] [1551988396.147114510]: Expected frequency for color = 30.00000
[ INFO] [1551988396.169324198]: setupStreams...
07/03 14:53:16,169 WARNING [140206503659456] (sensor.cpp:313) Unregistered
Media formats : [ INZC PAIR YUYV ]; Supported: [ ]
[ INFO] [1551988396.169831753]: depth stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551988396.169954137]: infra1 stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551988396.170957074]: color stream is enabled - width: 640,
height: 480, fps: 30
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
[ INFO] [1551988396.178935074]: publishStaticTransforms...
[ INFO] [1551988396.179070655]: RealSense Node Is Up!
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
Raw image, depth image and infra image are received. But poincloud data is
not received.
On Thu, Mar 7, 2019 at 4:35 AM RealSense Customer Support <
<EMAIL_ADDRESS>wrote:

Hi @pl95 https://github.com/pl95,

From "top" log, it looks the overall cpu consumption/loading is
quite heavy when you run "demo_pointcloud". Please run also "lscpu" to show
the info.
Try below command to see how it works.
$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
Indeed, above DCM exe command is used for Windows to upgrade your
SR300 firmware.
So far, I don't have Ubuntu 14.04 + Indigo environment. Will try to
setup to see how it goes.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/2935#issuecomment-470453129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aif038BgzQ0sMAL_CUVbkB_vnMO_LBYlks5vUN1CgaJpZM4ZbGcU
.

Hi,
I re-installed the point cloud package and check the image when I run the
demo_point cloud.  It shows images now when I run the demo. But I still not
have any image data for rs_rgbd.launch,
Is this information helps you solve the problem? Thank you so much for your
patience!
On Thu, Mar 7, 2019 at 3:04 PM Purong Liu<EMAIL_ADDRESS>wrote:

HI,

The "lscpu" log when "demo_pointclould" is running:
$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 60
Stepping:              3
CPU MHz:               3226.816
BogoMIPS:              5799.92
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3

"lscpu" log when "demo_pointcloud" NOT running:
$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 60
Stepping:              3
CPU MHz:               3306.453
BogoMIPS:              5799.92
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3
2. $ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
... logging to
/home/fetch/.ros/log/c5bee004-410b-11e9-b06f-d8cb8a5dca62/roslaunch-fetch6-16790.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://fetch6:40161/
SUMMARY
PARAMETERS

/camera/realsense2_camera/accel_fps: 1000
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: False
/camera/realsense2_camera/camera_aligned_depth_to_color_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_fisheye_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra1_frame_id:
camera_aligned_de...
/camera/realsense2_camera/camera_aligned_depth_to_infra2_frame_id:
camera_aligned_de...
/camera/realsense2_camera/color_fps: 30
/camera/realsense2_camera/color_height: 480
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: 640
/camera/realsense2_camera/depth_fps: 30
/camera/realsense2_camera/depth_height: 480
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: 640
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye: True
/camera/realsense2_camera/enable_imu: True
/camera/realsense2_camera/enable_infra1: True
/camera/realsense2_camera/enable_infra2: True
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/fisheye_fps: 30
/camera/realsense2_camera/fisheye_height: 480
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: 640
/camera/realsense2_camera/gyro_fps: 1000
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/infra1_fps: 30
/camera/realsense2_camera/infra1_height: 480
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra1_width: 640
/camera/realsense2_camera/infra2_fps: 30
/camera/realsense2_camera/infra2_height: 480
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra2_width: 640
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/serial_no:
/rosdistro: indigo
/rosversion: 1.11.21

NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[camera/realsense2_camera_manager-1]: started with pid [16808]
process[camera/realsense2_camera-2]: started with pid [16809]
[ INFO] [1551988395.758642023]: Initializing nodelet with 4 worker threads.
[ INFO] [1551988395.795874419]: RealSense ROS v2.0.3
[ INFO] [1551988395.795911935]: Running with LibRealSense v2.10.2
[ INFO] [1551988395.971667137]: getParameters...
[ INFO] [1551988396.002472106]: setupDevice...
[ INFO] [1551988396.002507340]: JSON file is not provided
[ INFO] [1551988396.002535316]: ROS Node Namespace: camera
[ INFO] [1551988396.002557651]: Device Name: Intel RealSense SR300
[ INFO] [1551988396.002573471]: Device Serial No:<PHONE_NUMBER>98
[ INFO] [1551988396.002587263]: Device FW version: <IP_ADDRESS>
[ INFO] [1551988396.002599760]: Device Product ID: 0x0AA5
[ INFO] [1551988396.002610195]: Enable PointCloud: Off
[ INFO] [1551988396.002622229]: Align Depth: Off
[ INFO] [1551988396.002640664]: Sync Mode: Off
[ INFO] [1551988396.002677609]: Device Sensors:
[ INFO] [1551988396.002709250]: Coded-Light Depth Sensor was found.
[ INFO] [1551988396.002724746]: RGB Camera was found.
[ INFO] [1551988396.002760196]: (Infrared, 2) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002773979]: (Fisheye, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002802157]: (Gyro, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002816048]: (Accel, 0) sensor isn't supported by
current device! -- Skipping...
[ INFO] [1551988396.002836535]: setupPublishers...
[ INFO] [1551988396.006296502]: Expected frequency for depth = 30.00000
[ INFO] [1551988396.126424813]: Expected frequency for infra1 = 30.00000
[ INFO] [1551988396.147114510]: Expected frequency for color = 30.00000
[ INFO] [1551988396.169324198]: setupStreams...
07/03 14:53:16,169 WARNING [140206503659456] (sensor.cpp:313)
Unregistered Media formats : [ INZC PAIR YUYV ]; Supported: [ ]
[ INFO] [1551988396.169831753]: depth stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551988396.169954137]: infra1 stream is enabled - width: 640,
height: 480, fps: 30
[ INFO] [1551988396.170957074]: color stream is enabled - width: 640,
height: 480, fps: 30
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,177 WARNING [140205670668032] (backend-v4l2.cpp:808) Empty
frame has arrived.
[ INFO] [1551988396.178935074]: publishStaticTransforms...
[ INFO] [1551988396.179070655]: RealSense Node Is Up!
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
07/03 14:53:16,182 WARNING [140205659801344] (backend-v4l2.cpp:808) Empty
frame has arrived.
Raw image, depth image and infra image are received. But poincloud data is
not received.
On Thu, Mar 7, 2019 at 4:35 AM RealSense Customer Support <
<EMAIL_ADDRESS>wrote:

Hi @pl95 https://github.com/pl95,

From "top" log, it looks the overall cpu consumption/loading is
quite heavy when you run "demo_pointcloud". Please run also "lscpu" to show
the info.
Try below command to see how it works.
$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud
Indeed, above DCM exe command is used for Windows to upgrade your
SR300 firmware.
So far, I don't have Ubuntu 14.04 + Indigo environment. Will try
to setup to see how it goes.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/2935#issuecomment-470453129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aif038BgzQ0sMAL_CUVbkB_vnMO_LBYlks5vUN1CgaJpZM4ZbGcU
.

Hi @pl95
Is demo_pointcloud.launch can't fit your usage? Instead of rs_rgbd.launch, you can also try below to have depth/ir/color images and visualize pointcloud via rviz.
$ roslaunch realsense2_camera rs_camera.launch enable_pointcloud:=true

HI @RealSenseCustomerSupport ,
I change the launch file rs_rgbd.launch as following, which match the demo_pointcloud.launch.

  ****

  ****

  ****

  ****

  ****

<!-- Launch the camera device nodelet-->
<include file="$(find realsense2_camera)/launch/includes/nodelet.launch.xml">
  <arg name="manager"                  value="$(arg manager)"/>
  <arg name="serial_no"                value="$(arg serial_no)"/>
  <arg name="json_file_path"           value="$(arg json_file_path)"/>

  <arg name="enable_pointcloud"        value="$(arg enable_pointcloud)"/>
  <arg name="enable_sync"              value="$(arg enable_sync)"/>
  <arg name="align_depth"              value="$(arg align_depth)"/>

  <arg name="fisheye_width"            value="$(arg fisheye_width)"/>
  <arg name="fisheye_height"           value="$(arg fisheye_height)"/>
  <arg name="enable_fisheye"           value="$(arg enable_fisheye)"/>

  <arg name="depth_width"              value="$(arg depth_width)"/>
  <arg name="depth_height"             value="$(arg depth_height)"/>
  <arg name="enable_depth"             value="$(arg enable_depth)"/>

  <arg name="color_width"              value="$(arg color_width)"/>
  <arg name="color_height"             value="$(arg color_height)"/>
  <arg name="enable_color"             value="$(arg enable_color)"/>

  <arg name="infra1_width"             value="$(arg infra1_width)"/>
  <arg name="infra1_height"            value="$(arg infra1_height)"/>
  <arg name="enable_infra1"            value="$(arg enable_infra1)"/>

  <arg name="infra2_width"             value="$(arg infra2_width)"/>
  <arg name="infra2_height"            value="$(arg infra2_height)"/>
  <arg name="enable_infra2"            value="$(arg enable_infra2)"/>

  <arg name="fisheye_fps"              value="$(arg fisheye_fps)"/>
  <arg name="depth_fps"                value="$(arg depth_fps)"/>
  <arg name="infra1_fps"               value="$(arg infra1_fps)"/>
  <arg name="infra2_fps"               value="$(arg infra2_fps)"/>
  <arg name="color_fps"                value="$(arg color_fps)"/>
  <arg name="gyro_fps"                 value="$(arg gyro_fps)"/>
  <arg name="accel_fps"                value="$(arg accel_fps)"/>
  <arg name="enable_imu"               value="$(arg enable_imu)"/>
</include>

<!-- RGB processing -->
<include if="$(arg rgb_processing)"
         file="$(find rgbd_launch)/launch/includes/rgb.launch.xml">
  <arg name="manager"                       value="$(arg manager)" />
  <arg name="respawn"                       value="$(arg respawn)" />
  <arg name="rgb"                           value="$(arg rgb)" />
  <arg name="debayer_processing"            value="$(arg debayer_processing)" />
</include>

  <node pkg="nodelet" type="nodelet" name="register_depth"
        args="load depth_image_proc/register $(arg manager) $(arg bond)" respawn="$(arg respawn)">
    <remap from="rgb/camera_info"             to="$(arg rgb)/camera_info" />
    <remap from="depth/camera_info"           to="$(arg depth)/camera_info" />
    <remap from="depth/image_rect"            to="$(arg depth)/image_rect_raw" />
    <remap from="depth_registered/image_rect" to="$(arg depth_registered)/sw_registered/image_rect_raw" />
  </node>

  <!-- Publish registered XYZRGB point cloud with software registered input -->
  <node pkg="nodelet" type="nodelet" name="points_xyzrgb_sw_registered"
        args="load depth_image_proc/point_cloud_xyzrgb $(arg manager) $(arg bond)" respawn="$(arg respawn)">
    <remap from="rgb/image_rect_color"        to="$(arg rgb)/image_rect_color" />
    <remap from="rgb/camera_info"             to="$(arg rgb)/camera_info" />
    <remap from="depth_registered/image_rect" to="$(arg depth_registered_filtered)/sw_registered/image_rect_raw" />
    <remap from="depth_registered/points"     to="$(arg depth_registered)/points" />
  </node>

  <!-- Publish registered XYZRGB point cloud with hardware registered input (ROS Realsense depth alignment) -->
  <node pkg="nodelet" type="nodelet" name="points_xyzrgb_hw_registered"
        args="load depth_image_proc/point_cloud_xyzrgb $(arg manager) $(arg bond)" respawn="$(arg respawn)">
    <remap from="rgb/image_rect_color"        to="$(arg rgb)/image_rect_color" />
    <remap from="rgb/camera_info"             to="$(arg rgb)/camera_info" />
    <remap from="depth_registered/image_rect" to="$(arg depth_registered)/image_raw" />
    <remap from="depth_registered/points"     to="$(arg depth_registered_pub)/points" />
  </node>

Now, I have the image on with the robot model. I don't know whether the problem should be solved in this way. But I think it is something I can try.


back-end application review process

For new applications that come in, we will set up a back-end process for city employees to track and update the status of each one.
Here's the planning document we're going off of based on our conversations with Jeanne: https://docs.google.com/document/d/16bSXDQId62rq7kq3Qdam4U1Axfhk1J90Pnbxm6Cr-ng/edit
Overall goals & constraints:

each individual property applied for will be tracked. some applicants will apply for 2 lots, in which case it will create 2 properties to review.
we will have a list of numerical stages, as well as a list of public statuses that a given property will be assigned, outlined here: https://docs.google.com/spreadsheets/d/1sS9ZfStfY5btsBa_2MVxCQsoM7ad9yM_TT4DFuvd0ys/edit
some statuses, especially in the beginning steps, will require us creating a page with tasks that must be completed before progressing to the next step
other steps later in the process will be done offline, so we will allow them to be set, probably in bulk
we will create a listing page that will allow admins to view all properties grouped by their status and give total counts of how many properties are in each stage
some steps will trigger automatic emails that are sent to the applicant notifying them of the status change
as each property moves through the process and given a public status the public map (example) will be updated

This is implemented.


Add Liga MX icons for Atom

What a fun project! I've created a set of icons with the colors of the Liga MX (Mexican Futbol League) teams. Thank you for allowing me to contribute!

Thanks for contributing. Sorry for the delay in merging.


Pass 'timeout' & 'retries' params & add new 'retry_timeout' param

Pass existing type params in puppet define aem::crx::package
Add new param retry_timeout to make the retrying of fetching package info more useful

:-(
Codeclimate & Travis/Rubocop should agree...
Rubocop:
lib/puppet/provider/aem_installer/default.rb:24:26: C: Style/PercentLiteralDelimiters: %i-literals should be delimited by [ and ]. (https://github.com/bbatsov/ruby-style-guide#percent-literal-braces)
@quickstart_fields = %i(home version)
Codeclimate requires () ....

I'll take a look to see if I can fix the rule set. I had the same problem, it actually has to do with the version of Ruby actually.

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/aem_installer: /etc/puppetlabs/code/environments/production/modules/upstream/aem/lib/puppet/type/aem_installer.rb:69: unknown type of %string
%i[user group].each do |type|
puppet --version
4.10.6

Yep, that'd be the error i ran into. I believe that the internal embedded ruby that Puppet uses doesn't support that syntax. I'm not up on the details of Ruby; but it's possible it wasn't added until Ruby 2.2. Though the rubocop.yml configuration should be using rules based on what was available only in Ruby2.0. So i have no idea what's going on there.

/me should not push code in a hurry before the weekend without running tests... :-(


Python scripts to upload data to s3 from a remote data source

Simplifies moving data from the various data sources to your s3 data buckets.
download_s3_data.py : From a different s3 bucket to yours.
url_to_bucket.py: To convert url to s3:// format. Run on file with urls to data sources before running download_s3_data.py
curl_to_s3.py: takes any file with a list of CURL-able sources and uploads data to your s3 bucket from there. Can also handle compressed files automatically.

@saurabh279 thanks, but given that I'm not a Python expert and that you admit these are somewhat hacky, I'd prefer not to merge into the main repo
If you want to host in your own GitHub, I'd be happy to make a page in this repo's wiki for "other resources" and link to your code there. Thoughts?


DEX Integration

User Story:
As a CDC project that is sending data to the CDC, I need to be able to send data through the CDC's front door, DEX (Data Exchange).
Description/Use Case
Presently, we are sending OTC COVID data directly to the Palantir system sitting inside the CDC via azure blob store, HHSProtect. This data is in CSV format and comes from BD Veritor. Instead, we need to interface with DEX and DEX can route to HHSProtect. To do this, we will use the Universal Pipeline and thus will send HL7v2 that closely aligns with the RadxMars OTC ELR IG.
The original plan was to onboard BDVeritor to UP and have them send us FHIR and we translate it to HL7v2 for DEX/HHSProtect. Since then, BDVeritor has pulled out of onboarding as just a covid sender to the covid pipeline and we need to either confirm they want to onboard as a FHIR sender or find another sender to send us FHIR/HL7 OTC Covid data.
We haven't worked through the policy approvals to send the CDC something other than OTC covid data, so if we find another sender, we can only accept OTC data from them OR we need to hash out the policy approvals.
We are also sending MPox data to another system in the CDC, but we will focus on COVID first.
Dev Notes:
Acceptance Criteria

[ ]  RS is able to send HL7v2 or FHIR data to the CDC through DEX

Closing due to DEX shutting down


[DISCUSSION] Trimming specs

ok to delete routing specs folder?
ok to delete views specs folder?

Out of date.


Set pipeline state as terraform variables

Description
Set the pipeline state in terraform vars to make it easer to override the configuration without changing git tracked files.
How has this been tested?
Please explain how you have tested the new changes.
By changing the values and looking at the end results.
Tested the validation with following result if not in PAUSED or ACTIVE:

Checklist

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have successfully run the E2E tests, and have included the links to the pipeline runs below
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] I have updated any relevant documentation to reflect my changes
[ ] I have assigned a reviewer and messaged them

Pipeline run links:

If this code change is OK with maintainers I will add code for all the other pipelines as well.

@martenlindblad legit, pls proceed!


Amazon image links corrupted after normalization

In version 5.3.0 such URL:
https://images-na.ssl-images-amazon.com/images/I/41kaOFDXzSL._SR600%2c315_PIWhiteStrip%2cBottomLeft%2c0%2c35_PIStarRatingFOURANDHALF%2cBottomLeft%2c360%2c-6_SR600%2c315_ZA81%252C561%2c445%2c290%2c400%2c400%2cAmazonEmberBold%2c12%2c4%2c0%2c0%2c5_SCLZZZZZZZ_FMpng_BG255%2c255%2c255.jpg
become:
https://images-na.ssl-images-amazon.com/images/I/41kaOFDXzSL._SR600%2c315_PIWhiteStrip%2cBottomLeft%2c0%2c35_PIStarRatingFOURANDHALF%2cBottomLeft%2c360%2c-6_SR600%2c315_ZA81%2C561%2c445%2c290%2c400%2c400%2cAmazonEmberBold%2c12%2c4%2c0%2c0%2c5_SCLZZZZZZZ_FMpng_BG255%2c255%2c255.jpg
The first one working great, but second is not. I'm using normalize-url without any options.
For some reason two characters from original URL are stripped of in normalized version:

@exentrich @sindresorhus I've investigated this issue and it's not a bug in normalize-url but an issue in the provided url.
Part of the normalization process in normalize-url is to use decodeURI. This will decode %25 as % since % is encoded as %25. It's also mentioned here https://datatracker.ietf.org/doc/html/rfc1738 as being unsafe.
You can test the example in this example https://stackblitz.com/edit/repro-normalize-url-iss125?file=index.js


Implement skeleton support

This PR implements skeleton support for our plugin. This allows us to present fully articulated hands to the user where OpenVR will provide the information for correct finger placement depending on sensors on the controllers.

There are a few things to round off but this is basically all working :)

I'll write up some more documentation on the WIKI but the asset now comes with the two required entries in the actions.json file and two premade scenes that implement the standard gloves that Valve supplies. You can use those scenes as they are or you can build your own.
Here is the right hand scene:

So it's inherited from the slim GLTF file that Valve supplies, this is the one without the textures but I have extracted the textures and applied them.
So our root node is a spatial node but I have applied our OpenVRPose.gdns script to it so it can be set to our skeleton action /actions/godot/in/right_hand. It is IMPORTANT hand remains any, don't set this to right hand even though we are dealing with the right hand. Its a special type of pose.
The Rootnode is just a spatial the GLTF import adds, next is our skeleton node with the skeleton implemented that is properly setup for OpenVR. Here I have applied our new OpenVRSkeleton.gdns' script.  This new node has 3 properties: ![image](https://user-images.githubusercontent.com/1945449/78019946-3fc21d80-739c-11ea-8206-b71297bbd2a2.png) Action is set to the same  /actions/godot/in/right_handaction.  Keep bones is set to true, if you set this to false or if no bones are added the plugin will load up the bones it gets from the plugin. If set to true it will use the bones we already have. Motion range allows us to switch between the two motion ranges OpenVR supports.With controllerallows you to grip the hand around the controller, you should set this if the controller is visible. If set toWithout controller` you can make a full closed fist.
Finally you'll see 5 Bone attachments named after each finger. These are nodes that follow the position of each finger tips.
When using this scene you can enable editable children and add additional objects to this or add things like a physics area to detect what the fingers are touching.

I have been working on a hand-system support the last days in here https://github.com/boku-ilen/godot-vr-toolkit, where i set different animations made in blender on the inputs for touch and pressed properties of the oculus. Did this pretty much exactly at the time you were implementing the skeleton support ...

Pretty sad timing now 😂

I have been working on a hand-system support the last days in here https://github.com/boku-ilen/godot-vr-toolkit, where i set different animations made in blender on the inputs for touch and pressed properties of the oculus. Finished this pretty much exactly at the time you were finishing the skeleton support ...
Pretty sad timing now 😂
Why sad timing? The great thing about supporting the skeleton API for OpenVR is that OpenVR does a lot of cool stuff for us, but the big downside of it is that it's specific for OpenVR.

Having a generic implementation that just reacts to controller inputs and can therefor be used for any VR platform is still something many will be interested in.
I was thinking of renaming my https://github.com/godotvr/godot-vr-common toolkit library to godot-vr-toolkit, have to think of a new name now :)

I actually am very unaware of how useful my whole repository is, especially since it is all writen in GDScript as opposed to your GDNative c++ code. But if you think that some of my things could be of use I would actually feel honored if I could collaborate. One thing i really missed on the  VR-common repository was input on UI on a mesh, so I made something that does work quite reliable. Feel free to contact me if I can collaborate somehow :)

I actually am very unaware of how useful my whole repository is, especially since it is all writen in GDScript as opposed to your GDNative c++ code. But if you think that some of my things could be of use I would actually feel honored if I could collaborate. One thing i really missed on the VR-common repository was input on UI on a mesh, so I made something that does work quite reliable. Feel free to contact me if I can collaborate somehow :)

The more contributors to vr-common the happier I'll be, there is only so much I can do with my attention already spread thin over all these projects. So please feel free to open issues on the repo to discuss ideas you want to add and submit some PRs with additions you think make sense.
Do please always ping me on discord or twitter when you do so, I get a flood of emails from github each day as a core contributor to Godot itself and miss a lot that are directed to my own repos.

For the next person looking for more OpenVRSkeleton documentation: https://gitlab.com/resourcify/resourcify-enterprise/-/merge_requests/294
Thanks @BastiaanOlij !

@arran-nz you're welcome :)
Your link only works if you have an account but documentation can also be found here: https://github.com/GodotVR/godot-openvr-asset/wiki/OpenVR-actions


[ExternalForcesAwareQP] Give the possibility to make the QP aware of external forces

This PR allows the QP to be aware of the external forces and compensate for them to ensure all constraints and objectives. Compliance of a task, if necessary, is achieved by uncompensating the external forces by adding to the task's reference acceleration the accelerations produced by these external forces.
Detailed description of the additions

[mc_rbdyn] Provide two new "sensors" implemented as devices: ExternalTorqueSensor & VirtualTorqueSensor
[mc_tvm] Add information of ExternalTorqueSensor both as joint torque and acceleration in Robot with two new methods tauExternal() and alphaDExternal(). Add the update of external torque and acceleration as both output and update of TVM in Robot to prevent recomputation for multiple tasks with the updateEF() method.
[mc_tvm] Modifies the DynamicFunction to include the compensation of external forces in b_ and a boolean in the constructor to activate or not this feature.
[mc_solver] Modifies DynamicsConstraint, initialize, and initialize_tvm constructors to include a boolean that allows activation of the compensation feature by forwarding it to the DynamicFunction.
[mc_tasks] Add two new compliant tasks CompliantPostureTask and CompliantEndEffectorTask to be used with this QP as it will naturally compensate external forces. Each task is a derivation of their non-compliant versions and adds getter and setter as well as datastore entries to control if a task should be compliant or not. Compliance for the tasks is achieved by adding the acceleration due to the external forces to the reference acceleration of the task.

Need some fixes for now, will update.

@mathieu-celerier  Thank you for the Pull Request for the new feature. I have a few questions.

If you use Tasks instead of TVM as the solver (which I understand is the default), does nothing change in the behavior of the controller (including the amount of computation)?
Even when using TVM, the behavior doesn't change unless you explicitly specify the option and add the compliance version of Posture/EndEffectorTask, right?
I see that the compensateExternalForces option of DynamicsConstraint is not supported in Tasks. Shouldn't a warning message be output when this is specified if the solver backend is Tasks?


drivers: counter: Add native_posix counter hardware model and driver

Adds native_posix hw counter model and the counter driver.
Functionality is needed by software which is tested
on native_posix and has dependency on counter.
Hardware model was developed similarly to HW timer model.
The counter driver wraps HW counter functions and exposes
basic functionalities: starting, stopping, setting and cancelling
single channel alarms.
Code was tested against: tests/drivers/counter/counter_basic_api.
Signed-off-by: Filip Zajdel<EMAIL_ADDRESS>

@aescolar Thank you for the review. I fixed all the mentioned issues. Does it seem correct now?

@nordic-krch Note that as maintainer for the counter your approval is also required before this could be merged.


System.IdentityModel.Tokens.Jwt Breaking Changes?

I posted this on Thinktecture's site as I am working with IdentityServer but wanted to post in here in case this is a known, breaking change that has a quick fix. I reviewed the code and it looks like what I am seeing is not expected but I can confirm it in a new solution with NuGet fully updated.
Has anyone updated to v<IP_ADDRESS>250711 of System.IdentityModel.Tokens.Jwt yet?
All of the extension points I was using off of the OpenIdConnectAuthenticationNotifications (AcrValues, RequestType, IdTokenHint all broke when moving from 4.0.1 and I cannot find any documentation on the changes from Microsoft.
Example:
if (n.ProtocolMessage.RequestType == OpenIdConnectRequestType.LogoutRequest)
                        {
                            var idTokenHint = n.OwinContext.Authentication.User.FindFirst("id_token");
                            var postLogoutRedirectUri = CloudConfigurationManager.GetSetting("IdpRedirectUri");
                            if (idTokenHint != null)
                            {
                                n.ProtocolMessage.IdTokenHint = idTokenHint.Value;
                            }
                        }
```

This is an interesting one. It appears to be intellisense related. After I fixed a code defect I realized the projects were building even though VS is reporting that no symbols can be found. I reproduced it on a total of 3 workstations and neither cleaning the solution nor purging the intellisense settings allows the symbols to resolve properly after updating the nuget package.

When you say broke, do you mean they don't get called?

@jlegan is this still of interest to you?

closing assuming the issue is resolved.


Implement String.Chars for Crawly.Request

To enable the requests to be written to file/log (for example in the WriteToFile pipeline) the String.Chars protocol is implemented as a trivial Kernel.inspect dump.

Hi thanks for the contribution, could you add in a test for this so that I can verify on my side the error that you mentioned in the closed PR?

Sorry for the late response, sure I will add a testcase for it :)


Expose refresh=True out to ls, glob

This is currently on _ls but not available through ls or glob.

Fixed in #34?


Matter Linux Bridge example - Thread commissioning

Hello everyone,
I am trying to get the Matter Linux Bridge example to run with a Thread radio.
GitHub hash of the SDK that was being used:
commit from last week: 9bde93872fbd16174fdf07c893f56992fdc00352
RCP Version:
OPENTHREAD/thread-reference-20200818-2475-g7c5dca178; NRF52840; May 17 2023 17:04:40
Platform:
Raspberry Pi 4 with Ubuntu 22.04
I can build the example using:
./scripts/examples/gn_build_example.sh examples/bridge-app/linux out/debug/bridge-app chip_enable_openthread=true
I modified the chip-cirque-device-base Dockerfile to use Ubuntu 22.04 as a base image and included bluez and bluetooth in the apt install command.
The chip-cirque-device-base image is used as a base for the Matter Linux Bridge Dockerfile.
For the Matter Linux Bridge image I modified the entrypoint.sh:
#!/bin/bash

service dbus start
sleep 1
service avahi-daemon start
sleep 1
bluetoothd &
sleep 1

echo -e 'OTBR_AGENT_OPTS="-I wpan0 -B eth0 spinel+hdlc+uart:///dev/ttyUSB0 trel://eth0"\nOTBR_NO_AUTO_ATTACH=0' > /etc/default/otbr-agent
service otbr-agent start

sleep 1
ot-ctl panid 0x1234
ot-ctl ifconfig up
ot-ctl thread start

chip-bridge-app --thread

I can start the container with the command:
docker run -v /dev/ttyACM0:/dev/ttyUSB0 -v /dev/ttyAMA0:/dev/ttyAMA0 --privileged --net=host matterbridge:latest
From inside the container I confirmed Bluetooth is working using bluetoothctl. The otbr-agent service is running and with ot-ctl I can scan for networks.
However after I successfully commission the device, the openthread radio is not configured. The openthread state is even disabled. Commissioning logs: MatterBridge.txt
How do I make sure the OpenThread Radio gets configured during commissioning?

I've added some variables to args.gni
chip_enable_openthread = true
chip_openthread_ftd = true
chip_config_network_layer_ble=true
chip_enable_openthread=true
chip_device_config_thread_ftd=true
chip_device_uses_otbr_posix_dbus=true
chip_enable_ble=true
chip_openthread_border_router=true

Only when I added the last one chip_openthread_border_router the OpenThread radio was commissioned onto the thread network.
Is it possible to commission the thread radio without being a border router?


Alt/Option + Scroll Wheel for Zoom shortcut

Your idea:
Affinity programs (Designer, Photo, Publisher) and Adobe programs (InDesign, Photoshop, etc) use Alt/Option + Scroll Wheel with the cursor in the window to zoom the window.  I'd like to add that functionality into HB, when the cursor is in the iFrame.
As I've been doing a lot of work in Publisher to create a new Theme for HB, I keep switching to HB and trying the shortcut for zooming and getting frustrated it doesn't work.  Now we have the zoom functionality in, it should be easy to add such a shortcut.
It should be limited to the iframe (doing the shortcut on the Editor shouldn't change anything).

We could add to this using right and left arrow to navigate pages, as most if not all pdf viewers do.

I wouldn't want to do any keyboard navigation in the same PR that covers my request above.  I believe it keyboard navigation is more complicated in design.
With my proposed feature, we can listen for mousescroll events inside the iFrame or Preview pane which is just based on the mouse position.
With keyboard interactions, we would need to be sure that the Preview Pane/iFrame has focus set on it, which I don't believe we really have right now.  Without focus, we don't know if pressing left or right arrows should move the cursor in the Editor or not (or any other place).  Maybe I'm wrong about the difficulty, but my brain just has some flashing lights saying "context sensitive hotkeys are hard when you have no way of focusing the context".


add some sort of was_deleted() boolean to the Message object to check of the message still Exists

Summary
allow for msg.was_deleted() or msg.deleted() or msg .deleted
What is the feature request for?
The core library
The Problem
my bot requires knowing if a message it sent is deleted.
The Ideal Solution
return true if the message still Exists
The Current Solution
is_deleted = False
try:
_delcheck = await interaction.channel.fetch_message(msg.id)
        except Exception as e:
            is_deleted = True

Additional Context
The "Current Solution" is barely tested and is very jank so this would be very helpful

Sounds like a good idea, I can think of scenarios I'd like that instead of try except'ing it.

If you are caching messages (which is the default given the intent), the message should get removed automatically from cache when the message_delete event is received.
If the message was created while the bot was caching messages, it should work to simply check if ctx._state._get_message(msg_id)  (similarly can be done on an Interaction, Message, etc. that has _state instead of ctx). This does use undocumented attributes though, but does not require an API call.
If the message was created before the bot was started, or otherwise the bot did not have access when it was created, then it would need to fetch the message to check.
In my opinion, this seems like a very specific use case, and as this is not something the Discord API has an endpoint for, so I think it would make more sense for individual bot developers to add this to their bot on their own, for example, you can have some util functions and include something like:
async def message_deleted(message: nextcord.Message) -> bool:
    if message._state._get_message(message.id) is not None:
        return False
    try:
        await message.channel.fetch_message(message.id)
        return False
    except nextcord.NotFound:
        return True

This can be implemented however you choose, it could even take a channel and message id rather than a Message object to make it even more flexible.

Why is this still open? Denver's comment seemed to resolve this issue

Seems I forgot to close this, sorry


az webapp up fails when providing --name without --plan parameter

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp up
Errors:
The command failed with an unexpected error. Here is the traceback:
list index out of range
Traceback (most recent call last):
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 658, in execute
    raise ex
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 713, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/commands.py", line 38, in _ex_handler
    raise ex
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 692, in _run_job
    result = cmd_copy(params)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/custom.py", line 3953, in webapp_up
    plan = get_plan_to_use(cmd=cmd,
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/_create_util.py", line 385, in get_plan_to_use
    return _determine_if_default_plan_to_use(cmd, _default_asp, resource_group_name, loc, sku, create_rg)
  File "/opt/homebrew/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/_create_util.py", line 404, in _determine_if_default_plan_to_use
    _asp_generic = plan_name[:-len(plan_name.split("_")[4])]
IndexError: list index out of range

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp up -n {} -g {} -l {} --dryrun --debug

Expected Behavior
Environment Summary
macOS-12.0.1-arm64-arm-64bit, Darwin 21.1.0
Python 3.10.1
Installer: HOMEBREW

azure-cli 2.31.0

Extensions:
connectedk8s 1.2.0
k8s-extension 1.0.0
customlocation 0.1.3
containerapp 0.2.0
azure-dev 0.0.1b38

Additional Context

Routing to service team.

can confirm, during my az-204 preperation i stumbled over this too:
az webapp up --location westeurope --html
The webapp 'blue-stone-7508e346c2794eb6814821afc9d9df79' doesn't exist
The command failed with an unexpected error. Here is the traceback:
list index out of range
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 658, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 713, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/commands.py", line 38, in _ex_handler
    raise ex
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 692, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/custom.py", line 3953, in webapp_up
    plan = get_plan_to_use(cmd=cmd,
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/_create_util.py", line 385, in get_plan_to_use
    return _determine_if_default_plan_to_use(cmd, _default_asp, resource_group_name, loc, sku, create_rg)
  File "/usr/local/Cellar/azure-cli/2.31.0/libexec/lib/python3.10/site-packages/azure/cli/command_modules/appservice/_create_util.py", line 404, in _determine_if_default_plan_to_use
    _asp_generic = plan_name[:-len(plan_name.split("_")[4])]
IndexError: list index out of range


Switch to loose mode

Hi!
Some components (e.g. #4212) doesn't work in IE9.
Switching on loose mode solves this problem.

Digging into this just a little bit and it appears that loose mode is normally not recommended.
This article delves into the implication of this plugin:
http://www.2ality.com/2015/12/babel6-loose-mode.html

@frooeyzanny Any idea why the loose mode is fixing the issues?

Con: You risk getting problems later on, when you switch from transpiled ES6 to native ES6. That is rarely a risk worth taking.

I agree with @matthewoates I would rather avoid using the loose mode unless we really know what we are doing.

@oliviertassinari Let's not use loose mode just for old IE compatibility -- there must be a more direct fix.

Ok, I've got it.
Thanks for feedback!

@frooeyzanny Feel free to submit a fix if you can find a more direct route! Otherwise post an issue and we'll try to get to it 👍


Unable to install go-oci8 on windows 64 bits again

Hello,
i m trying to install the package go-oci8 and always get the following message: become crazy.
thx for your help.
ericg
c:\go\work>go get github.com/mattn/go-oci8
pkg-config --cflags oci8
pkg-config: exit status<PHONE_NUMBER>
--- oci8.pc
prefix=/devel/target/XXXXXXXXXXXXXXXXXXXXXXXXXX
exec_prefix=${prefix}
libdir=C:/instantclient_12_1/sdk/lib/msvc
includedir=C:/instantclient_12_1/sdk/include
glib_genmarshal=glib-genmarshal
gobject_query=gobject-query
glib_mkenums=glib-mkenums
Name: oci8
Description: oci8 library
Libs: -L${libdir} -loci
Cflags: -I${includedir}
Version: 12.1
my configuration:
windows 10, Oracle client 64 b, GO 64
in PATH i have : C:\GO\BIN;C:\go\pkg-config-0.26\bin;C:\go\pkg-config-0.26\PKG_CONFIG_PATH;C:\go\TDM-GCC-64\bin
PKG_CONFIG_PATH=C:\go\pkg-config-0.26\PKG_CONFIG_PATH

May be this help
Click -> How to install pkg config in windows?

This solution worked for me.
https://gist.github.com/mnadel/8678269
Note. gcc that comes with minwg64 worked perfectly for me. Download Minwg64 and gcc will come with it. Make sure you have gcc in path.

Here is what I did:
Install and setup Go
Downloaded and install mingw64
https://mingw-w64.org/doku.php/download
I installed to: C:\app\mingw64
Then added the path C:\app\mingw64\ to the Path environment variable
Then downloaded and installed Oracle instant client
https://www.oracle.com/technetwork/database/database-technologies/instant-client/downloads/index.html
I installed to: C:\app\instantclient_11_2_64
Then added the path C:\app\instantclient_11_2_64\ to the Path environment variable
Then create user in database:
CREATE USER scott IDENTIFIED BY tiger DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp;
GRANT connect, resource, create view, create synonym TO scott;
GRANT execute ON SYS.DBMS_LOCK TO scott;
create or replace function SCOTT.SLEEP_SECONDS (p_seconds number) return integer is
begin
  dbms_lock.sleep(p_seconds);
  return 1;
end SLEEP_SECONDS;
/

Then test:
set CGO_CFLAGS=-IC:\app\instantclient_11_2_64\sdk\include\ -static
set CGO_LDFLAGS=-LC:\app\instantclient_11_2_64\sdk\lib\msvc\ -lstdc++ -loci -static
go test -v github.com/mattn/go-oci8 -tags noPkgConfig -args -disableDatabase=false -hostValid replace_with_your_db_host -username scott -password tiger

@mattn Close this?


Detect log alert tx one 7199 v5

Ticket
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/7199
https://github.com/OISF/suricata-verify/pull/2141 next version, hopefully green for 7

Next in https://github.com/OISF/suricata-verify/pull/2157


add new properties to imageInfo node

Description
Add image package's diff when there are an update available to a group. Add image info as distribution, version, date .
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] I run go fmt ./... to check that my code is properly formatted
[X] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #940 (fbb469f) into main (5deb89a) will decrease coverage by 0.06%.
The diff coverage is 9.52%.

:exclamation: Current head fbb469f differs from pull request most recent head 9114cb5. Consider uploading reports for the commit 9114cb5 to get more accurate results

@@            Coverage Diff             @@
##             main     #940      +/-   ##
==========================================
- Coverage   30.76%   30.70%   -0.07%
==========================================
  Files          45       45
  Lines        5343     5355      +12
==========================================
  Hits         1644     1644
- Misses       3469     3481      +12
  Partials      230      230

Impacted Files
Coverage Δ

pkg/models/devicegroups.go
100.00% <ø> (ø)

pkg/services/devicegroups.go
31.48% <9.52%> (-1.70%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5deb89a...9114cb5. Read the comment docs.


[validator] Quick fix to allow shared object cert exec block wait

One request: Only enter the retry loop if it is a shared object tx.

Is there even a possible case where this loop would be entered when it is an owned object tx?

One request: Only enter the retry loop if it is a shared object tx.

Is there even a possible case where this loop would be entered when it is an owned object tx?

normally not possible but when it happens it indicates a bug that should scream

Can we also add retry_cnt in the debug log?

Added retry_cnt to debug log, and print error if it's owned object tx


Fix typos in README

@irealva tagging you here, hope you don't mind!

Thank you for submitting this correction.


TFSlim: evaluate multiple validation batches using evaluation_loop

I'm trying to use placeholders for training with TF-Slim, as my training + evaluation data comes from outside of TF World. I've now got training working by using the workaround described in #6604 and keeping track of the last training batch to supply in the feed dict when calling sess.run(summary_op).
However, evaluation using evaluation_loop over multiple batches seems to not be possible. There are summary_op_feed_dict and eval_op_feed_dict arguments to the evaluation_loop function, but if I understand correctly, if I set num_evals > 1, then the same feed dict (+ data) will be used for every evaluation.
I'm happy add this functionality and issue a PR – is it true that right now the ability to evaluate over multiple validation batches using placeholders is not implemented? I'm using TF 12.1.

I would recommend you to use evaluate_once.
Take a look at evaluate_repeatedly to see how to use evaluate_once

Thanks for the help @sguada! However, I'm still not sure whether that solves the underlying issue of the feed_dict being a constant parameter to evaluate_once as far as I can see. In the function, there are the following lines:
while not session.should_stop():
        session.run(eval_ops, feed_dict)

And so until the should_stop flag is set, the same feed_dict will be used for every evaluation?
In the docstring of evaluate_repeatedly there is a comment that reads:

evaluate_once creates a local variable used to track the number of evaluations run via tf.contrib.training.get_or_create_eval_step

Perhaps this could be used in some way? Again, happy to contribute if it turns out there is something is missing, though perhaps I'm misunderstanding?
Thanks so much for your time!

If you want to change feed_dict in every run, you can use a hook. Example is as follows:
class MyFeedHook(session_run_hook.SessionRunHook):
  def before_run(self, run_context):
    return session_run_hook.SessionRunArgs(
        fetches=None, feed_dict=my-feed-dict-for-this-step)

@kencoken, given the inactivity here It sounds like that solved your problem.


Add some performance improvements

Summary
Trying to figure out the issue where the app gets hanged when opening the post options, I found that some database batches were taking more than expected. The most troublesome was the periodic status fetch, that was getting the status of all the users in the channel, and no matter the new status, updating and re-rendering all users in the channel (avatars, status, etc...). I also made some similar improvements for when we get the posts for a channel. If we already have all the posts, now we almost don't update any field in the database, improving the batching time.
Ticket Link
None
Release Note
Some performance improvements.

Tests failing though

@yasserfaraazkhan Regarding testing, this touches how we store posts, threads and users in the database. So the idea is a bit of smoke testing on stuff like updating posts, putting the posts as pinned, changing the user status, etc... and that kind of stuff.
No functionality should have changed, but hopefully the performance is better :P

Tested below scenarios and observed the functionality is working as expected.
post message, edit, restore, pin posts, save posts, upload attachments , leaving channel, adding members , Drafts messages


Don't load last app state if launching with an inbound link

If someone uses a ob: external link to launch the app, use that link instead of loading the last app state in app.js.

@jjeffryes is this still in progress?

Yes.

Revisit issue when we have an update Windows installer.

@jjeffryes What's the update on this?

@drwasho Brian is working on it.

This has been completed.


Python 3 support

Hi,
Last summer I used this library during an internship. During the internship I was working on a Django app which was compatible with both Python 2.7 and 3.4.
I made some small patches to your library to add Python 3 support. I juste cleaned up the test framework to get the Travis tests running on all combinations of supported Python and Django versions.
Please look at it carefully, I needed some iterations to get the travis scripts right.
If you want me to rebase/squash these commits I understand that.

Ties,
Python 3 support sounds great.  Thanks for contributing this.  Let me take
a closer look and get back to you.
Ted
On Fri, Jan 23, 2015 at 8:40 PM, Ties de Kock<EMAIL_ADDRESS>wrote:

Hi,
Last summer I used this library during an internship. During the
internship I was working on a Django app which was compatible with both
Python 2.7 and 3.4.
I made some small patches to your library to add Python 3 support. I juste
cleaned up the test framework to get the Travis tests running on all
combinations of supported Python and Django versions.
Please look at it carefully, I needed some iterations to get the travis
scripts right.
If you want me to rebase/squash these commits I understand that.
You can view, comment on, or merge this pull request online at:
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19
Commit Summary

Partial python3 compatibility
Handle the case where redirect field is empty.
Unit tests pass on Python 3.4.2/Django 1.7
Merge branch 'feature/python3' of github.com:ties/django-shibboleth-remoteuser
into feature/python3
Fix tests for Python 2.7/Django 1.5 combo
Other testrunner does not work yet
Django 1.5 is not supported on 3.4
Update the build matrix to match Django's compatibility

File Changes

M .travis.yml
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-0
(15)
M quicktest.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-1
(47)
M shibboleth/context_processors.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-2
(4)
M shibboleth/decorators.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-3
(2)
M shibboleth/middleware.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-4
(2)
M shibboleth/tests/init.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-5
(2)
M shibboleth/urls.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-6
(10)
M shibboleth/views.py
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19/files#diff-7
(17)

Patch Links:

https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19.patch
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19.diff
—
Reply to this email directly or view it on GitHub
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/pull/19
.

Hi,
Any update on this? ties, any caveats in using your fork of python3? I am trying to get shibboleth working with an app I wrote in django.
Cheers!

We're wondering about the status of this pull request too. We'd be happy to help if there's a specific problem holding this up. Otherwise, should we just use Ties' fork?

bbusenius,
FYI, I have been running ties's version successfully, I don't see any issues as of now.

@all: As far as I know this branch should work. It was worked without problems in the Django application I was integrating it in.
I have not tested it with Python 3.5/Django 1.8. If no alternative is available I recommend that this branch is merged.

Sorry for the delay, and thanks for contributing this PR. Merging it now.

Thanks for merging the feature 😊


(logs get): --log-dir option doesn't show all logs in directory

Note: All commands shown below are run as root.
Describe the bug
greengrass-cli logs get --logs-dir /greengrass/v2/logs doesn't show all logs in the directory.
To Reproduce

Deploy something on greengrass device such that logs are generated. Confirm that greengrass-cli logs get -lf /greengrass/v2/logs/greengrass.log shows the latest log to be at the current time t1.
Revise the deployment with another component which will also generate some logs. Confirm that greengrass-cli logs get -lf /greengrass/v2/logs/greengrass.log shows the latest log to be at the current time t2.
greengrass-cli logs get --logs-dir /greengrass/v2/logs does not show the latest log entry, as shown by greengrass-cli logs get --logs-dir /greengrass/v2/logs.

Expected behavior
I would expect greengrass-cli logs get --logs-dir /greengrass/v2/logs to show a superset of greengrass-cli logs get -lf /greengrass/v2/logs/greengrass.log, since the file /greengrass/v2/logs/greengrass.log is in the /greengrass/v2/logs directory, and logs-dir is documented as searching the whole directory for logs.
Actual behavior
greengrass-cli logs get --logs-dir /greengrass/v2/logs doesn't show the latest log messages. The last returned entry is from a previous deployment (a couple of hours earlier in my case).
Environment

OS: Ubuntu 18.04 on Jetson Nano
JDK version: 11.0.11 2021-04-20 (taken from java --version)
Nucleus version: 2.1.0
CLI version: 2.1.0

Additional context
I would expect --log-dir to look at all log entries present in all files in the specified directory. I usually add filters to this command to look for something specific. Because of this (alleged) bug, I no longer know how to look at all log messages in one command.

Hello Phillipe,
Can you confirm that the log files which you are trying to read are JSON formatted? The log reader will only work for JSON logs and not plain-text.

I confirm. Here is the latest log message generated in /greengrass/v2/logs/greengrass.log:

{"thread":"Thread-10","level":"INFO","eventType":null,"message":"Sending connect response for greengrass-cli-user-0","contexts":{},"loggerName":"software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler","timestamp":1621170371968,"cause":null}

Here is my Nucleus config:

componentType: "NUCLEUS"
configuration:
awsRegion: "us-east-1"
componentStoreMaxSizeBytes: "10000000000"
deploymentPollingFrequency: "15"
deploymentPollingFrequencySeconds: 15
envStage: "prod"
fleetStatus:
periodicStatusPublishIntervalSeconds: 86400
greengrassDataPlanePort: "8443"
iotCredEndpoint: "c1kj80aqxwkeoh.credentials.iot.us-east-1.amazonaws.com"
iotDataEndpoint: "a2kf5unhpbglxb-ats.iot.us-east-1.amazonaws.com"
iotRoleAlias: "MyGreengrassCoreTokenExchangeRoleAlias"
jvmOptions: "-Dlog.store=FILE"
logging:
format: "JSON"
mqtt:
spooler: {}
networkProxy:
proxy: {}
platformOverride: {}
runWithDefault:
posixShell: "sh"
posixUser: "ggc_user:ggc_group"
telemetry: {}
dependencies: []
lifecycle:
bootstrap:
requiresPrivilege: "true"
script: "\nset -eu\nKERNEL_ROOT="/greengrass/v2"\nUNPACK_DIR="/greengrass/v2/packages/artifacts-unarchived/aws.greengrass.Nucleus/2.1.0/aws.greengrass.nucleus"
\nrm -r "$KERNEL_ROOT"/alts/current/*\necho "-Dlog.store=FILE" > "$KERNEL_ROOT/alts/current/launch.params"
\nln -sf "$UNPACK_DIR" "$KERNEL_ROOT/alts/current/distro"\nexit 100"
version: "2.1.0"

@plafer,
We are unable to reproduce this issue. Can you confirm that this is still a problem?
If it is not a problem, or if we do not receive a reply, we will close this issue.


should install help templates

AIO packaging does something stupid with the erb templates for the various help things, patch it up

appears AIO have fixed this


Example for subscribing to topics?

I've been trying to find simple way to subscribe to few topics, but there's no example shared on wiki.
I've setup ApplicationMessageReceived but it's not getting any messages. I guess I need to subscribe to a topic, but there I'm stuck :/
Any pointers how to do it?

Never mind, found one in Unit Tests
https://github.com/chkr1011/MQTTnet/blob/master/Tests/MQTTnet.TestApp.NetFramework/PerformanceTest.cs

Hi @chall3ng3r,
thank you for your support. If you need more information please let me know.
Best regards
Christian

Glad to contribute back, and thank you for awesome lib :)


Offset brightness

Maybe I'm not using integration quite correctly, but I'll try to explain how it works for me: I have only 5-6 devices with brightness and/or color adjustment, I added them all to one integration. And I like the default settings, there is only one nuance. In the chandelier, my diode tape burned out (brightness and color temperature are regulated), I replaced it with another one, accidentally buying less power. And now its brightness is not quite enough for me (I use it only in the evening). It would be great if I could set the brightness offset for this device, for example +10%, in the settings. It seems to me that sunset offset will not work very correctly here, because it will also affect the temperature. Now I'm in daytime mode, I just turn up the brightness from the remote when I need it, but this does not meet the functions of a smart home :)

@bisquit2003 Hey all you need to do is create another configuration for your lower powered bulb, where the max_brightness is 100%. The others you can put on 90% brightness.
You need two configurations so you can store max_brightness values in two switches.

Basically just to to your integrations and add another adaptive-lighting instance.

Basically just to to your integrations and add another adaptive-lighting instance.

Thank you for your advice. But then everything will be lower in brightness at a specific time (for example, when it is already dark, but sleep mode is not turned on yet). I would like everything to remain as it was (for example, at 21.00 the brightness was about 50%, and specifically this chandelier was 60%). Although the best solution would be to install the LED strip of the correct brightness, as it was before)

But it sounds like you're saying the brightness of your lower powered bulb is no longer synced up to the rest of your bulbs? The default max brightness is 100% and it only will adapt to that at midday (noon), there's no way to go to 110% brightness from what you described in OP.

Sorry if I'm missing something obvious.

Are you just wanting the brightness higher for that specific bulb in the evenings?

But it sounds like you're saying the brightness of your lower powered bulb is no longer synced up to the rest of your bulbs? The default max brightness is 100% and it only will adapt to that at midday (noon), there's no way to go to e.g. 110% brightness from what you described in OP.

Of course, I understand that it is impossible to make 110% brightness, but since in the dark before turning on sleep mode, the brightness that the integration sets is much lower than 100%, a small offset to this set value would be my salvation. That is, the integration sets the brightness X, and for one lamp X + offset (or maybe someone needs a negative offset if 2 lamps of different capacities are used nearby), but no more than 100%

Are you just wanting the brightness higher for that specific bulb in the evenings?
You could setup that bulb in two different integrations, one with only the brightness switch on and one with only the color temp switch on. For the brightness integration, disable the color temp switch and set the sunrise/sunset offset. For the color temp integration, set it to default. You can keep the 2nd integration disabled during the day, and then enable it with an automation in the evening.

Well, it's more like Workaround

Are you just wanting the brightness higher for that specific bulb in the evenings?
You could setup that bulb in two different integrations, one with only the brightness switch on and one with only the color temp switch on. For the brightness integration, disable the color temp switch and set the sunrise/sunset offset. For the color temp integration, set it to default. You can keep the 2nd integration disabled during the day, and then enable it with an automation in the evening.

Well, it's more like Workaround

From what I understand anything we put in adaptive-lighting itself would also be a workaround for this issue. Many people keep lights in multiple integrations for this exact reason, it's a lot easier to customize this yourself when using automations.

From what I understand anything we put in adaptive-lighting itself would also be a workaround for this issue. Many people keep lights in multiple integrations for this exact reason, it's a lot easier to customize this yourself when using automation.
Maybe someone else will have a better idea.

I completely agree that I need to take this lamp to the second instance of integration, but reducing the brightness of other lamps in the first instance will not solve my problem, because the lamp I need will still shine dimly at night. And if my offer seems wrong to you, then the only solution for me is sunset offset

From what I understand anything we put in adaptive-lighting itself would also be a workaround for this issue. Many people keep lights in multiple integrations for this exact reason, it's a lot easier to customize this yourself when using automation.
Maybe someone else will have a better idea.

I completely agree that I need to take this lamp to the second instance of integration, but reducing the brightness of other lamps in the first instance will not solve my problem, because the lamp I need will still shine dimly at night. And if my offer seems wrong to you, then the only solution for me is sunset offset

Yeah I suggested two ideas and you're completely right about the first.
With the second, you'll be able to utilize sunset_offset in the 2nd switch to only modify brightness, while the switch is on.
So basically you'd have two switches for the same light light.lower_power_led in the switches:
switch.adaptive_lighting_lower_power_led
switch.adaptive_lighting_lower_power_led_night
switch.adaptive_lighting_lower_power_led_night has a sunset_offset of 3 hours, and the color_temp switch is always off.
During the day, switch.adaptive_lighting_lower_power_led_night is off,
Setup an automation that runs at night to turn switch.adaptive_lighting_lower_power_led_night on and switch.adaptive_lighting_lower_power_led off.
Since the color_temp switch is off, it'll only use the sunset_offset in switch.adaptive_lighting_lower_power_led_night to update the brightness.
Hope that makes sense.

@bisquit2003 Were you able to figure this out? I could write more descriptive steps if you'd like.

@bisquit2003 Were you able to figure this out? I could write more descriptive steps if you'd like.

Yes, I did this: I created a separate installation for this lamp and set the minimum brightness in the settings to at least 40%. It turned out what I wanted, without sunset offset

I think that the issue can be closed


MediaPlayerElement 'shakes' whilst starting to stream video file if machine is using an integrated processor

Describe the bug
When streaming an HLS source through the MediaPlayerElement control, the player will seem to shake rapidly for a few seconds. This only seems to occur during the first few seconds of the initial playback for each media source, if the player loops to the beginning it will not shake.

I have been able to reproduce this bug on an Intel Iris Xe processor, the machine I am running the test on works if the laptop is plugged into the power supply but will produce this bug if not connected to a power source.

Does not occur on my desktop machine or using the dedicated graphics card of my laptop.

Does not occur on another laptop of the exact same model regardless of whether it is plugged in to a power source. This leads me to believe it may be linked to some setting on the machine itself.

Steps to reproduce the bug

Clone this repo: https://github.com/JDilrew/MediaPlayerElement
Run the application
Press the play button on the transport controls

Expected behavior
The HLS video should be streamed smoothly from start to finish.
Screenshots
No response
NuGet package version
None
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response
https://github.com/microsoft/microsoft-ui-xaml/assets/56201127/9e4742f1-9435-4612-af67-2cc6ab218add
mftracelog.zip

@codendone I have attached the requested files, though I appreciate the video is difficult to discern much from. It was tough getting it to display any movement in my captures to demonstrate the issue, as it must be very minute changes in pixels and recording software such as OBS seemed to not capture it at all. In person however the movement was certainly noticable, so hopefully the trace logs are of use.

@JDilrew , thank you for capturing additional information. We suspect this is a dupe of an issue that was fixed with servicing that went out at the end of August. Could you try running windows update and then confirm if the issue is resolved?

@alsepkow I'm afraid my machine has been fully updated and the issue is still present.