Not working.

Hello.
I installed your plugin with have successfully.
Configured it in full auto (only login and password) and nothing appears :

no sonoff.json
no cloud connection (ngrep show nothing)

2020-08-17 23:17:25 DEBUG (MainThread) [homeassistant.setup] Dependency sonoff will wait for ['zeroconf']
2020-08-17 23:17:27 INFO (MainThread) [homeassistant.setup] Setting up sonoff
2020-08-17 23:17:27 DEBUG (MainThread) [custom_components.sonoff] AUTO mode start
2020-0
2020-08-17 23:17:27 DEBUG (Thread-7) [zeroconf] Sending (37 bytes #1) <DNSOutgoing:{multicast=True, flags=0, questions=[question[ptr,in,_ewelink._tcp.local.]], answers=[], authorities=[], additionals=[]}> as b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x08_ewelink\x04_tcp\x05local\x00\x00\x0c\x00\x01'...
2020-08-17 23:17:27 DEBUG (zeroconf-Engine-139677554195232) [zeroconf] Received from '<IP_ADDRESS>':5353 (socket 9): <DNSIncoming:{id=0, flags=0, n_q=1, n_ans=0, n_auth=0, n_add=0, questions=[question[ptr,in,_ewelink._tcp.local.]], answers=[]}> (37 bytes) as [b'\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x08_ewelink\x04_tcp\x05local\x00\x00\x0c\x00\x01']
202

It seems trying local mode (that will not work because I use hass in a container without net-network)
Any idea ?
Thnaks

I don't know. It should show something about login and load devices list.

Same issue here.

Update:
Running HASS.IO on Virtualbox.
Added mode: cloud to config and devices now showing in entity list.
However,  SonoffLAN does not show in Configuration > Integrations.

SonoffLAN don't support GUI config yet.

SonoffLAN don't support GUI config yet.

Thanks for the info. Not an issue for me, actually.
And big thanks for your work.

Is the problem still relevant?

No longer for me.

@max5962 ?

Hello @AlexxIT ,
still not working for me but i'm still debugging my issue :)
I change my container network ( remove home assistant from a private network in order to understand mdns request )

@max5962 in auto mode component should use cloud+local connection. Do you have indents in the config?

AlexxIT, у меня схожая проблема. Я добавил новое физическое устройство, но добавить его в НА не могу, пробовал разные режимы, mode: cloud / local. Удалял файл .sonoff.json,  новый не появлялся, устройства стали недоступными.
Поставил так:
sonoff:   username<EMAIL_ADDRESS> password: hpc51833
Это тоже не помогло добавить новое устройство.
Есть идеи?

AlexxIT, у меня схожая проблема. Я добавил новое физическое устройство, но добавить его в НА не могу, пробовал разные режимы, mode: cloud / local. Удалял файл .sonoff.json,  новый не появлялся, устройства стали недоступными.
Поставил так:
sonoff:   username<EMAIL_ADDRESS> password: hpc51833
Это тоже не помогло добавить новое устройство.
Есть идеи?

@balbulator нужно смотреть логи. Файл должен появиться

@balbulator нужно смотреть логи. Файл должен появиться

@balbulator нужно смотреть логи. Файл должен появиться

Логи Home Assistant?
`2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for xiaomi_gateway3 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.components.http] The 'base_url' option is deprecated, please remove it from your configuration
2021-01-18 20:46:21 WARNING (MainThread) [homeassistant.components.lovelace] Resources need to be specified in your configuration.yaml. Please see the docs
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 ERROR (MainThread) [homeassistant.components.switch] The tuya platform for the switch integration does not support platform setup. Please remove it from your config.
2021-01-18 20:46:27 ERROR (MainThread) [homeassistant.components.switch] The tuya platform for the switch integration does not support platform setup. Please remove it from your config.
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for rpi_power which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for rhvoice which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:29 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.components.uptime.sensor] The 'unit_of_measurement' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for x720 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:31 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2021-01-18 20:46:31 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.components.broadlink.remote] The remote platform is deprecated, please remove it from your configuration
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.components.broadlink.remote] The remote platform is deprecated, please remove it from your configuration
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.setup] Setup of hacs is taking over 10 seconds.
2021-01-18 20:46:38 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform xiaomi_miio is taking over 10 seconds.
2021-01-18 20:46:38 WARNING (MainThread) [homeassistant.components.vacuum] Setup of vacuum platform xiaomi_miio is taking over 10 seconds.
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 10 seconds
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Huawei Home Gateway for upnp
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 236, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 116, in async_setup_entry
device = await async_discover_and_construct(hass, udn, st)
File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 81, in async_discover_and_construct
return await Device.async_create_device(hass, location)
File "/usr/src/homeassistant/homeassistant/components/upnp/device.py", line 74, in async_create_device
upnp_device = await factory.async_create_device(ssdp_location)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client_factory.py", line 52, in async_create_device
root = await self._async_get_url_xml(description_url)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client_factory.py", line 290, in _async_get_url_xml
await self.requester.async_http_request('GET', url)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client.py", line 66, in async_http_request
await self.async_do_http_request(method,
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/aiohttp.py", line 103, in async_do_http_request
async with self._session.request(method, url, headers=headers, data=body) as response:
File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 1117, in __aenter__
self._resp = await self._coro
File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 544, in _request
await resp.start(conn)
File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 890, in start
message, payload = await self._protocol.read() # type: ignore
File "/usr/local/lib/python3.8/site-packages/aiohttp/streams.py", line 604, in read
await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ (as_timestamp(states.sensor.snapshot_backup.attributes["last_snapshot"])) | timestamp_custom("%d.%m.%Y %H:%M") }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ (as_timestamp(states.sensor.snapshot_backup.attributes["last_snapshot"])) | timestamp_custom("%d.%m.%Y %H:%M") }}")' for attribute '_state' in entity 'sensor.last_google_backup_train'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_google_drive"] }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_google_drive"] }}")' for attribute '_state' in entity 'sensor.snapshots_in_google_drive_train'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_hassio"] }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_hassio"] }}")' for attribute '_state' in entity 'sensor.snapshots_in_hassio_train'
2021-01-18 20:46:46 WARNING (MainThread) [custom_components.hacs] You have custom-components/sensor.rpi_power installed with HACS this repository has been removed, please consider removing it. Removal reason (removal)
2021-01-18 20:46:47 WARNING (MainThread) [custom_components.hacs] custom-components/sensor.rpi_power - Repository is archived.
2021-01-18 20:46:53 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 20 seconds
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 10 seconds
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 10 seconds
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 20 seconds
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 20 seconds
2021-01-18 20:47:16 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 40 seconds`

@balbulator нужно смотреть логи. Файл должен появиться

Логи Home Assistant?
`2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for xiaomi_gateway3 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:18 WARNING (MainThread) [homeassistant.components.http] The 'base_url' option is deprecated, please remove it from your configuration
2021-01-18 20:46:21 WARNING (MainThread) [homeassistant.components.lovelace] Resources need to be specified in your configuration.yaml. Please see the docs
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:26 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:27 ERROR (MainThread) [homeassistant.components.switch] The tuya platform for the switch integration does not support platform setup. Please remove it from your config.
2021-01-18 20:46:27 ERROR (MainThread) [homeassistant.components.switch] The tuya platform for the switch integration does not support platform setup. Please remove it from your config.
2021-01-18 20:46:27 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for rpi_power which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for rhvoice which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:29 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.components.uptime.sensor] The 'unit_of_measurement' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.components.template.sensor] The 'entity_id' option is deprecated, please remove it from your configuration
2021-01-18 20:46:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for x720 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-01-18 20:46:31 ERROR (MainThread) [homeassistant.components.ipp] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
2021-01-18 20:46:31 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.components.broadlink.remote] The remote platform is deprecated, please remove it from your configuration
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.components.broadlink.remote] The remote platform is deprecated, please remove it from your configuration
2021-01-18 20:46:33 WARNING (MainThread) [homeassistant.setup] Setup of hacs is taking over 10 seconds.
2021-01-18 20:46:38 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform xiaomi_miio is taking over 10 seconds.
2021-01-18 20:46:38 WARNING (MainThread) [homeassistant.components.vacuum] Setup of vacuum platform xiaomi_miio is taking over 10 seconds.
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 10 seconds
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:40 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 5 seconds
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Huawei Home Gateway for upnp
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 236, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 116, in async_setup_entry
device = await async_discover_and_construct(hass, udn, st)
File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 81, in async_discover_and_construct
return await Device.async_create_device(hass, location)
File "/usr/src/homeassistant/homeassistant/components/upnp/device.py", line 74, in async_create_device
upnp_device = await factory.async_create_device(ssdp_location)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client_factory.py", line 52, in async_create_device
root = await self._async_get_url_xml(description_url)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client_factory.py", line 290, in _async_get_url_xml
await self.requester.async_http_request('GET', url)
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/client.py", line 66, in async_http_request
await self.async_do_http_request(method,
File "/usr/local/lib/python3.8/site-packages/async_upnp_client/aiohttp.py", line 103, in async_do_http_request
async with self._session.request(method, url, headers=headers, data=body) as response:
File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 1117, in __aenter__
self._resp = await self._coro
File "/usr/local/lib/python3.8/site-packages/aiohttp/client.py", line 544, in _request
await resp.start(conn)
File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 890, in start
message, payload = await self._protocol.read() # type: ignore
File "/usr/local/lib/python3.8/site-packages/aiohttp/streams.py", line 604, in read
await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ (as_timestamp(states.sensor.snapshot_backup.attributes["last_snapshot"])) | timestamp_custom("%d.%m.%Y %H:%M") }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ (as_timestamp(states.sensor.snapshot_backup.attributes["last_snapshot"])) | timestamp_custom("%d.%m.%Y %H:%M") }}")' for attribute '_state' in entity 'sensor.last_google_backup_train'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_google_drive"] }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_google_drive"] }}")' for attribute '_state' in entity 'sensor.snapshots_in_google_drive_train'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_hassio"] }}")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 353, in async_render
render_result = compiled.render(kwargs)
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/local/lib/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 1, in top-level template code
File "/usr/local/lib/python3.8/site-packages/jinja2/sandbox.py", line 384, in getitem
return obj[argument]
jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 462, in async_render_to_info
render_info._result = self.async_render(variables, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 355, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
2021-01-18 20:46:41 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'attributes'') while processing template 'Template("{{ states.sensor.snapshot_backup.attributes["snapshots_in_hassio"] }}")' for attribute '_state' in entity 'sensor.snapshots_in_hassio_train'
2021-01-18 20:46:46 WARNING (MainThread) [custom_components.hacs] You have custom-components/sensor.rpi_power installed with HACS this repository has been removed, please consider removing it. Removal reason (removal)
2021-01-18 20:46:47 WARNING (MainThread) [custom_components.hacs] custom-components/sensor.rpi_power - Repository is archived.
2021-01-18 20:46:53 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 20 seconds
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 10 seconds
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:46:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 10 seconds
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:167f3dc0-1dd2-11b2-ada8-c0a0bb8c4a93"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 20 seconds
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.components.upnp] Wanted UPnP/IGD device with UDN/ST "uuid:3F815285-AB5A-88E0-AA44-1CBDB9A81D68"/"urn:schemas-upnp-org:device:InternetGatewayDevice:1" not found, aborting
2021-01-18 20:47:15 WARNING (MainThread) [homeassistant.config_entries] Config entry for upnp not ready yet. Retrying in 20 seconds
2021-01-18 20:47:16 WARNING (MainThread) [homeassistant.config_entries] Config entry for ipp not ready yet. Retrying in 40 seconds`

Может быть проблема, что НА работает через duckdns?

Может быть проблема, что НА работает через duckdns?

Вопрос снимается, разобрался. Проблема в том, что я прописал в конфиге ссылку на файл, а в файле еще раз указал "sonoff:"
Убрал из файла первую строчку "sonoff:" и все заработало
Благодарю за попытку помочь

Вопрос снимается, разобрался. Проблема в том, что я прописал в конфиге ссылку на файл, а в файле еще раз указал "sonoff:"
Убрал из файла первую строчку "sonoff:" и все заработало
Благодарю за попытку помочь


TILA-2384: Allow rejecting unhandled reservations

can_create_reservations >> can_create_staff_reservations (had been implemented in core with that name; updated ticket)
button conditions (omit for draft/payment pending, cancelled reservations):

deny: if (state == Confirmed || state == RequiresHandling)
returnToHandling: if (state == Confirmed || state == Denied))


Add support for integration into cloud services

AWS
Azure
GCp
PGvector database

The PGVector DB request is clear enough and may be something we look at as we do plan to expand our list of supported vector databases.
However what specific integrations / gaps with llmware workflows are you referring to when mentioning the big 3 Cloud providers (AWS, Azure, GCP)?

yes

Offering an integration with AWS Kendra would enable comparison use cases. I can see llmware being useful for quick proof-of-concept services. Being able to then compare that output to what a GenAI "service" like AWS Bedrock delivers would be helpful.  This could be a bit tricky as Kendra has vector db qualities but can also run in memory over documents in a way that is similar to FAISS. It doesn't seem to fit neatly into the same call currently being made to Milvus in the example docs.

Closing issue as stale.  We have added ~6 different vector DBs since the original issue was opened, along with a variety of integrations.  If specific request around AWS still pending, then please raise again as a specific isue.


Add verbose option to ChatVectorDBQAChain and question answering chains

This change makes it easier to investigate what is going on inside ChatVectorDBQAChain.

Thanks for adding this in @yuku! Great idea. Do you mind making the changes to ConversationalRetrievalQAChain as well? We're in the process of deprecating ChatVectorDBQAChain in favor of that one. Sorry that this wasn't more clear.

@agola11 Thanks for the feedback. I pushed two commits:

Add @deprecated comment to ChatVectorDBQAChain
Add verbose option to ConversationalRetrievalQAChain.fromLLM

I have marked the my last three comments as off-topic as they are outside the scope of this PR. Please forget them.

Rebased.

Thanks!


Request for User DIY Model Support in GitHub Copilot

I am writing to inquire about the possibility of introducing a feature that allows users to utilize their own custom models(through API token like that offered by OPENAI) in the GitHub Copilot extension.
As a frequent user of GitHub Copilot, I have found the tool to be incredibly useful in assisting with code generation. However, I believe that the ability to use custom models could greatly enhance the flexibility and effectiveness of the tool. I know there are some alternative models provided within Copilot currently, but the LLM community over the world is becoming more and more diversified. Different users may have different needs and preferences(like customized code style) when it comes to code generation, and a one-size-fits-all model may not always be the best solution.
Moreover, from the perspective of the extension, allowing users to use their own models through a customized API token could potentially reduce the load on your official servers. This could lead to cost savings and improved performance for all users. Additionally, it could provide an opportunity for a more flexible pricing for this extension.

Well, the Chat Participant API (https://github.com/microsoft/vscode/issues/199908) will enable people to write extensions that provide chat @ participants, and they can use whatever model they want.
But if you're asking for the ability to use all the same current functionality with a different model plugged in, I think that's very unlikely to happen in the near future. We've found that we can't just send the same prompts to a different model and get good results. Switching models usually requires more rounds of prompt crafting and tweaks.

Well, the Chat Participant API (microsoft/vscode#199908) will enable people to write extensions that provide chat @ participants, and they can use whatever model they want.
But if you're asking for the ability to use all the same current functionality with a different model plugged in, I think that's very unlikely to happen in the near future. We've found that we can't just send the same prompts to a different model and get good results. Switching models usually requires more rounds of prompt crafting and tweaks.

What a pity. Frankly, this would discourage me to subscribe Copilot again.


[WIP] Modifying Korean translations

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

제가 오픈소스 가이드를 읽으면서 번역이 매끄럽지 않다고 느끼는 부분을 수정하고 있습니다.
I am correcting the translation that is not smooth while reading the open source guide.
혹시 의견이 있으신 분은 댓글 달아주시면 감사하겠습니다.
If you have any suggestions, please leave a comment.

LGTM !

@JoonhunLee thanks for your contribution. I'll merge the PR once the test builds are green.

@JoonhunLee It looks like there are some test failures. If you could fix those, that will be great! We'll review the PR after.

👍

@JoonhunLee CI is still failing, sorry: https://github.com/github/opensource.guide/pull/2517/checks?check_run_id=3774401273#step:7:120
Do you need help understanding what needs to be done to fix this?

@MikeMcQuaid
Oh I didn't have time for check this pr.. sorry
May I ask for help on this failure??


docs(sdk): fix a typo in an error message

Description
Insignificant typo fix in error message.  I apologise if this is too minor, but it kept staring at me until I was forced to take action.  No need to list me as contributor
Did not update CHANGELOG.md
Testing
Didn't test

@tsahota we appreciate all contributions big or small. Glad that you are using wandb and hopefully enjoying your experience!


Multiview Images on Waymo

Thanks for this excellent codebase. I find for Waymo Open Dataset mmdet3d currently only processes the first image during data preprocessing and there is no multi-modality method implemented on Waymo. Any plan to support all five images and multi-modality detection pipeline on Waymo?

Yes, that's in our plan. But maybe recently we do not have enough resources to support it very soon. PRs are welcome.


Also create s3 bucket when a logging ALB is created

This gives the user the ability to import or have this bucket created on their behalf rather than leaving that up to manual work.

Resolved: https://github.com/terraform-community-modules/tf_aws_alb/commit/7842de9a740c2ae85ccd6355ba5ff92eedd84e12


Adds optional active class to target element

This adds rudimentary support for adding and removing an active class on the target element. My goal was to make it possible to use ember-pop-over for general purpose buttons and nav dropdowns where it's necessary to have an 'active' or 'pushed' state on the button itself.
If this was already possible and I missed it, or this code isn't up to snuff I'm all ears.
Thank you for all your work on this addon!
Example:
<button id='my-button'>
{{#my-popover for='my-button' activeClassName='active'}}

Item 1

Item 2

{{/my-popover}}

When you click on the button it should transform to <button id='my-button' class='active'> and 'active' will be removed when the popover hides.

This would be very good to have and useful!

Ooh! You can implement this using onshow and onhide. :)

This is supported using onhide and onshow as actions.
<button id='my-button' class="{{if active 'active'}}>
{{#my-popover for='my-button' onshow=(action (mut active) true) onhide=(action (mut active) false)}}

Item 1

Item 2

{{/my-popover}}

I'm don't want to support this; I'd prefer this to be done using the hooks I provided above. I can add documentation and a recipe for this pattern in the README.

Thanks Tim!


Put reset button instead of editable field on "Failed Login Count" profile page

Hi guys,
Wouldn't be better to show the "Failed Login Account" number as read only and a reset button somewhere instead of leaving it as an editable number ? I also think that not many people knows for what that field is (reset).
Regards,
Filis.

What if an admin wants to reset it for a user?

What if an admin wants to reset it for a user?

I spoke briefly to @filisko about this on IRC last week, and I think that’s the idea behind having a button - that it’d be used by admins. It doesn’t really make sense to have it for yourself, as the failed login count is reset to 0 when you log in successfully anyway.

What if an admin wants to set it to an arbitrary value so they can lock a user out? or will it not work like that?
Basically, is changing the value a non-existent usecase?

Basically, is changing the value a non-existent usecase?

I think so, yeah. It’s an automatically scaffolded field that used to be hidden (back when “lock out after x incorrect logins” was disabled by default), and the number you’d need to set in order to lock someone out isn’t necessarily known to CMS users. I’d be surprised if people are relying on that to disable user accounts, given that you can use the “reset password” functionality to bypass it.

ok - this makes sense, then - readonly with reset button. Who's going to do it? 👼


[Identity] Browser tests

Currently, the identity package doesn't have run the browser tests (echo skipped).
However, individual SDKs use ClientSecretCredential with disabled security in the browser through karma conf.

We should find a way to test with the InteractiveBrowserCredential in the CI,  and get rid of the ClientSecretCredential in our browser tests. (Also consider how the recorder would play in this scenario.)
If we are relying on ClientSecretCredential for a longer period for testing in the browsers, we should add browser tests in the identity package similar to what we have in the individual SDKs to figure out the things that might break the browsers so that it would help find the regressions sooner than when we import the identity library in our SDKs. Reference - https://github.com/Azure/azure-sdk-for-js/pull/14910

Refer this - https://github.com/sadasant/identity-browser-tests/blob/dev/AuthorizationCodeCredential/ideal.ts

For context:

Testing InteractiveBrowserCredential isn’t trivial with our current setup because the page that has Karma loaded needs to redirect to Azure, then come back, losing Karma’s state and potentially encountering other errors.
In the link that Karishma shared above, I’m starting to test how to use “puppeteer” to test these interactive credentials.

Puppeteer (or other libraries, like Casper.js) allow Node.js to manage browser tabs. They follow through redirections.
Even if testing is viable with Puppeteer, we still need to figure out how to make it work nicely with our current testing infrastructure.

My current thoughts are that I could start playing with Puppeteer while I work on the new features for the browser experience for JS, and once we have a reliable experience there (separate from our SDK repo), we could present it to the team.


Cannot try due large forces

According to the description, SPICE.hdf5 is downloaded from https://github.com/openmm/spice-dataset/releases:
https://github.com/openmm/spice-models/blob/b9023c7955c6e8f3f3fa9b73f6a4d5e9b3280990/five-et/README.md?plain=1#L3-L4
The file contains samples with large force (https://github.com/openmm/spice-dataset/issues/32) and createSpiceDataset.py doesn't filter them.
When I try to train the loss just fluctuates ~1e7 without any improvement.

@peastman could you clarify the force cutoff? And how did you apply it?

The filtering was implemented in https://github.com/openmm/spice-dataset/pull/41, which was merged after that release was created.  Once we're agreed on all remaining changes (especially anything for https://github.com/openmm/spice-dataset/issues/42), I'll create a 1.1 release.

@peastman the cutoff in https://github.com/openmm/spice-dataset/pull/41 is 1 Hartree/Bohr (≈ 49132 kJ/mol/nm), while in the email you mentioned 20000 kJ/mol/nm. Which ones was used?

My original model described in the first draft of the paper used 20,000 kJ/mol/nm.  The five newer models described in the current draft used 1 hartree/bohr.


Compile error when add link library by flags attribute

I has problems when working with ceedling like below.
For example I has test case call : test_screen . The implementation dependence X11 library. I takes a look and configures the flags attribute like bellow.
For example
:flags:
  :test:
    :compile:
      :test_screen:
        - -Wall
    :link:
      :test_screen:
        - -lX11

but the GCC return some kinds of linking error like could not found reference of some functions which I am using in my implementation.
The error build command
'gcc -lX11 "build/test/out/test_screen_runner.o" "build/test/out/test_screen.o" "build/test/out/unity.o" "build/test/out/Screen_Unix.o" "build/test/out/cmock.o" -o "build/test/out/test_screen.out"'
Trying to fix it. Then I found out the issue because of the incorrect order of linking.
the correct order must be
"gcc  "build/test/out/test_screen_runner.o" "build/test/out/test_screen.o" "build/test/out/unity.o" "build/test/out/Screen_Unix.o" "build/test/out/cmock.o" -o "build/test/out/test_screen.out -lX11"
But the command was generated by Ceendling. And then I stuck on there.
Really appreciate any suggestions or helps.
Thanks and best regards,

Sorry, but I would to know that the project still in maintain and some one will look at the issue. It's really a critical issue as my view.
Any suggestion to work around it ?
thanks

Work around is in referenced issue - update GCC. Otherwise someone will need to dive in and implement suffix (which is going to be useless once people will be using newer GCCs)

There is a patch for this in the works, but it's not quite ready yet. Sorry about the delay.

@mvandervoord
really thank you for your quick respond.
Can't wait to try the path. I also done by update GCC. But still really want to find another ways like your path

Fixed by adding support for a :libraries: section where you can specify :libraries:system: and then include the system libraries you want to include. This is injected into the end by default (though it can be set to any location by using option ${4}. See the manual for details). commit 336be34


Add topology visualization

Server and frontend implementation for topology visualization.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@35a099f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   71.32%
=========================================
  Files             ?       56
  Lines             ?     3672
  Branches          ?        0
=========================================
  Hits              ?     2619
  Misses            ?     1053
  Partials          ?        0

Continue to review full report at Codecov.

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


bug: the s390x arch is missed at quay.io/confidential-containers/cloud-api-adaptor:latest

Yesterday, when I try to run the e2e-test on one ibmcloud s390x cluster, I meet follow error:
...
time="2023-04-02T09:11:38-07:00" level=info msg="Install CoCo and cloud-api-adaptor"
Wait for the cc-operator-daemon-install DaemonSet be available
Wait for the pod cc-operator-daemon-install-pqqqf be ready
Wait for the cloud-api-adaptor-daemonset DaemonSet be available
Wait for the pod cloud-api-adaptor-daemonset-6p2cm be ready
Wait for the kata runtimeclass be created
=== RUN   TestCreateSimplePod
=== RUN   TestCreateSimplePod/Simple_Peer_Pod
    common_suite_test.go:35: timed out waiting for the condition
--- FAIL: TestCreateSimplePod (180.67s)
    --- FAIL: TestCreateSimplePod/Simple_Peer_Pod (180.67s)
FAIL
...

Try to find the root cause:
root@peer-pod1:~# kubectl get po -A
NAMESPACE                        NAME                                             READY   STATUS              RESTARTS       AGE
confidential-containers-system   cc-operator-controller-manager-fbb5dcf9d-nssxq   2/2     Running             0              4m6s
confidential-containers-system   cc-operator-daemon-install-xcfnl                 0/1     ContainerCreating   0              33s
confidential-containers-system   cloud-api-adaptor-daemonset-wzcrd                0/1     ErrImagePull        0              33s
...
root@peer-pod1:~# kubectl -n confidential-containers-system describe po cloud-api-adaptor-daemonset-wzcrd
Name:         cloud-api-adaptor-daemonset-wzcrd
Namespace:    confidential-containers-system
Priority:     0
Node:         <IP_ADDRESS>/<IP_ADDRESS>
Start Time:   Sun, 02 Apr 2023 09:22:31 -0700
Labels:       app=cloud-api-adaptor
              controller-revision-hash=57d57cb579
              pod-template-generation=1
Annotations:  <none>
Status:       Pending
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/cloud-api-adaptor-daemonset
Containers:
  cloud-api-adaptor-con:
    Container ID:
    Image:         quay.io/confidential-containers/cloud-api-adaptor:latest
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/local/bin/entrypoint.sh
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment Variables from:
      peer-pods-secret  Secret     Optional: false
      peer-pods-cm      ConfigMap  Optional: false
    Environment:        <none>
    Mounts:
      /root/.ssh/ from ssh (ro)
      /root/containers/ from auth-json (ro)
      /run/cri-runtime from cri-runtime-endpoint (rw)
      /run/netns from netns (rw)
      /run/peerpod from pods-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-fnsj8 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  cri-runtime-endpoint:
    Type:          HostPath (bare host directory volume)
    Path:          /run/containerd
    HostPathType:  Directory
  auth-json:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  auth-json-secret
    Optional:    true
  ssh:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  ssh-key-secret
    Optional:    true
  pods-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /run/peerpod
    HostPathType:
  netns:
    Type:          HostPath (bare host directory volume)
    Path:          /run/netns
    HostPathType:
  kube-api-access-fnsj8:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              node-role.kubernetes.io/worker=
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  47s                default-scheduler  Successfully assigned confidential-containers-system/cloud-api-adaptor-daemonset-wzcrd to <IP_ADDRESS>
  Normal   BackOff    20s (x2 over 45s)  kubelet            Back-off pulling image "quay.io/confidential-containers/cloud-api-adaptor:latest"
  Warning  Failed     20s (x2 over 45s)  kubelet            Error: ImagePullBackOff
  Normal   Pulling    8s (x3 over 47s)   kubelet            Pulling image "quay.io/confidential-containers/cloud-api-adaptor:latest"
  Warning  Failed     7s (x3 over 46s)   kubelet            Failed to pull image "quay.io/confidential-containers/cloud-api-adaptor:latest": rpc error: code = NotFound desc = failed to pull and unpack image "quay.io/confidential-containers/cloud-api-adaptor:latest": no match for platform in manifest: not found
  Warning  Failed     7s (x3 over 46s)   kubelet            Error: ErrImagePull

docker manifest inspect quay.io/confidential-containers/cloud-api-adaptor:latest
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 1057,
         "digest": "sha256:e33e859f5d0ddfea258c7bb0a72fcd448460f1328e4ca540e4e97e8dadbdf7cf",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 566,
         "digest": "sha256:a0992080e06ff3fb23f6c9041066abcb0d81b0e49b57fb404ab72ae284f0f571",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         }
      }
   ]
}

The s390x arch is missed at quay.io/confidential-containers/cloud-api-adaptor:latest

@liudalibj the latest is only built for amd64 (dev-[commitid]) as it includes libvirt support which requires cgo support.
The multi-arch builds are tagged with [commitid] and not with latest tag.
https://quay.io/repository/confidential-containers/cloud-api-adaptor?tab=tags&tag=latest

@liudalibj https://github.com/confidential-containers/cloud-api-adaptor/commit/aa3f4c6a7339b68f6bf231997f5702437f7f63bf

Sounds like we need customize the tag field in overlays file like https://github.com/confidential-containers/cloud-api-adaptor/blob/staging/install/overlays/ibmcloud/kustomization.yaml#L10 for e2e test. e.g. Retrieve and latest commit and reset it via https://github.com/confidential-containers/cloud-api-adaptor/blob/staging/test/provisioner/provision.go#L185

@wainersm @bpradipt do you think we need change the tag quay.io/confidential-containers/cloud-api-adaptor:latest to something like quay.io/confidential-containers/cloud-api-adaptor:$COMMIT in all providers like quay.io/confidential-containers/cloud-api-adaptor:latest so that e2e test is running against the right caa image?

@huoqifeng I don't think there is any change required for e2e test.
The e2e tests will be using the devel releases which includes all providers and the builds are tagged with latest tag.
However if we start running e2e for non-x86_64 architecture, then we need to think about few changes. Most importantly, building multi-arch devel releases using CGO since libvirt provider cannot be statically compiled. This will require s390x build runners imho or some mechanism to use qemu to natively build s390x binaries without cross-compilation.

Well, thanks @bpradipt I think we need figure out a solution because we'll need make sure the latest code work well on all arch. @liudalibj @stevenhorsman

@huoqifeng - I see you've started working on this. One thing that I've just had a play with is seeing how easy it would be to get the latest tag from the quay registry, so we could automatically (by default at least) use that if we are running s390x. It seems to be pretty straight forward:
package main

import (
    "encoding/json"
    "fmt"
    "io/ioutil"
    "log"
    "net/http"
)

func get_latest_caa_tag() string {
  resp, err := http.Get("https://quay.io/api/v1/repository/confidential-containers/cloud-api-adaptor/tag/")
  if err != nil {
      log.Fatal(err)
  }

  defer resp.Body.Close()

  body, err := ioutil.ReadAll(resp.Body)
  if err != nil {
      log.Fatal(err)
  }

  type QuayTagsResponse struct {
        Tags []struct {
                Name           string `json:"name"`
                Others         map[string]interface{} `json:"-"`
        } `json:"tags"`
        Others         map[string]interface{} `json:"-"`
  }

  var result QuayTagsResponse
  if err := json.Unmarshal(body, &result); err != nil {
    fmt.Println("Can not unmarshal JSON")
  }
  return result.Tags[0].Name
}

func main() {
	fmt.Printf("Latest tag: %+v",get_latest_caa_tag())
}

Which produces:
# go run http.go
Latest tag: 1764961c2ae1e59704832bc148094df9f248a61e

It's definitely not the greatest code, but I thought I'd share it, in case it is any help?

@stevenhorsman thanks for the hints, I'm using gopkg.in/src-d/go-git.v4 in the PR: https://github.com/confidential-containers/cloud-api-adaptor/pull/868, thanks in advance for your review for the PR :-)

@stevenhorsman thanks for the hints, I'm using gopkg.in/src-d/go-git.v4 in the PR: #868, thanks in advance for your review for the PR :-)

So I don't want to block the PR, but the advantage of getting the tag from quay is that I think it avoids issues where people are developing against a branch and the timing issue where a commit has been made, but the build hasn't completed yet, so I think there is extra value in this approach? That said I think your PR is better than what we currently have, so I'm happy to review it and then think about the quay registry enhancement later?

@stevenhorsman right, get tag from quay is good approach, question is can we take the last or [0] item form the tags items which does not have name "name": "latest" as the manifest generated from last commit? For example:
{
    "tags": [
        {
            "name": "1764961c2ae1e59704832bc148094df9f248a61e",
            "reversion": false,
            "start_ts":<PHONE_NUMBER>,
            "manifest_digest": "sha256:db34c1e6986746301f98f3b11ca3747f390dcf96a33c12335899e1173a999a67",
            "is_manifest_list": true,
            "size": null,
            "last_modified": "Mon, 24 Apr 2023 14:36:59 -0000"
        },
        {
            "name": "dev-1764961c2ae1e59704832bc148094df9f248a61e",
            "reversion": false,
            "start_ts":<PHONE_NUMBER>,
            "manifest_digest": "sha256:a8eb3fe0efa501132601eee174cc482fe3c20f842dbcd2a3ea4ec5e59dc3b78e",
            "is_manifest_list": true,
            "size": null,
            "last_modified": "Mon, 24 Apr 2023 14:33:01 -0000"
        },
        {
            "name": "latest",
            "reversion": false,
            "start_ts":<PHONE_NUMBER>,
            "manifest_digest": "sha256:a8eb3fe0efa501132601eee174cc482fe3c20f842dbcd2a3ea4ec5e59dc3b78e",
            "is_manifest_list": true,
            "size": null,
            "last_modified": "Mon, 24 Apr 2023 14:33:00 -0000"
        },


Shadow PC cloud streaming always crashes within 5-10min

Hi, this time it is on nixos but I have seen the exact same behavior on arch in the past. Now that I am trying out nixos I tought about giving hyprland another try but the same crash is happening again.
When I start the cloud stream up and do nothing then there is no crashes while on the windows desktop but the moment I start for instance streaming diablo 4 within a couple of min hyprland will crash back to gdm.
Hyprland Crash Report

Calm down, it was a misinput! MISINPUT!

Hyprland received signal 11 (Segmentation fault)

Version: v0.25.0

System info:
System name: Linux
Node name: nixos
Release: 6.1.34
Version: #1-NixOS SMP PREEMPT_DYNAMIC Wed Jun 14 09:15:34 UTC 2023

GPU:

os-release:
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="23.05.1123.aaef163eac7"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 23.05 (Stoat)"
SUPPORT_END="2023-12-31"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="23.05 (Stoat)"
VERSION_CODENAME=stoat
VERSION_ID="23.05"

Backtrace:
#0 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x824) [0x5562b4]
#1 | Hyprland(_Z25handleUnrecoverableSignali+0x3f) [0x5901ef]
#2 | /nix/store/dg8mpqqykmw9c7l0bgzzb5znkymlbfjw-glibc-2.37-8/lib/libc.so.6(+0x38d60) [0x7f9bb3172d60]
#3 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(wlr_addon_find+0) [0x7f9bb3d118a0]
#4 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(+0x8a6aa) [0x7f9bb3cfd6aa]
#5 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(wlr_linux_dmabuf_v1_set_surface_feedback+0x10) [0x7f9bb3cff0f0]
#6 | Hyprland(_ZN13CHyprRenderer20setWindowScanoutModeEP7CWindow+0x131) [0x494f71]
#7 | Hyprland(_ZN11CCompositor19setWindowFullscreenEP7CWindowb15eFullscreenMode+0x1b0) [0x596810]
#8 | Hyprland(_ZN11IHyprLayout15onWindowRemovedEP7CWindow+0x103) [0x4fa9e3]
#9 | Hyprland(ZN6Events22listener_destroyWindowEPvS0+0xda) [0x519fda]
#10 | Hyprland(_ZN15CHyprWLListener4emitEPv+0x3b) [0x508ecb]
#11 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7c) [0x7f9bb3d91a0c]
#12 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(+0xa7336) [0x7f9bb3d1a336]
#13 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(wlr_addon_set_finish+0x2e) [0x7f9bb3d1174e]
#14 | /nix/store/pg8if159dsvagrjqnd9j8qxgm04klm2k-wlroots-hyprland-0.17.0-dev/lib/libwlroots.so.12(+0x7f16e) [0x7f9bb3cf216e]
#15 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(+0x7ed7) [0x7f9bb3d8fed7]
#16 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(+0xe4f0) [0x7f9bb3d964f0]
#17 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(+0xea6f) [0x7f9bb3d96a6f]
#18 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(wl_client_destroy+0x80) [0x7f9bb3d90960]
#19 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(+0x8a95) [0x7f9bb3d90a95]
#20 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xa2) [0x7f9bb3d938e2]
#21 | /nix/store/pp7zlpdxb14w08ayv15zafi063zxm7jn-wayland-1.22.0/lib/libwayland-server.so.0(wl_display_run+0x25) [0x7f9bb3d91445]
#22 | Hyprland(main+0x488) [0x46d328]
#23 | /nix/store/dg8mpqqykmw9c7l0bgzzb5znkymlbfjw-glibc-2.37-8/lib/libc.so.6(+0x23ace) [0x7f9bb315dace]
#24 | /nix/store/dg8mpqqykmw9c7l0bgzzb5znkymlbfjw-glibc-2.37-8/lib/libc.so.6(__libc_start_main+0x89) [0x7f9bb315db89]
#25 | Hyprland(_start+0x25) [0x47b095]

Log tail:
[LOG] Registered signal for owner 1c11c18: 2172688 -> 1c11d78 (owner: DragIcon)
[LOG] Registered signal for owner 1c11c18: 2172698 -> 1c11ca8 (owner: DragIcon)
[LOG] Registered signal for owner 1c11c18: 2137908 -> 1c11de0 (owner: DragIcon)
[LOG] Drag icon mapped.
[LOG] Drag icon committed.
[LOG] Drag icon committed.
[LOG] Drag destroyed.
[LOG] Callback 1c11c48 -> 1c11c40, Drag removed.
[LOG] Drag icon unmapped.
[LOG] Drag icon destroyed.
[LOG] Callback 1c11e08 -> 1c11e00, DragIcon removed.
[LOG] Callback 1c11cd0 -> 1c11cc8, DragIcon removed.
[LOG] Callback 1c11d38 -> 1c11d30, DragIcon removed.
[LOG] Callback 1c11da0 -> 1c11d98, DragIcon removed.
[LOG] Started drag 2121bf0
[LOG] Registered signal for owner 1c11c18: 2121cb0 -> 1c11c20 (owner: Drag)
[LOG] Drag started with an icon 2141fa0
[LOG] Registered signal for owner 1c11c18: 2141fb8 -> 1c11d10 (owner: DragIcon)
[LOG] Registered signal for owner 1c11c18: 2141fc8 -> 1c11d78 (owner: DragIcon)
[LOG] Registered signal for owner 1c11c18: 2141fd8 -> 1c11ca8 (owner: DragIcon)
[LOG] Registered signal for owner 1c11c18: 2137908 -> 1c11de0 (owner: DragIcon)
[LOG] Drag icon mapped.
[LOG] Drag icon committed.
[LOG] Drag icon committed.
[LOG] Drag destroyed.
[LOG] Callback 1c11c48 -> 1c11c40, Drag removed.
[LOG] Drag icon unmapped.
[LOG] Drag icon destroyed.
[LOG] Callback 1c11e08 -> 1c11e00, DragIcon removed.
[LOG] Callback 1c11cd0 -> 1c11cc8, DragIcon removed.
[LOG] Callback 1c11d38 -> 1c11d30, DragIcon removed.
[LOG] Callback 1c11da0 -> 1c11d98, DragIcon removed.
[LOG] Keybind triggered, calling dispatcher (64, , 50)
[LOG] Set keyboard focus to surface 219b860, with window name: Shadow PC - Display
[LOG] Callback 219c350 -> 219c348, CWLSurface removed.
[LOG] CWLSurface 219c320 called destroy()
[LOG] Subsurface Node 1f83b30 destroyed
[LOG] Callback 1f83c38 -> 1f83c30, SurfaceTreeNode removed.
[LOG] Callback 1f83bd0 -> 1f83bc8, SurfaceTreeNode removed.
[LOG] Callback 1f83ca0 -> 1f83c98, SurfaceTreeNode removed.
[LOG] Window 219bbd0 unmapped (class Shadow PC - Display)
[WARN] Window 219bbd0 unmapped without being mapped??
[LOG] Window 219bbd0 destroyed, queueing. (class Shadow PC - Display)
[LOG] XWayland class raw: Shadow PC - Display
[LOG] Callback 219bc60 -> 219bc58, XWayland Window removed.
[LOG] Callback 219bcc8 -> 219bcc0, CWindow removed.
[LOG] Callback 219bd30 -> 219bd28, XWayland Window removed.
[LOG] Callback 219c140 -> 219c138, XWayland Window removed.
[LOG] Callback 219c2e0 -> 219c2d8, XWayland Window removed.
[LOG] Searching for matching rules for Shadow PC - Display (title: Shadow PC - Display)

tried it this morning with true and false and both times 3-5min ingame and I was back at GDM login.

On my Arch Linux hyprland, Shadow is crashing whole Xwayland proccess So I'm also forced to restart my session.

Still having this issue.I'm on Arch Linux with Hyprland. It happens when playing Dota and Shadow makes Hyprland crash which forces me to reboot my pc or restart a session. The shadow client is still running in the background though, because I still hear the sounds. Any fixes yet?

Still a thing?


[ALLUXIO-2311]Improve javadoc for LeaderSelectorClient (setCurrentMasterThread)

https://alluxio.atlassian.net/browse/ALLUXIO-2311

Can one of the admins verify this patch?

ok to test

Jenkins, add to whitelist

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11862/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11848/
Test PASSed.


Parameters lost

I used the 2.+ for the two request who needs keep sessions,and it worked.But when I changed it to 3.1.0,the first request is allright,the second failed,and I saw the request on the server had no parameters,all the parameters became null,what happened? Help!Help!Help!

For general help, please ask on StackOverflow.


Attaching files ?

Is it possible to attach files ?

Is it possible to attach files ?

@AdityaSher Your question is probably too broad to answer specifically without guessing what you mean. Attach files (FROM WHERE) & (TO WHAT)? Can one upload a file to a web server with a web form? Yes. That’s been possible since last century...If you know what you’re doing. Can one upload a file to your web server and then have a google apps script move, process, and store that into say Google Drive or Google Cloud Storage? Yes. That’s also possible. Here’s an article that discusses one way to do that (which you can adapt for your needs probably:
https://www.labnol.org/code/19747-google-forms-upload-files/
And some documentation to get you started:
https://developers.google.com/apps-script/advanced/drive
And StackDriver has a few answers: https://stackoverflow.com/questions/15670392/uploading-file-using-google-apps-script-using-htmlservice
Sent with GitHawk

Is it possible to attach files ?
I am sorry for being unclear.

here is my problem
Is is possile to attach a file on a static webpage hosted on gtihub pages ? (files directly get uploaded to a google form ? ) is that possible?


ALS speed layer could apply its own updates in real-time

Right now, models do not generally update themselves in real-time in the speed layer. In most cases it's because it's not that essential, and because it's difficult or impossible to coordinate updates consistently across a distributed process to compute updates.
However this happens to be untrue for ALS, where only one copy of the model is updated on the driver. It could also apply updates in near-real-time.

Actually, on further review, it does. Will add a note in the source code to resolve this issue, for (my) future reference.


Allow for room joins without first providing microphone permission

Describe the bug
I was curious enough to log in, but when it asks for microphone permission, i'm too scared to proceed.
To Reproduce
Steps to reproduce the behavior:

Go to https://thirdroom.io/world/#thirdroom-public:matrix.org
Click on 'Enter World'
Site asks for permission to use microphone
Being scared

Expected behavior
To be an inclusive and accessible social space, the software should empower users to participate in a safe and non-overwhelming way, even when they have social anxiety or other social problems.
An option to join muted, like voice chats such as Jitsi Meet have, would help me in this situations, so i can first check out the world without being forced to speak directly.
Joining a personal space first (like some "Home") would also help to get comfortable with the software without having to interact with other people. You could invite people later to hang out there.
There might be other resources and best practices to create a safe and welcoming onboarding for such social tools. You should coordinate with other efforts like Matrix, the VRChat Community and maybe mental health groups.
Check out these videos about your potential audience:

https://www.youtube.com/watch?v=4PHT-zBxKQQ
https://www.youtube.com/watch?v=5v_Dl7i4Bcw

Screenshots
A scary situation

Desktop:

OS: NixOS 22.05.2397.5c211b47aea
Browser: Chrome 104.0.5112.79

Thanks for the request @davidak it's definitely something that's on our radar 👍


wrong reference in local-cli/util/Config.js

local-cli/util/Config.js:36 should be referencing "${cwd}" instead of "${__dirname}" for the failure, since this object is attempting to walk a directory structure provided by cwd and not __dirname.

Look like you solved this - thanks!


Triage banner

Adds a banner for the triage page explaining why triage is needed. This does not show up on the vaccination page (not in the prototype), but can be added if it turns out it's needed.
Banner for "Triage needed"

Banner for "Triage follow-up needed"

This does not show up on the vaccination page (not in the prototype), but can be added if it turns out it's needed.
I checked with the designers, let's make the banners consistent between the triage and record sections.

These banners have been merged in with the vaccinations ones and now show up on the vaccinations page.


Ranges?

So what is this new Option "Ranges" and what's the meaning of the different colors for the range circles and spawn points?

Ranges show how far away the pokemon, gym or pokestop can be accessed from.
Thank you! And what is the meaning of the colors?

I just downloaded the 0.3.3 for OS X and I don't have the ranges option or the colored spawn points with timers =[

Don't quote me on this, but from my observations the different colors represent how soon the spot will spawn. Green means the spot currently has a spawn, blue means it will spawn soon and purple means it won't spawn for awhile. I don't have exact times when they change colors. This is all from my observation. Also, the spawns will change colors when, for instance, a spot that currently has a spawned a pokemon will gradually turn yellow then orange the closer it is to the end of the spawn time.  Also, if you hover your mouse over a spawn spot it will tell you when that spawn will occur.

Sounds like a valid answer but I would love a confirmation from admins :)


ci: unpin specific buildkit version and fix deployment subnets

Motivation
We previously had an issue with the following error: cannot reuse body, request must be retried and it's happening once again, but it might be for a different reason.
This commonly was a wrong error, caused by a containerd issue which has being tracked and solved here: https://github.com/docker/build-push-action/issues/761#issuecomment-1406261692
We had this previously reported in: https://github.com/ZcashFoundation/zebra/issues/3665
This PR also fixes the following error:
Invalid value for field 'resource.networkInterfaces[0].network': 'https://compute.googleapis.com/compute/v1/projects/zfnd-dev-zebra/global/networks/default'. The referenced network resource cannot be found.

Specifications
We're having errors when building, and this might be caused by an underlying error which containerd is not showing us correctly.
Solution

Unpin our old buildkit version and use the latest with included fixes
GCP VMs not only need a specific region set, but also a subnetwork, as we don't have default subnetworks available (those have to be explicitly created)

Review
Anyone from DevOps team
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

@teor2345 I had to fix another issue which was not ultimately solved by https://github.com/ZcashFoundation/zebra/commit/b3691c514a7a7ef8d13928436029f4b62d70facd
The VMs which did not start by the error, are already running.


DrawHole custom geometry function not working

DrawHole has an undocumented option to use a custom geometry function which is not working :
var geomFn = options.geometryFunction
if (geomFn) {
options.geometryFunction = function (c, g) {
g = _geometryFn(c, g)
return geomFn(c, g)
}
} else {
...
}
If it is changed to the code below it works :
var geomFn = options.geometryFunction
if (geomFn) {
options.geometryFunction = function (c, g) {
g = _geometryFn.bind(this)(c, g)
return geomFn.bind(this)(c, g)
}
} else {
...
}

It has been fixed and merged in the ol-ext library


Meltano discover all not working

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/416
Originally created by @jschatz1 on 2019-02-25 14:12:53

What is the current bug behavior?
(What is happening now)

[ ] meltano discover all has an error : Cannot list available plugins. Error: 'models'

What is the expected correct behavior?
(What should be happening)

[ ] meltano discover all should work.

Steps to reproduce
(How one can reproduce the issue)

[ ] meltano discover all

Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output)

[ ] See error above.

Possible fixes
(If you can, link to the line of code that might be responsible for the problem or suggest a fix)

[ ]

View 8 previous comments from the original issue on GitLab


IPv4 parsing for v2.0.0

I'm still a lowly purescript v0.10.7 user, so the v2.0.0 tag is the latest applicable for me. However, the fixes made to IPv4 octet parsing recently made were only applied to >= v3.0.0. I've made changes to the v2.0.0 commit, but I can't file a pull request without a backport branch in this repository. Would you be willing to pull my changes into a new version?
https://github.com/athanclark/purescript-uri/tree/v2.0.1

I've just created a v2-backport branch, if you'd like to submit a PR to that?

Yes please! Just filed in #21


What templates do you need ?

Please use this issue to list the use cases for which you would like to have templates. Provide as many details as possible to help author these templates to meet your requirements.
Thanks,
Logic Apps Templates working group.

test


upgrade to grails 3

Hello.
Please help me take a look at this upgrade. It will be good to do it on a separate branch (grails 3).
I have not upgraded the scripts yet and there may be some work to be done ( it still makes use of hibernate-hijacker and friends )

I noticed you did not convert over to use Spring Events but kept the HawkEventing.   Did you have a look at Spring Events and decide it was not worth the effort?  It would be nice to be able to drop Hawk Eventing in favor of Spring Eventing to reduce the conversion effort in the future.
Once this code has been merged I can test it on one of our 3.0 projects.   Great work and thanks for taking this up.

Hello Scott,
I did not try to drop hawk eventing because I think I don't have the deep understanding(yet) of the plugin required to make that change.
I also thought someone more knowledgeable about the plugin was already working on it.
It will be good to make the switch a move on to hibernate4
Please let mw know how we can move forward.....
-----Original Message-----
From: Scott Ryan
Sent: 5/13/2015 4:14 PM
To: multi-tenant/grails-multi-tenant-single-db
Cc: Omasiri
Subject: Re: [grails-multi-tenant-single-db] upgrade to grails 3 (#45)
I noticed you did not convert over to use Spring Events but kept the HawkEventing. Did you have a look at Spring Events and decide it was not worth the effort? It would be nice to be able to drop Hawk Eventing in favor of Spring Eventing to reduce the conversion effort in the future.
Once this code has been merged I can test it on one of our 3.0 projects. Great work and thanks for taking this up.
—
Reply to this email directly or view it on GitHub.


visual-directed fuzzing

To improve the ability for fuzzing translators there's one precondition:

Reconnect/remap overlays/translators that have crashed
Simple wrapper/launcher script for a translator that stores crashdumps and runs 1.

and one new step, the ability to define a range (similar to the zoom- feature) and then a fuzzing function that tells sensors to repeat the latest transfer (this can be done entirely in rwstat.c) but with a temporary fault injection with the specified fuzzing function. This closes the loop with the overlay feature helping us to find interesting fields and then the UI to specify where to place the corruption.

fixed in  da1c0662b02acfa1c23ffdbcae9de1ca2741dc6e


neovim's checkhealth returns an error for perl

Describe the bug
When you run checkhealth inside neovim it returns an error, "Neovim::Ext" cpan module is not installed, for the perl provider. While that particular perl module is not packaged given there is no previously reported issue I would assume this is a regression, many packaged vim extensions applications rely on perl support.
Steps To Reproduce
Steps to reproduce the behavior:

Install neovim (I am using home-manager but it seems to be reproducible no matter the method of install.)
run :checkhealth

Expected behavior
Test passes
Screenshots
If applicable, add screenshots to help explain your problem.
Notify maintainers
@manveru
@rvolosatovs
@ma27
Metadata

system: "x86_64-linux"
host os: Linux 5.10.52, NixOS, 21.11.20210727.8ecc61c (Porcupine)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre20210707_02dd6bb
channels(wyatt): "nixos-21.05pre281538.9e377a6ce42"
channels(root): "nixos-21.05pre290427.673aea9f84c"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

For context, this is the exact error, which I can reproduce locally with :checkhealth
## Perl provider (optional)
  - ERROR: perl provider error:
    - ADVICE:
      - "Neovim::Ext" cpan module is not installed

I don't think it was ever there, but I may be wrong.
It seems that to make this work we'd need to make a perl environment with Neovim::Ext package available to the executable at runtime.
I believe that would mean we should package https://github.com/jacquesg/p5-Neovim-Ext, which has not been updated in almost a year (last commit in master is dated Sep 6, 2020 https://github.com/jacquesg/p5-Neovim-Ext/commit/44e0b15b65a32397d2e77cbd59f2591935787f0f), which may or may not mean it is abandoned.
There are also quite a few issues upstream about this particular warning https://github.com/neovim/neovim/issues/15130 https://github.com/neovim/neovim/issues/15006 (more in history)
Given the above and the fact that there indeed were no complains about this I lean towards saying that the this is not worth doing at this point of time, especially given that modern neovim plugins are encouraged to use lua or other scripting languages, which are already there.
If you insist that we indeed need it, probably we should implement it in the same way as python or node is handled already in the derivation, so this would be an opt-in withPerl with a possible perlPackages.
@teto you probably have the most context here, maybe you could give some insights here?

You are on point :) I will try to change the Error to a warning upstream so that it's less stressful. As for nixpkgs, if no one is using a perl plugin, there is no reason ti implement this. I dont know of any perl plugin but if there is a provider there must be one ?! maybe check the other repos of the provider author. But right now the lua plugins are the hot stuff indeed.

looks good now, feel free to reopen


Enh/accelerated asset refactor

minor simplification of the code without changing the logic
docstring
naming convention

I see why you replaced sse by synchronous_events and not by sequence_of_synchronous_events. However, I think this might lead to confusion in the future, so this convention should be introduced and highlighted in the beginning of the documentation.
Or does anybody have a better idea on how to extend sse to make it more readable, but not too long?

I see why you replaced sse by synchronous_events and not by sequence_of_synchronous_events. However, I think this might lead to confusion in the future, so this convention should be introduced and highlighted in the beginning of the documentation.
Or does anybody have a better idea on how to extend sse to make it more readable, but not too long?

I agree, this could lead to problems. Also, if we do stick with this new name we should rename all of the synchronous_events_is_* functions to be at least a bit closer to grammatical correctness.

I see why you replaced sse by synchronous_events and not by sequence_of_synchronous_events. However, I think this might lead to confusion in the future, so this convention should be introduced and highlighted in the beginning of the documentation.
Or does anybody have a better idea on how to extend sse to make it more readable, but not too long?

I agree, this could lead to problems. Also, if we do stick with this new name we should rename all of the synchronous_events_is_* functions to be at least a bit closer to grammatical correctness.

Do you mean renaming is -> all and contains -> contain?
I looked into this issue of is/are in programming languages quite some time ago. There is no convention, and developers still use is instead of grammatically correct are.
Anyway, I don't have any preference here except that we should not call these functions as sse_xxx.
@Kleinjohann will you rename them as you wish and update the docs accordingly? Because I don't understand what problems could arise and how exactly we should highlight this at the beginning of asset docs.

ASSET in OOP
Fixed bugs

previously, intersection_matrix norm parameter is always None by default (there were no ways to change it since probability_matrix_xxx didn't have norm param)
previously, extract_synchronous_events ignored t_start and t_stop, that were passed in the intermediate steps of asset analysis, and always computed them from the input spike trains.

Changed behavior

verbose is True by default

Not sure

Does extract_sychronous_events work with any spiketrains or only those that has been used in the very input?
There are 2 functions - mask_matrices and cluster_matrix_entries - that can operate without a notion of a spiketrain. In tests, now I force creating an ASSET object with spiketrains to call these function. If you do call these functions without doing and presaving the intermediate steps (although for me it's hard to image, but let's suppose), we can easily move the logic of these functions outside of the ASSET class and still do the following in the class:

if mask_matrix is None
	mask_matrix = self.mask_matrices()
return cluster_matrix_entries(mask_matrix, ...)  # cluster_matrix_entries is defined outside

and the same for mask_matrices() function.
3. joint_probability_matrix requires filter_shape. I made it (5,1) by default. We could of course make it positional (no default value) and force users to think what the valid range of filter_shape is. Making it positional will also break the nice structure that I provided and the minimal knowledge of asset. We can highlight this caveat in the doc and show in the tutorial.
Simple API
Check out the example https://github.com/INM-6/elephant/blob/enh/accelerated_asset_refactor/elephant/asset_example.py
I'll remove it before merging and put in the Example docstring alongside with the long way (old style).

Not sure
1. Does extract_sychronous_events work with any `spiketrains` or only those that has been used in the very input?

2. There are 2 functions - `mask_matrices` and `cluster_matrix_entries` - that can operate without a notion of a spiketrain. In tests, now I force creating an ASSET object with spiketrains to call these function. If you do call these functions without doing and presaving the intermediate steps (although for me it's hard to image, but let's suppose), we can easily move the logic of these functions outside of the ASSET class and still do the following in the class:

it should only ever be used with those in the input, nothing else really makes any sense
Being able to call these separately might make a workflow more understandable since it can then mirror the execution order of ASSET functions. However, it might be worth it to sacrifice that to be able to put all of the code together for better maintainability.

Fixed bugs
1. previously, intersection_matrix `norm` parameter is always None by default (there were no ways to change it since probability_matrix_xxx didn't have `norm` param)

This was not a bug, intersection_matrix is only supposed to be called with norm=None from the probability_matrix_* functions. In the Monte-Carlo case this might work, but only if you always use the same normalisation, also for the surrogates. In the analytical version the Poisson estimation uses a normalisation that only matches norm=None in intersection_matrix.

Not sure
[...]

joint_probability_matrix requires filter_shape. I made it (5,1) by default. We could of course make it positional (no default value) and force users to think what the valid range of filter_shape is. Making it positional will also break the nice structure that I provided and the minimal knowledge of asset. We can highlight this caveat in the doc and show in the tutorial.

Sounds good to me, as long as all defaults make some sort of sense together, e.g. work in the simple test (which they seemed to do in the file you now removed again, right?)

Not sure
[...]

joint_probability_matrix requires filter_shape. I made it (5,1) by default. We could of course make it positional (no default value) and force users to think what the valid range of filter_shape is. Making it positional will also break the nice structure that I provided and the minimal knowledge of asset. We can highlight this caveat in the doc and show in the tutorial.

Sounds good to me, as long as all defaults make some sort of sense together, e.g. work in the simple test (which they seemed to do in the file you now removed again, right?)

filter_shape=(5,1) is taken from the tutorial (asset_showcase). It works for my test (even smaller shape might work as well) - I moved the test in the Examples section of the module docstring.

Being able to call these separately might make a workflow more understandable since it can then mirror the execution order of ASSET functions. However, it might be worth it to sacrifice that to be able to put all of the code together for better maintainability.

I leave it as it is now then. After you use it for a while, you get the final impression and can change the behavior as you wish.


Spelling correction

Change to correct the spelling error from "thr" to "the"

@oumageorge : Thanks for your contribution! The author, @douglaslMS, has been notified to review your proposed change.

#sign-off


NOTICE: Multiple packages are unavailable

The following packages are temporarily unavailable:

cpggen
cpggen-bin
cpggen-windows-bin

These would be republished without any binary plugins later this week.

They are back without the binaries.


[Bug] Migo and Serpent Person Issues

A review left on my scenario, Search for a Friend, mentioned that the Migo monster had no Evade or Horror effects.  I did a quick run through and found that this was actually the case.
I also noticed that the Serpent Person monster won't allow me to attack with a Spell when I run through a scenario that I'm working on.
Valkyrie Version 2.4.09

Windows 10

Feathered Person works for me:

this ticket has overlap with #1157

This is actually interesting. As it is now we only support a few attacks against the snake person. What the FFG app does is it treats the snake person as a humanoid, except for the attacks that mention legs in the description, which are obviously replaced by a snake tail in the descriptions.
I think the easiest fix for now is to add the attack mappings to the .ini file. That's because it's the only case that modify another "trait" attacks. I'll have a fix today.
The migo is a bit different case I think, but I'll check that as well.

So for the migo it seems there's a very simple string casing issue in horrors.ini and evade.ini ("Migo" instead of "MiGo").


Add support for calendar periods

This PR adds a new schedule, EveryCalendarDtSchedule that is aware of Dates.Period objects, allowing for true monthly diagnostics.
Closes #66

Passing atmos build:
https://buildkite.com/clima/climaatmos-ci/builds/20080


Automated cherry pick of #9543

Cherry pick of #9543 on release-5.37.
/cc  @hmhealey
NONE

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

/update-branch

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers

@marianunez @metanerd Would either of you be able to help merge this PR? (I don't have access and automerge won't work with failures)


The link for "simple-knn @ 44f7642" is not accessible and returns an error 404.

Just go to original gaussian_splatting and clone it!~


release 0.17

I propose to release 0.17 as at this point the master branch is quite stable

@niamster I am good with that. I'd like to do a bit of testing, in particular try it with celluloid-0.17.0 prerelease and push a pre1 of this release until the release of celluloid also lands, then we bump both over to 0.17.0 - what do you think?

If nothing else it would be good to update the gemspec and version on master to reflect that the current codebase is 0.17.0.pre... and after you do that, probably just cut a pre.

We need to update the tests to a higher version of rspec.

Running transpec on it and looking at the failing tests.

@niamster the tests are outdated. Just running transpec didn't fix them. I feel like we should have the mandatory cases green at least before cutting even a prerelease gem. I'd do this right now myself, but I am working on 0.17.0 of celluloid -- but I can come back to this if no one else is able to get on this.

@digitalextremist let me help you with that. I'll update the tests

Sweet. Thanks @niamster

@digitalextremist PR #43 is ready

Right on! Heading back to my desk in 60-90 minutes and I'll go through that. Thanks again @niamster

@digitalextremist I think #45 can be "safely" merged now.

@niamster even without 0.17.0 of celluloid itself?

@niamster I found a few things and noted those on the individual lines. The question is: should master of celluloid-io depend on 0.17.0-prerelease of celluloid right away? I still need at least two more days before I'd say that's wise. Even then, I'd like to push a 0.17.0.pre1 of celluloid-zmq with these sorts of changes... how about that?

ah, you are right. I thought that we have 0.17.0-prerelease here. I agree that celluloid-xxx master branches should be synchronous.

@niamster agreed, let's synchronize the versions. Feel free to bring #45 back in against a 0.17.0-prerelease branch of celluloid-zmq instead of master

I will update #48 to be 0.17.0 instead of 0.16.5 in light of this.

Especially to resolve the issues coming up in DCell, I am going to cut this in the next day or so, but as 0.17.0 to begin synchronizing versions across the suite.