Running the tests failed

Hi, I was trying to set up ubpf on a clean Ubuntu 20.04.6 LTS, everything went well but the tests failed. Below are the details:
sudo apt-get update
sudo apt install cmake # version == 3.16.3

sudo apt install python2
curl https://bootstrap.pypa.io/pip/2.7/get-pip.py --output get-pip.py
sudo python2 get-pip.py

git clone https://github.com/iovisor/ubpf/
git submodule init
git submodule update --recursive
pip2 install -r requirements.txt

sudo apt-get install libbpf-dev
sudo apt-get install libboost-all-dev

git clone https://github.com/serge1/ELFIO.git
sudo mv ELFIO/elfio/ /usr/local/include/

sudo apt-get install clang # clang version 10.0.0, newer than 3.7

cmake -S . -B build -DUBPF_ENABLE_TESTS=true
cmake --build build --config Debug
cmake --build build --target test -- # This is the step that gets wrong

I got the following error:
Running tests...
Test project /home/ubuntu/ubpf/build
      Start  1: cpu_v1
1/38 Test  #1: cpu_v1 ...........................***Failed    0.10 sec
      Start  2: cpu_v2
2/38 Test  #2: cpu_v2 ...........................***Failed    0.01 sec
      Start  3: cpu_v3
3/38 Test  #3: cpu_v3 ...........................***Failed    0.00 sec
      Start  4: elf_format
4/38 Test  #4: elf_format .......................***Failed    0.00 sec
      Start  5: no_bpf_bytecode
5/38 Test  #5: no_bpf_bytecode ..................***Failed  Required regular expression not found. Regex=[Test file has no BPF instructions
]  0.00 sec
      Start  6: invalid_return_value
6/38 Test  #6: invalid_return_value .............***Failed  Required regular expression not found. Regex=[Plugin returned invalid return value Hello World
]  0.00 sec
      Start  7: wrong_output
7/38 Test  #7: wrong_output .....................***Failed  Required regular expression not found. Regex=[Plugin returned incorrect return value 1 expected 3
]  0.00 sec
      Start  8: invalid_plugin_name
8/38 Test  #8: invalid_plugin_name ..............***Failed  Required regular expression not found. Regex=[failed to execute test
]  0.00 sec
      Start  9: plugin_failed
9/38 Test  #9: plugin_failed ....................***Failed  Required regular expression not found. Regex=[Plugin returned error code 2
]  0.00 sec
      Start 10: wrong_error
10/38 Test #10: wrong_error ......................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output  but expected Invalid
]  0.00 sec
      Start 11: expect_failure
11/38 Test #11: expect_failure ...................***Failed  Required regular expression not found. Regex=[Plugin returned invalid return value This is a negative test
]  0.00 sec
      Start 12: verifier_failure
12/38 Test #12: verifier_failure .................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output Failed to load program
]  0.00 sec
      Start 13: invalid_register
13/38 Test #13: invalid_register .................***Failed  Required regular expression not found. Regex=[Invalid register: %r50
]  0.00 sec
      Start 14: invalid_offset
14/38 Test #14: invalid_offset ...................***Failed  Required regular expression not found. Regex=[Failed to decode register and offset: %r1
]  0.01 sec
      Start 15: invalid_operand_count
15/38 Test #15: invalid_operand_count ............***Failed  Required regular expression not found. Regex=[Invalid number of operands for mnemonic: lddw
]  0.00 sec
      Start 16: invalid_label
16/38 Test #16: invalid_label ....................***Failed  Required regular expression not found. Regex=[Invalid label: NOT_A_LABEL
]  0.00 sec
      Start 17: invalid_mnemonic
17/38 Test #17: invalid_mnemonic .................***Failed  Required regular expression not found. Regex=[Invalid mnemonic: ldxq
]  0.01 sec
      Start 18: libbpf_plugin_usage
18/38 Test #18: libbpf_plugin_usage ..............***Failed  Required regular expression not found. Regex=[usage:
]  0.01 sec
      Start 19: invalid_lock
19/38 Test #19: invalid_lock .....................***Failed  Required regular expression not found. Regex=[Invalid number of operands
]  0.01 sec
      Start 20: invalid_lock2
20/38 Test #20: invalid_lock2 ....................***Failed  Required regular expression not found. Regex=[Invalid number of operands for lock
]  0.01 sec
      Start 21: include_test
21/38 Test #21: include_test .....................***Failed  Required regular expression not found. Regex=[PASS
]  0.01 sec
      Start 22: exclude_test
22/38 Test #22: exclude_test .....................***Failed  Required regular expression not found. Regex=[SKIP
]  0.00 sec
      Start 23: negative_include_test
23/38 Test #23: negative_include_test ............***Failed  Required regular expression not found. Regex=[SKIP
]  0.01 sec
      Start 24: negative_exclude_test
24/38 Test #24: negative_exclude_test ............***Failed    0.00 sec
      Start 25: usage
25/38 Test #25: usage ............................***Failed  Required regular expression not found. Regex=[Options:
]  0.01 sec
      Start 26: missing_test_path
26/38 Test #26: missing_test_path ................***Failed  Required regular expression not found. Regex=[test_file_path or test_file_directory
]  0.01 sec
      Start 27: missing_plugin_path
27/38 Test #27: missing_plugin_path ..............***Failed  Required regular expression not found. Regex=[plugin_path is required
]  0.01 sec
      Start 28: invalid_cpu_version
28/38 Test #28: invalid_cpu_version ..............***Failed  Required regular expression not found. Regex=[Invalid CPU version
]  0.00 sec
      Start 29: invalid_test_directory
29/38 Test #29: invalid_test_directory ...........***Failed  Required regular expression not found. Regex=[No such file or directory
]  0.00 sec
      Start 30: fail_with_error
30/38 Test #30: fail_with_error ..................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output
]  0.01 sec
      Start 31: unknown_directive
31/38 Test #31: unknown_directive ................***Failed  Required regular expression not found. Regex=[Test file has no BPF instructions.
]  0.01 sec
      Start 32: libbpf_program_bytes
32/38 Test #32: libbpf_program_bytes .............***Failed  Required regular expression not found. Regex=[0
]  0.01 sec
      Start 33: invalid_option
Could not find executable /home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
Looked in the following places:
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Release/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Release/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Debug/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Debug/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/MinSizeRel/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/MinSizeRel/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/RelWithDebInfo/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/RelWithDebInfo/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Deployment/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Deployment/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Development/bpf_conformance_runner
/home/ubuntu/ubpf/build/external/bpf_conformance/bin/Development/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Release/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Release/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Debug/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Debug/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/MinSizeRel/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/MinSizeRel/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/RelWithDebInfo/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/RelWithDebInfo/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Deployment/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Deployment/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Development/bpf_conformance_runner
home/ubuntu/ubpf/build/external/bpf_conformance/bin/Development/bpf_conformance_runner
Unable to find executable: /home/ubuntu/ubpf/build/external/bpf_conformance/bin/bpf_conformance_runner
33/38 Test #33: invalid_option ...................***Not Run   0.00 sec
      Start 34: list_used_instructions
34/38 Test #34: list_used_instructions ...........***Failed  Required regular expression not found. Regex=[Instructions used by tests
]  0.01 sec
      Start 35: list_unused_instructions
35/38 Test #35: list_unused_instructions .........***Failed  Required regular expression not found. Regex=[Instructions not used by tests
]  0.00 sec
      Start 36: back_compat
36/38 Test #36: back_compat ......................***Failed    0.01 sec
      Start 37: map_TEST_INTERPRET
37/38 Test #37: map_TEST_INTERPRET ...............   Passed    0.00 sec
      Start 38: map_TEST_JIT
38/38 Test #38: map_TEST_JIT .....................   Passed    0.00 sec

5% tests passed, 36 tests failed out of 38

Total Test time (real) =   0.32 sec

The following tests FAILED:
          1 - cpu_v1 (Failed)
          2 - cpu_v2 (Failed)
          3 - cpu_v3 (Failed)
          4 - elf_format (Failed)
          5 - no_bpf_bytecode (Failed)
          6 - invalid_return_value (Failed)
          7 - wrong_output (Failed)
          8 - invalid_plugin_name (Failed)
          9 - plugin_failed (Failed)
         10 - wrong_error (Failed)
         11 - expect_failure (Failed)
         12 - verifier_failure (Failed)
         13 - invalid_register (Failed)
         14 - invalid_offset (Failed)
         15 - invalid_operand_count (Failed)
         16 - invalid_label (Failed)
         17 - invalid_mnemonic (Failed)
         18 - libbpf_plugin_usage (Failed)
         19 - invalid_lock (Failed)
         20 - invalid_lock2 (Failed)
         21 - include_test (Failed)
         22 - exclude_test (Failed)
         23 - negative_include_test (Failed)
         24 - negative_exclude_test (Failed)
         25 - usage (Failed)
         26 - missing_test_path (Failed)
         27 - missing_plugin_path (Failed)
         28 - invalid_cpu_version (Failed)
         29 - invalid_test_directory (Failed)
         30 - fail_with_error (Failed)
         31 - unknown_directive (Failed)
         32 - libbpf_program_bytes (Failed)
         33 - invalid_option (Not Run)
         34 - list_used_instructions (Failed)
         35 - list_unused_instructions (Failed)
         36 - back_compat (Failed)
Errors while running CTest
make: *** [Makefile:73: test] Error 8

Noticing that somehow by default the binary for bpf_conformance_runner is at the wrong place, so I manually cp build/bin/bpf_conformance_runner build/external/bpf_conformance/bin/ and got
Running tests...
Test project /home/ubuntu/ubpf/build
      Start  1: cpu_v1
1/38 Test  #1: cpu_v1 ...........................***Failed    0.32 sec
      Start  2: cpu_v2
2/38 Test  #2: cpu_v2 ...........................***Failed    0.12 sec
      Start  3: cpu_v3
3/38 Test  #3: cpu_v3 ...........................***Failed    0.15 sec
      Start  4: elf_format
4/38 Test  #4: elf_format .......................***Failed    0.16 sec
      Start  5: no_bpf_bytecode
5/38 Test  #5: no_bpf_bytecode ..................   Passed    0.01 sec
      Start  6: invalid_return_value
6/38 Test  #6: invalid_return_value .............   Passed    0.06 sec
      Start  7: wrong_output
7/38 Test  #7: wrong_output .....................   Passed    0.01 sec
      Start  8: invalid_plugin_name
8/38 Test  #8: invalid_plugin_name ..............   Passed    0.01 sec
      Start  9: plugin_failed
9/38 Test  #9: plugin_failed ....................   Passed    0.02 sec
      Start 10: wrong_error
10/38 Test #10: wrong_error ......................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output  but expected Invalid
]  0.01 sec
      Start 11: expect_failure
11/38 Test #11: expect_failure ...................   Passed    0.01 sec
      Start 12: verifier_failure
12/38 Test #12: verifier_failure .................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output Failed to load program
]  0.01 sec
      Start 13: invalid_register
13/38 Test #13: invalid_register .................   Passed    0.01 sec
      Start 14: invalid_offset
14/38 Test #14: invalid_offset ...................   Passed    0.01 sec
      Start 15: invalid_operand_count
15/38 Test #15: invalid_operand_count ............   Passed    0.02 sec
      Start 16: invalid_label
16/38 Test #16: invalid_label ....................   Passed    0.01 sec
      Start 17: invalid_mnemonic
17/38 Test #17: invalid_mnemonic .................   Passed    0.01 sec
      Start 18: libbpf_plugin_usage
18/38 Test #18: libbpf_plugin_usage ..............***Failed  Required regular expression not found. Regex=[usage:
]  0.01 sec
      Start 19: invalid_lock
19/38 Test #19: invalid_lock .....................   Passed    0.01 sec
      Start 20: invalid_lock2
20/38 Test #20: invalid_lock2 ....................   Passed    0.01 sec
      Start 21: include_test
21/38 Test #21: include_test .....................***Failed  Required regular expression not found. Regex=[PASS
]  0.01 sec
      Start 22: exclude_test
22/38 Test #22: exclude_test .....................   Passed    0.01 sec
      Start 23: negative_include_test
23/38 Test #23: negative_include_test ............   Passed    0.01 sec
      Start 24: negative_exclude_test
24/38 Test #24: negative_exclude_test ............***Failed    0.01 sec
      Start 25: usage
25/38 Test #25: usage ............................   Passed    0.01 sec
      Start 26: missing_test_path
26/38 Test #26: missing_test_path ................   Passed    0.01 sec
      Start 27: missing_plugin_path
27/38 Test #27: missing_plugin_path ..............   Passed    0.01 sec
      Start 28: invalid_cpu_version
28/38 Test #28: invalid_cpu_version ..............   Passed    0.01 sec
      Start 29: invalid_test_directory
29/38 Test #29: invalid_test_directory ...........   Passed    0.01 sec
      Start 30: fail_with_error
30/38 Test #30: fail_with_error ..................***Failed  Required regular expression not found. Regex=[Plugin returned error code 1 and output
]  0.01 sec
      Start 31: unknown_directive
31/38 Test #31: unknown_directive ................   Passed    0.01 sec
      Start 32: libbpf_program_bytes
32/38 Test #32: libbpf_program_bytes .............***Failed  Required regular expression not found. Regex=[0
]  0.01 sec
      Start 33: invalid_option
33/38 Test #33: invalid_option ...................   Passed    0.00 sec
      Start 34: list_used_instructions
34/38 Test #34: list_used_instructions ...........   Passed    0.12 sec
      Start 35: list_unused_instructions
35/38 Test #35: list_unused_instructions .........   Passed    0.12 sec
      Start 36: back_compat
36/38 Test #36: back_compat ......................***Failed    0.01 sec
      Start 37: map_TEST_INTERPRET
37/38 Test #37: map_TEST_INTERPRET ...............   Passed    0.00 sec
      Start 38: map_TEST_JIT
38/38 Test #38: map_TEST_JIT .....................   Passed    0.00 sec

68% tests passed, 12 tests failed out of 38

Total Test time (real) =   1.41 sec

The following tests FAILED:
          1 - cpu_v1 (Failed)
          2 - cpu_v2 (Failed)
          3 - cpu_v3 (Failed)
          4 - elf_format (Failed)
         10 - wrong_error (Failed)
         12 - verifier_failure (Failed)
         18 - libbpf_plugin_usage (Failed)
         21 - include_test (Failed)
         24 - negative_exclude_test (Failed)
         30 - fail_with_error (Failed)
         32 - libbpf_program_bytes (Failed)
         36 - back_compat (Failed)
Errors while running CTest
make: *** [Makefile:73: test] Error 8

It is better than the prior success rate (5%), still some tests failed.
I am wondering about what is missing, e.g., is it necessary to roll back the clang version to 3.7? Thanks!

Thanks Alan! The issue is resolved.

Hi Alan, I moved to another clean Ubuntu 20.04.06 LTS VM, but somehow there is a few tests failed, as attached below.
Note that I was running the same set up as before (which gave me 100% tests passed), it seems to be caused by some minor reason between the two VMs.
611/630 Test #611: invalid_lock .......................................................................   Passed    0.01 sec
        Start 612: invalid_lock2
612/630 Test #612: invalid_lock2 ......................................................................   Passed    0.01 sec
        Start 613: include_test
613/630 Test #613: include_test .......................................................................***Failed  Required regular expression not found. Regex=[PASS
]  0.01 sec
        Start 614: exclude_test
614/630 Test #614: exclude_test .......................................................................   Passed    0.02 sec
        Start 615: negative_include_test
615/630 Test #615: negative_include_test ..............................................................   Passed    0.01 sec
        Start 616: negative_exclude_test
616/630 Test #616: negative_exclude_test ..............................................................***Failed    0.01 sec
        Start 617: usage
617/630 Test #617: usage ..............................................................................   Passed    0.01 sec
        Start 618: missing_test_path
618/630 Test #618: missing_test_path ..................................................................   Passed    0.01 sec
        Start 619: missing_plugin_path
619/630 Test #619: missing_plugin_path ................................................................   Passed    0.01 sec
        Start 620: invalid_cpu_version
620/630 Test #620: invalid_cpu_version ................................................................   Passed    0.01 sec
        Start 621: invalid_test_directory
621/630 Test #621: invalid_test_directory .............................................................   Passed    0.01 sec
        Start 622: fail_with_error
622/630 Test #622: fail_with_error ....................................................................   Passed    0.01 sec
        Start 623: unknown_directive
623/630 Test #623: unknown_directive ..................................................................   Passed    0.01 sec
        Start 624: libbpf_program_bytes
624/630 Test #624: libbpf_program_bytes ...............................................................***Failed  Required regular expression not found. Regex=[0
]  0.01 sec
        Start 625: invalid_option
625/630 Test #625: invalid_option .....................................................................   Passed    0.00 sec
        Start 626: list_used_instructions
626/630 Test #626: list_used_instructions .............................................................   Passed    0.29 sec
        Start 627: list_unused_instructions
627/630 Test #627: list_unused_instructions ...........................................................   Passed    0.28 sec
        Start 628: back_compat
628/630 Test #628: back_compat ........................................................................***Failed    0.01 sec
        Start 629: map_TEST_INTERPRET
629/630 Test #629: map_TEST_INTERPRET .................................................................   Passed    0.00 sec
        Start 630: map_TEST_JIT
630/630 Test #630: map_TEST_JIT .......................................................................   Passed    0.00 sec

99% tests passed, 8 tests failed out of 630

Total Test time (real) =   7.54 sec

The following tests FAILED:
        593 - cpu_v1 (Failed)
        594 - cpu_v2 (Failed)
        595 - cpu_v3 (Failed)
        596 - elf_format (Failed)
        613 - include_test (Failed)
        616 - negative_exclude_test (Failed)
        624 - libbpf_program_bytes (Failed)
        628 - back_compat (Failed)
Errors while running CTest
make: *** [Makefile:73: test] Error 8

What's odd is that the two VMs have the same exact OS release (20.04.6 LTS (Focal Fossa)), clang version etc.
The only minor difference is that the VM with 100% tests passed has a slightly different kernel verision:
# The one with 100% tests
ubuntu@ip-172-31-80-18:~/ubpf$ uname -a
Linux ip-172-31-80-18 5.15.0-1036-aws #40~20.04.1-Ubuntu SMP Mon Apr 24 00:21:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
# The one with 99% tests
lc@vm1:~/ubpf/programs$ uname -a
Linux rcf-vm1 5.15.0-1038-azure #45~20.04.1-Ubuntu SMP Tue Apr 25 18:45:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux


Getting 400 error when trying to install

Problem/Motivation
When I try to add the repo in the add-on store using this url:
https://github.com/hassio-addons/repository
I get  a 400 error on the POST.

When I click "Install" on the Hass.io add-in store, I get a 400 error in the console and add-on does not install.

Expected behavior
Add-on would install   properly and allow settings editing and start/restart like normal.
Actual behavior
400 Error per above.
Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Could you please provide some system log output?

I don't really see anything being printed to the home-assistant.log file:
2018-05-19 10:56:14 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 308, in _async_add_entity
    msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: automation.notify_on_arrive_router
2018-05-19 10:56:23 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-05-19 10:56:48 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

So looks like I am getting 400 or 404 error for all the:
http://hassio.local:8123/api/hassio/*

Endpoint so I can't install any add-ons. Not sure what is causing this all of a sudden. Pls let me know if you have any suggestions but will post this on the hass.io issues as well.

Apologies for the multiple posts. I just confirmed I am able to install other add-ons, so it the issue looks specific to this add-on. I forgot I had already added the community add-on repo to my add-on store.

@rkpatel33 Not the Home Assistant logfile, but the Hass.io System log file.
You can find this one under Hass.io -> System.

Apologies, here is the hass.io log, the last line is what appeared after I clicked install:
18-05-19 19:25:42 INFO (MainThread) [hassio.updater] Fetch update data from https://raw.githubusercontent.com/home-assistant/hassio/master/version.json
18-05-19 19:25:42 INFO (MainThread) [hassio.addons.git] Pull addon https://github.com/home-assistant/hassio-addons repository
18-05-19 19:25:42 INFO (MainThread) [hassio.addons.git] Pull addon https://github.com/hassio-addons/repository repository
18-05-19 19:25:43 INFO (MainThread) [hassio.addons] Load addons: 34 all - 0 new - 0 remove
18-05-19 20:04:26 ERROR (MainThread) [hassio.addons.addon] Addon a0d7b954_ide not supported on armhf

Addon a0d7b954_ide not supported on armhf
The add-on is no longer available/supported on ARM-based devices (e.g., Raspberry Pi).
For more information about this, read the official statement:
https://community.home-assistant.io/t/community-hass-io-add-on-ide-based-on-cloud9/33810/57?u=frenck


[release-1.7] remove-from-mesh should also restore rewritten app probes

This is an automated cherry-pick of #26673

@googlebot I consent.


TSC Meeting 2021-11-03

Please add topics for the agenda as comments on this issue.
The standing agenda items are:

Review TSC issue backlog
Review TSC-tagged issues (toggle to "open" after checking for recently "closed" items)

@ampproject/tsc

I'd like to present on the following topics:

Launching Bento.
Cloudflare hosting OpenJS JS Cache.
Cadence of updates for TSC from Working Groups.

I'd like to review recent updates to the TSC and discuss going forward operating model


V3.6 pm

Hi @IshentRas , these are my proposed changes that I would like to push to your v3.6 branch.
The PR consists in 3 commits:

the first one to fix the bug I explained in https://github.com/IshentRas/cookbook-openshift3/pull/165#issuecomment-336898458 where standalone install would fail when node['cookbook-openshift3']['openshift_common_api_hostname'] != node['fqdn']
the second to remove most of the new "wait for nodes to be registred" code which I find brittle and with limited value, as explained in https://github.com/IshentRas/cookbook-openshift3/pull/165/commits/2d532f5718e194c3c33085202d2ae27ec33e2019#r144873808
the third one to update the README.md since all kitchen tests for v3.6.x will pass after applying the above 2 changes.

Please review then merge to your v3.6 branch, or merge them review once merged.

@IshentRas you merged my changes to v3.6 branch after merging that branch to master, so my changes are not on master (only on v3.6 branch). Can you merge v3.6 branch into master again?

Lol I know that is what happened when you tired to do stuff from your mobile phone... Ill fix it asap

@jperville It has now been merged. I think I understand what you are saying about the wait for node... It is pointless as the system will fix it by itself next time it runs the chef-client...
No need to be clever here or to over complicate stuff...:+1:


Twill 2.8.0-beta.1 Return value of A17\Twill\Services\Blocks\Block::getForType() must be an instance of A17\Twill

Description

upgrade to Twill 2.8.0-beta.1

Build Twill - look at front end
Expected result
Site not to break
Actual result
Return value of A17\Twill\Services\Blocks\Block::getForType() must be an instance of A17\Twill\Services\Blocks\Block, null returned
Versions

2.8.0-beta.1

8.83.3

7.4

posgres

Hey @michaeljcoyne
Thank you for reporting, was this on a clean installation?
Kind regards,

No

Hey @michaeljcoyne,
I am having trouble reproducing this issue.
Does this happen on /admin or on the edit page of a specific model?
All information that you can give will help us.
Kind regards,

@michaeljcoyne if you have this error again, could you send a backtrace here?

@haringsrob
I tried upgrading the error and persists.
The gist of it is if I have a browser block previously I would be able to do this on front end.
`@php
$background = \App\Models\Background::find($item->background_id);
@endphp
@if($background)
{!! $background->renderBlocks() !!}
@endif
`
The render blocks would not throw an error.  I am assuming something has changed in the HasBlocks trait  or something related to this to break this.
Not sure what the easiest way to copy the stack trace out of Debug bar is.

If I revert
075aea60c2bc5c04a7e57ccd0f438ee77c83cf42
the error goes away.

Hi, I was able to reproduce this one. The error is thrown when a repeater is used inside a block.
https://github.com/area17/twill/blob/075aea60c2bc5c04a7e57ccd0f438ee77c83cf42/src/Models/Behaviors/HasBlocks.php#L37
The issue is repeater parameter is not passed to getForType method. Hope it helps

Thanks that helps @amsal
Fix is here: https://github.com/area17/twill/pull/1518

Good stuff - forgot to mention it was in a repeater, soz :)


Create l10n_cz.xml

@SniperKittenCZ  Follow-up - all the UI settings are now in game, which require quite a few more translated strings!
see https://github.com/GMNGjoy/FS25_ContractBoost/issues/26 for more information.


Stencil: add support for Nx 19

Is your feature request related to a problem? Please describe.
Currently, we're not able to upgrade to Nx 19 due to an unresolved dependency tree.

To be able to update to the latest Nx version, I'm forced to override @nxext/stencil dependency tree as follows:
"@nxext/stencil": {
  "@nx/eslint": "$@nx/eslint",
  "@nx/jest": "$@nx/jest",
  "@nx/react": "$@nx/react",
  "@nx/storybook": "$@nx/storybook",
  "@stencil/core": "$@stencil/core"
}

Describe the solution you'd like
I would like to be able to update to the latest Nx without the need to override the dependency tree.
Describe alternatives you've considered
Peer dependencies related to Nx in packages/stencil/package.json should allow Nx 19 as well:
"peerDependencies": {
  "@nxext/svelte": "^18.0.0",
  "@nx/cypress": "^18.0.8",
  "@nx/storybook": "^18.0.8",
  "@nx/jest": "^18.0.8",
  "@nx/react": "^18.0.8",
  "@nx/eslint": "^18.0.8"
},

Additional context
Add any other context or screenshots about the feature request here.

Closing this, I've tested the latest version and everything works as expected.


Wrong documentation

A correct documentation could be for example: Combining method 4 with the match interpolation of method 5 (cf. http://acl2014.org/acl2014/W14-33/pdf/W14-3346.pdf)
https://github.com/nltk/nltk/blob/39d8eeb2f249ad67d11300d97971f972039bdc63/nltk/translate/bleu_score.py#L635-L640

Thanks @dschaehi! Good catch on the documentation, that docstring is describing method 6 and copied and pasted partially.
Yes, the documentation you suggested is correct =)

Smoothing method 7:
Combining method 4 with the match interpolation of method 5.

@dschaehi if it's alright, lets keep the issue open until a pull-request is made to fix the docs =)

Sure :-)

The documentation has been changed by @stevenbird in commit 199e764, but it is still not correct. It should be methods 4 and 5

looks like this was corrected?
https://github.com/nltk/nltk/blob/develop/nltk/translate/bleu_score.py#L634

Yes, I can close it now.


convert to platform-agnostic pipeline

switch modules to containers (#42)
remove any biowulf-specific code from driver script

test run command to modify
/data/Ziegelbauer_lab/Pipelines/circRNA/v0.10.1/charlie -w=/data/Ziegelbauer_lab/circRNADetection/circRNA_daq_v0.10.x/samples_15 -m=init -g=hg38 -v=NC_009333.1,KT899744.1,NC_006273.2 -s /data/Ziegelbauer_lab/circRNADetection/circRNA_daq_v0.10.x/samples_15.tsv

Created a new samples.tsv file with just 4 samples from Vishal's samples_15.tsv.
/data/Ziegelbauer_lab/Pipelines/circRNA/v0.10.1/charlie \
    -w=/data/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_v0.10.1 \
    -m=init -g=hg38 -v=NC_009333.1,KT899744.1,NC_006273.2 \
    -s=/data/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/samples.tsv

Testing containerized version:
/data/Ziegelbauer_lab/Pipelines/circRNA/v0.10.1/charlie \
    -w=/data/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev \
    -m=init -g=hg38 -v=NC_009333.1,KT899744.1,NC_006273.2 \
    -s=/data/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/samples.tsv

/usr/bin/bash: line 32: fastq-filter: command not found
need to add to cutadapt docker

create_index failed due to missing output files
MissingOutputException in rule create_index in file /vf/users/Ziegelbauer_lab/Pipelines/circRNA/charlie-dev-sovacool/workflow/rules/create_index.smk, line 4:
Job 0 completed successfully, but some output files are missing. Missing files after 120 seconds. This might be due to filesystem latency. If that is the case, consider to increase the wait time with --latency-wait:
/vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/NCLscan_index/AllRef.ndx
Removing output files of failed job create_index since they might be corrupted:
/vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.genes.genepred_w_geneid, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/STAR_no_GTF/SA, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.fixed.gtf, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.transcripts.fa, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.dummy.fa, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/separate_fastas/separate_fastas.lst
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message

test on FRCE
/home/sovacoolkl/CHARLIE \
    -w=/scratch/cluster_scratch/sovacoolkl/charlie_dev_test/charlie_iss-99 \
    -m=init -g=hg38 -v=NC_009333.1,KT899744.1,NC_006273.2 \
    -s=/scratch/cluster_scratch/sovacoolkl/charlie_dev_test/samples.tsv

error in rule DCC
Activating singularity image /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/.snakemake/singularity/b688737477c8cf86b329e4227da72916.simg
+ '[' -d /lscratch/25273199 ']'
+ TMPDIR=/lscratch/25273199/09975c64-8e35-4c64-bd19-c0afbf581a78
+ '[' '!' -d /lscratch/25273199/09975c64-8e35-4c64-bd19-c0afbf581a78 ']'
+ mkdir -p /lscratch/25273199/09975c64-8e35-4c64-bd19-c0afbf581a78
++ dirname /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/CircRNACount
+ cd /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC
+ '[' PE == PE ']'
+ DCC @/vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/samplesheet.txt \
    --temp /lscratch/25273199/09975c64-8e35-4c64-bd19-c0afbf581a78/DCC --threads 4 --detect --gene \
    --bam /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/STAR2p/G1_Normal_p2.bam \
    -ss \
    --annotation /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.fixed.gtf \
    --chrM -G --rep_file /data/CCBR_Pipeliner/db/PipeDB/charlie/fastas_gtfs/hg38.repeats.gtf \
    --refseq /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.fa \
    --PE-independent \
    -mt1 @/vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/mate1.txt \
    -mt2 @/vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/mate2.txt
[W::hts_idx_load3] The index file is older than the data file: /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/STAR2p/G1_Normal_p2.bam.csi
Traceback (most recent call last):
  File "/usr/local/bin/DCC", line 11, in <module>
    load_entry_point('DCC==0.5.0', 'console_scripts', 'DCC')()
  File "/usr/local/lib/python3.8/dist-packages/DCC-0.5.0-py3.8.egg/DCC/main.py", line 490, in main
  File "/usr/local/lib/python3.8/dist-packages/DCC-0.5.0-py3.8.egg/DCC/main.py", line 679, in findCircSkipJunction
  File "/usr/local/lib/python3.8/dist-packages/DCC-0.5.0-py3.8.egg/DCC/Circ_nonCirc_Exon_Match.py", line 281, in findcircAdjacent
  File "/usr/local/lib/python3.8/dist-packages/DCC-0.5.0-py3.8.egg/DCC/Circ_nonCirc_Exon_Match.py", line 222, in getAdjacent
ValueError: invalid literal for int() with base 10: '3"'
[Tue Apr 30 00:44:26 2024]
Error in rule dcc:
    jobid: 0
    input: /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/samplesheet.txt, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/mate1.txt, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/mate2.txt, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/STAR2p/G1_Normal_p2.bam, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/ref/ref.fixed.gtf
    output: /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/CircRNACount, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/CircCoordinates, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/LinearCount, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/G1_Normal.dcc.counts_table.tsv, /vf/users/Ziegelbauer_lab/circRNADetection/sovacoolkl_charlie/charlie_dev/results/G1_Normal/DCC/G1_Normal.dcc.counts_table.tsv.filtered
    shell:

error on FRCE
sbatch: error: Invalid generic resource (gres) specification
Error submitting jobscript (exit code 1):

Looks like the DCC devs are aware of the issue and fixed it in the master branch -- https://www.github.com/dieterich-lab/DCC/issues/103

First run-through on biowulf completed successfully after several bug fixes. Re-rerun from start to finish completed successfully on biowulf. Test in progress on frce.

more problems on FRCE:
sbatch: error: CPU count per node can not be satisfied
sbatch: error: Batch job submission failed: Requested node configuration is not available

Currently running on FRCE with improved handling of config & cluster templates

error on FRCE:
SystemExit in file /home/sovacoolkl/CHARLIE/workflow/rules/init.smk, line 20:
File: /mnt/projects/CCBR-Pipelines/db/charlie/fastas_gtfs/hg38.fa does not exists!
  File "/home/sovacoolkl/CHARLIE/workflow/Snakefile", line 19, in <module>
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 190, in <module>
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 29, in check_readaccess
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 20, in check_existence
SystemExit in file /home/sovacoolkl/CHARLIE/workflow/rules/init.smk, line 20:
File: /mnt/projects/CCBR-Pipelines/db/charlie/fastas_gtfs/hg38.fa does not exists!
  File "/home/sovacoolkl/CHARLIE/workflow/Snakefile", line 19, in <module>
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 190, in <module>
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 29, in check_readaccess
  File "/home/sovacoolkl/CHARLIE/workflow/rules/init.smk", line 20, in check_existence

even though the file does exist 🤔
file /mnt/projects/CCBR-Pipelines/db/charlie/fastas_gtfs/hg38.fa

/mnt/projects/CCBR-Pipelines/db/charlie/fastas_gtfs/hg38.fa: ASCII text, with very long lines

upgraded snakemake in the shared conda env on FRCE to v7
conda activate /mnt/projects/CCBR-Pipelines/conda/envs/snakemake
mamba install -c bioconda snakemake=7.32.4

on FRCE, star_circrnafinder hangs indefinitely and gets cancelled by slurm, but actually completes successfully in < 3 hours when run interactively.


ImportError: module could not be found - Windows 10

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10.0.17134.407
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Binary
TensorFlow version: 1.12.0
Python version: 3.6.7
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): NA
GCC/Compiler version (if compiling from source): NA
CUDA/cuDNN version: 10.0.130 / <IP_ADDRESS> for Win 10
GPU model and memory: Quadro M520

Describe the problem
tensorflow fails on import with "module could not be found".  Other issue says to open a new issue due to differing config (https://github.com/tensorflow/tensorflow/issues/22794)
Provide the exact sequence of commands / steps that you executed before running into the problem

python
import tensorflow as tf

Any other info / logs
Python 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 13:35:33) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
Traceback (most recent call last):
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow_init_.py", line 24, in
from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python_init_.py", line 49, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 74, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\marktayl\AppData\Local\Programs\Python\Python36\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Duplicate of #23726


Need recursion protection ...

If the server goes into an infinite loop either via workspace or Rowan (my case:), there needs to be a way to terminate the process ... short of killing the gem, since killing the gem means that a developer will lose uncommitted work ...

@dalehenrich There are two options that already exist:

Console>Browse Processes allows you to debug or terminate server processes. (Right mouse Refresh may be needed)
Ctrl-F12 will interrupt the gci call in the Dolphin gui.

Let me know if these aren't sufficient.

I created an infinite loop in server code, and neither of these techniques helps.  User interrupts show a dialog but don't effect the looping; and I can't get the browse processes to open anything.  Appears totally wedged.

The good news is that it actually did eventually put up an almost out of stack exception, which I closed, and no work was lost.  But "wait it out" might not be a preferred workaround.

In order to fix this issue, needed to override base method ProcessorScheduler>>userBreak: Dolphin (at least this version doesn't seem to have the concept of code overrides) throws a resumable error if you define a method in two packages.
To get around this annoying problem, I created a new package Rowan UI Base PreInstall whose sole job for the moment is to remove the base version of userBreak:before loading package Rowan UI Base. This avoids the method conflict error. Note - doing it in the pre-install package script didn't work because the conflict error comes before the preinstall script runs which is rather silly.
The fix for this problem involves sending a soft break to the session (if available) before the process is interrupted (usually with Ctrl-F12). Then after the User Interrupt message box is raised, we send a no-op server string execution to force the soft break error to be raised.
Here is how it will look in 3.0.77 (screen shots from runtime image)

Press OK:

Press Debug:


Provide timings for each tasks

Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
We have a monorepo now with multiple apps and remote cache, so now it can be difficult to see if a optimization actually improves the speed of task.
Describe the solution you'd like
Allow giving a CLI argument --timing outputing how long each task took.
Describe alternatives you've considered
Timings could also be written to a json file which could be read by the CI if needed.

Hey @kevinsimper , I'm actively working on this. Keep an eye out for 1.9 release! I'm kind of keeping track of everything we're going to give you access to in https://github.com/vercel/turbo/pull/3431, but that PR itself is probably never getting merged (it's just my prototype work that I'm splitting off into reviewable / production worthy code)

Hey @kevinsimper this is now available in the latest canary. Try out the --summarize flag on any turbo run. Docs coming in https://github.com/vercel/turbo/pull/4467, when we have a stable release out.


Failed to import - react-svg-spinners

Failing module

GitHub: https://github.com/dephraiim/react-svg-spinners
npm: https://www.npmjs.com/package/react-svg-spinners

import { NinetyRing } from<EMAIL_ADDRESS>
Error message
After running deno run I got this:
error: Uncaught (in promise) SyntaxError: The requested module<EMAIL_ADDRESS>does not provide an export named 'NinetyRing'
  await import(entrypoint);

Additional info

esm.sh version: v106
Deno version: 1.30.0

default import seems to work. It contains all components on a POJO.

the server can not resolve the cjs exports correctly, so i just added ?cjs-export option as workaround for it

try
import { NinetyRing, NinetyRingWithBg } from "https://esm.sh/react-svg-spinners@0.3.1?cjs-exports=NinetyRing,NinetyRingWithBg"

@ije Amazing! Thank you for the quick turn-around.


LPAL-272 Cypress lpa clone tests

Purpose
LPAL-272 Cypress lpa clone tests
Approach

Cypress tests for LPA PF Clone that resemble Casper tests and Cypress PF not cloned tests.
New LpaTypePFClone.feature for cloning the lpa, which now gets stitched to rest of PF features,
Use Cypress env var to set whether cloned or not.
Modified existing PF feature files to be agnostic as to whether a clone or not, to avoid these being duplicated
Removed final references to old-style -  now add elements are address by data-cy names
when-no-capacity test formerly in casper's clone test, now in standard DonorPF test

Checklist

[x] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[x] I have added tests to prove my work
[ ] I have added mandatory tags to terraformed resources, where possible
[ ] If I added a package.json or composer.json, I also made sure this is included in the script in .github/workflows/dependabot-update.yml
[ ] The product team have tested these changes

Also: saw this rather odd comment in the CI test run:
CypressError: Timed out retrying after 12050ms: cy.click() failed because this element is detached from the DOM.
I haven't seen this with any of our other tests, and I'm wondering if we need to be concerned about it.

Also: saw this rather odd message in the CI test run:
CypressError: Timed out retrying after 12050ms: cy.click() failed because this element is detached from the DOM.
I haven't seen this with any of our other tests, and I'm wondering if we need to be concerned about it. Is this likely to be because of the clone popup disappearing when you select something to clone? It suggests there might be an issue with ordering in the test (e.g. looking for an element after it's been dismissed) or an issue with the button not being ready.

Indeed, it is intermittent. I will look a bit more at it to see if insisting on something being ready will fix it

Also: saw this rather odd message in the CI test run:
CypressError: Timed out retrying after 12050ms: cy.click() failed because this element is detached from the DOM.
I haven't seen this with any of our other tests, and I'm wondering if we need to be concerned about it. Is this likely to be because of the clone popup disappearing when you select something to clone? It suggests there might be an issue with ordering in the test (e.g. looking for an element after it's been dismissed) or an issue with the button not being ready.

Known issue with cypress :  https://github.com/cypress-io/cypress/issues/7306.   Have added some force click in and some extra checking items exist, to try to alleviate this


[EntityQueries] - Adding EntityQueryKind to EntityQueries and changing Properties to Expansion properties

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

this API didn't receive any direct call for the past 30 days.
only calls from our extension

clientApplicationId
count_
AppName

c44b4083-3bb0-49c1-b47d-974e53cbdf3c
55610
Portal

Hi @ori-licht, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ma/swaggerfeedback.

@ori-licht , could you please follow the action above for the breaking change review policy?


Add icingadb compability to enhanced mail

Hi!
Thanks for that great mail notification script - it looks pretty good and my customer quite likes it!
However, it does not seem to be compatible with icingadb atm.
Did a bit of monkey patching to "fix" this by replacing some URLs.
Will provide an PR for it with my quick and dirty fix, but maybe it would be better to have an variable to toggle between icingadb and monitoring?

The script needs to be updated to support IcingaDB. I've created a branch 3-icingadb-links for it.
I think the best solution here would be new configuration setting in  class SettingsIcinga with a default value and then use that var to set the right values.
Happy to take a PR @MisterMountain.


Exception: Cannot load CDF C library; checked . Try 'os.environ["CDF_LIB"] = library_directory' before import.

Hi,
I am trying to train the model on my custom dataset but while running ths script i get the below error:
I have already installed cdflib as per given in the repo but still error persists.
Traceback (most recent call last):
File "src/predict_3dpose.py", line 13, in
import data_utils
File "/home//src/data_utils.py", line 9, in
import xml_to_dataframe
File "/home/src/xml_to_dataframe.py", line 9, in
from spacepy import pycdf
File "/home//anaconda3/envs/3d-pose/lib/python3.6/site-packages/spacepy/pycdf/init.py", line 1303, in
'before import.').format(', '.join(_libpath)))
Exception: Cannot load CDF C library; checked . Try 'os.environ["CDF_LIB"] = library_directory' before import.
I even trying seeting the library path :+1:

import os
os.environ["CDF_LIB"] = "/home/yukti/anaconda3/envs/3d-pose/lib/python3.6/site-packages/cdflib"
from spacepy import pycdf
Still error persists.
Please suggest if i missed something.

os.environ["CDF_LIB"] = "/home/yukti/anaconda3/envs/3d-pose/lib/python3.6/site-packages/cdflib"

That looks like the path to the python wrapper of CDF. Try installing the library from https://cdf.gsfc.nasa.gov/

This is where cdf is installed .
I installed cdf using pip as per the repo instructions.
pip install cdflib

Actually I'm not sure why you're seeing that error.
Traceback (most recent call last):
File "src/predict_3dpose.py", line 13, in
import data_utils
File "/home//src/data_utils.py", line 9, in
import xml_to_dataframe
...

Line 9 of src/data_utils.py does not have import xml_to_dataframe
Please only open issues to ask questions about the code in this repo, not about changes that you have made locally, or code that you obtained elsewhere.

Actually I'm not sure why you're seeing that error.
Traceback (most recent call last):
File "src/predict_3dpose.py", line 13, in
import data_utils
File "/home//src/data_utils.py", line 9, in
import xml_to_dataframe
...

Line 9 of src/data_utils.py does not have import xml_to_dataframe
Please only open issues to ask questions about the code in this repo, not about changes that you have made locally, or code that you obtained elsewhere.

I have checked it has. The problem is CDF library. It is not able to read the CDF library.

Like I said, you are working with some old version of this code, or you are using code from somewhere else:
https://github.com/una-dinosauria/3d-pose-baseline/blob/666080d86a96666d499300719053cc8af7ef51c8/src/data_utils.py#L7-L14
No spacepy or xml_to_dataframe is to be found on the code of this repository. Double check what you have downloaded and try again -- I am muting this thread

No I am using code of this repo only as i am training on my custom dataset so the dataset is in xml which is then converted using pandas.


Docs: Refresh README.md; add a NuGet-specific one

As anyone can tell, NuGet hates inline HTML. So, I created a NuGet specific README that's more simplified and doesn't contain anything particularly special.
I also rewrote the existing README to make it look prettier. Enjoy!

Any updates on the rest of the requested changes before I take over?

Oops, sorry I forgot about this. I'll try do it soon...

lm*o

Done!
You might also want to consider simplifying the CI name 🙂

I thought about it but the title should explain what the action does in a comprehensive way, I could try to somehow separate the NuGet publishing logic from building and leave the building part in the README, but it's out of scope.


GPG error : exit status 2

I have a GPG error when i try to add my own PGP key but i can use this key with Enigmail in Thunderbird.
▶ ERROR GPG error: exit status 2
I have try: keybase config set gpg.command gpg2
Now i have: ▶ ERROR stat gpg2: no such file or directory
my log id: 228f5dc187a92d604b59b51c
Ty for help

It can't find gpg

But when i try gpg2 --list-secret-keys i see my key

specify the absolute path
keybase config set gpg.command /path/to/your/gpg

I get my first error: ▶ ERROR GPG error: exit status 2
I've try: keybase config set gpg.command /usr/bin/gpg2 and keybase config set gpg.command /usr/bin/gpg
same result

i can take a quick look if you send me another keybase log send

my log id: 3b3109b2e9ff5083f25e511c

You have some local GPG misconfiguration you'll have to debug on your own:
7326 2017-02-13T16:56:01.970120 ▶ [DEBU keybase gpg_cli.go:332] 1c7d gpg: starting migration from earlier GnuPG versions
7327 2017-02-13T16:56:01.970590 ▶ [DEBU keybase gpg_cli.go:332] 1c7e gpg: porting secret keys from '/home/hugo/.gnupg/secring.gpg' to gpg-agent
7328 2017-02-13T16:56:01.970656 ▶ [DEBU keybase gpg_cli.go:332] 1c7f gpg: impossible d'ouvrir « /home/hugo/.gnupg/secring.gpg » : Permission non accordée
7329 2017-02-13T16:56:01.972002 ▶ [DEBU keybase engine.go:66] 1c80 - RunEngine(GPGImportKeyEngine) -> ERROR: GPG error: exit status 2

secring.gpg:
53497656 -rw-------  1 root root      0 oct.  18 20:46 secring.gpg

@GotExx It's owned by root instead of the user you're running as (and it's empty).

Yes, this does not cause any security problems if secring.gpg belongs to the user and not a root ?

We're pretty busy over here, you're on your own!

yeah ofc thank's a lot


[INTEGRATION][SPARK] Support for Spark 3.3.0

Spark 3.3.0 has been realized on 16th July 2022.
We still need to wait for a docker image -> https://hub.docker.com/r/bitnami/spark/tags?page=1&name=3.3
After that we can turn on integration tests for the latest Spark version and see how is it working.

Although bitnami docker image is already available, we still need to wait for iceberg & delta support:

https://github.com/delta-io/delta/issues/1217
https://github.com/apache/iceberg/pull/5056

Draft PR on our side:

https://github.com/OpenLineage/OpenLineage/pull/896

Is Delta already supported as a format in OpenLineage? :)

@LucaSoato Yes, OpenLineage calls Delta a provider and is able to detect provider like delta or iceberg from query plans.


clang-format -i (All Dash Related Files)

This applies clang-format -i to all Dash specific files.
Includes for std::string and std::vector had to be added to masternodeconfig.h to allow successful build.

If we're going to add this, we should probably (eventually?) add some kind of CI check for formatting also, otherwise eventually we'll get out of skew with clang-format rules again and have to do other formatting PRs in the future.

What this has showed us is that the includes for all files need looking at.


Add exampling showing how to use ParetoSmooth

Hi,
A few days ago on Discourse, someone described a problem with ParetoSmooth in which the wrong (or at least unexpected) sample size was used. It turns out this is related to an old issue already reported. For example, ParetoSmooth produces different results given two formally equivalent Turing models:
Model  1
using Turing
using ParetoSmooth
using Distributions

@model function model(data)
    μ ~ Normal()
    data ~ Normal(μ, 1)
end

data = rand(Normal(0, 1), 100)

chain = sample(model(data), NUTS(), 1000)
rez1 = psis_loo(model(data), chain)

Model 2
using Turing
using ParetoSmooth
using Distributions

@model function model(data)
    μ ~ Normal()
    for i in 1:length(data)
        data[i] ~ Normal(μ, 1)
    end
end

data = rand(Normal(0, 1), 100)

chain = sample(model(data), NUTS(), 1000)
rez1 = psis_loo(model(data), chain)

The only thing that differs is the use of a for loop. Unfortunately, this distinction was not clear and we wasted time trying to figure out the problem.  Until a solution is added, I think it would be good to add an example explaining how to make a model work properly with ParetoSmooth.  I would be willing to make a PR. Is it the case that for loop or .~ is the recommended approach?

Yes, I think a PR would be great. As I mentioned in that issue, the ideal situation is to change the interface for ParetoSmooth.jl (or potentially ArviZ.jl, which frankly is probably the better package for LOO-CV this at this point) to take as input both a model and a dataset, where the dataset should be given as an iterator over IID observations. Then, the algorithm proceeds by removing each data point from the dataset one at a time and calculating the appropriate LOO distribution.

Sounds good. I will submit a PR to update the documentation later this week or during the weekend.
Do you have plans for changing the interface?


Screen output on node_manager not working

Hi,
I recently updated the node_manager, I am not able to output node to the terminal anymore.
A snippet from /var/log/dpkg.log
2019-12-02 17:14:24 upgrade ros-kinetic-node-manager-fkie:amd64 0.8.11-0xenial-20190227-103017-0800 0.8.12-0xenial-20191029-002604+0000
When I click the output button on node_manager, the terminal that runs node_manager outputs:
[INFO] [1576578161.392919]: Open screen terminal: /usr/bin/x-terminal-emulator -T "SCREEN /omav/omav_allocation_node on weixuan-blade"  -e /usr/bin/screen -x 6913._omav_omav_allocation_node
But no external screen is spawn.
My system setup:
System: Ubuntu 16.04,
ROS: kinetic
Terminal: terminator 1.91
When I run "sudo update-alternatives --config x-terminal-emulator"
I choose

0            /usr/bin/terminator.wrapper       50        auto mode

Any help much appreciated! Thanks!

Hi,
can you please check two things (in separate terminal):

Is the screen running: screen -ls
Does screen open if you run: /usr/bin/x-terminal-emulator -T "SCREEN /omav/omav_allocation_node on weixuan-blade" -e /usr/bin/screen -x 6913._omav_omav_allocation_node <-- This is the line which node_manager prints and executes to open screen terminal

Thank you very much for your quick response!

When I run screen -ls:
There are screens on:
7369._omav_spawn_omav	(17.12.2019 11:22:36)	(Detached)
7081._omav_omav_controller_node	(17.12.2019 11:22:36)	(Detached)
6913._omav_omav_allocation_node	(17.12.2019 11:22:35)	(Detached)
6832._omav_local_planner	(17.12.2019 11:22:35)	(Detached)
6727._omav_full_pose_waypoint_node	(17.12.2019 11:22:35)	(Detached)
3654._roscore--11311	(17.12.2019 11:14:50)	(Detached)
They are the running nodes in the node manager.
6 Sockets in /var/run/screen/S-weixuan.

2.When I run  /usr/bin/x-terminal-emulator -T "SCREEN /omav/omav_allocation_node on weixuan-blade" -e /usr/bin/screen -x 6913._omav_omav_allocation_node
I get
terminator: error: Additional unexpected arguments found: ['/omav/omav_allocation_node', 'on', 'weixuan-blade']
Thanks!

I tested it with terminator v1.91 on Ubuntu 18.04 and the command line works.
I think it is something with selected alternatives for x-terminal-emulator. Can you change it to terminator?

Thank you very much for your input! Indeed it has something to do with the selected alternatives for x-terminal-emulator. The catch is that I installed the terminator 1.91 from ppa:gnome-terminator/nightly-gtk3. When setting default terminal, I have to switch from /usr/bin/terminator.wrapper to  /usr/bin/gnome-terminal.wrapper. I will close this issue.


avidemux-nightly: add version 220130

Relates to https://github.com/ScoopInstaller/Extras/pull/7926

So users can test the next version of Avidemux

No hashes available

[x] I have read the Contributing Guide.

/verify

Looks like appveyor tests do not like the space in the middle of the download url:
https://www.avidemux.org/nightly/win64/avidemux_2.8.1 r220130_win64.exe#/dl.7z
                                                     ^

So can we replace the space with a %20 in the manifest?

Yes we can, I'll redo the regex so I can put a %20 in the autoupdate URL too

/verify


feat: update xcall sendcall message

Description:
Commit Message
feat: update xcall sendcall message

see the guidelines for commit messages.
Checklist:

[x] I have performed a self-review of my own code
[x] I have documented my code in accordance with the documentation guidelines
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[x] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Codecov Report

Merging #330 (35e9930) into main (2b3667d) will increase coverage by 32.89%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #330       +/-   ##
=============================================
+ Coverage     47.12%   80.01%   +32.89%
- Complexity        0      421      +421
=============================================
  Files            95       27       -68
  Lines         16073     2037    -14036
  Branches          0      284      +284
=============================================
- Hits           7574     1630     -5944
+ Misses         8499      266     -8233
- Partials          0      141      +141

see 122 files with indirect coverage changes


Remove the necessity to specify archive flags on the receiving end

everything is fine

This fixes the problem I was having with mismatched encode/decode of parcels


uGUI Overlay Canvas Support

Support for the new unity gui system and an overlay canvas would be nice. Currently my work around is to place the canvas in my game and to position it in front of the cardboard. My solution does not work very well and I end up with two version of my UI.

There's a GazeInputModule script in the project that works with uGUI, but
it needs a worldspace canvas in order to render in stereo.
-- Scott
On Fri, May 22, 2015 at 5:23 PM, Nicholas Ventimiglia <
<EMAIL_ADDRESS>wrote:

Support for the new unity gui system and an overlay canvas would be nice.
—
Reply to this email directly or view it on GitHub
https://github.com/googlesamples/cardboard-unity/issues/31.

I was able to get it to work, thanks.


tuya_iot getting error "Failed to establish a new connection"

I am getting a error where the API intermittently will fail to connect.
From what I can tell, the error causes the Tuya integration in Home Assistant to stop tracking device state. I have two devices, a light and a heat pump, and both are "frozen" in time after the error occurs. A reboot will usually fix the issue (presumably at the time of the reboot, the API is responsive again).
I can see multiple issues on Home Assistant Core which seem could be related:
https://github.com/home-assistant/core/issues/63957
https://github.com/home-assistant/core/issues/64077
https://github.com/home-assistant/core/issues/65099
https://github.com/home-assistant/core/issues/65524
https://github.com/home-assistant/core/issues/65634
https://github.com/home-assistant/core/issues/65758
I think one solution would be to use exponential backoff to retry the API. Based on the log below, it's looks to be trying a few times and then stops tracking state entirely.
Here's the most recent log from today, that shows the issue. Home Assistant shows no state change from 16:06 onwards.
2022-02-06 16:04:55 DEBUG (Thread-33) [tuya_iot] _on_log: Received PUBLISH (d0, q0, r0, m0), 'cloud/token/in/d249680c232bf1a26ec786b86fecbf0f', ...  (348 bytes)
2022-02-06 16:04:55 DEBUG (Thread-33) [tuya_iot] payload-> b'{"data":"dRgRVE73G2xRptoTBwYRK0o5qn+tmZWI+0Sadjg7p+jmFAPNqPDoQMSoWxiI7X62X0mAVEdXxSIK1ooNccSsMob3dCy5cx7t4SBdBSBhhpF+R/sAVw93LMPxvio06DqsgHu7nYUK4jOJ6ACEvb3roOoUgyKzMTLn80277aitytz2h0zqqUpBtojYaS1HUOApEfMiOiqJadn4K+tC3U4OboBuuSa2u1ZhLDtrFocRlGtjAWlupFrG58u/tvjGzn5z","protocol":4,"pv":"2.0","sign":"3d4f08833ce8be059c2a88b564dcb365","t":1644116694}'
2022-02-06 16:04:55 DEBUG (Thread-33) [tuya_iot] on_message: {'data': {'dataId': '3eeb7ae6-930c-4e3d-ac1c-399df3f0ba23', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 24, 'code': 'temp_current', 't': '1644116694', 'value': 24}]}, 'protocol': 4, 'pv': '2.0', 'sign': '3d4f08833ce8be059c2a88b564dcb365', 't':<PHONE_NUMBER>}
2022-02-06 16:04:55 DEBUG (Thread-33) [tuya_iot] mq receive-> {'data': {'dataId': '3eeb7ae6-930c-4e3d-ac1c-399df3f0ba23', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 24, 'code': 'temp_current', 't': '1644116694', 'value': 24}]}, 'protocol': 4, 'pv': '2.0', 'sign': '3d4f08833ce8be059c2a88b564dcb365', 't':<PHONE_NUMBER>}
2022-02-06 16:04:55 DEBUG (Thread-33) [tuya_iot] mq _on_device_report-> [{'3': 24, 'code': 'temp_current', 't': '1644116694', 'value': 24}]
2022-02-06 16:04:55 DEBUG (Thread-33) [homeassistant.components.tuya] Received update for device 078443178caab57ec4c8: {'switch': True, 'temp_set': 24, 'temp_current': 24, 'mode': 'cold', 'anion': False, 'temp_set_f': 61, 'temp_current_f': 32}
2022-02-06 16:05:18 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:05:18 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:05:44 DEBUG (Thread-33) [tuya_iot] _on_log: Received PUBLISH (d0, q0, r0, m0), 'cloud/token/in/d249680c232bf1a26ec786b86fecbf0f', ...  (348 bytes)
2022-02-06 16:05:45 DEBUG (Thread-33) [tuya_iot] payload-> b'{"data":"iHsj7kaTxdR5zYikRVh0oQoBrIUDK6SZ59En0NdecuUV0bpkMJU/e8e97NrJZwaKX0mAVEdXxSIK1ooNccSsMob3dCy5cx7t4SBdBSBhhpF+R/sAVw93LMPxvio06DqsgHu7nYUK4jOJ6ACEvb3roOoUgyKzMTLn80277aitytyHLFff/vzp/sSHFYMNyxN/EfMiOiqJadn4K+tC3U4Obp+vMnCJhNITPzBgDfMAFmWXG93EDTzim9Aa7i73r2/y","protocol":4,"pv":"2.0","sign":"a414390bb2befd85584774524097bf2e","t":1644116743}'
2022-02-06 16:05:45 DEBUG (Thread-33) [tuya_iot] on_message: {'data': {'dataId': '218f257e-4c72-4f29-9410-387f5a60522d', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 23, 'code': 'temp_current', 't': '1644116743', 'value': 23}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'a414390bb2befd85584774524097bf2e', 't':<PHONE_NUMBER>}
2022-02-06 16:05:45 DEBUG (Thread-33) [tuya_iot] mq receive-> {'data': {'dataId': '218f257e-4c72-4f29-9410-387f5a60522d', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 23, 'code': 'temp_current', 't': '1644116743', 'value': 23}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'a414390bb2befd85584774524097bf2e', 't':<PHONE_NUMBER>}
2022-02-06 16:05:45 DEBUG (Thread-33) [tuya_iot] mq _on_device_report-> [{'3': 23, 'code': 'temp_current', 't': '1644116743', 'value': 23}]
2022-02-06 16:05:45 DEBUG (Thread-33) [homeassistant.components.tuya] Received update for device 078443178caab57ec4c8: {'switch': True, 'temp_set': 24, 'temp_current': 23, 'mode': 'cold', 'anion': False, 'temp_set_f': 61, 'temp_current_f': 32}
2022-02-06 16:05:46 DEBUG (Thread-33) [tuya_iot] _on_log: Received PUBLISH (d0, q0, r0, m0), 'cloud/token/in/d249680c232bf1a26ec786b86fecbf0f', ...  (348 bytes)
2022-02-06 16:05:46 DEBUG (Thread-33) [tuya_iot] payload-> b'{"data":"o0YNq9wgHukb77DoDinU4AuUfzTPUFHg+IryeGIOWKzNIAVp5B5j/Wgkgx/szz6WX0mAVEdXxSIK1ooNccSsMob3dCy5cx7t4SBdBSBhhpF+R/sAVw93LMPxvio06DqsgHu7nYUK4jOJ6ACEvb3roOoUgyKzMTLn80277aitytz2h0zqqUpBtojYaS1HUOApEfMiOiqJadn4K+tC3U4ObhBhjV4btFSnXJlvbvKV+bZjAWlupFrG58u/tvjGzn5z","protocol":4,"pv":"2.0","sign":"d93f9d396e76ae4d939f60f0a14e30f6","t":1644116745}'
2022-02-06 16:05:46 DEBUG (Thread-33) [tuya_iot] on_message: {'data': {'dataId': 'f0aba7ce-3878-4dca-80f2-20b6303ed5bf', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 24, 'code': 'temp_current', 't': '1644116745', 'value': 24}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'd93f9d396e76ae4d939f60f0a14e30f6', 't':<PHONE_NUMBER>}
2022-02-06 16:05:46 DEBUG (Thread-33) [tuya_iot] mq receive-> {'data': {'dataId': 'f0aba7ce-3878-4dca-80f2-20b6303ed5bf', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 24, 'code': 'temp_current', 't': '1644116745', 'value': 24}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'd93f9d396e76ae4d939f60f0a14e30f6', 't':<PHONE_NUMBER>}
2022-02-06 16:05:46 DEBUG (Thread-33) [tuya_iot] mq _on_device_report-> [{'3': 24, 'code': 'temp_current', 't': '1644116745', 'value': 24}]
2022-02-06 16:05:46 DEBUG (Thread-33) [homeassistant.components.tuya] Received update for device 078443178caab57ec4c8: {'switch': True, 'temp_set': 24, 'temp_current': 24, 'mode': 'cold', 'anion': False, 'temp_set_f': 61, 'temp_current_f': 32}
2022-02-06 16:06:18 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:06:18 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:06:20 DEBUG (Thread-33) [tuya_iot] _on_log: Received PUBLISH (d0, q0, r0, m0), 'cloud/token/in/d249680c232bf1a26ec786b86fecbf0f', ...  (348 bytes)
2022-02-06 16:06:20 DEBUG (Thread-33) [tuya_iot] payload-> b'{"data":"gNFDOxLjZG3IJDxyG7mnzvfXpvkcj4kgIu1URZfC1e7Kt0mYlvr9LJd2Hc4Iab5nX0mAVEdXxSIK1ooNccSsMob3dCy5cx7t4SBdBSBhhpF+R/sAVw93LMPxvio06DqsgHu7nYUK4jOJ6ACEvb3roOoUgyKzMTLn80277aitytwwWOckLP1BaMf9gswE6vdBEfMiOiqJadn4K+tC3U4ObnNMQ2jHyxHDRK/NKMWvv4PlWZzn4sTjqROwVZy3mgVT","protocol":4,"pv":"2.0","sign":"c454868db621f241b62807100c47deb7","t":1644116779}'
2022-02-06 16:06:20 DEBUG (Thread-33) [tuya_iot] on_message: {'data': {'dataId': '1d448d81-3136-400b-8b8d-5bc35ebcf9ae', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 25, 'code': 'temp_current', 't': '1644116779', 'value': 25}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'c454868db621f241b62807100c47deb7', 't':<PHONE_NUMBER>}
2022-02-06 16:06:20 DEBUG (Thread-33) [tuya_iot] mq receive-> {'data': {'dataId': '1d448d81-3136-400b-8b8d-5bc35ebcf9ae', 'devId': '078443178caab57ec4c8', 'productKey': 'gylvqvz3p94i3zdn', 'status': [{'3': 25, 'code': 'temp_current', 't': '1644116779', 'value': 25}]}, 'protocol': 4, 'pv': '2.0', 'sign': 'c454868db621f241b62807100c47deb7', 't':<PHONE_NUMBER>}
2022-02-06 16:06:20 DEBUG (Thread-33) [tuya_iot] mq _on_device_report-> [{'3': 25, 'code': 'temp_current', 't': '1644116779', 'value': 25}]
2022-02-06 16:06:20 DEBUG (Thread-33) [homeassistant.components.tuya] Received update for device 078443178caab57ec4c8: {'switch': True, 'temp_set': 24, 'temp_current': 25, 'mode': 'cold', 'anion': False, 'temp_set_f': 61, 'temp_current_f': 32}
2022-02-06 16:06:25 DEBUG (Thread-18) [tuya_iot] Request: method = GET,                 url = https://openapi.tuyaus.com/v1.0/token/506c665c72bdc06091c264dac8ec4100,                params = None,                body = None,                t =<PHONE_NUMBER>539
2022-02-06 16:06:30 ERROR (Thread-18) [root] Uncaught thread exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/usr/local/lib/python3.9/site-packages/urllib3/util/connection.py", line 72, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/local/lib/python3.9/socket.py", line 954, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Try again

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 1040, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 358, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f0c25d07460>: Failed to establish a new connection: [Errno -3] Try again

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/requests/adapters.py", line 440, in send
    resp = conn.urlopen(
  File "/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py", line 785, in urlopen
    retries = retries.increment(
  File "/usr/local/lib/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='openapi.tuyaus.com', port=443): Max retries exceeded with url: /v1.0/token/506c665c72bdc06091c264dac8ec4100 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f0c25d07460>: Failed to establish a new connection: [Errno -3] Try again'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 164, in __run_mqtt
    mq_config = self._get_mqtt_config()
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openmq.py", line 62, in _get_mqtt_config
    response = self.api.post(
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 316, in post
    return self.__request("POST", path, None, body)
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 238, in __request
    self.__refresh_access_token_if_need(path)
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 164, in __refresh_access_token_if_need
    response = self.get(
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 302, in get
    return self.__request("GET", path, params, None)
  File "/usr/local/lib/python3.9/site-packages/tuya_iot/openapi.py", line 266, in __request
    response = self.session.request(
  File "/usr/local/lib/python3.9/site-packages/requests/sessions.py", line 529, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.9/site-packages/requests/sessions.py", line 645, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.tuyaus.com', port=443): Max retries exceeded with url: /v1.0/token/506c665c72bdc06091c264dac8ec4100 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f0c25d07460>: Failed to establish a new connection: [Errno -3] Try again'))
2022-02-06 16:07:19 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:07:19 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:08:19 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:08:19 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:09:19 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:09:19 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:10:19 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:10:19 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:11:19 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:11:20 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:12:20 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:12:20 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:13:20 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:13:20 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:14:20 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:14:20 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:15:20 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:15:21 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:16:21 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:16:21 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:17:21 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:17:21 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:18:21 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:18:21 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:19:21 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:19:21 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:20:21 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:20:22 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:21:22 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:21:22 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP
2022-02-06 16:22:22 DEBUG (Thread-33) [tuya_iot] _on_log: Sending PINGREQ
2022-02-06 16:22:22 DEBUG (Thread-33) [tuya_iot] _on_log: Received PINGRESP

Just dug into the code to see if I can figure out a way to prevent this from happening.
Aside from resolving the actual Tuya server issues, the code can be updated to be more resilient.
In this case, it's the MQTT client that is failing to re-connect after 2 hours.
In openmq the client is recreated. Normally this is fine. However in the call to self._get_mqtt_config() the API server fails to connect, and the error that is throw ripples all the way up to the run() loop. This loop doesn't handle the error, and so the MQTT server eventually expires and the loop is no longer replacing it.
I think this loop should have a try/except added so that it can handle any errors thrown, and continue trying to refresh the MQTT server until it is successful. Given that it's an API server, probably best to have exponential backoff so as to not hammer the server with requests when it is down.

Amazing work, here's hoping your PR gets accepted soon.
Here's another related issue: https://github.com/home-assistant/core/issues/63052

@zlinoliver Hello, will we get a new release with this fix soon?

Same thing.
After some time being offline localtuya stops working.
The logs shows it tried to contact tuya servers, and that is where it dies.
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.tuyaus.com', port=443): Max retries exceeded with url: /v1.0/token?grant_type=1 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x75d377d07fa0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))


are IPython 3 notebooks supported?

if not to do you have plans for supporting them in the future?

I dont think they are but i want to support them.
I'll try to find some time to work on this soon.

Hey @zonca I just tested it with an ipython notebook v3 (notebook format v4) and everything seems to be working fine. I just did an update fixing some other stuff so maybe just try the latest version.
Feel free to reopen or create another issue if you find a problem with it :)


Add VMware support and fix ulimits

This updates the vagrant provisioning script to correctly set the ulimits in Ubuntu, since the bin/coco-brunch file can't set them properly when run as the vagrant user.
Added some basic support into the Vagrantfile for VMware providers and uploaded a VMware compatible vagrant box based on trusty64 to https://github.com/spkane/vagrant-boxes/releases/download/v1.0.0/trusty64_vmware.box, that folks can use.

Thanks @spkane! What do you think of the current status of the Vagrant setup?

@nwinter The ulimits issue was causing some problems, but once that was resolved, it seems to work, as I can finally get the site to start locally (initially it was simply a blank screen). I haven't tried to do any real work with it yet, but as I do I might provide some additional tweaks.


Any plans to support TypeScript?

Thank you guys so much for the work that you do.
Are there any plans to support TypeScript?

Thanks @geoyws! That was a big question recently we wanted to do it but since it's a starter we concluded it should be as accessible as possible even for beginners.
The best solution would be to make a typescript branch if you're down for that? I will help you if needed but I can't maintain both languages at the same time by myself.
I took into consideration the ability to easily generate a typescript starter, so if you create a typescript branch named next-ts on this repo you will be able to do:
yarn create r3f-app next-ts my-start
If you are willing to work on the Typescript starter there is more than half the r3f community that would be interested:
https://twitter.com/onirenaud/status/1375737135102263304
I would be happy to add you as a maintainer if you want to do it!

All it took to "convert" the project to Typescript, was to add an empty tsconfig.json, run yarn dev, Next automatically fills the tsconfig.json with the right settings.
All I had to do was copy the path alias settings. Your current jsconfig.json config is basically valid tsconfig.json configuration.
All of the existing code is already valid TypeScript as Javascript is a subset. I'm not sure maintaining a separate branch is exactly required. You might just tell people how to do it.

Here are the steps to get the current project working with typescript:

touch tsconfig.json
start the dev server, next will fill the tsconfig.json and tell you to install typescript
yarn add --dev typescript @types/react
copy the path aliases from jsconfig.json to tsconfig.json

Since javascript is a subset of typescript everything else just works!

Apologies I have too much on my plate at the moment and can't afford the time. I hope someone else might be able to take this on.

@RenaudRohlinger cc @geoyws
If no one else is assigned, can I work on this issue?

Thank you very much @shuta13! As I mentioned in #37 I made a CLI tool (https://github.com/RenaudRohlinger/create-r3f-app) that allows us to clone a clean version of a branch from this repo with some small extra (when you do yarn create r3f-app next). With that tool, we could make another branch (typescript) so when you do yarn create r3f-app next typescript for example it would automatically clone the typescript branch.
I think it would imply to always keep the typescript branch up to date which is kind of hassle.
The other option (the best one imo) would be to do a small binary that uses something like execa and that would batch replace all the js files with ts extensions and then execute the following commands:
create a tsconfig.json file
yarn add --dev typescript @types/react
yarn build to generate a tsconfig.json from next or pick the template from next
copy the path aliases from jsconfig.json to tsconfig.json
Since the number of actions to do is pretty small, the script option is the way to go imo. We could host it on create-r3f-app and simply execute it if there is the "typescript" parameter.

It's always going to be better to just maintain the library in typescript if maintainers can rise to the challenge. This way, you are getting both typescript and javascript support for the price of one. When the project is in javascript, someone has to continuously go through the process of maintaining the type specification... might as well just write the program typed.

@RenaudRohlinger
Sorry for the late reply.
I have checked about https://github.com/RenaudRohlinger/create-r3f-app. I think that creating a new "typescript" branch would satisfy the requirement, but I also think that it would be better if all js files are replaced with ts files when the "typescript" parameter is passed.
I would like to create a PR with this implementation!

It's official, @shuta13 added the typescript support !! 👏👏👏


Add @FieldOrder annotation so Rule classes are minimized

When digging through the Borsh operation, it became clear that for serializing/deserializing the fields need to be encountered in the same order so the bytes can be read/written properly. Your most recent Rule system really helped formalize making that happen, but I realized that for many field types if we could just specify the order, that would be enough.
Hence this PR - now you can just annotate the fields with @FieldOrder() and for many classes, no Rule class will be necessary. The rule system still works great for special cases, but hopefully this should reduce the boilerplate needed for most classes. Even the PublicKeyRule could likely be simplified/removed as a result of this annotation, though I didn't do that work for this PR.

This is a welcome improvement. I  would consider putting the metaplex object in a different package name metaplex models inside the programs folder. This is not a native program.
I think the tests are missing the field annotation that may be the reason of the failure tests.

The metaplex objects are in the test dir, do you want them in the actual library model objects? I was just using them to test various aspects of deserializing with the annotation.
I'll get the test check passing too!

You were right, I had failed to update the test classes with the annotation! I updated the tests but also updated the serialize/deserialize to throw an InvalidArgumentException if the annotation is missing on any classes.

Leave the metaplex object on tests. That's my mistake

We might add a sub lib that has support for all programs and objects for projects

We might add a sub lib that has support for all programs and objects for projects

Yeah that sounds like a really good idea.


G

https://vm.tiktok.com/ZMLLEo74H/

@etoja07 Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.


Hacktoberfest

Type of change

Added new project

Changes proposed in this pull request

Project name : Youtube downloader

Short description :

It's a simple GUI built using Tkinter and pytube for downloading videos from YouTube. To download a video
enter the YouTube Video URL in the text box and click the Download button.
It will take some time to download the video depending on the video size, video quality, and network connectivity.
Navigate to the folder youtube_downloads and find the video in .mp4 format.
Checklist

[x] The code is Python 3 compatible
[x] I have added relevant comments in my file to make code understandable
[x] I have added my project in a folder which includes all the necessary files

A similar kind of project already exists : https://github.com/Mrinank-Bhowmick/python-beginner-projects/tree/main/projects/YouTube Video Downloader


Zapf Chancery

The Zapf Chancery font belongs to the "Decorative" font styles

@maba001 where is this notion of “Decorative”? I don’t think such a distinction exists in this tool.

This is just referring to the "CSS fallback". Zapf Chancery could be considered either "Cursive" or "Fantasy".
https://www.w3.org/Style/Examples/007/fonts.en.html#font-family

@maba001 fontfamily has a script that runs and detects the installed fonts automatically. So far none of the browsers tested have cursive or fantasy mapped to Zapf Chancery:

http://fontfamily.io/cursive
http://fontfamily.io/fantasy