use of multiple databases

is it possible to define different databases via SQLAlchemy and be able to get the Session for the requested DB ? something like
from apistar.backends.sqlalchemy_backend import Session

SessionDB1 = Session(NAMEOFDATABASE1)
SessionDB2 = Session(NAMEOFDATABASE2)

def create_customer(session: SessionDB1, name: str):
    customer = Customer(name=name)
    session.add(customer)
    session.flush()  # Flush the changes to the database. This will populate the customer id.
    return {'id': customer.id, 'name': customer.name}

with a configuration like
settings = {
    "DATABASES": {
    "default": {
        "URL": "postgresql://:@localhost/apistar",
        "METADATA": Base.metadata
    },
    "DB1": {
        "URL": "postgresql://:@localhost/apistar1",
        "METADATA": Base.metadata
    }
}
}

So you have some routes that use one database and another route that uses a different one. What is the use case for this behavior?
Your SessionDB1 and SessionDB2 are not registered components and will not be injected by the DependencyInjector in this case.  With your settings in that structure you will need to create two separate Components that return the appropriately configured Session objects and register those with your app.  You can use the README.md and the apistar.backends.sqlalchemy_backend module to see how the framework supplied Session Component is defined and copy that in your code.
If that satisfies your query consider closing this issue.

I could see wanting to have segmentation based on use case for tuning reasons.  I'm going to be hitting this same kind of issue soon with postgres for most things, but postGIS for specific things.

I build an API that needs both a DB for the internal needs of the API + a DB from a legacy system. For some endpoints, both are needed.

Defo a valid use case, yup. I’d suggest that alongside #400 we might want to include an example demonstrating how you can use components parameterized by the argument name in order to achieve this.

Closing this off given that 0.6 is moving to a framework-agnostic suite of API tools, and will no longer include the server. See https://discuss.apistar.org/t/api-star-as-a-framework-independant-tool/614 and #624.


[Feature Request] Configurable padding between pages in dual page mode for Surface Duo/general comfort on tablets

Describe your suggested feature
Add an option to insert a configurable-width deadspace between pages while in dual page mode.
Alternately, allow the user to change the anchoring points of the pages being rendered so the left page is centered on the left half of the display and the right page is centered on the right half, or any other alternate way of keeping visible content out of the center of the screen.
Other details
The Surface Duo line of phones have a gap inbetween their two screens which is treated as part of the main display when an app is spanned across both screens. It spans roughly 64 pixels (haven't dug into the SDK to check yet) and doesn't seem to be able to be disabled. This results in Tachiyomi cutting the left side of the right page and right side of the left page during dual page rendering.
It'd also be nice for certain comics which were intended to be read in book format and rely on deadspace between pages for their layouts (Scott McCloud's books on comics, as an example).
Sorry if this is a repeat request, it's a hard question to search.
Acknowledgements

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

Thinking about how to implement this and I've realized that the border cropper could do it fairly easily by just adding a fixed width horizontal border after cropping. I'm new to Kotlin but I'll take a shot at a PR for this later.

Alright, I've got a functional (but limited) proof of concept solution implemented here but I'm missing localization strings and need an approach for handling spanned pages. I'll PR when I can get it figured out.

Awesome.
Also don't translate anything unless you know the language. Translations are not required for PRs and things like Google translated strings I wouldn't accept.


nodelet manager process has died, exit code -11, dmesg --> usb usb2-port3: cannot disable, segfault

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16

Kernel Version (Linux Only)
4.13.0-36-generic

Platform
PC

SDK Version
2.45.0 }

Language
c++ }

Segment
Robot }

Issue Description
Hi Intel,
I got error when launch official realsense-ros-2.3.0, use my launch file which copy from rs_camera.launch and include/nodelet.launch.xml.
roslaunch error:
[ WARN] [1656065577.814077970]: Param '/fl_cam/stereo_module/auto_exposure_limit' has value 0 that is not in range [1, 200000]. Removing this parameter from dynamic reconfigure options.
[ WARN] [1656065577.827148874]: Param '/fl_cam/stereo_module/auto_gain_limit' has value 0 that is not in range [16, 248]. Removing this parameter from dynamic reconfigure options.
[ INFO] [1656065577.962120107]: Done Setting Dynamic reconfig parameters.
[ INFO] [1656065577.963537216]: depth stream is enabled - width: 848, height: 480, fps: 15, Format: Z16
[ INFO] [1656065577.964731016]: color stream is enabled - width: 640, height: 480, fps: 6, Format: RGB8
[ INFO] [1656065577.968293423]: setupPublishers...
[fl_cam/fl_cam_manager-2] process has died [pid 8828, exit code -11, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=fl_cam_manager __log:=/home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fl_cam-fl_cam_manager-2.log].
log file: /home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fl_cam-fl_cam_manager-2*.log
dmesg error
[   82.557328] audit: type=1400 audit(1656065110.496:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/etc/dconf/profile/user" pid=2878 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[  113.897267] usb 2-2: USB disconnect, device number 2
[  116.283063] usb 2-2: new SuperSpeed USB device number 4 using xhci_hcd
[  116.303670] usb 2-2: New USB device found, idVendor=8086, idProduct=0b07
[  116.303677] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  116.303682] usb 2-2: Product: Intel(R) RealSense(TM) Depth Camera 435
[  116.303686] usb 2-2: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435
[  116.303690] usb 2-2: SerialNumber:<PHONE_NUMBER>87
[  116.305049] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435  (8086:0b07)
[  116.306993] uvcvideo: Unable to create debugfs 2-4 directory.
[  116.307146] uvcvideo 2-2:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[  116.307153] uvcvideo 2-2:1.0: Entity type for entity Processing 2 was not initialized!
[  116.307158] uvcvideo 2-2:1.0: Entity type for entity Camera 1 was not initialized!
[  116.307485] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/input/input21
[  116.308545] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435  (8086:0b07)
[  116.309485] uvcvideo: Unable to create debugfs 2-4 directory.
[  116.309666] uvcvideo 2-2:1.3: Entity type for entity Processing 7 was not initialized!
[  116.309672] uvcvideo 2-2:1.3: Entity type for entity Extension 8 was not initialized!
[  116.309677] uvcvideo 2-2:1.3: Entity type for entity Camera 6 was not initialized!
[  117.522720] xhci_hcd 0000:00:14.0: Cannot set link state.
[  117.522732] usb usb2-port3: cannot disable (err = -32)
[  117.522743] usb 2-3: USB disconnect, device number 3
[  117.523917] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[  117.523939] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[  117.524161] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[  119.082831] usb 2-3: new SuperSpeed USB device number 5 using xhci_hcd
[  119.103201] usb 2-3: New USB device found, idVendor=8086, idProduct=0b3a
[  119.103202] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  119.103203] usb 2-3: Product: Intel(R) RealSense(TM) Depth Camera 435i
[  119.103204] usb 2-3: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435i
[  119.103205] usb 2-3: SerialNumber:<PHONE_NUMBER>33
[  119.104302] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[  119.105887] uvcvideo: Unable to create debugfs 2-5 directory.
[  119.105910] uvcvideo 2-3:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[  119.105911] uvcvideo 2-3:1.0: Entity type for entity Processing 2 was not initialized!
[  119.105912] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[  119.105956] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/input/input22
[  119.106282] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[  119.107060] uvcvideo: Unable to create debugfs 2-5 directory.
[  119.107087] uvcvideo 2-3:1.3: Entity type for entity Processing 7 was not initialized!
[  119.107087] uvcvideo 2-3:1.3: Entity type for entity Extension 8 was not initialized!
[  119.107088] uvcvideo 2-3:1.3: Entity type for entity Camera 6 was not initialized!
[  119.166972] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  119.167442] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  119.227542] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  119.227925] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  119.323565] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  122.333234] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[  131.717974] nodelet[4038]: segfault at 1 ip 00007f84746844a1 sp 00007f843fffda80 error 6 in librostime.so[7f847466d000+2b000]
[  137.668587] nodelet[4020]: segfault at 1 ip 00007fbe2436a4a1 sp 00007fbdefffda80 error 6 in librostime.so[7fbe24353000+2b000]
my launch file:

<node unless="$(arg external_manager)" pkg="nodelet" type="nodelet" name="$(arg manager)" args="manager" output="$(arg output)" required="$(arg required)" respawn="$(arg respawn)"/>
<node pkg="nodelet" type="nodelet" name="node" args="load realsense2_camera/RealSenseNodeFactory $(arg manager)" required="$(arg required)" respawn="$(arg respawn)">
  <param name="serial_no"                type="str"  value="$(arg serial_no)"/>
  <param name="usb_port_id"              type="str"  value="$(arg usb_port_id)"/>
  <param name="device_type"              type="str"  value="$(arg device_type)"/>
  <param name="json_file_path"           type="str"  value="$(arg json_file_path)"/>
  <param name="rosbag_filename"          type="str"  value="$(arg rosbag_filename)"/>

  <param name="enable_pointcloud"        type="bool" value="$(arg enable_pointcloud)"/>
  <param name="pointcloud_texture_stream" type="str" value="$(arg pointcloud_texture_stream)"/>
  <param name="pointcloud_texture_index"  type="int" value="$(arg pointcloud_texture_index)"/>
  <param name="allow_no_texture_points"  type="bool"   value="$(arg allow_no_texture_points)"/>
  <param name="ordered_pc"               type="bool"   value="$(arg ordered_pc)"/>

  <param name="enable_sync"              type="bool" value="$(arg enable_sync)"/>
  <param name="align_depth"              type="bool" value="$(arg align_depth)"/>

  <param name="fisheye_width"            type="int"  value="$(arg fisheye_width)"/>
  <param name="fisheye_height"           type="int"  value="$(arg fisheye_height)"/>
  <param name="enable_fisheye"           type="bool" value="$(arg enable_fisheye)"/>
  <param name="enable_fisheye1"          type="bool" value="$(arg enable_fisheye1)"/>
  <param name="enable_fisheye2"          type="bool" value="$(arg enable_fisheye2)"/>

  <param name="depth_width"              type="int"  value="$(arg depth_width)"/>
  <param name="depth_height"             type="int"  value="$(arg depth_height)"/>
  <param name="enable_depth"             type="bool" value="$(arg enable_depth)"/>

  <param name="confidence_width"         type="int"  value="$(arg confidence_width)"/>
  <param name="confidence_height"        type="int"  value="$(arg confidence_height)"/>
  <param name="enable_confidence"        type="bool" value="$(arg enable_confidence)"/>
  <param name="confidence_fps"           type="int"  value="$(arg confidence_fps)"/>

  <param name="color_width"              type="int"  value="$(arg color_width)"/>
  <param name="color_height"             type="int"  value="$(arg color_height)"/>
  <param name="enable_color"             type="bool" value="$(arg enable_color)"/>

  <param name="infra_width"              type="int"  value="$(arg infra_width)"/>
  <param name="infra_height"             type="int"  value="$(arg infra_height)"/>
  <param name="enable_infra"             type="bool" value="$(arg enable_infra)"/>
  <param name="enable_infra1"            type="bool" value="$(arg enable_infra1)"/>
  <param name="enable_infra2"            type="bool" value="$(arg enable_infra2)"/>
  <param name="infra_rgb"                type="bool" value="$(arg infra_rgb)"/>

  <param name="fisheye_fps"              type="int"  value="$(arg fisheye_fps)"/>
  <param name="depth_fps"                type="int"  value="$(arg depth_fps)"/>
  <param name="infra_fps"                type="int"  value="$(arg infra_fps)"/>
  <param name="color_fps"                type="int"  value="$(arg color_fps)"/>
  <param name="gyro_fps"                 type="int"  value="$(arg gyro_fps)"/>
  <param name="accel_fps"                type="int"  value="$(arg accel_fps)"/>
  <param name="enable_gyro"              type="bool" value="$(arg enable_gyro)"/>
  <param name="enable_accel"             type="bool" value="$(arg enable_accel)"/>
  <param name="enable_pose"              type="bool" value="$(arg enable_pose)"/>

  <param name="base_frame_id"            type="str"  value="$(arg base_frame_id)"/>
  <param name="depth_frame_id"           type="str"  value="$(arg depth_frame_id)"/>
  <param name="infra1_frame_id"          type="str"  value="$(arg infra1_frame_id)"/>
  <param name="infra2_frame_id"          type="str"  value="$(arg infra2_frame_id)"/>
  <param name="color_frame_id"           type="str"  value="$(arg color_frame_id)"/>
  <param name="fisheye_frame_id"         type="str"  value="$(arg fisheye_frame_id)"/>
  <param name="fisheye1_frame_id"        type="str"  value="$(arg fisheye1_frame_id)"/>
  <param name="fisheye2_frame_id"        type="str"  value="$(arg fisheye2_frame_id)"/>
  <param name="accel_frame_id"           type="str"  value="$(arg accel_frame_id)"/>
  <param name="gyro_frame_id"            type="str"  value="$(arg gyro_frame_id)"/>
  <param name="pose_frame_id"            type="str"  value="$(arg pose_frame_id)"/>

  <param name="depth_optical_frame_id"    type="str"  value="$(arg depth_optical_frame_id)"/>
  <param name="infra1_optical_frame_id"   type="str"  value="$(arg infra1_optical_frame_id)"/>
  <param name="infra2_optical_frame_id"   type="str"  value="$(arg infra2_optical_frame_id)"/>
  <param name="color_optical_frame_id"    type="str"  value="$(arg color_optical_frame_id)"/>
  <param name="fisheye_optical_frame_id"  type="str"  value="$(arg fisheye_optical_frame_id)"/>
  <param name="fisheye1_optical_frame_id" type="str"  value="$(arg fisheye1_optical_frame_id)"/>
  <param name="fisheye2_optical_frame_id" type="str"  value="$(arg fisheye2_optical_frame_id)"/>
  <param name="accel_optical_frame_id"    type="str"  value="$(arg accel_optical_frame_id)"/>
  <param name="gyro_optical_frame_id"     type="str"  value="$(arg gyro_optical_frame_id)"/>
  <param name="imu_optical_frame_id"      type="str"  value="$(arg imu_optical_frame_id)"/>
  <param name="pose_optical_frame_id"     type="str"  value="$(arg pose_optical_frame_id)"/>

  <param name="aligned_depth_to_color_frame_id"    type="str"  value="$(arg aligned_depth_to_color_frame_id)"/>
  <param name="aligned_depth_to_infra1_frame_id"   type="str"  value="$(arg aligned_depth_to_infra1_frame_id)"/>
  <param name="aligned_depth_to_infra2_frame_id"   type="str"  value="$(arg aligned_depth_to_infra2_frame_id)"/>
  <param name="aligned_depth_to_fisheye_frame_id"  type="str"  value="$(arg aligned_depth_to_fisheye_frame_id)"/>
  <param name="aligned_depth_to_fisheye1_frame_id" type="str"  value="$(arg aligned_depth_to_fisheye1_frame_id)"/>
  <param name="aligned_depth_to_fisheye2_frame_id" type="str"  value="$(arg aligned_depth_to_fisheye2_frame_id)"/>

  <param name="publish_tf"               type="bool"   value="$(arg publish_tf)"/>
  <param name="tf_publish_rate"          type="double" value="$(arg tf_publish_rate)"/>

  <param name="odom_frame_id"            type="str"  value="$(arg odom_frame_id)"/>
  <param name="topic_odom_in"            type="str"  value="$(arg topic_odom_in)"/>
  <param name="calib_odom_file"          type="str"    value="$(arg calib_odom_file)"/>
  <param name="publish_odom_tf"          type="bool" value="$(arg publish_odom_tf)"/>
  <param name="stereo_module/exposure/1" type="int"  value="$(arg stereo_module/exposure/1)"/>
  <param name="stereo_module/gain/1"     type="int"  value="$(arg stereo_module/gain/1)"/>
  <param name="stereo_module/exposure/2" type="int"  value="$(arg stereo_module/exposure/2)"/>
  <param name="stereo_module/gain/2"     type="int"  value="$(arg stereo_module/gain/2)"/>

  <param name="filters"                  type="str"    value="$(arg filters)"/>
  <param name="clip_distance"            type="double" value="$(arg clip_distance)"/>
  <param name="linear_accel_cov"         type="double" value="$(arg linear_accel_cov)"/>
  <param name="initial_reset"            type="bool"   value="$(arg initial_reset)"/>
  <param name="reconnect_timeout"        type="double" value="$(arg reconnect_timeout)"/>
  <param name="wait_for_device_timeout"  type="double" value="$(arg wait_for_device_timeout)"/>
  <param name="unite_imu_method"         type="str"    value="$(arg unite_imu_method)"/>
</node>
<node pkg="nodelet" type="nodelet" name="depth_points"
    args="load depth_image_proc/point_cloud_xyz $(arg manager) --no-bond"
    respawn="$(arg respawn)" output="$(arg output)">
  <remap from="image_rect" to="/$(arg camera)/aligned_depth_to_color/image_raw"/>
  <remap from="points"     to="/$(arg camera)/aligned_depth_to_color/points" />
</node>
<node pkg="topic_tools" type="throttle" name="$(arg camera)_color_hz_control" args="messages /$(arg camera)/color/image_raw 6 /$(arg camera)/color/image_raw/fix_rate" output="$(arg output)"/>

Hi @byhang  Is launch able to complete successfully if you use the original rs_camera.launch instead of your own copy of it?
Also, I note that your roslaunch log is identifying two separate cameras with unique serial numbers, a D435 and D435i.  Can you confirm whether you are launching more than one camera, please?  Thanks!

Hi @MartyG-RealSense
We use D435 D435i and D430, randomly, multi camera.
I use the original rs_camera.launch, got error, too.
➜  ~ roslaunch realsense2_camera rs_camera.launch camera:=fcb_hu_cam usb_port_id:=2-2
... logging to /home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/roslaunch-Eros-28314.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://Eros:41353/
SUMMARY
PARAMETERS

/fcb_hu_cam/realsense2_camera/accel_fps: -1
/fcb_hu_cam/realsense2_camera/accel_frame_id: fcb_hu_cam_accel_...
/fcb_hu_cam/realsense2_camera/accel_optical_frame_id: fcb_hu_cam_accel_...
/fcb_hu_cam/realsense2_camera/align_depth: False
/fcb_hu_cam/realsense2_camera/aligned_depth_to_color_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/aligned_depth_to_fisheye1_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/aligned_depth_to_fisheye2_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/aligned_depth_to_fisheye_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/aligned_depth_to_infra1_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/aligned_depth_to_infra2_frame_id: fcb_hu_cam_aligne...
/fcb_hu_cam/realsense2_camera/allow_no_texture_points: False
/fcb_hu_cam/realsense2_camera/base_frame_id: fcb_hu_cam_link
/fcb_hu_cam/realsense2_camera/calib_odom_file:
/fcb_hu_cam/realsense2_camera/clip_distance: -2.0
/fcb_hu_cam/realsense2_camera/color_fps: -1
/fcb_hu_cam/realsense2_camera/color_frame_id: fcb_hu_cam_color_...
/fcb_hu_cam/realsense2_camera/color_height: -1
/fcb_hu_cam/realsense2_camera/color_optical_frame_id: fcb_hu_cam_color_...
/fcb_hu_cam/realsense2_camera/color_width: -1
/fcb_hu_cam/realsense2_camera/confidence_fps: -1
/fcb_hu_cam/realsense2_camera/confidence_height: -1
/fcb_hu_cam/realsense2_camera/confidence_width: -1
/fcb_hu_cam/realsense2_camera/depth_fps: -1
/fcb_hu_cam/realsense2_camera/depth_frame_id: fcb_hu_cam_depth_...
/fcb_hu_cam/realsense2_camera/depth_height: -1
/fcb_hu_cam/realsense2_camera/depth_optical_frame_id: fcb_hu_cam_depth_...
/fcb_hu_cam/realsense2_camera/depth_width: -1
/fcb_hu_cam/realsense2_camera/device_type:
/fcb_hu_cam/realsense2_camera/enable_accel: False
/fcb_hu_cam/realsense2_camera/enable_color: True
/fcb_hu_cam/realsense2_camera/enable_confidence: True
/fcb_hu_cam/realsense2_camera/enable_depth: True
/fcb_hu_cam/realsense2_camera/enable_fisheye1: False
/fcb_hu_cam/realsense2_camera/enable_fisheye2: False
/fcb_hu_cam/realsense2_camera/enable_fisheye: False
/fcb_hu_cam/realsense2_camera/enable_gyro: False
/fcb_hu_cam/realsense2_camera/enable_infra1: False
/fcb_hu_cam/realsense2_camera/enable_infra2: False
/fcb_hu_cam/realsense2_camera/enable_infra: False
/fcb_hu_cam/realsense2_camera/enable_pointcloud: False
/fcb_hu_cam/realsense2_camera/enable_pose: False
/fcb_hu_cam/realsense2_camera/enable_sync: False
/fcb_hu_cam/realsense2_camera/filters:
/fcb_hu_cam/realsense2_camera/fisheye1_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye1_optical_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye2_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye2_optical_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye_fps: -1
/fcb_hu_cam/realsense2_camera/fisheye_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye_height: -1
/fcb_hu_cam/realsense2_camera/fisheye_optical_frame_id: fcb_hu_cam_fishey...
/fcb_hu_cam/realsense2_camera/fisheye_width: -1
/fcb_hu_cam/realsense2_camera/gyro_fps: -1
/fcb_hu_cam/realsense2_camera/gyro_frame_id: fcb_hu_cam_gyro_f...
/fcb_hu_cam/realsense2_camera/gyro_optical_frame_id: fcb_hu_cam_gyro_o...
/fcb_hu_cam/realsense2_camera/imu_optical_frame_id: fcb_hu_cam_imu_op...
/fcb_hu_cam/realsense2_camera/infra1_frame_id: fcb_hu_cam_infra1...
/fcb_hu_cam/realsense2_camera/infra1_optical_frame_id: fcb_hu_cam_infra1...
/fcb_hu_cam/realsense2_camera/infra2_frame_id: fcb_hu_cam_infra2...
/fcb_hu_cam/realsense2_camera/infra2_optical_frame_id: fcb_hu_cam_infra2...
/fcb_hu_cam/realsense2_camera/infra_fps: 30
/fcb_hu_cam/realsense2_camera/infra_height: 480
/fcb_hu_cam/realsense2_camera/infra_rgb: False
/fcb_hu_cam/realsense2_camera/infra_width: 848
/fcb_hu_cam/realsense2_camera/initial_reset: False
/fcb_hu_cam/realsense2_camera/json_file_path:
/fcb_hu_cam/realsense2_camera/linear_accel_cov: 0.01
/fcb_hu_cam/realsense2_camera/odom_frame_id: fcb_hu_cam_odom_f...
/fcb_hu_cam/realsense2_camera/ordered_pc: False
/fcb_hu_cam/realsense2_camera/pointcloud_texture_index: 0
/fcb_hu_cam/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
/fcb_hu_cam/realsense2_camera/pose_frame_id: fcb_hu_cam_pose_f...
/fcb_hu_cam/realsense2_camera/pose_optical_frame_id: fcb_hu_cam_pose_o...
/fcb_hu_cam/realsense2_camera/publish_odom_tf: True
/fcb_hu_cam/realsense2_camera/publish_tf: True
/fcb_hu_cam/realsense2_camera/rosbag_filename:
/fcb_hu_cam/realsense2_camera/serial_no:
/fcb_hu_cam/realsense2_camera/stereo_module/exposure/1: 7500
/fcb_hu_cam/realsense2_camera/stereo_module/exposure/2: 1
/fcb_hu_cam/realsense2_camera/stereo_module/gain/1: 16
/fcb_hu_cam/realsense2_camera/stereo_module/gain/2: 16
/fcb_hu_cam/realsense2_camera/tf_publish_rate: 0.0
/fcb_hu_cam/realsense2_camera/topic_odom_in: odom_in
/fcb_hu_cam/realsense2_camera/unite_imu_method:
/fcb_hu_cam/realsense2_camera/usb_port_id: 2-2
/rosdistro: kinetic
/rosversion: 1.12.13

NODES
/fcb_hu_cam/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
process[fcb_hu_cam/realsense2_camera_manager-1]: started with pid [28333]
process[fcb_hu_cam/realsense2_camera-2]: started with pid [28334]
[ INFO] [1656216895.017738315]: Initializing nodelet with 8 worker threads.
[ INFO] [1656216895.068328899]: RealSense ROS v2.3.0
[ INFO] [1656216895.068358642]: Built with LibRealSense v2.45.0
[ INFO] [1656216895.068373666]: Running with LibRealSense v2.45.0
[ INFO] [1656216895.093109684]:
[ INFO] [1656216895.387393310]: Device with serial number<PHONE_NUMBER>60 was found.
[ INFO] [1656216895.387487237]: Device with physical ID 2-2-12 was found.
[ INFO] [1656216895.387535774]: Device with name Intel RealSense D435 was found.
[ INFO] [1656216895.389099052]: Device with port number 2-2 was found.
[ INFO] [1656216895.389212797]: Device USB type: 3.2
[ INFO] [1656216895.395130169]: getParameters...
[ INFO] [1656216895.495449629]: setupDevice...
[ INFO] [1656216895.495481280]: JSON file is not provided
[ INFO] [1656216895.495494822]: ROS Node Namespace: fcb_hu_cam
[ INFO] [1656216895.495508840]: Device Name: Intel RealSense D435
[ INFO] [1656216895.495520234]: Device Serial No:<PHONE_NUMBER>60
[ INFO] [1656216895.495534481]: Device physical port: 2-2-12
[ INFO] [1656216895.495547952]: Device FW version: <IP_ADDRESS>
[ INFO] [1656216895.495559772]: Device Product ID: 0x0B07
[ INFO] [1656216895.495572669]: Enable PointCloud: Off
[ INFO] [1656216895.495587460]: Align Depth: Off
[ INFO] [1656216895.495601466]: Sync Mode: Off
[ INFO] [1656216895.495649676]: Device Sensors:
[ INFO] [1656216895.511838372]: Stereo Module was found.
[ INFO] [1656216895.524228121]: RGB Camera was found.
[ INFO] [1656216895.524279195]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1656216895.524307441]: num_filters: 0
[ INFO] [1656216895.524327996]: Setting Dynamic reconfig parameters.
[ WARN] [1656216895.972641477]: Param '/fcb_hu_cam/stereo_module/auto_exposure_limit' has value 0 that is not in range [1, 200000]. Removing this parameter from dynamic reconfigure options.
[ WARN] [1656216895.986240455]: Param '/fcb_hu_cam/stereo_module/auto_gain_limit' has value 0 that is not in range [16, 248]. Removing this parameter from dynamic reconfigure options.
[ INFO] [1656216896.102135764]: Done Setting Dynamic reconfig parameters.
[ INFO] [1656216896.103791925]: depth stream is enabled - width: 848, height: 480, fps: 30, Format: Z16
[ INFO] [1656216896.105308260]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8
[ INFO] [1656216896.105387437]: setupPublishers...
[fcb_hu_cam/realsense2_camera_manager-1] process has died [pid 28333, exit code -11, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=realsense2_camera_manager __log:=/home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fcb_hu_cam-realsense2_camera_manager-1.log].
log file: /home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fcb_hu_cam-realsense2_camera_manager-1*.log
^C[fcb_hu_cam/realsense2_camera-2] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
dmesg
[ 2666.520371] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/input/input28
[ 2666.521193] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435  (8086:0b07)
[ 2666.522080] uvcvideo: Unable to create debugfs 2-11 directory.
[ 2666.522234] uvcvideo 2-2:1.3: Entity type for entity Processing 7 was not initialized!
[ 2666.522239] uvcvideo 2-2:1.3: Entity type for entity Extension 8 was not initialized!
[ 2666.522242] uvcvideo 2-2:1.3: Entity type for entity Camera 6 was not initialized!
[ 2714.803929] usb 2-2: USB disconnect, device number 11
[ 2718.639787] usb 2-2: new SuperSpeed USB device number 12 using xhci_hcd
[ 2718.660401] usb 2-2: New USB device found, idVendor=8086, idProduct=0b07
[ 2718.660408] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2718.660412] usb 2-2: Product: Intel(R) RealSense(TM) Depth Camera 435
[ 2718.660417] usb 2-2: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435
[ 2718.660420] usb 2-2: SerialNumber:<PHONE_NUMBER>87
[ 2718.661760] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435  (8086:0b07)
[ 2718.663733] uvcvideo: Unable to create debugfs 2-12 directory.
[ 2718.663943] uvcvideo 2-2:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 2718.663948] uvcvideo 2-2:1.0: Entity type for entity Processing 2 was not initialized!
[ 2718.663952] uvcvideo 2-2:1.0: Entity type for entity Camera 1 was not initialized!
[ 2718.664199] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/input/input29
[ 2718.664971] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435  (8086:0b07)
[ 2718.665836] uvcvideo: Unable to create debugfs 2-12 directory.
[ 2718.666027] uvcvideo 2-2:1.3: Entity type for entity Processing 7 was not initialized!
[ 2718.666032] uvcvideo 2-2:1.3: Entity type for entity Extension 8 was not initialized!
[ 2718.666035] uvcvideo 2-2:1.3: Entity type for entity Camera 6 was not initialized!
[ 2955.783495] nodelet[28398]: segfault at 1 ip 00007f692c3394a1 sp 00007f6903703a80 error 6 in librostime.so[7f692c322000+2b000]
[ 3226.320203] hid-sensor-hub 0003:8086:0B3A.0006: No report with id 0xffffffff found
[ 3226.357131] hid-sensor-hub 0003:8086:0B3A.0006: No report with id 0xffffffff found
[ 3230.068119] hid-sensor-hub 0003:8086:0B3A.0006: No report with id 0xffffffff found
[ 3230.068405] hid-sensor-hub 0003:8086:0B3A.0006: No report with id 0xffffffff found

The cause of the 'entity type' kernel messages tends to be difficult to trace and if they are corrected then you may never find out for sure what caused them in the first place.  I previously enquired to the RealSense development team about them in 2020 and received the following explanation.

The message “Entity camera ... not initialized" is related to UVC topology defined in the firmware descriptor for USB device.
Those are protocol-specific messages and are apparently stemmed from firmware.

The most recent RealSense ROS user who experienced the errors suspected at https://github.com/IntelRealSense/librealsense/issues/10158#issuecomment-1028817808 that the problem had occurred because they had several different versions of the librealsense SDK installed on their computer. Is the presence of multiple installations a possibility on your own computer, please?

Hi @MartyG-RealSense ,
Thanks for your quick reply.
This is my installed deb version, all are the default, lasted versions in Ubuntu-16.04.
librealsense2_2.50.0-0~realsense0.6126_amd64.deb
librealsense2-dkms_1.3.18-0ubuntu1_all.deb
librealsense2-gl_2.50.0-0~realsense0.6126_amd64.deb
librealsense2-net_2.50.0-0~realsense0.6126_amd64.deb
librealsense2-udev-rules_2.50.0-0~realsense0.6126_amd64.deb
librealsense2-utils_2.50.0-0~realsense0.6126_amd64.deb
ros-kinetic-ddynamic-reconfigure_0.2.0-0xenial-20210503-114111-0800_amd64.deb
ros-kinetic-librealsense2_2.45.0-1xenial-20210506-081043-0800_amd64.deb
ros-kinetic-realsense2-camera_2.3.0-1xenial-20210506-084151-0800_amd64.deb

Building for 4.13.0-36-generic and 4.15.0-142-generic
Building initial module for 4.13.0-36-generic
Secure Boot not enabled on this system.
Maybe dkms error?

install log
➜  sudo apt-get install librealsense2-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
daemontools fonts-droid-fallback fonts-noto-mono libatk-bridge2.0-dev libatspi2.0-dev libepoxy-dev libglfw3 libgmp-dev libgmpxx4ldbl libgtk-3-dev libwnck-common libwnck22 libxfce4ui-1-0 libxfce4ui-common libxfce4util-bin
libxfce4util-common libxfce4util7 libxfconf-0-2 libxtst-dev nettle-dev x11proto-record-dev xfconf
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
librealsense2-udev-rules
The following NEW packages will be installed:
librealsense2-dkms librealsense2-udev-rules
0 upgraded, 2 newly installed, 0 to remove and 887 not upgraded.
Need to get 10.3 MB of archives.
After this operation, 81.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://librealsense.intel.com/Debian/apt-repo xenial/main amd64 librealsense2-dkms all 1.3.18-0ubuntu1 [10.3 MB]
Get:2 https://librealsense.intel.com/Debian/apt-repo xenial/main amd64 librealsense2-udev-rules amd64 2.50.0-0~realsense0.6126 [7,788 B]
Fetched 10.3 MB in 6s (1,522 kB/s)
Selecting previously unselected package librealsense2-dkms.
(Reading database ... 565549 files and directories currently installed.)
Preparing to unpack .../librealsense2-dkms_1.3.18-0ubuntu1_all.deb ...
Unpacking librealsense2-dkms (1.3.18-0ubuntu1) ...
Selecting previously unselected package librealsense2-udev-rules:amd64.
Preparing to unpack .../librealsense2-udev-rules_2.50.0-0~realsense0.6126_amd64.deb ...
Unpacking librealsense2-udev-rules:amd64 (2.50.0-0~realsense0.6126) ...
Setting up librealsense2-dkms (1.3.18-0ubuntu1) ...
Loading new librealsense2-dkms-1.3.18 DKMS files...
First Installation: checking all kernels...
Building for 4.13.0-36-generic and 4.15.0-142-generic
Building initial module for 4.13.0-36-generic
Secure Boot not enabled on this system.
Done.
uvcvideo:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.13.0-36-generic/updates/dkms/

videodev.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.13.0-36-generic/updates/dkms/

hid-sensor-accel-3d.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.13.0-36-generic/updates/dkms/

hid-sensor-gyro-3d.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.13.0-36-generic/updates/dkms/

depmod....
DKMS: install completed.
Building initial module for 4.15.0-142-generic
Secure Boot not enabled on this system.
Done.
uvcvideo:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.15.0-142-generic/updates/dkms/

videodev.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.15.0-142-generic/updates/dkms/

hid-sensor-accel-3d.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.15.0-142-generic/updates/dkms/

hid-sensor-gyro-3d.ko:
Running module version sanity check.

Original module
Installation

Installing to /lib/modules/4.15.0-142-generic/updates/dkms/

depmod....
DKMS: install completed.
\nLoading the modified modules into kernel... complete
Current status:
bbswitch, 0.8, 4.15.0-101-generic, x86_64: installed
bbswitch, 0.8, 4.15.0-142-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-210-generic, x86_64: installed
librealsense2-dkms, 1.3.18, 4.13.0-36-generic, x86_64: installed
librealsense2-dkms, 1.3.18, 4.15.0-142-generic, x86_64: installed
nvidia, 430.64, 4.13.0-36-generic, x86_64: installed
nvidia, 430.64, 4.15.0-142-generic, x86_64: installed
mod: videodev \t\t\t version: realsense2-dkms
mod: uvcvideo \t\t\t version: 1.1.2.realsense-1.3.18
mod: hid_sensor_gyro_3d \t version: realsense2-dkms
mod: hid_sensor_accel_3d \t version: realsense2-dkms
Setting up librealsense2-udev-rules:amd64 (2.50.0-0~realsense0.6126) ...
\nPostinst script activated...
Presets deployment:
no src dir
tgt dir exists
Presets deployment is skipped
➜  sudo apt-get install ros-$ROS_DISTRO-realsense2-camera
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
daemontools fonts-droid-fallback fonts-noto-mono libatk-bridge2.0-dev libatspi2.0-dev libepoxy-dev libglfw3 libgmp-dev libgmpxx4ldbl libgtk-3-dev libwnck-common libwnck22 libxfce4ui-1-0 libxfce4ui-common libxfce4util-bin
libxfce4util-common libxfce4util7 libxfconf-0-2 libxtst-dev nettle-dev x11proto-record-dev xfconf
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
ros-kinetic-ddynamic-reconfigure ros-kinetic-librealsense2
The following NEW packages will be installed:
ros-kinetic-ddynamic-reconfigure ros-kinetic-librealsense2 ros-kinetic-realsense2-camera
0 upgraded, 3 newly installed, 0 to remove and 887 not upgraded.
Need to get 13.1 MB of archives.
After this operation, 36.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-librealsense2 amd64 2.45.0-1xenial-20210506-081043-0800 [12.8 MB]
Get:2 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-ddynamic-reconfigure amd64 0.2.0-0xenial-20210503-114111-0800 [57.7 kB]
Get:3 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-realsense2-camera amd64 2.3.0-1xenial-20210506-084151-0800 [308 kB]
Fetched 13.1 MB in 1min 30s (144 kB/s)
Selecting previously unselected package ros-kinetic-librealsense2.
(Reading database ... 571989 files and directories currently installed.)
Preparing to unpack .../ros-kinetic-librealsense2_2.45.0-1xenial-20210506-081043-0800_amd64.deb ...
Unpacking ros-kinetic-librealsense2 (2.45.0-1xenial-20210506-081043-0800) ...
Selecting previously unselected package ros-kinetic-ddynamic-reconfigure.
Preparing to unpack .../ros-kinetic-ddynamic-reconfigure_0.2.0-0xenial-20210503-114111-0800_amd64.deb ...
Unpacking ros-kinetic-ddynamic-reconfigure (0.2.0-0xenial-20210503-114111-0800) ...
Selecting previously unselected package ros-kinetic-realsense2-camera.
Preparing to unpack .../ros-kinetic-realsense2-camera_2.3.0-1xenial-20210506-084151-0800_amd64.deb ...
Unpacking ros-kinetic-realsense2-camera (2.3.0-1xenial-20210506-084151-0800) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Setting up ros-kinetic-librealsense2 (2.45.0-1xenial-20210506-081043-0800) ...
Setting up ros-kinetic-ddynamic-reconfigure (0.2.0-0xenial-20210503-114111-0800) ...
Setting up ros-kinetic-realsense2-camera (2.3.0-1xenial-20210506-084151-0800) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...

From the information at the top of this case, it looks as though your intention was to use librealsense 2.45.0 and its matching ROS wrapper 2.3.0.  Indeed, this is shown in the roslaunch log.

In your latest comment at https://github.com/IntelRealSense/librealsense/issues/10624#issuecomment-1166489616 the logs have references to both librealsense 2.45.0 and 2.50.0, and two different kernel versions (4.13.0-36-generic and 4.15.0-142-generic).
In that comment, it also logs that the ros wrapper's 'Method 1' installation process of sudo apt-get install ros-$ROS_DISTRO-realsense2-camera was used.  This would install both the librealsense SDK and the ROS wrapper from packages at the same time.  This install method will also install the currently latest librealsense version and its matching wrapper.  So using that command today would not install 2.45.0 and 2.3.0, but instead install librealsense 2.50.0 and wrapper 2.3.2.
So if you had already installed librealsense 2.45.0 previously and then ran the Method 1 command then you could end up with two potentially conflicting installations of different versions of librealsense on the same computer.
My recommendations would therefore be:

If you have previously installed the ROS wrapper from source code then delete the entire ROS catkin workspace folder /catkin_ws/src/

Run the command below to uninstall all librealsense-related packages.

dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge

Install librealsense 2.50.0 and wrapper 2.3.2 together at the same time from packages with the command below.

sudo apt-get install ros-$ROS_DISTRO-realsense2-camera

Hi @MartyG-RealSense
sudo apt-get install ros-$ROS_DISTRO-realsense2-camera=2.3.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.3.2' for 'ros-kinetic-realsense2-camera' was not found
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
The newest version is 2.3.0 in my env, How can I do for official version 2.3.2?
apt search librealsense
Sorting... Done
Full Text Search... Done
librealsense2/xenial,now 2.50.0-0~realsense0.6126 amd64 [installed,automatic]
Intel(R) RealSense(tm) Cross Platform API - runtime
librealsense2-dbg/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) Camera Capture API - debug symbols
librealsense2-dev/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) Camera Capture API - development files
librealsense2-dkms/xenial,now 1.3.18-0ubuntu1 all [installed]
Modified kernel modules for librealsense2
librealsense2-gl/xenial,now 2.50.0-0~realsense0.6126 amd64 [installed,automatic]
Intel(R) RealSense(tm) - GLSL-enabled extensions
librealsense2-gl-dbg/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) GLSL extensions - debug symbols
librealsense2-gl-dev/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) Camera Capture API - development files
librealsense2-net/xenial,now 2.50.0-0~realsense0.6126 amd64 [installed,automatic]
Intel(R) RealSense(tm) - Network Bridge extension
librealsense2-net-dbg/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) Network Bridge extension - debug symbols
librealsense2-net-dev/xenial 2.50.0-0~realsense0.6126 amd64
Intel(R) RealSense(tm) Camera Capture API - Network Bridge extension development files
librealsense2-udev-rules/xenial,now 2.50.0-0~realsense0.6126 amd64 [installed,automatic]
Intel(R) RealSense(tm) Camera Capture API - udev rules
librealsense2-utils/xenial,now 2.50.0-0~realsense0.6126 amd64 [installed]
Intel(R) RealSense(tm) Camera Capture API - utils and demos
realsense-sdk-dev/xenial 2.7.7-0~realsense0.29 amd64
Intel(R) RealSense(tm) Camera Capture API - development files
realsense-sdk-utils/xenial 2.7.7-0~realsense0.29 amd64
Intel(R) RealSense(tm) Camera Capture API - utils and demos
ros-kinetic-librealsense/xenial 1.12.2-1xenial-20210506-081035-0800 amd64
Library for capturing data from the Intel(R) RealSense(TM) F200, SR300, R200, LR200 and ZR300 cameras.
ros-kinetic-librealsense2/xenial,now 2.45.0-1xenial-20210506-081043-0800 amd64 [installed,automatic]
Library for capturing data from the Intel(R) RealSense(TM) SR300, D400 Depth cameras and T2xx Tracking devices.

Hi @MartyG-RealSense ,
Are there any bugs in official realsense-ros-2.3.0?
I have to test at 2.3.0, because the newest official version is 2.3.0 in Ubuntu-16.04.
But I got same error,
use:

librealsense2-2.45.0
ros-kinetic-librealsense2-2.45.0
ros-kinetic-realsense2-camera-2.3.0
Ubuntu-16.04
4.13.0-36-generic kernel only (4.15.0-* are removed, than reinstall realsense deb)
official rs_camera.launch

$ dpkg -l | grep realsense

ii  librealsense2-dkms                           1.3.18-0ubuntu1                                       all          Modified kernel modules for librealsense2
ii  librealsense2-udev-rules:amd64               2.45.0-0~realsense0.4550                              amd64        Intel(R) RealSense(tm) Camera Capture API - udev rules
ii  ros-kinetic-librealsense2                    2.45.0-1xenial-20210506-081043-0800                   amd64        Library for capturing data from the Intel(R) RealSense(TM) SR300, D400 Depth cameras and T2xx Tracking devices.
ii  ros-kinetic-realsense2-camera                2.3.0-1xenial-20210506-084151-0800                    amd64        RealSense Camera package allowing access to Intel T265 Tracking module and SR300 and D400 3D cameras

$ roslaunch realsense2_camera rs_camera.launch usb_port_id:=2-2
[ INFO] [1656321482.793619608]: Stereo Module was found.
[ INFO] [1656321482.810608329]: RGB Camera was found.
[ INFO] [1656321482.811011033]: Motion Module was found.
[ INFO] [1656321482.811061586]: (Confidence, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1656321482.811094068]: num_filters: 0
[ INFO] [1656321482.811118709]: Setting Dynamic reconfig parameters.
[ WARN] [1656321483.256434565]: Param '/camera/stereo_module/auto_exposure_limit' has value 0 that is not in range [1, 200000]. Removing this parameter from dynamic reconfigure options.
[ WARN] [1656321483.270204556]: Param '/camera/stereo_module/auto_gain_limit' has value 0 that is not in range [16, 248]. Removing this parameter from dynamic reconfigure options.
[ INFO] [1656321483.398787511]: Done Setting Dynamic reconfig parameters.
[ INFO] [1656321483.400456437]: depth stream is enabled - width: 848, height: 480, fps: 30, Format: Z16
[ INFO] [1656321483.404092036]: color stream is enabled - width: 1280, height: 720, fps: 30, Format: RGB8
[ INFO] [1656321483.404170844]: setupPublishers...
[camera/realsense2_camera_manager-1] process has died [pid 7319, exit code -11, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=realsense2_camera_manager __log:=/home/byhang/.ros/log/8af7c8e0-f5f9-11ec-bba1-74e5f9ec52bb/camera-realsense2_camera_manager-1.log].
log file: /home/byhang/.ros/log/8af7c8e0-f5f9-11ec-bba1-74e5f9ec52bb/camera-realsense2_camera_manager-1*.log
dmesg
[  268.246154] nodelet[5891]: segfault at 1 ip 00007f762eef24a1 sp 00007f760127ba80 error 6 in librostime.so[7f762eedb000+2b000]

Regarding the [camera/realsense2_camera_manager-1] process has died error at the end of the launch process, a RealSense ROS user of Kinetic experienced it in https://github.com/IntelRealSense/realsense-ros/issues/473 and the solution for them in their particular case was a completely fresh installation.
In another similar case at https://github.com/IntelRealSense/realsense-ros/issues/1774 where the error number was -2 instead of -1, building the ROS wrapper from source code instead of packages resolved it.

Thank you @MartyG-RealSense very much for your careful assistance.
In Ubuntu-16.04, I build ddynamic-reconfigure-0.3.2、 realsense-ros-2.3.2 and librealsense2-2.50.0 from source code, than I solved this problem.


Not compiling under Windows / VS 2012

I tried building the example project under VS 2012 and unfortunately it completely fails. After updating all the project paths in the config file, the first error I'm getting is that it doesn't understand the __attribute__((packed)) syntax. After simply removing that, the next compile error comes up, etc.
Do you have a suggestion how to run it with VS 2012? Do I maybe need to follow libartnet's compilation instructions to build a .lib or .dll first (using MINGW)?
Thanks!

I don't think you should do something for compiling this.
Now there is no windows here because I am out for a while.
Could you wait some days for it.
When I get back to home, I will check this.
thanks

Great, thanks! It could also just be the VS project settings that need to get properly adjusted.
In the meantime, I did build the dll using MinGW, but I couldn't get that to load either.
So I'm looking forward to your trial. :)

Hello @aknoerig
I checked this issue and found some maintenance is required.
I pushed latest one. So everything must be fine!
Thanks,

Awesome, works like a charm! You just need to fix the reference to icon.rc in the vcxproj - either add the file or remove the reference.
Thanks!


Add new lievin cots

Adds the new Lievin CoTs for med_qa, medmc_qa and pubmed_qa

Fixes #66

Sorry for merging this so fast, I need it unfortunately for the plots


Add optional support of '#' character for comments + "key_name only"

Due to some weird INI files I have to manage (e.g. in https://sourceforge.net/projects/dhcpserver/ project), I would optionally like to support '#' character for comments, and have the ability to have keys without any value, and w/o the '=' sign as well.
So, for this and to keep compatibilty, 3 "defines" can be optionally added before including "mini/ini.h" file:

MINI_SUPPORT_HASH_CHARACTER_AS_COMMENT: support of '#' character for comments
MINI_SUPPORT_KEYNAME_ONLY: support of "key name" w/o any value nor '=' sign. 2 helper methods "isKeyNameOnly" + "setKeyNameOnly" are also added for managing this
MINI_KEYNAME_ONLY_VALUE: can be overridden for preventing possible collisions (default: "[^--NOVALUE--^]")

e.g.
Initial ini file
[fruits]
; My comment 1
apples=
# My comment 2
oranges=54
bananas=300
pears=
avocados

C code
...
#define MINI_SUPPORT_HASH_CHARACTER_AS_COMMENT
#define MINI_SUPPORT_KEYNAME_ONLY
#include "../mINI/src/mini/ini.h"

...

        const char* key = "avocados";
        if (ini["fruits"].isKeyNameOnly(key))
        {
            printf("\"keyname only\" for '%s' found.\n", key);
            // remove it
            ini["fruits"].remove(key);
            //  add a new one
            key = "ananas";
            ini["fruits"].setKeyNameOnly(key);
        }
        else
        {
            printf("\"keyname only\" not present for '%s'\n", key);
        }
...

ini file after changes
[fruits]
; My comment 1
apples=
# My comment 2
oranges=54
bananas=300
pears=
ananas

Hey - thanks for the contribution. Unfortunately this change would actually break some of my own uses for this library where various malformed lines are simply ignored rather than parsed, which is the desired functionality. I suggest you simply fork the library and add this functionality in. Thanks again and sorry for rejecting the PR.


replace utils/strings/InSlice to slices.Contains

How we don't need this deprecated function InSlice:
https://github.com/aquasecurity/trivy-db/blob/main/pkg/utils/strings/strings.go#L28-L35

@afdesk i just have to delete the inslice function.

@souravsk it seems Go version should be bumped up 1.18 for using slices.Contains. need to test it

Okay so are you going to update the go version

@afdesk can i take up this ??


use Env.GetUID() instead of LoggedInLoad() in tryGregordConnect

The previous approach would short circuit if the network was down. That
meant that the service would never retry connecting to gregor if the
network came back up. (In practice this caused some NPE crashes.)
This approach always starts the reconnect loop, as long as the user has
logged in before.
One of the goals here is to avoid consuming battery if the user's
actually logged out. However keybase logout doesn't clear the
GetUID, so this isn't perfect. @patrickxb, do you know a way to tell
whether we expect to be logged in, without actually hitting the
network?
r? @mmaxim @maxtaco

Are you saying that the network call in LoggedInLoad() is draining laptop batteries?  If the user is logged out, there will be no network call in LoggedInLoad().  HasSessionToken() will return false, check() won't be called.

He is saying that spamming retries to connect to Gregor when you are logged out would drain the battery, hence it is justified we have this logged in check in the first place (since if you aren't logged in, then all auth attempts against Gregor will fail).
The crux of the problem is that the called to LoggedInLoad fails if you are offline, so we never actually attempt to connect to Gregor. Once you come back online, OnLogin doesn't get called, and so the Gregor client connection object is just nil forever.

but what does calling env.getuid() tell you?

It indicates that at one point you logged in? I guess the idea would be it is better than no check at all, and would avoid this offline problem.

I still don't get it.  If the logged in check is needed, then why is this removing it?

why not just handle a network error from LoggedInLoad then?

Yeah that might be the better play here.

with this change, it seems like if I call keybase logout it will keep trying to connect to gregor (because getuid() won't be nil) which seems like what you are trying to prevent?

The problem with the existing check was that it returned false if the network was down, just like it would if you were a brand new client that had never logged in as anyone. But the difference between those two scenarios is that the second one is going to have an OnLogin event it can rely on to reestablish the gregor connection later, while the first doesn't have any events in the future to fix it. (Just the change in the network status of the host its on, which I don't think we use?)

with this change, it seems like if I call keybase logout it will keep trying to connect to gregor (because getuid() won't be nil) which seems like what you are trying to prevent?

Yes, I'd really like to fix that issue, hopefully while also fixing this PR's "starting Keybase with the network off permanently breaks the gregor connection" issue. Maybe we can hop on VC and figure out how to do it?

LoggedInLoad() with network error returned false, nil?

The commits 0c32b3b4b769...9465a12eb7da introduce visual changes on linux. :mag_right: 2 changed

Changed: Pinentry-Paper_Key_Error (before) (after)

Changed: Paper_Key-Normal (before) (after)

@patrickxb could you take another look?

5815967e9c4e1f3682ac6cb3486b25e546baa5e8


Redshift - Copy to temp table, prune table based on date, utilization of init_copy and post_copy

Added support for redshift copy to temp table, prune table (delete some amount of records based on date), init copy, post copy (also added to rdbms.py)
Also includes the rdbms.py post_copy update found in PR #1313

Can you either keep the PRs seperate or close #1313?

It would be great if you can find somebody who uses redshift in luigi to review. Thanks :)

I closed PR #1313 and will include updates here.
Luigi redshift users are quiet and unknown. Mortar Data uses some redshift functionality in their implementation of luigi, but they seem to have been inactive in the luigi community for awhile.

As rdbms.py is a common module for which is to be implemented (not executed itself), I do not see how it needs its own tests. Postgres.py and Redshift.py both implement Rdbms.py; thus, their unit tests indirectly test rdbms.py.

@dlstadther, oh ok. I didn't know that redshift inherited rdbms. If you think all code paths are tested. I'm fine with that :)

I'm currently using Luigi with Redshift, so I'll try these out when I get a chance.

+bump
(PRs are getting a little stagnate...I understand Luigi is undergoing a change in management, but the development must go on!)
Comments, questions, concerns, etc. are welcome.

@erikbern Thanks for the quick action! Greatly appreciated!

yes no problem – I'm happy to merge most stuff that goes into contrib right away :) just forgot about it
let me check if other things are pending


libhdfs3 instead of libhdfs

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes, see diff below.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): N/A
TensorFlow installed from (source or binary): N/A
TensorFlow version (use command below): N/A
Python version: N/A
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: N/A

Describe the problem
Current HDFS support in TensorFlow is based on libhdfs, a JNI wrapper for the HDFS client implemented in Java. Due to this design choice, users of libhdfs (and transitively TensorFlow)

need to keep in mind an implicit dependency on the JVM runtime,
have to do quite a bit of trickery to setup the environment expected by libhdfs.

libhdfs3 is a native implementation of an HDFS client, which could potentially free the users from the two issues mentioned above. The documentation of libhdfs3 claims that its C API is "almost the same" as that of libhdfs. I've verified this on the master version of TensorFlow and the diff is indeed negligible:
index 5f2b222622..0f168fe0dd 100644
--- a/tensorflow/core/platform/hadoop/hadoop_file_system.h
+++ b/tensorflow/core/platform/hadoop/hadoop_file_system.h
@@ -19,8 +19,8 @@ limitations under the License.
 #include "tensorflow/core/platform/env.h"

 extern "C" {
-struct hdfs_internal;
-typedef hdfs_internal* hdfsFS;
+struct HdfsFileSystemInternalWrapper;
+typedef HdfsFileSystemInternalWrapper* hdfsFS;
 }

What do you think?

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

This is strange, I've added all the necessary fields yet the label is still awaiting response.

Nagging Assignee @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@jhseu can you chime in on this?
@superbobry Please feel free to prepare a PR!

I'm happy with a configuration option. I considered using libhdfs3 with the initial implementation, but I was uncertain how much development it had left. Feel free to send a PR.

Nagging Assignees @jhseu, @cy89: It has been 19 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

FYI I'm working on a patch to support libhdfs3. The implementation is complicated by the fact that libhdfs3 is not binary compatible with libhdfs. I will submit a PR once I got a minimal working diff :)

Nagging Assignees @jhseu, @cy89: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Marking this as community support because @superbobry is working on a PR for it. Thanks!

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.


Bug for leave animations after page change on Nuxt 3

Hello,
First thing: Thank you for this awesome library, v-auto-animate is really a pleasure to use !
I encountered a bug that I dont succeed to resolve, so I created a minimal reproduction for everyone to see :
https://stackblitz.com/edit/github-vjhzhq?file=pages/test.vue
If you first go on the page /test and change the categories in the select tag, all animations are perfect.
But when you change page ("Go to homepage") and come back to the test page ("Back to test page") then all the animations for making the elements disappear are bugging, they don't act at all like before and even create a scroll bar etc...
I just identify that the top css property was different from the good to the bad animation, because on the good one the value stays at 0, but on the bad one it changes.

I Bryan, did you by any chance found a solution to this problem?


[0.80.0] apple_tv_scan unable to find AppleTV devices

Home Assistant release with the issue:
0.80.0
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
https://www.home-assistant.io/components/apple_tv/
Description of problem:
Recently installed HomeAssistant 0.80.0 and attempted to use the Apple TV component. Following the initial steps, HomeAssistant is unable to find any device using the 'apple_tv.apple_tv_scan' service. No errors found in the Home Assistant logs.
Home Sharing is enabled on the Apple TV and rebooted the Apple TV multiple times. Home Sharing works from my Apple Devices with the Apple TV. Both the Apple TV and the HomeAssistant Container are on the same (physical) network/subnet.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
  enable:
    - homekit

ios:
apple_tv:

Additional information:
Currently running tvOS12

having the same issue, how are you starting your docker container? the cmd line

I was having the same issue on 0.80.3, but it appears to be fixed in 0.81.0.
Output from home-assistant.log:
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.discovery] Found new service: apple_tv {'host': '<IP_ADDRESS>', 'port': 3689, 'hostname': 'Game-Room.local.', 'properties': {'DFID': '4', 'EiTS': '1', 'mV': '131082', 'aV': '196620', 'hG': '00000000-06b2-c289-794b-f60944fc4dcd', 'fs': '2', 'Name': 'Game Room', 'atSV': '65539', 'Ver': '131075'}, 'name': 'Game Room'}
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.discovery] Found new service: apple_tv {'host': '<IP_ADDRESS>', 'port': 3689, 'hostname': 'Living-Room.local.', 'properties': {'DFID': '3', 'EiTS': '1', 'mV': '131082', 'aV': '196620', 'hG': '00000000-06b2-c289-794b-f60944fc4dcd', 'fs': '2', 'Name': 'Living Room', 'atSV': '65539', 'Ver': '131075'}, 'name': 'Living Room'}
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded apple_tv from homeassistant.components.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setting up apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setup of domain apple_tv took 0.0 seconds.
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded remote from homeassistant.components.remote
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded media_player.apple_tv from homeassistant.components.media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setting up remote
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setup of domain remote took 0.0 seconds.
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded remote.apple_tv from homeassistant.components.remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.apple_tv entity: media_player.game_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.apple_tv entity: media_player.living_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new remote.apple_tv entity: remote.game_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new remote.apple_tv entity: remote.living_room_4

@d3vzer0 could you try on 0.81.0 and see if that fixes it?

Unfortunately still have the same issue. I have home-sharing enabled but HomeAssistant think's otherways:
2018-11-11 02:35:38 DEBUG (zeroconf-ServiceBrowser__touch-able._tcp.local.) [pyatv] Auto-discovered service LulzSec TV at <IP_ADDRESS> (no home sharing)

Thanks for the replies!
Unfortunately still have the same issue. I updated to HomeAssistant 0.82 (Docker). I have home-sharing enabled but HomeAssistant still thinks other-ways:
2018-11-11 02:35:38 DEBUG (zeroconf-ServiceBrowser__touch-able._tcp.local.) [pyatv] Auto-discovered service AppleTV at <IP_ADDRESS> (no home sharing)

I'm having a similar issue, but perhaps my specific setup might provide a few more clues. I've got two apple tvs, one an aTV4, the other an aTV4K. I have absolutely no issues with the the aTV4, but the 4K has been a consistent and baffling problem.
I can pair the 4K by disabling home sharing, rebooting, then re-enabling home sharing, as support threads on the home assistant forums have suggested, but this only lasts for a day or two at most before  home assistant loses a connection and begins spamming the logs with:
2018-11-13` 19:43:11 WARNING (MainThread) [homeassistant.components.media_player.apple_tv] A <class 'aiohttp.client_exceptions.ClientConnectorError'> error occurred: Cannot connect to host <IP_ADDRESS>:3689 ssl:None [Host is unreachable]
Just in case it's relevant, I use a Netgear Orbi as a wifi AP, and the aTV4 is wifi, while the aTV 4K is connected via ethernet to the Orbing satellite. I've tried the 4K wifi only, and it hasn't made a difference.
Running the latest hassio docker setup (0.82.0) on a generic linux server (Ubuntu bionic).


No way to set PresharedKey for L2TP VpnNativeProfile

There is no way to set the preshared key for a VpnNativeProfile, here is how I have a connection setup using just need a way to add the preshared key
var vpnProfile = new VpnNativeProfile();
vpnProfile.AlwaysOn = true;
vpnProfile.NativeProtocolType = VpnNativeProtocolType.L2tp;
vpnProfile.ProfileName = "Vpn";
vpnProfile.RequireVpnClientAppUI = true;
vpnProfile.RememberCredentials = true;
vpnProfile.RoutingPolicyType = VpnRoutingPolicyType.ForceAllTrafficOverVpn;
vpnProfile.TunnelAuthenticationMethod = VpnAuthenticationMethod.PresharedKey;
vpnProfile.UserAuthenticationMethod = VpnAuthenticationMethod.PresharedKey;
vpnProfile.Servers.Add("[vpn ip]");

var vpnMa = new VpnManagementAgent();
status = await vpnMa.AddProfileFromObjectAsync(vpnProfile);
var cred = new Windows.Security.Credentials.PasswordCredential
{
    UserName = "[username]",
    Password = "[password]"
};
var op = await vpnMa.ConnectProfileWithPasswordCredentialAsync(vpnProfile, cred);

===
Hi, @pulsegroupb2b, and thanks for filing this issue. The feedback channel you're using here (Send feedback about > This page) is for feedback about the documentation in this topic. For example, if you believe that the documentation in this topic is incorrect, or that info needed to succeed with a common scenario is missing.
For questions (or requests for help) regarding your specific scenario, like this, one option is to click Send feedback about > This product, and you'll be taken to Microsoft Q&A (more info about that below).
Here are all of the developer support resources, for completeness.

Microsoft Q&A is the right place to lobby for a change or a new feature, to make a suggestion, or to ask a product question.
For community assistance with development questions, there are our forums, and StackOverflow.
The Windows developer support site explains other support options.
The Visual Studio developer community is available, and responsive. The former User Voice feature is now there on the Suggest a feature tab, if you want to lobby for a change, a feature, or to make a suggestion.
For developer issues, or suspected product bugs, there's Microsoft Support; a support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.

I'll go ahead and close this issue now, since there's no action I can see that I can take in the documentation. You can always reply to a closed issue, or even re-open it if you feel it's been closed in error.
Thanks!
-Steve


Composer update - v1.1.22

Hi,
update to the latest version v1.1.22 is not working for me (composer update "brackets/craftable-pro" --with-all-dependencies)
I got this error when trying to update to a specific version (composer require brackets/craftable-pro "1.1.22"):

Is there documentation on which PHP packages/extensions are required?
Thanks,

It looks like sodium extension is required by laravel socialite (which is weird because it's not documented anywhere, but obviously it is). So you just need to install it.
We improve our docs and add a server requirements section with the list of all php extensions required.


Make failure handling more robust

rescue_from as a failure handling mechanism is brittle:

Only a single rescue_from block is handled, so if another block is selected, and that block re-raises, that error will be missed.
Only StandardError subclasses are caught, because ActiveJob uses rescue => e (https://github.com/rails/rails/blob/7101489293ece071013417aeed2da3aa1b0927c9/activejob/lib/active_job/execution.rb#L50), which is a shorthand for rescue StandardError => e.

Because there is no after_failure callback, we need to override perform_now, to catch any Exception and update the status. We keep the after_perfom callback because we don't want to call it if the job is retried in a retry_on block.
Fixes #8

I understand the problem, but have mixed feelings about your solution.
I see two different points in your issue:

Only StandardError subclasses are caught, because ActiveJob uses rescue => e

Take a look at https://github.com/rails/rails/search?q=rescue_with_handler&type=Code
ActionController and ActionCable are already rescuing Exception instead of StandardError, It may be worth submitting a PR to extend this behavior to ActiveJob and ActionMailer.

Only a single rescue_from block is handled, so if another block is selected, and that block re-raises, that error will be missed.

IMHO, an exception is not a failure if it's handled: it's just information.

Example: you can retry a job, with the status reinitialized to queued, and yet re-raise the exception for later inspection.
The problem with your solution is that the rescue is added after the rescue_with_handler in ActiveJob and will make the final decision despite the choices you might have made.
I'll think again but we might try using around_perform :
around_perform do
  yield
rescue Exception
  status.update(status: :failed)
  raise
end

Hi!

ActionController and ActionCable are already rescuing Exception instead of StandardError, It may be worth submitting a PR to extend this behavior to ActiveJob and ActionMailer.

Indeed, this one might be an upstream problem.
This still leaves the first (stronger) point.

IMHO, an exception is not a failure if it's handled: it's just information.

It may sound weird, but I completely agree! The problem is that activejob-status is (ab)using this mechanism to simply get notified of when an exception happens, but it doesn't really want to handle the exception! Because only a single rescue_from will ever be executed, it means only a single such listener will ever be executed. As a matter of fact, I discovered this bug because we actually added another such handler to our app:
rescue_from Exception do |e|
  ErrorPlatform.notify(e) # Log it to the exception monitor
  raise e
end

Turns  out this doesn't work, because ActiveJob::Status will never be notified about the errors I raised in the rescue_from handlers, or my handler will never be called because ActiveJob::Status got called first (this depends on the order of rescue_from additions). The only correct solution is to stack all the handlers.

I'll think again but we might try using around_perform

I tried that, but it's no good either, because that would catch the error before the rescue_from handlers.

Rails is now allowing jobs to rescue all exceptions  - https://github.com/rails/rails/pull/41214
The README has been updated : https://github.com/inkstak/activejob-status#activejobstatus-and-exceptions


Version upgrade warning like pip?

WARNING: You are using pip version 21.1.2; however, version 21.1.3 is available.
You should consider upgrading via the 'C:\Users\micro\AppData\Local\Programs\Python\Python39\python.exe -m pip install --upgrade pip' command.

We similarly could check for the newest version in Use.__init__ and warn the user whenever a new version is available, although we'll need a new class of Warning so users can filter it and/or we could add a config setting to disable the warning.

@amogorkon The version of justuse?

yeah


"onDeath" trigger

I was looking at MTG rules and they have a game style called Commander, where a Hero card is chosen as a Commander, and when it is eliminated from play, it returns to a "command zone" where it can be cast again. This would be more or less equivalent to returning to your hand, for all intents and purposes.
It could probably use a better name, but either way I'd like to be able to do something like this:
        {
            name: "Commander",
            creature: "Bio",
            manaCost: 8,
            health: 6,
            attack: 6,
            onDeath: {
                summon: {
                    count: 1,
                    card: "Commander",
                    where: "Hand",
                    who: "owner"
                }
            }
        }

I'm sure there are tons of other creative ways we could use that trigger as well.

Yes, this is especially a common trigger in HS, where it is called "Deathrattle". Definitely something we should support.

Syntax:
onDeath {
    heal 1 to 'you'
}

onDeath {
    summon 3 of 'Cheating shot' to 'owner' zone 'Deck'
}


Issue with github_branch_protection and github_repository_collaborator on first run

Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Terraform v0.12.19
Affected Resource(s)
Please list the resources as a list, for example:

github_branch_protection
github_repository_collaborator
I have used both 2.7.0 and 2.8 versions for the github provider

Terraform Configuration Files
resource "github_repository" "build_repo" {
  name          = {repo_name}
  private       = true

 #auto_init     = true
  template {
    owner       = {user_owner}
    repository  = {template_repo_name}
  }
}

resource "github_branch_protection" "master" {
  repository     =  {repo_name}  #"${github_repository.example.name}"
  branch         = "master"

  required_pull_request_reviews {
    dismiss_stale_reviews               = true
    required_approving_review_count     = 1
  }
}

resource "github_repository_collaborator" "add_collaborator" {
  repository = {repo_name}
  username   = {user_collaborator}
  permission = "maintain"
}

Expected Behavior
Create repo from template (tried auto_init) as well. Protect master branch and add collaborator successfully on first run
github_repository_collaborator.add_collaborator: Creation complete after 5s [id={repo_name}:{user_collaborator}]
github_branch_protection.master: Creation complete after 5s [id={repo_name}:master]

Actual Behavior
What actually happened?
github_repository_collaborator.add_collaborator: Creating...
github_branch_protection.master: Creating...
github_repository.build_repo: Creating...
github_repository.build_repo: Creation complete after 5s [id={repo_name}]

Error: PUT https://ghe.../api/v3/repos/{repo_name}/branches/master/protection: 404 Not Found []

  on main.tf line 20, in resource "github_branch_protection" "master":
  20: resource "github_branch_protection" "master" {

Error: PUT https://ghe.../api/v3/repos/{repo_name}/collaborators/{user_collaborator}: 404 Not Found []

  on main.tf line 30, in resource "github_repository_collaborator" "add_collaborator":
  30: resource "github_repository_collaborator" "add_collaborator" {

Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

Make sure repo does not already exist. Purpose of script is to build new repo with configs
terraform apply

Important Factoids
I am trying to build a repo with all these resources configuring items like branch protection and adding collaborators. The repo is created successfully. Using api v3 and only the two mentioned resources are not working on initial run, HOWEVER, on second run it is successful.
Using in GHE

Utilizing the right dependencies solved this issue


segfault in perform_dma  on dma branch

When running the legion version of pennant on a single node with the general runtime (Gasnet udp) I'm getting a segmentation fault:
LegionRuntime::LowLevel::CopyRequest::perform_dma(this=0x00007fdfc846a780) + 1650 at lowlevel_dma.cc:3542

When the application starts up I get a warning (reservation cannot be satisfied):
Pinned Memory Usage: GASNET=256, RMEM=0, LMB=2, SDP=64, total=322
[0 - 7fff7c222300] {4}{threads}: reservation ('EndpointManager workers') cannot be satisfied
********************
Running PENNANT v0.6
********************

Running Legion on 1 piece(s)
--- Mesh Information ---
Points:  61
Zones:  40
Sides:  158
Side chunks:  10
Point chunks:  4
Zone chunks:  3
Chunk size:  16
------------------------
Connection to localhost closed by remote host.

A backtrace of the offending thread reveals:
* thread #4: tid = 0x35ad11, 0x0000000103e3aae2 pennant`LegionRuntime::LowLevel::CopyRequest::perform_dma(this=0x00007fdfc846a780) + 1650 at lowlevel_dma.cc:3542, stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
  * frame #0: 0x0000000103e3aae2 pennant`LegionRuntime::LowLevel::CopyRequest::perform_dma(this=0x00007fdfc846a780) + 1650 at lowlevel_dma.cc:3542
    frame #1: 0x0000000103e343ad pennant`LegionRuntime::LowLevel::CopyRequest::check_readiness(this=0x00007fdfc846a780, just_check=false, rq=0x0000000000000000) + 2637 at lowlevel_dma.cc:623
    frame #2: 0x0000000103e43735 pennant`Realm::Domain::copy(this=0x00007fdfc8455c0c, srcs=0x0000000125b1e0e0, dsts=0x0000000125b1e0c8, requests=0x0000000125b1dcf8, wait_on=(id = 0, gen = 0), redop_id=0, red_fold=false) const + 8421 at lowlevel_dma.cc:5265
    frame #3: 0x0000000103e415fa pennant`Realm::Domain::copy(this=0x00007fdfc8455c0c, srcs=0x0000000125b1e0e0, dsts=0x0000000125b1e0c8, wait_on=(id = 0, gen = 0), redop_id=0, red_fold=false) const + 122 at lowlevel_dma.cc:5126
    frame #4: 0x0000000103ac46f6 pennant`LegionRuntime::HighLevel::RegionTreeForest::issue_copy(this=0x00007fdfc8600220, dom=0x00007fdfc8455c0c, op=0x00007fdfc8852188, src_fields=0x0000000125b1e0e0, dst_fields=0x0000000125b1e0c8, precondition=(id = 0, gen = 0)) + 262 at region_tree.cc:3823
    frame #5: 0x0000000103b31148 pennant`LegionRuntime::HighLevel::RegionTreeNode::issue_grouped_copies(context=0x00007fdfc8600220, info=0x0000000125b205a0, dst=0x00007fdfc84691e0, preconditions=0x0000000125b1ee78, update_mask=0x0000000125b1ee00, copy_domains_precondition=(id = 0, gen = 0), copy_domains=0x0000000125b1ed98, src_instances=0x0000000125b1eeb8, src_version_info=0x00007fdfc98b2170, postconditions=0x0000000125b1edc0, tracker=0x0000000000000000) + 4728 at region_tree.cc:13234
    frame #6: 0x0000000103b1f504 pennant`LegionRuntime::HighLevel::RegionTreeNode::issue_update_copies(this=0x00007fdfc9858ea0, info=0x0000000125b205a0, dst=0x00007fdfc84691e0, copy_mask=<unavailable>, valid_instances=0x0000000125b20268, tracker=0x0000000000000000) + 7316 at region_tree.cc:12923
    frame #7: 0x0000000103abaef7 pennant`LegionRuntime::HighLevel::RegionNode::register_region(this=0x00007fdfc9858ea0, info=0x0000000125b205a0, term_event=(id = 536871037, gen = 9), usage=0x0000000125b20580, user_mask=0x0000000125b20640, view=0x00007fdfc84691e0, needed_fields=0x00007fdfc8468d40) + 871 at region_tree.cc:15083
    frame #8: 0x0000000103aba6da pennant`LegionRuntime::HighLevel::RegionTreeForest::register_physical_region(this=0x00007fdfc8600220, ctx=(ctx = 0), ref=0x00007fdfc8468d20, req=0x00007fdfc8852800, index=0, version_info=0x00007fdfc98b2170, op=0x00007fdfc8852188, local_proc=(id =<PHONE_NUMBER>), term_event=(id = 536871037, gen = 9), log_name=0x00007fdfc8405320, uid=118) + 826 at region_tree.cc:1976
    frame #9: 0x000000010383cc93 pennant`LegionRuntime::HighLevel::SingleTask::map_all_regions(this=0x00007fdfc8852000, target=(id =<PHONE_NUMBER>), user_event=(id = 536871037, gen = 9), mapper_invoked=false) + 11091 at legion_tasks.cc:4580
    frame #10: 0x0000000103858688 pennant`LegionRuntime::HighLevel::PointTask::perform_mapping(this=0x00007fdfc8852000, mapper_invoked=false) + 120 at legion_tasks.cc:7590
    frame #11: 0x000000010386cd3c pennant`LegionRuntime::HighLevel::SliceTask::map_and_launch(this=0x00007fdfca826c00) + 1452 at legion_tasks.cc:10338
    frame #12: 0x000000010384be98 pennant`LegionRuntime::HighLevel::MultiTask::trigger_execution(this=0x00007fdfca826c00) + 632 at legion_tasks.cc:5992
    frame #13: 0x0000000103870d9b pennant`LegionRuntime::HighLevel::DeferredSlicer::perform_slice(this=0x000000012521d890, slice=0x00007fdfca826c00) + 75 at legion_tasks.cc:11087
    frame #14: 0x0000000103870f69 pennant`LegionRuntime::HighLevel::DeferredSlicer::handle_slice(args=0x00007fdfc8467c60) + 41 at legion_tasks.cc:11099
    frame #15: 0x0000000103c7b1d3 pennant`LegionRuntime::HighLevel::Internal::high_level_runtime_task(args=0x00007fdfc8467c60, arglen=20, userdata=0x0000000000000000, userlen=0, p=(id =<PHONE_NUMBER>)) + 1347 at runtime.cc:16797
    frame #16: 0x0000000103f00adb pennant`Realm::LocalTaskProcessor::execute_task(this=0x00007fdfc8407ac0, func_id=4, task_args=0x00007fdfc8467eb0) + 1707 at proc_impl.cc:719
    frame #17: 0x0000000103ebd424 pennant`Realm::Task::execute_on_processor(this=0x00007fdfc8467df0, p=(id =<PHONE_NUMBER>)) + 228 at tasks.cc:108
    frame #18: 0x0000000103ec2379 pennant`Realm::UserThreadTaskScheduler::execute_task(this=0x00007fdfc8407c00, task=0x00007fdfc8467df0) + 41 at tasks.cc:939
    frame #19: 0x0000000103ebf380 pennant`Realm::ThreadedTaskScheduler::scheduler_loop(this=0x00007fdfc8407c00) + 1840 at tasks.cc:492
    frame #20: 0x0000000103ec555e pennant`void Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &(obj=0x00007fdfc8407c00))>(void*) + 94 at threads.inl:127
    frame #21: 0x0000000103ea11e7 pennant`Realm::UserThread::uthread_entry() + 359 at threads.cc:747
    frame #22: 0x00007fff96c8e35b libsystem_platform.dylib`_ctx_start + 11

The warning message indicates that the Legion runtime has allocated more threads than allowed; it is not suggested but shouldn't lead to segment fault. Are you running with the most up-to-date dma code? It seems a little bit weird to me that the dma thread crashed when doing logging. Is there any possibility for me to reproduce the failure case?

I am running on eadf87d07a2f4fbdec6a1a410253cacb50ce52f4
I just tested this again and I get the same failure when running on a single node.
You can reproduce by using the pennant-legion example located here:
https://github.com/gshipman/pennant-legion
The latest failure is:
pennant: /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:2951: void LegionRuntime::LowLevel::CopyRequest::perform_new_dma(LegionRuntime::LowLevel::Memory, LegionRuntime::LowLevel::Memory) [with unsigned int DIM = 0u; LegionRuntime::LowLevel::Memory = Realm::Memory]: Assertion `ispace->me == get_runtime()->get_instance_impl(dst_inst)->metadata.is' failed.

Here is the backtrace of the offending thread:
[0] Thread 10 (Thread 0x7fe8e3c44700 (LWP 36742)):
[0] #0  0x00007fe8e1cc50a7 in sched_yield () from /usr/lib64/libc.so.6
[0] #1  0x000000000101a420 in gasneti_system_redirected_coprocess ()
[0] #2  0x000000000101acf5 in gasneti_print_backtrace ()
[0] #3  0x000000000108540d in gasneti_defaultSignalHandler ()
[0] #4  <signal handler called>
[0] #5  0x00007fe8e1c1f5f7 in raise () from /usr/lib64/libc.so.6
[0] #6  0x00007fe8e1c20ce8 in abort () from /usr/lib64/libc.so.6
[0] #7  0x00007fe8e1c18566 in __assert_fail_base () from /usr/lib64/libc.so.6
[0] #8  0x00007fe8e1c18612 in __assert_fail () from /usr/lib64/libc.so.6
[0] #9  0x0000000000f2cd3b in LegionRuntime::LowLevel::CopyRequest::perform_new_dma<0u> (this=0x7fe8a5454b10, src_mem=..., dst_mem=...) at /home/gshipman/local/src/legion/runtime/lowl
evel_dma.cc:2951
[0] #10 0x0000000000f1c82f in LegionRuntime::LowLevel::CopyRequest::perform_dma (this=0x7fe8a5454b10) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:3482
[0] #11 0x0000000000f19e77 in LegionRuntime::LowLevel::CopyRequest::check_readiness (this=0x7fe8a5454b10, just_check=false, rq=0x0) at /home/gshipman/local/src/legion/runtime/lowlevel
_dma.cc:613
[0] #12 0x0000000000f2127f in Realm::Domain::copy (this=0x7fe8a54163f0, srcs=std::vector of length 1, capacity 1 = {...}, dsts=std::vector of length 1, capacity 1 = {...}, requests=..
., wait_on=..., redop_id=0, red_fold=false) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:5206
[0] #13 0x0000000000f208b2 in Realm::Domain::copy (this=0x7fe8a54163f0, srcs=std::vector of length 1, capacity 1 = {...}, dsts=std::vector of length 1, capacity 1 = {...}, wait_on=...
, redop_id=0, red_fold=false) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:5067
[0] #14 0x0000000000d7eae0 in LegionRuntime::HighLevel::RegionTreeForest::issue_copy (this=0x2a61ab0, dom=..., op=0x7fe8dee88d00, src_fields=std::vector of length 1, capacity 1 = {...
}, dst_fields=std::vector of length 1, capacity 1 = {...}, precondition=...) at /home/gshipman/local/src/legion/runtime/legion/region_tree.cc:3862
[0] #15 0x0000000000da5cea in LegionRuntime::HighLevel::RegionTreeNode::issue_grouped_copies (context=0x2a61ab0, info=..., dst=0x7fe8a54512c0, preconditions=std::map with 0 elements,
update_mask=..., copy_domains_precondition=..., copy_domains=std::set with 1 elements, src_instances=std::map with 1 elements, src_version_info=..., postconditions=std::map with 0 ele
ments, tracker=0x0) at /home/gshipman/local/src/legion/runtime/legion/region_tree.cc:13398
[0] #16 0x0000000000ce64ee in LegionRuntime::HighLevel::CompositeNode::issue_update_copies (this=0x7fe8a5648d60, info=..., dst=0x7fe8a54512c0, traversal_mask=..., copy_mask=..., preco
nds=std::map with 0 elements, postconditions=std::map with 0 elements, tracker=0x0) at /home/gshipman/local/src/legion/runtime/legion/legion_views.cc:4476
[0] #17 0x0000000000ce4318 in LegionRuntime::HighLevel::CompositeView::issue_deferred_copies (this=0x7fe8a5453f80, info=..., dst=0x7fe8a54512c0, copy_mask=..., tracker=0x0) at /home/g
shipman/local/src/legion/runtime/legion/legion_views.cc:3952
[0] #18 0x0000000000da455b in LegionRuntime::HighLevel::RegionTreeNode::issue_update_copies (this=0x2c115a0, info=..., dst=0x7fe8a54512c0, copy_mask=..., valid_instances=std::map with
 1 elements, tracker=0x0) at /home/gshipman/local/src/legion/runtime/legion/region_tree.cc:13124
[0] #19 0x0000000000dab873 in LegionRuntime::HighLevel::RegionNode::register_region (this=0x2c115a0, info=..., term_event=..., usage=..., user_mask=..., view=0x7fe8a54512c0, needed_fi
elds=...) at /home/gshipman/local/src/legion/runtime/legion/region_tree.cc:15203
[0] #20 0x0000000000d76cab in LegionRuntime::HighLevel::RegionTreeForest::register_physical_region (this=0x2a61ab0, ctx=..., ref=..., req=..., index=2, version_info=..., op=0x7fe8dee8
8d00, local_proc=..., term_event=..., log_name=0x2899a00 "calcedgelen", uid=274) at /home/gshipman/local/src/legion/runtime/legion/region_tree.cc:1986
[0] #21 0x0000000000c5bf57 in LegionRuntime::HighLevel::SingleTask::map_all_regions (this=0x7fe8dee88b60, target=..., user_event=..., mapper_invoked=false) at /home/gshipman/local/src
/legion/runtime/legion/legion_tasks.cc:4604
[0] #22 0x0000000000c66d97 in LegionRuntime::HighLevel::PointTask::perform_mapping (this=0x7fe8dee88b60, mapper_invoked=false) at /home/gshipman/local/src/legion/runtime/legion/legion
_tasks.cc:7495
[0] #23 0x0000000000c702b7 in LegionRuntime::HighLevel::SliceTask::map_and_launch (this=0x2c103d0) at /home/gshipman/local/src/legion/runtime/legion/legion_tasks.cc:10206
[0] #24 0x0000000000c61112 in LegionRuntime::HighLevel::MultiTask::trigger_execution (this=0x2c103d0) at /home/gshipman/local/src/legion/runtime/legion/legion_tasks.cc:5907
[0] #25 0x0000000000c72a4c in LegionRuntime::HighLevel::DeferredSlicer::perform_slice (this=0x7fe8a5be9190, slice=0x2c103d0) at /home/gshipman/local/src/legion/runtime/legion/legion_t
asks.cc:10918
[0] #26 0x0000000000c72aeb in LegionRuntime::HighLevel::DeferredSlicer::handle_slice (args=0x7fe8dee4c0a0) at /home/gshipman/local/src/legion/runtime/legion/legion_tasks.cc:10930
[0] #27 0x0000000000e3e7b8 in LegionRuntime::HighLevel::Internal::high_level_runtime_task (args=0x7fe8dee4c0a0, arglen=20, userdata=0x0, userlen=0, p=...) at /home/gshipman/local/src/
legion/runtime/legion/runtime.cc:17758
[0] #28 0x0000000000f93824 in Realm::LocalTaskProcessor::execute_task (this=0x2a45e00, func_id=4, task_args=...) at /home/gshipman/local/src/legion/runtime/realm/proc_impl.cc:795
[0] #29 0x0000000000f6b8fe in Realm::Task::execute_on_processor (this=0x7fe8a56ad230, p=...) at /home/gshipman/local/src/legion/runtime/realm/tasks.cc:108
[0] #30 0x0000000000f6e1a8 in Realm::UserThreadTaskScheduler::execute_task (this=0x2a46160, task=0x7fe8a56ad230) at /home/gshipman/local/src/legion/runtime/realm/tasks.cc:939
[0] #31 0x0000000000f6c874 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x2a46160) at /home/gshipman/local/src/legion/runtime/realm/tasks.cc:492
[0] #32 0x0000000000f7213c in Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &Realm::ThreadedTaskScheduler::scheduler_loop> (obj=0x2a46160) at /home/gshipman/local/
src/legion/runtime/realm/threads.inl:127
[0] #33 0x0000000000f56af1 in Realm::UserThread::uthread_entry () at /home/gshipman/local/src/legion/runtime/realm/threads.cc:747
[0] #34 0x00007fe8e1c31110 in ?? () from /usr/lib64/libc.so.6
[0] #35 0x0000000000000000 in ?? ()

If I run on more than one node (change -n in run-darwin.sh), I get the following failure:
pennant: /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:2885: void LegionRuntime::LowLevel::find_shortest_path(LegionRuntime::LowLevel::Memory, LegionRuntime::LowLevel::Memor
y, std::vector<Realm::Memory>&): Assertion `dist.find(dst_mem) != dist.end()' failed.

Here is the backtrace of the offending thread:
0] Thread 11 (Thread 0x7fea9835b700 (LWP 36808)):
[0] #0  0x00007fead8c980a7 in sched_yield () from /usr/lib64/libc.so.6
[0] #1  0x000000000101a420 in gasneti_system_redirected_coprocess ()
[0] #2  0x000000000101acf5 in gasneti_print_backtrace ()
[0] #3  0x000000000108540d in gasneti_defaultSignalHandler ()
[0] #4  <signal handler called>
[0] #5  0x00007fead8bf25f7 in raise () from /usr/lib64/libc.so.6
[0] #6  0x00007fead8bf3ce8 in abort () from /usr/lib64/libc.so.6
[0] #7  0x00007fead8beb566 in __assert_fail_base () from /usr/lib64/libc.so.6
[0] #8  0x00007fead8beb612 in __assert_fail () from /usr/lib64/libc.so.6
[0] #9  0x0000000000f1c5d8 in LegionRuntime::LowLevel::find_shortest_path (src_mem=..., dst_mem=..., path=std::vector of length 0, capacity 0) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:2885
[0] #10 0x0000000000f2c6c7 in LegionRuntime::LowLevel::CopyRequest::perform_new_dma<0u> (this=0x7fea95270fe0, src_mem=..., dst_mem=...) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:2894
[0] #11 0x0000000000f1c82f in LegionRuntime::LowLevel::CopyRequest::perform_dma (this=0x7fea95270fe0) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:3482
[0] #12 0x0000000000f19e77 in LegionRuntime::LowLevel::CopyRequest::check_readiness (this=0x7fea95270fe0, just_check=false, rq=0x0) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:613
[0] #13 0x0000000000f197ab in LegionRuntime::LowLevel::DmaRequest::Waiter::event_triggered (this=0x7fea95271188) at /home/gshipman/local/src/legion/runtime/lowlevel_dma.cc:501
[0] #14 0x0000000000f80bf7 in Realm::GenEventImpl::trigger (this=0x7fea978e1120, gen_triggered=2, trigger_node=0, wait_on=...) at /home/gshipman/local/src/legion/runtime/realm/event_impl.cc:903
[0] #15 0x0000000000f8084f in Realm::GenEventImpl::trigger_current (this=0x7fea978e1120) at /home/gshipman/local/src/legion/runtime/realm/event_impl.cc:817
[0] #16 0x0000000000f7d6d1 in Realm::MetadataBase::handle_response (this=0x7fea952824d8) at /home/gshipman/local/src/legion/runtime/realm/metadata.cc:80
[0] #17 0x0000000000f7dd19 in Realm::MetadataResponseMessage::handle_request (args=..., data=0x7feaccfe4280, datalen=204) at /home/gshipman/local/src/legion/runtime/realm/metadata.cc:279
[0] #18 0x0000000000f1140b in IncomingMediumMessage<Realm::MetadataResponseMessage::RequestArgs, 172, &Realm::MetadataResponseMessage::handle_request, 6>::run_handler (this=0x7fea95252ab0) at /home/gshipman/local/src/legion/runtime/activemsg.h:372
[0] #19 0x0000000000fdc34b in IncomingMessageManager::handler_thread_loop (this=0x1f6e020) at /home/gshipman/local/src/legion/runtime/activemsg.cc:770
[0] #20 0x0000000000fe49d8 in Realm::Thread::thread_entry_wrapper<IncomingMessageManager, &IncomingMessageManager::handler_thread_loop> (obj=0x1f6e020) at /home/gshipman/local/src/legion/runtime/realm/threads.inl:127
[0] #21 0x0000000000f55f65 in Realm::KernelThread::pthread_entry (data=0x1f6e210) at /home/gshipman/local/src/legion/runtime/realm/threads.cc:562
[0] #22 0x00007feada7cbdc5 in start_thread () from /usr/lib64/libpthread.so.0
[0] #23 0x00007fead8cb321d in clone () from /usr/lib64/libc.so.6

Galen,
Does the single-node failure occur when using the master branch, or just the dma branch?

Just the dma branch. I can also get the multi-node version to run using master if I map tasks locally.

I have pushed implementation for unstructured data into dma branch. @gshipman Could you please pull and try how it works?


Puppeteer does no install chrome when using wendigo docker

It works just by removing the env that disables the automatic download:
wendigo-test.zip


Votes are tracked for nick changes

Also includes some casefolding for voting thanks to Dan.

Thank you for your contributions :)


Debug logging helpers?

I heard that you're interested in providing some debug logs to users, and you're primarily doing this based on the results of the userspace commands you run. That's helpful for systems things, but not so much for network things. Fortunately, there's a nice way you can get debug logs for networking things: ifconfig wg0 debug. Once you do this, dmesg will spit out messages prefixed with "wireguard: ", which you should be able to collect. You can turn it back off with ifconfig wg0 -debug.

Thanks for the tip, I will look into this!


[Scheduled Maintenance] Nodes to be updated due to high severity vulnerability

I hate converting times to ISO

[Note]
As a side effect of the node downtime all servers on the server panel will be uncontrollable. The servers already running will stay running.

[Update]
Maintenance has begun

[Completed]


Add missing description_hash argument that is required for Lightning Address

I'm not sure if this is the same as #76 or not, but I'm trying to implement Lightning Address (allowing users to connect to their own nodes: MyNode, Umbrel, etc.) and it looks like LNbits is not including the description_hash in the raw data when generating an invoice.
As per the LNurl-pay spec:

pr must have the h tag (description_hash) set to sha256(utf8ByteArray(metadata)).
https://github.com/fiatjaf/lnurl-rfc/blob/legacy/lnurl-pay.md

Is it possible to add this into the data?
Is this a bigger issue, where it depends on the underlying lightning implementation?

have you tested it this merge solved your issue?