ERROR: Failed to download PIT file!

Debian Jessie SM-T320
heimdall print-pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

Galaxy S5, Heimdall v1.4.0, Debian jessy
sudo heimdall flash --recovery recovery.img --no-reboot --verbose                             21:33
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

With a build from the source I get this:
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 0100

iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...

Galaxy S5, Heimdall v1.4.0, Debian Jessie
I also get this problem. Completely unclear on how to resolve it at this point:
% heimdall print-pit --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8960"
            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

I am also getting the same errors on Debian Jessie with my Galaxy Note 3 (sm-n900p).

Same errors on v1.4.0 on Galaxy S5 on a Mac

I also reinstalled firmware and recovery through Odin, then tried to pull PIT from Heimdall, and still could not.

Same thing on Galaxy Note 4 (N910F) on 1.4.0. I tried a print-pit with --usb-log-level debug --stdout-errors --verbose and got the following:
$ sudo heimdall print-pit --usb-log-level debug --stdout-errors --verbose
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.000354] [00000513] libusbx: debug [libusb_get_device_list]
[ 0.001567] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x15000000
[ 0.001598] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.001602] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.001606] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0300
[ 0.001609] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0x09
[ 0.001612] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x00
[ 0.001616] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x03
[ 0.001619] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x09
[ 0.001622] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x05ac
[ 0.001625] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x8007
[ 0.001628] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0300
[ 0.001632] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x02
[ 0.001635] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x01
[ 0.001638] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.001642] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.001662] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.001676] [00000513] libusbx: debug [process_new_device] found device with address 128 port = 0 parent = 0x7f9eac104218 at 0x0
[ 0.002035] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14000000
[ 0.002058] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.002062] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.002065] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0200
[ 0.002068] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0x09
[ 0.002071] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x00
[ 0.002074] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x01
[ 0.002077] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x09
[ 0.002089] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x05ac
[ 0.002092] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x8007
[ 0.002095] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0300
[ 0.002098] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x02
[ 0.002101] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x01
[ 0.002104] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.002108] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.002127] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.002132] [00000513] libusbx: debug [process_new_device] found device with address 129 port = 0 parent = 0x7f9eac104458 at 0x0
[ 0.002490] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14800000
[ 0.002724] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.002734] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.002742] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0200
[ 0.002746] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0x09
[ 0.002749] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x00
[ 0.002752] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x00
[ 0.002755] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x08
[ 0.002758] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x0a5c
[ 0.002761] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x4500
[ 0.002764] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0100
[ 0.002767] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x01
[ 0.002770] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x02
[ 0.002773] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.002776] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.002797] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.002802] [00000513] libusbx: debug [process_new_device] found device with address 4 port = 8 parent = 0x7f9eac105068 at 0x7f9eac1043c0
[ 0.003225] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14100000
[ 0.004013] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.004021] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.004024] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0110
[ 0.004027] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0x00
[ 0.004030] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x00
[ 0.004033] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x00
[ 0.004036] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x08
[ 0.004038] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x047d
[ 0.004046] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x1020
[ 0.004049] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0100
[ 0.004052] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x01
[ 0.004055] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x02
[ 0.004058] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.004061] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.004080] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.004085] [00000513] libusbx: debug [process_new_device] found device with address 1 port = 1 parent = 0x7f9eac200788 at 0x7f9eac1043c0
[ 0.004419] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x15400000
[ 0.004498] [00000513] libusbx: warning [darwin_cache_device_descriptor] could not retrieve device descriptor 05ac:8406: no connection to an IOService. skipping device
[ 0.004513] [00000513] libusbx: debug [libusb_unref_device] destroy device 0.0
[ 0.004829] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14c00000
[ 0.005069] [00000513] libusbx: warning [darwin_cache_device_descriptor] could not retrieve device descriptor 05ac:0263: device not responding. skipping device
[ 0.005079] [00000513] libusbx: debug [libusb_unref_device] destroy device 0.0
[ 0.005392] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14830000
[ 0.005670] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.005679] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.005682] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0200
[ 0.005685] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0xff
[ 0.005687] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x01
[ 0.005690] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x01
[ 0.005693] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x40
[ 0.005695] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x05ac
[ 0.005698] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x8289
[ 0.005720] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0106
[ 0.005728] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x01
[ 0.005733] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x02
[ 0.005738] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.005751] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.005776] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.005781] [00000513] libusbx: debug [process_new_device] found device with address 6 port = 3 parent = 0x7f9eaad004a8 at 0x0
[ 0.006145] [00000513] libusbx: debug [process_new_device] allocating new device for location 0x14500000
[ 0.006353] [00000513] libusbx: debug [darwin_cache_device_descriptor] device descriptor:
[ 0.006363] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDescriptorType:    0x01
[ 0.006369] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdUSB:             0x0200
[ 0.006373] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceClass:       0x02
[ 0.006377] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceSubClass:    0x02
[ 0.006381] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bDeviceProtocol:    0x00
[ 0.006385] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bMaxPacketSize0:    0x40
[ 0.006389] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idVendor:           0x04e8
[ 0.006394] [00000513] libusbx: debug [darwin_cache_device_descriptor]  idProduct:          0x685d
[ 0.006398] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bcdDevice:          0x0100
[ 0.006401] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iManufacturer:      0x01
[ 0.006404] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iProduct:           0x02
[ 0.006408] [00000513] libusbx: debug [darwin_cache_device_descriptor]  iSerialNumber:      0x00
[ 0.006411] [00000513] libusbx: debug [darwin_cache_device_descriptor]  bNumConfigurations: 0x01
[ 0.006429] [00000513] libusbx: debug [darwin_check_configuration] active config: 1, first config: 1
[ 0.006435] [00000513] libusbx: debug [process_new_device] found device with address 15 port = 5 parent = 0x7f9eaaf0a5b8 at 0x0
[ 0.006499] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006502] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006504] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006507] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006509] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006511] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006513] [00000513] libusbx: debug [libusb_unref_device] destroy device 21.128
[ 0.006517] [00000513] libusbx: debug [libusb_unref_device] destroy device 20.129
[ 0.006520] [00000513] libusbx: debug [libusb_unref_device] destroy device 20.4
[ 0.006523] [00000513] libusbx: debug [libusb_unref_device] destroy device 20.1
[ 0.006527] [00000513] libusbx: debug [libusb_unref_device] destroy device 20.6
[ 0.006532] [00000513] libusbx: debug [libusb_open] open 20.15
[ 0.006861] [00000513] libusbx: debug [usbi_add_pollfd] add fd 6 events 1
[ 0.006868] [00000513] libusbx: debug [darwin_open] device open for access
[ 0.006883] [00000513] libusbx: debug [libusb_get_device_descriptor]
[ 0.006923] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.006931] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.006952] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.007044] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.007061] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.007069] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.007073] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.007085] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status 0
[ 0.007103] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaad00e30 has callback 0x10284d260
[ 0.007109] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=4
[ 0.007150] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.007155] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.007158] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.007253] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.007266] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.007270] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.007273] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.007280] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status 0
[ 0.007284] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac200080 has callback 0x10284d260
[ 0.007293] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=18
      Manufacturer: "Sasmsung"
[ 0.007351] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.007358] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.007362] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.007442] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.007458] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.007465] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.007468] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.007473] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status 0
[ 0.007476] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaaf0a650 has callback 0x10284d260
[ 0.007480] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=4
[ 0.007513] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.007529] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.007546] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.007648] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.007667] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.007673] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.007678] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.007685] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status 0
[ 0.007688] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaad00e30 has callback 0x10284d260
[ 0.007695] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=16
           Product: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1
[ 0.007707] [00000513] libusbx: debug [libusb_get_config_descriptor] index 0

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
[ 0.007740] [00000513] libusbx: debug [libusb_claim_interface] interface 1
[ 0.008044] [00000513] libusbx: debug [get_endpoints] building table of endpoints.
[ 0.008060] [00000513] libusbx: debug [get_endpoints] interface: 1 pipe 1: dir: 1 number: 1
[ 0.008091] [00000513] libusbx: debug [get_endpoints] interface: 1 pipe 2: dir: 0 number: 1
[ 0.008130] [00000513] libusbx: debug [darwin_claim_interface] interface opened
Setting up interface...
[ 0.008139] [00000513] libusbx: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0
[ 0.009753] [00000513] libusbx: debug [get_endpoints] building table of endpoints.
[ 0.009767] [00000513] libusbx: debug [get_endpoints] interface: 1 pipe 1: dir: 1 number: 1
[ 0.009772] [00000513] libusbx: debug [get_endpoints] interface: 1 pipe 2: dir: 0 number: 1

Initialising protocol...
[ 0.009799] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.009803] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.009807] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.009961] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.009979] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.009983] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.009986] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.009995] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.009998] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.010005] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac101840 has callback 0x10284d260
[ 0.010008] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: 1015088
[ 0.010054] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.010059] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.010064] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.010288] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.010305] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.010315] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.010319] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.010326] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.010331] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.010336] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac101840 has callback 0x10284d260
[ 0.010346] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: 1015088
[ 0.010389] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.010396] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.010410] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.010519] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.010542] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.010549] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.010552] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.010557] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.010560] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.010563] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaae00100 has callback 0x10284d260
[ 0.010569] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: 1031952
[ 0.010602] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.010612] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.010615] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.010731] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.010761] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.010767] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.010774] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.010782] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.010787] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.010790] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaaf0a650 has callback 0x10284d260
[ 0.010793] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: 990944
[ 0.010833] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.010836] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.010840] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.011028] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.011039] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.011043] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.011045] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.011050] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.011053] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.011056] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac200080 has callback 0x10284d260
[ 0.011059] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: 1032096
[ 0.011085] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.011089] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.011092] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.011250] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.011266] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.011270] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.011273] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.011277] [00000513] libusbx: debug [darwin_handle_callback] handling control completion with kernel status -536854449
[ 0.011280] [00000513] libusbx: debug [darwin_transfer_status] transfer error: pipe is stalled
[ 0.011283] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac200080 has callback 0x10284d260
[ 0.011286] [00000513] libusbx: debug [ctrl_transfer_cb] actual_length=0
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: 1032096
[ 0.011294] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
[ 0.011297] [00000513] libusbx: debug [ep_to_pipeRef] pipe 2 on interface 1 matches
[ 0.011322] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.011326] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.011329] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 0.011350] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 0.011373] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 0.011378] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 0.011381] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 0.011386] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status 0
[ 0.011389] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac200080 has callback 0x10284d452
[ 0.011392] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=4
[ 0.011399] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
[ 0.011403] [00000513] libusbx: debug [ep_to_pipeRef] pipe 1 on interface 1 matches
[ 0.011428] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 0.011431] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.011434] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 1.892201] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 1.892253] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 1.892259] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 1.892262] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 1.892268] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status -536854447
[ 1.892271] [00000513] libusbx: warning [darwin_transfer_status] transfer error: timed out
[ 1.892274] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaad00e30 has callback 0x10284d452
[ 1.892278] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
 Retrying...
[ 2.393332] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
[ 2.393350] [00000513] libusbx: debug [ep_to_pipeRef] pipe 2 on interface 1 matches
[ 2.393413] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 2.393424] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 2.393429] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 2.393450] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 2.393468] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 2.393479] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 2.393484] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 2.393490] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status 0
[ 2.393494] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaae00100 has callback 0x10284d452
[ 2.393497] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=4
[ 2.393505] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
[ 2.393508] [00000513] libusbx: debug [ep_to_pipeRef] pipe 1 on interface 1 matches
[ 2.393533] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 2.393537] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 2.393541] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 4.895199] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 4.895234] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 4.895240] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 4.895243] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 4.895248] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status -536854447
[ 4.895252] [00000513] libusbx: warning [darwin_transfer_status] transfer error: timed out
[ 4.895255] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaae00100 has callback 0x10284d452
[ 4.895258] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
 Retrying...
[ 5.650114] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
[ 5.650133] [00000513] libusbx: debug [ep_to_pipeRef] pipe 2 on interface 1 matches
[ 5.650201] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 5.650221] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 5.650227] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 5.650265] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 5.650292] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 5.650299] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 5.650304] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 5.650311] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status 0
[ 5.650315] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaaf0a650 has callback 0x10284d452
[ 5.650320] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=4
[ 5.650340] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
[ 5.650345] [00000513] libusbx: debug [ep_to_pipeRef] pipe 1 on interface 1 matches
[ 5.650381] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 5.650386] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 5.650391] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 8.897836] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 8.897863] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 8.897876] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 8.897881] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 8.897889] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status -536854447
[ 8.897895] [00000513] libusbx: warning [darwin_transfer_status] transfer error: timed out
[ 8.897912] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac101840 has callback 0x10284d452
[ 8.897919] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
 Retrying...
[ 9.902682] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
[ 9.902697] [00000513] libusbx: debug [ep_to_pipeRef] pipe 2 on interface 1 matches
[ 9.902737] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 9.902744] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 9.902750] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[ 9.902897] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[ 9.902924] [00000513] libusbx: debug [handle_events] poll() returned 1
[ 9.902931] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[ 9.902936] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[ 9.902944] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status 0
[ 9.902949] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eaac00120 has callback 0x10284d452
[ 9.902954] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=4
[ 9.902965] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
[ 9.902970] [00000513] libusbx: debug [ep_to_pipeRef] pipe 1 on interface 1 matches
[ 9.903001] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[ 9.903007] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 9.903024] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[12.899696] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[12.899750] [00000513] libusbx: debug [handle_events] poll() returned 1
[12.899759] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[12.899765] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[12.899775] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status -536854447
[12.899802] [00000513] libusbx: warning [darwin_transfer_status] transfer error: timed out
[12.899817] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac000330 has callback 0x10284d452
[12.899824] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
 Retrying...
[14.153918] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x01 to pipeRef and interface
[14.153946] [00000513] libusbx: debug [ep_to_pipeRef] pipe 2 on interface 1 matches
[14.154018] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[14.154028] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[14.154035] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[14.154120] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[14.154149] [00000513] libusbx: debug [handle_events] poll() returned 1
[14.154156] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[14.154162] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[14.154171] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status 0
[14.154177] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac101840 has callback 0x10284d452
[14.154184] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=4
[14.154198] [00000513] libusbx: debug [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
[14.154204] [00000513] libusbx: debug [ep_to_pipeRef] pipe 1 on interface 1 matches
[14.154239] [00000513] libusbx: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
[14.154246] [00000513] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[14.154251] [00000513] libusbx: debug [handle_events] poll() 2 fds with timeout in 60000ms
[15.901154] [00001007] libusbx: debug [darwin_async_io_callback] an async io operation has completed
[15.901185] [00000513] libusbx: debug [handle_events] poll() returned 1
[15.901191] [00000513] libusbx: debug [op_handle_events] checking fd 4 with revents = 0
[15.901194] [00000513] libusbx: debug [op_handle_events] checking fd 6 with revents = 1
[15.901200] [00000513] libusbx: debug [darwin_handle_callback] handling bulk completion with kernel status -536854447
[15.901204] [00000513] libusbx: warning [darwin_transfer_status] transfer error: timed out
[15.901207] [00000513] libusbx: debug [usbi_handle_transfer_completion] transfer 0x7f9eac101840 has callback 0x10284d452
[15.901211] [00000513] libusbx: debug [bulk_transfer_cb] actual_length=0
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response.

ERROR: Protocol initialisation failed!

ERROR: Protocol initialisation failed!

Releasing device interface...
[15.901258] [00000513] libusbx: debug [libusb_release_interface] interface 1

[15.901584] [00000513] libusbx: debug [libusb_close]
[15.901711] [00000513] libusbx: debug [usbi_remove_pollfd] remove fd 6
[15.901748] [00000513] libusbx: debug [libusb_unref_device] destroy device 20.15
[15.901761] [00000513] libusbx: debug [libusb_exit]
[15.901765] [00000513] libusbx: debug [libusb_exit] destroying default context

Closing as I believe this was resolved Feb 21st.


Timeline View navigation

Hello! The library is great, a lot of features!
I have a question: is it posible to use functions like "moveToPreviousMonth()", "moveToNextMonth()", or a function to move to certain date in the Timeline View?  I have tried but with no luck.
Thanks in advance, William!

Hello!
This is planned for a future upgrade.  I'm currently working on moving the project over to TypeScript, so I can have a more manageable code base, and allow greater integration into other frameworks.  Once this is done, the next phase is features like this.  For example, being able to specify your default view, all views updating when public functions are called.
For the moment though, the Month view is the source of truth for the project.  All views open using the Month date as the core date to display.
Thanks for using the project and stay tuned! Don't forget to like and share the project as well :)
Thanks
Will

Thank you, Will!
However, I found a solution using JQuery for anyone who need it:
$('.jump-to-date').find('input[type="date"]').val('2024-10-03'); // date in SQL format
$('.go').trigger('click');
Greetings!


Help with the carousel's initial load using useEffect()

Hi @davidcetinkaya,
Thanks so much for offering to help with this part, I know it's kinda outside of the scope of Embla specifically so you really don't have to hold my hand like this but it'd be much appreciated to learn how to configure this useEffect function.
Here's the Carousel.js component
import React, { useEffect } from 'react';
import { useEmblaCarousel } from 'embla-carousel/react';
import styled from 'styled-components';

const Wrapper = styled.section`
  height: auto;
  overflow: hidden;

  .is-draggable {
    cursor: move;
    cursor: grab;
  }

  .is-dragging {
    cursor: grabbing;
  }
`;

const Container = styled.div`
  display: flex;
  width: 100vw;
  justify-content: stretch;
`;

const CarouselWrapper = ({ children }) => {
  const [emblaRef, emblaApi] = useEmblaCarousel({
    loop: true,
  });

  useEffect(() => {
    if (emblaApi) {
      // Embla API is ready
    }
  }, [emblaApi]);

  return (
    <Wrapper>

        <Container className="embla__container">
          {children}
        </Container>

    </Wrapper>
  );
};

export default CarouselWrapper;

Then each slide is just a gatsby-image wrapped in a div from this CarouselSlide.js component.
export const CarouselSlide = ({ image, alt }) => {
  return (

  );
};

I hope that makes sense, let me know if I need to include anything else. I think I just need an example of what to put in the useEffect bit.
Thanks in advance
Dave

Hi Dave (@davemullenjnr),
If I understand what you want to achieve correctly, the idea here is to hide the carousel content until Embla Carousel has placed the slides in loop positions. This will hide the initial content jumping. Try something along these lines:
import React, { useEffect, useState } from 'react';
import { useEmblaCarousel } from 'embla-carousel/react';
import styled from 'styled-components';

const Wrapper = styled.section`
  height: auto;
  overflow: hidden;

  .is-draggable {
    cursor: move;
    cursor: grab;
  }

  .is-dragging {
    cursor: grabbing;
  }
`;

const Container = styled.div`
  opacity: ${({ $emblaHasMounted }) => $emblaHasMounted ? 1 : 0};
  transition: opacity 0.2s;
  display: flex;
  width: 100vw;
  justify-content: stretch;
`;

const CarouselWrapper = ({ children }) => {
  const [emblaHasMounted, setEmblaHasMounted] = useState(false);
  const [emblaRef, emblaApi] = useEmblaCarousel({
    loop: true,
  });

  useEffect(() => {
    if (emblaApi && !emblaHasMounted) {
      // Embla API is ready
      setEmblaHasMounted(true);
    }
  }, [emblaApi, emblaHasMounted, setEmblaHasMounted]);

  return (
    <Wrapper>

        <Container className="embla__container" $emblaHasMounted={emblaHasMounted}>
          {children}
        </Container>

    </Wrapper>
  );
};

export default CarouselWrapper;

Let me know if it helps.
Best,
David

Amazing! That's worked perfectly, thank you so much. It's now in production: hoodiehut.co.uk
That's great to see how it works, too. Really appreciate the help with this. 🙏

I'm glad it helped. The website looks awesome Dave (@davemullenjnr), thanks for sharing the link 🙂.
Kindly,
David

Hello again Dave (@davemullenjnr),
The new docs website is up. Take a look if you like: https://www.embla-carousel.com/.
Cheers,
David

Hey @davidcetinkaya,
The new site looks awesome! Really beautiful work. Huge fan of the simplicity and looks great in dark mode. 👏


First impressions

After trying the quickstart with a local minikube on xhyve, I have some feedback.
Getting started worked well. I'm concerned that I had to fill out credentials for docker hub, because I never want to push our code-base as a public docker container, and I'm not purchasing private docker storage. It would be better to ask me how I want to store container I create.
Neither the quick start guide, nor the "next steps" discuss how to add more services; when perusing the examples, you have a mysql+PHP example, which sort of is enough, but I can't find docs about multiple services from my own repo (which is what I need).
I can't find good information on why Helm is used in devspace. I can't find information about how to configure ingress or load balancing and networking (if any), nor how DNS and other infrastructure services work in devspace.
After playing around a bit: nice experience with the hot reloading, btw; I do devspace down, but it only removes tiller, not the deployed pod of the quickstart-nodejs app (as reported by kubectl get pods). There are no docs on how to remove the runtime artifacts from minikube/k8s. Also, our environment is gcloud; and there are no docs on how to use its hosted kube/hosted docker registry (instead of hub.docker.com).
As I wanted to kill everything started, and that didn't work, I try devspace up again, in the same quickstart folder. Now it fails with [FATAL]  Error deploying devspace: Error deploying devspace-default: Error creating helm client: Waiting for tiller timed out, after a few minutes.
Furthermore, reading your "about" link on your home page is broken. And in your ToS, the link to the Privacy Policy is broken. And there's nothing about you guys in the README, nor what you charge for. The ToS seems adapted for a monthly subscription service, but there's nothing on the site that specifies what you charge for. This uncertainty for me as a first-time user. I simply can't see if you're trolling me — selling of my laptop configuration to third parties — or if you're trying to create a sort of developers-cloud-service, like Hashicorp is trying to. (I had to resort to reading your code-base to verify that it's not bad code, before installing, especially since you have a curl-from-internet type of installation instead of a brew install devspace, like I'd expect a mature project to have)
I also chose a different namespace, since I run a few different projects on my minikube; chose devspace-sample as the ns. This was nicely written into the yaml-config file. However, when doing the up-down-up sequence of commands I mentioned above, tiller was deployed to both default and devspace-default.

What happened?
Bad onboarding experience
What did you expect to happen instead?
Better onboarding
How can we reproduce the bug? (as minimally and precisely as possible)
Do your own quickstart, do devspace down, then kubectl get pods.
Local Environment:

Operating System: mac
Deployment method: helm

Kubernetes Cluster:

Cloud Provider: minikube
Kubernetes Version:

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-30T21:39:38Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Hi @haf! Thanks for your detailed description. Our team highly appreciates your feedback.

I created several issues based on your input: #418 #420 #421
Regarding network configuration, I would recommend taking a look at the official k8s docs: https://kubernetes.io/docs/concepts/cluster-administration/networking/
Your issue with tiller timeout and devspace down/up should be resolved in release v2.4.1 (thanks for pointing us to this issue. That was really helpful!)
Our "about page" is currently being built, so it might take a couple of weeks until we add the correct links to the devspace-cloud.com website. Then, you will find more details about us and what drives us to build developer tooling for cloud native technologies.

I am sorry that we did not provide all the information you needed earlier but this is still a very young project. We work hard to improve it every day and there is a lot more to come in terms of documentation, step-by-step guides etc. I am closing this for now as we have the referenced issues but if you have any further input, feel free to open the issue again or join us on slack: http://slack.devspace-cloud.com


[Error] Can't find autoload.php after installation with GPM

Fatal error: require_once(): Failed opening required '/Users/Hugo/Localhost/bootqamp-pkg2/packages/markdown/core/components/markdowneditor/model/vendor/autoload.php' (include_path='.:') in /Users/Hugo/Localhost/bootqamp-pkg2/packages/markdown/core/components/markdowneditor/model/markdowneditor/markdowneditor.class.php on line 127

Vendor folder is not supposed to be there I think..?

http://theboxer.github.io/markdown-editor/contributing/#installation

Ok, so you mean you also need to build the package, after installing it with GPM? I thought that was the hard way.. ;)

no, you just need to run composer install to fetch dependencies

That did the trick, thanks.
Amazing, amazing work, also by @rthrash and anyone else that helped. This is premium stuff, am so happy with it!

:+1:


[Bug] Autocomplete variable stays after choosing a value

My testing minimal init.vim
Plug 'neovim/nvim-lsp'
Plug 'haorenW1025/completion-nvim'
...
require'nvim_lsp'.gopls.setup{on_attach=require'completion'.on_attach

How to reproduce
nvim main.go
fmt.<choose Print> - hint <CR>, ${1:} stays in code

Expected behavior
After choosing options from autocomplete and pressing  variable ${1:} should disappear.

I'll try to upstream with the changes in https://github.com/neovim/neovim/pull/12118. However be aware that it's not the perfect solution. If you want a proper snippets support to still need vim-vsnip and vim-vsnip-integ. Or if you doesn't want any snippet from LSP you can turn if off by
    require'nvim-lsp'.gopls.setup({
      on_attach=require'completion'.on_attach
      capabilities = {textDocument = {completion = {completionItem = {snippetSupport = false}}}};
    })

Please try #126 and see if it works for you.

Thank you, I will check it later, but the solutions with vim-vsnip and vim-vsnip-integ ars totally fine and, it solved this issue.

I've merged it. Feel free to open other issue if you ran into other problems:)

I'm still seeing this behavior, unfortunately, and I do have vim-vsnip and vim-vsnip-integ installed and loaded.

@wbthomason Hmm that's weird. Can you open another issue and show your minimal init.vim? Thanks:)

@wbthomason dose it actually stays after you choose an option and then hit enter?

@haorenW1025 @FL3SH I'm now having trouble replicating the issue post 22e46d3, though now I don't get any snippet expansion at all (i.e. I don't get the ${1:} markers, but - for example when completing a function call with clangd - the completion result has the argument names/signatures filled in and places the cursor after the call rather than placing the cursor inside the call to fill out the arguments I want to pass).
I'll try to get a better idea of what's going on and make a new issue if I can say anything useful.

@wbthomason Actually it is expected to not having the ${1:} markers now because that’s the behavior in the default Omni completion. In the commit you point out I just try to align to behavior. But still you should have snippets expansion with vim-vsnip because it doesn’t care what your insert word is, the information for snippets is stored in the user_data of complete-items.

Reference PR in Neovim core: https://github.com/neovim/neovim/pull/12118

@haorenW1025: Sorry, I’m a bit confused - you’re saying it’s expected to not get the snippet placeholders (which I understand), but then how should I trigger expansion for snippets from the LSP server?

The snippets information stored in user_data of complete-items(see :h complete-items), for vim-vsnip-integ it just reads out the user_data and expand it. in completion-nvim I have a CompletionDone autocmd that call the vim-vsnip-integ function so it will expand the snippets if you confirm the completion.

I can no longer reproduce this; both vim-vsnip and completion-nvim have had some updates since I was able to, so it seems that something in those changes fixed whatever my issue was. Thank you!


Add tests for RateLimitInfra

Description:
Improve code coverage for https://github.com/envoyproxy/gateway/pull/939 by adding more kubernetes based  integration tests

pls assign it to me


ngShowIf (Feature Request)

Abstract
If is often desirable to insert a directive's content upon first usage, and show/hide thereafter.
That is, have an ngIf behaviour once, and ngShow behaviour thereafter.
Current state of affairs
The two directives in question are:

ngIf - the directive inserts/removes the contents from the DOM. The directive also creates a new child scope upon each insertion (unfavourable behaviour at times, as it forces outside/inside communication to be based on objects, rather than primitives).
ngShow - the directive simply shows or hides the contents. It does not affect the scope.

The request
It would be useful to have a directive that inserts the contents first time its value turns true, and following that simply hides and show it.
Example
Consider a typeahead directive on an input field:
<input typeahead="...">

The directive reveals a dropdown with options and search matches, like so:

The initiation of the dropdown may be time-consuming and its existence on the DOM performance-consuming. The dropdown may:

Require an AJAX call to obtain the options (in case of remote search).
Involve watches.
Have to sort the returned options.
Each item (and depending on the programmer, there may be hundreds of them):

Require DOM listeners (eg, mousedown).
Involve a watch (eg, selected).

On a single form, there may be 10 fields with such typeahead directives. And the user may or may not open the dropdowns. When the form represents a new entry, the dropdowns are likely to be opened; but when editing/reviewing an entry, very few (if any) dropdowns will be open.
And so if one chooses:

ngIf - quite a bit of work will have to be done every time a dropdown opens (think AJAX requests); and due to the child scope, one has to take some extra step to ensure state preservation (eg, the query that was entered).
ngShow - we do a lot of work (10 typeaheds X 10 AJAX calls and many listeners and watches), which may not be needed at all.

A directive that inserts on the first show but show/hide thereafter would solve this.
Code
ngIfShow
Here's a code for and ngIfShow directive, essentially a slimed-down marrige between ngIf and ngShow. As it uses transclude the inside scope is a sibling scope (which quite a few people aren't happy with).
.directive( 'ngIfShow', ['$animate', function($animate) {
  return {
    multiElement: true,
    transclude: 'element',
    priority: 600,
    terminal: true,
    restrict: 'A',
    link: function (scope, element, attr, ctrl, transclude) {
        var rendered = false,
            iClone;
        scope.$watch(attr.ngIfShow, function ngIfShowWatchAction(value) {

          if (!rendered){
            if (value) {
              transclude(function (clone, newScope) {
                iClone = clone;
                clone[clone.length++] = document.createComment(' end ngIfShow: ' + attr.ngIfShow + ' ');

                $animate.enter(clone, element.parent(), element);
                rendered = true;
              });
            }
          } else {
            $animate[value ? 'removeClass' : 'addClass'](iClone, 'ng-hide');
          }
        });
    }
  };
}])

ngShowIf
The following directive does the same thing, but behaves more like ngShow in that it does not affect the scope:
.directive( 'ngShowIf', [ '$compile', '$animate', function( $compile, $animate ) {
    return {
        priority: 600,
        terminal: true,
        restrict: 'A',

        compile: function compile( tElement, tAttributes ) {
            var iContents = tElement.html();
            tElement.empty();

            return function postLink( scope, element, attrs, controller ) {
                var iClone = false;

                scope.$watch( attrs.ngShowIf, function ngShowIfWatchAction( doShow ) {
                    if ( !iClone ) {
                        if ( doShow ) {
                            iClone = $compile( iContents )( scope );
                            $animate.enter( iClone, element );
                        }
                    } else {
                        $animate[ doShow ? 'removeClass' : 'addClass']( iClone, 'ng-hide' );
                    }

                });
            };

        }
    };
}])

I think the discussion has shown that there's not much chance this will be included into 1.x. Regarding the initial performance of many ngIf's, https://github.com/angular/angular.js/pull/12078 seems to address this in a more general way.


Don't try alternate path for tessdata

This simplifies the code and the user interface.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

@egorpugin, do you have an idea why AppVeyor CI fails since 24 days? The build complains about missing dirent.h.

@stweil
Are alternate paths required for handling how tessdata files are packaged under Linux.
I think it is
/usr/share/tesseract-ocr/4.00/tessdata
The old version might have been without the extra subdirectory 4.00

A path like /usr/share/tesseract-ocr/4.00/tessdata needs special handling during the build in any case. If the build had used /usr/share/tesseract-ocr/4.00, then this has to be changed to /usr/share/tesseract-ocr/4.00/tessdata.
By the way: @jbreiden @AlexanderP, do we really want to keep that path for the new Debian packages, or should be switch to /usr/share/tesseract-ocr/4.0/tessdata or even  /usr/share/tesseract-ocr/4/tessdata (and hope that Tesseract will use semantic versioning soon)?

The path /usr/share/tesseract-ocr/4.00 was chosen to avoid conflict when installing libtesseract3, which I had.
If necessary it can be changed.

@AlexanderP
Since the format of old traineddata and 4.0 traineddata is different, it makes sense to have a separate directory for the 4.0 files.
I think @stweil is suggesting using 4.0 or 4 instead of 4.00 as the subdirectory name.

Yes, exactly.

I got it.
It is necessary to wait for the answer @jbreiden

I have no preference between 4 4.0 and 4.00.  I am a little worried because the Ubuntu 18.04 freeze date is in 8 days. This would be a pretty major change and if we mess it up, there might not be enough time to recover.
https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule

Basically "now or never" if we want to change this for Ubuntu. With some risk if we attempt it.

Ubuntu 18.04 freeze date is in 8 days.

@jbreiden  traineddata for CJK and thai should also be updated before that - see
https://github.com/tesseract-ocr/tessdata_fast/pull/7
https://github.com/tesseract-ocr/tessdata_fast/pull/8

As we have libtesseract3 and libtesseract4, using 4 would be logical for me. That also fits both for semantic versioning and for the current versioning.

An unrelated question:
The new Debian tesseract-ocr uses package names for traineddata in two different forms, for example tesseract-ocr-deu and tesseract-ocr-script-frak. While the first description "tesseract-ocr language files for German" seems fine, I do not understand the description "tesseract-ocr script files for Fraktur". What are "script files"? Who has a better description? When looking closer on the descriptions, both should use the singular, as there is only a single traineddata file.

traineddata for CJK and thai should also be updated before that

@zdenop, that requires merging the related pull requests sent by @Shreeshrii first.

Script in the linguistic sense. It means not trained to a specific language. tesseract-ocr-script-frak is good for Fraktur writing whether Dutch or German.
As for 4 that is a good choice, but do you think it is important enough to be worth the risk?

So the description should be "tesseract-ocr file for Fraktur script".
I think the risk of fixing the path is low. A valid test only requires building the packages locally, installing them on a machine without any other relicts from previous tesseract experiments and running tesseract --list-langs there.

As we have libtesseract3 and libtesseract4, using 4 would be logical for me. That also fits both for semantic versioning and for the current versioning.

@jbreiden What will be tesseract version as per Debian/Ubuntu release? Is it still 4.00alpha?

description should be "tesseract-ocr file for Fraktur script" or maybe even better "tesseract-ocr data for Fraktur script".

I agree.  eg. for Devanagari script can be used for Hindi, Sanskrit, Marathi, Nepali  languages.
"tesseract-ocr traineddata file for Devanagari script" describes the package better than "tesseract-ocr script files for Devanagari"

Should some of the supported languages also be listed as part of description? There was a question sometime back regarding lat language and Latin script traineddata files.
eg. for https://packages.debian.org/sid/graphics/tesseract-ocr-script-deva
This package contains the data needed for processing images in a particular script (e.g. Hindi, Sanskrit, Marathi, Nepali  languages written in Devanagari script).

Please see related PR https://github.com/tesseract-ocr/tessdata_fast/pull/6/files
It includes Ray's description of the script level files.
+Initial capitals indicate the one model for all languages in that script.
+
+**Latin** is all latin-based languages,
+except vie, which has its own **Vietnamese**.
+
+**Devanagari** is hin+san+mar+nep+eng
+
+**Fraktur** is basically a combination of all the latin-based languages that have an 'old' variant.
+
+Most of the script models include English training data as well as the script, but not for **Cyrillic**, as that would have a major ambiguity problem.
+

I updated the description in the rules.
https://github.com/AlexanderP/tesseract-lang-debian/commit/61c6150f90c3fc7a7698f6f71a06b9fd347aa055
I'm waiting for suggestions.

For ubuntu lts packages are taken from Debian testing. Packages will switch
from sid to testing after 6 days, after loading into the sid. how long it
takes to synchronize from Debian testing to ubuntu, I do not know. We have
very little time, and there is a chance not to be in time.
At a minimum, need to update tesseract-lang.
it is necessary to make a decision.
22 февр. 2018 г. 10:22 пользователь "Stefan Weil"<EMAIL_ADDRESS>написал:
@AlexanderP https://github.com/alexanderp, do you think that changing the
tessdata path from /usr/share/tesseract-ocr/4.00 to
/usr/share/tesseract-ocr/4 is still possible before the Ubuntu deadline
(see discussion above)? I could help with testing or send pull requests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/pull/1328#issuecomment-367589746,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK8HYW4Vchlgbsxnq7p3Ac5HQrdWjQzks5tXRWogaJpZM4SLAQO
.

Basically "now or never" if we want to change this for Ubuntu. With some risk if we attempt it.

I'm afraid "now" is passing by, and we will have to live longer with 4.00.

I do not think that this is a big problem ... It will be possible to change the prefix before the release 4.0, and at any time.

Attempting official packages updates tonight. Trying to read and understand all the discussion...

@stweil @Shreeshrii Please look at Alexander's changelog and tell me if you see any trouble. For example, a commit that was reverted.
https://github.com/AlexanderP/dsc-file/blob/master/debian-tesseract/changelog

@jbreiden Thanks!
I updated tesseract-lang in PPA.
https://github.com/AlexanderP/tesseract-lang-debian/commit/ec69f6db6a6ddd138f1f21351654d0bd9347d8c3
repositories for rules
https://github.com/AlexanderP/tesseract-debian
https://github.com/AlexanderP/tesseract-lang-debian

There is probably no time left to fix mistakes, but if someone notices a horrible problem, please tell me right away.

@jbreiden, I don't see why you can't fix mistakes after March 1st according to the Ubuntu release process.
https://wiki.ubuntu.com/UbuntuDevelopment/ReleaseProcess
https://wiki.ubuntu.com/BetaProcess
https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule

March 1st FeatureFreeze, Debian Import Freeze
March 8th Beta 1 Freeze (for opt-in flavors; Monday), Beta 1 (for opt-in flavours)
March 29th DocumentationStringFreezep
April 5th Final Beta Freeze (Monday), Final Beta

@AlexanderP    @jbreiden
The list of languages in https://github.com/tesseract-ocr/tesseract/blob/
master/doc/tesseract.1.asc is NOT complete.
I just noticed this. It says:
There are currently language packs available for the following languages (in
 https://github.com/tesseract-ocr/tessdata):

That should be changed to tessdata_fast.
The list should add all the new languages and scripts. I see the list in
https://github.com/AlexanderP/tesseract-lang-debian/blob/
master/debian/lang.sh
It might be easiest for either you or Alex to update this based on
https://github.com/AlexanderP/tesseract-lang-debian/blob/master/debian/lang.txt
and
https://github.com/AlexanderP/tesseract-lang-debian/blob/master/debian/script.txt

I have create a PR - for the language list. Please see
https://github.com/tesseract-ocr/tesseract/pull/1343
ShreeDevi

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com
On Fri, Feb 23, 2018 at 2:22 PM, ShreeDevi Kumar<EMAIL_ADDRESS>wrote:

@AlexanderP    @jbreiden
The list of languages in https://github.com/tesserac
t-ocr/tesseract/blob/master/doc/tesseract.1.asc is NOT complete.
I just noticed this. It says:
There are currently language packs available for the following languages
(in https://github.com/tesseract-ocr/tessdata):

That should be changed to tessdata_fast.
The list should add all the new languages and scripts. I see the list in
https://github.com/AlexanderP/tesseract-lang-debian/blob/mas
ter/debian/lang.sh
It might be easiest for either you or Alex to update this based on
https://github.com/AlexanderP/tesseract-lang-debian/blob/
master/debian/lang.txt
and
https://github.com/AlexanderP/tesseract-lang-debian/blob/
master/debian/script.txt

We at the time limit, and I do not dare make any more changes.  As @AlexanderP explained, the packages flow from Debian Unstable -> Debian Testing -> Ubuntu. If everything works perfectly, we will just barely meet the deadline. You can watch the flow on the dashboards.
https://tracker.debian.org/pkg/tesseract-lang
https://tracker.debian.org/pkg/tesseract

Thank you to both of you!

Thank you all for your efforts to get it packaged to make it easily
accessible to a large number of users.
Some related and unrelated questions...

Will this be marked by a tag/release in the repo so that other packagers
eg. Mac, msys2 etc can also update their distributions?

Till now the recommendation to get latest version of tesseract was to
build from source. Now, thanks to Alex and Stefan, we have PPA for Ubuntu
and windows binaries.

Should the wiki be changed to give these priority over building from source?
@stweil, could you also build a Mac/osx version?

could you also build a Mac/osx version?

I plan to build one this week.

@stweil Thanks! Please also look at the addition of tessdata in dirname issue.

Please also look at the addition of tessdata in dirname issue.

@Shreeshrii , could you please test whether #1356 fixes that?

@stweil Yes, seems to be ok now after #1356.

Should the wiki be changed to give these priority over building from source?

I have made some changes to https://github.com/tesseract-ocr/tesseract/wiki

@AlexanderP Please update the PPAs to include #1356. That completes the tessdata_prefix related changes from this PR.

@Shreeshrii done


Is there a way to patch the cmdline.txt

I'm trying to modify cmdline.txt during the build phase but I'm struggling to find where cmdline.txt is generated. Can anyone point me in the right direction?
I'm mostly looking to change the console output to a different port so it doesn't show up during boot, i.e.
dwc_otg.lpm_enable=0  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait   logo.nologo
to
console=ttyAMA1 dwc_otg.lpm_enable=0  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait   logo.nologo

It gets generated here: https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-kernel/linux/linux-raspberrypi.inc#L139
You could overwrite the default value defined in the same recipe https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-kernel/linux/linux-raspberrypi.inc#L30 by using a bbappend, local.conf etc.

@agherzan Thanks! That's exactly what I was trying to find.


Use jgit 4.5.3

Fix exception handling for opening bitmap index files.
Unlikely to be detected in common Jenkins usage, but better to run the
current released version for those cases where it might be found.
See https://projects.eclipse.org/projects/technology.jgit/releases/4.5.3
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

Belated 🐝


Add column for comments to words

Subject to testing, this is https://github.com/Anaphory/lexibank/commit/4e717d829517737af532087b672f4c052a97ecce

@klamermaf In addition to a lot of nans instead of empty comments (that's for me to sort out), several of the comments are obviously not written for public display and will need cleanup. I have made a note of that in https://github.com/lessersunda/lexirumah-data/issues/18.

The column is now online. See for example http://localhost:6543/parameters/000#8/-9.193/124.801 in Teiwa-Lebang.

(Some of the comments in “Sky” need to go into the reference metadata, because they apply to the whole word list, not to some entry in it.)

Hi Gereon
I looked through the comments for sky, and for some other items. Fortunately not too much work:

"nan" can go everywhere.
The comments in the cell for 'sky' which relate to transcriptions can all go as well. There are just 7 cells in the comments for 'sky' that should be made empty because they contain statements about the transcription.

(They are kept in the original excel sheets with field notes so will not be lost).
Marian

From: Gereon Kaiping<EMAIL_ADDRESS>Sent: Friday, June 09, 2017 5:39 PM
To: Anaphory/lexibank
Cc: Klamer, M.A.F.; Mention
Subject: Re: [Anaphory/lexibank] Add column for comments to words (#22)
The column is now online. See for example http://localhost:6543/parameters/000#8/-9.193/124.801 in Teiwa-Lebang.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Anaphory/lexibank/issues/22#issuecomment-307423652, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVkOKE7-d2P_Yztx1Lajvpmw4fFDnGxOks5sCWdDgaJpZM4Nyv3C.


pending changes

remove private / shared palette separation, instead always carry entries forward
think about a less invasive palette reset than RIS/DECSTR (maybe hook into some XTSMGRAPHICS action)
properly define and document default palette as VT340 (lower 16 colors) + ANSI256 (up to 256) + zeroed (up to 4096)
remove other default palettes to shrink package size
transit to VT340 cursor positioning, remove all others for sixels
update tests & docs regarding changes
check if worker loop is properly guarded against malicious sixel data

So what was the story around https://github.com/xtermjs/xterm.js/pull/2503 ? I was so excited that almost everything was working, and then it seemed they abruptly pulled the plug.  Will they never ship sixel?  Or they might someday, just not anytime soon?
Is it OK if I point other JS devs looking for sixel this way?

I stalled the PR over there mostly due to time constraints. The PR grew really big over a quite long time, which makes it harder and harder to merge in. Furthermore its maintenance is not easy, as it uses many internal private symbols for the buffer and output interaction. In fact that code belongs into core some day, such a heavy lifting should not reside on an addon. But we never made it to that point, mainly because the whole image story is still uncertain ground in terminals and still might see more than one groundbreaking shift. All in all - no good conditions to be moved into core.

Is it OK if I point other JS devs looking for sixel this way?

Sure. Well the sixel lib has still a few issues on the decoder, but in general should do its job. The encoder is not yet wasm optimized, which has no priority on my end (just added it to have support in both directions).

I'm working on DOOM inside terminals now.  Would you be interested in me testing against xterm.js with this?  Perfectly fine if not, I do not want to create uninteresting work for you. :)  If you are interested, is there a recommended way to get xterm.js + xterm-addon-image working with a local shell?
Also:

transit to VT340 cursor positioning, remove all others for sixels

Is this about DECSDM?  I'm using that now for rendering to the bottom text row (when the that location is within 1000x1000 of the top-left, due to xterm limits).  If so, there is an odd interaction with transparent-images-over-old-images, as seen here.  This behavior currently affects wezterm and DomTerm.

@klamonte Sure, feel free to play around with it. This what you would need:

recent nodejs on your machine (imho v12 or v14 should do) with yarn installed
then call contents of bootstrap.sh
switch to xterm.js repo folder
run yarn start
open localhost:3000 with your browser (should be recent chrome/firefox/safari)

DECSDM is correctly support as far as I had tested it. The cursor positioning currently follow the right-or-below semantics (thats more like term would do it), which is subpar, compared to VT340's mode (always at first image column of the last image row). This needs to be changed before it can get release.
Since you play around with transparent composition, thats also not yet done in the addon. Planned for second alpha version.

I can't get it to work on Debian.
After installing:
nodejs
yarnpkg
webpack
node-express

Then (after aliasing yarn=yarnpkg):
yarn add express-ws

I get:
yarn add v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/2] ⠄ node-pty
error /home/autumn/t/xterm-addon-image/xterm.js/node_modules/node-pty: Command failed.
Exit code: 1
Command: node scripts/install.js
Arguments:
Directory: /home/autumn/t/xterm-addon-image/xterm.js/node_modules/node-pty
Output:
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: spawn node-gyp ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
    at onErrorNT (internal/child_process.js:470:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
    at onErrorNT (internal/child_process.js:470:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn node-gyp',
  path: 'node-gyp',
  spawnargs: [ 'rebuild' ]
}
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this comm

Based on the stack trace, something in there thinks it is running on Windows.
Any tips?

This looks like node-gyp is missing, hmm. How did you install nodejs? On ubuntu I never use the node packages from the distro repo, as they are broken in several ways, maybe thats the issue here?
For me the deb packages from here https://github.com/nodesource/distributions/blob/master/README.md always worked (take v14 as node-pty has issues with v16).

Yes Firefox is slower in WASM execution than Chrome, but 30 kb/s? Thats 500 times lower than I would expect, for Firefox I saw ~22 MB/s, while Chrome was around 41 in my tests. Whats the pixel size of a single frame from the doom output?
Are you sure that there is nothing else slowing down things? If you care enough, maybe open devtools-->performance in Chrome and record for a few seconds, while sixels are streamed. Then after stopping, check the tab "Bottom-Up" down below. I am pretty sure, that something else is going on here.

Oh I'm sure something else is going on too. :)  I'm sorry if it looked like I was saying your code is slow, I know it's very fast.  I just wanted you to see it, and if you want to play with it too you know where to look.

@klamonte Are there instructions anywhere how to get that DOOM thingy up and running?

@jerch
git clone https://gitlab.com/klamonte/xtermdoom.git
cd xtermdoom
ant jar
cp /path/to/doom1.wad doom1.wad
./run_xterm.bash

Some more discussion (I sort of threadjacked oops!) at: https://codeberg.org/dnkl/foot/issues/481#issuecomment-363377

@klamonte
Oh wow - not sixel is eating the precious CPU time, its the canvas renderer drawing uncached glyphs. Thats weird, somehow the glyph cache is not working for your chars. I suspect, that the runtime is also pretty bad without any sixel stream in between. This needs investigation...

@klamonte WezTerm is at ~35 FPS for me.

A couple things that may improve you for now: ...

Will try that tomorrow. All in all, this looks really promising, well done :smiley_cat:

@jerch

Thats weird, somehow the glyph cache is not working for your chars. I suspect, that the runtime is also pretty bad without any sixel stream in between. This needs investigation...

Jexer is unique in its sixel output strategy.  It emits images first, then text, and expects the text to destroy the image.  The images are also 1 row high and I think they might be doing like 10 cols max.  So lots of intersecting sixel and text.
Oh, and when multithread is enabled the sixel images are produced in whatever order the thread pool gets to them, so there will be lots of "place->sixel->place->sixel->..." and then "place->text->place->text->...".
Don't know if that helps or not.  🤷♀

Here are some results:

The canvas renderer currently does not cache RGB colors in FG/BG, thats the reason, why it bails out to uncached drawing. When I wrote the RGB extension for the buffer, the renderer got not fixed the same way, as that renderer was meant to be removed soon. Well it is still the default renderer, with uncached RGB path :smiley_cat:. Is there an easy way to set different FG/BG colors?
jexer.ECMA48.sixelPaletteSize=256 runs worse for me. I have no clue yet why (sixel decoding takes only 130ms of 5s runtime), but the browser jumps to 120% load. My suspect is the sheer amount of messages, which might create very high load for the message handling in the browser itself. Also the worker does not help here much, as the messages are still very small but many, which stalls the parser chain often with stack unwinding (thats quite costly). Imho you trigger here an edge case, where the sixel decoding would be better done in the main thread (not tested yet).

Oh, and when multithread is enabled the sixel images are produced in whatever order the thread pool gets to them, so there will be lots of "place->sixel->place->sixel->..." and then "place->text->place->text->...".

Thats prolly the reason why I see that such worse browser load with jexer.ECMA48.sixelPaletteSize=256. The context switches for sixel/text are quite expensive due to the internal worker setup (its kinda a "long line", I have no cheap memory mapping in place, SABs are a nightmare to use since spectre/meltdown).
I might try to run this with a non-worker based version (sixel decoding done directly in the mainthread), which should remove alot of the messaging overhead. But thats not a viable solution for xterm.js in general, as it makes the mainthread busy up to perceivable stalls for bigger images.

Yes indeed, with a non-worker variant everything runs smooth with jexer.ECMA48.sixelPaletteSize=256 at 55 FPS. Congrats - for finding the bottleneck of the worker approach :see_no_evil:
So here are the profiler numbers for that non-worker variant of a 6s record:

It shows, that the sixel decoding took only 5% of the runtime (thats the wasm-function[9] entry there). Most time was spent on putImageData. Also the second entry Major GC results from that for 80%. In summary 35% of the runtime is spent on the 2d canvas creation, which could be made much faster with a webgl canvas.

I think DOOM itself maxes at 60 FPS, as that is the same limit foot found.
You can eliminate the RGB by commenting out the getTheme().setFemme() line in src/xterm/XtermDOOM.java .

The canvas renderer currently does not cache RGB colors in FG/BG, thats the reason, why it bails out to uncached drawing. When I wrote the RGB extension for the buffer, the renderer got not fixed the same way, as that renderer was meant to be removed soon. Well it is still the default renderer, with uncached RGB path smiley_cat.

I used to cache RGB, and then notcurses-demo crashed me. :-)
https://gitlab.com/klamonte/jexer/-/issues/85

"subscribe"
(Hi @jerch, this is my new account.)

(Hi @jerch, this is my new account.)

WB! And no worries, I have not forgotten about the original topic (yet), but still have other things to do before I can get back to it. I even might introduce an optional worker setup setiing to work around the issue found above (so peeps can decide on their own, whether to use worker-based or mainthread-based decoding, depending on their integration needs).

Dealt with in several PRs.


Expanding Border

Add Expanding Border Button - Animation Button

Issue: I'm not sure this is what you expected. Please review this

I'm testing it again now and I noticed a problem that appears in dark mode well. For some buttons that border is inside the button (meaning you can still see red (or the button's color) from ourside the border). It's not apparent in light mode but can you look into it (as we don't know how anyone might use it).

I'm testing it again now and I noticed a problem that appears in dark mode well. For some buttons that border is inside the button (meaning you can still see red (or the button's color) from ourside the border). It's not apparent in light mode but can you look into it (as we don't know how anyone might use it).

Sorry I'm not test on dark mode yet. I will check it out

After get some diggin, I found the trick to make it better.. check it out

Great thanks!


chore: prepare fastapi-sqla to be compliant with sqlalchemy 2.0 - DIA-40134

Description

Prepare fastapi-sqla to be compliant with SQLAlchemy 2.0;
Run tests with SQLALCHEMY_WARN_20 environment variable;
Fix sqla and pytest warnings;

Related JIRA issues

DIA-40134

Related PRs

Thanks! Exciting stuff, I'm really looking forward SQL Alchemy 2.0 and especially psycopg3.


在gradio的demo上不管跑什么模块，终端始终都报同样的错误。

在gradio的demo上不管跑什么模块，终端都报同样的错误。
Traceback (most recent call last):
File "/mnt/ai212/workspace/dengtb/anaconda3/envs/ichat/lib/python3.8/site-packages/gradio/routes.py", line 414, in run_predict
output = await app.get_blocks().process_api(
File "/mnt/ai212/workspace/dengtb/anaconda3/envs/ichat/lib/python3.8/site-packages/gradio/blocks.py", line 1323, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "/mnt/ai212/workspace/dengtb/anaconda3/envs/ichat/lib/python3.8/site-packages/gradio/blocks.py", line 1257, in postprocess_data
prediction_value = block.postprocess(prediction_value)
File "/mnt/ai212/workspace/dengtb/anaconda3/envs/ichat/lib/python3.8/site-packages/gradio/components.py", line 4629, in postprocess
assert isinstance(
AssertionError: Expected a list of lists or list of tuples. Received: None

Could you mind sharing more information like environment and start command about this issue?
We also need the your operation steps, so that we can reproduce your problem.

same error

same error. Do you solved it?


Fetch etcd 3.5.5 for macOS M1 support

etcd didn't start supporting macOS ARM chips until their 3.5.5 release. This pull request updates the version of etcd to 3.5.5 in order to build etcd for all archs.
Signed-off-by: Iheanyi Ekechukwu<EMAIL_ADDRESS>

Thank you for the contribution!


Scripts Calling Other Scripts

Add support for scripts being able to call other scripts.

Closing this as we've de-emphasized the role of scripts.


add deserialize_time metric and fix body_read_time

avoids lumping these two parts of response processing together

I would suggest adding the gzip time for completion

it's fairly difficult to do that without pulling a fair bit of code from undici into here but I will look into it

I think we can only easily measure that for the request encoding, but I think worth adding

Timebox for the response... just would mean we can completely rule it out in 1 RT

I don't think it's possible to do this without rewriting the http client with a lower level API


Node Error: Module version mismatch

It's highly likely it's my environment problem but I couldn't seem to find a solution.
I recently upgraded Node to version 4 and try to run some test on the master branch and ran into this error:
~/grpc$ node src/node/test/math/math_server.js
module.js:434
  return process.dlopen(module, path._makeLong(filename));
                 ^
Error: Module version mismatch. Expected 46, got 14.
    at Error (native)
    at Object.Module._extensions..node (module.js:434:18)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/usr/local/google/home/stanleycheung/grpc/src/node/src/grpc_extension.js:38:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
stanleycheung@gummybear:~/grpc$ which npm
/usr/local/google/home/stanleycheung/.nvm/versions/node/v4.4.2/bin/npm
stanleycheung@gummybear:~/grpc$ which node
/usr/local/google/home/stanleycheung/.nvm/versions/node/v4.4.2/bin/node
stanleycheung@gummybear:~/grpc$ npm -v
2.15.0
stanleycheung@gummybear:~/grpc$ node -v
v4.4.2

I removed the entire node_modules folder and re-ran npm install on the root grpc directory

If you change the Node version you have to explicitly update the gRPC binary by doing npm install --update-binary

Yes, that solved my problem. Thanks!


Local validation for forked PRs

Instead of splitting the validate.yml file, this PR introduces a streamlined approach to handle validation tasks based on the pull request lifecycle.

When a PR is opened:

Local validation tasks will run immediately, ensuring the changes meet the necessary checks that do not require secrets.

When the PR is merged:

Validation tasks that require secrets will execute, ensuring sensitive operations are secure and only run after the PR is approved and integrated into the main branch.

Thanks for opening a PR!
I am not sure if the changes here are an improvement, however, since this removes full validation from PRs, so the validated URL can still be invalid/unreachable even if the PR is opened from this repository (which means it is already fine to trust the author, if they want the secret they already can push random changes to the main branch to get it)

Whoever opens a PR (whether from this repository or a fork) will need to go through the same validation process, correct? Could you please elaborate on what you mean by "better validation"?

Whoever opens a PR (whether from this repository or a fork) will need to go through the same validation process, correct

The idea is that they don't. Those with write access can open a PR from a branch of this repo and get extra validation of the links (e.g. post is reachable) and that the rich text can be expanded properly.  Those without write access and have to open a PR from their forks will not get these validation but can still get some local checks that don't require secrets.

In this commit, I have refactored the validation logic by splitting the original file into two separate files:

One to handle validations for pull requests opened from forked repositories.
Another to handle validations for pull requests opened from the same repository.

The local validation checks have been kept unchanged as they apply equally to both types of pull requests. However, this refactoring now allows for easier addition of specific validation checks in the future for either type of pull request as needed.
Please review the changes and let me know if any additional validation logic should be incorporated for either case.

TBH I would rather keep the relatively simpler workflow, but change it to use pull_request_target so it has access to secrets. I can open a PR for doing that

Superseded by https://github.com/nodejs/bluesky/pull/31, thanks for working on it!


Emulator specific commands

Would it make sense to introduce emulator specific commands? Would it make sense to make these commands mandatory?

Sample N shots : Would sample N shots from the full qubit register after executing a quantum circuit.
Probability in Zero : Would return a vector of probabilities to have qubits 0,...,M-1 in zero state.

Reason:

Saves computing effort for emulation based on state vector or density matrix propagation.
Emulation may be equally important to a user.

Hi @NormannMertigHitachiCambridge
Can you please file a new issue for this in the new repo? We can pick up the discussion there.
Cheers!


Azuread support

Ref:

https://github.com/rancher/rancher/issues/42939

SURE-4275

This PR adds the support for the AzureAD provider. When configured the rancher token command will prompt the user to select it, or use the local login.
The CLI will use the Device Authorization Grant, so it will ask the user to enter a code in the URL, as discussed in the RFC.
The PR adds also some refinements and refactor:
The getAuthProviders func now returns a []TypedProvider. With https://github.com/rancher/rancher/pull/44285 the GetType method was added, so that every provider automatically implements any interface with the same method.
type TypedProvider interface {
	GetType() string
}

func getAuthProviders(server string) ([]TypedProvider, error) {
	// fetch providers
}

With this we can actually do a type assertion on the returned interface and get the concrete underlying type.
Note: before merging the import for the struct will need to be updated.

One thought I had about the --prompt option that I figured I'd capture here before I forget. While it certainly works well, it feels like a bit of a non-standard approach to this sort of operation (copy/paste a URL from a blank page). We should definitely make sure that this UX is reasonable, and if it is, we should definitely add some extra text in the cli output to make it very clear to the user what the expected flow is in this scenario.

@crobby that's a legit concern. What about having a Rancher UI page that is not doing anything in the backend, but just showing you the URL, or maybe the query params? That will be pretty cool, and actually useful also to show the errors. The user will be prompted to input the code, and/or the other parameters.
It need a bit of work on the UI side, but not much.

Just to have something visual this is what I was trying to come up:

Please don't pay too much attention to the graphic, I'm not a frontend guy. It will be nice to have also a "copy" button, so the user can easily copy-paste the code, or whatever he needs.

In the final implementation, implementing the RFC there is no update on the UI.

Thanks @crobby. I've added just a couple of tests to the getAuthProviders func. Others are probably possible, but not without a bit of a refactors.
With the latest commit I've added a getClient func, used to create the HTTP client once, with the same TLS config. Otherwise the skipVerify or the caCerts options were going to be ignored in some requests. I guess this was the case for the BasicAuth, so there was probably a bug.
If that's the case I could try to reproduce it, open the bug, fix it in an isolated way and keep the two PRs smaller.
/cc FYI @samjustus @anupama2501

As discussed internally we can keep the changes as-is (reverting a func name) to keep the existing behaviour. We will address the issues in a next version of the cli.
/cc @crobby @andreas-kupries


System Feature temaple

Added system feature template. Could you please review?
The system feature template sets the system properties of device.

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/128