Updated Perth meetup organising / location / twitter

Updated Perth meetup organising / location / twitter

Sorry - I should have checked here before fixing this myself.


Initial implementation

Checklist

[x] Keep pull requests small so they can be easily reviewed.
[x] Update the documentation.
[x] Update the ./CHANGELOG.md.
[x] Link this PR to related issues.

Relates to https://ticket.vshn.net/browse/SPKS-46

At the meta-level, it looks like this is similar in functionality to https://github.com/appuio/openshift-prometheus-proxy, do I understand that correctly?

Yes, exactly. Prom-label-proxy combined with kube-rbac-proxy can handle the same use case as openshift-prometheus-proxy (which is what OpenShift 4 does).
In scope of SPKS-46 we use it without any authentication. It should just prevent users from listing all possible namespaces (UIDs).


Unit tests

There's a few options for unit test frameworks as far as Ada goes.
AUnit:
This is the AdaCore/GNAT offering, based off JUnit with modifications. It works, there's plenty of documentation for it, and it's familiar to most people.
VectorCast/Ada:
Commercial. Excellent quality, but probably not what's wanted for a project like this.
Ahven:
I know nothing about this one. Never used it. Seems like another take on JUnit for Ada.
Testing:
My own testing framework. Offers some unusual features like procedure testing, but isn't mature and takes a considerably different approach so it's far less familiar.
Your call. I'll get unit tests made up once a decision is made.

I don't mind too much. I personally would go with AUnit, though if you plan on implementing tests, I think you should be the one to decide :o). Have fun!


Can I have the WSL widget on top of login form?

Hey,
I love WSL and it works great on my site. Would like to ask though: Would it be possible to move the WSL widget so that it appears over the normal login form, instead of under?
Would be more logical for me to encourage the users to log in the easiest way.
Possible?
Thanks a lot for an awesome plugin!

WSL hooks into login_form action and in the login form it's the only suitable hook available. Just checked the wp-login.php code and haven't found any other hook. The only solution I think of is using CSS flex properties to switch the form and widget display positions.


Can't install rocm-dev on Debian Bullseye

Trying to install rocm-dev on Debian Bullseye (Testing) fails due to unmet dependencies.
$ sudo apt install rocm-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 llvm-amdgpu : Depends: libstdc++-5-dev but it is not installable or
                        libstdc++-7-dev but it is not installable
               Depends: libgcc-5-dev but it is not installable or
                        libgcc-7-dev but it is not installable
E: Unable to correct problems, you have held broken packages.

Neither libstdc++-5-dev, libstdc++-7-dev, libgcc-5-dev nor libgcc-7-dev are available for Bullseye anymore

Yes, same here.

And since these are closed source binaries that cannot be re-built for current systems, this, in effect makes all of ROCm lose a principle benefit of open source, being able to port to the system you need to run on.

Things are becoming worse. Now we have this:
$ sudo apt install rocm-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libhsa-runtime64-1 : Depends: libhsakmt1 (>= 2.9.0) but it is not installable
 llvm-amdgpu : Depends: libstdc++-5-dev but it is not installable or
                        libstdc++-7-dev but it is not installable
               Depends: libgcc-5-dev but it is not installable or
                        libgcc-7-dev but it is not installable
E: Unable to correct problems, you have held broken packages.

Any chance to solve this?

You can try to connect the repository for the stable version and take these packages from there, but for me, it breaks the system (conflict). Hope this fixes quickly.

You can try to connect the repository for the stable version and take these packages from there, but for me, it breaks the system (conflict). Hope this fixes quickly.

For me it breaks the system too. And with version 3.7.0, besides having to manually build package from source in https://salsa.debian.org/rocm-team/roct-thunk-interface, still no luck with those gcc dependencies.

I can confirm this is an issue with 3.7. However, you should remember that only Ubuntu 16.04 LTS xenial is supported, and it does provide libstdc++-5. Similarly Ubuntu 18.04 LTS bionic is supported and it provides libstdc++-7-dev.   Also Ubuntu 20.04 LTS focal provides libstdc++-7-dev.
I downloaded the llvm-amdgpu3.7.0_11.0.dev_amd64.deb manually and modified its dependencies (to include libstdc++-10-dev and libgcc-10-dev) and repackaged it back into deb file and installed using dpkg -i without failure.
After that I tested few binaries in /opt/rocm-3.7.0/llvm/bin/ and they all work without issue.
Then I was able to install hip-rocclr3.7.0
This also made /opt/rocm-3.7.0/hip/bin/hipconfig happy (after adding manually a /opt/rocm -> /opt/com-3.7.0 symlink).
And I did manage to compile and run many sample examples.
So it looks like fixable overall.

Still issue in ROCm 3.8.

For anybody struggling with working around this, here is a repackaged unsigned deb with dependencies for libstdc++-10-dev and libgcc-10-dev added.
wget http://repo.radeon.com/rocm/apt/debian/pool/main/l/llvm-amdgpu3.8.0/llvm-amdgpu3.8.0_11.0.dev_amd64.deb
mkdir tmp
dpkg-deb -R llvm-amdgpu3.8.0_11.0.dev_amd64.deb tmpllvm-amdgpu
sed -E -i -e 's/libstdc\+\+-7-dev,/libstdc++-7-dev|libstdc++-10-dev,/' -e 's/libgcc-7-dev$/libgcc-7-dev|libgcc-10-dev/' tmpllvm-amdgpu/DEBIAN/control
dpkg-deb -b tmpllvm-amdgpu llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
sudo dpkg -i llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
rm -rf tmpllvm-amdgpu

@baryluk you need to change the version number also in the DEBIAN/control file, not only the file name. Actually, the file name is irrelevant and only for informative purposes. Furthermore, it is better to use + instead of ~ since the ~ sorts before the rest, meaning that apt update would try to reinstall the broken version.
I have set up a apt repository to get the package. The release files are signed with my GPG key. Here is the apt sources line:
deb https://www.preining.info/debian buster rocm

This package can be installed on buster and above (for the time being).

@norbusan I know the filename is irrelevant. But the version is also irrelevant. As long as you don't remove and install the package using apt it is going to work.

@baryluk yes, that is correct. And since AMD is not shipping minor updates and only major version jumps, the installed version of yours will work the same way.

For anybody struggling with working around this, here is a repackaged unsigned deb with dependencies for libstdc++-10-dev and libgcc-10-dev added.
wget http://repo.radeon.com/rocm/apt/debian/pool/main/l/llvm-amdgpu3.8.0/llvm-amdgpu3.8.0_11.0.dev_amd64.deb
mkdir tmp
dpkg-deb -R llvm-amdgpu3.8.0_11.0.dev_amd64.deb tmpllvm-amdgpu
sed -E -i -e 's/libstdc\+\+-7-dev,/libstdc++-7-dev|libstdc++-10-dev,/' -e 's/libgcc-7-dev$/libgcc-7-dev|libgcc-10-dev/' tmpllvm-amdgpu/DEBIAN/control
dpkg-deb -b tmpllvm-amdgpu llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
sudo dpkg -i llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
rm -rf tmpllvm-amdgpu

https://www.functor.xyz/rocm/llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb (506MB)
9d8e9c711eaa367ef6f054eb3f7c373b8b81ae5a6980d5403f46ec287a72ac01  llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb

Done. Thanks.
But my tensorflow-rocm is not recognised. I use it inside RStudio. Do I have to install rocm-libs too? Instructions are a bit clumsy. Is it normal to have more than 10GB for that library?
Regards

@gfwp You need to install rocm-lib3.8.0 and rccl3.8.0  (or without version is you use unversioned ones). Then do pip3 install tensorflow-rocm, or something like that. Then in RStudio you probably need to do install.packages("tensorflow"). You need to make sure you have correct library paths (i.e. by setting LD_LIBRARY_PATH and ROCM_PATH) before you start. I do that manually like this: LD_LIBRARY_PATH=/opt/rocm-3.8.0/lib ROCM_PATH=/opt/rocm-3.8.0
I don't use RStudio, but I managed to make it work in Python, and R (just to test it).

@gfwp You need to install rocm-lib3.8.0 and rccl3.8.0 (or without version is you use unversioned ones). Then do pip3 install tensorflow-rocm, or something like that. Then in RStudio you probably need to do install.packages("tensorflow"). You need to make sure you have correct library paths (i.e. by setting LD_LIBRARY_PATH and ROCM_PATH) before you start. I do that manually like this: LD_LIBRARY_PATH=/opt/rocm-3.8.0/lib ROCM_PATH=/opt/rocm-3.8.0
I don't use RStudio, but I managed to make it work in Python, and R (just to test it).
Honestly your issue probably is for different issue, not related to this bug.

Thanks a lot

Just FYI, it's easier to workaround the issue if you just install dummy package using equivs: https://wiki.debian.org/Packaging/HackingDependencies
Just create empty package that provides libstdc++-7-dev and libgcc-7-dev.
That said, ROCm should fix its dependency in DEBIAN/control so it references "libstdc++-dev" and "gcc", instead of version-specific "libstdc++--dev" and "libgcc--dev" package.

@tai Thanks. That is a neat trick.
https://www.functor.xyz/rocm/fake-old-libgcc_99_all.deb  should do the trick and work with both rocm 3.8 and 3.9. The equivs source in in the same directory there on the server if you want to check it out.

For anybody struggling with working around this, here is a repackaged unsigned deb with dependencies for libstdc++-10-dev and libgcc-10-dev added.
wget http://repo.radeon.com/rocm/apt/debian/pool/main/l/llvm-amdgpu3.8.0/llvm-amdgpu3.8.0_11.0.dev_amd64.deb
mkdir tmp
dpkg-deb -R llvm-amdgpu3.8.0_11.0.dev_amd64.deb tmpllvm-amdgpu
sed -E -i -e 's/libstdc\+\+-7-dev,/libstdc++-7-dev|libstdc++-10-dev,/' -e 's/libgcc-7-dev$/libgcc-7-dev|libgcc-10-dev/' tmpllvm-amdgpu/DEBIAN/control
dpkg-deb -b tmpllvm-amdgpu llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
sudo dpkg -i llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
rm -rf tmpllvm-amdgpu

https://www.functor.xyz/rocm/llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb (506MB)
9d8e9c711eaa367ef6f054eb3f7c373b8b81ae5a6980d5403f46ec287a72ac01  llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb

please provide step by step guide. i am unable to understand that what to do with that downloaded file. and how to install it. then after which commands should i use. my amd gpu is not working in hashcat and all other applications. i have tried all methods. but same error. please help me.

For anybody struggling with working around this, here is a repackaged unsigned deb with dependencies for libstdc++-10-dev and libgcc-10-dev added.
wget http://repo.radeon.com/rocm/apt/debian/pool/main/l/llvm-amdgpu3.8.0/llvm-amdgpu3.8.0_11.0.dev_amd64.deb
mkdir tmp
dpkg-deb -R llvm-amdgpu3.8.0_11.0.dev_amd64.deb tmpllvm-amdgpu
sed -E -i -e 's/libstdc\+\+-7-dev,/libstdc++-7-dev|libstdc++-10-dev,/' -e 's/libgcc-7-dev$/libgcc-7-dev|libgcc-10-dev/' tmpllvm-amdgpu/DEBIAN/control
dpkg-deb -b tmpllvm-amdgpu llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
sudo dpkg -i llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb
rm -rf tmpllvm-amdgpu

https://www.functor.xyz/rocm/llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb (506MB)
9d8e9c711eaa367ef6f054eb3f7c373b8b81ae5a6980d5403f46ec287a72ac01  llvm-amdgpu3.8.0_11.1.dev~fix1_amd64.deb

please provide step by step guide. i am unable to understand that what to do with that downloaded file. and how to install it. then after which commands should i use. my amd gpu is not working in hashcat and all other applications. i have tried all methods. but same error. please help me.

Better go with @baryluk solution. Just install https://www.functor.xyz/rocm/fake-old-libgcc_99_all.deb. Then ensure you have libstdc++-10-dev and libgcc-10-dev installed. Finally just install rocm-dev from repo.
You can install this file with: dpkg -i fake-old-libgcc_99_all.deb. For rocm-dev, you can follow the instructions in https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html#ubuntu, but if you are using debian, instead of sudo apt install rocm-dkms && sudo reboot at step 3, you better use sudo apt install rocm-dev (no reboot needed in this case). This works if you are using debian testing and have most up to date kernel by having linux-image-amd64 linux-headers-amd64 packages installed and update to testing or unstable.
Hope it helps.

Hi sebastianlacuesta and others,
I have just signed in and want to thank you all !
This has solved my issue of installing rocm-libs in Debian 11
It is vital for upgrading HQplayer Embedded newer version with cuda offload.
Ii

Thanks all for your ideas and suggestions.
As we are not supporting Debian officially, we can not share official info on this.
Request to try with the above tricks and suggestions to overcome installation problems.
Thank you.

@ROCmSupport This is still a bug in the ROCm packages, and should be fixed in ROCm packages, as they are simply incorrect.

Hi @baryluk
We are not able to reproduce this issue with our supported OSes.
For ex: Ubuntu has libstdc++ packages and will be installed automatically.

Big thanks to  baryluk and sebastianlacuesta again !
I now also successfully installed rocm-dkms under Debian 11 after solving kernel header file not found issue.

Hi, I have this issue too, the fakegcc worked for me but there's still one broken dependency: libython3.8. I checked and  my python version is 3.9  and for some reason it can't install the older version. Does anyone know how to create a fakepython.deb file or something like that?

@Dev380 This bug is about the libstdc++ and libgcc-dev. Open a new bug about libpython3.8. Or actually look at the existing issue about this: https://github.com/RadeonOpenCompute/ROCm/issues/1236

@tai Thanks. That is a neat trick.
https://www.functor.xyz/rocm/fake-old-libgcc_99_all.deb should do the trick and work with both rocm 3.8 and 3.9. The equivs source in in the same directory there on the server if you want to check it out.
After downloading, go to directory you downloaded it to, and do sudo dpkg -i fake-old-libgcc_99_all.deb, then continue with normal ROCm installation just like for Ubuntu using normal install guide.

Clever fix! = ) I got a bit further with the fakegcc but not all the way. Hopefully Im stuck at something "easy"...
Im running Bulleye with 5.10.0-8-amd64. Im looking to install rocm to run hashcat on a RX570 board. Running apt install rocm-dkms I get stuck at the following (when rock-dkms is being configured)

Loading new amdgpu-4.3-52 DKMS files...
Building for 5.10.0-8-amd64
Building for architecture amd64
Building initial module for 5.10.0-8-amd64
Error! Bad return status for module build on kernel: 5.10.0-8-amd64 (amd64)
Consult /var/lib/dkms/amdgpu/4.3-52/build/make.log for more information.

Looking through the mentioned log I find at the end

/var/lib/dkms/amdgpu/4.3-52/build/Makefile:26: "Local GCC version 100202 does not match kernel compiler GCC version 100201"
/var/lib/dkms/amdgpu/4.3-52/build/Makefile:27: "This may cause unexpected and hard-to-isolate compiler-related issues"
MODPOST /var/lib/dkms/amdgpu/4.3-52/build/Module.symvers
ERROR: modpost: "migrate_vma_finalize" [/var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu.ko] undefined!
ERROR: modpost: "migrate_vma_pages" [/var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu.ko] undefined!
ERROR: modpost: "migrate_vma_setup" [/var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu.ko] undefined!
ERROR: modpost: "devm_request_free_mem_region" [/var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu.ko] undefined!

There is no file /var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu.ko
Any ideas or hints? Thanks a bunch!

Upgraded to Bullseye, removed all packages without source (incl the fake gcc tricky) and after making sure the kernel matches the compiler, rock-dkms gives
  CC [M]  /var/lib/dkms/amdgpu/4.3-52/build/amd/amdgpu/amdgpu_device.o
gcc: fatal error: cannot specify ‘-o’ with ‘-c’, ‘-S’ or ‘-E’ with multiple files

Wondering if it would be easier to have something with docker for the ubuntu userspace once the kernel parts are hacked together to compile-load with Bullseye?

Not using right now, but taking a look once in a while just to see how this goes. I tested clinfo with rocm-dev install and kernel in experimental 5.13 and it works. README.md points that  IPC and RDMA capabilities are not yet enabled, so if you don't need this, maybe can try it without rocm-dkms. I confirmed that kernel 5.10 doesn't support what rocm 4.3 userspace needs. Best of luck.

@martinpaljak Did you find a solution for that dkms build?
I'm seeing the same issue with the current release of the amdgpu-dkms driver on Ubuntu 21.10 installs:
  CC [M]  /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/scheduler/sched_main.o
gcc: fatal error: cannot specify ‘-o’ with ‘-c’, ‘-S’ or ‘-E’ with multiple files

My guess is that this is something that broke the and dkms setup with bullseye/impish. (But using CC=gcc-10 also doesn't fix the issue.)

@satmandu I have a custom kernel with some parts of enabled manually, using rocm-opencl clinfo shows the GPU as a device, at least. Hashcat does not see it, but I think that might be a simpler path than dealing with dkms.

rocm deb packages are designed for Ubuntu Focal, so either grab the necessary packages from Ubuntu and install them, or create custom packages that provide the dependencies for your distro.

Are .dsc, orig.tar.gz and diff.gz files avaiable for these packages? Or sources with proper debian directory so everyone can change locally and support other debian derived distros unofficially?

You can create your own dummy packages for libgcc-7-dev and libpython3.8, then manually link (dummy) libpython3.8 to libpython3.9 for rocm-gdb dependencies.
create two files "fake-libpython3.8" and "fake-libgcc-7-dev" (contents below)
install equivs
run equivs-build $file
install resulting deb files
configure rocm deb repository
install desired rocm packages (i use rocm-opencl and rocminfo)
"fake-libgcc-7-dev" contents:
Section: misc
Priority: optional
Standards-Version: 3.9.2

Package: fake-libgcc-7-dev
Version: 1.0
Provides: libgcc-7-dev, libstdc++-7-dev
Architecture: all
Description: Fake libgcc7-dev package to satisfy dependencies
 Fake libgcc7-dev package to satisfy dependencies

"fake-libpython3.8" contents:
Section: misc
Priority: optional
Standards-Version: 3.9.2

Package: fake-libpython3.8
Version: 1.0
Depends: libpython3.9
Provides: libpython3.8, libpython3.8-minimal, libpython3.8-stdlib
Architecture: all
Description: Fake libpython3.8 package to satisfy dependencies
 Fake libpython3.8 package to satisfy dependencies

## MANUAL INSTALL
#sudo ln -s /usr/lib/x86_64-linux-gnu/libpython3.9.so /usr/lib/x86_64-linux-gnu/libpython3.8.so
#sudo ln -s /usr/lib/x86_64-linux-gnu/libpython3.9.so /usr/lib/x86_64-linux-gnu/libpython3.8.so.1
#sudo ln -s /usr/lib/x86_64-linux-gnu/libpython3.9.so /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0

@xmixahlx another thing is that it tries to pull rocm-llvm, but I already have llvm-15 from
deb http://apt.llvm.org/focal/ llvm-toolchain-focal-15 main

I'll try to fake that too

Same problem when installing amdgpu-dkms on degraded kernel version 'x86_64 Linux 5.10.0-21-amd64' Parrot Electro ara 5.1 operating system
  947   │   LD [M]  /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.o  948   │ /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Makefile:26: "Local GCC version 100202 does not match kern        │ el compiler GCC version 100201"  949   │ /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Makefile:27: "This may cause unexpected and hard-to-isolat        │ e compiler-related issues"  950   │   MODPOST /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Module.symvers  951   │ ERROR: modpost: "migrate_vma_finalize" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.        │ ko] undefined!  952   │ ERROR: modpost: "migrate_vma_pages" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.ko]        │  undefined!  953   │ ERROR: modpost: "migrate_vma_setup" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.ko]        │  undefined!  954   │ ERROR: modpost: "devm_request_free_mem_region" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu        │ /amdgpu.ko] undefined!  955   │ make[2]: *** [/usr/src/linux-headers-5.10.0-21-common/scripts/Makefile.modpost:123: /var/lib/dkms/amdgpu        │ /<IP_ADDRESS>-1290604/build/Module.symvers] Error 1  956   │ make[2]: *** Deleting file '/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Module.symvers'  957   │ make[1]: *** [/usr/src/linux-headers-5.10.0-21-common/Makefile:1765: modules] Error 2  958   │ make: *** [/usr/src/linux-headers-5.10.0-21-common/Makefile:185: __sub-make] Error 2  959   │ make: Leaving directory '/usr/src/linux-headers-5.10.0-21-amd64'

Same problem when installing amdgpu-dkms on degraded kernel version 'x86_64 Linux 5.10.0-21-amd64' Parrot Electro ara 5.1 operating system
 │   LD [M]  /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.o
   │ /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Makefile:26: "Local GCC version 100202 does not match kern
   │ el compiler GCC version 100201"
   │ /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Makefile:27: "This may cause unexpected and hard-to-isolat
   │ e compiler-related issues"
   │   MODPOST /var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/Module.symvers
   │ ERROR: modpost: "migrate_vma_finalize" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.
   │ ko] undefined!
   │ ERROR: modpost: "migrate_vma_pages" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.ko]
   │  undefined!
   │ ERROR: modpost: "migrate_vma_setup" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu/amdgpu.ko]
   │  undefined!
   │ ERROR: modpost: "devm_request_free_mem_region" [/var/lib/dkms/amdgpu/<IP_ADDRESS>-1290604/build/amd/amdgpu
   │ /amdgpu.ko] undefined!

Please open a separate bug. As your issue has nothing to do with this issue.


Update BBE for consistency

Purpose
This PR update the names of the files related  to JWT service BBE, in order to maintain the consistency.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #21775 into stage will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage   #21775   +/-   ##
=======================================
  Coverage   14.67%   14.67%
=======================================
  Files          51       51
  Lines        1404     1404
  Branches      216      216
=======================================
  Hits          206      206
  Misses       1182     1182
  Partials       16       16

Continue to review full report at Codecov.

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


[Event Request] Codeunit 80 Sales Post - OnBeforePostItemLineNotToShip

Hi, in the Codeunit 80 Sales Post, would it be possible to get an event OnBeforePostItemLineNotToShip, like this :

Thanks

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Fix issue when adding a property on a vectorized collection

and define skip_vectorization and vectorize_property_name

hey, I took your changes and made a new PR here: https://github.com/weaviate/weaviate-python-client/pull/1250 - thx for fixing it :)


Remove IsJsonable

This removes the IsJsonable utility type from BaseControllerV2. It seems like we can get away with just using the Json type, and requiring that state generics extend Record<string, Json>.

For reference, here's the test suite I used for isJsonable. And here's the same test suite for Json.
Huh. Not as far off as I remember. It doesn't like interfaces or classes seemingly.

Edited one of the above playgrounds here for clarity.

Hah, go figure. I didn't realize IsJsonable prevent any. Given that any basically serves the role of disabling the type checker, it doesn't seem like a deal breaker that it can do the same here? We can just enforce not using it by convention.

Yep, we could do that! Or we could add a NotAny<> type condition specifically for that, and discard the rest in favour of this Json type.

On second thought, I think you're right. any is meant as an escape hatch, and we already need to be diligent about not using it. Adding additional obstacles to using it for controller state specifically doesn't seem especially valuable, since if we're not already diligent about not using it elsewhere, our types won't be correct regardless.


[Feature] New choice to deploy our bot

Descriptions
Maybe we van choose Heroku to deploy our bot

https://github.com/FawenYo/LINE_Bot_Tutorial


Search widget should use latest URLs

Currently, the search widget, which indexes the latest Boost release (1.87 as of this writing), returns links containing that specific version. For instance, "concurrent_factory" returns
https://www.boost.io/doc/libs/1_87_0/libs/flyweight/doc/reference/factories.html#concurrent_factory_synopsis
etc. It'd be better if it returned
https://www.boost.io/doc/libs/latest/libs/flyweight/doc/reference/factories.html#concurrent_factory_synopsis
instead.

I'm not very familiar with how search works, but it seems like the fix might need to be in boost-gecko rather than this repo. Am I wrong about that?
I did try changing the data-current-boost-version attribute to latest, but got this unsurprising error message.

Maybe @ashtum could provide thoughts on how to proceed?


ARROW-13191: [Go] allow external schema in ipc readers

10603

 Quality gate: Passed
 Everything looks good
Details

 Quality gate: Passed
 Everything looks good
Details

 Quality gate: Failed
 Everything looks good
Details


Is this project abandoned?

As the title says. Doesn't look like it's been updated for awhile, quite a few concerning open issues (including crashing the server, sending the password in response to login, incompatible with current version of nodemailer, etc. ) and other forks (for example: https://github.com/Overplay/waterlock-local-auth) appear to be more active.
So what is the status of this project? Any chance to have it move forward with one of the forks going into npm?

I would be glad to hear for the latest news either.
Thanks,

It´s happening the same with main watelock project... Nevertheless, a pull request was accepted a few days ago so it´s not totally abandoned 😜
@duhruh, could you give us some light about the project status?

+1

+1

@duhruh please let us know if someone can jump in and give you an hand guys.


Version 0.4.7

Updated requirements

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.66%. Comparing base (d7fc674) to head (74dca50).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   91.61%   91.66%   +0.04%
==========================================
  Files          73       73
  Lines        2314     2315       +1
  Branches      105      104       -1
==========================================
+ Hits         2120     2122       +2
  Misses        161      161
+ Partials       33       32       -1

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


[bug] Moving tables on HiDPI screens

Hi. Really nice extension!
When I was playing around with it on the demo site I observed that dragging and moving tables around on a HiDPI screen causes an offset.
This does not occur on screens with standard pixel ratio.
See attached gif demonstrating the issue:

I'm using latest Edge (Chromium-based) on Windows 10.
Cheers

Thank you for the very kind issue.
I could easily recognize it.


AdaptiveExpressions library could be in a separate repository

Consider moving AdaptiveExpressions  out of the BotBuilder repository, into its own repo.
One reason in particular is the struggle to get these tests right, and the build passing consistently.  The amount of time and effort spent on failing builds due to AdaptiveExpressions could be much more isolated if this library was in a separate repository, and just pulled in as a dependency.

@EricDahlvang this seems like it should be moved to microsoft/botframework-sdk as adaptive-expressions exists in botbuilder-js and work is being done on it in botbuilder-python.
What do you think?


Upgrade to Java v17

Ticket #63 is about upgrading to WildFly 27 Final. Let's upgrade to Java v17 as it is the version recommended by RedHat for WildFly v27. Java v17 is also the last LTS.

Let's first implement ticket #63 (WildFly upgrade) before working on this ticket.

Tradista is now upgraded to Java 17.
This ticket will be included in v2.0.0


PLAT-126343:  Add UI tests for agate/Dropdown

Enact-DCO-1.0-Signed-off-by: Stanca Pop<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Resolution

added UI tests for agate/Dropdown

Additional Considerations
Links
PLAT-126343
Comments

I feel that the verification script is somewhat lacking.
If there is a disabled element, it would be better if there is script to verify disabled function.
Hopefully the test script will be added after Agate TC is added more.


[ENHANCEMENT]: Export C14nCanonicalization, ExclusiveCanonicalization

Is your feature request related to a problem? Please describe...
I'm trying to use those classes for other processes, I have done it this way
const DOMParser = require("@xmldom/xmldom").DOMParser;

const C14nCanonicalization = require('xml-crypto/lib/c14n-canonicalization').C14nCanonicalization;
const ExclusiveCanonicalization= require('xml-crypto/lib/exclusive-canonicalization').ExclusiveCanonicalization;

let xml_string = '<root><child>123</child></root>';
let documentElement= (new DOMParser()).parseFromString(xml_string).documentElement;

// C14nCanonicalization
console.log( (new C14nCanonicalization()).process(documentElement, {}).toString() );
// ExclusiveCanonicalization
console.log( (new ExclusiveCanonicalization()).process(documentElement, {}).toString() );

Describe teh solution you'd like...
But I would like to make it a little more direct with the require, example:
//const C14nCanonicalization = require('xml-crypto/lib/c14n-canonicalization').C14nCanonicalization;
const C14nCanonicalization = require('xml-crypto/c14n-canonicalization');
//const ExclusiveCanonicalization= require('xml-crypto/lib/exclusive-canonicalization').ExclusiveCanonicalization;
const ExclusiveCanonicalization= require('xml-crypto/exclusive-canonicalization')

Describe the alternatives you've considered...
I don't know if it is already possible in a similar way, because I did not find it in the documentation

You're requireing the module, and then you need to reference the object in the module you'd like to work with. The only way to do what you're looking for would be to used a default export, and we aren't doing that. Otherwise you could use an import statement, but that is usually more TypeScript.


Turn on line separator detection for CSV/TSV import. Fixes #6691

Fixes #6691
Changes proposed in this pull request:

Turn on line separator detection for CSV/TSV import
Also add test coverage for the CRLF case for Windows

Rebased to test with latest importer changes.

@thadguidry You should be able to test this with the snapshot build

Built and tested.  Works like a charm now.  Thanks @tfmorris !

@thadguidry Thanks for testing! @wetneb Thanks for the review!


bsh.CallStack is not Serializable

I'm running beanshell scripts over an RMI connection and
I'm trying to return beanshell exceptions over the
connection, but I can't. I get the following exception:
java.rmi.UnmarshalException: error unmarshalling return;
nested exception is:
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException: bsh.CallStack
at sun.rmi.server.UnicastRef.invoke(Unknown
Source)
After looking at the source, it seems a simple change to
just implement the Serializable interface on the
bsh.CallStack class. An oversite perhaps?
Reported by: frdfsnlght
Original Ticket: "beanshell/bugs/156":https://sourceforge.net/p/beanshell/bugs/156

CallStack is serializable in BeanShell 3.0.0-SNAPSHOT.936

Closed: is as expected


[BUTTON IDEA]: diagonal patterns

Hey , I have new animated button idea to add : appearing diagonal patterns while hover on buttons.
Originally posted by @atenasadat in https://github.com/sButtons/sbuttons/discussions/1206

@atenasadat you are assigned to this

Sure. working on it


build: release prebuilt binaries

We need to release pre-built binaries for Linux, macOS, and Windows on each release. This can be done with some tooling. The binaries should follow the same naming convention for each release going forward so tooling and our scripts can bump a version in the URL.
Related: https://github.com/moov-io/docs/issues/27

I've used these tools before,

github-release for creating the release and uploading binaries
promu for (cross-)building on one system. Example Config

Whatever we do will likely be copied to each project, so that's why I'm leaning towards using a couple tools rather than grow the makefile.

I have also used gox and had a build script similar to the one used on Nats.io cross_compile.sh and leverage the travis-ci after_success: and tagged as a release


fix name_to_start_end regex

Describe changes
Fixes a bug in the regular expressions that was noticed while fixing agg_lt. The bug was identifying "-" in the interval name.
What issues are related
Related to https://github.com/ihmeuw-demographics/lifetableMethods/issues/23
Checklist
Packages Repositories

[X] Have you read the contributing guidelines for ihmeuw-demographics R packages?

[X] Have you added in tests for the changes included in the PR?
[X] Do the changes follow the ihmeuw-demographics code style?

Does this work with a name like "10-20"?

Nope only things formatted like "[{number}, {number})" which is how they are stored internally in hierarchyUtils and this helper function isn't exported currently.


History Page content difficult to parse

The page is basically inscrutable at this point.  We need to parse the fields better so the user can see changes to the article easily.

This issue has essentially been resolved in development, but not yet merged to production.  tl;dr -- added a latest_update field to :articles and on save copy that field into @version meta data then shown in the history and mailer.
Specifically here is what has changed:

Added a field for `latest_update" to the article model
Added a fieldset to article/_form for inputting the latest_update text
Edited articles_controller storng params to include :latest_update
Added a `blurb' text field to the Versions model
set article.rb to update version.blurb to_eq @article.latest_update when a version is created
boldNote: I attempted unsuccessfully to clear the latest_update form in the field also, the same field is present in the new_article view which may not make sensebold

More changes:

Edited History View to use new blurb and also minor cleanup
Edited mailer to include blurb info
Added conditional to articles#update to not send email if the latest_update field is blank

Changes to come before merging to production:

Change Date to EST on history page
Display environment in update email header
Add default message to History Page for blank blurbs

So, here's some feedback:

Change Date to EST on history page

You can't change the date to EST because not every user of the site is or will be in EST. I'll need you to review this article about having timezones per user in our app, which we will need to implement in this app.

It's set to local time. Not just est.
On Aug 20, 2015 7:28 PM, "Mark Nyon"<EMAIL_ADDRESS>wrote:

So, here's some feedback:

Change Date to EST on history page

You can't change the date to EST because not every user of the site is or
will be in EST. I'll need you to review this article
https://robots.thoughtbot.com/its-about-time-zones about having
timezones per user in our app, which we will need to implement in this app.
—
Reply to this email directly or view it on GitHub
https://github.com/BOWiki/BOW/issues/71#issuecomment-133210511.

To clarify. The time zone will match the current user.
On Aug 20, 2015 7:29 PM, "Darius Goore"<EMAIL_ADDRESS>wrote:

It's set to local time. Not just est.
On Aug 20, 2015 7:28 PM, "Mark Nyon"<EMAIL_ADDRESS>wrote:

So, here's some feedback:

Change Date to EST on history page

You can't change the date to EST because not every user of the site is or
will be in EST. I'll need you to review this article
https://robots.thoughtbot.com/its-about-time-zones about having
timezones per user in our app, which we will need to implement in this app.
—
Reply to this email directly or view it on GitHub
https://github.com/BOWiki/BOW/issues/71#issuecomment-133210511.

How is that being implemented?

I think there is s ruby method called localtime. If you look in
history.html you'll see that is what I am using. Obviously I can only see
one time zone, but we can get some one in a different place to confirm.
On Aug 20, 2015 7:32 PM, "Mark Nyon"<EMAIL_ADDRESS>wrote:

How is that being implemented?
—
Reply to this email directly or view it on GitHub
https://github.com/BOWiki/BOW/issues/71#issuecomment-133211101.

So here is some more feedback:

app/assets/javascripts/maps.coffee isn't used, so it needs to be removed, and should not have been added to version control.

app/assets/stylesheets/maps.scss - also isn't used, so it should be removed

app/controllers/maps_controller.rb - keeps repeating the same controller code over and over again from line 18 on. Check out app/controllers/articles_controller.rb and app/helper/articles_helper.rb for the marker_locations_for method. This will remove the multiple lines of code that are in app/controllers/articles_controller.rb and app/controllers/maps_controller.rb

app/helpers/maps_helper.rb - Remove, since it's not being used

app/views/maps/index.html.erb - The script at the end of the file should also be put into a helper, since its used in multiple places. This is the one that starts on line 33 with <script type="">

Looking at the history page - The message that is shown when there is no significant change has extra padding on either side caused by the space in the pre tag. The screenshot is shown

If there are no changes, there shouldn't be a sentence that says "Summary of changes in this version" with a box around it. The sentence "There are no significant changes in this version" should replace the sentence and the box.

MAde all the above fixes save those related to cleaning up the maps logic. @mark, please take a look when you get  a chance.

Where should I look at this update? Is it saved to github?

Based upon this diff, I have the following comments:
app/controllers/articles_controller.rb:69: if @article.latest_update != nil && @article.latest_update != "" can be replaced with unless @article.latest_update.blank?
app/mailers/user_notifier.rb: Is there a spec for the different subject lines?

I just pushed the blurbs branch adding validation that requires an article to have at least one subject. I added an rspec and factry .  Those specs seem to work fine.  However, after adding the custom validation specs, the geocoder specs are now failing.  full trace:
Failures:

geocoded has a latitude
Failure/Error: article = FactoryGirl.create(:article)
ActiveRecord::RecordInvalid:
Validation failed: An article must have at least one subject
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/validations.rb:79:in `raise_record_invalid'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/validations.rb:43:in `save!'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/attribute_methods/dirty.rb:29:in `save!'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/transactions.rb:291:in `block in save!'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/transactions.rb:347:in `block in with_transaction_returning_status'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/transaction.rb:188:in `within_new_transaction'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/transactions.rb:220:in `transaction'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/transactions.rb:344:in `with_transaction_returning_status'
./.bundle/gems/ruby/2.2.0/gems/activerecord-4.2.1/lib/active_record/transactions.rb:291:in `save!'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/configuration.rb:14:in `block in initialize'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/evaluation.rb:15:in `[]'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/evaluation.rb:15:in `create'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/strategy/create.rb:12:in `block in result'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/strategy/create.rb:9:in `tap'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/strategy/create.rb:9:in `result'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/factory.rb:42:in `run'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/factory_runner.rb:23:in `block in run'
./.bundle/gems/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/notifications.rb:166:in `instrument'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/factory_runner.rb:22:in `run'
./.bundle/gems/ruby/2.2.0/gems/factory_girl-4.5.0/lib/factory_girl/strategy_syntax_method_registrar.rb:20:in `block in define_singular_strategy_method'
./spec/models/article_spec.rb:51:in `block (2 levels) in <top (required)>'
./spec/rails_helper.rb:76:in `block (3 levels) in <top (required)>'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/generic/base.rb:15:in `cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/base.rb:92:in `cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:86:in `block (2 levels) in cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:87:in `call'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:87:in `cleaning'
./spec/rails_helper.rb:75:in `block (2 levels) in <top (required)>'

@campgurus So, the subject validation issue is #87, which is different from this one. I would take the subject validation code out of the 'blurbs' branch and put it into a separate branch off of master, one that starts with '87', such as 87_subject_validation. Put the code in that branch and try running the specs separately.

I have managed to make some changes to the factories which seem to have alleviated the validation error.  However, I am now getting a new error.  here is the trace:

ArticlesController#create when valid success
Failure/Error: expect(response).to redirect_to(article_path(Article.last))
ActionController::UrlGenerationError:
No route matches {:action=>"show", :controller=>"articles", :id=>nil} missing required keys: [:id]
./.bundle/gems/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:259:in `raise_generation_error'
./.bundle/gems/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:234:in `optimized_helper'
./.bundle/gems/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:220:in `call'
./.bundle/gems/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:345:in `block (2 levels) in define_url_helper'
./spec/controllers/articles_controller_spec.rb:50:in `block (4 levels) in <top (required)>'
./spec/rails_helper.rb:76:in `block (3 levels) in <top (required)>'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/generic/base.rb:15:in `cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/base.rb:92:in `cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:86:in `block (2 levels) in cleaning'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:87:in `call'
./.bundle/gems/ruby/2.2.0/gems/database_cleaner-1.3.0/lib/database_cleaner/configuration.rb:87:in `cleaning'
./spec/rails_helper.rb:75:in `block (2 levels) in <top (required)>'

What is the actual error that is attached to this stacktrace?

the relevant branch is "blurbs"

Did we rebase this? I still see some changes on master that are not implemented in the blurbs branch.

We are currently adding Cucumber specs as we try to re-add these fixes with more robust testing.
Current failing test has capybara unable to find the form field.  The current field name matches the html id for the element.  here is the error/trace:
~/development/blackops$ rake cucumber                                                             *[blurbs]
/Users/dariusgoore/.rubies/ruby-2.2.1/bin/ruby -S bundle exec cucumber  --profile default
Using the default profile...
Feature: Edit article with blurbs
  In order to send a clear update
  As an editor
  I want to add a summary of my edits

  Scenario: Article Edit With Blurb                                       # features/edit_with_blurbs.feature:6
    Given I am on the show page                                           # features/step_definitions/path_steps.rb:4
    And I follow "Edit"                                                   # features/step_definitions/general_steps.rb:4
    When I fill in "article_latest_update" with "This is my edit summary" # features/step_definitions/general_steps.rb:8
      Unable to find field "article_latest_update" (Capybara::ElementNotFound)
      ./features/step_definitions/general_steps.rb:9:in `/^I fill in "(.*?)" with "(.*?)"$/'
      features/edit_with_blurbs.feature:9:in `When I fill in "article_latest_update" with "This is my edit summary"'
    And I press "Update Article"                                          # features/step_definitions/general_steps.rb:12
    And visit the history page                                            # features/step_definitions/path_steps.rb:10
    Then I should see "This is my edit summary"                           # features/step_definitions/general_steps.rb:16

Failing Scenarios:
cucumber features/edit_with_blurbs.feature:6 # Scenario: Article Edit With Blurb

Taking a look at the state of this branch now. It looks like there is a warning and an error. The error is:
 Scenario: Article Edit With Blurb                       # features/Edit_with_blurbs.feature:6
    Given I am on the show page                           # features/step_definitions/path_steps.rb:4
      PG::UniqueViolation: ERROR:  duplicate key value violates unique constraint "states_pkey"
      DETAIL:  Key (id)=(33) already exists.
      : INSERT INTO "states" ("name", "id", "ansi_code", "created_at", "updated_at") VALUES ($1, $2, $3, $4, $5) RETURNING "id" (ActiveRecord::RecordNotUnique)
      ./features/step_definitions/path_steps.rb:5:in `/^I am on the show page$/'
      features/Edit_with_blurbs.feature:7:in `Given I am on the show page'
    And I follow "Edit"                                   # features/step_definitions/general_steps.rb:4
    When I fill in "blurb" with "This is my edit summary" # features/step_definitions/general_steps.rb:8
    And I press "Update Article"                          # features/step_definitions/general_steps.rb:12
    And visit the history page                            # features/step_definitions/path_steps.rb:10
    Then I should see "This is my edit summary"           # features/step_definitions/general_steps.rb:16

. There is an attached warning which I believe is related
[mnyon@mnyon ~/code/ebwiki (git::blurbs) ] rake cucumber
/Users/mnyon/.rvm/rubies/ruby-2.2.1/bin/ruby -S bundle exec cucumber  --profile default
WARNING: You have set Rails' config.cache_classes to false (most likely in config/environments/cucumber.rb).  This setting is known to cause problems with database transactions. Set config.cache_classes to true if you want to use transactions.

I think that I need to investigate the state of the DB when tests are running.

Forensics...
[mnyon@mnyon ~/code/ebwiki (git::blurbs) ] rake cucumber
...
[7] pry(#<Cucumber::Rails::World>)> Rails.env
=> "development"

[mnyon@mnyon ~/code/ebwiki (git::blurbs) ] rake
...
1] pry(#<RSpec::ExampleGroups::Agency>)> Rails.env
=> "test"

For a short term solution, I invoked a RAILS_ENV= test cucumber, which runs the features in the test environment. This seems to deal with the failure occurring before. Unfortunately, the test is going to a different page than expected.
While we want to test
http://example.com/articles/<article_name>/edit,
the feature test looks like the test is not on the Edit Case page as expected, but this page:
http://www.example.com/guidelines
We need to put the proper page in.

While I am not sure blurbs is the right way to go about adding more descriptive "commit messages" to edits, the need to do better than what we have in place is becoming very clear as we attempt to view changes, made by our first very active public editor.  Viewing the following history tab e.g. :http://ebwiki.org/articles/charly-leundeu-keunang/history it is basically impossible to figure out what changes he has made to the content.

I think the solution is to create an associated table commit_messages or something attached to the version s.t. commit_message belongs_to Version.  Trying to figure out hos to create an association with the Versions table which was created within the paper_trail gem.

I am still trying to figure out the best way to do this.  I was thinking this was like our other nested elements like links, but I am not sure it works.  First of all, once a link is created, that editable link is displayed within the article form. We don't want previous commit messages displayed in the form and nor should they be editable. My current thought is to create a last_version_summary field that saves with the article which will always be on the form displaying the last edit summary.  Then use a callback to edit @article.versions.last.summary, which will be the permanent record of the change summary.

We got an answer to this question on SO here: https://stackoverflow.com/questions/36168574/how-to-access-paper-trails-version-model.
The answer points to discussion of "storing metadata" in the paper_trail docs: https://github.com/airblade/paper_trail#4c-storing-metadata

With the last commit, this finally works. In all, this is what has been done:

Added a summary attribute to Article model to store the blurb temporarily
Added a field for summary within the Article edit/create form
Add a model method to Article to return the article.summary
Add a comment attribute to the Versions table to permanently house the summary
Set meta data to copy the summary into the version comment field
Set article.summary => nil within the article edit action to make the field blank for editing

Still need to add some rspec to:

test the validation that editor provides a summary when editing
test that version has a summary that matches the edit entry

Non-essential things I would still like to change:

remove the field for new articles and set the summary field to "article created"
use a popup form when the user clicks to submit to remind the user to submit a summary of changes

helpful tutorial on this is: https://samurails.com/gems/papertrail/

One ore thing when this issue is approved.  We should add the summary to the email to followers s.t. they can get a sense of what has been changed in the article without having to visit the site.  At the very least, we need to let them know to check the history tab.

So I think that the order of the commits should be reversed, most recent first.
I also think that there should be some explanatory text to describe what the history tab does, and to distinguish history of the information written from the history of the case itself. This includes outlining which fields trigger history.
Also, if someone enters the summary without making changes, it just saves without comment. It should raise an error and allow the user to enter/update information
Finally, is there an objection to putting everything in version history? Seems like a lot could slip through the cracks as is...

To the last point,  is there an objection to putting everything in version history? the answer is no.
If I am understanding correctly, this has already been fixed.  A new version is created when any attribute is changed, with :summary now an exception to that rule.

but an update doesn't occur if someone updates any associated pieces, such as subjects, links or comments.

Not at this time.  Let's release this and make a new issue for associated objects. Actually, the issue already exists  in #481.

Then that needs to be added to the copy on the history page, otherwise it's not really clear.

Ok.  But rather than me interpreting what you are saying, making changes, coming back to you, making more changes, can you just edit the following text which is currently there to change it to what you want?

Any time any information about a case is updated, a new version is created. This page shows the history of this article and lists all the changes that have been made to the article over time.


fix: update auth logic

As auth can be undefined on the server as well, it's absolute necessary to check if auth object exists on the server. Better detection of a client would be of typeof window of typeof document.


Add error detection for Substance-only species

Substance-only can only be applied to species

Implemented in https://github.com/sys-bio/vscode-antimony/commit/35f35e9a091bd921f567bc3645bafecb7bddea0c


Menu highlight in manual mode

When passing the stages, the menu buttons are highlighted when ready.

rebased

@TaunT
What do you think about leaving only the last clicked button highlighted and setting the rest to default ?

@ogkalu2 It is possible this way) Some kind of mark is needed, because in manual mode you get distracted by other things and several times it happened that I mistakenly pressed an already completed step, starting it again and losing something


Invalidate routes instead of paths

It would be nice to be able to invalidate routes instead of path/pathSet.
from #514
Ex.
{
  route: 'posts[{keys:postIds}].myFunction',
  call: () => {
    ...
    return { route: 'posts[{keys}].data', invalidated: true };
  }
}

@quazzie unbounded invalidations can be tricky and dangerous.  Here is a bit more defined way of doing this.
{
    route: 'posts[{keys:postIds}].myFunction',
    call: (aliasMap) => {
        ...
        // use array syntax, its faster.
        return { path: ['posts', aliasMap.postIds, 'data'], invalidated: true };
    }
}

* literally used in the correct english way here, not figuratively


Add rpath fix to Native Publish PyTorch

This adds the install name tool rpath fix to downloading the pytorch native libraries.
It also updates the gradle script that runs the publish to run on osx which has
the fixer tool instead of osx.
It does have a minor breaking aspect as now the publish must be run from osx. I
did add an early error in case it is run from a different os.

Codecov Report

Merging #1639 (26cf01e) into master (bb5073f) will decrease coverage by 1.36%.
The diff coverage is 62.08%.

@@             Coverage Diff              @@
##             master    #1639      +/-   ##
============================================
- Coverage     72.08%   70.72%   -1.37%
- Complexity     5126     5421     +295
============================================
  Files           473      507      +34
  Lines         21970    23769    +1799
  Branches       2351     2589     +238
============================================
+ Hits          15838    16810     +972
- Misses         4925     5665     +740
- Partials       1207     1294      +87

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <ø> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../modality/cv/translator/YoloTranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...i/djl/modality/cv/translator/YoloV5Translator.java
5.69% <0.00%> (ø)

...odality/cv/translator/YoloV5TranslatorFactory.java
8.33% <0.00%> (-1.67%)
:arrow_down:

...pi/src/main/java/ai/djl/ndarray/BytesSupplier.java
54.54% <0.00%> (-12.13%)
:arrow_down:

api/src/main/java/ai/djl/ndarray/NDArray.java
77.84% <ø> (+0.56%)
:arrow_up:

...ain/java/ai/djl/ndarray/index/dim/NDIndexPick.java
100.00% <ø> (ø)

... and 243 more

Continue to review full report at Codecov.

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


Support for external wallets in templates

This issue is part of https://github.com/latticexyz/mud/issues/2256

Motivation
Currently, the templates generated by the create-mud command use internal burner wallets in the clients. To facilitate non-local environments, developers are required to manually integrate external wallet connections.
Having external wallet support into the templates would be beneficial. This issue is aimed at achieving that goal.
Possible implementation options
Several approaches can be considered.
External wallet support options
Note: wagmi is a React library that internally utilizes the vanilla JavaScript library @wagmi/core.
Major libraries supporting wallet connections include:

@rainbow-me/rainbowkit: Styled React components built on wagmi. Used by Sky Strife and Redstone websites.
connectkit: Styled React components built on wagmi.
@rabby-wallet/rabbykit: Styled UI built on @wagmi/core.
@web3modal/wagmi: Styled UI built on @wagmi/core.
wagmi: React Hooks built on @wagmi/core.
@wagmi/core (and @wagmi/connectors): A vanilla JavaScript library.
mipd: JavaScript utilities for EIP-6963 by the wevm team. This is used in @wagmi/core. The retrieved Ethereum providers can be used for the viem's client custom transport. Although the conventional window.ethereum (EIP-1193) still works with viem, it's not recommended due to limitations in multi-wallet support. Most wallets are compatible with EIP-6963.

Options for integrating external wallets into templates
The objective is to maintain the current user experience in existing templates, which are designed to work out-of-the-box without necessitating external wallets.
Options include:

Creating new templates that use external wallets instead of the existing burner wallets.
Updating existing templates to support both external wallets and burner wallets.

Ideally, the create-mud command would allow users to choose their preferences for various aspects (e.g., react or vanilla, burner or external wallet, wagmi or rainbowkit, ecs or something). However, this requires improvement to template management and create-mud, which I'd like to work on a separate project if desired.
Proposed solution
For the external wallet connection, I'd like to use @wagmi/core for vanilla templates and wagmi for react templates. This approach is preferred as it's less-opinionated and does not add any new dependencies, since developers are likely to use Wagmi in their projects. I will not include support for the WalletConnect v2 protocol, as it requires a project ID for setup. Developers can add the support later easily.
For the integration of external wallet support into templates, I'd like to create new templates (vanilla-external-wallet and react-external-wallet) that include this feature, thereby not impacting existing templates. As the better wallet support project advances, I plan to update these new templates continually. Once it's ready, I'll apply the wallet support into the existing templates and remove the newly added ones. An alternative approach could be starting with implementations in the examples/ directory before rolling them out to the templates. I don't think combining the existing burner wallets and external wallets within the same client is a good idea due to the complexity it introduces. Wagmi does not effectively manage providers and burner wallets together, so the client code would need additional wallet management logic.

Open Questions
How should we continue supporting the burner wallet feature in our templates?
I'll bring the main account (from an external wallet) and session account mapping feature to the templates as my next task in the project, which reduces the friction of signing transactions multiple times. It's a more realistic setup but still requires an external wallet to be installed. I am thinking about whether we want all templates to include the burner wallets which work without external wallets.

Closing in favor of https://github.com/latticexyz/mud/issues/2852


version 3.3 freeze the app and high cpu usage 100%

version 3.3 freeze the app and high cpu usage 100%

Hello @mouness2020, could you provide me more information about steps to reproduce and iOS version?
And could you remake this issue using our template for issues, if it possible, thank you 🙏

cant reproduce


Allow user creation from user management GUI

Generally its a bad idea to enable user registration for anyone, so i rather disable that. However if i do, there is no alternative to make users from an administrator perspective.
Please allow a 'create user' option from the user management.

@pgigis could you take a look at this? Essentially we need a simple form for an admin to create a new user (and check if we disable the registration feature and instead redirect the user to a force-password-change form when the user connects for the first time). So workflow:

admin creates new user and sets a new password
user connect with the password and is redirected to a force passwd change form
user updates the password (which is from now on known only to him)
We probably do not need the user reg form with this.

@slowr do you also agree with this approach? We also support LDAP and radius currently, so this admin-based perspective will complement nicely the existing mechanisms.

@pgigis could you take a look at this? Essentially we need a simple form for an admin to create a new user (and check if we disable the registration feature and instead redirect the user to a force-password-change form when the user connects for the first time). So workflow:

admin creates new user and sets a new password
user connect with the password and is redirected to a force passwd change form
user updates the password (which is from now on known only to him)
We probably do not need the user reg form with this.

@slowr do you also agree with this approach? We also support LDAP and radius currently, so this admin-based perspective will complement nicely the existing mechanisms.

Sounds like the best approach to me. 👍

Since we are heavily refactoring the frontend with react.js, this issue will be moved in another milestone after 1.6.0.

Addressed in new frontend (to be released): https://github.com/FORTH-ICS-INSPIRE/artemis-web


SpecifierSet has no attribute split

Running the tests on cheroot, I'm seeing this error:
  Installing backend dependencies: finished with status 'done'
    Preparing wheel metadata: started
    Preparing wheel metadata: finished with status 'error'
    ERROR: Command errored out with exit status 1:
     command: /Users/jaraco/code/public/cherrypy/cheroot/.tox/python/bin/python /Users/jaraco/code/public/cherrypy/cheroot/.tox/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/tmpkxgh82j6
         cwd: /Users/jaraco/code/public/cherrypy/cheroot
    Complete output (28 lines):
    Traceback (most recent call last):
      File "/Users/jaraco/code/public/cherrypy/cheroot/.tox/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 207, in <module>
        main()
      File "/Users/jaraco/code/public/cherrypy/cheroot/.tox/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 197, in main
        json_out['return_val'] = hook(**hook_input['kwargs'])
      File "/Users/jaraco/code/public/cherrypy/cheroot/.tox/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 69, in prepare_metadata_for_build_wheel
        return hook(metadata_directory, config_settings)
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 156, in prepare_metadata_for_build_wheel
        self.run_setup()
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 142, in run_setup
        exec(compile(code, __file__, 'exec'), locals())
      File "setup.py", line 138, in <module>
        __name__ == '__main__' and setuptools.setup(**setup_params)
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/__init__.py", line 145, in setup
        return distutils.core.setup(**attrs)
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/distutils/core.py", line 108, in setup
        _setup_distribution = dist = klass(attrs)
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 446, in __init__
        _Distribution.__init__(self, {
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/distutils/dist.py", line 292, in __init__
        self.finalize_options()
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 735, in finalize_options
        ep.load()(self, ep.name, value)
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 291, in check_specifier
        packaging.specifiers.SpecifierSet(value)
      File "/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-build-env-2krlo7y7/overlay/lib/python3.8/site-packages/setuptools/_vendor/packaging/specifiers.py", line 594, in __init__
        specifiers = [s.strip() for s in specifiers.split(",") if s.strip()]
    AttributeError: 'SpecifierSet' object has no attribute 'split'

I suspect this issue is brought about by #1847, and what's happening is the declarative config python_requires is transforming the value and later the value is parsed again. This code illustrates how the same error is elicited by a double construction:
>>> packaging.specifiers.SpecifierSet(packaging.specifiers.SpecifierSet('>=2.7,!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/jaraco/code/public/pypa/setuptools/setuptools/_vendor/packaging/specifiers.py", line 594, in __init__
    specifiers = [s.strip() for s in specifiers.split(",") if s.strip()]
AttributeError: 'SpecifierSet' object has no attribute 'split'

But wait - if 'check_specifier' is called when a declarative 'python_requires' is indicated, then how is it that invalid specifiers were allowed in the bug (#1787)?

Oh, nevermind. It looks like cheroot is doing something weird in its setup.py.

Please reopen this, we need a workaround as it break lots and lots of projects.

@ssbarnea it only breaks hacks

Indeed, I'm extremely reluctant to support projects that wish to read declarative config on their own. I suggest if you wish to continue to read declarative config and pass it into setup(), then you'll need to support that interface and (conditionally) normalize any contents before passing into setup(). Maybe it makes sense for setuptools to support accepting a SpecifierSet for python_requires. I'd probably accept a patch for that, though I'd say it is something of a feature request.


Quarantine frequent failures

This PR quarantines many of the test groups that have been frequently failing,
so that we can stabilize the master branch. With the master branch stable, we
can assign quarantined tests to individuals to further inspect and make
progress on re-establishing test coverage.
From there we can establish which category the test failures fall under:

Genuine bug. It may be that the test failure is due to a genuine bug in
Cilium. We can then determine the severity and consider whether it should
block the upcoming release or be treated as a standard bug report.
Fixable. The test can be made reliable with relatively few changes. In this
case, we can fix and re-enables the test, and close the GitHub issue as
“fixed”. Note that once the fix is merged, we may want to keep the test in
quarantine for some time longer to ensure that the fix will properly resolve
the flakiness.
No longer needed. If the functionality covered by the test is covered by
other existing tests, then the test can be deleted completely and the GitHub
issue closed as “won’t fix”.
Important, but not fixable. If the functionality covered by the test is
important and not covered by other tests, then we can leave the corresponding
GitHub issue open and come up with a plan to address the test failure during
the next development cycle.

(Props to @twpayne who wrote up the initial proposal of the above
classification, which I've made minor tweaks to here)
This PR is split into the following commits, based primarily on cross-referencing the recently updated Cilium Github
Issues against the CI dashboard and quarantining the most frequent failures.

contrib: Add quarantine commit creation script

Rough script to help quarantine tests by check name, works in a fair number
of cases but the results do need to be checked to determine whether the
quarantine selected the correct test.

test/Services: Quarantine 'Checks service on same node'

Example failures: #17919
24 failures recorded on master since Nov 10

test/Services: Quarantine 'Tests with direct routing'

Example failures: #18014 (IPv6), #17895 (IPv6), #13839, #12690
46 (k8s-1.21) + 22 (k8s-1.22) failures recorded on master since Nov 10

test/Services: Quarantine 'Checks graceful termination'

Example failures: #18045
42 (k8s-1.21) + 39 (k8s-1.22) failures recorded on master since Nov 10

test/Services: Quarantine 'IPv6 masquerading across K8s nodes'

Example failures: #17942
20 failures recorded on master since Nov 10

test/DatapathConfiguration: Quarantine 'Encapsulation'

Example failures: #17545, #17353, #17069 (low hanging fruit)
64 failures recorded on master since Nov 10 across four tests

The above tests were selected for quarantine primarily based on exceeding a
threshold on failure frequency over the past couple of weeks and based on
community members actively engaging with the corresponding GitHub issues in the
past week. It is not comprehensive, CI dashboard for instance shows a long tail
of less frequent failures. However, this will hopefully help to stabilize CI
for the immediate term and provide a focus for us to evaluate the stability of
the branch in the short term, and start to point towards ways to improve the
codebase in the medium term.

/test

I suppose we can take the "Graceful termination" test off the list. With fixes from Martynas (kube-dns pods connectivity issue) and myself, the test looks to be in a good shape. I triggered a few runs locally and in Jenkins.

IPv6 masquerading across K8s nodes might potentially be addressed via  https://github.com/cilium/cilium/issues/17942#issuecomment-979324634 . @qmonnet did you take a closer look?

For tests that we believe to have fixed already, I suggest that we run the entire CI with the test re-enabled 10x. Ideally rebased on top of this PR so that it should result in 10 green runs.

Re https://github.com/cilium/cilium/issues/18014, we are still on it (trying to reproduce it locally, but running into multiple other flakes).

IPv6 masquerading across K8s nodes might potentially be addressed via #17942 (comment) . @qmonnet did you take a closer look?

No not yet, and just to be clear I have no idea if it will fix this flake. It's not the goal of that PR - I just stated that the PR will touch the failing test, so the flaking behaviour may (or may not) disappear in the process.

/mlh new-flake Cilium-PR-K8s-1.22-kernel-4.19

/mlh new-flake Cilium-PR-K8s-1.16-net-next

I've added some updates on the failures reported by this CI run. If they fail again soon then we should also quarantine these ones. I've also updated #18073 with some pointers about what's going wrong there.
The Travis failure appears to be a temporary issue with the upstream llvm.org infrastructure, details here: #18074.
Merging this PR to improve state of the tree. We can follow up with additional quarantining PRs for other frequently failing CI tests as they come up.
As for those tests which are being improved right now, I suggest that we merge the fixes and then observe how reliable those fixes are in the quarantine, then once we've had ten or so successful runs for those tests we move them back out of quarantine.


Added views

Blog app - Views :eye: :eye:
In this project I have added the views associated with the Models and Controllers already created in the Blog App
Highlights
Implement the design from the sneak peek wireframes
Use methods that I have created in the Blog App - processing data in models.
Cheers and happy reviewing!

Thank you @DeliceLydia for approving my project :pray:


cannot import name 'nvcc' from 'tvm.contrib' (unknown location)

Hello ,when i try to use longformer at the 'tvm' mode to run with cuda kernel, but there is a nvcc  error.
Is it necessary to compile the CUDA Kernel to use LongFormer on the GPU ，thank you

May i need to install tvm from the source code and change the longformer's tvm package to another name?

hi, i met the same error, have you solved it?

hi, i met the same error, have you solved it?

In my own case, i installed longformer from pip, but i copyed the diagonaled_mm_tvm.py to my project dir and use: 'from diagonaled_mm_tvm import diagonaled_mm' in my own python file, then the error occored.  After i change it to "from longformer.diagonaled_mm_tvm import diagonaled_mm", everything is fine.

hi, i met the same error, have you solved it?


AI Builder SDK not able to connect to powerapps env

Login using PowerApps credentials and register a model with AI Builder
from aibuilder.core.environment import Environment
from aibuilder.models.constants import ModelClientResponseStatus
env = Environment.get(environment_name=aib_environment)
response = env.register_model(model_name=aib_model_name, connection=service, override=True)
if response != ModelClientResponseStatus.success:
raise Exception('Model registration failed')
print(f"Registered AI Builder model {aib_model_name}")

@akshatakalp We do not handle support issues here. Try contact MS Support or post your question in the forums.
If you have a question about one of our code samples, please let us know which sample.


Allow target-only ES decorators

This allows users to write ES decorators that contain only a target parameter.
Fixes #53208

Yeah, I was confused by this too--in general, function types with fewer parameters are assignable to ones with more (there's even a FAQ entry explaining this), so having a minimum-parameter-count check in the first place made no sense to me and I'd expect the check to just be, is it assignable to the correct function type

Is the requirement for at least one parameter (target) just a sanity check? It seems inconsistent with our function assignability rules.

IIRC, this is a sanity check that @DanielRosenwasser added many years ago to catch a failure to invoke a decorator factory that takes no arguments. See isPotentiallyUncalledDecorator.

Yeah, I was confused by this too--in general, function types with fewer parameters are assignable to ones with more (there's even a FAQ entry explaining this), so having a minimum-parameter-count check in the first place made no sense to me and I'd expect the check to just be, is it assignable to the correct function type

We don't type check the decorator as if it were a callback, we type check it as if it were a direct invocation by the runtime. This is a very narrow fix to address a specific case within decorators. Changing the mechanics to use assignability would be a fairly extensive rewrite.


Modify grading policy

Previously the grading policy was:
collection grade = (# points earned) / max( # submitted questions, Q)

This PR introduces a collection model field (type bool, default=True), "correctness_matters" and modifies the grading policy such that
If collection.correctness_matters:
    grade = (# points earned) / max( # submitted questions, Q )  # same as previous policy
else:
    grade = (# submitted questions) / max( # submitted questions, Q)

Travis CI seems to be complaining about some style issues, unrelated to changes in this PR (not sure why now as opposed to before - won't fix in this PR)


Canno't install on D10.0

Describe the bug
during compiling dpk got:
[dcc32 Fatal Error] XSuperJSON.pas(1): F2084 Internal Error: AV0D798E88-R00000014-0
Screenshots

Hi, this plug-in just supports from 10.1 Berlin to later versions at this stage.
It's mentioned (here) in ReadMe.
By the way, It's a bug in the Seattle version which is really buggy, it's looking for XSuperJSON beside the dpr but it is present in the Utils folder!


relative paths going outside of hosts folder don't work with mkHost

problem
currently, if you try to do something like this in the default.nix of your hosts folder:
{
  imports = [
    ../foo/bar.nix
  ];
}

it won't work due the host folder being in it's own derivation.
workaround
you can use the self input to set absolute paths like so:
{
  imports = [
    "${self}/foo/bar.nix"
  ];
}

not an issue after e0929cdc52e96393d734ddc669cb2e7900eb581a


News Tab

[ ] Archive we're hiring announcement
[x] Include announcement about Shaash coming to lab
[x] American Heart Association conference attendance - https://www.ahajournals.org/doi/10.1161/circ.150.suppl_1.4116410
[x] https://www.nature.com/articles/s41569-024-01105-y comment in Nature
[x] Develop a feed from X posts to news

Question:

What do you mean by archive the hiring post?
The thumbnail image ratio is very awkward. Should I increase its width a little bit?

Need to fit images to size


add GOENV_APPEND_GOPATH and GOENV_PREPEND_GOPATH options

I'm open to other implementations and wording, but I'd like to find a way to get something like this out soon. Let me know what you think. Thanks!
fixes #147

Awesome! I'll try to see if I can get around to addressing the failing tests soon...

@syndbg Alright, I made a bit of a change but I think you'll like it. Ready for re-review.

@syndbg Alright, I made a bit of a change but I think you'll like it. Ready for re-review.

@syndbg Alright, I made a bit of a change but I think you'll like it. Ready for re-review.


NameError: uninitialized constant AWS::S3::Base

Good afternoon,
require 'aws/s3'
=> true
AWS::S3::Base.establish_connection!(
  :access_key_id     => 'abc',
  :secret_access_key => '123'
)
NameError: uninitialized constant AWS::S3::Base

This happened to me just 5 minutes ago. It would be helpful if you updated the instructions to use either of the solutions listed in this SO answer, or state what should work instead. Using s3sh failed for me too, but it wouldn't be the only route to using the library anyway.
Kind regards,
yb

I had the same issue. I removed aws-sdk gem and it started to work again.
Looks like aws-s3 and aws-sdk gems can't work together.


in ref callback, ref is someitimes not part of the DOM yet

Not sure if this is supposed to work this way or not, but it seemed odd to have the ref only work sometimes.
I've got a div with a ref callback, and using that ref I wanted to get it to initialize swipejs which requires a width from the ref's children. However, I found that the ref is sometimes not yet part of the DOM. So when it tries to access the width on the page within the ref callback sometimes the width is zero, and sometimes it is my expected width of ~1000px. I dug in, and saw the width being 0, document.querySelectorAll('.swipe') being [], and ref.parentNode being null during the times it wasn't working. Other times those all returned expected results of the width, the ref, and the parent.
Didn't have time to dig in too deep, but I did find a workaround by just grabbing the ref in the callback, and then using that ref in the componentDidMount lifecycle hook.
Here's my code with the working workaround
import { h, Component } from 'preact'
import SwipeJS from 'swipejs'

class Example extends Component {
  constructor (props) {
    super(props)
    this.state = {
      activeIndex: 0
    }
  }

  componentDidMount() {
    const ref = this.swipeRef
    if (ref) {
      this.swipe = this.swipe || new SwipeJS(ref)
    }
  }

  componentWillUnmount () {
    if (this.swipe) {
      this.swipe.kill()
      this.swipe = false
    }
  }

  initializeSwipe (ref) {
    if (!ref) {
      // ref is called on removal with null element
      return
    }
    this.swipeRef = ref
  }

  render (props, state) {
    return (

 this.initializeSwipe(ref)}>

    )
  }
}

export default Example

Hi there - preact doesn't guarantee refs are called after parent elements are mounted. Instead (and in general in React codebase), I recommend instead using the ref callback to store a reference to the created element, then using the componentDidMount() lifecycle event to initialize your swipe system.

Hi thanks, yeah that is what I ended up doing. I couldn't find the documentation in react on how exactly that was supposed to work. Glad to know that's expected behavior.

Great! Think we should close out this issue then?

@developit Just running into an issue which is related to ref callback I think when trying out blueprintjs EditableText component with Preact. I need to investigate some more, but can you clarify whether Preact follows the same callback pattern as React here i.e.

The ref attribute takes a callback function, and the callback will be executed immediately after
the component is mounted or unmounted
https://facebook.github.io/react/docs/refs-and-the-dom.html

Asking here as may be related to this issue. Sorry if you answered above, I wasn't totally clear on the answer.

Currently Preact does not defer ref callback invocation like it does componentDidMount(). If that breaks enough things then maybe we'll need to look into doing it.  I've never run into anything until this issue, but maybe it was a result of people not realizing there was a difference there.

Great thanks for clarifying! I've not come across any issues around this before either, but for reference here's one example of where it seems breaking. https://github.com/palantir/blueprint/blob/master/packages/core/src/components/editable-text/editableText.tsx#L115
With Preact focus is not given to the input, I assume because it's not attached.
Also with Preact, that ref callback seems to be getting called every time I type a char in the input, I've not had time to debug that one yet.

This stumped me for a while too. Below is an example of some code where Preact requires I refactor it to ensure the event listeners are correctly added.
onReference = (iframe) => {
	if (this.viewport) {
		this.viewport.removeEventListener('hashchange', this.onHashChange);
	}
	this.viewport = iframe ? iframe.contentWindow : undefined;
	if (this.viewport) {
		this.viewport.addEventListener('hashchange', this.onHashChange, false);
	}
};

render() {
	return ;
}

I'm having the same issue. I was assuming on having the ref callback triggered after mount/unmount.

Hmm - @landabaso that doesn't seem any different from React's behavior. ref is invoked when the element is added to the DOM, not the virtual DOM.  If a hoc defers rendering of the DOM element, the ref is deferred as well.

Yes, the ref is deferred. That's works Ok. But when the callback is triggered, clonedChildren has not been attached to the DOM yet.
I need to access the .parentNode of the clonedChildren.
I can access .parentNode of the element in this.onChildrenIsMounted when using React.
It's not the case with Preact.

It's something I'm open to, just haven't had time to explore. Technically, refs should not be used to pierce component boundaries - that is what's causing the issue here - so the number of times this has come up is only twice. Happy to explore options though, just it's not something I've ever run into myself.

I admit it's a strange situation.
I'd usually pass a callback to the HoC. In this case I cannot pass a callback to the HoC that renders the clonedChildren because the HoC is a 3rd party lib :-/

ahh yeah. the other case I saw for this was in a third party lib as well.

I guess this will happen more often as more users try to use preact.
There's a workaround. I can defer the call to dialogChildrenRef using setTimeout(..., 0). It's a hack, but not super-terrible I guess...
So far I only had 3 issues porting my App to preact (https://github.com/developit/preact/issues/551, this one here, and another one I'll be investigating later).
Thanks for sharing this lib!

Nice! I was going to suggest the setTimeout hack, but I didn't know if it would fix your usecase. Glad there's at least a workaround for now.  We'll get #551 solved, that was just an oversight on my part.

I think this is one of the big reasons I'm unable to switch a big application over to preact is the fact that refs aren't a 1:1 with react.
I've been building a little react component over here: https://github.com/hanford/react-drag-drawer and lines like this break. In react, this.drawer (a ref) will always be defined, but they're always not defined in preact.
Any workarounds or ideas?

I would definitely avoid invoking DOM side effects from within render like this - instead, use componentDidUpdate() / componentDidMount():
componentDidMount() {
  if (this.state.open) {
   this.attachListeners();
  }
}

componentDidUpdate(prevProps, prevState) {
  if (this.state.open && !prevState.open) {
    this.attachListeners();
  }
}

Ideally, you want render() to be a pure VDOM pipeline, it should never trigger any external effects.

Great advice! Thanks again @developit

Hi, I think I have similar issue but I didn't fully understand the conversation above.
I have this test code:
class Test extends Component {
  setRef = (el) => {
    console.log("Setting ref to " + el);
    //if (!el) return;
    this.el = el;
  }
  showA = () => {
    this.setState({show: true});
  }
  closeA = () => {
    this.setState({show: false});
  }
  showEl = () => {
    console.log(this.el);
  }
  updateEl = () => {
    this.el.textContent = new Date().getTime().toString();
  }
  renderA() {
    const { show } = this.state;
    if (!show) return null;
    return (

        A <button onClick={this.closeA}>Close A</button>

    );
  }
  render() {
    return (

        {this.renderA()}

        <button onClick={this.showA}>Show A</button>
        <button onClick={this.showEl}>Show el</button>
        <button onClick={this.updateEl}>Update el</button>

    );
  }
}

Reproducing steps: click Show A, click Close A, click Update el.
Console output:
Setting ref to [object HTMLDivElement]
Setting ref to null
Setting ref to [object HTMLDivElement]
Setting ref to [object HTMLDivElement]
Setting ref to null

So after closing A element my ref callback is being called twice and second time with null, so I can't use DOM element anymore. If I uncomment the if line then everything seems to be working though.
Could you please explain this behavior? What is best way to store correct reference to DOM element in Preact?

@Kagami you're missing a key prop on the conditionally rendered
 in renderA().   Without a key or a component reference, that
 and the
 with the ref are being swapped.  In VDOM, the last element of a given type is always removed, unless keys are used to indicate which needs to be removed.
// render after clicking "Show A":

A <button onClick={this.closeA}>Close A</button>

  <button onClick={this.showA}>Show A</button>
  <button onClick={this.showEl}>Show el</button>
  <button onClick={this.updateEl}>Update el</button>

// render after clicking "Close A":

  <button onClick={this.showA}>Show A</button>
  <button onClick={this.showEl}>Show el</button>
  <button onClick={this.updateEl}>Update el</button>

Since there's nothing to indicate which div is which, it's removing the second one instead of the first.  Making <RenderA> a component or assigning
 to the div returned from renderA() will fix the issue.
Cheers!

We completely rewrote the ref handling in Preact X and fixed this :tada: An alpha release is already available on npm :100:

import React from 'react';
import Menu from '../icons/Menu.png';
export default class IconButton extends React.Component{
constructor(){
super();
    this.icon = null;
    this.login = null;

    this.handleMouseOver = this.handleMouseOver.bind(this);
}

handleMouseOver(toggle){
    console.log("handleMouseOver Called");

    let background = "#034d79";
    let foreground = "white";
    if(toggle === true){
        background = "white";
        foreground = "#034d79";
    }
    console.log("icon: "+this.icon);
    if(this.icon != null){
        this.icon.setAttribute("background-color", background);
        this.icon.setAttribute("color", foreground);
    }
    if(this.login != null){
        this.login.setAttribute("background-color", background);
        this.login.setAttribute("color", foreground);
    }

}

render(){
    return (

             {this.icon = node;}} onMouseEnter={this.handleMouseOver(true)} onMouseLeave={this.handleMouseOver(false)} className="login-icon">
            <button name="login" align="right" ref={node => {this.login = node;}} onMouseEnter={this.handleMouseOver(true)} onMouseLeave={this.handleMouseOver(false)} className="login-button">Login</button>

    );
}

}
The ref holder variable shows null! ? Could someone help me understand why this null error is?
Can I set the attributes like this?

@Kamarudeen-k you are calling your mouse handler functions in render() when you should only be passing references to them.
-<foo onClick={this.foo(true)}>
+<foo onClick={this.foo.bind(this,true)}>

Here is the corrected code:
        return (

                 {this.icon = node;}} onMouseEnter={this.handleMouseOver(true)} onMouseLeave={this.handleMouseOver(false)} className="login-icon">
                <button name="login" align="right" ref={node => {this.login = node;}} onMouseEnter={thithis.handleMouseOver.bind(this,true)} onMouseLeave={ththis.handleMouseOver.bind(this,false)} className="login-button">Login</button>

        );

Thank you for your quick response. yes, It works with its reference


TypeScript: JSDoc tooltips are shared between types and values, but not functions

Issue Type: Bug

Create a TypeScript file.
Create a type alias with some name, and write a JSDoc comment for it.

For types and functions:

Create a function with the same name, write a different JSDoc comment.
Hover over the type name. You will see the function’s comment, followed by the type’s comment.
Hover over the function. You will only see the function’s comment.

For types and values:

Create a value identifier with the same name, write a different JSDoc comment.
Hover over the type name. You will see the type’s comment, followed by the value’s comment.
Hover over the value identifier. You will see the type’s comment, followed by the value’s comment.

VS Code version: Code - Insiders 1.56.0-insider (0123d26aaa393bccf99f31f1eac07df6c9e218ce, 2021-04-29T05:12:38.091Z)
OS version: Linux x64 5.11.0-7614-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (8 x 2300)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
7.64GB (0.18GB free)

Process Argv
--no-sandbox --unity-launch --crash-reporter-id dbbd25fe-3f4e-426a-9c89-45e060834124

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

Extensions: none

Please share example code (as text) that demonstrates the issue

@mjbvz I have!


'start the workshop' hyperlink generates 404

Describe the bug
When going through the Access AWS instance portion of exercise, there is a 'start the workshop' hyperlink near bottom and clicking on this link leads to a 404.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on 'start the workshop'. (URL is:  https://signalfx.github.io/observability-workshop/v4.8/imt/gdi/k3s/)
See error -- 404

Fixed in https://github.com/signalfx/observability-workshop/commit/c3012decdfac492eb3684fdd8439f9fd8463c86d


ModuleNotFoundError: No module named 'featex'

When I try to import eegtools,it turns out that"ModuleNotFoundError: No module named 'featex'",but featex.py is exactly where it is. It's strange, why?

I don't know. Are you using Python 3? Eegtools used to work fine with Python 2, but requires non-trivial work to update it to Python 3.

2, but requires non-trivial work to update it to Python 3.

Thanks, It is exactly the python version problem, and I have solved the problem by using Python 2.


feat: add alpha parameter to lasso_regression

Closes #163.
Summary of Changes
Add alpha parameter to lasso regression

🦙 MegaLinter status: ❌ ERROR

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
2
0
0
0.56s

✅ PYTHON
mypy
2

0
1.57s

❌ PYTHON
ruff
2
2
4
0.04s

✅ REPOSITORY
git_diff
yes

no
0.02s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by

Note that pytest isn't catching the warning correctly.

:tada: This PR is included in version 0.12.0 :tada:
The release is available on:

v0.12.0
GitHub release

Your semantic-release bot :package::rocket:


Retrieve endpoint/15

Since tests needs elasticsearch and webapi running. ElasticActorTest is moved to it(IntegrationTest) folder. It can be run using it:test in sbt.


Add protection to our BinaryOperators to prevent objects growing too large

Objects like FreqMap should only be used with a small number of keys, otherwise we could end up hitting limits in accumulo/hbase for the size of the rows.
In our BinaryOperators (like FreqMapAggregator), before merging the objects we should check whether the result will be too big. The aggregator should be configured with the key size limit. It should also have a flag to control what to do in the case that the objects cannot be safely merged - either throw an exception or log a warning and truncate the objects. If an exception is thrown then this will have severe consequences for Accumulo's tablet servers (similarly in HBase).
This will require changes to the binary operators in Koryphe too.

Are the row size limits defined anywhere for the stores? Have just set it to an arbitrary integer for now, but that can be easily changed.
Also, is this protection to be implemented for every single subclass of KorypheBinaryOperator? I've looked through most of them, and they seem like they either won't need it, or implementing the truncation would be non-trivial.


Make tests work on any machine

This PR

Make tests work on any machine using gpts library
Moves development dependencies into optional dependencies

If you want to reuse your existing model file, run a quick
mkdir -pv ~/.cache/gpts/mistral/
mv -v ~/pkg/mistral/mistral-7b-instruct.gguf ~/.cache/gpts/mistral/mistral-7b-instruct-v0.2.Q8_0.gguf

Heck yeah!!!! Accepted.