Support for Delta 2

Hi,
are there any plans/timeline to support Ecoflow Delta 2?
Is there anything I can help with (I have one).
Thank you :)

I also have a Delta 2 with additional battery device and need to use this cool integration.
@vwt12eh8 Let me know, if I can help

+1 for this !
Tell me if I can help, my delta 2 is on his way.

+1 here as well... Just got a Delta 2 and would also be willing to help/test/etc.

+1 again.
Waiting for the next realease contains DELTA 2 maybe ...

+1

+1 from me

Instead of spamming with +1 could one who already has the Delta 2 on hand test if 8055/tcp is only open in IOT mode or also when the device is connected to an access point? Please state your firmware version and whether it is the latest fw. I would be interested if the "local API" has also been "locked down" on the Delta 2, same as with the other Deltas. #60

Instead of spamming with +1 could one who already has the Delta 2 on hand test if 8055/tcp is only open in IOT mode or also when the device is connected to an access point? Please state your firmware version and whether it is the latest fw. I would be interested if the local API has also been "locked down" on the Delta 2, same as with the other Deltas. #60

Delta 2 IOT is always on, no button, and all TCP ports are closed

Instead of spamming with +1 could one who already has the Delta 2 on hand test if 8055/tcp is only open in IOT mode or also when the device is connected to an access point? Please state your firmware version and whether it is the latest fw. I would be interested if the local API has also been "locked down" on the Delta 2, same as with the other Deltas. #60

If you think there is a way to bypass the restrictions of the latest Delta 2 update, I can try to get one to work on.

Instead of spamming with +1 could one who already has the Delta 2 on hand test if 8055/tcp is only open in IOT mode or also when the device is connected to an access point? Please state your firmware version and whether it is the latest fw. I would be interested if the local API has also been "locked down" on the Delta 2, same as with the other Deltas. #60

Delta 2 IOT is always on, no button, and all TCP ports are closed

Confirmed. With Delta Pro I can telnet to 8055 and get a stream of data. With Delta 2, I cannot.

Sadly I let their support know that I'll return my new Delta Pro as they have chosen to close the comms port. For me it is vital to get/send data from the unit. Without it any integration is kind of crude.

Sadly I let their support know that I'll return my new Delta Pro as they have chosen to close the comms port. For me it is vital to get/send data from the unit. Without it any integration is kind of crude.

Is the service the same when using bluetooth (except that you have to have another bluetooth device in range)?

I got the API data from ECOFLOW for my Delta 2 and it works:
curl -X GET
https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=XXXXX
-H 'Content-Type: application/json'
-H 'appKey: xxx'
-H 'secretKey: xxx'
It shows the following output:
object
code: "0"
message: "Success"
data: object
soc: 74
remainTime: -5939
wattsOutSum: 0
wattsInSum: 0

Have you that as well to integrate to HA (in confguration.yaml). You need to request appKey and secretKey from Ecoflow.
Please note that there is a bug with soc with an extra battery, the return value is only of the main one, not the average of the 2.
 - platform: rest
   unique_id: ecoflow_time_left
   unit_of_measurement: "min"
   device_class: duration
   name: Ecoflow Time Left
   resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxx
   value_template: '{{ "%.1f" | format(value_json.data.remainTime)}}'
   method: GET
   headers:
     content_type:  'application/json'
     appKey: 'xxx'
     secretKey: 'xxx'

 - platform: rest
   unique_id: ecoflow_watt_out
   unit_of_measurement: "W"
   device_class: power
   name: Ecoflow Watt Out
   resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxx
   value_template: '{{ "%.1f" | format(value_json.data.wattsOutSum)}}'
   method: GET
   headers:
     content_type:  'application/json'
     appKey: 'xxx'
     secretKey: 'xxx'

 - platform: rest
   unique_id: ecoflow_watt_in
   unit_of_measurement: "W"
   device_class: power
   name: Ecoflow Watt In
   resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxx
   value_template: '{{ "%.1f" | format(value_json.data.wattsInSum)}}'
   method: GET
   headers:
     content_type:  'application/json'
     appKey: 'xxx'
     secretKey: 'xxx'

 - platform: rest
   unique_id: ecoflow_soc
   unit_of_measurement: "%"
   device_class: battery
   name: Ecoflow State of Charge
   resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxx
   value_template: '{{ "%.1f" | format(value_json.data.soc)}}'
   method: GET
   headers:
     content_type:  'application/json'
     appKey: 'xxx'
     secretKey: 'xxx'

How it looks (minutes have been converted to H:M:

I think your use of the REST Platform is very unfriendly to the Ecoflow API.
If you would use RESTful (https://www.home-assistant.io/integrations/rest/) I believe the same sensors/result could be archived with just one API call. For each update your HA instance will execute four API calls!

I agree - e.g. something like this
sensor:

platform: rest
name: ecoflow_xxxx
resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxxxxxxxxxxxxxx
scan_interval: 5
timeout: 30
authentication: digest
headers:
User-Agent: Home Assistant
Content-Type: application/json
Accept: application/json
appKey: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
secretKey: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
json_attributes_path: '$.data'
json_attributes:

soc
remainTime
wattsOutSum
wattsInSum
template:

sensor:

name: "EcoFlow xxxx - State of charge"
unit_of_measurement: "min"
device_class: battery
state: >
{% if state_attr('sensor.ecoflow_xxx', 'soc') == None %}
0
{% else %}
{{ state_attr('sensor.ecoflow_xxx', 'soc') }}
{% endif %}

sensor:

name: "EcoFlow xxx - Remain time"
unit_of_measurement: "%"
device_class: duration
state: >
{% if state_attr('sensor.ecoflow_xxx', 'remainTime') == None %}
0
{% else %}
{{ state_attr('sensor.ecoflow_xxx', 'remainTime') }}
{% endif %}

sensor:

name: "EcoFlow xxx - Watts Out Sum"
unit_of_measurement: "W"
device_class: power
state: >
{% if state_attr('sensor.ecoflow_xxx', 'wattsOutSum') == None %}
0
{% else %}
{{ state_attr('sensor.ecoflow_xxx', 'wattsOutSum') }}
{% endif %}

sensor:

name: "EcoFlow xxx - Watts In Sum"
unit_of_measurement: "W"
device_class: power
state: >
{% if state_attr('sensor.ecoflow_xxx', 'wattsInSum') == None %}
0
{% else %}
{{ state_attr('sensor.ecoflow_xxx', 'wattsInSum') }}
{% endif %}

Thank you @maltetgh and @Jenda987 for the tip! I've updated that in my HA.
Though one would argue that hammering Ecoflow APi could make them give us access locally to our Delta2 (or close the API completly!).

Can you only read or also write to that API? Especially setting the AC in Watts like in the App?

Can you only read or also write to that API? Especially setting the AC in Watts like in the App?
Nope, only read, sadly...

i have made like this (inspired by this thread)
sensor:

platform: rest
name: ecoflow_xxxxxxxxxxxxxxxxxx
resource: https://api.ecoflow.com/iot-service/open/api/device/queryDeviceQuota?sn=xxxxxxxxxxxxxxxxxx
scan_interval: 5
timeout: 30
authentication: digest
headers:
User-Agent: Home Assistant
Content-Type: application/json
Accept: application/json
appKey: yyyyyyyyyyyyyyyyyyyy
secretKey: zzzzzzzzzzzzzzzzzzzzz
json_attributes_path: '$.data'
json_attributes:

soc
remainTime
wattsOutSum
wattsInSum

template:
- sensors:
ecoflow_xxxxxxxxxxxxxxxxxx_in:
unique_id: 'ecoflow_xxxxxxxxxxxxxxxxxx_in'
device_class: power
unit_of_measurement: "W"
value_template: '{{int(state_attr("sensor.ecoflow_xxxxxxxxxxxxxxxxxx", "wattsInSum"))}}'
ecoflow_xxxxxxxxxxxxxxxxxx_out:
unique_id: 'ecoflow_xxxxxxxxxxxxxxxxxx_out'
device_class: power
unit_of_measurement: "W"
value_template: '{{int(state_attr("sensor.ecoflow_xxxxxxxxxxxxxxxxxx", "wattsOutSum"))}}'
ecoflow_xxxxxxxxxxxxxxxxxx_remain:
unique_id: 'ecoflow_xxxxxxxxxxxxxxxxxx_remain'
device_class: duration
unit_of_measurement: "min"
value_template: '{{int(state_attr("sensor.ecoflow_xxxxxxxxxxxxxxxxxx", "remainTime"))}}'
ecoflow_xxxxxxxxxxxxxxxxxx_bat:
unique_id: 'ecoflow_xxxxxxxxxxxxxxxxxx_bat'
device_class: battery
unit_of_measurement: "%"
value_template: '{{int(state_attr("sensor.ecoflow_xxxxxxxxxxxxxxxxxx", "soc"))}}'
    ecoflow_delta_solar_in:
        unique_id: 'ecoflow_delta_solar_in'
        value_template: '{% if states("switch.sonoff_10013a7d14") == "on" %}0{% else %}{{ states("sensor.ecoflow_ddebz5zda210752_in")}}{% endif %}'
        device_class: power
        unit_of_measurement: "W"
    ecoflow_delta_power_in:
        unique_id: 'ecoflow_delta_power_in'
        value_template: '{% if states("switch.sonoff_10013a7d14") == "on" %}{{ states("sensor.ecoflow_ddebz5zda210752_in")}}{% else %}0{% endif %}'
        device_class: power
        unit_of_measurement: "W"

then if my sonoff plug is on (power from grid) i push watts in in power grid fake sensor else in solar fake sensor  by this way i can have a "solar input" like value , if someone have an idea to make a fake sensor (calculated) to have a kwh value (input/output, solar/grid) to let us use it in energy tab it could be great

to put in configuration.yml.txt
this is for configuration.yml for visual i use a custom plugin (on HACS) custom tesla style power card
with code below (serial removed replaced by xxx)
type: custom:tesla-style-solar-power-card
show_w_not_kw: 1
speed_factor: 0.2
hide_inactive_lines: 1
show_gap: true
change_house_bubble_color_with_flow: 0
energy_flow_diagramm_line_factor: 2
battery_extra_entity: sensor.ecoflow_xxx_bat
grid_to_battery_entity: sensor.ecoflow_delta_power_in
generation_to_battery_entity: sensor.ecoflow_delta_solar_in
battery_to_house_entity: sensor.ecoflow_xxx_out
generation_extra_entity: null
grid_extra_entity: switch.sonoff_xxx

to put in configuration.yml.txt
this is for configuration.yml for visual i use a custom plugin (on HACS) custom tesla style power card
with code below (serial removed replaced by xxx)
type: custom:tesla-style-solar-power-card show_w_not_kw: 1 speed_factor: 0.2 hide_inactive_lines: 1 show_gap: true change_house_bubble_color_with_flow: 0 energy_flow_diagramm_line_factor: 2 battery_extra_entity: sensor.ecoflow_xxx_bat grid_to_battery_entity: sensor.ecoflow_delta_power_in generation_to_battery_entity: sensor.ecoflow_delta_solar_in battery_to_house_entity: sensor.ecoflow_xxx_out generation_extra_entity: null grid_extra_entity: switch.sonoff_xxx

Works, tks you.

Hello, Does this api code still work for you? it stopped working yesterday for me…

I've implemented basic support for Delta 2 and River 2 Max.

I've implemented basic support for Delta 2 and River 2 Max.

I can confirm this working on my Delta 2

Fantastic! Works perfectly with my Delta 2. Thank you for the super job.

After send disable wifi command, this ports opening. Any wrong command (agressive scan) - closed. + private message on mastadon :)
PORT      STATE    SERVICE    VERSION
340/tcp   filtered unknown
1062/tcp  filtered veracity
1216/tcp  filtered etebac5
1600/tcp  filtered issd
2030/tcp  filtered device2
3333/tcp  filtered dec-notes
4006/tcp  filtered pxc-spvr
5051/tcp  filtered ida-agent
5432/tcp  filtered postgresql
6543/tcp  filtered mythtv
9968/tcp  filtered unknown
10002/tcp filtered documentum
10617/tcp filtered unknown
50000/tcp filtered ibm-db2
52869/tcp filtered unknown


Add support for np.correlate and np.convolve

As title. Lack of FFT support prevents the implementation of
efficient convolution alg.
Closes #2500

Codecov Report

Merging #2777 into master will decrease coverage by 0.05%.
The diff coverage is 62.32%.

@@            Coverage Diff             @@
##           master    #2777      +/-   ##
==========================================
- Coverage   86.19%   86.14%   -0.06%
==========================================
  Files         323      323
  Lines       66721    66866     +145
  Branches     7455     7481      +26
==========================================
+ Hits        57513    57603      +90
- Misses       8016     8070      +54
- Partials     1192     1193       +1


[FIX] Missing a few startup script for Superprofile

Fixes the Superprofile Docker start script.
Adds:

[x] A startup script to fix fauna data init
[x] Update docs to add VM support

Thank you!

Thanks.

Backport data initialization  #182

Thanks @Dnouv for looking over the bug so quickly!😇


Fix imports and docs about CSS imports by not specifying node_modules.

In Angular, imports of CSS files from third party libraries should be done without specifying node_modules.
Specifying that folder makes it so applications fail to compile in Angular 16 with the new ESBuild feature.

It gets rid of the following error message:
X [ERROR] Can't find stylesheet to import.
  ╷
1 │ @import "node_modules/@yaireo/tagify/src/tagify";
  │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  node_modules\ngx-tagify\styles\tagify.scss 1:9  root stylesheet [plugin angular-sass]

    angular:styles/global:styles:2:8:
      2 │ @import 'node_modules/ngx-tagify/styles/tagify.scss';

Maybe I added node_modules/ after deprecation of ~, because my IDE was not resolving it otherwise. By now, it works. Thanks!

Thank you :)

@Brakebein You have undone this change, which breaks any project using Angular's esbuild based compilation.
https://github.com/Brakebein/ngx-tagify/commit/4d274a0f037617d3b968dfac0784b6b7efb8a177

No worries, I know this can be tricky at times. Thanks for the quick reaction


Refresh fails to refresh

Type: Bug
Opened a saved query.
Called designer.
Added a column.
Published change.
Closed designer.
Added new column to saved query.
New column flagged as not found.
Refreshed (several times).
Error still there.
Closed query.
Reopened query.
Problem gone.
Azure Data Studio version: azuredatastudio 1.46.1 (ba29842b81dec01177415e53948ca2168e69c3f8, 2023-10-02T18:14:22.887Z)
OS version: Windows_NT x64 10.0.19045
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E3-1230 v5 @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.92GB (6.51GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

newdatabase
kev
1.0.0

admin-pack
Mic
0.0.2

admin-tool-ext-win
Mic
0.1.3

agent
Mic
0.49.0

import
Mic
1.5.5

powershell
ms-
2022.7.2

profiler
Mic
0.14.0

query-history
Mic
0.5.3

schema-compare
Mic
1.21.0

sql-database-projects
Mic
1.3.1

schema-visualization
R0t
0.9.1

db-snapshot-creator
sea
0.1.0

simple-data-scripter
sea
0.1.6

vscodeintellicode
Vis
1.2.1

@deej79
Can you elaborate how did you refresh?
Did you try running "Refresh Intellisense Cache" command?

Right-click on table | Refresh
Right-click on database | Refresh
Right-click on connection | Refresh
I don't know anything about the "Refresh Intellisense Cache" command. Where is it or how is it invoked?

Additional information:
I added more columns using Design option.
I added the new columns to a DISCONNECTed query. They were all recognized.
I connected and ran successfully.
In the first pass (as reported earlier) the query tab was CONNECTed to the database.

You can run "Refresh Intellisense Cache" command using below steps:

Ctrl + Shift + P or Go To "Manage" (Gear) Icon > Run Command Palette...
Start typing "Refresh Intellisense Cache" and select command to run.

This will trigger refresh in intellisense to load new database objects added to your database.
Refreshing connection or objects doesn't trigger this command.

Closing as solution has been provided.


Error message during start

Factorio version 1.1.57
Error:
Failed to load mods: Error while loading item prototype "pc-unlimited-uranium-rounds-magazine" (ammo): Value (inf) outside of range. The data type allows values from -((huge number)) to ((huge number)) in propriety tree a ROOT.ammo.pc-unlimited-uranium-rounds-magazine.magazine_size

Update:
Downgrading Factorio to version 1.1.53 fixed the issue (for now)

Hi! Thanks for reporting the issue.
Could you please send a screenshot of the error? It includes some small little details that could help solve the problem.

Sure

Thanks! I think I see the issue: The Factorio developers have changed the limit of the magazine size from infinite to the 128-bit integer limit. I'll have to release an update that changes the magazine size to said 128-bit integer limit.
It's still practically infinite, like how would oneself use 340 undecillion bullets?
Anyway, thanks again for reporting! A patch should be out in the next 12 hours.

Thanks for the quick response :)

A hotfix has been released, which (should) fix the bug. It is a bit of a bodge, so it will need improvement later, and technically, the ammo is no longer infinite, but practically, it is.
Again, thank you so much for reporting this issue! If you encounter this bug (or any other bug) again, please make a new issue. Cheers!


Removed fax field from order billing

Since the fax field is no longer present in 5.2 order generation failed.
By removing the fax field order generation works again.

@bcremer should we merge this?
@3stadt could you update your branch please?


The daemon died after some time for no reason

Do you have any logs from this session?

I have the same thing happening. Nothing useful in my logs. The process just seems to randomly die after a period of time.

@downspot do you have debug enables logging? Also could you send the log anyway, it might be useful for debugging.

Don't have debugging enabled. I am not sure I see an option for that. Running Automated EBS Snapshots version 0.4.1. Github is not letting me attach the file.
2015-10-11 00:33:42,818 - auto-ebs - INFO - Connecting to AWS EC2 in us-east-1
2015-10-11 00:33:45,274 - auto-ebs - INFO - The newest snapshot for vol-becc92fa is 1402 seconds old
2015-10-11 00:33:45,274 - auto-ebs - INFO - No need for a new snapshot of vol-becc92fa
2015-10-11 00:33:45,396 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:45,547 - auto-ebs - INFO - The newest snapshot for vol-f5e6b8b1 is 1397 seconds old
2015-10-11 00:33:45,548 - auto-ebs - INFO - No need for a new snapshot of vol-f5e6b8b1
2015-10-11 00:33:45,681 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:46,062 - auto-ebs - INFO - The newest snapshot for vol-89109472 is 1394 seconds old
2015-10-11 00:33:46,062 - auto-ebs - INFO - No need for a new snapshot of vol-89109472
2015-10-11 00:33:46,233 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:46,355 - auto-ebs - INFO - The newest snapshot for vol-7c109487 is 1389 seconds old
2015-10-11 00:33:46,355 - auto-ebs - INFO - No need for a new snapshot of vol-7c109487
2015-10-11 00:33:46,506 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:46,639 - auto-ebs - INFO - The newest snapshot for vol-c5f9663e is 1384 seconds old
2015-10-11 00:33:46,639 - auto-ebs - INFO - No need for a new snapshot of vol-c5f9663e
2015-10-11 00:33:46,834 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:46,961 - auto-ebs - INFO - The newest snapshot for vol-a6f9665d is 1380 seconds old
2015-10-11 00:33:46,961 - auto-ebs - INFO - No need for a new snapshot of vol-a6f9665d
2015-10-11 00:33:47,104 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:47,782 - auto-ebs - INFO - The newest snapshot for vol-f3ea7508 is 1376 seconds old
2015-10-11 00:33:47,783 - auto-ebs - INFO - No need for a new snapshot of vol-f3ea7508
2015-10-11 00:33:47,953 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:48,367 - auto-ebs - INFO - The newest snapshot for vol-00ea75fb is 1372 seconds old
2015-10-11 00:33:48,367 - auto-ebs - INFO - No need for a new snapshot of vol-00ea75fb
2015-10-11 00:33:48,528 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:48,870 - auto-ebs - INFO - The newest snapshot for vol-6059499b is 1366 seconds old
2015-10-11 00:33:48,870 - auto-ebs - INFO - No need for a new snapshot of vol-6059499b
2015-10-11 00:33:49,060 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:49,278 - auto-ebs - INFO - The newest snapshot for vol-f9415102 is 1362 seconds old
2015-10-11 00:33:49,278 - auto-ebs - INFO - No need for a new snapshot of vol-f9415102
2015-10-11 00:33:49,402 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:49,537 - auto-ebs - INFO - The newest snapshot for vol-f0f1ec0b is 1356 seconds old
2015-10-11 00:33:49,537 - auto-ebs - INFO - No need for a new snapshot of vol-f0f1ec0b
2015-10-11 00:33:49,658 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:49,804 - auto-ebs - INFO - The newest snapshot for vol-d7ecf12c is 1352 seconds old
2015-10-11 00:33:49,804 - auto-ebs - INFO - No need for a new snapshot of vol-d7ecf12c
2015-10-11 00:33:49,932 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:50,082 - auto-ebs - INFO - The newest snapshot for vol-05812bff is 1348 seconds old
2015-10-11 00:33:50,082 - auto-ebs - INFO - No need for a new snapshot of vol-05812bff
2015-10-11 00:33:50,244 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:50,380 - auto-ebs - INFO - The newest snapshot for vol-62862c98 is 1345 seconds old
2015-10-11 00:33:50,381 - auto-ebs - INFO - No need for a new snapshot of vol-62862c98
2015-10-11 00:33:50,501 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:50,632 - auto-ebs - INFO - The newest snapshot for vol-d4963c2e is 1343 seconds old
2015-10-11 00:33:50,632 - auto-ebs - INFO - No need for a new snapshot of vol-d4963c2e
2015-10-11 00:33:50,747 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:50,900 - auto-ebs - INFO - The newest snapshot for vol-9a973d60 is 1340 seconds old
2015-10-11 00:33:50,900 - auto-ebs - INFO - No need for a new snapshot of vol-9a973d60
2015-10-11 00:33:51,178 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:51,318 - auto-ebs - INFO - The newest snapshot for vol-99e56063 is 1339 seconds old
2015-10-11 00:33:51,318 - auto-ebs - INFO - No need for a new snapshot of vol-99e56063
2015-10-11 00:33:51,449 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:51,602 - auto-ebs - INFO - The newest snapshot for vol-bbe76241 is 1336 seconds old
2015-10-11 00:33:51,603 - auto-ebs - INFO - No need for a new snapshot of vol-bbe76241
2015-10-11 00:33:51,711 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:51,838 - auto-ebs - INFO - The newest snapshot for vol-a2a82f58 is 1333 seconds old
2015-10-11 00:33:51,838 - auto-ebs - INFO - No need for a new snapshot of vol-a2a82f58
2015-10-11 00:33:51,960 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:52,095 - auto-ebs - INFO - The newest snapshot for vol-72b73088 is 1331 seconds old
2015-10-11 00:33:52,096 - auto-ebs - INFO - No need for a new snapshot of vol-72b73088
2015-10-11 00:33:52,225 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:52,480 - auto-ebs - INFO - The newest snapshot for vol-1d9e0b74 is 1329 seconds old
2015-10-11 00:33:52,480 - auto-ebs - INFO - No need for a new snapshot of vol-1d9e0b74
2015-10-11 00:33:52,609 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:52,728 - auto-ebs - INFO - The newest snapshot for vol-12b5dd7b is 1326 seconds old
2015-10-11 00:33:52,728 - auto-ebs - INFO - No need for a new snapshot of vol-12b5dd7b
2015-10-11 00:33:52,860 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:52,990 - auto-ebs - INFO - The newest snapshot for vol-66e2ff0f is 1323 seconds old
2015-10-11 00:33:52,991 - auto-ebs - INFO - No need for a new snapshot of vol-66e2ff0f
2015-10-11 00:33:53,109 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:53,231 - auto-ebs - INFO - The newest snapshot for vol-889c81e1 is 1320 seconds old
2015-10-11 00:33:53,232 - auto-ebs - INFO - No need for a new snapshot of vol-889c81e1
2015-10-11 00:33:53,422 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:53,566 - auto-ebs - INFO - The newest snapshot for vol-c8227681 is 1315 seconds old
2015-10-11 00:33:53,566 - auto-ebs - INFO - No need for a new snapshot of vol-c8227681
2015-10-11 00:33:53,696 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:53,827 - auto-ebs - INFO - The newest snapshot for vol-28346561 is 1310 seconds old
2015-10-11 00:33:53,827 - auto-ebs - INFO - No need for a new snapshot of vol-28346561
2015-10-11 00:33:53,941 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:54,057 - auto-ebs - INFO - The newest snapshot for vol-31b6e478 is 1306 seconds old
2015-10-11 00:33:54,058 - auto-ebs - INFO - No need for a new snapshot of vol-31b6e478
2015-10-11 00:33:54,179 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:54,314 - auto-ebs - INFO - The newest snapshot for vol-c84af683 is 1301 seconds old
2015-10-11 00:33:54,314 - auto-ebs - INFO - No need for a new snapshot of vol-c84af683
2015-10-11 00:33:54,444 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:54,586 - auto-ebs - INFO - The newest snapshot for vol-6a61fd21 is 1295 seconds old
2015-10-11 00:33:54,586 - auto-ebs - INFO - No need for a new snapshot of vol-6a61fd21
2015-10-11 00:33:54,778 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:54,904 - auto-ebs - INFO - The newest snapshot for vol-bb3ba7f0 is 1291 seconds old
2015-10-11 00:33:54,904 - auto-ebs - INFO - No need for a new snapshot of vol-bb3ba7f0
2015-10-11 00:33:55,131 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:55,263 - auto-ebs - INFO - The newest snapshot for vol-31342cdf is 1286 seconds old
2015-10-11 00:33:55,263 - auto-ebs - INFO - No need for a new snapshot of vol-31342cdf
2015-10-11 00:33:55,428 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:55,593 - auto-ebs - INFO - The newest snapshot for vol-db31f33a is 1281 seconds old
2015-10-11 00:33:55,593 - auto-ebs - INFO - No need for a new snapshot of vol-db31f33a
2015-10-11 00:33:55,802 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:55,922 - auto-ebs - INFO - The newest snapshot for vol-7c36f49d is 1277 seconds old
2015-10-11 00:33:55,922 - auto-ebs - INFO - No need for a new snapshot of vol-7c36f49d
2015-10-11 00:33:56,076 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:56,229 - auto-ebs - INFO - The newest snapshot for vol-ec42ef0d is 1272 seconds old
2015-10-11 00:33:56,230 - auto-ebs - INFO - No need for a new snapshot of vol-ec42ef0d
2015-10-11 00:33:56,351 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:56,501 - auto-ebs - INFO - The newest snapshot for vol-8142ef60 is 1268 seconds old
2015-10-11 00:33:56,502 - auto-ebs - INFO - No need for a new snapshot of vol-8142ef60
2015-10-11 00:33:56,608 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:56,751 - auto-ebs - INFO - The newest snapshot for vol-049307e5 is 1262 seconds old
2015-10-11 00:33:56,751 - auto-ebs - INFO - No need for a new snapshot of vol-049307e5
2015-10-11 00:33:56,886 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:57,006 - auto-ebs - INFO - The newest snapshot for vol-149c08f5 is 1258 seconds old
2015-10-11 00:33:57,006 - auto-ebs - INFO - No need for a new snapshot of vol-149c08f5
2015-10-11 00:33:57,113 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:57,247 - auto-ebs - INFO - The newest snapshot for vol-f482c215 is 1253 seconds old
2015-10-11 00:33:57,247 - auto-ebs - INFO - No need for a new snapshot of vol-f482c215
2015-10-11 00:33:57,365 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:57,500 - auto-ebs - INFO - The newest snapshot for vol-7e82c29f is 1249 seconds old
2015-10-11 00:33:57,501 - auto-ebs - INFO - No need for a new snapshot of vol-7e82c29f
2015-10-11 00:33:57,763 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:57,910 - auto-ebs - INFO - The newest snapshot for vol-2aace7cb is 1243 seconds old
2015-10-11 00:33:57,910 - auto-ebs - INFO - No need for a new snapshot of vol-2aace7cb
2015-10-11 00:33:58,055 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:58,190 - auto-ebs - INFO - The newest snapshot for vol-28a4f4c9 is 1239 seconds old
2015-10-11 00:33:58,190 - auto-ebs - INFO - No need for a new snapshot of vol-28a4f4c9
2015-10-11 00:33:58,326 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:58,462 - auto-ebs - INFO - The newest snapshot for vol-a6a5f547 is 1234 seconds old
2015-10-11 00:33:58,462 - auto-ebs - INFO - No need for a new snapshot of vol-a6a5f547
2015-10-11 00:33:58,591 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:58,719 - auto-ebs - INFO - The newest snapshot for vol-46a5f5a7 is 1229 seconds old
2015-10-11 00:33:58,719 - auto-ebs - INFO - No need for a new snapshot of vol-46a5f5a7
2015-10-11 00:33:58,827 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:58,959 - auto-ebs - INFO - The newest snapshot for vol-56f1a3b7 is 1224 seconds old
2015-10-11 00:33:58,959 - auto-ebs - INFO - No need for a new snapshot of vol-56f1a3b7
2015-10-11 00:33:59,094 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:59,222 - auto-ebs - INFO - The newest snapshot for vol-6e6c318f is 1221 seconds old
2015-10-11 00:33:59,222 - auto-ebs - INFO - No need for a new snapshot of vol-6e6c318f
2015-10-11 00:33:59,348 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:59,485 - auto-ebs - INFO - The newest snapshot for vol-2a81dfcb is 1216 seconds old
2015-10-11 00:33:59,485 - auto-ebs - INFO - No need for a new snapshot of vol-2a81dfcb
2015-10-11 00:33:59,600 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:33:59,766 - auto-ebs - INFO - The newest snapshot for vol-312e14d0 is 1211 seconds old
2015-10-11 00:33:59,766 - auto-ebs - INFO - No need for a new snapshot of vol-312e14d0
2015-10-11 00:33:59,910 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:00,118 - auto-ebs - INFO - The newest snapshot for vol-d0494c31 is 1208 seconds old
2015-10-11 00:34:00,118 - auto-ebs - INFO - No need for a new snapshot of vol-d0494c31
2015-10-11 00:34:00,268 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:00,418 - auto-ebs - INFO - The newest snapshot for vol-de27263f is 1203 seconds old
2015-10-11 00:34:00,419 - auto-ebs - INFO - No need for a new snapshot of vol-de27263f
2015-10-11 00:34:00,558 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:00,728 - auto-ebs - INFO - The newest snapshot for vol-402a2ba1 is 1197 seconds old
2015-10-11 00:34:00,728 - auto-ebs - INFO - No need for a new snapshot of vol-402a2ba1
2015-10-11 00:34:00,872 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:00,996 - auto-ebs - INFO - The newest snapshot for vol-c5bc0025 is 1192 seconds old
2015-10-11 00:34:00,996 - auto-ebs - INFO - No need for a new snapshot of vol-c5bc0025
2015-10-11 00:34:01,123 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:01,278 - auto-ebs - INFO - The newest snapshot for vol-bda5195d is 1190 seconds old
2015-10-11 00:34:01,278 - auto-ebs - INFO - No need for a new snapshot of vol-bda5195d
2015-10-11 00:34:01,413 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:01,561 - auto-ebs - INFO - The newest snapshot for vol-f8a11d18 is 1188 seconds old
2015-10-11 00:34:01,561 - auto-ebs - INFO - No need for a new snapshot of vol-f8a11d18
2015-10-11 00:34:01,692 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:01,907 - auto-ebs - INFO - The newest snapshot for vol-bee0655e is 1185 seconds old
2015-10-11 00:34:01,907 - auto-ebs - INFO - No need for a new snapshot of vol-bee0655e
2015-10-11 00:34:02,051 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:02,210 - auto-ebs - INFO - The newest snapshot for vol-43e267a3 is 1184 seconds old
2015-10-11 00:34:02,210 - auto-ebs - INFO - No need for a new snapshot of vol-43e267a3
2015-10-11 00:34:02,360 - auto-ebs - INFO - No old snapshots to remove
2015-10-11 00:34:02,522 - auto-ebs - INFO - The newest snapshot for vol-4f645d86 is 1181 seconds old
2015-10-11 00:34:02,522 - auto-ebs - INFO - No need for a new snapshot of vol-4f645d86
2015-10-11 00:34:02,635 - auto-ebs - INFO - Deleting snapshot snap-3a6d2e76
2015-10-11 00:34:02,719 - auto-ebs - ERROR - 400 Bad Request
2015-10-11 00:34:02,719 - auto-ebs - ERROR -
InvalidSnapshot.InUseThe snapshot snap-3a6d2e76 is currently in use by ami-xxxxxxxx003bde58-e7cb-4fda-bd62-c066643c89c7
2015-10-11 00:34:02,719 - auto-ebs - WARNING - Could not remove snapshot: The snapshot snap-3a6d2e76 is currently in use by ami-833771e6
2015-10-11 00:34:02,719 - auto-ebs - INFO - Done deleting snapshots
2015-10-11 00:34:02,719 - auto-ebs - INFO - Sleeping 300 seconds until next check

I do not see the debug enabled option, how can enable it?

any update about this.

Sorry, have been too busy with other stuff. I intent to take a look sometime during this week or weekend. But a quick look in the code says at least that the debug option is always enabled per default. But there is not so much debug logging :/

good, keep me posted please.
If you need any help with the code, I would be happy to help.

I have not been able to reproduce this, my daemon runs continuously without any crashes. @FarasSadek do you have an error like the one @downspot reported too in your logs? I can't really see why that error would pose an issue for the daemon though, but it's the only oddity I see in the log..

Yeah that error seems like a moot point it's only referring to a snapshot that can't be removed as it's in use for an AMI. On a side note I should point out that that I am also running a cron job in addition to the daemon that is automatically generating the config files for watched and unwatched volumes. I shouldn't be doing something like this however as the daemon could be in the middle of reading those files while running and possibly crash the process? Basically I am doing this on a job, every 45 mins:
/opt/rh/python27/root/usr/bin/automated-ebs-snapshots --config /etc/aws/auto-ebs-snapshots.conf --watch-file /etc/aws/auto-ebs-snapshots-volumes-active.conf
/opt/rh/python27/root/usr/bin/automated-ebs-snapshots --config /etc/aws/auto-ebs-snapshots.conf --unwatch-file /etc/aws/auto-ebs-snapshots-volumes-inactive.conf
Which is adding and removing volumes based on whether the instance is running or not. The daemon could be reading these files while running and possibly be causing my crashes. Also since reporting this in the ticket I haven't had a crash, so there's that.

Just looked in the logs again and there is nothing that's error based other than the one pasted above. It's been running clean. My thinking is there is some other underlying problem unrelated to automated-ebs-snapshots. Will continue to monitor on my side.

YES,
I got this ERROR too.  But I don't think this is the cause of the issue.
On Sat, Oct 17, 2015 at 2:12 PM, Sebastian Dahlgren <
<EMAIL_ADDRESS>wrote:

I have not been able to reproduce this, my daemon runs continuously
without any crashes. @FarasSadek https://github.com/FarasSadek do you
have an error like the one @downspot https://github.com/downspot
reported too in your logs? I can't really see why that error would pose an
issue for the daemon though, but it's the only oddity I see in the log..
—
Reply to this email directly or view it on GitHub
https://github.com/skymill/automated-ebs-snapshots/issues/21#issuecomment-148938736
.

--
Faras Sadek
Senior System Engineer
Computing office
Harvard John A. Paulson School of Engineering and Applied Sciences
33 Oxford Street , MD G109
Cambridge MA 02138
<EMAIL_ADDRESS>http://www.seas.harvard.edu/directory/fadel

Possibly found what is killing the damon on my end. This is the last log entry I see before the damon died.
2015-12-06 01:57:25,042 - auto-ebs - ERROR - 400 Bad Request
2015-12-06 01:57:25,042 - auto-ebs - ERROR -
ConcurrentSnapshotLimitExceededToo many concurrent snapshot requests for a volume7a132795-ef08-4d45-929b-635552f24bc6


Pairing issues- Devices going dead while pairing

Hi Robert,
I am using the chip ZGM130S as the controller for the zwave devices to pair and control. While in the pairing process, I am facing issues.
When I trigger the device after initiating the pairing from zwaveJs-UI, I see that the device addition fails(node is dead) within the range of 1 meter. This issue is happening with all devices, i.e., Power, Battery, and FLIRS.
I also see that re-interviewing or refreshing is helping to fetch the device info, but I need to perform it a couple or more times.
I do not know if there's any issue in the zwaveJS UI or with the setting of tx power but I am encountering this issue very frequently. I am attaching the setting.json file for reference and the controller options screenshot. Let me know, what else is needed to study this issue and to provide us a solution.
Thank you.
Regards,
Mohan Krishna
settings.json

@AlCalzone any clue what could cause this?
2024-01-04T09:57:43.042Z CNTRLR   finished adding node 2:
                                    basic device class:    Routing Slave
                                    generic device class:  Thermostat
                                    specific device class: General Thermostat V2
                                    supported CCs:
                                    · Basic (0x20)
                                    · Manufacturer Specific (0x72)
                                    · Thermostat Mode (0x40)
                                    · Thermostat Setpoint (0x43)
                                    · Version (0x86)
                                    · Z-Wave Plus Info (0x5e)
                                    · Thermostat Fan Mode (0x44)
                                    · Multilevel Sensor (0x31)
                                    · Association (0x85)
                                    · Configuration (0x70)
                                    · Association Group Information (0x59)
                                    · Transport Service (0x55)
                                    · Device Reset Locally (0x5a)
                                    · Powerlevel (0x73)
                                    · Security (0x98)
                                    · Security 2 (0x9f)
                                    · Supervision (0x6c)
                                    · Firmware Update Meta Data (0x7a)
                                    controlled CCs:
2024-01-04T09:57:43.046Z CNTRLR » [Node 002] Assigning SUC return route...
2024-01-04T09:57:43.047Z CNTRLR » [Node 002] Deleting SUC return route...
2024-01-04T09:57:43.060Z SERIAL » 0x01060055000205ab                                                   (8 bytes)
2024-01-04T09:57:43.062Z DRIVER » [Node 002] [REQ] [DeleteSUCReturnRoute]
                                    payload: 0x000205
2024-01-04T09:57:43.083Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:43.086Z SERIAL « 0x0104015501ae                                                       (6 bytes)
2024-01-04T09:57:43.088Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:43.090Z DRIVER « [RES] [DeleteSUCReturnRoute]
                                    was executed: true
2024-01-04T09:57:43.124Z SERIAL « 0x01210055050139000000007f7f7f7f7f00010400000000020300007f7f7f7f7f0 (35 bytes)
                                  000b2
2024-01-04T09:57:43.126Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:43.128Z DRIVER « [REQ] [DeleteSUCReturnRoute]
                                    callback id:     5
                                    transmit status: NoAck
2024-01-04T09:57:43.142Z SERIAL » 0x01060051000206ac                                                   (8 bytes)
2024-01-04T09:57:43.144Z DRIVER » [Node 002] [REQ] [AssignSUCReturnRoute]
                                    payload: 0x000206
2024-01-04T09:57:43.147Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:43.150Z SERIAL « 0x0104015101aa                                                       (6 bytes)
2024-01-04T09:57:43.152Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:43.154Z DRIVER « [RES] [AssignSUCReturnRoute]
                                    was executed: true
2024-01-04T09:57:43.231Z SERIAL « 0x01210051060151000000007f7f7f7f7f00010600000000020300007f7f7f7f7f0 (35 bytes)
                                  000df
2024-01-04T09:57:43.233Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:43.236Z DRIVER « [REQ] [AssignSUCReturnRoute]
                                    callback id:     6
                                    transmit status: NoAck
2024-01-04T09:57:43.455Z SERIAL » 0x011000a900010002029f04250000000007fe                              (18 bytes)
2024-01-04T09:57:43.459Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      7
                                  └─[Security2CCKEXGet]
2024-01-04T09:57:43.474Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:43.476Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:57:43.478Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:43.481Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:57:47.645Z SERIAL « 0x011d00a90701019c007f7f7f7f7f00010700000000020400000000000000af    (31 bytes)
2024-01-04T09:57:47.658Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:47.672Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            7
                                    transmit status:        NoAck, took 4120 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:57:47.681Z SERIAL » 0x011000a900010002029f04250000000007fe                              (18 bytes)
2024-01-04T09:57:47.682Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      7
                                  └─[Security2CCKEXGet]
2024-01-04T09:57:47.685Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:47.689Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:57:47.690Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:47.692Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:57:51.846Z SERIAL « 0x011d00a907010199007f7f7f7f7f00010700000000020400000000000000aa    (31 bytes)
2024-01-04T09:57:51.855Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:51.865Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            7
                                    transmit status:        NoAck, took 4090 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:57:51.876Z SERIAL » 0x011000a900010002029f04250000000007fe                              (18 bytes)
2024-01-04T09:57:51.877Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      7
                                  └─[Security2CCKEXGet]
2024-01-04T09:57:51.880Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:51.884Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:57:51.885Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:51.887Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:57:56.017Z SERIAL « 0x011d00a907010197007f7f7f7f7f00010700000000020400000000000000a4    (31 bytes)
2024-01-04T09:57:56.027Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:56.035Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            7
                                    transmit status:        NoAck, took 4070 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:57:56.047Z CNTRLR   [Node 002] The node did not respond after 3 attempts, it is presumed dead
2024-01-04T09:57:56.051Z CNTRLR   [Node 002] Security S2 bootstrapping failed, the node was not granted any S2 s
                                  ecurity class: The node did not acknowledge the command (ZW0204)
2024-01-04T09:57:56.055Z CNTRLR   [Node 002] Beginning interview - last completed stage: None
2024-01-04T09:57:56.056Z CNTRLR   [Node 002] new node, doing a full interview...
2024-01-04T09:57:56.056Z CNTRLR » [Node 002] querying protocol info...
2024-01-04T09:57:56.065Z CNTRLR   [Node 002] [+] [Node Naming and Location] name: "pac03"
2024-01-04T09:57:56.080Z DRIVER       the message was handled
2024-01-04T09:57:56.085Z SERIAL » 0x010500410002b9                                                     (7 bytes)
2024-01-04T09:57:56.086Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x0002
2024-01-04T09:57:56.098Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:56.101Z SERIAL « 0x010a0141d39c0104080600f1                                          (12 bytes)
2024-01-04T09:57:56.102Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:56.104Z DRIVER « [RES] [GetNodeProtocolInfo]
                                    payload: 0xd39c0104080600
2024-01-04T09:57:56.109Z CNTRLR « [Node 002] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Thermostat
                                  specific device class: General Thermostat V2
                                  node type:             End Node
                                  is always listening:   true
                                  is frequent listening: false
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     100000 kbps
                                  protocol version:      3
2024-01-04T09:57:56.121Z CNTRLR   [Node 002] Interview stage completed: ProtocolInfo
2024-01-04T09:57:56.123Z CNTRLR » [Node 002] pinging the node...
2024-01-04T09:57:56.141Z SERIAL » 0x010f00a900010002010025000000000876                                (17 bytes)
2024-01-04T09:57:56.143Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      8
                                  └─[NoOperationCC]
2024-01-04T09:57:56.150Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:57:56.153Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:57:56.155Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:57:56.157Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:58:00.294Z SERIAL « 0x011d00a908010198007f7f7f7f7f00010700000000020400000000000000a4    (31 bytes)
2024-01-04T09:58:00.312Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:58:00.322Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            8
                                    transmit status:        NoAck, took 4080 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:58:00.327Z CNTRLR   [Node 002] The node did not respond after 1 attempts, it is presumed dead
2024-01-04T09:58:00.329Z CNTRLR   [Node 002] ping failed: The node did not acknowledge the command (ZW0204)
2024-01-04T09:58:00.332Z CNTRLR » [Node 002] querying node info...
2024-01-04T09:58:00.335Z CNTRLR » [Node 002] pinging the node...
2024-01-04T09:58:00.345Z SERIAL » 0x010f00a900010002010025000000000977                                (17 bytes)
2024-01-04T09:58:00.346Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      9
                                  └─[NoOperationCC]
2024-01-04T09:58:00.350Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:58:00.354Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:58:00.355Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:58:00.356Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:58:04.462Z SERIAL « 0x011d00a909010195007f7f7f7f7f00010700000000020400000000000000a8    (31 bytes)
2024-01-04T09:58:04.472Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:58:04.482Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            9
                                    transmit status:        NoAck, took 4050 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:58:04.489Z CNTRLR   [Node 002] The node did not respond after 1 attempts, it is presumed dead
2024-01-04T09:58:04.492Z CNTRLR   [Node 002] ping failed: The node did not acknowledge the command (ZW0204)
2024-01-04T09:58:04.494Z CNTRLR   [Node 002] Interview attempt (1/5) failed, node is dead.
2024-01-04T09:58:04.507Z DRIVER   all queues idle
2024-01-04T09:58:04.523Z CNTRLR » [Node 002] querying current thermostat mode...
2024-01-04T09:58:04.526Z CNTRLR » [Node 002] pinging the node...
2024-01-04T09:58:04.578Z DRIVER   all queues busy
2024-01-04T09:58:04.584Z SERIAL » 0x010f00a900010002010025000000000a74                                (17 bytes)
2024-01-04T09:58:04.585Z DRIVER » [Node 002] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      10
                                  └─[NoOperationCC]
2024-01-04T09:58:04.589Z SERIAL « [ACK]                                                                   (0x06)
2024-01-04T09:58:04.593Z SERIAL « 0x010401a90152                                                       (6 bytes)
2024-01-04T09:58:04.594Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:58:04.596Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2024-01-04T09:58:08.736Z SERIAL « 0x011d00a90a010198007f7f7f7f7f00010700000000020400000000000000a6    (31 bytes)
2024-01-04T09:58:08.751Z SERIAL » [ACK]                                                                   (0x06)
2024-01-04T09:58:08.762Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            10
                                    transmit status:        NoAck, took 4080 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    TX power:               0 dBm
                                    measured noise floor:   0 dBm
2024-01-04T09:58:08.769Z CNTRLR   [Node 002] The node did not respond after 1 attempts, it is presumed dead
2024-01-04T09:58:08.772Z CNTRLR   [Node 002] ping failed: The node did not acknowledge the command (ZW0204)
2024-01-04T09:58:08.774Z CNTRLR   [Node 002] failed to refresh values for Thermostat Mode, endpoint 0: The messa
                                  ge cannot be sent because node 2 is dead (ZW0202)
2024-01-04T09:58:08.779Z DRIVER   all queues idle

Did you change the power values, especially the measured at 0? If so, did someone tell you which values to use?

Hi @AlCalzone ,
Thanks for your response.
Yes, we updated the values of the measured at 0 to 3.3. PFA screenshot for reference.
And we are using ZGM130S , which is a silabs controller(700 series). Let me know if anything is needed.
Regards,
Mohan Krishna

Hi @AlCalzone,
Do you happen to have any updates on the above data? Can you please help us to sort out this?
Regards,
Mohan Krishna

https://github.com/zwave-js/node-zwave-js/issues/6521

One thing that might help is to upgrade the firmware on the Zstick.  I see from the picture it is 7.15.4.  Might want to read this https://zwave-js.github.io/node-zwave-js/#/troubleshooting/otw-upgrade

Hi @apella12,
Thanks for your response.
Yes, the thermostat is connected to a 5v DC input. The issue is not with a single device, and all powered devices are working in the same manner. When the pairing is initiated, we trigger the node info button to release NodeInfo from the device. Thereafter, we noticed the device is paired as dead and once we refresh CC or re-interview the nodeId then it'll pull the info from the device. It just stopped while pairing, as you said like a battery device.
Btw, Is there any problem with the power settings? I used 9.9, 3.3 dbm as the values for the normal power level & measured power at 0 dbm. Help us to resolve this issue.
Regards,
Mohan Krishna

As this is happening with all devices it could be the controller.  I would update the firmware to 7.18.3 That what I am using.  As to the power I don't know.  I have gotten conflicting advice from mfg, but my 700 is (6, 0) in USA).  Your values could be too high.

Unfortunately, the logs can't tell us why there is a connectivity problem with the device, but there is one. A few ideas:

The inclusion might (not sure) be happening at 40 kbps and then for normal communication the controller attempts to use 100 kbps, which is channel 0. That channel has a much higher background noise than the others (-87 dBm vs. -108 dBm), so there might be too much noise for reliable communication. Is there another device nearby that could cause this RF noise?
I'm still not sure which controller you have (the actual device, not the chip). Most 700 series controllers are indistinguishable from software. Is this a GPIO module or a USB stick? If it's a USB stick, did you put it on an extension cord?
Where did you get the values for the power setting from? Wrong values may cause connectivity issues.
Are both the controller and the devices using the same RF region (Europe)?


suggest the speed is the kilometer/hour by default

suggest the speed is the kilometer/hour by default.
such as this picture
https://share.weiyun.com/d9870bf162335e233840b1c72ba5e332

You can configure speed using server-wide once.


How to locate tool referenced in .csproj using DotNetCliToolReference?

Let's say I want to invoke some CLI command that is defined in .csproj like this:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <ItemGroup>
    <DotNetCliToolReference Include="SomeCliTool" Version="4.1.0" />
  </ItemGroup>
</Project>

Now, I would like to invoke the tool.
import tl = require('vsts-task-lib/task');
const pathToCliTool = tl.withMsbuild('./MyWebApplication.csproj').which('someclitool')
await ts.tool(pathToCliTool).exec();

I don't think I fully understand what you're trying to do. Why are you trying to accomplish by using 'withMsbuild'? The which function should be run directly on tl.
Could you provide more details on the issue you're facing?

tl.which('some-cli-tool-referenced-with-nuget') does to recognize the tool, since it is not globally installed. If I'm not mistaken...

Ok, so if I understand correctly, you have the tool installed somewhere, but not globally, and you need a way to find the path to tool?
I think what you might need is findMatch, theres some good documentation on this stuff here. Still not 100% sure I'm answering your question though. What are you trying to do with the 'withMsbuild' function?

I'm going to close, please reopen if appropriate.

Sorry, I forgot this issue.
Well, findMatch doesn't find it.
The thing is, that the tools is downloaded by nuget.exe somewhere (I don't now where) and it is possible to use it via Visual Studio's Package Manager Console (PowerShell with some extra paths).
However, I would like to invoke the tool in my build task.
Maybe somebody from msbuild or nuget team could help....
PS: There is no reopen button

Well, findMatch doesn't find it.

This still seems to me like a case where findMatch should be used (and if its not working that feels like a bug). How have you tried to use it?

@Liero any update on this - specifically could you provide a little more info on how you're trying to use findMatch?

I disvovered  that the tool I wanted to use (LibMan) works only when globally installed and doesn't work with DotNetCliToolReference, so this issue is not valid anymore. Thanks


Files are not in addons folder but this location is required

Hey! When installing the plugin via the asset store, the content is placed in the projects root folder. But the icon locations require the path to be  addons/scaffolder/assets.

Hey @creadicted! :/ Yeah, sorry about that. It's actually much more than just the icons depending on the directory structure.
Unfortunately, with the way I am actively making updates to this repo (as a submodule of my main game repo), it's not feasible for me to restructure the scaffolder repo to store the files in an addons/ folder inside of itself.
And--while it's probably technically possible for me to make the app able to dynamically update the expected path locations--there are so many parts of the application structure that depend of these path structures, and it would be an enormous amount of work to maintain all the logic to support that.
I've tried to update the README.md and getting_set_up.md docs to mention moving the files, but I'm not sure how discoverable that is for folks like you. I'll also make sure I update the AssetLib descriptions to mention this next time I update them!
Unfortunately, I don't think I can show any sort of console error message until long after all the build errors are reported within Godot.
Does that make sense?
Thanks for the feedback!

I think I have a solution. Next time I cut a release (in two-ish weeks, I think), I'll try moving all the scaffolder files into subdirectories within a separate branch, and I'll post that version in the AssetLib.


yoshimi: 1.3.6 -> <IP_ADDRESS>

please also merge into 15.09, as the previous version did not reliably work in ardour4.4

@cillianderoiste
When I tried to build locally again, I had the same error as travis had before.
This version builds locally, and fixes  the other bug, but travis still doesn't like it.

@cillianderoiste
Thanks!
Could you also merge this into 15.09, as the old version doesn't run reliably in ardour4.
Or should I do a separate PR for that?

@magnetophon thanks for reminding me. I've cherry-picked it to 15.09.


Added favicon

What is the change?
I have added a favicon for the website, code written in header.ejs (code:).The favicon is located in the images (which is created by me) folder which is inside the public folder and I have also changed the value const URL which is const URL = "mongodb://localhost:27017/blogDB"; (as you said) and one more thing the favicon created is simple it's just the logo with the border of color combination white and pink. I hope you will like my favicon :).
Related issue?
issue: #105
How was it tested?
I have tested the website by using the hyper terminal and mongod server.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:

"mongodb://localhost:27017/blogDB" this is only used for testing on your local system.
Add the favicon to assets folder
Change base branch to develop, follow the Contribution guidelines mentioned in CONTRIBUTING.md

This is how you change base branch

Sir, I have changed the destination of favicon to assets folder but I can't access favicon as it now not available in the static (public) folder and I have tried many ways to access favicon but I cant access it, sir can you please help where  I am going wrong?

Sir, I have changed the destination of favicon to assets folder but I can't access favicon as it now not available in the static (public) folder and I have tried many ways to access favicon but I cant access it, sir can you please help where I am going wrong?

I don't get it? You can't access it?
If you're a beginner I understand, I'd advise you to close this PR. Make a new branch from main and then add your changes and make a new PR.

Sir can I put the favicon inside the public folder because from there I can display it on the website using the HTML  tag but when the favicon is inside the assets then my HTML tag is not working.

Sir can I put the favicon inside the public folder because from there I can display it on the website using the HTML tag but when the favicon is inside the assets then my HTML tag is not working.

You have to change the path for

Sir can I put the favicon inside the public folder because from there I can display it on the website using the HTML tag but when the favicon is inside the assets then my HTML tag is not working.

You have to change the path in link tag.

Sir I did that but it's not working (favicon is located at assets folder).

Sir I did that but it's not working (favicon is located at assets folder).

Then it is incorrect

Sir this is the tag I used .I have located this tag under the header.ejs file. Now can you tell me where I am going wrong and what should be the correct path?

Sir, I have sent the screenshot of html tag which I am using.

Sir now can you tell me where I am going wrong and what should be the correct path?

Sir, I have sent the screenshot of html tag which I am using.

Sir now can you tell me where I am going wrong and what should be the correct path?

This is not the correct path.

I'll let you know the correct path after my class gets over.
Try this till then, try using this for setting favicon. Just update the path according to our project-
app.use('/favicon.ico', express.static('images/favicon.ico'));

OK sir :)

sir, correct path?

Sir, correct path?

You still couldn't figure out?

Since we used public folder for static files app.use(express.static("public"));
Add an images folder to public, store the favicon there and add this tag to the header.ejs.
<link rel="icon" href="/images/favicon.ico">

There are other methods to do this but since you're a beginner, this method will be easier 🙂

Ok, sir got it. Thank you

Sir one last question I am having  problem with editing so can I close this PR and create a new one and I will push my work to your develop repository?

Sir one last question I am having problem with editing so can I close this PR and create a new one and I will push my work to your develop repository?

Don't push it to develop, push your changes to a new branch and when making a PR change base branch to develop. Refer to screenshot sent above to see how change base branch while making PR.


Correction for raw affiliation Leiden Institute of Advanced Computer Science, Leiden University, The Netherlands; Leiden Institute of Computer Science , , , The ,; School of Science and Technology, University of Camerino, Italy; Sorbonne Université, CNRS, LIP6, France; Sorbonne Université, CNRS, LIP6, Paris, France,; of and , of , , ,

Correction needed for raw affiliation Leiden Institute of Advanced Computer Science, Leiden University, The Netherlands; Leiden Institute of Computer Science , , , The ,; School of Science and Technology, University of Camerino, Italy; Sorbonne Université, CNRS, LIP6, France; Sorbonne Université, CNRS, LIP6, Paris, France,; of and , of , , ,
raw_affiliation_name: Leiden Institute of Advanced Computer Science, Leiden University, The Netherlands; Leiden Institute of Computer Science , , , The ,; School of Science and Technology, University of Camerino, Italy; Sorbonne Université, CNRS, LIP6, France; Sorbonne Université, CNRS, LIP6, Paris, France,; of and , of , , ,
new_rors: 02en5vm52;05f82e368;02feahw73;0005w8d69;0496n6574;027bh9e22;05krcen59
previous_rors: 02en5vm52;05f82e368;02feahw73;0005w8d69;0496n6574;027bh9e22
works_examples: W4323066480
contact: 0ef0855ade1aecb28bf3dbf50250e582:7a451cf453916757e565c7820f @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Add support for specifying extra manifests via helm

Problem Statement
Fixes: https://github.com/external-secrets/external-secrets/issues/2961
Closes: #3417
Proposed Changes
How do you like to solve the issue and why? Explained in the issue.
Checklist

[X] I have read the contribution guidelines
[X] All commits are signed with git commit --signoff
[X] My changes have reasonable test coverage
[X] All tests pass with make test
[X] I ensured my PR is ready for review with make reviewable

hi @upodroid ! I believe this is a duplicate from https://github.com/external-secrets/external-secrets/pull/3417. While I don't mind that - same comments there apply here. Can you please add a simple helm unittest to make sure we have coverage for this feature? 😄 It could be a service account addition for what it's worth.

I didn't see that PR, he forgot to xref the issue. I'll fix the unit test now.

This PR was helpful.
https://github.com/traefik/traefik-helm-chart/pull/643

@upodroid  thank you for your contribution (on a sunday!) 😄


HTMLElement.style wrongly defined as readonly

The style property of HTMLElement must not be readonly. Please, read https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/style#Setting_styles carefully in order to understand why.

Quoting from the link above: "Styles should not be set by assigning a string directly to the style property (as in elt.style = "color: blue;"), since it is considered read-only"
What am I missing?

From the text you quoted, you are missing the "string" part. And if you just continue reading...

Instead, styles can be set by assigning values to the properties of style. For adding specific styles to an element without altering other style values, it is preferred to use the individual properties of style (as in elt.style.color = '...')

To me it seems that MDN's page needs some revision, but putting that aside, who hasn't at some point modified the style of an element directly? Haven't you ever done something like document.querySelector('#important-link').style.backgroundColor = 'red?

I think you've misunderstood how readonly works. It simply means that the property itself is read-only and you can't assign directly to it. But you can of course read the style property and then assign to any of its properties. In other words, this works fine:
const e: HTMLElement = getSomeHTMLElement();
e.style.backgroundColor = 'red';  // Ok

You're absolutely right. In any case, let me briefly explain what I was trying to do. It was something like this:
function f(e: Partial<HTMLElement>) { }

f({
    style: {color: 'red'}
})

Which I wrongly thought didn't work because of the readonly. What I really needed was a recursive version of Partial, which I created like so:
type DeepPartial<T> = {
    [P in keyof T]?: DeepPartial<T[P]>
}

Thanks for your time and patience 😉


feat: Agenda proposed badge

Adds a grey 'Proposed' badge to sessions with a state of proposed. The tooltip text is TBD
In dark mode darkens the 'BoF' badge to make it more readable. Before: . After:  .

This PR is awaiting the tooltip text to be provided.
fixes #8026

@cindymorgan : help us develop the right popup text?

@rjsparks hah, I'd DMd Cindy yesterday to follow up about this too


DBZ-6794 Dbz crashed on parsing MySQL DDL statement (SELECT 1 + @sum:=1 AS ss;)

https://issues.redhat.com/browse/DBZ-6794

Upstream pr: https://github.com/antlr/grammars-v4/pull/3661

@harveyyue Applied, thanks


Post UAT Iteration 1 - ErrorContractsNotRetrieved not raised by Chainlink Contracts Monitor when all nodes are down

During UAT,  Timo added a chainlink node for node monitoring and contracts monitoring. After switching off the VPN, a node downtime alert was raised as expected, however, an ErrorContractsNotRetrieved alert was not raised.
We need to investigate why this happened and if there is a bug we need to solve it.

This is the expected behaviour since ErrorNoSyncedDataSources alert is raised in this case. Moreover, ErrorContractsNotRetrieved is only raised when contracts could not be retrieved from weiwatchers. @crsfalzon

@Cherrett Opened this again. The issue is now the resolved alert.


Controls should reference their query using query = rather than sql =

It's simpler in code and readability to reference queries using the query = attribute rather than the sql = attribute.
This occurs throughout the mod, but as a specific example:
https://github.com/turbot/steampipe-mod-github-compliance/blob/226cb890cb650fd12455270f95f30ce6e0bdac49/cis_supply_chain_v100/section_1.sp#L69-L81
Could be changed from:
sql           = query.default_branch_requires_2_pull_request_reviews.sql

to:
query         = query.default_branch_requires_2_pull_request_reviews

Addressed in https://github.com/turbot/steampipe-mod-github-compliance/pull/39


resolved conflicts :feature/webpack3

Closing this PR since there is already one open for the same.

@reznord
It was for feature/webpack3 branch as it has fix conflicts :-)

I did it already ;) that's why closed this. Will be pushing the PR soon

Oh!!!!!  great 👍


Configure public endpoints on gateway for mithrill

Closing since this was done as part of preparation for production release.

Closing since this was done as part of preparation for production release.


Writing a string to a varint field can result in a message that cannot be deserialized

Example:
message Envelope {
	int32 type = 1;
	string name = 2;
}

/* ... */
var Envelope = compile(proto).Envelope;
var pbf = new Pbf();

Envelope.write({
    type: 'foo',
    name: 'test'
});

Envelope.read(new Pbf(pbf.finish()))

Result: Error: Unimplemented type: 4
It seems to be due to val being being coerced into NaN. I have not tested if other number types are affected.
A simple solution would be to force it to always be a number:
// Current
val = +val;

// Replacement
val = +val || 0;

But, maybe it would be better to if (isNaN(val)) throw new Error()?

Oddly enough, while testing adding a throw, I found that isNaN is really slow.
This reduces performance in the encode benchmark by about 25%.
if (isNaN(val)) throw new Error('Expected number');

On the other hand, this has almost no impact:
if (!(val < 0) && !(val >= 0)) throw new Error('Expected number');

I'd prefer val || 0 — we don't want to care about validating input too much, because the main priority of this library is performance and simplicity.


Bugfix/issue 35

Modified the TranscriptFetcher so that all the caption urls are searched through for a the desired language before making the request. This fixes issue #35 where the order in which YouTube returns the caption urls can bug the Fetcher out.
It also modifies the code so that English is the default language searched for.

bump

Hi @danielcliu,
sorry for the late reply, but I was on vacation for the last 2 weeks and very busy right before that. I will look at you PR today or tomorrow.
Thank you very much for your contribution!

@danielcliu took me a bit longer than expected to get around to implementing this, but I finally managed to do so. I think this approach is much more stable and reliable. Also it allows us to get a lot more structured information, which I have already used to improve the error messages. This makes it easy to add a public method to the API which provides the functionality which was asked for in #22. This also opens up the door for translating transcripts, which also is kinda cool.
What do you think of this? 😊

@danielcliu Thank you very much for your feedback, I will implement these changes and then merge this PR.
Also, once again, thank you very much for your contribution and time! 😊👍

the coverage has decreased by 0.7% do you care?

@danielcliu I generally do care, but in this case it has gone down, because there are no testcases for find_generated_transcript and find_manually_created_transcript, since they are no longer used by find_transcript. But as I will make them part of the public API before the next release, I will also add tests when I do that. So in this case I don't mind, as the tests will be added before the next release.
As you already pointed out, mixing different features in this PR probably isn't the most elegant thing to do. But I think a small project like this won't suffer from that, as I have a good overview of what's going on.


Support Webpack 4.0

What problem does this feature solve?
Running < webpack 4.0, which is much faster and improved over webpack 3x.
What does the proposed API look like?
N/A

Wrong project.  Whoops.


feat(client): document deis version

This feature flips docopt-go's version parsing logic switch off
in favour of our own in-house version parsing lib. This has the
following side-benefits, all of which are valid commands:

deis -v
deis version
deis help version

ported from deis/deis#4895

I tested this locally and verified it works. Nice job!
$ ./client/deis -v
2.0.0-dev
$ ./client/deis --version
2.0.0-dev
$ ./client/deis version
2.0.0-dev
$ ./client/deis
Usage: deis <command> [<args>...]
$ ./client/deis -h

The Deis command-line client issues API calls to a Deis controller.

Usage: deis <command> [<args>...]

Option flags::

  -h --help     display help information
  -v --version  display client version
...


9.4.1 breaks with<EMAIL_ADDRESS>(latest Stable)

Works fine with<EMAIL_ADDRESS>Both better-sqlite3 and multiple-ciphers break with electron LTS
Env: win64
Command:  node-gyp rebuild --release --target=29.0.1  --dist-url=https://electronjs.org/headers

@6180339 Already tested here and being tracked in the upstream.

Hello! Has there been any progress on this ? I tried upgrading to electron 29 and I faced an issue with better-sqlite as well. Thanks a lot!

@pelletier197 please see if https://github.com/WiseLibs/better-sqlite3/issues/1127 works for you.

Fixed in v9.4.5.


Typo in README

In README

.gitingore: Specifies intentionally untracked files to ignore

.gitingore should be .gitignore

fixed in next release


Arbitrary property name on first level

Hello!
I would like to ask a question about json-schema itself and how ajv maybe already manage that please.
JSON Schema
I need to use on first level of my object description an arbitrary property name, that could be latin letters for example. I'm using already patternPropererties keyword on some other objects but on first level, I really don't know to achieve it. It should give something like this:
        "^[A-Za-z]+$": {
          type: 'object'
        }

I hope my explanation is correct and really look forward on a way to do this and be validated.
Thanks!

Please ask general JSON Schema usage questions on StackOverflow, this issue tracker is for Ajv issues


[type: refactor] refactor code

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2123 (d2a594b) into master (3333cf3) will decrease coverage by 0.69%.
The diff coverage is 69.44%.

:exclamation: Current head d2a594b differs from pull request most recent head 2df3ae3. Consider uploading reports for the commit 2df3ae3 to get more accurate results

@@             Coverage Diff              @@
##             master    #2123      +/-   ##
============================================
- Coverage     60.21%   59.52%   -0.70%
+ Complexity     4044     4019      -25
============================================
  Files           609      607       -2
  Lines         18103    18076      -27
  Branches       1733     1727       -6
============================================
- Hits          10901    10759     -142
- Misses         6320     6442     +122
+ Partials        882      875       -7

Impacted Files
Coverage Δ

...yu/common/dto/convert/selector/DivideUpstream.java
0.00% <ø> (ø)

...mmon/dto/convert/selector/DubboSelectorHandle.java
0.00% <0.00%> (ø)

...to/convert/selector/SpringCloudSelectorHandle.java
0.00% <ø> (ø)

...common/dto/convert/selector/WebSocketUpstream.java
0.00% <ø> (ø)

...in/apache/dubbo/proxy/ApacheDubboProxyService.java
58.33% <0.00%> (+0.64%)
:arrow_up:

...u/plugin/cryptor/request/CryptorRequestPlugin.java
58.82% <ø> (ø)

...plugin/cryptor/response/CryptorResponsePlugin.java
59.37% <ø> (ø)

...lugin/cryptor/strategy/CryptorStrategyFactory.java
40.00% <ø> (ø)

...lugin/springcloud/loadbalance/LoadBalanceRule.java
0.00% <0.00%> (ø)

...ingcloud/handler/SpringCloudPluginDataHandler.java
6.89% <33.33%> (+6.89%)
:arrow_up:

... and 34 more

Continue to review full report at Codecov.

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


Exception preventing message list to load

This morning I noticed that the plugin is crashing Nylas for some reason. Inspecting the detailed logs I found this:
{"host":"xxx","timestamp":"2016-11-09T08:04:29.289Z","payload":"TypeError: Cannot read property '0' of undefined\n    at ThreadUnsubscribeStore.loadMessagesViaAPI (thread-unsubscribe-store.es6:129:9)\n    at ThreadUnsubscribeStore.loadLinks (thread-unsubscribe-store.es6:74:10)\n    at new ThreadUnsubscribeStore (thread-unsubscribe-store.es6:35:10)\n    at ThreadUnsubscribeStoreManager.getStoreForThread (thread-unsubscribe-store-manager.es6:11:26)\n    at ThreadUnsubscribeQuickActionButton.load (unsubscribe-buttons.jsx:96:50)\n    at ThreadUnsubscribeQuickActionButton.componentWillMount (unsubscribe-buttons.jsx:25:10)\n    at ReactCompositeComponentWrapper.performInitialMount (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactCompositeComponent.js:350:14)\n    at ReactCompositeComponentWrapper.mountComponent (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactCompositeComponent.js:257:21)\n    at Object.mountComponent (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactReconciler.js:47:35)\n    at ReactDOMComponent.mountChildren (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactMultiChild.js:240:44)\n    at ReactDOMComponent._createInitialChildren (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactDOMComponent.js:699:32)\n    at ReactDOMComponent.mountComponent (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactDOMComponent.js:524:12)\n    at Object.mountComponent (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactReconciler.js:47:35)\n    at ReactCompositeComponentWrapper.performInitialMount (/Applications/Nylas N1.app/Contents/Resources/app.asar/node_modules/react/lib/ReactCompositeComponent.js:370:34)\n    at

The soon I disable the plugin, everything is fine again.

I believe this is the same issue as #62

Fixed! Release v1.6.3 should solve it (there was a minor update in the thread object)

It's working for me now using the new v1.6.3. Thanks!


mac-28 & mac-29 lost external connection phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-28 & mac-29 lost external connection phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting both machines to restore connection.


Better errors for non-exported types

// @filename a.ts

declare function foo(): any

declare function bar(): any;

export { bar };

// @filename b.ts

import { foo, bar } from "./a";

Currently we provide the following error messages:
Module '"./a"' has no exported member 'foo'.
Module '"./a"' has no exported member 'bar'.

We could instead provide the errors:
Module '"./a"' declares 'foo' locally, but it is not exported.
Module '"./a"' declares 'bar' locally', but it is exported as 'baz'.

Also using the
'{0}' is declared here.

related span.
Later on, we could provide quick fixes to respectively

Export foo from ./a.
Correct the usage of bar to baz.

@DanielRosenwasser Is there any way to check if a variable was declared in a module? I mean, in order to show message Module '"./a"' declares 'foo' locally, but it is not exported., need to check if it was declared in a module locally.

There should be a symbol table for sourceFile.locals if it's non-exported (as opposed to sourceFile.symbol.exports.


Client Allocation Request for: 上海源信网络科技有限公司

Client Allocation Questions
Core Information

Name: 上海源信网络科技有限公司
Website / Social Media: https://www.yuanxinw.com
DataCap Requested: 5TiB
Addresses to be Notarized: f1qlbancoayu2xnyzh5b7v7cdccdfeprbsqapa7sq
Notary Requested: philippbanhardt

Hey @yuanxinw-network - thanks for your request. Can you kindly add more information / context here on:

yourself , e.g. include links to social media / news mentions etc
your history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time etc
type, size and source of the data you (and by extension other Discover participants) are looking to store on Filecoin, e.g. public data vs private data etc
your relationship with the data, especially with regard to copyright
how you intend to store the data on Filecoin, e.g. redundancy, location / miner preferences, etc

Thanks

Hey @yuanxinw-network - thanks for your request. Can you kindly add more information / context here on:

yourself , e.g. include links to social media / news mentions etc
your history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time etc
type, size and source of the data you (and by extension other Discover participants) are looking to store on Filecoin, e.g. public data vs private data etc
your relationship with the data, especially with regard to copyright
how you intend to store the data on Filecoin, e.g. redundancy, location / miner preferences, etc

Thanks

Hey philippbanhardt, thank you for your response. My answer to your question is as follows.
Q1: yourself , e.g. include links to social media / news mentions etc
A1: This is Yuanxin network found in 2018 which provide network data access and cloud computing platform service.
We are committed to providing customers with high-quality servers and network equipment hosting and rental, cloud computing, advanced defense, Internet broadband,  maintenance and management of IT infrastructure, private cloud deployment and other IT services.
Official website：https://www.yuanxinw.com
Q1: your history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time etc
A1: Our company have no history working on IPFS/Filecoin but we are very interested in it.
Q1: type, size and source of the data you (and by extension other Discover participants) are looking to store on Filecoin, e.g. public data vs private data etc
A1: We are going to support some private data, including the data users store in the server.
Q1: your relationship with the data, especially with regard to copyright
A1: We will sign use agreements with customers to ensure that data can be stored in filecoin.
Q1: how you intend to store the data on Filecoin, e.g. redundancy, location / miner preferences, etc
A1: We will choose some miners whose power must be lager than 1.5PiB and have stable performance. Each data should be stored in 8 copies, and at least five different miners.


fetch only the current user's media records

Description of changes
Please provide a short description of the change or if the change is sufficiently described in the GitHub issue, provide a link to the issue.
How has this been tested?
Please describe the test strategy you followed.

[ ] automated unit test
[ ] automated integration test
[ ] automated acceptance test
[ ] manual, exploratory test

In case of manual test, please document the test well including a set of user instructions and prerequisites. Each including an action, it's result, and where appropriate a screenshot.
Checklist before requesting a review

[ ] My code follows the coding guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My code fulfilles all acceptance criteria
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have made corresponding changes to the documentation
[ ] I have added explanation of architectural decision and rationales to wiki/adr
[ ] I have updated the changes in the ticket description

Checklist for reviewer

[ ] The code works and does not throw errors
[ ] The code is easy to understand and there are no confusing parts
[ ] The code follows the coding guidelines of this project
[ ] The code change accomplishes what it is supposed to do
[ ] I cannot think of any use case in which the code does not behave as intended
[ ] The added and existing tests reasonably cover the code change
[ ] I cannot think of any test cases, input or edge cases that should be tested in addition
[ ] Description of the change is included in the documentation

Gibt es eine Möglichkeit nach zu schauen, welche Medien in der Datenbank hochgeladen wurden?

Also anscheind wurden meine anderen Datein, auf Paul gespeichert und nicht auf mich 😆
Heißt aber es funktioniert wie es sollte.


Fix hovering for SVG elements

For SVG elements is returning an empty list. This makes it seem like the
webkit engine in my QT version is not at least respecting the CSSOM
spec. Making it use getBoundingClientRect only for SVG elements ensures
backwards compatibility.

Merged as e32eb0596d391b8dbfc161cd26245410da9aa5a7. Thanks!


Emacs doesn't follow Xresources settings on nixos-unstable

Issue description
After updating nixos-unstable, Emacs doesn't seem to follow my Xresources settings for turning off the toolbar, menubar etc. Other Xresources settings, such as for setting terminal colours and font do still work.
It doesn't seem like the nix expression for emacs has changed between the commits, so I'm a bit stumped. (I was on nixpkgs a7c8f5e before updating.)
A workaround would be to just disable these in the emacs init file itself (don't know how but pretty sure it's possible).
Steps to reproduce

Install emacs and xrdb, e.g. in /etc/nixos/configuration.nix:

  environment.systemPackages = with pkgs; [
    emacs
    xorg.xrdb
  ];

Create a file named xresources with the following contents:

emacs.cursorBlink:        off
emacs.menuBar:            off
emacs.toolBar:            off
emacs.verticalScrollBars: off

In /etc/nixos/configuration.nix:

  services.xserver.enable = true;
  services.xserver.displayManager.sessionCommands = "xrdb ~/xresources";

Start an X session and run the command emacs from a terminal, and observe that emacs starts, but the cursor blinks, the menu bar is visible, the toolbar is visible and vertical scroll bars are visible, despite all of these being turned off in the xresources file. 😞

Technical details

System: 17.09.git.abdb58e407 (Hummingbird)
Nix version: nix-env (Nix) 1.11.13
Nixpkgs version: "17.09.git.abdb58e407"
Sandboxing enabled: build-use-sandbox = false

So this is easy to do via init.el instead:
(blink-cursor-mode -1)
(menu-bar-mode -1)
(toggle-scroll-bar -1)
(tool-bar-mode -1)

I don't think I had any particular reason for disabling these in xresources instead of init.el in the first place, therefore I'll close this eventually if no one has any ideas. 😮

The main advantage of the Xresources method is that Emacs will turn off those things before it even creates the frame, potentially giving faster startup.

On second thought, I don't think I'll close this just yet, just because I feel like this might be an artifact of another underlying bug somewhere else or something, especially since I don't think the direct nix expression changed. So future debugging may involve seeing if there are other emacs x resources settings that are being set (if there are other settings, I haven't checked).
I'll close this though if I find that I cannot reproduce this anymore, or if multiple others say they cannot reproduce this (indicating it's most likely just something do to with my system in particular)... or if this issue becomes so old that everyone uses wayland now.

This is a real problem that I too have run into. For example, If you build Emacs with:
myEmacs = (pkgs.emacs.override {withGTK3=false; withGTK2=false; withX=true;});
xrdb cursor will not apply.

I've just run into this when switching to the emacsGcc version of emacs-overlay. I also had to update some stuff for my window manager since the WM_CLASS changed from emacs to WM_CLASS(STRING) = "-emacs-28-0-50-wrapped_", ".emacs-28.0.50-wrapped_". Could .Xresources loading be changed by emacs being wrapped somehow?

It looks like changing from emacs.$property to *.$property makes it work, so it does appear to be something to do with the name changing.


Is this buildable on MacOSX and Windows anymore?

No that would probably take some work to get the ports bsck up to date. Do you have any interest in giving it a go, please go ahead. But currently we cannot maintain that part.


Is there a way to generate check box?

If not, is it possible to customize code? Please advise, thank you

Hi huchenhai,
You can use the "format" in your schema like this:
{
  "type": "boolean",
  "format": "checkbox"
}

Hope this help.

@hoangcia  thank you, you saved my life

@hoangcia Hi, it works but another problem is, whatever the checkbox value is , it always shows as checked. Even when i set value false, but it still initialize as checked

@huchenhai  How are you setting the value? Just jumping in here that false and null both work for me when playing around with checkboxes in http://jeremydorn.com/json-editor/ .
I'm new to this library (migrating from JSONform as it seems more sleak/maintained) but happy to try to help.

@FilipNest Hi Filip, thank you. The problem has fixed, i guess it was because the data type i passed. I passed "false" as string, so it recognized any string as True.

@huchenhai it's polite to close the issue if it's been solved


Design for CD2L-GM graph matching algorithm

Description
We want to understand how we can implement the CD2L-GM algorithm in StellarGraph.
Read the paper, and do some high level design to understand if we can implement it using existing components or if we need to implement new components.
Done Checklist (Development)

[ ] Documentation on Google Docs
[ ] Team demo

CD2L-GM algorithm would be implemented from the published work Cross-domain Network Representation (http://gnosis.stellargraph.xyz/catalog/paper/899/). This work achieves graph matching in two seperate steps. One step is node matching across two independent graphs (each node in target graph to a group of nodes called super node in source graph). Within this step, potential links across graphs are predicted. The following step is path matching between paths (formed by generated super edges connecting super nodes) in source graph and edges in target graph. Jointly contributed by node matching and path matching, the graph matching output a set of updated edges on target graph as well as their weights, from which we can do further node embedding or whatever. The aim of this algorithm is to enrich structures of target graph by learning from source graph in predicting potential links across two graphs.
The CD2L-GM algorithm could be implemented into two classes corresponding to the node matching and path matching respectively.


[Suggestion] Add Bewitchment support for Vampires and Werewolves

I really like this mod, as I think it's really cool, but would it be possible to add support for Vampires and Werewolves from Bewitchment? Vampires can only drink blood, while Werewolves are entirely carnivorous, which conflicts a bit with this mod, and I don't think it can be fixed with just a datapack, sadly.

Okay never mind, Bewitchment managed to add compat for vampires and I was just never informed of this. Last I was told was that it was something you'd have to do. Sorry for that redundant request.