Data not making it after upgrading to 2022.4.0

Hi there,
I updated Home Assistant today and it looks like the data is not making it into HA anymore.. The state of the sensor says 'connected' but the attributes are now completely missing. My wife and I really rely on your integration so I would really appreciate it if you could look. I will try and look myself and if I see the fix ill push a PR through. Thanks a bunch!

I checked the API and the data is still there so it seems like somethings changed on the HA side to cause the attributes not to come in properly

I have noticed the same issue.....
The owlet platform sensor seems to work correctly and reports connected/disconnected depending on if it is placed on the base station or not; however the attributes that normally appeared when you click on the sensor entity no longer seem to appear.
With multiple entries in the log files like below.
Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'heart_rate' when rendering '{% if states.sensor.owlet_smart_sock_xxxxxx.attributes.heart_rate and states.sensor.owlet_smart_sock_xxxxxx.attributes.heart_rate.state != "Unknown" %} {{states.sensor.owlet_smart_sock_xxxxxx.attributes.heart_rate}} {% else %} -1 {% endif %}'

Thanks for the comments so far!
The workaround that I used was to downgrade from 2022.4.1 to 2022.3.8. I did this utilizing the following command in editor: hassio ha update --version=2022.3.8
I'm hoping that someone comes up with a solution. My technical skills are not up to the task of diagnosing and fixing.

Found the issue and fixed in my own repo (RampantRedsFan/ha-sensor.owlet).

Hi RampantRedsFan
I have manually installed you repo and can confirm that it is working as intended, with all sensors appearing and pulling in correct values......great job and thankyou for your quick fix to this issue.

Great work, such a relief because of how much we rely on this integration! Thank you @RampantRedsFan for the fix!

Hi,
Thank you for the fix in your fork @RampantRedsFan , I was about to start fixing it myself.
Anyhow, I'm having some issues:

Using the version in this repo the entity didn't ever appear in HA.
Using your fork, the entity appears (and the sensor too if configured) but appears as Disconnected an attributes values are quite strange (no values in DSN or vitals and true in LOW INTEG READ and  SOCK DISCON ALRT):

The sock is charging and the base is connected (I can see that info in the app too) so... are these default values until first vitals readings are taken or something is wrong?
Thanks!

Hey Luis,
I believe that the master has been updated to fix the initial issue and
likely the issues that you note in your message. I would suggest that
instead of using my fork, you utilize the master. I am keeping my fork out
there for those (like myself) who benefit from some of the quarks that you
point out, but if you are interested in a cleaner version, I think that the
master is the way to go.
Take care!
On Fri, Jul 1, 2022 at 7:38 AM Luis Alberto Pérez García <
@.***> wrote:

Hi,
Thank you for the fix in your fork @RampantRedsFan
https://github.com/RampantRedsFan , I was about to start fixing it
myself.
Anyhow, I'm having some issues:

Using the version in this repo the entity didn't ever appear in HA.
Using your fork, the entity appears (and the sensor too if
configured) but appears as Disconnected an attributes values are quite
strange (no values in DSN or vitals and true in LOW INTEG READ and SOCK
DISCON ALRT):

[image: image]
https://user-images.githubusercontent.com/615268/176887290-c7cbd8f7-dded-439e-8018-7d00f5e415d6.png
The sock is charging and the base is connected (I can see that info in the
app too) so... are these default values until first vitals readings are
taken or something is wrong?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/jlamendo/ha-sensor.owlet/issues/13#issuecomment-1172253140,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVK3ZY2OBWWDICAW54UN7DVR3KCLANCNFSM5SYG25GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sent from my mobile

Not sure about that. I tried master and got no entity nor sensor but an error log. Using yours, I got it working. Only thing, it seems to take some default values while sock is not in use. If the sock is in use, I got the right values but, when the sock is charging, it shows the values in the image on my previous comment (disconnected, charging to 0, two alarms to true and rest of values empty).
Thanks!

@RampantRedsFan yours works as well! Thank you
i thought i would shar my sock card as well

type: vertical-stack
cards:
  - type: custom:stack-in-card
    cards:
      - type: custom:stack-in-card
        cards:
          - type: custom:mushroom-template-card
            primary: Owlet Socket
            icon: mdi:owl
            icon_color: |-
              {% set state=states('sensor.owlet_connection_state') %}
              {% if state=='Connected' %}
              green
              {% elif state=='Disconnected' %}
              amber
              {% endif %}
            entity: sensor.owlet_connection_state
            tap_action:
              action: more-info
            hold_action:
              action: none
            double_tap_action:
              action: more-info
            secondary: |-
              {% set state=states('sensor.owlet_connection_state') %}
              {% if state=='Connected' %}
              Connected
              {% elif state=='Disconnected' %}
              Disconnected
              {% endif %}
            card_mod:
              style: |
                ha-card {
                  --ha-card-background: none;
                  padding: 0px !important;
                  margin-left: 6px !important;
                  margin-top: 6px !important;
                  margin-bottom: 6px !important;
                  --ha-card-box-shadow: none;
                  transition: all 0s;
                }
                :host {
                  --mush-icon-border-radius: 12px;
                }
          - type: custom:stack-in-card
            cards:
              - type: custom:mushroom-template-card
                card_mod:
                  style: |
                    ha-card {
                      height: 200px !important;
                      background: url(https://i0.wp.com/www.threelambs.ca/wp-content/uploads/2018/02/Owlet-Soc-Gen-3-3.jpg?fit=1200%2C1200&ssl=1) center / cover no-repeat !important;
                      --ha-card-border-radius: 0px;
                      --ha-card-box-shadow: none;
                      margin-left: 0px !important;
                      margin-top: 0px !important;
                      margin-right: 0px !important;
                      margin: -8px;
                      transition: all 0s;
                    }
              - type: custom:stack-in-card
                cards:
                  - type: custom:mushroom-chips-card
                    chips:
                      - type: template
                        entity: sensor.owlet_charging_status
                        icon_color: |-
                          {% set state=states('sensor.owlet_charging_status') %}
                          {% if state=='0' %}
                          disabled
                          {% elif state=='1' %}
                          green
                          {% endif %}
                        icon: >-
                          {{ state_attr('sensor.owlet_charging_status', 'icon')
                          }}
                        content: '{{ states(''sensor.owlet_charging_status'') }}'
                        tap_action:
                          action: more-info
                      - type: template
                        entity: sensor.owlet_current_battery_level
                        icon_color: deep-orange
                        icon: >-
                          {{ state_attr('sensor.owlet_current_battery_level',
                          'icon') }}
                        content: '{{ (states(''sensor.owlet_current_battery_level''))}} %'
                        tap_action:
                          action: more-info
                      - type: template
                        entity: sensor.owlet_heart_rate
                        icon_color: pink
                        icon: '{{ state_attr(''sensor.owlet_heart_rate'', ''icon'') }}'
                        content: '{{ (states(''sensor.owlet_heart_rate''))}} BPM'
                        tap_action:
                          action: more-info
                      - type: template
                        entity: sensor.owlet_oxygen_level
                        icon_color: green
                        icon: '{{ state_attr(''sensor.owlet_oxygen_level'', ''icon'') }}'
                        content: '{{ (states(''sensor.owlet_oxygen_level''))}} %'
                        tap_action:
                          action: more-info
                      - type: template
                        entity: sensor.owlet_movement
                        icon_color: blue
                        icon: '{{ state_attr(''sensor.owlet_movement'', ''icon'') }}'
                        content: '{{ (states(''sensor.owlet_movement''))}} %'
                        tap_action:
                          action: more-info
                    card_mod:
                      style: |
                        .chip-container {
                          flex-flow: column !important;
                          --chip-spacing: 0px;
                          --chip-background: none;
                          --chip-box-shadow: none;
                          transition: all 0s;
                        }
                card_mod:
                  style: |
                    ha-card {
                      position: absolute;
                      right: 8px;
                      top: 8px;
                      background: rgba(var(--rgb-card-background-color), 0.9);
                      box-shadow: none;
                      border-radius: 12px;
                      transition: all 0s;
                    }
            card_mod:
              style: |
                ha-card {
                  border-radius: 12px;
                  box-shadow: none;
                  margin-left: 6px;
                  margin-right: 6px;
                }
          - type: horizontal-stack
            cards:
              - type: custom:mushroom-template-card
                icon: >-
                  {{ state_attr('sensor.owlet_current_monitoring_status',
                  'icon') }}
                icon_color: >-
                  {% set state=states('sensor.owlet_current_monitoring_status')
                  %}

                  {% if state=='True' %}

                  green

                  {% elif state=='False' %}

                  disabled

                  {% endif %}
                layout: vertical
                entity: sensor.owlet_current_monitoring_status
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
              - type: custom:mushroom-template-card
                icon: '{{ state_attr(''sensor.owlet_charging_status'', ''icon'') }}'
                icon_color: |-
                  {% set state=states('sensor.owlet_charging_status') %}
                  {% if state=='0' %}
                  disabled
                  {% elif state=='1' %}
                  green
                  {% endif %}
                layout: vertical
                entity: sensor.owlet_charging_status
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
              - type: custom:mushroom-template-card
                icon: '{{ state_attr(''sensor.owlet_low_battery_alert'', ''icon'') }}'
                icon_color: |-
                  {% set state=states('sensor.owlet_low_battery_alert') %}
                  {% if state=='False' %}
                  disabled
                  {% elif state=='True' %}
                  red
                  {% endif %}
                layout: vertical
                entity: sensor.owlet_low_battery_alert
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                primary: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
              - type: custom:mushroom-template-card
                icon: '{{ state_attr(''sensor.owlet_high_heart_rate_alert'', ''icon'') }}'
                icon_color: |-
                  {% set state=states('sensor.owlet_high_heart_rate_alert') %}
                  {% if state=='False' %}
                  disabled
                  {% elif state=='True' %}
                  red
                  {% endif %}
                layout: vertical
                entity: sensor.owlet_high_heart_rate_alert
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
              - type: custom:mushroom-template-card
                icon: '{{ state_attr(''sensor.owlet_low_heart_rate_alert'', ''icon'') }}'
                icon_color: |-
                  {% set state=states('sensor.owlet_low_heart_rate_alert') %}
                  {% if state=='False' %}
                  disabled
                  {% elif state=='True' %}
                  red
                  {% endif %}
                layout: vertical
                entity: sensor.owlet_low_heart_rate_alert
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                primary: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
              - type: custom:mushroom-template-card
                icon: >-
                  {{ state_attr('sensor.owlet_low_oxygen_level_alert', 'icon')
                  }}
                icon_color: |-
                  {% set state=states('sensor.owlet_low_oxygen_level_alert') %}
                  {% if state=='False' %}
                  disabled
                  {% elif state=='True' %}
                  red
                  {% endif %}
                layout: vertical
                entity: sensor.owlet_low_oxygen_level_alert
                hold_action:
                  action: more-info
                double_tap_action:
                  action: more-info
                tap_action:
                  action: more-info
                secondary: ''
                badge_color: ''
                badge_icon: ''
                primary: ''
                card_mod:
                  style: |
                    ha-card {
                      --ha-card-box-shadow: none;
                      --ha-card-background: none;
                    }
        card_mod:
          style: |
            ha-card {
              background-color: rgba(207,207,196, 0.2);
            }

That is a really cool card! I will be using it. Thanks for sharing!
On Sun, Feb 26, 2023 at 6:17 PM Brad @.***> wrote:

@RampantRedsFan https://github.com/RampantRedsFan yours works as well!
Thank you
i thought i would shar my sock card as well
[image: image]
https://user-images.githubusercontent.com/58960644/221443393-f850eec5-53ac-4e7c-bf20-85d7b0833ecd.png
type: vertical-stack
cards:

type: custom:stack-in-card
cards:

type: custom:stack-in-card
cards:

type: custom:mushroom-template-card
primary: Owlet Socket
icon: mdi:owl
icon_color: |-
{% set state=states('sensor.owlet_connection_state') %}
{% if state=='Connected' %}
green
{% elif state=='Disconnected' %}
amber
{% endif %}
entity: sensor.owlet_connection_state
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: more-info
secondary: |-
{% set state=states('sensor.owlet_connection_state') %}
{% if state=='Connected' %}
Connected
{% elif state=='Disconnected' %}
Disconnected
{% endif %}
card_mod:
style: |
ha-card {
--ha-card-background: none;
padding: 0px !important;
margin-left: 6px !important;
margin-top: 6px !important;
margin-bottom: 6px !important;
--ha-card-box-shadow: none;
transition: all 0s;
}
:host {
--mush-icon-border-radius: 12px;
}
type: custom:stack-in-card
cards:

type: custom:mushroom-template-card
card_mod:
style: |
ha-card {
height: 200px !important;
background: url(https://i0.wp.com/www.threelambs.ca/wp-content/uploads/2018/02/Owlet-Soc-Gen-3-3.jpg?fit=1200%2C1200&ssl=1) center / cover no-repeat !important;
--ha-card-border-radius: 0px;
--ha-card-box-shadow: none;
margin-left: 0px !important;
margin-top: 0px !important;
margin-right: 0px !important;
margin: -8px;
transition: all 0s;
}
type: custom:stack-in-card
cards:

type: custom:mushroom-chips-card
chips:

type: template
entity: sensor.owlet_charging_status
icon_color: |-
{% set state=states('sensor.owlet_charging_status') %}
{% if state=='0' %}
disabled
{% elif state=='1' %}
green
{% endif %}
icon: >-
{{ state_attr('sensor.owlet_charging_status', 'icon')
}}
content: '{{ states(''sensor.owlet_charging_status'') }}'
tap_action:
action: more-info
type: template
entity: sensor.owlet_current_battery_level
icon_color: deep-orange
icon: >-
{{ state_attr('sensor.owlet_current_battery_level',
'icon') }}
content: '{{ (states(''sensor.owlet_current_battery_level''))}} %'
tap_action:
action: more-info
type: template
entity: sensor.owlet_heart_rate
icon_color: pink
icon: '{{ state_attr(''sensor.owlet_heart_rate'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_heart_rate''))}} BPM'
tap_action:
action: more-info
type: template
entity: sensor.owlet_oxygen_level
icon_color: green
icon: '{{ state_attr(''sensor.owlet_oxygen_level'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_oxygen_level''))}} %'
tap_action:
action: more-info
type: template
entity: sensor.owlet_movement
icon_color: blue
icon: '{{ state_attr(''sensor.owlet_movement'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_movement''))}} %'
tap_action:
action: more-info
card_mod:
style: |
.chip-container {
flex-flow: column !important;
--chip-spacing: 0px;
--chip-background: none;
--chip-box-shadow: none;
transition: all 0s;
}
card_mod:
style: |
ha-card {
position: absolute;
right: 8px;
top: 8px;
background: rgba(var(--rgb-card-background-color), 0.9);
box-shadow: none;
border-radius: 12px;
transition: all 0s;
}
card_mod:
style: |
ha-card {
border-radius: 12px;
box-shadow: none;
margin-left: 6px;
margin-right: 6px;
}

type: horizontal-stack
cards:

type: custom:mushroom-template-card
icon: >-
{{ state_attr('sensor.owlet_current_monitoring_status',
'icon') }}
icon_color: >-
{% set state=states('sensor.owlet_current_monitoring_status')
%}
{% if state=='True' %}
green
{% elif state=='False' %}
disabled
{% endif %}
layout: vertical
entity: sensor.owlet_current_monitoring_status
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_charging_status'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_charging_status') %}
{% if state=='0' %}
disabled
{% elif state=='1' %}
green
{% endif %}
layout: vertical
entity: sensor.owlet_charging_status
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_low_battery_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_low_battery_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_battery_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_high_heart_rate_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_high_heart_rate_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_high_heart_rate_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_low_heart_rate_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_low_heart_rate_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_heart_rate_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: >-
{{ state_attr('sensor.owlet_low_oxygen_level_alert', 'icon')
}}
icon_color: |-
{% set state=states('sensor.owlet_low_oxygen_level_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_oxygen_level_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
card_mod:
style: |
ha-card {
background-color: rgba(207,207,196, 0.2);
}

—
Reply to this email directly, view it on GitHub
https://github.com/jlamendo/ha-sensor.owlet/issues/13#issuecomment-1445496372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVK3Z5RMV726BWJ442FXITWZPQBRANCNFSM5SYG25GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sent from my mobile

Same!!
Jon Singh
On Feb 26, 2023, at 7:13 PM, RampantRedsFan @.***> wrote:

That is a really cool card! I will be using it. Thanks for sharing!
On Sun, Feb 26, 2023 at 6:17 PM Brad @.***> wrote:

@RampantRedsFan https://github.com/RampantRedsFan yours works as well!
Thank you
i thought i would shar my sock card as well
[image: image]
https://user-images.githubusercontent.com/58960644/221443393-f850eec5-53ac-4e7c-bf20-85d7b0833ecd.png
type: vertical-stack
cards:

type: custom:stack-in-card
cards:
type: custom:stack-in-card
cards:
type: custom:mushroom-template-card
primary: Owlet Socket
icon: mdi:owl
icon_color: |-
{% set state=states('sensor.owlet_connection_state') %}
{% if state=='Connected' %}
green
{% elif state=='Disconnected' %}
amber
{% endif %}
entity: sensor.owlet_connection_state
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: more-info
secondary: |-
{% set state=states('sensor.owlet_connection_state') %}
{% if state=='Connected' %}
Connected
{% elif state=='Disconnected' %}
Disconnected
{% endif %}
card_mod:
style: |
ha-card {
--ha-card-background: none;
padding: 0px !important;
margin-left: 6px !important;
margin-top: 6px !important;
margin-bottom: 6px !important;
--ha-card-box-shadow: none;
transition: all 0s;
}
:host {
--mush-icon-border-radius: 12px;
}
type: custom:stack-in-card
cards:
type: custom:mushroom-template-card
card_mod:
style: |
ha-card {
height: 200px !important;
background: url(https://i0.wp.com/www.threelambs.ca/wp-content/uploads/2018/02/Owlet-Soc-Gen-3-3.jpg?fit=1200%2C1200&ssl=1) center / cover no-repeat !important;
--ha-card-border-radius: 0px;
--ha-card-box-shadow: none;
margin-left: 0px !important;
margin-top: 0px !important;
margin-right: 0px !important;
margin: -8px;
transition: all 0s;
}
type: custom:stack-in-card
cards:
type: custom:mushroom-chips-card
chips:
type: template
entity: sensor.owlet_charging_status
icon_color: |-
{% set state=states('sensor.owlet_charging_status') %}
{% if state=='0' %}
disabled
{% elif state=='1' %}
green
{% endif %}
icon: >-
{{ state_attr('sensor.owlet_charging_status', 'icon')
}}
content: '{{ states(''sensor.owlet_charging_status'') }}'
tap_action:
action: more-info
type: template
entity: sensor.owlet_current_battery_level
icon_color: deep-orange
icon: >-
{{ state_attr('sensor.owlet_current_battery_level',
'icon') }}
content: '{{ (states(''sensor.owlet_current_battery_level''))}} %'
tap_action:
action: more-info
type: template
entity: sensor.owlet_heart_rate
icon_color: pink
icon: '{{ state_attr(''sensor.owlet_heart_rate'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_heart_rate''))}} BPM'
tap_action:
action: more-info
type: template
entity: sensor.owlet_oxygen_level
icon_color: green
icon: '{{ state_attr(''sensor.owlet_oxygen_level'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_oxygen_level''))}} %'
tap_action:
action: more-info
type: template
entity: sensor.owlet_movement
icon_color: blue
icon: '{{ state_attr(''sensor.owlet_movement'', ''icon'') }}'
content: '{{ (states(''sensor.owlet_movement''))}} %'
tap_action:
action: more-info
card_mod:
style: |
.chip-container {
flex-flow: column !important;
--chip-spacing: 0px;
--chip-background: none;
--chip-box-shadow: none;
transition: all 0s;
}
card_mod:
style: |
ha-card {
position: absolute;
right: 8px;
top: 8px;
background: rgba(var(--rgb-card-background-color), 0.9);
box-shadow: none;
border-radius: 12px;
transition: all 0s;
}
card_mod:
style: |
ha-card {
border-radius: 12px;
box-shadow: none;
margin-left: 6px;
margin-right: 6px;
}
type: horizontal-stack
cards:
type: custom:mushroom-template-card
icon: >-
{{ state_attr('sensor.owlet_current_monitoring_status',
'icon') }}
icon_color: >-
{% set state=states('sensor.owlet_current_monitoring_status')
%}

{% if state=='True' %}
green
{% elif state=='False' %}
disabled
{% endif %}
layout: vertical
entity: sensor.owlet_current_monitoring_status
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}

type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_charging_status'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_charging_status') %}
{% if state=='0' %}
disabled
{% elif state=='1' %}
green
{% endif %}
layout: vertical
entity: sensor.owlet_charging_status
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_low_battery_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_low_battery_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_battery_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_high_heart_rate_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_high_heart_rate_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_high_heart_rate_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
type: custom:mushroom-template-card
icon: '{{ state_attr(''sensor.owlet_low_heart_rate_alert'', ''icon'') }}'
icon_color: |-
{% set state=states('sensor.owlet_low_heart_rate_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_heart_rate_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
type: custom:mushroom-template-card
icon: >-
{{ state_attr('sensor.owlet_low_oxygen_level_alert', 'icon')
}}
icon_color: |-
{% set state=states('sensor.owlet_low_oxygen_level_alert') %}
{% if state=='False' %}
disabled
{% elif state=='True' %}
red
{% endif %}
layout: vertical
entity: sensor.owlet_low_oxygen_level_alert
hold_action:
action: more-info
double_tap_action:
action: more-info
tap_action:
action: more-info
secondary: ''
badge_color: ''
badge_icon: ''
primary: ''
card_mod:
style: |
ha-card {
--ha-card-box-shadow: none;
--ha-card-background: none;
}
card_mod:
style: |
ha-card {
background-color: rgba(207,207,196, 0.2);
}

—
Reply to this email directly, view it on GitHub
https://github.com/jlamendo/ha-sensor.owlet/issues/13#issuecomment-1445496372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVK3Z5RMV726BWJ442FXITWZPQBRANCNFSM5SYG25GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sent from my mobile
—
Reply to this email directly, view it on GitHubhttps://github.com/jlamendo/ha-sensor.owlet/issues/13#issuecomment-1445626498, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADKLFE5XI2N2IWRRDOB4E6TWZQLTVANCNFSM5SYG25GA.
You are receiving this because you authored the thread.Message ID: @.***>

This fix is merged in now, but man that card is awesome! Will for sure be using it with my next kid.


disable retries and lengthen the request timeout for debug builds

It's hard to do debugging in the API when the app keeps making requests. We may need to tweak this, but for now I think it's worthwhile that volley should just chill for slow requests.

@Revenaunt I'm going to merge this but feel free to yell at me if you hate this idea.


Dual display with HDMI and DP

I used the contents of this repository to successfully Hackintosh with Deskmini 110+Mojave.
It is possible to use a 4K monitor with DP.
We also added a monitor via HDMI to make it a dual display.
At this time, MacOS recognizes the HDMI monitor, but a black screen is displayed.
Are you experiencing a similar problem?
Also, how do you think these problems should be solved?
If you can come up with a solution, I would appreciate it if you could tell me.
Thank you very much.

@AKKYM try to power on with only DP port monitor plugged in. when you enter macOS, plugged in the HDMI monitor.

In my environment, when the monitor is plugged into the DP and HDMI ports and turned on, the DP monitor will be displayed correctly, but the HDMI monitor has a black screen.
If the monitor is plugged into the DP port only and then turned on, and then plugged into the HDMI port, the DP monitor will be displayed correctly, but the HDMI monitor will turn black.
When the monitor is plugged into the HDMI port only, turn on the power, and then plug the monitor into the DP port, both monitors will be displayed correctly.
In this case, the monitor used for the DP port is a 4K 60Hz monitor, and the monitor used for the HDMI port is a FullHD 60Hz monitor.
I want both monitors to display properly when plugged into both ports and turned on.
Do you know what the solution is?


Fix: loan risk styles

There's used input's type='number' in NumberInputWithUnits. Is that fine?

yeah, that is the source of the bug, those styles are not supposed to apply to NumberInputWithUnits and there is no other type='number' they need to apply to. I added this in the last PR just for consistency and didn't realize it messed up Loan risk. I will figure out a better way to target these the next time I need to make changes here.


Extra padding on datagrid checkbox when its inside clrForm

Describe the bug
In data grid, checkbox column gets extra padding when it is wrapped inside a clrForm
Root cause - checkbox label gets additional classes "clr-col-12 clr-col-md-2" when wrapped inside "clrForm"
How to reproduce
https://stackblitz.com/edit/clarity-light-theme-v2-qkdlgk
Expected behavior
No extra padding should be added for checkbox inside the datagrid
Versions
App

Angular: [8.2.0]
Clarity: [2.1.0]

The issue seems to be a clobbering of .datagrid-column-separator and the left: .5rem; applied to it. Not sure if the form css is causing this or not but removing that alignes the separator correctly.

This is just the toggle all checkbox specifically, and it is because the host wrapper adds the label dynamically. We ought to just use the CSS version of the checkbox in the toggle to fix this.

Version 4,  #4289 and #4397 seems to be the same and still actual.
How to fix?

Any idea when this will be fixed?  We use several datagrid's within forms and it really throws off the clean UI we are trying to achieve with your framework.


Add multiple selection

More of a prototype. Allowing edits from maintainers.
Connects to https://github.com/vaadin/vaadin-list-box/issues/10

This change is

Is this really something we should add to list-mixin? Multiple selected tabs doesn’t make any sense.
I think I would’ve rather added this only to list-box, so we can avoid having a low-level API (multipleSelected) in addition the the more ”options-specific” API that was suggested for list-box (selectedOptions).

Thanks for the PR. The list-mixin, however, might be a wrong layer for it because then all components extending the mixin would automatically be multi-selectable; <vaadin-list-box> should have multi-selection while <vaadin-tabs> probably shouldn't.
This could work better as an additional mixin that could then be selectively picked for the components that should be multi-selectable.

Wow – talk about timing 😄 Me and Tomi commented about the same thing at the exact same minute.

The suggested selectedOptions is a read-only property (in <select>) and exposes HTML elements in a property. This is something I think we don't have in any other components; might be problematic for the Flow integration also.
Note that similar selectedItems in paper-listbox is also read-only while selectedValues isn't. selectedValues as an array of numbers might work well here also.

selectedValues as an array of numbers might work well here also.

That’s something I’ve been meaning to write an issue about. In <vaadin-select>, you can set use the value of an item to select it (e.g. <vaadin-select value="foobar"> when you have <vaadin-item value="foobar">). But that’s not possible with list-box currently – I think that should be fixed.
If that happens, then selectedValues should probably support indexes and string values as well.

Closing in favour of https://github.com/vaadin/vaadin-list-mixin/pull/56


Improve CLI usage

Add a --help switch

Manpage?

Handle unknown args with an error (It just silently ignores rn)

I can work on these if you'd like I just wanted to have something to highlight that the cli interface can be a bit pokey rn.

Also currently no support for passing quoted strings to opts.

Also currently no support for passing quoted strings to opts.


Pyff should be able to verify metadata signatures using a CA

When verifying metadata files, Pyff need the exact signing certificate.  Add an option so Pyff can also verify the metdata signature based on a CA.
So: CA has signed metadata key and metadata is signed by metadata key, but Pyff only trusts CA and should build a trust chain for the metadata signature.

https://github.com/leifj/pyXMLSecurity/pull/3


add support for Reflection-Llama-3.1

any idea that we add Reflection-Llama-3.1 model?

Don't need, it was a scam.

It's available here for historical purposes: https://ollama.com/library/reflection


The visitor is looking for a book by name

As a buyer, I can search for a book by name to get acquainted with it, and maybe buy.
The main scenario

I enter the title of the book and click the Search button.
The site shows me a list of books in the title of which the entered string occurs.

Alternative scenario

If there are no suitable books, the site shows that the book has not been found.

You can implement simple search with filtering in database

For an accurate understanding of business logic, namely concentration on it. I wanted to understand how unitTest works without access to the database.
A little later everything will be with the database.


use qtpy wrapper

What is the need for changing pyside6 to Pyqt ? I choose pyside6 for the license.

ok just read the other  comment, my bad


ForwardRef.init() got an unexpected keyword argument 'is_class'

Greetings,
Trying out your project for the first time, and after installing and configuring I get the following error when building with make html.
Using version 2.0.1 and pydantic 2.1.1
Running Sphinx v7.2.6
Exception occurred:
  File "/home/jacob/.local/share/virtualenvs/.../lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 221, in eval_type_lenient
    value = _make_forward_ref(value, is_argument=False, is_class=True)
TypeError: ForwardRef.__init__() got an unexpected keyword argument 'is_class'
The full traceback has been saved in /tmp/sphinx-err-t6cdcfow.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make: *** [Makefile:20: html] Error 2

I copy the full traceback here:
# Platform:         linux; (Linux-5.10.0-26-amd64-x86_64-with-glibc2.31)
# Sphinx version:   7.2.6
# Python version:   3.10.0 (CPython)
# Docutils version: 0.18.1
# Jinja2 version:   3.1.2
# Pygments version: 2.17.2

# Last messages:

# Loaded extensions:

# Traceback:
Traceback (most recent call last):
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinx/cmd/build.py", line 293, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinx/application.py", line 233, in __init__
    self.setup_extension(extension)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinx/application.py", line 406, in setup_extension
    self.registry.load_extension(self, extname)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinx/registry.py", line 447, in load_extension
    mod = import_module(extname)
  File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinxcontrib/autodoc_pydantic/__init__.py", line 16, in <module>
    from sphinxcontrib.autodoc_pydantic.directives.autodocumenters import (
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/sphinxcontrib/autodoc_pydantic/directives/autodocumenters.py", line 11, in <module>
    from pydantic_settings import BaseSettings
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic_settings/__init__.py", line 1, in <module>
    from .main import BaseSettings, SettingsConfigDict
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic_settings/main.py", line 40, in <module>
    class BaseSettings(BaseModel):
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 172, in __new__
    set_model_fields(cls, bases, config_wrapper, types_namespace)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 400, in set_model_fields
    fields, class_vars = collect_model_fields(cls, bases, config_wrapper, types_namespace, typevars_map=typevars_map)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic/_internal/_fields.py", line 98, in collect_model_fields
    type_hints = get_cls_type_hints_lenient(cls, types_namespace)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 212, in get_cls_type_hints_lenient
    hints[name] = eval_type_lenient(value, globalns, localns)
  File "/home/jacob/.local/share/virtualenvs/bblearn-7K6zF-Oo/lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 221, in eval_type_lenient
    value = _make_forward_ref(value, is_argument=False, is_class=True)
TypeError: ForwardRef.__init__() got an unexpected keyword argument 'is_class'

Hi @sanjacob,
thanks for raising the issue! This issue could be very well related to autodoc_pydantic and a API incompatibility with newer pydantic versions. To clarify this, I will require a minimal reproducible example from you. Otherwise I can't help :-(.
Could you provide a simple example showcasing the error? Thanks!

I think this is an issue with Python 3.10. I'll check with Python 3.10.11 and give an update.

Indeed, this resolved itself upon upgrading the python version


Fix spelling error

'posessed' > 'possessed'

I'm working on a giant patch right now and I will pull this once I'm thru with that :)

Closed in 343d73aa6a59f5a6672b5eb433ea1c689654728d


A path forward for cross-platform

In order to support PowerShell Core on platforms other than Windows, it's necessary to abstract the credential storage part of this module out into something where we can plug in different solutions on different platforms. For instance:

Windows Credential Vault
MacOS Keychain
Linux D-Bus secret service, or pass

Something like Docker's Credential Helpers seems to be the best approach, although we can't just use theirs, because their plugins and client library are written in Go, which doesn't really interop with ... anything.

Obviously Microsoft decided to tackle this. I'm just not going to bother trying to compete with that.

What is the current Microsoft plan for this? Is it available?

https://github.com/PowerShell/SecretManagement


[UBS-User. Bonus notification] The notification about received bonuses is sent 4 times

Environment: all.
Reproducible: always.
Build found: 21.06.22
Preconditions
Create a user and make an order that is paid via Fondy (e.g. 'Безпечні відходи' in quantity of 4 packages (each package is per 250UAH), total amount - 1000UAH).
User is Logged in to GreenCity as an Administrator: https://ita-social-projects.github.io/GreenCityClient/#/ubs
Steps to reproduce

Open 'Замовлення' tab and find order mentioned in preconditions
Open the order found in step 1 and change order`s status to the 'Привезе сам'
Update the page
Change order`s status to the 'Виконано'
Make the amount of bags less, so that the paid sum is higher than it became as the result
Transfer the rest money to bonuses
Click on the 'Зберегти' button
Log in to GreenCity as a User (https://ita-social-projects.github.io/GreenCityClient/#/ubs Use credentials as for Client mentioned in preconditions)
Open 'Повідомлення' tab and find order mentioned in preconditions

Actual result

The notification about received bonuses is sent 4 times

Expected result

The notification about recieved bonuses should be one time

User story and test case links
E.g.: "User story #2796
Test case"

Notificatiion is sent only one time


Fixed the workability of the bot

"Don't follow list" is deleted due to bugs.

just wondering what the bugs were?

@thestation, bugs were due to the fact that the contributor did not make an update for repo, before making a pull request.


[Feature request] Local training for object detection

hello EveryOne .
please Add localML feature to
object detection Scenario .

@briacht
I've seen several similar requests for local object detection training, do we want to prioritize this working item?

@briacht
@LittleLittleCloud
please  make it .

I would also love the ability to train object detection models locally. Ideally on the GPU. Model builder is fun to use thanks for working on it :)

Another customer asking for this!

Additional request: #1367

Another customer ask in the Marketplace Q&A

Thanks for quoting me, I forgot all about this!

No worries, thanks for the feedback @CommanderLake!

Unfortunately I still use VS2017 for which support has been dropped.

Another customer requested this feature https://github.com/dotnet/machinelearning-modelbuilder/issues/1965

I am also looking forward to this feature, and hope to experience it soon.

I am also interested in this feature.

Hope to support local training as soon as possible

I would love to have this feature.

@luisquintanilla to kick off partner team conversation for this.

I'm not allowed to use Azure, please add support for local object detection training. It would be a great feature.

@luisquintanilla  @beccamc   This Issue was removed from Fall 2022 Milestone. Will it support the future?

Hi @chenzanyu
We are working on bringing this scenario to ML.NET and Model Builder in the near future.

Would love to see this. I learn on my self hosted personal project then I bring that skill to work and host it on Azure. :)

This feature will be very helpful. Thanks to all who are working on this.

hi,
please Add localML feature to
object detection Scenario.

Hope they bring the Local feature to obj detection ;/

The local object detection training has been released in May. Simply upgrading model builder to 17.16.* or later to enjoying

Please update the UI to include 'Local` instead of just 'Azure'.  This is VS2022:

Was the local button removed after it has been released?
This article had it available: https://devblogs.microsoft.com/dotnet/object-detection-ml-dotnet-model-builder/


Remote window / integration tests is broken

illegalState - creating UNKNOWN service instance ExtensionGalleryService: Error: illegalState - creating UNKNOWN service instance ExtensionGalleryService
    at InstantiationService._createServiceInstanceWithOwner (file:///Users/bpasero/Development/Microsoft/monaco/out/vs/platform/instantiation/common/instantiationService.js:171:23)
    at InstantiationService._createAndCacheServiceInstance (file:///Users/bpasero/Development/Microsoft/monaco/out/vs/platform/instantiation/common/instantiationService.js:156:43)
    at InstantiationService._getOrCreateServiceInstance (file:///Users/bpasero/Development/Microsoft/monaco/out/vs/platform/instantiation/common/instantiationService.js:113:29)

Caused by 8743d95c76e76b5b665c5b1b1ba2ef9ebdbbad49

This is caused, because of using instantiationService to create DesktopRemoteExtensionManagementService.
https://github.com/microsoft/vscode/blob/1cc26ce/src/vs/workbench/services/extensionManagement/electron-browser/extensionManagementServerService.ts#L40
Error does not happen when I changed this to create the instance directly
const extensionManagementService = new DesktopRemoteExtensionManagementService(remoteAgentConnection.getChannel<IChannel>('extensions'), this.localExtensionManagementServer, logService, galleryService, configurationService, productService);

Pushing above fix for now to unblock builds.
@jrieken Any insights why the former did not work?

It seems using IInstantiationService to create DesktopRemoteExtensionManagementService is causing this error:
https://github.com/microsoft/vscode/blob/1cc26ce/src/vs/workbench/services/extensionManagement/electron-browser/extensionManagementServerService.ts#L40
No error is seen, when I changed this to instantiate DesktopRemoteExtensionManagementService directly
const extensionManagementService = new DesktopRemoteExtensionManagementService(remoteAgentConnection.getChannel<IChannel>('extensions'), this.localExtensionManagementServer, logService, galleryService, configurationService, productService);

Pushing this to unblock builds.
@jrieken any insights about the difference here?

@sandy081 Did you find anything out here? One other possible case could be a service depending on this service and since it's still creating it cannot be depended on

@jrieken Oh no, I did not find any.
I closed it as I was cleaning up issues for current milestone. I forgot about this.
Will reopen and investigate it during endgame (or debt week)

@jrieken Did some investigation but could not find out the root cause (also tried enabling trace in InstantiationService). Probably you might be faster in understanding it. I made it simpler to reproduce from sources

Comment out following line
https://github.com/microsoft/vscode/blob/6ddaba3a52b59b1679b07d1423ebc641ba72cf5b/src/vs/workbench/services/extensionManagement/electron-browser/extensionManagementServerService.ts#L33
Open remote window - you will see following error

ERR illegalState - creating UNKNOWN service instance ExtensionGalleryService: Error: illegalState - creating UNKNOWN service instance ExtensionGalleryService
    at InstantiationService._createServiceInstanceWithOwner (file:///Users/sandy081/work/vscode/out/vs/platform/instantiation/common/instantiationService.js:171:23)
    at InstantiationService._createAndCacheServiceInstance (file:///Users/sandy081/work/vscode/out/vs/platform/instantiation/common/instantiationService.js:156:43)
    at InstantiationService._getOrCreateServiceInstance (file:///Users/sandy081/work/vscode/out/vs/platform/instantiation/common/instantiationService.js:113:29)
    at Object.get (file:///Users/sandy081/work/vscode/out/vs/platform/instantiation/common/instantiationService.js:36:45)
    at Workbench.initLayout (file:///Users/sandy081/work/vscode/out/vs/workbench/browser/layout.js:141:42)
    at file:///Users/sandy081/work/vscode/out/vs/workbench/browser/workbench.js:67:26
    at InstantiationService.invokeFunction (file:///Users/sandy081/work/vscode/out/vs/platform/instantiation/common/instantiationService.js:43:24)
    at Workbench.startup (file:///Users/sandy081/work/vscode/out/vs/workbench/browser/workbench.js:61:38)
    at DesktopMain.open (file:///Users/sandy081/work/vscode/out/vs/workbench/electron-browser/desktop.main.js:61:52)

This is interesting... It does seems to be an issue with the instantiation service but I don't know yet what exactly. Whenever something is instantiated it's dependency graph (of services) is built and then root-by-root dependencies are created first. It seems that the extensionGalleryService appears as root two times, e.g after it has already been instantiated and that's something we don't expect.

Ok, this isn't a problem with the dependency graph but somewhat concurrent modifications of the internal instantiation service stats. This is the cause: https://github.com/microsoft/vscode/blob/6ddaba3a52b59b1679b07d1423ebc641ba72cf5b/src/vs/workbench/services/extensionManagement/electron-browser/extensionManagementServerService.ts#L41.
So, there is a dependency graph. We start with those nodes that have no dependencies and instantiate them, then remove those node, and restart with the new set of nodes. What's happening here is that resolving roots has side-effect on subsequent dependencies because it again uses the instantiation service. That leads to unexpected results because the dependency graph is now out-of-sync with the real world


Solution

HTML Portfolio

Welcome to the HTML Portfolio Project
This is a showcase of my work and skills.

About Me
Portfolio
Contact

About Me
I am a passionate web developer with a strong background in HTML, CSS, and JavaScript. I love creating beautiful and interactive websites that engage users.

Portfolio

Project 1
Description of Project 1.

Project 2
Description of Project 2.

Contact
If you'd like to get in touch with me, feel free to send an email to<EMAIL_ADDRESS>

© 2023 HTML Portfolio

portfolio


Can I deploy objects with different ports on a server?

E：An obj name corresponds to a port. For details, see < XXX. XXX. Obyadapter > in server.conf, where service, endpoint and protocol are one-to-one correspondence.
There won't be much benefit from deploying multiple instances on one server, because when the same service is deployed on one server, there will be no usability consideration. When one server hangs up, it will no longer provide available services.
C：一个obj name对应一个端口。具体可以看一下server.conf里的<xxx.xxx.objAdapter>，里面servant，endpoint和protocol是一一对应的；
一台服务器上面部署多个实例并不会有太多的收益 ，因为相同的服务部署在一台服务器上面 ，就没有可用性方面的考量了，当一台服务器挂掉的时候 ，就不再提供可用的服务了。


ParquetTpchTest.xxx often timeout after 10min

Bug description
We are seeing frequent timeouts for ParquetTpchTest.xxx tests. These tests seem to take more than 10 min to run. It would be nice to optimize the tests to run faster.
CC: @majetideepak @Yuhta @pedroerp
System information
n/a
Relevant logs
No response

All the time is being spent in writing TPC-H data to a DuckDB table after this change https://github.com/facebookincubator/velox/pull/6719/files
We do this per test making it ~19x slower.

CC: @duanmeng

The fix here https://github.com/facebookincubator/velox/pull/7860 allows the test to complete in around 1 minutes 18 seconds.
Improving the performance of DuckDbQueryRunner::createTable is likely non-trivial.


Center offset and weird behavior of lower part of the waveform (OutlineBuffer)

After doing my first implementation with the OutlineBuffer (based on the documentation in the Readme), I am running into the issue where there is a center deviation between the 2 halfs of the waveform, and the bottom half seems to behave weirdly.
Demonstration video: https://youtu.be/_qVR8wtTCcM
Is this expected behavior and if so, how could this be solved?
Thanks

Apologies, I missed the comments to that repository for a while.
This looks indeed odd. I haven't seen that in the project where I use the OutlineBuffer.
Just to rule out some possibilities:
What is the buffer? Is that directly from the microphone?
Is there any chance that there are invalid numbers in it?
I don't know how to reproduce it at the moment, maybe you can post some information, like what OS, and if applicable share some code.
Thanks for the feedback


Update licensing

This PR adds license headers and license checks as discussed in #92.
It also adds a CI check for license headers.
It's a pretty big PR, sorry, but I had to touch every single Go file in the repo.
I've left it to only Go files for now, the tool can do YAML files as well, but I figured this was big enough already.
Closes #92.

Codecov Report

Merging #590 (99398d5) into main (5f118ec) will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #590      +/-   ##
==========================================
+ Coverage   60.37%   60.46%   +0.08%
==========================================
  Files          46       46
  Lines        5593     5593
==========================================
+ Hits         3377     3382       +5
+ Misses       2006     2001       -5
  Partials      210      210

Impacted Files
Coverage Δ

internal/cmd/certgen.go
12.82% <ø> (ø)

internal/cmd/root.go
100.00% <ø> (ø)

internal/cmd/server.go
7.62% <ø> (ø)

internal/cmd/versions.go
28.57% <ø> (ø)

internal/cmd/xdstest.go
3.65% <ø> (ø)

internal/crypto/certgen.go
77.21% <ø> (ø)

internal/envoygateway/config/config.go
0.00% <ø> (ø)

internal/envoygateway/config/decoder.go
70.00% <ø> (ø)

internal/gatewayapi/contexts.go
76.02% <ø> (ø)

internal/gatewayapi/helpers.go
66.38% <ø> (ø)

... and 39 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Adds node modules as a volume

What's this PR do?
Mounts a volume for node_modules, apparently its that easy!
http://jdlm.info/articles/2016/03/06/lessons-building-node-app-docker.html
http://stackoverflow.com/questions/30043872/docker-compose-node-modules-not-present-in-a-volume-after-npm-install-succeeds
How should this be reviewed?
Can you docker-compose up without running npm install?
Relevant tickets
Fixes #754

Closing this in favor of Activity Events PR #756 ^

 Add Node Modules as a volume in Dockerfile

@deadlybutter Not sure how to test this one... or maintain the Docker setup in general...

@aaronschachter Me & sergii found a weird bug w/ Docker when it came to installing new npm modules, this was the fix. As I said during the meeting feel free to ignore Docker / remove it if you want! I think we were excited to play around with it but it's not being used on prod

@deadlybutter Since there aren't any plans to start using Docker in production in the near future, I'm going to close this and #754 for now.


Enable openshift e2e tests on centos

@jim-minter @jackfrancis @pweil-

@kargakis the openshift centos e2e test failed with:
$ az group deployment create --name openshift-eastus-14694 --resource-group openshift-eastus-14694 --template-file /go/src/github.com/Azure/acs-engine/_output/openshift-eastus-14694/azuredeploy.json --parameters /go/src/github.com/Azure/acs-engine/_output/openshift-eastus-14694/azuredeploy.parameters.json
2018/05/11 18:29:04
Error from deployment for openshift-eastus-14694 in resource group openshift-eastus-14694:exit status 1
2018/05/11 18:29:04 Command Output: ERROR: Marketplace purchase eligibilty check returned errors. See inner errors for details

I'll look into the failure on Monday but it looks like an issue with the CI subscription not being able to access the centos image.

@kwoodson can you walk me through how to check the enabled subscriptions in the centos image?

Also, seeing a permission issue when running locally that needs to be fixed before we merge this
https://github.com/Azure/acs-engine/issues/2960

@CecileRobertMichon can you please restart the test?

@kargakis it failed again with $ az group deployment create --name openshift-eastus-40186 --resource-group openshift-eastus-40186 --template-file /go/src/github.com/Azure/acs-engine/_output/openshift-eastus-40186/azuredeploy.json --parameters /go/src/github.com/Azure/acs-engine/_output/openshift-eastus-40186/azuredeploy.parameters.json 2018/05/16 16:18:55  Error from deployment for openshift-eastus-40186 in resource group openshift-eastus-40186:exit status 1 2018/05/16 16:18:55 Command Output: ERROR: Marketplace purchase eligibilty check returned errors. See inner errors for details.

@kwoodson any idea why we are seeing marketplace errors when using the published centos image?

Here are the image fields used for the centos image:
https://github.com/Azure/acs-engine/blob/bcda440129a9c662fc44499e5d37d2acd960dda9/pkg/acsengine/defaults.go#L96-L101

@CecileRobertMichon ping

@kargakis the latest test failed with a vm extension provisioning error so I restarted it

@kargakis please rebase
/lgtm

@CecileRobertMichon rebased, ptal
/unassign


Fix Dast workflow

The dast workflow still points to MIW configuration and flow for testing the catalog request

Fixed by https://github.com/eclipse-tractusx/tractusx-edc/pull/1278


New comment.

Dear human,
Here's a new entry for your approval. :tada:
Merge the pull request to accept it, or close it to send it away.
:heart: Your friend Staticman :muscle:

Field
Content

message
reverse phone free information lookup phone telus 411 find a person yellow pages nj cell phone director yellow pages usa directory online

phone dialer

name
Jessie

email
0519b0356cda370df021686d8b0f1a45

url
https://storify.com/reversecellnum1/free-reverse-cell-phone-lookup-no-charge

hidden

date
2017-06-18T00:36:22.692Z

Spammy link


TypeBuilder.hx - Uncaught exception Null Access

I've tried to figure this out myself for a few hours but I'm very new to Haxe.
/home/USER/haxelib/ldtk-haxe-api/git/src/ldtk/macro/TypeBuilder.hx:938: lines 938-944 : Uncaught exception Null Access
/home/USER/haxelib/ldtk-haxe-api/git/src/ldtk/macro/TypeBuilder.hx:82: characters 3-21 : Called from here
/home/USER/haxelib/ldtk-haxe-api/git/src/ldtk/Project.hx:36: characters 11-61 : Called from here
src/game/assets/World.hx:4: characters 5-80 : Called from here

This error occurs when I try to compile for any of the 4 platform options after following the guide on your site. I'm on Pop!_OS 22.04 LTS which is based on Ubuntu 22.04 LTS.
Haxe 4.2.5
ase: [2.0.1]
castle: [git]
deepnightLibs: 1.0.73 [git]
format: [3.5.0]
heaps-aseprite: 0.1.2 [git]
heaps: [git]
hldx: [1.10.0]
hlopenal: [1.5.0]
hlsdl: [1.10.0]
hscript: 2.5.0 [git]
ldtk-haxe-api: 1.0.0 [git]
redistHelper: [0.7.3]

Hi! Thanks for reporting this bug and sorry for inconvenience.
It's fixed, you may update the lib:
haxelib update ldtk-haxe-api


Post/exit calls

Hey @lubc @ercohen14 @mauro-oto,
I just wrote an article about our exit calls. Please check it out and let me know.
Thanks!

@etagwerker Cool! Looks good to me 👍


failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found

docker-compose.yaml
version: "3.9"

services:
  win10:
    image: dockurr/windows:1.09
    hostname: win10
    container_name: win10-dev
    stop_grace_period: 2m
    restart: unless-stopped
    environment:
      VERSION: "https://example.com/win10.iso"
      #VERSION: "win10"
      RAM_SIZE: "8G"
      CPU_CORES: "4"
      DISK_SIZE: "100G"
      MANUAL: "Y"
      TZ: Asia/Shanghai
    devices:
      - /dev/kvm
    cap_add:
      - NET_ADMIN
    ports:
      - "8006:8006"
      - "3389:3389/tcp"
      - "3389:3389/udp"
    volumes:
      - ./_docker-data/w10/storage:/storage

error log
[+] Running 1/1
 ✔ Container win10-dev  Started                                                                                0.0s
win10-dev  | ❯ Starting Windows for Docker v1.09...
win10-dev  | ❯ For support visit https://github.com/dockur/windows
win10-dev  |
win10-dev  | ❯ Creating a growable disk image in raw format with a size of 100G...
win10-dev  | ❯ Booting Windows using QEMU emulator version 8.1.2 ...
win10-dev  |
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
win10-dev  | BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
win10-dev  | BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
win10-dev  |
Press any key to boot from CD or DVD......

BdsDxe: failed to start Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0): Time out
win10-dev  | BdsDxe: loading Boot0003 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
win10-dev  | BdsDxe: starting Boot0003 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
win10-dev  |
UEFI Interactive Shell v2.2
win10-dev  | EDK II
win10-dev  | UEFI v2.70 (Debian distribution of EDK II, 0x00010000)
win10-dev  | Mapping table
win10-dev  |       FS0: Alias(s):CD0a0b:;BLK2:
win10-dev  |           PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)/CDROM(0x1)
win10-dev  |       FS1: Alias(s):F0a0:;BLK3:
win10-dev  |           PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)/VenMedia(C5BD4D42-1A76-4996-8956-73CDA326CD0A)
win10-dev  |      BLK4: Alias(s):
win10-dev  |           PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0)
win10-dev  |      BLK0: Alias(s):
win10-dev  |           PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
win10-dev  |      BLK1: Alias(s):
win10-dev  |           PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)/CDROM(0x0)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
^Ccanceled

file tree
# tree
.
├── docker-compose.yaml
└── _docker-data
    └── w10
        └── storage
            ├── data.img
            ├── win10.iso
            ├── windows.rom
            └── windows.vars

my  serverhost is ubuntu20, and windows iso is from https://windowsxlite.com/Optimum10ProV2/
Windows X-Lite (19045.3758) 'Optimum 10 Pro' by FBConan

you  mean file name  must be custom.iso needed instaed of win10.iso ???

well done

remark: https://windowsxlite.com/Optimum10ProV2/ this version win10 has a bug as ablove


Capitalized menu text

Capitalized menu text for 'Open Terminal Here' and 'Open Terminal in Project Root' to align it with Atom's convention.

LGTM, but can you squash this into one commit?

I can, sure. Why do you care? For cleanness (which I dig)?


idle_container configuration in openwhisk

Currently, the Invoker component configuration in the application.conf has the following configuration for container proxy :
container-proxy {
timeouts {
# The "unusedTimeout" in the ContainerProxy,
#aka 'How long should a container sit idle until we kill it?'
idle-container = 10 minutes
pause-grace = 50 milliseconds
}
how and where can I change the idle-container value?

change this value  idle-container = 10 minutes.

Change this value  idle-container = 10 minutes. You can do it by editing the application.conf or passing an environment variable to override the value.

Is in possible to change the environment variable without reinstalling through the helm or rebuild by gradle and then upgrade with helm?

@parichehrvn can you explain what is the difference btw idle-container & pause-grace???

@parichehrvn can you explain what is the difference btw idle-container & pause-grace???

@joey0320 When a container runs out, it stays running for up to 50 milliseconds. In other words, it is hot for up to 50 milliseconds. This time is determined by pause-grace.
If no request is made to execute the function on the container within these 50 milliseconds, the container will be suspended for 10 minutes. In these 10 minutes, the container is warm and if requested, it will have a warm start. This time is determined by idle-container.
The pause container is a container which holds the network namespace for the pod.

@joey0320 When a container runs out, it stays running for up to 50 milliseconds. In other words, it is hot for up to 50 milliseconds. This time is determined by pause-grace.
If no request is made to execute the function on the container within these 50 milliseconds, the container will be suspended for 10 minutes. In these 10 minutes, the container is warm and if requested, it will have a warm start. This time is determined by idle-container.
The pause container is a container which holds the network namespace for the pod.

Is it possible to change the environment variable without reinstalling through the helm or rebuild by gradle and then upgrade with helm?

@parichehrvn you do not need to rebuild but do need to redeploy.

Is it possible to change the environment variable without reinstalling through the helm or rebuild by gradle and then upgrade with helm?

@parichehrvn you do not need to rebuild but do need to redeploy.

close as resolved/no update


[BUG] Legend position between right axis and chart

Hello,
my problem is the position of the legend if i have an addional y axis on the right side.

I expected the legend to be on the outside like the position is set to left.

If i got an mistake in my settings here is what i use:
chart_test.txt
Thanks for your help!

@DerBaer1987 what version are you using? I thought that was fixed around 2.4 or 2.5

i'm using Version 2.6.0

@DerBaer1987 do you have a fiddle that reproduces this? What does your config look like?

https://jsfiddle.net/venagny4/
problem found. sometimes we add chart.js 2.5 and not 2.6. In 2.6 it is fixed.
excuse the circumstances.


persian unknown characters

Neovim shows unknown symbols for a valid utf-8 Persian text. Actually, this is related to Neovim 0.8.0 (development branch).

After stable release of 0.8.0 and having some minor releases the issue is still there, but I think Neovim team don't want to fix it, and they want to drop the Persian support, so I will stick with Emacs for writing Persian documents.


powershell task verbosePreference parameter does not work

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops-2019&fireglass_rsn=true#fireglass_params&tabid=a72a3d8c170676b3&start_with_session_counter=3&application_server_address=euroclear11.prod.fire.glass
following setting takes no effect on the job's powershell session configuration

task: PowerShell@2
inputs:
verbosePreference:  continue

@yangxinyun -- Xinyun, thank you for your feedback.  This repo is solely for documentation issues, and this seems product-related.  Please add it here:

Developer Community

cc @steved0x for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Not use RandomHorizontalFlip?

The train_transform() is not used in the base_transform. So does this project use  RandomHorizontalFlip?
Or this function is called other place?

Hi,
The complete data augmentation is undergo in the augmentation branch and is very close to completion, it just needs to be tested (I have been caught up with other work or it would already be done). However, random horizontal flip is not used anywhere else, so until that is merged with master we just apply the base transforms.

According to the paper, the data augmentation should only add ~3 - 5% to the mAP though.

Thanks!


This component is not functioning properly

This component is not working properly. Is there an error in my configuration?

This component is not working properly. Is there an error in my configuration?

Hey. I have stopped the working. I will get back. Stay tuned.


[Typo] README.md

In line 280 of the README.md it says In case if linting or testing is failing
It should say In case of linting or testing is failing
README.md

Can you assign me this?

I made a PR regarding this, https://github.com/trekhleb/javascript-algorithms/pull/888

I am new to open source, I want to take up the issue can you please guide me a bit. Can you please assign me to this task.

if its done then why issue is still opened?


wllkle/caching updates

Tested on: MacOS version: High Sierra v. 10.13.6.
Caching folder populated:

Merge is ready to be pushed into Master branch.


Login problems

Hello,
I changed my code as explained in another issue because I was not receiving the code but I'm not still able to login.
I debugged the DLL and  I saw that the code was accepted but there is an error in "PerformRequestAsynch()"
"Could not find member 'onlineAccess' on object of type 'Persona'. Path 'userAccountInfo.personas[0].onlineAccess', line 1, position 119."
Someone knows what could be the problem?
Thanks.

Add below properties to Persona class (namespace UltimateTeam.Toolkit.Models)
public string OnlineAccess { get; set; }
public string ReturningUserTier { get; set; }

Thank you for the reply... I made the change that you suggest me and now the error is changed.
503 (Service Unavailable) on the same method (PerformRequestAsynch()) that is caused calling LoginResponse.AuthData = await AuthAsync();
There are other changes to do?

Seems the same problem described on #399 but there I didn't find any solution.

I didn't yet understood if someone was able to use this API with Fifa 19 or not...

a small fix to the solution:
Instead of:
public string OnlineAccess { get; set; }
we should use:
public string onlineAccess { get; set; }

a small fix to the solution:
Instead of:
public string OnlineAccess { get; set; }
we should use:
public string onlineAccess { get; set; }

Always the same result...you are able to login? if yes can you post all the dll source code?

I have found some constant that was remained to 2018...changed and now I have a new error... {"Unable to get Phishing Token WebApp."}

Sometimes I'm able to login, other times I got the error, it was on the Resources.cs that you found the 2018 url?

I have found some constant that was remained to 2018...changed and now I have a new error... {"Unable to get Phishing Token WebApp."}
EDIT: ok maybe I have understood also this, some part of code need to be comment

have you found a solution for this?

Just add a comment on
// LoginResponse.PhishingToken = await ValidateAsync(LoginDetails);
on
PerformRequestAsync

i did that then it gave "Got no Nucleus Data and Auth Data during the Loginprocess" error, i then changed it to
LoginResponse.PhishingToken = new PhishingToken();
LoginResponse.PhishingToken.Token = LoginResponse.AuthData.phishingToken;
but data is very bad and i am spending countless hours trying to get the api working, it is a struggle :)

I made several changes...now I can't remember all...if can help this is the modified library that I'm using at the moment:
https://ufile.io/qract

Please, could you put a link to the version that worked with FUT19 to use as a start for FUT20? Thank you.


Sample distribution per cancer types?

Dear concern,
Could you please provide the statistics of the different types of data (i.e., for DNA methylation, copy numbers, mutations, miRNA, and gene expression) per cancer types?
I got the same from an old publication (Link: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3919969/pdf/nihms-549280.pdf, see page 14). However, it's pretty old and seems a lot of samples across other cancer types have subsequently been added.
Thanks in advance.

Hi BioXAI, thanks for you interest in this project! The specific repo stores analysis code for one publication under the TCGA PanCanAtlas umbrella. I do not have all those statistics on other datatypes easily available. This resource might point you in the right direction.

@gwaygenomics, thanks a million for the pointers.


Tesseract 4.0 Alpha results differe between IIS and Console App

Hi Charles,
Thanks for all the great work of making Tesseract 4.0 available.
I am developing a web application that uses Tesseract 4.0.0 Alpha dll. I get different results when I use it in an IIS Web application. The console application seems to produce better results. tessdata path is the same. I use the tessdata best. psm and engine mode are same. First, Is tesseract recommended for MVC application and if so What could be causing this difference?
Anyone has tried with IIS and faced similar issue? Your help is much appreciated.

I find a difference when passing Bitmap verses reading natively with Pix.  Bitmaps are not as good.
Sent from my iPad
On Nov 11, 2018, at 9:39 AM, rajeshkalpathi <notifications<EMAIL_ADDRESS>wrote:
Hi Charles,
Thanks for all the great work of making Tesseract 4.0 available.
I am developing a web application that uses Tesseract 4.0.0 Alpha dll. I get different results when I use it in an IIS Web application. The console application seems to produce better results. tessdata path is the same. I use the tessdata best. psm and engine mode are same. First, Is tesseract recommended for MVC application and if so What could be causing this difference?
Anyone has tried with IIS and faced similar issue? Your help is much appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://protect-us.mimecast.com/s/j5LgCzp9w5IMJZrQh41C5F?domain=github.com, or mute the threadhttps://protect-us.mimecast.com/s/K5mGCADAYoIN7XRLt8U2w_?domain=github.com.

I directly loadfromfile (png generated using Ghostscript). PNG is a 600 DPI image using the following gs options
-o "{@newFilePath}" -r600 -sPageList={pageNumber} -q -dTextAlphaBits=4 -dINTERPOLATE -dDITHER=600 -sDEVICE=png16m -dSAFER "{@pdfFile}"
Attaching a word document to highlight the difference. Kindly excuse me for not able to share the full png file.
Tesseract Github Issue 449.docx

I figured out the issue was due to an improper use of Pix file.
Thanks for your support.


findblock.php cron failure "Unable to add block Duplicate entry"

Im getting this errors on findblock cron..
the only thing i change was from mooples to ahmedbodi stratum..
2013-12-19 14:29:01 - INFO  --> Blockhash       Height  Amount  Confirmations   Diff        Time
2013-12-19 14:29:01 - INFO  --><PHONE_NUMBER>7c98b...  209029  1   27      0.68838563  2013-12-19 14:00:48
2013-12-19 14:29:01 - FATAL --> Unable to add block: 209029: SQL Query failed: Duplicate entry '209029-00000000367c98b3d9bd4dd238854a89aeb71ffd28153b18710d1e2d6' for key 'height'
2013-12-19 14:29:01 - INFO  --> 000000004cdbc72...  209035  1   21      1.03308847  2013-12-19 14:02:27
2013-12-19 14:29:02 - FATAL --> Unable to add block: 209035: SQL Query failed: Duplicate entry '209035-000000004cdbc72d45a416345d40496c4eb9d6bf9fa8922ce2b146b8c' for key 'height'
2013-12-19 14:29:02 - INFO  --><PHONE_NUMBER>5bab2...  209040  1   16      1.11958657  2013-12-19 14:05:03
2013-12-19 14:29:02 - FATAL --> Unable to add block: 209040: SQL Query failed: Duplicate entry '209040-00000000235bab201dcc14badb773a521623f8c226adfa364d80feb6a' for key 'height'
2013-12-19 14:29:02 - INFO  --><PHONE_NUMBER>473bc...  209014  1   42      0.32444515  2013-12-19 13:56:56
2013-12-19 14:29:02 - FATAL --> Unable to add block: 209014: SQL Query failed: Duplicate entry '209014-0000000175473bceee053b2d80a38f37fc8dd96efa45e03a155b22c94' for key 'height'
2013-12-19 14:29:02 - INFO  --> 00000000a2ae656...  209016  1   40      0.36526435  2013-12-19 13:57:10
2013-12-19 14:29:02 - FATAL --> Unable to add block: 209016: SQL Query failed: Duplicate entry '209016-00000000a2ae656d7ccd4abaa74856e3c1bc3dd5ff8b8c1199fa40609' for key 'height'
2013-12-19 14:29:02 - INFO  --> 000000013bfeb84...  209027  1   29      0.60933883  2013-12-19 14:00:32
2013-12-19 14:29:02 - FATAL --> Unable to add block: 209027: SQL Query failed: Duplicate entry '209027-000000013bfeb8476f8a404fe034d6a85ed3dd5ddf4eb139440849e03' for key 'height'

impossible to find a reliable translation for : "Your blockchain forked and broke the blocks created."
Can you detail a little bit to understand what you meant?

Maybe this helps :
There can be multiple transactions per block, the findblock.php can't handle it, because it processes transactions like there were blocks.
Look at the official documentation :
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list

listsinceblock
Get all transactions in blocks since block [blockhash], or all transactions if omitted.

Simply comment out the error to ignore it and it will do its job.

I don't a er hat on that would fix it. It already lists all new transactions since the last block and only looks at those with generate or immature as a status. Regular transactions like users paid will be ignored. Commenting this out can cause serious issues with any coin that likes to hard fork. But in the end it's an operators call if they are OK with it.

@TheSerapher
It fixed the error for generated blocks like this one which are including a fee
that's not a hard fork at all, but it causes a mysql exception thus breaking the cronjob
    [
        {
          "account": "coinium",
          "address": "LP3NeLiVZUKFnD8Zb75stXiUJoCyWJHq1D",
          "category": "generate",
          "amount": 49.50000000,
          "label": "coinium",
          "vout": 0
        },
        {
          "account": "coinium",
          "address": "LhE5mG6mCybU6ZttJ5TshqAfVHv2Z8Ttan",
          "category": "generate",
          "amount": 0.50000000,
          "label": "coinium",
          "vout": 1
        }
      ],

Probably something that wasn't done in the past? At least I don't remember a coin that generated two transactions for a single block causing a blockhash collision (some hash for two transactions). From your sample one could adjust the system and look at the "vout" field. Seems that if there is more than one only the first is the actual block.
Been too long out of the loop and too many coins left and right, but maybe someone will gain something from this :-)

I'm expericing this with Feathercoin 0.13.
2018-03-05 18:05:02 - INFO --> Starting RPC block detecion, blocks are stored in                                                                                Database 2018-03-05 18:05:02 - INFO --> | Blockhash            |          Height |     Am                                                                                ount | Confirmations |                Difficulty |               Time | 2018-03-05 18:05:02 - INFO --> | 709eaafd693392a0e... |         2114358 |                                                                                40 |             2 |<PHONE_NUMBER>5238 | 2018-03-05 18:01:3 | 2018-03-05 18:05:02 - INFO --> | 709eaafd693392a0e... |         2114358 |                                                                                0 |             2 |<PHONE_NUMBER>5238 | 2018-03-05 18:01:3 | 2018-03-05 18:05:02 - CRIT --> Unable to add block: (2114358) 709eaafd693392a0ec                                                                                d8254e9c2428192d1aa256447f36507c28c35872036f06: SQL Query failed: Duplicate entr                                                                                y '2114358-709eaafd693392a0ecd8254e9c2428192d1aa256447f36507c28c358' for key 'he                                                                                ight' 2018-03-05 18:10:02 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:15:01 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:20:01 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:25:02 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:30:01 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:35:01 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:40:02 - CRIT --> Cronjob is currently disabled due to errors, use                                                                                -f option to force running cron. 2018-03-05 18:42:36 - INFO --> Starting block share detection, this may take a w                                                                                hile 2018-03-05 18:42:36 - INFO --> | Block ID |     Height |          Amount |   Sha                                                                                re ID |                    Shares | Finder          | Worker          |                                                                                Type | 2018-03-05 18:42:36 - INFO --> |       89 |    2114358 |              40 |    11                                                                                34226 |           23207083.257233 | [19] jimmy24651 | jimmy24651.1    |  stratum


Remove watchedNamespace

Since d89c6a624cfd0962e2ed25238ec671baebda0ca5, this option was not respected.
It seems there is no complain, and maybe we can delete this option. And instead, using the new option MeshConfig.DiscoverySelectors
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test lint_istio

gencheck_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test lint_istio

gencheck_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
a2c76758cafc175f03be8348d514b8cd1b957a67
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign @howardjohn


Unifies createDashboard functions

This PR removes internal createDashboard and moves that login in to the public createDashboard :)

@javisantana I removed changes to the API from this PR, so it only includes some minor refactoring. Would you please take a look? Thanks!

:es:


Wrong object build on Rails 5

I am facing issue in Rails 5.1.4, when trying to creat recurring event. In Rails 4.x.x it works fine but since I upgraded to Rails 5, facing the below issue.
Here is my params

params = {"event":{"data":"title":"gk","event_type":"sync","notify":false,"start_datetime":"2017-11-04 15:30:00 UTC","repeat":true,"schedule":{"occurrence":"daily"},"end_schedule":{"ends":false}},"calendar_options":{"occurrence":"month","startdate":"2017-11-01 00:00:00 UTC"}}
2.3.1 :086 > Event.new(params)
=> #<Event id: nil, title: 'gk', created_by: nil, repeat: false, start_datetime: nil, end_schedule: {}, occurences_completed: 0, data: nil, schedule: #<IceCube::Schedule:0x0000000a8cef60 @start_time=2017-11-03 13:46:21 +0000, @end_time=2017-11-03 14:46:21 +0000, @all_recurrence_rules=[], @all_exception_rules=[]>, event_type: nil, notify: false, notification_schedule: nil, created_at: nil, updated_at: nil>

When I checked schedule, it returns me IceCuve::Schedule object instead of Hash.

2.3.1 :087 >event.schedule
=> #<IceCube::Schedule:0x0000000a8cef60 @start_time=2017-11-03 13:46:21 +0000, @end_time=2017-11-03 14:46:21 +0000, @all_recurrence_rules=[], @all_exception_rules=[]>

Expected:

2.3.1 :087 >event.schedule
=> {"occurrence":"daily"}

What is wrong here, do I need to make some changes to work it.
Please let me know if you need further information regarding the issue.

IceCube doesn't do anything to attach itself to your Event rails model. What are you using to integrate it?

Hi @avit ,
Here is what I am using ice_cube with my ActiveRecord model.
class Event < ApplicationRecord
  include IceCube

  serialize :schedule, IceCube::Schedule
end

So When object is initializing, I am getting the output as earlier mentioned.

@sourabhu-cuelogic you need to explicitly call #to_hash method, e.g.
event.schedule.to_hash


Support uploading packages to Google Cloud Storage

There are sometimes issues with uploading large blobs (>1GB) to App Engine Blobstore.  If Simian supported serving blobs in Google Cloud Storage (aka GCS), then admins would be able to work around Blobstore issues by uploading to GCS directly.
Simian could either ingest from GCS and add to it's Blobstore instance, or just serve directly from GCS:
https://cloud.google.com/appengine/docs/python/blobstore/#Python_Using_the_Blobstore_API_with_Google_Cloud_Storage

This would be a great feature, I am running into these same issues. Thanks

how are things looking on this? I'm in the process of populating our simian instance and uploading seems really slow despite my 40Mbps upload speed.... 75 minutes to upload 1GB of data

Sorry, no news here.  I doubt we'll be able to work on this anytime soon.

GCS bucket can be specified with BLOBSTORE_GS_BUCKET env variable in app.yaml


Default support for .ruby-env? (via rvm)

ref: https://rvm.io/workflow/projects#project-file-ruby-version

Some projects require extra configuration in environment; this is supported by using the .ruby-env file:

echo "JRUBY_OPTS=--1.9" >> .ruby-env
This variable will be set when entering the project directory and reverted to its previous value when exiting the project directory.

It looks like it uses bash syntax, so you should be able to call:
Dotenv.load(".ruby-env")

Let me know if that doesn't work for you.

yeah, that would work, of course.  Just though you might like the idea


TestCafe can't compile TypeScript projects that have some specific options in tsconfig.json

What is your Test Scenario?
Run tests written in TypeScript and enable the following TypeScript options in tsconfig.json:
"declaration"
"sourceMap"
"noEmit"
"noEmitHelpers"
"mapRoot"

And probably the following options too:
"rootDir"
"sourceRoot"
"lib"
"typeRoots"
"types"

What is the Current behavior?
TestCafe can't compile test files and shows an error about conflicting options.
What is the Expected behavior?
Successful compilation.
What is your web application and your TestCafe test code?

Execute this command...
See the error...

Your Environment details:

testcafe version:                   1.3.1-rc.1
node.js version:
command-line arguments:
browser name and version:
platform and version:
other:

I can't get the point for this feature.
For a well structure project this should not be a problem.
You webapp should have its tsconfig under webapp directory and test script should have a seperated one under test script directory.
I don't think it worth to introduce a breaking change for such a feature.

We also seem to have a problem with esModuleInterop

Thank you for the info, @Pita . We will check it when we get ready to fix the issue.

Any updates? It seems this causes a problem when I'm trying to import dayjs lib in ts-mode, like:

import dayjs from 'dayjs';

and when I'm trying to run test I get:

Module '".../node_modules/dayjs/index"' can only be default-imported using the 'esModuleInterop' flag

That's very annoying, I cant import any of date-libraries like moment or dayjs and this seems to me as a critical bug since I cant use ts-testcafe to write my tests on.

Also seems to be related to https://github.com/DevExpress/testcafe/issues/3970

@orihomie consider using import dayjs = require( 'dayjs')
(https://www.typescriptlang.org/docs/handbook/modules.html#export--and-import--require)

I've worked around using --ts-config-path and passing
{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true
  }
}

onto testcafe launch script.