Define a decent HAL for flash that will allow the use of filesystems

For the moment the embryo of a flash HAL is only dedicated to tests.
For it to be more useful it has to be able to communicate with potential file systems & offer better interfaces.
The HAL should be able to communicate to the upper layers:

Its total size (in bytes ?)
Its erase size depending on the address/sector ? (erasable sectors might vary in size)
Its various or minimum available write size (page, qword, word, etc)
ECC, OOB ?

This has to be very practical and eliminate as much guess work as possible for the upper layers, so accessors might be a solution, like:

int flash_get_size(struct flash *ctx);
int flash_get_erase_size(struct flash *ctx, size_t addr);
int flash_get_write_size(struct flash *ctx, size_t addr);
int flash_get_block(struct flash *ctx, size_t addr) ?
...

Otherwise, a flash_probe(ctx, &probe_info)  can be a solution that offers the option to be easy to extend in the future, but will probably require to output a complete flash mapping, which might prove to be difficult with no dynamic memory allocation.
We still have the option to put this mapping statically in picoRTOS_device.h, though, but what about hypothetical external flashes ?

There will be an attempt in v1.8.x, but i'm not convinced


Various Nest sensors not being discovered

Home Assistant release (hass --version):
0.29.5
Python release (python3 --version):
3.4.2
Component/platform:
sensor.nest
Description of problem:
I have three Nest thermostats and I'm getting different degrees of functionality.  The three thermostats are showing up and functionality seems to be working.  It looks like the "binary_sensors" for all three are discovering.  The "sensors" though are not.
My three thermostats are: basement, main_floor, and upstairs.
I see all three for thermostat_name.binary_sensor.BLANK
I see all three climate.thermostat_name
I only see sensor.basement_humidity though.. Not sensor.main_floor_humidity nor sensor.upstairs_humidity.  I would also expect to see all of the sensors defined below in my configuration.yaml for all three thermostats.
I'm also no longer seeing my Nest Protects...
All three thermostats:

Only 1 sensor showing up for "basement"

Expected:
Nest Protects to be discovered.  All three thermostats to be discovered with all sensors defined in configuration.yaml
Problem-relevant configuration.yaml entries and steps to reproduce:
sensor:
  - platform: nest
    monitored_conditions:
      - 'temperature'
      - 'target'
      - 'humidity'
      - 'operation_mode'
      - 'last_ip'
      - 'local_ip'
      - 'last_connection'
      - 'battery_level'
      - 'weather_condition'
      - 'weather_temperature'
      - 'weather_humidity'
      - 'wind_speed'
      - 'wind_direction'
      - 'co_status'
      - 'smoke_status'

Traceback (if applicable):
Sep 30 14:56:26 automation hass[9828]: ERROR:homeassistant.components.sensor:Error while setting up platform nest
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 107, in _setup_platform
Sep 30 14:56:26 automation hass[9828]: discovery_info)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 68, in setup_platform
Sep 30 14:56:26 automation hass[9828]: add_devices(sensors)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 198, in add_entities
Sep 30 14:56:26 automation hass[9828]: if self.component.add_entity(entity, self):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 134, in add_entity
Sep 30 14:56:26 automation hass[9828]: entity.update_ha_state()
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 156, in update_ha_state
Sep 30 14:56:26 automation hass[9828]: state = STATE_UNKNOWN if self.state is None else str(self.state)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 112, in state
Sep 30 14:56:26 automation hass[9828]: return getattr(self.device, self.variable)
Sep 30 14:56:26 automation hass[9828]: AttributeError: 'Device' object has no attribute 'operation_mode'

Additional info:
After that Traceback I'm also seeing these that I think are related to me using templates that are looking for the sensors that aren't showing up...
Sep 30 14:56:26 automation hass[9828]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Sep 30 14:56:26 automation hass[9828]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Sep 30 14:56:26 automation hass[9828]: return self._compiled.render(kwargs).strip()
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Sep 30 14:56:26 automation hass[9828]: return self.environment.handle_exception(exc_info, True)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Sep 30 14:56:26 automation hass[9828]: reraise(exc_type, exc_value, tb)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Sep 30 14:56:26 automation hass[9828]: raise value.with_traceback(tb)
Sep 30 14:56:26 automation hass[9828]: File "<template>", line 1, in top-level template code
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/sandbox.py", line 355, in call
Sep 30 14:56:26 automation hass[9828]: return __context.call(__obj, *args, **kwargs)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 387, in forgiving_float
Sep 30 14:56:26 automation hass[9828]: return float(value)
Sep 30 14:56:26 automation hass[9828]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: During handling of the above exception, another exception occurred:
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Sep 30 14:56:26 automation hass[9828]: self._callback(*self._args)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Sep 30 14:56:26 automation hass[9828]: future.set_result(callback(*args))
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Sep 30 14:56:26 automation hass[9828]: raise TemplateError(err)
Sep 30 14:56:26 automation hass[9828]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Sep 30 14:56:26 automation hass[9828]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Sep 30 14:56:26 automation hass[9828]: return self._compiled.render(kwargs).strip()
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Sep 30 14:56:26 automation hass[9828]: return self.environment.handle_exception(exc_info, True)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Sep 30 14:56:26 automation hass[9828]: reraise(exc_type, exc_value, tb)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Sep 30 14:56:26 automation hass[9828]: raise value.with_traceback(tb)
Sep 30 14:56:26 automation hass[9828]: File "<template>", line 1, in top-level template code
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 335, in forgiving_round
Sep 30 14:56:26 automation hass[9828]: value = round(float(value), precision)
Sep 30 14:56:26 automation hass[9828]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: During handling of the above exception, another exception occurred:
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Sep 30 14:56:26 automation hass[9828]: self._callback(*self._args)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Sep 30 14:56:26 automation hass[9828]: future.set_result(callback(*args))
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Sep 30 14:56:26 automation hass[9828]: raise TemplateError(err)
Sep 30 14:56:26 automation hass[9828]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Sep 30 14:56:26 automation hass[9828]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Sep 30 14:56:26 automation hass[9828]: return self._compiled.render(kwargs).strip()
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Sep 30 14:56:26 automation hass[9828]: return self.environment.handle_exception(exc_info, True)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Sep 30 14:56:26 automation hass[9828]: reraise(exc_type, exc_value, tb)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Sep 30 14:56:26 automation hass[9828]: raise value.with_traceback(tb)
Sep 30 14:56:26 automation hass[9828]: File "<template>", line 1, in top-level template code
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 335, in forgiving_round
Sep 30 14:56:26 automation hass[9828]: value = round(float(value), precision)
Sep 30 14:56:26 automation hass[9828]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: During handling of the above exception, another exception occurred:
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Sep 30 14:56:26 automation hass[9828]: self._callback(*self._args)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Sep 30 14:56:26 automation hass[9828]: future.set_result(callback(*args))
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Sep 30 14:56:26 automation hass[9828]: raise TemplateError(err)
Sep 30 14:56:26 automation hass[9828]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Sep 30 14:56:26 automation hass[9828]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Sep 30 14:56:26 automation hass[9828]: return self._compiled.render(kwargs).strip()
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Sep 30 14:56:26 automation hass[9828]: return self.environment.handle_exception(exc_info, True)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Sep 30 14:56:26 automation hass[9828]: reraise(exc_type, exc_value, tb)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Sep 30 14:56:26 automation hass[9828]: raise value.with_traceback(tb)
Sep 30 14:56:26 automation hass[9828]: File "<template>", line 1, in top-level template code
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 335, in forgiving_round
Sep 30 14:56:26 automation hass[9828]: value = round(float(value), precision)
Sep 30 14:56:26 automation hass[9828]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'state'
Sep 30 14:56:26 automation hass[9828]: During handling of the above exception, another exception occurred:
Sep 30 14:56:26 automation hass[9828]: Traceback (most recent call last):
Sep 30 14:56:26 automation hass[9828]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Sep 30 14:56:26 automation hass[9828]: self._callback(*self._args)
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Sep 30 14:56:26 automation hass[9828]: future.set_result(callback(*args))
Sep 30 14:56:26 automation hass[9828]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Sep 30 14:56:26 automation hass[9828]: raise TemplateError(err)
Sep 30 14:56:26 automation hass[9828]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'state'

I've commented out my templates that refer to the missing sensors and all of the Traceback's in the "Additional Info" section weren't there as I figured.

I started commenting out items and have made some progress.  Commenting out "operation_mode" gets me past my first post.  Using this configuration.yaml:
  - platform: nest
    monitored_conditions:
      - 'temperature'
      - 'target'
      - 'humidity'
#      - 'operation_mode'
      - 'last_ip'
      - 'local_ip'
      - 'last_connection'
      - 'battery_level'
      - 'weather_condition'
      - 'weather_temperature'
      - 'weather_humidity'
      - 'wind_speed'
      - 'wind_direction'
      - 'co_status'
      - 'smoke_status'

I got all of the sensors down until it hit "weather_condition".  Then I got this Traceback:
Oct 01 00:19:53 automation hass[16726]: ERROR:homeassistant.components.sensor:Error while setting up platform nest
Oct 01 00:19:53 automation hass[16726]: Traceback (most recent call last):
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 107, in _setup_platform
Oct 01 00:19:53 automation hass[16726]: discovery_info)
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 68, in setup_platform
Oct 01 00:19:53 automation hass[16726]: add_devices(sensors)
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 198, in add_entities
Oct 01 00:19:53 automation hass[16726]: if self.component.add_entity(entity, self):
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 134, in add_entity
Oct 01 00:19:53 automation hass[16726]: entity.update_ha_state()
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 155, in update_ha_state
Oct 01 00:19:53 automation hass[16726]: ).result()
Oct 01 00:19:53 automation hass[16726]: File "/usr/lib/python3.4/concurrent/futures/_base.py", line 402, in result
Oct 01 00:19:53 automation hass[16726]: return self.__get_result()
Oct 01 00:19:53 automation hass[16726]: File "/usr/lib/python3.4/concurrent/futures/_base.py", line 354, in __get_result
Oct 01 00:19:53 automation hass[16726]: raise self._exception
Oct 01 00:19:53 automation hass[16726]: File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
Oct 01 00:19:53 automation hass[16726]: result = next(coro)
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 181, in async_update_ha_state
Oct 01 00:19:53 automation hass[16726]: state = STATE_UNKNOWN if self.state is None else str(self.state)
Oct 01 00:19:53 automation hass[16726]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 147, in state
Oct 01 00:19:53 automation hass[16726]: return getattr(self.structure.weather.current, self.variable)
Oct 01 00:19:53 automation hass[16726]: File "/home/hass/.homeassistant/deps/nest/nest.py", line 254, in current
Oct 01 00:19:53 automation hass[16726]: return Forecast(self._current, self._tz)
Oct 01 00:19:53 automation hass[16726]: File "/home/hass/.homeassistant/deps/nest/nest.py", line 205, in __init__
Oct 01 00:19:53 automation hass[16726]: fget('observation_epoch')))))
Oct 01 00:19:53 automation hass[16726]: TypeError: float() argument must be a string or a number, not 'NoneType'

I went one by one and commented out all weather related sensors until wink loaded properly..  I used this configuration.yaml to get wink working - Including the Nest Protects.  Looks like the issue is with the weather related sensors.
  - platform: nest
    monitored_conditions:
      - 'temperature'
      - 'target'
      - 'humidity'
#      - 'operation_mode'
      - 'last_ip'
      - 'local_ip'
      - 'last_connection'
      - 'battery_level'
#      - 'weather_condition'
#      - 'weather_temperature'
#      - 'weather_humidity'
#      - 'wind_speed'
#      - 'wind_direction'
      - 'co_status'
      - 'smoke_status'

Each of the weather related sensor would result in a Traceback:
Oct 01 00:36:19 automation hass[18289]: ERROR:homeassistant.components.sensor:Error while setting up platform nest
Oct 01 00:36:19 automation hass[18289]: Traceback (most recent call last):
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 107, in _setup_platform
Oct 01 00:36:19 automation hass[18289]: discovery_info)
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 68, in setup_platform
Oct 01 00:36:19 automation hass[18289]: add_devices(sensors)
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 198, in add_entities
Oct 01 00:36:19 automation hass[18289]: if self.component.add_entity(entity, self):
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 134, in add_entity
Oct 01 00:36:19 automation hass[18289]: entity.update_ha_state()
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 155, in update_ha_state
Oct 01 00:36:19 automation hass[18289]: ).result()
Oct 01 00:36:19 automation hass[18289]: File "/usr/lib/python3.4/concurrent/futures/_base.py", line 402, in result
Oct 01 00:36:19 automation hass[18289]: return self.__get_result()
Oct 01 00:36:19 automation hass[18289]: File "/usr/lib/python3.4/concurrent/futures/_base.py", line 354, in __get_result
Oct 01 00:36:19 automation hass[18289]: raise self._exception
Oct 01 00:36:19 automation hass[18289]: File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
Oct 01 00:36:19 automation hass[18289]: result = next(coro)
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 181, in async_update_ha_state
Oct 01 00:36:19 automation hass[18289]: state = STATE_UNKNOWN if self.state is None else str(self.state)
Oct 01 00:36:19 automation hass[18289]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/sensor/nest.py", line 145, in state
Oct 01 00:36:19 automation hass[18289]: return getattr(self.structure.weather.current.wind, self.variable)
Oct 01 00:36:19 automation hass[18289]: File "/home/hass/.homeassistant/deps/nest/nest.py", line 254, in current
Oct 01 00:36:19 automation hass[18289]: return Forecast(self._current, self._tz)
Oct 01 00:36:19 automation hass[18289]: File "/home/hass/.homeassistant/deps/nest/nest.py", line 205, in __init__
Oct 01 00:36:19 automation hass[18289]: fget('observation_epoch')))))
Oct 01 00:36:19 automation hass[18289]: TypeError: float() argument must be a string or a number, not 'NoneType'

@jwl17330536 check if this will work for you.
Override the deps/nest/nest.py with this file https://gist.githubusercontent.com/tchellomello/439e5896a85d0dc5e045e1e52aec69bd/raw/77cc0c5b65e9076b611d5bc4d31c6189f49a40bd/nest.py
cd deps/nest
mv nest.py nest.py.orig
wget https://gist.githubusercontent.com/tchellomello/439e5896a85d0dc5e045e1e52aec69bd/raw/77cc0c5b65e9076b611d5bc4d31c6189f49a40bd/nest.py

Then override the component sensor/nest component with this code https://gist.githubusercontent.com/tchellomello/c8c49b24578acad81830d08f94782bdb/raw/39ea85eef2d956188fb044d5d92acefc25afba86/nest.py
mkdir -p custom_components/sensor
cd custom_components/sensor
wget https://gist.githubusercontent.com/tchellomello/c8c49b24578acad81830d08f94782bdb/raw/39ea85eef2d956188fb044d5d92acefc25afba86/nest.py

Then use this configuration:
sensor:
  - platform: nest
    monitored_conditions:
      - 'temperature'
      - 'target'
      - 'humidity'
      - 'last_ip'
      - 'local_ip'
      - 'last_connection'
      - 'battery_level'
      - 'mode'   # <--- note that this one changed name
      - 'weather_condition'
      - 'weather_temperature'
      - 'weather_humidity'
      - 'wind_speed'
      - 'wind_direction'
      - 'co_status'
      - 'smoke_status'

Restart HA and it should be displayed.  Let me know if worked and we get start a PR for this.

I followed your instructions and got an error loading wink:
Oct 01 13:03:12 automation hass[23908]: ERROR:homeassistant.bootstrap:Invalid config for [sensor.nest]: value is not allowed @ data['monitored_conditions'][7]. Got 'mode'. Please check the docs at https://home-assistant.io/components/sensor.nest/
I put custom_components in "deps/nest" ... so the full path is "deps/nest/custom_components/sensor" which I'm wondering if that's right.  Where should cusom_compenents be?

I think I found where the custom_components directory should be... config_directory/custom_components ?
Tracebacks aside, it loaded all of my sensors!  All three thermostats, all the configured sensors on each, and my nest protects!
Here are the Traceback's for you:
Oct 01 13:27:31 automation hass[25148]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Oct 01 13:27:31 automation hass[25148]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Oct 01 13:27:31 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Oct 01 13:27:31 automation hass[25148]: return self._compiled.render(kwargs).strip()
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Oct 01 13:27:31 automation hass[25148]: return self.environment.handle_exception(exc_info, True)
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Oct 01 13:27:31 automation hass[25148]: reraise(exc_type, exc_value, tb)
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Oct 01 13:27:31 automation hass[25148]: raise value.with_traceback(tb)
Oct 01 13:27:31 automation hass[25148]: File "<template>", line 1, in top-level template code
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/sandbox.py", line 329, in getattr
Oct 01 13:27:31 automation hass[25148]: value = getattr(obj, attribute)
Oct 01 13:27:31 automation hass[25148]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:31 automation hass[25148]: During handling of the above exception, another exception occurred:
Oct 01 13:27:31 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:31 automation hass[25148]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Oct 01 13:27:31 automation hass[25148]: self._callback(*self._args)
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Oct 01 13:27:31 automation hass[25148]: future.set_result(callback(*args))
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Oct 01 13:27:31 automation hass[25148]: raise TemplateError(err)
Oct 01 13:27:31 automation hass[25148]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:31 automation hass[25148]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:31 automation hass[25148]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Oct 01 13:27:31 automation hass[25148]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Oct 01 13:27:31 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Oct 01 13:27:31 automation hass[25148]: return self._compiled.render(kwargs).strip()
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Oct 01 13:27:31 automation hass[25148]: return self.environment.handle_exception(exc_info, True)
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Oct 01 13:27:31 automation hass[25148]: reraise(exc_type, exc_value, tb)
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Oct 01 13:27:31 automation hass[25148]: raise value.with_traceback(tb)
Oct 01 13:27:31 automation hass[25148]: File "<template>", line 1, in top-level template code
Oct 01 13:27:31 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/sandbox.py", line 329, in getattr
Oct 01 13:27:32 automation hass[25148]: value = getattr(obj, attribute)
Oct 01 13:27:32 automation hass[25148]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:32 automation hass[25148]: During handling of the above exception, another exception occurred:
Oct 01 13:27:32 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:32 automation hass[25148]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Oct 01 13:27:32 automation hass[25148]: self._callback(*self._args)
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Oct 01 13:27:32 automation hass[25148]: future.set_result(callback(*args))
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Oct 01 13:27:32 automation hass[25148]: raise TemplateError(err)
Oct 01 13:27:32 automation hass[25148]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:32 automation hass[25148]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:32 automation hass[25148]: ERROR:asyncio:Exception in callback run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144
Oct 01 13:27:32 automation hass[25148]: handle: <Handle run_callback_threadsafe.<locals>.run_callback() at /srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py:144>
Oct 01 13:27:32 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 99, in async_render
Oct 01 13:27:32 automation hass[25148]: return self._compiled.render(kwargs).strip()
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 989, in render
Oct 01 13:27:32 automation hass[25148]: return self.environment.handle_exception(exc_info, True)
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/environment.py", line 754, in handle_exception
Oct 01 13:27:32 automation hass[25148]: reraise(exc_type, exc_value, tb)
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/_compat.py", line 37, in reraise
Oct 01 13:27:32 automation hass[25148]: raise value.with_traceback(tb)
Oct 01 13:27:32 automation hass[25148]: File "<template>", line 1, in top-level template code
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/jinja2/sandbox.py", line 329, in getattr
Oct 01 13:27:32 automation hass[25148]: value = getattr(obj, attribute)
Oct 01 13:27:32 automation hass[25148]: jinja2.exceptions.UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:32 automation hass[25148]: During handling of the above exception, another exception occurred:
Oct 01 13:27:32 automation hass[25148]: Traceback (most recent call last):
Oct 01 13:27:32 automation hass[25148]: File "/usr/lib/python3.4/asyncio/events.py", line 120, in _run
Oct 01 13:27:32 automation hass[25148]: self._callback(*self._args)
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/util/async.py", line 147, in run_callback
Oct 01 13:27:32 automation hass[25148]: future.set_result(callback(*args))
Oct 01 13:27:32 automation hass[25148]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/template.py", line 101, in async_render
Oct 01 13:27:32 automation hass[25148]: raise TemplateError(err)
Oct 01 13:27:32 automation hass[25148]: homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'attributes'
Oct 01 13:27:32 automation hass[25148]: WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'attributes'

@jwl17330536 the custom_componenets should be under the <configuration_dir>.
Glad it worked. the traceback seems to be related with another part of HA. I think we can work on PR to get it merged. I'll try to look into this.
Thanks for testing it.

No problem. Thanks for putting it together and getting it fixed.
Sent from my iPhone

On Oct 1, 2016, at 1:48 PM, Marcelo Moreira de Mello<EMAIL_ADDRESS>wrote:
@jwl17330536 the custom_componenets should be under the .
Glad it worked. the traceback seems to be related with another part of HA. I think we can work on PR to get it merged. I'll try to look into this.
Thanks for testing it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

So we will have a working version in 0.29.7? ;-)

@broesie  not sure if it will be included on 0.29.7 but it should be in the next version once we get the PR https://github.com/home-assistant/home-assistant/pull/3665 merged.


UI of Riot Android should look like Riot iOS example top panel color, green + etc

Top headings should be centered for all views

The android client has its own design. There is no reason to have the same design than  the IOS client.
You can easily customize it.


not recompiling/reloading happening

I'm new to the modern ways of javascript development i used vue-cli with this template to start my vue project. When i save files (i tried: main.js, App.vue and HelloWorld.vue) nothing happens. I need to restart the server to see my changes. I'm on a NFS share so i know inotify does not work, so i enabled polling by placing
  watchOptions: {
    aggregateTimeout: 300,
    poll: 1000
  },

between these two lines https://github.com/vuejs-templates/webpack/blob/develop/template/build/webpack.base.conf.js#L22-L23 as described here https://webpack.js.org/configuration/watch/#watchoptions
I also tried passing --watch-poll 1000 --watch to webpack-dev-server on this line https://github.com/vuejs-templates/webpack/blob/develop/template/package.json#L8
I also tried increase aggregateTimeout to<PHONE_NUMBER>
I'm not sure what else i can do from this point to further debug this issue. webpack-dev-server is not available as executable on my system path so i'm not sure how vue-cli launches it.

This comment solved it for me https://github.com/vuejs-templates/webpack/issues/432#issuecomment-346954884


Align source and reference image using feature matching

I have made test with some real-life images and the script start to work on some of them.

Transform found:
{
  transform: {
    rotation: -0.19385536506284526,
    scale: 1.0368736678504342,
    translation: { column: 42, row: 8 }
  },
  nbMatches: 49,
  nbInliers: 5,
  nbRansacIterations: 1000
}

Another image, that is pretty different from the source works a lot worse. Maybe we could still enhance the matching a bit, but I think the matching is bad because the typo is different.

Transform found:
{
  transform: {
    rotation:<PHONE_NUMBER>4172754,
    scale: 10.581497571701478,
    translation: { column: 1629, row: 1215 }
  },
  nbMatches: 25,
  nbInliers: 2,
  nbRansacIterations: 1000
}

This result doesn't make sense. We can see that if they are only 2 inliers, the results are probably aberrant.

I created a new function called filterDistanceEucledean, which takes matches where many source keypoints can point to the same destination keypoint, and which returns the keypoints that are the closest in space to the ones in the destination. It is a simple way to eliminate some outliers in our specific case where we approximately know where the destination is.
By using this function, I am getting better results with the image with a different typo, even though they are still varying from one run to another. Here is the result in a good case.

Todo:

[ ] The image that is extended with a margin should be the source and not the reference.
[ ] Test an ROI containing some background

Test on an ROI containing background
Images with enhanced contrast

Reference:

Keypoints found and matches

## Final transform found:
{
  transform: {
    rotation: -176.93926671318394,
    scale: 0.7716111373412708,
    translation: { column: 359, row: 153 }
  },
  stats: {
    nbMatches: 106,
    nbInliers: 3,
    nbRansacIterations: 1000,
    nbSourceKeypoints: 239,
    nbDestinationKeypoints: 280
  }
}

As they are a lot of keypoints, it is more likely that the model found by ransac has more inliers, here 3 instead of the usual 2 when the model is bad. To detect bad matching, we could use a criteria nbInliers/nbKeypoints that should have a minimal value, as well as requiring a minimum of 3 inliers.

rotation: -176.93926671318394,
This transformation would be rejected. We know the orientation is already the same. You can see in the current Python code that there are some checks done on the feature matching alignment. If it cannot be done it falls back to another method (minimum difference).
I doesn't make sense to try and find matching keypoints when the images have different visual patterns.

I doesn't make sense to try and find matching keypoints when the images have different visual patterns.

I totally agree, but we have to compute the matches in order to get the transformation and we can then check the rotation and scale rignt?


async is a reserved keyword in Python 3.7

While debugged the api.tasks, I hit a depreciation warning. Basically, 'async' will be a reserved word in Python 3.7 so quest will break. We are using the kwarg async=True as a flag for running tasks in the background. Maybe change the kwarg to 'delayed'. Open to suggestions.

I know that async is short for asynchronous and it is a little bit longer but why don't we change it to the longer version? Then we can keep the same word.

Here is what PEP8 advised to do in these cases:

single_trailing_underscore_: used by convention to avoid conflicts with Python keyword.

So we could use async_ which looks weird. Maybe async_task . For some reason, I don't like asynchronous not sure why, maybe its just too annoying to spell.

Alright I can change all the async's to async_task if that is what you like. I really don't have a preference but as long as we don't hit a reserved word.

Okay I just made a PR for this issue and updated the async word. I did not update the docs but @sdc50  and I need to have a document day where we just do an overhaul on the docs. Thanks.


Remove monitor statements to increase speed

Apparently monitor functions can bog DynaSim down by an order of 5-50x. I'm going to experiment removing this and seeing how it affects sim speed

For a model consisting of the following:
80 RS cells, 20 IB, 20 NG, 20 FS, and 20 LTS cells, removing monitor statements reduced run time from 67.039671 seconds to 36.0714 seconds. Compile flag was turned on.


Model Zoo IR-152 download link is broken

Hi,
In model zoo, the download link of IR-152 is broken. Also, is it possible upload the files to google drive?
Thank you!

It seems that I can’t use Baidu drive in my region.

Hi, we have checked the baidu drive link and pw, and we did not find any problem. Please check again. Currently, our google drive has reached its upper limit, we will try to upload the model to google drive in near future.


Scrollbar appears with Dotter Panel

Do not observe the same on my machine - but attempted a fix.


Client: Store last used workbook app and select it on startup.

Sets the agent type when either the broader agent grouping or the more specific agent type within the grouping is set and changes constructors to use field setters instead of property setters to avoid side effects as necessary so that we don't update the preference all the time when constructing the items/controller.
Fixes #58.

build


PASS mode anonymous access for Apache 2.4

I couldn't get anonymous access to work without this patch using Apache 2.4.  PASS mode worked fine when authenticated, but got a 500 error when unauthenticated.
With this patch, all that is required in Apache config is a block like:
<Location /anon>
    OIDCUnAuthAction PASS
</Location>

If I've just overlooked something and PASS mode should work with Apache 2.4 without this patch, please advise the configuration required to get it to work.  As always, please let me know if you like the idea of the patch but would like some refactoring.
Thanks.

thanks; I noticed Apache 2.2 works differently indeed for the standard use case but your patch is also required for 2.2 if Require statements other than "valid-user" are configured on the path; perhaps you can add the same code (or refactor it in to a function) for the 2.2 authz routine as well, or else I can do it later

Thanks @zandbelt, I'll update the PR ASAP.

@zandbelt let me know if you're happy with the change for <2.4.

For those using OIDCUnAuthAction pass: be aware that using this in a secure manner requires at least version 2.1.5 https://github.com/pingidentity/mod_auth_openidc/releases/tag/v2.1.5


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit 82198e8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8122898:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Please support null safety (Flutter 2+)

When trying to use some snippets, such as the getform, the generated code is not null-safety compliant:

Also, it would be nice if the generated code is linted (with https://pub.dev/packages/lint for example).

I will do it today!!

By the way, this snippet shouldn't create the FormState key inside the build method, re-creating it at every build.

Yes, this was one of the snippets I left behind, haha but I just updated it, today I'm finishing everyone's update and I'll have a new version available!

`import 'package:flutter/material.dart';
import 'package:get/get.dart';
import 'package:sacrafood/app/modules/login/controller.dart';
class CustomForm extends Container {
final GlobalKey _formKey = GlobalKey();
final controller = Get.find();
@override
Widget build(BuildContext context) {
return Form(
key: key,
child: Column(
children: [
TextFormField(
keyboardType: TextInputType.emailAddress,
decoration: InputDecoration(labelText: 'Email'),
enableSuggestions: true,
maxLength: 32,
style: TextStyle(fontSize: 20),
onSaved: (v) => this.controller.onSavedEmail(v),
onChanged: (v) => this.controller.onChangedEmail(v),
validator: (v) => this.controller.onValidateEmail(v),
),
TextFormField(
keyboardType: TextInputType.text,
decoration: InputDecoration(labelText: 'Senha'),
enableSuggestions: true,
obscureText: true,
maxLength: 20,
style: TextStyle(fontSize: 20),
onSaved: (v) => this.controller.onSavedPassword(v),
onChanged: (v) => this.controller.onChangedPassword(v),
validator: (v) => this.controller.onValidatePassword(v),
),
MaterialButton(
onPressed: () async {
final FormState form = this._formKey.currentState!;
if (form.validate()) {
form.save();
await this.controller.login();
}
},
child: Text('OK'),
)
],
));
}
}
`


GraphiteReporter: Unable to report to Graphite

I am trying to make changes in dropwizard-master\dropwizard-example to integrate with graphite to view metrics dashboard.
Example version:    dropwizard-example
0.8.1-SNAPSHOT
Have Made below changes:
In pom.xml added dependency

io.dropwizard
dropwizard-metrics
${project.version}

io.dropwizard
dropwizard-metrics-graphite
${project.version}

Within HelloWorldApplication --> run added
MetricRegistry metrics = new MetricRegistry();
MetricsFactory mfac = configuration.getMetricsFactory();
mfac.configure(environment.lifecycle(), metrics);
Counter counter = metrics.counter("nameOfCounter");
counter.inc();
counter.inc();
counter.inc();
counter.inc();
counter.inc();
And example.yml report to graphite server hosted by hostedgraphite.com
metrics:
reporters:
- type: console
timeZone: UTC
output: stdout
durationUnit: milliseconds
rateUnit: seconds
frequency: 120 seconds
- type: graphite
host: hostedgraphite.com
port: 2003
prefix: <API_KEY_REGISTERED>
When GraphiteReporter tries report it gives  Connection timed out: connect as below:
WARN  [2015-03-30 10:23:17,851] com.codahale.metrics.graphite.GraphiteReporter: Unable to report to Graphite
! java.net.ConnectException: Connection timed out: connect
! at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~[na:1.7.0_65]
! at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[na:1.7.0_65]
! at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[na:1.7.0_65]
! at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[na:1.7.0_65]
! at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[na:1.7.0_65]
! at java.net.PlainSocketImpl.connect(Unknown Source) ~[na:1.7.0_65]
I am new to dropwizard usage. Please suggest which configuration is incorrect (tried with port 80 and host as IP address)?

Are you certain the hostname is correct?

Thanks. After correcting host/port able to view nameOfCounter in graphite and able to configure few metrics for hibernate active/max connections.
One more help I need. Can we view hibernate query time on graphite which gets written in console as
INFO  [2015-03-30 15:37:26,462] org.hibernate.engine.internal.StatisticalLoggingSessionEventListener: Session Metrics {
89309 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
61978 nanoseconds spent preparing 1 JDBC statements;
85075 nanoseconds spent executing 1 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
184392 nanoseconds spent executing 1 flushes (flushing a total of 1 entities and 0 collections);
11934 nanoseconds spent executing 1 partial-flushes (flushing a total of 0 entities and 0 collections)

To my knowledge there is not a metrics module which listens for Hibernate's internal metrics.


Getting android build error

Sometimes I'm getting this error
:react-native-video-processing:processDebugAndroidTestManifest FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-video-processing:processDebugAndroidTestManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 16 cannot be smaller than version 17 declared in library [com.github.kesha-antonov:ffmpeg-android-java:e69ea470d69d271fafbd03d0a4b0ea67d6731ccc] /Users/andrew/src/jh-mobile/node_modules/react-native-video-processing/android/build/intermediates/exploded-aar/com.github.kesha-antonov/ffmpeg-android-java/e69ea470d69d271fafbd03d0a4b0ea67d6731ccc/AndroidManifest.xml
     Suggestion: use tools:overrideLibrary="com.github.hiteshsondhi88.libffmpeg" to force usage

Where do we need to add tools:overrideLibrary="com.github.hiteshsondhi88.libffmpeg" to avoid that? @kesha-antonov
My minSdkVersion is 17 in both AndroidManifest.xml and app/build.gradle

I tried to add tools:overrideLibrary="com.github.hiteshsondhi88.libffmpeg" in my project's manifest but it doesn't help. Seems it should be added to your library.

Hey!
Do you have this?
https://github.com/shahen94/react-native-video-processing/issues/67#issuecomment-305023617

yes @kesha-antonov. Described error appears after android studio's indexing complete but it disappears after pressing build app and the app successfully build.

I just want to know if we can prevent it

I don't know.
I build android through CLI (not android studio)

@gevorg94 Plenty of libraries give me grief like that. I find a postinstall hook in the package.json is the best option since we are all working on the bleeding edge. This covers more than react-native-video-processing but you should get the idea.
a section of my scripts in package.json::
    "patch-rnvp2": "sed -i -e 's/23.0.1/25.0.0/g' 'node_modules/react-native-video-processing/android/build.gradle'",
    "patch-rnmm": "sed -i -e 's/23.0.1/25.0.0/g' 'node_modules/react-native-media-meta/android/build.gradle'",
    "postinstall": "npm run patch-rnvp1; npm run patch-rnvp2; npm run patch-rnmm;",```

@gevorg94 Did you get your build working per my solution? If so I think we could add it to the readme and close the issue.

No I haven't tried to build with your solution yet. I will try it soon

@gevorg94 also note the solution I provide only works if you already have your project open in Android Studio... the build.gradle files for each node module won't exist until Android Studio does a sync. So the other solution would be to not run a postinstall hook and instead just note that you have to execute that as a standard script afterward.
In this order:

npm install
Open the project in Android Studio
npm run gradlePatches (or whatever you want to call it)

close please

For anyone searching like I was, I fixed this by adding the following to my AndroidManifest.xml:
<uses-sdk tools:overrideLibrary="com.github.hiteshsondhi88.libffmpeg"/>

How i could forget that, ya i guess you're right.
I got an error when gradle sync the project, but when i build project - it built without any error. If you guys are getting an error when gradle starts sync the project - add this line to the manifest file - the gradle sync error should be fixed.
@zachrnolan if we'll add this line to the manifest of our project, can it fix gradle sync error ?

@shahen94 I got the error when trying to build my project on Android react-native run-android after doing the initial install in the readme. It wouldn't build until I added the uses-sdk line above.


[FEATURE REQ] Documentation for build tool in msdocs

I believe this can be considered resolved with the existing documentation here: https://learn.microsoft.com/en-us/azure/developer/java/sdk/get-started-maven
As well as the updates coming soon here: https://github.com/MicrosoftDocs/azure-dev-docs-pr/pull/4248


Spring Cloud Contract Generates Weak Tests

Producer side test cases generated by Spring Cloud Contract have weak assertions which can also pass even while it is behaving incorrectly.
Sharing a sample contract to elaborate on my concern.
Contract
request:
  method: GET
  url: /staticData/getAnswers
response:
  status: 200
  body:
    - "value": "0"
      "displayText": "No"
    - "value": "1"
      "displayText": "Yes"
  headers:
    Content-Type: application/json

Generated Test
...
DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
assertThatJson(parsedJson).array().contains("['value']").isEqualTo("0");
assertThatJson(parsedJson).array().contains("['displayText']").isEqualTo("No");
assertThatJson(parsedJson).array().contains("['value']").isEqualTo("1");
assertThatJson(parsedJson).array().contains("['displayText']").isEqualTo("Yes");
...

The above generated test would also pass if the producer returned any of the below incorrect outputs.
[
  {
    "value": "0",
    "displayText": "Yes"
  },
  {
    "value": "1",
    "displayText": "No"
  }
]

[
  {
    "value": "0",
    "displayText": "No"
  },
  {
    "value": "1",
    "displayText": "Yes"
  },
  {
    "value": "-1",
    "displayText": "NA"
  },
]

Here I would like to highlight two concerns:

The test can be false successful by cross comparing the data as highlighted in example 1
The test can be false successful even when additional unexpected elements are returned

Also, I tried using spring.cloud.contract.verifier.assert.size and assertJsonSize  property but they had no effect on the generated test classes so it seems to be fully ignored.
Generated test classes should look more like the below code to avoid such false success scenarios
DocumentContext parsedJson = JsonPath.parse(response.getBody().asString());
assertThatJson(parsedJson).elementWithIndex(0).field("['value']").isEqualTo(0);
assertThatJson(parsedJson).elementWithIndex(0).field("['displayText']").isEqualTo("No");
assertThatJson(parsedJson).elementWithIndex(1).field("['value']").isEqualTo(1);
assertThatJson(parsedJson).elementWithIndex(1).field("[displayText']").isEqualTo("Yes");
assertThatJson(parsedJson).array().hasSize(2);

This code was tested on Java 11 with Spring Boot Version 2.7.13 and Spring Cloud Contract Version 3.1.8

@marcingrzejszczak: Tks for acknowledging the request and tagging it as an enhancement.
I wanted to enquire whether this can be taken up in the near future or this is currently at the bottom of the stack pending prioritization.


Attribute Match Selector Is Case Sensitive

Example Html
<input type="TexT">
<script>>
document.querySelector('input[type="teXt"]').value="Test";
</script>>
It is work with JavaScript + Chrome
Does not find  - AngleSharp
var context = BrowsingContext.New(Configuration.Default);
var htmlParser = context.GetService();
var document = htmlParser.ParseDocument(html)
document.QuerySelectorAll("input[type =  'text']");
Thank you!

Yes this is indeed a bug - the attribute match selector should be case insensitive!
Do you want to make a PR?
Otherwise I'll try to find time on the weekend.

The attribute match selector should be case insensitive!
No, only standart W3C(html5) attribute values

attribute  Name -  should be case insensitive
attribute Value - only W3C(html5) case insensitive, such type ...

Example,
<input type="TexT"  MyattribA="z123"  value="testval">
<script>
alert(document.querySelector('input[type="teXt"]').value);  //Google+JS - OK
alert(document.querySelector('input[myattribA="z123"]').value); //Goole+JS OK
alert(document.querySelector('input[myattribA="Z123"]').value); //Goole+JS Not find
</script>

Yes, good point. It seems like there is a whitelist of certain attribute names that cause case insensitive value comparison.
Do you have the specification part / whitelist?

I do'nt have full whitelist list , :(
for example
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#<input>_types

Not sure what input types (these are values not names) should be useful for.
I would then just go for all known attribute names.

The full list:
https://html.spec.whatwg.org/multipage/semantics-other.html#case-sensitivity-of-selectors

Landed in devel and the preview.


Applying rails-ujs using webpackers

What's the right way to use rails-ujs with webpacker? What I did are the following:

Add snippet of code under shared.js

plugins: [
  new webpack.ProvidePlugin({
    $: 'jquery',
    jQuery: 'jquery'
  }),
  new webpack.ProvidePlugin({
    rails: 'rails-ujs'
  })
],

Add this snippet of code on app/javascript/packs/application.js

// This file is automatically compiled by Webpack, along with any other files
// present in this directory. You're encouraged to place your actual application logic in
// a relevant structure within app/javascript and only use these pack files to reference
// that code so it'll be compiled.
//
// To reference this file, add <%= javascript_pack_tag 'application' %> to the appropriate
// layout file, like app/views/layouts/application.html.erb

console.log($.fn.jquery);
rails.start();
console.log('Hello World from Webpacker');

bin/webpack-watcher will build well however I am receiving this error on my browser.
ReferenceError: Can't find variable: Rails

Looks like rails-ujs requires the file's this to be the global window object, which it is not in modules. For now, there is a shim as explained in the webpack docs:
require('imports-loader?this=>global!rails-ujs');

I didn't try this with ProvidePlugin but it should work, too...

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.


Shapefile reader can fail on empty records

Using QGIS, it is possible to edit a shapefile and remove all points in a record.  The record will still exist in the shapefile, but it will be empty.  Internally, its record length (in words) will be 2.   In such a case, the ShapefileReader class can fail to advance the file position properly, so that the next record read will fail.
Propose to modify the ShapefileReader class to avoid the failure.

Issue addressed.   Fix posted.


Test usage error

Hi,
After following the installation instructions, I tried to launch a test with the following command :
>>> import numpy as np
>>> import Cluster_Ensembles as CE
>>> cluster_runs = np.random.randint(0, 50, (50, 15000))
>>> consensus_clustering_labels = CE.cluster_ensembles(cluster_runs, verbose = True, N_clusters_max = 50)

I got the following error :
>>> consensus_clustering_labels = CE.cluster_ensembles(cluster_runs, verbose = True, N_clusters_max = 50)

INFO: Cluster_Ensembles: cluster_ensembles: due to a rather large number of cells in your data-set, using only 'HyperGraph Partitioning Algorithm' (HGPA) and 'Meta-CLustering Algorithm' (MCLA) as ensemble consensus functions.

*****
INFO: Cluster_Ensembles: HGPA: consensus clustering using HGPA.

#
INFO: Cluster_Ensembles: wgraph: writing wgraph_HGPA.
INFO: Cluster_Ensembles: wgraph: 15000 vertices and 2500 non-zero hyper-edges.
#

#
INFO: Cluster_Ensembles: sgraph: calling shmetis for hypergraph partitioning.
/home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Hypergraph_Partitioning/hmetis-1.5-linux/shmetis: 1: /home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Hypergraph_Partitioning/hmetis-1.5-linux/shmetis: Syntax error: "(" unexpected
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Cluster_Ensembles.py", line 300, in cluster_ensembles
    cluster_ensemble.append(consensus_functions[i](hdf5_file_name, cluster_runs, verbose, N_clusters_max))
  File "/home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Cluster_Ensembles.py", line 648, in HGPA
    return hmetis(hdf5_file_name, N_clusters_max)
  File "/home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Cluster_Ensembles.py", line 973, in hmetis
    labels = sgraph(N_clusters_max, file_name)
  File "/home/philippe/miniconda3/envs/concenssus/lib/python2.7/site-packages/Cluster_Ensembles/Cluster_Ensembles.py", line 1201, in sgraph
    with open(out_name, 'r') as file:
IOError: [Errno 2] No such file or directory: 'wgraph_HGPA.part.50'

Have you installed METIS?

Make sure to chmod 755 each of the executables whose absolute path binding is returned by $ locate shmetis.

All files are in 755

I installed from here:
http://glaros.dtc.umn.edu/gkhome/metis/metis/download
followed the instructions and it worked but I'm using Mac.


Bump CBR and provider to unblock renovate pipeline

Affected modules
| terraform-ibm-modules/cbr/ibm (source) | module | minor | 1.27.0 -> 1.28.1 |
Requires the whole module to bump to IBM Provider 1.70.0

Terraform CLI and Terraform provider versions

Terraform version:
Provider version:

Terraform output

Debug output

Expected behavior

Actual behavior

Steps to reproduce (including links and screen captures)

Run terraform apply

Anything else

By submitting this issue, you agree to follow our Code of Conduct

Addressed in #288


Move the trex package under executor

Currently, only the executor package uses the trex package.

Tested against an OpenShift Virtualization 4.14 cluster.

Change: Rebase


C#: Bindings generator now translates BBCode docs to XML comments

It's not perfect, but much better than what we had before.
Here's the full diff of the generated bindings: https://gist.github.com/neikeq/5298b69567a24a683a42777aa3fcdbb7
Regarding member/type/etc references, right now the following are not automatically resolved but it would be possible with some mapping:
Generating FuncRef.cs...
Cannot resolve type from method reference in documentation: @GDScript.funcref
Cannot resolve type from method reference in documentation: @GDScript.funcref

Generating GDScriptFunctionState.cs...
Cannot resolve type from method reference in documentation: @GDScript.yield
Cannot resolve type from method reference in documentation: @GDScript.yield

Generating Node.cs...
Cannot resolve method reference for non-Godot.Object type in documentation: String.match
Cannot resolve method reference for non-Godot.Object type in documentation: String.match

Generating Texture.cs...
Cannot resolve type from method reference in documentation: @GDScript.load

Generating WeakRef.cs...
Cannot resolve type from method reference in documentation: @GDScript.weakref

Marking this for cherry-picking, as it's a documentation improvement that would be great to have in the 3.1.x branch.

Cherry-picked for 3.1.1.


Zendriver issue with listener loop interruption

flare-bypasser  | 2024-12-08 23:36:50,077 [asyncio] [ERROR]: Task exception was never retrieved
flare-bypasser  | future: <Task finished name='Task-35' coro=<Listener.listener_loop() done, defined at /usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/connection.py:606> exception
=InvalidStateError('invalid state')>
flare-bypasser  | Traceback (most recent call last):
flare-bypasser  |   File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/connection.py", line 126, in __call__
flare-bypasser  |     self.__cdp_obj__.send(response["result"])
flare-bypasser  | StopIteration: (FrameId('B1214E78BA72CC5D4850EE688E8653D1'), LoaderId('EDF9E37B9AFCDD3D690E47D2FFA5CAC0'), 'net::ERR_ABORTED')
flare-bypasser  |
flare-bypasser  | During handling of the above exception, another exception occurred:
flare-bypasser  |
flare-bypasser  | Traceback (most recent call last):
flare-bypasser  |   File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/connection.py", line 653, in listener_loop
flare-bypasser  |     tx(**message)
flare-bypasser  |   File "/usr/local/lib/python3.11/site-packages/zendriver_flare_bypasser/core/connection.py", line 129, in __call__
flare-bypasser  |     return self.set_result(e.value)
flare-bypasser  |            ^^^^^^^^^^^^^^^^^^^^^^^^
flare-bypasser  | asyncio.exceptions.InvalidStateError: invalid state
flare-bypasser  | 2024-12-08 23:37:36,337 [flare_bypasser.flare_bypasser] [INFO]: fork #0, Close webdriver
flare-bypasser  | Processing timeout (max_timeout=60.0)
flare-bypasser  | Traceback (most recent call last):
flare-bypasser  |   File "/usr/local/lib/python3.11/site-packages/flare_bypasser/browser_wrapper.py", line 404, in _wait_first
flare-bypasser  |     finished, to_cancel_tasks = await asyncio.wait(
flare-bypasser  |                                 ^^^^^^^^^^^^^^^^^^^
flare-bypasser  |   File "/usr/local/lib/python3.11/asyncio/tasks.py", line 428, in wait
flare-bypasser  |     return await _wait(fs, timeout, return_when, loop)
flare-bypasser  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
flare-bypasser  |   File "/usr/local/lib/python3.11/asyncio/tasks.py", line 535, in _wait
flare-bypasser  |     await waiter
flare-bypasser  | asyncio.exceptions.CancelledError

Fixed in this commit


Function inlining

Add the function inlining optimization.

Currently, for the recursive example, the call doesn't get inlined at all. This is not expected, I would expect it to unroll a few calls based on how many times we apply our rules.

The reason that recursive function calls do not get inlined is that the function body also has a function call, so inlining only increases the cost of the rewritten program (thank you Oliver for figuring this out)


fix: add support for nodejs10.x runtime

I've update the version check to add support for nodejs 10.x, and made it so that it won't throw an exception when the provider runtime isn't present.

I'm getting a [BABEL] ... Invalid Option: '10.x' is not a valid value for 'targets.node'. error when using your modifications. Not sure, but I think you need to remove the .x from the version number before passing it to babel?

@theBenForce could you please remove .x from the node version as suggested by @jonasduever

I just added the requested change to remove .x from the node version. Let me know if anything else needs updated.

Works fine using node v10.15.3 on Windows 10 1809, serverless 1.43.0.

LGTM. Thanks all for PR.


PAPIv3: move to, aspirate, dispense at arbitrary location

Overview
As a PAPIv3 author, I'd like to command liquid handling actions to occur at a specific location in deck coordinates so I can enable complex workflows.
Acceptance criteria
A PAPIv3 author may:

[ ] Call pipette_context.aspirate with a location in deck coordinates
[ ] Call pipette_context.dispense with a location in deck coordinates
[ ] Call aspirate or dispense without deck coordinates to perform the action in place

Implementation notes
This likely requires new PE commands rather than trying to shoehorn these advanced use cases into the existing, well-based commands

Hey team! Please add your planning poker estimate with ZenHub @mattwelch @sanni-t @SyntaxColoring @y3rsh


[NEW ALGORITHM] Bron-Kerbosch Algorithm for undirected graph

Name:
Bron-Kerbosch Algorithm
About:
The Bron-Kerbosch Algorithm is a recursive, backtracking algorithm, widely used in fields such as social network analysis, bioinformatics, and community detection, where identifying clusters or highly interconnected subgroups is valuable. It’s efficient for finding all cliques in sparse graphs and often outperforms brute-force approaches due to its pruning techniques.

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

assigned


Create space between glued together words

@jawn Thank you, I am merging this now and it should be live soon.


if i don't want to use dev set and test set

hello, everyone;
i'm training a model and i use shell script which indicates my dev set file and test set file like this:
--dev_prefix=./nmt_dev_test_data/dev
--test_prefix=./nmt_dev_test_data/test
but i found it was too time-consuming when "decoding to output ./nmt_model/output_dev"。in my machine with 12 cpu core and 4 gpu，it takes 12 hours ! my dev set file has 100000 lines.
now i have two questions.

if i don't use dev set and test set when training, this will effects my trained model?
if don't effect my trained model , how can i modify my shell script or source code to achieve this goal?

thans. everybody

It will be hard to see how your model actually perform during training if you don't use dev and test set, and you won't be able to select the best model.
Have you considered sample test/dev data to smaller size?
Another option is increasing the value of  --steps_per_external_eval flag to make external eval less frequent.


chore(ci): try a different ubuntu runner

We are getting random cancels with ubuntu-latest that seem to be similar to previous issues on github end (the github-hosted runner itself reports failure)

ok tons of cancels with ubuntu 24, let me try ubuntu... 20!? grasping here


fixed issue with keyboard input being ignored by gizmo

fixes issue #204 as well as other issues of keypresses being ignored

Seems to work on my end. Approved the pipeline for now

Thanks for the PR


chore(): ignore bower.json in npm installations.

This may confuse and break some loaders (e.g. webpack) that are configured to read bower.json descriptor files (see https://github.com/codewizz/bower-resolve-webpack-plugin/pull/2#pullrequestreview-29257842). Installed NPM modules do not require bower.json as it also points to a non-existent file (dist/debug.js).
This is common for isomorphic libraries (e.g. https://github.com/visionmedia/superagent/commit/8ae738056afae55df77218d7c17c39e2bb54b950) (just noticed superagent is from you guys as well :D)

Coverage remained the same at 63.75% when pulling 212ddc9ce1442b4f43065d00e796bb378e2ad739 on joaovieira:patch-1 into 27d93a37f7f6cd76e273826ee7d8252be2d5f457 on visionmedia:master.


First serious attempt at view recycling

[ ] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

Before merging

So many tests
Generated code updates for reuseIds
Generated code updates for getting the list of children tags

Follow-ups

Events to track reuse hits and misses
Create the idToSubtree map lazily in applyReuse() to reduce allocations
Create ReuseSubtree.children lazily, or maybe use a custom singly-linked list

I’m going to shift my focus to compose side for now. It has the giant benefit of working without the protocol layer.
https://github.com/cashapp/redwood/pull/1896


fix ignored clearold flag

Wanted to notify about this bug in OpenSSL, I stumbled upon it during development of vpp static server https POST that uses crypto engine + pipeline support.
I failed to get the git push working, so I am posting the commit that fixes the bug I experienced.
From ea7e8b0f6123846d143d0a6132b47c62a931db5e Mon Sep 17 00:00:00 2001
From: Ofer Heifetz<EMAIL_ADDRESS>Date: Tue, 24 Jan 2023 12:16:33 -0800
Subject: [PATCH] fix ignored clearold flag

When ssl3_read_n() is called with clearold == 1, packet data should
be moved to start of buffer, but the routine had a memmove() call
regardless to clearold value.

On a system that is configured to use piplines, the above flag ignorance
may cause situation where two records use the same address.

Signed-off-by: Ofer Heifetz<EMAIL_ADDRESS>---
 ssl/record/rec_layer_s3.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/ssl/record/rec_layer_s3.c b/ssl/record/rec_layer_s3.c
index 1db1712a09..58e0066dee 100644
--- a/ssl/record/rec_layer_s3.c
+++ b/ssl/record/rec_layer_s3.c
@@ -230,8 +230,10 @@ int ssl3_read_n(SSL *s, size_t n, size_t max, int extend, int clearold,
                  * effect on memmove arguments and therefore no buffer
                  * overrun can be triggered.
                  */
-                memmove(rb->buf + align, pkt, left);
-                rb->offset = align;
+                if (clearold == 1) {
+                    memmove(rb->buf + align, pkt, left);
+                    rb->offset = align;
+                }
             }
         }
         s->rlayer.packet = rb->buf + rb->offset;
--
2.25.1

Interesting. This is actually the same bug that was fixed in master recently - see #19456. The code has been moved around a bit there (it now lives in a different file in a different function) - but its the same thing. Probably a backport of the same fix that was applied there should be applied here too. Your proposed fix is not wrong, but I think the memmove is actually redundant in the clearold == 1 case for the reasons explained in https://github.com/openssl/openssl/pull/19456#discussion_r1006945684

My fix for this, plus some backports of other related pipelining bugs that were fixed in master recently is in #20208

So both 1.1.1 and 3.1/3.0 next release should have the above mentioned pipeline issue resolved?
When I saw the bug first thing I did is look at latest release of above OpenSSL and saw that the same code exists.

So both 1.1.1 and 3.1/3.0 next release should have the above mentioned pipeline issue resolved?

Well it will be fixed in the next release after #20208 is merged. The code repository is currently frozen due to the 3.0.8/1.1.1t release taking place tomorrow. So it won't be in the next release - but hopefully the one after that. I've currently only backported it to 3.1/3.0. 1.1.1 is in security fix only mode at the moment.
It should already be fixed in master (the 3.2 development branch).

@mattcaswell this looks like it is addressed now?

@mattcaswell this looks like it is addressed now?

Yes. This is fixed. Closing.


500 error when merging a pull request

Been using a forked repo for a while with no issues, I have 29 merged pull requests on the master repo from this fork
Trying to merge the 30th and it comes up with a 500 error
In the stdout.log this is what it says:
[Macaron] Completed /svr1/si/pulls?type=all&sort=&state=open&labels=0&milestone=0&assignee=0 200 OK in 50.264442ms
[Macaron] Started GET /svr1/si/pulls/79 for 217.xx.xx.xx
[Macaron] Completed /svr1/si/pulls/79 200 OK in 302.220192ms
[Macaron] Started POST /svr1/si/pulls/79/merge for 217.xx.xx.xx
2015/11/10 14:54:56 [...routers/repo/pull.go:380 MergePullRequest()] [E] GetPullRequestByPullID: git pull: From /home/gitgogs/gogs-repositories/chubbyninja/si
 * branch            master     -> FETCH_HEAD

[Macaron] Completed /svr1/si/pulls/79/merge 500 Internal Server Error in 1.125154275s

fork repo is chubbyninja/si and master is svr1/si
I'm using Go 1.5 and Gogs · Version: <IP_ADDRESS>3 Beta
Any idea what could be causing this error? Thanks!

@ChubbyNinja Hi... can you update to 0.7.0...

Sure, doing that now and report back!

Awesome - I didn't realise PR wasn't finished in 0.6.9.
<IP_ADDRESS>7 told me there was a conflict so couldn't auto merge - sorted :+1: thanks

:100:


Use in TypeScript Project

Hello,
I had some issues running this in an Angular 2 project with TypeScript and angular cli. First of all the imports didn't work. I could solve that by adjusting the path to:
import {  reducer as searchReducer, reduxSearch} from 'redux-search/dist/es/index.js'
which feels kinda wrong..
secondly i receive Babel errors, how to avoid that?
babelHelpers is not defined
Your search seams to be really great but it would be nice to easier use it outside of React and Babel environment. :-)

Hm, well the problems are completely unrelated to React/Angular. Seems to be a TypeScript issue.
redux-search publishes 3 build targets: UMD (for <script> tag usage), CommonJS (for Webpack 1), and ES (for Webpack 2, Rollup, etc). The latter (Webpack 2 and Rollup) are still ironing out module issues as far as I can tell and as a result, they don't yet work quite right. But that's the idea.
I've used TypeScript for a few library projects, but not recently- and never with an application that imports other libraries like redux-search. So I'm not sure why it's giving you problems. (An error message or more info about "the imports didn't work" may be helpful, but no promises.)
I can fix the babelHelpers issue for you though. In fact, it should already be fixed if you'll update to version 2.3.2.


XSJob trigger end_date not processed correctly

Describe the bug
Defining an end_date in an xsjob trigger doesn't seem to be taken into account

What version of the XSK are you using?
latest

To Reproduce
handler.js
function handle(){
    console.error("--------- ECHOOOO --------");
}

file.xsjob
{
	"description": "Check Status of users in Azure",
	"action": "project.handler.xsjs::handle",
	"schedules": [
		{
            "description": "Run handler",
            "xscron": "* * * * * * */5",
            "parameter": {}
        }
	]
}

trigger.xsjs
let job = new $.jobs.Job({
    uri: "project/jobs/file.xsjob"
});

// execute the job for 60 seconds, starting from now
job.configure({
    status: true,
    start_time: new Date(),
    end_time: new Date(Date.now() + 60000)
});

In the log I see
[2021-11-12T11:56:16.898Z] [INFO] Scheduled Job: [project/jobs/file.xsjob] of group: [xsk-defined] at: [*/5 * * * * ? *]
[2021-11-12T11:56:20.269Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:56:20.275Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:56:20.435Z] [INFO] Importing: project/jobs/handler.xsjs
[2021-11-12T11:56:20.469Z] [INFO] Imported: project/jobs/handler.xsjs
[2021-11-12T11:56:20.476Z] [ERROR] --------- ECHOOOO --------
[2021-11-12T11:56:20.535Z] [DEBUG] Deleting job: project/jobs/file.xsjob
[2021-11-12T11:56:20.539Z] [DEBUG] Deleting job: project/jobs/file.xsjob
[2021-11-12T11:56:20.541Z] [INFO] Unscheduled Job: [project/jobs/file.xsjob] of group: [xsk-defined]

The number of executions seems random
[2021-11-12T11:58:14.587Z] [INFO] Scheduled Job: [project/jobs/file.xsjob] of group: [xsk-defined] at: [*/5 * * * * ? *]
[2021-11-12T11:58:15.241Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:58:15.249Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:58:15.452Z] [INFO] Importing: project/jobs/handler.xsjs
[2021-11-12T11:58:15.480Z] [INFO] Imported: project/jobs/handler.xsjs
[2021-11-12T11:58:15.487Z] [ERROR] --------- ECHOOOO --------
[2021-11-12T11:58:20.247Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:58:20.252Z] [ERROR] Trying to use HTTP Session Facade without a valid Session (HTTP Request/Response)
[2021-11-12T11:58:20.410Z] [INFO] Importing: project/jobs/handler.xsjs
[2021-11-12T11:58:20.431Z] [INFO] Imported: project/jobs/handler.xsjs
[2021-11-12T11:58:20.437Z] [ERROR] --------- ECHOOOO --------
[2021-11-12T11:58:20.569Z] [DEBUG] Deleting job: xsk-defined.project/jobs/file.xsjob
[2021-11-12T11:58:20.573Z] [DEBUG] Deleting job: xsk-defined.project/jobs/file.xsjob

Discussed and cannot reproduce.


'libdwarf-0/libdwarf.h' file not found, but libdwarf installed by pacman

src/spray_dwarf.h:17:10: fatal error: 'libdwarf-0/libdwarf.h' file not found
#include <libdwarf-0/libdwarf.h>
^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [Makefile:43: build/info.o] Error 1
P.S. My system: Manjaro(Linux 6.6.8-2-MANJARO)

I'd try removing the libdrawf that's installed through pacman and installing manually instead. That's how I build Spray on my machine. There's a tarball of libdwarf's source code here on the libdwarf's GitHub mirror. The root of the extracted folder contains a file called INSTALL. It explains how to install libdwarf in detail. If you get build errors when installing libdwarf, feel free to post them here. :)

I'd try removing the libdrawf that's installed through pacman and installing manually instead. That's how I build Spray on my machine. There's a tarball of libdwarf's source code here on the libdwarf's GitHub mirror. The root of the extracted folder contains a file called INSTALL. It explains how to install libdwarf in detail. If you get build errors when installing libdwarf, feel free to post them here. :)

I was able to build and install spray, but when in the examples folder I compiled the file, spray gave this error
spray: src/debugger.c:1478: void init_load_address(Debugger *): Assertion `parse_base16 (addr, &load_address.value) == SP_OK' failed.
zsh: IOT instruction (core dumped)  spray a.out
foobar
foo
free(): double free detected in tcache 2

Oh yes, I should consider adding the header locally. That would make the install much easier. Did you try copyting libdwarf.h into src and using the Pacman installation of libdwarf to build Spray?

Oh yes, I should consider adding the header locally. That would make the install much easier. Did you try copyting libdwarf.h into src and using the Pacman installation of libdwarf to build Spray?

Yup, I tried that.
But on startup it gives the same error when installing libdwarp via pacman, and when installing via the libdwarp script.

I think there are two issues in the output you posted.
The function in which the failure occurred is meant to read the load address of the process that the debugger trances (the "tracee"). The way it does this is to open the /proc/<pid>/maps file of the tracee process and read everything in the initial line until a - character is found. This part of the file is expected to be a valid hexadecimal number. You can read about the technique at the end of this post. I'm not sure from the start which part of the process of reading the load address failed here.
The other issue is the double free at the end. That one happens on my machine too, although I have not seen/noticed it before. I also wonder why ASan doesn't seem to catch it.

Also, I hope you are on the v0.0.1 commit. main has some unfinished changes, which mean that you don't get syntax highlighting.

But on startup it gives the same error when installing libdwarp via pacman, and when installing via the libdwarp script.

Yes, the following three lines from the output are the real issue there. The rest is all printed by the example.
spray: src/debugger.c:1478: void init_load_address(Debugger *): Assertion `parse_base16 (addr, &load_address.value) == SP_OK' failed.
zsh: IOT instruction (core dumped) spray a.out

And I don't think this error is related to libdwarf. The function in which the assertion failed (init_load_address) doesn't call libdwarf code, and in fact debug information is initialized before init_load_address is called. If init_debug_info returns a valid pointer (which is checked here before init_load_address is called), then I assume that your libdwarf installation works, since init_debug_info calls into libdwarf code.

If you want, you could try the following to poke at the problem:

Check if proc_maps_filepath (initialized on line 1462 by snprintf) is correct. There's no assertion checking the outcome of snprintf. If the filepath is correct, then it should look like this: /proc/<pid>/maps, where <pid> is replaced by the literal of the number in dbg->pid.
You could also check the contents of addr (line 1471). Maybe there is an issue with getdelim.

Essentially, we need to find out why an invalid hexadecimal literal is passed to parse_base16. Along the way, it would be nice to add more assertions to init_load_address. It also seems like parse_base16 doesn't check if the given string is a null-pointer. If it were a null-pointer, parse_base16 would segfault (see line 945).
There's probably a blatant bug here 😅. I just while debugging that is_dyn_exec returned false, so, potentially, I never got the chance to really test the code you're having trouble with.


chore(deps): upgrade golang.org/x/net to v0.17.0

Description
Close #1151
Bumping to<EMAIL_ADDRESS>to resolve vulnerability.

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use
unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Looks like mainline cometbft also upgraded, See: https://github.com/cometbft/cometbft/blob/aae8e3861a628114bb3694bebb205babbed16f02/go.mod#L37

Note govulncheck is still failing for a different reason:
Vulnerability #1: GO-2023-2382
    Denial of service via chunk extensions in net/http
  More info: https://pkg.go.dev/vuln/GO-2023-2382
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>
so I think we should bump Go versions in a seperarate PR

The mempool tests are so flakey 😢


How to find a section's UID

Not a bug - but there's no discussion option for this repo. I'm setting this up for the first time and the docs say you need to change the hidden input to the section's UID. There is no way to find this in the control panel as far as I can tell. If you edit a section, you get the section's ID (4). Could we add something to the docs of this plugin or Craft's docs that describe how to find a section's UID please?
I'm trawling through the project config files but I can't immediately tell from there which ID I'm meant to use either.

Hi, you’re right; it’s not that easy to find at first glance.
The section’s UID is in the file’s name in config/project/sections. For example, I have a section with a handle of mySection, and the project config filename is: mySection--b6ef4bae-8a6d-45fa-8764-7456719485aa.yaml, which means the section UID is b6ef4bae-8a6d-45fa-8764-7456719485aa.
You can also find this by getting the section by ID or handle and then fetching its UID from what’s returned (in a plugin or a module): Craft::$app->sections->getSectionById() or Craft::$app->sections->getSectionByHandle().
Or by getting an entry from that section and then getting its section and UID from there, which can be done in your templates too: {{ craft.entries.slug('test1').one().section.uid }}.
Hope this helps!

Got it, thanks!

Thanks for flagging this, @darylknight!
I've reworked the readme to reflect the available options—and in the process discovered that we actually support sending a Section’s handle, directly:
{{ hiddenInput('sectionHandle', 'mySection') }}

For the sake of closing the loop on your question—@i-just’s PHP API example can be replicated in Twig, like this:
{% set section = craft.app.sections.getSectionByHandle('mySection') %}

{{ hiddenInput('sectionUid', section.uid) }}

That's great, thank you for the extra info


lib/container: Introduce OstreeImageReference

In order to implement ostree-based GPG/signapi verification, we
need the configuration for an ostree remote.
Having a canonical stringified representation of this will
allow using it on command lines and in user interfaces.
The goal is to make it as easy as possible to combine the two in e.g.:
$ ostree remote add fedora --set=gpgkeypath=/etc/pki/rpm-gpg --custom-backend=ostree-ext
$ ostree-ext-cli rebase ostree-remote-image:fedora:quay.io/coreos/fedora-coreos:stable

(ostree-ext-cli rebase doesn't exist, but maybe it will later)

Trying to teach rpm-ostree rebase about the new signing stuff, I hit ergnomic issues.   This is just one idea.
Another one is to make this a URL, like ostreeregistry:myremote:quay.io/exampleos:latest.  So ostreeregistry is a scheme (like https) and its syntax is REMOTENAME:IMGREF.   Actually I'm leaning towards that.

Maybe ostreeimage?  Or something else?

OK I reworked this per https://github.com/ostreedev/ostree-rs-ext/pull/77#issuecomment-918430662 but still need to implement SignatureSource::ContainerPolicy (and add an API that uses OstreeImageReference but that's easy).

OK, lifting draft on this one.  I only lightly tested the SignaturePolicy::ContainerPolicy and SignaturePolicy::ContainerPolicyAllowInsecure paths, but I don't think it's a really big deal right now, just a best effort from our part at this point.  The important one is SignaturePolicy::OstreeRemote.

Just double-checking, : is a disallowed character in an OSTree remote name, right? (I haven't encountered it before, but I think this should be the relevant grammar).
If I'm understanding this scheme proposal correctly, it does rely on : being a reserved/separator token which can't appear in the inner remotename values.

Yep, that's exactly right.  Kelvin and I debated this extensively.  It's why today doing:
rpm-ostree rebase --experimental registry:quay.io/coreos/fedora-coreos
fails today because it's ambiguous whether registry is an ostree remote name or a containers-image schema.
(registry and docker:// are synonymous to containers-image)
This PR is basically introducing a much more verbose and not-ambiguous syntax to explicitly denote we're fetching an ostree-container.
Which, cuts against the "container native" bit by introducing something new and unique to us.  But OTOH, booting a container is special, and the extra typing/cognitive burden shouldn't be a problem in practice.

See also e.g. https://github.com/coreos/coreos-assembler/pull/2402

Other possibilities:
ostree-remote-registry:fedora:quay.io/coreos/fedora:stable
(i.e. we add a shorthand remote-registry for remote-image:...:registry:...)
An entirely different one is something like: quay.io/coreos/fedora:stable?signature=ostree:fedora - here we extend the container image FQIN with a HTTP-like query parameter syntax.  The danger here is a potential future incompatibility with an extension to container image FQIN.

(i.e. we add a shorthand remote-registry for remote-image:...:registry:...)

Did this.  But there's still the open question about other formats.

I do like the shorter ostree-remote-registry, I didn't see ambiguities. Are you maybe thinking of fully dropping ostree-remote-image in favor of that, or there will be consumers needing that?

Are you maybe thinking of fully dropping ostree-remote-image in favor of that, or there will be consumers needing that?

I think we need to support e.g. ostree-remote-image:fedora:oci-archive:/path/to/some.ociarchive and ostree-remote-image:fedora:containers-storage:quay.io/coreos/fedora:stable - i.e. fetching from not-docker-registry sources in the same way skopeo and the https://github.com/containers/image supports.

We should probably also have a shorthand ostree-registry-signed:quay.io/coreos/stable that expands to ostree-image-signed:registry:quay.io/coreos/stable or so.

Also @travier pointed out right now we'll be discarding any container image signatures during pull.  It'd be nicer to have skopeo also spit these out and save them so we can show that (and re-execute the signature verification again).  Alternatively, we can just serialize the data for signature verification and show that (i.e. don't re-execute verification).

:+1: I like this idea and how it's shaping up!

OK, let's roll with this for 0.3 - in rpm-ostree this functionality is still experimental, and I think anyone else using this crate is probably aware that it's still evolving and may change, so a semver bump to 0.4 in the future is likely, and maybe we end up with different strings.
But I'd like to try to stick to this unless there's a decently strong reason to break it.


Fix pubchem namespace

Everywhere you're mentioning pubchem you should really be using pubchem.compound

@cthoyt I'm not sure I understand what you mean.
The namespace is called 'pubchem.compound'? In the graphs its just called 'pubchem', though.

Yes, so in the graphs it should be called pubchem.compound

Ok. I can do that.
But it will take an extra step in the SIDER graph since bio2bel creates it as 'pubchem' not 'pubchem.compound'. I'll have to go over all the nodes and change their namespace, unless you're going to change it in bio2bel as well?

Cray, solved with https://github.com/bio2bel/sider/commit/d1aceaaf5b231197e3a7052ef45d44f7998f1230


Create Households Redux Store

Like the clients, issue #22  needs a separate file to define the Household reducer and related functions.

[ ] Create a new file under store/ducks to define the Household reducer.

[ ] Use clients interface and endpoint since households endpoint is not ready.

[ ] Create a reducer for Households.

[ ] Create selectors to fetch a list of households from the store and also to fetch individual household information by id

[ ] Add actions to add and remove households from store

* Create a new redux store for Households

what xactly will this entail?, since we are going to be working with only the one store.

I meant to say to create a separate file for the reducer of Households under store/ducks folder like the clients.ts. Writing "create a new redux store" does entitle something else. So sorry for the confusion. I am editing the description. Please take a look if there are any other issues!

[ ] Add action creators for Households fetching
[ ] Modify clients dux to store households by Id to separate between other types of clients and families
[ ] Add household specific selectors

This issue is now redundant. An alternative solution to this issue can be resolved with issue #34.


Error 400 when trying to select a portion of code and sending a prompt

unhandled status from server: 400 {"error":{"message":"The requested model is not supported.","param":"model","code":"model_not_supported","type":"invalid_request_error"}}

Copilot Chat Extension Version: v0.17.1
VS Code Version:
OS Version: Windows 11 in remote connection to WSL
Logs:

Steps to Reproduce:

Open a file
Start a chat
Select code
Send any prompt

Can you try restarting your VS Code instance? We did just stop an experiment that was using a temporary model.
If still having issues after restarting please attach your logs via CTRL + SHIFT + U -> Github Copilot Chat

Yes. Restarting vscode now solves the problem. Thank you


Allow searching by the RFC number

Yup, my memory sucks too -- but I think that being able to search by the RFC number (e.g: RFC1034) would be helpful - people keep referring to documents by number, and it's often useful to be able to look them up by that as well. I think: "RFC1034", "RFC 1034" and possibly just "1034" -> "Domain Names - Concepts And Facilities"

Was thinking that too.

Any chance of re-opening this? I tried to create a search engine from the everyRFC search bar, but I'm really sad that it doesn't support search-by-number. It would've been really nice to be able to do that when you don't know the RFC's full name.

The commit made this work; can you give an example where it doesn't?

My mistake, it actually does work. I was looking up a non-existent RFC number.

On the other hand, looking up 3-digit RFCs doesn't work until they are padded with a leading zero. So for instance, "0761" brings up a search result for RFC-761, but "761" does not.
I don't know if the official RFC numbering scheme requires a padding zero or not, but being able to omit it is a pretty nice convenience feature. I'm not sure whether it's worth opening a new issue for this, so I'll just leave this as a comment here.

Makes sense.

(and not at all annoying - thanks!)


Add app release prop

This property is currently tracked in iOS and missed on Android.
This should be added for parity and allow for cross-platform comparisons between builds.

:+1:

closing in favor of https://github.com/mixpanel/mixpanel-android/pull/294, which resolves this for Android as well as iOS


scancodes in command palette

Windows Terminal version
12.3472.0
Windows build number
10.0.22000.376
Other Software
No response
Steps to reproduce
Press ctrl+shift+p
Type "qua"
Notice the "Summon Quake window" shortcut
Expected Behavior
The shortcut text should be "Win + `". I don't know the scancodes by heart.
Actual Behavior
The shortcut text is: win + sc(41).

Huh. This is a good point. We switched that to being bound to a scancode instead of the character, so that it would work on non-en-US layouts the same, but the sc() notation is a little hard to parse.
I wonder if there's a way for us to store the sc internally, but still display the character in the SUI&cmdpal...

you can convert the scancode to a keyname using the win32 API GetKeyNameText() which works but has a somewhat annoying API, here is an example which converts the example in the issue report sc(41) to `:
std::string scan_code_to_string(unsigned int scan_code)
{
    std::vector<char> buffer;
    buffer.resize(64);
    if (!GetKeyNameTextA(
            static_cast<unsigned long>(scan_code) << 16,
            buffer.data(),
            static_cast<int>(buffer.size())))
    {
        throw std::runtime_error{"cannot get key name"};
    }

    return {buffer.data()};
}

When run in a very small hack program I get the following output:

Maybe I can fix this, but I haven't touched the code in quite some while, is this the line where the conversion would need to happen https://github.com/microsoft/terminal/blob/main/src/cascadia/TerminalApp/ActionPaletteItem.cpp#L41?
Maybe something like this? @DHowett
-        item->KeyChordText(senderCommand.KeyChordText());
+        item->KeyChordText(find_and_replace_scancodes(senderCommand.KeyChordText()));

If you point me in the correct direction I can whip up a patch next weekend.

this looks great to me! if it ends up being the wrong place, we can iterate on it together in the PR :)

@DHowett I created a PR, it works on my machine :) not super-happy with the code, but it works.


SASL Authentication failed

Hi,
I cannot connect to MongoDB instance that has authentication enabled in it.
MongoDB version 3.2.6, Debian Wheezy.
Best regards

@vic3lord do you have more details about this? you should be able to pass the credentials in the mongo uri

I have passed the credentials through URI still get the same error

are the credentials in a different db? are you passing authSource in the url? what do you see in the mongodb log?
we need more details to be able to debug what's happening.

I'm sorry, but I don't have that kind of information, I'd love to help out but don't work on it anymore... would love to know the answer for the future though...
Thanks