R200 and ZR300 not working properly on new librealsense version

Required Info

Camera Model
R200 / ZR300

Firmware Version
<IP_ADDRESS> / <IP_ADDRESS>

Operating System & Version
Ubuntu 16.04.3 LTS

Kernel Version (Linux Only)
4.10.0-35-Generic

I run in some trouble with the Intel RealSense R200 two weeks ago (the same problem came up for the ZR300 and another R200).
The R200 had the FW/V <IP_ADDRESS>.
The problem is that the two R200s and the ZR300 do not work in any way, neither with the librealsense library and demos nor with any other tools on Ubuntu like cheese, q4l2 and v4l2.
But I got always device information by lsusb -D /dev/bus/usb/...:
Device: ID 8086:0a80 Intel Corp.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2 ?
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0         9
  idVendor           0x8086 Intel Corp.
  idProduct          0x0a80
  bcdDevice           14.8a
  iManufacturer           1 Intel Corp
  iProduct                2 Intel RealSense 3D Camera R200
  iSerial                 3 SN_2521001926
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength         1677
    bNumInterfaces          6
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              126mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass         14 Video
      bFunctionSubClass       3 Video Interface Collection
      bFunctionProtocol       0
      iFunction               4 Intel(R) RealSense(TM) 3D Camera (R200) Left-Right
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        14 Video
      bInterfaceSubClass      1 Video Control
      bInterfaceProtocol      0
      iInterface              4 Intel(R) RealSense(TM) 3D Camera (R200) Left-Right
      VideoControl Interface Descriptor:
        bLength                13
        bDescriptorType        36
        bDescriptorSubtype      1 (HEADER)
        bcdUVC               1.10
        wTotalLength           68
        dwClockFrequency       48.000000MHz
        bInCollection           1
        baInterfaceNr( 0)       1
      VideoControl Interface Descriptor:
        bLength                18
        bDescriptorType        36
        bDescriptorSubtype      2 (INPUT_TERMINAL)
        bTerminalID             1
        wTerminalType      0x0201 Camera Sensor
        bAssocTerminal          0
        iTerminal               0
        wObjectiveFocalLengthMin      0
        wObjectiveFocalLengthMax      0
        wOcularFocalLength            0
        bControlSize                  3
        bmControls           0x00000000
      VideoControl Interface Descriptor:
        bLength                28
        bDescriptorType        36
        bDescriptorSubtype      6 (EXTENSION_UNIT)
        bUnitID                 2
        guidExtensionCode         {342d6818-2cdd-7340-ad23-7214739a074c}
        bNumControl            21
        bNrPins                 1
        baSourceID( 0)          1
        bControlSize            3
        bmControls( 0)       0xfd
        bmControls( 1)       0xfb
        bmControls( 2)       0x7f
        iExtension              0
      VideoControl Interface Descriptor:
        bLength                 9
        bDescriptorType        36
        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
        bTerminalID             3
        wTerminalType      0x0101 USB Streaming
        bAssocTerminal          0
        bSourceID               2
        iTerminal               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass        14 Video
      bInterfaceSubClass      2 Video Streaming
      bInterfaceProtocol      0
      iInterface              4 Intel(R) RealSense(TM) 3D Camera (R200) Left-Right
      [...]
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         2
      bInterfaceCount         2
      bFunctionClass         14 Video
      bFunctionSubClass       3 Video Interface Collection
      bFunctionProtocol       0
      iFunction               5 Intel(R) RealSense(TM) 3D Camera (R200) Depth
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass        14 Video
      bInterfaceSubClass      1 Video Control
      bInterfaceProtocol      0
      iInterface              5 Intel(R) RealSense(TM) 3D Camera (R200) Depth
      VideoControl Interface Descriptor:
        bLength                13
        bDescriptorType        36
        bDescriptorSubtype      1 (HEADER)
        bcdUVC               1.10
        wTotalLength           40
        dwClockFrequency       48.000000MHz
        bInCollection           1
        baInterfaceNr( 0)       3
      VideoControl Interface Descriptor:
        bLength                18
        bDescriptorType        36
        bDescriptorSubtype      2 (INPUT_TERMINAL)
        bTerminalID             4
        wTerminalType      0x0201 Camera Sensor
        bAssocTerminal          0
        iTerminal               0
        wObjectiveFocalLengthMin      0
        wObjectiveFocalLengthMax      0
        wOcularFocalLength            0
        bControlSize                  3
        bmControls           0x00000000
      VideoControl Interface Descriptor:
        bLength                 9
        bDescriptorType        36
        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
        bTerminalID             5
        wTerminalType      0x0101 USB Streaming
        bAssocTerminal          0
        bSourceID               4
        iTerminal               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               8
        bMaxBurst               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass        14 Video
      bInterfaceSubClass      2 Video Streaming
      bInterfaceProtocol      0
      iInterface              5 Intel(R) RealSense(TM) 3D Camera (R200) Depth
      [...]
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         4
      bInterfaceCount         2
      bFunctionClass         14 Video
      bFunctionSubClass       3 Video Interface Collection
      bFunctionProtocol       0
      iFunction               6 Intel(R) RealSense(TM) 3D Camera (R200) RGB
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass        14 Video
      bInterfaceSubClass      1 Video Control
      bInterfaceProtocol      0
      iInterface              6 Intel(R) RealSense(TM) 3D Camera (R200) RGB
      VideoControl Interface Descriptor:
        bLength                13
        bDescriptorType        36
        bDescriptorSubtype      1 (HEADER)
        bcdUVC               1.10
        wTotalLength           53
        dwClockFrequency       48.000000MHz
        bInCollection           1
        baInterfaceNr( 0)       5
      VideoControl Interface Descriptor:
        bLength                18
        bDescriptorType        36
        bDescriptorSubtype      2 (INPUT_TERMINAL)
        bTerminalID             6
        wTerminalType      0x0201 Camera Sensor
        bAssocTerminal          0
        iTerminal               0
        wObjectiveFocalLengthMin      0
        wObjectiveFocalLengthMax      0
        wOcularFocalLength            0
        bControlSize                  3
        bmControls           0x0000000a
          Auto-Exposure Mode
          Exposure Time (Absolute)
      VideoControl Interface Descriptor:
        bLength                13
        bDescriptorType        36
        bDescriptorSubtype      5 (PROCESSING_UNIT)
        bUnitID                 7
        bSourceID               6
        wMaxMultiplier      16384
        bControlSize            3
        bmControls     0x0000177f
          Brightness
          Contrast
          Hue
          Saturation
          Sharpness
          Gamma
          White Balance Temperature
          Backlight Compensation
          Gain
          Power Line Frequency
          White Balance Temperature, Auto
        iProcessing             0
        bmVideoStandards     0x 0
      VideoControl Interface Descriptor:
        bLength                 9
        bDescriptorType        36
        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
        bTerminalID             8
        wTerminalType      0x0101 USB Streaming
        bAssocTerminal          0
        bSourceID               7
        iTerminal               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               8
        bMaxBurst               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass        14 Video
      bInterfaceSubClass      2 Video Streaming
      bInterfaceProtocol      0
      iInterface              6 Intel(R) RealSense(TM) 3D Camera (R200) RGB
     [...]
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
        ** UNRECOGNIZED:  20 ff 42 49 53 54 00 01 04 07 02 00 00 00 00 00 01 08 e8 03 02 09 e8 03 03 0a e8 03 04 0b 4c 04
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength           22
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000002
      Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x02
      Latency Tolerance Messages (LTM) Supported
    wSpeedsSupported   0x0008
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   3
      Lowest fully-functional device speed is SuperSpeed (5Gbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
Device Status:     0x0010
  (Bus Powered)
  Latency Tolerance Messaging (LTM) Enabled

The problem appears when I simply install ros-kinetic-realsense_camera on a fresh Ubuntu machine, which worked fine until.
I solved it in the end with a firmware update.
After this, I tried to compile/install the library librealsense from source, in several versions.
The librealsense versions v1.11.0 up to v1.12.1 compiled and build with catkin_make/cmake without any trouble and then I compiled and build the realsense-repository against the different versions and tested older versions.
Sadly, I forgot to try older versions of librealsense and realsense-repo with the R200 and old FW/V...
Maybe anyone else could try this..
However, before and after the FW update, I got the dmesg output:
[10373.509785] usb 2-3: new SuperSpeed USB device number 8 using xhci_hcd
[10373.532478] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[10373.532482] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10373.532484] usb 2-3: Product: Intel RealSense 3D Camera R200
[10373.532486] usb 2-3: Manufacturer: Intel Corp
[10373.532487] usb 2-3: SerialNumber: SN_2521001926
[10373.536198] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[10373.539915] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[10373.539919] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[10373.540538] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[10373.544954] uvcvideo: Unable to create debugfs 2-8 directory.
[10373.545072] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[10373.545319] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input20
[10373.546769] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[10373.550442] uvcvideo: Unable to create debugfs 2-8 directory.
[10373.550553] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[10373.550557] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[10373.550714] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input21
[10378.408970] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.459518] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.509925] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.560402] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.610916] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.661352] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.711823] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.762679] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.813048] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.863535] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.914022] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10378.964413] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10379.014811] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[10379.065230] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).

The failed to query part appears when I call roslaunch realsense_camera r200_nodelet_default.launch.
The other sample node roslaunch realsense_camera r200_nodelet_rgbd.launch crashes instantly and dmesg shows the same log.
`roslaunch realsense_camera r200_nodelet_rgbd.launch `
... logging to /home/[user]/.ros/log/2c59263c-a435-11e7-8e97-d481d7480b42/roslaunch-[user]-[pc]-5480-31240.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.

Traceback (most recent call last):
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/__init__.py", line 307, in main
    p.start()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 268, in start
    self._start_infrastructure()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 217, in _start_infrastructure
    self._load_config()
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 132, in _load_config
    roslaunch_strs=self.roslaunch_strs, verbose=self.verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/config.py", line 451, in load_config_default
    loader.load(f, config, verbose=verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 746, in load
    self._load_launch(launch, ros_config, is_core=core, filename=filename, argv=argv, verbose=verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 718, in _load_launch
    self._recurse_load(ros_config, launch.childNodes, self.root_context, None, is_core, verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 652, in _recurse_load
    default_machine, is_core, verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 682, in _recurse_load
    val = self._include_tag(tag, context, ros_config, default_machine, is_core, verbose)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 95, in call
    return f(*args, **kwds)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 587, in _include_tag
    inc_filename = self.resolve_args(tag.attributes['file'].value, context)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 183, in resolve_args
    return substitution_args.resolve_args(args, context=context.resolve_dict, resolve_anon=self.resolve_anon)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 370, in resolve_args
    resolved = _resolve_args(resolved, context, resolve_anon, commands)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 383, in _resolve_args
    resolved = commands[command](resolved, a, args, context)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 151, in _find
    source_path_to_packages=source_path_to_packages)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 197, in _find_executable
    full_path = _get_executable_path(rp.get_path(args[0]), path)
  File "/usr/lib/python2.7/dist-packages/rospkg/rospack.py", line 203, in get_path
    raise ResourceNotFound(name, ros_paths=self._ros_paths)
ResourceNotFound: rgbd_launch
ROS path [0]=/opt/ros/kinetic/share/ros
ROS path [1]=/home/[user]/[catkin_ws]/src
ROS path [2]=/opt/ros/kinetic/share

But this may be a problem with the realsense repo.
I got older versions of realsense-repo with librealsense v1.11.0 and v1.11.1 to be running and can complie/build the newest version 2.0 of librealsense and realsense but the R200 is not working with them.
I also had the problem while FW update that the calibration tool returns an error DS_INVALID_ARG.
I think there is a problem with the librealsense library, but I had no suggestions for a further insight or to investigate this.
Strange is to solve this by a FW update.
The errors of the uvcvideo driver is more troublesome.
The stable versions for me are FW/V <IP_ADDRESS>, librealsense v1.12.1, realsense 1.8.0.

Hello @KappesR
Please use version 1.12.1 with R200 / ZR300 models.
Versions 2.x support only D400 and SR300 series.
See supported devices under releases

Hi @dorodnic ,
thanks for the reponse!
There is may be a misunderstanding.
I already use v1.12.1 for R200 with realsense repo version 1.8.0:

The stable versions for me are FW/V <IP_ADDRESS>, librealsense v1.12.1, realsense 1.8.0.

But dmesg and roslaunch realsense_camera r200_nodelet_rgbd.launch throw still the above messages.
The fact I can compile/build realsense 2.0.0 with librealsense 2.x.x is not so important, sry for this.

Hi @KappesR,
Can you provide us the details of the computer you are using with these cameras? Note that the ZR300 has been validated only on the Joule 570x board with limited validation on the Up Board.
To verify that the R200 camera works, try connecting the R200 to the USB 3.0 port of a Windows 10 PC and check if it works with the Windows SDK sample apps, found here. Wait a few minutes after connecting the camera so the driver can install. If the driver does not install automatically, you can download it here.
Regards,
Jesus
Intel Customer Support
For best support, post issues in the RealSense Community.

Hi @jlgarcia75,
I'm use a Latitude 5480 (i5 7th gen.) with the above Ubuntu and kernel-version for all cameras.
Want you just to check it is a hardware issue of the R200 I have?
I ask because in Ubuntu, the R200 is running with librealsense version 1.12.1, but in dmesg the uvcvideo driver show these messages everytime when I call roslaunch realsense_camera r200_nodelet_default.launch:
[  465.656755] uvcvideo: Non-zero status (-71) in video completion handler.
[  465.664756] uvcvideo: Non-zero status (-71) in video completion handler.
[  465.664819] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).
[  465.715523] uvcvideo: Failed to query (SET_CUR) UVC control 1 on unit 7: -32 (exp. 2).

That's my first problem because the driver has some problems.
My second problem is that roslaunch realsense_camera r200_nodelet_rgbd.launch crashes instantly and the parameter enable_ir:=true or enable_pointcloud:=true does not effect the other launch script roslaunch realsense_camera r200_nodelet_default.launch.
I got the depth and rgb stream as well as the camera_infos for both, but I can't get any information about the ir stream or pointcloud in this manner.

I tried it with the Windows SDK as you described.
The examples worked for the R200 on a NUC. But if a example failed for some reason, any further execution of the failed example or other examples failed as well.
I needed to replug the R200 and it worked again.

@KappesR,
Did you try to patch the uvcvideo driver with /librealense/scripts/patch-uvcvideo-ubuntu-mainline.sh? After applying this patch, type: sudo modprobe uvcvideo.
If this doesn't work, your camera or connection may have a hardware problem. Have you tried connecting the camera via a powered USB 3.0 HUB?
The R200 camera is discontinued so if it is a hardware problem and you are still within your warranty period, you can get a refund from your point of purchase.
Jesus G.
Intel Customer Support

@jlgarcia75,
yes but I tested it again on a fresh Ubuntu 16.04 (same as everytime), but it did not work at all.
R200 is not connected.
I followed the installation guide for tag v1.12.1 and it pointed out the script you mentioned works for Ubuntu 14.04:

Update to 4.4 Stable Kernel
    Run the following script to install necessary dependencies (GCC 4.9 compiler and openssl) and update kernel to v4.4-wily

        ./scripts/install_dependencies-4.4.sh

    Run the following script to patch uvcvideo.ko

        ./scripts/patch-uvcvideo-4.4.sh v4.4-wily (note the argument provided to this version of the script)

        This script involves shallow cloning the Linux source repository (~100mb), and may take a while
(OR) Keep 3.19.xx Kernel
    Run the following script to patch uvcvideo.ko

        ./scripts/patch-uvcvideo-ubuntu-mainline.sh

    (R200 Only with 3.19.xx Kernel) Install connectivity workaround. Note this script needs to be run from within the scripts folder:

        cd scripts
        ./install-r200-udev-fix.sh
        cd ..

        This udev fix is not necessary for kernels >= 4.2
        Use of 3.19.xx Kernel is not recommended.

Nethertheless, I run the script and I got the message: Error :: You must put some 'source' URIs in your sources.list
So, I followed this:

(OR) Ubuntu 14.04.5 or Ubuntu 16.04.xx (Kernel 4.4)
./scripts/patch-uvcvideo-16.04.simple.sh

I started the script and after setting the configurations it terminated with the error:
scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: file or directory not found
compilation terminated.
scripts/Makefile.host:91: recipe for target „scripts/sign-file“ failed
make[2]: *** [scripts/sign-file] error 1
Makefile:566: recipe for target „scripts“ failed
make[1]: *** [scripts] error 2
Makefile:531: recipe for target „__build_one_by_one“ failed
make: *** [__build_one_by_one] error 2

I remembered the last time I left this error message as it is, because it worked nethertheless.
This time, I run the following to fix this:
sudo apt-get install python-pip python-dev libffi-dev libssl-dev libxml2-dev libxslt1-dev libjpeg8-dev zlib1g-dev
I run the ./scripts/patch-uvcvideo-16.04.simple.sh again and the previous error is gone, but a new one appeared:
  MODPOST 1 modules
WARNING: "media_entity_cleanup" [/home/[user]/librealsense/ubuntu-xenial/drivers/media/usb/uvc//uvcvideo.ko] undefined!
WARNING: "media_entity_init" [/home/[user]/librealsense/ubuntu-xenial/drivers/media/usb/uvc//uvcvideo.ko] undefined!
WARNING: "media_entity_create_link" [/home/[user]/librealsense/ubuntu-xenial/drivers/media/usb/uvc//uvcvideo.ko] undefined!
  CC      /home/[user]/librealsense/ubuntu-xenial/drivers/media/usb/uvc//uvcvideo.mod.o
  LD [M]  /home/[user]/librealsense/ubuntu-xenial/drivers/media/usb/uvc//uvcvideo.ko
make: Directory „/home/[user]/librealsense/ubuntu-xenial“ leave
Unloading existing uvcvideo driver...
modprobe: ERROR: could not insert 'uvcvideo': Exec format error

dmesg output is (while the ):
[ 1251.988300] usbcore: deregistering interface driver uvcvideo
[ 1252.332956] media: Linux media interface: v0.10
[ 1252.339834] Linux video capture interface: v2.00
[ 1252.347285] uvcvideo: version magic '4.4.83+ SMP mod_unload ' should be '4.10.0-35-generic SMP mod_unload '

Is it just a problem with the kernel-version (uname -r: 4.10.0-35-generic)?

I have no success in Ubuntu with any RS camera...I also have the following errors:
ERROR [140028983531328] (types.h:123) uvcvideo kernel module is not loaded Last Error: Success
RealSense error calling rs2_query_devices(context:0x202cd70):
uvcvideo kernel module is not loaded Last Error: Success

@KappesR ,
You need to follow the installation instructions from the master branch for installing the backend and patching the kernel.
The instructions you refer to apply for the 4.4 kernel that was current when the tag was issued (Nov 2016)

I followed the installation guide for tag v1.12.1 and it pointed out the script you mentioned works for Ubuntu 14.04:

Please reinstall the backend accordingly and update

@ev-mp ,
thanks also!
I tried as you mentioned on a clean Ubuntu 16.04 with 4.10.0-35-generic.
I opened qv4l2 which is a tool for video grapping and can be used as well as the ros realsense nodes.
So, the dmesg output with this tool is as follow:
[  165.989929] usb 2-3: new SuperSpeed USB device number 6 using xhci_hcd
[  166.012596] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[  166.012599] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  166.012602] usb 2-3: Product: Intel RealSense 3D Camera R200
[  166.012604] usb 2-3: Manufacturer: Intel Corp
[  166.012606] usb 2-3: SerialNumber: SN_2521007700
[  166.016238] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[  166.020329] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[  166.020336] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[  166.021300] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[  166.025502] uvcvideo: Unable to create debugfs 2-6 directory.
[  166.025595] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[  166.025875] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input16
[  166.026961] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[  166.031024] uvcvideo: Unable to create debugfs 2-6 directory.
[  166.031115] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[  166.031119] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[  166.031355] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input17
[  204.455146] uvcvideo: Failed to query (GET_CUR) UVC control 6 on unit 7: -32 (exp. 2).
[  204.456210] uvcvideo: Failed to query (GET_CUR) UVC control 4 on unit 6: -32 (exp. 4).

Still, the same problem.
Without the use of the ros realsense nodes the error appears also.
The view:

I got two errors from this programm:
Error Hue: Input/Output error
Error Exposure (Absolute): Input/Output error

In which way this correlate to the dmesg output I can only guess.
Maybe there is still a problem with the uvcvideo update or a problem with the firmware?
@jlgarcia75,
I tried to use the warranty three weeks ago, but it was denied.
I hope it's ok to publish this here:

The reasoning was as follow:
You can check the status of your Return by logging into your account.
This RMA has been denied. The product is sold AS-IS as stated on the website. There is no warranty support.

I already ordered a USB 3.0 Hub with powered ports, but it's curious that two R200 broke in one week.
And that the ZR300 has the same errors as well..

@KappesR,
The return period for RealSense cameras is 90 days so if you purchased them over 90 days ago that is why your request is denied.  Or, I noticed that your request is for an "Exchange." R200 cameras are discontinued and there are no more in stock. If you purchased it within 90 days then you can get a refund, but not an exchange.
Have you tried the USB HUB yet? It may solve your problems. It is odd for all three cameras to fail simultaneously unless it is a USB issue.
Jesus
Intel Customer Support

@jlgarcia75,
I see, we bought them one year and two months ago, so that is the reason for the denied request.
I tried the USB Hub now but same error log, any further ideas?
Thanks for the help so far!

@KappesR , please perform  several troubleshooting and data gathering steps:

Use the device with Windows OS or some other PC and check whether the same issues can be reproduced
Run dmesg -wT and then do the following:

Connect R200 to the USB port.
Run cpp-tutorial1-depth demo in a separate terminal
Check whether the device is streaming and also collect and share output from both terminals

@ev-mp,
thanks for the steps:
1.
I have done this before:

I tried it with the Windows SDK as you described.
The examples worked for the R200 on a NUC. But if a example failed for some reason, any further execution of the failed example or other examples failed as well.
I needed to replug the R200 and it worked again.

Its not the same behavior.
2.
I have tested cpp-tutorial-1-depth and cpp-tutorial-2-streams.
cpp-tutorial-1-depth:
Console Output:

                                    .n.::.
                              .       :hWWXh.
                              .:.      X. hWB.
                              hh       :  nWh:
                            .:.        .  BWhh
                            :X          ::WBXB
                                             n
                             .              :n
                             .             h:
                            .n             h
                             :   .         h
                                           :: ...
                     .nXBhBn:BBBnnn                   .nhh..
                  :nWWWWWWBBXnhBhn:                     .   h
              .:BWXWB:  ..n:                                h
         :. ::.   ..     :n                                 h
       :h.      .:
                .                      .

While dmesg -wT:
[Mo Okt 16 15:25:13 2017] usb 2-3: new SuperSpeed USB device number 10 using xhci_hcd
[Mo Okt 16 15:25:13 2017] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[Mo Okt 16 15:25:13 2017] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mo Okt 16 15:25:13 2017] usb 2-3: Product: Intel RealSense 3D Camera R200
[Mo Okt 16 15:25:13 2017] usb 2-3: Manufacturer: Intel Corp
[Mo Okt 16 15:25:13 2017] usb 2-3: SerialNumber: SN_2521001926
[Mo Okt 16 15:25:13 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:25:13 2017] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[Mo Okt 16 15:25:13 2017] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[Mo Okt 16 15:25:13 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:25:13 2017] uvcvideo: Unable to create debugfs 2-10 directory.
[Mo Okt 16 15:25:13 2017] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[Mo Okt 16 15:25:13 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input24
[Mo Okt 16 15:25:13 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:25:13 2017] uvcvideo: Unable to create debugfs 2-10 directory.
[Mo Okt 16 15:25:13 2017] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[Mo Okt 16 15:25:13 2017] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[Mo Okt 16 15:25:13 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input25

In several runs, no error appeared.
cpp-tutorial-2-depth:
Console Output:
~$ cpp-tutorial-2-streams
There are 1 connected RealSense devices.

Using device 0, an Intel RealSense R200
    Serial number:<PHONE_NUMBER>
    Firmware version: <IP_ADDRESS>
^C
~$ cpp-tutorial-2-streams
There are 1 connected RealSense devices.

Using device 0, an Intel RealSense R200
    Serial number:<PHONE_NUMBER>
    Firmware version: <IP_ADDRESS>
^C

Image Output:

On the first run:
dmesg -wT:
[Mo Okt 16 15:33:28 2017] usb 2-3: USB disconnect, device number 10
[Mo Okt 16 15:33:31 2017] usb 2-3: new SuperSpeed USB device number 11 using xhci_hcd
[Mo Okt 16 15:33:31 2017] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[Mo Okt 16 15:33:31 2017] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mo Okt 16 15:33:31 2017] usb 2-3: Product: Intel RealSense 3D Camera R200
[Mo Okt 16 15:33:31 2017] usb 2-3: Manufacturer: Intel Corp
[Mo Okt 16 15:33:31 2017] usb 2-3: SerialNumber: SN_2521001926
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo: Unable to create debugfs 2-11 directory.
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[Mo Okt 16 15:33:31 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input26
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo: Unable to create debugfs 2-11 directory.
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[Mo Okt 16 15:33:31 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input27

The second run:
[Mo Okt 16 15:33:28 2017] usb 2-3: USB disconnect, device number 10
[Mo Okt 16 15:33:31 2017] usb 2-3: new SuperSpeed USB device number 11 using xhci_hcd
[Mo Okt 16 15:33:31 2017] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[Mo Okt 16 15:33:31 2017] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mo Okt 16 15:33:31 2017] usb 2-3: Product: Intel RealSense 3D Camera R200
[Mo Okt 16 15:33:31 2017] usb 2-3: Manufacturer: Intel Corp
[Mo Okt 16 15:33:31 2017] usb 2-3: SerialNumber: SN_2521001926
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo: Unable to create debugfs 2-11 directory.
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[Mo Okt 16 15:33:31 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input26
[Mo Okt 16 15:33:31 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Mo Okt 16 15:33:31 2017] uvcvideo: Unable to create debugfs 2-11 directory.
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[Mo Okt 16 15:33:31 2017] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[Mo Okt 16 15:33:31 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input27
[Mo Okt 16 15:33:42 2017] uvcvideo: Non-zero status (-71) in video completion handler.

On the second start of cpp-tutorial-2-streams the log  [Mo Okt 16 15:33:47 2017] uvcvideo: Non-zero status (-71) in video completion handler. appears only once or three times. After this, it appears everytime two times by restarting the binary.

Hi @KappesR, according to the logs and the provided screenshots:

Device enumeration is performed correctly (USB3 device).
Kernel module is properly configured (no missing formats).
Librealsense streams and renders all R200-available sensors.
The message :

uvcvideo: Non-zero status (-71)

is a warning and can be safely disregarded.
I cannot immediately comment on ros-node log  as you should probably refer it to https://github.com/intel-ros/realsense , but there are hints for the package configuration issues:

ResourceNotFound: rgbd_launch

But other than that the software stack is properly configured and fully functional, and ,actually, I'd recommend to use this specific host as a reference system to validate the two additional R200 that you've mentioned in your previous posts.
As to the scenario that the device stops streaming and requires a manual re-plug - it is definitely an issue on a Host-Device level,  and without having kernel log and a deterministic reproduction flow it would be a pure speculative to determine what went wrong.
Based on previous experience the R200 family sensible to cables length/quality and the power. In addition the host USB controllers from different vendor matters.
Please run a comprehensive search on the issues archive to obtain additional community inputs and reccomendations, e.g (#117), (#67), (#418) and more

@ev-mp,
i tried further test programs of the librealsense.
I can reproduce the uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1) with the following library example:
cpp-config-ui:
Console:
~$ cpp-config-ui:
Capturing DEPTH at 628 x 468, fov = 56.6 x 43.7, distortion = NONE
Capturing COLOR at 640 x 480, fov = 55.0 x 42.3, distortion = MODIFIED_BROWN_CONRADY
Capturing INFRARED at 640 x 480, fov = 57.5 x 44.7, distortion = NONE
Capturing INFRARED2 at 640 x 480, fov = 57.5 x 44.7, distortion = NONE

Dmesg -wT:
[Di Okt 17 13:50:52 2017] usb 2-3: new SuperSpeed USB device number 8 using xhci_hcd
[Di Okt 17 13:50:52 2017] usb 2-3: New USB device found, idVendor=8086, idProduct=0a80
[Di Okt 17 13:50:52 2017] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Di Okt 17 13:50:52 2017] usb 2-3: Product: Intel RealSense 3D Camera R200
[Di Okt 17 13:50:52 2017] usb 2-3: Manufacturer: Intel Corp
[Di Okt 17 13:50:52 2017] usb 2-3: SerialNumber: SN_2521001926
[Di Okt 17 13:50:52 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Di Okt 17 13:50:52 2017] uvcvideo 2-3:1.0: Entity type for entity Extension 2 was not initialized!
[Di Okt 17 13:50:52 2017] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[Di Okt 17 13:50:52 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Di Okt 17 13:50:52 2017] uvcvideo: Unable to create debugfs 2-8 directory.
[Di Okt 17 13:50:52 2017] uvcvideo 2-3:1.2: Entity type for entity Camera 4 was not initialized!
[Di Okt 17 13:50:52 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/input/input20
[Di Okt 17 13:50:52 2017] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[Di Okt 17 13:50:52 2017] uvcvideo: Unable to create debugfs 2-8 directory.
[Di Okt 17 13:50:52 2017] uvcvideo 2-3:1.4: Entity type for entity Processing 7 was not initialized!
[Di Okt 17 13:50:52 2017] uvcvideo 2-3:1.4: Entity type for entity Camera 6 was not initialized!
[Di Okt 17 13:50:52 2017] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.4/input/input21
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:07 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:08 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).
[Di Okt 17 13:51:08 2017] uvcvideo: Failed to query (GET_CUR) UVC control 18 on unit 2: -32 (exp. 1).

Screen:

The errors appear after i press start capture, for some time the capturing does not start. After the uvcvideo driver stop failing, the video capture is working.
I will look into the closed issues you mentioned and let you know if i could fix it with them, thereby I was able to reproduce the issue with the librealsense examples, with qv4l2 and with the ROS-Wrapper it is a independent issue to the ROS Wrapper and to the librealsense library. Maybe the uvcvideo driver update is not working correctly.

Hello @KappesR,
Do you still need help with this issue?
Regards,
Jesus G.
Intel Customer Support

Hi @jlgarcia75,
yes, I tried to solve the problem with the attached issues by @ev-mp and it didn't worked.
I search further in the issue list of the ros-wrapper but couldn't solved this up yet.
If you have some further suggestions, I would be glad.

Hi @KappesR , I'm not sure that I'm following the issue with you :  Initially you indicated that all three devices stopped working,  but then you did provide streaming captures for at least some of the devices.
Can you clarify what are the currently unresolved issues are ? thanks

Hello @KappesR,
Do you still need help with this issue?
Regards,
Jesus G.
Intel Customer Support

I have met the same problem on Ubuntu 16.04.3? do you have a solution now?

Me too, crash when set parameter
error that occur is
RealSense error calling rs_device_supports_option( ....


It just works: The homebrew manager for MacOS (or linux)

Link

https://brew.sh/

Code (very prominent on site):
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

I take Homebrew in the list, thanks!


Keyboard shortcuts sometimes not working in editor

(Using Old Edge)
Describe the bug

Ctrl-Z in the editor presses the A button in the simulator
Ctrl-C doesn't work

It doesn't always do this either. If I right click on the block, then I can do the shortcuts again, but if I click on the sim and then back to the editor, it's broken. I can only get it to register shortcuts after right clicking (left click doesn't focus to the editor)
Desktop :
OS: Windows
Browser: Old Edge (44.18362.449.0)

@livcheerful if the simulator is selected then all the controls will be on simulator and not on the editor. Can you confirm if this happens even if the simulator is not selected?

Ah I see. I think the only way to unselect the simulator is to right click. Left clicking in the editor doesn't focus away from the simulator (in blocks). Like if I drag a block out and the ctrl-Z, it doesn't work.

@livcheerful should I keep this bug open?

I haven't seen this one in a while! Closing


Support dataframe columns containing lists

This chart renders fine using the default renderer in Altair
alt.Chart(
    pd.DataFrame({
        'month': ['January', 'January'],
        'value': [3.0, 1.0],
        'label': [['Benzene', '(μg/m³)'], ['Carbon monoxide', '(mg/m³)']]
    })
).mark_point().encode(
    x='value',
    y='month'
).facet(
    'label'
)

Trying the same chart after enabling vegafusion with alt.data_transformers.enable('vegafusion'), yields this error:
ValueError: DataFusion error: External error: Internal error: Unsupported data type in hasher: List(Field { name: "item", data_type: Utf8, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }). This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker
    Context[0]: Failed to get node value

While lists are useful to split strings over multiple lines, there might be a workaround here using labelExpr. However, this is for a class taught to first year students and I want to avoid making it too complicated so I might just stick with single line string labels for now.

Thanks for the report!
My initial guess (based on the error message) is that the issues here is that the chart facets by the list column, which results in a GROUP BY query in DataFusion, and it looks like DataFusion might not support that yet.  I'll look at either fixing it in DataFusion or working around it by keeping the logic on the client in situations like this.

This isn't straightforward to work around unfortunately. VegaFusion's planning logic, which decides which transforms should be evaluated on the server, doesn't currently have access to the schema of the input tables, so we can't just check the column types and keep the aggregate transform on the client if there's a list column.

Upstream support in DataFusion was merged in https://github.com/apache/arrow-datafusion/pull/7616. So when DataFusion 32 is released and VegaFusion updates to it, this bug will be fixed.
I'll keep this open until VegaFusion has the update

That's great, thank you Jon!


fixfix can not resolve host and port

Proposed changes
Issue Number: close #xxx
pick from https://github.com/apache/doris/pull/25254
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.86 seconds
stream load tsv:          575 seconds loaded<PHONE_NUMBER>9 Bytes, about 124 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>7 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.72 seconds
stream load tsv:          577 seconds loaded<PHONE_NUMBER>9 Bytes, about 123 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>5 Bytes

run p0


Ensure network exists on startup

When started, check if the specified network exists or eventually create it.

Hi, I was trying to run the instance create on v2.0 branch and I got -{"code":500,"message":"Internal Server Error"}. The docker logs on redzilla container shows
time="2018-04-10T04:22:46Z" level=info msg="Container create mynew"
time="2018-04-10T04:22:46Z" level=error msg="Internal Error: Error response from daemon: network redzilla not found"
My docker network ls shows
f21742fa706d        redzilla_redzilla   bridge              local
67e9a7a6ce24        redzilla_webproxy   bridge              local
The folder name prefix is used. Is this the same issue or some networking issue on my side? (I had installed the docker(17.12.1-ce) and docker compose(1.19.0) as given in docker site)

Hi
You can Try with
docker network create redzilla
Or look at the config file / environment vars to set another network name
from those that exists in docker
Need to review this to make it start with default settings.
Thanks
sent from my phone
Il mar 10 apr 2018, 06:41 rmvpaps<EMAIL_ADDRESS>ha scritto:

Hi, I was trying to run the instance create on v2.0 branch and I got
-{"code":500,"message":"Internal Server Error"}. The docker logs on
redzilla container shows
time="2018-04-10T04:22:46Z" level=info msg="Container create mynew"
time="2018-04-10T04:22:46Z" level=error msg="Internal Error: Error
response from daemon: network redzilla not found"
My docker network ls shows
f21742fa706d redzilla_redzilla bridge local
67e9a7a6ce24 redzilla_webproxy bridge local
The folder name prefix is used. Is this the same issue or some networking
issue on my side? (I had installed the docker(17.12.1-ce) and docker
compose(1.19.0) as given in docker site)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/muka/redzilla/issues/9#issuecomment-379971772, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA-VVYbYzzzU_0zPOMdH0STemk_0nC0Vks5tnDfwgaJpZM4SrsaF
.


copr: Add vectorize sha2

Signed-off-by: Rustin-Liu<EMAIL_ADDRESS>PCP #5751

What have you changed?
Add vectorize sha2.
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
None
Does this PR affect tidb-ansible?
None
Refer to a related PR or issue link (optional)
#5751
Benchmark result if necessary (optional)
None
Any examples? (optional)
None

Thanks a lot! Please also run your PR against a copr-test that enables the sha2 push down.

Thanks a lot! Please also run your PR against a copr-test that enables the sha2 push down.

passed.

@sre-bot  /run-integration-copr-test copr-test=pr/98

@sre-bot   /run-integration-copr-test copr-test=pr/98

@rleungx  PTAL~

@sre-bot   /run-integration-copr-test copr-test=pr/98

Passed all tests.
PTAL~

LGTM. Thanks

/merge

@sre-bot  /run-auto-merge//merge

@sre-bot  /merge

Sorry, the integration test is broken recently. Your PR will be merged after it is fixed :)

/run-integration-common-test

/run-all-tests

/run-all-tests

@sre-bot /merge

/merge

/merge

/test

/merge


Accuracy of the map

Hello!
Thanks for this awesome framework!
Could you advise please.
How can achieve such accuracy of the outdoor map to have a single layer of ground (one surface) without doubled ground or "thick film" of the ground?
Thank you!

I think enabling floor constraint helps in resolving the doubled ground issue.

@koide3 Thank you for your reply!
Is it correct to enable "floor detection" option for an outdoor map with a road slope with ascents and descents?

The floor plane correction assumes that the environment has a flat floor. If you need to consider ascents/descents or multiple floors, please consider using interactive_slam that enables manually inserting plane constraints to the map.

I've already started using it.
Thanks a lot!


Issues while runing node.js

After runing "node caltech_pd.js" under path "caltech-pedestrian-dataset-extractor" ,there is a Issue.As follow:
module.js:339
throw err;
^
Error: Cannot find module './build/Release/fs-ext'
at Function.Module._resolveFilename (module.js:337:15)
at Function.Module._load (module.js:287:25)
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Object. (/home/zqy/Desktop/lstm-rcnn-pedestrian-detection/caltech-dataset/caltech-pedestrian-dataset-extractor/node_modules/fs-ext/fs-ext.js:20:15)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Module.require (module.js:366:17)
So I run "npm install -g fs-ext" under path "caltech-pedestrian-dataset-extractor", but there is a new issue.As follow:
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "fs-ext"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR!     /home/zqy/Desktop/lstm-rcnn-pedestrian-detection/caltech-dataset/caltech-pedestrian-dataset-extractor/node_modules/npm-debug.log
How to fix it?

I have try updating npm version to 5.3.0, and node version to v8.2.1. but it doesn't seem work when runing "npm install -g fs-ext" under path "caltech-pedestrian-dataset-extractor". As follows:
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/fs'
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-07-28T04_46_59_992Z-debug.log

npm install -g fs-ext works fine for me. I am on node version v6.6.0.

Alright, thank u. I just try it on node version v6.6.0.


Cannot install the Mac version

An error appeared and said “wiregui” is damaged and can’t be opened. You should move it to the Trash." After I tried to open the application

indeed, I think some new version from Mac broke it, will need to rebuild it
I don't have a Mac with the development tools installed to build it at the moment, once I have I can try to rebuild

Hello! I have a similar issue, i had the following message: You can’t open the application “wiregui” because this application is not supported on this Mac.
Could be possible generate the version for intel amd64 based architectures?
Thanks in advance!


Reward container error handling

📲 What

Adds an Error State view to the Rewards Container, allowing the user to tap a button to retry fetching backing infos.

🤔 Why
This is part of the first release of the Native Checkout project.
Trello card: https://trello.com/c/gmkKdvTG/1492-error-handling-for-loading
🛠 How

The fetchProject(projectOrParam:) on ProjectPamphletViewModel now returns SignalProducer<Project, ErrorEnvelope> instead of SignalProducer<Project, Never>. This will tell the callers when an error occurred.
On ProjectPamphletViewModel.swift, the configurePledgeCTAView output now emits Signal<(Either<Project, ErrorEnvelope>, Bool), Never>
The PledgeCTAContainerViewViewModel receives the (Either<Project, ErrorEnvelope>, Bool) as an input and will take care of the UI logic based on what's sent (.left(project) or .right(error)).

👀 See

Before 🐛
After 🦋

♿ Accessibility

[ ] Tap targets use minimum of 44x44 pts dimensions
[ ] Works with VoiceOver
[ ] Supports Dynamic Type

✅ Acceptance criteria

[ ] From Discovery, turn on Flight Mode on your device and tap on any project
[ ] The Activity Indicator should be visible
[ ] Once the server returns an error, the Activity Indicator should disappear and the Retry button should be visible.
[ ] Turn off flight mode and tap the retry button. The Back this Project button should be visible and the retry Button should be hidden.

 Error Handling for loading


Add: Canal 8 Durazno [UY]

Channel Name
Canal 8 Durazno
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
UY
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/UY
Languages
spa
Categories (optional)
General
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
No response
Logo
https://cds-assets.cdn.antel.net.uy/imagenes/recursos/MjUcQ3yJp2idhOVJT47PZOEhLJPkh8ns8K7ALbFK.jpeg
Notes
No response

Added in https://github.com/iptv-org/database/commit/b3e079a4f019936d827aa323411273f5c7440ee9


considering jose library from dist/browser instead of dist/node

This is more of a discussion rather than an issue. Apologies if this had a better place to be asked than here, I used this space for lack of a discussions tab.
I am running a project scaffolded through create electron-vite in react. Ordinarily with a simple index.js file using the jose library I am able to generate the expected PublicKeyType & PrivateKeyType but when using the jose library inside of main.ts app.whenReady in electron-vite react project it is giving types of CryptoKey for both the public & private keys. Upon research I found that, jose's dist/browser code is being used from node modules rather than dist/node code which is required for my project to run successfully.
Can somebody point me to the configuration changes required to tell electron-vite to use dist/node within jose library and not the dist/browser for this to resolve the methods used of jose.
PS: I have tried nodeIntegration: true, hoping it would help but no luck. I have been going through similar issues and the docs but no luck.

Hey! 👋 @suraj-sella
Perhaps you can provide a minimal replication repo for our discussion.

@caoxiemeihao Thank you so much for responding.
Here is a minimal replication repo as requested: https://github.com/suraj-sella/electron-vite-jose
Please note that I have used require statements and you can see the cryptoRuntime is node:crypto as expected.
If you replace those require with import statements (I am assuming that is standard) cryptoRuntime becomes webCryptoAPI and the functionality fails.
Again, highly appreciate the time you spend with this query.

Case 1: import * as jose from 'jose' means it will be resolve by Vite, and the actual loaded path is dist/browser/index.js

Case 2: const jose = require('jose') will not resolved by Vite, which means that using the require(id) function of Node.js to load the module, the actual path is dist/node/cjs/index.js.

This is simply because Vite will not parse the require(id) function by default and we do not want require(id) to be parsed by Vite in the Electron main process.
If you wiant to import dist/node or dist/browser very accurately you can complete the import path.
Although Vite can be configured to control the imported path, this may not apply to all npm modules.
BTW,  another way is to change the import path by resolve.alias. This is a very convenient way. I will often use it to achieve my purpose.
e.g.
// vite.config.ts
{
  resolve: {
    // For Vite parse `import` path.
    alias: {  jose: 'jose/dist/node/cjs/index.js' },
  },
}


Modernizr

Trying to detect touchevents using Modernizr in App.jsx to roll the appropriate DnD backend...
if (__DEVCLIENT__) {
  Modernizr = require('./external/modernizr.js');
}
App = DragDropContext(Modernizr && Modernizr.touchevents ? TouchBackend : HTML5Backend)(App);

getting undefined in the browser console - Guessing this has something to do with SSR?
Any help much appreciated - Thx

I haven't used Modernzr with this repo and on SSR before. Sounds like an SSR issue.
If you have more sample code (or a branch up), maybe we could have a look and try to debug this further.

Ok, solution was to use this webpack loader - peerigon/modernizr-loader
But the trick is to use webpack.DefinePlugin(){...} to control how it all works in App.jsx:
if (__DEVCLIENT__ || __PRODCLIENT__) {
  const Modernizr = require('modernizr');
  App = DragDropContext(Modernizr.touchevents ? TouchBackend : HTML5Backend)(App);
} else {
  App = DragDropContext(TouchBackend({ enableMouseEvents: true }))(App);
}

just need to add another flag for PROD webpack config:
new webpack.DefinePlugin({
  __PRODCLIENT__: true, // false on SSR

}),


fix: automatically sign in after password reset succeeds

[x] PR conforms to Pull Request guidelines.

Issue #, if available:
https://github.com/aws-amplify/amplify-ui-android/issues/160
Description of changes:
Update password reset to automatically sign in after password reset successfully completes.  This matches with current behavior in Amplify Swift
How did you test these changes?

Manually tested on simulator to ensure that password reset automatically signs user in on completion.
Manually tested use case when a user signs in with a temporary password is prompted with password reset and workflow works as expected.
Added a unit test for the sign case of when password reset is required due to temporary password requiring reset.

Documentation update required?

[x] No
[ ] Yes (Please include a PR link for the documentation update)

General Checklist

[x] Added Unit Tests
[ ] Added Integration Tests
[x] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I think we just need to add some additional unit tests here around the state transitions.

If password reset confirmation succeeds, state should be signed in
If password reset confirmation succeeds but sign in fails, state should be sign in
If password reset returns a result of DONE, state should be sign in

Added additional unit tests to cover test cases suggested by @mattcreaser


Data accessible via API

Most of the data that is displayed via the web UI is also accessible via the API, however, some information is still missing. I would like to use this issue to collect the missing parts.
A possibly non exhaustive list I've been able to come up with that is still missing:

runtime information shown on /status
currently pending/firing alerts
loaded config :heavy_check_mark:
loaded rules

Anything I'm missing?
@beorn7 @brian-brazil @fabxc @juliusv

It's basically everything under the Status tab, i.e. not only /status but also /flags, /config, /rules, /targets. Not sure if any of those can already be queried via the API.

We have to be a little careful with some of those, as things like rule groups will likely change the formats even if the feature itself was backwards compatible.

@brian-brazil Agreed. For rules and config I was thinking for a start to really just expose the loaded string source.
@beorn7 /targets and /alertmanagers already exists on the API and was released in v1.5.0, but the others I agree with.

I will start working on the /status/config endpoint exposing the currently loaded config as displayed in the UI.

How much is left here?

@brian-brazil In regards to exposing the status: Still working on https://github.com/prometheus/prometheus/pull/2711.

How much is left here?

With https://github.com/prometheus/prometheus/pull/2711 merged, the loaded config can be retrieved via the API.
I will update the initial issue description. @brancz hope you don't mind.
I will see what I can do in regards to "currently pending/firing alerts" following up on https://github.com/prometheus/prometheus/pull/4012 and https://github.com/prometheus/prometheus/pull/3656.

@mxinden Go for it.

How much is left here?

With https://github.com/prometheus/prometheus/pull/4318 merged, I updated the top level issue:

currently pending/firing alerts :heavy_check_mark:
loaded rules :heavy_check_mark:

I think this can be closed.

I can see runtime information at /status but I also see an open PR for this https://github.com/prometheus/prometheus/pull/5165 which tries to add some stuff which is already present. Not sure what else is left to be added. Closing this for now and can be reopened if needed.


Logo contribution

Hi, I design logo contributions to open source software. We can update the logo of this project if you want. more simple and memorable a logo...

No, Thanks


Cannot compile examples

Hi
Thanks for this nice move towards WebRTC
I am trying to compile the examples, on PI3 Debian, following your instructions
I am hitting the following error

pi@raspberrypi:~/gstwebrtc-demos/sendrecv/gst $ gcc webrtc-sendrecv.c $(pkg-config --cflags --libs gstreamer-webrtc-1.0 gstreamer-sdp-1.0 libsoup-2.4 json-glib-1.0) -o webrtc-sendrecv
Package gstreamer-webrtc-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing gstreamer-webrtc-1.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gstreamer-webrtc-1.0' found Package json-glib-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing json-glib-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'json-glib-1.0' found
webrtc-sendrecv.c:9:21: fatal error: gst/gst.h: No such file or directory
#include <gst/gst.h>
^
compilation terminated.

Can't get around it, please help :)
Phil

What GStreamer version are you using? Did you install 1.14? Can you check if you have a file called gstreamer-webrtc-1.0.pc on your filesystem? If not, you need to install the dev packages for the gst-plugins-bad libraries.
Same for json-glib-1.0, you need to install the libjson-glib-dev package for that.

Thanks for the quick answer
json-glib side fixed with
$ sudo apt-get install libjson-glib-dev
Gstreamer-webrtc-1.0.pc not there, true.
Please indicate what is the name of the dev package for the gst-plugins-bad libraries
Phil

version I have here
pi@raspberrypi:~/gstwebrtc-demos/sendrecv/gst $ sudo apt-get install gstreamer-1.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libqtgstreamer-1.0-0' for regex 'gstreamer-1.0'
Note, selecting 'gir1.2-gstreamer-1.0' for regex 'gstreamer-1.0'
Note, selecting 'libqt5gstreamer-1.0-0' for regex 'gstreamer-1.0'
gir1.2-gstreamer-1.0 is already the newest version (1.10.4-1).
libqt5gstreamer-1.0-0 is already the newest version (1.2.0-4).
libqtgstreamer-1.0-0 is already the newest version (1.2.0-4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

got it. shall I start here?
https://github.com/centricular/gstwebrtc-demos#building-gstreamer-manually-from-source

Hi, here is my case:
I use gst-uninstalled tool to build from source, following this guide: https://arunraghavan.net/2014/07/quick-start-guide-to-gst-uninstalled-1-x/
and after install some missing libs: libjson-glib-dev, libnice..  finally, it pass the compile, but when I run the webrtc-sendrecv, it appears:
Required gstreamer plugin 'webrtc' not found
here is my env after run : pkg-config --cflags --libs gstreamer-webrtc-1.0
-pthread -I/root/gst/master/gstreamer/libs -I/root/gst/master/gstreamer -I/root/gst/master/gstreamer/libs -I/root/gst/master/gstreamer -I/root/gst/master/gstreamer/libs -I/root/gst/master/gst-plugins-bad/gst-libs -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -L/root/gst/master/gstreamer/libs/gst/base/.libs -L/root/gst/master/gstreamer/gst/.libs -L/root/gst/master/gst-plugins-bad/gst-libs/gst/webrtc/.libs -lgstwebrtc-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0

Well, what's your configure output for -bad? What's your libnince version? You will need 0.1.14

@tp-m it's ok know, you remind me with " what's your configure output for -bad ".
I go to ~/gst/master/gst-plugins-bad folder and
./configure; make; make install
then recompile and run webrtc-sendrecv, it's ok know.
so the guide in https://arunraghavan.net/2014/07/quick-start-guide-to-gst-uninstalled-1-x/ not so exact， it says using below command to build will be ok:
$ ./gstreamer/scripts/git-update.sh
maybe we should enter each module and run ./autogen.sh;make;make install
Thanks all the same!


VMware Releases Security Advisory for Multiple Products -<PHONE_NUMBER>2

@DGovEnterprise -  Please review and approve on the advisory.

Please add links to CVEs before i can approve

editing the document further, adding links to CVEs


Handle GeoJSON GeometryCollection

Handle geometry with type='GeometryCollection'.
GeometryCollection is described in section 3.1.8 of the GeoJSON spec.
TODO
[ ] Tests

Looks good. Can you add a simple test case?

Tweaked the existing tests and implementation so that GeometryCollection is handled just like any other geometry type.

I'm good with merging this when you are @Pessimistress


preserving the existing appbuilder properties and conventions inside the middleware

same as #59 but targetted to dev branch.

Hi @tugberkugurlu, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Would be really cool if you can push a nuget package somewhere which has this fix.

thanks!


CultureSelector.razor smaller alternative

[EDIT by guardrex to provide complete code for the property and that matches the doc's current example naming.]
on CultureSelector.razor we could remove the need for a controller by using this code on Culture set
@inject IJSRuntime JS

...

private CultureInfo Culture
{
    get => CultureInfo.CurrentCulture;
    set
    {
        if (value is null || value == Culture)
        {
            return;
        }

        var str = CookieRequestCultureProvider.DefaultCookieName + "="
           + CookieRequestCultureProvider.MakeCookieValue(new RequestCulture(value));

        await JS.InvokeVoidAsync("eval", $"document.cookie = \"{str}\"");

        Nav.NavigateTo(Nav.Uri, forceLoad: true);
    }
}

(await used because I used onchange instead of bind)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
Version Independent ID: d6f07538-228e-9f96-680f-6c324caf11d6
Content: ASP.NET Core Blazor globalization and localization
Content Source: aspnetcore/blazor/globalization-localization.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Let's ask @hishamco what he thinks about that.

@guardrex you could avoid eval if you want, but you'll have to create a small js function that will set document.cookie and call it instead

I have a feeling that you're going to have to re-pitch the whole idea on the JS interop basis because I think that eval like this on the basis of client data is going to be flatly rejected by the PU. Perhaps, you should close this issue and make a new issue with the complete updated approach using JS interop, then we can ping Hisham to look at that approach.

@guardrex what is PU ?

"product unit" ... Steve, Javier, Tanay, etc. ... The ones who actually know how to write real software ... not 🦖  Dinohacks™ 😆.

Seems I came late ;), I'm not sure why you are using await JS.InvokeVoidAsync("eval", $"document.cookie = \"{str}\""); which is something scary
Please let me know are using Server-Side Blazor or WebAssembly, coz things different here

@hishamco ... I don't think we want to make changes to what the doc shows. If devs want to take a different approach (e.g., @omuleanu's JS concept) to avoid the controller/round-trip, that's fine, but I think they'd just do that on their own. Do you disagree? Do you prefer for the doc's example to change? I'm 🏃⛰⛏😅 as usual and we're very busy with high priority issues; so if this can be taken as an optional case for devs to implement on their own if they want it, then I'd prefer to close this and stick with what we have.

@guardrex I'm not suggesting to change the docs, AFAIK our docs already have a sample. The questions are:

What's the wrong with what we have?
What are the advantages for the suggested approach over settings the culture from Program.cs?

I'm saying that you're suggesting it. @omuleanu is suggesting the change. I'm asking the same questions.

Nothing if the round-trip perf isn't a problem. I don't think it's a big deal.

It isn't about setting the culture from Program.cs. It's about avoiding the round-trip to the controller to set the cookie. It's to avoid this ...
[Route("[controller]/[action]")]
public class CultureController : Controller
{
    public IActionResult Set(string culture, string redirectUri)
    {
        if (culture != null)
        {
            HttpContext.Response.Cookies.Append(
                CookieRequestCultureProvider.DefaultCookieName,
                CookieRequestCultureProvider.MakeCookieValue(
                    new RequestCulture(culture, culture)));
        }

        return LocalRedirect(redirectUri);
    }
}

As I mentioned earlier if it's in Server-Side Blazor you can set the culture with the available stragtegies, either in PageModel, MVC Controller. In Blazor WebAssembly this could be done in Program.cs itself
I don't think there's an issue here, he could use his technique in custom implementation, taking the JavaScript risk in his mind

As usual @guardrex os fast to open , so fast to close ;)


README

Codecov Report

Merging #2 into master will increase coverage by 0.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   85.86%   86.03%   +0.17%
==========================================
  Files          21       21
  Lines         969      967       -2
==========================================
  Hits          832      832
+ Misses        110      108       -2
  Partials       27       27

Impacted Files
Coverage Δ

jobsession.go
88.88% <ø> (+1.76%)
:arrow_up:

jobarray.go
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Differentiate between LED-Device Enable/Disable and Switch On/Off

Summary
Differentiate between LED-Device Enable/Disable and Switch On/Off allows to
switch off LED-Devices output when there is no signal e.g. given no source is available any longer.
In case input is available again, LED-Devices are switched on.
In both cases, the LED-Device shows enabled allowing to differentiate from error state or a suspend/resume scenario.
Currently, switch on/off is implemented, if no source is available (addressing #828).
Open: The change will allow fixing #930. here work is in progress...
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[X] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[ ] Other, please describe:

If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[X] No

If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature
[X] Related documents have been updated (docs/docs/en)

[ ] Related tests have been updated

PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD

[ ] Yes, CHANGELOG.md is also updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Fixes: #828

@Lord-Grey Is the PR done so far?

Yes, Let us merge the PR now.


Update README to reflect latest code

This change updates the readme to reflect the latest code, method of testing and hopefully a fix for the PyPi syntax.

Non-code change, merging.


Truncate execution error message in list execution calls

TL;DR
For repeated execution failures with long error message stack traces, the call to list executions can exceed the default gRPC message size.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/3337
Follow-up issue
NA

Yeah, the primary use-case case for this endpoint is predominantly listing execution phases in the UI - output results are discarded. To render the full error message/output we usually land on the individual execution page which should call GetExecution to get details in full


GetBlockHeader call is missing

No api call for get_block_header:
https://github.com/bitshares/bitshares-core/blob/319d7b96a4d29902db80631022bb021ca79ac950/libraries/app/database_api.cpp#L66

Contributions are highly appreciated!


Method registerApplicationAsync(tags) error "The certificate for this server is invalid..."

Hi there ! On iOS, Android and WP8, the method registerApplicationAsync(tags) end in the error callback with this message :
The certificate for this server is invalid. You might be connecting to a server that is pretending to be #######.servicebus.windows.net” which could put your confidential information at risk.

But Azure account for development is recent... And if I try with prod account, the result is the same. Do you have an idea ? Thanks a lot !!!
I'm on Cordova 5, the last version.

change tags content ?

Since january, Azure change their operation so now it works : we're now using azure-mobile-services Cordova plugin ;)


Stop using GitHub Discussions

We'll stop using GitHub Discussions.
Please use GitHub Issues instead.
For details, please see the following issue.

https://github.com/suzuki-shunsuke/suzuki-shunsuke/issues/2

Done.

https://github.com/suzuki-shunsuke/tfaction/pull/2069


External stage refresh gets skipped in snowflake

Describe the bug
I've yesterday created my external stage from gcs to snowflake.
The create steps seems to work properly and all the data is ready. Today the data needs a refresh but out of nowhere my external stage gets SKIPPED all the time
Steps to reproduce
`version: 2
sources:

name: gcs_external_stage
schema: external_stages
database: "{{ target.database }}"
tables:

name: table
external:
location: "@{{ target.database }}.schema.stage/path/table/"
file_format: '( type = json )'`

Expected results
I would expect that the data gets refreshed with the new data that landed in the gcs bucket
Actual results
1 of 1 SKIP
Screenshots and log output
dbt run-operation dbt_external_tables.stage_external_sources
Running with dbt=1.7.4
Registered adapter: snowflake=1.7.1
Found x models, x tests, 1 operation, x sources, 0 exposures, 0 metrics, x macros, 0 groups, 0 semantic models
1 of 1 START external source external_stages.table
1 of 1 SKIP
System information
The contents of your packages.yml file:
Which database are you using dbt with?

[ ] redshift
[x ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
1.7.4

The operating system you're using:
The output of python --version:
Additional context
3.10.7

https://getdbt.slack.com/archives/CJN7XRF1B/p1711403569740349
found this discussion


Switch turns off few seconds after turning on, guest WiFi remains active

HA Version: 0.104.3
Fritzbox-tools Version: 1.5.3
First of all thank for this component. İt's nice to see how well organized you guys are. 👍
Somehow my guests WiFi switch turns back off 2-3 seconds after I turned it on in Lovelace, but guest WiFi on the Fritzbox remains active.
Thanks in advance.

started to work again without me having changed anything. As suddenly as it stopped working. Not sure what is happening.

Strange. Thanks for coming back for the info, though.

I got this behaviour after upgrading to version 1.7.0 of this integration on my production system. I first assumed it was related to the update of fritzconnection.
On the first glimpse I don't see what might causing this.

I had same behavior:
the switch (lovelace) for the WLAN switches always (~every 30s) off despite it's on, and the switch for the guest-WLAN turns always on despite it's off.
I made a change in switch.py  FritzBoxWifiSwitch#_async_fetch_update and now it works as expected:
            _LOGGER.debug(f"WiFi {self._network_num} GetInfo:")
            _LOGGER.debug(wifi_info)
            self._is_on = wifi_info["NewEnable"] is True


Add ligature rendering

Add GSUB "liga" and "rlig" rendering support.
Solves #236, #230 and also #245.
Glyph rendering options are added to enable each GSUB feature individually.
Only "liga" and "rlig" are supported, and enabled by default as the spec suggests.
A "ligatures" checkbox is added to index.html.
Plus a small layout improvement to the glyph-inspector.
This is open for comments, especially on the options API :-)

Good job! Looks great and the options.features easy. I need to try this soon 👍
Performance-wise what did you found? Is it fast enough even with a lot of ligatures?

options.features looks perfect! Great job!

I haven't tested for performance, but it's probably very poor :-(
2 problems here:

there are so many types of substitutions, and so many ways to declare them in lookup tables, including multiple lookup tables, overlapping each other with duplicates... I'm a bit in the dark here, without a global comprehension including complex scripts and features.
you can't have the same data structures and algorithms for rendering speed (read-only) and ease of edition (list, add, remove...). Or if you can, it's really not obvious.

I chose to sacrifice perf in favor of a more general approach including font editing. The test fonts I used contained very few liga substitutions (about 10 max).

BTW I just noticed PR #228 already proposed a fix for #245.

@fpirsch I see!... No problem for the performance if it's good enough for a few substitutions but if it's really slow (reading) for big fonts we probably should note it somewhere and put an example to deactivate it. (Or deactivating it by default is an option too).

@fdb would you be OK for a merge & new release (including gh-pages for the online demo) ?

Sorry for the late reply. I'll make a release now.
The GitHub pages now come from master, so no the gh-pages branch is no longer needed.


Update forgot password mechanism to set a chosen password

Currently the forgot password mechanism generates a random password. This should be changed to an implementation where you can set a new password via a form which can be reached via a link in an email.

Resolved by #115


Display analysis UUID

Tasks

resolves #86

Status
Stable.
Changes

Added axios (npm, GitHub) as dependency to "promisify" compiler.loadSolcVersion() properly.
Refactored lib/client.js as we now need different data, depending on API interactions. Mage interactions more granular.
Refactored lib/controllers/analyze.js:

Now execution flow is largely flattened, also there is no more Promise and callback hells
Now we have only one spinner there instead of 3 diffrent spinners.
Added more spinnter messages to indicate execution stages more clearly. When error is encountered, current spinner message will be preserved, so we can narrow code segment, where error was triggered. Also, crucial execution stages will be preserved at screen:

Compiler loading (or downloading).
Compile status.
Analysis submission (including UUID).

Refactored lib/controllers/api-version.js to follow changes in lib/client.js.
Now text issue formatter will display N/A for issue titles, when API response contains issue with empty field.

Regards, @blitz-1306.

Nice work!


TikTok & Instagram embeds opening in browser on page load in iOS React Native

React version: 17.0.2
Package version: 2.2.2
iOS 16, works fine on Android.
We are using React Native's webview to serve our site, and when the page loads it automatically attempts to deep link into both TikTok & Instagram apps after the components mount.
https://user-images.githubusercontent.com/37327997/191157572-3fcea125-49de-4b2a-b371-3b2f5c845000.MP4

Solution was to add instagram & tiktok to React Native Webview's origin whitelist

I just started looking at this component. I'm wanting to embed TikTok and others into a react native app.  So - do I understand correctly that you're using react-social-media-embed in react from your web server into a react-native webview?

@magnum6actual i am looking to do the same thing. did you go with the same approach?


The Inventory Changer Tab is buggy

I'm using Windows 11 22H2. Everything seems to be normal until I click add item in Inventory Changer, the tab width keep increasing until it fit with the  monitor width which reallly strange and it made me feel so upset
Can anyone help me get through this?

I'm using Windows 11 22H2. Everything seems to be normal until I click add item in Inventory Changer, the tab width keep increasing until it fit with the monitor width which reallly strange and it made me feel so upset Can anyone help me get through this?

its normal i have that too just live with it lol

Fixed


Typo

pluralization of "sat" under Fungibility considerations
" === Fungibility considerations ===
Since any sat can be sent to any address at any time, SATS that are transferred, even those with some public history, should be considered to be fungible with other sats with no such history."

Nice, ty!


Env file created even when no environment variables are written

The library creates the env file for environment variables even when no snap options are set that lead to environment variable assignments.

A check of whether envVars is empty  or not could be added, before adding env vars to buffer and creating .env file os.WriteFile:
https://github.com/canonical/edgex-snap-hooks/blob/5f794f78f1030a335ff6876dc23a1c98f5bc46ee/options/env.go#L79-L89

The legacy options have the same issue. After installation, the logs shows the empty files being generated when app options is false.


reproduce linderman-lab HMM demos

This is to track the 'porting' of all  the HMM examples
from https://github.com/lindermanlab/ssm-jax/tree/main/notebooks

[x] arhmm-example.ipynb
[x] bernoulli-hmm-example.ipynb
[ ] factorial-hmm.ipynb
[x] gaussian-hmm-example.ipynb
[x] gaussian-hmm-sticky-transitions-example.ipynb
[x] poisson-hmm-example.ipynb
[ ] twarhmm-example.ipynb

Let's leave factorial (and time-warped ARHMM since it's a special case of factorial) for a future enhancement.


beacon communication between 2 galileo

Hi i am trying to connect two galileos using beacon but discover and adverting dont fing ench other... how can i use to communicate beetwhenn galileos? this is my code in both galileos:
var Bleacon = require('bleacon');
console.log("START");
var uuid = 'e2c56db5dffb48d2b060d0f5a71096e6';
var major = 0; // 0 - 65535
var minor = 0; // 0 - 65535
var measuredPower = -59; // -128 - 127 (measured RSSI at 1 meter)
Bleacon.startScanning();
console.log("start scaning");
//Bleacon.startScanning('e2c56db5dffb48d2b060d0f5a71096e0', 0, 0);
console.log("start adverting");
Bleacon.startAdvertising(uuid, major, minor, measuredPower);
Bleacon.on('discover', function (bleacon) {
console.log("discover");
console.log(bleacon);
});

@rabertol please provide debug output: sudo DEBUG=* node <file>.js
Also, do things work if you have one galileo scanning and the other one advertising?

Closing do to inactivity, please re-open with requested info.


npm ERR! missing script: clean

Following the steps in this tutorial results in the error below below whne using Build Clean or Rebuild Solution.  There is indeed to clean in package.json.  Should there be?  If it needs to be added what should the command be?  It isn;t clear that it is needed as the project builds and runs.
I am having a problem with breakpoints in debugging the TS code.  Will create a new issue for it if I can't figure it out.
------ Clean started: Project: NodejsWebApp1, Configuration: Debug Any CPU ------
npm ERR! missing script: clean
npm ERR!      C:\Users\joseo\AppData\Roaming\npm-cache_logs\2019-11-07T15_16_15_572Z-debug.log
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\Node.js Tools\Microsoft.NodejsToolsV2.targets(56,5): error MSB3073: The command "npm run clean" exited with code 1.
Done building project "NodejsWebApp1.njsproj" -- FAILED.
Build FAILED.
========== Clean: 0 succeeded, 1 failed, 0 sk

@joseogl  Thank you for the feedback.
Please add a link to the tutorial below and we will have this issue investigated further.

Closing the issue now, please comment below if there are still issues.


Added allStairs for pocketMaterials to allow MCEdit to load pocket edition levels

Copied and pasted the line that generates the stairs for alpha materials.
This allows MCEdit to load Pocket Edition worlds again.

Had it fixed locally, see the latest commits.  Thanks anyhow.


/livevideo/state does not work

On a single display configuration both play and stop do not have an effect on live video playback (using webcam)
debug: Sent OSC to <IP_ADDRESS>:10023 with /livevideo/state and [{"type":"s","value":"play"}]
debug: Sent OSC to <IP_ADDRESS>:10023 with /livevideo/state and [{"type":"s","value":"stop"}]

Yes, it's the same issue as #39.

Following 6.04c documentation this start/stop should be available

int response received with Songbeamer 6.04c update
system: ** Log cleared **
debug: Received OSC message from: {"address":"<IP_ADDRESS>","family":"IPv4","port":10023,"size":28}
debug: OSC Content is: {"address":"/livevideo/state","args":[{"type":"i","value":0}]}
warn: received a message with an unknown address - not implemented
debug: Received OSC message from: {"address":"<IP_ADDRESS>","family":"IPv4","port":10023,"size":28}
debug: OSC Content is: {"address":"/livevideo/state","args":[{"type":"i","value":1}]}
warn: received a message with an unknown address - not implemented

@Lasibian  - wrong response type?

Trying to change it with OSC doesn't work either ...

with 6.04c

[x] updates are send from songbeamer to OSC
[ ] stop change is applied using OSC?
[ ] start livevideo is applied?

[ ] Preset boolean only applied once changed in GUI once
[ ] change logic of action to include "should excecute" like others


Changing Time Values

I was wondering how to change cooldown times and request expire times. I tried changing the values in the source code itself and then restarting the bot, but that didn't seem to work

Hello! Normally you don't have to edit source code of the module by your own because you can provide configuration values as described in the README, like this:
const TicTacToe = require('discord-tictactoe');
new TicTacToe({ language: 'en', command: '!ttt', requestExpireTime: 5 })
  .login('YOUR_BOT_TOKEN')
  .then(() => console.log('TicTacToe bot is ready to be used.'));

Can you try like that? Or maybe can you send me your source code?

@ShreyasAyyengar Any news on that?

Re-open the issue if you still have the problem :+1:


Trigger global failure on shell error?

Is your feature request related to a problem? Please describe.
Is there a way to trigger a global halt of the workflow when a particular (shell) action fails instead of continuing with other rules? I have some actions that apply to the whole source location and if they fail it doesn't make sense to go on. It doesn't do much harm though.
Describe the solution you'd like
Something like a fail_globally attribute on the shell action:
    actions: # TODO fail completely when this fails
      - shell:
          cmd: pwsh -C "Write-Error this should stop everything"
          ignore_errors: false
          # HERE: Causes the whole workflow to stop on failure if an error happens and ignore_errors==false
          fail_globally: true

** Alternatives **
I'm hitting this because I have a rule that I want to run just once, so I use a filter to grab just the whole source folder as a way of executing the rule once. This is the rule I want to fail globally. I guess this is sort of a hack so maybe there's a better way.

Apologies again. I was confused. I realized the ignore_errors field is doing what I want, but when calling pwsh you have to explicitly pass out the exit code for it to make it up the chain.
 - shell: pwsh -c "exit 1"; exit %errorlevel%;

Reopening. Sorry to flip-flop on this one. After some more experience with the tool it looks like ignore_errors: false causes the actions for that rule to be skipped, but not for all rule processing to stop and organize to halt, which is what I was looking for. I've edited the description to include the python action and filter, which are similar.


[Improvement-3878][ui] Fixed the problem that custom parameters could not be edited and zk displayed abnormally when the workflow started

issues #3878

Codecov Report

Merging #4644 (0dea95e) into dev (ef0def3) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #4644      +/-   ##
============================================
- Coverage     44.75%   44.73%   -0.03%
+ Complexity     3356     3354       -2
============================================
  Files           538      538
  Lines         22996    22996
  Branches       2676     2676
============================================
- Hits          10293    10287       -6
- Misses        11784    11789       +5
- Partials        919      920       +1

Impacted Files
Coverage Δ
Complexity Δ

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...er/master/processor/queue/TaskResponseService.java
66.66% <0.00%> (-5.56%)
8.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-2.44%)
7.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


add open, close, read, write

Adds OPEN_FILE, CLOSE_FILE, READ_LINE, READ_CHAR, and WRITE IO functions. Since the read and write operations take in a file descriptor, I've also reserved numbers 0 1 and 2 to have their usual FD meaning, so users can print to stderr, read from stdin, etc.
Here's an example:
type IO_T:
  Done { magic, expr }
  Call { magic, func, argm, cont }

def IO_T/MAGIC:
  return (0xD0CA11, 0xFF1FF1)

def IO_T/wrap(x):
  return IO_T/Done(IO_T/MAGIC, x)

def IO_T/bind(a, b):
  match a:
    case IO_T/Done:
      return b(a.expr)
    case IO_T/Call:
      return IO_T/Call(IO_T/MAGIC, a.func, a.argm, lambda x: IO_T/bind(a.cont(x), b))

def call_io(func, argm):
  return IO_T/Call(IO_T/MAGIC, func, argm, lambda x: IO_T/Done(IO_T/MAGIC, x))

def main:
  do IO_T:
    * <- call_io("WRITE", (1, "what is your name?\n"))
    name <- call_io("READ_LINE", 0)
    * <- call_io("WRITE", (1, "Hello, '"))
    * <- call_io("WRITE", (1, name))
    * <- call_io("WRITE", (1, "'!\n"))

    file <- call_io("OPEN_FILE", ("testing.txt", "w"))
    * <- call_io("WRITE", (file, "Your name is: "))
    * <- call_io("WRITE", (file, name))
    * <- call_io("WRITE", (file, "!"))
    * <- call_io("CLOSE_FILE", file)

    return 42

Is that example right? Isn't it with instead of do?

@VictorTaelin That example was fixed in #369, it should be correct now

oh sure, my bad


Add "system uninstall" command

don't overwrite existing Istio installation

add new checks for install/uninstall to make sure namespaces aren't terminating

check that namespaces exist before uninstalling

change to use fmt.Printf instead of print

Fixes #625

There is an option of installing riff/Knative on a cluster that already has Istio installed. The new changes makes this possible by treating Istio as a separate dependency.
We are now skipping installation of Istio if the namespace already exists and we only remove Istio and istio-system namespace when using the --istio flag or user confirms the removal

Rebased and squashed changes

Thanks for doing this @trisberg - it will be really handy for testing or to cleanup between demos without blowing the entire cluster away.


[BUG/ISSUE] WingetUI isn't detected by Winget

I used Winget to install WingetUI on Windows 11. I believe this problem happened because WingetUI got installed in Portuguese

If you install it in English, does it get detected?

If you install it in English, does it get detected?

actually no

Upgrading from 1.4. does work?

I believe needs-author-answer tag is no longer needed

This seems fixed!

no, it is not.
I must change the installer program. bame

I thought this was fixed by https://github.com/martinet101/WingetUI/commit/0e07410a6d75aebc062e3027b70ddce250dc53ce

No, https://github.com/martinet101/WingetUI/commit/0e07410a6d75aebc062e3027b70ddce250dc53ce fixed issue with WingetUI failing to be updated from itself (cause winget was also running)


Close socketChannel in finally block

I think @hachikuji 's patch is more promising, for fixing KAFKA-6260