text:
All the sensors are gone after latest release

I just updated to the latest release, made the changes accordingly to the docs and created the sensors in this way:
- platform: climacell
  api_key: !secret climacell_api
  name: climacell
  latitude: !secret latitude_casa
  longitude: !secret longitude_casa
  monitored_conditions:
    realtime:
      conditions:
        - weather_condition
        - temperature
        - feels_like
        - humidity
        - visibility
        - cloud_cover
        - precipitation
        - precipitation_type
        - pressure
        - wind_speed
        - wind_direction
        - wind_gust
        - moon_phase
        - sunset
        - sunrise
        - pm25
        - pm10
        - o3
        - co
        - so2
        - no2
        - epa_aqi
        - epa_health_concern
        - pollen_tree
        - pollen_weed
        - pollen_grass
        - road_risk_score
#          - road_risk
        - road_risk_confidence
        - road_risk_conditions
        - fire_index
      scan_interval:
        days: 0
        hours: 2
        minutes: 0
        seconds: 0
        milliseconds: 0
      exclude_interval:
        1:
          - "23:30"
          - "06:00"
    daily:
#    forecast_observation: 1
      conditions:
        - weather_condition
        - temperature
        - feels_like
        - humidity
        - visibility
        - precipitation
        - precipitation_probability
        - precipitation_accumulation
        - pressure
        - wind_speed
        - wind_direction
        - sunset
        - sunrise
      scan_interval:
        days: 0
        hours: 2
        minutes: 0
        seconds: 0
        milliseconds: 0
      exclude_interval:
        1:
          - "23:30"
          - "06:00"
    hourly:
#    forecast_observations:
      conditions:
        - weather_condition
        - temperature
        - feels_like
        - humidity
        - visibility
        - cloud_cover
        - precipitation
        - precipitation_probability
        - precipitation_type
        - pressure
        - wind_speed
        - wind_direction
        - wind_gust
        - moon_phase
        - sunset
        - sunrise
        - pm25
        - pm10
        - o3
        - co
        - so2
        - no2
        - epa_aqi
        - epa_health_concern
        - pollen_tree
        - pollen_weed
        - pollen_grass
        - road_risk_score
        - road_risk
        - road_risk_confidence
        - road_risk_conditions
      scan_interval:
        days: 0
        hours: 2
        minutes: 0
        seconds: 0
        milliseconds: 0
      exclude_interval:
        1:
          - "23:30"
          - "06:00"
    nowcast:
#    forecast_observations:
      conditions:
        - weather_condition
        - temperature
        - feels_like
        - humidity
        - visibility
        - cloud_cover
        - precipitation
        - precipitation_type
        - pressure
        - wind_speed
        - wind_direction
        - wind_gust
        - sunset
        - sunrise
        - pm25
        - pm10
        - o3
        - co
        - so2
        - no2
        - epa_aqi
        - epa_health_concern
        - pollen_tree
        - pollen_weed
        - pollen_grass
        - road_risk_confidence
        - road_risk_conditions
      scan_interval:
        days: 0
        hours: 2
        minutes: 0
        seconds: 0
        milliseconds: 0
      exclude_interval:
        1:
          - "23:30"
          - "06:00"
```
But after a restart i have NO sensors created and the HA log doesn't show any errors....
Where i am wrong?

Hi, please put the component log to debug level and post here the details.
# Logging
logger:
  logs:
    custom_components.climacell: debug

Thanks,
Renato

Here it is:
2020-07-02 16:07:34 INFO (MainThread) [custom_components.climacell] __init__ async_setup start for domain climacell.
2020-07-02 16:07:34 INFO (MainThread) [custom_components.climacell] __init__ async_setup done for domain climacell.
2020-07-02 16:07:34 INFO (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'sensor' start for climacell with config OrderedDict([('platform', 'climacell'), ('api_key', '705pJoYnoQZwDj4VXpEannn1bHWX8S8h'), ('name', 'climacell'), ('latitude', 42.0472856), ('longitude', 13.4308795), ('monitored_conditions', OrderedDict([('realtime', OrderedDict([('conditions', ['weather_condition', 'temperature', 'feels_like', 'humidity', 'visibility', 'cloud_cover', 'precipitation', 'precipitation_type', 'pressure', 'wind_speed', 'wind_direction', 'wind_gust', 'moon_phase', 'sunset', 'sunrise', 'pm25', 'pm10', 'o3', 'co', 'so2', 'no2', 'epa_aqi', 'epa_health_concern', 'pollen_tree', 'pollen_weed', 'pollen_grass', 'road_risk_score', 'road_risk_confidence', 'road_risk_conditions', 'fire_index']), ('scan_interval', datetime.timedelta(seconds=7200)), ('exclude_interval', [OrderedDict([(1, ['23:30', '06:00'])])])])), ('daily', OrderedDict([('conditions', ['weather_condition', 'temperature', 'feels_like', 'humidity', 'visibility', 'precipitation', 'precipitation_probability', 'precipitation_accumulation', 'pressure', 'wind_speed', 'wind_direction', 'sunset', 'sunrise']), ('scan_interval', datetime.timedelta(seconds=7200)), ('exclude_interval', [OrderedDict([(1, ['23:30', '06:00'])])])])), ('hourly', OrderedDict([('conditions', ['weather_condition', 'temperature', 'feels_like', 'humidity', 'visibility', 'cloud_cover', 'precipitation', 'precipitation_probability', 'precipitation_type', 'pressure', 'wind_speed', 'wind_direction', 'wind_gust', 'moon_phase', 'sunset', 'sunrise', 'pm25', 'pm10', 'o3', 'co', 'so2', 'no2', 'epa_aqi', 'epa_health_concern', 'pollen_tree', 'pollen_weed', 'pollen_grass', 'road_risk_score', 'road_risk', 'road_risk_confidence', 'road_risk_conditions']), ('scan_interval', datetime.timedelta(seconds=7200)), ('exclude_interval', [OrderedDict([(1, ['23:30', '06:00'])])])])), ('nowcast', OrderedDict([('conditions', ['weather_condition', 'temperature', 'feels_like', 'humidity', 'visibility', 'cloud_cover', 'precipitation', 'precipitation_type', 'pressure', 'wind_speed', 'wind_direction', 'wind_gust', 'sunset', 'sunrise', 'pm25', 'pm10', 'o3', 'co', 'so2', 'no2', 'epa_aqi', 'epa_health_concern', 'pollen_tree', 'pollen_weed', 'pollen_grass', 'road_risk_confidence', 'road_risk_conditions']), ('scan_interval', datetime.timedelta(seconds=7200)), ('exclude_interval', [OrderedDict([(1, ['23:30', '06:00'])])])]))]))]).
2020-07-02 16:07:34 INFO (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'sensor' start for climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime' update: auto.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime' interval: 2:00:00.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime' exceptions: [OrderedDict([(1, ['23:30', '06:00'])])].
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell] ClimacellRealtimeDataProvider initializated for: weather_code,temp,feels_like,humidity,visibility,cloud_cover,precipitation,precipitation_type,baro_pressure,wind_speed,wind_direction,wind_gust,moon_phase,sunset,sunrise,pm25,pm10,o3,co,so2,no2,epa_aqi,epa_health_concern,pollen_tree,pollen_weed,pollen_grass,road_risk_score,road_risk_confidence,road_risk_conditions,fire_index.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime' condition list: weather_code,temp,feels_like,humidity,visibility,cloud_cover,precipitation,precipitation_type,baro_pressure,wind_speed,wind_direction,wind_gust,moon_phase,sunset,sunrise,pm25,pm10,o3,co,so2,no2,epa_aqi,epa_health_concern,pollen_tree,pollen_weed,pollen_grass,road_risk_score,road_risk_confidence,road_risk_conditions,fire_index.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: weather_condition, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: temperature, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: feels_like, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: humidity, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: visibility, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: cloud_cover, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: precipitation, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: precipitation_type, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pressure, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_speed, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_direction, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_gust, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: moon_phase, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: sunset, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: sunrise, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pm25, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pm10, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: o3, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: co, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: so2, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: no2, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: epa_aqi, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: epa_health_concern, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_tree, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_weed, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_grass, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_score, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_confidence, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_conditions, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: fire_index, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'daily' observations: 0:05:00.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'daily' update: auto.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'daily' interval: 2:00:00.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'daily' exceptions: [OrderedDict([(1, ['23:30', '06:00'])])].
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell] ClimacellDailyDataProvider initializated for: [weather_code,temp,feels_like,humidity,visibility,precipitation,precipitation_probability,precipitation_accumulation,baro_pressure,wind_speed,wind_direction,sunset,sunrise] .
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'daily' condition list: weather_code,temp,feels_like,humidity,visibility,precipitation,precipitation_probability,precipitation_accumulation,baro_pressure,wind_speed,wind_direction,sunset,sunrise.

This log is incomplete, please check carefully and put all the rows here.
Thanks,
Renato

I am also having this issue

I quoted all the log entries about the component showed in the HA log.

@In-Orbits please quote also your logs so i can check if i forgot something, but i am sure i quoted all.

Having the same issue after latest update - all sensors show in Dev tools but state for all is unknown.
Could the additional 'conditions' line under each type of monitoring be causing an issue? It worked fine before without this.

Hi, try to use this configuration to test the component and post here the logs if the sensors not works.
## Weather climatecell.co
  - platform: climacell
    api_key: !secret climacell_api_key
    name: example
    latitude: !secret gps_geo_home_lt
    longitude: !secret gps_geo_home_ln
    monitored_conditions:
      realtime:
        conditions:
          - temperature
          - feels_like
          - dewpoint
          - humidity
          - wind_speed
          - wind_direction
          - wind_gust
          - pressure
          - precipitation
          - precipitation_type
          - sunset
          - sunrise
          - visibility
          - cloud_cover
          - cloud_base
          - cloud_ceiling
          - surface_shortwave_radiation
          - moon_phase
          - weather_condition
          - pm25
          - pm10
          - o3
          - no2
          - co
          - so2
          - epa_aqi
          - epa_primary_pollutant
          - epa_health_concern
          - pollen_tree
          - pollen_weed
          - pollen_grass
          - road_risk_score
          - road_risk_confidence
          - road_risk_conditions
          - fire_index
        update: auto
        scan_interval:
          # At least one of these must be specified:
          days: 0
          hours: 0
          minutes: 30
          seconds: 0
          milliseconds: 0

In your logs you should find some rows like this:
2020-07-03 09:13:17 DEBUG (SyncWorker_9) [custom_components.climacell] _retrieve_data response.text: {"lat":yyyyy,"lon":xxxxx,"temp":{"value":23.31,"units":"C"},"feels_like":{"value":23.31,"units":"C"},"wind_speed":{"value":1.38,"units":"m/s"},"wind_gust":{"value":3.25,"units":"m/s"},"baro_pressure":{"value":1011.125,"units":"hPa"},"visibility":{"value":10,"units":"km"},"humidity":{"value":88.63,"units":"%"},"wind_direction":{"value":303.88,"units":"degrees"},"precipitation":{"value":0,"units":"mm/hr"},"precipitation_type":{"value":"none"},"cloud_cover":{"value":0,"units":"%"},"fire_index":{"value":2.125},"sunrise":{"value":"2020-07-03T03:40:50.374Z"},"sunset":{"value":"2020-07-03T18:47:59.501Z"},"moon_phase":{"value":"waxing_gibbous"},"weather_code":{"value":"clear"},"epa_aqi":{"value":29.8125},"pm25":{"value":9.25,"units":"µg/m3"},"pm10":{"value":26.625,"units":"µg/m3"},"o3":{"value":17.875,"units":"ppb"},"no2":{"value":5.3125,"units":"ppb"},"co":{"value":0.875,"units":"ppm"},"so2":{"value":3.625,"units":"ppb"},"epa_health_concern":{"value":"Good"},"pollen_tree":{"value":null,"units":"Climacell Pollen Index"},"pollen_weed":{"value":null,"units":"Climacell Pollen Index"},"pollen_grass":{"value":0,"units":"Climacell Pollen Index"},"observation_time":{"value":"2020-07-03T07:13:17.548Z"}}

@r-renato I have no entries like those in my log as none sensor is created....

and no ERROR? ummm that's bizarre.
the following rows show the sensors creation. did you check if you see them under Developer Tools -> States menu?
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: weather_condition, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: temperature, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: feels_like, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: humidity, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: visibility, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: cloud_cover, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: precipitation, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: precipitation_type, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pressure, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_speed, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_direction, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: wind_gust, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: moon_phase, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: sunset, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: sunrise, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pm25, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pm10, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: o3, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: co, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: so2, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: no2, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: epa_aqi, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: epa_health_concern, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_tree, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_weed, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: pollen_grass, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_score, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_confidence, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: road_risk_conditions, climacell.
2020-07-02 16:07:34 DEBUG (SyncWorker_7) [custom_components.climacell.sensor] __init__ setup_platform 'realtime', add sensor fo condition: fire_index, climacell.

No, i see no sensor under Developer Tools -> States menu

Only one that is not related to the eventually created sensor by climacell custom component.

Try to use cc_ as filter.

No way....

I see a climacell.climacell_weather inside services... which is his purpose?

I tried to put off from the sensors configuration daily, hourly and nowcast, leaving only realtime and the sensors are there again. SO definitely there are problems with daily, hourly and nowcast sensors...

I double checked, re-added daily sensors and the sensors are gone again......

Please post your logs and configuration.
Thanks,
Renato

I already posted the config in the opening post of this issue and also the logs. No new from there. Now i put off from the sensors config all what is related to daily, hourly and nowcast leaving only realtime. This is the screenshot i have now:

Puoi farmi vedere la configurazione di questa scheda?
Renato

          - type: custom:ha-card-weather-conditions
            style: |
              ha-card {
                font-size: 14px;
                font-family: 'Georgia';
                font-weight: normal;
                background: none; border-radius: 0px; box-shadow: none;
              }
              .icon.bigger {
                width: 10em;
                height: 10em;
                margin-top: -4em;
                position: absolute;
                left: 0em;
              }
              .title {
                position: absolute;
                left: calc(140px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                top: 0.6em;
                font-weight: 300;
                font-size: calc(14px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
              }
              .moon {
                position: absolute;
                left: calc(115px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                top: calc(63px - (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                font-weight: 300;
                font-size: calc(14px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
                line-height:20px;
                display: inline-block;
              }
              .temp {
                position: absolute;
                // top: 0.65em;
                font-weight: 300;
                font-size: calc(49px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
                right: 1em;
                margin-top: 2px;
              }
              .tempc {
                position: absolute;
                font-weight: 300;
                font-size: calc(12px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                // font-size: 1.5em;
                vertical-align: super;
                color: var(--primary-text-color);
                right: 1em;
                margin-top: -11px;
                margin-right: 7px;
              }
            name: 'Meteo Avezzano'
            language: it
            animation: true
            camera: camera.immagini_radar_infrarossi
            uv:
              protection_window: binary_sensor.protection_window
              ozone_level: sensor.current_ozone_level
              uv_index: sensor.current_uv_index
              uv_level: sensor.current_uv_level
              max_uv_index: sensor.max_uv_index
              set_skin_type_1: sensor.skin_type_1_safe_exposure_time
              set_skin_type_2: sensor.skin_type_2_safe_exposure_time
              set_skin_type_3: sensor.skin_type_3_safe_exposure_time
              set_skin_type_4: sensor.skin_type_4_safe_exposure_time
              set_skin_type_5: sensor.skin_type_5_safe_exposure_time
              set_skin_type_6: sensor.skin_type_6_safe_exposure_time
            pollen:
              tree:
                entity: sensor.cc_climacell_pollen_tree
                min: 0
                max: 5
                low: 1
                high: 3
              weed:
                entity: sensor.cc_climacell_pollen_weed
                min: 0
                max: 5
                low: 1
                high: 3
              grass:
                entity: sensor.cc_climacell_pollen_grass
                min: 0
                max: 5
                low: 1
                high: 3
              fire_index:
                entity: sensor.cc_climacell_fire_index
                min: 0
                max: 5
                low: 1
                high: 3
            air_quality:
              pm25: sensor.cc_climacell_pm25
              pm10: sensor.cc_climacell_pm10
              o3: sensor.cc_climacell_o3
              co: sensor.cc_climacell_co
              epa_aqi: sensor.cc_climacell_epa_aqi
              epa_health_concern: sensor.cc_climacell_epa_health_concern
#              epa_primary_pollutant: sensor.climacell_epa_primary_pollutant
              no2: sensor.cc_climacell_no2
              so2: sensor.cc_climacell_so2
            alert:
              fire_risk:
                entity: sensor.cc_climacell_fire_index
                icon: mdi:campfire
                min: 1
                max: 100
                show_if_ge: 1
              thunderstorms_risk:
                entity: binary_sensor.dpc_avezzano_temporali_oggi
#                show_if_on: false
              hydraulic_risk:
                entity: binary_sensor.dpc_avezzano_idraulico_oggi
              hydrogeological_risk:
                entity: binary_sensor.dpc_avezzano_idrogeologico_oggi
            weather:
              icons_model: climacell
              current:
                sun: sun.sun
                moon_phase: sensor.cc_climacell_moon_phase
                current_conditions: sensor.cc_climacell_weather_condition
                humidity: sensor.cc_climacell_humidity_percentage
                pressure: sensor.cc_climacell_barometric_pressure
                temperature: sensor.cc_climacell_temperature
                visibility: sensor.cc_climacell_visibility
                wind_bearing: sensor.cc_climacell_wind_direction
                wind_speed: sensor.cc_climacell_wind_speed
                precipitation: cc_sensor.climacell_precipitation
                feels_like: sensor.cc_climacell_feels_like
                forecast: true
              forecast:
                meteogram: camera.climacell_meoteogram
                icons:
                  day_1: sensor.cc_climacell_weather_condition_0d
                  day_2: sensor.cc_climacell_weather_condition_1d
                  day_3: sensor.cc_climacell_weather_condition_2d
                  day_4: sensor.cc_climacell_weather_condition_3d
                  day_5: sensor.cc_climacell_weather_condition_4d
                temperature_high:
                  day_1: sensor.cc_climacell_max_temperature_0d
                  day_2: sensor.cc_climacell_max_temperature_1d
                  day_3: sensor.cc_climacell_max_temperature_2d
                  day_4: sensor.cc_climacell_max_temperature_3d
                  day_5: sensor.cc_climacell_max_temperature_4d
                temperature_low:
                  day_1: sensor.cc_climacell_min_temperature_0d
                  day_2: sensor.cc_climacell_min_temperature_1d
                  day_3: sensor.cc_climacell_min_temperature_2d
                  day_4: sensor.cc_climacell_min_temperature_3d
                  day_5: sensor.cc_climacell_min_temperature_4d
                precipitation_probability:
                  day_1: sensor.cc_climacell_precipitation_probability_0d
                  day_2: sensor.cc_climacell_precipitation_probability_1d
                  day_3: sensor.cc_climacell_precipitation_probability_2d
                  day_4: sensor.cc_climacell_precipitation_probability_3d
                  day_5: sensor.cc_climacell_precipitation_probability_4d
                precipitation_intensity:
                  day_1: sensor.cc_climacell_max_precipitation_0d
                  day_2: sensor.cc_climacell_max_precipitation_1d
                  day_3: sensor.cc_climacell_max_precipitation_2d
                  day_4: sensor.cc_climacell_max_precipitation_3d
                  day_5: sensor.cc_climacell_max_precipitation_4d

Te lo avevo già chiesto, ma senza risposta: come si fa ad avere i sensori dell'object 'sea'?

I nomi di alcuni sensori sono cambiati cc_climacell_max_precipitation_0d cc_climacell_precipitation_max_0d e via dicendo per quelli che hanno min e max, inoltre i sensori con le date partono da 1d e non più da 0d.
Per i sensori del layer sea io ho utilizzato un componente che ho sviluppato ma non ho ancora messo su hacs. In questo periodo ho parecchie attività che mi portano a finire di lavorare tardi e non sono riuscito a seguire gli hobby. Porta pazienza appena posso lo registro.
Grazie, ciao.
Renato

Ok, ma io non ho quei sensori... non sono stati creati probabilmente perchè non ho i sensori daily ed hourly....

Provo e riprovo, ma i sensori vengono creati solo se in sensor: metto solo realtime. E in questo caso non ho neanche i sensori del forecast!

I sensori sono corretti così, prova. ;)
- type: custom:ha-card-weather-conditions
            style: |
              ha-card {
                font-size: 14px;
                font-family: 'Georgia';
                font-weight: normal;
                background: none; border-radius: 0px; box-shadow: none;
              }
              .icon.bigger {
                width: 10em;
                height: 10em;
                margin-top: -4em;
                position: absolute;
                left: 0em;
              }
              .title {
                position: absolute;
                left: calc(140px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                top: 0.6em;
                font-weight: 300;
                font-size: calc(14px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
              }
              .moon {
                position: absolute;
                left: calc(115px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                top: calc(63px - (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                font-weight: 300;
                font-size: calc(14px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
                line-height:20px;
                display: inline-block;
              }
              .temp {
                position: absolute;
                // top: 0.65em;
                font-weight: 300;
                font-size: calc(49px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                color: var(--primary-text-color);
                right: 1em;
                margin-top: 2px;
              }
              .tempc {
                position: absolute;
                font-weight: 300;
                font-size: calc(12px + (26 - 14) * ((100vw - 300px) / (1600 - 300)));
                // font-size: 1.5em;
                vertical-align: super;
                color: var(--primary-text-color);
                right: 1em;
                margin-top: -11px;
                margin-right: 7px;
              }
            name: 'Meteo Avezzano'
            language: it
            animation: true
            camera: camera.immagini_radar_infrarossi
            uv:
              protection_window: binary_sensor.protection_window
              ozone_level: sensor.current_ozone_level
              uv_index: sensor.current_uv_index
              uv_level: sensor.current_uv_level
              max_uv_index: sensor.max_uv_index
              set_skin_type_1: sensor.skin_type_1_safe_exposure_time
              set_skin_type_2: sensor.skin_type_2_safe_exposure_time
              set_skin_type_3: sensor.skin_type_3_safe_exposure_time
              set_skin_type_4: sensor.skin_type_4_safe_exposure_time
              set_skin_type_5: sensor.skin_type_5_safe_exposure_time
              set_skin_type_6: sensor.skin_type_6_safe_exposure_time
            pollen:
              tree:
                entity: sensor.cc_climacell_pollen_tree
                min: 0
                max: 5
                low: 1
                high: 3
              weed:
                entity: sensor.cc_climacell_pollen_weed
                min: 0
                max: 5
                low: 1
                high: 3
              grass:
                entity: sensor.cc_climacell_pollen_grass
                min: 0
                max: 5
                low: 1
                high: 3
              fire_index:
                entity: sensor.cc_climacell_fire_index
                min: 0
                max: 5
                low: 1
                high: 3
            air_quality:
              pm25: sensor.cc_climacell_pm25
              pm10: sensor.cc_climacell_pm10
              o3: sensor.cc_climacell_o3
              co: sensor.cc_climacell_co
              epa_aqi: sensor.cc_climacell_epa_aqi
              epa_health_concern: sensor.cc_climacell_epa_health_concern
#              epa_primary_pollutant: sensor.climacell_epa_primary_pollutant
              no2: sensor.cc_climacell_no2
              so2: sensor.cc_climacell_so2
            alert:
              fire_risk:
                entity: sensor.cc_climacell_fire_index
                icon: mdi:campfire
                min: 1
                max: 100
                show_if_ge: 1
              thunderstorms_risk:
                entity: binary_sensor.dpc_avezzano_temporali_oggi
#                show_if_on: false
              hydraulic_risk:
                entity: binary_sensor.dpc_avezzano_idraulico_oggi
              hydrogeological_risk:
                entity: binary_sensor.dpc_avezzano_idrogeologico_oggi
            weather:
              icons_model: climacell
              current:
                sun: sun.sun
                moon_phase: sensor.cc_climacell_moon_phase
                current_conditions: sensor.cc_climacell_weather_condition
                humidity: sensor.cc_climacell_humidity_percentage
                pressure: sensor.cc_climacell_barometric_pressure
                temperature: sensor.cc_climacell_temperature
                visibility: sensor.cc_climacell_visibility
                wind_bearing: sensor.cc_climacell_wind_direction
                wind_speed: sensor.cc_climacell_wind_speed
                precipitation: cc_sensor.climacell_precipitation
                feels_like: sensor.cc_climacell_feels_like
                forecast: true
              forecast:
                meteogram: camera.climacell_meoteogram
                icons:
                  day_1: sensor.cc_climacell_weather_condition_1d
                  day_2: sensor.cc_climacell_weather_condition_2d
                  day_3: sensor.cc_climacell_weather_condition_3d
                  day_4: sensor.cc_climacell_weather_condition_4d
                  day_5: sensor.cc_climacell_weather_condition_5d
                temperature_high:
                  day_1: sensor.cc_climacell_temperature_max_1d
                  day_2: sensor.cc_climacell_temperature_max_2d
                  day_3: sensor.cc_climacell_temperature_max_3d
                  day_4: sensor.cc_climacell_temperature_max_4d
                  day_5: sensor.cc_climacell_temperature_max_5d
                temperature_low:
                  day_1: sensor.cc_climacell_temperature_min_1d
                  day_2: sensor.cc_climacell_temperature_min_2d
                  day_3: sensor.cc_climacell_temperature_min_3d
                  day_4: sensor.cc_climacell_temperature_min_4d
                  day_5: sensor.cc_climacell_temperature_min_5d
                precipitation_probability:
                  day_1: sensor.cc_climacell_precipitation_probability_1d
                  day_2: sensor.cc_climacell_precipitation_probability_2d
                  day_3: sensor.cc_climacell_precipitation_probability_3d
                  day_4: sensor.cc_climacell_precipitation_probability_4d
                  day_5: sensor.cc_climacell_precipitation_probability_5d
                precipitation_intensity:
                  day_1: sensor.cc_climacell_precipitation_max_1d
                  day_2: sensor.cc_climacell_precipitation_max_2d
                  day_3: sensor.cc_climacell_precipitation_max_3d
                  day_4: sensor.cc_climacell_precipitation_max_4d
                  day_5: sensor.cc_climacell_precipitation_max_5d

No, mi spiace, ma forse non sono riuscito a farmi capire. I sensori del forecast NON vengono creati dal component.
Gli unici sensori creati sono questi:

Come vedi non ci sono sensori per il forecast.
Se controlli la configurazione dei sensori nel mio primo post vedrai che ho inserito tutto correttamente (sia realtime che daily, hourly e nowcast) ma se li metto tutti e tre NESSUN sensore viene creato mentre se uso solo realtime ho i sensori sopra mostrati.

Ok finally good news !!!!
Sono finalmente riuscito ad ottenere tutti i sensori inserendo sempre (anche se i docs dicono sia opzionale) forecast_observations. Ora potresti spiegarmi come utilizzare in forecast anche gli altri dati disponibili come visibilità, copertura nuvole, rischio stradale etc.? Basta creare un'altra card ? Hai degli esempi?
Comunque grande lavoro!!!

how about realtime conditions , i couldn't make it work

how about realtime conditions , i couldn't make it work

Here it is my config about realtime:
  monitored_conditions:
    realtime:
      conditions:
        - weather_condition
        - temperature
        - feels_like
        - humidity
        - visibility
        - cloud_cover
        - cloud_base
        - cloud_ceiling
        - surface_shortwave_radiation
        - precipitation
        - precipitation_type
        - pressure
        - wind_speed
        - wind_direction
        - wind_gust
        - moon_phase
        - sunset
        - sunrise
        - pm25
        - pm10
        - o3
        - co
        - so2
        - no2
        - epa_aqi
        - epa_health_concern
        - pollen_tree
        - pollen_weed
        - pollen_grass
        - road_risk_score
        - road_risk_confidence
        - road_risk_conditions
        - fire_index
      update: auto
      scan_interval:
        days: 0
        hours: 2
        minutes: 0
        seconds: 0
        milliseconds: 0
      exclude_interval:
        1:
          - "23:30"
          - "06:00"

Hi There, My issue is solved. not sure how but all my sensors got renamed with cc_cc_ prefixes on them. Thanks

On my side, after updating to the latest release i have many sensors doubled with _2 added to them and, more, almost all sensors are unavailable.
What happened????

let me see, put here the component logs.
the latest releases contain only a small bug fix for FORECAST_OBSERVATIONS.

After a restart the sensors are here again, but why i have doubled some sensors?

Hi, can you check again with the new release?
Thanks,
Renato

Now back to the old names... can you tell me which is the difference between precipitation_max and precipitation_accumulation? Which one to use in forecast ?

repo: r-renato/ha-climacell-weather


text:
Starship High altitude flight tests

Hi, awesome API !!! Is any option how add Starship SN HOP tests to Launches category or adding new category as Events. Only my idea, thank you very much for your really hard work, love this API...

Same here, I wish I could add a parameter to the 'upcoming launches' URL to also have it list SN tests/hops as well as normal SpaceX rocket launches

Not currently, but Launch Library v2 does track these
For example, https://ll.thespacedevs.com/2.2.0/launch/73ae8553-cc90-46e9-9a01-70a712493856/?format=json

source: gharchive/issue

authors: ChopsKingsland RoyalCrown jakewmeyer

repo: r-spacex/SpaceX-API

license_type: permissive

license_source: bigquery


text:
update default build-tools version from 29.0.3 to 33.0.0

Due to the default build-tools version 29.0.3 becoming somewhat old, builds started failing with the latest runner images like `ubuntu-latest.
ps: This PR updates to 33.0.0 and not to 34.0.0 for backward compatibility reasons with some old runner versions

Please merge this @r0adkll Also failed my build today :/

Please merge this @r0adkll Also failed my build today :/

Hi @leonlatsch, you can set the version manually on your code until this pr is merged. I have resolved this issue by setting version manually.

Please merge this @r0adkll Also failed my build today :/

Hi @leonlatsch, you can set the version manually on your code until this pr is merged. I have resolved this issue by setting version manually.

Yes, I did that too. Just wanted to let the author know that this is needed

source: gharchive/pull-request

authors: bhargav-buku hamz4k leonlatsch

license: MIT

license_source: github-api


text:
Optional Codec for GEOMETRY

Optional Codec for type GEOMETRY  based on existence of org.locationtech.jts.geom.Geometry in Classpath

@gmullerb Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Overall, I'm pleased with this PR. @gmullerb have you not been able to sign the CLA? We need it to move forward. Tnx.

@gmullerb, May I remind you we need your signature on the CLA.

Related discussion on our mailing list: https://groups.google.com/forum/#!topic/r2dbc/68aDbnAHDuw
We should also document somewhere that Geometry support is an extension and subject to change as soon as we decide how to proceed on R2DBC SPI level wit Geo support.

@gmullerb Thank you for signing the Contributor License Agreement!

Completed with only minor polishing and documentation.
Thanks @gmullerb!

My Pleasure!

authors: gmullerb gregturn mp911de pivotal-issuemaster


text:
🛑 Home Assistant is down

In e37d047, Home Assistant ($SECRET_SITE_HA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Home Assistant is back up in 38ae70f.


text:
🛑 Pet Project is down

In 7127b22, Pet Project ($RINFO_SITE) was down:

HTTP code: 504
Response time: 10503 ms

Resolved: Pet Project is back up in 4da1bd5.


text:
🛑 Pet Project is down

In 1a7408f, Pet Project ($RINFO_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pet Project is back up in 5a6b56d.


text:
Pin keystone client version

Also fixes deprecated oslo. namespace

:+1:

Thanks for the oslo_config fix! :+1:

authors: BenjamenMeyer TheSriram isaacm

repo: racker/eom


text:
(Improvement) Incorporate Cross Browser Testing

So it looks like we qualify for a free OSS license from Sauce Labs.
What this offers us:
Being able to run javascript tests in multiple browsers https://saucelabs.com/products/javascript-unit-testing
Unlimited UI automation with up to 5 concurrent VM's in pretty much any browser we want:
https://saucelabs.com/platforms
We also get as much manual testing as we want for 10 minute sessions per use(after 10 minutes it kills the session and you can just start another one right away)
We could create some simplistic UI tests in something like nightwatch.js and have them run with the travis.ci and sauce labs integrations https://docs.travis-ci.com/user/sauce-connect/
This could allow us to automate visual regression testing by recording screenshots and videos by having sauce labs show us how UI elements look and perform in multiple browsers and possibly catch errors so were aware of them early.
This could make canon-react more useful when developers are able to see how it looks and performs in multiple browsers even if they dont have them installed or available locally(looking at you windows, mobile browsers etc...)
To clarify this is free for testing work on canon-react itself(and not private rax projects) but if you ever have some kind of edge case you can reproduce in canon-react by uploading a static page somewhere public to test manually or via automation then we should be good to go.

To clarify this issue is to just spike and see if sauce labs could be useful to us, also if you ever wanted to experiment with it this would be a good chance.

repo: rackerlabs/canon-react

license: mit


text:
Add optional prop to display additional content on the FormPopover footer

This PR adds a new prop to the FormPopover component in order to allow developers to display additional content after the control buttons/links (e.g. submit and cancel).
Problem
I have a submittable popover component using the FormPopover component and I need to display a right-aligned tooltip on the footer. There is no appropriate way to use a FormPopover and display additional content after the control buttons. The only thing similar is the additionalControls prop, but it is rendered before the cancel component.
Questions

Do you think the new prop name (additionalInfo) is a good one?

Tasks

[x] Add support for new prop in FormPopover
[x] Implement demo
[x] Update changelog

Screenshot of a submittable popover displaying an additional status indicator

A few things I am wondering about - the demo seems to be very contrived and offers little insight into why you would use this feature. Do you think that passing in a tooltip trigger with the tooltip itself indicating 'Optional additionalControlsContent' would be any clearer? Also, maybe additionalControlsContent for the name, as it indicates where the additional info is going to go. Lastly, is this a common enough pattern to warrant putting it into Canon-React? I haven't seen tooltips in footers anywhere... I'm not 100% opposed to it, I just worry about prematurely optimizing.

we often have pricing tooltips in footers, don't we?

@adampickeral Snap, that's right! Those are typically right aligned, yeah?

@hannahstwinter, thanks for sharing your thoughts.
I agree the demo can be improved. I went on the same route as the other additionalControls prop and tried to keep them similar. Any suggestions?

Do you think that passing in a tooltip trigger with the tooltip itself indicating 'Optional additionalControlsContent' would be any clearer?

My problem is strictly related to displaying tooltips on the footer, but I tried to keep names less specific. I think your suggestion of additionalControlsContent is a good one!

is this a common enough pattern to warrant putting it into Canon-React?

I found a couple places with pricing tooltips as Adam said. One of them even duplicate the same behaviour as the FormPopover and implements a tooltip prop. My motivation was to keep things simple and perhaps reuse this feature in the future for refactorings or just for new popovers with pricing tooltips.

I can definitely see having this in Canon-React - for some reason I had forgotten entirely about pricing tooltips. That said, as I mentioned above, I'm pretty sure those are right aligned - is that something that we would want to enforce here? If not, there would need to be a custom rule/custom style on the element every time it is used for that application. I wonder about exposing that as a toggle-able feature... That would be too much, yeah? I'm not sure what the best approach on that one is...
I agree that the demo could accidentally imply that the extra content should be a tooltip... What about tooltip underlined text - Opt. Addl Controls Content - and have the tooltip explain that the extra content can be anything? Yay for using existing features to make your demos more robust, eh? 😄

I'm pretty sure those are right aligned - is that something that we would want to enforce here?

I kept asking myself if the popover should be more helpful for the "90%" use case (i.e. display something right aligned). You're right, the application would need at least a global CSS rule to push that extra content to the right. It's flexible, but not so convenient. btw, Flexbox would be handy here 😄. I'm not sure if Canon has recommendations for this kind of trade-off; that'd help.
I'm going to implement your suggestion for the demo with the tooltip.

I feel like additionalInfo is a bit of a strange name. Could it be something like additionalFooterContent?

once you have finished with code changes, please squash everything into a single commit.
also remove the changes to the changelog, that happens during the release process

I'll make the changes @adampickeral. btw, I just searched in the repo and docs and there is no clear mention or explanation for the squash practice but I've seen a reminder on almost every PR. Is this something we should improve on the Contributing documentation (not in this PR of course)?
I found this bullet-point in the docs:

Intermediate and work-in-progress commits should be rebased out

we can update the contributing guidelines. i do consider all the commits in here to be intermediate ones though that are either addressing code review changes or are really just parts of the whole feature

LGTM

authors: adampickeral hannahstwinter ilmotta willcumbie


text:
I tried to goto /xyz path but api call from / path is getting called. why is this ?

  <Route path="/" component={Mail}>
    <Route path="mail/:id" component={MailID} />
    <Route path="calendar" component={calendar}/>
    <Route path="request" component={request} />
  </Route>

I tried to goto directly  /request  but in network tab I saw  api from Mail component is getting called. How is  / path api getting called is it because I put api call in componentWillMount ???

is it because I put api call in componentWillMount?

That seems most likely. Going to /request will render Mail along with the request component, which will indeed result in Mail's componentWillMount being called. If you only want it to happen when / is the route, make a component to use with DefaultRoute instead and put your API call there.

authors: TonyFrancis jabjab

repo: rackt/react-router


text:
react-router not working, and component not found in Route and IndexRoute

I'm using react-router 2.0.0-rc5, and react 0.14.6
my Route config is:
import React from 'react';
import ReactDOM from 'react-dom';
import { Router, Route, IndexRoute, browserHistory } from 'react-router';

...

ReactDOM.render(<Router history={browserHistory}>
    <Route path="/" component={BasicLayout}>
        <IndexRoute component={HomeIndex} />
        <Route path="music" component={MusicIndex}>
            <IndexRoute component={MusicList}/>
            <Route path=":id" component={MusicPlayer}/>
        </Route>
        <Route path="photos" component={PhotoIndex}>
            <IndexRoute component={PhotoList}/>
            <Route path=":album" component={AlbumViewer}>
                <IndexRoute component={DefaultPhotoView}/>
                <Route path=":id" component={PhotoView}/>
            </Route>
        </Route>
    </Route>
    <Route path="/welcome" component={WelcomeIndex}/>
</Router>, document.getElementById('app'))

When I use webpack dev-server, and open localhost:8080, then got:

If I replace 'component' with 'handler', then no warnings, but nothings inside the RouterContext:

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Could you post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.

authors: karfield taion


text:
Figure out how to get errors reliably from r2.cmd(j)

We talked briefly about this here
Unfortunately, option 2 has a few pitfalls:

Lost ANSI coloring
doesn't work in some cases, example axt @ jksdhfdskjf 2>foo prints ERROR: Invalid command 'axt @ klasjdlkasjd' (0x61) but not in the foo file

Option 1 only works in some of the r2langs
Can you help me understand this issue and why it'd be hard to do it for, say r2lang-python? It's a pretty big issue for auto-mode.

Ok did some thoughs about this long standing issue and finally implemented r2pipe2 in r2. Check the new { command which takes cmd as a json object and returns a json with the output, error code , return value and log messages associated.
The next step will be to try every single command (about 8000) and ensure the return code and errors are consistent with what’s expected. Which is not good it is right now but it was about the time to tackle this

Amazing! This looks great so far!!
Getting some random segfaults, though
[0x00001c10]> {"cmd": "aaa" }
{"res":"","error":false,"value":0,"code":0,"logs":[{"type":"WARN","origin":"logline","message":"Analyze all flags starting with sym. and entry0 (aa)"}{"type":"WARN","origin":"logline","message":"Analyze imports (af@@@i)"}{"type":"WARN","origin":"logline","message":"Analyze entrypoint (af@ entry0)"}{"type":"WARN","origin":"logline","message":"Analyze symbols (af@@@s)"}{"type":"WARN","origin":"logline","message":"Recovering variables"}{"type":"WARN","origin":"logline","message":"Analyze all functions arguments/locals (afva@@@F)"}{"type":"WARN","origin":"logline","message":"Analyze function calls (aac)"}{"type":"WARN","origin":"logline","message":"Analyze len bytes of instructions for references (aar)"}{"type":"WARN","origin":"logline","message":"Finding and parsing C++ vtables (avrr)"}{"type":"WARN","origin":"logline","message":"Analyzing methods"}{"type":"WARN","origin":"logline","message":"Recovering local variables (afva)"}{"type":"WARN","origin":"logline","message":"Type matching analysis for all functions (aaft)"}{"type":"WARN","origin":"logline","message":"Propagate noreturn information (aanr)"}{"type":"WARN","origin":"cmd_anal_all","message":"Use -AA or aaaa to perform additional experimental analysis"}],"code":0}
[0x00001c10]> {"cmd": "aaaa" }
{"res":"","error":false,"value":0,"code":0,"logs":[{"type":"WARN","origin":"logline","message":"Analyze all flags starting with sym. and entry0 (aa)"}{"type":"WARN","origin":"logline","message":"Analyze imports (af@@@i)"}{"type":"WARN","origin":"logline","message":"Analyze entrypoint (af@ entry0)"}{"type":"WARN","origin":"logline","message":"Analyze symbols (af@@@s)"}{"type":"WARN","origin":"logline","message":"Recovering variables"}{"type":"WARN","origin":"logline","message":"Analyze all functions arguments/locals (afva@@@F)"}{"type":"WARN","origin":"logline","message":"Analyze function calls (aac)"}{"type":"WARN","origin":"logline","message":"Analyze len bytes of instructions for references (aar)"}{"type":"WARN","origin":"logline","message":"Finding and parsing C++ vtables (avrr)"}{"type":"WARN","origin":"logline","message":"Analyzing methods"}{"type":"WARN","origin":"logline","message":"Recovering local variables (afva)"}{"type":"WARN","origin":"logline","message":"Type matching analysis for all functions (aaft)"}{"type":"WARN","origin":"logline","message":"Propagate noreturn information (aanr)"}{"type":"WARN","origin":"logline","message":"Scanning for strings constructed in code (/azs)"}{"type":"WARN","origin":"logline","message":"Finding function preludes (aap)"}{"type":"WARN","origin":"logline","message":"Enable anal.types.constraint for experimental type propagation"}],"code":0}
[0x00001c10]> { "cmd": "aaaa" }
{"res":"","error":false,"value":0,"code":0,"logs":[{"type":"WARN","origin":"logline","message":"Analyze all flags starting with sym. and entry0 (aa)"}{"type":"WARN","origin":"logline","message":"Analyze imports (af@@@i)"}{"type":"WARN","origin":"logline","message":"Analyze entrypoint (af@ entry0)"}{"type":"WARN","origin":"logline","message":"Analyze symbols (af@@@s)"}{"type":"WARN","origin":"logline","message":"Recovering variables"}{"type":"WARN","origin":"logline","message":"Analyze all functions arguments/locals (afva@@@F)"}{"type":"WARN","origin":"logline","message":"Analyze function calls (aac)"}{"type":"WARN","origin":"logline","message":"Analyze len bytes of instructions for references (aar)"}{"type":"WARN","origin":"logline","message":"Finding and parsing C++ vtables (avrr)"}{"type":"WARN","origin":"logline","message":"Analyzing methods"}{"type":"WARN","origin":"logline","message":"Recovering local variables (afva)"}{"type":"WARN","origin":"logline","message":"Type matching analysis for all functions (aaft)"}{"type":"WARN","origin":"logline","message":"Propagate noreturn information (aanr)"}{"type":"WARN","origin":"logline","message":"Scanning for strings constructed in code (/azs)"}{"type":"WARN","origin":"logline","message":"Finding function preludes (aap)"}{"type":"WARN","origin":"logline","message":"Enable anal.types.constraint for experimental type propagation"}],"code":0}
[0x00001c10]> { "cmd": "aaaa" }
[1]    4832 segmentation fault  r2 -A -i r2ai/main.py ~/Downloads/svchost.exe

should bef ixed in https://github.com/radareorg/radare2/pull/22975 . thanks for reporting!

works great with that patch!
in the future, should i open issues in radare2 for anything else i find related to this or do you prefer I keep here?

authors: dnakov trufae


text:
Build website with Jekyll

This depends on #433 getting merged first.

Removes unused image, JS, and CSS assets
Replaces Slick (the image carousel) with an updated version on a CDN (mainly for https support)
Optimizes image assets to reduce bandwidth
Adds Jekyll with templated release notes, homepage, and appcast (for app updates)
Integrates with automated Travis builds

@radiant-player/radiant-player-mac this is ready for review

If you'd like to test this, try running ./scripts/build-website.sh then cd website/_site and check out the results.

Just a thought - as this is triggered by Travis, does this mean it'll automatically deploy after any commit to master?

Yes, that is correct and is by design.  For the website, any commit to master will sync gh-pages with the website.  It is limited to the master branch, so other branches won't go to gh-pages.  I think this is the behavior we want for the website.
For automatically building the app itself, that will have some different logic (based on tags, so that when we tag 1.2.3 it will build and deploy 1.2.3, but only on that specific commit).

Seems to be a merge conflict in index.html.  Let me know when that's sorted and I'll check it out.
And don't forget to port over the PR from last night as I think it's included in the "old" section ;-)

Okay, merge conflicts are resolved and this should be good to go

Yo - haven't forgotten. Just getting a ./scripts/build-website.sh: line 5: bundle: command not found error, which I'm guessing is something to do with not having the right gems installed, maybe.
Trying to work it out now. If it is specific ruby gems that need installing, will these need specifying in the travis config?

Bundler is assumed to exist already (it's commonly installed with ruby) and is preinstalled on Travis.  On your local machine, you can gem install bundler to grab a copy.

Oh, and once you have bundler installed, you run bundle install to install the other dependencies.  Anyways, again this is something Travis does automatically.

Spent the past 2 minutes trying to work out what that notification sound was - turns out it was GitHub telling me you'd replied. This is what happens when I don't have music playing :anguished:
OK, will try that and report back shortly!

Oh and I went through the changelog - nice one logging the ticket. I'll push that up too when I'm done with this.

I just rebased this - you may need to re-pull

Will do :+1:

I have a favicon.ico file to contribute once this PR is merged. :)

Only issue with the build process was @options[:href_ignore] will be renamed in a future 3.x.x release: http://git.io/vGHHy` -- not sure if that's a Jekyll thing though
Aside from that, seems to be looking good. Though I'm making a mental note to rewrite that carousel to be pure CSS - the performance of that slick slider is awful.
:shipit:

That's the html test tool - we can fix later I think...
Merging!
@andrewnorell, ready for the favicon!

authors: andrewnorell chrismou jacobwgillespie

repo: radiant-player/radiant-player-mac


text:
Remove Commons metadata / rework bands object

Opening an issue for discussion that came up on our last STAC call - considering removing the 'commons' extension. A few reasons came up:

It's confusing, to have 'commons extension' and 'common metadata'
We now have 'summaries' which are a cleaner way to  do one of the things commons metadata was used for.
The only case it seems really useful is the 'bands' object.

The key thing to do is to figure out another way to handle the bands. I wonder if one option is to just make it something that can be added at the collection level?

Some additional thoughts:
The Commons extension served two purposes originally.
One was to present users with what fields were the same across all Items in a Collection. As @cholmes points out the summaries extension now does that in a better way. Fields with a single value have a summary of one value, but can also includes summaries of all the fields.
The other was to avoid redundancy. However, in practice there's really only a couple fields (with the exception of eo:bands) that this ends up being used for, such as instruments or constellation. This is not much savings. And in an API it makes more sense to not use commons as it makes querying extremely difficult. Furthermore, the confusion to the user when they look at an Item and it does not actually contain all the values does not seem worth it.
The additional issue with the eo:bands properties is that it's a list of objects, so it's not queryable in any way currently. I also find it confusing to map out assets to bands.
I would propose two related changes:

return the Assets definition to core as an integral part of a collection
define spectral bands using the eo extension in the asset definition. Each asset will have an associated spectral_bands array of objects indicating the spectral bands in that asset.  This might introduce some redundant fields (multiple assets which contain the same band), but since this is at the collection level and note items this really isn't a big deal.

I suspect @m-mohr might have a problem with this since he has a use case where he doesn't have Items, but in that case I'm wondering how you use the eo:bands object anyway.

If you are exposing data as cloud API / service as Google and openEO do, you don't really want to expose the structure of the assets to users so that's why assets won't work well. What we do is to just specify the bands in the summaries as with all other fields. (+ openEO uses the data cube extension and bands are a dimension.)
So, just having bands in assets is not ideal and we discussed last call that the "properties"/"summaries" should still include something if there's a field specified in the assets (like with gsd). Still thinking myself about the best solution...

We talked about this on the 4/13 call and agreed that the bands in assets is not ideal, and the path forward is just to move the bands object to the collection level. The structure would stay the same, it'd be defined in the extension (so not something that confuses people who are using stac for non-eo purposes), and it would live as a top level catalog thing. There is precedence already for other extensions defining top level collection fields.

I forgot about that yesterday: What happens for Items that don't have collections? Do they still list bands in properties? I'm just thinking about the use case Seth pushed earlier (single items) and I'm using now in openEO, too. That's basically what we added providers and license for in common metadata. Having bands only at the collection level would break that use case.

I thought Seth had been fine with breaking that use case when we got the single file STAC extension. Like to just have one file where you have a collection + item (though I forget if it ever achieved that goal).
If we do want to support it I suppose we could just say that bands object can also be inserted at the properties level.

I thought Seth had been fine with breaking that use case when we got the single file STAC extension. Like to just have one file where you have a collection + item (though I forget if it ever achieved that goal).

So we can also remove license and providers from the common metadata? I like that... ;-)
Whatever we do, it should be consistent. So if we add bands to collections and not to items, I'd remove at least providers (and probably also license).

If we do want to support it I suppose we could just say that bands object can also be inserted at the properties level.

Agreed.

So we can also remove license and providers from the common metadata? I like that... ;-)

Yeah, I had thought we got there, though perhaps am misremembering, or maybe I dreamed it.

After discussion this morning with @anayeaye @jbants and @m-mohr we came to a more flexible solution here for bands object.
We're closing #785 without merging.  eo:bands stays at the Item properties level, which makes it useful for eventual search or inclusion into summaries.   With #760 the eo:bands can be specified for a specific asset, so the index referencing can be removed.  If you want to specify what bands an asset has you don't reference another array you just define an array of those bands.
Finally, we will issue a new proposal for extending the asset definitions to do something similar to the Commons extension that is getting removed, but in much more limited fashion.

Just a note - whenever you do the commons extension removal be sure to remove this paragraph in the collection spec:

A group of STAC Item objects from a single source can share a lot of common metadata. This is especially true with satellite imagery that uses the STAC EO or SAR extension. Rather than including these common metadata fields on every Item, they can be provided in the properties of the STAC Collection that the STAC Items belong to.

It's the second paragraph. Not sure how that got in there without even an indication that you need an extension to do this (unless I'm reading it wrong?).

I guess we forgot to change this when moving this behavior from core to the extension.

authors: cholmes m-mohr matthewhanson

repo: radiantearth/stac-spec


text:
Fix rad_group_switch synopsis text

Fix the synopsis text formatting from a code block to a regular text block.

[x] Read the contribution guide
[x] Commands include options for Linux, MacOS, and Windows within codetabs
[x] New file and folder names are globally unique
[x] Page references use shortcodes instead of markdown or URL links
[x] Images use HTML style and have alternative text
[x] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
The rad group switch page currently uses code formatting for the synopsis text. This PR fixes the formatting.

Issue reference
Fixes: N/A

@brooke-hamilton - The CLI docs are autogenerated from Radius repository. Can you close this and make changes to the file in radius repository

authors: Reshrahim brooke-hamilton

repo: radius-project/docs


text:
🛑 GPS Receiver API is down

In 690dd11, GPS Receiver API (http://tracker.ace-energy.co.th/receiver/api/v1/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GPS Receiver API is back up in b3b665b.

repo: radiuszon/upptime


text:
migrate components to react 19

Feature request
Overview

Migration to react 19
Examples in other libraries

React rc
Who does this impact? Who is this for?

Most of the projects using Radix-ui
Additional context
react rc docs

Several components depend on react-remove-scroll@2.6.0, which in turn depends on use-callback-ref@^1.3.0, a package that hasn’t updated its peer dependencies. Even react-remove-scroll@2.6.1 still relies on use-callback-ref, so we all depend on that package upgrading its peer.

react-remove-scoll@2.6.2 has been released which increments use-callback-ref to a react 19 version.

authors: RicardoGEsteves escorponox garnerp

repo: radix-ui/primitives


text:
Toggle to color code hex rw scale

Would be a good visual on hexes to see if they currently hit rw scale limits or are available to use without penalty.

Perhaps instead of hex color visual. What if we had a hotspot location feature that showed the number of hotspots in each of its corresponding hexes (from res4-10)

Resolved with #96 . You can enable the hex density count legend by toggling "Location Hexes" on.


text:
vmnet error compilation on Ubuntu Lucid

Hi,
Second pull request with the issue identifier, it should solve it.
Have a good day
Fabien

Fabien,
Version 1.5 of the script and patches should work on that kernel. Have
you tried them?
Regards,
Radu
On 10/20/2011 12:20 PM, Fabien Engels wrote:

Hi,
Second pull request with the issue identifier, it should solve it.
Have a good day
Fabien
You can merge this Pull Request by running:
git pull https://github.com/fabienengels/vmware-server-linux-2.6.3x-kernel master
Or you can view, comment on it, or merge it online at:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3
-- Commit Summary --

Solved vmnet compilation error on Ubuntu Lucid (2.6.32-33-server) #1

-- File Changes --
M vmware-server-2.0.2-203138-update.patch (159)
-- Patch Links --
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.patch
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.diff

--
Radu Cotescu http://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web: 	radu.cotescu.com http://radu.cotescu.com
Email: 	radu@cotescu.com mailto:radu@cotescu.com
Cell: 	+40 744 406 353

Hi,
I used the last one provided on your web site, version 1.6 (and last
commit from your repo). Is it not compatible with Lucid ? and should I
use only the 1.5 one ?
All I know using the provided patch with your master make it works
with an up to date lucid :)
btw finally I moved to virtualbox who is able to run Linux 2.2 (no
comment :) ) as well as VMWare Server :)
Bests
Fabien
2011/10/22 Radu Cotescu
reply@reply.github.com:

Fabien,
Version 1.5 of the script and patches should work on that kernel. Have
you tried them?
Regards,
Radu
On 10/20/2011 12:20 PM, Fabien Engels wrote:

Hi,
Second pull request with the issue identifier, it should solve it.
Have a good day
Fabien
You can merge this Pull Request by running:
git pull https://github.com/fabienengels/vmware-server-linux-2.6.3x-kernel master
Or you can view, comment on it, or merge it online at:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3
-- Commit Summary --

Solved vmnet compilation error on Ubuntu Lucid (2.6.32-33-server) #1

-- File Changes --
M vmware-server-2.0.2-203138-update.patch (159)
-- Patch Links --
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.patch
   https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.diff

--
Radu Cotescu http://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web:    radu.cotescu.com http://radu.cotescu.com
Email:  radu@cotescu.com mailto:radu@cotescu.com
Cell:   +40 744 406 353
--
Reply to this email directly or view it on GitHub:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3#issuecomment-2488982

Version 1.6 handles kernels higher than 2.6.38. 1.5 is for 2.6.32 - 2.6.35.
On 10/22/2011 12:05 PM, Fabien Engels wrote:

Hi,
I used the last one provided on your web site, version 1.6 (and last
commit from your repo). Is it not compatible with Lucid ? and should I
use only the 1.5 one ?
All I know using the provided patch with your master make it works
with an up to date lucid :)
btw finally I moved to virtualbox who is able to run Linux 2.2 (no
comment :) ) as well as VMWare Server :)
Bests
Fabien
2011/10/22 Radu Cotescu
reply@reply.github.com:

Fabien,
Version 1.5 of the script and patches should work on that kernel. Have
you tried them?
Regards,
Radu
On 10/20/2011 12:20 PM, Fabien Engels wrote:

Hi,
Second pull request with the issue identifier, it should solve it.
Have a good day
Fabien
You can merge this Pull Request by running:
git pull https://github.com/fabienengels/vmware-server-linux-2.6.3x-kernel master

Or you can view, comment on it, or merge it online at:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3

-- Commit Summary --

Solved vmnet compilation error on Ubuntu Lucid (2.6.32-33-server) #1

-- File Changes --
M vmware-server-2.0.2-203138-update.patch (159)
-- Patch Links --
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.patch
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.diff

--
Radu Cotescuhttp://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web:    radu.cotescu.comhttp://radu.cotescu.com
Email:  radu@cotescu.commailto:radu@cotescu.com
Cell:   +40 744 406 353
--
Reply to this email directly or view it on GitHub:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3#issuecomment-2488982

--
Radu Cotescu http://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web: 	radu.cotescu.com http://radu.cotescu.com
Email: 	radu@cotescu.com mailto:radu@cotescu.com
Cell: 	+40 744 406 353

Oh ok ... so my patch is useless, sorry to waste your time.
Maybe it could be nice to provide patches for various kernel versions
and applied one of them depending of uname output. So people won't
have to worry anymore about the version to use, just get the last one
but it'll be an extra bonus since your work it's really hepful and
should be done by VMWare ... :)
2011/10/22 Radu Cotescu
reply@reply.github.com:

Version 1.6 handles kernels higher than 2.6.38. 1.5 is for 2.6.32 - 2.6.35.
On 10/22/2011 12:05 PM, Fabien Engels wrote:

Hi,
I used the last one provided on your web site, version 1.6 (and last
commit from your repo). Is it not compatible with Lucid ? and should I
use only the 1.5 one ?
All I know using the provided patch with your master make it works
with an up to date lucid :)
btw finally I moved to virtualbox who is able to run Linux 2.2 (no
comment :) ) as well as VMWare Server :)
Bests
Fabien
2011/10/22 Radu Cotescu
reply@reply.github.com:

Fabien,
Version 1.5 of the script and patches should work on that kernel. Have
you tried them?
Regards,
Radu
On 10/20/2011 12:20 PM, Fabien Engels wrote:

Hi,
Second pull request with the issue identifier, it should solve it.
Have a good day
Fabien
You can merge this Pull Request by running:
git pull https://github.com/fabienengels/vmware-server-linux-2.6.3x-kernel master
Or you can view, comment on it, or merge it online at:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3
-- Commit Summary --

Solved vmnet compilation error on Ubuntu Lucid (2.6.32-33-server) #1

-- File Changes --
M vmware-server-2.0.2-203138-update.patch (159)
-- Patch Links --
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.patch
    https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3.diff

--
Radu Cotescuhttp://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web:    radu.cotescu.comhttp://radu.cotescu.com
Email:  radu@cotescu.commailto:radu@cotescu.com
Cell:   +40 744 406 353
--
Reply to this email directly or view it on GitHub:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3#issuecomment-2488982

--
Radu Cotescu http://radu.cotescu.com
Radu Cotescu | Software Developer, Tech Blogger, Author
Web:    radu.cotescu.com http://radu.cotescu.com
Email:  radu@cotescu.com mailto:radu@cotescu.com
Cell:   +40 744 406 353
--
Reply to this email directly or view it on GitHub:
https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/pull/3#issuecomment-2489111

authors: fabienengels raducotescu


text:
Add TopRight and BottomRight position to TabPosition

This PR adds TopRight and BottomRight position to TabPosition and implements issue #410.
TopRight example

BottomRight example

Thank you for your feedback. I haveve updated this with the requested changes.

repo: radzenhq/radzen-blazor


text:
Table: Columns not updating correctly when passing new column layout.

Overview of the problem
Buefy version: [0.4.0]
Vuejs version: [2.3.1]
Description
I have the table-columns in a loop like so:
<b-table-column
  v-for="(field, index) in ModelClass.overviewFields"
  :key="index"
  :field="field.key"
  :label="field.label"
>
  {{ props.row.attributes[field.key] }}
</b-table-column>

That way, i can dynamically change the layout of the table in a data-driven way.
Steps to reproduce

See above html
Update ModelClass.overviewFields a couple of times -> the columns get messed up.

The problem lies within the way the <td>-components edit the tables column-property in TableColumn.vue:
const repeated = this.$parent.columns.some((column) => {
  return column.label === this.label
})
!repeated && this.$parent.columns.push(this.$props)

The columns should be reset before refilled.
Expected behaviour
The table component should correctly recalculate the column labels.

This is fixed in next release (v0.4.1), columns will be reactive.

@jwahdatehagh this.$refs.table.columns = [] getting error as below.
@rafaelpimpa , i tried columns=[], it doesn't help.
Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders. Instead, use a data or computed property based on the prop's value. Prop being mutated: "columns"

I don't see where @tanhs question was ever answered. I have the same issue with dynamic columns. I can't fix it because the problem is in the table component.

Yeah my answer did work half a year ago. Now i just rerender the entire table when columns change by leveraging v-if on the table (in my usecase i'm setting 'loading' to true just before doing an ajax call, so Vue will definitely rerender the table.
<b-table
  v-if="!loading"
  :data="data"
>
  // ...
</b-table>

You could achieve the same thing by toggling the table like this:
changeColumns () {
  this.showTable = false
  this.$nextTick(() => this.showTable = true)
}

(given you have a <b-table v-if="showTable">)

authors: jwahdatehagh rafaelpimpa talismax tanhs

repo: rafaelpimpa/buefy


text:
Create a ragu-dom wrapper for VueJs

There are also a client for React: https://github.com/ragu-framework/ragu-client-react
The same need to be done for VueJs.

https://github.com/ragu-framework/ragu-client-vue

repo: ragu-framework/ragu


text:
pull in fix for pivotal-cf#19, om_network_name param does not allow spaces

quick fix originally suggested at https://github.com/pivotal-cf/pcf-pipelines/issues/19, to permit spaces in the network name.

thanks @trevormarshall

authors: rahulkj trevormarshall

repo: rahul-kj/pcf-concourse-pipelines


text:
Add Servo detach implementation

This change adds a detach() method to the Servo class, which allows the servo to be "stopped". This can be important for software-PCM-controlled servos and for minimising CPU usage.
For comparison with the equivalent implementation in the Python GPIO Zero implementation, see the relevant:

documentation;
Python source, where detach calls value.setter which calls RPiGPIOPin._set_frequency() which then finally calls GPIO.PWM.stop();
lower-level Rust source, where IoPin::clear_pwm() calls soft_pwm.stop().

I'd be grateful if you'd consider this for incorporation into the library. This PR builds on @RustyPro's nice #28 changes for adding a set_position() implementation, which I've also found to be a useful and important addition to the library.

thanks for your contribution @llewelld !
unfortunately, I currently do not have the capacity to test this. see https://github.com/rahul-thakoor/rust_gpiozero/issues/11 I can add you as a maintainer if you are up for it :)
or, perhaps @dcroote is able to test this?

Thanks @rahul-thakoor for your reply (I missed #11 so hadn't appreciated this was the situation).
If @dcroote is able to help then I'd appreciate the additional eyes.
More broadly if the objective is to ultimately try to replicate the functionality of Python GPIO Zero then that's something I'd be interested to help with. While I appreciate the offer as a way to move things forwards, I'd prefer to try to tackle some existing issues, or fill some gaps between this and the Python version, before you consider me as a maintainer.

Thanks- I will need a few days but I'd be happy to have a look

authors: dcroote llewelld rahul-thakoor


text:
Network meter "speed test button" can't be disabled.

The Speedtest button on hover button in the network meter setting does nothing when unchecked.
I'm expecting it to hide the speed test button in the network meter, but it doesn't.

This is fixed in v1.5.1-rc.1, as it had been reported by a colleague of mine. If you want to access it now, go into the global settings skin, click the "Opt-in to development testing" button, and download the update through the update notification.

authors: SpaceBeeGaming raiguard

repo: raiguard/ModernGadgets


text:
[Feature Request] Ability to create several tables in one version

As the title suggests, it would be nice if it’s possible to have several tables created in one version change itself. Also, I find it odd that there are no provisions to apply foreign keys and also unique constraint on columns. Those would be nice features to have.

+1

Builder has known limitations and they are described in the plugin's documentation. Index management is planned. Multiple PHP scripts per migration is unlikely to be implemented in the near future. It requires a complex UI solution which would move our focus away from our primary goal - the content management system development. Builder is a helper tool, which has it's own limitations, but still doesn't limit your abilities to develop plugins. Everything that can't be implemented with Builder can be done manually.

Maybe a feature that merges versions will help on that. Yes it's e a little problem because when you develop a plugin sometimes you need to add/remove/change table fields.

Yes then it doesn’t help reduce plugin development time. So far, builder added more time for me to build plugins. I have switched back to console scaffolding because of these:

I tried making a Db. The table has a foreign key but builder doesn’t support it. So had to go back and fix it.
Since the Db is foreign key based it needs both tables to be pushed in same version. So had to write that again. Ultimately, I ended up removing the builder_table_create_some_table name and switched to the standard create_some_table.php format since I felt it’s too long.
I uploaded my plugin to octobercms.com. Got an error that I need to specify plugin name. I realize octoberCMS backend parses Plugin.php. I created a Plugin.php and move the Plugin.yaml data to this in appropriate sections. It all started to work now. I feel having two files would only create an overhead in the long run to have two different possible places for configuration.
Currently, Builder sets model timestamps to false when it generates the models. Several of the models I built required timestamp and there isn’t a provision within Builder to add timestamps. So, I had to manually enter timestamps, come back to backend, refresh and only then I was able to see created_on and updated_on appear in the autocomplete in Models section.

On a completely different note, I also had one technical issue with building a plugin that shared same navigation menu. I thought if I specify the same navigation name it may merge (it doesn’t work that way). In the end, I transferred even my second plugin’s Plugin.yaml into a Plugin.php and used this method to add the sub menu. I appreciate the amount of work that has been put into this and find some features really interesting but I haven’t personally felt a big difference in accelerating my plugin development. I think Builder is more oriented to non-developers who want to get into OctoberCMS development than for developers as they are pretty good doing things using console scaffolding commands.

1, 2 - foreign keys and indexes are planned.
3 - plugin.yaml support is planned too.
4. Timestamps are planned.

Good to know they’re planned. Looking forward to these updates.

authors: SaifurRahmanMohsin alekseybobkov tsioukas vojtasvoboda

repo: rainlab/builder-plugin


text:
Invalid argument(s): Failed to load dynamic library 'libopencv_dart.so'

Hello
I am developing an app using the opencv_dart plugin. With it, I can easily implement image operations such as grayscale conversion and pencil drawing conversion. It is really great!
When I run it on an old tablet, I encounter an error loading lib. If possible, please help me analyze the reason.Thank you very much!
Describe the bug
crash logs =>
E/flutter ( 5108): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to load dynamic library 'libopencv_dart.so': dlopen failed: empty/missing DT_HASH in "libopencv_dart.so" (built with --hash-style=gnu?)
E/flutter ( 5108): #0      _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:11:43)
E/flutter ( 5108): #1      new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:22:12)
E/flutter ( 5108): #2      loadNativeLibrary (package:opencv_dart/src/native_lib.dart:37:29)
E/flutter ( 5108): #3      cimgproc (package:opencv_dart/src/native_lib.dart:48:42)
E/flutter ( 5108): #4      cimgproc (package:opencv_dart/src/native_lib.dart)
E/flutter ( 5108): #5      getStructuringElement. (package:opencv_dart/src/imgproc/imgproc.dart:591:15)
E/flutter ( 5108): #6      cvRun (package:opencv_dart/src/core/base.dart:83:76)
E/flutter ( 5108): #7      getStructuringElement (package:opencv_dart/src/imgproc/imgproc.dart:591:3)
To Reproduce
just call
var kernel = cv.getStructuringElement(cv.MORPH_RECT, (kernelSize, kernelSize));
In fact, opencv cannot be initialized, and calling any API will result in an error
Smartphone (please complete the following information):

Device:  MI PAD 2 (mobile)       • A3P472621E67            • Android 5.1 (API 22)
ABI Version [android-x64]

Additional context
flutter:   Flutter (Channel stable, 3.24.3, on macOS 14.3 23D56 darwin-arm64)
opencv_dart: 1.2.5

@cuishijie1991 API level 22 is not supported, the minimum supported API is 24.
It's because some videoio API only available since 24, you can compile opencv and dartcv from source to make it work on API 22.

Thank you for your replay, I will try

@cuishijie1991 API level 22 is not supported, the minimum supported API is 24.
It's because some videoio API only available since 24, you can compile opencv and dartcv from source to make it work on API 22.

Thank you for your replay, I will try!


text:
🛑 RiotSkin4CN-Download is down

In d7ce9dc, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in 1308c54.


text:
🛑 RiotSkin4CN-Download is down

In 6f56d8f, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in 5121912.


text:
🛑 RiotSkin4CN-Download is down

In 45b780a, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in b364a08.


text:
🛑 RiotSkin4CN-Download is down

In 3ceb1ea, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in e1871c8.


text:
Set Cover

Get Cover from web or from YouTube video

[X] from YouTube video
[ ] from web
[ ] Convert to correct apect ratio

What is the correct aspect ratio? Or the best resolution?

correct aspect ratio is 1:1 (square), generally the larger the better (4K TV and USDX roulette has 1920x1920 px).

fanart.tv has high quality covers with (exactly) 1000x1000 px.

Youtube thumbnail crop to 1:1 ratio db717ecbea7b79fc7fa2f13cc3ddf4c03e4dc52c

MusicBrainz has a REST API to query album art and informations about songs.
They also define a unique identifier for artists, albums, and songs.
The MusicBrainz API is free for non-commercial use.

@achimmihca i using musicbrainz  for additional infos. See #39.
Next step is to get the pictures from there.
But i think we should also use fanart.tv. At least for background.

authors: achimmihca bohning rakuri255


text:
DSEGOG-58 adding button to reset zooming and panning

Description
This adds a plot button which resets both the zooming and the panning currently set on the plot to whatever its default calculated value was. This is achieved by setting a boolean flag on the ChartJS canvas object, which calls chart.resetZoom whenever it changes.
Testing instructions
Hit the button. Is the zooming and panning reset? Great success!

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage

Agile board tracking
Closes DSEGOG-58

This is okay but doesn't test the view reset functionality terribly well. Ideally, I'd like to spy on the chart.resetZoom method but I'm not sure if this can be done or not. Any ideas, Louise?

Anything testing the Chart.js code will likely need to be done in e2e tests. I have some working tests with Playwright on Firefox which include testing zoom/pan behaviour (what we'd do here in zoom/pan in, take a screenshot, reset zoom and expect to be back to "normal")
I'm just debugging some issues on why Chrome isn't loading the chart libraries when running via Playwright before I can create a PR to add e2e tests for chart.js stuff

That's what I thought, thanks! In the meantime, I'll leave this as is and can be reviewed/merged whenever

authors: louise-davies sam-glendenning

repo: ral-facilities/operationsgateway


text:
bin/ec: generate valid deposits for the deposit contract given some validator keys

take a keystore and make a "deposit_data.json" file like the staking-cli

will take this up!

repo: ralexstokes/ethereum-consensus


text:
AsyncView http request loops inside a TabView

The http request keeps on looping if i place this inside a TabView. What is the workaround for this? Please advise.

The http request keeps on looping if i place this inside a TabView. What is the workaround for this? Please advise.

@chitgoks oh, i'm having the same problem.
I think the root cause is adding task (or refreshable) to View.
So, render view -> task call -> task finished -> render view -> .... and loops
public var body: some View {
        AsyncResultView(
            result: model.result,
            reloadAction: { Task { await model.load() } },
            content: content
        )
        .task {
            await model.loadIfNeeded()
        }
        .refreshable {
            await model.load()
        }
    }

Ref: async-function-swiftui

I fixed by:

Remove task and refreshable
Handle Task in init function of model

public init(asyncOperation: AsyncOperation? = nil) {
        if let asyncOperation {
            asyncOperationBlock = asyncOperation
        }
        Task {
            await load()
        }
    }

p/s: I'm happy if this package gets fixed, it's worth looking forward to

I actually got this to work. but seeing as im new to ios, my knowledge is limited.
I placed the AsyncView inside another container, say, a ZStack. Works good.
But i do not understand why.

I also tried as you said but it only solves the infinite loop problem.
When i switch to another tab and come back again, api is called again and view will re-render and view's state not kept.
Anyway congrats on solving your problem. ✌✌✌

also us3d to have that problem. i guess inside your body is only the async view?
what i did was something like
if let obj then show ui
else show asyncView block code

authors: chitgoks ngodacdu

repo: ralfebert/AsyncView


text:
add support for item retrieval via IDs, item removal, RSM and MAM

Hi Ralph,
we would love to see this changes in wokkel. There's a couple of leftover TODO or FIXME, we will take care to remove them if you are willing to merge with your repo. Let us know.
Adrien & Jérôme

will split the changes in separate pull requests

repo: ralphm/wokkel


text:
airflow 2 support

This PR adds support for airflow 2, and:

Drops support for airflow 1 (to avoid complicating the tests, because airflow.operators.dummy is not importable in v1, and airflow.operators.dummy_operator is not importable in v2),
Drops support for python 2.7 (airflow 2 doesn't support it),
Drops .travis.yml (I guess it doesn't work anymore).

I have tested this in a "hello world"-like environment and it seems to work fine.
@kxepal feel free to make any alterations on top if you want to.

I've been running this for a week on 2.1.3 -- haven't found any issues so far.


text:
applySpec function not supplied helpful error message

Error is unhelpful when a function is not supplied, e.g.
applySpec({id: "10"}, 1)

Encountered this myself. We don't usually do input-validation, but here it's probably a good idea to do so, as it's very easy to forget always.
But if we do this, we should probably also make the same change to evolve and where.

authors: asaf-romano mattS-H

repo: ramda/ramda