Error connecting Integration

I am trying to add the integration and when I put the IP address in it throws the fault in the screenshot. Anything I am doing wrong?

Can you include some logs please?

I can't see anything in the logs in regards to this integration. I have removed the original foxess modbus integration. Including deleting all the config.yaml section of it too

Are you using the same IP? Same port? H1 inverter? Slave address 247? LAN or W610 (or other RTU to TCP adapter)?

Same IP as before, same port 502, H1 inverter, Slave should still be 247 and it is hard wired via LAN.
Master version 1.48
Slave version 1.02
Manager version 1.45

Ok, can you try -> v1.0.2 please and let me know what's in the logs? You'll need to turn on debug logging for the component.

On version 1.0.3 now and still the same. Here is the only thing I have seen in the logs for it.
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:370
Integration: Modbus (documentation, issues)
First occurred: 7:31:37 PM (1 occurrences)
Last logged: 7:31:37 PM
modbus HA-FoxESS-Modbus-LAN communication closed

Can you send me a screenshot of that log message please? I don't recognise the format.

Here is another log I can get if input an incorrect IP address but it doesn't appear when I put the correct IP in.
This error originated from a custom integration.
Logger: pymodbus.logging
Source: custom_components/foxess_modbus/modbus_client.py:22
Integration: FoxESS - Modbus (documentation, issues)
First occurred: 7:38:01 PM (2 occurrences)
Last logged: 7:38:04 PM
Connection to (<IP_ADDRESS>, 502) failed: timed out

Have you disabled the other modbus integration? The previous log you sent 'connection closed' looks to be from the HA modbus client.

Just comment out the references in your configuration file.
If you hit 'full logs' do you see this? It's set at info level so it won't appear in the overview window.
https://github.com/nathanmarlor/foxess_modbus/blob/main/custom_components/foxess_modbus/modbus_client.py#L30

I don't see what you've sent me but could you clarify what I need in my config file to get the logging you require?

Add this:
logger:
default: info
logs:
custom_components.foxess_modbus: debug

I get this by adding that?

It mustn't register the logger before the config has completed.
The only thing I can suggest is to try modpoll directly ->https://www.modbusdriver.com/modpoll.html

Logger: pymodbus.logging
Source: runner.py:179
First occurred: 6:32:34 PM (2 occurrences)
Last logged: 6:32:38 PM
Ignoring launch of delayed reconnection, another is in progress
Failed to connect: [Errno 104] Connect call failed ('<IP_ADDRESS>', 502)
This is the only error I can get and still can't get it to connect with 1.0.4

This error originated from a custom integration.
Logger: pymodbus.logging
Source: custom_components/foxess_modbus/modbus_client.py:22
Integration: FoxESS - Modbus (documentation, issues)
First occurred: 6:50:27 PM (3 occurrences)
Last logged: 6:50:27 PM
Failed to connect: [Errno 111] Connect call failed ('<IP_ADDRESS>', 502)
Ignoring launch of delayed reconnection, another is in progress
I can get this error if I put an incorrect IP in

Are you sure you don't have the original modbus integration running? The LAN port only seems to like one connection.

I have deleted all the information from the config file and anything in the custom components folder too. Also removed anything from HACS. Restarted and still the same. But I do feel like something on the network is still talking to the Modbus port or it could be something to do with my home network potentially stopping this integration from having access. How much does this differ to the original Modbus integration?

I haven't checked but it's likely using the exact same pymodbus library. I've been testing against both the W610 and LAN port and noticed that the LAN port stopped responding. I forced a disconnect and it came back alive shortly after. Maybe worth disconnecting your ethernet connection, letting the inverter lose it's IP etc then reconnect?

I have set my inverter with a fixed IP so I might change it to another address and cycle the connection to see what it does.

Very new to modpoll but here is what I am able to get so far.

I do have the same issue with my USR-610. there is no other integration running that can cause the connection error on modbus.
When using gmodbus, I can connect perfectly fine and read data
restarting the USR-610 does not help

I wonder if this is a firmware issue at the inverter end? I am on Master version 1.48 Slave version 1.02 Manager version 1.45

I'm don't think so, because I can read all the data from the USR-610
but just to check, I have a H3:
Master : 1.67 Slave : 1.02Manager : 1.51

@benbeton H3s aren't supported yet.

@nathanmarlor I know, but I thought the USR should be usable aswell, maybe with restrictions. I'll happy to help with the H3 integration

Did the full reboot and nothing changed. Just to clarify this can be done via the direct LAN port on the inverter?

Yep, I've been testing against both RTU -> TCP and direct into the LAN port. Copy/paste your HA config here and I'll have a quick look?

`
Loads default set of integrations. Do not remove.
default_config:
Text to speech
tts:

platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
frontend:
themes: !include_dir_merge_named themes
FoxESS Modbus Plugin - Configuration and Sensor Mappings
Source https://github.com/StealthChesnut/HA-FoxESS-Modbus
This file isn't a valid configuration file!
Instructions:
copy the custom_components directory to your HA custom_components directory
Add ONE of the modbus: lines to your configuration.yaml
Add the sensors below to your configuration.yaml

USB: Edit the file to update the connection settings

LAN: Add a new secret to your secrets file - FoxESSInverterIP:
#modbus: !include custom_components/HA-FoxESS-Modbus/modbusUSB.yaml
modbus: !include custom_components/HA-FoxESS-Modbus/modbusLAN.yaml
#Sensors turn power values into power/hour values for meters
sensor:
- method: left
name: pv1_sum
platform: integration
round: 2
source: sensor.pv1_power
unit_time: h
- method: left
name: pv2_sum
platform: integration
round: 2
source: sensor.pv2_power
unit_time: h
- method: left
name: pv_total_sum
platform: integration
round: 2
source: sensor.pv_power_now
unit_time: h
- method: left
name: load_sum
platform: integration
round: 2
source: sensor.load_power
unit_time: h
- method: left
name: bat_charge_sum
platform: integration
round: 2
source: sensor.battery_charge
unit_time: h
- method: left
name: bat_discharge_sum
platform: integration
round: 2
source: sensor.battery_discharge
unit_time: h
- method: left
name: feedin_sum
platform: integration
round: 2
source: sensor.feed_in_power
unit_time: h
- method: left
name: grid_consumption_sum
platform: integration
round: 2
source: sensor.grid_consumption
unit_time: h
- platform: integration
name: losses_sum
source: sensor.system_losses
unit_time: h
method: left
round: 2
#Templates enable math operations against states/values to give us better data
template:
- sensor:
- name: "Battery Discharge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) > 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Battery Charge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) < 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "Feed In Power"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) > 0 %}
{{ states('sensor.grid_ct') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Grid Consumption"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) < 0 %}
{{ states('sensor.grid_ct') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "PV Power Now"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ (states('sensor.pv1_power') | float(default=0) + states('sensor.pv2_power') | float(default=0) ) * 1 }}
- name: "PV Energy Daily"
device_class: "energy"
unit_of_measurement: "kWh"
state: >
{{ ((states('sensor.pv1_daily') | float(default=0) + states('sensor.pv2_daily') | float(default=0) ) * 1 ) | round(2) }}
- name: "System Losses"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ ((states('sensor.pv1_power') | float(default=0)
+ states('sensor.pv2_power') | float(default=0)
+ states('sensor.grid_consumption') | float(default=0)
+ states('sensor.battery_discharge') | float(default=0)
- states('sensor.battery_charge') | float(default=0)
- states('sensor.feed_in_power') | float(default=0)
- states('sensor.load_power') | float(default=0) )) | round(2) }}
- name: "Time Period 1 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 1 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
# Utility Meters - Provides meters to be used with the energy dashboard and reset daily
utility_meter:
load_daily:
source: sensor.load_sum
cycle: daily
pv1_daily:
source: sensor.pv1_sum
cycle: daily
pv2_daily:
source: sensor.pv2_sum
cycle: daily
bat_charge_daily:
source: sensor.bat_charge_sum
cycle: daily
bat_discharge_daily:
source: sensor.bat_discharge_sum
cycle: daily
feedin_daily:
source: sensor.feedin_sum
cycle: daily
grid_daily:
source: sensor.grid_consumption_sum
cycle: daily
losses_daily:
source: sensor.losses_sum
cycle: daily`

Loads default set of integrations. Do not remove.
default_config:
Text to speech
tts:

platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
frontend:
themes: !include_dir_merge_named themes
FoxESS Modbus Plugin - Configuration and Sensor Mappings
Source https://github.com/StealthChesnut/HA-FoxESS-Modbus
This file isn't a valid configuration file!
Instructions:
copy the custom_components directory to your HA custom_components directory
Add ONE of the modbus: lines to your configuration.yaml
Add the sensors below to your configuration.yaml

USB: Edit the file to update the connection settings

LAN: Add a new secret to your secrets file - FoxESSInverterIP:
#modbus: !include custom_components/HA-FoxESS-Modbus/modbusUSB.yaml
modbus: !include custom_components/HA-FoxESS-Modbus/modbusLAN.yaml
#Sensors turn power values into power/hour values for meters
sensor:
- method: left
name: pv1_sum
platform: integration
round: 2
source: sensor.pv1_power
unit_time: h
- method: left
name: pv2_sum
platform: integration
round: 2
source: sensor.pv2_power
unit_time: h
- method: left
name: pv_total_sum
platform: integration
round: 2
source: sensor.pv_power_now
unit_time: h
- method: left
name: load_sum
platform: integration
round: 2
source: sensor.load_power
unit_time: h
- method: left
name: bat_charge_sum
platform: integration
round: 2
source: sensor.battery_charge
unit_time: h
- method: left
name: bat_discharge_sum
platform: integration
round: 2
source: sensor.battery_discharge
unit_time: h
- method: left
name: feedin_sum
platform: integration
round: 2
source: sensor.feed_in_power
unit_time: h
- method: left
name: grid_consumption_sum
platform: integration
round: 2
source: sensor.grid_consumption
unit_time: h
- platform: integration
name: losses_sum
source: sensor.system_losses
unit_time: h
method: left
round: 2
#Templates enable math operations against states/values to give us better data
template:
- sensor:
- name: "Battery Discharge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) > 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Battery Charge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) < 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "Feed In Power"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) > 0 %}
{{ states('sensor.grid_ct') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Grid Consumption"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) < 0 %}
{{ states('sensor.grid_ct') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "PV Power Now"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ (states('sensor.pv1_power') | float(default=0) + states('sensor.pv2_power') | float(default=0) ) * 1 }}
- name: "PV Energy Daily"
device_class: "energy"
unit_of_measurement: "kWh"
state: >
{{ ((states('sensor.pv1_daily') | float(default=0) + states('sensor.pv2_daily') | float(default=0) ) * 1 ) | round(2) }}
- name: "System Losses"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ ((states('sensor.pv1_power') | float(default=0)
+ states('sensor.pv2_power') | float(default=0)
+ states('sensor.grid_consumption') | float(default=0)
+ states('sensor.battery_discharge') | float(default=0)
- states('sensor.battery_charge') | float(default=0)
- states('sensor.feed_in_power') | float(default=0)
- states('sensor.load_power') | float(default=0) )) | round(2) }}
- name: "Time Period 1 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 1 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
# Utility Meters - Provides meters to be used with the energy dashboard and reset daily
utility_meter:
load_daily:
source: sensor.load_sum
cycle: daily
pv1_daily:
source: sensor.pv1_sum
cycle: daily
pv2_daily:
source: sensor.pv2_sum
cycle: daily
bat_charge_daily:
source: sensor.bat_charge_sum
cycle: daily
bat_discharge_daily:
source: sensor.bat_discharge_sum
cycle: daily
feedin_daily:
source: sensor.feedin_sum
cycle: daily
grid_daily:
source: sensor.grid_consumption_sum
cycle: daily
losses_daily:
source: sensor.losses_sum
cycle: daily

`
Loads default set of integrations. Do not remove.
default_config:
Text to speech
tts:

platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
frontend:
themes: !include_dir_merge_named themes
FoxESS Modbus Plugin - Configuration and Sensor Mappings
Source https://github.com/StealthChesnut/HA-FoxESS-Modbus
This file isn't a valid configuration file!
Instructions:
copy the custom_components directory to your HA custom_components directory
Add ONE of the modbus: lines to your configuration.yaml
Add the sensors below to your configuration.yaml

USB: Edit the file to update the connection settings

LAN: Add a new secret to your secrets file - FoxESSInverterIP:
#modbus: !include custom_components/HA-FoxESS-Modbus/modbusUSB.yaml
modbus: !include custom_components/HA-FoxESS-Modbus/modbusLAN.yaml
#Sensors turn power values into power/hour values for meters
sensor:
- method: left
name: pv1_sum
platform: integration
round: 2
source: sensor.pv1_power
unit_time: h
- method: left
name: pv2_sum
platform: integration
round: 2
source: sensor.pv2_power
unit_time: h
- method: left
name: pv_total_sum
platform: integration
round: 2
source: sensor.pv_power_now
unit_time: h
- method: left
name: load_sum
platform: integration
round: 2
source: sensor.load_power
unit_time: h
- method: left
name: bat_charge_sum
platform: integration
round: 2
source: sensor.battery_charge
unit_time: h
- method: left
name: bat_discharge_sum
platform: integration
round: 2
source: sensor.battery_discharge
unit_time: h
- method: left
name: feedin_sum
platform: integration
round: 2
source: sensor.feed_in_power
unit_time: h
- method: left
name: grid_consumption_sum
platform: integration
round: 2
source: sensor.grid_consumption
unit_time: h
- platform: integration
name: losses_sum
source: sensor.system_losses
unit_time: h
method: left
round: 2
#Templates enable math operations against states/values to give us better data
template:
- sensor:
- name: "Battery Discharge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) > 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Battery Charge"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.battery_discharge_power') | float(default=0) ) < 0 %}
{{ states('sensor.battery_discharge_power') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "Feed In Power"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) > 0 %}
{{ states('sensor.grid_ct') | float(default=0) * 1 }}
{% else %}
0
{% endif %}
- name: "Grid Consumption"
device_class: "power"
unit_of_measurement: "kW"
state: >
{% if (states('sensor.grid_ct') | float(default=0) ) < 0 %}
{{ states('sensor.grid_ct') | float(default=0) * -1 }}
{% else %}
0
{% endif %}
- name: "PV Power Now"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ (states('sensor.pv1_power') | float(default=0) + states('sensor.pv2_power') | float(default=0) ) * 1 }}
- name: "PV Energy Daily"
device_class: "energy"
unit_of_measurement: "kWh"
state: >
{{ ((states('sensor.pv1_daily') | float(default=0) + states('sensor.pv2_daily') | float(default=0) ) * 1 ) | round(2) }}
- name: "System Losses"
device_class: "power"
unit_of_measurement: "kW"
state: >
{{ ((states('sensor.pv1_power') | float(default=0)
+ states('sensor.pv2_power') | float(default=0)
+ states('sensor.grid_consumption') | float(default=0)
+ states('sensor.battery_discharge') | float(default=0)
- states('sensor.battery_charge') | float(default=0)
- states('sensor.feed_in_power') | float(default=0)
- states('sensor.load_power') | float(default=0) )) | round(2) }}
- name: "Time Period 1 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 1 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_1_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - Start Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_start') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
- name: "Time Period 2 - End Time"
icon: "mdi:calendar-clock"
state: >
{% set raw_time = states('sensor.time_period_2_end') | int %}
{% set hours = raw_time // 256 %}
{% set minutes = raw_time - (hours * 256) %}
{{ strptime(hours | string + ":" + minutes | string, '%H:%M').time() }}
# Utility Meters - Provides meters to be used with the energy dashboard and reset daily
utility_meter:
load_daily:
source: sensor.load_sum
cycle: daily
pv1_daily:
source: sensor.pv1_sum
cycle: daily
pv2_daily:
source: sensor.pv2_sum
cycle: daily
bat_charge_daily:
source: sensor.bat_charge_sum
cycle: daily
bat_discharge_daily:
source: sensor.bat_discharge_sum
cycle: daily
feedin_daily:
source: sensor.feedin_sum
cycle: daily
grid_daily:
source: sensor.grid_consumption_sum
cycle: daily
losses_daily:
source: sensor.losses_sum
cycle: daily`

All my comments are missing when I paste it?

@andykorol1  you've still got the modbus include in there?

So you reboot with that, confirm no sensors load etc. but modpoll still doesn't work?

Yeah reboot with it as is, my sensors still show in my dashboard but just at the last known value as they still show up as an entity in the entities list. Had another play with modpoll can get it to show a reply time out error now by changing it to RTU over TCP

I'm definitely seeing some thing from the inverter via modpoll as if I put an incorrect IP in it says there is no slave but with the correct IP I get the reply time out error. What version of firmware are you using it on?

That could be it - perhaps they put the model type in a different place in the modbus address space. Can you get anything from addresses 10000 or 30000? That's where the model number for RTU and TCP connections lives respectively.

I've been trying to use CAS modbus and get the following error
TCP <IP_ADDRESS>:502 timeout: 3
Device: 247
Read Coil status starting at 30000 for 1
[03/15/23 22:16:28] Ready...
[03/15/23 22:16:49] Connect to TCP <IP_ADDRESS>:502 timeout: 3
[03/15/23 22:16:49] => Poll: F7 01 01 2B 00 01
[03/15/23 22:16:49] <= Response: F7 81 02
[03/15/23 22:17:21] Recv error: Exception Response:
The device responded but with an error instead of data
0x02 - ILLEGAL DATA ADDRESS

Progress finally!!

@andykorol1 your model number starts with AIO so the autodetect isn't working. Should be able to add it. To confirm you were using the modbus USB file with no modifications?

Modbus LAN with no modifications

Can you try this please?
https://github.com/nathanmarlor/foxess_modbus/releases/tag/v1.3.0b1

I've got the same issue still, but I am doing it remotely on my phone so will need to go through it all when I get home

I too have an AIO that is connected via LAN and worked previously.  That instance of HA is shut down and I am now testing on another.  I have the latest version and reset everything as described above.  I get the same error as the very first post after I enter my modbus host.
I get the same output from modpoll as @andykorol1 just above with the same command and below is my log:
2023-03-19 13:17:23.233 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Reading register: (10000, 10, (247)) 2023-03-19 13:17:23.233 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Connecting to modbus - ({'modbus_type': 'TCP', 'host': '<IP_ADDRESS>', 'port': '502'}) 2023-03-19 13:17:23.300 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Closing connection to modbus 2023-03-19 13:17:23.301 WARNING (MainThread) [custom_components.foxess_modbus.config_flow] ModbusIOException() 2023-03-19 13:19:08.000 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Reading register: (10000, 10, (247)) 2023-03-19 13:19:08.000 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Connecting to modbus - ({'modbus_type': 'TCP', 'host': '<IP_ADDRESS>', 'port': '502'}) 2023-03-19 13:19:08.087 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Closing connection to modbus 2023-03-19 13:19:08.088 WARNING (MainThread) [custom_components.foxess_modbus.config_flow] ModbusIOException() 2023-03-19 13:45:16.118 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Reading register: (10000, 10, (247)) 2023-03-19 13:45:16.118 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Connecting to modbus - ({'modbus_type': 'TCP', 'host': '<IP_ADDRESS>', 'port': '502'}) 2023-03-19 13:45:16.343 DEBUG (MainThread) [custom_components.foxess_modbus.modbus_client] Closing connection to modbus 2023-03-19 13:45:16.344 WARNING (MainThread) [custom_components.foxess_modbus.config_flow] ModbusIOException()

@andykorol1 @m24andrew please try v1.4.0b2.

Hi Nathan, unfortunately I am experiencing the same here.
To exclude all possibile issues due to my HA installation I stopped the VM and created a brand new VM_test (then installed HACS and downloaded your script, nothing else).
I get the same error as the other guys here, but if I open modpoll from the same machine I can get a response just fine.

I'm reaching 30000 because I'm still running on pure LAN.
I'm sorry if I'm giving you headaches, it's really not my intention but something is weird here (and as you said it's likely my/our fault but I can't really pinpoint what the issue is...)
Set-up:
PC (running VM*) (and running modpoll) <--> Router <--> Unmanaged Switch <--> H1 Inverter [LAN port]
VM* fresh ova_9.5 downloaded tonight
Questions:
Do you see anything wrong with my setup, or that you'd like to see different?
Did you try connecting with pure LAN to your Inverter? Or are you aware of anyone who successfully connected in this way?

Tomorrow morning I'm gonna start again by trying to restart the inverter. Maybe that's it... I really DK
Ah BTW, just to leave a trace:
Master : 1.54
Slave : 1.02
Manager : 1.57

@Ndrinta Have you tried the latest bet?

On it.

Winner winner chicken dinner!

Hopefully @m24andrew and @andykorol1 have similar success!

I'm now comparing the newly created entities with stuff I might have altered already in my config because I found a few "_2", and I know that should't have happened.

Yeah, I was using an old Modbus config with lots of custom stuff and a few sensor names were already taken, just done some adjustments and all the automation should be happy as nothing had ever happened.
Thanks 👍 you are great!

FYI @Ndrinta I've just released this as v1.3.1 (not v1.4.x) as the LAN issue goes back white a way. It doesn't change anything - it's just a version number - but in case you were wondering what happened to v1.4...

@nathanmarlor All sorted and working perfectly now! Thank you so much for your hardwork.


Drop pygeos

Recently the bot update 0.3.0 PR ( https://github.com/conda-forge/dask-geopandas-feedstock/pull/11 ) was merged. However it did not include dependency updates. Upstream pygeos was dropped. However it is still listed as a dependency here
https://github.com/conda-forge/dask-geopandas-feedstock/blob/7663128f7c8f9affb79e3e81780cafefe8560542/recipe/meta.yaml#L24
It would be good to drop the dependency in the recipe. May also be worthwhile to patch the repodata to drop the dependency. Also it may be worth enabling Grayskull for the update bot by updating conda-forge.yml. For example ( https://github.com/conda-forge/dask-cuda-feedstock/pull/16 )

May also be worthwhile to patch the repodata to drop the dependency

I suppose that is not needed (or at least not critical).
Basically, the dependency logic that we would like to express is "shapely>=2 OR pygeos", but I don't think you can express such conditional dependency.
So we removed pygeos as dependency to allow people to not install it (if they know they have shapely>=2), but if you are using older shapely (not all packages already are compatible with the latest shapely), you still need pygeos.

Just came across this, as currently installing dask-geopandas from conda-forge brings in pygeos no matter what, even if you do have shapely2 and therefore the warning keeps coming on import (which is avoidable of course with the environment variable).
UserWarning: Shapely 2.0 is installed, but because PyGEOS is also installed, GeoPandas will still use PyGEOS by default for now. To force to use and test Shapely 2.0, you have to set the environment variable USE_PYGEOS=0. You can do this before starting the Python process, or in your code before importing geopandas:

import os
os.environ['USE_PYGEOS'] = '0'
import geopandas

In a future release, GeoPandas will switch to using Shapely by default. If you are using PyGEOS directly (calling PyGEOS functions on geometries from GeoPandas), this will then stop working and you are encouraged to migrate from PyGEOS to Shapely 2.0 (https://shapely.readthedocs.io/en/latest/migration_pygeos.html).
  import geopandas

Started a new PR at #15 to drop pygeos (based on #13, but without the inspect-grayskul bot stuff). Note that this is applied on dask-geopandas 0.3.1. Would need a repodata-patch for dask-geopandas 0.3.0 if there's interest.

Yes, we can probably just drop pygeos completely nowadays, and not try to express "shapely>=2 OR pygeos" (given that shapely 2.0 is no longer just released). @weiji14 Thanks for the PR!


Mobile Number Update[FEATURE]

I'm healthcare worker ,my name was registered by our hospital in the bulk registration my mobile last digit was entered wrong.
i have took the vaccine of both doses but i cannot able to get the vaccination certificate.requesting you kindly make provision for updating mobile number,also don't have any option for downloading vaccination certificate by beneficiary id earlier it was available.

my vaccine 1 dose done using another mobile but now i am required to change my cell no.

I have vaccinated 1st dose with another mobile no but now I want to change my mobile no

Kindly make this possible with the help of the proof provided

My father has been vaccinated with both the dose however mobile number entered by operator is wrong due to bulk updating. Now i am unable to download the certificate. Also since we know the number we tried to contact the person to transfer number but he denies to help.
Instead of mobile number being mandatory requirement, indentification document through which it is registered should be mandatory to download certificate.

9955901897

Mobile number chek kiya jay


petfood-metric pod can't start

in CloudWatch Evidently step, petfood pod can't start
$ kubectl get pods | grep petfood

petfood-5f7758dfbb-p4pnn                0/1     InvalidImageName   0               23m
petfood-5f7758dfbb-tw82p                0/1     InvalidImageName   0               23m
petfood-metric-bdfb8d576-klxb7          0/1     CrashLoopBackOff   8 (4m18s ago)   20m
petfood-metric-bdfb8d576-vgqsn          0/1     CrashLoopBackOff   8 (4m43s ago)   20m

$ kubectl logs petfood-metric-bdfb8d576-klxb7
[2024-05-01 11:21:49 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2024-05-01 11:21:49 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:5000 (1)
[2024-05-01 11:21:49 +0000] [1] [INFO] Using worker: sync
[2024-05-01 11:21:49 +0000] [8] [INFO] Booting worker with pid: 8
[2024-05-01 11:21:49 +0000] [9] [INFO] Booting worker with pid: 9
[2024-05-01 11:21:49 +0000] [10] [INFO] Booting worker with pid: 10
[2024-05-01 11:21:49 +0000] [11] [INFO] Booting worker with pid: 11
[2024-05-01 11:21:49 +0000] [8] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
    worker.init_process()
  File "/usr/local/lib/python3.8/site-packages/gunicorn/workers/base.py", line 134, in init_process
    self.load_wsgi()
  File "/usr/local/lib/python3.8/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/usr/local/lib/python3.8/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/usr/local/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
    return self.load_wsgiapp()
  File "/usr/local/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/usr/local/lib/python3.8/site-packages/gunicorn/util.py", line 359, in import_app
    mod = importlib.import_module(module)
  File "/usr/local/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/app/petfood-metric.py", line 10, in <module>
    from aws_xray_sdk.ext.flask.middleware import XRayMiddleware
  File "/usr/local/lib/python3.8/site-packages/aws_xray_sdk/ext/flask/middleware.py", line 1, in <module>
    import flask.templating
  File "/usr/local/lib/python3.8/site-packages/flask/__init__.py", line 7, in <module>
    from .app import Flask as Flask
  File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 28, in <module>
    from . import cli
  File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 18, in <module>
    from .helpers import get_debug_flag
  File "/usr/local/lib/python3.8/site-packages/flask/helpers.py", line 16, in <module>
    from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.8/site-packages/werkzeug/urls.py)

Found a workaround solution for this issue - https://stackoverflow.com/questions/77213053/why-did-flask-start-failing-with-importerror-cannot-import-name-url-quote-fr
It is because Werkzeug 3.0.0 was released and Flask doesn't specify the dependency correctly (requirements says Werkzeug>=2.2.0)
Updates the requirements.txt in both ~/environment/workshopfiles/one-observability-demo/PetAdoptions/petfood and ~/environment/workshopfiles/one-observability-demo/PetAdoptions/petfood-metric, re-run then solve.
However, still need maintainer to fix the problem here.

Hello @Anorlondo448  @oceannic,
Thank you for your patience. I have recently on-boarded to the team and I'm following up with issues for this project.
CloudWatch Evidently was discontinued per: https://aws.amazon.com/blogs/mt/support-for-amazon-cloudwatch-evidently-ending-soon/
We have removed this module from the workshop so this should no longer be an issue.

Hello @Anorlondo448  @oceannic,
Thank you for your patience. I have recently on-boarded to the team and I'm following up with issues for this project.
CloudWatch Evidently was discontinued per: https://aws.amazon.com/blogs/mt/support-for-amazon-cloudwatch-evidently-ending-soon/
We have removed this module from the workshop so this should no longer be an issue.


Unable to Override Background Color via className Prop on Input Component

I am facing an issue where specifying a background color via the className prop on the Input component from @material-tailwind/react does not reflect the specified color.
Here's a snippet of how I am using the component:
<Input
  label="Search..."
  className={"bg-black"}
/>

Upon inspecting the DOM, I observed that the class bg-black is indeed being applied:
class="peer w-full h-full bg-transparent text-blue-gray-700 ... bg-black"

However, despite bg-black appearing after bg-transparent, the background color remains as specified by bg-transparent. I'd expect bg-black to override the background color as it's specified later in the class string.

Hey @NPJigaK, You can use the important! modifier on the className to override the existing class. For instance:
<Input
  label="Search..."
  className="!bg-black"
/>

In my case i want to apply the background only to the label but using the className inside labelProps overrides the borders too


Only strip off 1 folder from extracted SDK

Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>

@Mesbah-Alam for review

https://ci.eclipse.org/openj9/job/systemtest.getDependency/165/

I changed the job to be monthly. There is no need to run it daily.


運行webui時報錯 OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like meta-llama/Meta-Llama-3-8B-Instruct is not the path to a directory containing a file named config.json.

Reminder

[X] I have read the README and searched the existing issues.

System Info
使用官方提供colab產生報錯，之前沒看過這個錯誤
https://colab.research.google.com/drive/1eRTPn37ltBbYsISy9Aw2NuI2Aq5CQrD9?usp=sharing#scrollTo=YLsdS6V5yUMy
Reproduction
%cd /content/
%rm -rf LLaMA-Factory
!git clone https://github.com/hiyouga/LLaMA-Factory.git
%cd LLaMA-Factory
%ls
!pip install -e .[torch,bitsandbytes]
!pip install --upgrade huggingface_hub
!huggingface-cli login
%cd /content/LLaMA-Factory/
!GRADIO_SHARE=1 llamafactory-cli webui
Expected behavior
/content/LLaMA-Factory
2024-06-08 19:35:32.160912: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2024-06-08 19:35:32.213608: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-06-08 19:35:32.213658: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-06-08 19:35:32.215169: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-06-08 19:35:32.223133: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-06-08 19:35:33.353341: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Running on local URL:  http://<IP_ADDRESS>:7860/
Running on public URL: https://154122968acade1394.gradio.live/
This share link expires in 72 hours. For free permanent hosting and GPU upgrades, run gradio deploy from Terminal to deploy to Spaces (https://huggingface.co/spaces)
2024-06-08 19:36:09.790298: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-06-08 19:36:09.790349: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-06-08 19:36:09.791557: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-06-08 19:36:10.934261: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
06/08/2024 19:36:16 - INFO - llamafactory.hparams.parser - Process rank: 0, device: cuda:0, n_gpu: 1, distributed training: False, compute dtype: torch.float16
[INFO|tokenization_auto.py:666] 2024-06-08 19:36:16,826 >> Could not locate the tokenizer configuration file, will try to use the model config instead.
/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py:1132: FutureWarning: resume_download is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use force_download=True.
warnings.warn(
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_errors.py", line 304, in hf_raise_for_status
response.raise_for_status()
File "/usr/local/lib/python3.10/dist-packages/requests/models.py", line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 1722, in _get_metadata_or_catch_error
metadata = get_hf_file_metadata(url=url, proxies=proxies, timeout=etag_timeout, headers=headers)
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 1645, in get_hf_file_metadata
r = _request_wrapper(
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 372, in _request_wrapper
response = _request_wrapper(
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 396, in _request_wrapper
hf_raise_for_status(response)
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_errors.py", line 367, in hf_raise_for_status
raise HfHubHTTPError(message, response=response) from e
huggingface_hub.utils._errors.HfHubHTTPError:  (Request ID: Root=1-6664b2b0-76dfb7c841464f471ae513b2;976efd10-7b96-4419-bba4-98891e8fd91c)
403 Forbidden: Authorization error..
Cannot access content at: https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json.
If you are trying to create or update content,make sure you have a token with the write role.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/transformers/utils/hub.py", line 399, in cached_file
resolved_file = hf_hub_download(
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 1221, in hf_hub_download
return _hf_hub_download_to_cache_dir(
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 1325, in _hf_hub_download_to_cache_dir
_raise_on_head_call_error(head_call_error, force_download, local_files_only)
File "/usr/local/lib/python3.10/dist-packages/huggingface_hub/file_download.py", line 1826, in _raise_on_head_call_error
raise LocalEntryNotFoundError(
huggingface_hub.utils._errors.LocalEntryNotFoundError: An error happened while trying to locate the file on the Hub and we cannot find the requested files in the local cache. Please check your connection and try again or make sure your Internet connection is on.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/llamafactory-cli", line 8, in
sys.exit(main())
File "/content/LLaMA-Factory/src/llamafactory/cli.py", line 96, in main
run_exp()
File "/content/LLaMA-Factory/src/llamafactory/train/tuner.py", line 33, in run_exp
run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
File "/content/LLaMA-Factory/src/llamafactory/train/sft/workflow.py", line 31, in run_sft
tokenizer_module = load_tokenizer(model_args)
File "/content/LLaMA-Factory/src/llamafactory/model/loader.py", line 53, in load_tokenizer
tokenizer = AutoTokenizer.from_pretrained(
File "/usr/local/lib/python3.10/dist-packages/transformers/models/auto/tokenization_auto.py", line 837, in from_pretrained
config = AutoConfig.from_pretrained(
File "/usr/local/lib/python3.10/dist-packages/transformers/models/auto/configuration_auto.py", line 934, in from_pretrained
config_dict, unused_kwargs = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/transformers/configuration_utils.py", line 632, in get_config_dict
config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/transformers/configuration_utils.py", line 689, in _get_config_dict
resolved_config_file = cached_file(
File "/usr/local/lib/python3.10/dist-packages/transformers/utils/hub.py", line 442, in cached_file
raise EnvironmentError(
OSError: We couldn't connect to 'https://huggingface.co/' to load this file, couldn't find it in the cached files and it looks like meta-llama/Meta-Llama-3-8B-Instruct is not the path to a directory containing a file named config.json.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 2658, in block_thread
time.sleep(0.1)
KeyboardInterrupt
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/llamafactory-cli", line 8, in
sys.exit(main())
File "/content/LLaMA-Factory/src/llamafactory/cli.py", line 100, in main
run_web_ui()
File "/content/LLaMA-Factory/src/llamafactory/webui/interface.py", line 76, in run_web_ui
create_ui().queue().launch(share=gradio_share, server_name=server_name, inbrowser=True)
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 2563, in launch
self.block_thread()
File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 2660, in block_thread
print("Keyboard interruption in main thread... closing server.")
KeyboardInterrupt
Killing tunnel <IP_ADDRESS>:7860 <> https://154122968acade1394.gradio.live/
Others
No response

这应该不是框架问题，检查一下网络链接

i`m also with the same problem with Vertex-AI

i just solved... Change ur hugging_face acess token to 'read' if is  fine-grained

hugging_face access token has Repositories permissions, add read access for meta-llama/Meta-Llama-3-8B-Instruct


Long titles are hidden behind the buttons

Version

react-native-router-flux v3.35.0
react-native v0.28

Expected behaviour
Long titles are displayed with dots at the end

Actual behaviour
Long titles are hidden behind buttons

Steps to reproduce

Set long title for a scene

Thank you for reporting, are you up to do a pull request?

Actually, I've already done and waiting for being merged  ; )
https://github.com/aksonov/react-native-router-flux/pull/1088


refactor(app): update robot settings networking for ot-3

Overview
updates the robot settings network page for the ot-3. refactors the disconnect modal to match current style patterns and allow usage from device details overflow menu.
closes RCORE-221,  RCORE-222,  RCORE-223,  RCORE-224

disconnect modal states:

Test Plan

Manually verified disconnect modal success and failure states from robot settings networking and device details pages
Added unit tests for disconnect modal and "Disconnect from Wi-Fi" button and overflow menu option
Added unit tests for OT-3 copy changes

Changelog

Update robot settings networking for OT-3

Review requests
review disconnect modal approach and verify functionality
Risk assessment
low

@nusrat813 since im pretty sure 6.3 is going to be based off of edge would you mind making sure this change is okay before we merge? i think it would be tougher revert than just verify this specific change set is good to go now


Fix typo

Just that.
lintian told me to do it.

I think this was patched in #1153

@michael-grunder Just a couple of minutes!!


Compile under ubuntu

Although I installed zlib1g-dev I am getting now undefined reference to inflateInit_ ... etc
Any solution ?

Just check with Debian Jessie x64 with installed zlib1g-dev-1.2.8 and npk-tools compiled successfully.
You could try to check, which linking options is recommended (via pkg-config) and then correct Makefile:
pkg-config --libs libz

thank you. I just added -lz at the end and it compiled.
However when tried extracting I was always getting "Error: remain file chunk not enogh for partition"
Which versions does it support?

It supports old versions. I personally use it with ROSv5. With ROSv6 it works not so good.

Hm nice. Does these file contain executables etc? Are all these written in C?

What file do you mean? If you mean MikroTik packages (with *.npk extension), then the answer is yes. They are contain executables/libraries/drivers. RouterOS is just some kind of Linux distributive with a lot of proprietary code.

And yes this files are mostly binary and written in compilable languages (e.g. C, C++, etc.) So, even when you extract them, you can not easily audit them.

Compilation issue is solved, and after latest changes in source code the unpacking of newer versions of NPK files is supported too, so I close this issue. Feel free to open new issue if something going not as expected.


add wheel to PyPI for Python3

Can you please add a wheel to PyPI for Python3?  Currently I only see Python2 there and it is a pain because when using this with Azure Functions, it forces me to build from source which in turn requires Docker.   Anyways, it would be nice to have Python3 wheels available.   Thanks

@srinathnarayanan What's our story with Python 3?

any update?  still waiting for this as it is making working with Python Azure Functions more difficult as it requires docker to build.  Having the binary wheel available in PyPI would make that easier and faster.

Hi @bigdatamoore , I uploaded a python3 wheel for the latest version (3.0.2- https://pypi.org/project/azure-cosmos/#files ). Sorry for the delay!

Thanks so much.  You have no idea how much time this will save us in doing builds for Python azure functions.  I appreciate your quick response.


A question: Cover art for www.streamingsoundtracks.com

Hello!
Do you think you may like to create similar page to display art of streaming soundtrack at streamingsoundtracks.som? In the source code of main page, the ID code (asin) of current album is contained in link like "http://www.streamingsoundtracks.com/modules.php?name=Album&asin=B01EMCBULY" and then the image can be linked by the album ID as "http://www.streamingsoundtracks.com/images/cover/500/B01EMCBULY.jpg". The code changes every few minutes as soundtracks change.
I can display the cover art, but it is not that neat like your descent.
Thanks, Jan

Unfortunately I don't plan on supporting any other sources besides Last.fm, and possibly Spotify. It might not be too hard to fork this project and use streamingsoundtracks.com instead of Last.fm if you or someone else would like to develop it.


Cloning the project by default doesn't clone limine and will break when building

Maybe we need add back git submodule update --init some where

This should be fixed by running git submodule update --init to xtask build.rs. I don't know if this is the best place to put it. It seems that if I add it as part of xtask, it doesn't work the first time. Because this has nothing to do with building xtask, It prob doesn't belong in the build.rs. We should maybe find a better place for it.

I went ahead and fixed it. Problems like this could be solved if we had a CI/CD build.


How should we handle the difference in dependency name vs package name?

Currently, we show the package name.  Which is more meangful to the viewer?

Do you mean should we display the possible explicit_name_in_toml name?

Correct.  When listing dependencies, how should we handle that split.

As the tool is focused on showing packages and we just choose defaults from a workspace, I would say we should not be mucking with the dependency name.  I see this similarly out of scope as --manifest-path


Change current verification method to Twilio verify api

Fix #44
TWILIO_VERIFY_SERVICE_SID needs to be added to ENV vars.
createConnectionService needs to be reviewed because it uses old createUser service (strips phone numbers, checks for US validity, etc).
send code and validate code endpoints need to be called with installation id set on headers.

Ill add installationId to api requests that need it. Could you just add some documentation to this?

Parse add it automatically when request to the server. Is present on request object outside of the params


[hotfix] Handle unicode in encryption [OSF-7200]

Purpose
Names on Dropbox and Google drive break when we try to encrypt them.
Changes

Add helper function to ensure incoming strings to be encoded are in the proper utf-8 format
Add tests for helper function and encryption in general since it was untested.

Side effects
None known
Ticket
https://openscience.atlassian.net/browse/OSF-7200
[#OSF-7200]
QA Considerations

Test auth on at least 1 addon. I did dropbox locally and it worked. Per MattF if it works for one, there is no reason it shouldn't work for all of them. Worth testing at least one or two for a sanity check, but probably not worth checking all of them (especially if you can't easily change your name on the service).
Change your name on  to contain unicode madness and try to authorize the addon on the osf
Ensure it also works with non-unicode madness

@alexschiller If this is a hotfix, can you please resend this to master? Can you also verify that this was branched off of master?


What is an "immersive environment"

"immersive environment" could mean lots of things.
Can this be made clearer?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: bd4a6b76-b5ac-d343-f20b-1841380fbc99
Version Independent ID: 59b6019f-3cf0-6fb7-fc46-f714bb877a6c
Content: DisplayInformation.ResolutionScale Property (Windows.Graphics.Display) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Graphics.Display/DisplayInformation.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Thanks! I'm investigating.
-Steve

UPDATE: I'm changing the term to "app window".
'Immersive environment" is now out of date. It refers to Windows 8 where "immersive" apps ran in a different environment from the desktop, which had its own scale factor.
-Steve


Fix block proof generation with zero supply increase

@sebastiencs anything pending for this one?

@tizoc Yes, I will push more changes


Benchmark can not run

npm install eventemitter2 signals

module.js:340
    throw err;
          ^
Error: Cannot find module '../lib/core'
    at Function.Module._resolveFilename (module.

Thanks. It wasn't updated after latest refactoring.
Fixed and published as v0.3.3


CenterMode issue when upgrading from v0.15.4

Hi,
I still don't know if this is a bug from react-slick or not.
Currently Im trying to upgrade my react-slick version from 0.15.4 to 0.23.1.
I have make sure that I use react v16.0.0 and react-dom v16.0.0 like the one used in codesandbox.
I realised some of my slider are broken while some aren't, after further investigation, it happens because of responsive prop, to be precise it is centerMode prop, so if I remove centerMode from the responsive prop, it works fine.
Another issue is about custom arrows, it doesn't appear so we can have dots but not the arrows.
Does anyone ever experience something like this before?
Sorry I can't give the example on pen because it works fine if we only have react, react-dom, and react-slick. I just want to know if someone has ever experienced something like this, how do they solve it.
Thank you

Would you mind creating a codesandbox demo for the same issue?

Thanks for your response @laveesingh.
After further investigation, the bug appeared not from react-slick.
Sorry for this misleading issue.


Remove bunny dns or ...

The repository is called 'free-for-life,' but Bunny DNS only provides 20 million free queries. Therefore, if a website gets a lot of visitors, those free queries may run out before the owner dies.

It is still a free plan.


[good-first-issue] Respond to commands only when mentioned

Summary
Right now the bot responds to any command followed by /. This may create conflicts if there are multiple bots in the group and a
given command is not meant for this bot.
So the bot should respond only when it is addressed. E.g: /command@bot_name
Implementation
A possible way to implement this is using regular expressions. We can add regex filters in CommandHandlers.
https://github.com/JIITODC/bot/blob/22302be3e738a49ec22da6be882a50f16376a292/bot.py#L54
Here is a brief documentation on the regex filter that the python-telegram-bot api wrapper provides:
https://python-telegram-bot.readthedocs.io/en/stable/telegram.ext.filters.html#telegram.ext.filters.Filters.regex
Lastly, a little guide on regular expressions:
https://medium.com/factory-mind/regex-tutorial-a-simple-cheatsheet-by-examples-649dc1c3f285
Alternatives
Do suggest in the comments if you have some other approach in mind. :smiley:
If this is your first time contributing
Hey! :wave: If you're interested to work on this issue, do comment, "I would like to work on this issue. Please assign this to me.", below to let others know that you're interested in working on this. Also, do take a look at the contributing guide which will take you step by step from forking this repo to creating a pull request :rocket: :fire:.
We use the python-telegram-bot api wrapper. Here is a link to its documentation: https://python-telegram-bot.readthedocs.io/en/stable/index.html
Feel free to ask anything related to this issue :hugs:

Hey @DelusionalOptimist, Can I take up this issue?

Go ahead, @Abjcodes! 👍🏻

@DelusionalOptimist @rexagod Please review the PR and notify me if there are any changes to be made.


LaTeX: add xelatexWithHeaders

Changes:

Introduce someTexWithHeaders
latexWithHeaders as a special case of someTexWithHeaders
Introduce xelatexWithHeaders, as a special case of someTexWithHeaders

Remove use of package CTeX

Introduce ctexWithHeaders, as a special case of someTexWithHeaders
latex as a special case of latexWithHeaders
xelatex as a special case of xelatexWithHeaders

Remove use of package CTeX

Introduce ctex, as a special case of ctexWithHeaders
Export xelatexWithHeaders, ctex, ctexWithHeaders in module Reanimate.LaTeX
Export ctex in module Reanimate
Change xelatex to ctex in doc_xelatex.hs

Breaking Changes:

xelatex does not automatically use package CTeX now
ctex has the old behavior of xelatex (with package CTeX)

Yeah, it sounds sensible to have a version of 'xelatex' without 'ctex'.

I would propose to rename the current xelatex function to ctex, and make xelatex without \usepackage{ctex}, but I guess this will (silently) break some existing code.

Breaking changes are fine.

Could you rename doc_xelatex.hs to doc_ctex.hs. And could you add a new example for xelatex. The example could use unicode symbols instead of chinese symbols.

I tried this for a xelatex example:
main :: IO ()
main = reanimate $ docEnv $ animate $ const $
  withStrokeWidth 0 . withFillOpacity 1 . scale 4 . center $
  xelatex "αβγδε"

It seems that I don't have a proper font, it produces a GIF like this:

Hm, I can't come up with an example where xelatex differs from plain latex. Let's delete the doc_xelatex.hs example.


Empty sidebar. Files are not listed.

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T17:15:57.756Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

crane
Hvy
0.3.8

blockalign
San
0.6.0

php-formatter
Sop
0.2.4

php-debug
fel
1.11.1

php-intellisense
fel
1.5.1

phpcs
ika
0.7.0

sublime-keybindings
ms-
3.0.2

php-docblocker
nei
1.3.0

laravel-blade
one
1.10.0

Steps to Reproduce:

File open folder -> chose my project folder
I got empty sidebar with no files listed. Even ctrl + R/Recent project folder too didn't work.

Reproduces without extensions: Yes/No

Does this happen with every folder or just a particular one?

It happens with every folder. Trying to open projects with File->Open Recents or Ctrl+R also dint work out.

@Sarav-S can you make sure to update to our lated 1.17 release.

I think I have the latest version @bpasero

@Sarav-S can you share a screenshot how your files explorer in the sidebar looks like?

After adding folder through File->Open or File->Open Recents or Ctrl+R, I get only welcome screen.

You can see my project title VSCode header. Actually the files are available when I do Cmd+P to open them. But it isn't available only on sidebar

@sandy081 didn't we push a change so that the files explorer is never hidden?
@Sarav-S if you right click on the title of the explorer you should be able to bring back the files explorer properly.

@bpasero I think explorer is open only except files are not listed. Please check screenshot.

@bpasero I have this same issue, except for Mac OS Sierra https://screencast-o-matic.com/watch/cbnt3w634b

@Sarav-S do you see this context menu:

You mean this one?

Looks like we broke this in 1.17 while refactoring split view and views viewlet. And it is pretty bad.
Till 1.15 we were supporting toggling files explorer visibility. In 1.16 we took off that support #32962 here also making sure previous state is not considered. After refactoring we are no longer overriding the previous state.
I think this should be a candidate for 1.18 release.

Steps to reproduce:

Download 1.15 version of VS Code
Open VS Code on a folder
Hide the file explorer view
Update to latest

Expected: File explorer is not shown and cannot be retrieved
Analysis:
Looks like we broke this in 1.17 while refactoring split view and views viewlet.
Till 1.15 we were supporting toggling files explorer visibility. In 1.16 we took off that support #32962 here also making sure previous state is not considered. After refactoring we are no longer overriding the previous state.
Impact: Low
Users who had file explorer hidden in 1.15 release might not see file explorer and also cannot retrieve it after upgrading to latest version. Workaround is to clear cache or upgrade to insiders. Also, I only see 2 users filed this issue till now.

@sandy081 Thanks! It worked :)

Reopening it for discussion for including it in October release or not.

It is quite bad, and the fix looks simple, I think we should get it in for October.


fix(telescope): Correct index for finder

Use Config.options.commands.history instead of Config.options.history
Its a new regression that caused errors when using Noice telescope

Damn, my bad. Thanks!


[8pt] Bug with fim_post_processing fatal error(s)

Reproduced error in src_adjust_usgs_rating_trace.py and ultimately src_roughness_optimzation.py

After addressing the errors in src_adjust_usgs_rating_trace.py and src_roughness_optimzation.py, a new error came up when running fim_pipeline.sh. This new error appears in the src_adjust_spatial_obs.py.


Issue: hydrogen:clear-results does not clear dock

Issue: hydrogen:clear-results does not clear dock
Is there a way to clear the dock via keyboard shortcut? hydrogen:clear-results only clears outputs in code, if any, but does not clear the dock if dock is used for results. Thanks in advance for you help.
Windows 10 Home Premium 64bit
Atom 64bit v 1.21.1
Hydrogen 2.0.1

Can store.kernel.outputStore.clear() be mapped to a keyboard shortcut? If so, that would solve this PR-free.

Can store.kernel.outputStore.clear() be mapped to a keyboard shortcut?

Not exactly. You would need a custom command in your init script and even then it would be a bit of a hack and could break if we changed something in the future.
I think it's a good point that clearing results should include the output area (I would like it to as a user as well). This change is also the simplest solution to get the custom keyboard shortcut to work so its win-win.

@lgeiger I am tagging this as "good first issue", let me know if I am wrong about in case i've forgotten something that will come up :thinking:.

Ben, once Dock Clear is successfully implemented, what should my configs look like in order to combine clear dock and execute cell in hydrogen in a single shortcut? See my starting point below - thx in advance.
init.coffee
atom.commands.add 'atom-text-editor', 'hydrogen:clear-results-run-cell', ->
???
keymap.cson
'.platform-win32 atom-text-editor:not([mini]), .platform-linux atom-text-editor:not([mini])':
'ctrl-alt-enter': 'hydrogen:clear-results-run-cell'

I'm on mobile at the moment so I'll post a link with an example that is almost the same
See also : https://atom.io/docs/api/v1.21.1/CommandRegistry#instance-dispatch
Let me know how that goes!

Thanks Ben - I'll check it out.
Any ETA for this issue?

@dsanalytics I sent a PR for this just now. If interested, check our CONTRIBUTING.md to see how to set up a dev version of hydrogen and try it out. I've found hacking on atom to be a really fun way to learn to code.

Thank you gentlemen! Atom seems to be fast becoming my primary platform for DS!

How long does it usually take to get package update in Atom through Install in Settings? No huge rush - just asking to learn about the process.

Good question. Anytime features/fixes are added to the development branch they need to be "shipped" to become available as a release on apm
We will ship soon I'm sure, but I really think you should get a development branch working since you seem to have the interest 😀
More on apm release specifics here

Uhm is this still not implemented?


Add new option in scss/dollar-variable-empty-line-before

Hi,
Add option for a have space between dollar variables if this varaibles are map or list but filled.
Ex:
$var;
$var2: "";
$var3: ();

$var4: (
  "foo"
);

$var5: (
  "foo": "bar"
);

@kristerkari 😊


Android build fails when adding Ionic Native plugin BackgroundGeolocation to project

Short description of the problem:
When I generate a new starter project:
ionic start test-project --v2
and add the BackgroundGeolocation plugin from Ionic Native:
ionic plugin add cordova-plugin-mauron85-background-geolocation
the android build:
ionic build android
fails with this error:
:processDebugResources
/home/pavlina/Projects/ionic-2.rc-1/platforms/android/res/xml/authenticator.xml:5:19-33: AAPT: No resource found that matches the given name (at 'icon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/res/xml/authenticator.xml:6:24-38: AAPT: No resource found that matches the given name (at 'smallIcon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/build/intermediates/res/merged/debug/xml/authenticator.xml:2: error: Error: No resource found that matches the given name (at 'icon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/build/intermediates/res/merged/debug/xml/authenticator.xml:2: error: Error: No resource found that matches the given name (at 'smallIcon' with value '@drawable/icon').

FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':processDebugResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 9.847 secs

Error: /home/pavlina/Projects/ionic-2.rc-1/platforms/android/gradlew: Command failed with exit code 1 Error output:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/home/pavlina/Projects/ionic-2.rc-1/platforms/android/res/xml/authenticator.xml:5:19-33: AAPT: No resource found that matches the given name (at 'icon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/res/xml/authenticator.xml:6:24-38: AAPT: No resource found that matches the given name (at 'smallIcon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/build/intermediates/res/merged/debug/xml/authenticator.xml:2: error: Error: No resource found that matches the given name (at 'icon' with value '@drawable/icon').

/home/pavlina/Projects/ionic-2.rc-1/platforms/android/build/intermediates/res/merged/debug/xml/authenticator.xml:2: error: Error: No resource found that matches the given name (at 'smallIcon' with value '@drawable/icon').

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':processDebugResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Which @ionic/app-scripts version are you using?
0.0.36
I need this Cordova plugin in my app and this completely stops me to build for Android and test on device. Please let me know what the problem is and how to fix.
Thanks!

Hello, thanks for using Ionic! This is actually an issue with the plugin and not with app-scripts. It looks as if the plugin is expecting you to add some icons. Because this is not an app-scripts issue I am going to close this one for now.

H

This issue was moved to driftyco/ionic-native#752

@jgw96 but this plugin is part of Ionic Native and I was expecting at least all plugins in this package to be supported in Ionic. Where should I move the issue then?

Hello! I have just moved this issue to the ionic native repo. You can see the new issue in the comment above (:

OK, thanks!

@jgw96 with help from plugin author here I found out that adding a file icon.png in /path/to/project/platforms/android/res/drawable/icon.png solves the build issue.
I wounder would it be possible this icon.png to be generated in the res/drawable directory of the project, like the other icons and then automatically copied to platforms/android/res/drawable/icon.png, so the plugin can work with Ionic out of the box?

Just for reference, in case someone else has the same issue. It seems to be issue of the background geolocation plugin with Cordova 6.4.0. Should be fixed in https://github.com/mauron85/cordova-plugin-background-geolocation/issues/195


"Your sales" vs "Apple's sales"

When you join the Apple Developer program and sign the contracts, you give Apple all the rights to sell your apps. So, technically, you are not selling any apps anywhere and there are no sells to be declared anywhere.

The fact that Apple acts as a commission agent for you does not exempt you from proper invoicing. In addition, this script can be used to create recapitulative statements, which are also necessary for correct tax treatment in the EU – see README.


testperf always failed

Prerequisite:
OS: Ubuntu 16.04, RAM available11G , Intel(R) Xeon(R) CPU
CUDA: 8.0
gcc: 5.4.0-6ubuntu1~16.04.5
h2o4: 0.0.4, download h2o4gpu whl file from anaconda cloud
https://anaconda.org/gpuopenanalytics/h2o4gpu
Python: 3.6, use Anaconda3
How
I cloned h2o4gpu project, and then I run relevant make subcommand when my env is ready to complete.
When I run make testperf, the build subcommand runs ok, but run dotestperf subcommand will fail.  Relevant error info:
ln -sf "/root/h2o4gpu/src/interface_py"/build/lib/ch2o4gpu_cpu.so .
ln -sf "/root/h2o4gpu/src/interface_py"/build/lib/ch2o4gpu_gpu.so .
make[1]: Leaving directory '/root/h2o4gpu/src/interface_py'
mkdir -p ./tmp/
H2OGLM_PERFORMANCE=1 pytest -s --verbose --durations=10 -n 1 --fulltrace --full-trace --junit-xml=build/test-reports/h2o4gpu-test.xml tests_open 2> ./tmp/h2o4gpu-test.9174_2017.10.25-15:48:14.log
Makefile:364: recipe for target 'dotestperf' failed
make: *** [dotestperf] Error 2

When I check error log, I find pytest run error:
root@sd002024:~/h2o4gpu# cat ./tmp/h2o4gpu-test.9174_2017.10.25-15\:48\:14.log
usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: -n tests_open
  inifile: None
  rootdir: /root/h2o4gpu

So, I check again my pytest version and pytest --help output info, not get any valid info about parameter.
root@sd002024:~/h2o4gpu# pip freeze | grep pytest
pytest==3.2.3

The solution is:
delete -n parameter in Makefile and try again, but I got another error ... ...
ImportError: cannot import name 'TruncatedSVDH2O
__________________________________________________________________________________________________ ERROR collecting tests_open/test_tsvd.py __________________________________________________________________________________________________
ImportError while importing test module '/root/h2o4gpu/tests_open/test_tsvd.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests_open/test_tsvd.py:6: in <module>
    from h2o4gpu.solvers import TruncatedSVDH2O
E   ImportError: cannot import name 'TruncatedSVDH2O'

So, based on above error, I check again:
(test) root@sd002024 test# python
Python 3.6.3 |Anaconda, Inc.| (default, Oct 13 2017, 12:02:49)
[GCC 7.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import h2o4gpu
>>> from h2o4gpu.solvers import TruncatedSVDH2O
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'TruncatedSVDH2O'
>>> dir(h2o4gpu.solvers)
['ElasticNet', 'ElasticNetH2O', 'KMeans', 'Lasso', 'LinearRegression', 'LogisticRegression', 'Pogs', 'Ridge', '__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__', 'elastic_net', 'kmeans', 'lasso', 'linear_regression', 'logistic', 'pogs', 'ridge', 'utils']
>>>

So, h2o4gpu don't have TruncatedSVDH2O class, any ideas or bug ?

@memory-yancy the version on anaconda cloud is a bit dated - we added TruncatedSVD just recently. You'll have to either remove the current Python package manually and build the whole project yourself (make fullinstall) or download one of our bleeding-edge wheels (links in the main readme).

@memory-yancy as for pytest: error: unrecognized arguments: -n tests_open - this occurs when you don't have pytest-xdist installed. We have it in our requirements-buildonly.txt, which is not bundled with the wheel.
In general, if you want to run our tests its a good idea to build the project yourself, then you don't have to worry about missing dependencies etc.

@mdymczyk It's a good point thought that a user should be able to install a wheel and with the build still test.  But in any case, we already have github issue where all tests will be implanted directly into the code instead of separate, like sklearn, so can test anything from the wheel alone.


Move HandlePositionProvider to common

Proposed Changes

Move HandlePositionProvider to common
Reuse Alignment instead of custom enum

Testing
Test: Test edit selection handles should not change.

Ok, let's do it in AOSP first


Move auto_contiguous before lowering

This should fix the perf isssues.

Perf report looks pretty bad.  Is there something else needed?

Perf regression should be fixed by #3494.

Perf regression should be fixed by #3494.

Do we close this out then or get 3494 in before this?


[Subtask] Report HTTP port of Shuffle Server to the coordinator

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the subtask
Report HTTP port of Shuffle Server to the coordinator
Parent issue
#1941
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

This feature has already been done


auto close of the airsim API

Hello
I am new to this kind of things, but I have configure it for almost a week. There is still some problem.
when I load the airsim environment, it is working fine, but when I start running the "python3 daniel.py --level_name 'Final_Tier_1' ", The API auto shutdown and loading some error.  I tried to debug, I think the problem is with the load_level function, it seems reset everything, because when I comment this line, it is not auto shutdown, but the problem is with the ground truth gate. The problem of the API auto shutdown is shown image below. Is it the problem with the environment that I install or [..?]

thanks for you interest in the repo.
I have personally never seen the error message before and I'm not sure this is from the agent that I created. Note that the competition has been some years ago, and highly likely the airsim API has changed and linkages were broken.
Maybe you can take a look at the default drone and try to control that instead: https://microsoft.github.io/AirSim/apis/
I don't intend to keep this repo maintained so you will need to look into what's reasonable.

I got it. Thank you for the information anyway. I will look into this more.


Help ?

public class PipedInputTests
{
[Test]
public void Add_Given2Numbers_Should_OutputSum()
{
var result = new AppRunner().RunInMem("Add 40 20");
result.ExitCode.Should().Be(0);
result.Console.Out.Should().Be(@"60");
}
}
I wanted this from docs to run.
Cant find this methods Should
Is docs outdated ?
Didnt see this method in repo.

Ups, found Shoud in repo.
But still, are docs outdated ?

Ok cloned repo, found i need nuget FluentAssertions
Shame docs dont mentions it
Old chunck of coal like me didnt know..

Hi @krzm is this the kind of indicator that would have helped?

@krzm, other than the Should red-herring, how's your experience of the framework.  I see you've built a few console apps and possibly a similar console framework.  I'd be interested to hear your impressions..

Hi @drewburlingame, yes it would help.
Problem is, test failed for unknow to me as yet reason.
I begun to like Console recently.
I did some simple lib solutions of my own, witch are tailored to my simple needs.
I seen this vid: https://youtu.be/dKBuvdGsYYc
I thouth maby i dont need my own libs.
I started to look at CommandDotNet.
I think it's impresive.
Started in doc section getting started.
Hope to see how i can use it by doing some examples, from docs or repo.

We've had a lot of improvements since that video.  Feel free to reach out to us in a discussion on this repo or via discord with any questions.

And let us know if you have suggestions to improve the docs.


Migrating to react: Rendering of BlazeComponents via React is NOT possible

Hi guys,
I made the decision to migrate my project to React - at least to build new features in React from now in.
Meteor Guide mentions https://github.com/gadicc/meteor-blaze-react-component as the way to render Blaze-Templates from a react-component.
BUT when installing meteor-blaze-react-component my app crashes with weird errors like
Uncaught TypeError: Super expression must either be null or a function, not undefined .
In the docs I read that meteor-blaze-react-component requires templating-package installed, which I think BlazeComponents overwrites or replaces.
Ok, so is there any quick way to do what meteor-blaze-react-component does with BlazeComponents?

Not sure. I have not used that package.

It was due to a name conflict on the BlazeComponent class.  @duce3 just submitted a PR to fix this, which I've merged and released in v1.4.2.  For more details see https://github.com/gadicc/meteor-blaze-react-component/pull/19.
This issue can be closed.


Prettify Readme

This includes broken headers, the broken screenshots, code samples, ...

That's absolutely brilliant. Have been wanting to sort this out for ages. Cheers.


PreparedStatement setTimestamp() binding broken for TIMESTAMP column in WHERE clause

I have a simple SQLite database with a simple table:
CREATE TABLE IF NOT EXISTS test_timestamp (
        id INTEGER PRIMARY KEY,
        description TEXT,
        created_on TIMESTAMP NOT NULL DEFAULT (STRFTIME('%Y-%m-%d %H:%M:%f', 'NOW'))
)

I populate the table with a single column:
INSERT INTO test_timestamp (description) VALUES ('test');

If I query this table using the query below with a setTimestamp() binding, then the WHERE clause matches ZERO rows regardless of how many that match.
      final Calendar UTC_CALENDAR = Calendar.getInstance(TimeZone.getTimeZone("UTC"));
      PreparedStatement ps = conn.prepareStatement(
          "SELECT id, description, created_on FROM test_timestamp WHERE created_on < ?");
      Timestamp timestamp = new Timestamp(System.currentTimeMillis() + 100000L);
      ps.setTimestamp(1, timestamp, UTC_CALENDAR);
      ResultSet rs = ps.executeQuery();  // NO ROWS MATCH QUERY

However, if I change the query and use setString() binding instead, then the WHERE clause DOES MATCH the appropriate rows:
      final String DATE_TIME_PATTERN = "yyyy-MM-dd HH:mm:ss.SSS";
      final ZoneId UTC_ZONE = ZoneId.of("UTC");
      final DateTimeFormatter DATE_TIME_FORMATTER = DateTimeFormatter.ofPattern(DATE_TIME_PATTERN);

      PreparedStatement ps = conn.prepareStatement(
        "SELECT id, description, created_on FROM test_timestamp "
        + "WHERE created_on < (STRFTIME('%Y-%m-%d %H:%M:%f', ?))");

      Instant instant  = Instant.ofEpochMilli(timestamp.getTime());  // use the exact same time as above

      ZonedDateTime  zonedDateTime   = instant.atZone(UTC_ZONE);

      ps.setString(1, DATE_TIME_FORMATTER.format(zonedDateTime));
      ResultSet rs = ps.executeQuery();  // ALL EXISTING ROWS MATCH

This seems like a bug to me.  I have tried setTimestamp() with and without the Calendar parameter and either way it fails.
I am attaching the code to reproduce the issue.
sqlite-test.zip

You are telling SQLite to compare a TEXT date-time to an INTEGER value when you use setTimestamp, so it converts milliseconds to a string and compares that to your formatted date-time string. That's causing the behavior you see. If you force the driver to use TEXT, like you want, then it works fine. Configure the date_class property like this:
Properties props = new Properties();
props.setProperty("date_class", "text");
conn = DriverManager.getConnection(jdbcUrl, props);

Then your test program works as you expect.

Seems like this has been answered, closing.


No license?

A Stallman bot without a license just doesn't seem right.

I'm sorry, here it is :) https://github.com/marekjedrzejewski/stallmanbot/commit/86cb91a1a6ad70aea9fc6db8e63e1a282e28c8bf


test: Add WebKit to interop tester

Nice @MarcoPolo I can see that you are currently blocked by the addition of the webkit tests to webRTC which is causing the same error I am debugging it myself.

Great! Please ping me when you figure it out. Or let me know if you want to pair debug this. I'll pause this work until that's done.

This is currently blocked by the lack of support for the RTCPeerConnection API on WebkitGTK as explained in this comment

closing in favor of https://github.com/libp2p/js-libp2p/issues/1808


EntryElement should be Entry Element (with space)

For consistency with Abstract Element, Based on and other two-word keywords.

 EntryElement should be 'Entry Element'

Overcome by events in grammar 6.0. Will not fix in 5.x


Create good instructions for setting up a development environment

We need good, easy to follow instructions for setting up a developer environment for the Keptn Lifecycle Toolkit.  This should be centered in the CONTRIBUTING.md file for the repository although that can link to other documents if appropriate.
Source material to get you started:

Follow the Keptn setup for Go/Docket/K8s etc

https://github.com/keptn/keptn/tree/master/docs/developer

https://github.com/keptn/lifecycle-toolkit#install-a-dev-build
https://github.com/keptn/lifecycle-toolkit/blob/main/CONTRIBUTING.md#contributing
https://github.com/keptn/lifecycle-toolkit/blob/main/operator/README.md

is this issue is same as #212 ?

Hi, I am interested in this issue. Also if anyone else wants to work/working already I can happy to collaborate.

Good catch, @Amishakumari544 !  I missed it because the other one talks about a "Contributor's Guide", although, when I read the text of that one, it was actually talking about setting up the development environment, too.  Whatever, we need all of this stuff!

interested


test: make project ID visible

The project-id was treated as a secret but it is not a secret.
After this change it will be possible to copy and paste scw k8s cluster creation command.

There are still other places in the code where we use ${{ secrets.SCW_DEFAULT_PROJECT_ID }} Should theses also be changed to the hardcoded version? For example in the run command of create private network.

You are right, will fix it soon.

not applicable anymore


Add option to use old blog styling

The diff will be a lot less horrendous once the refactor-comment-api branch merges. I wanted to get this out to discuss the license implications though.
The SSC blog styling is licensed under GPL3, which is incompatible with MIT. However, since this copies the look only, and not the code, I think the terms may not necessarily apply. It may still be good practice to add acknowledgements.
~The background image is loaded from where it's hosted on SSC, so it's not distributed as part of the extension, but I'm not sure if that's a valid workaround.~
The background is now an original creation to avoid the whole question.

Thanks for bringing this to my attention. I think there are several ways to handle the licensing issue.
First, I would much prefer to keep the styles that you copied from elsewhere in a separate file so that we can add a comment where we got it from. This makes it much easier to track code we don't “own” and to pull it out if someone complains (which I don't think is too likely). It should not be too hard to refactor styles.js to allow including styles from either a string literal or a file (I'd be fine with having every style in a separate file, too).
There are some independent advantages to putting styles into files: it's much easier to edit them in an IDE when they are in a separate CSS file, so the editor understands the file syntax. The main downside is that we create a lot of small files, but I'm not sure that's all that concerning since the total number of files is likely to be small (currently, there are 3 styles, I'm not sure that there will ever be more than 10).
Second, we could relicense the project as GPLv3 if that resolves the issue — I don't care that much about the license so long as it's somewhat permissive. And if you agree with this, we could easily do this, since you and I are the only two contributors so far. Otherwise, I would suggest committing the file and waiting until someone complains; I think the copyright status of CSS files is a little bit of a grey area, and I doubt anyone cares enough to make a big fuzz about this. I think so long as we have a way to remove the file if someone complains, we should be fine.

I think you're right about separating out the option css into files. It may actually be a good time to organize the others too, instead of having everything in the main folder. I'll probably to that in a separate branch though.
For the old style css, I think separating out the file is sufficient for now. Fwiw, no one's complained about it in acx tweaks.

Sorry, been a bit busy lately, I'll finish this up soon. I think you can squash the commits into one if that's an issue.

Take your time, I'll just keep this open for a while.
(At some point, I may want to create a release with some of the new features. Let me know if you have an opinion on which features should be included.)


Fixes https://github.com/apache/superset/issues/19264
BEFORE/AFTER SCREENSHOTS
https://user-images.githubusercontent.com/70410625/159783385-494dc7e1-603e-469a-bf5d-b97bcf8b00cb.mov
https://user-images.githubusercontent.com/70410625/159784037-39dad8e9-1ef8-422f-8bbd-91b413155711.mov
TESTING INSTRUCTIONS
Check the video for instructions.
ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Tests well! Merging!

🏷  preset:2022.11

This appears to have caused a regression: #19592


[Question ]Noise level

Dear all,
I'm a newbie to Malmo. I'm looking information about how agent deal with noise level ? At the moment, I've created:

an agent ( agent_host = MalmoPython.AgentHost())
loading xml mission file and starting mission (agent_host.startMission(...))
Define list of command ( cmd = ["move 1", "turn 1"]
send random command to agent to execute. (agent_host.sendCommand)

If I increase noise level, how it will affect agent to choose a command ?
I try to look for noise level information but I don't see any thing.
Many Thanks,

Can you explain a little more what you are trying to do? What do you mean by noise level in this context?
Cheers,
Dave.

Dear Davey,
This is my requirement:
You should provide a solution for an agent without sensory input which takes random
actions.
2.2 Requirements
Sensors: None
Actions: Discrete and noise free. An action takes at least 200 ms to carry out
My solution is:

Create an agent ( import MalmoPython; agent_host = MalmoPython.Agent_Host())
Loading xml file mission and start mission (agent_host.startMission(my_mission, my_mission_record ))
Declare discrete actions (discrete_action_list =["turn 1", "move 1","movenorth 1"....)
Taking a random action (agent_host.sendCommand(discrete_action_list[random_index])

I'm not sure about noise level in the requirement. Is it a agent configuration attribute ? I try to figure out but still have no idea about it.
Thanks a lot.
Quy

We haven't implemented an agent noise level attribute in Malmo - the agent will always try to act on the command you send it. There is a degree of indeterminacy however, due to the nature of the Minecraft environment. For instance, sending a "move 1" command may or may not result in the agent moving, depending on whether the agent is able to move - there might be a wall blocking the agent, say, or flowing water pushing the agent back. You can mitigate against this (put the agent in a flat arena, don't add any water etc), in which case the only noise would be caused by temporal factors - the asynchronous communication, Minecraft's clock speed, etc. The precise length of time for an action/observation cycle will vary, depending on how long the TCP action message takes to travel, how long the agent takes to process the action, how quickly the action is reflected in the Minecraft world (which can depend on both the Minecraft client and server processes and the communication between them), and how quickly the observation TCP message is returned. But under typical operating conditions, 200ms should easily cover all of that, so if you are allowing 200ms after each sendCommand call, you can effectively describe the system as "noise free". So if that's what you are after, no special work is required.
If you want to add noise, you can program it directly on your side - for example, I seem to recall that the Arcade Learning Environment allows you to specify the probability that sending a new action actually repeats the previous action instead.
Does this answer your question?

It's been a while, so I'm closing this - but please reopen if you still have questions about this.


The logic for AllNotIn and AnyNotIn are the wrong way around

Conditions for collections. Take for example, AllNotIn, the documentation says:

none of the members of attribute value collection are members of "values"

Yet the test is:
https://github.com/ketgo/py-abac/blob/master/tests/test_policy/test_conditions/test_collection.py#L80
    @pytest.mark.parametrize("condition, what, result", [
        ...
        (AllNotIn([2]), [1, 2], True),

Of the 2 values for the attribute value collection (1 and 2), 2 is a member of "values", so the condition should return False.

Hi @SpoonMeise , thanks for pointing this out! The docs needs to be corrected as the implementation is correct. The AllNotIn is suppose to check if all the members in the list are not present in the attribution value. It's basically a NOT of the AllIn condition. The naming is confusing. Maybe I should use Not first in all of such conduction names?

Just had a look, the implementation of AllNotIn and AnyNotIn is correct. The description in the docs is misleading. The AllNotIn condition checks if all the values in a access request attribute is not in the "values" field of the condition. In the test since the condition "values" is just [2] while the access request attribute is [1, 2], since all the values of the request attribute is not in condition "values" so the result should be True. This is what the test is validating.
I believe your use-case can be supported by using the AnyIn and AnyNotIn conditions. The idea here is we are checking if the user has a one or more roles which the policy allows. The AllIn and AllNotIn conditions are useful if you want to make sure all the roles specified in the policy are assigned to the user.
Regarding renaming the conditions, I think its a good idea if it makes the policy easier to read and would be more than happy to include it as a feature. I might not be able to get on it for while. Would you like to open a PR and give it a try? I think one approach of achieving this is by driving a new named class from AnyIn, AllIn, etc and adding it to the factory in https://github.com/ketgo/py-abac/blob/master/py_abac/policy/conditions/schema.py.

Yes, the documentation is wrong and needs to be corrected. The basic idea around these conditions is checking for subsets, i.e. one is subset of another. When writing the documentation I thought that would not be user friendly so decided of not using such. Maybe describing in terms of sets would be more clear? Any suggestions? :)


odata.nextLink not working

I had to change line 63 path =<EMAIL_ADDRESS>|| null; to path = body['odata.nextLink'] || null; or path would always be null.  I'm using graph.windows.net so maybe that makes a difference.  Great library!  Thanks!

I change line 63 to path =<EMAIL_ADDRESS>|| body['odata.nextLink'] || null; so that should cover both cases.


fix(diagnostic_graph_aggregator): fix a bug where unit links were incorrectly updated

Description
Close #6928
Fixed a bug where unit links were incorrectly updated. https://github.com/autowarefoundation/autoware.universe/issues/6928
Tests performed

Not applicable (the iterator is invalidated by assignment, but it works in my environment, so I didn't add any code to detect it.).
Effects on system behavior

Not applicable.
Interface changes

None
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

LGTM :+1: