extremas: true issue

Checklist

[ x] I updated the card to the latest version available
[ x] I cleared the cache of my browser
[ x] I verified that I'm really running the lastest version in my browser console
[ x] I checked if there is another issue opened with the same problem

Describe the bug
extremas: true  is showing outside card graph area
Version of the card
Version: 1.7
To Reproduce
This is the configuration I used:

Screenshots

Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):

Browser chrome
Version [e.g. 22]

Smartphone (please complete the following information):

Device: pc
OS: win 10
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

It does work yet with multi-y axis, forgot to say it in the documentation.

Would you mind sharing your config (stripped down if possible) with just the series without details and the yaxis part of apex_config you have so that I can see an example of how you are doing it? (Would be one of many solution but at least it gives me an example).
I'll add support to it, but points on the graphs are linked to a y-axis, so I'd need to figure out which one. Your config would help.

I will give the full set  as there are some tricks played to get it correct I will also post a new pic - without the extremas as this is constantly changing as you add extras

apexcharts_card_templates:
  default: null
  heating:
    color_list:
      - 'rgb(128, 0, 128)'
      - 'rgb(0, 128, 128)'
      - 'rgb(0, 0, 255)'
      - 'rgb(0, 255, 0)'
      - 'rgb(255, 0, 0)'
      - 'rgb(128, 128, 128)'
    header:
      show: true
      title: .
      floating: false
      show_states: true
      colorize_states: true
    now:
      show: true
    experimental:
      disable_config_validation: true
    graph_span: 1d
    span:
      end: hour
    all_series_config:
      extend_to_end: false
      fill_raw: zero
      group_by:
        duration: 2min
        func: max
      curve: stepline
      stroke_width: 2
      show:
        extremas: false
    y_axis_precision: 0
    apex_config:
      yaxis:
        - show: false
          decimalsInFloat: 0
          min: -100
          max: 0
        - show: false
          decimalsInFloat: 0
          min: -100
          max: 0
        - show: true
          opposite: true
          min: 0
          max: 100
          decimalsInFloat: 0
        - show: true
          decimalsInFloat: 0
          min: -3
          max: 30
        - show: false
          decimalsInFloat: 0
          min: -3
          max: 30
        - show: false
          decimalsInFloat: 0
          min: -3
          max: 30
      xaxis:
        type: datetime
        zoom:
          type: x
          enabled: true
          autoScaleYaxis: true
      chart:
        type: line
        stacked: false
        height: 350
        zoom:
          type: x
          enabled: true
          autoScaleYaxis: true
        toolbar:
          show: true
          floating: true
          offsetX: -60
          offsetY: 0
          tools:
            download: true
            selection: true
            zoom: true
            zoomin: false
            zoomout: false
            pan: true
            reset: true
          autoSelected: zoom
      grid:
        borderColor: 'rgb(40, 40, 40)'
        strokeDashArray: 0
        position: back
        row:
          colors:
            - 'rgb(60, 60, 60)'
            - transparent
          opacity: 0.1
        column:
          colors:
            - 'rgb(60, 60, 60)'
            - transparent
          opacity: 0.1
        xaxis:
          lines:
            show: true
        padding:
          top: 0
          right: 4
          bottom: 0
          left: 4
      title:
        align: centre
        margin: 0
        offsetX: 5
        offsetY: -75
        floating: false
        style:
          fontSize: 22px
          fontWeight: bold
          fontFamily: Segoe UI Light
          color: 'rgb(255, 255, 255)'
    show:
      loading: false

              - config_templates: heating
                series:
                  - entity: sensor.wiser_itrv_back_room_2
                    attribute: device_reception_RSSI
                    name: Device RSSI
                    show:
                      in_header: false
                  - entity: sensor.wiser_itrv_back_room_2
                    attribute: controller_reception_RSSI
                    name: Controller RSSI
                    show:
                      in_header: false
                  - entity: climate.wiser_back_room
                    attribute: percentage_demand
                    name: Demand
                    unit: '%'
                    type: area
                  - entity: climate.wiser_back_room
                    attribute: temperature
                    name: Target
                    unit: ℃
                  - entity: climate.wiser_back_room
                    attribute: current_temperature
                    name: Current
                    unit: ℃
                  - entity: sensor.outdoor_temperature
                    name: Outdoor
                y_axis_precision: 0
                apex_config:
                  title:
                    text: Back Room Heating
                type: 'custom:apexcharts-card'
                gridrow: 1 / 1
                gridcol: 2 / 2
                style: 'ha-card { height: 100%; }'

data from chart
category,Device RSSI,Controller RSSI,Demand,Target,Current,Outdoor
Wed Feb 17 2021,-71,-76,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-71,-76,0,20.5,21.5,10.61
Wed Feb 17 2021,-71,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-71,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-76,-80,0,20.5,21.5,10.61
Wed Feb 17 2021,-75,-79,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-77,0,20.5,21.5,10.61
Wed Feb 17 2021,-72,-78,0,20.5,21.5,10.61
Wed Feb 17 2021,-74,-79,0,20.5,21.5,10.61
Wed Feb 17 2021,-73,-79,0,20.5,21.5,10.61
Wed Feb 17 2021,-73,-78,0,20.5,21.5,10.61
Wed Feb 17 2021,-73,-78,0,20.5,21.5,10.61
Wed Feb 17 2021,-73,-77,0,20.5,21.5,10.72
Wed Feb 17 2021,-73,-79,0,20.5,21.5,10.72
Wed Feb 17 2021,-74,-79,0,20.5,21.4,10.61
Wed Feb 17 2021,-74,-79,0,20.5,21.4,10.72
Wed Feb 17 2021,-71,-79,0,20.5,21.4,10.61
Wed Feb 17 2021,-74,-80,0,20.5,21.4,10.61
Wed Feb 17 2021,-76,-80,0,20.5,21.4,10.61
Wed Feb 17 2021,-76,-80,0,20.5,21.4,10.61
Wed Feb 17 2021,-76,-81,0,20.5,21.4,10.61
Wed Feb 17 2021,-75,-81,0,20.5,21.4,10.61
Wed Feb 17 2021,-75,-81,0,20.5,21.4,10.5
Wed Feb 17 2021,-75,-80,0,20.5,21.4,10.5
Wed Feb 17 2021,-77,-80,0,20.5,21.4,10.5
Wed Feb 17 2021,-74,-80,0,20.5,21.4,10.5
Wed Feb 17 2021,-76,-81,0,20.5,21.4,10.5
Wed Feb 17 2021,-76,-82,0,20.5,21.3,10.5
Wed Feb 17 2021,-76,-80,0,20.5,21.4,10.5
Wed Feb 17 2021,-76,-81,0,20.5,21.4,10.5
Wed Feb 17 2021,-75,-80,0,20.5,21.3,10.5
Wed Feb 17 2021,-79,-83,0,20.5,21.3,10.39
Wed Feb 17 2021,-74,-79,0,20.5,21.4,10.39
Wed Feb 17 2021,-74,-79,0,20.5,21.3,10.5
Wed Feb 17 2021,-73,-79,0,20.5,21.3,10.5
Wed Feb 17 2021,-75,-80,0,20.5,21.3,10.5
Wed Feb 17 2021,-75,-80,0,20.5,21.3,10.5
Wed Feb 17 2021,-73,-78,0,20.5,21.3,10.5
Wed Feb 17 2021,-73,-79,0,20.5,21.3,10.5
Wed Feb 17 2021,-72,-77,0,20.5,21.3,10.39
Wed Feb 17 2021,-70,-75,0,20.5,21.3,10.39
Wed Feb 17 2021,-70,-74,0,20.5,21.3,10.39
Wed Feb 17 2021,-71,-76,0,20.5,21.3,10.39
Wed Feb 17 2021,-71,-77,0,20.5,21.3,10.5
Wed Feb 17 2021,-74,-79,0,20.5,21.3,10.5
Wed Feb 17 2021,-76,-82,0,20.5,21.3,10.5
Wed Feb 17 2021,-74,-80,0,20.5,21.3,10.5
Wed Feb 17 2021,-73,-78,0,20.5,21.3,10.5
Wed Feb 17 2021,-73,-79,0,20.5,21.3,10.5
Wed Feb 17 2021,-74,-78,0,20.5,21.3,10.39
Wed Feb 17 2021,-73,-78,0,20.5,21.3,10.39
Wed Feb 17 2021,-73,-79,0,20.5,21.3,10.39
Wed Feb 17 2021,-73,-78,0,20.5,21.3,10.39
Wed Feb 17 2021,-76,-80,0,20.5,21.3,10.28
Wed Feb 17 2021,-72,-77,0,20.5,21.3,10.28
Wed Feb 17 2021,-74,-80,0,20.5,21.3,10.28
Wed Feb 17 2021,-74,-79,0,20.5,21.2,10.28
Wed Feb 17 2021,-73,-76,0,20.5,21.2,10.28
Wed Feb 17 2021,-73,-78,0,20.5,21.2,10.28
Wed Feb 17 2021,-73,-78,0,20.5,21.2,10.28
Wed Feb 17 2021,-73,-77,0,20.5,21.2,10.28
Wed Feb 17 2021,-74,-79,0,20.5,21.2,10.28
Wed Feb 17 2021,-74,-77,0,20.5,21.2,10.28
Wed Feb 17 2021,-72,-77,0,20.5,21.2,10.28
Wed Feb 17 2021,-73,-78,0,20.5,21.2,10.22
Wed Feb 17 2021,-72,-77,0,20.5,21.2,10.22
Wed Feb 17 2021,-72,-76,0,20.5,21.2,10.22
Wed Feb 17 2021,-72,-78,0,20.5,21.3,10.22
Wed Feb 17 2021,-72,-77,0,20.5,21.2,10.22
Wed Feb 17 2021,-71,-77,0,20.5,21.2,10.22
Wed Feb 17 2021,-71,-77,0,20.5,21.3,10.22
Wed Feb 17 2021,-72,-75,0,20.5,21.3,10.11
Wed Feb 17 2021,-71,-76,0,20.5,21.3,10.11
Wed Feb 17 2021,-71,-79,0,20.5,21.3,10
Wed Feb 17 2021,-71,-77,0,20.5,21.2,10
Wed Feb 17 2021,-72,-77,0,20.5,21.2,10
Wed Feb 17 2021,-72,-78,0,20.5,21.2,10
Wed Feb 17 2021,-75,-79,0,20.5,21.2,10
Wed Feb 17 2021,-73,-79,0,20.5,21.2,10
Wed Feb 17 2021,-74,-78,0,20.5,21.2,10
Wed Feb 17 2021,-73,-78,0,20.5,21.2,10
Wed Feb 17 2021,-73,-79,0,20.5,21.2,9.89
Wed Feb 17 2021,-73,-79,0,20.5,21.1,9.89
Wed Feb 17 2021,-75,-79,0,20.5,21.2,9.89
Wed Feb 17 2021,-73,-82,0,20.5,21.2,9.89
Wed Feb 17 2021,-73,-78,0,20.5,21.2,9.89
Wed Feb 17 2021,-73,-80,0,20.5,21.1,9.89
Wed Feb 17 2021,-73,-79,0,20.5,21.2,9.89
Wed Feb 17 2021,-74,-79,0,20.5,21.2,9.89
Wed Feb 17 2021,-73,-78,0,20.5,21.1,9.78
Wed Feb 17 2021,-73,-79,0,20.5,21.2,9.78
Wed Feb 17 2021,-73,-80,0,20.5,21.1,9.78
Wed Feb 17 2021,-75,-80,0,20.5,21.1,9.78
Wed Feb 17 2021,-76,-81,0,20.5,21.1,9.78
Wed Feb 17 2021,-77,-82,0,20.5,21.2,9.72
Wed Feb 17 2021,-71,-77,0,20.5,21.1,9.72
Wed Feb 17 2021,-71,-77,0,20.5,21.1,9.61
Wed Feb 17 2021,-74,-79,0,20.5,21.1,9.61
Wed Feb 17 2021,-73,-79,0,20.5,21.1,9.61
Wed Feb 17 2021,-77,-78,0,20.5,21.1,9.61
Wed Feb 17 2021,-73,-78,0,20.5,21.1,9.61
Wed Feb 17 2021,-73,-78,0,20.5,21.1,9.5
Wed Feb 17 2021,-76,-81,0,20.5,21.1,9.39
Wed Feb 17 2021,-76,-81,0,20.5,21.1,9.39
Wed Feb 17 2021,-76,-82,0,20.5,21.1,9.39
Wed Feb 17 2021,-75,-80,0,20.5,21.1,9.39
Wed Feb 17 2021,-76,-80,0,20.5,21.1,9.39
Wed Feb 17 2021,-74,-80,0,20.5,21,9.28
Wed Feb 17 2021,-76,-81,0,20.5,21,9.39
Wed Feb 17 2021,-73,-79,0,20.5,21,9.28
Wed Feb 17 2021,-74,-79,0,20.5,21,9.28
Wed Feb 17 2021,-78,-79,0,20.5,21,9.28
Wed Feb 17 2021,-73,-80,0,20.5,21,9.28
Wed Feb 17 2021,-73,-78,0,20.5,21,9.22
Wed Feb 17 2021,-74,-79,0,20.5,21,9.22
Wed Feb 17 2021,-77,-80,0,12,21,9.22
Thu Feb 18 2021,-76,-80,0,12,21,9.22
Thu Feb 18 2021,-76,-78,0,12,21,9.22
Thu Feb 18 2021,-72,-77,0,12,21,9.22
Thu Feb 18 2021,-71,-76,0,12,21,9.22
Thu Feb 18 2021,-75,-80,0,12,21,9.22
Thu Feb 18 2021,-75,-80,0,12,21,9.22
Thu Feb 18 2021,-73,-79,0,12,21,9.22
Thu Feb 18 2021,-75,-80,0,12,21,9.22
Thu Feb 18 2021,-73,-79,0,12,21,9.11
Thu Feb 18 2021,-73,-78,0,12,21,9.11
Thu Feb 18 2021,-77,-82,0,12,21,9.11
Thu Feb 18 2021,-73,-78,0,12,21,9.11
Thu Feb 18 2021,-72,-76,0,12,21,9
Thu Feb 18 2021,-81,-82,0,12,21,9
Thu Feb 18 2021,-73,-79,0,12,21,9.11
Thu Feb 18 2021,-73,-79,0,12,21,9.11
Thu Feb 18 2021,-74,-78,0,12,21,9.11
Thu Feb 18 2021,-76,-81,0,12,21,9.11
Thu Feb 18 2021,-76,-81,0,12,21,9.11
Thu Feb 18 2021,-76,-82,0,12,21,9
Thu Feb 18 2021,-77,-79,0,12,21,9
Thu Feb 18 2021,-74,-76,0,12,21,8.89
Thu Feb 18 2021,-74,-78,0,12,21,8.78
Thu Feb 18 2021,-73,-79,0,12,21,8.78
Thu Feb 18 2021,-73,-76,0,12,20.9,8.78
Thu Feb 18 2021,-73,-79,0,12,20.8,8.78
Thu Feb 18 2021,-74,-78,0,12,20.8,8.78
Thu Feb 18 2021,-73,-78,0,12,20.8,8.72
Thu Feb 18 2021,-71,-78,0,12,20.8,8.72
Thu Feb 18 2021,-71,-76,0,12,20.7,8.72
Thu Feb 18 2021,-72,-78,0,12,20.7,8.72
Thu Feb 18 2021,-73,-78,0,12,20.7,8.72
Thu Feb 18 2021,-73,-78,0,12,20.6,8.72
Thu Feb 18 2021,-74,-78,0,12,20.6,8.61
Thu Feb 18 2021,-73,-81,0,12,20.6,8.61
Thu Feb 18 2021,-73,-78,0,12,20.6,8.61
Thu Feb 18 2021,-73,-78,0,12,20.5,8.61
Thu Feb 18 2021,-73,-79,0,12,20.5,8.5
Thu Feb 18 2021,-73,-78,0,12,20.5,8.5
Thu Feb 18 2021,-72,-77,0,12,20.5,8.5
Thu Feb 18 2021,-72,-77,0,12,20.4,8.5
Thu Feb 18 2021,-73,-77,0,12,20.4,8.5
Thu Feb 18 2021,-72,-77,0,12,20.4,8.5
Thu Feb 18 2021,-73,-79,0,12,20.4,8.39
Thu Feb 18 2021,-72,-77,0,12,20.4,8.39
Thu Feb 18 2021,-72,-77,0,12,20.3,8.5
Thu Feb 18 2021,-72,-77,0,12,20.3,8.5
Thu Feb 18 2021,-74,-77,0,12,20.3,8.5
Thu Feb 18 2021,-72,-77,0,12,20.3,8.5
Thu Feb 18 2021,-72,-77,0,12,20.3,8.61
Thu Feb 18 2021,-74,-77,0,12,20.3,8.72
Thu Feb 18 2021,-72,-77,0,12,20.2,8.72
Thu Feb 18 2021,-73,-78,0,12,20.2,8.72
Thu Feb 18 2021,-74,-78,0,12,20.2,8.72
Thu Feb 18 2021,-73,-81,0,12,20.2,8.61
Thu Feb 18 2021,-73,-78,0,12,20.1,8.5
Thu Feb 18 2021,-72,-77,0,12,20.1,8.5
Thu Feb 18 2021,-76,-77,0,12,20.1,8.39
Thu Feb 18 2021,-73,-78,0,12,20.1,8.28
Thu Feb 18 2021,-72,-77,0,12,20.1,8.22
Thu Feb 18 2021,-73,-78,0,12,20.1,8.22
Thu Feb 18 2021,-72,-78,0,12,20.1,8.28
Thu Feb 18 2021,-73,-78,0,12,20.1,8.28
Thu Feb 18 2021,-73,-78,0,12,20,8.28
Thu Feb 18 2021,-73,-78,0,12,20,8.28
Thu Feb 18 2021,-73,-78,0,12,20,8.28
Thu Feb 18 2021,-73,-79,0,12,20,8.28
Thu Feb 18 2021,-74,-78,0,12,20,8.39
Thu Feb 18 2021,-73,-78,0,12,20,8.39
Thu Feb 18 2021,-73,-78,0,12,20,8.39
Thu Feb 18 2021,-73,-79,0,12,20,8.5
Thu Feb 18 2021,-73,-79,0,12,19.9,8.5
Thu Feb 18 2021,-73,-78,0,12,19.9,8.5
Thu Feb 18 2021,-73,-78,0,12,19.9,8.39
Thu Feb 18 2021,-74,-78,0,12,19.9,8.39
Thu Feb 18 2021,-73,-78,0,12,19.9,8.39
Thu Feb 18 2021,-76,-78,0,12,19.9,8.39
Thu Feb 18 2021,-73,-78,0,12,19.9,8.39
Thu Feb 18 2021,-73,-79,0,12,19.8,8.5
Thu Feb 18 2021,-73,-78,0,12,19.8,8.5
Thu Feb 18 2021,-73,-78,0,12,19.9,8.61
Thu Feb 18 2021,-73,-77,0,12,19.8,8.61
Thu Feb 18 2021,-73,-78,0,12,19.8,8.61
Thu Feb 18 2021,-72,-77,0,12,19.8,8.72
Thu Feb 18 2021,-72,-78,0,12,19.8,8.72
Thu Feb 18 2021,-72,-78,0,12,19.8,8.72
Thu Feb 18 2021,-73,-77,0,12,19.8,8.72
Thu Feb 18 2021,-73,-79,0,12,19.8,8.72
Thu Feb 18 2021,-73,-79,0,12,19.8,8.72
Thu Feb 18 2021,-73,-78,0,12,19.8,8.72
Thu Feb 18 2021,-73,-77,0,12,19.7,8.72
Thu Feb 18 2021,-73,-78,0,12,19.7,8.89
Thu Feb 18 2021,-73,-78,0,12,19.7,9
Thu Feb 18 2021,-75,-78,0,12,19.7,9.11
Thu Feb 18 2021,-73,-77,0,12,19.7,9.22
Thu Feb 18 2021,-73,-79,0,12,19.7,9.22
Thu Feb 18 2021,-75,-78,0,12,19.7,9.22
Thu Feb 18 2021,-73,-78,0,12,19.7,9.22
Thu Feb 18 2021,-72,-78,0,12,19.7,9.28
Thu Feb 18 2021,-73,-78,0,12,19.7,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.7,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-72,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-80,0,12,19.6,9.28
Thu Feb 18 2021,-72,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.28
Thu Feb 18 2021,-73,-78,0,12,19.5,9.28
Thu Feb 18 2021,-73,-78,0,12,19.6,9.22
Thu Feb 18 2021,-74,-78,0,12,19.5,9.22
Thu Feb 18 2021,-73,-78,0,12,19.5,9.22
Thu Feb 18 2021,-75,-78,0,12,19.5,9.22
Thu Feb 18 2021,-73,-78,0,12,19.5,9.22
Thu Feb 18 2021,-73,-78,0,12,19.5,9.28
Thu Feb 18 2021,-73,-78,0,12,19.5,9.28
Thu Feb 18 2021,-74,-77,0,12,19.5,9.28
Thu Feb 18 2021,-75,-78,0,12,19.5,9.22
Thu Feb 18 2021,-73,-78,0,12,19.5,9.22
Thu Feb 18 2021,-73,-77,0,12,19.5,9.22
Thu Feb 18 2021,-73,-77,0,12,19.5,9.28
Thu Feb 18 2021,-73,-77,0,12,19.5,9.22
Thu Feb 18 2021,-73,-78,0,12,19.4,9.22
Thu Feb 18 2021,-72,-78,0,12,19.4,9.22
Thu Feb 18 2021,-72,-77,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-73,-77,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-74,-78,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-75,-79,0,12,19.3,9.11
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-72,-79,0,12,19.4,9.11
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.4,9.11
Thu Feb 18 2021,-72,-77,0,12,19.3,9.11
Thu Feb 18 2021,-73,-78,0,12,19.3,9.11
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-77,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.3,8.89
Thu Feb 18 2021,-73,-79,0,12,19.3,8.89
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.2,9
Thu Feb 18 2021,-74,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-78,0,12,19.3,9
Thu Feb 18 2021,-73,-79,0,12,19.3,9.11
Thu Feb 18 2021,-73,-78,0,12,19.3,9.11
Thu Feb 18 2021,-73,-77,0,12,19.2,9.11
Thu Feb 18 2021,-73,-78,0,12,19.2,9.11
Thu Feb 18 2021,-73,-79,0,12,19.2,9.11
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-79,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.22
Thu Feb 18 2021,-75,-78,0,12,19.2,9.22
Thu Feb 18 2021,-73,-78,0,12,19.2,9.11
Thu Feb 18 2021,-73,-77,0,12,19.2,9
Thu Feb 18 2021,-73,-80,0,12,19.2,8.89
Thu Feb 18 2021,-73,-78,0,12,19.2,8.78
Thu Feb 18 2021,-72,-77,0,12,19.2,8.78
Thu Feb 18 2021,-73,-78,0,12,19.1,8.78
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-76,-78,0,12,19.2,8.72
Thu Feb 18 2021,-72,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-72,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-72,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-77,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-74,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-76,-80,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19.1,8.72
Thu Feb 18 2021,-74,-78,0,12,19.1,8.72
Thu Feb 18 2021,-73,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19.1,8.78
Thu Feb 18 2021,-74,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-79,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-79,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.89
Thu Feb 18 2021,-74,-78,0,12,19,8.89
Thu Feb 18 2021,-73,-78,0,12,19,8.89
Thu Feb 18 2021,-74,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.78
Thu Feb 18 2021,-74,-81,0,12,19,8.78
Thu Feb 18 2021,-73,-78,0,12,19,8.72
Thu Feb 18 2021,-76,-79,0,12,19,8.72
Thu Feb 18 2021,-73,-78,0,12,19,8.61
Thu Feb 18 2021,-73,-78,0,12,19,8.61
Thu Feb 18 2021,-73,-78,0,12,19,8.5
Thu Feb 18 2021,-73,-78,0,12,18.9,8.5
Thu Feb 18 2021,-73,-78,0,12,19,8.39
Thu Feb 18 2021,-73,-79,0,12,19,8.39
Thu Feb 18 2021,-73,-78,0,12,18.9,8.39
Thu Feb 18 2021,-73,-78,0,12,18.9,8.5
Thu Feb 18 2021,-73,-79,0,12,18.9,8.5
Thu Feb 18 2021,-73,-78,0,12,18.9,8.5
Thu Feb 18 2021,-73,-77,0,12,18.9,8.61
Thu Feb 18 2021,-72,-78,0,12,18.9,8.61
Thu Feb 18 2021,-72,-77,0,12,18.9,8.61
Thu Feb 18 2021,-72,-77,0,12,18.9,8.5
Thu Feb 18 2021,-71,-78,0,12,18.9,8.5
Thu Feb 18 2021,-72,-77,0,12,18.9,8.5
Thu Feb 18 2021,-72,-77,0,12,18.9,8.5
Thu Feb 18 2021,-71,-76,0,12,18.9,8.5
Thu Feb 18 2021,-72,-76,0,12,18.9,8.5
Thu Feb 18 2021,-72,-77,0,12,18.9,8.5
Thu Feb 18 2021,-72,-77,0,12,18.9,8.5
Thu Feb 18 2021,-71,-77,0,12,18.9,8.5
Thu Feb 18 2021,-71,-77,0,12,18.9,8.5
Thu Feb 18 2021,-72,-77,0,12,18.9,8.61
Thu Feb 18 2021,-73,-76,0,12,18.9,8.61
Thu Feb 18 2021,-72,-77,0,12,18.9,8.61
Thu Feb 18 2021,-72,-77,0,12,18.9,8.61
Thu Feb 18 2021,-71,-77,0,12,18.9,8.61
Thu Feb 18 2021,-71,-76,0,12,18.9,8.61
Thu Feb 18 2021,-73,-78,0,12,18.9,8.72
Thu Feb 18 2021,-71,-76,0,12,18.9,8.72
Thu Feb 18 2021,-72,-77,0,12,18.9,8.72
Thu Feb 18 2021,-71,-77,0,12,18.9,8.72
Thu Feb 18 2021,-72,-77,0,12,18.9,8.72
Thu Feb 18 2021,-72,-77,0,12,18.9,8.72
Thu Feb 18 2021,-72,-76,0,12,19,8.72
Thu Feb 18 2021,-72,-77,0,12,19,8.78
Thu Feb 18 2021,-72,-76,0,12,19,8.78
Thu Feb 18 2021,-72,-77,0,12,19,8.78
Thu Feb 18 2021,-66,-77,0,12,19,8.89
Thu Feb 18 2021,-74,-77,0,12,19,8.89
Thu Feb 18 2021,-72,-77,0,12,19,9.11
Thu Feb 18 2021,-72,-77,0,12,19,9.22
Thu Feb 18 2021,-72,-77,0,12,19,9.28
Thu Feb 18 2021,-72,-77,0,12,19.1,9.39
Thu Feb 18 2021,-72,-77,0,12,19.1,9.5
Thu Feb 18 2021,-72,-78,0,12,19.1,9.72
Thu Feb 18 2021,-74,-79,0,12,19.2,9.89
Thu Feb 18 2021,-74,-79,0,12,19.2,10
Thu Feb 18 2021,-74,-80,0,12,19.2,10.11
Thu Feb 18 2021,-73,-79,0,12,19.2,10.11
Thu Feb 18 2021,-75,-79,0,12,19.2,10.11
Thu Feb 18 2021,-73,-80,0,12,19.3,10.11
Thu Feb 18 2021,-74,-80,0,12,19.4,10.11
Thu Feb 18 2021,-73,-78,0,12,19.4,10.22
Thu Feb 18 2021,-73,-78,0,12,19.4,10.28
Thu Feb 18 2021,-74,-78,0,12,19.4,10.5
Thu Feb 18 2021,-73,-78,0,12,19.5,10.61
Thu Feb 18 2021,-74,-78,0,12,19.7,10.61
Thu Feb 18 2021,-73,-77,0,12,19.9,10.78
Thu Feb 18 2021,-73,-79,0,12,20.2,11
Thu Feb 18 2021,-73,-78,0,12,20.4,11
Thu Feb 18 2021,-73,-78,0,12,20.8,11.11
Thu Feb 18 2021,-73,-78,0,12,21.2,11.22
Thu Feb 18 2021,-73,-77,0,12,21.5,11.22
Thu Feb 18 2021,-72,-78,0,12,21.8,11.28
Thu Feb 18 2021,-73,-79,0,12,21.8,11.22
Thu Feb 18 2021,-73,-78,0,12,21.8,11.22
Thu Feb 18 2021,-73,-77,0,12,21.8,11.28
Thu Feb 18 2021,-73,-78,0,12,21.9,11.28
Thu Feb 18 2021,-74,-78,0,12,21.8,11.22
Thu Feb 18 2021,-73,-79,0,12,21.7,11.22
Thu Feb 18 2021,-76,-79,0,12,21.6,11.28
Thu Feb 18 2021,-73,-79,0,12,21.5,11.39
Thu Feb 18 2021,-72,-77,0,12,21.4,11.5
Thu Feb 18 2021,-72,-77,0,12,21.2,11.5
Thu Feb 18 2021,-74,-80,0,12,21.2,11.39
Thu Feb 18 2021,-72,-78,0,12,21,11.28
Thu Feb 18 2021,-72,-77,0,12,20.9,11.28
Thu Feb 18 2021,-73,-78,0,12,20.8,11.22
Thu Feb 18 2021,-74,-78,0,12,20.7,11.22
Thu Feb 18 2021,-74,-79,0,12,20.6,11.22
Thu Feb 18 2021,-74,-79,0,12,20.5,11.22
Thu Feb 18 2021,-74,-79,0,12,20.5,11.11
Thu Feb 18 2021,-73,-78,0,12,20.4,11.11
Thu Feb 18 2021,-72,-77,0,12,20.3,11.11
Thu Feb 18 2021,-73,-78,0,12,20.3,11.11
Thu Feb 18 2021,-73,-78,0,12,20.2,11.22
Thu Feb 18 2021,-72,-77,0,12,20.2,11.28
Thu Feb 18 2021,-74,-78,0,12,20.2,11.28
Thu Feb 18 2021,-73,-78,0,12,20.1,11.28
Thu Feb 18 2021,-73,-78,0,12,20.1,11.28
Thu Feb 18 2021,-74,-78,0,12,20,11.28
Thu Feb 18 2021,-73,-78,0,12,20,11.22
Thu Feb 18 2021,-73,-80,0,20,20,11.22
Thu Feb 18 2021,-73,-78,0,20,19.9,11.11
Thu Feb 18 2021,-73,-78,0,20,19.9,11
Thu Feb 18 2021,-73,-79,0,20,19.9,10.78
Thu Feb 18 2021,-73,-78,0,20,19.9,10.61
Thu Feb 18 2021,-74,-78,0,20,19.9,10.5
Thu Feb 18 2021,-73,-78,0,20,19.9,10.5
Thu Feb 18 2021,-72,-77,0,20,19.9,10.39
Thu Feb 18 2021,-72,-77,0,20,19.9,10.39
Thu Feb 18 2021,-72,-77,0,20,19.9,10.39
Thu Feb 18 2021,-72,-79,0,20,19.9,10.39
Thu Feb 18 2021,-73,-77,20,20,19.8,10.39
Thu Feb 18 2021,-73,-78,20,20,19.8,10.28
Thu Feb 18 2021,-72,-77,0,20,19.9,10.28
Thu Feb 18 2021,-72,-77,20,20,19.8,10.22
Thu Feb 18 2021,-74,-77,0,18,19.9,10.22
Thu Feb 18 2021,-73,-78,0,18,19.8,10.22
Thu Feb 18 2021,-73,-77,0,18,19.9,10.22
Thu Feb 18 2021,-72,-78,0,18,19.8,10.11
Thu Feb 18 2021,-75,-77,0,18,19.8,10.11
Thu Feb 18 2021,-72,-78,0,18,19.8,10
Thu Feb 18 2021,-75,-78,0,18,19.9,10
Thu Feb 18 2021,-72,-78,0,18,19.8,10
Thu Feb 18 2021,-73,-78,0,18,19.9,10
Thu Feb 18 2021,-73,-78,0,18,19.8,9.89
Thu Feb 18 2021,-73,-78,0,18,19.8,9.89
Thu Feb 18 2021,-72,-77,0,18,19.9,9.78
Thu Feb 18 2021,-74,-78,0,18,19.9,9.89
Thu Feb 18 2021,-73,-78,0,18,19.9,9.78
Thu Feb 18 2021,-74,-78,0,18,19.9,9.72
Thu Feb 18 2021,-73,-78,0,18,19.9,9.72
Thu Feb 18 2021,-73,-78,0,18,19.9,9.72
Thu Feb 18 2021,-73,-78,0,18,19.9,9.61
Thu Feb 18 2021,-73,-78,0,18,19.9,9.61
Thu Feb 18 2021,-74,-79,0,18,19.9,9.61
Thu Feb 18 2021,-73,-79,0,18,19.8,9.61
Thu Feb 18 2021,-74,-79,0,18,19.8,9.5
Thu Feb 18 2021,-74,-79,0,18,19.8,9.5
Thu Feb 18 2021,-73,-79,0,18,19.8,9.5
Thu Feb 18 2021,-74,-79,0,18,19.8,9.5
Thu Feb 18 2021,-74,-80,0,18,19.8,9.61
Thu Feb 18 2021,-71,-77,0,18,19.8,9.5
Thu Feb 18 2021,-71,-76,0,18,19.8,9.39
Thu Feb 18 2021,-69,-73,0,18,19.8,9.39
Thu Feb 18 2021,-69,-74,0,18,19.8,9.28
Thu Feb 18 2021,-72,-76,0,18,19.8,9.28
Thu Feb 18 2021,-71,-77,0,18,19.8,9.28
Thu Feb 18 2021,-72,-75,0,18,19.8,9.39
Thu Feb 18 2021,-73,-77,0,18,19.8,9.39
Thu Feb 18 2021,-72,-77,0,18,19.8,9.28
Thu Feb 18 2021,-71,-76,0,18,19.9,9.28
Thu Feb 18 2021,-71,-77,0,18,19.9,9.28
Thu Feb 18 2021,-71,-77,0,18,19.9,9.28
Thu Feb 18 2021,-71,-76,0,18,19.9,9.39
Thu Feb 18 2021,-71,-77,0,18,19.9,9.39
Thu Feb 18 2021,-71,-76,0,18,19.9,9.39
Thu Feb 18 2021,-71,-77,0,18,19.9,9.39
Thu Feb 18 2021,-71,-76,0,18,19.9,9.39
Thu Feb 18 2021,-71,-75,0,18,19.9,9.5
Thu Feb 18 2021,-71,-76,0,18,19.9,9.5
Thu Feb 18 2021,-73,-77,0,18,19.9,9.5
Thu Feb 18 2021,-71,-77,0,18,19.9,9.5
Thu Feb 18 2021,-72,-77,0,18,19.9,9.5
Thu Feb 18 2021,-72,-78,0,18,19.9,9.5
Thu Feb 18 2021,-72,-77,0,18,19.9,9.61
Thu Feb 18 2021,-71,-76,0,18,19.9,9.61
Thu Feb 18 2021,-71,-76,0,18,19.9,9.5
Thu Feb 18 2021,-71,-76,0,18,19.8,9.5
Thu Feb 18 2021,-72,-77,0,18,19.8,9.39
Thu Feb 18 2021,-72,-77,0,18,19.8,9.28
Thu Feb 18 2021,-72,-78,0,18,19.8,9.28
Thu Feb 18 2021,-72,-77,0,18,19.8,9.39
Thu Feb 18 2021,-72,-77,0,18,19.8,9.39
Thu Feb 18 2021,-73,-77,0,18,19.8,9.28
Thu Feb 18 2021,-72,-77,0,18,19.8,9.22
Thu Feb 18 2021,-72,-77,0,18,19.8,9.11
Thu Feb 18 2021,-72,-77,0,18,19.8,9.11
Thu Feb 18 2021,-72,-77,0,18,19.8,9.11
Thu Feb 18 2021,-73,-78,0,18,19.8,9.11
Thu Feb 18 2021,-72,-79,0,18,19.8,9
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.78
Thu Feb 18 2021,-73,-78,0,18,19.8,8.78
Thu Feb 18 2021,-73,-78,0,18,19.8,8.78
Thu Feb 18 2021,-73,-80,0,18,19.8,8.78
Thu Feb 18 2021,-74,-80,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-73,-78,0,18,19.8,8.89
Thu Feb 18 2021,-74,-78,0,18,19.8,8.78
Thu Feb 18 2021,-73,-78,0,18,19.8,8.72
Thu Feb 18 2021,-73,-78,0,18,19.7,8.72
Thu Feb 18 2021,-73,-78,0,18,19.7,8.72
Thu Feb 18 2021,-74,-78,0,18,19.7,8.72
Thu Feb 18 2021,-73,-78,0,18,19.7,8.72
Thu Feb 18 2021,-73,-78,0,18,19.7,8.72
Thu Feb 18 2021,-76,-78,0,18,19.7,8.72
Thu Feb 18 2021,-73,-78,0,18,19.7,8.78
Thu Feb 18 2021,-73,-78,0,18,19.7,9.11
Thu Feb 18 2021,-73,-78,0,18,19.7,9.28
Thu Feb 18 2021,-73,-78,0,18,19.7,9.61
Thu Feb 18 2021,-73,-78,0,18,19.7,9.72
Thu Feb 18 2021,-73,-78,0,18,19.7,9.89
Thu Feb 18 2021,-73,-77,0,18,19.7,10
Thu Feb 18 2021,-72,-77,0,18,19.7,10
Thu Feb 18 2021,-73,-77,0,18,19.7,10.11
Thu Feb 18 2021,-72,-77,0,18,19.7,10
Thu Feb 18 2021,-72,-77,0,18,19.7,10.22
Thu Feb 18 2021,-72,-75,0,18,19.7,10.28
Thu Feb 18 2021,-73,-78,0,18,19.7,10.39
Thu Feb 18 2021,-73,-80,0,18,19.7,10.28
Thu Feb 18 2021,-73,-78,0,18,19.7,10.22
Thu Feb 18 2021,-73,-78,0,18,19.7,10.22
Thu Feb 18 2021,-73,-78,0,18,19.7,10.28
Thu Feb 18 2021,-72,-77,0,18,19.7,10.5
Thu Feb 18 2021,-72,-77,0,18,19.7,10.5
Thu Feb 18 2021,-72,-77,0,18,19.7,10.61
Thu Feb 18 2021,-71,-77,0,18,19.7,10.72
Thu Feb 18 2021,-73,-78,0,18,19.7,10.72
Thu Feb 18 2021,-73,-78,0,18,19.7,10.39
Thu Feb 18 2021,-73,-77,0,18,19.7,10.28
Thu Feb 18 2021,-72,-78,0,18,19.7,10.22
Thu Feb 18 2021,-73,-77,0,18,19.7,10.11
Thu Feb 18 2021,-72,-77,0,18,19.7,10
Thu Feb 18 2021,-72,-77,0,18,19.7,10.11
Thu Feb 18 2021,-72,-78,0,18,19.7,10.11
Thu Feb 18 2021,-72,-77,0,18,19.7,10.22
Thu Feb 18 2021,-72,-79,0,18,19.7,10.11
Thu Feb 18 2021,-72,-77,0,18,19.7,10.11
Thu Feb 18 2021,-73,-78,0,18,19.7,10.11
Thu Feb 18 2021,-72,-77,0,18,19.7,10
Thu Feb 18 2021,-72,-77,0,18,19.7,9.89
Thu Feb 18 2021,-72,-77,0,18,19.7,10
Thu Feb 18 2021,-73,-77,0,18,19.7,10.22
Thu Feb 18 2021,-72,-77,0,18,19.7,10.28
Thu Feb 18 2021,-72,-77,0,18,19.6,10.39
Thu Feb 18 2021,-72,-77,0,18,19.7,10.39
Thu Feb 18 2021,-72,-77,0,18,19.7,10.39
Thu Feb 18 2021,-72,-77,0,18,19.7,10.39
Thu Feb 18 2021,-75,-79,0,18,19.7,10.28
Thu Feb 18 2021,-71,-76,0,18,19.7,10.5
Thu Feb 18 2021,-72,-77,0,18,19.7,10.72
Thu Feb 18 2021,-71,-76,0,18,19.7,10.78
Thu Feb 18 2021,-71,-76,0,18,19.7,10.78
Thu Feb 18 2021,-72,-77,0,18,19.7,10.72
Thu Feb 18 2021,-74,-79,0,18,19.7,10.61
Thu Feb 18 2021,-75,-80,0,18,19.8,10.39
Thu Feb 18 2021,-72,-77,0,18,19.8,9.89
Thu Feb 18 2021,-74,-79,0,18,19.8,9.89
Thu Feb 18 2021,-73,-78,0,18,19.8,9.89
Thu Feb 18 2021,-74,-78,0,18,19.8,10
Thu Feb 18 2021,-72,-79,0,18,19.8,10.22
Thu Feb 18 2021,-72,-77,0,18,19.8,10.39
Thu Feb 18 2021,-72,-76,0,18,19.8,10.61
Thu Feb 18 2021,-73,-77,0,18,19.8,10.72
Thu Feb 18 2021,-73,-78,0,18,19.8,10.72
Thu Feb 18 2021,-73,-78,0,18,19.9,10.72
Thu Feb 18 2021,-72,-78,0,18,19.9,10.72
Thu Feb 18 2021,-72,-77,0,18,19.9,10.72
Thu Feb 18 2021,-74,-77,0,18,19.9,10.72
Thu Feb 18 2021,-71,-77,0,18,19.9,10.78
Thu Feb 18 2021,-73,-78,0,18,19.9,10.78
Thu Feb 18 2021,-72,-77,0,18,20,10.78
Thu Feb 18 2021,-73,-78,0,18,20,10.78
Thu Feb 18 2021,-72,-79,0,18,20,10.72
Thu Feb 18 2021,-72,-77,0,18,20,10.72
Thu Feb 18 2021,-72,-77,0,18,20,10.61
Thu Feb 18 2021,-73,-77,0,18,20,10.5
Thu Feb 18 2021,-75,-80,0,18,20,10.5
Thu Feb 18 2021,-75,-79,0,18,20,10.5
Thu Feb 18 2021,-75,-82,0,18,20.1,10.5
Thu Feb 18 2021,-73,-79,0,18,20.1,10.5
Thu Feb 18 2021,-72,-78,0,18,20.1,10.5
Thu Feb 18 2021,-74,-81,0,18,20.1,0
Thu Feb 18 2021,-72,-77,0,18,20.1,10.22
Thu Feb 18 2021,-70,-75,0,18,20.1,10.22
Thu Feb 18 2021,-72,-77,0,18,20.1,10.11
Thu Feb 18 2021,-71,-76,0,18,20.1,10.11
Thu Feb 18 2021,-71,-76,0,18,20.1,10.11
Thu Feb 18 2021,-72,-77,0,18,20.2,9.89
Thu Feb 18 2021,-71,-76,0,18,20.2,9.89
Thu Feb 18 2021,-72,-76,0,18,20.2,9.89
Thu Feb 18 2021,-72,-77,0,18,20.2,9.89
Thu Feb 18 2021,-71,-76,0,18,20.2,9.78
Thu Feb 18 2021,-73,-76,0,18,20.2,9.78
Thu Feb 18 2021,-74,-78,0,18,20.2,9.72
Thu Feb 18 2021,-74,-79,0,18,20.2,9.72
Thu Feb 18 2021,-75,-80,0,18,20.2,9.72
Thu Feb 18 2021,-75,-82,0,18,20.2,9.72
Thu Feb 18 2021,-77,-80,0,18,20.2,9.72
Thu Feb 18 2021,-76,-79,0,18,20.2,9.72
Thu Feb 18 2021,-76,-78,0,18,20.3,9.61
Thu Feb 18 2021,-70,-75,0,18,20.2,9.61
Thu Feb 18 2021,-77,-82,0,18,20.3,9.5
Thu Feb 18 2021,-71,-77,0,18,20.3,9.39
Thu Feb 18 2021,-71,-75,0,18,20.3,9.28
Thu Feb 18 2021,-71,-76,0,18,20.3,9.22
Thu Feb 18 2021,-72,-75,0,18,20.3,9.11
Thu Feb 18 2021,-70,-75,0,18,20.3,9.11
Thu Feb 18 2021,-71,-76,0,18,20.3,9.11
Thu Feb 18 2021,-71,-76,0,18,20.3,9
Thu Feb 18 2021,-71,-76,0,18,20.3,8.89
Thu Feb 18 2021,-71,-77,0,18,20.3,8.89
Thu Feb 18 2021,-73,-77,0,18,20.3,8.78
Thu Feb 18 2021,-72,-77,0,18,20.3,8.78
Thu Feb 18 2021,-72,-76,0,18,20.3,8.72
Thu Feb 18 2021,-71,-76,0,18,20.3,8.72
Thu Feb 18 2021,-72,-77,0,18,20.3,8.61
Thu Feb 18 2021,-72,-77,0,18,20.3,8.61
Thu Feb 18 2021,-71,-76,0,18,20.3,8.5
Thu Feb 18 2021,-72,-77,0,18,20.3,8.5
Thu Feb 18 2021,-70,-76,0,18,20.3,8.5
Thu Feb 18 2021,-69,-74,0,18,20.4,8.39
Thu Feb 18 2021,-70,-74,0,18,20.3,8.39
Thu Feb 18 2021,-72,-77,0,18,20.3,8.28
Thu Feb 18 2021,-72,-77,0,18,20.4,8.28
Thu Feb 18 2021,-71,-76,0,18,20.4,8.22
Thu Feb 18 2021,-69,-76,0,18,20.4,8.22
Thu Feb 18 2021,-72,-75,0,18,20.4,8.11
Thu Feb 18 2021,-74,-79,0,18,20.4,8.11
Thu Feb 18 2021,-71,-74,0,18,20.4,8.11
Thu Feb 18 2021,-73,-77,0,18,20.4,8.11
Thu Feb 18 2021,-71,-76,0,18,20.4,8.11
Thu Feb 18 2021,-72,-77,0,20.5,20.5,8.11
Thu Feb 18 2021,-73,-77,0,20.5,20.5,8
Thu Feb 18 2021,-72,-76,0,20.5,20.5,7.89
Thu Feb 18 2021,-72,-78,0,20.5,20.5,7.89
Thu Feb 18 2021,-74,-79,0,20.5,20.5,7.78
Thu Feb 18 2021,-72,-78,0,20.5,20.5,7.78
Thu Feb 18 2021,-74,-79,0,20.5,20.5,7.78
Thu Feb 18 2021,-76,-81,0,20.5,20.6,7.78
Thu Feb 18 2021,-72,-77,0,20.5,20.6,7.78
Thu Feb 18 2021,-72,-76,0,20.5,20.6,7.72
Thu Feb 18 2021,-72,-77,0,20.5,20.6,7.72
Thu Feb 18 2021,-71,-76,0,20.5,20.6,7.72
Thu Feb 18 2021,-70,-75,0,20.5,20.7,7.72
Thu Feb 18 2021,-73,-78,0,20.5,20.7,7.72
Thu Feb 18 2021,-73,-77,0,20.5,20.7,7.61
Thu Feb 18 2021,-73,-78,0,20.5,20.7,7.61
Thu Feb 18 2021,-72,-77,0,20.5,20.7,7.61
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.5
Thu Feb 18 2021,-74,-79,0,20.5,20.8,7.5
Thu Feb 18 2021,-72,-80,0,20.5,20.8,7.5
Thu Feb 18 2021,-71,-76,0,20.5,20.8,7.5
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.5
Thu Feb 18 2021,-72,-76,0,20.5,20.8,7.5
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.5
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.39
Thu Feb 18 2021,-71,-76,0,20.5,20.8,7.39
Thu Feb 18 2021,-71,-76,0,20.5,20.8,7.39
Thu Feb 18 2021,-73,-77,0,20.5,20.8,7.39
Thu Feb 18 2021,-72,-78,0,20.5,20.8,7.39
Thu Feb 18 2021,-71,-76,0,20.5,20.8,7.39
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.39
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.39
Thu Feb 18 2021,-71,-76,0,20.5,20.8,7.28
Thu Feb 18 2021,-70,-77,0,20.5,20.8,7.28
Thu Feb 18 2021,-72,-77,0,20.5,20.8,7.28
Thu Feb 18 2021,-70,-75,0,20.5,20.9,7.28
Thu Feb 18 2021,-71,-76,0,20.5,20.9,7.28
Thu Feb 18 2021,-71,-77,0,20.5,20.9,7.28
Thu Feb 18 2021,-72,-77,0,20.5,20.9,7.22
Thu Feb 18 2021,-71,-76,0,20.5,20.9,7.22
Thu Feb 18 2021,-72,-77,0,20.5,20.9,7.22
Thu Feb 18 2021,-73,-78,0,20.5,20.9,7.22
Thu Feb 18 2021,-74,-79,0,20.5,21,7.22
Thu Feb 18 2021,-74,-79,0,20.5,21,7.22
Thu Feb 18 2021,-73,-79,0,20.5,21,7.22
Thu Feb 18 2021,-72,-78,0,20.5,21,7.22
Thu Feb 18 2021,-76,-78,0,20.5,21,7.22
Thu Feb 18 2021,-73,-78,0,20.5,21,7.22
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7.11
Thu Feb 18 2021,-73,-77,0,20.5,21.1,7.11
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7
Thu Feb 18 2021,-73,-77,0,20.5,21.1,7.11
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7.11
Thu Feb 18 2021,-73,-78,0,20.5,21.1,7.11
Thu Feb 18 2021,-72,-78,0,20.5,21.1,7
Thu Feb 18 2021,-73,-77,0,20.5,21.1,7.11
Thu Feb 18 2021,-73,-78,0,20.5,21.1,7.11
Thu Feb 18 2021,-72,-79,0,20.5,21.1,7.11
Thu Feb 18 2021,-73,-78,0,20.5,21.1,7.11
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7
Thu Feb 18 2021,-73,-79,0,20.5,21.1,7
Thu Feb 18 2021,-72,-77,0,20.5,21.1,7
Thu Feb 18 2021,-73,-78,0,20.5,21.1,7
Thu Feb 18 2021,-74,-80,0,20.5,21.1,7
Thu Feb 18 2021,-74,-79,0,20.5,21.1,7
Thu Feb 18 2021,-73,-78,0,20.5,21,6.89
Thu Feb 18 2021,-77,-81,0,20.5,21.1,6.89
Thu Feb 18 2021,-74,-80,0,20.5,21,6.89
Thu Feb 18 2021,-72,-77,0,20.5,21,6.78

well done


kube-prometheus integration

Describe the bug
I couldn't find a way for the Lens to use an existing prometheus installation. In other words, we have an installed kube-prometheus stack but no metrics are visible in the app. Metrics appear only after installing another prometheus stack in the lens-metrics namespace (using the button in the settings).
Expected behavior
Kontena Lens automatically (or with some extra configuration) should use an existing prometheus installation
Environment (please complete the following information):

Lens Version: 2.1.4
OS: Linnux
Installation method (e.g. snap or AppImage in Linux): AppImage

I think this is a pretty mandatory feature.
What's funny is I tried the install for Lens' own Prometheus, and every single node-exporter is pending because the port is already used on every single node. By the exact same deployment on another namespace, same for kube-state-metrics etc....
And, I'm still getting the metrics ! Because they're there and Lens' Prometheus is scraping them.
This thing needs to get debunked, it will also represent a real no-go for many users that you have to install workload that "duplicates" a very common in k8s-prometheus installation.

We don't have built-in feature for using existing prometheus with Kontena Lens app yet. This feature is coming soon and we suggest you wait for it unless you are K8S pro user. If you are pro, take a look at the manifests we are using to deploy metrics feature. Adjust to suit your needs: https://github.com/kontena/lens/tree/master/app/manifests/metrics
tl;dr; easy mode for configuring existing Prometheus setup is coming soon.

This feature is now out 🚀
To enable metrics along kube-prometheus, go to cluster settings and use monitoring/prometheus-k8s:9090 as prometheus service address.
To able to see all metrics on Lens dashboard you are required tweak prometheus labelings a bit:

To see node metrics properly, please add

    - action: replace
      regex: (.*)
      replacement: $1
      sourceLabels:
      - __meta_kubernetes_pod_node_name
      targetLabel: kubernetes_node

relabeling to node-exporter servicemonitor crd (for example kubectl edit -n monitoring servicemonitors node-exporter).

to see cluster's pod usage on cluster overview properly, please add metricsRelabeling to kubelet service monitor (kubectl edit -n monitoring servicemonitors node-exporter)

metricRelabelings:
    - action: replace
      sourceLabels:
      - node
      targetLabel: instance

Hey @nevalla, I have custom Prometheus installation (not kube-prometheus). Currently, the service is running like prometheus-service on port 8080 in monitoring namespace. I guess the way to add it to cluster settings would be `monitoring/prometheus-service:8080' correct?
Additionally, wanted to confirm the second part of adding the prometheus labelings. We have node-exporters running as daemons (not containers) for scaping node metrics. Any clue what would need to change for those configs? I am not sure where the metricsRelabelings part should be added

Here's some prometheus related docs related to lens: https://github.com/kontena/lens/blob/master/troubleshooting/custom-prometheus.md

Hi @jnummelin while they are helpful, they dont fit my use case since I am not using kube-prometheus or node exporter which the above documents suggest. I am using Node exporter as a service on the nodes itself, example - https://prometheus.io/docs/guides/node-exporter/
So far, I have not been able to use the above settings in my setup and Prometheus fails to understand the config (obvious cz the documentation for cluster's pod usage is not clear)

This feature is now out 🚀
To enable metrics along kube-prometheus, go to cluster settings and use monitoring/prometheus-k8s:9090 as prometheus service address.
To able to see all metrics on Lens dashboard you are required tweak prometheus labelings a bit:

To see node metrics properly, please add

    - action: replace
      regex: (.*)
      replacement: $1
      sourceLabels:
      - __meta_kubernetes_pod_node_name
      targetLabel: kubernetes_node

relabeling to node-exporter servicemonitor crd (for example kubectl edit -n monitoring servicemonitors node-exporter).

to see cluster's pod usage on cluster overview properly, please add metricsRelabeling to kubelet service monitor (kubectl edit -n monitoring servicemonitors node-exporter)

metricRelabelings:
    - action: replace
      sourceLabels:
      - node
      targetLabel: instance

It would be great to be more specific. I've been playing around for 4h, after installing prometheus-operator, trying to figure out wath's need to be modified in the prometheus configuration.
Wath job need to be modified ? Is it in the prometheus config ? Do i place it randomly ?
My servicemonitor is named prometheus-operator-node-exporter , do i still need to modify it through the kubectl edit command ?

Lens supports now kube-prometheus out of the box and should not require additional configuration.

Still does not work out of the box when using kube-prometheus-stack helm installation.

Still does not work out of the box when using kube-prometheus-stack helm installation.

Similar issue for me, used kube-prometheus-stack and could not get any metrics

Still does not work out of the box when using kube-prometheus-stack helm installation.

Similar issue for me

Still does not work out of the box when using kube-prometheus-stack helm installation.

Similar issue for me, used kube-prometheus-stack and could not get any metrics

Same

Same on Kind, doesn't work. Metrics server deployed but Lens ignores the setting.

Just want to leave a comment on this issue since I ran into it.
Lens version 4.0.8
Prometheus setup : Prometheus Operator
To get metrics to show up in Lens: go to cluster->settings
Under Prometheus drop down choose " Prometheus Operator" NOT "Auto detect"
It works for me after this fix

Just want to leave a comment on this issue since I ran into it.
Lens version 4.0.8
Prometheus setup : Prometheus Operator
To get metrics to show up in Lens: go to cluster->settings
Under Prometheus drop down choose " Prometheus Operator" NOT "Auto detect"
It works for me after this fix

Wanted to share what worked for me Using Helm Chart : prometheus-operator
Lens version 4.0.8
Under Settings Add the following
Prometheus Service Address : [namespace]/prometheus-operated:9090
Prometheus installation method : Helm
With the above you will be able to see only Requests and Limits for CPU and Memory but not Node's usage
To see Cluster's Pod  usage and node metrics properly
Changes need to be made in ServiceMonitor CRD

In 'node-exporter' ServiceMonitor  Add (Under spec: then endpoints:)
relabelings:
- action: replace
regex: (.*)
replacement: $1
sourceLabels:
- __meta_kubernetes_pod_node_name
targetLabel: kubernetes_node

In 'Kubelet' ServiceMonitor add (Under spec: then endpoints:)
metricRelabelings:
- action: replace
sourceLabels:
- node
targetLabel: instance

All metrics are shown perfectly after this fix

Same problem here.
I used (installed)

kube-prometheus-stack 13.13.0

(https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)

lens 4.1.3

and I added extra configuration following
https://github.com/lensapp/lens/blob/master/troubleshooting/custom-prometheus.md
and all resource appear well

and I set lens configuration like this

but still metric didn't appear.... (infinitely loading)

How can I solve this problem..?!

@socar-hardy probably related to a private GKE, see discussion here: https://github.com/lensapp/lens/issues/1731#issuecomment-779196430

I was experiencing the same issue with kube-prometheus-stack but got it working today. I believe my issue was that I was overriding the namespace in which kube-state-metrics was installing (which I did to try to get "Advanced Metrics" in the Digital Ocean UI). Here's me config which is working:
# values.yaml
kubelet:
  serviceMonitor:
    https: false
    metricRelabelings:
    - action: replace
      sourceLabels:
      - node
      targetLabel: instance

nodeExporter:
  serviceMonitor:
    relabelings:
      - action: replace
        regex: (.*)
        replacement: $1
        sourceLabels:
        - __meta_kubernetes_pod_node_name
        targetLabel: kubernetes_node

# helmfile.lock (just to display the helm release version
- name: kube-prometheus-stack
  repository: https://prometheus-community.github.io/helm-charts
  version: 13.13.1

Lens config:

Setup:
Kubernetes on Digital Ocean
Kube Prometheus Stack

Ehh. UPDATE: I was getting cluster level metrics with the above configuration but not pod level metrics. Turns out removing the custom config in values.yaml resultet in pod level metrics as well. I believe that means that for me, leaving all settings alone works and my problem was trying to override the kube-state-metrics namespace. I could even set Lens to Auto-Detect my prometheus installation and it still worked.

I used the loki-stack helm chart from https://grafana.github.io/loki/charts to setup a full PLG stack.  Here is my final configuration that works with all Lens metrics:
grafana:
  enabled: true
  persistence:
    enabled: true
    storageClassName: default
prometheus:
  enabled: true
  alertmanager:
    persistentVolume:
      storageClass: default
  server:
    persistentVolume:
      storageClass: default
    global:
      scrape_interval: 30s
  kubelet:
    serviceMonitor:
      relabelings:
      - action: replace
        regex: (.*)
        replacement: $1
        sourceLabels:
        - __meta_kubernetes_pod_node_name
        targetLabel: kubernetes_node
      metricRelabelings:
      - action: replace
        sourceLabels:
        - node
        targetLabel: instance

We had a requirement to get this working via terraform for our AKS clusters and were successful using 2 steps,
step 1 - terraform
resource "helm_release" "monitoring" {
atomic = true
chart = "kube-prometheus-stack"
name = "kube-prometheus-stack"
create_namespace = true
namespace = "lens-metrics"
repository = "https://prometheus-community.github.io/helm-charts/"
timeout = 180
wait = true
set {
name  = "rbacEnable"
value = "false"
}
depends_on = [
azurerm_kubernetes_cluster.azure,
]
}
Step 2 - change cluster setting in lens IDE
In the lens IDE we also needed the extra bit mentioned by @Supesharisuto which was,
To get metrics to show up in Lens: go to cluster -> settings Under Prometheus drop down choose " Prometheus Operator" NOT "Auto detect"

After that metrics started showing

Unable to get metrics working here either.
How does lens query metrics behind the scenes? I have a basic kube-prometheus setup on EKS, followed https://github.com/lensapp/lens/blob/master/troubleshooting/custom-prometheus.md as well.

I was having issues as well and was able to get mine working.
To investigate, check out this file for the queries they're using. Note that's the default "Lens" provider, but you may be using the Helm or Operator providers. Just check the other files to be sure. If you want to see how they set up their built-in prometheus feature, check out this configmap. In my case, I needed to add a little snippet to my node-exporter job.
- action: replace
   source_labels:
   - __meta_kubernetes_pod_node_name
   target_label: kubernetes_node

I'm still having this issue using kube-prometheus-stack. After editing the node-exporter ServiceMonitor CRD, the pod-level statistics work flawlessly. Sadly, no matter what i do, i never seem to get the node/cluster level statistics to display anything. It always shows the "Metrics are not availabe...." error message.
Interestingly, auto-detect works in my case (like it did for @jgrau)

Update: It works using Lens 5.2.7. Additionally, i had to move from using kube-prometheus-stack to using the prometheus operator. Reporting works now. Only issue is that the CPU Usage is displayed as 0.00 in the gauge. In the graph, it is reported to be 0.8.

Current versions 5.3.3 works for me with Prometheus 4.12.0 helm chart and setting the metrics detection to helm in cluster settings. Auto detection did not work! Curiously, Using Prometheus 15.x.x did not work for me. The same is true with current versions of kube-prometheus-stack. Grafana boards are filled. I also can see metrics in kubectl top nodes or kubectl top pod, but not in the Lens app. So, I'll stick with Prometheus 4.12.0 for the moment. My cluster is purely educational, anyway.

seems like this was fixed in #4617. Hopefully everything will work in the next version :)

Prometheus 5 metrics are not displayed in Lens 5.4.6 for me.

What worked partly for me was some part of https://github.com/lensapp/lens/issues/4435#issuecomment-1129179399
I put the following in a custom values.yaml:
prometheus:
  monitor:
    enabled: false
    metricRelabelings:
      - action: replace
        regex: (.*)
        replacement: $1
        sourceLabels:
          - __meta_kubernetes_pod_node_name
        targetLabel: kubernetes_node

Then I installed the metrics-server via prometheus chart:
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update
helm install  kube-metrics prometheus-community/kube-state-metrics -f values.yaml

After that, I installed prometheus:
helm repo addrometheus-community https://prometheus-community.github.io/helm-charts/
helm repo update
helm install --set server.global.scrape_interval=30srometheusrometheus-community/prometheus --version=15.8.7'"

But with this I only see the memory usage on nodes, no disk or cpu. Also, I have to tell Lens that prometheus metrics have been installed with helm. Neither the operator or auto detection settings work. Better than nothing, but not perfect. Ultimately, I reverted back to prometheus 4.12.0 because that still works out of the box.


ServiceAccount can't be created if not using ingressController

Hi,
I have a problem because I use the serviceAccount but I don't use IngressController. And with the last changes, It's impossible to use it. Also I need to mount the token because I use vault-secret-webhook and for this is necessary. Can be this optional and enable it by any environment?
Is there any workaround to fix it?
Thanks

Which change did you see cause this, or what chart versions did you upgrade to/from that you saw this break?
There are conditions that gate the creation of the ServiceAccount, but they've always been in place and haven't changed in quite some time.
We'd be open to accepting a PR that makes it independent of the controller and PSP. The tricky part is making it compatible with the existing configuration under the ingressController section--we wouldn't want to interfere with that and break existing configuration on upgrades.
If you decide to add a PR, I'd suggest creating a new serviceAccount section under the deployment section of values.yaml with the same contents as the existing section, but with create set to false.
You can then create a helper function in _helpers.tpl that renders either the original ServiceAccount (from the configuration under ingressController), the new one if enabled (i.e. if it has either create: true or its name field set), or an empty string if neither are enabled, and replace the existing serviceAccountName blocks (e.g. https://github.com/Kong/charts/blob/kong-2.2.0/charts/kong/templates/migrations.yaml#L42-L44 and https://github.com/Kong/charts/blob/kong-2.2.0/charts/kong/templates/deployment.yaml#L62-L64) with that helper.
That pattern should allow you to configure a ServiceAccount independently while maintaining compatibility with existing configuration.

Hi, the problem I have is that I need the automountServiceAccountToken enabled without enabling ingressController
Could be something like:
...
ingressController:
  enabled: false
...
  serviceAccount:
    # Specifies whether a ServiceAccount should be created
    create: true
    # The name of the ServiceAccount to use.
    # If not set and create is true, a name is generated using the fullname template
    name:
    # The annotations for service account
    annotations: {}
    automountServiceAccountToken: true
...

Thanks!

Hi,
I am looking for the same feature to allow the chart to create a service account, and I do agree @rainest comment, but is the code below a bit confusing and related to @ichasco-heytrade comment ?
{{- define "kong.serviceAccountName" -}} {{- if .Values.ingressController.serviceAccount.create -}}     {{ default (include "kong.fullname" .) .Values.ingressController.serviceAccount.name }} {{- else -}}     {{ default "default" .Values.ingressController.serviceAccount.name }} {{- end -}} {{- end -}}
We might rename the helper kong.serviceAccountName to kong.ingressController.serviceAccountName to allow the addition of a feature to create a serviceAccount for Kong ?
Thanks.

@ludovic-pourrat not sure what's confusing in the snippet. It's just determining the account name based on the combination of the create and name settings, either returning the name you set or a default name. The path that uses default as the name if you set create off but don't provide a name is a bit odd, but whatever.
We'd keep the single kong.serviceAccountName function, since the proposed change here wouldn't create an additional, separate account: you can only have the one ServiceAccount bound to the Pod (which contains both Kong and the controller), so you wouldn't get two accounts, one for the controller and one for Kong.
The change I'm suggesting is that you create a new section of values.yaml to configure the existing account: since the account is used by the entire Pod and not just the controller, it doesn't really make sense to configure it under the controller settings. Since it's effectively a Deployment-wide setting (Pod-wide, but we don't make the distinction), this would make more sense:
deployment:
  serviceAccount:
    create: false
    name:
    annotations: {}

We don't want to break existing configuration, however, so we'd keep the section under ingressController for now and still honor it if has non-default settings. The kong.serviceAccountName would return, in order of precedence:

ingressController.serviceAccount.name
deployment.serviceAccount.name
(include "kong.fullname" .) if create=true or default if create=false

Effectively, use the name from the ingressController section if it's set, since only users who'd intentionally changed the default in the past would have a value there. Annotations would be handled similarly, where we'd use the ingressController section value if set to anything other than the default empty object.
That allows us to smoothly transition to the new setting location without breaking existing configurations. We'd eventually deprecate and then remove the old location.

@rainest got it now! I was missing your point mainly because we deploy the ingress controller alone in one instance of the chart, separately from both the control plane and the data plane.
We might revert back then this approach and couple the ingress controller to the control plane helm chart instance.
The reason behind this request was because of our integration to the Vault injector agent, requiring us to have serviceAccount in place for granting access to the related Vault secrets.
Your proposal for setting up the serviceAccount name is ok for me. I will investigate a solution following that path and will advise accordingly.
Thanks.

@rainest, according to your feedback and proposal, this should look like this
For the values.yaml
deployment:   serviceAccount:     create: false     name:      annotations: {}
For the helper
{{/* Create the name of the service account to use */}} {{- define "kong.serviceAccountName" -}} {{- if .Values.ingressController.serviceAccount.name -}} {{- if .Values.ingressController.serviceAccount.create -}}     {{ default (include "kong.fullname" .) .Values.ingressController.serviceAccount.name }} {{- else -}}     {{ default "default" .Values.ingressController.serviceAccount.name }} {{- end -}} {{- else -}} {{- if .Values.deployment.serviceAccount.create -}}     {{ default (include "kong.fullname" .) .Values.deployment.serviceAccount.name }} {{- else -}}     {{ default "default" .Values.deployment.serviceAccount.name }} {{- end -}} {{- end -}} {{- end -}}
and an additional service-account.yaml template as follow
{{- if or .Values.podSecurityPolicy.enabled (and .Values.deployment.enabled .Values.deployment.serviceAccount.create) -}} apiVersion: v1 kind: ServiceAccount metadata:   name: {{ template "kong.serviceAccountName" . }}   namespace: {{ template "kong.namespace" . }}   {{- if .Values.ingressCondeploymenttroller.serviceAccount.annotations }}   annotations:   {{- range $key, $value := .Values.deployment.serviceAccount.annotations }}     {{ $key }}: {{ $value | quote }}   {{- end }}   {{- end }}   labels:     {{- include "kong.metaLabels" . | nindent 4 }} {{- end -}}
I will test this approach.
Thanks

@ludovic-pourrat checking in on this, would you be able to make a draft available? There was interest in this internally as well, since we need the token mounted for another of our products (Kuma) even when the controller isn't enabled, so if it's more or less ready we'd be interested in helping test it/work out any issues before merging it in.

@rainest yes I will proceed in the next 48h.

we also notice this behaviour... where we have to forcefully create the SA before the migrations.. otherwise they wont start.. impacting how kong can actually automatically deployed and managed by ArgoCD

So after playing around with options for the templates, I've concluded that there really isn't anything that'd support either configuration without making the template logic convoluted and verbose, so we may as well make an immediate breaking change with a warning if you've set either of the overrides in the ingressController config.
@ludovic-pourrat would you be able to reopen the PR and cherry-pick https://github.com/Kong/charts/pull/455/commits/24d185c2b8287f75ab2c19663af29fa02e15523f into it? I can open my own with content from your branch, but wanted to make sure you got credit for the PR.

Handled by #455

Nice work thanks a lot !


feat(members): add gradient to members list

Adds a gradient to the right and left side in the members scroll list.
Also removes the marginRight from the last avatar in the list.

This looks outstanding! Thanks so much @ocarreterom!!


Make Light Mode and Dark Mode buttons sticky

Description
I think the light mode and dark mode button should be sticky on the right most upper side of the page. I had to scroll down all the way to footer, every time I wanted to switch the theme.
I'd like to know your thoughts about this.
Screenshots
No response
Additional information
No response

can i work on this issue?

I'm not a maintainer @NextThread, You should ask @eddiejaoude or any other maintainer.

hey @NextThread, can I work on this issue? Will do the PR soon. Thankyou!

Just for my understanding, do you want to bring the switcher to the navbar, or do you want to rework the navbar?
I think when bringing the switcher to the top we also need to rework it, so it doesn't use that much space in the header

I think making it sticky at the bottom would be good, as there will be too many things on the top right side.

I think the themes are generally at the top of the page to ensure visibility for users.
@eddiejaoude @Cahllagerfeld, I kindly request your review of the pull request associated with issue #395. Additionally, please advise if any adjustments are needed in the navbar

Hey @namrata18s  and @immortalAbdul01 to me it's still not 100% clear how this should be have given me keep it in the footer. Will we need a sticky footer then, or did you imply something else with your idea?


add farmer's delight support

Looks good. I'll merge in a sec.

noo forgot to add farmersdelight to the fabric.mod.json :(((

not like suggest does anything tho...


Add new document to talk about extra sphinx tips

Provide a place for sphinx/reStructuredText information that doesn't belong in README or CONTRIBUTING
See

https://github.com/aiven/devportal/blob/tibs-sphinx-tips/SPHINX-TIPS.rst
https://github.com/aiven/devportal/blob/tibs-sphinx-tips/README.rst
https://github.com/aiven/devportal/blob/tibs-sphinx-tips/CONTRIBUTING.rst

Suggesting a different name of the new file, or deciding the text belongs in an existing file instead, is definitely in scope for this PR.
Fix: https://github.com/aiven/devportal/issues/712

How about sharing the documentation about our documentation as part of our documentation? I know you like documentation!
(I'd also like to discuss/review some of these new tips) I think using the existing platform could make content more findable rather than in the buckets of randomness as it is right now, README and CONTRIBUTING are already fairly epic, we're adding these tips plus additional contribution approaches .... let's use something bookmarkable/linkable/navigable and nice to look at

@TibsAtWork are you going to work on Lorna's comment?

I'm happy if you want to take it on, @ftisiot - I don't think I'd get round to it in the next couple of days.

Following @lornajane's comment, I put the Tips&tricks in the same format as our devportal under a "Documentation" section.
Could you please review and comment, I feel this is far from perfect

I thin this is also already good. However, we discussed the redirection today and I wonder if we can make a note not encouraging contributors to make redirection only if really needed it. I am not sure what would be the criteria here.


Add Didier Verkindt and Antoine Bernard to FRA-INP-S8 in groups.rst

Didier Verkindt (IN2P3/LAPP) will work with Dominique Boutigny (IN2P3/LAPP) on the TMA commissioning.
Antoine Bernard (IN2P3/LPSC) will work with Johan Bregeon (IN2P3/LPSC) and Fabio Hernandez (CC-IN2P3) on the profiling and optimization of the DRP pipeline.

Superseded by https://github.com/lsst-sitcom/sitcomtn-050/pull/64


How to display validation errors in the context of an Astronomy Model?

In the documentation, I have seen that in order to display errors you are using an Astronomy model:
{{#with post}}
<input type="text" name="title" />

{{getValidationError "title"}}

{{/with}}

My particular need is to know how to provide a User Astronomy model to my New User form in such a way that it will be empty of any validation errors when the form loads and would reactively display the errors when the model is validated?
I am able to do exactly what I've described above with the use of an extra Session variable but if feels "hacky"! I want to know how to do it properly.
Thanks for the amazing packages!  :+1:

You can do it in several ways. The one I've propose in the example app was here https://github.com/jagi/meteor-astronomy-examples/blob/master/client/routing.js#L31. However it's using routing. The better way for doing it would be using the onCreated hook of the template. One of the astronomy users posted such code, which seems to be very elegant way of doing it. It can look like this:
Template.InsertForm.onCreated(function() {
  this.user = new User();
});

Template.InsertForm.events({
  'change input': function(e) {
    var fieldValue = e.currentTarget.value;
    var fieldName = e.currentTarget.id;
    this.user.set(fieldName, fieldValue);
  }
});

And in template

{{user.getValidationError 'fieldName'}}

or
{{#with user}}

{{getValidationError 'fieldName'}}

{{/with}}

@jagi thanks for the quick reply, I tried the alternative you suggested but it didn't work for me so I went with the router option and now it works perfectly. The other thing I was looking for was to add custom messages to the validators that don't take a first argument, e.g. Validators.required(). Just tried Validators.required(null, "My Custom message") and it worked just fine.
I wanted to suggest that that should be in the documentation as well. Thanks again for your help!

Ok no problem :-). Yes I'm working on documentation to make it's more detailed. There will be separate website with docs only, similar to Meteor docs.


httplz: 1.5.0 -> 1.5.1

Motivation for this change
It's a minor update, it only updates the hyper-native-tls Rust dependency.
https://github.com/thecoshman/http/releases/tag/v1.5.1
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

nix path-info -Sh ./result
/nix/store/gfgd5kwpb6gxb1a61dlma71dyyqkhj73-httplz-1.5.0	  35.5M
nix path-info -Sh ./result
/nix/store/d3c2xzwynkwf8jlidp53psymqi5fx7bz-httplz-1.5.1	  35.5M
Notify maintainers

@GrahamcOfBorg build httplz

@mmahut thanks

@GrahamcOfBorg build httplz

Tyvm


Add Typescript support

Why this feature is required (specific use-cases will be appreciated)?
When using Typescript in strict mode, the code will not compile because TS definitions are not present.
Have you tried any other work arounds?
I have tried looking up definitions in DefinitelyTyped repository but it's not there.
Are you willing to work on it with little guidance?
Maybe.

The source code is written in typescript. So I am not sure why separate typings are required?

@thetutlage Ok. I am unsure if I'm installing @adonisjs/fold package correctly then. When I do npm i @adonisjs/fold, version 4.0.9 gets installed. That version is written in JavaScript thus TSC complains about missing definitions.

Are you using it with Adonisjs or outside of it?

I’m using it as a standalone package.

Okay, then I suggest installing with @alpha tag.
npm i @adonisjs/fold@alpha

This gives you the latest version

Also don't get tripped with the @alpha tag. This is mainly relevant for AdonisJS. The package itself is stable

So is there a reason why NPM default version is not the newer one? It’s not considered stable?

The default version is used by many of the AdonisJS v4 apps in production. The @alpha version is targeting v5 of the framework and is a complete rewrite.
I do not want to break existing v4 applications. So thats why published it under a different tag.


Error (Errno::ENOENT)

I'm having this error, even though I have wget installed and the program used to work, I reinstalled everything from scratch but the error persists.

@jooito you have added wget to PATH environment variable (second item)?

Yes I did, as I said before, it was working before.
I proceeded to remove and add again before I reinstalled it.

After update the code as advised. I got another error


Update dependencies

I've tested it locally and everything worked as expected, even Webpack 4.1

Awesome thanks a lot! 🙏

Sorry that was a bit to quick.
I tested it locally and there are currently some issues.

https://github.com/Milanzor/webpack-watched-glob-entries-plugin/issues/1

Thanks! Will check that if I can fix/help with that issue.

Just a question: if I switch back to Webpack 3.x in my PR it should work, right?
Also, what issues did you encounter, so I can test it on my side as well?

Thanks a lot for helping out!
I created a new PR regarding Webpack 4.
Some external Webpack Plugins need to update first.
https://github.com/HaNdTriX/webextension-toolbox/pull/13

Just released Version 0.2.0

https://github.com/HaNdTriX/webextension-toolbox/releases/tag/v0.2.0
https://www.npmjs.com/package/webextension-toolbox

Awesome, many thanks!


Improve apply retry

This PR is mostly related to issues #82 and #87.

util.Retry was replaced by util.RetryOnError which is a copy of k8s.io/client-go/util/retry.OnError. It seems to be the standard way to do retries with newer versions of the k8s client library.
The two errors http2.GoAwayError and errors.StatusError with err.ErrStatus.Reason == metav1.StatusReasonServiceUnavailable are automatically retried.
List functions are also retried now

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

@kramerul Thank you for signing the Contributor License Agreement!

few comments:
IsRetryableErr was meant to represent error that could be retried at a higher level due to resource conflicts (ie one resource waiting for the other). i think we should keep it that way. http2 errors should be retried at a lower level and not leak out to higher level retry mechanisms.
i would also like to stick with util.Retry to keep things very simple for now.

IsRetryableErr should probably be renamed to something like IsResourceChangeBlockedErr to indicate better that resource change is blocked on somethign else in the system (like another resource being changed).

Hi @cppforlife,
I renamed IsRetryableErr to IsResourceChangeBlockedErr and reverted the usage of RetryOnError although in my point of view the code looked simpler and an exponential backoff is missing now.


Java SDK ReBAC support

make sure to merge #15 before merging, as #15 contains some things that were missing from this PR


Error messages not bubbled up to caller when making API calls via the sdk

[REQUIRED] Environment

Browser version: node.js, no browser
Alchemy SDK version: 3.2.0, but I suspect latest as well

[REQUIRED] Describe the problem
When making an sdk call to update webhook configuration (via sdk.notify.updateWebhook or sdk.notify.createWebhook), The error that is bubbled up to the caller has no information for the caller to know what the actual issue is.
Specifically, the message field on the error looks like 400: [Object object]
How to reproduce:
Because I can't see the underlying error, I don't know what I'm doing in my code that is causing an error, but one way to reproduce is to attempt to call sdk.notify.updateWebhook for an address activity webhook, with a set of newAddresses that is >= 35k in length. In this case, we get back Error: 503: [Object object] consistently.
Relevant code or sample repro:
I have a strong suspicion I have found the place in the code where this issue stems from:
https://github.com/alchemyplatform/alchemy-sdk-js/blob/5fdff2fb76dc668cf10be3dbf8955a6d92303414/src/internal/dispatch.ts#L58
From the axios docs, the response object that comes back from an axios call contains a data field that is an object, and so the construction of the error string in this line, which is currently:
lastError = new Error(response.status + ': ' + response.data);

Is broken because the stringification of response.data will always be [Object object]
I think this line needs to look like
lastError = new Error(response.status + ': ' + JSON.stringify(response.data));

or perhaps (from the axios docs)
lastError = new Error(response.status + ': ' + response.data.toJSON());

@TheWisestOne Thanks for posting the issue along with your detailed investigation! I tried reproducing the 503 error with the following code:
const addAddress = '0x7f268357A8c2552623316e2562D90e642bB538E5';
const addAddresses = new Array(36000).fill(addAddress);
try {
    await alchemy.notify.updateWebhook(addressWh, {
      addAddresses,
      removeAddresses: [removeAddress]
    });
  } catch (e: any) {
    console.log('found error', e.message);
  }

The resulting log prints:
  console.log
    found error 503: {"message":"Internal server error","name":"ServerError"}

The output is the same even if I use JSON.stringify(response.data)  on the line you mentioned. Can you share your code example?

Hmm, so the easiest place for me to repro was during webhook creation. The code that is executing on my deployed instance is compiled javascript, which looks like:
    try {         const webhook = await sdk.notify.createWebhook(webhookUrl, 'ADDRESS_ACTIVITY', {             addresses,         });     }     catch (error) {         logger_1.logger.error(error.message);         logger_1.logger.error(`Failed to create an address activity webhook with error: ${error}`);         return null;     }
here logger_1 is a simple winston logger that writes out to console.
The output here is:
  {"context":{},"level":"ERROR","logLevel":"ERROR","message":"400: [object Object]"}
{"context":{},"level":"ERROR","logLevel":"ERROR","message":"Failed to create an address activity webhook with error: Error: 400: [object Object]"}

so we can see that error.message is the string: 400: [object Object]
I will try to create a more isolated test-case, I just have to figure out how to do that with all the appropriate environment variables in place so I can run it locally


allowing any angular version greater than 13

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/ngneat/transloco/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
When we use any angular version > major release 13 it's like:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: <my super duper personnal project>@<version of my project>
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@ngneat/transloco-scoped-libs
npm ERR!   @ngneat/transloco-scoped-libs@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry

Issue Number: #646
What is the new behavior?
No log complaing we should force for scoped libs utils
Does this PR introduce a breaking change?
[ ] Yes
[X ] No

@dfa1234  This is actually an issue with the scoped-libs package build. since in the original package.json, you don't see any peerDeps.
This needs to be disabled at Nx level, you can see an example in other package configurations.
Try it

@shaharkazaz Thank to you
Lately now I'm really into Nx so here what I think you suggest do to.
The only problem is that when I'm doing npm run build:scoped-libs in your project,
and look in dist
I don't really see the same package.json that I get from npm when I download your library.
So I pressume I need to do something else than npm run build:scoped-libs to really see the final build that you  publish on npm

@dfa1234 I'm not sure I understand, the change you made should cover it.
npm run build:scoped-libs is what you need to run to see the npm build version, nothing else. share the package.json that you are getting.
make sure to run it before your change 🙂

@shaharkazaz
wonderfull, but I'm still affraid there is something I'm missing here.
I was so affraid of isue with nx cache (that I don't really want to use rn)
I did some tests for you with 2 clean install
My commands are:
rm -rf ~/.nx # just to be sure there is no cache here!
git clone git@github.com:ngneat/transloco.git
cd transloco/
npm i
npm run build:scoped-libs
cat dist/libs/transloco-scoped-libs/package.json # to see what we have here

WITHOUT ANY CHANGES
Here the result I have:
{
  "name": "@ngneat/transloco-scoped-libs",
  "version": "3.0.5",
  "description": "Transloco support tool for libraries with translations",
  "main": "src/lib/transloco-scoped-libs.js",
  "bin": {
    "transloco-scoped-libs": "src/index.js"
  },
  "publishConfig": {
    "access": "public"
  },
  "bugs": {
    "url": "https://github.com/ngneat/transloco/issues"
  },
  "homepage": "https://ngneat.github.io/transloco/docs/tools/scope-lib-extractor",
  "repository": {
    "type": "git",
    "url": "https://github.com/ngneat/transloco"
  },
  "keywords": [
    "angular",
    "angular 2",
    "i18n",
    "translate",
    "angular translate",
    "angular i18n",
    "transloco",
    "comments",
    "build",
    "optimize"
  ],
  "license": "MIT",
  "author": "Itay Oded",
  "contributors": [
    {
      "name": "Shahar Kazaz",
      "url": "https://github.com/shaharkazaz"
    },
    {
      "name": "Netanel Basal",
      "url": "https://netbasal.com"
    }
  ],
  "dependencies": {
    "@angular/animations": "16.0.4",
    "@angular/common": "16.0.4",
    "@angular/compiler": "16.0.4",
    "@angular/core": "16.0.4",
    "@angular/platform-browser": "16.0.4",
    "@angular/platform-browser-dynamic": "16.0.4",
    "@ngneat/transloco-utils": "^3.0.5",
    "chalk": "4.1.2",
    "chokidar": "3.5.2",
    "command-line-args": "5.2.0",
    "cosmiconfig": "8.1.3",
    "fs-extra": "9.1.0",
    "glob": "7.1.7",
    "rxjs": "7.8.0",
    "tslib": "2.3.1",
    "zone.js": "0.13.0"
  },
  "types": "./src/index.d.ts"
}

WITH MY CHANGE BEFORE
I added updateBuildableProjectDepsInPackageJson:false
before performing npm run build:scoped-libs
{
  "name": "@ngneat/transloco-scoped-libs",
  "version": "3.0.5",
  "description": "Transloco support tool for libraries with translations",
  "main": "src/lib/transloco-scoped-libs.js",
  "bin": {
    "transloco-scoped-libs": "src/index.js"
  },
  "publishConfig": {
    "access": "public"
  },
  "bugs": {
    "url": "https://github.com/ngneat/transloco/issues"
  },
  "homepage": "https://ngneat.github.io/transloco/docs/tools/scope-lib-extractor",
  "repository": {
    "type": "git",
    "url": "https://github.com/ngneat/transloco"
  },
  "keywords": [
    "angular",
    "angular 2",
    "i18n",
    "translate",
    "angular translate",
    "angular i18n",
    "transloco",
    "comments",
    "build",
    "optimize"
  ],
  "license": "MIT",
  "author": "Itay Oded",
  "contributors": [
    {
      "name": "Shahar Kazaz",
      "url": "https://github.com/shaharkazaz"
    },
    {
      "name": "Netanel Basal",
      "url": "https://netbasal.com"
    }
  ],
  "dependencies": {
    "@ngneat/transloco-utils": "^3.0.5",
    "chalk": "^4.1.2",
    "chokidar": "^3.5.2",
    "command-line-args": "^5.1.1",
    "glob": "^7.1.7",
    "fs-extra": "^9.1.0"
  },
  "types": "./src/index.d.ts"
}

Here what I have right now for you, maybe I will try to perform a complete build to see if it differ from this

The 2nd package seems correct.
What's the issue you are worried about? the change resolved the issue.
When these flags were added I guess the scoped libs got missed.

My concern is that the result with or without the flag slightly differ from what there is in npm right now:
package.json

I presume I need to build from the previous commit 6b0109c49336b20805b04c66257d26dd2311d60f
Now it's working great


Write a GitHub workflow to download the swagger.json from the server

We should be able to write a workflow relatively simply that turns on the VM, downloads the swagger, and creates a new branch and PR to merge the changes. We would then only have to worry about updating the VM and triggering the workflow.

As discussed during our 2024 R2 retrospective, it is now getting painful to have to manually create PRs every time the swagger definition updates. We need to prioritize this automation as part of the 2025 R1 release cycle, potentially for bomanalytics-openapi as well.

Resolved in internal repository.


Trivy reports a high severity vulnerability CVE-2018-8292

We are using self hosted action runners and kata containers are our main dependencies, so after upgrading to newer versions of packages also, i am facing this vulnerability.
Currently we are using Ubuntu 20.04 (Bionic),  By upgrading to Ubuntu 22.04 (Jammy) will this be fixed permanently, need your inputs.

@SiddarthaKura Hey! The CVE seems to be about .NET Core https://nvd.nist.gov/vuln/detail/CVE-2018-8292. The only thing in actions-runner that depends on .NET would be actions/runner. Are you basically saying that some versions of actions/runner are affected by the CVE?
If so, why does upgrading to Ubuntu 22.04 resolve that? 🤔 I'm quite lost.

Yes Yusuke, how do we resolve them? any mitigation steps

@SiddarthaKura Maybe file an issue in https://github.com/actions/runner if you thin actions/runner is affected by CVE? 🤔

@SiddarthaKura Does Trivy tell you exactly which file in the runner image is affected? If so, could you share it so that we can perhaps figure out how to fix it?

@SiddarthaKura How did you resolve your issue? Did my answer help?


some parts in explorer not being colored

hey! after installing almost everything was colored except for the selection in file explorer even though the pictures you provided it shows them colored.

It colorizes only that elements, that is colored, usually with blue. Selection highlight are grey - this is intended design choice by Microsoft to ensure there's enough contrast with background, so it should not be colorized.


Python doc blocks are yellow with Nord color scheme

I have neovim nightly and the most up to date version of nvim-treesitter and this plugin. For some reason, Python doc blocks are highlighted in yellow (#ffff00), which I'm pretty sure isn't intended. Otherwise, everything seems to be highlighted correctly.
What can I do to fix this, and what other information should I provide?
I'd wager the problem is in these lines: https://github.com/ChristianChiarulli/nvcode-color-schemes.vim/blob/master/nord.yml#L192-L199

You can overwrite it locally with this (after you load the plugin):
" Treesitter
highlight! TSText guifg='#A3BE8C'
highlight! TSStrong guifg='#A3BE8C'
highlight! TSEmphasis guifg='#A3BE8C'
highlight! TSUnderline guifg='#A3BE8C'
highlight! TSTitle guifg='#A3BE8C'
highlight! TSLiteral guifg='#A3BE8C'
highlight! TSURI guifg='#A3BE8C'

This will give you the green color you'd expect from nordic python docstrings :)
The nordic yellow color is #EBCB8B, in case you want to stick with yellow.

Should be fixed in this PR Some of Treesitter highlight groups are still in a work in progress.

Confirming this is fixed.


Use as tablename the filename without .csv

Having a default table name can be a pain if we want to support join between tables.
So we can use fielname as tablename.

To use the filename as tablename means that we need to remove that information from:

class SettingsDB
remove the input field from the UI (tab Settings)
on CSVDB class get the filename (without '.csv') and use it as table name

Resolved in #43


Various web hook and events serialisation fixes.

Considering https://github.com/MagnusS/okra/pull/102#issuecomment-1096316747, it looks like in gitlab.atd the avatar_url field of type namespace has to be nullable. I believe this is also the case for type user_short and type user.


Move Configuration Management from SIG CLI guides to the kubectl reference

This is a Feature Request

What would you like to be added

Move the pages under Configuration Management from the SIG CLI guides to the upstream kubectl reference
Why is this needed
Part of https://github.com/kubernetes/website/issues/25943. The source code to move resides here. You can refer to https://github.com/kubernetes/website/issues/45600 to see how it can be done.
Comments

/sig docs
/language-en
/help-wanted

/language en
/help

I would like to work on this issue. @sreeram-venkitesh.

/assign


Loss gen tokens

Takes advantage of the new functionality in Composer to weight microbatches by loss generating tokens, and not just total tokens. See the Composer PR (https://github.com/mosaicml/composer/pull/3677) for more details and manual testing.
Note: this needs a Composer release and bump (and CI won't pass until that happens)

@mvpatel2000 yeah, CI won't pass until release


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #42.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #42

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


VSCode extensions reinstall itself on every connection

Hi people,
I am using VSCode to connect to a remote server for development. Every time I connect VSCode to this server, it is reinstalling all the extensions. Remote server is Ubuntu 20.04.1 LTS server. Auth is done via ssh key.
Host VSCodeServer
  HostName <IP_ADDRESS>
  User UserName
  Port 22
  ForwardAgent yes
  IdentityFile C:\Users\UserName\.ssh\id_rsa

Below is the output of this process.
c1d5a4d2f610: running
Acquiring lock on /home/user/.vscode-server/bin/ea3859d4ba2f3e577a159bc91e3074c5d85c0523/vscode-remote-lock.user.ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Found existing installation at /home/user/.vscode-server/bin/ea3859d4ba2f3e577a159bc91e3074c5d85c0523...
Checking /home/user/.vscode-server/.ea3859d4ba2f3e577a159bc91e3074c5d85c0523.log and /home/user/.vscode-server/.ea3859d4ba2f3e577a159bc91e3074c5d85c0523.pid for a running server
Looking for server with pid: 1497
Found running server...
Installing extensions...
Installing extensions...

*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
*

Checking server status on port 42261 with wget
c1d5a4d2f610: start
sshAuthSock====
webUiAccessToken====
listeningOn==42261==
osReleaseId==ubuntu==
arch==x86_64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime==129809==
serverStartTime====
c1d5a4d2f610: end

VSCode Version: 1.52.1
OS Version: Windows 10 Enterprise  - v1909

Steps to Reproduce:

Install Remote-SSH plugin
Connect to remote server

Does this issue occur when all extensions are disabled?: ~Yes/No~ Not Applicable

Are you just commenting on the log message? It is not reinstalling extensions, just installing new ones if needed.

Are you just commenting on the log message? It is not reinstalling extensions, just installing new ones if needed.

I do not have new extensions.

I do not have new extensions.

Right, this is working as expected. The log message could be misleading but it's correct.

Right, this is working as expected. The log message could be misleading but it's correct.


Random photos not in album chosen

I have uninstalled and reinstalled 3 times. Seems to work for a while and then photos are appearing that are not in the album I have chosen. Photos that I don't want projected onto my TV. Help.

Is this during the screensaver playback? You can select the albums(s) to show in Screensaver Settings > User selection. Make sure you have at least 1 selection made or it'll randomly choose albums to display.


Add globe icon for language picker

In home screen language settings need an icon (othewise non-native speaker has no way of knowing where to change the language).
Deleted old makecode.com site contents.

Great minds think alike https://github.com/Microsoft/pxt/commit/7273049a026fe06b5387f2ff55a7cb3f796daf63

That is too much of coincidence.


DB constraints - not for H2

Add a remark that no referential constraints are generated for H2 (+ reasoning)

Thank you @patricebender! I included your proposed sentence in the introduction of that chapter. Please give it a quick review if it overall makes sense to you or if it needs some tweaking :)


Documentation examples incorrect

In the documentation, code is given that does not run.  The problem is that the node feature matrix is transposed vs. what it should be.
Example given:
fg = FeaturedGraph(erdos_renyi(100, 20))
fg = FeaturedGraph(fg, nf=rand(100, 5)) # DimensionMismatch

Correct code:
fg = FeaturedGraph(erdos_renyi(100, 20))
fg = FeaturedGraph(fg, nf=rand(5, 100))

Another example:
model = Chain(
    GCNConv(1024=>256, relu),
    x -> (node_feature(x), global_feature(x)),
    (nf, gf) -> (softmax(nf), identity.(gf))
) # this works

Implicit expectation:
model(some_featuredgraph) # ❌ this should work, but does not

Actual result: UndefVarError: node_feature not defined.  This is very confusing, because node_feature(some_featuredgraph) works without issue in the same Pluto notebook.
Defining a function get_nf_gf solves this:
get_nf_gf(fg) = (node_feature(fg), global_feature(fg))

model = Chain(
    GCNConv(1024=>256, relu),
    get_nf_gf,
    (nf, gf) -> (softmax(nf), identity.(gf))
)

model(some_featuredgraph) # ✔


translatable nestedform - third attempt

This PR adds support for translatable nested forms https://github.com/wintercms/wn-translate-plugin/pull/54
It now directly targets the main branch and includes the old wip/translatable-nested form branch + latest main additions.
Hopefully this one can be merged.

@mjauvin I've now tested this with repeaters + nested forms in the following variations:
nestedform
  > repeater
     > text

and
repeater
  > nestedform
      > text

Both worked well.

Thanks for merging! :bow:

Feel free to submit the PR for the autocomplete issue

@mjauvin here you go with the autocomplete fix https://github.com/wintercms/wn-translate-plugin/pull/70


Websockets support needs to be enabled if hosted behind a reverse proxy

Hello,
Thanks for making this, it's very useful! I was hosting the editor behind a Nginx reverse proxy using the Nginx Proxy Manager which I believe is pretty common amongst self-hosting enthusiasts and found out that the "Websockets Support" option was required to be enabled if not you would not be able to connect to the server to save your notes for collaboration. Just mentioning it here in case someone else faces the same problem.

Hi, thanks for noticing this! Closing this issue for now.


⚠ Samsung has degraded performance

In 55b98e3, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2889 ms

Resolved: Samsung performance has improved in ae25daf.


dial unix /var/run/docker.sock: no such file or directory

I like your Kitematic client.

Now I want to start with docker in Terminal. But when I pull a new image I see the following error:

I found the Issue #261 but $(docker-machine env dev) not fix my problem.

Hi,
Thanks for this. If you use docker pull centos instead of sudo pull centos it should work.
Let me know if it's not working. Thanks!

Thanks it works!


DBZ-1392 (Test, don't merge)

@Naros, @jpechane, so here's the change after applying the auto-formatter. LGTM, I'd say. WDYT?

@gunnarmorling LGTM as well.  Do you want to or shall I modify the POM in this PR so that the auto format task happens automatically without needing a profile?


Accordion

Feature request
I created a simple yet elegant accordion component that offers expandable sections with a smooth and clean transition. Furthermore, the component is highly customizable, allowing you to adjust colors, sizes and other properties.
Describe the feature you need
I would like to request a review of my pull request [#270] for the addition of a simple accordion component to the project.
Additional information

Merged. Thanks for your contribution! 👍


[Backport] [2.x] [BWC and API enforcement] Decorate the existing APIs with proper annotations (part 1) (#9520)

Backport of https://github.com/opensearch-project/OpenSearch/pull/9520 to 2.x

@andrross mind please approving?

@owaiskazi19 @kotwanikunal folks could I ask please for approval to get this backport in? thank you


fix: add type definition for configuring forkTsChecker

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Added type definition for NuxtConfiguration for new build.typescript option.

TypeScript validation was failing with new configuration model.

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #5326 into dev will decrease coverage by 44.44%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             dev    #5326       +/-   ##
==========================================
- Coverage   95.7%   51.25%   -44.45%
==========================================
  Files         74       74
  Lines       2513     2513
  Branches     639      639
==========================================
- Hits        2405     1288     -1117
- Misses        91      948      +857
- Partials      17      277      +260

Impacted Files
Coverage Δ

packages/generator/src/generator.js
0% <0%> (-100%)
:arrow_down:

packages/typescript/src/index.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/index.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/options/server.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/run.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/commands/start.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/commands/generate.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/options/common.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/utils/constants.js
0% <0%> (-100%)
:arrow_down:

packages/cli/src/setup.js
0% <0%> (-100%)
:arrow_down:

... and 39 more

Continue to review full report at Codecov.

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

I can also provide more precise types from fork-ts-checker docs if that would be helpful, but we'd then need to keep them in sync. I don't think they currently export the Config type, though it is present in the built npm module.

Thanks for  your PR @danielroe !
I suggested a little change. And for the type of the options of ForkTsChecker, there is IMO too many properties to stay in sync, I prefer see if we can import it from somewhere, or see with the maintainer how we could have them.

Thanks @danielroe @kevinmarrec :heart:


Aether Grass Block Item top face displayed incorrectly

Ah, the good old grass top texture issue. Grayscale grass texture on top of a dropped aether grass block item. See attached:

The grass top texture is also gray when held in the player's hand. Seems to smoothly change from gray to colored based on the player's pitch rotation.

(To be added to https://github.com/devs-immortal/The-Aether/milestone/1 )

Re-test is warranted here, unable to reproduce this in the latest version of 1.16.5 nor 1.17

Assuming resolved in 1.17


The specified device interface or feature level is not supported on this system

Hi
I encounter a problem in my W10 64bit laptop P51s, it's two video cards, nvidia and integrated intel.
I've setup nvdia as primary use and Dxdiag shows that Directx 12 is running normally.
Here is my code:
import time
import numpy as np
import d3dshot
p1=time.time()
d = d3dshot.create(capture_output="numpy")
img2=d.screenshot()
p2=time.time()
print ("it takes "+str(p2-p1)+ " seconds to capture in D3D.")

Traceback (most recent call last):
File "C:/Users/jianghu/PycharmProjects/diaexplo/mess_d3d.py", line 14, in
d = d3dshot.create()
File "C:\Python38\lib\site-packages\d3dshot_init_.py", line 64, in create
d3dshot = D3DShot(
File "C:\Python38\lib\site-packages\d3dshot\d3dshot.py", line 24, in init
self.detect_displays()
File "C:\Python38\lib\site-packages\d3dshot\d3dshot.py", line 194, in detect_displays
self.displays = Display.discover_displays()
File "C:\Python38\lib\site-packages\d3dshot\display.py", line 109, in discover_displays
display = cls(
File "C:\Python38\lib\site-packages\d3dshot\display.py", line 40, in init
self.dxgi_output_duplication = self._initialize_dxgi_output_duplication()
File "C:\Python38\lib\site-packages\d3dshot\display.py", line 66, in _initialize_dxgi_output_duplication
return d3dshot.dll.dxgi.initialize_dxgi_output_duplication(self.dxgi_output, self.d3d_device)
File "C:\Python38\lib\site-packages\d3dshot\dll\dxgi.py", line 257, in initialize_dxgi_output_duplication
dxgi_output.DuplicateOutput(d3d_device, ctypes.byref(dxgi_output_duplication))
_ctypes.COMError: (-2005270524, 'The specified device interface or feature level is not supported on this system.', (None, None, None, 0, None))
Process finished with exit code 1
Could you suggest what I should do to fix the issue?

I have this same problem as well, it would be great if you could help us to find a workaround. Thank you very much.

Does your computer (or laptop) have both integrated and dedicated GPUs? If so, then maybe it's related to the following issue: Error generated when Desktop Duplication API-capable application is run against discrete GPU.
Basically, the Desktop Duplication API doesn't support being run against the dedicated GPU in this case. Thus, the function DuplicateOutput fails and returns the error DXGI_ERROR_UNSUPPORTED (as we can see in the log you posted).
This was exactly my case and all I had to do was to force python to use the integrated GPU.
I'd suggest @nbrochu to document this since it's quite a shady issue and makes d3dshot unusable!

@gabriel-dev Thanks for making me aware of the use case of using it on laptops with hybrid GPUs (where I assume rendering gets switched from one to the other for power management purposes). I personally couldn't have anticipated this problem as I don't have a Windows laptop but it's very clear from what you linked that it runs into an issue on hybrid GPU systems.
To clarify for anyone else reading, it only causes an issue on laptops. I have multiple displays attached on my desktop, some on my discrete GPU, others on my integrated graphics and D3DShot works fine capturing any of them.
I'm really curious about the output of d.displays on laptop like these. If someone could help me out with that one that would be great.
I'd love to add a note to the documentation but I need to know what I'm dealing with first. Is the issue resolved by doing something in D3DShot (e.g. Picking a display set on the integrated graphics) or do you have do something outside to force Python to use that display adapter?
Also, not sure that this is necessarily the issue @hujiangchuan encountered but it could be. DXGI_ERROR_UNSUPPORTED can be raised in a lot of other cases like Windows<->Python bitness mismatch for example.

Someone getting this error in the dual-gpu laptop scenario reached out to me and we managed to get D3DShot fully working. There is no code fix required. As mentioned by @gabriel-dev, you need to make sure your python.exe and related processes you use (ipython, jupyter etc.) are set to be rendered exclusively on the integrated GPU. I will write a little guide for the wiki tomorrow and link to it from the readme in a warning to laptop users.


Example endpoint not found

If I don't include an express route explicitly, for example, the code below works:
app.post('/appname', function(req, res) {
    res.json({
      "version": "1.0",
      "response": {
        "shouldEndSession": true,
        "outputSpeech": {
          "type": "SSML",
          "ssml": "<speak>Hmm <break time=\"1s\"/> not sure why we misconfigured this skill</speak>"
        }
      }
    });

});

then my node app throws a "There was an error calling the remote endpoint, which returned HTTP 404 : Not Found".  I'm using the example code and it doesn't set the endpoint anywhere.  What am i doing wrong?  (This is more of a clarification than an issue... has to be something I'm doing wrong, although I've literally copied and pasted the example code)

@cpup22 What did you do to resolve this? (for the next person)

There are three entries:

alexaApp.express(app, "/echo/"); --in code
var alexaApp = new alexa.app("skillname"); --in code
https://example.com/echo/skillname --this is configured inside the amazon skill console

I wanted it to be https://example.com/skillname to invoke my skill so I was confused why my setup wasn't working. Then I noticed the "/echo" within the alexa-app code. as soon as I adjusted entry #3 above to include /echo/skillname instead of just /skillname it worked.

Thanks @cpup22. If you think the documentation can be clearer please do contribute!


Suggestion: extend searching with markdown content

Would it be possible to extend the built-in storybook search input to include results from the markdown from this plugin? So that a search when using storybook-readme is a full storybook text search, on top of the default filtering for story names.

@ndelangen what do you think about this? As I know you are going to implement supporting of md  out of the box this this feature request maybe should be moved to stroybooks repo?

@ndelangen ping

I've moved on to just using storybooks with the built-in markdown loader. I would be interested in storybook text content being searchable, but that is unrelated to this plugin. Closing.