Superfly NVSwitch bringup

This issue tracks the bring-up of NVSwitch on the Superfly Platform and Infrastructure.
cc @draper7 @tqbf @mrkurt

Hi gang,
Using debian 11 bullseye 5.10-23 AMD kernel results in a segfault during SEV setup.
Running with older kernels that may have bugs fixed upstream burns my flow. I installed Debian's 6.1-9 kernel.
sdake@nice:~$ hostnamectl
   Static hostname: nice
         Icon name: computer-server
           Chassis: server
        Machine ID: d2c1a8d880ec4ce3b7e16d718ba2bd34
           Boot ID: d52758ded0d34bbe863a1afbc74806f2
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.1.0-9-amd64
      Architecture: x86-64

It appears older kernels cannot detect SEV settings in the UEFI firmware. the 6.1 kernel displays this:
ccp 0000:32:00.1: SEV: memory encryption not enabled by BIOS

Install kernel-6.1.0-0 on Debian 11.
The guide is missing two critical steps required to build Nvidia kernel modules:
Add this to the pin list in /etc/apt/preferences
Package: linux-headers-6.1
Pin:release a=unstable
Pin-Priority: 1000

And install the kernel headers:
sudo apt install linux-headers-6.1.0-0.deb11.7-amd64

taking a look at the dmesg differences between a related platform that works, versus one the one under test:
sdake@beast-06 ~> sudo dmesg | cut -c16- > /tmp/dmesg-aw.txt
sdake@nice:~$ sudo dmesg | cut -c16- > /tmp/dmesg-fly.txt

Examining the diff with meld brew install meld:
The functional system displays:
AMD-Vi: Using global IVHD EFR:0x59f77efa2094ade, EFR2:0x0

While the NVSwitch system does not. This led to the following content:
PCI Passthrough walkthrough
Interesting finds along the way:
Optimus GPU manager
Forum for GPU passthrough BAR errors
Documentation change to korg.

Kernel Lore

I paused the comparison of the two kernel dmesg logs. It is evident that the Broadcom PEX88048 is not enumerating properly in Linux. None of the devices behind this bus type enumerate at all!

After more investigation, I found the PEX switches are PEX88096.
As part of the process of bringup, I was attempting to target Linux's PCI enumeration to function correctly.
I modified the file:
/etc/default/grub.d/aw.cfg

And set the boot flag pci=realloc,nocrs,nommconf. This seems to have blocked the bootup. I don't have console access.
Would someone mind modifying the file or removing it, and running sudo update-grub that has console access?
Thank you,
-steve

After @draper7 modified the dropin grub file, I tried a variety of the following. Unfortunately, the PCI bus does not enumerate properly.
Next steps:

try pci=realloc with pci=assign-busses,pci_scan_all,nocrs
try disabling ACPI
finish reading the kernel/drivers/pci source code.
Map the bus as it comes from an early PCI dump (as configured by BIOS).

it is viable and possible that a UEFI setting is misconfigured. I am running the latest 6.1 kernel, and find it unlikely it is the cause, although I will take a look through the default kernel config.
It is very clear the BroadCom PEX devices are failing to map.
I am not sure WHY they are failing to map. This is why I need the early pci dump.
I do think it would be helpful to accept other suggestions, as always.
sdake@nice:~$ sudo cat /etc/default/grub.d/aw.cfg
sudo: unable to resolve host nice: Name or service not known
GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX modprobe.blacklist=nouveau biosdevname=0 net.ifnames=1 cgroup_enable=memory swapaccount=1 pci=assign-busses,pcie_scan_all,nocrs"

sdake@nice:~$ sudo dmesg | grep pci | grep failed
sudo: unable to resolve host nice: Name or service not known
[    0.769730] pci 0000:02:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769733] pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769740] pci 0000:02:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769742] pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769751] pci 0000:04:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769754] pci 0000:04:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769760] pci 0000:04:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769762] pci 0000:04:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769838] pci 0000:0a:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769841] pci 0000:0a:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769843] pci 0000:0b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769847] pci 0000:0b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769887] pci 0000:0e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769890] pci 0000:0e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769892] pci 0000:0f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769895] pci 0000:0f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770141] pci 0000:42:04.0: BAR 15: failed to assign [mem size 0x00900000 64bit pref]
[    0.770144] pci 0000:42:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770146] pci 0000:42:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770152] pci 0000:42:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770154] pci 0000:42:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770156] pci 0000:42:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770201] pci 0000:47:00.0: BAR 15: failed to assign [mem size 0x00900000 64bit pref]
[    0.770204] pci 0000:47:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770207] pci 0000:48:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770209] pci 0000:48:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770210] pci 0000:48:18.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770212] pci 0000:48:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770216] pci 0000:48:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770218] pci 0000:48:18.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770219] pci 0000:48:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770221] pci 0000:48:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770288] pci 0000:4e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770290] pci 0000:4e:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770292] pci 0000:4e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770294] pci 0000:4e:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770295] pci 0000:4f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770297] pci 0000:4f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770299] pci 0000:4f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770301] pci 0000:4f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770597] pci 0000:90:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.770600] pci 0000:90:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.770601] pci 0000:91:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.770603] pci 0000:91:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.770606] pci 0000:92:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770608] pci 0000:92:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770610] pci 0000:92:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770612] pci 0000:92:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770614] pci 0000:92:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770616] pci 0000:92:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770618] pci 0000:92:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770620] pci 0000:92:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770622] pci 0000:92:04.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770624] pci 0000:92:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770625] pci 0000:92:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770627] pci 0000:92:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770628] pci 0000:92:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770630] pci 0000:92:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770632] pci 0000:93:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770633] pci 0000:93:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770637] pci 0000:94:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770640] pci 0000:94:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770642] pci 0000:94:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770644] pci 0000:94:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770646] pci 0000:94:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770647] pci 0000:94:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770649] pci 0000:94:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770650] pci 0000:94:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770652] pci 0000:94:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770654] pci 0000:94:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770656] pci 0000:94:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770658] pci 0000:94:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770660] pci 0000:94:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770662] pci 0000:94:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770663] pci 0000:94:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770665] pci 0000:94:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770667] pci 0000:94:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770668] pci 0000:94:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770743] pci 0000:9a:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770744] pci 0000:9a:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770746] pci 0000:9a:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770748] pci 0000:9a:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770749] pci 0000:9a:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770751] pci 0000:9a:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770753] pci 0000:9b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770754] pci 0000:9b:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770756] pci 0000:9b:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770758] pci 0000:9b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770759] pci 0000:9b:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770761] pci 0000:9b:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770801] pci 0000:9e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770803] pci 0000:9e:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770804] pci 0000:9e:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770806] pci 0000:9e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770807] pci 0000:9e:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770809] pci 0000:9e:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770811] pci 0000:9f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770813] pci 0000:9f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770814] pci 0000:9f:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770816] pci 0000:9f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770817] pci 0000:9f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770819] pci 0000:9f:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771036] pci 0000:d0:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.771038] pci 0000:d0:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.771040] pci 0000:d1:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.771041] pci 0000:d1:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.771043] pci 0000:d2:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771045] pci 0000:d2:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771047] pci 0000:d2:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771049] pci 0000:d2:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771051] pci 0000:d2:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771053] pci 0000:d2:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771054] pci 0000:d2:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771056] pci 0000:d2:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771058] pci 0000:d2:04.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771059] pci 0000:d2:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771061] pci 0000:d2:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771063] pci 0000:d2:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771065] pci 0000:d2:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771066] pci 0000:d2:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771068] pci 0000:d3:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771069] pci 0000:d3:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771072] pci 0000:d4:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771074] pci 0000:d4:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771076] pci 0000:d4:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771078] pci 0000:d4:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771080] pci 0000:d4:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771081] pci 0000:d4:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771082] pci 0000:d4:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771084] pci 0000:d4:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771086] pci 0000:d4:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771088] pci 0000:d4:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771089] pci 0000:d4:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771090] pci 0000:d4:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771092] pci 0000:d4:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771094] pci 0000:d4:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771095] pci 0000:d4:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771097] pci 0000:d4:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771172] pci 0000:da:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771174] pci 0000:da:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771176] pci 0000:da:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771177] pci 0000:da:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771179] pci 0000:da:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771181] pci 0000:da:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771182] pci 0000:db:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771184] pci 0000:db:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771185] pci 0000:db:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771187] pci 0000:db:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771189] pci 0000:db:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771190] pci 0000:db:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771230] pci 0000:de:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771231] pci 0000:de:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771233] pci 0000:de:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771235] pci 0000:de:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771236] pci 0000:de:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771238] pci 0000:de:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771240] pci 0000:df:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771241] pci 0000:df:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771243] pci 0000:df:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771244] pci 0000:df:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771246] pci 0000:df:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771247] pci 0000:df:10.0: BAR 13: failed to assign [io  size 0x1000]

Gigabyte Manual

Gigabyte Block Diagram

After @draper7 modified the dropin grub file, I tried a variety of the following. Unfortunately, the PCI bus does not enumerate properly.
Next steps:

try pci=realloc with pci=assign-busses,pci_scan_all,nocrs
try disabling ACPI
finish reading the kernel/drivers/pci source code.
Map the bus as it comes from an early PCI dump (as configured by BIOS).

it is viable and possible that a UEFI setting is misconfigured. I am running the latest 6.1 kernel, and find it unlikely it is the cause, although I will take a look through the default kernel config.
It is very clear the BroadCom PEX devices are failing to map.
I am not sure WHY they are failing to map. This is why I need the early pci dump.
I do think it would be helpful to accept other suggestions, as always.
sdake@nice:~$ sudo cat /etc/default/grub.d/aw.cfg
sudo: unable to resolve host nice: Name or service not known
GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX modprobe.blacklist=nouveau biosdevname=0 net.ifnames=1 cgroup_enable=memory swapaccount=1 pci=assign-busses,pcie_scan_all,nocrs"

sdake@nice:~$ sudo dmesg | grep pci | grep failed
sudo: unable to resolve host nice: Name or service not known
[    0.769730] pci 0000:02:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769733] pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769740] pci 0000:02:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769742] pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769751] pci 0000:04:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769754] pci 0000:04:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769760] pci 0000:04:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769762] pci 0000:04:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769838] pci 0000:0a:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769841] pci 0000:0a:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769843] pci 0000:0b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769847] pci 0000:0b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769887] pci 0000:0e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.769890] pci 0000:0e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.769892] pci 0000:0f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.769895] pci 0000:0f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770141] pci 0000:42:04.0: BAR 15: failed to assign [mem size 0x00900000 64bit pref]
[    0.770144] pci 0000:42:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770146] pci 0000:42:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770152] pci 0000:42:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770154] pci 0000:42:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770156] pci 0000:42:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770201] pci 0000:47:00.0: BAR 15: failed to assign [mem size 0x00900000 64bit pref]
[    0.770204] pci 0000:47:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770207] pci 0000:48:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770209] pci 0000:48:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770210] pci 0000:48:18.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770212] pci 0000:48:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770216] pci 0000:48:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770218] pci 0000:48:18.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770219] pci 0000:48:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770221] pci 0000:48:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770288] pci 0000:4e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770290] pci 0000:4e:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770292] pci 0000:4e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770294] pci 0000:4e:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770295] pci 0000:4f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770297] pci 0000:4f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770299] pci 0000:4f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770301] pci 0000:4f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770597] pci 0000:90:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.770600] pci 0000:90:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.770601] pci 0000:91:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.770603] pci 0000:91:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.770606] pci 0000:92:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770608] pci 0000:92:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770610] pci 0000:92:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770612] pci 0000:92:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770614] pci 0000:92:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770616] pci 0000:92:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770618] pci 0000:92:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770620] pci 0000:92:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770622] pci 0000:92:04.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770624] pci 0000:92:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770625] pci 0000:92:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770627] pci 0000:92:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770628] pci 0000:92:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770630] pci 0000:92:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770632] pci 0000:93:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770633] pci 0000:93:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.770637] pci 0000:94:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770640] pci 0000:94:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770642] pci 0000:94:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770644] pci 0000:94:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770646] pci 0000:94:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770647] pci 0000:94:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770649] pci 0000:94:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770650] pci 0000:94:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770652] pci 0000:94:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770654] pci 0000:94:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770656] pci 0000:94:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770658] pci 0000:94:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770660] pci 0000:94:08.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770662] pci 0000:94:08.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770663] pci 0000:94:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770665] pci 0000:94:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770667] pci 0000:94:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770668] pci 0000:94:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770743] pci 0000:9a:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770744] pci 0000:9a:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770746] pci 0000:9a:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770748] pci 0000:9a:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770749] pci 0000:9a:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770751] pci 0000:9a:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770753] pci 0000:9b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770754] pci 0000:9b:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770756] pci 0000:9b:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770758] pci 0000:9b:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770759] pci 0000:9b:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770761] pci 0000:9b:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770801] pci 0000:9e:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.770803] pci 0000:9e:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.770804] pci 0000:9e:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770806] pci 0000:9e:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.770807] pci 0000:9e:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.770809] pci 0000:9e:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770811] pci 0000:9f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770813] pci 0000:9f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770814] pci 0000:9f:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.770816] pci 0000:9f:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.770817] pci 0000:9f:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.770819] pci 0000:9f:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771036] pci 0000:d0:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.771038] pci 0000:d0:03.1: BAR 13: failed to assign [io  size 0x6000]
[    0.771040] pci 0000:d1:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.771041] pci 0000:d1:00.0: BAR 13: failed to assign [io  size 0x6000]
[    0.771043] pci 0000:d2:04.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771045] pci 0000:d2:04.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771047] pci 0000:d2:08.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771049] pci 0000:d2:08.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771051] pci 0000:d2:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771053] pci 0000:d2:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771054] pci 0000:d2:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771056] pci 0000:d2:04.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771058] pci 0000:d2:04.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771059] pci 0000:d2:08.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771061] pci 0000:d2:08.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771063] pci 0000:d2:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771065] pci 0000:d2:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771066] pci 0000:d2:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771068] pci 0000:d3:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771069] pci 0000:d3:00.0: BAR 13: failed to assign [io  size 0x4000]
[    0.771072] pci 0000:d4:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771074] pci 0000:d4:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771076] pci 0000:d4:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771078] pci 0000:d4:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771080] pci 0000:d4:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771081] pci 0000:d4:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771082] pci 0000:d4:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771084] pci 0000:d4:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771086] pci 0000:d4:0c.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771088] pci 0000:d4:0c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771089] pci 0000:d4:0c.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771090] pci 0000:d4:08.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771092] pci 0000:d4:04.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771094] pci 0000:d4:04.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771095] pci 0000:d4:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771097] pci 0000:d4:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771172] pci 0000:da:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771174] pci 0000:da:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771176] pci 0000:da:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771177] pci 0000:da:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771179] pci 0000:da:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771181] pci 0000:da:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771182] pci 0000:db:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771184] pci 0000:db:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771185] pci 0000:db:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771187] pci 0000:db:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771189] pci 0000:db:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771190] pci 0000:db:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771230] pci 0000:de:00.0: BAR 14: failed to assign [mem size 0x00300000]
[    0.771231] pci 0000:de:00.0: BAR 15: failed to assign [mem size 0x00300000 64bit pref]
[    0.771233] pci 0000:de:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771235] pci 0000:de:00.0: BAR 14: failed to assign [mem size 0x00100000]
[    0.771236] pci 0000:de:00.0: BAR 15: failed to assign [mem size 0x00100000 64bit pref]
[    0.771238] pci 0000:de:00.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771240] pci 0000:df:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771241] pci 0000:df:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771243] pci 0000:df:10.0: BAR 13: failed to assign [io  size 0x1000]
[    0.771244] pci 0000:df:10.0: BAR 14: failed to assign [mem size 0x00200000]
[    0.771246] pci 0000:df:10.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.771247] pci 0000:df:10.0: BAR 13: failed to assign [io  size 0x1000]

The real problem with the above kernel command line is ACPI's bus configuration was not honored, so the PCI busses were "ignored". After reverting, same problem persists.

While waiting on a reboot, I found this to b e an interesting read: https://forums.developer.nvidia.com/t/a100-pcie-isnt-recognized-by-bios/198546/27

At this point, I have a few viable hypothesis for why PCI enumeration is failing.
Device naming. The interaction of LVM, MD Raid, and NVMe result in incorrect mapping when the Linux kernel attempts to redefine the PCI bus using pci=realloc=on.
Insufficient power. The specs for the Gigabyte server state three PSUs must be connected and a fourth serves as a hot spare. The system reports only two PSUs in use .
Carried Ubuntu kernel patches. An earlier exchange mentioned this metal I am using is in a known working state. The only real delta, then would be the kernel.
Different kernel config. As the 8 GPUs require a BAR that is 128Gig in size, coupled with other devices in the  system, the pci allocator in ACPI runs out of room, or lacks sufficient algorithms to build a correct device map.
Some other environment problem. The possibilities are endless.
In our last standup on June 26, we mentioned that I am not quite blocked, but close.
Our goal is to implement NVSwitch mode 1 to enable the 8 A100 servers to share the NVswitch in the platform to provide secure isolated SXM4.
To achieve this goal, we don't need Debian on the platform hardware. The solutions proposed during an independent blocker resolution brainstorm session:

ask Fly.io to reimage the system with ubuntu.
Rebuild the Debian kernel image with the same kernel config as used in Ubuntu.
Rebuild the Debian kernel image with the same kernel configuration and carried patches as in Ubuntu.

Our sprint planning estimate for Nvswitch is size=7 (roughly 3-5 days.) schedule for NVSwitch implementation compatible with SXM4.
I have burned 80-120 hours simply attempting to achieve a PCI bus enumeration that would present something to manage with the NVIDIA kernel driver.
Getting NVSwitch to work on Debian is not the goal and can be handled independently. Therefore;
I will try 2. If the system boots, but 2 does not operate according to expectations, 3 will be tried. If 3 does not operate according to expectations, We will ask Fly to reimage to Ubuntu.
I am not very keen on rebuilding a kernel, as I have no console. A failure here will short circuit to solution 1.
Thank you.
Steve
Therefore, for A100 is 3-5 days.
not sufficient when the pci bus is enumerated differently.
result in changing the bus topology in a way that some form of indexing that occurs within the OS to find one of these resources is failing when adding pci=realloc=on to the kernel command line.
It was also mentioned via email


[libsystemd] Build error on x64-linux

Package: libsystemd:x64-linux -> 254
Host Environment

Host: x64-linux
Compiler: GNU 11.4.0
vcpkg-tool version: 2023-11-16-4c1df40a3c5c5e18de299a99e9accb03c2a82e1e
vcpkg-scripts version: 45f6e57d3 2023-12-06 (26 小时前)

To Reproduce
./vcpkg install wxwidgets:x64-linux
Failure logs
-- Using cached systemd-systemd-v254.tar.gz.
-- Cleaning sources at Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source Path-to-vcpkg-install-dir/downloads/systemd-systemd-v254.tar.gz
-- Applying patch pkgconfig.patch
-- Using source at Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Configuring x64-linux-dbg
-- Configuring x64-linux-dbg done
-- Configuring x64-linux-rel
-- Configuring x64-linux-rel done
-- Building (x64-linux-dbg)...
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: Path-to-vcpkg-install-dir/downloads/tools/ninja/1.10.2-linux/ninja -C Path-to-vcpkg-install-dir/buildtrees/libsystemd/x64-linux-dbg libsystemd.a devel
    Working Directory: Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean
    See logs for more information:
      Path-to-vcpkg-install-dir/buildtrees/libsystemd/build-x64-linux-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_ninja.cmake:3 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_build_ninja.cmake:24 (z_vcpkg_build_ninja_build)
  ports/libsystemd/portfile.cmake:24 (vcpkg_build_ninja)
  scripts/ports.cmake:170 (include)

Path-to-vcpkg-install-dir/buildtrees/libsystemd/build-x64-linux-dbg-out.log
ninja: Entering directory `Path-to-vcpkg-install-dir/buildtrees/libsystemd/x64-linux-dbg'
[1/191] Generating src/basic/filesystems-gperf.h with a custom command
[2/191] Generating version.h with a custom command
[3/191] Generating src/basic/filesystem-switch-case.h with a custom command (wrapped by meson to capture output)
[4/191] Generating src/basic/errno-list.txt with a custom command (wrapped by meson to capture output)
[5/191] Generating src/libsystemd/audit_type-list.txt with a custom command (wrapped by meson to capture output)
[6/191] Generating src/basic/arphrd-list.txt with a custom command (wrapped by meson to capture output)
[7/191] Generating src/basic/cap-list.txt with a custom command (wrapped by meson to capture output)
[8/191] Generating src/basic/filesystem-list.h with a custom command (wrapped by meson to capture output)
[9/191] Generating src/basic/af-list.txt with a custom command (wrapped by meson to capture output)
[10/191] Generating src/core/systemd.pc with a custom command
FAILED: src/core/systemd.pc
Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py config.h version.h ../src/v254-832da4078b.clean/src/core/systemd.pc.in src/core/systemd.pc
Traceback (most recent call last):
  File "Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py", line 9, in <module>
    import jinja2
ModuleNotFoundError: No module named 'jinja2'
[11/191] Generating src/udev/udev.pc with a custom command
FAILED: src/udev/udev.pc
Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py config.h version.h ../src/v254-832da4078b.clean/src/udev/udev.pc.in src/udev/udev.pc
Traceback (most recent call last):
  File "Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py", line 9, in <module>
    import jinja2
ModuleNotFoundError: No module named 'jinja2'
[12/191] Generating src/libudev/libudev.pc with a custom command
FAILED: src/libudev/libudev.pc
Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py config.h version.h ../src/v254-832da4078b.clean/src/libudev/libudev.pc.in src/libudev/libudev.pc
Traceback (most recent call last):
  File "Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py", line 9, in <module>
    import jinja2
ModuleNotFoundError: No module named 'jinja2'
[13/191] Generating src/libsystemd/libsystemd.pc with a custom command
FAILED: src/libsystemd/libsystemd.pc
Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py config.h version.h ../src/v254-832da4078b.clean/src/libsystemd/libsystemd.pc.in src/libsystemd/libsystemd.pc
Traceback (most recent call last):
  File "Path-to-vcpkg-install-dir/buildtrees/libsystemd/src/v254-832da4078b.clean/tools/meson-render-jinja2.py", line 9, in <module>
    import jinja2
ModuleNotFoundError: No module named 'jinja2'
[14/191] Generating src/basic/errno-to-name.h with a custom command (wrapped by meson to capture output)
[15/191] Generating src/basic/errno-from-name.gperf with a custom command (wrapped by meson to capture output)
[16/191] Generating src/basic/arphrd-to-name.h with a custom command (wrapped by meson to capture output)
[17/191] Generating src/basic/arphrd-from-name.gperf with a custom command (wrapped by meson to capture output)
[18/191] Generating src/basic/cap-from-name.gperf with a custom command (wrapped by meson to capture output)
[19/191] Generating src/basic/af-from-name.gperf with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.

I tried on a virtual ubuntu 22.04 and got same error

You use the following command to install jinja2, and then reinstall it.
apt-get install python-jinja2

Thanks a lot, it worked.
I have virtual python environment activated and it has jinja2, and I think it should work but not. Now, I deactivate the virtual env and install python-jinja2 package, it worked.


Use GUI management

First take a look at the following

https://github.com/jeremykenedy/laravel-roles#opening-an-issue
https://github.com/jeremykenedy/laravel-roles/issues?q=is%3Aissue+is%3Aclosed

Please describe what you are needing help with below:
hi,
i have update my .env with this variable to enable GUI. i have
ROLES_GUI_ENABLED=true
ROLES_GUI_AUTH_ENABLED=true
ROLES_GUI_MIDDLEWARE_ENABLED=true
ROLES_GUI_MIDDLEWARE='role:admin'
ROLES_GUI_CREATE_ROLE_MIDDLEWARE_TYPE='role'
ROLES_GUI_CREATE_ROLE_MIDDLEWARE_TYPE='administrators'
ROLES_GUI_CREATE_PERMISSION_MIDDLEWARE_TYPE='role'
ROLES_GUI_CREATE_PERMISSION_MIDDLEWARE_TYPE='administrators'
ROLES_GUI_BLADE_EXTENDED='layouts.app'
ROLES_GUI_TITLE_EXTENDED='template_title'
ROLES_GUI_LARAVEL_ROLES_ENABLED=false
ROLES_GUI_TOOLTIPS_ENABLED=true
ROLES_GUI_DATATABLES_JS_ENABLED=false
but my question is, can i use your project to manage user, role, permission like your printscreen, without make it from scratch ?
because when i add this configuration on my .env, i can't acces to the route <IP_ADDRESS>/permissions or anything else in http get.
i use laravel 5.8.

This package is for roles, permissions, and levels only.
For users management you need to also pull in laravel-users: https://github.com/jeremykenedy/laravel-users
Being unable to access the routes sounds like there may an environment issue.

Hi there,
I know the issue is closed but I'm experiencing the same problem. I have followed the instructions and had no problems with installing the package.
Things I tried:
I have added the ENV variables to .env and set the ROLES_GUI_ENABLED=true. I got 404 not found when trying to access routes.
I changed the default value inside config/roles.php to true. Still no luck.
I copied your routes to my own routes file and changed the groupo namepace to '\jeremykenedy\LaravelRoles\App\Http\Controllers\' (just added the \ so it wouldn't concatenate to my Apps controller namepace ). Then something at last happend. I got this: 'InvalidArgumentException No hint path defined for [laravelroles].  No hint path defined for [laravelroles].'
Since I use Laravel 5.8 I initially did not add the namespace to the providers array inside config.app. I tried anyway but this did not resolve the issue.
My .env file works for other variables I use so I doubt that is the problem.
Thanks in advance.

Hello,
I wouldn't recommend overwriting the routes in your web.php. You may want to consider removing those and go with the built calls.
You should publish the config file, update your .env file then it should all work out the box. If you are using the laravel-users package you may want to configure that as well.
You may have a jam in your autoloader which can be cleared with composer dump-autoload. My first thought is the config and the env are cached in the autoloader.

Thanks for your fast reply, I went fiddling around in the service provider. I just did a plain old die(), to check if the SP even got triggerd, it did. So it booted but didn't access the routes. After removing the if (config('roles.rolesGuiEnabled')) statement in the boot and register method I could access the routes and everything worked. Apperently the config() function takes a key as in a config filename and then a string or array of multiple keys that are in that config file like below:
if (config('roles',['rolesGuiEnabled']))
if (config('roles','rolesGuiEnabled'))
If I use one of these inside the RoleServiceProvider it works. I'm curious if other people have the same issue or if it's just me.


Re-fork repositories to avoid confusion

@ilwoolyu To avoid confusion, could you delete your project ilwoolyu/RigidAlignment and re-fork the one hosted in the NIRALUser organization. See https://github.com/NIRALUser/RigidAlignment
The fork graph currently shows this:

@pdedumast: After @ilwoolyu is done, you may have to do the same.
Thanks :pray:

Done.
On Tue, Dec 3, 2019 at 5:32 PM Jean-Christophe Fillion-Robin <
<EMAIL_ADDRESS>wrote:

@ilwoolyu https://github.com/ilwoolyu To avoid confusion, could you
delete your project ilwoolyu/RigidAlignment and re-fork the one hosted in
the NIRALUser organization. See
https://github.com/NIRALUser/RigidAlignment
The fork graph currently shows this:
[image: image]
https://user-images.githubusercontent.com/219043/70098817-2cc05c00-15fb-11ea-9dbe-36b9dd6c2107.png
@pdedumast https://github.com/pdedumast: After @ilwoolyu
https://github.com/ilwoolyu is done, you may have to do the same.
Thanks 🙏
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NIRALUser/RigidAlignment/issues/4?email_source=notifications&email_token=ACHEZZWJ3ZAV7C7DCBSIIKLQW3UBLA5CNFSM4JVAH6T2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H52263A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHEZZXBPAYOBG44SITODULQW3UBLANCNFSM4JVAH6TQ
.

👍

Thanks everyone :+1:


Fix get_revision for multiple repo sources

Up for debate is whether you guys want to keep '0' as the default for maxRevision or change it to 'None.

Thanks for the fix. I will try to get a release out in the next 2 days.


Typos? (sccs? scss?)

Are those typos?
https://github.com/NathanWalker/angular-seed-advanced/blob/master/tools/tasks/seed/build.html_css.ts#L79
https://github.com/NathanWalker/angular-seed-advanced/blob/master/tools/tasks/seed/build.html_css.ts#L102
https://github.com/NathanWalker/angular-seed-advanced/blob/master/tools/tasks/seed/build.html_css.ts#L129
https://github.com/NathanWalker/angular-seed-advanced/blob/master/tools/tasks/seed/build.html_css.ts#L182

@Sn3b looks like a contributor mishap. Just pushed up fix alongside some nice package updates.
Thanks for heads up!


disable Starlark language server

Change-Id: If271ce889f462f09a4cb0cd731ef51da0c8967ae

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.72%. Comparing base (4742c96) to head (8f754f7).

Additional details and impacted files
@@                            Coverage Diff                             @@
##           I55e149f3ae0c7f9d7b4247b32a3845e3fc31bb1a      #55   +/-   ##
==========================================================================
  Coverage                                      67.72%   67.72%
==========================================================================
  Files                                             21       21
  Lines                                            251      251
  Branches                                           5        5
==========================================================================
  Hits                                             170      170
  Misses                                            81       81

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


[Feature][Connector-V2] Support TableSourceFactory/TableSinkFactory on clickhouse connector

close #6410

Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Current test
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Please fix CI

same as https://github.com/apache/seatunnel/pull/6975

Probably close this PR since it's duplicated.


update launch tasks to remove unused services - hubspotSync, jsync and segmentListener from systemSettings services from db

https://github.com/Shippable/pm/issues/10092

updated launch tasks here - https://github.com/Shippable/pm/issues/10092.
this is not needed, closing


not all named sub-expressions produce their own RuleKind

I noticed an issue with the current parser codegen. Named sub-expressions no longer generate a RuleKind. To repro, adding ContractName to ContractDefinition below, doesn't add the new kind or change the CST. Test snapshots are unchanged as well.
NOTE: This also happens with choice: nodes, and possibly other types.
- name: "ContractDefinition"
  kind: "Rule"
  unversioned:
    sequence:
      - optional:
          terminal: "abstract"
      - terminal: "contract"
      - name: "ContractName"
        reference: "Identifier"
      - optional:
          reference: "InheritanceSpecifierList"
      - delimitedBy:
          open: "{"
          expression:
            zeroOrMore:
              reference: "ContractBodyElement"
          close: "}"

Purposely doesn't work for optional: or reference:. Not clear what it would mean in those two cases.

Not clear what it would mean in those cases.

I would have thought they would be able to generate their own RuleKind, and insert a node with such kind in the CST.

For reference: and choice:, this is for readability, as we might have two nodes of the same kind in succession, and we need to differentiate which is which.
For things like optional: this is even more important, since we don't generate null/empty nodes, so in order to maintain a consistent CST shape, we need to have a named parent (with 0-1 children).


scan all files for cpe: and add as products

https://csrc.nist.gov/pubs/ir/7695/final

Implemented as targeting tools that produce instead of regex scan of all files.


27 default search accommodation no results

This PR adds a new page for the search results. The page contains a webcomponent which handles the actual UI and is written in React.
It shows a localized message when there are no results to be shown - The results layout will be implemented in #37 .

requestOrOffer is a varchar in the database and not a boolean so initially I got an error making the request. However, it does make sense - You want to know whether a topic is a request or an offer, a boolean doesn't fit (unless you rename it to isRequest or isOffer I suppose) - Hence the change.
Images are removed!

True, requestOrOffer should have been renamed as well, and seams I forgot to change it in the database... was like you changed it to before but when doing the API redesign I thought made more sense that were to be a boolean. But doesn't really matter its fine like it is, just wanted to know why and I see that I forgot to change it everywhere needed. I say we close it.


CreatedAtAction fails to find correct route if action method postfixed with Async

Greetings,
Using ASP.NET Core 3.1 web api project and Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer v4.1.1 package
Given following controller:
[Route("v{version:apiVersion}/[controller]")]
[ApiVersion("1.0")]
[ApiController]
public class ViewsController : BaseApiController

and action methods:

[HttpGet("{viewId:int}")]
[ProducesResponseType(typeof(MessageLogViewModel), StatusCodes.Status200OK)]
[ProducesResponseType(StatusCodes.Status404NotFound)]
public async Task<IActionResult> GetViewByIdAsync(int viewId)
{
     return Ok(viewId)
}

[Route("create")]
[HttpPost]
[ProducesResponseType(StatusCodes.Status201Created)]
[ProducesResponseType(StatusCodes.Status400BadRequest)]
public async Task<IActionResult> CreateViewAsync([FromBody] CreateViewCommand createViewCommand, ApiVersion version)
{
    var id = await this.Mediator.Send(createViewCommand);
    return id > 0 ?
       this.CreatedAtAction(nameof(this.GetViewByIdAsync), new { viewId = id, version = version.ToString() }, null)
        : (IActionResult)this.BadRequest();
}

Following exception raised:
System.InvalidOperationException: No route matches the supplied values.
   at Microsoft.AspNetCore.Mvc.CreatedAtActionResult.OnFormatting(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.ExecuteAsyncCore(ActionContext context, ObjectResult result, Type objectType, Object value)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor.ExecuteAsync(ActionContext context, ObjectResult result)
   at Microsoft.AspNetCore.Mvc.ObjectResult.ExecuteResultAsync(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultAsync(IActionResult result)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeNextResultFilterAsync[TFilter,TFilterAsync]()

However if I rename GetViewByIdAsync to GetViewById everything works fine.
Additional info:
.NET Core SDK (reflecting any global.json):
 Version:   3.1.302
 Commit:    41faccf259

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.302\

Host (useful for support):
  Version: 3.1.6
  Commit:  3acd9b0cd1

Without testing it, but based on your example, I'm 99% sure this is caused by the known, breaking change: Async suffix trimmed from controller action names. It affects link generation. Everything else looks correct to me.
This has also been called out in #651, #601, and #558.

Did this suggestion solve your issue?

It seems this issue is resolved. If you really want the Async suffix, you can also explicitly decorate actions with [ActionName("...")] or there is a MVC option to revert the behavior (but there be dragons). If you're still stuck, I'm happy to re-open the issue or elaborate further. Thanks.


Improve const_assert error messages

They now look like:
error[E0308]: mismatched types
  --> tests/trait_impl.rs:42:5
   |
42 |     const_assert!(false);
   |     ^^^^^^^^^^^^^^^^^^^^^ expected struct `static_assertions::True`, found struct `static_assertions::False`
   |
   = note: expected type `static_assertions::True`
              found type `static_assertions::False`
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

instead of
error[E0080]: evaluation of constant value failed
  --> tests/trait_impl.rs:40:1
   |
40 | const_assert!(false);
   | ^^^^^^^^^^^^^^^^^^^^^ attempt to subtract with overflow
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

This is purely cosmetic but I find it nice.

Is it worth adding some UI tests to make sure these don't regress?

@sgrif does Cargo have a built-in way to do UI tests or would I have to write my own script? I quite like the style of rustc's UI tests.

I think this: https://github.com/laumann/compiletest-rs does tests like rustc's ui tests

Ah, I went too fast through reviews and missed #[macro_export(local_inner_macros)] :/
I don't think it is needed though since we use the $crate keyword ?

Apparently the $crate::macro! pattern breaks when I set edition = "2018" in Cargo.toml, which is extremely odd to me. 😐
Gonna change it to have local_inner_macros just to be consistent and on the safe side.

Yes, https://github.com/laumann/compiletest-rs is how you'd do UI tests in a crate. See https://github.com/diesel-rs/diesel/tree/master/diesel_compile_tests for an example

Apparently the $crate::macro! pattern breaks when I set edition = "2018" in Cargo.toml, which is extremely odd to me. neutral_face
Gonna change it to have local_inner_macros just to be consistent and on the safe side.

That's because in 2018 you need to explicitely reexport the macros from lib.rs, otherwise they're not accessible from the root of the crate


cmd/link: bad relocations on darwin

parent: 19024:e2f19c96b7e2 tip, darwin/amd64

$ hg clpatch 55100044
$ ./make.bash
$ go run -race pkg/runtime/race/testdata/cgo_test_main.go

crashes with random failures depending on revision number.
The root cause is that runtime.racefuncenter calls to a random address instead of
__tsan_func_enter.

If
	CALL	__tsan_func_enter(SB)
is replaced with:
	MOVQ	$__tsan_func_enter(SB), AX
	CALL	AX
then it works correctly.

The difference that I see between these versions is:
machoreloc1 rs->name=__tsan_read r->type=120
machoreloc1 rs->name=__tsan_read r->type=247

120 refers to D_ADDR and works, 247 refers to D_PCREL and does not work.
Not sure where to dig further.

It looks to me like later refactoring of the code has removed even the possibility of writing the alternate form, so there's not much left to do here. I don't know why the PC-relative instruction failed, but it has to do with relocations and linking and probably magic indirections, so it's not surprising there is a detail wrong somewhere.


Add an ability to distinguish runned browsers

When Selenoid runs several containers at the same time Selenoid-UI shows this containers as similar blocks.

It's hard to understand where is needed test is run.
So, I offer to add new capability to Selenoid. Something like this:
{
    "browserName": ...
    "selenoidLabel": "TestLogOnWithRightCredentials"
}

@ElijahCapricorn just pass an additional capability...
name: my-custom-test-tag

... and you will see an additional tag on the rectangle.

Here are the docs about it: http://aerokube.com/selenoid/latest/#_custom_test_name

@vania-pooh oh, sorry. I didn't see this when was reading documentation. Thanks for your reply.


How to add instructions Coach Mark on UINavigationBar item

A simple search yields the answers you're looking for. #31 is good start.


add: Praveen Kumar

Description
Added Praveenkumar.json in public/data and also Added Praveenkumar.json in array of profile lists present in src/ProfilesList.json.
Related Issues
#264
Changes Proposed
Added Praveenkumar.json in public/data and src/ProfilesList.json.
Checklist

[✅] I have read and followed the Contribution Guidelines.
[✅] All new and existing tests passed.
[✅] I have updated the documentation to reflect the changes I've made.
[✅] My code follows the code style of this project.
[✅] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@sha0urya Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and Star the repo to help us grow even further!


Ideas about how to reduce tickets, stress and troubleshooting: Would like to provide the ability for a user to visualize their YAML file

Ideas about how to reduce tickets, stress and troubleshooting. I see that we often have clients that don’t really understand what they have deployed via their yaml.  Some times it may be the person who deployed it but often it is someone who is working with the system who did not deploy it.  I ran across this
GitHub - pmsipilot/docker-compose-viz: Docker compose graph visualization
This reads a yaml file and outputs a block diagram (png file).  Options allow you to remove some of the noise or create different views:
--no-volumes
--no-ports
--no-networks
-r|--horizontal (changes the orientation)
I was thinking if we could build a web page where you could paste the contents of the yaml file into it and it would output a png file (block diagram).  This would help the customer to understand what he has as well as it would be a good tool for us when we need to troubleshoot what they have.  I was thinking it could be part of our WEB UI so that it was distributed on site.  Deploying it as part of the UI would solve the issue a customer may have about publicly posting his yaml file.  I’ve attached a few examples that this tool built against our docker-compose-demo/docker-compose-rabbitmq-mssql.yaml at master · Senzing/docker-compose-demo

This feature request came from Paul Lohr.  Here are some attachments he provided.
![topologyWports](https://user-images.githubusercontent.com/46696819/148833068-a0d539ee-c676-415b-81a7-d3a5d2d5

83b5.png)


DNS request timed out. time out was 2 seconds.

Hi! I have problems with DNScrypt-proxy-win32.
this is what i did :

then i changed my DNS to <IP_ADDRESS> after that i tried to nslookup reddit.com and then i got this one :

please help me to figure it out.
edit : i can access github.com without any single problem, but i cant open any other websites.

<IP_ADDRESS> is a bit unusual. I'm curious about why you chose that IP. Sure, it's reserved for local use, but I'm not sure if Windows handles it like <IP_ADDRESS> by default.
Did you try with <IP_ADDRESS>?

i've tried to change the IP address from <IP_ADDRESS> - <IP_ADDRESS> but all of them have the same result.
i checked my router, i found that actually my machine have successfully made a connection to <IP_ADDRESS>:443 (OpenDNS), but idk why my machine has not yet received the DNS queries.

Did you try with other DNS services?

i have the same problem, but when i Use Google DNS servers instead of <IP_ADDRESS> everything works. Please help.

do i need to open ports?

Yes, you need to make sure that port 443 is open, both on TCP and UDP. Check that you don't have anything blocking port 443, including over UDP.

To open port 443 do i have to go into my router settings?

Port 443 is open but 53 is blocked

Ok. Let's start by looking at what the proxy says when you are starting it. Can you try the following command in the proxy folder?
dnscrypt-proxy -R dnscrypt.org-fr -t 0

E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy -R dnscrypt.org-fr -t 0
[INFO] + DNS Security Extensions are supported
[INFO] + Namecoin domains can be resolved
[INFO] + Provider supposedly doesn't keep logs
[NOTICE] Starting dnscrypt-proxy 1.6.0
[INFO] Generating a new session key pair
[INFO] Done
[INFO] Server certificate #808464433 received
[INFO] This certificate looks valid
[INFO] Server key fingerprint is 4A96:7AF8:6B84:922E:DF98:402A:57DE:DFFA:6EBB:FC
A7:9ABC:AFE2:E584:B14C:A9A0:1464
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>

Excellent! Now try again without the -t 0:
dnscrypt-proxy -R dnscrypt.org-fr

Keep the command line window open and change your DNS settings to <IP_ADDRESS>. Does the Internet work?

E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy -R dnscrypt.org-fr
[INFO] + DNS Security Extensions are supported
[INFO] + Namecoin domains can be resolved
[INFO] + Provider supposedly doesn't keep logs
[NOTICE] Starting dnscrypt-proxy 1.6.0
[INFO] Generating a new session key pair
[INFO] Done
[ERROR] Unable to bind (UDP) [Address already in use [WSAEADDRINUSE ]]
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>

These commands must be run in an elevated command prompt https://github.com/jedisct1/dnscrypt-proxy/blob/master/README-WINDOWS.markdown#how-to-open-an-elevated-command-prompt

My internet works when i change it to <IP_ADDRESS>
i am running command prompt as administrator
when i go to www.opendns.com/welcome it says
Oops…
You aren’t using OpenDNS yet.
Let’s fix that.
If you haven’t restarted your computer yet,
please do that now.
and internetbadguys.com is showing as a demonstration site not phishing

Great! So everything seem to work. Looks like you don't have any problems with anything blocking the required port.
Presumably, what happened is that you tried to install the service without being in an elevated command prompt.
So, let's try installing the service. Close the previous window, open a new elevated prompt and type:
dnscrypt-proxy -R dnscrypt.org-fr --install

Does it work?

what if it is already installed?
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy -R dnscrypt.org-fr --install
[INFO] + DNS Security Extensions are supported
[INFO] + Namecoin domains can be resolved
[INFO] + Provider supposedly doesn't keep logs
[ERROR] Unable to install the service
[ERROR] Make sure that you are using an elevated command prompt and that the service hasn't been already installed
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>

Run
dnscrypt-proxy --uninstall

first.

E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy --uninstall
[INFO] The dnscrypt-proxy service has been removed from this system

Looks great. Now run the --install command again.

E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy --install
[ERROR] Resolver information required.
[ERROR] The easiest way to do so is to provide a resolver name.
[ERROR] Example: dnscrypt-proxy -R mydnsprovider
[ERROR] See the file [dnscrypt-resolvers.csv] for a list of compatible public re
solvers
[ERROR] The name is the first column in this table.
[ERROR] Alternatively, an IP address, a provider name and a provider key can be
supplied.
[ERROR] Consult http://dnscrypt.org and https://github.com/jedisct1/dnscrypt-pro
xy/blob/master/README-WINDOWS.markdown for details.
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>--install
'--install' is not recognized as an internal or external command,
operable program or batch file.
E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>

this is what i have written
dnscrypt-proxy.exe -R "fvz-rec-ch-zu-01" -L "E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0\dnscrypt-resolvers.csv" --test=0
dnscrypt-proxy.exe -R "fvz-rec-ch-zu-01" -L "E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0\dnscrypt-resolvers.csv"  --install

The command you just typed before:
https://github.com/jedisct1/dnscrypt-proxy/issues/198#issuecomment-129692446

E:\DNSCrypt\dnscrypt-proxy-win32 1.6.0>--install
'--install' is not recognized as an internal or external command,
operable program or batch file.

If you want to use the fvz-rec-ch-zu-01 OpenNIC server:
dnscrypt-proxy.exe -R fvz-rec-ch-zu-01 --install

See the documentation here: https://github.com/jedisct1/dnscrypt-proxy/blob/master/README-WINDOWS.markdown#the-windows-service
All you have to do is:
dnscrypt-proxy --uninstall
dnscrypt-proxy -R <name> --install

With <name> being the name of the resolver you want to use, such as cisco, dnscrypt.org-fr or fvz-rec-ch-zu-01.

E:\DNSCrypt\dnscrypt-proxy-win32  1.6.0>dnscrypt-proxy.exe -R fvz-rec-ch-zu-01 --install
[INFO] - [fvz-rec-ch-zu-01] does not support DNS Security Extensions
[INFO] + Namecoin domains can be resolved
[INFO] + Provider supposedly doesn't keep logs
[INFO] The dnscrypt-proxy service has been installed and started
[INFO] The registry key used for this service is SYSTEM\CurrentControlSet\Services\dnscrypt-proxy\Parameters
[INFO] Now, change your resolver settings to <IP_ADDRESS>:53

So, if you can access the internet now, you're all set!

do i change my primary DNS in IPv4  to <IP_ADDRESS>

Yes.

I had the same issue with nslookup. It seems like a bug. dig from cygwin works fine yet nslookup claims timeout. DNS is working fine, btw. Manually setting the server to <IP_ADDRESS> also works with nslookup.
Example on Windows 7:
C:\>nslookup github.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  <IP_ADDRESS>

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\>nslookup github.com <IP_ADDRESS>
Server:  localhost
Address:  <IP_ADDRESS>

Non-authoritative answer:
Name:    github.com
Addresses:  <IP_ADDRESS>
          <IP_ADDRESS>

C:\>


Why is Travis CI configured to check against so many versions of Cabal and GHC?

Right now, the Travis CI build is configured to check this package against 17 version combinations of Cabal and GHC.
Can we remove some of them?
We need to check against 7.8.4 (LTS Haskell) and up, but I think we can remove some of the remaining ones (7.0., 7.2., 7.4., 7.6.).

I think the current travis file was contributed by an outside user, but I'm not sure if they were using an old GHC that didn't work with inflections, or if something else motivated the change. I'd be ok with making the file more standard, and getting rid of some really old GHC versions that it doesn't seem likely anyone is using anymore. If we're changing this, we may want to follow the PR made by @juanpaucar on twitter-feed, since that seems to be the way that Travis wants to be configured now.

@jsl Sounds good.

So i'm going to move this to the containers in travis... but since we usually use ghc 7.6, 7.8 and 7.10; i'd remove the other ghc versions. Is this ok @jsl @jpvillaisaza ?

Sure! If this Travis recipe is working well, I think we have about 10 other
projects that could use it too! Maybe even a short blog post with our
Travis config so that it's easy to find for other haskellers looking for
idiomatic, simple Travis confogs?
On Friday, July 24, 2015, Juan Paucar<EMAIL_ADDRESS>wrote:

So i'm going to move this to the containers in travis... but since we
usually use ghc 7.6, 7.8 and 7.10; i'd remove the other ghc versions. Is
this ok @jsl https://github.com/jsl @jpvillaisaza
https://github.com/jpvillaisaza ?
—
Reply to this email directly or view it on GitHub
https://github.com/stackbuilders/inflections-hs/issues/12#issuecomment-124551384
.

--
Justin Leitgeb http://justinleitgeb.com
Twitter: @justinleitgeb http://twitter.com/justinleitgeb
Github: @jsl https://github.com/jsl
Co-Founder and CTO, Stack Builders Inc. http://www.stackbuilders.com

@juanpaucar @jsl Sounds good to me (updating the Travis configuration and the blog post).

So we have this repo https://github.com/hvr/multi-ghc-travis .
It hasn't been updated yet, although there's an issue from April https://github.com/hvr/multi-ghc-travis/issues/17 .
I could write something short if you want it that post

Done. See https://github.com/stackbuilders/inflections-hs/commit/4813adec73a03063f71e58bd337e3cc45f1b7470.


Extensible payload handler

We use Tracelogging extensively in our system and we often log nested EventData objects via Write. The current implementation doesn't work for this scenario since it just calls ToString() on each value in the Payload collection. This change allows for implementing your own handler for converting EventWrittenEventArgs to TraceTelemetry.

@jafletch,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@jafletch, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@jafletch, it looks similar to the existing concept of Telemetry Initializers that allow one to modify/enrich telemetry item context before it gets sent. Is there another scenario or requirement this change might address?

@Dmitry-Matveev I am pretty new to AI in general and I just glanced through the docs in initializers and processors and it isn't obvious that would solve my problem, but perhaps I am just not familiar enough. The issue that I have is that I need to get access to the underlying ETW EventData object before that gets encoded into the properties of the TraceTelemetry object. The current implementation very simply passes over that EventData calling ToString() on the various parts of the payload and puts those in as properties of TraceTelemetry. I like most of what the current implementation does, but I want to be able to override that one behavior. I am open to any option that lets me do that.

@jafletch how about we give you an event off of the module, where you would get the EventData object and the TraceTelemetry object produced out of it and you could massage the TraceTelemetry object the way you see fit before it is passed down the pipeline?

@karolz-ms Sure, that sounds like basically what my change enables. For reference, here is my OnEventWrittenHandler currently looks like:
        public static void Track(EventWrittenEventArgs eventData, TelemetryClient client)
        {
            var telemetry = eventData.ToTraceTelementry(includePayload: false);

            eventData.ExtractPayloadData(telemetry);

            client.Track(telemetry);
        }

where the ToTraceTelementry extension method is just a slightly altered version of the Track EventData extension method that previously existed in the code. So I am able to reuse all of the functionality of setting up the TraceTelemetry object that this code was previously doing and just opt out of the payload handling part.
If you passed me the TraceTelemetry object with the payload fields already in there per the current ToString() mechanism, that doesn't seem useful so I would want to make sure that I get full control over handling the payload.

@jafletch Two questions then

How generic is your handler that deals with nested EventData objects? Would that be something that is universally useful? If so, we should just incorporate this into the module.

if the answer is "no"

I would like you to modify your proposal so that there is no includePayload bool parameter on for the ToTraceTelemetry method. Please refactor the code so that it has the building blocks you need (methods on EventDataExtensions, e.g. CreateTelemetry, AddStandardProperties, AddPayloadProperties) and make the ToTraceTelemetry and your custom EventData --> TraceTelemetry converter use these methods.

The latter is to ensure (to the foreseeable extent) that if someone else comes along and wants to create TraceTelemetry in yet another slightly different way, we do not have to change anything in the module code anymore.

@karolz-ms No, I wouldn't consider my solution sufficient for all cases. We are lucky in that we have a pretty narrow set of things that come through payload and my implementation is enough to handle those, but it isn't something I would be comfortable shipping much more broadly. I think this is going to be a pretty hard problem for a general solution which is why I think this particular extensibility point will be essential.
Agreed on point (2). I'll make some changes there and push them up.
Thanks! We already have people waiting on AI support so this is pretty cool for us.

I wonder why do we need an extensibility on telemetry module when it may be more natural to implement a custom eventsource listener? The benefit of custom listener is that you get a full control over it's behavior and granularity of configuring it only for the event sources you are interested in.

@SergeyKanzhelev the granularity part is also present with our EventSourceTelemetryModule (through the Sources property, specifically)

Ok I believe the current code reflects the requested changes

@karolz-ms my question was what benefit telemetry module gives comparing to the custom event listener. It feel like close to zero code reuse unless I missing something important.

To give some context here - exposing a callback to allow one to extract more data is a very common scenario. Same way you need access to EventData object - one may need access to HttpClient to properly initializer the dependency telemetry object.
So long term we need a new layer in the SDK layering model that will enable such scenario in a more generic way.
We discussed it with @karolz-ms offline at Friday and floated ideas like TelemttryFactory<EventData> object and things of this nature. But there are more considerations at play. So we do not have a clear solution right away.
I think we need to get this change and later refactor it into the generic approach. I'd also like to know what would be your experience with the callback approach and ideas around it.

Ok I believe all the feedback is addressed now


Add support for creating, deleting and renaming IMAP folders

Expected behaviour
A user should be able create, delete and rename IMAP folders
Actual behaviour
The user has to do it via the web client
Notes
It doesn't look too complex to implement: https://tools.ietf.org/html/rfc3501#page-34
A similar issue will want to be raised for WebDAV.
This blocks #900

See also https://code.google.com/archive/p/k9mail/issues/162

We currently don't revert local operations that fail on the server. I believe without this functionality having the ability to create new folders can very easily lead to situations where users lose messages, e.g. because we fail to copy them to the destination folder but delete them from the source folder.
We should fix that before allowing users to add/modify folders.

@cketti I understand your concern: message lost must not happen.
Is there already a ticket for this "bigger" issue?

BTW funny thing is that K-9 actually creates folders but without user expecting it: https://github.com/k9mail/k-9/issues/3755

Hi @cketti. Was there any progress on reverting local operations so we can advance on this issue then on #900? Thanks.

Still not feasable in 5.7xx ?

any chance we can get something like this added with a warning message about the potential complications? some of us don't even have a web interface for our email to work around this so easily

Any progress?

This is a five year-old bug now. It can almost go to school now.

This is a five year-old bug. It can almost go to school now.

Yes.
And it's too bad it's not yet available. Have to use my webmail for that.

Couldn't this be simplified with supporting IMAP CREATE, RENAME, DELETE only in synced online state and just refreshing the folder list afterwards. Then there is no message handling for this on client side. Everything should be handled by the server.
I really miss the possibility to create new folders without going to a desktop. ;-)

Have been searching on how to create a folder for almost an hour because i could not believe you can’t :(
This is essential for a mature e-mail client

This bug is probably going to be handled using the Mozilla approach. It either waits for decades to get fixed or someone forks the project entirely and people gonna use it. If it wasn't for K9-Mail's great batch management I'd have used the app that came with my phone by now.

If you don't have anything of value to add to this conversation, then please don't comment. To be very clear: Complaining about people not putting in work for free is not adding value to any conversation.
This is still an open source project and the tone and content of the last two comments shows a lack of appreciation of the work people put in the project.
Not only does that not help solve this specific issue, it is also extremely discouraging for maintainers and contributors alike.
Additionally, comments like these also spam everyone subscribed to this issue, which is annoying for everyone involved. So, please, just don't.

Can you please consider adding this one to #6488? Thanks.

I can't see any way to create, rename and move emails and folders at all (yet). Hope it gets added.

+1


Event type error says mitmproxy has crashed without actually crashing

Problem Description
Some sort of event type error...? This happened when I was testing modify_body and modify_headers options (see reproduction steps) and it results in repeated error messages with really long tracebacks.
The error messages begin by saying that mitmproxy has crashed, but it doesn't actually crash.
[... lots more traceback before the below]
  File "/home/elespike/venvs/mitmproxy/lib/python3.9/site-packages/mitmproxy/proxy/layer.py", line 144, inhandle_event
    command = command_generator.send(send)
  File
"/home/elespike/venvs/mitmproxy/lib/python3.9/site-packages/mitmproxy/proxy/layers/http/__init__.py", line136, in _handle_event
    yield from self.client_state(event)
  File "/home/elespike/venvs/mitmproxy/lib/python3.9/site-packages/mitmproxy/proxy/utils.py", line 23, in
_check_event_type
    raise AssertionError(
AssertionError: Unexpected event type at HttpStream.state_done: Expected no events, got
RequestEndOfMessage(stream_id=1).

Steps to reproduce the behavior:

Start with default options
Set modify_body and modify_headers as follows:

modify_body:
  - :~u webhook.site ~q::
hey

modify_headers:
  - :~u webhook.site ~s:content-type:text/html

Visit https://webhook.site

System Information
Mitmproxy: 7.0.4
Python:    3.9.2

Thanks! Your modifications triggered an interested  race condition in our protocol implementation.
https://github.com/mitmproxy/mitmproxy/pull/4932 should fix this, could you please verify if that is true?
(the webhook.site website will still not work properly with your changes, but that is about to be expected I guess)

That did it! Thanks for looking into this. =)


🎉 - Added PowerShell setup script

As pr @waldekmastykarz request here - I've converted the Bash script to run in PowerShell, and tested it on my W11 machine
Solves #19

Awesome! Thank you so much for such a quick turnaround ❤


Clear marker array for every message

The right implementation would use the marker ids + lifetime, but this it at least better than letting it grow forever ;)

I checked, the loop is so fast,  it doesn't matter. Showing only half a marker array is also of no benefit ;)


pkg/trace/writer: be less verbose about flushes

This change modifies the logging level applied when reporting that a
flush to the Datadog API has occurred from "INFO" to "DEBUG". This
matches the behaviour in the core agent.
Closes #2939

Hi - just wondering if this fix went into the latest release - version 0.24.1?

This will go into the next release (6.11.0)
On Sat, 2 Mar 2019 at 13:22, Damien Gallagher<EMAIL_ADDRESS>wrote:

Hi - just wondering if this fix went into the latest release - version
0.24.1?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/DataDog/datadog-agent/pull/3099#issuecomment-468911701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGYGlOaqT5zmIMyCBWQmZTcdqFZ9oi9Xks5vSl7-gaJpZM4bUjUq
.

Any idea when that will be? Sorry for me it is hard to see the correlation between the latest release on mvn repository (0.24.1) and the next release (6.11.0)

Hi @damogallagher,
I am guessing that by the maven release you mean what is available at https://mvnrepository.com/artifact/com.datadoghq/dd-java-agent ? Both are different projects with uncorrelated release cycles, hence the two different versions. The two are interacting together to gather (dd-java-agent a.k.a. dd-trace-agent) and forward (datadog-agent) traces to Datadog. Some docs are available at https://docs.datadoghq.com/tracing/languages/java/. Since this issue affects datadog-agent you'll need to wait for its next release, 6.11.
Feel free to let me know if you need additional clarification.
Arthur

Perfect thanks for the clarification @arbll


Fixed layout forcing expand on hover for sidebar mini

I'm using latest 2.4.2 and have added "fixed" to the body tag but when the menu is in mini mode the menu expands on hover instead of the menu items pulling out to the right.
The documentation only says the fixed layout cannot work with boxed layout but mentions no other limitation. I can also see in the demo.js the function changeLayout forces $pushMenu.expandOnHover() for fixed class.
Why is this and can the fixed layout work without expanding the sidebar menu?

Exactly, the same problem to me
version: "2.4.2"
I search the source code an find this
if (this.options.expandOnHover || ($('body').is(Selector.mini + Selector.layoutFixed))){
    this.expandOnHover()
    $('body').addClass(ClassName.expandFeature)
}

Does it for some special purpose?
I really need it not bind the 'hover' event when I use layout 'fixed' and 'mini'
Hope to your relpy


Fixed publishing step

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test docs-presubmit

/retest


🐛 Break on TypeScript parameter properties

Environment information
Playground

What happened?
Biome should break lines when at least one parameter property is present.
See the related prettier PR prettier#14402.
Playground link
Expected result
The following code:
class MyClass {
  constructor(a: string, protected x: number, b: string) {}
}

should be formatted as Prettier:
class MyClass {
	constructor(
		a: string,
		protected x: number,
		b: string
	) {}
}

Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Can I work on this?


fix for unpredictable mapping of entity names to sensors in concord232 binary_sensor

Description:
Bug:  When using the concord232 platform, binary_sensor entity names, e.g., binary_sensor.unnamed_device_2, can map to different sensors in the concord alarm system in an unpredictable way.
Fix: Sort the sensors by zone number right after they are queried.  This gives both a predictable order and a simple mapping from zone numbers to entity numbering when the zones do not have names.
Related issue (if applicable): fixes #11289
I don't think new documentation is needed, but this should go in the release notes to explain the possibly changed behavior.
Checklist:
If the code communicates with devices, web services, or third-party tools:

[X ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Hi @rwa,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Please add a comment to the release PR when that is opened, to highlight the change.


infra: support custom base image

Signed-off-by: hejianpeng<EMAIL_ADDRESS>fixes: https://github.com/envoyproxy/gateway/issues/327
this PR make folks can custom base image for better debugging by running following command:
IMAGE_BASE=<your_base_image:-ubuntu:jammy> make kube-install-image

collect is not enough, dev users also need change logging level on the fly by logging, or check stats from /stats
BTW, envoy-gateway need a long way to go.

I would like to get input from @arkodg before merging this PR due to https://github.com/envoyproxy/gateway/issues/327#issuecomment-1233643635.

since the goal is to improve debuggablity, would prefer EG provided commands, reports directly instead of the user swapping out the container image to something that contains more utility commands in it

@zirain is https://github.com/envoyproxy/gateway/pull/749#issuecomment-1337876893 something you can take on? It would be a big help to the project.

I do not think it's a good idea to provider feature on eg, maybe a tools call egctl?

yeah egctl makes a lot of sense here, which can be the entry point to  analyze / report / collect subcmd ?

I do not think it's a good idea to provider feature on eg, maybe a tools call egctl?

yeah egctl makes a lot of sense here, which can be the entry point to analyze / report / collect subcmd ?

yes, that's what I think.

@danehans @arkodg let's close this first, then I will raise a proposal about new binary named egctl, WDYT?

@danehans @arkodg let's close this first, then I will raise a proposal about new binary named egctl, WDYT?

sounds good, thanks !

close this for https://github.com/envoyproxy/gateway/issues/794


ref(Dockerfile): install az cli via pip, not apt-get

The Ubuntu-packaged version of az has some crypto issues, at least when used in our Jenkins pipeline. Specifically, some az storage commands will time out and fail with an HTTPSConnectionPool error.
Installing via pip works around this issue. I've tested this live on our Jenkins CI instance.

Is this the issue that's been hounding me at https://github.com/Azure/draft/issues/252? If so I owe you a cookie!!! 🍪


Allow arbitrary args and flags

Hi Jawher,
Is there is a way to allow arbitrary arguments and flags in a command? I have a script which wraps another tool and want to give users the ability to pass any args/flags to the underlying tool as if they were using it directly. I'm able to pass arbitrary string args using:
app := cli.App(...)
...
app.Command("tool", "Send a command directly to the tool using the INSTANCE configuration", func(cmd *cli.Cmd) {
	instance := cmd.String(InstanceArg)
	args := cmd.StringsArg("ARGS", nil, "tool arguments")
	cmd.Spec = "INSTANCE [ARGS...]"

	cmd.Action = func() {
		// pass *args along to tool
	}
})

However, I haven't figured out a clean way to allow arbitrary flags as well. Ideally, I would be able to run the command like:
> main.go tool INSTANCE [args...] [flags...]

I don't want to clutter up my code with all of the potential args/flags for underlying tool, and would prefer not to manually parse os.Args before calling app.Run. Any suggestions?
Regards,
ZPatrick

Hi,
The -- is what you're looking for (see [this section of the README)[https://github.com/jawher/mow.cli#operators]).
In your case:
app := cli.App(...)
...
app.Command("tool", "Send a command directly to the tool using the INSTANCE configuration", func(cmd *cli.Cmd) {
    instance := cmd.String(InstanceArg)
    args := cmd.StringsArg("ARGS", nil, "tool arguments")
    cmd.Spec = "INSTANCE [-- ARGS...]"

    cmd.Action = func() {
        // pass *args along to tool
    }
})

You can then call your command like this:
app tool cp -R source dest

And instance will be populated with "cp" and args with ["-R", "source", "dest"]

Just what I was looking for, thanks!


Supports docker-compose version 2

Supports docker-compose version 2. Ex.:
version: '2'
services:
service:
image: qkrijger/hello-world-wiremock-server:0.1.0-SNAPSHOT
ports:
- 80
testimage:
image: d7330fed7586
links:
- service:server

Hi @inaiat . Thanks for contributing!
I merged this commit. It was far from done though - the tests failed on linux, due to the IP address not being set (in docker compose v2, you need to get that value from the network). Did you test it on Mac with Boot2Docker?

Also, next time please make sure to sign off your commit

Hi Krijger,
I test on Mac with docker-machine.
Thanks.
On Sat, Mar 26, 2016 at 3:21 PM, Quinten Krijger<EMAIL_ADDRESS>wrote:

Hi @inaiat https://github.com/inaiat . Thanks for contributing!
I merged this commit. It was far from done though - the tests failed on
linux, due to the IP address not being set (in docker compose v2, you need
to get that value from the network). Did you test it on Mac with
Boot2Docker?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/stackwork/stackwork/pull/59#issuecomment-201908552

Cool. I take it the current version still works i.c.w. boot2docker? Would be nice if you could verify that.


cell metadata appears changed in liveshare session

Open a notebook
Start a liveshare session
A guest joins the liveshare session
Edit and run some cells
The notebook shows up in the git diff with a vsls_cell_id key that appears removed

This should be marked as transient.

Previous discussion: https://github.com/microsoft/vscode/issues/120127


Inconsistent mouse wheel scroll behavior on Wayland

Describe the bug
Mouse wheel scrolling is wrong on Wayland. Scrolling down works perfectly, but scrolling up only scrolls about a quarter of the way it would scroll down. Very annoying :-) Everything is fine on X11 (even with Xwayland)
To Reproduce
Steps to reproduce the behavior:

Connect to RDP server with wlfreerdp
Open a document
Use the mouse wheel to scroll down a few times
Use the mouse wheel to scroll up a few times

Expected behavior
Scrolling down and up scrolls by the same amount of lines.
Screenshots
Application details

FreeRDP git 971be4fe9
wlfreerdp /u:<user> /v:<host>
This is FreeRDP version 3.0.0-dev (971be4fe9) Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=ON WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=ON WITH_FAAD2=ON WITH_FFMPEG=TRUE WITH_FFMPEG=TRUE WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=ON WITH_GSSAPI=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENCL=ON WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=OFF WITH_PCSC=ON WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=ON WITH_SWSCALE=ON WITH_THIRD_PARTY=OFF WITH_VAAPI=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=ON WITH_WINPR_TOOLS=ON WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XV=ON WITH_ZLIB=ON Build type:          Release CFLAGS:               -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -DWINPR_DLL Compiler:            GNU, 9.3.0 Target architecture: x64
Server is Windows 10 Version 1903
wlfreerdp-log.txt

Desktop (please complete the following information):

OS: Linux Manjaro

I get +-10 "steps" on scrolling with the axis event, which does not seem to be enough for Windows to behave appropriately.
When I override with 0x78 (the value on X11) here:
https://github.com/FreeRDP/FreeRDP/blob/7733fe7a8a7d96b42699690d6a8d07d782f084a8/client/Wayland/wlf_input.c#L174
It works as expected. Not a nice solution though.

@yol looks like a correct patch, can you create a pr for that?

Not sure it is the way to go though - it would degrade the scrolling experience with touch pads, for example, because they are continuous and don't send only discrete steps.

@yol what dou you mean wit continoous? Everything in a computer is discrete ;)
Already getting smaller/bigger numvers depending on hw and acceleration

Well, scrolling via touchpad is arguably more continuous than discrete wheel steps (which are discrete also in the real world, while for touchpad this is not the case). So for wheel scrolling, you will get 10 or 15 as value on Wayland (depending on the compositor...). For touchpad scrolling, you'll get significantly smaller values depending on how "fast" you are scrolling, but you will get lots more of those events.
Touchpad scrolling over RDP will probably be horrible if you just replace the value with 0x78 without further adjustments. How does Windows handle this natively?

Ah, I thought you found a fux with abs values?

Other than that, you might want to scale (range of wayland events to rdp event range)

https://wayland.freedesktop.org/libinput/doc/latest/development.html#using-libinput-as-library has some information about the event and how to use it.

I have the same problem, both with a touchpad and a mouse wheel.


List top authors

Top Authors in Authors page.
Order by owned plugins count

Issues to be fixed/clarified:
[Authors page]

plugins with capital letter?
separator between 2x2 columns
authors with 0 plugins - do not show at all
authors sorting?

[Site Header]

authors link - separate from NativeScript.org?
hasMoreItems - scrolling issue on bigger resolutions, present in Home page as well


Package tremor-query and tremor-script in docker

Describe the problem you are trying to solve

Currently the docker file does not package tremor-query nor tremor-script
binaries - these would be useful to assist folk who are learning tremor via the
docker image
Describe the solution you'd like

Add to the dockerized images.
Notes

Document invoking the tools via docker run + docker exec against a running container

We already ship tremor-tool. Since we want to consolidate on that perhaps we can prioritize on that so people don't get sad when tremor-query / tremor-script go away?

Yes, that's the implementation I had in mind - its high time we merged all those together into a single better tool!

renaming this to reflect the intend.

closing as a duplicate of #8 and #7


Remove fomantic progress module

Replace it with HTML <progress> element. The bar won't animate or go green at 100% anymore but I think it's not something that fits stylistically anyways.

Will this make the progress green?
progress[max=100][value=100] {
    color etc
}

It seems working. https://jsfiddle.net/k8rjmaqu/   (it's just an personal opinion to make 100% as green, not a blocker)

Will this make the progress green?
progress[max=100][value=100] {
    color etc
}

Yes it would work for the case where max is 100 like it is for the milestone bar, but I think we could also opt to make the milestone bar always green, like GitHub does.


Double quote character is not encoded as described in the doc

Describe the bug
as described in the doc the following code
const link = (
  <Link
    to="/shop"
    search={{
      pageIndex: 3,
      includeCategories: ['electronics', 'gifts'],
      sortBy: 'price',
      desc: true,
    }}
  />
)

should result in the following search params:
pageIndex=3&includeCategories=%5B%22electronics%22%2C%22gifts%22%5D&sortBy=price&desc=true

However, it actually creates the following:
pageIndex=3&includeCategories=%5B"electronics"%2C"gifts"%5D&sortBy=price&desc=true

The double quotes are not encoded somehow.
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-cpktmg?file=src%2Fmain.tsx
Steps to Reproduce the Bug or Issue

click on the About link
you'll see the double quotes are not encoded from URL search params

Expected behavior
The double quotes should be encoded as described in the doc
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 123.0.6312.87 (Official Build) (arm64)

Additional context
No response

Oops, never mind. I found that if you console.log the double quotes are encoded. I believe it's just the browser shows them as double quotes.