PIPX Installation error in v6.0.0a5

Hi.
When I try to install copier me through: pipx install copier,  I get an error.
I just tried installing version v6.0.0a4 and it worked fine.
My system:
Mac Os X 10.15.7 just installed and I have only installed Comman Line Tool for Xcode 12.
Error:
`
$> pipx install copier
ERROR: Command errored out with exit status 1:
command: /Users/estraka/.local/pipx/venvs/copier/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"'; file='"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-wheel-bdw9mqi7
cwd: /private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/
Complete output (114 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.macosx-10.14.6-x86_64-3.8
creating build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/init.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/regex.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/_regex_core.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/test_regex.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
running build_ext
building 'regex._regex' extension
creating build/temp.macosx-10.14.6-x86_64-3.8
creating build/temp.macosx-10.14.6-x86_64-3.8/regex_3
xcrun -sdk macosx clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -arch arm64 -arch x86_64 -I/Users/estraka/.local/pipx/venvs/copier/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8 -c regex_3/_regex.c -o build/temp.macosx-10.14.6-x86_64-3.8/regex_3/_regex.o
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:63:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:807:2: error: Unsupported architecture
#error Unsupported architecture
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:64:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/limits.h:8:2: error: architecture not supported
#error architecture not supported
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported
#error architecture not supported
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_blkcnt_t;      /* total blocks /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:56:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_blksize_t;     / preferred block size /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:57:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_dev_t;         / dev_t /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:60:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_gid_t;         / [???] process and group IDs /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:61:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_id_t;          / [XSI] pid_t, uid_t, or gid_t*/
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:62:9: error: unknown type name '__uint64_t'
typedef __uint64_t      __darwin_ino64_t;       /* [???] Used for 64 bit inodes /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:68:9: error: unknown type name '__darwin_natural_t'
typedef __darwin_natural_t __darwin_mach_port_name_t; / Used by mach /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:70:9: error: unknown type name '__uint16_t'; did you mean '__uint128_t'?
typedef __uint16_t      __darwin_mode_t;        / [???] Some file attributes /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:71:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_off_t;         / [???] Used for file sizes /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:72:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_pid_t;         / [???] process and group IDs /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:73:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_sigset_t;      / [???] signal set /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:74:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_suseconds_t;   / [???] microseconds /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:75:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_uid_t;         / [???] user IDs /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:76:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_useconds_t;    / [???] microseconds */
^
note: '__uint128_t' declared here
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:43:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_wctype_t;
^
note: '__uint128_t' declared here
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:75:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types/_va_list.h:31:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/types.h:37:2: error: architecture not supported
#error architecture not supported
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
error: command 'xcrun' failed with exit status 1
ERROR: Failed building wheel for regex
ERROR: Command errored out with exit status 1:
command: /Users/estraka/.local/pipx/venvs/copier/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"'; file='"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-record-brjqgggf/install-record.txt --single-version-externally-managed --compile --install-headers /Users/estraka/.local/pipx/venvs/copier/include/site/python3.8/regex
cwd: /private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/
Complete output (114 lines):
running install
running build
running build_py
creating build
creating build/lib.macosx-10.14.6-x86_64-3.8
creating build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/init.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/regex.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/_regex_core.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
copying regex_3/test_regex.py -> build/lib.macosx-10.14.6-x86_64-3.8/regex
running build_ext
building 'regex._regex' extension
creating build/temp.macosx-10.14.6-x86_64-3.8
creating build/temp.macosx-10.14.6-x86_64-3.8/regex_3
xcrun -sdk macosx clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -arch arm64 -arch x86_64 -I/Users/estraka/.local/pipx/venvs/copier/include -I/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8 -c regex_3/_regex.c -o build/temp.macosx-10.14.6-x86_64-3.8/regex_3/_regex.o
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:63:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:807:2: error: Unsupported architecture
#error Unsupported architecture
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:64:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/limits.h:8:2: error: architecture not supported
#error architecture not supported
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported
#error architecture not supported
^
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_blkcnt_t;      /* total blocks /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:56:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_blksize_t;     / preferred block size /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:57:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_dev_t;         / dev_t /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:60:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_gid_t;         / [???] process and group IDs /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:61:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_id_t;          / [XSI] pid_t, uid_t, or gid_t*/
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:62:9: error: unknown type name '__uint64_t'
typedef __uint64_t      __darwin_ino64_t;       /* [???] Used for 64 bit inodes /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:68:9: error: unknown type name '__darwin_natural_t'
typedef __darwin_natural_t __darwin_mach_port_name_t; / Used by mach /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:70:9: error: unknown type name '__uint16_t'; did you mean '__uint128_t'?
typedef __uint16_t      __darwin_mode_t;        / [???] Some file attributes /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:71:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_off_t;         / [???] Used for file sizes /
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:72:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_pid_t;         / [???] process and group IDs /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:73:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_sigset_t;      / [???] signal set /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:74:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_suseconds_t;   / [???] microseconds /
^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:75:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_uid_t;         / [???] user IDs /
^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:76:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_useconds_t;    / [???] microseconds */
^
note: '__uint128_t' declared here
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:43:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_wctype_t;
^
note: '__uint128_t' declared here
In file included from regex_3/_regex.c:50:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:75:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types/_va_list.h:31:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/types.h:37:2: error: architecture not supported
#error architecture not supported
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
error: command 'xcrun' failed with exit status 1
----------------------------------------
ERROR: Command errored out with exit status 1: /Users/estraka/.local/pipx/venvs/copier/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"'; file='"'"'/private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-install-xrjq2jj2/regex/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/jp/3c05l4lj75nfs_jt0_mqfpv80000gn/T/pip-record-brjqgggf/install-record.txt --single-version-externally-managed --compile --install-headers /Users/estraka/.local/pipx/venvs/copier/include/site/python3.8/regex Check the logs for full command output.
Error installing copier.
`

After several days looking for the problem, and deciding to write the issue, I just found the solution. The problem is related to the XCODE Command Line (12) of MAC, and the defined architecture (arm). To solve it, just specify the variable:
export ARCHFLAGS = "- arch x86_64"

In any case this should go against pip or pipx probably.


Create Vote List Modal

Designs
Figma: https://www.figma.com/file/9lCwprCNaoAmUDmiMQpFEA/DAOhaus-v3?node-id=5597%3A117112

Elements

Title: Proposal Votes (#) < # is members who have voted
Vote lines:

Date/time of vote (in users timezone)
Membercard
Vote Y/N
Vote token total

Total // Yes (voting token amount) / No (voting token amout)
Close button

Behavior

After 6 member votes, the modal start inset scrolling
Total should always remain visible, only member/voting amounts should scroll

Data

need new dao context elements for vote queries
add to dao-data first
pagination or fetch all (loop)

Designs added, moving to ready


Incorrectly displayed height in players view

Hello, I ran into a problem that the height of the terrain when moving tokens by players to the area is displayed incorrectly: where it should be +5, it display +10, where should be +10, there is +5. It also doesnt work for players to switch to heights by moving the keys or wasd - changes are simply not taken. But if you do all the same things for the dm, everything works as it should. How can I solve this?

I think this is fixed in v0.4.1 but let me know if it isn't!


Kerbal space program

What are you experiencing an issue with?

[ ] Aurora
[ x] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[ ] Enhancement suggestion
[ ] Device issue
[ ] Other, (Fill in another type of issue here)

It Would be great if you could add kerbal space program, to supported games.

Razer has support for KSP, it should work with Aurora through the Razer Wrapper. I was never able to get it to work, but still worth a try.

Is it possible if you convert it to g910?

Like I said, it should work though Aurora using the Razer Wrapper.

Aa, ok. I give a try

Is it possible to convert this to newer ksp version?
http://forum.kerbalspaceprogram.com/index.php?/topic/137859-11-ksp-logitech-rgb-control-v101-2016-22-04/


Web Automation: Wait

Description
Create a class that includes methods for all applicable waits for the Web Automation using Implicit and Explicit Waits.
Included methods should be as follows:

Wait for URL to be
Wait for URL to contain
Wait for Title to be
Wait for Title to contain
Wait for Element to be present
Wait for Element to be visible
Wait for Element to be invisible
Wait for Nested Element to be present
Wait for Nested Element to be visible
Wait for Nested Element to be invisible
Wait for List Element to be present
Wait for List Element to be visible
Wait for List Element to be invisible
Wait for Nested List Element to be present
Wait for Nested List Element to be visible
Wait for Nested List Element to be invisible
Wait for Element to be clickable
Wait for Attribute Value to be
Wait for Attribute Value to contain
Wait for Text to be
Wait for Text to contain
Wait for Selection State to be
Wait for Element Count to be
Wait for Alert to be present

Dependencies

N/A

Implementation is done. Setting status to READY TO TEST.

Testing is done. Setting status to DONE.


Helm release name must be airflow

I came across your repo and gave it a go with minikube.
I changed the values file to use the apache/airflow:latest image and then ran:
$ helm install .

I got the following error:
$ helm install .
Error: release manageable-peacock failed: Deployment.apps "manageable-peacock-scheduler" is invalid: [spec.template.spec.containers[0].volumeMounts[0].name: Not found: "airflow-dags", spec.template.spec.containers[1].volumeMounts[1].name: Not found: "airflow-dags"]

Versions:
$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

you should run the install from a directory higher than the helm chart itself and do something like helm install ./airflow [flags]

That isn't the issue, it should work the same way whether I am in the same directory as the chart or in another directory.
The issue is that the chart hard-codes the volumeMount to look for a volume called airflow-dags, but the volume is created with a name that is tied to the helm release name: {{ template "airflow.fullname" . }}-dags.
The fix is to change the chart to look for the volume name the same way, i.e. using {{ template "airflow.fullname" . }}-dags` everywhere.


removed depracated startswith

I have updated the usage of inline bool llvm::StringRef::startswith(llvm::StringRef Prefix) const with inline bool llvm::StringRef::starts_with(llvm::StringRef Prefix) const as llvm-18/llvm/ADT/StringRef.h has marked startswith as deprecated.
Please let me know if you have any questions or if this pull request violates any contribution rules.

Thanks for the PR! I think this change is already included in #1550.
Note that AdaptiveCpp currently supports LLVM versions back to 14, so in general such fixes also require backwards-compatibility #ifdefs

Thanks for letting me know, I will close this request. Also, thanks for telling me how this project implements such changes by taking backwards-compatibility into account. Backwards-compatibility was definitely one of those things that I was worried my proposed changes would break but I was not confident about the cleanest way (for this project) to take it into account.


Adding the cli command option for --pod-ip-allocation-mode for cluster creation and nodepool addition in AKS

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az aks create -g MyResourceGroup -n MyManagedCluster --os-sku Ubuntu --max-pods MaxPodsPerNode --network-plugin azure --vnet-subnet-id /subscriptions/00000/resourceGroups/AnotherResourceGroup/providers/Microsoft.Network/virtualNetworks/MyVnet/subnets/NodeSubnet --pod-subnet-id /subscriptions/00000/resourceGroups/AnotherResourceGroup/providers/Microsoft.Network/virtualNetworks/MyVnet/subnets/PodSubnet --pod-ip-allocation-mode StaticBlock
General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

WIP

WIP

Removed the WIP after adding all the changes for this agentpool option.

This PR is a placeholder and waiting on this property to get released in the SDK. Requesting early feedback.

Please add some unit test cases (see examples in test_agentpool_decorator.py) and at least one live test case (see examples in test_aks_commands.py) for the newly added option.

I have added the requested UT and live test case.

Please resolve merge conflicts

Merge conflicts were resolved

Please fix CI issues

All the review comments have been addressed and this PR is blocked on CI failures for reviewers to approve.

Queued another live test to validate the change.

Oh, the live test failed, it seems that there is a toggle that controls the use of features. In this case, please exclude the case from the default test matrix src/aks-preview/azcli_aks_live_test/configs/ext_matrix_default.json so it won't be executed in cli runner.

Queued another live test to validate the change.

Oh, the live test failed, it seems that there is a toggle that controls the use of features. In this case, please exclude the case from the default test matrix src/aks-preview/azcli_aks_live_test/configs/ext_matrix_default.json so it won't be executed in cli runner.

Added the test to the exclusion list.


Do not recomment newer npm versions (unless should be with node.js version)

We should recommend palyers to stay with the npm version that comes with their npm version and do not update npm

This adapter has been deprecated.
So most certainly this this issue will not be asolved anymore


WIP - Issue #4281 Add performance tests for advanced pom support

Context
See #4281

@ljacomet to verify that everything works on CI, you should run a full branch pipeline build (we do not do that automatically). The results will then show up here in the "checks" section.

Go to https://builds.gradle.org/project.html?projectId=Gradle_Check&tab=projectOverview&branch_Gradle_Check
select your branch
start a "Branch Accept (Trigger)" build

(and in "select your branch", just type in the number of the PR, that is to say 4291 here)


Feature Request: IATA Airport Codes

Thanks for the great app, and for responding so quickly to fix issues!
Would it be possible to add an option to use IATA airport codes for cities (For example CKG for Chongqing, rather than CHO) in the 'compact view'?
I realize there might be potential issues with cities such as Tokyo, London, New York, etc. that have multiple airports which might require an additional selection.
Here's a list of codes put together by nationsonline.org:
https://www.nationsonline.org/oneworld/IATA_Codes/airport_code_list.htm

@ExHongKonger Hi again) Maybe you are the pilot?)) I`ll think about it! In my opinion cities are more relevant for searching and more friendly for people. Curious to know what do you think about it :)

Hi!
I'm not a pilot, but I spend far too much time on planes, so I tend to remember cities by their airport codes.  I agree that most people would probably prefer the city name, but it might be a nice option for frequent flyers.

@ExHongKonger done. 9,766 IATA Airport Codes added!


Prisma migrate diff just crashed.

Hi Prisma Team! Prisma Migrate just crashed.
Command
migrate diff --from-schema-datamodel=prisma/schema.prisma --to-url=mysql://root:password@localhost:3306/covia --preview-feature --script
Versions

Name
Version

Platform
darwin-arm64

Node
v17.4.0

Prisma CLI
3.9.2

Engine
bcc2ff906db47790ee902e7bbc76d7ffb1893009

Error
Error: Error in migration engine.
Reason: [migration-engine/connectors/sql-migration-connector/src/sql_renderer/mysql_renderer.rs:282:81] called `Option::unwrap()` on a `None` value

Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new

Context: this unwrap is failing.
    fn render_drop_foreign_key(&self, foreign_key: &ForeignKeyWalker<'_>) -> String {
        format!(
            "ALTER TABLE {table} DROP FOREIGN KEY {constraint_name}",
            table = self.quote(foreign_key.table().name()),
            constraint_name = Quoted::mysql_ident(foreign_key.constraint_name().unwrap()),
        )
    }

So we have a foreign key without a constraint name. That should be possible for us to track and address.

Can you confirm this might be the case in your database @codymihai?

(note that the missing constraint name could be something wrong in Prisma code)

@janpio what basically I want to do is:
I've migrated everything from prisma 1 to primsa 2 on my local machine and also on a dev env and now I dumped the production database which uses the primsa 1 and I want to get all sql queries necessary(or the diff) between the prisma 2 schema and the old prisma 1 database


Ftp client: Fix burst download

I attempted FTP burst download with PX4 and encountered some issues. After a certain period, the burst download would halt, and the remaining data would be downloaded as missed parts. Upon inspecting the PX4 code, I discovered the following comment: /* perform transfers in 35K chunks - this is determined empirically */.
When attempting to resume burst download for incomplete files, I observed that missed parts were managed using a file-sized buffer with a binary value (1 or 0) for each byte. This implies that for a 10MB file, it requires 10MB of RAM to download.
With this pull request, instead of storing the entire missed parts in memory, we now only store the offset and size of the missing parts. Burst download is restarted if the file is not complete before checking missed parts.
To test the handling of missed parts, I modified my PX4 to skip 4 packets every 10,000.

Can someone help me for the macOS check ? I have no such hardware and I don't know what is the problem.
 Got signal: Abort trap: 6 (6) (system_tests_runner.cpp:12) 708 <empty trace>

Neither do I have a Mac. Have you run the tests with address sanitizer? Configure with -DASAN=On.

I rented a Mac server (Intel based) and ran tests in debug and relwithdebinfo build type, and guess what, everything passed fine :sob:.

Finally https://github.com/mavlink/MAVSDK/actions/runs/8133538655/job/22225232773?pr=2235#step:10:725

@chep this looks like a bit of a problematic one:
[01:25:36|Debug] allocate<PHONE_NUMBER>3709543729 empty bytes (mavlink_ftp_client.cpp:520)

https://github.com/mavlink/MAVSDK/actions/runs/8134545366/job/22227629255?pr=2235#step:10:718

@chep by the way, I can reproduce it like this:
cmake --build build -j30 && build/src/system_tests/system_tests_runner --gtest_filter=SystemTest.FtpDownloadBurstBigFileLossy --gtest_repeat=100 --gtest_break_on_failure

I think it's an edge cases when the message containing the burst_end=1 is lost.

I think it's an edge cases when the message containing the burst_end=1 is lost.

Oh…
You're right.
I'm gonna check that.

@chep I've reverted your fix given it didn't fix it, and came up with something that seems to pass the tests.
Would you mind testing this against your PX4 test case again?

Test failed again, remaining byte count was negative. I think I fixed it. I'll try with my PX4 test case today.

You can see how PX4 arbitrary "stop at 35K" which is not according to the spec, opens all sorts of edge cases. :cry:

It works here with PX4.
I don't know px4 code at all, I just found this comment…
https://github.com/PX4/PX4-Autopilot/commit/97b8e7a20e1bf64b7677911e6bbab300ff471358

Yep, I've seen this comment. Thanks for figuring this out in the first place. While I would want to change the PX4 implementation, we need to try to be compatible with current and older PX4 versions anyway, so the fixes are good!
Thanks for testing again, I'll go ahead and merge this now!


Use block load attribute to remove duplicate logic from MaterializeBlockPointer pass

The logic in shouldRemove in the RewriteTensorPointer pass duplicates the same logic in MaterializeBlockPointer: https://github.com/intel/intel-xpu-backend-for-triton/blob/main/third_party/intel/lib/TritonIntelGPUTransforms/MaterializeBlockPointer.cpp#L50
This duplication is necessary for the Matrix transpose multiplication case because the block pointer is defined outside a scf.for loop, but the load is inside the loop. The previous logic in RewriteTensorPointer could not "see" into the scf.for loop block and decided to remove the tensor pointer even though its result was used by a block load. This PR changes the processing of a scf.for loop to associate the arguments to the for loop with any users inside the for loop body block. That change coupled with #2400 makes the duplicated logic not necessary for the matrix transpose case.
But, the goal of #2380 is to remove the duplicated code. I believe we should be able to do this by checking the block attribute to the load, but I am wondering if there are other tensor pointers that we want to keep, even if the load/store is not tagged with the block attribute. For now I am only checking the block tag inside the scf section of RewriteTensorPointer, but I think we should consider expanding this check, and possibly removing the dpas layout checks inside RewriteTensorPointer. In other words, if we have a tensor pointer followed by a block load, we always keep the tensor pointer. @etiotto @whitneywhtsang @chengjunlu do other cases exist where we do not have a blocked load but want to keep the tensor pointer? One case I can think of is where we have a DPAS dot operation, a blocked load input, and an input that cannot be a block load (but could be materialize through scatter/gather vectorization per #2181). So perhaps the logic should be:
check if tensor pointer is used by load/store
if yes and check if block attribute is on load/store -- keep tensor pointer
if yes and no block attribute -- keep tensor pointer if tensor + load/store has DPAS layout
if no -- remove tensor pointer

I am going to run this through CI and benchmarks and make sure there are no regressions while we discuss the above topic.

Close #2380

After looking at the test failure I have realized this approach won't work. I did not realize we needed to mark all TensorPtr related ops for removal when walking the module. Our pass follows the upstream pass pattern, but in upstream they remove all TensorPtr related ops regardless of how they are used - we want to propagate that use info.
I wrote a proof of concept version of this PR which essentially does a DFS on each TensorPtr op to find a load/store op to see if we need to remove or keep the TensorPtr. That requires two additional data structures though - one to keep the working set of operations, and one to keep the set of values to remove. Not a big deal, but messier than I would like. This seems to work but still has some bugs. The other approach would be to write an analysis pass and tag each op with TensorPtr type for removal based on the analysis -- theoretically we can keep more complex state, but it does seem like the result might be a similar process as I have implemented. Is one approach preferred over another, especially since we may remove this pass in the future?

Here's the new, working algorithm:
First, walk the tree and look for MakeTensorPtr ops. For each MakeTensorPtr op, we do a DFS to find load/store users of the op. If we have a store associated with DPAS layout, or a block load, then we do not mark the MakeTensorPtr op for removal. Otherwise, we mark it for removal.
Next, we make a pass through all the ops again and make sure we removal all MakeTensorPtr-related ops for each MakeTensorPtr marked for removal (tt.advance, rewrite the loads, etc).
I also had to move the fp8 column major block load logic to MaterializeBlockPointer, but that is expected if the goal is to cleanup duplication.

That last commit should instead say remove stores too...

I don't know why github won't let me reply directly to your comment, but isn't
%0 = maketensorptr
%2:1 = scf.for %iv = %c0_i32 to %c5120_i32 step %c32_i32 iter_args(%arg = %0) {
  %1 = add %arg, 1
  scf.yield %1
}

the same as the test I added, with add replace to tt.advance? tt.advance is handled generically, presumably add would be handled the same way. Here's the debug log output from the newly added case for the first make_tensor_ptr op:
[tritonintelgpu-rewrite-tensor-pointer]: Considering: %10 = tt.make_tensor_ptr %arg0, [%c1024_i64, %c5120_i64], [%c5120_i64, %c1_i64], [%9, %c0_i32] {order = array<i32: 1, 0>} : <tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>
[tritonintelgpu-rewrite-tensor-pointer]: Processing op: %13:3 = scf.for %arg3 = %c0_i32 to %c5120_i32 step %c32_i32 iter_args(%arg4 = %cst, %arg5 = %10, %arg6 = %12) -> (tensor<256x256xf32, #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>>, !tt.ptr<tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>, !tt.ptr<tensor<32x256xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>)  : i32 {
  %16 = tt.advance %arg5, [%c0_i32, %c32_i32] : <tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>
  %17 = tt.advance %arg6, [%c32_i32, %c0_i32] : <tensor<32x256xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>
  scf.yield %arg4, %16, %17 : tensor<256x256xf32, #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>>, !tt.ptr<tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>, !tt.ptr<tensor<32x256xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>
}
[tritonintelgpu-rewrite-tensor-pointer]: Processing op: %16 = tt.advance %arg5, [%c0_i32, %c32_i32] : <tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>
[tritonintelgpu-rewrite-tensor-pointer]: Not a load store and not a loop, adding users to working set.
[tritonintelgpu-rewrite-tensor-pointer]: Processing op: scf.yield %arg4, %16, %17 : tensor<256x256xf32, #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>>, !tt.ptr<tensor<256x32xf16, #triton_gpu.dot_op<{opIdx = 0, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>, !tt.ptr<tensor<32x256xf16, #triton_gpu.dot_op<{opIdx = 1, parent = #triton_intel_gpu.dpas<{repeatCount = 8, systolicDepth = 8, executionSize = 16, opsPerChan = 2, threadsPerWarp = 16, warpsPerCTA = [8, 4], repCluster = [4, 2], A = [32, 16], B = [16, 32], C = [32, 32]}>, kWidth = 2}>>>

scf.yield has no users so we stop the iteration there.
There might be cases this misses, but I think we should add them as we find them. Considering all possible cases upfront will be quite difficult, and note the old algorithm behaved similarly (only considered the inner body of  scf.for loop and the yield operands).

I don't know why github won't let me reply directly to your comment

Probably need to reply to the original thread which is higher, but doesn't matter.

scf.yield has no users so we stop the iteration there.

True, I guess is fine as MLIR doesn't have PHINodes.

There might be cases this misses, but I think we should add them as we find them. Considering all possible cases upfront will be quite difficult, and note the old algorithm behaved similarly (only considered the inner body of  scf.for loop and the yield operands).

My concern is not if we generate good code, more on if we would ever run into an infinite loop, which is a behavior that we never want. Anyways, I cannot think of an example.


Task: Clean datasource review page

Remove Generate CRUD page button
Remove New query button
“You’re in” message (after successfully connecting - database schema fetch - to a datasource in the onboarding step)

Checkout Notion card for more details.

@rishabhrathod01 not yet. We could not pick up this sprint.
We can in the upcoming sprint, but for us this will not be an S. If you have bandwidth, feel free to pick it up.


MINOR: WorkerUtils#topicDescriptions must unwrap exceptions properly

Would it be possible to add a test?

I added a unit test.

retest this please

retest this please

retest this please

The test failure is a connect integration test.  It is not related to this (connect doesn't use this code)
19:51:19 > Task :connect:runtime:integrationTest FAILED


(chore): Refactor id validation

Hi, i'd be dropping hints on various commits or files as much as I can.
So first of all, a few things, maybe you did them intentionally

Validation: you are not validating data from req.body, req.params etc, so you'd get errors when trying to access values which wasn't sent by he clients

Work on avoiding code repetition
e.g every controller method has the error block
res.status(500).json({         errors: {           status: '500',           detail: 'Internal server error',         },       });

This feature can be offloaded to a utility package that'll be imported by all controllers, so you could have say a utility.handleErrors function, which would handle errors emanating from your controllers
Other cases are text scattered around the controller  e.g appears twice in the user-controller
you could have such texts defined in a constants.js file, and just reference them when needed

I think the pattern used in your routes file is pretty cool btw

Just seeing this. Thanks a lot @solutionstack . Would work on improving on those, thanks

You could look into any of the following for your validation needs

[Express Validator] (https://express-validator.github.io/docs/)

[Joi] (https://github.com/hapijs/joi)


Passed parameters validation

Hi Roman,
Lets assume these scripts:

build.ps1

$params = @{
    File    = 'tasks.ps1'
    Task    = 't1'

    param1  = 'param1'
    param2  = 'param2'
    # param3  = 'param3' - forgot to specify this param
    # lots of other params here
    param99 = 'param99'
}

Invoke-Build @params

tasks.ps1

param(
    [Parameter(Mandatory)][string]$param1,
    [Parameter(Mandatory)][string]$param2,
    [Parameter(Mandatory)][string]$param3,
    # another params here
    [Parameter(Mandatory)][string]$param99
)

task t1 {
    Write-Build 'Hello World!'
}

I run build.ps1 on a build server, and it hangs forever.
The reason is that mandatory parameter param3 is not passed to Invoke-Build. 2 problems here:

Was really difficult to identify the reason of the behavior.
With huge amount of parameters, its difficult to find the missing one.

Maybe you have an idea, how to check that all mandatory parameters are passed?

Here's how we do it, we do an assertion in Enter-Build like this:
Enter-Build {
  assert ($buildTimestamp) "buildTimestamp is not defined!";
}

Yes, unfortunately Mandatory is not an option in non-interactive scenarios. (I think it's the PowerShell usability issue but it's another story.)
There are probably several ways to deal with this. One is suggested by @nsartor (thanks!). Another possible, maybe the simplest ands a bit lazy is this:
param(
    [string]$param1 = $(throw),
    [string]$param2 = $(throw),
    [string]$param3 = $(throw),
    # another params here
    [string]$param99 = $(throw)
)

To make it neater, add error messages after throws, depending on a parameter.
But even bare throw is kind of enough if the error shows the line with the parameter name.

Thanks for suggestions, guys!


Small fixes

TODO:

[x] check readme
[x] check changelog

merged in https://github.com/netguru/react_webpack_rails/commit/30399b0ba664367c3c5c7bed45b008bf2da7a79e


Questions about dataset

I'd like to use /CodeXGLUE/Code-Code/CodeCompletion-token/dataset/javaCorpus/token_completion dataset, and have a following question.
When I download the dataset, it is already splited by ' . '.
The original data might be "package org.vaadin.teemu.clara.demo". Could you explain it?

To better evaluate token level accuracy, we tokenize the original code.
Take package org.vaadin.teemu.clara.demo as an example, if it isn't split by ., org.vaadin.teemu.clara.demo will be seen as a single token. The accuracy score of prediction A package org.vaadin.teemu.clara is the same as prediction B package net. But prediction A is obviously better than B.


Managing OWNER on postgresql.

When I inspect the schema on postgresql, it seems atlas does not consider the owner of the schema or table.
In case of inspection with SQL, when I call
atlas schema inspect -u "postgres://postgres:test1234@localhost:5732/test?sslmode=disable" > test.sql

Even if the schema and table are from a different owner, the generated SQL does not recognize of them.
And if I specify schema using
atlas schema inspect -u "postgres://postgres:test1234@localhost:5732/test?search_path=test&sslmode=disable" > test.sql

Then, it does not show the schema in the create table query too.
In case of HCL, ddl can follow schema regardless of there are search_path in URL or not.
So, if some tables are moved to other schema or change the owner, then is it possible to follow that change by atlas ddl?

Agreed! I would love to have role support within atlas


Failed to delete

Hi，May I ask is this the normal output? or the file is locked or something that I need to fix.
Would you mind give me some suggestions?
A fatal error occurred: Error while recursively deleting '/experiments/sec_eval/sec-eval-350m-prefix/trained/cwe-089/0-py/sec_codeql_db/trap' (eventual cause: MultiIOException "java.io.IOException: Failed to delete /......

Hi, this looks like a problem with CodeQL or file permision issues on your operating system. I suggest to try to fix the issue in those directions.


[FEATURE] Add option to call parent of expression

I'm using JsqlParser to parse SQL script, which is always select statement and is written in Spark SQL syntax.
My goal is to travel through all functions and replace them with correct analog to target database (for example postgres).
Using visitor is great feature. but I can only change existing Function object, change function name, change parameters and so on.
But in some cases I need to replace this Function with other Expression, for example with Subtraction.
Look at this example:
SELECT to_unix_timestamp("col1") from mytable; -> this is valid spark sql
SELECT ("col1" - to_date('1970-01-01', 'yyyy-mm-dd')) * 86400 -> this is valid oracle sql
Here i need to change to_unix_timestamp function with Multiplication.
I wish there was an option to get parentExpression on my Function in a visitor and call something like replaceWith(multiplication)

Greetings.
All of that is very possible. What challenges exactly are you facing please?


[InitialSetup]Make configuration changes for angular framework integration

Problem
Angular framework is require  in developing the Frontend of the application
*TODO
Make code and filesystem changes to integrate angular framework in the repository
Add any other context or screenshots about the feature request here.

@ian0549 if this is done kindly close the issue.


Automatically update routes list

If a specific app is being displayed, and a new route is then created (or an existing route is then deleted) using the CLI (or perhaps another UI window) then the list of routes remains unchanged. The list of routes is not updated until the page is refreshed.
This is inconsistent with the behaviour of the graphs on this page, which will automatically update themselves if a new route is added and then called.
The page should automatically detect that a new route has been created (or deleted) and update the display accordingly. We already have a background thread fetching stats, so it is not unreasonable to also have a background thread fetching a list of routes. The thread should probably run only whilst the app in question was being displayed.

See also https://github.com/fnproject/ui/issues/41, which describes the same issue for the top-level apps list.


st2actionrunner reloads on adding a new pack

Currently, I have tried installing some custom st2packs by baking them in a docker image following https://github.com/StackStorm/st2packs-dockerfiles and it worked well. But everytime I add a new pack by updating the image, the st2actionrunner pod reloads. So if I want to be able to add packs on a regular basis, it will certainly affect the execution of the actions and workflows running at that moment. Is there another way to add packs without affecting the execution?

Originally reported in https://forum.stackstorm.com/t/stackstorm-ha-st2actionrunner-k8s-rescheduling-death-consequences/910/.
The mechanism of re-starting st2acrionrunner to pick up new packs is how the stackstorm-ha Helm chart deployment was designed and works. The packs filesystem should be copied to st2actionrunner container which happens on init stage via sidecar containers.
There is however another edge case here which coming from the st2 core:

Yes indeed, sudden re-schedule or death of st2actionrunner leads to broken workflow execution, according to: https://github.com/StackStorm/st2/issues/4716 Ideally if st2 core could tolerate such failures with action re-schedules.

I believe there are 2 possible ways to improve this story:
handle properly st2actionrunner failures/re-schedules in st2 core or re-architect stackstorm-ha.
This could be a future enhancement.

Hi @kritikash18 , Did you find any alternative for this.
I tried installing new pack/modifying existing packs and everything actually impact running action/workflow and it is marked as 'Abandoned'.

Hi @kritikash18 , Did you find any alternative for this.
I tried installing new pack/modifying existing packs and everything actually impact running action/workflow and it is marked as 'Abandoned'.


DuckDB backend does not support List

Describe the bug
src/mitchdevenport/demo ❯ spice run
Spice.ai runtime starting...
2024-03-19T21:57:33.535316Z  INFO spiced: Metrics listening on <IP_ADDRESS>:9091
2024-03-19T21:57:33.536908Z  INFO runtime::http: Spice Runtime HTTP listening on <IP_ADDRESS>:3000
2024-03-19T21:57:33.536923Z  INFO runtime::flight: Spice Runtime Flight listening on <IP_ADDRESS>:50051
2024-03-19T21:57:33.536987Z  INFO runtime::opentelemetry: Spice Runtime OpenTelemetry listening on <IP_ADDRESS>:50052
2024-03-19T21:57:33.879076Z  INFO runtime: Loaded dataset: eth_recent_transactions
2024-03-19T21:57:33.879122Z  INFO runtime::dataconnector: Refreshing data for eth_recent_transactions
Nested list is not supported yet.
thread 'tokio-runtime-worker' panicked at /Users/mitch/.cargo/git/checkouts/duckdb-rs-7cfb8083041eafcf/375d26e/src/vtab/arrow.rs:381:13:
not yet implemented
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: duckdb::vtab::arrow::record_batch_to_duckdb_data_chunk
   4: <duckdb::vtab::arrow::ArrowVTab as duckdb::vtab::VTab>::func
   5: duckdb::vtab::func
   6: __ZN6duckdb14CTableFunctionERNS_13ClientContextERNS_18TableFunctionInputERNS_9DataChunkE
   7: __ZNK6duckdb17PhysicalTableScan7GetDataERNS_16ExecutionContextERNS_9DataChunkERNS_19OperatorSourceInputE
   8: __ZN6duckdb16PipelineExecutor15FetchFromSourceERNS_9DataChunkE
   9: __ZN6duckdb16PipelineExecutor7ExecuteEy
  10: __ZN6duckdb12PipelineTask11ExecuteTaskENS_17TaskExecutionModeE
  11: __ZN6duckdb12ExecutorTask7ExecuteENS_17TaskExecutionModeE
  12: __ZN6duckdb8Executor11ExecuteTaskEb
  13: __ZN6duckdb13ClientContext19ExecuteTaskInternalERNS_17ClientContextLockERNS_15BaseQueryResultEb
  14: __ZN6duckdb18PendingQueryResult15ExecuteInternalERNS_17ClientContextLockE
  15: __ZN6duckdb17PreparedStatement7ExecuteERNSt3__113unordered_mapINS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEENS_5ValueENS_33CaseInsensitiveStringHashFunctionENS_29CaseInsensitiveStringEqualityENS6_INS1_4pairIKS8_S9_EEEEEEb
  16: _duckdb_execute_prepared_arrow
  17: duckdb::raw_statement::RawStatement::execute
  18: <db_connection_pool::dbconnection::duckdbconn::DuckDbConnection as db_connection_pool::dbconnection::SyncDbConnection<r2d2::PooledConnection<duckdb::r2d2::DuckdbConnectionManager>,&dyn duckdb::types::to_sql::ToSql>>::execute
  19: runtime::databackend::duckdb::DuckDBUpdate::create_table
  20: <runtime::databackend::duckdb::DuckDBBackend as runtime::datapublisher::DataPublisher>::add_data::{{closure}}
  21: runtime::datafusion::DataFusion::attach_connector_to_publisher::{{closure}}
  22: tokio::runtime::task::core::Core<T,S>::poll
  23: tokio::runtime::task::harness::Harness<T,S>::poll
  24: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  25: tokio::runtime::scheduler::multi_thread::worker::Context::run
  26: tokio::runtime::context::scoped::Scoped<T>::set
  27: tokio::runtime::context::runtime::enter_runtime
  28: tokio::runtime::scheduler::multi_thread::worker::run
  29: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  30: tokio::runtime::task::core::Core<T,S>::poll
  31: tokio::runtime::task::harness::Harness<T,S>::poll
  32: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fatal runtime error: Rust panics must be rethrown
os: process already finished

To Reproduce
Run the spice runtime with the following dataset:
- from: spice.ai/eth.recent_transactions
  name: eth_recent_transactions
  acceleration:
    enabled: true
    refresh_mode: full
    refresh_interval: 10s
    engine: duckdb

Issue is not lists, it's nested lists. Exact todo!() is https://github.com/duckdb/duckdb-rs/blob/b82db396d116fc2dd9311802544610c0f2d06c34/src/vtab/arrow.rs#L380

Fix for UTF8[] https://github.com/duckdb/duckdb-rs/pull/300

Confirmed fixed.


Algorithm for checking if a string can be rearranged into a palindrome

I would like to do this in C++. Also for hacktoberfest. Another question, if I ended up doing this, where should I put the file?

Sure, go ahead. You can put it in Algorithms folder

PR: https://github.com/ephremdeme/data-structure-and-algorithms/pull/338

hey @Kanhakhatri065 .
plz assign me this in any of java/c#.

@Kanhakhatri065 , implemented the solution in C# and submitted a PR #351


Update README.md

name_policy is the correct_argument.

Lol this PR is a duplicate of this existing PR https://github.com/gmalivenko/pytorch2keras/pull/136


Fix errors in console on IO page

Summary
There are several warnings in the console on https:/developer.newrelic.com/instant-observablity when running it locally:
react.development.js:220 Warning: Failed prop type: The prop `variant` is marked as required in `Button`, but its value is `undefined`
react.development.js:220 Warning: Failed prop type: The prop `name` is marked as required in `PackTile`, but its value is `undefined`.
Warning: Failed prop type: The prop `fields` is marked as required in `PackTile`, but its value is `undefined`

Additionally, there seems to be a spike in this error which has triggered pager duty pages. Seems to be related to SDK, though it mostly happens on /instant-observability page, esp when requesting the page initially with query params already set
Error: Cannot read properties of undefined(reading 'Component')

Acceptance criteria

[ ]

Helpful links

closing as this page no longer exists.


Install snooty in conda environment

Is there any way to install snooty in conda environment?

Others seem to be able to use snooty on conda, like in #19

The question is, "Is there a way to install snooty in conda environment?"
The easy answer is, "Yes." Just use pip: pip install snooty-lextudio.
Now, if your question is, "Can you install snooty from an anaconda channel?" The answer is, "No."
I've been trying to set up the necessary upstream feedstocks with conda-forge so we can answer, "Yes," to the second question, but I've run into an upstream dependency issue specifically with fett. If we can replace the templating engine with Jinja2 that'd be the last piece of the puzzle, I believe.


fix(md-3800): autochart crash

:tada: This PR is included in version 1.1.0-alpha.63 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


use absolute URIs

examples have relative URIs, should be absolute.
Absolute URIs are compliant to our REST guide.
format: uri doesn't allow relative URIs, depending on tool being used (e.g. error for StopLight).
format: uri-reference allows both relative and absolute URIs, but isn't used by gCloud schemas

done


Renaming variables or functions in a Jupyter Notebook is very slow

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.85.2
OS Version: Ubuntu 22.04

Steps to Reproduce:

Open a Jupyter notebook
Paste in the following:

import numpy as np
a=np.array([1,2,3])
b=a / np.linalg.norm(a)
b+=1
print(b)

Try to rename b to a_norm

For this case the renaming finishes in ~10 seconds on my machine. For larger cells, it may not succeed at all.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


[Feature][Timothy] EAS Workflow improvements

Added workflow_dispatch to github actions
Updated eas projectId
Check version number change before publishing to npm
Added publish to Github package repository for create-t4-app

I see the expo deployment action is failing because it wants the platform to be specified when building,


bug(cdk/schematics): Regression in CDK version 9.2.2 where the public api changed

Reproduction
Install the CDK with version 9.2.2 and try to import createUpgradeRule and RuleUpgradeData from the schematics package of the CDK.
with version 9.2.1 it was working. So the API was broken in a patch version.
Expected Behavior
It should be possible to import createUpgradeRule and RuleUpgradeData with the version 9.2.2 of @angular/cdk
import {
  createUpgradeRule,
  RuleUpgradeData,
} from '@angular/cdk/schematics';

Actual Behavior
A regression was introduced with this version where those two functions are not exported anymore this causes the build to fail.
error TS2305: Module '"@angular/cdk/schematics"' has no exported member 'createUpgradeRule'.
error TS2305: Module '"@angular/cdk/schematics"' has no exported member 'RuleUpgradeData'.

Environment

Angular: 9.1.3
CDK/Material: 9.2.1 -> 9.2.2
Browser(s): ---
Operating System (e.g. Windows, macOS, Ubuntu): macOs

cdk/schematics is unfortunately not a public API and is not documented anywhere. We'd like to someday offer some of what we've built publicly, but for now we don't have the ability to support it as such.


new logo added

I have added a new logo. What can be done is , we can added a line graph in the background maybe to depict ranking

Hi @manavmehra96. First, thank you for you help!
I would prefer something done only for this project. I would not like to copy something made by another person.
Also, this is too patriotic for me.
Thanks again!


Suricata <IP_ADDRESS> seems to be broken

Describe the bug
After upgrading Suricata service to v <IP_ADDRESS>, every analyse of a PCAP file ends with:
  File "/var/lib/assemblyline/.local/lib/python3.11/site-packages/assemblyline_v4_service/common/base.py", line 181, in handle_task
    self.execute(request)
  File "/opt/al_service/suricata_/suricata_.py", line 267, in execute
    sha256, filename, extracted_file_path = file.values()
                                            ^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'values'

It appears to be totally independent whether the PCAP contains any files to extract or not.
My suspicion is that the commit https://github.com/CybercentreCanada/assemblyline-service-suricata/commit/df33beafb51211da04aaf0e2fb1123e4dcbb0bbe#diff-fbf3caf42b80c9be6f4d38504bf6689bf2b8c341a3bb00146cd875a6c123225dR261 on line 261 in suricata_/suricata_.py misses .values() that was there before :)
To Reproduce
Steps to reproduce the behavior:

Update Suricata to v <IP_ADDRESS>
Analyse any file, e.g.  _linux_EXTRACTED_tcpdump.pcap(2).zip (password: zippy)
See error

Expected behavior
Analyse is done and results are reported.
Screenshots
Environment (please complete the following information if pertinent):

Assemblyline Version: <IP_ADDRESS>
Browser: [e.g. chrome, safari]

Additional context

This should be resolved in the latest stable release.


Replace workspaceRoot with workspaceFolder

Updated VS Code launch.json configuration settings so that interactive debugging can be initiated from the debugger menu.
The variable workspaceRoot has been deprecated in favor of workspaceFolder, as per the VS Code website:
https://code.visualstudio.com/docs/editor/variables-reference

Q: Why isn't ${workspaceRoot} documented?
A: The variable ${workspaceRoot} was deprecated in favor of ${workspaceFolder} to better align with Multi-root Workspace support.

I confirmed the new configuration as you can see in the screenshot.

I don't think I understand why the README.md file change is causing a bunch of stuff like this in Travis:
 FAIL  src/__tests__/get-source-map.js
  ● Test suite failed to run
    SecurityError: localStorage is not available for opaque origins

      at Window.get localStorage [as localStorage] (../../node_modules/jsdom/lib/jsdom/browser/Window.js:257:15)
          at Array.forEach (<anonymous>)

@InTEGr8or it's unrelated to your changes (ref: https://github.com/facebook/jest/issues/6766)

Ping!

<EMAIL_ADDRESS>


Introduce IANA-BCP47 to validate the IETF language code

Hello again,
This PR introduces a more robust solution for validating user input of IETF language codes using the iana-bcp47 library. Compared to the older bcp47 library, this new implementation validates each subtag against the IANA Language Subtag Registry, rather than relying on a predefined whitelist.
Context
highfestiva/bcp47.py#7
In my experience with an older version of pymkv, valid language codes such as zh-Hans-CN would cause a ValueError during validation. These codes are valid according to BCP47 standards but were not included in the whitelist used by bcp47. To address this issue, I decided to implement a validator that strictly adheres to IANA's rules, which this PR introduces.
What's Changed
Previously, the is_bcp47 function was removed, and user input was directly set as the language metadata. While I have not tested whether incorrect language codes can cause issues when MKV files are loaded in other software, I believe a simple validation mechanism should still be included.
With the proposed logic, if the user-entered language code fails validation:

A warning message is displayed with specific details about the error.
The language of the MKVTrack is set to None if the code is invalid.

This ensures that language metadata conforms to IANA standards while providing helpful feedback to users.

The iana-bcp47 library doesn’t appear fully vetted yet, and it’s lacking solid tests. I need some time to review it, and after that, I’ll decide whether to include iana-bcp47 as a dependency.


different status feedback

Agent Mode:

[x] Pull Model (openITCOCKPIT Server request data from Agent)
[ ] Push Model (Agent send data to openITCOCKPIT)

Versions

openITCOCKPIT Monitoring Agent Version: 3.x.x

Operating system
Debian GNU/Linux 11 (bullseye)

Do you use an HTTP proxy? -> no
Are you using Auto-TLS, HTTPS or HTTP? -> yes
Used CPU architecture: i386, amd64, arm64 or armhf? -> amd64

Describe the bug
Substate other than running is issued as a warning. i have installed ufw firewall and postfix,
Substate is: (code=exited, status=0/SUCCESS)

More information about what should be considered as successful by the Agent can be found here:
https://www.computernetworkingnotes.com/linux-tutorials/systemd-units-explained-with-types-and-states.html
At the moment only Active (running) is considered successfully. Active (exited) and Active (waiting) should also be added to the consideration list

Tracked by ITC-2885

This issue will be resolved in an upcoming version of openITCOCKPIT


Suggestion : Implement Feature toggling per model

A follow-up on this discussion #926
I suggest implementing a feature toggling mechanism per model to make it scale. For instance JSON Schema output is available on OpenAI, not on Anthropic, whereas Caching is on Anthropic and not on OpenAI. Same for seed, logit_bias, etc.
So it would looke more like
export const MODEL_PROVIDERS: readonly {
    id: string
    detail: string
    url: string
    available_features: Feature[],
}

type Feature = "seed" | "logit_bias" | "ephemeral_caching" | "json_schema_output" | ...

...

isFeatureAvailable(model, "seed"): boolean

I've centralized the info in llms.json . Could you take a peek and review the anthropic feature set?
I will render this data in the docs too.

I'm going to mark this as closed. You will find then centralized model info at https://github.com/microsoft/genaiscript/blob/main/packages/core/src/llms.json . It is used to disable optional features like logprobs and also rendred in the docs.


Added dismissible property to showDialog action

remember to -

update schema
add this as an example to kitchen sink's existing dialog example
update documentation


research & fix deployment

we disabled automated deployments with changesets, and now we need to find an alternative way to do it

In travis time for safe-react-components as I mentioned we had this script to build and send compiled files to a devops managed source
https://github.com/gnosis/safe-react-components/blob/9f718d1dac968a37309f60f6d82b21bebe249eac/.travis.yml#L21
In this line we uploaded to devops repository as we do with static files for web or safe-apps
https://github.com/gnosis/safe-react-components/blob/9f718d1dac968a37309f60f6d82b21bebe249eac/.travis.yml#L71
We could do something similar but on github actions. I know that for safe-react-components the system is still mounted on their side, we should just start using it and ask to them to add also anotherone for safe-apps-sdk

@dasanra, I'm testing a scenario with changesets because I'd still like to use it to keep track of releases/change descriptions because it's essential given that developer teams are relying on this package. I should have some proposals soon

@dasanra So without the release step the changesets action doesn't publish releases on github, so I suggest forking the action and adjusting it to our needs, the code is fairly simple: https://github.com/changesets/action/blob/main/src/index.ts
I suggest we just allow to execute a custom command on the release step


Typo on WebGL2 Picking page

Minor issue on the WebGL2 Picking page. In the Clicking on an Object section it says:
"So, let's start with the last example from the article on drawing multiple things that draws 200 things."
The examples in the linked page only show how to draw 3 things (not 200). It would be good to update this, because it's using the "200 things" as the base code for picking - but I'm not sure if the code really is the same (if it is the same, then just change "200" to "3"!).

Thanks! I guess I didn't include the 200 object example in WebGL2. (it's in the WebGL1 page). I'll have to fix that

So I fixed the article the picking article was referencing so it has a 200 object example
https://webgl2fundamentals.org/webgl/lessons/webgl-drawing-multiple-things.html

Awesome! That page is way cooler with 200 objects too ;)


Refactor Buildpipelines

So far, there's only a single buildpipeline, and it must be manually triggered. This system should be refactored to the following:

[x] Add multi-pipeline system where each pipeline can be run in series or parallel.
[x] Each pipeline is supposed to watch certain files and write to different files.

Solved in pull request #17


Add showHomeButton to sap.m.Page

Please note that this is not a bug report, but a feature request.
In applications that have deep navigation structures, it will be necessary to press the back button multiple times to get back to the main menu. If an application is opened through a routing URL, it isn't even possible to reach the main menu using back buttons.
To make the application easier for users, a home button should be implemented. However, a home button requires the header of each page to be customized and is quite tedious.
It would be of great convenience, if a showHomeButton property would have been implemented, similar to the showNavButton. When the showHomeButton is set to true, a home button should appear at the left side of the back button. It would also be great if a custom handler can be attached to e.g. homeButtonPress

hi is showHomeButton property added  to sap.m.Page?

Hi,
There were additional controls and concepts in the meantime which can help to fulfill this requirement.
Please have a look at the following controls and samples for more details:
https://openui5.hana.ondemand.com/entity/sap.f.ShellBar
https://openui5.hana.ondemand.com/entity/sap.uxap.ObjectPageLayout/sample/sap.uxap.sample.ObjectPageOnJSON
https://openui5.hana.ondemand.com/entity/sap.f.DynamicPage/sample/sap.f.sample.DynamicPageFreeStyle
https://openui5.hana.ondemand.com/entity/sap.m.Breadcrumbs/sample/sap.m.sample.Breadcrumbs
Best Regards,
Nikolay


Add CI/CD

Probably with GitHub Actions.
Need to look into Jenkins as well.

Make the deployment process as automated as possible.
Plus, try to make migrating the server faster in case of server failure. This could be done by scripting the server migration process.
It'd be ideal to be able to deploy the website on the server just by cloning this repository and running a few commands. Both for the K8s control plane and worker nodes.

Get notified whenever there's a new commit to Flarim framework. (Could be done just by watching the repo)
An automated system to build a Docker container based on the new version of Flarim framework.

Plus, implement https://kubernetes.io/docs/concepts/security/secrets-good-practices/


Always register the swift-lldb debug adapter provider

Issue: #848
We can always register this and that way the user does not need to reload the window when use change to using lldb-dap. Now they can use the updated debug configurations right away

@adam-fowler the debug session does nothing if the path does not exist or cannot find in toolchain, so added a check to verify that the the debug adapter does exist so the user gets an error message instead of silently failing. I see that we are already listening to changes to swift.debugger.useDebugAdapterFromToolchain and swift.debugger.path settings, else where so seemed a little more complex than necessary to listen to this again to register the debug provider


[PE-D][Tester E] Duplicate check for Name field does not include capitalisation of letters

Duplicate check for Name field does not include capitalisation of letters
I have added a contact with the command add n/sohn Doe p/98765432<EMAIL_ADDRESS>a/John street, block 123, #01-01 r/brUdder m/bza

And added another contact with command add n/Sohn Doe p/98765432<EMAIL_ADDRESS>a/John street, block 123, #01-01 r/brUdder m/bza

The only difference is the capitalisation of the letter S in 'Sohn'

Labels: severity.High type.FunctionalityBug
original: verakohh/ped#7

add to planned enhancement: duplicate handling


Only let Aurora run while playing games (Suggestion)

What are you experiencing an issue with?

[x] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[x] Enhancement suggestion
[ ] Device issue
[ ] Other, (Fill in another type of issue here)

Expected behavior:
Explain here what should happen.
I would like to use my default Corsair keyboard profiles from CUE but whenever I launch a game like CS:GO I would like it to switch over to Aurora.

This is possible if you disable the desktop profile (and have the option enabled in settings if you're using the latest dev release.)

Whenever I try to launch the latest dev release I get a error that GameStateListener couldn't start.

You don't need to use the Dev release to use the feature. It is only that if you're using the Dev release that the option must be enabled for it to work on the Dev release. Could you open another issue for the error you are receiving.


238 added move cursor to solved squares mode and test for it

CI failed:
`  Errors found:
/home/runner/work/crosswordApp/crosswordApp/app/src/main/res/values/strings.xml:32: Error: "move_selection_to_solved_squares" is not translated in "ru" (Russian) [MissingTranslation]
move selection to solved squares
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/runner/work/crosswordApp/crosswordApp/app/src/main/res/values-ru-rRU/strings.xml:26: Error: "move_selection_to_solved_squares_text" is translated here but not found in default locale [ExtraTranslation]
печатать в решенные клетки`


Does datahub provide a rest interface for data ingestion

Before I used the python script under metadata-ingestion to import data.
But I found an HTTP interface in #1791 accidentally. Is this method recommended? Is there any related documentation?
curl 'http://localhost:8080/datasets?action=ingest' -X POST -H 'X-RestLi-Protocol-Version:2.0.0' --data '{"snapshot":{"aspects":[{"com.linkedin.dataset.DatasetProperties":{"description":"descriptionForTest2","tags":["tag1","tag2"],"customProperties":{}}}],"urn":"urn:li:dataset:(urn:li:dataPlatform:hdfs,test2,EI)"}}'

This is mostly a "backdoor API" used by the MCE ingestion pipeline. You can certainly use it for debugging purposes and it's mentioned here: https://github.com/linkedin/datahub/tree/master/gms
If you're after a proper CREATE API, you'll need to add one to the GMS like so: https://github.com/linkedin/datahub/blob/master/gms/impl/src/main/java/com/linkedin/metadata/resources/identity/CorpUsersEditableInfoResource.java#L25

Got it


GitHub repo consolidation

As discussed at the meeting we need to consolidate the GSD repos, in broad terms we want to keep:
gsd-database (actual GSD data)gsd-project-plans (Policy and higher-level stuff)gsd-tools (software/tools)
get to stay and everything else gets merged or removed:
gsd-datavalues - CWE type data, this should probably live in a directory in the gsd-database?
gsd-objects - data about researchers/projects/etc intended for confidence scoring - this should probably be moved into the gsd-database?
gsd-demo - this should probably be moved into gsd-tools?
gsd-api-demo - this should probably be moved into gsd-tools?
gsd-experimental - should be merged into gsd-project-plans
gsd-url-processing - some experimental work, should be merged into gsd-tools
gsd-url-downloads - experimental copy of URL data, this definitely needs to go away, I've emailed the Internet Archive about buying their private URL mirroring service but no reply. This should probably be moved into an S3 bucket (requestor pays?)
gsd-url-list - experimental data, this should go away asap (it's basically just URL's extracted from the GSD dataset)
Thoughts/comments?

i would recommend moving gsd-api-demo & gsd-demo into gsd-project-plans as it is not a specific tool but rather to demonstrate the capabilities of gsd.  As the project is updated, the demo will change
i agree with all other recommendations.

cloudsecurityalliance/gsd-datavalues data sent via PR and issues transfered.

cloudsecurityalliance/gsd-objects issue merged and repo deleted

cloudsecurityalliance/gsd-url-list scrapped as per plan

gsd-url-processing merged into gsd-tools as per plan

gsd-url-downloads renamed to obsolete-gsd-url-downloads

gsd-experimental data and issues moved to gsd-project-plans as per plan

i would recommend moving gsd-api-demo & gsd-demo into gsd-project-plans as it is not a specific tool but rather to demonstrate the capabilities of gsd. As the project is updated, the demo will change
i agree with all other recommendations.

@athix what are your thoughts? I think your tool is mature enough it should go into gsd-tools, and it is definitely a tool we plan to use (at least initially), is it safe to merge in, or do we want it separate or?

@kurtseifried @TheFoxAtWork
I'm fine with merging it into either repo personally. My thoughts are that it can either be the base for the API and UI code, or we can toss it wholesale if a better solution is found.
My $0.02 would be to merge it into the tools repo for now, and if we want to replace it with a different solution down the line then it should be easy enough to wipe the folder and replace it with the new code. The human readable part I think we can be flexible on how it works during these early stages, while the machine readable API we may want to define sooner rather than later so that other tools can rely on a stable interface to begin building out the second order toolings.

I actually think it's a bad idea to set the expectation of a static data format. This is one of the things slowly killing CVE (static data and many tools that are not evolving very rapidly). I would also suggest if we want "static" we provide that as an option (e.g. a translation layer) but behind the scenes we actually keep moving forwards (if the market really wants this they can ask for it, but I'm not spending effort from the start providing it, I don't even know if it's needed).
Also that's for the GSD namespace, we don't control any other namespace, so hopefully that factor also helps encourage consumers of GSD data to be nimble.

Having stable APIs is critical to building out the tooling around this, at least from a dev perspective. Having a rapid development pace is fine, but you can't just break the API out of nowhere or you'll quickly drive people away from relying on it. In short: follow semver and provide a reasonable timeframe for downstream developers to upgrade to new major versions. Avoid major version bumps whenever possible, while being willing to make breaking changes when there is real benefit to be had.

I think more generally what I'm saying is I don't think we have to invent another data format, and I don't think we should.
E.g. we currently use the OSV data format in the GSD namespace (which is definitely better for opensource/git style world than the CVE JSON I invented). I think the expectation should be we use other well known data format(s) such as the ones listed in https://github.com/cloudsecurityalliance/gsd-project-plans/blob/main/data-formats/Thoughts-on-data-formats.md , especially as we may have vulnerabilities, but also incidents or malware which have their own (better, more specific) data formats. To say nothing of the stuff other people put in their own namespaces.
Basically, we punt on this and trust that OSV/etc will be good stewards. One problem can be the slowness, to the point where some data formats have already been supplanted by others because they moved so slow (everything that was XML based).
Long term maybe we invent another data format, but I don't want to until there is a clear need, for now, let's outsource/abstract it away to others who specialize in it.

After giving it some more thought, I think I'll go with Emily's suggestion and put it into the project plans repo. If we want to use it as the basis for the actual implementation, we can always move it over to the tools repo then. Until then, keep it clearly labeled as the demo and sorted appropriately.

gsd-project-plans also renamed to gsd-project

tool merged into gsd-project and original repos deleted.

this leaves the repo of url mirror data which is to big to merge in to anything so closing for now.


Added no_std option and split pe and macho into features

This incidentally fixes #7 .
This may be a big change, but the public API for this crate does not change after this PR, i.e. not breaking.
The goal of this is just to get this compiled for no_std, and removing support for pe and macho was needed as the *-unwind-info dependencies require std (didn't look too deep into them, so maybe we can change those as well).
The reason for no_std is that I wanted to integrate this into my kernel (https://github.com/Amjad50/Emerald).
I really like this project, and its really fast and more flexible to get stack traces.
Let me know what you think

Thanks, I support this!
Could you adjust the github CI so that we run at least cargo check for all combinations of on/off features? Otherwise it'll be too easy to forget a #[cfg_attr] annotation as we change things.
Oh and don't worry about the public API, at this stage I still want to be free to break API if it simplifies things.

Good idea, I added it to CI

Hello @mstange can this be merged? thanks

Thank you!

This has been published in 0.10.0.


Make version flags configurable

I would like to use '-v' for '--verbose' and only expose version as
'--version'. This change allows me to do this without changing the
defaults for everybody else.

Awesome, thanks a lot!


Implement transient associations

From https://github.com/faucct/factory_girl/tree/feature/transient_associations. I claim no credit for the work except to update the code.
I ran into the same problems (Issue #1024) as were addressed in the existing open PR https://github.com/thoughtbot/factory_bot/pull/1027, and made it compatible with current master. If there is a more supported way to do this, I'd be happy to delete this PR and do it the other way.
My use case:
I am using FactoryBot to generate nested Hash structures for use as mock responses from the AWS API. These structures sometimes fully contain other fully-defined structures within them, and sometimes simply echo data that would be well-formed values in those other structures. My strategy has been to do things like this:
factory :base_aws_object, :class => Hash do
  initialize_with { attributes.stringify_keys }
  skip_create

  factory :ebs_volume do
    sequence(:volume_id) { |n| "vol-#{n}" }
    size { 8 }
    ....
  end

  factory :ebs_snapshot do
    transient do
      ebs_volume
    end

    sequence(:snapshot_id) { |n| "snap-#{n}" }
    description { "Test Snapshot" }
    volume_id { ebs_volume['volume_id'] }
    volume_size { ebs_volume['size'] }
    ....
  end
end

Without this PR, the transient associations are still added to the final Hash when doing build(:ebs_snapshot), and thus are rejected by the AWS API gem as invalid.

Thanks for taking a look at this. I will try to take a look later this week.
I appreciate the work you did do get the branch up to date, but I don't want to wipe out the authorship of the original commit. I think the right way to go is to keep the original author on the commit but then add yourself as a co-author by putting:
 Co-authored-by: Your Name<EMAIL_ADDRESS>
in the commit message.

Replaced by #1290 to maintain original credit.


Fix error thrown when rendering with no items

This may happen when all the items in the pipeline are filtered out or fail validation.
Test added to cover this case

Thanks!


Update to actions/upload-artifact@v4

Fixes this warning in the GitHub CI annotations:
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3.
For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

This should be kept up to date by dependabot. Why didn't we get a pr ? 🤔

Good point. I just searched the PRs and found:
https://github.com/elastic/apm-aws-lambda/pull/446
Missing reasoning why the PR was closed.
@reakaleek Do you remember?

This should be kept up to date by dependabot. Why didn't we get a pr ? 🤔

Good point. I just searched the PRs and found: #446
Missing reasoning why the PR was closed. @reakaleek Do you remember?

The actions/upload-artifact@v4 action had a breaking change. We had to skip the update in several repositories because some workflows couldn't handle the change. Also, it is/was incompatible with our custom actions.
I might have skipped it as a precaution here. We still need to migrate to v4 properly.
If v4 is working correctly in this repo, please feel free to go ahead.

@reakaleek Thanks for the details.
We only use @v3 in one place:
  test:
    strategy:
      fail-fast: false
      matrix:
        platform:
          - "ubuntu-latest"
          - "macos-latest"
    runs-on: ${{ matrix.platform }}
    steps:
      - uses: actions/checkout@v4
      - name: Bootstrap Action Workspace
        uses: ./.github/actions/bootstrap
      - name: Test
        run: make test junitfile="${{ matrix.platform }}-junit-report.xml"
      - uses: actions/upload-artifact@v3
        if: success() || failure()
        with:
          name: test-results-${{ matrix.platform }}
          path: '*-junit-report.xml'

To decide if updating v3 to v4 is working correctly, we need to know who the consumer of *-junit-report.xml is. Do you have any information about this?

@reakaleek Thanks for the details. We only use @V3 in one place:
  test:
    strategy:
      fail-fast: false
      matrix:
        platform:
          - "ubuntu-latest"
          - "macos-latest"
    runs-on: ${{ matrix.platform }}
    steps:
      - uses: actions/checkout@v4
      - name: Bootstrap Action Workspace
        uses: ./.github/actions/bootstrap
      - name: Test
        run: make test junitfile="${{ matrix.platform }}-junit-report.xml"
      - uses: actions/upload-artifact@v3
        if: success() || failure()
        with:
          name: test-results-${{ matrix.platform }}
          path: '*-junit-report.xml'

To decide if updating v3 to v4 is working correctly, we need to know who the consumer of *-junit-report.xml is. Do you have any information about this?
[UPDATE] Just found this
 report:
    runs-on: ubuntu-latest
    steps:
      - uses: elastic/apm-pipeline-library/.github/actions/test-report@current
        with:
          artifact: /test-results-(.*)/
          name: 'JUnit Tests $1'
          path: "*-junit-report.xml"        # Path to test results (inside artifact .zip)
          reporter: java-junit              # Format of test results

@reakaleek Thanks for the details. We only use @V3 in one place:
  test:
    strategy:
      fail-fast: false
      matrix:
        platform:
          - "ubuntu-latest"
          - "macos-latest"
    runs-on: ${{ matrix.platform }}
    steps:
      - uses: actions/checkout@v4
      - name: Bootstrap Action Workspace
        uses: ./.github/actions/bootstrap
      - name: Test
        run: make test junitfile="${{ matrix.platform }}-junit-report.xml"
      - uses: actions/upload-artifact@v3
        if: success() || failure()
        with:
          name: test-results-${{ matrix.platform }}
          path: '*-junit-report.xml'

To decide if updating v3 to v4 is working correctly, we need to know who the consumer of *-junit-report.xml is. Do you have any information about this?

Ah, thank you for the context. The only consumer of the junit report is https://github.com/elastic/apm-aws-lambda/actions/workflows/test-reporter.yml, but it's disabled because it's broken for another reason, which we haven't been able to solve yet.
I think this workflow was actually the reason why we did not upgrade to v4.
In some repositories, we dismissed the test reporter workflow entirely. Hence, you can upgrade to v4.

@kruskall Do you mind to approve?


Upgrade log-update and fix example

This PR upgrades [log-update]https://github.com/sindresorhus/log-update to the latest version to include the fix for SIGINT (https://github.com/sindresorhus/log-update/issues/17).
Additionally, it adds peerDependencies field that requires the latest version of lists to fix the example.
Fixes #8
Related to https://github.com/sindresorhus/log-update/issues/17
Related to https://github.com/SamVerschueren/listr/issues/85

@SamVerschueren, can you take a look and help us?

@SamVerschueren perhaps you might want to expand maintainers list for this repo and package to include contributors?

I published changes from this PR as<EMAIL_ADDRESS>

Sorry for the late reply. A lot has happened in my personal life so I took some time off from OSS. I merged this one and released a new version 0.5.0. I'll bump the version in Listr as well.
I would be happy to accept someone to help me triage these issues and PRs.

I’d propose myself to help but I’m also trying to get away from open source responsibilities since it’s been eating too much of my time. Still please do count on me if things are urgent and you need some help.


Gradle sync error

Describe the bug
Gradle sync fails every time with message: Android dependency 'com.google.android.gms:play-services-flags' has different version for the compile (16.0.1) and runtime (17.0.0) classpath. You should manually set the same version via DependencyResolution
Expected behavior
Gradle sync normaly
Smartphone (please complete the following information):

Device: Android emolator
OS: Android Q

Try to bump up flutter app android compileSdkVersion and targetSdkVersion to 29 which is Android 10


[hotfix] fixing infinite retries in prod

@mistercrunch Thanks for fixing this! We experience exactly same issue in production. Given this is a pretty significant bug, can you issue a minor bug fix release soon to include this? Thanks!


Ability to output report for only those functions which exceed threshold.

When I run cr on a large file I get a lot of output. I only want to see the functions that exceed my thresholds. Is there currently an undocumented way to get this limited output? Is this something that other people would be interested in?

There's nothing to help you do this currently.
If you don't mind jumping through a few hoops, for now you could:

Generate a report using the json formatter.

Parse the JSON output.

Something like:
var filtered = data.reports.filter(function (report) {
    if (report.cyclomatic > whatever) { // or report.maintainability etc
        return true;
    }
});

Print the filtered array however you want.

I appreciate that's a bit of an arse ache though. If you're minded to take a stab at properly implementing something with a command line option, be my guest. :)


[WebToolsE2E][Aspire] For Aspire Starter App projects with redis checked, an error occurs when running ‘azd init’.

REGRESSION INFO: Not repro on Aspire 8.0 preview 4
INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU
Install SDK 8.0.203
Install Aspire 8.0 Preview 5 [8.0.0-preview.5.24179.3]
Apply NuGet Feeds.
Install azd

REPRO STEPS

Open Command Prompt, run the following commands to create and build an Aspire application

dotnet new aspire-starter --use-redis-cache -o aspirestarter
cd aspirestarter
dotnet build

Runing 'azd init', select 'Use code in the current directory' > Confirm and continue initializing my app > select 'apiservice' and 'webfrontend', type a new environment name, press enter

ACTUAL
ERROR: configuring ingress for resource cache: binding for does not specify a container port, ensure WithServiceBinding for this resource specifies a hostPort value

EXPECTED
'azd init' can be run successfully.

This issue also reproduce on Mac arm64 with .NET 8.0.204 April Servicing SDK + Aspire 8.0 Preview 5 [8.0.0-preview.5.24179.3] installed.

@rajeshkamal5050 can we have someone investigate, please?

@vhvb1989 this should be addressed by https://github.com/Azure/azure-dev/pull/3612 ?

Yes, @rajeshkamal5050  #3612 has the fix for the breaking change

@rajeshkamal5050 @vhvb1989 I tried using this script to get the latest azd to verify this fix. The script is installing version 1.8.0-beta.1-daily.3649348, which was the same version of azd when we opened this issue. Is there a newer version of azd available and how can I get it? Thanks!

@balachir , azd's daily has an issue.  We're working on it. The daily version you are getting is old.

@balachir , azd daily build is ready now.  You can run the script the get the latest and test.

Verify that this issue has been fixed in the latest build.