Uncaught error in JSON.parse which brakes test task

Run this test:
"@fixture jj";

"@page http://tema.livejournal.com";

"@test"["qqq"] = {
    '1.Click <b> "tema"': function() {
        var bElement = $("#lj_controlstrip_new").find(":containsExcludeChildren(tema)");
        act.click(bElement, {});
    }
};

Test fail will be reported correctly, however after this error occurs in JSON.parse within Hammerhead (can't be reproduced in HHM) and task frozes.

Any news on this?

It's done, but wait for some commits from @AlexanderMoskovkin

we'll fix it when the https://github.com/DevExpress/testcafe/pull/130 issue is closed to avoid merging problems. https://github.com/DevExpress/testcafe/pull/130 is close to be closed =)


add default permission in case owner is null

to cover all cases, add a catch that will return a drop table with permission "default" in case the owner is null

Thanks a lot, I'll reserve for it some time to test it, if you don't mind


In the log file which are being generated , can the source of it be changed ?

Is it possible to change the source URL/ destination ?

In test suite changing the source , to a different path. Is it possible ?

There's no built-in way, but you can use pre-Rebot modifiers or otherwise post-process outputs after execution. See the User Guide for more details and use robotframework-users or other such forums if you need more help. This tracker is for bug reports and concrete enhancement request.


Avoid extra '>' or '"' when using #include directive

When including files, tokens are inserted twice: when expading the #include snippet and when choosing the file

System information
Output of clangd --version:
clangd version 13.0.1
Features: linux
Platform: x86_64-pc-linux-gnu

Editor/LSP plugin: Neovim / built-in LSP
Operating system: Artix Linux 5.16.10

Can you elaborate? What plugin are you using for completion, and what sequence of keystrokes triggers the behavior?
It is expected that typing > will insert the snippet including > and also an extra >. Otherwise this sounds like a bug, but the protocol for this case has been inspected and tested with different clients, so it may be a client bug...

Can you elaborate?

Sure! I'm using nvim-cmp for completion (coupled with Luasnip as the snippets engine), though I think it's reproducible with other setups within neovim (with coq, for instance). As for the sequence of keystrokes, I have recorded a demo:
https://user-images.githubusercontent.com/84649544/156798305-c986fef7-d583-4d34-819c-db3b6fb86202.mp4
If I press esc (leaving vim's insert mode) instead of return at the end, it works as expected.

so it may be a client bug

Indeed, though it's been reported here, which lead to believe it was an issue with clangd itself.

instead of a screenshot/video can you pass --log=verbose into your clangd arguments and send the clangd logs after performing the problematic code completion?
the logs will include the clangd's response, which has the range to be replaced and the text it should be overwritten with. on all the examples i've tried the range includes the closing > or ". if you include your logs we can make sure that's the case with you as well then we can decide whether it's a bug on clangd side or your LSP client implementation.
feel free to re-open once you post the clangd logs.

Here's a log of me trying to include <iostream>: https://gist.github.com/igorlfs/0815714f7d3893f25bab60eb15fec634.

'V[14:05:52.439] >>> {"id":4,"jsonrpc":"2.0","result":{"isIncomplete":false,"items":[{"filterText":"INIReader.h>","insertText":"INIReader.h>","insertTextFormat":2,"kind":17,"label":" INIReader.h>","score":0.78725427389144897,"sortText":"40b67681INIReader.h>","textEdit":{"newText":"INIReader.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ia32intrin.h>","insertText":"ia32intrin.h>","insertTextFormat":2,"kind":17,"label":" ia32intrin.h>","score":0.78725427389144897,"sortText":"40b67681ia32intrin.h>","textEdit":{"newText":"ia32intrin.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ibus-1.0/","insertText":"ibus-1.0/","insertTextFormat":2,"kind":19,"label":" ibus-1.0/","score":0.78725427389144897,"sortText":"40b67681ibus-1.0/","textEdit":{"newText":"ibus-1.0/","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iconv.h>","insertText":"iconv.h>","insertTextFormat":2,"kind":17,"label":" iconv.h>","score":0.78725427389144897,"sortText":"40b67681iconv.h>","textEdit":{"newText":"iconv.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"idn2.h>","insertText":"idn2.h>","insertTextFormat":2,"kind":17,"label":" idn2.h>","score":0.78725427389144897,"sortText":"40b67681idn2.h>","textEdit":{"newText":"idn2.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ieee754.h>","insertText":"ieee754.h>","insertTextFormat":2,"kind":17,"label":" ieee754.h>","score":0.78725427389144897,"sortText":"40b67681ieee754.h>","textEdit":{"newText":"ieee754.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ifaddrs.h>","insertText":"ifaddrs.h>","insertTextFormat":2,"kind":17,"label":" ifaddrs.h>","score":0.78725427389144897,"sortText":"40b67681ifaddrs.h>","textEdit":{"newText":"ifaddrs.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"immintrin.h>","insertText":"immintrin.h>","insertTextFormat":2,"kind":17,"label":" immintrin.h>","score":0.78725427389144897,"sortText":"40b67681immintrin.h>","textEdit":{"newText":"immintrin.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ini.h>","insertText":"ini.h>","insertTextFormat":2,"kind":17,"label":" ini.h>","score":0.78725427389144897,"sortText":"40b67681ini.h>","textEdit":{"newText":"ini.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"initializer_list>","insertText":"initializer_list>","insertTextFormat":2,"kind":17,"label":" initializer_list>","score":0.78725427389144897,"sortText":"40b67681initializer_list>","textEdit":{"newText":"initializer_list>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"intrin.h>","insertText":"intrin.h>","insertTextFormat":2,"kind":17,"label":" intrin.h>","score":0.78725427389144897,"sortText":"40b67681intrin.h>","textEdit":{"newText":"intrin.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"inttypes.h>","insertText":"inttypes.h>","insertTextFormat":2,"kind":17,"label":" inttypes.h>","score":0.78725427389144897,"sortText":"40b67681inttypes.h>","textEdit":{"newText":"inttypes.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"invpcidintrin.h>","insertText":"invpcidintrin.h>","insertTextFormat":2,"kind":17,"label":" invpcidintrin.h>","score":0.78725427389144897,"sortText":"40b67681invpcidintrin.h>","textEdit":{"newText":"invpcidintrin.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iomanip>","insertText":"iomanip>","insertTextFormat":2,"kind":17,"label":" iomanip>","score":0.78725427389144897,"sortText":"40b67681iomanip>","textEdit":{"newText":"iomanip>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"ios>","insertText":"ios>","insertTextFormat":2,"kind":17,"label":" ios>","score":0.78725427389144897,"sortText":"40b67681ios>","textEdit":{"newText":"ios>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iosfwd>","insertText":"iosfwd>","insertTextFormat":2,"kind":17,"label":" iosfwd>","score":0.78725427389144897,"sortText":"40b67681iosfwd>","textEdit":{"newText":"iosfwd>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iostream>","insertText":"iostream>","insertTextFormat":2,"kind":17,"label":" iostream>","score":0.78725427389144897,"sortText":"40b67681iostream>","textEdit":{"newText":"iostream>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iproute2/","insertText":"iproute2/","insertTextFormat":2,"kind":19,"label":" iproute2/","score":0.78725427389144897,"sortText":"40b67681iproute2/","textEdit":{"newText":"iproute2/","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"isl/","insertText":"isl/","insertTextFormat":2,"kind":19,"label":" isl/","score":0.78725427389144897,"sortText":"40b67681isl/","textEdit":{"newText":"isl/","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iso646.h>","insertText":"iso646.h>","insertTextFormat":2,"kind":17,"label":" iso646.h>","score":0.78725427389144897,"sortText":"40b67681iso646.h>","textEdit":{"newText":"iso646.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"istream>","insertText":"istream>","insertTextFormat":2,"kind":17,"label":" istream>","score":0.78725427389144897,"sortText":"40b67681istream>","textEdit":{"newText":"istream>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"iterator>","insertText":"iterator>","insertTextFormat":2,"kind":17,"label":" iterator>","score":0.78725427389144897,"sortText":"40b67681iterator>","textEdit":{"newText":"iterator>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"OMX_IVCommon.h>","insertText":"OMX_IVCommon.h>","insertTextFormat":2,"kind":17,"label":" OMX_IVCommon.h>","score":0.78725427389144897,"sortText":"80000000OMX_IVCommon.h>","textEdit":{"newText":"OMX_IVCommon.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"OMX_Image.h>","insertText":"OMX_Image.h>","insertTextFormat":2,"kind":17,"label":" OMX_Image.h>","score":0.78725427389144897,"sortText":"80000000OMX_Image.h>","textEdit":{"newText":"OMX_Image.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"OMX_Index.h>","insertText":"OMX_Index.h>","insertTextFormat":2,"kind":17,"label":" OMX_Index.h>","score":0.78725427389144897,"sortText":"80000000OMX_Index.h>","textEdit":{"newText":"OMX_Index.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"__clang_cuda_intrinsics.h>","insertText":"__clang_cuda_intrinsics.h>","insertTextFormat":2,"kind":17,"label":" __clang_cuda_intrinsics.h>","score":0.78725427389144897,"sortText":"80000000__clang_cuda_intrinsics.h>","textEdit":{"newText":"__clang_cuda_intrinsics.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"dbstl_base_iterator.h>","insertText":"dbstl_base_iterator.h>","insertTextFormat":2,"kind":17,"label":" dbstl_base_iterator.h>","score":0.78725427389144897,"sortText":"80000000dbstl_base_iterator.h>","textEdit":{"newText":"dbstl_base_iterator.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"dbstl_inner_utility.h>","insertText":"dbstl_inner_utility.h>","insertTextFormat":2,"kind":17,"label":" dbstl_inner_utility.h>","score":0.78725427389144897,"sortText":"80000000dbstl_inner_utility.h>","textEdit":{"newText":"dbstl_inner_utility.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"gd_io.h>","insertText":"gd_io.h>","insertTextFormat":2,"kind":17,"label":" gd_io.h>","score":0.78725427389144897,"sortText":"80000000gd_io.h>","textEdit":{"newText":"gd_io.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"hexagon_circ_brev_intrinsics.h>","insertText":"hexagon_circ_brev_intrinsics.h>","insertTextFormat":2,"kind":17,"label":" hexagon_circ_brev_intrinsics.h>","score":0.78725427389144897,"sortText":"80000000hexagon_circ_brev_intrinsics.h>","textEdit":{"newText":"hexagon_circ_brev_intrinsics.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"mpif-io-constants.h>","insertText":"mpif-io-constants.h>","insertTextFormat":2,"kind":17,"label":" mpif-io-constants.h>","score":0.78725427389144897,"sortText":"80000000mpif-io-constants.h>","textEdit":{"newText":"mpif-io-constants.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"mpif-io-handles.h>","insertText":"mpif-io-handles.h>","insertTextFormat":2,"kind":17,"label":" mpif-io-handles.h>","score":0.78725427389144897,"sortText":"80000000mpif-io-handles.h>","textEdit":{"newText":"mpif-io-handles.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},{"filterText":"zzip-io.h>","insertText":"zzip-io.h>","insertTextFormat":2,"kind":17,"label":" zzip-io.h>","score":0.78725427389144897,"sortText":"80000000zzip-io.h>","textEdit":{"newText":"zzip-io.h>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}}]}}\n\n'

is the latest response you've received from clangd. as you can see all of those replace the range of line:0 from character:10 to 12. including iostream>:
{"filterText":"iostream>","insertText":"iostream>","insertTextFormat":2,"kind":17,"label":" iostream>","score":0.78725427389144897,"sortText":"40b67681iostream>","textEdit":{"newText":"iostream>","range":{"end":{"character":12,"line":0},"start":{"character":10,"line":0}}}},

If I followed correctly the document contents when you made the request is:
#include <i>

the range from 10-12 on this line covers i>, hence your editor should replace i> with iostream> leaving no extra brackets.


Narrator is not providing any confirmation after activating "Keep on top" button

A team member will update this issue with more details soon.

This is your friendly Microsoft Issue Bot. I created this issue automatically as requested by a team member.

Hi @grochocki, shall I take this up?

Sure thing -- thanks for taking a look!


some amateur tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@425eb05). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage        ?   72.15%
=======================================
  Files           ?       39
  Lines           ?     3257
  Branches        ?        0
=======================================
  Hits            ?     2350
  Misses          ?      907
  Partials        ?        0

Flag
Coverage Δ

unittests
72.15% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add TCP read logs

Based on top of #4674. Needed to run on the testbed.

#4674 was merged with all relevant fixes. This is not needed any more.


Add table transactions.

This adds a Transaction API that exposes some Table updates that can be performed in a single commit.
The transaction works by replacing the underlying TableOperations passed to individual updates with a transaction version that applies changes to the table metadata result of the previous update. If the transaction commit needs to retry, it re-runs commit for each update in order. Each update must be committed before the next update is created to ensure a clear order.
Transaction also returns a table, which can be passed to code that expects a Table instead of a Transaction. Operations on that table become part of the transaction.

@Parth-Brahmbhatt, @danielcweeks, could you review this PR?


refactor: Make query() return an Iterable

Fixes #31
I added a unit test but since it's not really testing anything important, I'm happy to remove it.
I also went ahead and upped semver, though that, too, can be removed from this PR.
cc @spydon

Thanks for the approval! I think the CI needs an explicit approval before running.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.842%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
92

Relevant Lines:
95

💛  - Coveralls


[Logging v2] - Can't access the Logging Overview as Cluster Member

I am able to access the Logging Overview as Cluster Owner, Project Owner and Project Member.
But he Logging App link is not shown for Cluster Member

Rancher version: master-head (09/28/2020) ec04f78 HA k8s with Downstream DO RKE cluster

@izaac Does the cluster member have access to any project in this case ?

The user has access to a Project and a Namespace:
The first screenshot was taken using user1 to list the members.

Then from here is user2


Ceph-ansible fails to check devices while trying to re-run playbook to add 2 new RGW

Bug Report
What happened:
Added 2 RGW servers into Ansible inventory and run playbook check before running the playbook to apply changes
What you expected to happen:
Expected to get all checks passed as per last execution awhile ago then run playbook to get the 2 RGW installed but all 5 OSD/MON nodes I have in the cluster return below error.
First time I see this error so sharing here to understand more
fatal: [node01]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/roles/ceph-validate/tasks/check_devices.yml': line 7, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: resolve root_device
      ^ here
fatal: [node02]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/roles/ceph-validate/tasks/check_devices.yml': line 7, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: resolve root_device
      ^ here
fatal: [node03]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/roles/ceph-validate/tasks/check_devices.yml': line 7, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: resolve root_device
      ^ here
fatal: [node04]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/roles/ceph-validate/tasks/check_devices.yml': line 7, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: resolve root_device
      ^ here
fatal: [node05]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/roles/ceph-validate/tasks/check_devices.yml': line 7, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: resolve root_device
      ^ here

NO MORE HOSTS LEFT ******************************************************************************************************************************************
        to retry, use: --limit @/home/ansible/ansible-retry/site.retry

PLAY RECAP **************************************************************************************************************************************************
node01       : ok=41   changed=0    unreachable=0    failed=1    skipped=66   rescued=0    ignored=0
node02       : ok=36   changed=0    unreachable=0    failed=1    skipped=63   rescued=0    ignored=0
node03       : ok=32   changed=0    unreachable=0    failed=1    skipped=67   rescued=0    ignored=0
node04       : ok=32   changed=0    unreachable=0    failed=1    skipped=67   rescued=0    ignored=0
node05       : ok=32   changed=0    unreachable=0    failed=1    skipped=67   rescued=0    ignored=0
sgw01        : ok=31   changed=0    unreachable=0    failed=0    skipped=67   rescued=0    ignored=0
sgw02        : ok=31   changed=0    unreachable=0    failed=0    skipped=67   rescued=0    ignored=0

How to reproduce it (minimal and precise):

run ansible-playbook site.yml --check
Share your group_vars files, inventory and full ceph-ansibe log
Environment:

OS (e.g. from /etc/os-release): CentOS Linux release 7.8.2003 (Core) VERSION="7 (Core)"
Kernel (e.g. uname -a): 3.10.0-1127.10.1.el7.x86_64
Docker version if applicable (e.g. docker version):
Ansible version (e.g. ansible-playbook --version): ansible-playbook 2.8.8
ceph-ansible version (e.g. git head or tag or stable branch):
Ceph version (e.g. ceph -v): ceph version 14.2.9 nautilus (stable)

Please share the full ansible log, inventory and variables defined in group_vars/host_vars

Hi @dsavineau
Thanks for assisting here.
I shared the files with you via email. Unfortunately can't share publicly here

Hi guys.. I wonder if you had the chance to check logs?

Not yet sorry, we're pretty busy atm.
Probably next week.

Can we update label on this case to follow up when possible?
Regards

Sorry for the delay.
You didn't mentioned the ceph-ansible version you were using but I assume it's either a v4.0.x tag or the stable-4.0 branch because you're deploying Nautilus. Am I right ?
The playbook is failing on the root device detection for the OSD nodes.
https://github.com/ceph/ceph-ansible/blob/stable-4.0/roles/ceph-validate/tasks/check_devices.yml#L2-L10
According to the logs you provided, the first task is skipped so there's not stdout attribute on the registered variable root_device used on the second task.
|  TASK [ceph-validate : find device used for operating system] ******************
|  Thursday 10 September 2020  11:21:35 +1200 (0:00:02.471)       0:03:19.418 ****
|  skipping: [node01]
|  skipping: [node02]
|  skipping: [node03]
|  skipping: [node04]
|  skipping: [node05]

Can you run findmnt -v -n -T / -o SOURCE  on one on the OSD nodes ?
You said this issue occured when re-running the playbook. Is there somehow a collocation between the root device of the OSD nodes and one of the OSD device ?
It would also be helpful to get the output of the lsblk command.

Hi @dsavineau
Apologies for delay and missing info. Missed the notification of your update
I have Nautilus deployed
The only change I recall on the server is deploying benchmark tools
After comparing versions of ansible, python and pip with other zone Ceph cluster with exactly same setup and versions
This other cluster is not experiencing this error as per below
INSTALLER STATUS ********************************************************************************************************************************************
Install Ceph Monitor           : Complete (0:01:35)
Install Ceph Manager           : Complete (0:01:48)
Install Ceph OSD               : Complete (0:02:09)
Install Ceph RGW               : Complete (0:00:56)
Install Ceph NFS               : Complete (0:01:14)
Install Ceph Client            : Complete (0:00:32)
Install Ceph iSCSI Gateway     : Complete (0:01:14)
Install Ceph Dashboard         : Complete (0:02:02)
Install Ceph Grafana           : Complete (0:01:13)
Install Ceph Node Exporter     : Complete (0:01:19)

Thursday 05 November 2020  07:15:03 +1300 (0:00:00.093)       0:19:21.869 *****
===============================================================================

Here's the information you requested
# pip --version
pip 20.0.2 from /usr/lib/python2.7/site-packages/pip (python 2.7)

# ansible --version
/usr/lib64/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
**ansible 2.8.8**
  config file = /root/ansible.cfg
  configured module search path = [u'/usr/share/ceph-ansible/library']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  **python version = 2.7.5 (default, Apr  2 2020, 13:16:51) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]**

# findmnt -v -n -T / -o SOURCE
/dev/mapper/centos-root

# lsblk

NAME                                                                                MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                                                                                8:0    0   1.8T  0 disk
ââceph--e9ed643a--47e7--44fa--bbd8--e3ff0ccb3def-osd--data--e8eefdba--f2ed--400c--a908--29681e0ce17c 253:14   0   1.8T  0 lvm
sdb                                                                                8:16   0   1.8T  0 disk
ââceph--cd161348--68a3--43dd--82c7--1bbbb1acaedd-osd--data--9b8e0acf--a7b2--4fa7--870c--5aff2ba5240c 253:7    0   1.8T  0 lvm
sdc                                                                                8:32   0   1.8T  0 disk
ââceph--3e439275--167e--4ffe--ab74--809e238285c9-osd--data--4a5e09d4--a732--4c50--9f18--66f99172e918 253:5    0   1.8T  0 lvm
sdd                                                                                8:48   0   1.8T  0 disk
ââceph--cecfbfa8--a15a--417f--a1da--7605faa8ec99-osd--data--444b4ed8--cd30--47ba--82d7--18828b007964 253:16   0   1.8T  0 lvm
sde                                                                                8:64   0   1.8T  0 disk
ââceph--3bba5a26--1a84--4f76--8849--3019b5606acf-osd--data--6d6a1e59--a0c8--45f0--8f3c--226ec39e9319 253:6    0   1.8T  0 lvm
sdf                                                                                8:80   0   1.8T  0 disk
ââceph--ca01fe9b--a03b--42c6--ae9a--f5b3597a9471-osd--data--52ea6ad8--eee9--467d--a5e0--8a6377ebd364 253:8    0   1.8T  0 lvm
sdg                                                                                8:96   0   1.8T  0 disk
ââceph--cf7a3d20--118c--47ca--a979--b40fe6f28614-osd--data--b87adf80--ae3f--4c9c--87ce--de04dcabc954 253:10   0   1.8T  0 lvm
sdh                                                                                8:112  0   1.8T  0 disk
ââceph--5cb94175--c033--441b--af87--b425ffefb2e9-osd--data--5f3c956b--de9f--41ce--8425--64235813d33a 253:15   0   1.8T  0 lvm
sdi                                                                                8:128  0   1.8T  0 disk
ââceph--1f31cc99--6dcb--4777--a238--5cc633e4b225-osd--data--fc566987--a2fa--42e7--9327--794d87a95e2c 253:19   0   1.8T  0 lvm
sdj                                                                                8:144  0   1.8T  0 disk
ââceph--095dc297--d240--4cd6--b5a7--754df08538e4-osd--data--27bc7048--4327--495e--aacd--ad65b580cba5 253:9    0   1.8T  0 lvm
sdk                                                                                8:160  0   1.8T  0 disk
ââceph--f87703cb--b965--407d--8d7c--960c81933dd8-osd--data--67b37ea2--df22--4583--bcc6--6218a0444084 253:13   0   1.8T  0 lvm
sdl                                                                                8:176  0   1.8T  0 disk
ââceph--4da0849d--fb04--464f--84b9--08ea712b52be-osd--data--e514ca18--5872--48ab--94ca--b093f96ad289 253:20   0   1.8T  0 lvm
sdm                                                                                8:192  0   1.8T  0 disk
ââceph--83876441--2b17--49b5--b646--dab4b1e7b05e-osd--data--38bb596e--327d--4fa3--a9e3--12a6a52966c2 253:12   0   1.8T  0 lvm
sdn                                                                                8:208  0   1.8T  0 disk
ââceph--26f2ddbb--a645--4d83--a0c0--c1c9a0821288-osd--data--fc5baf4f--92fc--4d18--b256--1c17c8a65ca5 253:17   0   1.8T  0 lvm
sdo                                                                                8:224  0   1.8T  0 disk
ââceph--48bfe4c6--d4ab--4795--b0e7--81df80b2e298-osd--data--eed9f303--0ef4--4a51--8937--ff2552ef4401 253:11   0   1.8T  0 lvm
sdp                                                                                8:240  0 232.4G  0 disk
ââsdp1                                                                                8:241  0     1G  0 part /boot
ââsdp2                                                                                8:242  0 231.4G  0 part
  ââcentos-root-real                                                                                253:0    0    50G  0 lvm
  â ââcentos-root                                                                                253:1    0    50G  0 lvm  /
  â ââcentos-root_yum_20190912114147                                                                 253:3    0    50G  0 lvm
  ââcentos-root_yum_20190912114147-cow                                                               253:2    0     4M  0 lvm
  â ââcentos-root_yum_20190912114147                                                                 253:3    0    50G  0 lvm
  ââcentos-swap                                                                                253:4    0  11.8G  0 lvm  [SWAP]
  ââcentos-home                                                                                253:18   0 169.6G  0 lvm  /home
sr0                                                                                11:0    1  1024M  0 rom

Could you try to run this standalone playbook ?
---
- hosts: osds
  become: true
  tasks:
    - name: find device used for operating system
      command: findmnt -v -n -T / -o SOURCE
      changed_when: false
      register: root_device

    - name: resolve root_device
      command: "readlink -f {{ root_device.stdout }}"
      changed_when: false
      register: _root_device

    - name: set_fact root_device
      set_fact:
        root_device: "{{ _root_device.stdout }}"

# findmnt -v -n -T / -o SOURCE
/dev/mapper/centos-root

As far as I can see, this look normal, because the root mount point is using a LV which isn't part of any OSD devices.

HI @dsavineau
Playbook started OK then got stuck
After running playbook again returns error
Run retry mode succesfully
$ ansible-playbook osd.yml --check
/usr/lib64/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10. Deprecation warnings can be disabled by setting deprecation_warnings=False
in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

[WARNING]: Skipping plugin (/usr/share/ceph-ansible/plugins/filter/test_ipaddrs_in_ranges.py) as it seems to be invalid: cannot import name
ipaddrs_in_ranges

PLAY [osds] *************************************************************************************************************************************************

TASK [Gathering Facts] **************************************************************************************************************************************
Thursday 05 November 2020  09:29:18 +1300 (0:00:03.146)       0:00:03.146 *****
ok: [node03]
ok: [node01]
ok: [node05]
ok: [node04]
^C [ERROR]: User interrupted execution

$ ansible-playbook osd.yml --check
/usr/lib64/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10. Deprecation warnings can be disabled by setting deprecation_warnings=False
in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

[WARNING]: Skipping plugin (/usr/share/ceph-ansible/plugins/filter/test_ipaddrs_in_ranges.py) as it seems to be invalid: cannot import name
ipaddrs_in_ranges

PLAY [osds] *************************************************************************************************************************************************

TASK [Gathering Facts] **************************************************************************************************************************************
Thursday 05 November 2020  13:45:24 +1300 (0:00:00.463)       0:00:00.464 *****
ok: [node03]
ok: [node02]
ok: [node01]
ok: [node04]
ok: [node05]

TASK [find device used for operating system] ****************************************************************************************************************
Thursday 05 November 2020  13:45:49 +1300 (0:00:25.089)       0:00:25.554 *****
skipping: [node01]
skipping: [node02]
skipping: [node03]
skipping: [node04]
skipping: [node05]

TASK [resolve root_device] **********************************************************************************************************************************
Thursday 05 November 2020  13:45:50 +1300 (0:00:01.354)       0:00:26.908 *****
fatal: [node01]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/osd.yml': line 10, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: resolve root_device
          ^ here
fatal: [node02]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/osd.yml': line 10, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: resolve root_device
          ^ here
fatal: [node03]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/osd.yml': line 10, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: resolve root_device
          ^ here
fatal: [node04]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/osd.yml': line 10, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: resolve root_device
          ^ here
fatal: [node05]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'

    The error appears to be in '/usr/share/ceph-ansible/osd.yml': line 10, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: resolve root_device
          ^ here
        to retry, use: --limit @/home/owolfi/ansible/ansible-retry/osd.retry

PLAY RECAP **************************************************************************************************************************************************
node01       : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0
node02       : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0
node03       : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0
node04       : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0
node05       : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0

Thursday 05 November 2020  13:45:51 +1300 (0:00:00.847)       0:00:27.755 *****
===============================================================================
Gathering Facts ------------------------------------------------------------------------------------------------------------------------------------- 25.09s
find device used for operating system ---------------------------------------------------------------------------------------------------------------- 1.35s
resolve root_device ---------------------------------------------------------------------------------------------------------------------------------- 0.85s

$ ansible-playbook osd.yml --limit @/home/owolfi/ansible/ansible-retry/osd.retry
/usr/lib64/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10. Deprecation warnings can be disabled by setting deprecation_warnings=False
in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

[WARNING]: Skipping plugin (/usr/share/ceph-ansible/plugins/filter/test_ipaddrs_in_ranges.py) as it seems to be invalid: cannot import name
ipaddrs_in_ranges

PLAY [osds] *************************************************************************************************************************************************

TASK [find device used for operating system] ****************************************************************************************************************
Thursday 05 November 2020  13:59:27 +1300 (0:00:00.703)       0:00:00.703 *****
ok: [node03]
ok: [node02]
ok: [node04]
ok: [node05]
ok: [node01]

TASK [resolve root_device] **********************************************************************************************************************************
Thursday 05 November 2020  13:59:29 +1300 (0:00:02.284)       0:00:02.988 *****
ok: [node01]
ok: [node02]
ok: [node03]
ok: [node04]
ok: [node05]

TASK [set_fact root_device] *********************************************************************************************************************************
Thursday 05 November 2020  13:59:31 +1300 (0:00:01.379)       0:00:04.368 *****
ok: [node01]
ok: [node02]
ok: [node03]
ok: [node04]
ok: [node05]

PLAY RECAP **************************************************************************************************************************************************
node01       : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
node02       : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
node03       : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
node04       : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
node05       : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

Thursday 05 November 2020  13:59:31 +1300 (0:00:00.865)       0:00:05.233 *****
===============================================================================
find device used for operating system ---------------------------------------------------------------------------------------------------------------- 2.29s
resolve root_device ---------------------------------------------------------------------------------------------------------------------------------- 1.38s
set_fact root_device --------------------------------------------------------------------------------------------------------------------------------- 0.87s


lets remove all type: LoadBalancer from quickstarts and use label expose: true instead

see this issue for background https://github.com/fabric8io/fabric8-maven-plugin/issues/341

It looks like the quickstarts are not using LoadBalancer anymore?
Also I wonder if the f-m-p don't add expose by default?
Do we need to have these service yml files anymore?
https://github.com/fabric8-quickstarts/spring-boot-webmvc/blob/master/src/main/fabric8/svc.yaml

In fact it should be automatically added by the ExposeEnricher if the port is one of 80, 443, 8080 or 9090

Okay there is a bunch left
./cdi-cxf/src/main/fabric8/service.yml:  type: LoadBalancer
./infinispan-server/src/main/fabric8/service.yml:  type: LoadBalancer
./spring-boot-cxf-jaxrs/src/main/fabric8/deployment.yml:  type: LoadBalancer
./spring-boot-cxf-jaxws/src/main/fabric8/deployment.yml:  type: LoadBalancer
./spring-boot-hystrix/src/main/fabric8/service.yml:  type: LoadBalancer
./spring-boot-ribbon/src/main/fabric8/service.yml:  type: LoadBalancer
./vertx-simple/src/main/fabric8/service.yml:  type: LoadBalancer
./vertx-web/src/main/fabric8/service.yml:  type: LoadBalancer

I am not sure if vertx is detected as port 8080 or something and thus required there. But the fmp may get a vertx detector to find that automatic in the future.
But for the SB then we ought to detect the port and do this OOTB now, so they can likely be removed.

We are down to only
./cdi-cxf/src/main/fabric8/service.yml:  type: LoadBalancer
./infinispan-server/src/main/fabric8/service.yml:  type: LoadBalancer
./vertx-simple/src/main/fabric8/service.yml:  type: LoadBalancer
./vertx-web/src/main/fabric8/service.yml:  type: LoadBalancer

Okay the have all been migrated now.
However vertx-simple has not as its dead, and replaced with vertx-web. We will delete this git repo in the near future.


VSCode markdown preview from "Dendron: Show Preview" does not match color theme

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Describe the bug
The theme of Dendron: Show Preview and Dendron: Show Preview v2 does not match my selected color theme (Atom One Dark). Instead, the rendered theme appears to be the default dark theme.

To Reproduce

Enable a non-standard color theme in VSCode.
Preview Dendron using Dendron: Show Preview and Dendron: Show Preview v2 and observe the inconsistent colors.

Expected behavior
The preview to match the selected theme, similar to how the normal Markdown preview works.

Screenshots
See above.
Desktop (please complete the following information)

OS: MacOS version 11.5.2
VSCode: version 1.60.1
Dendron: version v0.59.1
Browser: Chrome, Version 93.0.4577.82 (Official Build) (x86_64)

This issue also appears with other themes, and on my second computer, so I don't think it is related to my particular setup.

Dendron currently does not allow for custom theming of either the preview or the published site. This is one of our highest request features in regards to preview and publishing.

from https://wiki.dendron.so/notes/PjXL1NKL7yHV0ExHnROBl.html#context

Good to know. Thanks!


Adding in sys exit of status and using kuberenetes client for requests

Description
Even though we had worked on a different PR for fixing all kubectl and oc commands to use the KUBECONFIG set from the cerberus config. When running in jenkins, that workaround did not work properly I would still get errors like the below. I edited the way to get pods and get nodes to use the kubernetes python client instead. The couple of commands I could not find in the kuberenetes client I added the "--kubeconfig" option to the oc/kubectl calls.
Also in running in jenkins I noticed we never exit with a status based on the true/false that's published.


[#5514] Adding simple data methods

Fix https://github.com/Azure/azure-sdk-for-java/issues/5514 and https://github.com/Azure/azure-sdk-for-java/issues/5516

Not to be implemented like this


Install fails on long webappprefix name

Describe the bug
Install fails on long webappprefix name
To Reproduce
Steps to reproduce the behavior:

Add a long Webapp Prefix to the install script
Issue: Install fails to create webapp due to max char length

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Are you using the CloudShell?
If not using the CloudShell:

OS: [e.g. iOS]
PowerShell version
Modules installed

Additional context
Add any other context about the problem here.

It already works.

@code4clouds raised this from your feedback, but seems to work. If you think otherwise please reopen


Split person for David Lawrence Miller

Has three different persons in the DB. See https://twitter.com/millerdl/status/663818098475196416 for URLs.

http://depsy.org/person/333208
http://depsy.org/person/438045
http://depsy.org/person/435249

Fixed :)
Here's the merged profile:  http://depsy.org/person/333208


Fail the context to start if both Brave and OTel is on the classpath

https://github.com/spring-cloud/spring-cloud-sleuth/issues/1855

The current Sleuth OTel conditions to run OTel are such that you have to set spring.sleuth.tracer.mode=AUTO and if you have Sleuth OTel on the classpath then we will pick OTel over Brave. I'm starting to wonder if we should actually fail the context if you have both. We could print out a warning that you have both and you should consider excluding one, wdyt @jonatan-ivanov ?

Potential solution - https://github.com/spring-cloud-incubator/spring-cloud-sleuth-otel/pull/37

I agree that making an opt-out version that throws an exception is better. @jonatan-ivanov I've closed my PR, please feel free to create your own.


discarding secondary aligmnent needed for some metrics to strictly abide by their definition

https://github.com/c-BIG/NPM-sample-qc/blob/8557652cd606d843c1352eeea899b1827629caf0/bin/metrics/metrics.py#L189
Picard CollectMultipleMetrics (used here picard CollectInsertSizeMetrics) does not allow for secondary alignment filter as an option.
So this step need to be precedded by a process which will actively remove secondary alignment

Same issue with
https://github.com/c-BIG/NPM-sample-qc/blob/8557652cd606d843c1352eeea899b1827629caf0/bin/metrics/metrics.py#L43

Opened with another commit (latest)


Is Apollo required?

I am getting this error typeormGetConnection is undefined, and I am unsure why. The docs indicate that Apollo isn't required, but I am unsure if this is the because of this error.

If your application uses Apollo Server, pass ApolloServerLoaderPlugin() as a plugin when instantiating the server.

It is required to do what is done in ApolloServerLoaderPlugin() against each request pre-call and post-call. So, if apollo-server is used, just passing ApolloServerLoaderPlugin() as plugin would work. Otherwise,  calling ApolloServerLoaderPlugin.requestDidStart and ApolloServerLoaderPlugin.willSendResponse against each request might work.

I am getting this issue as well. There have been many breaking changes with Typeorm 0.3.0+ . I'm reverting to Typeorm 0.2.45 for now until other packages that I use (TypeDI, TypeGraphql) are able to catchup.


What's the best way to update annotations?

The repository is currently using annotations from a year ago. The idea of updating the annotations manually with each release sounds bad. Is there any way to automate updating them in this repository?
I've created the annotation generator (https://github.com/astrochili/defold-annotations) that can be run on any server that has Lua. Also it automatically checks for Defold updates every day and makes a release of new annotations if needed. Is there any way this could help?

There are aloso other options where updated annotations can be found:

https://github.com/d954mas/defold-api-emmylua/ (Java)
https://github.com/mikatuo/defold-lua-annotations/ (C#)

Many thanks for your interest! We want to make a tighter integration of lua language server and defold, although we haven't decided yet on the details. Eventually, we want to bundle the language server in the editor, and perhaps make the editor prep theb annotations from it's own engine docs and script_api files.

That's a good idea. I guess the lua files will be available in the jar archive of the editor? All the time I'm in a hurry to implement something that is already planned :D

I guess the lua files will be available in the jar archive of the editor?
This is the part of the details we haven't decided upon yet :D
Maybe it will be generated on the fly and communicated to the language server. script_api files can be added/removed when adding/removing dependencies or they can be edited as files in the project file tree, so there is a need for some dynamicity. Do you have a use case for annotation files other than to use in the editor for e.g. linting and code completion?

Do you have a use case for annotation files other than to use in the editor for e.g. linting and code completion?

Of course the case is using in VSCode. It works like shooting fish in a barrel. Just install Lua Language Server extension for VSCode and add somewhere Defold lua annotations.
First I wrote an VSCode extension that parsed sdoc files from the editor's jar archive so that the annotations would always match the installed version of Defold and would not be downloaded from anywhere else.
But since sdoc was declared a bit outdated format, and it's easier to parse json, I went the way of downloading and parsing documentation in json files from editor releases. And want to place these annotations automaticaly somewhere in shared space of my VSCode extension outside the game project.

script_api files can be added/removed when adding/removing dependencies or they can be edited as files in the project file tree, so there is a need for some dynamicity.

That's a good point. Now I understand that not everything is so simple and obvious.


BUG CSV Export functionality doesn't respect UTF8 extended characters

From https://github.com/silverstripe/silverstripe-userforms/issues/402
The CSV export in this add-on is not working for languages like Persian & Arabic and i can't set char-set to UTF-8

Also see https://github.com/silverstripe/silverstripe-cms/issues/1335

https://github.com/silverstripe/silverstripe-framework/pull/7833 may have resolved this

This definitely won't be a problem in 4.x (he says)
I'm not sure 3.x will see any more love around this; I did quite a bit of investigation in the BOM stuff and it was a pain. I'm loathed to handroll code to fix this. There's no realistic league/csv version to use that matches our PHP version requirements so I think think this is going to remain an issue except when someone decides to create their own UTF-8 exporter.

#wontfix for SS3 IMO.


[draft] fix ssl

ssl certs - is nice
curl / bash / toInt64(value) - motivation need to be clarified.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update troubleshoot to v0.93.1

What this PR does / why we need it:
Update troubleshoot to the current version:
ce15527 (tag: v0.93.1) fix: Use correct cron job kind when discovering API versions (#1554)
91da8f1 chore(deps): bump azure/docker-login from 1 to 2 (#1552)
1a8aff1 chore(deps): bump the security group with 9 updates (#1551)
ece20d3 chore(deps): bump helm.sh/helm/v3 from 3.15.0 to 3.15.1 in /examples/sdk/helm-template in the security group (#1550)
80e5fac (tag: v0.93.0) feat: New host collector and analyzer for Kernel Configs (#1546)
51c07b4 (tag: v0.92.2) feat(analyzer): let cluster resource case insensitive to fix name inconsistent (#1547)
bd7bae6 chore(deps): bump the security group with 9 updates (#1549)
9d41460 chore(deps): bump helm.sh/helm/v3 from 3.14.4 to 3.15.0 in /examples/sdk/helm-template in the security group (#1548)
fb0f81d bug: [sc-103753] Host analysers are not deduplicating during multiple spec merges #1485 (#1542)

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

NONE

Does this PR require documentation?

this is a dup of #4652 which has merge conflicts


Folder option disabled.

Hi Jason, love the idea behind GAPS (Unraid/Docker) just small issue, I'm not using PLEX and really was looking forward to use the folder option. Could you add the option in the next update if possible.
Thanks and keep up the good work.
P.S. I am not using Plex but Emby could that be something for a future release.....

Thanks, I'm glad to hear it. Folders are going to be tough but I'm planning to re-add it. I have a huge update coming soon and then can work on folders next. I haven't used Emby, but it looks like they might have an API I can tap into. https://github.com/MediaBrowser/Emby.ApiClient I'll put it on the list.

Being able to select folders for gaps to use just based on filenames of files in the folders would be more than enough.


Support Habanas' Gaudi Accelerator

🚀 Feature
Recently Intel's Habana Labs announced AWS nodes for their Gaudi Accelerator. As described in the reddit post there seems to be a lot of potential for model parallel solution that require fast interconnect between processors.
Looking at the pytorch migration guide there is room for lightning to assist in making this process seamless, helping users to not have to worry about this details (especially around the KCRS -> RSCK format for convolutions).
I suggest we introduce a new accelerator type such that we can enable this in lightning through the accelerator flag, i.e:
trainer = Trainer(accelerator='hpu')

HPU is what the accelerator seems to be called within the migration guide.
cc @borda

just for the record: #12258 and #12200


events in scipy.integrate.solve_ivp: How do I setup an events criteria?

In the following code, I simulate a parashoot in free fall. I want the simulation to stop at the ground (y = 0) or one point below. Currently, I have the problem, that the simulation terminates around y = 8.77... above 0. How can I set up the termination event?
Reproducing code example:
g = 10
k = 0.01

def para(t,Y):
    y1 = Y[0]
    y2 = Y[1]
    dy1_dt = y2
    dy2_dt = -g + k*y2**2
    return [dy1_dt,dy2_dt]

def hit_ground(t, Y): return Y[0]

import numpy as np
tend = 40
time = np.linspace(0,tend,100)
tspan = (0, tend)

Y0 = [1000,0]

from scipy.integrate import solve_ivp
hit_ground.terminal = True
Y = solve_ivp(para,tspan,Y0,events=hit_ground,t_eval=time)

if Y.status == 1:
    print('Success, termination event occured.')
if Y.status == 0:
    print('Success, t end reached.')

plt.plot(Y.t,Y.y[0,:],'k-',label='Y')
plt.plot(Y.t,Y.y[1,:],'r-',label='dY/dt')
plt.xlabel('Time')
plt.ylabel('Hight')
plt.legend()
plt.grid()
plt.xlim(0,Y.t[-1]+5)

Definitely not the expected result.  Using t_eval with events causes the event time point to not be appended to the result as you found out.  I suggest until this is fixed that you remove t_eval from the call to solve_ivp and use dense_output=True and then generate your y values at t_eval  using the returned sol attribute.

For very long and complex simulations, dense_output is not always a possibility, as it increases the memory usage considerably. I think that given that a terminal event will prevent solution.t from being equivalent to t_eval anyway, it would not be unreasonable to include the terminal event time in solution.t. Either that, or the y_events could be returned along with t_events, so that you can easily append the terminal state onto solution.y if needed.

After #10672 merged, the solve_ivp result contains y_events for corresponding t_events.
@deschenk feel free to reopen if you think that it is not properly resolved.


Introduce staging binary cache to reduce our binary cache size

The idea is to have buckets to test VCL configuration on them.
In particular I want to create a new S3 bucket that we would start pushing to with hydra.
The VCL rules in fastly would check both buckets for the migration period.
After we have migrated the part of the binary cache that we are interested,
we make the VCL rules only hit the new bucket.
After that we add an archiving rule to transition the old bucket to aws glacier: https://aws.amazon.com/blogs/aws/archive-s3-to-glacier/

What's this migration all about?

@edolstra to reduce AWS costs on our binary cache.

@Mic92 Yeah but why do we need a separate bucket for that? The way I imagine doing GC is that the GC process would set a tag on objects that we consider garbage, and then we can have a lifecycle rule that moves them to Glacier. As an intermediate step, we could have an access control rule that only makes them inaccessible (so if we screw up, we can restore them more cheaply than from Glacier).

@edolstra sounds easier actually. I thought it might be also expensive to run api requests on all objects. But it looks like it's still doable:
Let's say we need 1-2 requests per object it would be ({1,2} * 889587727) / (1e6) = 889.5 -> 1779.1
What would be the best way to find all the objects to keep.

Okay, so I also had a chat with @edef1c who is working on a more sound gc algorithm.
@zimbatm also documented the current tools and what needs to be done (hopefully soon documented in a more public state)
From that I saw that it's actually not so trivial to get the list of all live store paths for this big bucket.
So here is my plan B in case we cannot make the gc work soon enough:

We would just deploy this solution and make hydra push to the new bucket. Old store paths would be accessible through the old bucket and new data in the new bucket. Fastly will check both.
We remove the old bucket from fastly after some transition period.
After some testing period, we send the whole old bucket to glacier.

If someone wants to suggest a technically better solution, they are welcome to implement it.

I think this staging infrastructure is already useful on its own to test new configuration with fastly without breaking cache.nixos.org. So I am going to merge this.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2024-07-10-long-term-s3-cache-solutions-meeting-minutes-7/48821/4

Let's say we need 1-2 requests per object it would be ({1,2} * 889587727) / (1e6) = 889.5 -> 1779.1 Dollar

That's pretty acceptable as a one-time cost.

What would be the best way to find all the objects to keep?

I once wrote a nix command that determines the closure of all reachable store paths from the store-paths.xz files of the NixOS/Nixpkgs releases (and whatever other roots we might want to keep).

@edolstra great. We can use consider this command if someone also provides the actual GC scripts. Does this run the check single threaded? How long do you think it would take to process a single eval? @edef1c also pointed out that tagging s3 objects can be potential dangerous because hydra might start referring to the objects that we considered dead. She was proposing to enable versioning and delete the current version of the narinfo instead so that hydra would re-create it. I will proceed testing my two-bucket option further with a staging hydra, but please don't feel blocked on improving your gc alternative. We should certainly use it if it's ready in time.


HttpAdminServices configuration in carbon.xml is not templated.

Describe the issue:
HttpAdminServices configuration is used to expose all AdminServices in HTTP transport. The Axis2Config —> HttpAdminServices configuration in carbon.xml is not templated, hence cannot be configured from the deployment.toml.
Expected behavior:
This config should be configurable through the deployment.toml
Environment information :

Product Version: [IS 5.10.0]

Hi @tharakawijekoon ,
What is the requirement to expose all AdminServices in HTTP transport? Can you explain the requirement?

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Allow content-tagger to deal with specialist-publisher content

As part of migrating specialist-publisher tagging to content-tagger,
allow content-tagger to handle browse pages and topics for specialist-publisher.
We already prevented panopticon from handling specialist-publisher tags
(https://github.com/alphagov/panopticon/pull/357 and https://github.com/alphagov/panopticon/pull/358).
We make an exception for the link type 'topics' for specialist-publisher finders.
Specialist publisher still hardcodes these, and they are not yet in publishing-api,
so it is not safe to handle them in content-tagger.
https://trello.com/c/YoeWtswr/609-totally-migrate-specialist-publisher-v1-tagging

LG


Auto load nnedi plugin when using nnedi3_rpow2 function please

Hello Stax,
When creating a custom filter using nnedi3( ) the line to load the nnedi3 plugin is automatically added into the avs script.
Will it be possible to add this too when the nnedi3_rpow2( ) function of nnedi3  is used in a custom made filter please ?
For example i create a filter :
nnedi3_rpow2(2, cshift="Spline36Resize", fwidth=%target_width%, fheight=%target_height%)
and the plugin line will be automatically added into the avs script like when creating a simple nnedi3 filter
Somewhat a simple rule like : nnedi3 or nnedi3_rpow2 = auto call nnedi3 plugin
PS: I know i can add the line to load the plugin directly into the filter I created, just wondering if it won't be "cleaner" to auto load it as other recognized plugins in the Staxrip program.
Thanks a lot in advance

Hi,
it will work in the next build, I think you can also use a commend meanwhile:
#nnedi3(

Thanks a lot for this, really appreciate it.


Display the Rewards on Portfolio

right now the portfolio when ADA is selected it shows the link to cardano website which is useless, can we move the rewards data into the portfolio, cuz it is annoying to have to jump to rewards and add it mentally to the balance to grasp the entire $$ value

right now the portfolio when ADA is selected it shows the link to cardano website which is useless, can we move the rewards data into the portfolio, cuz it is annoying to have to jump to rewards and add it mentally to the balance to grasp the entire $$ value

I get what you mean about the portfolio showing the link to the Cardano website when ADA is selected—it doesn't really add much value. Moving the rewards data directly into the portfolio would definitely streamline things and make it easier to see the total value without having to jump back and forth. This change could enhance the user experience significantly by providing a clearer picture of the overall balance in one place. If you have more suggestions or need assistance with anything else, just let me know!
@portssa


Allow launch wizard for Azure images

Adds feature flagged Azure support.
Depends on https://github.com/RHEnVision/provisioning-frontend/pull/224

/retest


MM-18972

Summary
Migrated following javascript files to Typescript
components/widgets/settings/-

[X] bool_setting & test
[X] radio_setting & test
[X] setting & test
[X] text_setting & test

Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/12456

@hanzei this is because we removed prop-types missing in props validation react/prop-types since we are using typescript

Also let me know if this is a good approach (working with TS first time) so i can continue on other two files

Hey @M-ZubairAhmed! Approach looks good, just a couple small comments.
As for the lint errors, though should be disappearing once you remove PropTypes from the file, so I'm not sure what's happening there.

This seems to be happening only functional components not for class components

@devinbinnie i have fixed the changes

@M-ZubairAhmed take a look at components/loading_image_preview.tsx, it's a functional component that is passing the linter. Maybe there's something in there that would help?

@M-ZubairAhmed You have some tests failing:
Summary of all failing tests
 FAIL  components/interactive_dialog/dialog_element/dialog_element.test.jsx
  ● components/interactive_dialog/DialogElement › subtype email

    TypeError: Cannot read property 'includes' of undefined

      127 |                 maxLength = maxLength || TEXT_DEFAULT_MAX_LENGTH;
      128 |
    > 129 |                 if (subtype && TextSetting.validTypes.includes(subtype)) {
          |                                                       ^
      130 |                     type = subtype;
      131 |                 } else {
      132 |                     type = 'input';

      at DialogElement.includes [as render] (components/interactive_dialog/dialog_element/dialog_element.jsx:129:55)
      at ReactShallowRenderer._mountClassComponent (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:809:37)
      at ReactShallowRenderer.render (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:738:14)
      at render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:53)
      at fn (node_modules/enzyme-adapter-utils/src/Utils.js:99:18)
      at Object.render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:18)
      at new render (node_modules/enzyme/src/ShallowWrapper.js:397:22)
      at shallow (node_modules/enzyme/src/shallow.js:10:10)
      at Object.it (components/interactive_dialog/dialog_element/dialog_element.test.jsx:50:25)

  ● components/interactive_dialog/DialogElement › subtype invalid

    TypeError: Cannot read property 'includes' of undefined

      127 |                 maxLength = maxLength || TEXT_DEFAULT_MAX_LENGTH;
      128 |
    > 129 |                 if (subtype && TextSetting.validTypes.includes(subtype)) {
          |                                                       ^
      130 |                     type = subtype;
      131 |                 } else {
      132 |                     type = 'input';

      at DialogElement.includes [as render] (components/interactive_dialog/dialog_element/dialog_element.jsx:129:55)
      at ReactShallowRenderer._mountClassComponent (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:809:37)
      at ReactShallowRenderer.render (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:738:14)
      at render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:53)
      at fn (node_modules/enzyme-adapter-utils/src/Utils.js:99:18)
      at Object.render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:18)
      at new render (node_modules/enzyme/src/ShallowWrapper.js:397:22)
      at shallow (node_modules/enzyme/src/shallow.js:10:10)
      at Object.it (components/interactive_dialog/dialog_element/dialog_element.test.jsx:65:25)

  ● components/interactive_dialog/DialogElement › subtype password

    TypeError: Cannot read property 'includes' of undefined

      127 |                 maxLength = maxLength || TEXT_DEFAULT_MAX_LENGTH;
      128 |
    > 129 |                 if (subtype && TextSetting.validTypes.includes(subtype)) {
          |                                                       ^
      130 |                     type = subtype;
      131 |                 } else {
      132 |                     type = 'input';

      at DialogElement.includes [as render] (components/interactive_dialog/dialog_element/dialog_element.jsx:129:55)
      at ReactShallowRenderer._mountClassComponent (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:809:37)
      at ReactShallowRenderer.render (node_modules/react-test-renderer/cjs/react-test-renderer-shallow.development.js:738:14)
      at render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:53)
      at fn (node_modules/enzyme-adapter-utils/src/Utils.js:99:18)
      at Object.render (node_modules/enzyme-adapter-react-16/src/ReactSixteenAdapter.js:666:18)
      at new render (node_modules/enzyme/src/ShallowWrapper.js:397:22)
      at shallow (node_modules/enzyme/src/shallow.js:10:10)
      at Object.it (components/interactive_dialog/dialog_element/dialog_element.test.jsx:80:25)

 FAIL  components/widgets/settings/text_setting.test.tsx
  ● components/widgets/settings/TextSetting › render component with required props

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `components/widgets/settings/TextSetting render component with required props 1`

    - Snapshot
    + Received

    @@ -5,11 +5,11 @@
        labelClassName=""
      >
        <input
          className="form-control"
          id="string.id"
    -     maxLength={null}
    +     maxLength={-1}
          onChange={[Function]}
          type="input"
          value="some value"
        />
      </Setting>

      17 |             />
      18 |         );
    > 19 |         expect(wrapper).toMatchInlineSnapshot(`
         |                         ^
      20 | <Setting
      21 |   inputClassName=""
      22 |   inputId="string.id"

      at Object.toMatchInlineSnapshot (components/widgets/settings/text_setting.test.tsx:19:25)

  ● components/widgets/settings/TextSetting › render with textarea type

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `components/widgets/settings/TextSetting render with textarea type 1`

    - Snapshot
    + Received

    @@ -5,12 +5,12 @@
        labelClassName=""
      >
        <textarea
          className="form-control"
          id="string.id"
    -     maxLength={null}
    +     maxLength={-1}
          onChange={[Function]}
    -     rows="5"
    +     rows={5}
          style={Object {}}
          value="some value"
        />
      </Setting>

      47 |             />
      48 |         );
    > 49 |         expect(wrapper).toMatchInlineSnapshot(`
         |                         ^
      50 | <Setting
      51 |   inputClassName=""
      52 |   inputId="string.id"

      at Object.toMatchInlineSnapshot (components/widgets/settings/text_setting.test.tsx:49:25)

Snapshot Summary
 › 2 snapshots failed from 1 test suite. Inspect your code changes or run `npm run test-ci -- -u` to update them.

Working on it

@devinbinnie thanks for the suggestion , all tests are now passing, please review the the pr

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

How is this state PR, when it was approved by the team member ??

Hey @M-ZubairAhmed! Looks like it just needs one more review from @catalintomai and it's ready to go.
@catalintomai when you have time, can you help review this PR from @M-ZubairAhmed?

Hey @M-ZubairAhmed! Looks like it just needs one more review from @catalintomai and it's ready to go.
@catalintomai when you have time, can you help review this PR from @M-ZubairAhmed?

@jasonblais , how many core committer review approvals do community members PRs need? I believe this one had two already.

@catalintomai Each PR requires two dev reviews, and a QA review where applicable. I believe Saturn's review would apply for QA review in this case.

@catalintomai Each PR requires two dev reviews, and a QA review where applicable. I believe Saturn's review would apply for QA review in this case.

Thanks. Saturnino's infotag above has "Core Committer" in it. Maybe we should update the doc and explicitly refer to dev core committers as opposed to QA Core Committers/or QA short.

I am very impressed by review process of this project, let me check out more issues so i can contribute to this project.


Document TOC hierarchy inconsistent

It seems inconsistent with other Azure product documents that a "Artifact Cache" feature is only documented in Tutorials and not mentioned in Concepts or How-To Guides

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

ID: dbf84d44-59ce-ffad-8963-7e8820d836a9
Version Independent ID: 5d9981f1-ee37-a640-c626-9dca55056b8d
Content: Artifact Cache - Overview - Azure Container Registry
Content Source: articles/container-registry/tutorial-artifact-cache.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@zojovano
Thanks for your feedback! We will investigate and update as appropriate.

@zojovano
Thank you for bringing this to our attention.
I've delegated this to content author @tejaswikolli-web, who will review it and offer their insightful opinions.

@tejaswikolli-web
Could you please review add comments on this, update as appropriate.

changed it.
#please-cose

#please-close


Add support for diverging scales

Create a version of scale_colour_gradient2() for diverging palettes, that takes a specified input value.

Added in version <IP_ADDRESS>00 - scheduled for release on CRAN with version 1.0.2


Chrome Often Leaves Filehandles Open

After several weeks of running on 80+ devices, /tmp/.com.google.Chrome.* will have thousands of directories.  Something is not closing right.  How can we fix it?

This is kind of hacked / solved with https://github.com/KristopherKubicki/glimpser/pull/41


Duplicate workspace names on creation

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

With the recent movement to auto-create workspace on click of "New Workspace", we're not asking for the workspace name and hence clicking multiple times it creates workspace with the same name (username)
Action Performed:

Go to FAB, click on New Workspace
Go back to the Home page and then click on New Workspace again
Go to the sidebar you'll see both the workspaces have the same name.

Expected Result:
Should've created workspaces with different names.
Actual Result:

Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @zanyrenney (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Proposal
Ideally, this should be handled at the backend, as we're sending the policyName empty in the policy_create API call.
If at all we plan to solve at the client-side:
We can either SidebarScreen or actions/Policy.js addd a default name generator.

Approach 1 - Append timestamp

policyName: `${email.match(/^.+(?=@)/)[0]} ${new Date().getTime()}`

Approach 2 - Append random names
https://gist.github.com/tkon99/4c98af713acc73bed74c

Approach 3 - Random characters

 policyName: `${email.match(/^.+(?=@)/)[0]} ${uid(6)}`

Triggered auto assignment to @Dal-Papa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Hi @mananjadhav ! Thanks for your input.
Ultimately we expect users to create a single workspace in the vast majority of cases, and anyone creating multiple workspaces has a more advanced setup where they will need to change the name so they can differentiate between them. There is also plans to have a "Configure Workspace" step after the first one gets created.
So we won't need that for now.

Thanks for clarification


Feature/1.2

Latest Changes:
Enable SDK to hide message prompt in the login/register process

I've resolved the conflicts.


[19983] Split the CustomStdLogConsumer into a BaseLogConsumer and a StdLogConsumer.

In this version, the CustomStdLogConsumer has been split into two: a BaseLogConsumer that filters the logs based on their kind and content and a StdLogConsumer that prints the logs through std.

Codecov Report
Attention: Patch coverage is 0% with 54 lines in your changes are missing coverage. Please review.

Project coverage is 68.14%. Comparing base (20b5978) to head (83ef3e1).

Files
Patch %
Lines

cpp_utils/src/cpp/logging/LogConfiguration.cpp
0.00%
25 Missing :warning:

cpp_utils/src/cpp/logging/StdLogConsumer.cpp
0.00%
17 Missing :warning:

cpp_utils/src/cpp/logging/BaseLogConsumer.cpp
0.00%
11 Missing :warning:

...tils/include/cpp_utils/logging/BaseLogConsumer.hpp
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   69.96%   68.14%   -1.83%
==========================================
  Files          60       62       +2
  Lines        1455     1491      +36
  Branches      388      401      +13
==========================================
- Hits         1018     1016       -2
- Misses        212      249      +37
- Partials      225      226       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Added line follower as a submodule. Check readme.

Hey, thanks for the pull!
Would you prefer to put this in its own repo, maybe "smarc_control", where we can put all the other control stuff as well? I'll create it anyways, then we can decide what to do.
On another note, I much prefer git subtree to submodules. Submodules are harder to discover and harder for people who are not familiar with the concept. In this case though, I think e.g. the "smarc_control" repo could contain the master branch, and you could work on your fork, discarding the need for subtrees or submodules altogether.

I've added a new repo here: https://github.com/smarc-project/smarc_control . As said above, I would suggest adding your package within that repo, either with subtree or by moving things around.

Alright, I'll look into subtrees and pull to smarc_control after fixing
some bugs around. I want my utils to be a separate repo since I use those
things everywhere.
Maybe a smarc_planning would make sense too in the future?
On 16 February 2018 at 14:34, Nils Bore<EMAIL_ADDRESS>wrote:

I've added a new repo here: https://github.com/smarc-project/smarc_control
. As said above, I would suggest adding your package within that repo,
either with subtree or by moving things around.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/smarc-project/smarc_base/pull/1#issuecomment-366236260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGvGOSGxE6jT6HTCfx1eq1293a49BfDQks5tVYPcgaJpZM4SIUeG
.

Thanks, I appreciate the effort. "smarc_planning" would definitely make sense as well. Tell me when you want it and I'll create that as well.


Rename Dict.setdefault().

The function setdefault() in Dict is kind of confusing to read, because it's not clear that it only sets a default if the value is missing.  We should debate possible variations on chat:

children.setdefault(name, []); // current way to do it
children.set_or_get(name, []);
children.set_or_get({key: name, default: []);
other possibilities?

Once we we get consensus, we can sweep the code to fix.

I think what we have is exactly the interface of the setdefault method in Python, which I'm guessing is where the name came from.  The function would just be called set if it set the thing unconditionally.  I think get_or_set is another name I've seen for this sort of thing, but I'm not sure it'd be clearer.

Yeah, if we can't come up with a clearly superior name, we can close this.  This came up when @adnrs96 and I were looking at some code.  The setdefault idiom is something that not all programmers know about it.  But the function is definitely useful, because it's hard to write the idiom in a non-clumsy way without the helper.

One subtle, but important, difference between our dict.js setdefault and the setdefault in Python is that the latter is parameterized with a function, so it only builds default objects when there is no value for the key.  Our JS code, on the other hand, forces users to create tiny empty objects when they're not going to be used.
Despite that, I'm closing this anyway, because it still doesn't seem super actionable.


[Feature Request] Abyss Jewels

It would be nice to add abyss jewel support
sites like https://poecraft.com/jewels already have the mods, so it shouldn't be too hard to add them

Please have patience. The league has been live for less than 2 days, and in between playing sessions I haven't had nearly enough time to implement all the new mechanics and content, of which there is a hell of a lot this time around.

Hi is there an ETA for when this feature will be available? Maybe even releasing it in pieces since there are a lot of changes.

@blake59: in the meantime, you can just add the jewel's stats on random pieces of your gear.

You can make custom jewels with the stats. It's just a bit of work ATM and you need to look them up every time

Full support for Abyss Jewels is coming in the next update, which should be out within the next day.


Network Graphs have no content

I have LCC running on a Raspberry Pi 5 successfully, except the Network component graphs are vacant.
The displayed IPs, Local and External, are correct.
The up/down textual values appear to be active and correct.
I have never seen anything displayed in any of the graph spaces.
All other component graphs are apparently populating correctly.

Apparently the downspeedgraph and upspeedgraph functions are now different, and maybe buggy.
I have insufficient knowledge about Lua to figure out much of this, so it would be great if someone could.
LCC does everything I want from Conky and does it very well, except for this bug.
I am running RPi5 (Linux 6.1.0-rpi8-rpi-2712)
conky 1.18.3
LCC 0.8.0
Lua 5.1.5
Thanks, Dave

Ahh...  I see that Issue No. 8 describes this problem and suggests a fix.  I works for me.  Sorry for not reading every issue before posting.


add whisper normalization on training

Hi :D
In the present whisper finetuning implementation, we are training with raw text (no normalisation) and then we do testing and validating using whisper normalisation. This is a little adjustment to fine-tune the model on whisper normalisation, as encode only accomplishes tokenisation and not normalisation.

from transformers.models.whisper.tokenization_whisper import WhisperTokenizer

test = "hello i have fifty two dollars"

tokenizer = WhisperTokenizer.from_pretrained("openai/whisper-base")
print(tokenizer._normalize(test))
print(tokenizer.decode(tokenizer.encode(test)))
print(tokenizer.decode(tokenizer.encode(tokenizer._normalize(test))))

#print outputs
hello i have $52
<|startoftranscript|><|notimestamps|>hello i have fifty two dollars<|endoftext|>
<|startoftranscript|><|notimestamps|>hello i have $52<|endoftext|>

taking into account normalized_transcripts param
def text_pipeline(wrd):
  if hasattr(hparams, "normalized_transcripts"):
      wrd =tokenizer._normalize(wrd)
  yield wrd
  tokens_list = tokenizer.encode(wrd)
  # avoid bos and eos tokens.
  tokens_list = tokens_list[1:-1]
  yield tokens_list
  tokens_bos = torch.LongTensor([hparams["bos_index"]] + tokens_list)
  yield tokens_bos
  tokens_eos = torch.LongTensor(tokens_list + [hparams["eos_index"]])
  yield tokens_eos
  tokens = torch.LongTensor(tokens_list)
  yield tokens

Hello @Moumeneb1,
Thanks for the PR! Are you sure they are doing normalisation on the training transcript in the official Whisper paper? If I'm not mistaken they are not doing it but feel free to correct me.
By the way, do you have results on normalised training vs un-normalised training?

Hi :D !
The model produces numbers as numeric values (even without applying normalization), but on datasets like CommonVoice or librispeech for example, the numbers on the transcript are written as text. They don't really talk about this in the article during finetunning, but since the model has this behavior, I think they used it during training as well.
These are some outputs I've got  with Plan Whisper outputs without normalization the output from  and I've got results like

"So if he has $3,000 a month in income",
"all four million. So they'll put, they collect $270",
" by 2060. And it turns out"

Happy holidays btw :D

Hello,
Do you have any results to share? e.g. WER ?
Happy new year :)

Hello @Moumeneb1,
Any news on this PR please?
Thanks!


PowerShell Preview in MS Store still on 7.2-rc.1

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
7.2.0 has been released but PowerShell Preview in the MS Store is still on 7.2-rc.1.
Expected behavior
Preview version should be greater or equal to the stable version.

Actual behavior
N/A

Error details
N/A

Environment data
N/A

Visuals
No response

I guess we should wait 1-2 week after release.

PowerShell Preview and PowerShell are 2 different channels (apps) in MS Store. The former only publish preview releases, and the latter only for stable releases,

It just seemed odd to me that preview is behind stable, but I guess that makes sense if there's no new preview.

Yeah, a new preview will be out in December (I could be wrong on the schedule), and that will be published to the "PowerShell Preview" channel only.

So you guys are telling me that

A new PowerShell stable release is available: v7.2.0
Upgrade now, or check out the release page at:
https://aka.ms/PowerShell-Release?tag=v7.2.0

is the normal and expected experience from PowerShell Preview?
I've never seen a software where its "preview" channel is so disconnected from the main product that it doesn't receive stable updates. It's just fundamentally wrong -- unless you actually want to decommission the channel entirely.

@NatoBoram Please open new issue with your proposal.


[WIP] feat(toast): add pauseTimeoutOnHover functionality to notifications

🔗 Linked issue
Not linked to an issue.
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This pull request introduces a new feature to the Notification component in the src/runtime/components/overlays/Notification.vue file. The changes add a prop to allow pausing the notification timeout on hover.

Added a pauseTimeoutOnHover prop to the Notification component to enable or disable pausing the timeout when the notification is hovered. The default value for this prop is set to true.
Updated the onMouseover and onMouseleave functions to check the pauseTimeoutOnHover prop before pausing or resuming the timer.

Hello team,
I was unsure which part in the documentation you would like to be updated? and that's why i have not included those documentation changes here, yet.
As soon as you suggest which part need to be updated, i will do that. Thank you!

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

I was unsure which part in the documentation you would like to be updated?

You can add that information here, with the related boolean prop:
https://github.com/nuxt/ui/blob/d0e626c55185ba93dd07eb71167e3e6aeed4a013/docs/content/2.components/notification.md?plain=1#L138-L153

Thank you boss!


fix issue #258

Changed SensorStateClass for Inverter Energy Production Day/Month/Year/Total from TOTAL_INCREASING to TOTAL.

Thanks for taking the time to submit this.
I'm not sure this will produce the correct long-term statistics, though. As I understand the docs, the total state class for the daily, weekly and monthly entities would have to be accompanied by a last_reset value in order to exhibit the expected behavior. Support for negative values is not great overall.
We could try to work around this by inverting the sign used by RCT Power for their production measurements such that total_increasing can be used. But that would break statistics for existing installations. :thinking: Do you have any other ideas?

I'm not familiar with the integration's code, nor with the HA docs. But I would believe that the solution MUST be to invert the negative measurements that the RCT API is putting out, because that is where the source of the inconsistency seems to be.
Looking at the outputs of the production measurements (in HA with your integration), there is also an inconsistency between
sensor.rct_power_storage_grid_energy_production_absolute_total - which is positive - and all the other ...grid_energy_production... statistics, which are negative.
The effect is that you cannot use these measures as inputs for the HA "Energy" Dashboard without getting nonsensical statistics for net grid usage, autarky and energy flows/distribution - that obviously also assumes positive numbers throughout to do its accounting!
Thus, I doubt that the existing statistics that people might have from this are actually that useful...

to answer folowing statement from my pov:
you cannot use these measures as inputs for the HA "Energy" Dashboard without getting nonsensical statistics for net grid usage, autarky and energy flows/distribution
I've been comparing the statistics in the inverter and the statistics gathered by homeAssistant/influxDB/Graphana and these seem to be correct. I've also compared data for grid feed between Homeassistant/the inverter/P1 port on digital enerymeter installed by the grid operator (used for my billing) and they are simmilar (allthough the time interval between measurements differ.

Thanks for the reply.
To clarify, since you don't mention the sign problem explicitly: I'm not saying that the statistics weren't correct by their absolute values, but that they arrive at Home Assistant, specifically the Energy dashboard, with the incorrect (negative) sign. And that is where the calculations performed by the Energy dashboard seem to get confused...
This is yesterday's Energie dashboard graphics for me:

And this is the report for yesterday from the RCT Portal:

The configuration screen for the Energy Dashboard throws an error about the grid_production_day... being negative:

Not sure if you can make sense of the German labels for the graphs. I could translate those if needed.
But the issue is that the 'Energieverteilung' graph reports the energy usage of my home to have been 22.8 kWh - which is entirely off, about twice as high as correct. The RCT board has the energy usage to be 11.33 kWh.
I haven't yet found a way to reconstruct the dashboard house consumption values from the RCT outputs, but there must be something...  it might be something weird like the dashboard discarding the 'invalid' negative measurement for grid_production and just hopping to the next variable in an array or such...

Just for info, my integration works OK. No negative sign.

@mqatgit
I believe that your issue comes from not following the proposed setup for the energy dashboard. Here is my setup, using different measurements as proposed in the documentation:

With this, the values in the dashboard closely resemble the ones shown in the RCT portal or the RCT app, except for the home consumption. It appears that the home consumption in HA is calculated from the other values (generation, grid feed, grid load, battery feed, battery load). However, the generation measurement is a DC value (prior to conversion and conversion losses) which is why even with these settings the total consumption always appears a bit higher then in the portal or in the app.

@gutwinski , thank you very much, that is an excellent suggestion, as it indeed fixes my problem with the HA energy dashboard - looking good now!
(But I'm not aware of which part of the documentation - regarding the "proposed setup of the Energy dashboard" - I missed that would have contained that information? I.e., to what proposed setup do you refer?)
However, I still believe that the negative values for grid_production_today etc. are an error that needs to be fixed. Note that, as I said before, ...grid_production_absolute_total is the ONLY positive value among the whole set of grid_production... measures. Which is probably exactly why it works with the dashboard, and the others don't. Also note that the Energy dashboard is fine with measures reported on a daily basis in other places. For example, I still have my solar panels' daily output pulled from the RCT inverter into the dashboard, and that works just fine.

@mqatgit
Sorry, with the documentation I meant the READ.ME file and more specifically the part about the energy dashboard:
https://github.com/weltenwort/home-assistant-rct-power-integration#usage-with-the-built-in-energy-dashboard

@gutwinski Thanks! I had seen the READ.ME, but didn't read that part close enough. It seemed so evident to me to use 'daily' measures...


Feature: custom divider

@mikepenz:
Can you please add the option for a custom divider style. Just define a style in style.xml that can be overridden and remove the option to set color by code? So it would be possible to use a drawable as divider
styles.xml;
    <style name="aboutlibraries_custom_divider">
        <item name="android:layout_width">1dp</item>
        <item name="android:layout_height">match_parent</item>
        <item name="android:background">@drawable/divider_vert_blue_middle</item>
    </style>

@Scrounger so you want to have a divider between the items? or a divider in the card?
You can already adjust the design of the card by either overwriting the xml of one item
Copy and paste this in and adjust hte xml:
https://github.com/mikepenz/AboutLibraries/blob/develop/library/src/main/res/layout/listitem_opensource.xml
or you hook into the view generation with the LibsConfiguration via:
https://github.com/mikepenz/AboutLibraries/blob/develop/library/src/main/java/com/mikepenz/aboutlibraries/LibsConfiguration.java#L240

Overriding the layout file is easier. Just setted your diverders color to transparent and added my custom divider


[Subtask] Fix broad-exception-caught Pylint rule for client-python

Describe the subtask

Currently the try...except block only catchs general exception Exception, please replace it with more specific exceptions.

Parent issue
#3560

Hi @rich7420, thanks for your interest for this issue.
You can try to remove the broad-exception-caught rule from disable section in pylintrc and run the pylint task to run pylint checks, you would see where the problem is, then you can try to solve them

Hi @rich7420, thanks for your interest for this issue.
You can try to remove the broad-exception-caught rule from disable section in pylintrc and run the pylint task to run pylint checks, you would see where the problem is, then you can try to solve them.

Actually this issue is related to the current issue I make: #4012
The current client-python should have better error handling structure like client-java, maybe you can help to solve this issue first?


enable submitting alternate address where there was no possibility before

https://www.pivotaltracker.com/story/show/157090660
This is the bare minimum I could do to make this work. The UI still sucks as discussed with Maria and Troy--I'll be submitting a second PR ASAP to hopefully make it slightly more obvious what the user should do.
See https://github.com/votinginfoproject/vip-embeddable-tool/commit/1ced5bc0af4de3c1f807035962f24ac11641db5a#diff-aa1adde62301a7810fc28dbfe926891d for history.

@tank157 Funny, that's exactly what I said to myself when I tweaked this code... 😆

@tank157 Would you mind re-reviewing? I decided just to throw my updated changes in this PR because they are pretty minimal and straightforward.

微妙な反応だね。Thanks...haha

I wonder if subtle reaction has more significance than I understand.


replace zoomify with ok zoomer on applicable versions

Ok zoomer supports fabric again

zume better. https://modrinth.com/mod/zume

zume better. https://modrinth.com/mod/zume

https://github.com/skywardmc/additive/issues/51


Reset proxy headers to avoid spoofing alerts

https://trello.com/c/7qWgBlA7/617-investigate-handling-actiondispatchremoteipipspoofattackerror
Previously a user could manually specify these headers, which could
result in a spoofing error for Rails apps trying to detect the client
IP address 1. Although the use of the headers by the end user is
valid, we can't trust and shouldn't care about any proxies that the
request has been through before reaching our network. This ensures
the proxy headers are reset before the request continues.
Trying this manually (before/after) shows that:

Fastly does not have a default value for the Client-IP header, so
it's consistent to enforce that it is unset.

Fastly pre-populates X-Forwarded-For with the "actual" client IP,
so we should preserve that (but ignore any pre-existing header).

Note that HTTP headers are not case sensitive.

Note that to test this I had to manually tweak the Nginx config (/etc/nginx/nginx.conf) on one of the cache machines, so that it would print the "Client-IP" header:
    log_format timed_combined '$remote_addr - $remote_user [$time_local]  '
      '"$request" $status $body_bytes_sent '
      '"$http_referer" "$http_user_agent" '
      '$request_time $upstream_response_time '
      '$gzip_ratio $sent_http_x_cache $sent_http_location $http_host '
      '$ssl_protocol $ssl_cipher '
      '$http_x_forwarded_for '
      '$http_client_ip';