text:
States panel only shows color attributes for Hue bulbs when I open the color picker on the Hue app

Home Assistant release with the issue:

0.67.1
Last working Home Assistant release (if known):
Not sure when it changed but definitely working in the past.
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io on RPi3
Component/platform:

https://www.home-assistant.io/components/light/
Description of problem:
The states panel only shows color attributes when the color picker is open on my mobile phone.

This is what it looks like.
I then have to open the color picker on my hue app (this screen)

And then the states page magically refreshes with all color attributes.

After closing the color picker within the Hue app, the states page will again refresh back to the original screenshot, without color attributes.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  bridges:
    - host: 192.168.1.109
      allow_unreachable: true

Traceback (if applicable):

Additional information:

The Hue states will not show color information when a white color (i.e. color_temp) is set.

authors: CheeseySandal amelchio

repo: home-assistant/home-assistant


text:
Neato Botvac D7 Latest Firmware (4.3.1) Causes Component Not To Setup

Home Assistant release with the issue:

All after this firmware update
Last working Home Assistant release (if known):
None after this firmware update
Operating environment (Hass.io/Docker/Windows/etc.):

All environments impacted
Component/platform:

neato:
https://www.home-assistant.io/components/neato
Description of problem:
After updating to firmware 4.3.1 HA will fail to load as neato has changed the cleaning service name.  This issue is a problem with the dependency and it is fixed in this PR: https://github.com/stianaske/pybotvac/pull/28
Once it is merged and a new version of the dependency is pushed to pypi I will submit a PR to correct this.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
neato:
  username: username
  password: password

Traceback (if applicable):
Error during setup of component neato
Traceback (most recent call last):
  File "/home/pi/home-assistant/homeassistant/setup.py", line 148, in _async_setup_component
    component.setup, hass, processed_config)  # type: ignore
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/pi/home-assistant/homeassistant/components/neato.py", line 154, in setup
    hass.data[NEATO_LOGIN] = NeatoHub(hass, config[DOMAIN], Account)
  File "/home/pi/home-assistant/homeassistant/components/neato.py", line 178, in __init__
    self._hass.data[NEATO_ROBOTS] = self.my_neato.robots
  File "/home/pi/home-assistant/lib/python3.6/site-packages/pybotvac/account.py", line 63, in robots
    self.refresh_robots()
  File "/home/pi/home-assistant/lib/python3.6/site-packages/pybotvac/account.py", line 111, in refresh_robots
    endpoint=robot['nucleo_url']))
  File "/home/pi/home-assistant/lib/python3.6/site-packages/pybotvac/robot.py", line 42, in __init__
    raise UnsupportedDevice("Version " + self.service_version + " of service houseCleaning is not known")
pybotvac.robot.UnsupportedDevice: Version basic-4 of service houseCleaning is not known

Additional information:

Same issue, same log. Just to confirm:
Error during setup of component neato Traceback (most recent call last):   File "/usr/local/lib/python3.6/site-packages/homeassistant/setup.py", line 148, in _async_setup_component     component.setup, hass, processed_config)  # type: ignore   File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.6/site-packages/homeassistant/components/neato.py", line 103, in setup     hass.data[NEATO_LOGIN] = NeatoHub(hass, config[DOMAIN], Account)   File "/usr/local/lib/python3.6/site-packages/homeassistant/components/neato.py", line 127, in __init__     self._hass.data[NEATO_ROBOTS] = self.my_neato.robots   File "/usr/local/lib/python3.6/site-packages/pybotvac/account.py", line 64, in robots     self.refresh_robots()   File "/usr/local/lib/python3.6/site-packages/pybotvac/account.py", line 112, in refresh_robots     endpoint=robot['nucleo_url']))   File "/usr/local/lib/python3.6/site-packages/pybotvac/robot.py", line 42, in __init__     raise UnsupportedDevice("Version " + self.service_version + " of service houseCleaning is not known") pybotvac.robot.UnsupportedDevice: Version basic-4 of service houseCleaning is not known

@rafuz so you don't get stuck, I have updated my custom component and personal repo with the D7 code and latest changes: https://github.com/dshokouhi/hass-neato-custom-component
to revert back you just need to remove the files and restart

Got my D7 yesterday and was curious about HASS integration, and I'm happy to say your extra commits did the trick for me!
Thank you!

Hi,
Im new to home assistant. Where can i add this code for Neato? Im using HA for docker/qnap.
B/rgs Mads

Hi mjuhldk,
Instructions are included with the github link
[(https://github.com/dshokouhi/hass-neato-custom-component)]
kind regards,
Ruben

Got this error:
Mon Dec 10 2018 12:08:04 GMT+0100 (Centraleuropæisk normaltid)
Error during setup of component neato
Traceback (most recent call last):
File "/usr/src/app/homeassistant/setup.py", line 148, in
_async_setup_component
component.setup, hass, processed_config)  # type: ignore
File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/neato.py", line 155, in setup
hass.data[NEATO_LOGIN] = NeatoHub(hass, config[DOMAIN], Account)
File "/config/custom_components/neato.py", line 179, in init
self._hass.data[NEATO_ROBOTS] = self.my_neato.robots
File "/config/deps/lib/python3.6/site-packages/pybotvac/account.py",
line 63, in robots
self.refresh_robots()
File "/config/deps/lib/python3.6/site-packages/pybotvac/account.py",
line 109, in refresh_robots
endpoint=robot['nucleo_url']))
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 41, in init
if self.service_version not in SUPPORTED_SERVICES:
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 213, in service_version
return self.available_services['houseCleaning']
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 209, in available_services
return self.state['availableServices']
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 205, in state
return self.get_robot_state().json()
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 163, in get_robot_state
return self._message({'reqId': "1", 'cmd': "getRobotState"})
File "/config/deps/lib/python3.6/site-packages/pybotvac/robot.py",
line 60, in _message
response.raise_for_status()
File "/usr/local/lib/python3.6/site-packages/requests/models.py",
line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
https://nucleo.neatocloud.com/vendors/neato/robots/OPS35518-30451178BEA2/messages
Den man. 10. dec. 2018 kl. 11.01 skrev rudeq notifications@github.com:

Hi mjuhldk,
Instructions are included with the github link
[(https://github.com/dshokouhi/hass-neato-custom-component)]
kind regards,
Ruben
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/19044#issuecomment-445757742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Arot-XyZUzo1Hk0Q-exomMK1gMU4f0Fgks5u3jDigaJpZM4ZDEPC
.

Hi.
A reset of the botvac fixed the issue.
Thanks
Regards mads
man. 10. dec. 2018 kl. 16.30 skrev Daniel Shokouhi <notifications@github.com

:

@mjuhldk https://github.com/mjuhldk that error usually means the botvac
is either not connected to wifi or it needs to be restarted. Can you check
the status of the botvac in the neato app and make sure you can still
control it? Restarting the botvac usually fixes that error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/19044#issuecomment-445856297,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Arot-Zx0iuN3ooCKrJRsUJBgDPEt_efKks5u3n4FgaJpZM4ZDEPC
.

When this fix will be in home assistant?

@rafuz we need pybotvac to release a new pypi package since the PR was merged, then I can submit a PR to bump the library.

Dear,
https://github.com/stianaske/pybotvac/commit/1d39638ae0c0081d266e7ad74e0bf89d9971442b
seems to be fixed.
Could you fix in ha?
Thanks

source: gharchive/issue

authors: dshokouhi iosdal mjuhldk rafuz rudeq

license_type: permissive

license_source: github-api


text:
websocket regression in 0.84.x

Home Assistant release with the issue:
0.84.1 - 0.84.6
Last working Home Assistant release (if known):
0.83.3
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 18.04.1 LTS x86_64
Component/platform:
Websocket API
Description of problem:
A regression from 0.83.3, any 0.84.x release so far will not permit me to subscribe to events. I authenticate using api_password.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
websocket_api:

http:
  api_password: !secret http_password

Traceback (if applicable):
2018-12-22 10:19:38 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139957755556136] Error handling message: {'id': 7702, 'type': 'subscribe_events', 'event_type': 'state_changed'}
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/websocket_api/connection.py", line 66, in async_handle
    handler(self.hass, self, schema(msg))
  File "/usr/local/lib/python3.6/dist-packages/homeassistant/components/websocket_api/commands.py", line 102, in handle_subscribe_events
    if not connection.user.is_admin:
AttributeError: 'NoneType' object has no attribute 'is_admin'

Additional information:

If I switch my websocket client authentication from api_password to access_token, it works again. This appears to be a regression specific to the legacy api password authentication.

I already reported this as #19522

authors: FezVrasta Human


text:
Sonos Play 1 issues

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.54.0
**Description of problem:**Errors in log. I have 2 Sonos Play 1, 1 works fine but the 2nd on there are the errors below and I can restart a stream that was playing via HA but I cannot stop it.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/aiohttp/web_protocol.py", line 422, in start
resp = yield from self._request_handler(request)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/aiohttp/web.py", line 306, in _handle
resp = yield from handler(request)
File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
res = yield from res
File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
res = yield from res
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
return (yield from handler(request))
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/http/init.py", line 428, in handle
result = yield from result
File "/usr/lib/python3.4/asyncio/coroutines.py", line 143, in coro
res = yield from res
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/websocket_api.py", line 388, in handle
yield from self._writer_task
File "/usr/lib/python3.4/asyncio/futures.py", line 390, in iter
return self.result()  # May raise too.
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
result = coro.throw(exc)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/websocket_api.py", line 238, in _writer
yield from self.wsock.send_json(message, dumps=JSON_DUMP)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/aiohttp/http_writer.py", line 128, in drain
yield from self._protocol._drain_helper()
File "/usr/lib/python3.4/asyncio/streams.py", line 197, in _drain_helper
yield from waiter
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in iter
yield self  # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/asyncio/selector_events.py", line 582, in _read_ready
data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2017-09-25 01:22:27 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.dining_room is taking over 10 seconds
2017-09-25 01:22:28 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:05:54 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.dining_room is taking over 10 seconds
2017-09-25 02:05:55 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:06:06 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:06:17 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:06:28 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:06:32 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2017-09-25 02:06:38 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:06:49 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:00 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:11 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:22 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:33 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:44 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:07:55 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:06 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:17 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:28 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:39 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:50 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:08:51 ERROR (MainThread) [homeassistant.helpers.entity] Update for media_player.dining_room fails
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 386, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 382, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.4/http/client.py", line 1172, in getresponse
response.begin()
File "/usr/lib/python3.4/http/client.py", line 351, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.4/http/client.py", line 313, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.4/socket.py", line 371, in readinto
return self._sock.recv_into(b)
ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
timeout=timeout
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 649, in urlopen
_stacktrace=sys.exc_info()[2])
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 357, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/packages/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
chunked=chunked)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 386, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 382, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.4/http/client.py", line 1172, in getresponse
response.begin()
File "/usr/lib/python3.4/http/client.py", line 351, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.4/http/client.py", line 313, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/lib/python3.4/socket.py", line 371, in readinto
return self._sock.recv_into(b)
requests.packages.urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 225, in async_update_ha_state
yield from self.hass.async_add_job(self.update)
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in iter
yield self  # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/sonos.py", line 458, in update
if self._player.is_coordinator:
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/soco/core.py", line 333, in is_coordinator
self._parse_zone_group_state()
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/soco/core.py", line 775, in _parse_zone_group_state
cache_timeout=5)['ZoneGroupState']
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/soco/services.py", line 656, in GetZoneGroupState
return self.send_command('GetZoneGroupState', *args, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/soco/services.py", line 387, in send_command
data=body.encode('utf-8')
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/api.py", line 112, in post
return request('post', url, data=data, json=json, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/api.py", line 58, in request
return session.request(method=method, url=url, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
resp = self.send(prep, **send_kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
r = adapter.send(request, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/requests/adapters.py", line 488, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2017-09-25 02:09:22 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.dining_room is taking over 10 seconds
2017-09-25 02:09:23 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 02:10:06 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.dining_room is taking over 10 seconds
2017-09-25 02:10:07 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-09-25 03:00:53 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.dining_room is taking over 10 seconds
2017-09-25 03:00:54 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10

any idea on this one please?

does no one else get this?

This looks like local connectivity problems. Are you still seeing these errors?

I'm having the same error:
2017-12-14 06:31:56 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 06:58:18 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 07:30:15 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 08:35:55 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 13:52:54 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 14:16:17 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 16:22:46 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 17:45:58 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 18:09:13 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
2017-12-14 18:38:29 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10

Tested this file, custom_components/media_player/sonos.py in my configuration to remove the same timeout error and lost all updating of media_player state cards, state <> shows the first media player with song playing the rest do not after restart and all show they are coordinators after the first song ends no more updates. ???

Right, that one no longer works with current HA. Try this one instead.
My rework has now been merged and will be in 0.64.

Yep Works perfect Thanks

brilliant.. thank you


text:
Feature alexa launch request

Description:
Add intent script support for the LaunchRequest skill request type.
Note: New to python, so may have made some coding standard violations.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3104
Example entry for configuration.yaml (if applicable):
intent_script:
  amzn1.ask.skill.08888888-7777-6666-5555-444444444444:
    action:
      service: script.turn_on
      entity_id: script.red_alert
    speech:
      type: plain
      text: OK

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:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @steverhoades,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Can you add a test

@balloob added some tests to cover LaunchRequest.

source: gharchive/pull-request

authors: balloob homeassistant steverhoades


text:
Update node-abi to 2.1.1 for Electron 1.8.0 support

Otherwise "Could not detect abi for version 1.8.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron"
Please publish new version after merge if possible.

Workaround for Yarn:
"resolutions": {
    "node-abi": "^2.1.1"
  }

I don't think there's the need to release a new version since 2.1.1 satisfies the version requirements of ^2.0.0 (https://semver.npmjs.com/).
Since you're using yarn I think regenerating the yarn.lock file should solve the issue.

@lgeiger Problem is that yarn resolves ^2.0.0 to 2.0.3 And not to 2.1.1. I use Yarn 1.0. yarn upgrade doesn't help also.

Problem is that yarn resolves ^2.0.0 to 2.0.3 And not to 2.1.1. I use Yarn 1.0. yarn upgrade doesn't help also.

Woa, to me this looks like pretty serious bug in yarn.
In any case 👍 for merging this (Sorry, I don't have write access).

Things a more complicated. If I remove node_modules (and revert yarn.lock), it is resolved to 2.1.0. That's why in the electron-builder I always prefer to update dependencies version.

In any case :+1: for merging this (Sorry, I don't have write access).

You do now! :wink:

In any case :+1: for merging this (Sorry, I don't have write access).

You do now! :wink:

Thanks @ralphtheninja

authors: develar lgeiger ralphtheninja

license: MIT


text:
[Bug]: settings UI not loading

What happened?
Hello,
I am on the latest homebridge on Ubuntu and was using the Eufy plugin for a while now. I just noticed that the settings UI for this plugin no longer loads. I tried installing an older version, also tried on a completely separate system with a new Homebridge but it still does not load.  I have Eufy plugin v2.2.14.
Can someone please help?
Device Type
Station (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Ubuntu 18.04+ (Supported)
Relevant log output
None. The settings UI simple shows empty box.

config
None

hello, can you try using incognito browser mode ? Which browser are you using ?

okay Incognito worked. Strange. Not sure what got messed up with the cookies. I tried in two separate machines that I have homebridge on.

yeah, some times cache aren't refresh correctly especially when I'm updating the UI which was the case these last weeks. Thanks for your feedback, you should be fine by clearing the browser cache. I'm closing the issue.

repo: homebridge-eufy-security/plugin


text:
Show changes in logs

I suggest adding to logs info about every device status change. Look every this.platform.log.info() in the code below:
/**
     * Handle 'SET' requests from HomeKit
     * These are sent when the user changes the state of an accessory,
     * for example, turning on a Light bulb.
     */
    async setActive(value) {
        this.platform.log.debug(`Accessory: setActive() for device '${this.accessory.displayName}'`);
        const parameters = {
            operate: value === this.platform.Characteristic.Active.ACTIVE ? 1 : 0,
        };
        this.sendDeviceUpdate(this.accessory.context.device.deviceGuid, parameters);
		this.platform.log.info(`${this.accessory.displayName}: ${value === 1 ? "On" : "Off"}`);
    }
    async setTargetHeaterCoolerState(value) {
        this.platform.log.debug(`Accessory: setTargetHeaterCoolerState() for device '${this.accessory.displayName}'`);
        const parameters = {
            operate: 1,
        };
        switch (value) {
            case this.platform.Characteristic.TargetHeaterCoolerState.AUTO:
                parameters.operationMode = 0;
				this.platform.log.info(`${this.accessory.displayName}: Mode Auto`);
                break;
            case this.platform.Characteristic.TargetHeaterCoolerState.COOL:
                parameters.operationMode = 2;
				this.platform.log.info(`${this.accessory.displayName}: Mode Cool`);
                break;
            case this.platform.Characteristic.TargetHeaterCoolerState.HEAT:
                parameters.operationMode = 3;
				this.platform.log.info(`${this.accessory.displayName}: Mode Heat`);
                break;
            default:
                this.platform.log.error('Unknown TargetHeaterCoolerState', value);
                return;
        }
        this.sendDeviceUpdate(this.accessory.context.device.deviceGuid, parameters);
    }
    async setRotationSpeed(value) {
        this.platform.log.debug(`Accessory: setRotationSpeed() for device '${this.accessory.displayName}'`);
        const parameters = {};
        switch (value) {
            // See README for the mapping of slider position to Comfort Cloud payload.
            case 0:
                // HomeKit independently switches off the accessory
                // in this case, which triggers setActive().
                // Nothing to handle here, but documenting for clarity.
                break;
            case 1:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.Quiet;
				this.platform.log.info(`${this.accessory.displayName}: Quiet Mode`);
                break;
            case 2:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.One;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed 1`);
                break;
            case 3:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.Two;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed 2`);
                break;
            case 4:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.Three;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed 3`);
                break;
            case 5:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.Four;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed 4`);
                break;
            case 6:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.Five;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed 5`);
                break;
            case 7:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.Powerful;
				this.platform.log.info(`${this.accessory.displayName}: Powerful Mode`);
                break;
            case 8:
                parameters.ecoMode = enums_1.ComfortCloudEcoMode.AutoOrManual;
                parameters.fanSpeed = enums_1.ComfortCloudFanSpeed.Auto;
				this.platform.log.info(`${this.accessory.displayName}: Fan speed Auto`);
                break;
        }
        this.sendDeviceUpdate(this.accessory.context.device.deviceGuid, parameters);
    }
    async setSwingMode(value) {
        this.platform.log.debug(`Accessory: setSwingMode() for device '${this.accessory.displayName}'`);
        const parameters = {};
        if (value === this.platform.Characteristic.SwingMode.SWING_ENABLED) {
            // Activate swing mode
            // and (if needed) reset one set of fins to their default position.
            switch (this.platform.platformConfig.swingModeDirections) {
                case enums_1.SwingModeDirection.LeftRightAndUpDown:
                    parameters.fanAutoMode = enums_1.ComfortCloudFanAutoMode.AirSwingAuto;
					this.platform.log.info(`${this.accessory.displayName}: Swing mode Left/Right and Up/Down`);
                    break;
                case enums_1.SwingModeDirection.LeftRightOnly:
                    parameters.fanAutoMode = enums_1.ComfortCloudFanAutoMode.AirSwingLR;
                    parameters.airSwingUD = this.swingModeUpDownToComfortCloudPayloadValue(this.platform.platformConfig.swingModeDefaultPositionUpDown);
					this.platform.log.info(`${this.accessory.displayName}: Swing mode Left/Right`);
                    break;
                case enums_1.SwingModeDirection.UpDownOnly:
                    parameters.fanAutoMode = enums_1.ComfortCloudFanAutoMode.AirSwingUD;
                    parameters.airSwingLR = this.swingModeLeftRightToComfortCloudPayloadValue(this.platform.platformConfig.swingModeDefaultPositionLeftRight);
					this.platform.log.info(`${this.accessory.displayName}: Swing mode Up/Down`);
                    break;
                default:
                    parameters.fanAutoMode = enums_1.ComfortCloudFanAutoMode.AirSwingAuto;
					this.platform.log.info(`${this.accessory.displayName}: Swing mode Auto`);
                    break;
            }
        }
        else if (value === this.platform.Characteristic.SwingMode.SWING_DISABLED) {
            // Deactivate swing mode and reset fins to default positions.
            parameters.fanAutoMode = enums_1.ComfortCloudFanAutoMode.Disabled;
            parameters.airSwingLR = this.swingModeLeftRightToComfortCloudPayloadValue(this.platform.platformConfig.swingModeDefaultPositionLeftRight);
            parameters.airSwingUD = this.swingModeUpDownToComfortCloudPayloadValue(this.platform.platformConfig.swingModeDefaultPositionUpDown);
			this.platform.log.info(`${this.accessory.displayName}: Swing mode Off`);
        }
        this.sendDeviceUpdate(this.accessory.context.device.deviceGuid, parameters);
    }
    /**
     * Maps the internal left-right swing mode position enum to the corresponding
     * Comfort Cloud value.
     *
     * @param position The internal value for the left-right position.
     * @returns The corresponding Comfort Cloud value for the given position.
     */
    swingModeLeftRightToComfortCloudPayloadValue(position) {
        switch (position) {
            case enums_1.SwingModePositionLeftRight.Left:
                return enums_1.ComfortCloudAirSwingLR.Left;
            case enums_1.SwingModePositionLeftRight.CenterLeft:
                return enums_1.ComfortCloudAirSwingLR.CenterLeft;
            case enums_1.SwingModePositionLeftRight.Center:
                return enums_1.ComfortCloudAirSwingLR.Center;
            case enums_1.SwingModePositionLeftRight.CenterRight:
                return enums_1.ComfortCloudAirSwingLR.CenterRight;
            case enums_1.SwingModePositionLeftRight.Right:
                return enums_1.ComfortCloudAirSwingLR.Right;
            default:
                return enums_1.ComfortCloudAirSwingLR.Center;
        }
    }

I close because I added a pull request in this matter.


text:
Logs agent DaemonSet doesn't work on GKE

This is (1) really bad and (2) a bit baffling. When created in the kube-system namespace, the DaemonSet is deleted after ~30 seconds.
As a workaround, we could either use the default namespace, or create something like a honeycomb-system namespace.
There's also an argument for starting to use ksonnet here, since the namespace used for RBAC is coupled to the one the DaemonSet is deployed in.

Workarounds are now documented here: https://honeycomb.io/docs/connect/kubernetes/gke/, so closing this.

repo: honeycombio/kubernetes-manifests


text:
Client components are very slow and cause stack overflow

What version of Hono are you using?
4.5.4
What runtime/platform is your app running on?
Chrome
What steps can reproduce the bug?
Here's the full benchmark reproduction.
https://github.com/krausest/js-framework-benchmark/pull/1723
Hono is much slower than Solidjs, the reference fast framework. The current result makes Hono the slowest JS framework. Up to 100 times slower in a medium number of components, and the browser stack overflows when the number of components is high (benchmarks fail).

The profiler confirms the inefficient implementation of client components in Hono.

What is the expected behavior?
Have an acceptable performance, at least on par with React.
https://krausest.github.io/js-framework-benchmark/2024/table_chrome_127.0.6533.72.html
What do you see instead?
Use other frameworks like Solidjs for client components.
Additional information
No response

Hi @aminya, thank you for creating the issue!
I am investigating now, and we can probably achieve the expected performance, so wait a moment!

authors: aminya usualoma

repo: honojs/hono


text:
env(c) does not get overridden Bindings sent via app.request() but c.env does

What version of Hono are you using?
4.6.11
What runtime/platform is your app running on? (with version if possible)
Node
What steps can reproduce the bug?
Start the following with a DATABASE_URL=postgres://postgres:postgres@localhost:5432/postgres already defined at the system level
import { Hono, Context, Next } from 'hono'
import { env } from 'hono/adapter'

interface Bindings {
  DATABASE_URL: string
}

const app = new Hono<{ Bindings: Bindings }>()

app.use(async (c: Context<{ Bindings: Bindings }>, next: Next) => {
  const { DATABASE_URL } = env(c)

  console.log('Middleware env(c) DATABASE_URL', DATABASE_URL)
  console.log('Middleware c.env.DATABASE_URL', c.env.DATABASE_URL)

  return next()
})

app.get('/', async (c) => {
  const { DATABASE_URL } = env(c)

  console.log('Route env(c) DATABASE_URL', DATABASE_URL)
  console.log('Route c.env.DATABASE_URL', c.env.DATABASE_URL)

  c.text('ding!')
})

// override the Bindings
app.request('/', undefined, { DATABASE_URL: 'postgres://xxx:yyy@localhost:5432/zzz' })

What is the expected behavior?
I expect env(c) to get its values from the Bindings sent through app.request() the same way c.env does.
Middleware env(c) DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz
Middleware c.env.DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz

Route env(c) DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz
Route c.env.DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz

What do you see instead?
env(c) gets the old system defined DATABASE_URL while c.env gets the updated overridden Bindings passed by app.request()
Middleware env(c) DATABASE_URL postgres://postgres:postgres@localhost:5432/postgres
Middleware c.env.DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz

Route env(c) DATABASE_URL postgres://postgres:postgres@localhost:5432/postgres
Route c.env.DATABASE_URL postgres://xxx:yyy@localhost:5432/zzz

Additional information
No response

I think it seems to be expected result
https://github.com/honojs/hono/blob/main/src/helper/adapter/index.ts#L10

@EdamAme-x This isn't documented so it was unexpected behaviour.

That is documented in this section: https://hono.dev/docs/api/context#env. Or can you create a PR for a document for it?

@yusukebe sounds good. I'll probably try to have their docs reference each other and explain the slight differences in behaviour. Now to think how to word it correctly...

authors: EdamAme-x Soviut yusukebe


text:
refactor(utils/url): Decode parameters more accurately without performance degradation.

More accurate decoding in query string parsing. (e.g., encoded keys)
performance
The following are the results of a comparison between hono's v3.1.3 and fast-querystring (which is used in elysia) with a slight modification to the benchmarks/query-param added in this PR.
In some places, hono's v3.1.3 is faster because decoding is skipped, and compared to that, this PR has a performance decrease. Nevertheless, the speed reduction is slight, and the amount of code has not increased.
This should be changed as it is unsuitable for a framework not to get parameters right.
bun
$ npm run bench:bun

> bench:bun
> bun run ./src/bench.mts

cpu: Apple M2 Pro
runtime: bun 0.5.8 (arm64-darwin)

benchmark            time (avg)             (min … max)       p75       p99      p995
------------------------------------------------------- -----------------------------
• {"url":"http://example.com/?page=1","key":"page"}
------------------------------------------------------- -----------------------------
hono 3.1.3        65.82 ns/iter  (61.54 ns … 198.54 ns)  65.23 ns 117.97 ns 133.18 ns
hono with PR      66.68 ns/iter  (60.56 ns … 174.03 ns)  66.41 ns 123.95 ns  138.5 ns
fastQuerystring   90.34 ns/iter  (84.92 ns … 269.87 ns)  88.87 ns 143.85 ns 167.52 ns

summary for {"url":"http://example.com/?page=1","key":"page"}
  hono 3.1.3
   1.01x faster than hono with PR
   1.37x faster than fastQuerystring

• {"url":"http://example.com/?url=http://example.com&page=1","key":"page"}
------------------------------------------------------- -----------------------------
hono 3.1.3       158.91 ns/iter  (150.2 ns … 333.56 ns) 155.87 ns 217.88 ns 324.67 ns
hono with PR     121.36 ns/iter (111.56 ns … 219.51 ns) 119.86 ns 184.04 ns    193 ns
fastQuerystring  161.95 ns/iter  (152.05 ns … 230.4 ns) 163.67 ns 225.31 ns 227.72 ns

summary for {"url":"http://example.com/?url=http://example.com&page=1","key":"page"}
  hono with PR
   1.31x faster than hono 3.1.3
   1.33x faster than fastQuerystring

• {"url":"http://example.com/?page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3        93.51 ns/iter   (88.1 ns … 216.14 ns)  92.46 ns 146.49 ns 192.24 ns
hono with PR      98.15 ns/iter   (93.23 ns … 176.8 ns)  97.18 ns 149.85 ns 162.26 ns
fastQuerystring   88.39 ns/iter  (82.92 ns … 211.82 ns)  87.12 ns 143.22 ns 178.06 ns

summary for {"url":"http://example.com/?page=1"}
  fastQuerystring
   1.06x faster than hono 3.1.3
   1.11x faster than hono with PR

• {"url":"http://example.com/?url=http://example.com&page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3       181.37 ns/iter (170.66 ns … 302.08 ns) 180.01 ns 243.45 ns 247.03 ns
hono with PR     186.77 ns/iter (176.45 ns … 290.13 ns)  190.2 ns  246.7 ns 263.16 ns
fastQuerystring  162.25 ns/iter  (153.31 ns … 302.2 ns) 159.61 ns 227.72 ns 247.82 ns

summary for {"url":"http://example.com/?url=http://example.com&page=1"}
  fastQuerystring
   1.12x faster than hono 3.1.3
   1.15x faster than hono with PR

• {"url":"http://example.com/?url=http://example.com/very/very/deep/path/to/something&search=very-long-search-string"}
------------------------------------------------------- -----------------------------
hono 3.1.3       196.09 ns/iter  (183.96 ns … 276.2 ns) 194.43 ns 257.71 ns 272.48 ns
hono with PR     232.93 ns/iter (222.82 ns … 309.85 ns) 231.97 ns 294.33 ns 299.66 ns
fastQuerystring  259.47 ns/iter (249.71 ns … 319.48 ns) 258.02 ns 315.05 ns 315.56 ns

summary for {"url":"http://example.com/?url=http://example.com/very/very/deep/path/to/something&search=very-long-search-string"}
  hono 3.1.3
   1.19x faster than hono with PR
   1.32x faster than fastQuerystring

• {"url":"http://example.com/?search=Hono+is+a+small,+simple,+and+ultrafast+web+framework+for+the+Edge.&page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3       184.92 ns/iter (174.18 ns … 326.26 ns) 187.11 ns 254.86 ns 256.74 ns
hono with PR     621.62 ns/iter (576.61 ns … 810.12 ns)  623.6 ns 810.12 ns 810.12 ns
fastQuerystring  542.04 ns/iter (516.23 ns … 739.35 ns) 538.62 ns 710.87 ns 739.35 ns

summary for {"url":"http://example.com/?search=Hono+is+a+small,+simple,+and+ultrafast+web+framework+for+the+Edge.&page=1"}
  hono 3.1.3
   2.93x faster than fastQuerystring
   3.36x faster than hono with PR

• {"url":"http://example.com/?a=1&b=2&c=3&d=4&e=5&f=6&g=7&h=8&i=9&j=10"}
------------------------------------------------------- -----------------------------
hono 3.1.3       628.45 ns/iter (598.59 ns … 732.02 ns) 638.18 ns 732.02 ns 732.02 ns
hono with PR     658.52 ns/iter  (525.1 ns … 733.42 ns) 661.84 ns 733.42 ns 733.42 ns
fastQuerystring   301.3 ns/iter (283.41 ns … 388.77 ns) 302.77 ns 383.02 ns 388.77 ns

summary for {"url":"http://example.com/?a=1&b=2&c=3&d=4&e=5&f=6&g=7&h=8&i=9&j=10"}
  fastQuerystring
   2.09x faster than hono 3.1.3
   2.19x faster than hono with PR

node
$ npm run bench:node

> bench:node
> tsx ./src/bench.mts

cpu: Apple M2 Pro
runtime: node v18.14.0 (arm64-darwin)

benchmark            time (avg)             (min … max)       p75       p99      p995
------------------------------------------------------- -----------------------------
• {"url":"http://example.com/?page=1","key":"page"}
------------------------------------------------------- -----------------------------
hono 3.1.3        41.39 ns/iter  (37.95 ns … 516.84 ns)  43.52 ns  57.09 ns  60.73 ns
hono with PR      55.12 ns/iter     (52.5 ns … 68.3 ns)  57.14 ns  62.19 ns  64.97 ns
fastQuerystring   66.02 ns/iter  (63.96 ns … 372.19 ns)   65.9 ns  72.42 ns  73.45 ns

summary for {"url":"http://example.com/?page=1","key":"page"}
  hono 3.1.3
   1.33x faster than hono with PR
   1.6x faster than fastQuerystring

• {"url":"http://example.com/?url=http://example.com&page=1","key":"page"}
------------------------------------------------------- -----------------------------
hono 3.1.3        124.2 ns/iter  (118.8 ns … 131.31 ns) 126.15 ns 130.28 ns 130.52 ns
hono with PR      76.68 ns/iter    (73.77 ns … 88.6 ns)  79.09 ns  83.51 ns  84.45 ns
fastQuerystring  199.72 ns/iter (194.35 ns … 217.53 ns) 202.18 ns 211.56 ns 211.94 ns

summary for {"url":"http://example.com/?url=http://example.com&page=1","key":"page"}
  hono with PR
   1.62x faster than hono 3.1.3
   2.6x faster than fastQuerystring

• {"url":"http://example.com/?page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3        80.57 ns/iter  (77.79 ns … 104.94 ns)  82.96 ns  89.03 ns  99.25 ns
hono with PR      91.85 ns/iter    (87.9 ns … 107.6 ns)   93.9 ns 101.43 ns 103.75 ns
fastQuerystring   71.55 ns/iter   (68.54 ns … 86.92 ns)  74.12 ns  82.68 ns  82.95 ns

summary for {"url":"http://example.com/?page=1"}
  fastQuerystring
   1.13x faster than hono 3.1.3
   1.28x faster than hono with PR

• {"url":"http://example.com/?url=http://example.com&page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3       164.39 ns/iter (153.94 ns … 197.98 ns) 168.11 ns 186.43 ns 196.59 ns
hono with PR     167.32 ns/iter (163.34 ns … 181.16 ns) 169.12 ns 176.17 ns 177.04 ns
fastQuerystring  202.08 ns/iter (195.31 ns … 213.89 ns) 204.75 ns  213.7 ns  213.7 ns

summary for {"url":"http://example.com/?url=http://example.com&page=1"}
  hono 3.1.3
   1.02x faster than hono with PR
   1.23x faster than fastQuerystring

• {"url":"http://example.com/?url=http://example.com/very/very/deep/path/to/something&search=very-long-search-string"}
------------------------------------------------------- -----------------------------
hono 3.1.3       161.58 ns/iter (156.25 ns … 172.65 ns)  163.5 ns 168.73 ns 172.38 ns
hono with PR     200.47 ns/iter (195.61 ns … 212.69 ns) 202.35 ns 210.52 ns 211.87 ns
fastQuerystring  400.78 ns/iter (393.91 ns … 439.39 ns) 402.97 ns 426.57 ns 439.39 ns

summary for {"url":"http://example.com/?url=http://example.com/very/very/deep/path/to/something&search=very-long-search-string"}
  hono 3.1.3
   1.24x faster than hono with PR
   2.48x faster than fastQuerystring

• {"url":"http://example.com/?search=Hono+is+a+small,+simple,+and+ultrafast+web+framework+for+the+Edge.&page=1"}
------------------------------------------------------- -----------------------------
hono 3.1.3       165.62 ns/iter (159.12 ns … 206.62 ns) 167.27 ns 182.45 ns 203.05 ns
hono with PR        646 ns/iter (634.85 ns … 691.84 ns) 647.97 ns 691.84 ns 691.84 ns
fastQuerystring  724.25 ns/iter (711.73 ns … 763.09 ns) 725.07 ns 763.09 ns 763.09 ns

summary for {"url":"http://example.com/?search=Hono+is+a+small,+simple,+and+ultrafast+web+framework+for+the+Edge.&page=1"}
  hono 3.1.3
   3.9x faster than hono with PR
   4.37x faster than fastQuerystring

• {"url":"http://example.com/?a=1&b=2&c=3&d=4&e=5&f=6&g=7&h=8&i=9&j=10"}
------------------------------------------------------- -----------------------------
hono 3.1.3       534.15 ns/iter  (524.4 ns … 561.31 ns) 536.08 ns 552.36 ns 561.31 ns
hono with PR     419.28 ns/iter (410.06 ns … 449.23 ns) 421.47 ns 439.72 ns 449.23 ns
fastQuerystring  397.81 ns/iter (388.85 ns … 414.47 ns) 400.37 ns 412.43 ns 414.47 ns

summary for {"url":"http://example.com/?a=1&b=2&c=3&d=4&e=5&f=6&g=7&h=8&i=9&j=10"}
  fastQuerystring
   1.05x faster than hono with PR
   1.34x faster than hono 3.1.3

Hi @usualoma !
Thanks for the PR.
I've implemented the decoding query parameters, but I needed more confidence. So I am thankful that this PR supports decoding + and keys with spaces. And I think it is good that you have created a benchmark. As for performance, it is faster than fast-querystring, which is great.
I'll merge it!

This change brings new bug.
?pretty&foo=bar could be resolved with { foo: 'bar' }, but now cannot be resolved

But with new query system：

Bug requested: https://github.com/honojs/hono/issues/1022

authors: tangye1234 usualoma yusukebe


text:
[Client types] make args param optional if the input has no required keys

This PR modifies the ClientRequest type, so the args param is only required if the input has required keys (specified by the validator).

See #1583

Oops. @MonsterDeveloper Could you run the command to prettify the code?
npx prettier --write ./src

@yusukebe done:)

Oops! Please run denoify!

Sorry, forgot about denoifying each commit:) Should be OK now.

Perfect! I'll merge it now and release the new version including this later. Thank you very much!!

authors: MonsterDeveloper yusukebe


text:
Update context.ts

Allow typecast in context.get(), e.g.
const user = context.get<User>('user');

Nice! Thank you!

authors: bkniffler yusukebe


text:
Try percentage padding

Map (at least) is offcenter on mobile

Centers after refresh. Also has white bar on right side of scrolled.

repo: hookom/climbontheway

license: mit

license_source: bigquery


text:
🛑 FWB is down

In cdefbd4, FWB ($FWB_SITE) was down:

HTTP code: 403
Response time: 392 ms

Resolved: FWB is back up in eebc42b after 46 minutes.

repo: hoopybe/uptime


text:
CB-13498 Consume new CM api to bulk decommission hosts (hosts/removeH…

…ostsFromCluster).
The new API is available from 7.2.13 (CM version 7.5.3), before that it will use the old approach.
See detailed description in the commit message.

Achievement unlocked: Commit over 100K changed lines. :smile:

authors: lajosrodek lturcsanyi

repo: hortonworks/cloudbreak


text:
Projection processor should support UDF with one or more arguments

Support projections with one or more arguments, constants and nested invocations. Some examples

upper(name)
concat(first, last)
substring(str, 0, 10)
lower(trim(text))

One option could be to have a code text editor with pop up and use the type information available in the UDF api to prompt for the arguments.

@shahsank3t , you should be able to pass functions as "expr" objects within projections as follows:
"projections":[{"expr":"LOWER(driverName) AS DN"},{"expr":"driverId"}]

Once #1224 is merged, we could introduce similar changes for projection processor.

Raised PR : https://github.com/hortonworks/streamline/pull/1255

thanks @sameer79 , merged #1255 to master

repo: hortonworks/streamline


text:
Exec tachikoma update 20160804151810

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage decreased (-0.009%) to 99.695% when pulling 290246d4a8ff8a72d6f5a9026479cbf424a3cda0 on pazjacket:tachikoma/update-20160804151810 into 77a776d257a2436999eb722afb99b372b7aa9f95 on hoshinotsuyoshi:master.

authors: coveralls pazjacket

repo: hoshinotsuyoshi/vultrlife


text:
Read_data_file function updated

Features added:

Custom separator support for text files.
Reading data from CSV files (with default separator ',')
Reading data from excel file with supported formats (xls, xlsx, xlsm, xlsb, odf, ods and odt)

Changes and specifications:

For txt files default separator is blank space that will deal with space-separated or line separated numbers.
header parameter is only for excel files.
The extension of the file is identified first and then the process is initiated.
For CSV file separator is set to ','.
For excel files parameter of the header to mention from which row to start reading numbers is available. To start from row 0, the header is kept None as default.
Excel files are read using pandas. Update required in the project requirements, to include pandas too.
Lines are stripped to avoid endline space to get included in the next line number.
The number which is read as a string is first converted in float and then to int, to avoid errors due to float as a string to int direct conversions.
Exception handling used with appropriate warning in case of exceptions to handle strings or unwanted data in middle.

I think idea files may be due to trial execution of the program on my side, I'll remove them.
Actually in the function earlier data was appended in a list as int, so I thought the list has to contain only int, but I'll change that and keep it float only, if I don't change it to float it will be string by default so as we are talking about numbers so float seems better.
I'll include the tests and also make the required changes to code style.

Oh, yeah you're right. The function earlier does seem to be appending ints, that's a nice catch. Unintended bug :D
Yes, I'm really happy with pretty much everything else, once the tests are ready and everything else is updated, I'd be glad to merge! Thanks a lot for the effort :)

And I would also like to suggest either the test file should be moved to probdists directory or the paths of all text files that are stored in probdists should be changed by adding probdists/ to the paths, otherwise, there are chances of path error in the text files names.

@errpv78 That's a good suggestion. For now, I used a hacky approach and just added another .parent for obtaining the path so as to not break the test.py file. You're welcome to improve this if you like(in this PR or a separate one, I'm fine with either) :)

Okay so I'll just add the tests and then we can finish this pr and later fix the paths thing in a new issue separately.

@errpv78 sounds good

The tests have been included and I have also corrected the issue of the tests in this pr only as to run tests that were necessary. Some changes have been made in test.py and probdists/init.py to include tests. The code format is also corrected.

@errpv78 could you refresh your fork to the latest version of the repo, and then modify the test.py file? It's a little difficult to resolve the conflicts and I'm afraid I might end up breaking something

Okay I'll do that

I have tried to resolve conflicts here, can you confirm if that had worked?

@errpv78 The errors are caused because pandas wasn't a part of the library before this PR, so the linters weren't installing it before checking the code. I have updated the github action now to install pandas, but I'm afraid you'll have to make a new PR for the updated github actions to run.
Secondly, don't forget you'll have to change the numbers sample data files' path, since right now they're located in the main directory, while in the code you proposed they'll have to be in the probdists directory so do take care of that. I see you didn't change the path of numbers_binomial.txt for example, and a few other .txt files so that will cause the code to fail.
Also, since you're now making a new PR, you might as well refresh your fork to the latest version and then submit the PR.
Cheers :)

@errpv78 Also, this PR is sort of an urgency because the other PRs made depend on it, so let me know if you could finish it by today, otherwise I'll have to let you wait for a couple of days :( and merge other PRs first, following which you'll be able to make your PR.

Okay, I'll refresh the fork and make the second PR shortly. So in that, I have to update the changes that couldn't be merged until now and update paths of txt files. Anything else?

@errpv78 That's right. Just to reiterate, I'll list the changes again:
Update read_data_file(), update path of files, add the new data files you created, add the TestGeneraldistribution class you created in test.py,  update test.py to use your modified file paths. If you want, you can also include a note about the usage of the updated read_data_file() function in USAGE.md, or you can do that in another PR when you've got time.
I hope that makes it clear!


text:
User is not able to open the details page of few orders

Note
JS error 'handler:TypeError: Cannot read properties of undefined (reading 'doclist')' is observed on console.
Current behavior
The details page does not open for some orders, leaving the user unable to view the order details.
Expected behavior
The details page should open and display the relevant information for every order when clicked.
Steps to reproduce the issue
Log in to the BOPIS App.
Navigate to the Orders section.
Click on an order to view its details.
Observe that the details page fails to load for certain orders.
Environment details
App version : V2.24.0
App environment : UAT
Additional information
Here is the detail of few orders in which this issue is observed
Instance - UCG-UAT(any super or admin user)
Facility - Frank And Oak - Mile End Menswear, Order - #1010102729
Facility - Frank And Oak - Quartier DIX30, Order - #1010102686
https://jam.dev/c/d8436e0c-f4ac-4c85-a6ad-aa17b05cae96

Issue verified and working fine in release v2.24.1. Hence, closing it.
https://jam.dev/c/797f1d73-27d6-4b0d-b423-ae28cb5b0140

repo: hotwax/bopis


text:
Incorrect Item and Sequence Number Display in Count Details After Switching Tabs

Current behavior
An incorrect item is displayed in the Count Details panel.
The sequence number does not match the item shown in the Pending tab.
Expected behavior
When switching to the Pending tab, the first item in the tab should be displayed in the Count Details panel.
The sequence number should correctly match the first item of the Pending tab.
Steps to reproduce the issue
Navigate to the Assigned section and select the Counted tab.
Select an item from the Counted tab and note its sequence number in the Count Details panel.
Switch to the All tab.
Navigate to the Pending tab.
Observe the item and sequence number displayed in the Count Details panel.
Environment details
App version : v2.3.1
App environment : UAT
Additional information
https://jam.dev/c/a9b02b99-87f3-4c9a-bbcb-9e6413acc209

@Adameddy26 This is also fixed in the release v2.3.4 please verify.

repo: hotwax/inventory-count


text:
The product results on the Catalog page lack padding at both ends.

Current behavior
The product results on the Catalog page lack padding at both ends.
Expected behavior
To enhance the appearance and spacing of the product results on the Catalog page, it is necessary to add padding at both ends. Padding must be 16px.
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

Closing as this issue is not relevant due to change in UI.

repo: hotwax/preorder


text:
[enhence]syncup/syncdown是否支持添加ignore文件，目前是手动写.sh配置dir来做的，是否有直接添加ignore的方法

syncup/syncdown是否支持添加ignore文件，
目前是手动写.sh配置dir来做的，是否有直接添加ignore的方法

感谢反馈。
这个我考虑过 #39 也有人提过，不过我不太喜欢向git那样的.ignore文件形式来实现：

如果按git的风格，ignore一般是逐层放置的，这样做有时候可能要一层层查下去看文件排除的设置，个人觉得不是那么方便。
场景方面和git有点不同，.gitingore可以算是git配置的一部分，但是ignore文件对于用户来讲就完全是多加的一个文件，不是很喜欢这种做法。
现在命令行有个参数--include-regex可以通过正则表达式来顾虑，不过会考虑加一个带文件参数来读取一个总的过滤配置。
还有一个办法是通过find命令之类的来做过滤工作，再调用·bypy·，当然这个办法比较敷衍。

--include-regex 在尝试用alias来实现了

authors: houtianze ryanemax

repo: houtianze/bypy


text:
Create Dockerfile

Create Dockerfile

#4 this is good!


text:
facebook payload not working

controller.hears('test', 'message_received', function(bot, message) {
var attachment = {
    'type':'template',
    'payload':{
        'template_type':'generic',
        'elements':[
            {
                'title':'Chocolate Cookie',
                'image_url':'http://cookies.com/cookie.png',
                'subtitle':'A delicious chocolate cookie',
                'buttons':[
                    {
                    'type':'postback',
                    'title':'Eat Cookie',
                    'payload':'chocolate'
                    }
                ]
            },
        ]
    }
};

bot.reply(message, {
    attachment: attachment,
});

});
controller.on('facebook_postback', function(bot, message) {
if (message.payload == 'chocolate') {
    bot.reply(message, 'You ate the chocolate cookie!')
}

});
But bot did not reply You ate the chocolate cookie!
Reason found

Closed due to inactivity.

I have the same issue...any fix about that?

@azanoni please start a new issue with an example of the code that doesn't work.

I started here https://github.com/howdyai/botkit/issues/814 its rare that a issue still not working for a year ago

I resolve this issue with this comment
https://github.com/hyperoslo/facebook-messenger/issues/15#issuecomment-216933326
The botkit readme should be updated.

@azanoni We are planning on a Facebook provisioning doc that contains a sane list of subscriptions to get you started, thanks for the reminder!

payload  will not work , you need to check the messages_postback in Webhook settings

authors: apotox azanoni peterswimm yaminodestiny

repo: howdyai/botkit


text:
What's kind of message?

I saw some Bot can post message like below format, I do not look like normal message.

Can we do that with botkit?
Thanks

Yes, you can do this using attachments.
See here for an example:
https://github.com/howdyai/botkit/blob/master/examples/demo_bot.js#L82

authors: ZuzooVn benbrown


text:
Caching Results

I'm wondering what the best way is to cache results.
So far I'm thinking of saving JSON for, let's say, activities returned from the API itself to a database, and then loading that into a calendar view or something. It would greatly reduce the number of API calls made every time I page through a calendar filled with activities for example. This method would require me to pull the JSON off of a model, but I don't know if that's possible with your library.
Now, I'm not sure this is the best approach, but I have nothing else :)
Is there perhaps another caching strategy that I could implement to save on API calls?

I just thought about this more and I don't think I need to model's complete JSON representation stored in my DB flavor of choice. I can cache what I need to show in the calendar interface and build something like the Calender week views from the stored cache data

repo: hozn/stravalib


text:
set_control is incorrect with regard to mode

The comment above set_control  is not quite correct with the docs.  From the API:
All control calls with mode must include heattemp and cooltemp parameters.
If you are in mode auto, it is perfectly legal to set ONLY heattemp and cooltemp.  The document is saying that heattemp and cooltemp must be supplied when we SET mode.  Not that mode needs to be supplied for heat/cool.
This is causing homeassistant (and the main.py test that ships with your library) to fail when trying to set the temp.   When I remove fan and mode from the urlencode line, and ONLY send heattemp and coldtemp, I am able to change my settings.
before:
set_control Fail {'error': True, 'reason': 'Mode change is not allowed when running schedule'}.
Heat setpoint is 72.0
Cool setpoint is 79.0

set_control Fail {'error': True, 'reason': 'Mode change is not allowed when running schedule'}.
Heat setpoint is 72.0
Cool setpoint is 79.0

after:
set_control Success!
Heat setpoint is 60.0
Cool setpoint is 90.0

set_control Success!
Heat setpoint is 72.0
Cool setpoint is 79.0

I believe the correct thing to do is this:
When setting fan, only set fan.
When setting heat/cool, set both heat cool and nothing else.
When setting mode, set mode, heat and cool.
No other set of operations works for me.
{"api_ver":3,"type":"residential"}

A voice from my NetBSD days!  Hi Tim!
Feel like submitting a patch?  I mean it seems reasonable.

Ha, I was wondering!  Lemme try to throw one together.

BTW, if you own one of these, which I assume you do, you might be interested in:
https://github.com/garbled1/gnhast-python-collectors/tree/master/venstar_influx
It's a tool that feeds the runtime data into influx.

I've been meaning to do something like that.  Looks better than what I was doing with my old RCS rs485 thermostat (shoving data into mysql and then worrying about it later).
If you do a pull request, I'll just approve it and then push a new release to pypi in the next day or two.

oh nevermind. just saw the pull request.  It's merged. (I'm far away from my Venstar thermostat so I can't test it).

Cool, once you push the new release, we should do a pullup req to hass to require that version.  :) Thanks!
I might tackle discovery for it in hass.  I had that working with SSDP in gnhast, so it should be easy to do in python.

ok. Just looking at Grafana and it's going to require some concerted effort.

https://github.com/home-assistant/home-assistant/pull/29954

Sweet.  Thanks Tyler.

authors: garbled1 hpeyerl tyler-public


text:
38 3.10 save email drafts

Refactoring of the email system, allow saving of email templates

Coverage decreased (-0.1%) to 99.867% when pulling 18b602a692d7086a1e68eae7a318ab46ae8afefc on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage decreased (-0.1%) to 99.867% when pulling 18b602a692d7086a1e68eae7a318ab46ae8afefc on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage remained the same at 100.0% when pulling a61e61f9b63bba58b6868678ab510650a0552b25 on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage decreased (-0.1%) to 99.869% when pulling 49b8b40635426552e21c1ebd391372d9db3c853a on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage decreased (-0.1%) to 99.869% when pulling 80378a95a767586051b0b86b37f7504663ee5603 on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage remained the same at 100.0% when pulling 3ec9f034c1cf1e8fef390268700aeda82c9088a2 on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage remained the same at 100.0% when pulling c94100c1476703cf0662999a788de0c1aebeca44 on 38_3.10_SaveEmailDrafts into a466c64fb2e6529f6f7fe787d558edf9ec2f3a6f on dev.

Coverage remained the same at 100.0% when pulling 9ee97abae815e4fcd5fcf8fa4a0a4e2b3f0f1f3c on 38_3.10_SaveEmailDrafts into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Coverage remained the same at 100.0% when pulling b0c84df5a54b90e6873d094db33c121f89f744aa on 38_3.10_SaveEmailDrafts into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Coverage decreased (-0.8%) to 99.218% when pulling 95a4b4b22b1cf7946e0a673871f56267ea8ee8a0 on 38_3.10_SaveEmailDrafts into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Coverage remained the same at 100.0% when pulling 52387e855490f91d4a94eaa070670048aa075857 on 38_3.10_SaveEmailDrafts into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Coverage remained the same at 100.0% when pulling 773247e90ab44ceb8053ea4a6e82c36d47467616 on 38_3.10_SaveEmailDrafts into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Coverage remained the same at 100.0% when pulling ece09b4ffe05062cbe0b583c1682350aaec01b33 on 38_3.10_SaveEmailDrafts into 23dfe3037caf7a7e29641b7cd74c2d9ec335d256 on dev.

Coverage increased (+0.02%) to 98.98% when pulling f49dc8d053d6a2a61b6605078aef2522ec6c066c on 38_3.10_SaveEmailDrafts into 48418a55dba13ec3e101caa2c8e28c1193ad9491 on dev.

Coverage increased (+0.02%) to 98.98% when pulling f49dc8d053d6a2a61b6605078aef2522ec6c066c on 38_3.10_SaveEmailDrafts into 48418a55dba13ec3e101caa2c8e28c1193ad9491 on dev.

Coverage increased (+0.002%) to 99.871% when pulling 27c9ffa029026388affac802b3f16ee868373ffb on 38_3.10_SaveEmailDrafts into a3d6c68b45e5df9e57578a4f9ce660fb37bd86be on dev.

Coverage remained the same at 100.0% when pulling db3e93b5148e565d6e3e4e3d0f9dbfb36bbddf19 on 38_3.10_SaveEmailDrafts into ba289f001f2e57e87f3b0abdac9ba4f64c1fe978 on dev.

Coverage decreased (-0.6%) to 99.399% when pulling 2b1c30e4633ea7773f6931a760637863691fd4b7 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage decreased (-0.4%) to 99.641% when pulling 41d9a35322b522695b7e5c174a3eb8bea73dac93 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage decreased (-0.4%) to 99.639% when pulling b98b43feb2e7e867a33722f3c7532240358d1fc0 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage remained the same at 100.0% when pulling b98b43feb2e7e867a33722f3c7532240358d1fc0 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage remained the same at 100.0% when pulling 6218fccba29a2808202bc33707e4bec94a0ee22b on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage remained the same at 100.0% when pulling c04f2ede9578c764cfde7edf91cda79ae73b4519 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage remained the same at 100.0% when pulling c04f2ede9578c764cfde7edf91cda79ae73b4519 on 38_3.10_SaveEmailDrafts into 873a45c0d1f0f583a01a27ee56a77bd895ecdda5 on dev.

Coverage remained the same at 100.0% when pulling a087cb0515067f129737bed4696587cc8e3cfb41 on 38_3.10_SaveEmailDrafts into 760a5036dd76e4a287707a07a8fa478227c795b3 on dev.

Coverage remained the same at 100.0% when pulling a86c5978bb4cffdc19889804373342f22c6db64e on 38_3.10_SaveEmailDrafts into e058c575315973e91984fa066e8b79ffcc7d5106 on dev.

Coverage remained the same at 100.0% when pulling 7877ec1e65dcce12778433b15ad5ffb3ff8f4493 on 38_3.10_SaveEmailDrafts into a2f3342d1e0e38080f19961abbf3bedb89648edb on dev.

🎉 🎉 🎉

authors: Baschdl TimBasel coveralls


text:
Is this package multi-threaded?

Is MosesPunctNormalizer.normalize() thread safe? It seems to be working but just wanted to double check.

It is, as long as you're not changing the string you passed into normalize() from another thread at the same time.

authors: ejkitchen jelmervdl

repo: hplt-project/sacremoses


text:
pecl install hprose 报错

安装hprose扩展，编译hprose_common.lo文件时报错，貌似7.1以上的php版本安装都会报这个错
系统版本：
Linux 78fab336ae08 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
php版本：
7.3
扩展安装情况：

RUN apt-get update
&& apt-get install -y
vim
git
zip
wget
libz-dev
libssl-dev
libpcre3-dev
&& apt-get clean
&& apt-get autoremove
&& docker-php-ext-install bcmath
&& docker-php-ext-install sockets
&& docker-php-ext-install pdo_mysql
&& pecl install -o -f redis
&& docker-php-ext-enable redis
&& rm -rf /tmp/*

Swoole extension
RUN wget https://github.com/swoole/swoole-src/archive/v4.3.3.tar.gz -O swoole.tar.gz
&& mkdir -p swoole
&& tar -xf swoole.tar.gz -C swoole --strip-components=1
&& rm swoole.tar.gz
&& (
cd swoole
&& phpize
&& ./configure --enable-async-redis --enable-mysqlnd --enable-openssl --enable-http2
&& make -j$(nproc)
&& make install
)
&& rm -r swoole
&& docker-php-ext-enable swoole
这是我遇到的报错信息：

creating libtool
appending configuration tag "CXX" to libtool
configure: creating ./config.status
config.status: creating config.h
running: make
/bin/bash /tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/libtool --mode=compile cc  -I. -I/tmp/pear/temp/hprose -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/include -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/main -I/tmp/pear/temp/hprose -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib  -DHAVE_CONFIG_H  -g -O2   -c /tmp/pear/temp/hprose/php_hprose.c -o php_hprose.lo
mkdir .libs
cc -I. -I/tmp/pear/temp/hprose -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/include -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/main -I/tmp/pear/temp/hprose -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /tmp/pear/temp/hprose/php_hprose.c  -fPIC -DPIC -o .libs/php_hprose.o
/bin/bash /tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/libtool --mode=compile cc  -I. -I/tmp/pear/temp/hprose -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/include -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/main -I/tmp/pear/temp/hprose -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib  -DHAVE_CONFIG_H  -g -O2   -c /tmp/pear/temp/hprose/hprose_common.c -o hprose_common.lo
cc -I. -I/tmp/pear/temp/hprose -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/include -I/tmp/pear/temp/pear-build-defaultuserTioZT3/hprose-1.6.6/main -I/tmp/pear/temp/hprose -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -DHAVE_CONFIG_H -g -O2 -c /tmp/pear/temp/hprose/hprose_common.c  -fPIC -DPIC -o .libs/hprose_common.o
/tmp/pear/temp/hprose/hprose_common.c: In function '__get_fcall_info_cache':
/tmp/pear/temp/hprose/hprose_common.c:202:8: error: 'zend_fcall_info_cache {aka struct _zend_fcall_info_cache}' has no member named 'initialized'
fcc.initialized = 1;
^
/tmp/pear/temp/hprose/hprose_common.c: In function '__create_php_object':
/tmp/pear/temp/hprose/hprose_common.c:764:12: error: 'zend_fcall_info_cache {aka struct _zend_fcall_info_cache}' has no member named 'initialized'
fcc.initialized = 1;
^
Makefile:196: recipe for target 'hprose_common.lo' failed
make: *** [hprose_common.lo] Error 1
ERROR: `make' failed

一样的问题

该问题已修复

authors: Soft-me akaQin andot

repo: hprose/hprose-php


text:
转COCO数据集格式请教

The nuclei dateset with annotation file can be found here: https://github.com/hrlblab/CircleNet/blob/master/docs/DATA.md

1  在COCO格式的注释里，annotations中的segmentation字段多出了如下图所示的内容，其中width和height在image字段中已经出现了，如果直接用circlenet直接训练的话，这个必须加吗？

2  extreme_points代表什么意思？
3  MoNuSeg_extreme_train2021.json和MoNuSeg_train2021.json有什么区别？

The nuclei dateset with annotation file can be found here: https://github.com/hrlblab/CircleNet/blob/master/docs/DATA.md

在COCO格式的注释里，annotations中的segmentation字段多出了如下图所示的内容，其中width和height在image字段中已经出现了，如果直接用circlenet直接训练的话，这个必须加吗？

MoNuSeg_extreme_train2021.json

No worries!
(1) This is indeed extra information. You should only need circle center and circle radius.
(2) The extreme points are for a baseline method (ExtremeNet: https://github.com/xingyizhou/ExtremeNet) if you would like to reproduce our results. You can read their paper to understand it, but it is not needed for CircleNet.
(3) MoNuSeg_extreme_train2021.json has the extreme points calculated. MoNuSeg_train2021.json does not have extreme points.

MoNuSeg_train2021.json

专家您好，谢谢您的解答，还有几个疑问：
1  在MoNuSeg_train2021.json中有extreme points字段，如下图所示

2  如果extreme points这个字段我不需要，在MoNuSeg_train2021.json中我就默认这个字段的值？还是删除该字段？

Dear Sir, please ask questions in English so that we and other users can understand. The first author of this work does not understand Chinese. Thanks

Thanks, please use English.
You should be able to delete the extreme points if only using CircleNet.

No worries!
(1) This is indeed extra information. You should only need circle center and circle radius.
(2) The extreme points are for a baseline method (ExtremeNet: https://github.com/xingyizhou/ExtremeNet) if you would like to reproduce our results. You can read their paper to understand it, but it is not needed for CircleNet.
(3) MoNuSeg_extreme_train2021.json has the extreme points calculated. MoNuSeg_train2021.json does not have extreme points.

You just said MoNuSeg_train2021.json does not have extreme points, however, I found extreme points in this MoNuSeg_train2021.json. What's wrong? Thank you so much!

My mistake. MoNuSeg_train2021.json does not require extreme points but is included for convenience.

On Feb 21, 2022, at 3:00 AM, lixiangMindSpore @.***> wrote:
No worries!
(1) This is indeed extra information. You should only need circle center and circle radius.
(2) The extreme points are for a baseline method (ExtremeNet: https://github.com/xingyizhou/ExtremeNet https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxingyizhou%2FExtremeNet&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=scyhEQMRTxIN62dWKrQ1JaH%2BD1bwFkGT7mfu%2BgBfG%2FI%3D&reserved=0) if you would like to reproduce our results. You can read their paper to understand it, but it is not needed for CircleNet.
(3) MoNuSeg_extreme_train2021.json has the extreme points calculated. MoNuSeg_train2021.json does not have extreme points.
You just said MoNuSeg_train2021.json does not have extreme points, however, I found extreme points in this MoNuSeg_train2021.json. What's wrong? Thank you so much!
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F78945582%2F154881223-fc8b6f9c-a53b-41a6-9704-f53a3e1b24e3.png&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=ob2IK5yzGzwfKfquiRODG911Lo5pKmHW8gQRRwX%2B%2FIM%3D&reserved=0
—
Reply to this email directly, view it on GitHub https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhrlblab%2FCircleNet%2Fissues%2F12%23issuecomment-1046423176&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3K6mEPEdSfJ%2BEL38m8z6i1nGYRoxx9CDnBZKb5RoG%2Fs%3D&reserved=0, or unsubscribe https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFQ7ZQY6FAXLM7AWSQYLXULU4GTDTANCNFSM5ON4EOSA&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=EQZji5C8k8cjEuQM56E4LJL5stR3wgVF53vldoc5Leo%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOS https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=V7oiKiXaVg2SBqM5hlY0mSnq5xiXNIh%2Biz34Y8ZrWuU%3D&reserved=0 or Android https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=67fX7CK7XlA1BVKfiox7oZsVeO7U4dR4%2BlVAMjcPUnU%3D&reserved=0.
You are receiving this because you commented.

My mistake. MoNuSeg_train2021.json does not require extreme points but is included for convenience.
…
On Feb 21, 2022, at 3:00 AM, lixiangMindSpore @.***> wrote: No worries! (1) This is indeed extra information. You should only need circle center and circle radius. (2) The extreme points are for a baseline method (ExtremeNet: https://github.com/xingyizhou/ExtremeNet https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxingyizhou%2FExtremeNet&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=scyhEQMRTxIN62dWKrQ1JaH%2BD1bwFkGT7mfu%2BgBfG%2FI%3D&reserved=0) if you would like to reproduce our results. You can read their paper to understand it, but it is not needed for CircleNet. (3) MoNuSeg_extreme_train2021.json has the extreme points calculated. MoNuSeg_train2021.json does not have extreme points. You just said MoNuSeg_train2021.json does not have extreme points, however, I found extreme points in this MoNuSeg_train2021.json. What's wrong? Thank you so much! https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F78945582%2F154881223-fc8b6f9c-a53b-41a6-9704-f53a3e1b24e3.png&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=ob2IK5yzGzwfKfquiRODG911Lo5pKmHW8gQRRwX%2B%2FIM%3D&reserved=0 — Reply to this email directly, view it on GitHub https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhrlblab%2FCircleNet%2Fissues%2F12%23issuecomment-1046423176&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=3K6mEPEdSfJ%2BEL38m8z6i1nGYRoxx9CDnBZKb5RoG%2Fs%3D&reserved=0, or unsubscribe https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFQ7ZQY6FAXLM7AWSQYLXULU4GTDTANCNFSM5ON4EOSA&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=EQZji5C8k8cjEuQM56E4LJL5stR3wgVF53vldoc5Leo%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOS https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=V7oiKiXaVg2SBqM5hlY0mSnq5xiXNIh%2Biz34Y8ZrWuU%3D&reserved=0 or Android https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|ethan.h.nguyen%40mail-service-3-mx.vanderbilt.edu|50eb0016ce3545b1482508d9f4e64629|ba5a7f39e3be4ab3b45067fa80faecad|0|0|637810092137641560|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=67fX7CK7XlA1BVKfiox7oZsVeO7U4dR4%2BlVAMjcPUnU%3D&reserved=0. You are receiving this because you commented.

Thank you so much!

authors: EthanHNguyen hrlblab lixiangMindSpore

repo: hrlblab/CircleNet


text:
DioError ║ Status: 404 Not Found

createChatCompletionStream() return 404 error.

up

HI @berkayhh
I found the issue.  For my Chat GPT account payment is not linked.

authors: AnandSaran berkayhh


text:
Recode.Task.TagTODO fails with a FunctionClauseError

On a file like:
defmodule MyApp.Error do
  @moduledoc """
  docs
  """
  defexception reason: "undefined error",
               code: nil

  @typedoc """
  type doc
  """
  @type t :: %__MODULE__{reason: any, code: integer() | nil}

  @doc nil
  def message(%{reason: reason}), do: inspect(reason)
end

Recode fails with a FunctionClauseError error:
> mix recode --dry
Read 5 files in 0.06s
....!...................................................!!..
 File: lib/error.ex
[Specs 14/3] Functions should have a @spec type specification.
Execution of the Recode.Task.TagTODO task failed with error:
** (FunctionClauseError) no function clause matching in String.split/3
    (elixir 1.15.7) lib/string.ex:478: String.split(nil, "\n", [])
    (recode 0.7.0) lib/recode/task/tags.ex:98: Recode.Task.Tags.find_tags/2
    (recode 0.7.0) lib/recode/task/tags.ex:54: Recode.Task.Tags.check_tags/3
    (sourceror 0.14.1) lib/sourceror/zipper.ex:380: Sourceror.Zipper.do_traverse/3
    (recode 0.7.0) lib/recode/task/tags.ex:17: Recode.Task.Tags.run/2
    (recode 0.7.0) lib/recode/runner/impl.ex:144: Recode.Runner.Impl.run_task/3
    (elixir 1.15.7) lib/enum.ex:2510: Enum."-reduce/3-lists^foldl/2-0-"/3
    (elixir 1.15.7) lib/task/supervised.ex:101: Task.Supervised.invoke_mfa/2

Execution of the Recode.Task.TagFIXME task failed with error:
** (FunctionClauseError) no function clause matching in String.split/3
    (elixir 1.15.7) lib/string.ex:478: String.split(nil, "\n", [])
    (recode 0.7.0) lib/recode/task/tags.ex:98: Recode.Task.Tags.find_tags/2
    (recode 0.7.0) lib/recode/task/tags.ex:54: Recode.Task.Tags.check_tags/3
    (sourceror 0.14.1) lib/sourceror/zipper.ex:380: Sourceror.Zipper.do_traverse/3
    (recode 0.7.0) lib/recode/task/tags.ex:17: Recode.Task.Tags.run/2
    (recode 0.7.0) lib/recode/runner/impl.ex:144: Recode.Runner.Impl.run_task/3
    (elixir 1.15.7) lib/enum.ex:2510: Enum."-reduce/3-lists^foldl/2-0-"/3
    (elixir 1.15.7) lib/task/supervised.ex:101: Task.Supervised.invoke_mfa/2

 File: lib/fmt.ex
[Specs 15/3] Functions should have a @spec type specification.
[Specs 19/3] Functions should have a @spec type specification.

 File: mix.exs
Updates: 1
Changed by: Format
     ...|
24 24   |      {:freedom_formatter, ">= 2.0.0", only: :dev},
25 25   |      {:recode, "~> 0.6", only: :dev},
   26 + |
26 27   |      # {:dep_from_hexpm, "~> 0.3.0"},
   28 + |
27 29   |      # {:dep_from_git, git: "https://github.com/elixir-lang/my_dep.git", tag: "0.1.0"}
28 30   |    ]
     ...|

Executed 60 tasks in 0.02s.
Files: 5 (.ex: 2, .exs: 3)
Updated 1 file
 Found 5 issues
Finished in 0.09s.

I've updated my https://github.com/axelson/recode_formatter_repro with this error case (in https://github.com/axelson/recode_formatter_repro/commit/7a3c5a683a03f188d513494015fefc13e4a29a69)

Thanks for reporting. The bug is fixed in 0.7.1.

authors: NickNeck axelson

repo: hrzndhrn/recode


text:
RFE: Instead of username/password using certificates - possible?

HI,
would it be possible to add certificates for opening a websocket connection?
Yours,
Jogi

Upvote from me. Need also possibility to connect to secure websocket servers using a client certificate.

Should already work. Did you try to set KeyStore and KeyStore Password within SoapUI Preferences.

Yes, it works by adding correct certificates in the JRE which SOAP UI using.

OK, this works of course. But my question was, does it also work when adding a Keyfile within the SoapUI Preferences, which is the standard approach for mutual authentication with SoapUI.

Suppose you want to open a websocket to wss://echo.websocket.org, which certificate should I install in the JRE which SoapUI is using into which keystore?
(maybe in jre\lib\security\cacerts ?)

Hi , I am trying to open a new Websocket Connection using wss, and i keep receiving the following:
Cancelling due to failed test step:java.util.concurrent.ExecutionException: javax.websocket.DeploymentException: Handshake error.], time taken = 302
I ve tried to export the certificate that I need and use it as a keystore in the SSL settings it did not work.
I added the certificate to the jre\lib\security\cacerts file and used that as a keystore, it recognizes it and the status is ok, but I keep getting the same handshake error when I try to open a new connection

Did you try the documented way?https://support.smartbear.com/readyapi/docs/projects/requests/ssl.html

authors: alcalda hschott oaxjogi rarsov sashat720

repo: hschott/ready-websocket-plugin


text:
[Fix] The language pt-br is invalid.

I imagine that because the name of the file is “pt-br.json” and not “pt_br.json” the translation doesn't work.

Fixed in v1.3.1, thanks for reporting @seriousfreezing

authors: KadTheHunter seriousfreezing

repo: hschwar/AccurateBlockPlacement-Reborn


text:
JDK 11

We would like to move on the JDK 11.
We're using your image so I've done a pull request with the necessary changes.

Thanks. PR merged.

Something went wrong and the image was not generated.
Is it just a matter of tagging the commit?
Can you have a look?

Ah, sorry, I forgot to push the tag. The release should be available within the next minutes.

authors: giorgiovinci hseeberger

repo: hseeberger/scala-sbt


text:
Can't call setState (or forceUpdate) on an unmounted component.

Full message:
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
in ParentSize (created by ItemList)
This seems to happen because of https://github.com/hshoff/vx/blob/master/packages/vx-responsive/src/components/ParentSize.js#L18 The component lives inside a transition that removes it conditionally, the raf probably comes a single frame too late.
I think the best way around it would be to track mounted state in componentDidMount/componentWillUnmount: https://reactjs.org/blog/2015/12/16/ismounted-antipattern.html , and then checking for it before doing setState.

so https://github.com/hshoff/vx/blob/master/packages/vx-responsive/src/components/ParentSize.js#L18 was just merged in yesterday but hasn't been published yet (https://github.com/hshoff/vx/pull/335).
Which version of @vx/responsive are you using? also which browser and version do you see this? and finally, do you have a repro of the bug so I can ensure that this gets fixed? (no worries if not)

Oops, i was just browsing the code looking for what could've caused it, but setState in a raf will definitively crash transitiongroup. My dependencies are quite outdated atm: "@vx/responsive": "0.0.158"

I'll add a is mounted guard around the setState call in the raf version and publish it in 0.0.172 and we can see if that fixes it for the transitiongroup case.

v0.0.172 is published: https://github.com/hshoff/vx/releases/tag/v0.0.172
@drcmda would you mind updating your @vx/responsive dep to this version and seeing if the warning is still present?

Upgrading @vx/responsive fixed the warning message for me.

@JacquiManzi thanks for following up @JacquiManzi!
Going to close this issue as it appears resolved. @drcmda happy to re-open if you find it did not fix for your use case.

@hshoff thanks! it looks like it's fixed!

authors: JacquiManzi drcmda hshoff

repo: hshoff/vx


text:
请问draw3D是怎么用的呢？

您好，根据您的代码我
import matplotlib.pyplot as plt from mpl_toolkits.mplot3d import Axes3D
带％的那句会提示格式错误，就没加，然后调用 draw3D  的时候却提示我没有这个函数，去 axes3d 的api里查了查夜没找到这个函数，请问您是怎么用的呢

%的那句是ipython notebook里面的宏指令，在那个里面会有用，在其他地方使用的话直接去掉就好，但可能需要补充其他的代码

repo: hsmyy/zhihuzhuanlan


text:
Body::set_mime should take Option<impl Into<Mime>>

It's currently impossible to unset the mime associated with the body. We should make it so we can unset the mime passed to the body.

I believe this doesn't work because the compiler can't infer the impl generic for None. We could have a Body::remove_mime, maybe?

@yoshuawuyts The code in the PR is finished (and correct), but I've shown in the doc comment of the function why it (as @jbr hints at) a somewhat ugly solution. As I write in the commit message, there are a couple of alternatives: Better documentation, or the introduction of a function.
There is also the possibility I've misunderstood you and you want Body::mime to be an Option, but I'm not familiar enough with the code base to know if that would make sense.

There is also the possibility I've misunderstood you and you want Body::mime to be an Option, but I'm not familiar enough with the code base to know if that would make sense.

Yeah, that's what I was thinking 😅 . I ran into this when trying to write a converter for vcr-cassette where we couldn't express a body without a mime type. Good defaults are important, but having a way to actually unset the mime type seems like something we should support.

@yoshuawuyts #387 should do this correctly now, and doesn't add any new warnings

@yoshuawuyts As #387 was merged, I think this should be closed

authors: halvko jbr yoshuawuyts

repo: http-rs/http-types