General tweaks and enhancements

Description
Please include a summary of changes and related issue (if any).
Related to issue #58 - list of changes included there.
Tests

[ ] Please provide evidence of your successful dbt run / dbt test here
[ ] Any comparison between prod and dev for any schema change

Running a full refresh on dev to check for any issues, will likely take overnight so results will be added later along with an incremental run and tests.
Checklist

[x] Follow dbt style guide
[x] Tag the person(s) responsible for reviewing proposed changes
[x] Notes to deployment, if a full-refresh is needed for any table

Notable model changes:

Updating the cluster_by to cluster_by = ['ingested_at::DATE', 'block_timestamp::DATE'] because we use ingested_at in the incremental, but end-users will use block_timestamp
Changing metrics models to be incremental

dbt run -m transactions+ --full-refresh
23:26:35  Found 12 models, 211 tests, 0 snapshots, 0 analyses, 605 macros, 0 operations, 0 seed files, 8 sources, 0 exposures, 0 metrics
23:26:36  Concurrency: 4 threads (target='default')
05:48:00  Finished running 9 incremental models in 22885.05s.
05:48:00  Completed with 1 error and 0 warnings:
05:48:00  Database Error in model receipts (models/core/receipts.sql)
05:48:00    000904 (42000): SQL compilation error: error line 39 at position 24
05:48:00    invalid identifier 'INGESTED_AT'
05:48:00    compiled SQL at target/run/near/models/core/receipts.sql
05:48:00  Done. PASS=8 WARN=0 ERROR=1 SKIP=0 TOTAL=9

Error in receipts was due to the change adding ingested_at to the cluster, but not ensuring ingested_at is in the model, but the rest were successful. Running transactions atm.
dbt test
...
06:38:31  Finished running 211 tests in 986.95s.
06:38:31
06:38:31  Completed with 1 error and 16 warnings:
06:38:31
06:38:31  Failure in test sequence_gaps_blocks_block_height (models/core/blocks.yml)
06:38:31    Got 49033 results, configured to fail if >25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/sequence_gaps_blocks_block_height.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_actions_events_addkey_allowance__NUMBER__None (models/core/actions_events_addkey.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/actions_events_addkey.yml/dbt_expectations_expect_column_8f50adaaf780e9e0a42b0bc88d3f9e15.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_block_challenges_result__ARRAY (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_b26f6cad7555e0bbe6539e3455a714b0.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_chunk_mask__ARRAY (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_f5de2e7a0293ed723a0f2cb113e5c66a.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_chunks__ARRAY (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_d727ac588a858a5dc0607c185d90ccaa.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_events__ARRAY (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_4aacf6552ce7e6fe93778fba407fcd1d.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_gas_price__NUMBER (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_6c3d2e8b80d20ed8288e4f2f42f13d0a.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_rent_paid__NUMBER (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_a59d45644327648d41be28e9e7fe4212.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_total_supply__NUMBER (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_0d811d8cb1289afb8900fa06703a1ac8.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_validator_proposals__ARRAY (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_da06b53cf5c51b32d24f8ef33b0d61e6.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_blocks_validator_reward__NUMBER (models/core/blocks.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/blocks.yml/dbt_expectations_expect_column_3e1d026a4643474b5a029c759753aebd.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_metrics_daily_gas_avg_gas_price__NUMBER (models/metrics/metrics_daily_gas.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/metrics/metrics_daily_gas.yml/dbt_expectations_expect_column_1805ea2dcc21d86bca56ece0878f4dd3.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_receipts_logs__ARRAY (models/core/receipts.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/receipts.yml/dbt_expectations_expect_column_4461347252ef2d2a125ed3bf890e0e99.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_receipts_proof__ARRAY (models/core/receipts.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/receipts.yml/dbt_expectations_expect_column_b8068db1b903cf306b28977476949ef6.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_receipts_receipt_outcome_id__ARRAY (models/core/receipts.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/receipts.yml/dbt_expectations_expect_column_67baaf912e6113673308d1337486535f.sql
06:38:31
06:38:31  Warning in test dbt_expectations_expect_column_values_to_be_in_type_list_transactions_tx_receipt__ARRAY (models/core/transactions.yml)
06:38:31    Got 1 result, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/transactions.yml/dbt_expectations_expect_column_2d7df3e7d6fa4f2eb982cae3c57f3571.sql
06:38:31
06:38:31  Warning in test tx_gaps_transactions_block_height__txn_hash__tx_count (models/core/transactions.yml)
06:38:31    Got 8 results, configured to warn if between 1 and 25000
06:38:31
06:38:31    compiled SQL at target/compiled/near/models/core/transactions.yml/tx_gaps_transactions_block_height__txn_hash__tx_count.sql
06:38:31
06:38:31  Done. PASS=194 WARN=16 ERROR=1 SKIP=0 TOTAL=211

Need to look at the trigger for these type expectation tests, for example the following only returns ARRAY, which is what we want to see but, as configured, the test is tripping a warning.
select distinct typeof(validator_proposals) from near.dev.blocks

No issues with receipts after column fix:
➜  near_dbt git:(hotfix-58) dbt run -m receipts --full-refresh
15:38:24  Running with dbt=1.1.0
15:38:25  Found 12 models, 211 tests, 0 snapshots, 0 analyses, 607 macros, 0 operations, 0 seed files, 8 sources, 0 exposures, 0 metrics
15:38:25
15:38:27  Concurrency: 4 threads (target='dev')
15:38:27
15:38:27  1 of 1 START incremental model DEV.receipts .................................... [RUN]
16:51:02  1 of 1 OK created incremental model DEV.receipts ............................... [SUCCESS 1 in 4354.52s]
16:51:02
16:51:02  Finished running 1 incremental model in 4357.32s.
16:51:02
16:51:02  Completed successfully
16:51:02
16:51:02  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Correcting the dockerfile back to fishtownanalytics

Fixed test issue, needed to correctly identify FLOAT instead of NUMBER, etc.
15:39:32  Finished running 211 tests in 66.85s.
15:39:32
15:39:32  Completed with 1 error and 1 warning:
15:39:32
15:39:32  Failure in test sequence_gaps_blocks_block_height (models/core/blocks.yml)
15:39:32    Got 49257 results, configured to fail if >25000
15:39:32
15:39:32    compiled SQL at target/compiled/near/models/core/blocks.yml/sequence_gaps_blocks_block_height.sql
15:39:32
15:39:32  Warning in test tx_gaps_transactions_block_height__txn_hash__tx_count (models/core/transactions.yml)
15:39:32    Got 8 results, configured to warn if between 1 and 25000
15:39:32
15:39:32    compiled SQL at target/compiled/near/models/core/transactions.yml/tx_gaps_transactions_block_height__txn_hash__tx_count.sql
15:39:32
15:39:32  Done. PASS=209 WARN=1 ERROR=1 SKIP=0 TOTAL=211


chore(main): release 1.1.3

:robot: I have created a release beep boop
1.1.3 (2024-10-08)
Bug Fixes

Update node version in release workflow (e0f3e4e)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.3
:sunflower:


Add documentation for new 1.8.1 features + add new option in config - update interval

add documentation
change default refresh interval from 60 s to 10 s
add option in config - Refresh Interval

Version increase missing in package-lock.json. Please update in line with package.json, as per process in CONTRIBUTING.md.

Feedback on the commit messages: Please make them more descriptive going forward so that reviewers know what was changed in a commit at a glance. A decent resource on the topic is: https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide.
The pattern "Update FILE" isn't very descriptive.

@jandersonhill, the next steps here are to merge the pull request and then run the respective release workflow from the tag v1.8.1 which will be created automatically once the PR is merged.

Done!

Nice! Congratulations on your first release using the new workflow(s). 👏

Thanks for all your help! Next on my list is to look into the npm token. The issues at home should be less demanding over the next few weeks, so things should run somewhat more smoothly now we're all used to the new workflow :-)


you can add an automatic update only to a specified div (in this case, it would be a checkout status div) using javascript.jquery

You can add an automatic update only to a specified div (in this case, it would be a checkout status div) using javascript.jquery
For the customer's order status to be updated, without having to update the order page

Use issues to report bugs, please post your suggestions/questions on the forums.


[v2.3] Alertmanger does not deploy

Version: Master (2.3) (5/3/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Try to set up an alert with a notifier

Result:

No errors in API/UI but in rancher logs alert manager will not deploy.

Other details that may be helpful:
Logs snippets:
2019/05/03 17:39:34 [WARNING] error updating ns p-jp2f9 status: Operation cannot be fulfilled on namespaces "p-jp2f9": the object has been modified; please apply your changes to the latest version and try again
2019/05/03 17:39:34 [WARNING] error updating ns c-665qj status: Operation cannot be fulfilled on namespaces "c-665qj": the object has been modified; please apply your changes to the latest version and try again
E0503 17:40:17.569330       6 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
2019/05/03 17:43:21 [ERROR] ProjectRoleTemplateBindingController p-jp2f9/creator-project-owner [cluster-prtb-sync] failed with : couldn't ensure roles: couldn't create role project-owner: clusterroles.rbac.authorization.k8s.io "project-owner" already exists
2019/05/03 17:43:21 [ERROR] ClusterRoleTemplateBindingController c-665qj/u-gco5pror65-admin [cluster-crtb-sync] failed with : couldn't ensure roles: couldn't create role cluster-owner: clusterroles.rbac.authorization.k8s.io "cluster-owner" already exists
2019/05/03 17:43:21 [ERROR] ProjectRoleTemplateBindingController p-bqg25/creator-project-owner [cluster-prtb-sync] failed with : couldn't create role project-owner-promoted: clusterroles.rbac.authorization.k8s.io "project-owner-promoted" already exists
2019/05/03 17:43:21 [ERROR] ClusterAlertRuleController c-665qj/scheduler-system-service [cluster-alert-rule-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; ple
ase apply your changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertRuleController c-665qj/controllermanager-system-service [cluster-alert-rule-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modif
ied; please apply your changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertRuleController c-665qj/db-over-size [cluster-alert-rule-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; please apply yo
ur changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertRuleController c-665qj/deployment-event-alert [cluster-alert-rule-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; pleas
e apply your changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertRuleController c-665qj/no-leader [cluster-alert-rule-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; please apply your
changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertGroupController c-665qj/etcd-alert [cluster-alert-group-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; please apply yo
ur changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertGroupController c-665qj/event-alert [cluster-alert-group-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; please apply y
our changes to the latest version and try again
2019/05/03 17:43:21 [ERROR] ClusterAlertGroupController c-665qj/kube-components-alert [cluster-alert-group-deployer] failed with : update cluster c-665qj failed, Operation cannot be fulfilled on clusters.management.cattle.io "c-665qj": the object has been modified; plea
se apply your changes to the latest version and try again

2019/05/03 18:31:23 [ERROR] ClusterAlertGroupController c-665qj/cag-fnmnh [cluster-alert-group-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-group-controller] failed
 with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:31:52 [ERROR] ClusterAlertRuleController c-665qj/car-6ff8s [cluster-alert-rule-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-rule-controller] failed wi
th : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:32:09 [ERROR] ProjectAlertRuleController p-f2lgt/less-than-half-workload-available [project-alert-rule-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [project-alert-ru
le-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:32:09 [ERROR] ProjectAlertRuleController p-f2lgt/memory-close-to-resource-limited [project-alert-rule-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [project-alert-rul
e-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:32:09 [ERROR] ProjectAlertGroupController p-f2lgt/projectalert-workload-alert [project-alert-group-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [project-alert-group-
controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:34:29 [ERROR] Failed to send alert: Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:34:29 [ERROR] Failed to send alert: Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:34:29 [ERROR] Failed to send alert: Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:34:29 [ERROR] Failed to send alert: Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found
2019/05/03 18:34:29 [ERROR] Failed to send alert: Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found

Environment information
Single-node rancher but HA is also affected. This was working a few days ago such as in rc2? or rc3?

https://github.com/rancher/rancher/issues/19970

Version: Master (v2.3) (5/6/19)
Alertmanager is now deploying; we can successfully get alerts (notifications) now.


Integration with existing alarm

Would be nice to have the option to forward arm states to a action for example if alarmo arms the action is to arm the main house alarm that’s connected to HA using this https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/envisalink.markdown.
So to shorten it off it would me nice to be able to trigger the Mail alarm also.
#feature request

Can't you do this with an automation?

Can't you do this with an automation?

This seems quite feasible.
Alarmo already will get the option for creating separate entities for each area, there will be a ‘master’ entity on top to link them.

This seems quite feasible.
Alarmo already will get the option for creating separate entities for each area, there will be a ‘master’ entity on top to link them.

Yes it would be possible through a automation but since Alarmo is so user friendly it would be nice to have actions on arm/disarm as well in the Alarmo GUI.

Yes it would be possible through a automation but since Alarmo is so user friendly it would be nice to have actions on arm/disarm as well in the Alarmo GUI.

You will be knee deep in features :D

You will be knee deep in features :D

Handled on a first come, first serve basis 😉

Handled on a first come, first serve basis 😉


Radio

can make custom radio channel?

Use the RADIO_URL env variable

How does the RADIO env work?


fix: Adjust . typing auto indentation

Fixes https://github.com/rust-analyzer/rust-analyzer/issues/629
bors r+

Woah, I remember when we had three-digit issue numbers.

Turns out there are only 6(5 with this one gone) open issues with a 3 digit number left.


open distro  security plugin not working on 32-bit windows 8 machine

When I started elastic search with security plugin installed in my 32-bit windows machine, elasticsearch didnt worked but when i removed the plugin and again started elasticsearch it was working well. Help needed

Please provide logs, exceptions and error messages.

I solved the problem by adding
transport.host: localhost
transport.tcp.port: 9300 to the yml
Thankyou

@


hyprexpo: can't load the plugin

when i try to load the plugin with hyprpm it says everything was ok but when doing hyprctl plugin list says no plugins loaded

Logs i found usefull:
[LOG] [functionhook] assembler returned:

[LOG] [functionhook] assembler returned:
/tmp/hypr/.hookcode.asm: Assembler messages:
/tmp/hypr/.hookcode.asm:7: Error: operand type mismatch for `movabs'

[ERR] [functionhook] failed, unsupported asm / failed assembling:
push %r12
push %rbp
mov %rsi, %rbp
push %rbx
mov %rdi, %rbx
sub $0x60, %rsp
movzx 0x291fbb(%rip), %eax

[ERR]  [PluginSystem] Plugin /home/loseardes77/.local/share/hyprpm/hyprland-plugins/hyprexpo.so (Handle 1f09290) crashed in init. Unloading.
[LOG]  [PluginSystem] Plugin  unloaded.

I'm on latest git version of hyprland
i have tryed to compile separated and load with hyprctl but i get the same logs and this error message on hyprctl:
error in loading plugin, last error: Plugin /home/loseardes77/Repos/hyprland-plugins/hyprexpo/hyprexpo.so could not be loaded: plugin crashed/threw in main: [he] Failed initializing hooks

https://github.com/hyprwm/Hyprland/blob/main/CMakeLists.txt#L95-L95
try compiling hyprland with -fno-pie -fno-pic

https://github.com/hyprwm/Hyprland/blob/main/CMakeLists.txt#L95-L95
try compiling hyprland with -no-pie -fno-pic

I get the exact same logs

I thought this had to be with my pc.
So is a bug with the hook system?

yah

Still can't see why it works for other people then but i believe in you to fix it <3

patch.txt
try this for hyprland

Do i need to refresh the Hyprland session?

refresh? it's a patch, recompile it with it

I mean after compiling installing exit hyprland and re enter or only the Headers is what matters?

yea re enter its a code patch

[LOG] [functionhook] assembler returned:

[LOG] [functionhook] assembler returned:
/tmp/hypr/.hookcode.asm: Assembler messages:
/tmp/hypr/.hookcode.asm:7: Error: no such instruction: `movz -0x7f6d71c27235(%rip),%eax'

[ERR] [functionhook] failed, unsupported asm / failed assembling:
push %r12
push %rbp
mov %rsi, %rbp
push %rbx
mov %rdi, %rbx
sub $0x60, %rsp
movzx 0x29230b(%rip), %eax

[ERR]  [PluginSystem] Plugin /home/loseardes77/Repos/hyprland-plugins/hyprexpo/hyprexpo.so (Handle 21f84e0) crashed in init. Unloading.
[LOG]  [PluginSystem] Plugin  unloaded.

 Gimme sec

patch.txt
fixed

the patch is only for the HookSystem.cpp and hpp right?

Ok now works fine.
Thanks you!

well wait for me to commit it lol

done, enjoy

I still seem to be getting the same problem


Fixed typo in method name

Fixed typo in method name. From #substration: to #substraction:

@NicolasAnquetil


rye build should use python version from .python-version

Steps to Reproduce
Running rye build uses whatever version of python is configured for rye's global installation.
Expected Result
Rye should use the python version specified in the .python-version file.
Actual Result
$ rye --version
rye 0.36.0
commit: 0.36.0 (12c024c7c 2024-07-07)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

$ cat .python-version
3.11

$ python  --version
Python 3.11.9

$ rye build --wheel -v
building myproject-py
* Creating isolated environment: venv+uv...
* Using external uv from /home/myname/.rye/uv/0.2.22/uv
* Installing packages in isolated environment:
  - hatchling
> /home/myname/.rye/uv/0.2.22/uv pip install hatchling
< Resolved 5 packages in 65ms
< Installed 5 packages in 4ms
<  + hatchling==1.25.0
<  + packaging==24.1
<  + pathspec==0.12.1
<  + pluggy==1.5.0
<  + trove-classifiers==2024.7.2
* Getting build dependencies for wheel...
* Installing packages in isolated environment:
  - hatch-mypyc
> /home/myname/.rye/uv/0.2.22/uv pip install hatch-mypyc
< Resolved 10 packages in 69ms
< Installed 5 packages in 66ms
<  + hatch-mypyc==0.16.0
<  + mypy==1.11.0
<  + mypy-extensions==1.0.0
<  + setuptools==71.0.4
<  + typing-extensions==4.12.2
* Building wheel...
Successfully built myproject_py-0.0.1-cp312-cp312-linux_x86_64.whl

Note the cp312 tag instead of cp311.
Version Info
rye 0.36.0
commit: 0.36.0 (12c024c7c 2024-07-07)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Other Info
I tested the following patch, which "fixes" the issue, but requires adding build as a dev-dependency.
diff --git a/rye/src/cli/build.rs b/rye/src/cli/build.rs
index 324f76b..d98657d 100644
--- a/rye/src/cli/build.rs
+++ b/rye/src/cli/build.rs
@@ -83,7 +83,7 @@ pub fn execute(cmd: Args) -> Result<(), Error> {
             style(project.normalized_name()?).cyan()
         );

-        let mut build_cmd = Command::new(get_venv_python_bin(&self_venv));
+        let mut build_cmd = Command::new(get_venv_python_bin(&project.venv_path()));
         build_cmd
             .arg("-mbuild")
             .env("NO_COLOR", "1")

Related: #1152

Yeah this looks off. I'll take a look.

Yeah this is an interesting problem. We depend on build so we can't use the user's environment.

I think we need to create an ephemeral virtualenv with uv.

I believe I have a fix here: https://github.com/astral-sh/rye/pull/1250


go test fails due to redefinition of sliceToStylesheetStr(), which now takes a directory parameter

Fixed. Don't remember when.


GeoObject textures overlap when they are very close

Original thread: http://beyondar.com/node/98

Was there any advance or solution for this bug?, this is extremely important for augmented reality geo based.


remove "Global Consent Cookie Sandbox"

Still some instances of project name from older experimental versions.

Thanks for pointing that out. All "cookie sandbox" has been replaced with "manager".


make installer ssh keepalive much longer

5 seconds works just fine on my powerful desktop but I've observed several failures on my much less powerful OSX laptop. At two minutes I don't see this.

This change is

👍

IIUC this should help when the network is flaky too 👏


Set a limit for the max key/value size

We will need to use some logic within our Deque + StringBuilder buffer pair to check if something is too big.

Also, if we parse a token and its size is greater than the limit, we can discard it as well.
At the end, when we exit after processing all full commands (and parsing tokens), if the buffer's size is greater than the limit, it means we have a bunch of junk input we can discard, and then we discard. T

There is an edge case to handle. We know based on the token parsing logic there will be no more \r\n in the buffer, but what if we get two separate messages sent like: <over_limit>\r ... \n<valid_tokens>.  So if the last character is \r, clear everything except it.

If we have <over_limit>\r ... <other...> we will know we can discard later if a \r\n comes. But what if the client doesn't follow the protocol and keeps on sending data over the limit with no delim? Doing this optimization will save us memory space but clearing out unused memory (AND ITS EASY TO IMPLEMENT).

Can we set a max size for our string buffer too? Thing about 2 * max_entry_size
Key and value can have the same size limit for now

Previous discussion, ignore. Implementation has changed.
We will need to use some logic within our Deque + StringBuilder buffer pair to check if something is too big.

Also, if we parse a token and its size is greater than the limit, we can discard it as well.
At the end, when we exit after processing all full commands (and parsing tokens), if the buffer's size is greater than the limit, it means we have a bunch of junk input we can discard, and then we discard. T

There is an edge case to handle. We know based on the token parsing logic there will be no more \r\n in the buffer, but what if we get two separate messages sent like: <over_limit>\r ... \n<valid_tokens>.  So if the last character is \r, clear everything except it.

If we have <over_limit>\r ... <other...> we will know we can discard later if a \r\n comes. But what if the client doesn't follow the protocol and keeps on sending data over the limit with no delim? Doing this optimization will save us memory space but clearing out unused memory (AND ITS EASY TO IMPLEMENT).

Can we set a max size for our string buffer too? Thing about 2 * max_entry_size
Key and value can have the same size limit for now


feature/Introduce Menu-Items instead of Strings

Signed-off-by: Björn Müller<EMAIL_ADDRESS>Introduce menu items (displayName, urlFragment) instead of strings

[x] Ensure that you followed http://eclipse.github.io/winery/dev/ToolChain#github---prepare-pull-request. Especially, we require a single commit
[x] Ensure that the commit message is a good commit message
[x] Ensure to use auto format in all files
[x] Ensure that you appear in NOTICE at Copyright Holders
[ ] Tests created for changes
[ ] Documentation updated (if needed)
[ ] Screenshots added (for UI changes)

Can one of the admins verify this patch?


Riya/removeskulist

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:
We had initially implemented an API to return skus available for the Redis Enterprise service. After being informed that the right way to do this is by implementing the SKU contract where ARM returns the skus after contacting the service RP, we recently rolled out changes to support that. We do not need to expose the previous API anymore. This API was not usable by customers since we had not rolled out the manifest changes for the previous implementation so this will not have customer impact.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Breaking changes new intake created: https://msazure.visualstudio.com/b32aa71e-8ed2-41b2-9d77-5bc261222004/_workitems/edit/25626928

Hi @msyyc, I am requesting a breaking changes review for CI-BreakingChange-Python-Track2. Please let me know if there are questions or some fixes more to do from my end.

@rkmanda Hi, I had a question on how the public docs will be updated for ARM internal API (https://armwiki.azurewebsites.net/api_contracts/SKUContract.html?tabs=resource-type-level). The document mentions that individual RPs shouldn't specify the API in their spec. Is there anything from our end to onboard the documentation for this API? Similar to how Microsoft.Compute has: https://learn.microsoft.com/en-us/rest/api/compute/resource-skus/list?tabs=HTTP

/pr RequestMerge


Remove trailing whitespaces from code block in delete-foreign-key-rel…

…ationships.md

@Saibamen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @Saibamen for submitting this PR. Your commit will be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor.
#sign-off


Provider rehydrate true breaks server-side rendering

Type: Bug

Packages
Version

fela-dom
6.0.5

Description
Provider with rehydrate prop set to true possibly breaks server-side rendering. Needs probably more investigation, details, minimal example.
ERROR in TypeError: document.querySelectorAll is not a function

What's the rehydrate prop? Can't find any documentation on it

It's auto-enabled and won't be required at all soon (rehydration now knows if styles can be rehydrated or not).
Also trying with the latest example-react, I can't reproduce this as we have a hasDOM() check to prevent rehydration calls on the server.

Also trying with the latest example-react, I can't reproduce this as we have a hasDOM() check to prevent rehydration calls on the server.

In my project, I am actually doing some mocks in SSR (facepalm):
globals: {
  document: {},
  window: { location: { hash: { substr: () => '' } } }
}

which actually passes hasDom test. How about more robust check:
const hasDom = !!(
  typeof window !== 'undefined' &&
  window.document &&
  window.document.createElement
);

Oh thats it! Feel free to send a PR!


Summary Vs Finding confidence level mismatch - PEBKAC ?

Hi @jeremylong
I find there is a Confidence mismatch between the "findings summary list" and the "individual findings"?
For example; in the report image below, we see in the summary forsocket.io-parser:4.0.4having no confidence value :

..then going to the individual finding, the confidence is “Highest” ???

**Is this a parameter setting, an error, or something else? eg user error 🙂 **
Also, this tool is fantastic, and I really appreciate the effort you make with it. 🏅
Warm regards

Looks like a bug.

OK cool. I did not want to assume.
FYI - It was from a docker container today. For the sake of the report I am currently working on, Can I have any confidence in either Summary OR Finding confidence level?

First - the confidence is just an estimate as to whether the correct CPE was identified and has nothing to do with exploitability. The confidence in both the summary table and the one listed next to each CPE should match.


[WIP] Update CI and add version command

What does this do / why do we need it?

[x] Update travis.yml to release binaries
[x] Add version command
[x] Update docs to reflect changes
[ ] Update travis.yml to include brew bump-formula-pr
[ ] Fix to use golang/dep credentials and some commands i changed to test on my repo.

What should your reviewer look out for in this PR?
Do you need help or clarification on anything?

Is it enough to write commands in travis file or you prefer Makefile/bash script etc.?
Travis need auth token to release binaries this can be supplied with environment variable set from travis UI or can be set in yml with secure token as described in travis docs.
Windows and *nix are tested on different systems, will it be a problem to release from travis without waiting windows finish?

Which issue(s) does this PR fix?

fixes #209
fixes #957
fixes #949

Is it enough to write commands in travis file or you prefer Makefile/bash script etc.?

i'd prefer to have a bash script, so that we can easily run it from elsewhere if needed. can put it under hack/.

here's a block of YAML i generated for .travis.yml - i give it to you, to integrate into this PR :)
deploy:
  provider: releases
  api_key:
    secure: fL9GX11J3JLizEBTPZHN32wuAT91eAJsGl0kjlAdIc6Lb/9UCe1XZGgFnpQFN4qo/S+omhHBDbM6Ty1xhNy7xmjDecpQGDU8Rmap9Oll0TuxqMigG+njOuPp5VUYPofPP0PGKdxAcYg+KaFM7x0o2rK+qA046NHwo2gH1BbE+bn55TZglEajEfc8j9iX4jt96KC7zlu+WiKArLmfUtlrI8m8ZYgbYcvFmlYjeCiEqlNhvNL59ejug9Rl0PLtPbamqVXkGLafYtekgPCb4WSxBiCt8pq5Rb5svk9YcdXpiaWQhZjMPAuKN6BrmN2lw1PiXzADUG5fjvNc8eo2HY70GD2utU9cAsY8VIafhoH5n6uM1WI8MHwDfd7P1PiQA3ZGQ8CPwk4q/8HSfQU9ap7vZgSF63pTIbtlviyIG67orOJE9PWWncl9olYM946UylZu6m3hWI/rmJxOeJ1UJjym/3GNPMRfKubaGhV/TyRdM0bKX4M0cXHU6k/ESVFupGXdKRt4RpvkD4/1Km6b2OShW6PNI+ifFspnJr7obkI7dm7ubySdnNz4lMv9WWymxRpMVc8hUAhuoDvXeZJq7pSnkjBEWDxIRoTkA93CU3/Rf7MFYCJMnGSqjcxWUpIfCAk2/r4BqL9NQnqBvvVt+MYi64QaD5n7ZF3dVbr6HZ2zjSU=
  file: ''
  on:
    repo: golang/dep

Windows and *nix are tested on different systems, will it be a problem to release from travis without waiting windows finish?

i don't think so. we're not going to tag a release on a commit without it having passed all of CI anyway, so by the time the actual tag push happens, we'll already be sure that windows is 👍 .

weee!

a8802c0 master

department

dep


cargo publish of a [lib] fails when dependencies exist newer than my toolchain version

Problem
Captured from https://internals.rust-lang.org/t/pre-rfc-msrv-aware-resolver/19871/65?u=epage

I had a very unpleasant experience:
I work on old version of Rust, usually I develop my library with dependencies by:
cargo +nightly -Z minimal-versions update

But when I publish my library by cargo publish, I got:
Caused by:
 package `home v0.5.9` cannot be built because it requires rustc 1.70.0 or newer, while the currently active rustc version is 1.65.0

Is there cargo publish update dependencies by -Z minimal-versions, or it's best to update the dependent version based on the rust-version.

Proposed Solution
No response
Notes
No response

We talked about this in today's team meeting.
Though we changed out guidance on committing Cargo.lock based on crate kind (bin/lib), we still choose whether to include the Cargo.lock based on if its a bin or example.  Without the Cargo.lock being included, we generate a new one with the verify step which uses the latest dependencies.
We have rust-lang/rfcs#3537 but that excludes "ephemeral" workspaces which is targeted at cargo install but I believe it also applies to cargo publish (need to verify that).
Options

Include Cargo.lock as a statement of what was verified, fixing this is a side effect

Mostly meaningless but doesn't take up much space

Prefer verifying with existing lockfile
Prefer verifying with latest and tell the user to upgrade (ie "do dev on latest even if you support older")
Prefer verifying with latest but allow overriding with MSRV aware resolver
Extend the MSRV-aware resolver RFC change to cargo publish (which we'll need to distinguish from cargo install as they are both ephemeral)

ehuss pointed out that the verify step using the latest dependencies, rather than your lockfile, was very intentional to ensure you verified what your dependents are going to run.
As the main point of discussion was whether to include this in the RFC or if we could do a quick fix, we decided to shift the conversation to this issue.

ehuss pointed out that the verify step using the latest dependencies, rather than your lockfile, was very intentional to ensure you verified what your dependents are going to run.

With an MSRV-aware resolver, we will move from dependents using "latest" (all dependent on what was already in their lockfile) to multiple points within their version timeline.  For myself, the earlier points in that timeline are what are more likely to break you then the later points.
For myself, I feel like most cargo publish verification is too late and should be a very loose safety catch.  Currently, we don't support packaging and then publishing a workspace, so packaging errors in a cargo publish step puts you in an awkward state.  Even if we have workspace support, your release process usually includes other steps like updating changelogs and versions, etc that need to be undone.

the verify step using the latest dependencies, rather than your lockfile, was very intentional to ensure you verified what your dependents are going to run.

This isn't the current behavior, if you have a crate where the lockfile is included in the published package, that lockfile will be used during the verify step.

With #14815, I think this can be closed.


[WIP] mixer_module: limit actuator_control callbacks

don't register additional callbacks if actuator_controls_0 or actuator_controls_1 are already registered
fixes #15043

Untested.

I'm wondering about a worst case scenario where this wouldn't be sufficient. For example if all sensors failed and we wanted to activate a parachute (on PWM).
How about a backup scheduled run in 20 ms (50 Hz) that we kick forward each iteration?


Downloading video and audio files????

Ok, I downloaded youtube-dl, created and tested a batch file to download video files from my YouTube playlists.  Next, I wanted to extract audio from the video files in my playlist. So I downloaded FFmpeg.  I created a batch file to extract the audio from the files.  Tested the batch file and it worked.  Went back to run the batch file to download the videos and it now converts them to audio mp3 format?? Here is what I have:
Using: youtube-dl 2017.01.14
FFmpeg and youtube-dl in system variable path
Audio command line:
youtube-dl -i -o "C:\YouTube\Audio\%%(playlist)s/%%(playlist_index)s - %%(title)s.%%(ext)s" --batch-file "C:\Youtubedl\Batch Files\Playlists.txt" --extract-audio --audio-format mp3
Video Command Line:
youtube-dl -i -o "C:\YouTube\Video\%%(playlist)s/%%(playlist_index)s - %%(title)s.%%(ext)s" --batch-file "C:\Youtubedl\Batch Files\Playlists.txt"
What am I missing?  Download videos worked fine before downloading FFmpeg?
Thanks for the help!

Carefully read new issue template and provide all requested information.


Fixed #23967 -- Added formats for Greek

For ticket #23967 (https://code.djangoproject.com/ticket/23967#ticket)

I can confirm too that the correct format for greek locale is "%d/%m/%Y. That being said, I haven't actually tested the patch, but it seems be correct.
The only thing I might disagree with is the thousand separator. AFAIK there is no standard convention for this and it might be better idea not to specify it (i.e. to leave it as it is).

@pmav99 Hello! I don't think that we can leave the thousand seperator as it is because the default (from https://github.com/spapas/django/blob/ffb3a065a4d60612f85f9474cb28b478b7e2760f/django/conf/global_settings.py#L422) is THOUSAND_SEPARATOR = ',' which for Greek (and other EU countries) is used as a decimal seprator.

Could you squash the commits and add release notes for 1.7.3 similar to 1ac32e76ac14323eef70142f57b8d7a3a192a829? I've updated the title of this PR to a commit message format that follows our guidelines. Thanks.

Done on #3875.


Russian Qbot

All the translations of Qbot, but in russian. How do I feel after working on this? My head hurts.

This will need to be updated to 5.1.


Again: ZB_ESP_MAC: MAC RX buffer is full! (TZ-218)

The Rx buffer overflow issue should have been fixed in the latest  esp-zigee-sdk version. Could you please update it and try again?
If the problem still persists, please feel free to contact us with the log information that is helpful for us to fix problem.
Originally posted by @xieqinan in https://github.com/espressif/esp-zigbee-sdk/issues/53#issuecomment-1657770312
Thanks a lot but its not solved the issue.
Im trying to pair about 20 Zigbee devices to the network at the same time. And it always leads to "MAC RX buffer is full!" error. Sometimes it even leads to cycle errors waterfall like this:
(244254) ZB_ESP_MAC: MAC RX buffer is full!
(244259) ZB_ESP_MAC: MAC RX buffer is full!
...
(2757175) ZB_ESP_MAC: MAC RX buffer is full!
(2757180) ZB_ESP_MAC: MAC RX buffer is full!
(2757185) ZB_ESP_MAC: MAC RX buffer is full!
I saw you increased ZB_MAC_RX_QUEUE_CAP constant from 10 to 20 but i think it should be much bigger size like 128 or 256. Also ZB_MAC_QUEUE_SIZE seems to be increased according the code comments.

Hi,
The issue may not necessarily be related to the ZB_MAC_QUEUE_SIZE. Could you please provide information about the specific function or request that leads to this issue? Sharing the reproducible code here would be beneficial for fixing.

You can use "esp_zigbee_gateway" example. Just try to pair at least 10 Zigbee devices at the same time.

Thanks for your information, I will try it.

You can use "esp_zigbee_gateway" example. Just try to pair at least 10 Zigbee devices at the same time.

Do you have any other operations you performed on this example? I attempted to reproduce the issue using the method you provided, but it seems to be functioning correctly on my end.

Here i did use esp_zigbee_gateway example, set Wifi params, set MAX_CHILDREN to 128 and try to pair about 15 devices at the same time. My end devices are trying to pair new network at the startup and i just power it on and wait.
`art: Pro cpu up.
W (364) clk: esp_perip_clk_init() has not been implemented yet
I (371) cpu_start: Pro cpu start user code
I (371) cpu_start: cpu freq: 160000000 Hz
I (371) cpu_start: Application information:
I (374) cpu_start: Project name:     esp_zigbee_gateway
I (380) cpu_start: App version:      1
I (384) cpu_start: Compile time:     Aug  2 2023 10:29:02
I (390) cpu_start: ELF file SHA256:  8731a1c93d095343...
I (396) cpu_start: ESP-IDF:          v5.1
I (401) cpu_start: Min chip rev:     v0.0
I (405) cpu_start: Max chip rev:     v0.99
I (410) cpu_start: Chip rev:         v0.0
I (415) heap_init: Initializing. RAM available for dynamic allocation:
I (422) heap_init: At 4081FFA0 len 0005C670 (369 KiB): D/IRAM
I (429) heap_init: At 4087C610 len 00002F54 (11 KiB): STACK/DIRAM
I (435) heap_init: At 50000010 len 00003FF0 (15 KiB): RTCRAM
I (443) spi_flash: detected chip: generic
I (446) spi_flash: flash io: dio
I (451) sleep: Configure to isolate all GPIO pins in sleep state
I (457) sleep: Enable automatic switching of GPIO sleep configuration
I (464) coexist: coex firmware version: ebddf30
I (470) coexist: coexist rom version 5b8dcfa
I (475) app_start: Starting scheduler on CPU0
I (479) main_task: Started on CPU0
I (479) main_task: Calling app_main()
I (489) example_connect: Start example_connect.
I (489) pp: pp rom version: 5b8dcfa
I (489) net80211: net80211 rom version: 5b8dcfa
I (509) wifi:wifi driver task: 4087f264, prio:23, stack:6656, core=0
I (509) wifi:wifi firmware version: b2f1f86
I (509) wifi:wifi certification version: v7.0
I (509) wifi:config NVS flash: enabled
I (519) wifi:config nano formating: disabled
I (519) wifi:mac_version:HAL_MAC_ESP32AX_761,ut_version:N
I (519) wifi:Init data frame dynamic rx buffer num: 32
I (529) wifi:Init management frame dynamic rx buffer num: 32
I (529) wifi:Init management short buffer num: 32
I (539) wifi:Init dynamic tx buffer num: 32
I (539) wifi:Init static tx FG buffer num: 2
I (549) wifi:Init static rx buffer size: 1700
I (549) wifi:Init static rx buffer num: 10
I (559) wifi:Init dynamic rx buffer num: 32
I (559) wifi_init: rx ba win: 6
I (559) wifi_init: tcpip mbox: 32
I (569) wifi_init: udp mbox: 6
I (569) wifi_init: tcp mbox: 6
I (569) wifi_init: tcp tx win: 5744
I (579) wifi_init: tcp rx win: 5744
I (579) wifi_init: tcp mss: 1440
I (589) wifi_init: WiFi IRAM OP enabled
I (589) wifi_init: WiFi RX IRAM OP enabled
I (599) phy_init: phy_version 202,b4b3263,May 17 2023,20:14:14
W (639) esp_adapter: wifi_reset_mac_wrapper() has not been implemented yet
W (639) wifi:(bf)761:0x600a7cac:0x01b4b4b0
W (639) wifi:(agc)0x600a7128:0xd2153800, min.avgNF:0xce->0xd2(dB), RCalCount:0x153, min.RRssi:0x800(-128.00)
W (649) wifi:(TB)WDEV_PWR_TB_MCS0:19
W (659) wifi:(TB)WDEV_PWR_TB_MCS1:19
W (659) wifi:(TB)WDEV_PWR_TB_MCS2:19
W (659) wifi:(TB)WDEV_PWR_TB_MCS3:19
W (669) wifi:(TB)WDEV_PWR_TB_MCS4:19
W (669) wifi:(TB)WDEV_PWR_TB_MCS5:19
W (669) wifi:(TB)WDEV_PWR_TB_MCS6:18
W (679) wifi:(TB)WDEV_PWR_TB_MCS7:18
W (679) wifi:(TB)WDEV_PWR_TB_MCS8:17
W (679) wifi:(TB)WDEV_PWR_TB_MCS9:15
W (689) wifi:(TB)WDEV_PWR_TB_MCS10:15
W (689) wifi:(TB)WDEV_PWR_TB_MCS11:15
I (689) wifi:11ax coex: WDEVAX_PTI0(0x55777555), WDEVAX_PTI1(0x00003377).
I (699) wifi:mode : sta (60:55:f9:f6:f9:90)
I (699) wifi:enable tsf
I (709) example_connect: Connecting to Wifi...
I (709) example_connect: Waiting for IP(s)
I (3119) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
I (3119) wifi:(connect)dot11_authmode:0x3, pairwise_cipher:0x3, group_cipher:0x3
I (3699) wifi:state: init -> auth (b0)
I (3699) wifi:state: auth -> assoc (0)
I (3709) wifi:state: assoc -> run (10)
I (3709) wifi:(trc)phytype:CBW20-SGI, snr:58, maxRate:144, highestRateIdx:0
I (3709) wifi:(trc)rate(S-MCS7, schedIdx:0), ampdu(rate:S-MCS7, schedIdx(0, stop:8)), snr:58, ampduState:wait operational
I (3719) wifi:ifidx:0, rssi:-38, nf:-96, phytype(0x3, CBW20-SGI), phymode(0x3, 11bgn), max_rate:1440, he:0
I (3729) wifi:max ampdu length exponent:3(65535 bytes), mmss:5(4 us)
W (3729) wifi:[ADDBA]rx delba, code:39, delete tid:0
I (3739) wifi:(extcap)mbssid:0, enhanced_mbssid_advertise:0, complete_nontxbssid_profiles:0
I (3749) wifi:connected with Wifi, aid = 2, channel 11, BW20, bssid = 70:a7:41:d8:4a:c5
I (3749) wifi:cipher(pairwise:0x3, group:0x3), pmf:0, security:WPA2-PSK, phy:11bgn, rssi:-38
I (3759) wifi:pm start, type: 1, itwt_start:0
I (3769) wifi:pm start, type:1, aid:0x2, trans-BSSID:70:a7:41:d8:4a:c5, BSSID[5]:0xc5, mbssid(max-indicator:0, index:0), he:0
I (3779) wifi:set rx beacon pti, rx_bcn_pti: 10, bcn_timeout: 25000, mt_pti: 10, mt_time: 10000
I (3789) wifi:[ADDBA]TX addba request, tid:0, dialogtoken:1, bufsize:64, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x0)
I (3799) wifi:[ADDBA]TX addba request, tid:7, dialogtoken:2, bufsize:64, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x30)
I (3809) wifi:[ADDBA]TX addba request, tid:5, dialogtoken:3, bufsize:64, A-MSDU:0(not supported), policy:1(IMR), ssn:0(0x0)
I (3819) wifi:BcnInt:102400, DTIM:1
I (3819) wifi:[ADDBA]RX addba response, status:0, tid:0/tb:1(0xa1), bufsize:64, batimeout:0, txa_wnd:64
I (3829) wifi:[ADDBA]RX addba response, status:0, tid:7/tb:1(0xa1), bufsize:64, batimeout:0, txa_wnd:64
I (3839) wifi:[ADDBA]RX addba response, status:0, tid:5/tb:1(0xa1), bufsize:64, batimeout:0, txa_wnd:64
W (3859) wifi:idx:0, ifx:0, tid:6, TAHI:0x100c54a, TALO:0xd841a770, (ssn:1, win:64, cur_ssn:1), CONF:0xc0006005
I (4849) esp_netif_handlers: example_netif_sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (4849) example_connect: Got IPv4 event: Interface "example_netif_sta" address: <IP_ADDRESS>
I (5489) example_connect: Got IPv6 event: Interface "example_netif_sta" address: fe80:0000:0000:0000:6255:f9ff:fef6:f990, type: ESP_IP6_ADDR_IS_LINK_LOCAL
I (5489) example_common: Connected to example_netif_sta
I (5499) example_common: - IPv4 address: <IP_ADDRESS>,
I (5499) example_common: - IPv6 address: fe80:0000:0000:0000:6255:f9ff:fef6:f990, type: ESP_IP6_ADDR_IS_LINK_LOCAL
I (5509) wifi:Set ps type: 1
I (5529) main_task: Returned from app_main()
I (5539) ESP_ZB_GATEWAY: ZDO signal: 23, status: -1
I (5539) ESP_ZB_GATEWAY: Zigbee stack initialized
I (5539) ESP_ZB_GATEWAY: ZDO signal: 54, status: 0
I (5539) ESP_ZB_GATEWAY: Start network formation
I (5549) ESP_ZB_GATEWAY: Formed network successfully (ieee_address: 90:f9:f6:00:00:f9:55:60, PAN ID: 0x2acd, Channel:13)
I (6009) ESP_ZB_GATEWAY: ZDO signal: 54, status: 0
I (6009) ESP_ZB_GATEWAY: Network steering started
W (8919) wifi:idx:1, ifx:0, tid:0, TAHI:0x100c54a, TALO:0xd841a770, (ssn:0, win:64, cur_ssn:0), CONF:0xc0000005
I (21259) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21299) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21319) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21369) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21379) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21379) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21409) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21419) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21439) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
I (21469) ESP_ZB_GATEWAY: ZDO signal: 18, status: 0
W (21929) ZB_ESP_MAC: MAC RX buffer is full!
W (21939) ZB_ESP_MAC: MAC RX buffer is full!
W (21939) ZB_ESP_MAC: MAC RX buffer is full!
W (21949) ZB_ESP_MAC: MAC RX buffer is full!
W (21949) ZB_ESP_MAC: MAC RX buffer is full!
W (21949) ZB_ESP_MAC: MAC RX buffer is full!
W (21959) ZB_ESP_MAC: MAC RX buffer is full!
W (21959) ZB_ESP_MAC: MAC RX buffer is full!
W (21959) ZB_ESP_MAC: MAC RX buffer is full!
W (21959) ZB_ESP_MAC: MAC RX buffer is full!
W (21969) ZB_ESP_MAC: MAC RX buffer is full!
W (21969) ZB_ESP_MAC: MAC RX buffer is full!
W (21979) ZB_ESP_MAC: MAC RX buffer is full!
`
(its just looping)
I use ESP32-C6-DevKitC-1 V1.1

It using IDF Component manager:
idf_component.yml
dependencies:
  espressif/esp-zboss-lib: ">=0.5.4"
  espressif/esp-zigbee-lib: ">=0.7.4"
  ## Required IDF version
  idf:
    version: ">=5.1.0"

If it could help i can record network activity dump with TI Packet Sniffer

Hi,

Here i did use esp_zigbee_gateway example, set Wifi params, set MAX_CHILDREN to 128 and try to pair about 15 devices at the same time. My end devices are trying to pair new network at the startup and i just power it on and wait.

I attempted to reproduce the bug using the method you provided, but it seems there is some differences between my results and yours.

W (20480) ZB_ESP_MAC: MAC RX buffer is full!
W (20480) ZB_ESP_MAC: MAC RX buffer is full!
W (20480) ZB_ESP_MAC: MAC RX buffer is full!
W (20490) ZB_ESP_MAC: MAC RX buffer is full!
I (20500) ESP_ZB_GATEWAY: New device commissioned or rejoined (short: 0xe7e6)
I (20520) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (20520) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (20560) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (20630) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK

Due to a large number of frames being received by the gateway with insufficient buffer space, the message MAC RX buffer is full! is being displayed. Once the received frame has been processed and the buffer is released, the normal process resumes. I'm uncertain why you are experiencing a log loop on your end. In the next stage, there are three potential ways to address this issue:

Please switch to the latest master branch of esp-zigbee-sdk and not change anything for attemptting the process again . Afterwards, please provide feedback on the outcome.
Distribute the end devices among different routers to establish a Zigbee mesh network.
Attempt to pair the end devices with the coordinator at different times.

Once the received frame has been processed and the buffer is released, the normal process resumes.
I think it should be but I have loop errors many time. Even if I powering off whole pairing devices after got errors.
Sometimes it leads to few buffer errors and continue joining devices but later it end with core dump.

Hi,
I have been unable to reproduce the issue. Are you certain that you are using the latest esp-zigbee-sdk branch in your project? I noticed a slight difference in the logs, such as 'ZDO signal: NWK Device Associated (0x12), status: ESP_OK'."
I will continue to resolve the issue, if you have any update for it, please inform me.

Hi, I have been download updated example from here and just set wifi SSID and dependencies versions to espressif/esp-zboss-lib: "~0.6.0" espressif/esp-zigbee-lib: "~0.8.0". Then I was upload fw and powered on my end devices (13 pcs).
Its dont falling to the bootloop anymore but still leading to weird behavior and successfully paired devices to the network in the end.
log.txt

@BogatovT We can't reporduce the issue even with ~15 zigbee devices reboot at the same time. It seems the issue is caused by some particular packet sent by your test device.
Could you share us the sniffer packet with us? And what's the zigbee device in your test? Do you see the same issue if you test with the HA_on_off_light example?

Hi, I was rebuild example with last 0.9.0 sources and reproduced it with 15 devices. It leads to RX buffer overflow again.
In the first attempt everything was ok and all devices are paired to the network.
In the second attempt it has periodically core panic (log_1 and smartrf_1).
In the third attempt it has few overflow errors and successfully paired whole devices (log_2 and smartrf_2).
I was saved sniffer sessions, you can open it with TI SmartRF Packet Sniffer software. Sniffer sessions are packed into the zip because github cannot attach this file extension.
log_1.txt
log_2.txt
sniffer.zip

And what's the zigbee device in your test? Do you see the same issue if you test with the HA_on_off_light example?

I cant test it with HA_on_off_light because i have only two ESP-C6 devboards.
I test it with my CC2530 boards developed to lights dimming control. It based on the modified Z-stack firmware. Every device has a router role and sending his dimmer level to the coordinator after connecting and every 30 seconds. It works well with some zigbee2mqtt coordinators and another TI devices based on Z-stack,

I can get this error by calling esp_zb_zdo_binding_table_req() (v0.9.3) with dst_addr = 0xffff in a network with 17 devices, it feels like it may be trying to query bindings on every device and gets stuck in a loop:
2023-09-12 13:04:44.811008 I (24940) nutt.ZigbeeDevice: Binding table:
2023-09-12 13:04:44.861645 E (24980) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:44.882739 E (25000) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:44.892315 E (25010) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:44.909469 E (25030) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:50.870094 E (30990) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:57.071107 I (37200) nutt.ZigbeeDevice: Binding table:
2023-09-12 13:04:57.124449 E (37240) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:57.135785 E (37250) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:57.146586 E (37260) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:57.209339 E (37330) ESP_ZIGBEE_API_ZDO: zdo_binding_table_resp(794): Not found the device binding table request alarm, failed to cancel it
2023-09-12 13:04:57.581109 W (37710) ZB_ESP_MAC: MAC RX buffer is full!
2023-09-12 13:04:57.589705 W (37720) ZB_ESP_MAC: MAC RX buffer is full!
2023-09-12 13:04:57.595324 W (37720) ZB_ESP_MAC: MAC RX buffer is full!
...
2023-09-12 13:05:19.164173 W (59280) ZB_ESP_MAC: MAC RX buffer is full!
2023-09-12 13:05:19.169568 W (59280) ZB_ESP_MAC: MAC RX buffer is full!
2023-09-12 13:05:19.175399 W (59290) ZB_ESP_MAC: MAC RX buffer is full!
# restarted to stop it

I'm using CONFIG_IEEE802154_RX_BUFFER_SIZE=100.

@nomis @BogatovT ,
For this issue, we have already attempted to optimize the Zigbee buffer mechanism in esp-zigbee-lib v0.9.5. Could you please try it again?

I tested it with device pairing. It works more smoothly but still sometimes errors happen.

@BogatovT ,
Will it still print MAC RX buffer is full until you reset the chip?

@xieqinan
MAC RX buffer is full error still happens. It could be repeating in few seconds and then works normally. In other way this error leads to core panic.
I`m not sure about it still buffer overflows until I reset the chip. But it really works better now!
I can try to reproduce any situations if it will help.

Hello @BogatovT ,

It could be repeating in few seconds and then works normally.

This is a normal phenomenon because the received buffer of the MAC layer is set to 20. If many devices issue the association request,  it is possible to trigger a full buffer condition.

In other way this error leads to core panic.

Could you please provide the core panic log?"

@xieqinan
I was updated zigbee_gateway example files from master and update libs version in dependencies to 1.0.0. And just set my wifi SSID and pass.
I tried to pair more than 30 devices at the same time to accurately reproduce it.
log.txt

@xieqinan
I was found another case with this buffer overflow. And it can reproduce with the same example code and some additions.
Add it in esp_zigbee_gateway.c:
#include "zboss_api.h"

bool rawCmdHandlerCb(uint8_t bufid) {
    uint8_t buf[zb_buf_len(bufid)];
    zb_zcl_parsed_hdr_t *cmd_info = ZB_BUF_GET_PARAM(bufid, zb_zcl_parsed_hdr_t);
    memcpy(buf, zb_buf_begin(bufid), sizeof(buf));
    ESP_LOGI("RAW", "bufid: %d size: %d", bufid, sizeof(buf));
    for (int i = 0; i < sizeof(buf); ++i) {
        printf("0x%02X ", buf[i]);
    }
    printf("\n");
    printf("cluster id: 0x%02X, command id: %d\n", cmd_info->cluster_id, cmd_info->cmd_id);
    printf("rssi: %d, profile_id: %d\n", cmd_info->rssi, cmd_info->profile_id);
    printf("is_common_command: %d, disable_default_response: %d\n",
           cmd_info->is_common_command, cmd_info->disable_default_response);
    printf("is_manuf_specific: %d, manuf_specific: %d\n\n",
           cmd_info->is_manuf_specific, cmd_info->manuf_specific);
    return true;
}

And add it in esp_zb_task() task:
 esp_zb_cluster_list_t *clusterList = esp_zb_zcl_cluster_list_create();
 // on off
 esp_zb_on_off_cluster_cfg_t onOffClusterCfg;
 onOffClusterCfg.on_off = ESP_ZB_ZCL_ON_OFF_ON_OFF_DEFAULT_VALUE;
 esp_zb_attribute_list_t *onOffCluster = esp_zb_on_off_cluster_create(&onOffClusterCfg);
 esp_zb_cluster_list_add_on_off_cluster(clusterList, onOffCluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
 esp_zb_cluster_list_add_on_off_cluster(clusterList, onOffCluster, ESP_ZB_ZCL_CLUSTER_CLIENT_ROLE);
 // level control
 esp_zb_level_cluster_cfg_t levelClusterCfg;
 levelClusterCfg.current_level = ESP_ZB_ZCL_LEVEL_CONTROL_CURRENT_LEVEL_DEFAULT_VALUE;
 esp_zb_attribute_list_t *levelCluster = esp_zb_level_cluster_create(&levelClusterCfg);
 esp_zb_cluster_list_add_level_cluster(clusterList, levelCluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
 esp_zb_cluster_list_add_level_cluster(clusterList, levelCluster, ESP_ZB_ZCL_CLUSTER_CLIENT_ROLE);
 esp_zb_ep_list_t *epList = esp_zb_ep_list_create();
 esp_zb_ep_list_add_ep(epList, clusterList, 1, ESP_ZB_AF_HA_PROFILE_ID, ESP_ZB_HA_LEVEL_CONTROLLABLE_OUTPUT_DEVICE_ID);
 esp_zb_device_register(epList);
 esp_zb_raw_command_handler_register(rawCmdHandlerCb);
 esp_zb_device_cb_id_handler_register(rawCmdHandlerCb);

This code works but periodically it has looping buffer overflow about 200 seconds and than rebooting.
full_code.txt
log.txt

@BogatovT.
This issue can refer to esp-zigbee-core. This means that the user utilizes the bufid to retrieve and handle commands from the zboss stack. It is necessary for the user to free the bufid manually.

@xieqinan
Ok, thanks. Where I can find more information about handling raw data? For example this responses https://github.com/espressif/esp-zigbee-sdk/issues/94#issuecomment-1706350174 ?

@BogatovT ,

Ok, thanks. Where I can find more information about handling raw data? For example this responses #94 (comment) ?

We have not provided extensive documentation for handling raw data. If you need a solution for specific raw data, feel free to raise a related issue.

@BogatovT Please file separate feature requests if you want more callback ids which are missing in current SDK. Raw data handling is a temp solution which is not recommended now.
Back to the origin Buffer is full issue, we have had some enhancements recently, could you try again with the latest SDK (esp-zigbee-lib v1.0.4, esp-zboss-lib v1.0.3) and check whether the issue still exist?

@chshu  I was update example code and libs. Tried to pair the same devices as before. It was no "buffer full" error but rebooting with Core panic.
log.txt

@BogatovT The current Zboss macsplit based zigbee gateway+rcp solution is an experimental feature, we do see some stability issues recently.
We are working on a new zigbee gateway solution which will base on the ot_rcp, some stress tests are on going, will push to github in 2024 Q1.

@BogatovT The ot_rcp based Zigbee Gateway example is available now: https://github.com/espressif/esp-zigbee-sdk/tree/main/examples/esp_zigbee_gateway
Note:

Please use the esp-idf master branch (Commit ad3e1e3 or later). It will be supported in the coming IDF v5.1.3 and later release versions.
Enable OPENTHREAD_NCP_VENDOR_HOOK option before building ot_rcp example.

Feel free to try out the new feature, and let us know if any questions or suggestions.


Uninstall of python-dotenv does not (really) work

Issue description
I also tried reaching out on stackoverflow, but at this point. it feels like a bug
version: pipenv, version 2023.3.20
I try to uninstall python-dotenv. Should be easy, right? It's not in my Pipfile, and in my pipenv-graph it's not listed as a transitive dependency.
Following this series of commands:

$ echo "graph"; pipenv graph | grep python-dotenv; echo "Pipfile.lock"; cat Pipfile.lock | grep python-dotenv; echo "Pipfile"; cat Pipfile | grep python-dotenv
graph
Loading .env environment variables...
python-dotenv==1.0.0
Pipfile.lock
        "python-dotenv": {
Pipfile
$ pipenv uninstall python-dotenv
Loading .env environment variables...
Removing python-dotenv from Pipfile.lock...
Uninstalling python-dotenv...
Found existing installation: python-dotenv 1.0.0
Uninstalling python-dotenv-1.0.0:
  Successfully uninstalled python-dotenv-1.0.0

Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
Locking [dev-packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
Updated Pipfile.lock (9362bc95e99217f2f5cac841a8b99b7b491e5c52886bf094ff10df3874969e05)!
$ echo "graph"; pipenv graph | grep python-dotenv; echo "Pipfile.lock"; cat Pipfile.lock | grep python-dotenv; echo "Pipfile"; cat Pipfile | grep python-dotenv
graph
Loading .env environment variables...
Pipfile.lock
        "python-dotenv": {
Pipfile

notice, how it's NOT deleted from the Pipfile.lock?, well, if i now run "pipenv install", I went full circle and have it back in my pipenv graph.
I thought removing it manually from the pipfile lock would work, but after running "pipenv lock" (or any other command that recreates the lockfile) it's back in there again, even if it was not present in the Pipfile nor pipenv graph.
Expected result
the package being actually removed, and not reappearing again

pipenv --support is way to large to paste here
pipenv__support.txt

@soraphis Ok I spent a bit debugging this, and it seems it is because you have django-dotenv = "*" in your Pipfile which certainly requires python-dotenv  -- I am not sure why its showing up as a top level item in the graph though.

Sorry, I was slightly off base in my last response, the real reason its included is uvicorn:  https://github.com/encode/uvicorn/blob/master/pyproject.toml#L41

Thanks for taking the time and looking into it. What I don't really get is: why isn't showing up in the graph? Other dependencies are also listed multiple times if required by multiple packages...

For the record, I tested this the other day out of curiosity. PDM also installs python-dotenv when importing from this Pipfile, but doesn't list it in pdm list --graph at all, which I thought was very strange.

The new version of pipdeptree appears to fix this, I have a PR out to update pipenv.

Well it kind of fixes it -- it shows up in the graph, just not under uvicorn, which seems odd.

Whether it appears in the graph is kind of secondary, I think. The real problem here is that:

python_dotenv is an optional dependency of uvicorn
python_dotenv and dotenv are incompatible

Thus:

Nothing strictly requires python_dotenv (at least uvicorn doesn't, I haven't checked all other packages)
python_dotenv is installed anyway (for what reason?)
dotenv package breaks / may break as a result

IIRC, pipenv graph always showed python_dotenv as a top-level dependency, not under uvicorn.
Pure speculation: maybe the resolver includes all optional dependencies, thus python_dotenv is installed, but the dependency tree does not consider optional dependencies, thus it is not listed as a dependency of any other package.

Actually that part is easy to explain @derula --
uvicorn = {extras = ["standard"], version = "*"}
extras = ["standard"] does tell it to install all of: https://github.com/encode/uvicorn/blob/master/pyproject.toml#L38-L46

Ah, okay, I must have missed that. Then I guess there are 2 separate problems:

@soraphis shouldn't be using the standard extra because that will cause python-dotenv to be installed, conflicting with dotenv
python-dotenv (maybe all optional deps?) not listed as sub-dependency of uvicorn

python-dotenv (maybe all optional deps?) not listed as sub-dependency of uvicorn

@derula that should be reported upstream to pipdeptree

@derula that should be reported upstream to pipdeptree

Upstream ticket has existed upstream for over 4 years: tox-dev/pipdeptree/issues/107
PR has since been created, diverged, and closed: tox-dev/pipdeptree/pull/138
Seems like it won't be fixing itself :)


Description The row spacing is too small because the environment or cluster is associated

关联环境/集群，行间距过小

dump with https://github.com/masastack/MASA.PM/issues/326

重复issue


Convert scripts to Python 3

Use https://docs.python.org/2/library/2to3.html

@MichalPospech if this is done, please close it. For now postponing this issue to the next sprint.

Please do not use 2to3...  It often breaks Python 2 compatibility (#173) to get to Python 3.  I would advicate futurize (https://python-future.org) or moderize (python-modernize/python-modernize) instead.  Happy to help if that would be of interest.

Due to nontrivial merging postponing to the next sprint.

@MichalPospech how is it going? I'm postponing this issue to the next sprint.

@MichalPospech will not continue on this, @AlexejPopovic please revisit what was done and complete this.

Merged to devel, finally ;)


Placing in /etc/profile.d breaks X

After copying scipt to /etc/profile.d and rebooting. The graphical login screen is stuck in an endless loop asking for password, I input correct password then it loops back to asking for password again. Removing the file from /etc/profile.d and rebooting fixed this and allowed me to login and start the desktop.

I have the same problem, and when running cat .xsession-errors the error "/ etc / X11 / Xsession: 5: /etc/profile.d/motd.sh: Syntax error:" ("unexpected"

Here is my forked version with correct way to install
https://plasmoduck.github.io/raspberrypi-motd/
On Fri, Jun 22, 2018 at 12:09 PM, P4N1CO<EMAIL_ADDRESS>wrote:

I have the same problem, and when running cat .xsession-errors the
error "/ etc / X11 / Xsession: 5: /etc/profile.d/motd.sh: Syntax
error:" ("unexpected"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Source the motd.sh script in the file ~/.profile by placing a link to
it at the end of the file like /path/to/motd.sh and it will be executed
after login.
On Sun, Jun 24, 2018 at 4:34 AM, Chris Garvin
<EMAIL_ADDRESS>wrote:

Here is my forked version with correct way to install
https://plasmoduck.github.io/raspberrypi-motd/
On Fri, Jun 22, 2018 at 12:09 PM, P4N1CO<EMAIL_ADDRESS>wrote:

I have the same problem, and when running cat .xsession-errors the
error "/ etc / X11 / Xsession: 5: /etc/profile.d/motd.sh: Syntax
error:" ("unexpected"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Very good, it worked.


Update tests due to changes in edit_active.tendering role

Depends on:

https://github.com/openprocurement/openprocurement.auctions.core/pull/134

Pull Request Test Coverage Report for Build 74

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.009%

Totals

Change from base Build 73:
0.0%

Covered Lines:
542

Relevant Lines:
686

💛  - Coveralls


variable "undoValue" isn't initialized correctly

Hi,
in function "submitEvent" you use variable "undoValue" in a condition. In my opinion, these variable is (...in some cases...?) never initialized and undefined during submit.
Therefore i got the same problems as described in #1392.
Could you please have a look?

@kiesslir ,
Fixed in the current


error when uploading archieve to appstore

ERROR ITMS-90635: "Invalid Mach-O Format. The Mach-O in bundle "HeartKeeper.app/Frameworks/Quickblox.framework" isn’t consistent with the Mach-O in the main bundle. The main bundle Mach-O contains armv7(machine code) and arm64(machine code), while the nested bundle Mach-O contains armv7(bitcode) and arm64(bitcode). Verify that all of the targets for a platform have a consistent value for the ENABLE_BITCODE build setting."

Hi,
Where are you getting this error?
Q-municate has bitcode disabled for now, cause it is shipped with QuickbloxWebRTC framework which is not supporting bitcode for now.

so what is the workaround for now..

At first I need to know where are you getting this error, at least.

i am done with making an archieve of the app but when i upload the archieve to the appstore this  error comes after few minutes.

should i downgrade the version of the pod ...?

It wouldn't help probably in your case. Try this http://stackoverflow.com/questions/37689054/sudden-error-when-uploading-to-itunesconnect-itms-90635-invalid-mach-o-format

@Anilkr91, Hello. Any updates?

i was able to upload the binary when i deselect the use bitcode option when uploading to Appstore.. Do you have any other way around to solve the issue.

@Anilkr91 , We're working on it, but, unfortunately, there is no ETA.

@Anilkr91  resolved, QuickbloxWebRTC.framework supports bitcode now


MWW version won't install after 2024.12

Flavor
MicroWakeWord
Checklist

[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..
[X] I am able to consult debug logging for my ESPHome instance.

Describe the issue
Install fail after updating Esphome to 2024.12
Reproduction steps

...
Debug logs
INFO ESPHome 2024.12.0 INFO Reading configuration /config/esphome/onju-voice-04.yaml... INFO Generating C++ source... INFO Updating<EMAIL_ADDRESS>INFO Updating submodules (components/esp-adf-libs, components/esp-sr) for<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Updating<EMAIL_ADDRESS>INFO Compiling app... Processing onju-voice-04 (board: esp32-s3-devkitc-1; framework: espidf; platform: https://github.com/pioarduino/platform-espressif32.git#51.03.07) -------------------------------------------------------------------------------- Library Manager: Installing improv/Improv @ 1.2.4 INFO Installing improv/Improv @ 1.2.4 Downloading [####################################] 100% Unpacking [####################################] 100% Library Manager<EMAIL_ADDRESS>has been installed! INFO<EMAIL_ADDRESS>has been installed! Library Manager: Installing esphome/noise-c @ 0.1.6 INFO Installing esphome/noise-c @ 0.1.6 Downloading [####################################] 100% Unpacking [####################################] 100% Library Manager<EMAIL_ADDRESS>has been installed! INFO<EMAIL_ADDRESS>has been installed! Library Manager: Resolving dependencies... INFO Resolving dependencies... Library Manager: Installing esphome/libsodium @ 1.10018.4 INFO Installing esphome/libsodium @ 1.10018.4 Downloading [####################################] 100% Unpacking [####################################] 100% Library Manager<EMAIL_ADDRESS>has been installed! INFO<EMAIL_ADDRESS>has been installed! Library Manager: Installing kahrendt/ESPMicroSpeechFeatures @ 1.1.0 INFO Installing kahrendt/ESPMicroSpeechFeatures @ 1.1.0 Downloading [####################################] 100% Unpacking [####################################] 100% Library Manager<EMAIL_ADDRESS>has been installed! INFO<EMAIL_ADDRESS>has been installed! /data/cache/platformio/packages/framework-espidf Already Patched: yes HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash - framework-espidf @ 3.50105.0 (5.1.5) - tool-cmake @ 3.21.3 - tool-esptoolpy @ 4.8.1 - tool-mklittlefs @ 3.2.0 - tool-ninja @ 1.7.1 - tool-riscv32-esp-elf-gdb @ 12.1.0+20221002 - tool-xtensa-esp-elf-gdb @ 12.1.0+20221002 - toolchain-esp32ulp @ 2.35.0-20220830 - toolchain-riscv32-esp @ 12.2.0+20230208 - toolchain-xtensa-esp32s3 @ 12.2.0+20230208 Reading CMake configuration... -- Found Git: /usr/bin/git (found version "2.39.5") -- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).' -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- The ASM compiler identification is GNU -- Found assembler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-gcc -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-gcc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-g++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Building ESP-IDF components for target esp32s3 NOTICE: Following dependencies have new versions available: Dependency "espressif/esp-nn": "1.0.2" -> "1.1.0" Consider running "idf.py update-dependencies" to update your lock file. Processing 1 dependencies: [1/1] idf (5.1.5) -- Configuring incomplete, errors occurred! See also "/data/build/onju-voice-04/.pioenvs/onju-voice-04/CMakeFiles/CMakeOutput.log". fatal: not a git repository (or any parent up to mount point /) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). CMake Error at /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:266 (message): Failed to resolve component 'esp_adc_cal'. Call Stack (most recent call first): /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:302 (__build_resolve_and_add_req) /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:309 (__build_expand_requirements) /data/cache/platformio/packages/framework-espidf/tools/cmake/build.cmake:603 (__build_expand_requirements) /data/cache/platformio/packages/framework-espidf/tools/cmake/project.cmake:604 (idf_build_process) CMakeLists.txt:3 (project) ========================= [FAILED] Took 12.70 seconds =========================

Your solution lies here https://github.com/dreimer1986/onju-voice-satellite/blob/main/esphome/onju-voice-microwakeword.yaml check lines 68 and 69. When I ever find out how to cherry pick changes for pull requests, I will even make one here, but for now I can only tell you what to hand edit... sorry. Already waay too much tinkering in my code base to just say, "Hi, here's is my lil pull request with 387462 modifications. Have fun."
The problem is the new version does some version bump that does not support ADF-Pipeline and we have to manually hop back a bit.
https://github.com/gnumpi/esphome_audio/issues/74

Thanks !


Clicking the ⚙  icon in kernel selector doesn't do anything

On the prerelease Jupyter extension, open the IW and click on the kernel selector in the top right. Then, click on the ⚙ icon for any environment. Nothing happens.

Previous gear icon issue: https://github.com/microsoft/vscode/issues/146667 was duped against the bigger "handling preferred better" issue: https://github.com/microsoft/vscode/issues/146339

It doesn't do anything it seems, we should now remove it.

Let's merge it into https://github.com/microsoft/vscode/issues/148287


feat: frontmatter

Frontmatter for the current page is available via useCurrentFrontmatter, it doesn't update when modified though.

We might be able to invalidate the module on change. Or we setup our own HMR

I think we could inject our own HMR listeners in each page and call some sort of refreshFrontmatter that re-evaluates the resource, will do it soon


CI for Intel Mac?

Do we care to support Intel Mac? Do our internal repos/users use intel mac to run services? If not, we probably can close this issue as "won't fix" (and make a note in README).
Note that

Our CI has stopped building on Intel mac since macos-latest became an alias for macos-14
Some examples/tests currently fail on intel mac; e.g.: https://github.com/juspay/services-flake/pull/226#issuecomment-2168564419

Do we care to support Intel Mac? Do our internal repos/users use intel mac to run services?

We don’t recommend that at least

If not, we probably can close this issue as "won't fix" (and make a note in README)

👍


Data Source

Hello, I'm working on an Eisenhower matrix project and was trying to find where you stored the data for your cool looking js app?

Hi! This app is storing all the data as simple JSON object with arrays inside it. The JSON is stored in browser's local storage. You can read more about it here: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API.

Here you can see where the data is fetched from the storage the first time: https://github.com/attuo/Priorizer/blob/ce7bda5f3188bfb4f047f80010f0f99e226ed2d0/src/components/Platform/Platform.js#L14
Here you can see how the data is read: https://github.com/attuo/Priorizer/blob/master/src/hooks/usePersistedState.js
Here you can see the initial state of the JSON data, so when the App is empty: https://github.com/attuo/Priorizer/blob/master/src/utils/initData.js

So all in all, basically it just stores the data as JSON to browser's own data storage, so on your PC. I hope this answered your question. :)

@attuo Ok so if I understand what you said the app data is stored with the json. Where is the actual decision logic contained for this, as I understand it there is no actual logic, this is the GUI container for such logic as you state is a PoC?


InvalidPluginException: Unsupported API version

An error named "InvalidPluginException: Unsupported API version" may occour on 1.13.x and 1.14.x!
Temporary fix:
https://github.com/SpillereNO/BlowableObsidians/wiki/Unsupported-API-version
Permanently fix:

[ ] fixed this permanently

This will now occur on 1.15.x as well.


[#14] [WIP] update domains

Codecov Report

Merging #16 (1a152c6) into main (82850af) will decrease coverage by 21.07%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##               main      #16       +/-   ##
=============================================
- Coverage     75.00%   53.93%   -21.07%
  Complexity       16       16
=============================================
  Files             4        7        +3
  Lines            64       89       +25
  Branches          3        3
=============================================
  Hits             48       48
- Misses           14       39       +25
  Partials          2        2

Impacted Files
Coverage Δ

...yninwx/lib/services/AbstractInwxUpdateService.java
0.00% <0.00%> (ø)

...vices/ApacheHttpClientStaticInwxUpdateService.java
0.00% <0.00%> (ø)

...rwell/jdyninwx/lib/services/InwxUpdateService.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fizzbuzz Reverse Using Stack

I contribute the Fizzbuzz reverse program in C++ using Stack.

Thank you for your PR!
Unfortunately your solution isn't in the scope of this repository :/
The goal is to find creative/abstract new solutions to FizzBuzz. Not string reversals.
Please consult the readme for more information and see The top 5 samples here.
Thanks anyway! :)


Changing status & Automod Badge

Can someone make the bot change status. Like i mean that the bot is changing between multiple statuses. Like this "website"  "50 servers" "100 users". The bot changes between those.
Make the bot so that the bot can get the automod badge!
Also add filters to music. Like nightcore & 8D

Give 5 euros and I'll do it xD

3?
Olliver Halvorsen

jun. 2023 kl. 9:26 pm skrev barrierunlocked @.***>:

Give 5 euros and I'll do it xD
—
Reply to this email directly, view it on GitHubhttps://github.com/saiteja-madha/discord-js-bot/issues/363#issuecomment-1586307039, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2WV2VUGYGTIJ55NULCFAYDXKYLXZANCNFSM6AAAAAAY3KAJ6E.
You are receiving this because you authored the thread.Message ID: @.***>

I offer you 3

Deal?

Yeah. Add me on dc: halvi07
Olliver Halvorsen

jun. 2023 kl. 1:22 am skrev barrierunlocked @.***>:

Deal?
—
Reply to this email directly, view it on GitHubhttps://github.com/saiteja-madha/discord-js-bot/issues/363#issuecomment-1586374044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2WV2VTJOL4CM7ILRI52HNLXKZHKZANCNFSM6AAAAAAY3KAJ6E.
You are receiving this because you authored the thread.Message ID: @.***>

still waiting to get paid ngl

I had it and it is so gimmicky lol, currently i am working on an owner command to change the bot's status without having to edit the config, like YAGPDB


Request more useful coloration in disassembly

It would help greatly speed up reading this form of SPIR-V (types on the right, with the operands) if:

types were a different color than non types
color for thing X is the same on both sides of the = (note the side of the = is already trivially visually discernible)

color for thing X is the same on both sides of the = (note the side of the = is already trivially visually discernible)

Right now definitions are blue and uses are yellow.   This is a hold-over from when the assembly syntax didn't use the equality sign and result ids were in place as specified by the binary format.  It enhanced readability to make result-ids a different colour from other IDs.
If we change to make result IDs the same as uses, then (except for your first suggestion), all IDs would be the same colour.  Is that what you mean?

Yes. It is easier to visually match up the same thing if it is rendered the same way. It seems better to have color carry an additional meaning. Currently, it is harder to pick out types than left/right of the =.
(I have no criticism or complaints about how we got here.)

Unlikely that we will change this.


Dataframe of the survival function (cph.predict_survival_function())

Hello,
The output of this is an NxD dataframe. Each column appears to correspond to the row index of the data and the row is the probability of survival. So surivial_df[i, j] is the probability of the jth datapoint surviving after i units of time. Why do the row values skip values? For example, my first row value is 47.0 and the second jumps to 128.0. Why does it not start from 1 and increase by 1 unit of time?

It's a good question. Because you are using a semi-parametric estimator, specifically the baseline-hazard is non-parametric. The baseline-hazard (and hence the baseline-survival) only has "information" to change at times observed in the dataset (if you sort your observations, you'll see ..., 47, 128, ...).
You can "fill-in" the gaps using the timeline argument in the predict_survival_function to create a custom timeline to evaluate against.

I see, thanks for the insight!
Doing something like this worked for me
survival_func_cph = cph.predict_survival_function(censored_X,
   conditional_after=censored_subjects_last_obs, times = range(100) )


Board Review: Introducing apimanagement-custom-widget-scaffolder

Contacts and Timeline

Service team responsible for the client library: @Azure/apim-team
Main contacts: @JMach1 & @azaslonov
Expected stable release date for this library: 1st July

About the Service

Link to documentation introducing/describing the service: http://aka.ms/apimdocs/portal/
Link to the service REST APIs:
@azure/api-management-custom-widgets-scaffolder - apiview.dev
@azure/api-management-custom-widgets-tools - apiview.dev
Is the goal to release a Public Preview, Private Preview, or GA? GA

About the client library

Name of client library: @azure/apimanagement-custom-widget-scaffolder
Link to library reference documentation: in development, soon accessible on https://aka.ms/apimdocs/portal/customwidgets
Is there an existing SDK library? If yes, provide link: No

Step 1: Champion Scenarios

Champion scenario 1

Customer uses his Developer Portal, which is part of the Azure API Management service.
Customer wants to customize it further, beyond what it's allowed now using various common widgets.
Customer begins process of creation of a custom widget via their admin interface of their Dev Portal, specifies name of their custom widget and which technology to use:

Customer copies generated npx command and runs it locally (example of the generated command:
npx @azure/apimanagement-custom-widget-scaffolder --displayName="Contoso widget" --tech="react" --openUrl="http://localhost:8080" --managementApiEndpoint="management.azure.com" --resourceId="subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.ApiManagement/service/<service-name>").
NPX command executes this library and creates a scaffold of a custom widget for the custommer.

Champion scenario 2

Customer runs the npx @azure/apimanagement-custom-widget-scaffolder command directly and provides answers to all the prompts:  (the exact wording of some of the questions is expected to change)

Champion scenario 3

Programmatically (not expected to be used like this by customers, only by various MS tools, e. g. APIMs' VS Code extension)

import { generateProject, TDeployConfig, TWidgetConfig } from "@azure/apimanagement-custom-widget-scaffolder";

async function main(): Promise<void> {
  const widgetConfig: TWidgetConfig = {
      displayName: "Contoso widget",
      tech: "react",
  };
  const deployConfig: TDeployConfig = {
    managementApiEndpoint: "management.azure.com",
    resourceId: "subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.ApiManagement/service/<service-name>",
  };

  return generateProject(widgetConfig, deployConfig)
    .then(() => console.log("Your project has been generated successfully!"))
    .catch(console.error);
}

Step 2: Quickstart Samples (Optional)

(Optional) Using your APIMs' Developer Portal instance, copy command to scaffold a custom widget with prefilled some of the fields and run it instead of next step
npx @azure/apimanagement-custom-widget-scaffolder
fill in all the questions asked by the Inquirer

Scheduled for 7/19 9a-11a PDT

Recording (MS INTERNAL ONLY)


BUG: Actor call has created too many clients

Note that the issue tracker is NOT the place for general support.  For
discussions about development, questions about usage, or any general questions,
contact us on https://discuss.xorbits.io/.
Sometimes, this log happens:

I get this too, when you create more than 100 actors.


add docs directory to cookiecutter template with the necessary tooling to build

it would be nice to have the cookiecutter template that is created to include a docs directory that has the docs-as-code templates.  for example https://github.com/lila/readthedoc-test  uses sphinx and github actions to build and deploy in github pages.  other frameworks are fine too...

Cookiecutter has been replaced by copier


ref_map bug

Hi,
I'm getting this error with v2.0.4:
Failed to evaluate 'ref_map' (reason 1 of 1): Evaluating read_map(ref_map_file) failed: Failed to read_map("gs://pacbio-wdl/hifi-wdl-resources-v2p0p0-rc6/GRCh38.ref_map.v2p0p0-rc6.gcp.tsv") (reason 1 of 1): [Attempted 1 time(s)] - IOException: Could not read from gs://pacbio-wdl/hifi-wdl-resources-v2p0p0-rc6/GRCh38.ref_map.v2p0p0-rc6.gcp.tsv: 404 Not Found GET https://storage.googleapis.com/download/storage/v1/b/pacbio-wdl/o/hifi-wdl-resources-v2p0p0-rc6%2FGRCh38.ref_map.v2p0p0-rc6.gcp.tsv?alt=media&userProject=terra-a6717d5b No such object: pacbio-wdl/hifi-wdl-resources-v2p0p0-rc6/GRCh38.ref_map.v2p0p0-rc6.gcp.tsv
Note, this is via Terra.

I'm curious if this issue has a solution? Thanks

The paths have been updated in the input templates:
https://github.com/PacificBiosciences/HiFi-human-WGS-WDL/blob/main/backends/gcp/singleton.gcp.inputs.json
https://github.com/PacificBiosciences/HiFi-human-WGS-WDL/blob/main/backends/gcp/family.gcp.inputs.json


Add example of lists manipulation

Control flow exercises often need lists, but there are no examples or exercises to introduce people in list manipulation.

To be verified during the next tutorial session.

Linked to #215

Is this not covered by Exercises on lists in basic datatypes?


Document with Swagger

We should totally use Swagger to document the API. Maybe using https://github.com/ruby-grape and https://github.com/ruby-grape/grape-swagger. This would also have the added effect of decoupling the API code from the visualisation code.

Can we use swagger without rewriting the API to use Grape? Or is that simple enough anyway? @pezholio any experience would be helpful, otherwise we'll just work it out :)

@pezholio @floppy In terms of what we want documented: would only the API endpoints mentioned in current readme (pertaining exclusively to metrics and their metadata) be documented via Grape or would the Dashboard endpoints also be documented? From naive POV it seems like the Dashboard portion of the Apps strength is being GUI and WYSIWYG

Yeah, dashboard endpoints are definitely a secondary concern, being built for human use.

@Floppy I have a question - where is the auto documented swagger API envisioned as existing? Is it for inclusion in lieu of (and at the same URL as) bothan.io/api OR is it envisioned as an additional page that is generated for every users who generate their own Bothan instance via the Heroku sign up?

Hm, good question. it could be either, really. If it's in the app, then it's going to be correctly set up with the right URLs, etc. I'm guessing because swagger and grape are part of the app, then it will be there rather than on bothan.io itself.

cool, good to have clarity. I guess the bothan.io docs URL could then point to https://demo.bothan.io/(whatever-stub-is-decided-for-documentation)


Output VMSS cloud config settings.

Output VMSS cloud config settings for AKS to consume.

@JunSun17 What's the functional purpose of this change?


[6] Connect this DevOps pipeline to the GitHub repository

Hey team! Please add your planning poker estimate with Zenhub @even1111112 @nicksome168 @PepperandSummer @un-poco @yjhsieh2022


(PUP-5934) Add optional fact refresh after applying catalog

This is PR #7666 targeted at master with a few minor adjustments

jenkins please test this on redhat7-64a,windows2019-64a with servertests

CLA signed by all contributors.


Rewrote interval lists to support future work in interval aggregation

jenkins

Again, happy to take criticism on names / structure

I think this API is a lot cleaner though

jenkins

jenkins

I did a benchmarking experiment.
My inputs:

VDS: vds created from seq 1<PHONE_NUMBER>00 mapped to "1  $i   A   T   NA", and imported with hail importannotations.  This is a 3M variant sites vds.
interval file: exome capture regions provided by Monkol.  Seems like pretty random non-overlapping interval over chr1.  39K variants fall in these intervals, slightly over 1%.

My cmd line:
hail read -i <vds> filtervariants intervals --keep -i <interval list>  count, with the read/filter/count repeated 10 times.  I ran this on the current master and this branch on one core on my laptop.  I then calculated the time per iteration.
Benchmark results
current master: 4.876s, with a std dev of  0.18
this branch: 4.716s, with a std dev of  0.18
mean ratio: 0.967
Conclusion: this branch is faster than master for interval queries by 3-4%

Note that it does take slightly longer to prepare an interval list on the master, about 250ms for the 220k intervals I got from Monkol.

jenkins