Homekit controller - Configured, but no entity available

Home Assistant release with the issue:
0.71.0
Last working Home Assistant release (if known):
0.71.0
Operating environment (Hass.io/Docker/Windows/etc.):
Docker running on Synology NAS DSM918+ since version 0.65.0
Component/platform:
https://www.home-assistant.io/components/homekit_controller/
Description of problem:
I have 4 wifi switches (Insignia) which have an independent control app, but are also HomeKit compliant and have Homekit IDs for setup.  I've wanted to use these in HA and was pleased when I saw the release of the HomeKit controller component.  I've setup the switches as per documentation and once removed from the HomeKit app I was able to get the configuration link in the HA frontend.  I configured the 4 switches by using the relevant HomeKit ID and they disappeared from the frontend.
I currently can't find any reference to the switches in the Entity listing, but as per the logs I can see they are being detected.  I've filtered out lines containing homekit_controller, but can provide more relevant lines around the particular errors if necessary.  I've been unable to determine the problem and have posted several queries in the forums.  Others have also posted similar.
https://community.home-assistant.io/t/homekit-controller-not-working-correctly/54676
https://community.home-assistant.io/t/help-setup-devices-for-control-with-homekit-controller-component/55927
https://community.home-assistant.io/t/homekit-controller-how-to-find-entity-id-to-add-to-ui/55260
2018-06-14 18:10:01 DEBUG (SyncWorker_11) [homeassistant.components.homekit_controller] Discovered unique device D2:29:9D:1B:74:A9
2018-06-14 18:10:01 DEBUG (SyncWorker_10) [homeassistant.components.homekit_controller] Discovered unique device DE:2F:3E:B7:DA:C9
2018-06-14 18:10:01 DEBUG (SyncWorker_5) [homeassistant.components.homekit_controller] Discovered unique device 41:51:EE:B6:F6:90
2018-06-14 18:10:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Discovered unique device 05:74:78:20:68:EF
2018-06-14 18:10:01 DEBUG (SyncWorker_3) [homeassistant.components.homekit_controller] Discovered unique device E1:CA:79:52:0B:1B
2018-06-14 18:10:03 INFO (SyncWorker_11) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-14 18:10:03 INFO (SyncWorker_10) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-14 18:10:03 INFO (SyncWorker_5) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-14 18:10:03 INFO (SyncWorker_19) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-14 18:10:03 INFO (SyncWorker_3) [homeassistant.components.homekit_controller] Setting up Homekit device NL22
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 243, in discovery_dispatch
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 98, in __init__
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 112, in accessory_setup
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 243, in discovery_dispatch
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 98, in __init__
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 112, in accessory_setup
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 243, in discovery_dispatch
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 98, in __init__
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 112, in accessory_setup
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 243, in discovery_dispatch
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 98, in __init__
  File "/usr/src/app/homeassistant/components/homekit_controller/__init__.py", line 112, in accessory_setup

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
   enable:
      - homekit

Traceback (if applicable):
Additional information:

It's better to filter the log using the logger component than after the log was collected. There's a lot of lines missing now from the stack trace.

@MartinHjelmare What filter do you recommend and I'll set it and do a restart.  I had following configured.
logger:
default: warning
logs:
homeassistant.components.homekit_controller: debug
Adding more of the details.
2018-06-15 03:26:24 DEBUG (SyncWorker_14) [homeassistant.components.homekit_controller] Discovered unique device 41:51:EE:B6:F6:90
2018-06-15 03:26:24 DEBUG (SyncWorker_3) [homeassistant.components.homekit_controller] Discovered unique device DE:2F:3E:B7:DA:C9
2018-06-15 03:26:24 DEBUG (SyncWorker_10) [homeassistant.components.homekit_controller] Discovered unique device D2:29:9D:1B:74:A9
2018-06-15 03:26:24 DEBUG (SyncWorker_13) [homeassistant.components.homekit_controller] Discovered unique device E1:CA:79:52:0B:1B
2018-06-15 03:26:24 DEBUG (SyncWorker_4) [homeassistant.components.homekit_controller] Discovered unique device 05:74:78:20:68:EF
2018-06-15 03:26:25 INFO (SyncWorker_14) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-15 03:26:25 INFO (SyncWorker_3) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-15 03:26:25 INFO (SyncWorker_10) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-15 03:26:25 INFO (SyncWorker_4) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-06-15 03:26:25 INFO (SyncWorker_13) [homeassistant.components.homekit_controller] Setting up Homekit device NL22
2018-06-15 03:26:28 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 243, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 98, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 112, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 614, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(0 bytes read, 747 more expected)
2018-06-15 03:26:28 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 243, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 98, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 112, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 614, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(0 bytes read, 747 more expected)
2018-06-15 03:26:28 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 243, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 98, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 112, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 614, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(0 bytes read, 747 more expected)
2018-06-15 03:26:28 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 243, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 98, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 112, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 614, in _safe_read
raise IncompleteRead(b''.join(s), amt)
http.client.IncompleteRead: IncompleteRead(0 bytes read, 747 more expected)

That filter is good. Thanks for providing the extended log. That log should be enough to start a conversation with someone that wants to fix the bug.

Same here, i have same kind of switches added to hassio v0.71 with the Homekit pin code but no entities were added

@mjg59 Hi Mathew,
I reviewed your original development efforts on the HomeKit Controller and I also agree that it's a powerful feature for HA to open up an easy way to integrate HomeKit enable devices.  Zwave could learn something from the method behind Homekit about making it end-user simple.  I currently have 5 Insignia WiFi Homekit light switches that I can't control with HA and I don't really want to replace.  I'm excited about the hope your efforts provide and I've seen others with the same desire.
Just wanted to make you aware of this and the issue that I posted (14974) around the homekit controller in the event you have some time to take a review.
https://github.com/home-assistant/home-assistant/pull/13346
Brian

I'm on vacation at the moment, but I'll work on this once I'm back. Thanks for the report!

Enjoy your vacation and will watch for any help I can provide upon your return.

Ok I think I've identified the problem here and I'm working with upstream to come up with a fix.

Fantastic news. Maybe 0.73.0 will have it. If it gets in an 0.73.0b release let me know and I’ll test it as I’m in synology docker and should be quick. Brian

@mjg59 Is there anyway to get your patch for 0.72.1 in advance to try it out early? (sorry, but excited to get my 5 switches up and running as I have some automations planned for them)

Try editing homeassistant/components/homekit_controller/init.py and replace
REQUIREMENTS = ['homekit==0.6']

with
REQUIREMENTS = ['https://github.com/mjg59/homekit_python/archive/http_read.zip#homekit==0.9']

and then restart hass.

@mjg59 I did notice that I have two entities for the nanoleaf (light.nl22 and light.aurora) so I'm thinking the homekit_controller one is the nl22 and it is not working correctly.  the light.aurora is the one I've got in the UI and is working as expected (found by discovery via the new nanoleaf component).  Just wanted to note that as the errors are related to the SyncWorker_14 that seems to be the NanoLeaf.

Ok I see it finding four of your switches, but unfortunately it doesn't seem to get much further. Do you see any messages about it taking over 10 seconds to do any setup? Are all of these devices paired with Home Assistant?

I disconnected them from the Insignia software on the wifi and then paired them all with HA successfully.
I just checked the log file again before I responded and some errors came in.  I only copied the first of what appears to be code errors for each device.
2018-07-06 01:42:24 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:42:55 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:43:26 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:43:56 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:44:27 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:44:57 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 244, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 99, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 113, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 612, in _safe_read
chunk = self.fp.read(min(amt, MAXAMOUNT))
File "/config/deps/lib/python3.6/site-packages/homekit/secure_http.py", line 48, in read
self.data += self.parent._read_response()
File "/config/deps/lib/python3.6/site-packages/homekit/secure_http.py", line 138, in _read_response
data = self.sock.recv(exp_len)
ConnectionResetError: [Errno 104] Connection reset by peer
2018-07-06 01:44:58 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Then there is a series of timeouts.
2018-07-06 01:45:28 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:45:59 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:46:29 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:46:59 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:47:30 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:48:00 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:48:31 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:49:01 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:49:32 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:50:02 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:50:33 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:51:03 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:51:34 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:52:05 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:52:36 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:53:06 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30
2018-07-06 01:53:37 WARNING (MainThread) [homeassistant.components.light] Updating homekit_controller light took longer than the scheduled update interval 0:00:30

Ok, can you try making the changes in https://github.com/home-assistant/home-assistant/pull/15315 ? The put_characteristics bit may not exist, so ignore that. If that fails we're going to have to do some more debugging.

I'm trying to make those edits, but got to the last changes in the init.py noted in 15315 and my file does not match at the end
`@@ -223,7 +227,8 @@ def update_characteristics(self, characteristics):
def put_characteristics(self, characteristics):
"""Control a HomeKit device state from Home Assistant."""
body = json.dumps({'characteristics': characteristics})

   self._securecon.put('/characteristics', body)

   with self._lock:

       self._securecon.put('/characteristics', body)`

I can't find the def put_characteristics

Sorry.. just read your note to me again.. "The put_characteristics bit may not exist, so ignore that"  making the other changes and testing

Presume that I don't have to unpair from HA as I am not sure how to do that anyway.. restarting HA now.

ok.. presuming my changes are now in use then it appears no change and we'll have to consider further debugging.  Is there anything that I can do to gather you more info?
2018-07-06 02:55:11 DEBUG (SyncWorker_8) [homeassistant.components.homekit_controller] Discovered unique device 41:51:EE:B6:F6:90
2018-07-06 02:55:11 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Discovered unique device AE:2D:C4:BD:DD:82
2018-07-06 02:55:11 DEBUG (SyncWorker_12) [homeassistant.components.homekit_controller] Discovered unique device D2:29:9D:1B:74:A9
2018-07-06 02:55:11 DEBUG (SyncWorker_9) [homeassistant.components.homekit_controller] Discovered unique device DE:2F:3E:B7:DA:C9
2018-07-06 02:55:11 DEBUG (SyncWorker_14) [homeassistant.components.homekit_controller] Discovered unique device 05:74:78:20:68:EF
2018-07-06 02:55:12 INFO (SyncWorker_8) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-06 02:55:12 INFO (SyncWorker_18) [homeassistant.components.homekit_controller] Setting up Homekit device NL22
2018-07-06 02:55:12 INFO (SyncWorker_12) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-06 02:55:12 INFO (SyncWorker_9) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-06 02:55:12 INFO (SyncWorker_14) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found Unknown Service: A18E1901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found Unknown Service: A18E7901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found Unknown Service: A18E6901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found lightbulb
2018-07-06 02:55:13 DEBUG (SyncWorker_18) [homeassistant.components.homekit_controller] Found Unknown Service: A2
2018-07-06 02:56:40 WARNING (MainThread) [homeassistant.core] Unable to find service homekit/start
2018-07-06 03:29:39 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 248, in discovery_dispatch
device = HKDevice(hass, host, port, model, hkid, config_num, config)
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 100, in init
self.accessory_setup()
File "/usr/src/app/homeassistant/components/homekit_controller/init.py", line 115, in accessory_setup
data = json.loads(response.read().decode())
File "/usr/local/lib/python3.6/http/client.py", line 462, in read
s = self._safe_read(self.length)
File "/usr/local/lib/python3.6/http/client.py", line 612, in _safe_read
chunk = self.fp.read(min(amt, MAXAMOUNT))
File "/config/deps/lib/python3.6/site-packages/homekit/secure_http.py", line 48, in read
self.data += self.parent._read_response()
File "/config/deps/lib/python3.6/site-packages/homekit/secure_http.py", line 138, in _read_response
data = self.sock.recv(exp_len)
ConnectionResetError: [Errno 104] Connection reset by peer

Ok - before we start, are you comfortable setting up a virtualenv?

I'm not a dev, but I should be able to follow directions if that's possible.  I have a Synology NAS 918+ running docker, so would there be a docker environment that I could setup?  Been in the IT industry for years working with devs and have administered and setup various server environments.  If you are game then I am.

Hm, doing this with docker may be more complicated - let me think about what the easiest way to do this will be.

I also have a Hyper-V server (2012) that I can run something on, so there are other options.  Thought there might be a ready container for it, but let me know your thoughts.

@mjg59 Just wanted to confirm that 0.73.0 does not seem to have resolved the problem.  I have not made the same changes yet, but thought I'd let you know.  Let me know if you've thought of anyway that I can test/check anything in my environment to help debug the problem.

@mjg59 Just installed v 0.74.0 to check out the changes to the HomeKit Controller.  It shows in the log a switch found, but as of yet can't find any reference under entities.  Any guidance you can provide?
2018-07-20 19:03:00 DEBUG (SyncWorker_0) [homeassistant.components.homekit_controller] Discovered unique device DE:2F:3E:B7:DA:C9
2018-07-20 19:03:00 DEBUG (SyncWorker_2) [homeassistant.components.homekit_controller] Discovered unique device D2:29:9D:1B:74:A9
2018-07-20 19:03:00 DEBUG (SyncWorker_14) [homeassistant.components.homekit_controller] Discovered unique device 41:51:EE:B6:F6:90
2018-07-20 19:03:00 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Discovered unique device AE:2D:C4:BD:DD:82
2018-07-20 19:03:00 DEBUG (SyncWorker_6) [homeassistant.components.homekit_controller] Discovered unique device 05:74:78:20:68:EF
2018-07-20 19:03:00 INFO (SyncWorker_0) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-20 19:03:00 INFO (SyncWorker_2) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-20 19:03:00 INFO (SyncWorker_14) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-20 19:03:01 INFO (SyncWorker_6) [homeassistant.components.homekit_controller] Setting up Homekit device NS-CH1XIS8
2018-07-20 19:03:01 INFO (SyncWorker_19) [homeassistant.components.homekit_controller] Setting up Homekit device NL22
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found Unknown Service: A18E1901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found Unknown Service: A18E7901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found Unknown Service: A18E6901-CFA1-4D37-A10F-0071CEEEEEBD
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found lightbulb
2018-07-20 19:03:01 DEBUG (SyncWorker_19) [homeassistant.components.homekit_controller] Found Unknown Service: A2
2018-07-20 19:03:03 DEBUG (SyncWorker_2) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-20 19:03:03 DEBUG (SyncWorker_0) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-20 19:03:03 DEBUG (SyncWorker_2) [homeassistant.components.homekit_controller] Found switch
2018-07-20 19:03:03 DEBUG (SyncWorker_6) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-20 19:03:03 DEBUG (SyncWorker_0) [homeassistant.components.homekit_controller] Found switch
2018-07-20 19:03:03 DEBUG (SyncWorker_14) [homeassistant.components.homekit_controller] Found accessory-information
2018-07-20 19:03:03 DEBUG (SyncWorker_6) [homeassistant.components.homekit_controller] Found switch
2018-07-20 19:03:03 DEBUG (SyncWorker_14) [homeassistant.components.homekit_controller] Found switch

@mjg59 Hi Mathew, Not sure if you are going to have any time to look into this as I'm still available to assist in any testing or patch tests.  I also saw another item that seems related and I posted some addition and recent info on 0.74.1
https://github.com/home-assistant/home-assistant/issues/14320#issuecomment-408066076

still same prob , on 0.81.6

Same here!

Has this problem been fixed or a solution. I'm using 0.82.1 and trying to get my Leviton DH6HD-1BZ switches to work. They seem to pair but don't show up on the Home Assistant front end. I do see when I pair the switch it creates a file in the /config/.homekit folder. I'm also getting the error "Disconnected: Did not receive auth message within 10 seconds"

@beit-no1 has your problem been fixed?

Yes. All 4 insignia switches now functioning in 89.2. Had to do one at a time and rename entity as it assumes same. Thanks

beit-no1
I'm still having an issue with my insignia switches, now i cannot enter the PIN code I already reset my switches but every time I tried to enter the code I have the message "This accessory is already paired to another device".  Any idea?

Did you make sure they are not somehow linked in your Apple Home.  I definitely went in there and made sure they were removed.  I then did a hard reset on them and was able to get them into HA.  I did have to do them one by one as they each had the same default entity_id and so I'd rename it once in HA.  I now have 4 of them...

I delete the devices from insignia connect app and from Apple home kit, now I'm going to do these steps:

add one switch to the insignia app to give it a wifi signal
delete the switch from insignia pp
restart HA
in the UI add the PIN code, look for it in HA and rename it on customize.yaml or where?, rename entity_id or friendly name
repeat same for switch # 2

thanks

I don’t delete mine from the insignia app. I can still use them there as well as HA. I renamed mine using the gear icon once I added it to an entity Lovelace card. Then repeated.


cigien: Watch (?:keanu[\W_]+)?reeves[\W_]+cbd[\W_]+oil(?:[\W_]+(?:buy|order|\d++|[\da-f]{5,}+)s?)*

cigien requests the watch of the watch_keyword (?:keanu[\W_]*+)?reeves[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:buy|order|\d++|[\da-f]{5,}+)s?)*. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?:keanu[\W_]*+)?reeves[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:buy|order|\d++|[\da-f]{5,}+)s?)* has been seen in 4 true positives, 0 false positives, and 0 NAAs.

(?:keanu[\W_]*+)?reeves[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:buy|order|\d++|[\da-f]{5,}+)s?)* has been seen in 4 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ

Approved by Makyen in Charcoal HQ


EFS not supported by resourcegroupstaggingapi

Apologies, I'm back again with another resource groups tagging api feature request. It looks like EFS file systems aren't supported in moto's implementation, though they are supported in this api by AWS (https://docs.aws.amazon.com/resourcegroupstagging/latest/APIReference/supported-services.html).
@mock_aws
class MyTestClass(unittest.TestCase):
    def setUp(self):
        efs = boto3.client("efs", region_name="us-east-1")
        efs.create_file_system(CreationToken="1234")

    def test_stuff(self):
        boto3.client("resourcegroupstaggingapi", region_name="us-east-1")
            .get_resources()["ResourceTagMappingList"] # No resources are returned, expected the file system created in setUp()

Taking a look in the implementation it looks like this is missing altogether so this would be a net-new feature rather than a bug with any existing code https://github.com/getmoto/moto/blob/master/moto/resourcegroupstaggingapi/models.py.
Relevant Versions:
moto - 5.0.9
boto3 - 1.34.135
Python - 3.11.6
MacOS - 14.5

The more the merrier @rdbatch02!
This is already part of moto >= 5.0.11.dev11.

Amazing, thanks @bpandola and @bblommers for the super quick turnaround!


Support tls version config for elasticsearch

Proposed changes
Add sslVersion  for elasticsearch

Types of changes

Bugfix (non-breaking change which fixes an issue)

Linked Issues

https://github.com/rancher/rancher/issues/16070
https://github.com/rancher/rancher/issues/16042
Further comments

Backend is not merged yet

@loganhz can you remove the waiting label when the backend changes have been merged?


Added support for TypeGraphQL Input- and ArgTypes

I have added support for TypeGraphQL InputTypes and ArgsTypes to the @graphql-codegen/typescript-type-graphql plugin, as requested in #2177.

Great! Thanks @borremosch !


PressableButton creates glow only for left hand

##Bug:
"Blob" (blue glow) is only visible for pointers on the left hand on PressableButtons
##Recreate:
Copy the ActionButton from UX Components and create your own prefab.
##Info:
The project is based on the DevTemplate. I did not change any profiles or subsystems that may have an effecot on pointers. Interestingly the FrontPlate animation works for the right hand, if im using the handray. The blob only appears for the handray and near interaction of the left hand. The ActionButton (default) does not show any blobs for handrays but they show up for both hands on near interaction. Feels like something gets mixed up, when copying the prefab.
##Screenshot:

##Versions
Unity 2022.3.7f1
MRTK3 (from FeatureTool)
Target: Unity Editor & HoloLens 2

Found it: The FrontPlate shader contains Blob1 and Blob2. Only Blob1 was enabled on my copy. Maybe calling this Left and Right instead of 1 and 2 would be more comprehesnsive


Possible to stream the zip out, while still adding files

I have a use case, where I need to get a bunch of files from S3, zip them into one archive, then send it over http to a client.
Would it be possible to start sending the file as soon as some files are streamed in from S3, so the entire archive doesnt need to be buffered in memory?
Ie start file 1 from S3, pipe it into zipstream, and pipe that to te response?

Ok cool, just wasn't clear from divine ration.
So, do I still have to order the addFiles, so they are sequential? Or
can I just kick off 10 addFiles in one go, and simultaneously start
the output?
Dharmesh
On 5 Feb 2012, at 11:03, wellawaretech
<EMAIL_ADDRESS>wrote:

I think the module already does what you want; it takes streams as input and begins outputting the ZIP file before the input is finished; it certainly not buffers everything in memory. Also you can set up a pipe to the response, ie.
zipStream.pipe(response)
One thing though, instead of "yourStream.pipe(zipStream)" you should instead do "zipStream.addFile(yourStream, ...)"
As far as I see it now, it would be a nice-to-have to be able to pipe data into a zipStream object directly, but it's not needed.

Reply to this email directly or view it on GitHub:
https://github.com/wellawaretech/node-zipstream/issues/2#issuecomment-3816934

They have to be sequential. In the ZIP file the compressed files are appended one after the other; it wouldn't make sense to start them simultaneously.


Create ObjectTransformation class

This class must have operations to compute object translation, scaling and rotation.

https://github.com/ramnasidharta/graphical-recipe/pull/16


Docs: How to build a custom ISO

I think we have this already covered in our docs: https://kairos.io/docs/installation/automated/#iso-remastering


UDP packet loss

Some users reported they have packet loss on UDP. also, someone's syncing issue is fixed by disabling the UDP for the network.
Some possible cases:
1- 2024/01/07 11:15:06 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2- filtering and blocking UDP/QUIC packets by ISPs.

Let me add something here.
This should not have an impact on synchronization, mainly affecting the broadcast of voting.
Because the synchronization of the nodes I tested was normal,
but the voting score kept decreasing, and after disabling UDP, the score gradually increased.

This should not have an impact on synchronization, mainly affecting the broadcast of voting.

Sounds weird. Maybe there is something else related to this issue.

Synchronization involves read and write operations, which are closely related to the performance of the available CPUs and disk I/O. As far as I know, some inexpensive ISPs provide services with poor performance in these two areas.


RFC/WIP: Add support for PDBPP_HIJACK_PDB=0 to not replace pdb module

TODO:

[ ] test
[ ] rename to just PDBPP_HIJACK or PDBPP_DISABLE ?
[ ] verify if it works with eggs also (where the hack is not used?!)

I usually just do pdb.pdb.set_trace.

Useful though anyway.


The output of ceval is not as the same format at the official version?

As https://github.com/hkust-nlp/ceval/blob/main/README_zh.md shows:

but the result of ours is:

The script is:
TASKS="ceval-valid*"
BATCH_SIZE=1
NUM_SHOTS=5

MODEL="" # model path
API=vllm
CUDA_VISIBLE_DEVICES=7 lm_eval \
    --model ${API} \
    --model_args pretrained=${MODEL},dtype="half", gpu_memory_utilization=0.9 \
    --tasks ${TASKS} \
    --batch_size ${BATCH_SIZE} \
    --num_fewshot ${NUM_SHOTS} \
    --trust_remote_code \
    --output_path ./result

How can I get the same ouput as the official version?
Thanks!

Since GPT-4 and ChatGPT API replies may change every day, week or month, there may be no way to get the same output as reported 8 months ago (according to the last change date of the README_zh.md link you provided).
You can also try to find exact version of lm-eval code they used (probably some 0.3.0 like with updates) and check reproducibility.


Add clear function for form controls

As user, I want to be able to delete my input in the search field with one click, so that I save time on deleting every single character. See example attached to this ticket.
Acceptance criteria:

[ ] Find a way to place a button/icon in input fields in order that the user can delete inputs in a bulk
[ ] Implement solution

Do we reset to the initial value like a form reset or just to an empty value?

@hirsch88 can you check my example? For the other question I would say we do a form reset or do you have use-cases in mind where this would not work.
Components with.pdf

Figma example can be found here

https://github.com/baloise/design-system/issues/698


ci: add clientgen/generate to presubmit

This adds the clientgen and generate calls to the presubmit check. This ensures that the generated code is always up to date.

/assign @karlkfi

Looks like some sorting differences in the generate output. Is it not consistent or was it generated with a different permutation of tool versions?


Help with API Token generation

Hello there, big fan of your plugin. Please can you share a procedure for getting the TOKEN of Xbox API?
Thanks in advance!
Regards!

https://github.com/grzegorz914/homebridge-xbox-tv#configuration-and-enable-web-api-control


Multiprocessing

For implementing gamepad support, it seems to make sense to run a separate process that monitors gamepad inputs and sends messages to exokit. I prefer this architecture rather than bogging exokit down with even more functionality. It's also more stable, considering that a crash in one module won't affect the overall system.
This issue is to collect some thoughts about a sort of "standard interface" for this type of work. Refs:
Composable Reliability for Asynchronous Systems
The Magic Ring Buffer
share-node-memory npm package, for named shared memory

I disagree with that approach, because it's not compatible with other platforms that don't allow or simply don't have fork. It also adds another IPC channel and asynchony/potential race, and another context switch for a project that's based around having a well-controlled synchronous render loop.

It doesn't rely on fork. It only relies on spawning child processes, and sharing blocks of memory with them. Every OS supports that.

Child process uses fork, and as far as I know is banned from iOS.
On Sat, Aug 11, 2018 at 12:58 AM Shawn Presser<EMAIL_ADDRESS>wrote:

It doesn't rely on fork. It only relies on spawning child processes, and
sharing blocks of memory with them. Every OS supports that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webmixedreality/exokit/issues/343#issuecomment-412251044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGmu6YmPhEGj2bwMWoR_ZeeO8B_Iv4GEks5uPmR7gaJpZM4V4dvw
.

Hmm, you're right. On the other hand, since the child processes are written in javascript, it's easy to collapse all of them into a single address space for platforms that don't support child processes.

So why play multiprocess tricks if the inline solution works everywhere?
On Sat, Aug 11, 2018 at 7:58 AM Shawn Presser<EMAIL_ADDRESS>wrote:

Hmm, you're right. On the other hand, since the child processes are
written in javascript, it's easy to collapse all of them into a single
address space for platforms that don't support child processes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/webmixedreality/exokit/issues/343#issuecomment-412270646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGmu6S52SjAZTGApaYNh3I0-1oX8OlJ8ks5uPsb6gaJpZM4V4dvw
.

I think this is a special case of how to do extensibility. I don't think "multiprocessing" is in scope for the core, though I'm interested in supporting the case of integrating modules that do it.
That should be pretty easy right now with node modules, but if there's a problem we hadn't considered there please open another issue for it.


multi-job output variable named Foo.Bar

It is explained in this section how to grab a variable output from one job, in another job: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#set-a-multi-job-output-variable
However the variable name is simply "myOutputVar" in your example, and you access it like this:
myVarFromJobA: $[ dependencies.A.outputs['setvarStep.myOutputVar'] ]

However in my case, the variable I need to access is set by an executable and it's named "GitVersion.SemVer".
How do I access that using this syntax? I tried this, but the extra "." in the property name doesn't seem to work:
myVarFromJobA: $[ dependencies.A.outputs['setvarStep.GitVersion.SemVer'] ]
I have tried to guess other ways and they all failed:
myVarFromJobA: $[ dependencies.A.outputs['setvarStep.variables['GitVersion.SemVer']]' ]

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

ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
Content: Define variables - Azure Pipelines
Content Source: docs/pipelines/process/variables.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@dazinator Thank you for the question, assigning this to the author for further review.
In the meantime, please refer to the following:

Azure DevOps community
Azure DevOps support
Azure DevOps on StackOverflow

Think this issue is still present..?

@dazinator : For a faster answer to you question, check these resources:

Azure DevOps community
Azure DevOps support
Azure DevOps on StackOverflow

@juliakm Can you take a look?

I had no issues including a period in the variable name.
jobs:
  # Set an output variable from job A
  - job: A
    pool:
      vmImage: 'ubuntu-20.04'
    steps:
    - script: echo "##vso[task.setvariable variable=myOutput.Var;isOutput=true]this is the value"
      name: setvarStep
    - script: echo $(setvarStep.myOutput.Var)
      name: echovar

  # Map the variable into job B
  - job: B
    dependsOn: A
    pool:
      vmImage: 'ubuntu-20.04'
    variables:
      myVarFromJobA: $[ dependencies.A.outputs['setvarStep.myOutput.Var'] ]  # map in the variable
                                                                            # remember, expressions require single quotes
    steps:
    - script: echo $(myVarFromJobA)
      name: echovar


Error after new version of hydrator, when trying to create new input or fetch it

I think this error could be for this repository, so I created issue ticket here too, did reference with my original issue report in zfcampus/zf-apigility-admin-ui repository
zfcampus/zf-apigility-admin-ui#149

@developer-devPHP thanks for sharing it. I'll look into it asap.

@ezimuel @developer-devPHP
Please see my fix in zend-hydrator: https://github.com/zendframework/zend-hydrator/pull/96

@webimpress thanks for this fixes.
Do you know any estimation, when it could be merged?

@developer-devPHP No idea, sorry.
Depends on @ezimuel


Cannot find module "react" from "web/static/bower_components/react/react-dom"

I'm getting the following error with my Phoenix app that uses Brunch:
Cannot find module "react" from "web/static/bower_components/react/react-dom"
I have the following code:
import React from 'bower_components/react/react';
import ReactDOM from 'bower_components/react/react-dom';
import Map from './components/Map';

ReactDOM.render(<Map />, document.getElementById('map-container'))

I can work around the problem my using React.render() instead of ReactDOM.render(), but I get the depreciation warning for React.render().
My workaround code is:
import React from 'bower_components/react/react';
import Map from './components/Map';
React.render(<Map />, document.getElementById('map-container'))

I'm getting the same behavior but in a Rails 4.2 app.
ReferenceError: ReactDOM is not defined

I just ran bower install react in an empty folder with the following index.html:
<!DOCTYPE html>
<html>
  <body>
    <div id="container">
    </div>
    <script src="./bower_components/react/react.js"></script>
    <script src="./bower_components/react/react-dom.js"></script>
    <script>
      var ExampleApplication = React.createClass({
        render: function() {
          var elapsed = Math.round(this.props.elapsed  / 100);
          var seconds = elapsed / 10 + (elapsed % 10 ? '' : '.0' );
          var message =
            'React has been successfully running for ' + seconds + ' seconds.';

          return React.DOM.p(null, message);
        }
      });
      var ExampleApplicationFactory = React.createFactory(ExampleApplication);
      var start = new Date().getTime();
      setInterval(function() {
        ReactDOM.render(
          ExampleApplicationFactory({elapsed: new Date().getTime() - start}),
          document.getElementById('container')
        );
      }, 50);
    </script>
  </body>
</html>

It ran successfully:

react.js and react-dom.js in the Bower distributions are UMD builds. Since the example runs fine in the browser, the problem has to be with the way your build tool of choice (e.g. Brunch) handles UMD files. I don’t think there’s anything here that we can fix so I’m closing, but please feel free to suggest a solution if you’re sure this is something we can fix on our side.


cannot compile clang

When I execute facebook-clang-plugins/clang/setup.sh to compile clang, the error presents as follows.
  make: *** [all] Error 2
  strip: '/home/parallels/opensrc/infer/facebook-clang-plugins/clang/install/bin/*': No such file
  find: `/home/parallels/opensrc/infer/facebook-clang-plugins/clang/install/lib': No such file or directory

There are also many 'undefined reference' warnings, for example:
 CMakeFiles/cxx.dir/__/src/debug.cpp.o: In function `std::__1::__get_db()':
 debug.cpp:(.text._ZNSt3__18__get_dbEv+0x21): undefined reference to `__cxa_guard_acquire'
 debug.cpp:(.text._ZNSt3__18__get_dbEv+0x4c): undefined reference to `__cxa_guard_release'
 ...

Can you please provide more information? Please include:

the version of infer
the full history of commands you used to run infer
the full output (please use https://gist.github.com/ or equivalent)

Please include OS you use and version of gcc/clang you have on your system as well

I am building the infer of the latest version in github on ubuntu 14.04. The ubuntu OS is installed in the virtual machine Parallels(TM) on Mac OS (intel Core i7 cpu).
The command 'uname -a' printed information as follows.
Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
I run the following commands:
git clone https://github.com/facebook/infer.git
cd infer
./build-infer.sh java
It succeeded.
Then I run './build-infer.sh clang' and it failed. The clang version
Then I run the following commands:
cd facebook-clang-plugins/clang
rm installed.version
./setup.sh
The output of setup.sh is in

'https://gist.github.com/yinle2002/027fefccdd408f7105aa07bbe8ba5675'
 However, command './setup.sh' returned 0 and produced file installed.version, whose contents is as follows:

0fe7f0565f6646d5f262daea00d9dae58fd44dc7b073e24707a987b3282c6d47 ?src/clang-4.0.tar.xz
78bdffeea7b0a38eb78dd9c5f43a1718d2d5024bd090b6b83c237b1c5cf35c72 ?setup.sh
So I think the clang version is 4.0.

I meant your host compiler that is used to compile that clang - from your gist it looks like you have gcc 4.8.4 which should be new enough to compile clang.
I've seen those errors before but I thought they were fixed (https://github.com/facebook/facebook-clang-plugins/blob/master/clang/setup.sh#L82 should do it)
I'm going to try and reproduce the problem on local VM, but it may take some time

@yinle2002 could you check if you have c++ libraries installed?
Simply run following command: apt list | grep libstdc++

I reproduced the problem on my VM. I was unable to find the fix yet, but I'm planning to look into it more. Stay tuned

Issue reproduces with newest clang-3.9.1 release. I created bug report, hopefully they will have a fix/workaround for it

Hi @akotulski
Thank you for your response.
In  https://llvm.org/bugs/show_bug.cgi?id=31291, the bug is expected to be closed. However, how should I do to make 'setup.sh' work? Is there any concrete guide?

Hi @akotulski
Thank you for your response.
In https://llvm.org/bugs/show_bug.cgi?id=31291, the bug is expected to be closed. However, I still wonder how should I do to make 'setup.sh' work? Is there any concrete guide?

I'm planning to update source code of clang we use. Then it should work for you.

Hi @akotulski  and @leo-yinle ,
I also have a problem but I am not sure it is the same as the one above.
In my case, I got the following error messages during the clang compilation.
[ 51%] Linking CXX static library ../libLLVMAnalysis.a
make[3]: Leaving directory `/tmp/clang-setup.VeTyKm/build'
[ 51%] Built target LLVMAnalysis
make[2]: Leaving directory `/tmp/clang-setup.VeTyKm/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/clang-setup.VeTyKm/build'
strip: '/home/khheo/project/infer_ropas/facebook-clang-plugins/clang/install/bin/*': No such file
find: `/home/khheo/project/infer_ropas/facebook-clang-plugins/clang/install/lib': No such file or directory
/tmp/clang-setup.VeTyKm ~/project/infer_ropas
~/project/infer_ropas
make -C /home/khheo/project/infer_ropas/facebook-clang-plugins/libtooling all \
          CC=clang CXX=clang++ \
          CFLAGS="-g -O2" CXXFLAGS="-g -O2" \
          CPP="clang -E" LDFLAGS="" LIBS="" \
          LOCAL_CLANG=/home/khheo/project/infer_ropas/facebook-clang-plugins/clang/install/bin/clang \
          CLANG_PREFIX=/home/khheo/project/infer_ropas/facebook-clang-plugins/clang/install \
          CLANG_INCLUDES=/home/khheo/project/infer_ropas/facebook-clang-plugins/clang/install/include
make[1]: Entering directory `/home/khheo/project/infer_ropas/facebook-clang-plugins/libtooling'
make[1]: *** No rule to make target `build/SimplePluginASTAction.o', needed by `build/FacebookClangPlugin.dylib'.  Stop.
make[1]: Leaving directory `/home/khheo/project/infer_ropas/facebook-clang-plugins/libtooling'
make: *** [clang_plugin] Error 2

I use
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty
khheo@rec:~/project/infer_ropas$ gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I just committed https://github.com/facebook/infer/commit/3096e8448b124607dc0a0a0df99795711502683f to fix that problem. Please fetch infer's master and remember to update facebook-clang-plugins submodule by running git submodule update
@KihongHeo by the fact that you are using ubuntu 14.04 I'd say it's likely the same issue. Please try again with newest version of infer.


PathProvider should provide a way to access the Library directory

Currently under iOS PathProvider getApplicationDocumentsDirectory method returns the Documents directory.
It should be noted that this is NOT (or at least SHOULD NOT be) the standard path where an iOS app stores its data!
From https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html

Use this directory (Documents directory - ed.) to store user-generated content. The contents of this directory can be made available to the user through file sharing; therefore, this directory should only contain files that you may wish to expose to the user.

Use the Library subdirectories for any files you don’t want exposed to the user. Your app should not use these directories for user data files.

Content in both directories is automatically backed up by iCloud.
BTW, It's currently very easy to access this directory (documents + '../Library') but the workaround is system-specific and not really future-proof.
As Android doesn't differentiate between the two, I think we can safely add a getApplicationLibraryDirectory that returns the AppData dir (the same as getApplicationDocumentsDirectory) under Android and the Library dir under iOS.
Maybe this is not ideal, but at least won't break BC.
I can provide a PR if the maintainer likes this approach.

The more I think about this, the more I think that the current API design of this plugin is a bit off.
The main issue is that actually the iOS Documents directory is much closer to the Android External Storage directory than the AppData directory, while the AppData directory is closer to the Library (or even the Library/Application Support) directory.
I think that this plugin should actually have three cross-platform methods:

getApplicationLibraryDirectory which maps to NSLibraryDirectory (or maybe NSApplicationSupportDirectory which is even more standard) on iOS and AppData on Android
getApplicationDocumentsDirectory: which maps to NSDocumentDirectory on iOS and the External storage path on Android.
the getTemporaryDirectory which should be ok as it is now (although there are some subtle differences between Caches and tmp under iOS).

On top of these methods the plugin can provide platform-specific methods (e.g. android appdata and external storage, direct access to iOS NSSearchPathForDirectoriesInDomains, etc.).
Unfortunately this approach would completely destroy BC, unless we introduce these methods with brand new names (e.g. getLibraryDirectory, getDocumentsDirectory, etc.) and put the old ones as deprecated.

I just want to mention, path_provider doesn't seem to work on iOS 11.2.

I agree with sroddy that we need a getApplicationLibraryDirectory method. Also needed is a way to set files to not be backed up, for application files that can easily be recreated/downloaded.
Any action on this issue?

Any new update on this issue?

I agree there should be some way to get the something like the NSApplicationSupportDirectory on iOS. Please see https://github.com/flutter/plugins/pull/1566.
Having getApplicationDocumentsDirectory give external storage by default seems like it might not be a great experience since sometimes external storage isn't available (including on simulators). Can developers try external storage and fall back on the documents directory if it can't be written?


Add Error type to the lexer tokens (and sort them)

Summary
Error type wasn't known to the lexer. That makes puppet-lint to fire unquoted_string_in_{selector|case} on this type check.
Additional Context
Consider this code:
$x ? {
  Error => false,
  default => true,
}

Puppet-lint will raise a warning on the line containing the Error.
Related Issues (if any)
Checklist

[ ] 🟢 Spec tests.
[ ] 🟢 Acceptance tests.
[ ] Manually verified.

JFYI, the change is untested.. I'm unable to test it right now.

I added some naive test. Not sure if it's good enough.


how can i use thirdparty npm package with reactjs.net?

i want to use other thirdparty npm package in my project,i import it to my js,but when i run in iisexpress,i got a exception.
import { Button } from 'antd';

ReactDOM.render(
  <div>
    <Button type="primary">Primary</Button>
    <Button>Default</Button>
    <Button type="ghost">Ghost</Button>
    <Button type="dashed">Dashed</Button>
  </div>,
  mountNode
);

What is the exception you are getting ?


Getting java.lang.NoClassDefFoundError: jdk/nashorn/api/scripting/ScriptObjectMirror while running on Linux box

Hi Peter,
We have written webservice tests in karate and able to run the tests on local mac machine but currently getting the error  java.lang.NoClassDefFoundError: jdk/nashorn/api/scripting/ScriptObjectMirror while running on Linux box. Initially we were getting nullpointer exception and sent a PR and after the merge, we started getting another issue "java.lang.NoClassDefFoundError: jdk/nashorn/api/scripting/NashornScriptEngineFactory". We sent the PR for to fix this and now we are getting another issue "java.lang.NoClassDefFoundError: jdk/nashorn/api/scripting/ScriptObjectMirror".  The Java version on my mac and TEP(linux) is same and the only difference is operating system. Do you have any fix for this.
Thanks,
Rani

Rani - I have a feeling TEP may be relying on OpenJDK, I am not 100% sure, but maybe Karate needs the Oracle JDK to work properly.  Can you confirm the exact JDK version, but I will also investigate.

adding some context. Karate's CI has been running regularly on Ubuntu / Linux with this Travis setup: https://github.com/intuit/karate/blob/master/.travis.yml

closing as duplicate of #196

@ptrthomas  I got same error on TEP job.
Java version:
/usr/java/default/bin/java
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
Stacktrace:
Caused by: java.lang.ClassNotFoundException: jdk.nashorn.api.scripting.ScriptObjectMirror
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:97)
at com.intuit.karate.ScriptValue.(ScriptValue.java:330)
at com.intuit.karate.ScriptValue.(ScriptValue.java:315)
at com.intuit.karate.Script.evalInNashorn(Script.java:420)
at com.intuit.karate.Script.evalInNashorn(Script.java:394)
at com.intuit.karate.Script.eval(Script.java:316)
at com.intuit.karate.Script.eval(Script.java:194)
at com.intuit.karate.ScriptContext.(ScriptContext.java:114)
at com.intuit.karate.StepDefs.(StepDefs.java:81)
at com.intuit.karate.cucumber.KarateObjectFactory.getInstance(KarateObjectFactory.java:80)
at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:38)
at cucumber.runtime.StepDefinitionMatch.runStep(StepDefinitionMatch.java:37)
at com.intuit.karate.cucumber.CucumberUtils.runStep(CucumberUtils.java:136)
at com.intuit.karate.cucumber.KarateRuntime.runStep(KarateRuntime.java:78)

@amitnagesh refer #196 this is because only the JRE is installed. please work with the folks who own the build node and fix, this is not an issue with karate, thanks.

The same symptom is caused also by having an older version of the Maven maven-surefire-plugin and when using openjdk.  The problem does not appear when using Oracle sdk.
To fix the problem while using openjdk, change your Maven Surefire Plugin to the following:
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>3.0.0-M1</version>
                ...
            </plugin>

I encountered this as a result of having the following surefire plugin configuration:
    <configuration>
      <forkCount>0</forkCount>
    </configuration>

My guess as to whats happening: The software you're running requires a jdk, however maven runs with the jre. If you don't fork then you'll be using maven's JRE, instead of forking into a new JDK.

@rrowlands thanks ! that makes sense and explains some of the observations. I'll point others to this when needed. also provides some ideas on better detection of this case in the future, at least for more helpful logs


[Feature] Docker image

Hey @arikchakma 👋
This tool looks really cool and nicely designed 👍  I would love to see a docker image for this editor. Would make it a lot easier to test/play around with it, and eventually self-host it .
Is this something you're interested in adding?

Currently, I don't have plans to make it a docker image (maybe later). You can copy & paste the editor folder into the components and install its dependencies. It should work fine.
Thanks, let me know if you need any help.


Improve selenium tests

[x] Perform Wireshark (request) logging to see whether the data effectively gets resampled
[ ] Log the console output to check whether no errors are thrown
[x] Maybe also look at the events

see #17


Integration with LeoCAD (render LDraw models and annimations)

LeoCAD is a CAD program for creating virtual LEGO models.

Issue on LeoCAD tracker

https://github.com/leozide/leocad/issues/70

@Symbian9 That sounds very interesting and we will be glad to assist you in adding support for appleseed in LeoCAD! Let us know if/when you start working on this, we will gladly invite you on the appleseed Slack team if you want to get real time answers to your questions.
Closing this issue since the work should be entirely on LeoCAD's side (modulo bugs and missing features in appleseed which will mandate separate issues).


Proper spacing between the logo and title of website on navbar

Is your feature request related to a problem? Please describe.
The logo and title in the navbar are getting too much close to each other and also they are sticking towards the left in the window.
Describe the solution you'd like
It can easily be solved by providing proper margins and padding to both icon and title in the navbar. It may happen that mobile view has to be resolved according to that, but it can be handled easily.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context

If you can, please give this issue hacktoberfest tag and assign it to me if you can.

Okay @AKSHATNEMA please go ahead!


Legend is affected by values that don't map to a country

Example: the population data from the World Bank includes a row for the world (id: WLD) that causes the legend to go up to the total world population thus rendering the map useless.
How to handle such data in d3.geomap? Leave it to the user or remove values that don't map to countries?

Since unit IDs can be arbitrary, this should be handled by the user, i. e. such rows need to be removed beforehand.


requirePaddingNewlinesBeforeKeywords rule with switch statement

It would appear that the requirePaddingNewlinesBeforeKeywords does not consider a case inside a switch statement a block. We require a break before if statements but would not require one as the first line inside a case. Its pretty rare we would run across advanced logic in a case but though I would bring this up.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6752837-requirepaddingnewlinesbeforekeywords-rule-with-switch-statement?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Going to be closing older/inactive issues and labeling with orphaned to track anything we might want to reopen again later (if we want to add it again or something has a PR). Thanks


Get output of Git diff commands for later use

Fixed the git diff command so now it works & gets the output for later use, since we're abandoning Windows support, not much has changed, but this works now

Not much has changed here, but since this works, and the build passes, merging this into master.
This closes #90


Private mode not working

My Setup
YI 1080p Home Camera
Firmware Version | 0.2.0
Base Version | <IP_ADDRESS>_202007141512
Model Suffix | y21ga
'Disable cloud'/'Private mode' seems not to work. Tested several combinations of setting in the hack but still able to see live pictures in YI app with LAN and LTE connect.

Have you reboot the cam after each change?
What is the content of /etc/hosts?
When 'Disable cloud'/'Private mode' option is enabled, the file should contain the following lines (after a reboot).
<IP_ADDRESS>    api.eu.xiaoyi.com
<IP_ADDRESS>    api.us.xiaoyi.com
<IP_ADDRESS>    api.xiaoyi.com.tw
<IP_ADDRESS>    log.eu.xiaoyi.com
<IP_ADDRESS>    log.us.xiaoyi.com
<IP_ADDRESS>    log.xiaoyi.com.tw

Did you solve the problem?

Sorry for bothering you guys. It's working ok. The problem were sitting on fornt of the PC.
Thanks!

Thanks! Private mode is working ok.


Unable to convert to vanilla Elytra

Putting a Customizable Elytra alone in the crafting table splits the wings and removes their dye colors instead on converting it to a vanilla Elytra like the mod page says.
Customizable Elytra version 1.6.5 for 1.19.3

My bad, the description on the mod page is outdated. In newer versions right clicking on a cauldron will turn your elytra back into a vanilla one!


Run qFlex natively on Mac OSX using clang

Can confirm that everything is working!

Let me try to automatize the process on Mac OS X. Otherwise, I'll merge this PR. Thanks!

Can confirm that everything is working!

@alankao64, can you double check that everything is working by just running:
autoreconf -i && autoconf && ./configure && make -j8 && make -j8 run-tests

Thanks!

@alankao64, can you double check that everything is working by just running:

Confirmed everything works after updating cirq!


[SPARK-20166][SQL] Use XXX for ISO 8601 timezone instead of ZZ (FastDateFormat specific) in CSV/JSON timeformat options

What changes were proposed in this pull request?
This PR proposes to use XXX format instead of ZZ. ZZ seems a FastDateFormat specific.
ZZ supports "ISO 8601 extended format time zones" but it seems FastDateFormat specific option.
I misunderstood this is compatible format with SimpleDateFormat when this change is introduced.
Please see SimpleDateFormat documentation and FastDateFormat documentation.
It seems we better replace ZZ to XXX because they look using the same strategy - FastDateParser.java#L930, FastDateParser.java#L932-L951  and FastDateParser.java#L596-L601.
I also checked the codes and manually debugged it for sure. It seems both cases use the same pattern ( Z|(?:[+-]\\d{2}(?::)\\d{2})).
Note that this should be rather a fix about documentation and not the behaviour change because ZZ seems invalid date format in SimpleDateFormat as documented in DataFrameReader and etc, and both ZZ and XXX look identically working with FastDateFormat
Current documentation is as below:
   * <li>`timestampFormat` (default `yyyy-MM-dd'T'HH:mm:ss.SSSZZ`): sets the string that
   * indicates a timestamp format. Custom date formats follow the formats at
   * `java.text.SimpleDateFormat`. This applies to timestamp type.</li>

How was this patch tested?
Existing tests should cover this. Also, manually tested as below (BTW, I don't think these are worth being added as tests within Spark):
Parse
scala> new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000-11:00")
res4: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala>  new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000Z")
res10: java.util.Date = Tue Mar 21 09:00:00 KST 2017

scala> new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-11:00")
java.text.ParseException: Unparseable date: "2017-03-21T00:00:00.000-11:00"
  at java.text.DateFormat.parse(DateFormat.java:366)
  ... 48 elided
scala>  new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000Z")
java.text.ParseException: Unparseable date: "2017-03-21T00:00:00.000Z"
  at java.text.DateFormat.parse(DateFormat.java:366)
  ... 48 elided

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000-11:00")
res7: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000Z")
res1: java.util.Date = Tue Mar 21 09:00:00 KST 2017

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-11:00")
res8: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000Z")
res2: java.util.Date = Tue Mar 21 09:00:00 KST 2017

Format
scala> new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").format(new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000-11:00"))
res6: String = 2017-03-21T20:00:00.000+09:00

scala> val fd = org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ")
fd: org.apache.commons.lang3.time.FastDateFormat = FastDateFormat[yyyy-MM-dd'T'HH:mm:ss.SSSZZ,ko_KR,Asia/Seoul]

scala> fd.format(fd.parse("2017-03-21T00:00:00.000-11:00"))
res1: String = 2017-03-21T20:00:00.000+09:00

scala> val fd = org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXXX")
fd: org.apache.commons.lang3.time.FastDateFormat = FastDateFormat[yyyy-MM-dd'T'HH:mm:ss.SSSXXX,ko_KR,Asia/Seoul]

scala> fd.format(fd.parse("2017-03-21T00:00:00.000-11:00"))
res2: String = 2017-03-21T20:00:00.000+09:00

cc @srowen and @ueshin, could you take a look please?

Test build #75413 has started for PR 17489 at commit a0e332d.

Test build #75413 has finished for PR 17489 at commit a0e332d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75413/
Test PASSed.

Merged build finished. Test PASSed.

I see, so ZZ means something different to FastDateFormat, and what it means actually matches what XXX means to SimpleDateFormat? But FastDateFormat also supports XXX and supports it the same way? then this makes sense.
I think you need to check cases like "-1100" and "11". Is there any case that worked before but not after the change?

ZZ means something different to FastDateFormat, and what it means actually matches what XXX means to SimpleDateFormat?

Yes, it seems so given my tests and checking the codes.

But FastDateFormat also supports XXX and supports it the same way?

Yes, it is.

I think you need to check cases like "-1100" and "11".

Up to my knowledge, both cases should be XX and X for each. It seems throwing an exception as below if we use XXX or ZZ.
scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000-1100")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-1100
  at org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
  at org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
  ... 48 elided

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXXX").parse("2017-03-21T00:00:00.000-11")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-11
  at org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
  at org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
  ... 48 elided

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-1100")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-1100
  at org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
  at org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
  ... 48 elided

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-11")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-11
  at org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
  at org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
  ... 48 elided

XX and X test for both as below:
scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSXX").parse("2017-03-21T00:00:00.000-1100")
res18: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSX").parse("2017-03-21T00:00:00.000-11")
res19: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala> new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSXX").parse("2017-03-21T00:00:00.000-1100")
res20: java.util.Date = Tue Mar 21 20:00:00 KST 2017

scala> new java.text.SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSX").parse("2017-03-21T00:00:00.000-11")
res21: java.util.Date = Tue Mar 21 20:00:00 KST 2017

Is there any case that worked before but not after the change?

I understand this concern and that's why I checked the codes. They look using the same timezone pattern for both ZZ and XXX - FastDateParser.java#L930, FastDateParser.java#L932-L951  and FastDateParser.java#L596-L601.

I think the question is: would this cause any input that currently works to not work?
It's not a deal-breaker but that's the question. Doesn't "-1100" work right now? it would stop working if the default is XXX. According to the docs, the current default of ZZ should allow that and it seems to work.
If it's a corner case we need to break in order to fix bigger problems, that's possible, but just trying to quantify that. That is, maybe this is also solvable with a doc change, to describe correctly what it currently does rather than change what it does?

I tested "-1100" cases before with ZZ.
I guess this was rather a bug in commons-lang but fixed after we upgrade commons-lang SPARK-17985. I just downloaded Spark 2.0.0 and test the codes below:
scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-1100")
res2: java.util.Date = Tue Mar 21 20:00:00 KST 2017

Spark 2.1.0:
scala> org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-1100")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-1100
  at org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
  at org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
  ... 48 elided

Let me just fix up the documentation if you are worried of it. I am fine with it.

Otherwise, let me ask if both ZZ to XXX are really the same to Apache commons user mailing list.

OK, then "-1100" doesn't work right now, though it used to. ZZ is supposed to support "-1100" according to the Java docs, but then again, that also suggests some things don't work which do actually work because we're using FastDateFormat. ZZ actually means, to FastDateFormat, what XXX means to the Java implementation? but both interpret XXX the same way?
It does seem simpler to standardize on XXX because it's clearer all around, if they both behave the same way and behave how ZZ already behaves. In that case, we do want to update the doc and implementation to use XXX, I think.
The problem is that "-1100" should have worked according to docs but didn't? I think that it's OK for it to continue to not work then.
More importantly, this is supposed to be the ISO 8601 default format right? and XXX means that, not ZZ.
It's a complex situation but I think this is good change for 2.2. Of course, this only affects the default. One can override with any specific format.

Yes. I asked a question to commons mailing list about this for clarity. Let me update you when I have an answer.

@srowen, I had a great answer about ZZ - here. It seems okay to use XXX instead.

I tried to grep this pattern. I think these are all if I haven't missed ones. Thanks for approving it.

Merged to master

Thank you for asking the details and merging it  @srowen.

No one knows what happened to you. Please file a JIRA with a full reproducer with full error messages with some analysis you can make.


Add @DefaultCommand(string description)

Discussion found at https://github.com/BradleyChatha/jcli/pull/5#discussion_r516807169

Using null is weird and unintuitive, even if it's just a "learn once and get over it" kind of thing.

Is it worth adding a UDA for this, when only a single default command will appear in most projects? Especially since the command itself can easily be named "DefaultCommand"?

I am leaning towards implementing it, since clarity is definitely something I'd like to have here, but again it's only for a single part of any tool's code that has this weird behaviour.
The default command does have special behaviour and limitations within CommandLineInterface though, so it also does make sense to make that difference more explicit beyond "passing null to a UDA".
If I can't think of a good reason not to do this by tomorrow, then I'll go ahead and implement it.

After second thought I'm taking back my comment about @DefaultCommand and would suggest to go with @CommandDefault. This will match other @Command* UDAs


Implement fail fast

Implement fail fast functionality, i.e check for the failure condition first and exit with an error instead of checking for a positive condition and continuing with the functionality.
https://github.com/XichengTong/SoftwareSupplyChainSecurity_HW1/blob/e32bee2352c30a83d3f281323abb1bd64c0ea378/main.py#L30

use `# Fail-fast check for failure condition to Implement fail fast functionality
    if response.status_code != 200:
        if debug:
            print(f"Failed to fetch log entry. Status code: {response.status_code}")
        return None`


[New Port Request] gnuradio

Library name:gnuradio
Library description:GNU Radio is a free & open-source software development toolkit that provides signal processing blocks to implement software radios. It can be used with readily-available, low-cost external RF hardware to create software-defined radios, or without hardware in a simulation-like environment. It is widely used in hobbyist, academic, and commercial environments to support both wireless communications research and real-world radio systems.
Source repository URL:https://github.com/gnuradio/gnuradio
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

This port's dependencies are not include in vcpkg now:

alsa
gmp
gsm
mplib
oss
portaudio
sphinx
swig
uhd

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.

@JackBoosY Most of the unpackaged dependencies are not required to build a workable GNU Radio installation. Infact, I'm not sure that any of those are. Swig has been replaced by Pybind11 in the next release of GNU Radio.


Two way audio not working

Hello. My english is not very good, sorry about that. This is my enviroment, config and hardware:
Camera: Dahua DH-IPC-HDW1430DT-STW with ONVIF Profile S / T

go2rtc server: Home Assistant addon on version 1.3.1.
 I'm missing something? Thanks in advance :)

You have some mixed log. It's hard to understand what's going on there. CSeq has random sequence.
You need to collect log from only one connection.

Thanks @AlexxIT . I just did it one more time (with just one stream opened) with the same result. There is a six differents CSeq  numbers. I will try to setup a new server with the Windows binary right now.

Using the binary for Windows I got more than one CSeq too. I am using stunnel for the SSL in Windows and Nginx Proxy Manager on Home Assistant.
13:54:32.925 INF go2rtc version 1.3.1 windows/amd64
13:54:32.930 INF [api] listen addr=:1984
13:54:32.933 INF [rtsp] listen addr=:8554
13:54:32.935 INF [srtp] listen addr=:8443
13:54:32.936 INF [webrtc] listen addr=:8555/tcp
13:55:22.068 TRC [rtsp] client request:
DESCRIBE rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif RTSP/1.0
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.3.1
CSeq: 1

13:55:22.078 TRC [rtsp] client response:
RTSP/1.0 401 Unauthorized
Cseq: 1
Www-Authenticate: Digest realm="Login to RANDSTRING",nonce="RANDNONCE"

13:55:22.079 TRC [rtsp] client request:
DESCRIBE rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif RTSP/1.0
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.3.1
CSeq: 2
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif", response="47e302f913753881941bdf8466b54ae4"
Accept: application/sdp

13:55:22.092 TRC [rtsp] client response:
RTSP/1.0 200 OK
X-Accept-Dynamic-Rate: 1
Content-Base: rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/
Content-Type: application/sdp
Cseq: 2
Cache-Control: must-revalidate
Content-Length: 574

v=0
o=-<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>
s=Media Server
c=IN IP4 <IP_ADDRESS>
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
m=video 0 RTP/AVP 96
a=control:trackID=0
a=framerate:20.000000
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D0032;sprop-parameter-sets=Z00AMukAUAFrQgAAAwACAAADACgIAA==,aOqPIAA=
a=recvonly
m=audio 0 RTP/AVP 8
a=control:trackID=1
a=rtpmap:8 PCMA/8000
a=recvonly
m=application 0 RTP/AVP 107
a=control:trackID=4
a=rtpmap:107 vnd.onvif.metadata/90000
a=recvonly

13:55:22.107 TRC [rtsp] client request:
SETUP rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=0 RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
CSeq: 3
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=0", response="1e524dbf6dcff91a55d8d8df657560ea"

13:55:22.121 TRC [rtsp] client response:
RTSP/1.0 200 OK
Cseq: 3
Session:<PHONE_NUMBER>;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=0-1;ssrc=8cde42e1
X-Dynamic-Rate: 1

13:55:22.148 TRC [rtsp] client request:
DESCRIBE rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1 RTSP/1.0
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.3.1
CSeq: 1

13:55:22.266 TRC [rtsp] client response:
RTSP/1.0 401 Unauthorized
Cseq: 1
Www-Authenticate: Digest realm="Login to RANDSTRING",nonce="31ffc4e4-be59-4105-bd74-6474957b0ee3"

13:55:22.269 TRC [rtsp] client request:
DESCRIBE rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1 RTSP/1.0
User-Agent: go2rtc/1.3.1
CSeq: 2
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="31ffc4e4-be59-4105-bd74-6474957b0ee3", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1", response="06043a27a7c3ea5a1ff8da89fff8fab2"
Accept: application/sdp
Require: www.onvif.org/ver20/backchannel

13:55:22.281 TRC [rtsp] client response:
RTSP/1.0 200 OK
Content-Base: rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1/
X-Accept-Dynamic-Rate: 1
Content-Type: application/sdp
Cache-Control: must-revalidate
Cseq: 2
Content-Length: 469

v=0
o=-<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>
s=Media Server
c=IN IP4 <IP_ADDRESS>
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
m=video 0 RTP/AVP 96
a=control:trackID=0
a=framerate:20.000000
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D001E;sprop-parameter-sets=Z00AHukBQHtCAAADAAIAAAMAKAgA,aOqPIAA=
a=recvonly
m=audio 0 RTP/AVP 8
a=control:trackID=1
a=rtpmap:8 PCMA/8000
a=recvonly

13:55:22.291 TRC [rtsp] client request:
SETUP rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=1 RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
CSeq: 4
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/trackID=1", response="d53626d6f2eca17a9ee9628cf5d6f70e"
Session:<PHONE_NUMBER>

13:55:22.301 TRC [rtsp] client response:
RTSP/1.0 200 OK
Cseq: 4
Session:<PHONE_NUMBER>;timeout=60
Transport: RTP/AVP/TCP;unicast;interleaved=2-3;ssrc=953fc6a5
X-Dynamic-Rate: 1

13:55:22.303 TRC [rtsp] client request:
TEARDOWN rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1/ RTSP/1.0
CSeq: 3
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="31ffc4e4-be59-4105-bd74-6474957b0ee3", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1/", response="74bf5656162833a0a0038e906be2ce74"

13:55:22.305 TRC [rtsp] client request:
PLAY rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/ RTSP/1.0
CSeq: 5
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/", response="2b131d61385bd15709c22c39a5051b94"
Session:<PHONE_NUMBER>

13:55:22.417 TRC [rtsp] client response:
RTSP/1.0 200 OK
Session:<PHONE_NUMBER>
Range:
Rtp-Info: url=trackID=0;seq=1;rtptime=0,url=trackID=1;seq=1;rtptime=0
Cseq: 5

13:55:47.310 TRC [rtsp] client request:
OPTIONS rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/ RTSP/1.0
Session:<PHONE_NUMBER>
CSeq: 6
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/", response="7f2350aa327f046ac0acc5a36f828cf5"

13:55:47.374 TRC [rtsp] client response:
RTSP/1.0 200 OK
Cseq: 6
Public: OPTIONS, DESCRIBE, ANNOUNCE, SETUP, PLAY, PAUSE, TEARDOWN, GET_PARAMETER, SET_PARAMETER, REDIRECT, RECORD
Server: Rtsp Server/3.0

13:56:12.367 TRC [rtsp] client request:
OPTIONS rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/ RTSP/1.0
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/", response="7f2350aa327f046ac0acc5a36f828cf5"
Session:<PHONE_NUMBER>
CSeq: 7

13:56:12.424 TRC [rtsp] client response:
RTSP/1.0 200 OK
Cseq: 7
Public: OPTIONS, DESCRIBE, ANNOUNCE, SETUP, PLAY, PAUSE, TEARDOWN, GET_PARAMETER, SET_PARAMETER, REDIRECT, RECORD
Server: Rtsp Server/3.0

13:56:37.420 TRC [rtsp] client request:
OPTIONS rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/ RTSP/1.0
CSeq: 8
Authorization: Digest username="admin", realm="Login to RANDSTRING", nonce="cc6850d7-7c6a-4501-a923-bf65ecafc199", uri="rtsp://<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif/", response="7f2350aa327f046ac0acc5a36f828cf5"
Session:<PHONE_NUMBER>

13:56:37.485 TRC [rtsp] client response:
RTSP/1.0 200 OK
Cseq: 8
Public: OPTIONS, DESCRIBE, ANNOUNCE, SETUP, PLAY, PAUSE, TEARDOWN, GET_PARAMETER, SET_PARAMETER, REDIRECT, RECORD
Server: Rtsp Server/3.0

How your go2rtc config looks like? And how you start stream?

How your go2rtc config looks like? And how you start stream?

Current config:

log:
  level: info  # default level
  api: info
  exec: info
  ngrok: info
  rtsp: trace
  streams: info
  webrtc: info

streams:
  dahua_camera:
    - rtsp://admin:admin@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
    - rtsp://admin:admin@<IP_ADDRESS>/cam/realmonitor?channel=1&subtype=1

I am using a Web Browser (Chrome right now) to start the stream. I am using the link provided in go2rtc web ui under "WebRTC Magic": https://<IP_ADDRESS>:1985/webrtc.html?src=dahua_camera&media=video+audio+microphone

1985? You have changed this port via docker?

Oh. I see. Your camera doesn't support ONVIF T.
It has no backchannel track in the response. So go2rtc starts a second stream and tries to find the backchannel there.
Maybe your camera has different firmwares or different models with real ONVIF T support.

OK. You can reopen this issue then

As you correctly noted, just the camera model does not guarantee anything. You also need the right firmware.
So the list of supported cameras can create even more problems.


Improve plot clarity with combined mean and HDI legend elements

Closes #142 and #143.

Previously the figure legends were quite messy. The main thing this PR does is to create single legend entries which include both the central tendency and the HDI. This is actually a bit involved and so we now build up a list of handles and labels in the plotting functions. With this we can call ax.legend once at the end of the plot functions. See my StackOverflow question and post on Twitter.
I updated the plot methods for all the pymc experiments to use this new approach. There is certainly still scope for slight improvement, but I think this is a good step forward in improving the plots.

Examples for synthetic control plots...
Before

After
Note the combined line+shaded region in the legend

Examples for difference in differences
Before

After

[ ] I should update the plots in README

I originally tried to do this on a better way, with everything handled internally in the plot function. But I ran into problems. It may be that I discovered a bug in matplotlib. See the solution here https://stackoverflow.com/a/74935897 If this can be made to work, it would be much cleaner.

Thanks for the comments @juanitorduz. I believe I've dealt with all those changes except for an external axis legend. I agree that it's suboptimal for the synthetic control plots, but I'll improve it in a separate PR.
I also re-ran some notebooks because I was not fond of the green shaded region for the causal impact.

Just left a comment regarding a commented line: either remove or uncomment ;) Feel free to merge.


The platform currently works in optimistic mode, which means it does not obtain states from MQTT topics, but it sends and remembers control commands.
It uses a sensor under the hood to obtain the current temperature.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3111
Example entry for configuration.yaml (if applicable):
climate:
  - platform: mqtt
    name: Study
    target_sensor: sensor.study_temperature

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New files were added to .coveragerc.

Here's the use of climate.mqtt with broadlink for controlling AC: https://community.home-assistant.io/t/ac-temperature-with-broadlink/16869/2?u=clkao

@clkao any updates on this PR?

@clkao Would love to see this make it into 0.53 or 0.54, but there are a few changes that have been requested.

@dale3h oops, I've been a bit busy.  I believe the remaining is the doc update (please help!) and improving coverage (essential methods are tested).

The coverage is to low https://coveralls.io/builds/12726373/source?filename=homeassistant%2Fcomponents%2Fclimate%2Fmqtt.py please set that over 94%

Ping. Can you add more test? I try to merge it for next release if you finish the unittests :+1:

I'd love to see that component merged! However, I think it's a bit weird that the temperature is being read from a separate sensor. It's a MQTT climate device - shouldn't it get its temperature via MQTT (or at least be able to get the temperature via MQTT)? If you're using it with a physical device (i.e., the other side of the MQTT connection) that does not allow to read temperature values, you can still setup a different sensor and push its values to MQTT via a simple automation.

@clkao are you still interested in finishing this? Otherwise I'd 'adopt' this PR, add some tests, add a possibility to receive temperature via MQTT, …

@tinloaf please proceed.  I won't have much time on this until mid-Oct.

Thanks. :) I just moved your commits over to my new pull request #9589 and added tests as well the possibility to receive the current temperature via MQTT.

Thanks, @tinloaf! I've edited the description of this PR.


Update scancode.io models to handle new scancode-toolkit scan fields

In a scancode JSON output, all Packages detected in a scan are present in a top-level attribute named packages. Likewise, all detected Dependencies are placed in the dependencies attribute. Multiple copies of the same package can be present in the packages field, if a particular package was detected multiple times in the same codebase. Each copy of this package will have a different package_uid. A package_uid is the purl of that package with a qualifier named uuid that is specific to the scancode run.  e.g. pkg:pypi/django-audit-tools@0.4.0?uuid=9c19275c-c3fe-43dd-b6ec-a4f2bf65810f
For each Resource that is for a Package, the for_packages for those Resources will be populated with the package_uid of the Package they are for.
We will need to create a DiscoveredDependency model to handle the dependencies from the new top-level dependency attribute from a scan.
We also need to modify the DiscoveredPackage model to better store/query the new package_uid values. Currently, we put the package_uids for a package in the extra_data field.
The serializers of these models will have to be updated as well.
The value in a Resource's for_packages field is not a purl, but a package_uid. for a particular instance of a Package detected during a scan. In the new output, multiple copies of the same package can appear in the top-level packages field. Each copy has a different package_uid. We'll have to find a way to keep the package_uids around on Resources and to display the package_uids properly in the for_packages field in the scancode.io JSON output.

@JonoYang are we now ready to close this on?

@tdruez This is finished now that #486 is merged.


Implementation of drawing an Image into context

This change is

#1235  #1245

:shipit:

:shipit:


CB-13108:Add validations for accepting CMK from create-aws-environment cli

See detailed description in the commit message.

@satyabollineni The commit history seems to be messed up, there are two unrelated commits.

Some asks. Also a general q: As I see, processing of the new ARN field is still missing, so e.g. it is not set in the DTO nor in the entity, not persisted to the DB. I suppose these parts will come in subsequent PR(s), perhaps as part of CB-13110.

Yes, Just splitting the PR's so that review would be easier and faster. I will make the changes in DTO files in parallel.

@bergerdenes My local gradle build was success but the PR bot is continuously failing for the same error. I tried adding escape characters  in the regex but no luck in PR bot(local build passes without escape characters as well. Could you please help me with some pointers to avoid this PR bot failure?


Bash process terminates on VirtualBox cloned machine.

I am running a virtual box runner, that starts 3 concurrent machines, and runs the same script on the 3 of them (At the point of the error).
2 of the machines run successfully (the machines are cloned from the same image and the same snapshot).
In one of the machines, the output i see in the pipelines window usually stops at the middle of execution (without error, or prior notice).
When I logged into the machine I noticed that the command executed finished (it built around 5 modules, I stopped seeing the output on the 2nd module).
When I look at the task manager, I see no bash processes as opposed to the machines in which the script completed as needed.
I tried to think what could cause the ssh connection / cygwin bash window to close, but found nothing on the windows event log (only seen the sshd user log-on event).
Any ideas?

This is a mirror repository, it litteraly says "Mirror of GitLab CI, please use GitLab.com repo for issues https://gitlab.com/gitlab-org/gitlab-ce".
This repository has been inactive for over a year!


feat: adds support for stdout.

This PR adds support for stdout as output for debug log. Most of the references to stdout in modsec world points to /dev/stdout as the target although it isn't idiomatic to Windows.

Thank you for contributing to Coraza WAF, your effort is greatly appreciated
Before submitting check if what you want to add to coraza list meets quality standards before sending pull request. Thanks!

Make sure that you've checked the boxes below before you submit PR:

[ ] My code includes positive and negative tests.
[ ] I have an appropriate description with correct grammar.
[ ] I have read Contribution guidelines, maintainers note and Quality standard.
[ ] My code is properly linted and passes pre-commit tests.

Thanks for your contribution :heart:

@fzipri actually this is debug log and most of the usages I saw (did a
quick research in GitHub/Google) was pointing to /dev/stdout. More so this
started as a need for us to display logs in stdout so I would hold the
addition of stderr until someone request for it.
On Fri, 30 Sept 2022, 14:16 Felipe Zipitría, @.***>
wrote:

@.**** commented on this pull request.
In internal/corazawaf/waf.go
https://github.com/corazawaf/coraza/pull/449#discussion_r984528688:

@@ -420,9 +420,15 @@ func (w *WAF) SetDebugLogPath(path string) error {
w.Logger.SetOutput(io.Discard)
return nil
}

if path == "/dev/stdout" {

What about using stderr? Should this deserve also a case for it?
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/pull/449#discussion_r984528688, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAVLI5NLPZRBJHONMUDWA3KZRANCNFSM6AAAAAAQZTU3XY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I added support for stderr as per @fzipi and @anuraaga suggestion.

Approved! :)