[ 1884.614466] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614469] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614476] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614491] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614493] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614500] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614503] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614506] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614517] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614531] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614534] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614550] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614553] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614556] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614563] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614578] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614580] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614596] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614599] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614602] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614609] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614629] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614632] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614635] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614642] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614657] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614659] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614675] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614679] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614682] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614688] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614703] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614706] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614716] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614719] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614722] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614729] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614744] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614746] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614762] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614765] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614768] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614775] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614790] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614792] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614799] systemd-journald[252]: /dev/kmsg buffer overrun, some messages lost.
[ 1884.614809] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614816] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614819] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614826] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614826] systemd-journald[252]: /dev/kmsg buffer overrun, some messages lost.
[ 1884.614841] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614843] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614860] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614863] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614866] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614872] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614887] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614890] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614906] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614909] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614912] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614922] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614937] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614940] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614956] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614959] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.614962] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.614969] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.614984] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.614986] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.614996] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.614999] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.615002] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.615009] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615027] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615030] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615046] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.615049] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.615052] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.615059] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615074] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615076] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615083] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.615086] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.615089] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.615095] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615110] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615113] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615133] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.615136] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.615139] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.615145] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615160] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615163] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615174] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[ 1884.615177] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00002000/00004000
[ 1884.615180] pcieport 0000:00:01.2:    [13] NonFatalErr
[ 1884.615187] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615197] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615200] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615210] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615213] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615223] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615225] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615236] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615238] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615249] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615251] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615261] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615264] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615274] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615276] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615287] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615289] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615300] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615302] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615312] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615315] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615325] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615328] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615338] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615340] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615351] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615353] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615364] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615366] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615376] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615379] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615389] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615392] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615403] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615405] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615416] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615418] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615428] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615431] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615441] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615444] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615454] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615456] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615467] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615469] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615481] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615483] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615494] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615496] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615506] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615509] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615519] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615522] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615532] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615534] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615545] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615547] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615558] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615560] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615570] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615573] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615583] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615585] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615596] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615598] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615608] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615611] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615621] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615623] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615634] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615636] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615647] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615649] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615659] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615662] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615672] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615674] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615685] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615687] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615698] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615700] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615710] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615713] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615723] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615725] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615728] ------------[ cut here ]------------
[ 1884.615730] firmware failed to ack driver for leaving Deep Power mode
[ 1884.615736] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615739] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615753] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615759] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615770] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615773] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615759] WARNING: CPU: 1 PID: 85 at drivers/net/wireless/realtek/rtw88/ps.c:107 rtw_power_mode_change+0xe6/0x120 [rtw88_core]
[ 1884.615784] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615787] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615798] Modules linked in:
[ 1884.615799] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615800]  ccm tls
[ 1884.615802] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615803]  hid_logitech_hidpp mousedev joydev hid_logitech_dj usbhid rfcomm snd_seq_dummy
[ 1884.615813] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615814]  snd_hrtimer snd_seq snd_seq_device
[ 1884.615817] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615819]  cmac algif_hash algif_skcipher af_alg bnep wl(POE) snd_sof_amd_rembrandt
[ 1884.615828] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615831]  snd_sof_amd_renoir
[ 1884.615831] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615834]  snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp intel_rapl_msr zenergy(OE) snd_sof
[ 1884.615843] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615846]  intel_rapl_common rtw88_8822ce
[ 1884.615847] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615850]  snd_sof_utils rtw88_8822c edac_mce_amd snd_soc_core rtw88_pci snd_compress
[ 1884.615859] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615860]  ac97_bus rtw88_core snd_pcm_dmaengine
[ 1884.615863] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615866]  snd_hda_codec_hdmi kvm snd_hda_intel snd_pci_ps snd_rpl_pci_acp6x snd_intel_dspcfg
[ 1884.615876] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615877]  irqbypass mac80211 snd_intel_sdw_acpi
[ 1884.615879] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615883]  snd_hda_codec crct10dif_pclmul btusb btrtl snd_acp_pci polyval_clmulni
[ 1884.615892] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615894]  vfat btbcm
[ 1884.615896] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615899]  libarc4 polyval_generic snd_hda_core btintel fat snd_pci_acp6x
[ 1884.615908] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615909]  gf128mul btmtk
[ 1884.615911] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615912]  r8168(OE)
[ 1884.615914]  ghash_clmulni_intel snd_pci_acp5x snd_hwdep rapl bluetooth r8169 snd_rn_pci_acp3x
[ 1884.615923] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615924]  snd_pcm cfg80211
[ 1884.615927] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615928]  snd_acp_config snd_timer pcspkr wdat_wdt snd_soc_acpi acpi_cpufreq ecdh_generic
[ 1884.615938] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615939]  snd realtek ccp
[ 1884.615941] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615944]  snd_pci_acp3x i2c_amd_mp2_pci mdio_devres soundcore rfkill i2c_piix4 k10temp
[ 1884.615953] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615954]  libphy 8250_dw
[ 1884.615955] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615958]  mac_hid uinput crypto_user loop fuse bpf_preload ip_tables
[ 1884.615967] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615968]  x_tables btrfs
[ 1884.615969] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615972]  blake2b_generic xor raid6_pq libcrc32c mmc_block amdgpu drm_buddy
[ 1884.615980] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615983]  gpu_sched
[ 1884.615983] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.615985]  i2c_algo_bit drm_suballoc_helper crc32_pclmul drm_ttm_helper sdhci_acpi sdhci ttm
[ 1884.615994] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.615996]  sha512_ssse3 aesni_intel
[ 1884.615997] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.615999]  drm_display_helper crypto_simd cec mmc_core cryptd video
[ 1884.616008] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616008]  wmi overlay
[ 1884.616010] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616012]  ext4 crc32c_generic crc32c_intel crc16 mbcache jbd2 dm_mod
[ 1884.616021] pcieport 0000:00:01.2: AER: can't find device of ID0008

[ 1884.616024] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616026] CPU: 1 PID: 85 Comm: kworker/u17:0 Tainted: P        W  OE      6.4.11-chos3-chimeraos-1 #1 3a4ab7e908db79638d38c14ebbe295384c408c99
[ 1884.616031] Hardware name: ATARI VCS 800 Black Walnut/VCS, BIOS <IP_ADDRESS>1-VCS.23 08/04/2021
[ 1884.616035] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616038] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616050] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616034] Workqueue: rtw_tx_wq rtw_tx_work [rtw88_core]
[ 1884.616053] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616065] pcieport 0000:00:01.2: AER: can't find device of ID0008

[ 1884.616067] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616078] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616069] RIP: 0010:rtw_power_mode_change+0xe6/0x120 [rtw88_core]
[ 1884.616081] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616093] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616095] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616096] Code: 20 93 3f cc 44 30 e0 78 23 45 84 ed 48 c7 c0 64 fa d4 c1 48 c7 c6 6d fa d4 c1 48 c7 c7 18 dc d4 c1 48 0f 45 f0 e8 1a 95 72 cb <0f> 0b 5b 5d 41 5c 41 5d e9 dd 99 3f cc 48 8b 8b 98 4b 00 00 8b 83
[ 1884.616099] RSP: 0018:ffffa67a003fbd80 EFLAGS: 00010286
[ 1884.616103] RAX:<PHONE_NUMBER>000000 RBX: ffff9628c4232080 RCX:<PHONE_NUMBER>000027
[ 1884.616106] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616106] RDX: ffff962df6c616c8 RSI:<PHONE_NUMBER>000001 RDI: ffff962df6c616c0
[ 1884.616109] RBP: 000001b6cdb91117 R08:<PHONE_NUMBER>000000 R09: ffffa67a003fbc10
[ 1884.616109] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616111] R10:<PHONE_NUMBER>000003 R11: ffffffff8f0ca868 R12: 00000000c1b930ff
[ 1884.616114] R13:<PHONE_NUMBER>000000 R14: ffff9628c4236b08 R15:<PHONE_NUMBER>000001
[ 1884.616117] FS:<PHONE_NUMBER>000000(0000) GS:ffff962df6c40000(0000) knlGS:0000000000000000
[ 1884.616120] CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
[ 1884.616121] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616123] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616123] CR2: 000055d5845840e8 CR3: 00000001b54a0000 CR4:<PHONE_NUMBER>3506e0
[ 1884.616127] Call Trace:
[ 1884.616131]  <TASK>
[ 1884.616134] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616137] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616148] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616133]  ? rtw_power_mode_change+0xe6/0x120 [rtw88_core cd4c35c1cb96ef8ff7489657ccda71e1e812bcf0]
[ 1884.616151] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616162] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616168] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616164]  ? __warn+0x81/0x130
[ 1884.616180] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616183] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616175]  ? rtw_power_mode_change+0xe6/0x120 [rtw88_core cd4c35c1cb96ef8ff7489657ccda71e1e812bcf0]
[ 1884.616194] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616197] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616205]  ? report_bug+0x171/0x1a0
[ 1884.616209] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616211]  ? prb_read_valid+0x1b/0x30
[ 1884.616214] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616217]  ? __x86_return_thunk+0x9/0x10
[ 1884.616223]  ? handle_bug+0x3c/0x80
[ 1884.616227] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616229] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616230]  ? exc_invalid_op+0x17/0x70
[ 1884.616234]  ? asm_exc_invalid_op+0x1a/0x20
[ 1884.616242] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616244] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616256] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616247]  ? rtw_power_mode_change+0xe6/0x120 [rtw88_core cd4c35c1cb96ef8ff7489657ccda71e1e812bcf0]
[ 1884.616259] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616270] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616273] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616275]  rtw_pci_tx_kick_off_queue+0x78/0x80 [rtw88_pci da26097672de40c76b9c46845f387fefb5cb920e]
[ 1884.616285] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616287] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616290]  rtw_pci_tx_kick_off+0x3b/0x50 [rtw88_pci da26097672de40c76b9c46845f387fefb5cb920e]
[ 1884.616299] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616301] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616312] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616303]  rtw_tx_work+0x249/0x280 [rtw88_core cd4c35c1cb96ef8ff7489657ccda71e1e812bcf0]
[ 1884.616316] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616327] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616330] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616336]  process_one_work+0x1c7/0x3d0
[ 1884.616342] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616344]  worker_thread+0x51/0x390
[ 1884.616344] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616350]  ? __pfx_worker_thread+0x10/0x10
[ 1884.616356] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616353]  kthread+0xe8/0x120
[ 1884.616359] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616360]  ? __pfx_kthread+0x10/0x10
[ 1884.616365]  ret_from_fork+0x2c/0x50
[ 1884.616371] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616373] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616380]  </TASK>
[ 1884.616381] ---[ end trace<PHONE_NUMBER>000000 ]---
[ 1884.616384] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616387] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616400] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616403] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616416] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616413] rtw_8822ce 0000:01:00.0: failed to dequeue 236 skb TX queue 1, BD=0x00050018, rp 23 -> 5
[ 1884.616419] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616431] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616434] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616445] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616447] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616458] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616460] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616470] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616473] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616483] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616485] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616495] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616497] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616507] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616510] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616520] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616522] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616532] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616534] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616544] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616546] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616556] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616558] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616568] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616570] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616580] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616582] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616592] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616595] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616605] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616607] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616617] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616619] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616629] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616631] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616641] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616643] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616653] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616655] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616665] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616667] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616677] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616679] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616689] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616691] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616701] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616703] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616713] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616716] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616726] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616728] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616738] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616740] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616750] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616752] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616762] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616764] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616774] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616776] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616786] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616788] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616798] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616800] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616810] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616812] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616822] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616825] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616835] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616837] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616847] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616849] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616859] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616861] pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0
[ 1884.616871] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.616873] pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0
[ 1884.616883] pcieport 0000:00:01.2: AER: can't find device of ID0008
[ 1884.619654] rtw_8822ce 0000:01:00.0: failed to dequeue 18 skb TX queue 1, BD=0x00180018, rp 5 -> 24
[ 1886.555358] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1886.558691] rtw_8822ce 0000:01:00.0: failed to send h2c command
[ 1886.561831] rtw_8822ce 0000:01:00.0: failed to send h2c command
[ 1888.688687] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1888.692036] rtw_8822ce 0000:01:00.0: failed to send h2c command
[ 1890.614969] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1892.745272] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1894.665254] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1894.668543] rtw_8822ce 0000:01:00.0: failed to send h2c command
[ 1894.671685] rtw_8822ce 0000:01:00.0: failed to send h2c command
[ 1896.581895] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[ 1896.585283] rtw_8822ce 0000:01:00.0: failed to send h2c command

firmware failed to leave lps state

can you try this?
https://github.com/lwfinger/rtw88/issues/61#issuecomment-1023821042

That worked! Even in the installer. Added the conf and restarted NetworkManager doing a fresh install as I type this. I didn’t try it based on the other comments in that issue thread saying it didn’t change much for them.

Yeah, we should be able to do that. Can you provide the results of cat /sys/class/dmi/id/*

@daniellasalle can you confirm if this fixes the issue for you as well?

atari-vcs-dmi.txt

Can one of you test this to make sure it runs on your device?
https://github.com/ChimeraOS/device-quirks/pull/75
clone the repo, switch to pastaq/vcs_net branch, then run the file sudo usr/share/device-quirks/id-device
it should detect  the atari vcs and write the config file to /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Yes creating /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf and adding
[connection]
wifi.powersave = 2

then rebooting got the wifi working!
However I am not sure if I am alone with this problem but when pinging an IP the ping replies are very fast as they should be.
Yet when I ping a FQDN it takes some time (10-15 seconds) before the first reply comes in.
I have also tripled checked /etc/resolv.conf and it was populate by DHCP lease I believe.
The real problem is that when I try installing a game using this "working wifi connection" that I still get a "no_internet_error" yet the NetworkManager does show me has connected.
This is looking better and better...

What is your normal DNS?

If by "normal" you mean my ISP's DNS then it is <IP_ADDRESS> which is Bell Canada.
It's also the one in /etc/resolv.conf

Perhaps the problem was related to the RJ45 cable being first plugged in. Then I connected on wifi and lastly unplugged RJ45.
Now I just booted with no RJ45 cable plugged and wifi profile configured and... it works!
Thanks a lot for solving another big one for us <3


(minor bug) long notices become blanc lines

In a function I am building an sql dynamically. This sql becomes a long string. Because of an error The sql is printed with
raise notice '%', sql
Showing an sql of 3250 characters is no problem, but adding some 180 extra characters results in a blank line. When de sql is shortened by changing the raise command to
raise notice '%',left(sql,2000);
does show the first part of the sql. Is it possible to repair this problem by increasing the upper length limit or by truncating the lengthy string and adding some dots (e.g. "lengthy stri...")?

dbeaver Version <IP_ADDRESS>204170718 (Windows)
test function:
CREATE OR REPLACE FUNCTION public.test()
RETURNS void
LANGUAGE plpgsql
AS $function$
declare
i integer;
t_string text;
t_info text;
t_text text;
begin
--string length 100
t_string:='abcdefghijklmnopqrstuvwxyABCDEFGHIJKLMNOPQRSTUVWXYabcdefghijklmnopqrstuvwxyABCDEFGHIJKLMNOPQRSTUVWXY';
t_text:='';
for i in 1..50 loop
t_info:=(i*length(t_string))::text||' characters:';
raise notice '%', t_info;
t_text:=t_text||t_string;
raise notice '%', t_text;
end loop;
END;
$function$
;
Strings with length 3300 and up are not visible. Selecting the text shows that the text is replaced by spaces:

Strangely enough, every single line is visible to me (and the last one actually being 5000 characters long):

Is it possible to verify the output against any other DBMS tool?

I only work with PostgreSQL. What I can do is test the function on another server or test it using the Ubuntu version of dbeaver.

I mean, any other tool like DBeaver, e.g., pgAdmin.

What's your driver version?

I guessed I needed to lookup the ODBC driver version (hence the questionmark). Now I looked up details from dbeaver:

Is this what you need?

Sorry for the confusion. Yes, I was talking about the driver that DBeaver uses.
Unfortunately, I'm still unable to reproduce this issue against the exact driver version.
My last assumption is that this issue is OS-specific. Judging by the L&F, you're using Windows 7. ¯\_(ツ)_/¯

Does the issues still actual for the latest DBeaver version?

Yes (DBeaver updated today), still on Windows 7

Thank you for update.


Bladebit runs 7% slower on Fedora-35 and Ubuntu-21.10 compared to RHEL-8.4

1) Problem
Bladebit runs 7% slower on Fedora-35 and Ubuntu-21.10 compared to RHEL-8.4

2) Test description
I installed these 3 distributions on the SAME machine and run 5 plots.
And I also used the same bladebit executable on all three (mounted from 2nd drive).
These are results:

2a) RHEL-8.4, Kernel 4.18.0-305.25.1.el8_4.x86_64
124044.12443.out:Finished plotting in 350.49 seconds (5.84 minutes).
124044.12443.out:Finished plotting in 344.27 seconds (5.74 minutes).
124044.12443.out:Finished plotting in 343.97 seconds (5.73 minutes).
124044.12443.out:Finished plotting in 345.64 seconds (5.76 minutes).
124044.12443.out:Finished plotting in 360.38 seconds (6.01 minutes).

2b) Fedora-35-server, Kernel 5.14.10-300.fc35.x86_64
2385.29416.out:Finished plotting in 384.14 seconds (6.40 minutes).
2385.29416.out:Finished plotting in 370.80 seconds (6.18 minutes).
2385.29416.out:Finished plotting in 370.82 seconds (6.18 minutes).
2385.29416.out:Finished plotting in 370.98 seconds (6.18 minutes).
2385.29416.out:Finished plotting in 385.65 seconds (6.43 minutes).

2c) Ubuntu-21.10-server, Kernel 5.13.0-21-generic
3603.14006.out:Finished plotting in 382.11 seconds (6.37 minutes).
3603.14006.out:Finished plotting in 367.04 seconds (6.12 minutes).
3603.14006.out:Finished plotting in 366.88 seconds (6.11 minutes).
3603.14006.out:Finished plotting in 367.07 seconds (6.12 minutes).
3603.14006.out:Finished plotting in 382.60 seconds (6.38 minutes).

3) Discussion of results:
- Fedora-35 and Ubuntu-21.10 have comparable performance, about 367-370 seconds
  (Looking into details I would say U21.20 is 3 seconds faster than F35, but that is not topic here).
- RHEL-8.4 runs in ~344 seconds, that is ~25 seconds faster (=7%)

A performance loss of 7% is HUGE and I did not expect this as bladebit
should not put stress on the kernel.

That might explain conflicting benchmark results when comparing
same/different hardware/CPU configs. Until now it was assumed
the Linux distribution has only minor influence. But this proves
choosing a Linux distribution has a major influence on bladebit performance

4) Going further

I would be interested if this is also seen/confirmed by other bladebit users ?

What could be causing this performance regression?

This has indeed been like this from the beginning. Bladebit was originally mainly developed on Amazon Linux 2, which is based on RHEL, and consistently got better times than Ubuntu when testing on the same machine.
I have not tested CentOS, so I would be curious what times are obtained there, and if it is comparable to RHEL times.
As for the reasoning, I'd like to know myself, but it could be a number of things, starting with each distro including different versions of GCC.  Though I suspect that might not be it. Have you tried tests with clang to see what times you get?
I'd love to hear what @mocksoul has to say as his more in-depth Linux expertise.

I run only my one "golden" self-compiled executable (AVX) on all three distributions, so GCC/Clang are out of scope.
But it uses the distribution-specific libraries:
ldd bladebit
linux-vdso.so.1 (0x00007fff64fa9000)
libnuma.so.1 => /lib64/libnuma.so.1 (0x00007f4028b10000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f402877b000)
libm.so.6 => /lib64/libm.so.6 (0x00007f40283f9000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f40281e1000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4027fc1000)
libc.so.6 => /lib64/libc.so.6 (0x00007f4027bfc000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4028d1c000)

Yes but the distros usually have different versions of GCC, which will yield different outputs, as will Clang.

Looking into the details where the performance is lost:
1a) RHEL-8.4
119	Finished F1 generation in 1.33 seconds.
121	Finished F1 sort in 7.24 seconds.
124	  Finished pairing L/R groups in 8.5250 seconds. Created<PHONE_NUMBER> pairs.
127	  Finished computing Fx in 8.1830 seconds.
143	  Finished sorting in 13.09 seconds.
144	Finished forward propagating table 2 in 30.13 seconds.
147	  Finished pairing L/R groups in 8.4670 seconds. Created<PHONE_NUMBER> pairs.
150	  Finished computing Fx in 8.6370 seconds.
152	  Finished sorting in 13.58 seconds.
153	Finished forward propagating table 3 in 31.00 seconds.
156	  Finished pairing L/R groups in 8.4410 seconds. Created<PHONE_NUMBER> pairs.
159	  Finished computing Fx in 8.8220 seconds.
161	  Finished sorting in 13.47 seconds.
162	Finished forward propagating table 4 in 31.04 seconds.
165	  Finished pairing L/R groups in 8.4570 seconds. Created<PHONE_NUMBER> pairs.
168	  Finished computing Fx in 8.8040 seconds.
170	  Finished sorting in 13.42 seconds.
171	Finished forward propagating table 5 in 30.99 seconds.
174	  Finished pairing L/R groups in 8.4600 seconds. Created<PHONE_NUMBER> pairs.
177	  Finished computing Fx in 8.4870 seconds.
179	  Finished sorting in 12.95 seconds.
180	Finished forward propagating table 6 in 30.20 seconds.
183	  Finished pairing L/R groups in 8.4330 seconds. Created<PHONE_NUMBER> pairs.
186	  Finished computing Fx in 8.0270 seconds.
187	Finished forward propagating table 7 in 16.77 seconds.
188	Finished Phase 1 in 178.70 seconds.
191	  Finished prunning table 6 in 0.34 seconds.
193	  Finished prunning table 5 in 7.55 seconds.
195	  Finished prunning table 4 in 7.20 seconds.
197	  Finished prunning table 3 in 7.07 seconds.
199	  Finished prunning table 2 in 7.02 seconds.
200	Finished Phase 2 in 29.47 seconds.
203	  Finished compressing tables 1 and 2 in 20.72 seconds
206	  Finished compressing tables 2 and 3 in 21.52 seconds
209	  Finished compressing tables 3 and 4 in 21.36 seconds
212	  Finished compressing tables 4 and 5 in 21.69 seconds
215	  Finished compressing tables 5 and 6 in 22.77 seconds
218	  Finished compressing tables 6 and 7 in 27.23 seconds
220	Finished Phase 3 in 135.30 seconds.
223	  Finished writing P7 in 0.45 seconds.
225	  Finished writing C1 table in 0.00 seconds.
227	  Finished writing C2 table in 0.00 seconds.
229	  Finished writing C3 table in 0.34 seconds.
230	Finished Phase 4 in 0.80 seconds.
231	Finished plotting in 344.27 seconds (5.74 minutes).
1b) Ubuntu
119	Finished F1 generation in 1.33 seconds.
121	Finished F1 sort in 6.88 seconds.
124	  Finished pairing L/R groups in 8.5860 seconds. Created<PHONE_NUMBER> pairs.
127	  Finished computing Fx in 8.2450 seconds.
143	  Finished sorting in 15.91 seconds.
144	Finished forward propagating table 2 in 33.09 seconds.
147	  Finished pairing L/R groups in 8.3990 seconds. Created<PHONE_NUMBER> pairs.
150	  Finished computing Fx in 8.5450 seconds.
152	  Finished sorting in 17.28 seconds.
153	Finished forward propagating table 3 in 34.52 seconds.
156	  Finished pairing L/R groups in 8.3750 seconds. Created<PHONE_NUMBER> pairs.
159	  Finished computing Fx in 8.9210 seconds.
161	  Finished sorting in 17.23 seconds.
162	Finished forward propagating table 4 in 34.82 seconds.
165	  Finished pairing L/R groups in 8.3740 seconds. Created<PHONE_NUMBER> pairs.
168	  Finished computing Fx in 8.9600 seconds.
170	  Finished sorting in 17.22 seconds.
171	Finished forward propagating table 5 in 34.85 seconds.
174	  Finished pairing L/R groups in 8.3700 seconds. Created<PHONE_NUMBER> pairs.
177	  Finished computing Fx in 8.6860 seconds.
179	  Finished sorting in 15.92 seconds.
180	Finished forward propagating table 6 in 33.27 seconds.
183	  Finished pairing L/R groups in 8.4050 seconds. Created<PHONE_NUMBER> pairs.
186	  Finished computing Fx in 8.2180 seconds.
187	Finished forward propagating table 7 in 16.92 seconds.
188	Finished Phase 1 in 195.68 seconds.
191	  Finished prunning table 6 in 0.33 seconds.
193	  Finished prunning table 5 in 7.63 seconds.
195	  Finished prunning table 4 in 7.28 seconds.
197	  Finished prunning table 3 in 7.14 seconds.
199	  Finished prunning table 2 in 7.09 seconds.
200	Finished Phase 2 in 29.72 seconds.
203	  Finished compressing tables 1 and 2 in 21.88 seconds
206	  Finished compressing tables 2 and 3 in 22.42 seconds
209	  Finished compressing tables 3 and 4 in 22.62 seconds
212	  Finished compressing tables 4 and 5 in 23.04 seconds
215	  Finished compressing tables 5 and 6 in 24.16 seconds
218	  Finished compressing tables 6 and 7 in 26.69 seconds
220	Finished Phase 3 in 140.82 seconds.
223	  Finished writing P7 in 0.47 seconds.
225	  Finished writing C1 table in 0.00 seconds.
227	  Finished writing C2 table in 0.00 seconds.
229	  Finished writing C3 table in 0.35 seconds.
230	Finished Phase 4 in 0.82 seconds.
231	Finished plotting in 367.04 seconds (6.12 minutes).

Discussion of results

Each sort loses 3-4 seconds, causing phase1 to lose 15seconds
compressing tables loses ~1 seconds each

So the main loss is in "sorting".

Yes but the distros usually have different versions of GCC, which will yield different outputs, as will Clang.

I compiled only once (some weeks ago with RHEL-8.x)
md5sum bladebit
9da6366fbd61e7902509076add3d4ddc  bladebit
The SAME executables runs fine on all 3 distributions (of course it uses the system libraries as shown with ldd which are different)

Oh. Your RHEL-compiled exe was ABI compatible with Ubuntu?

Oh. Your RHEL-compiled exe was ABI compatible with Ubuntu?

Yes!


Remove references to Tuist Cloud and update the pricing model

We are flattening Tuist Cloud features into Tuist (e.g. Tuist Cache, Tuist Tests) and rolling out a new pricing model. This PR updates the website to reflect those changes.

Looks good!


Add Personal Photo to Home Page Mobile

The home page doesn't look very personal or light.
A photo should be added of myself to try increase conversion.
Inspiration should be taken from other portfolios.
Opera's website has a great example of how this could be implemented.

Blocked pending results of #89


Delete Conversation Reference from ConversationIdFactory when SkillDialog receives EndOfConversation while using ExpectReplies

Fixes https://github.com/microsoft/botbuilder-js/issues/2712

Pull Request Test Coverage Report for Build 168503

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 83.37%

Totals

Change from base Build 167849:
0.08%

Covered Lines:
15521

Relevant Lines:
17710

💛  - Coveralls


checkbox color changes accent color

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.0.12
Describe the bug
changing the checkbox color changes many different parts of the theme (seems to override the accent color?) with 'colorful active states' turned on (minimal theme settings > features)
https://user-images.githubusercontent.com/99437376/195996665-7f41ff33-5bcd-490e-ae63-b947ed90ad7d.mp4
Debug info
SYSTEM INFO:
Obsidian version: v1.0.0
Installer version: v0.15.9
Operating system: Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64 21.6.0
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal
Snippets enabled: 0
Restricted mode: off
Plugins installed: 15
Plugins enabled: 11
1: Natural Language Dates v0.6.1
2: Emoji Shortcodes v2.1.2
3: Omnisearch v1.6.4
4: Periodic Notes v0.0.17
5: Tag Wrangler v0.5.3
6: Advanced URI v1.28.2
7: Calendar v1.5.10
8: Style Settings v0.4.12
9: Dataview v0.5.47
10: Hider v1.2.3
11: Minimal Theme Settings v6.0.5
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Closed in 6.0.13
https://github.com/kepano/obsidian-minimal/releases/tag/6.0.13

However the new interactive-accent variable cannot be found anywhere in the settings. I opened a new issue #455 to address this.


tf.keras.layers.Conv2dTranspose doesn't support different dilation_rate

System information.
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)
TensorFlow 2.0.0 installed by anaconda
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
NVIDIA-SMI 460.80 Driver Version: 460.80 CUDA Version: 11.2
Describe the problem.
While using tf.keras.layers.Conv2dTranspose with dilation param setting different values for row and columns, it turns out to be a bug. Inferred from the error info, there exists an assert that dilation[0] has to be equal to dilation[1], however, that conflicts with the documentation and I suggest that there's no reason for not supporting various values for dilation. If I am wrong, please correct me and maybe the documentation should be revised, or maybe the function should be improved.
Describe the current behavior.
While using tf.keras.layers.Conv2dTranspose with dilation param setting different values for row and columns, it turns out to be a bug. Inferred from the error info, there exists an assert that dilation[0] has to be equal to dilation[1].
Describe the expected behavior.
Different values for dilation param accross different axes should be support, or, documentation should be revised.
Standalone code to reproduce the issue.
e.g.
conv2d_transpose = tf.keras.layers.Conv2DTranspose(32, (3, 2), (1, 1), 'valid', dilation_rate=(1, 2))
print(conv2d_tanspose(np.ones((100, 28, 28, 1), dtype=np.float32)))
Source code / logs.

@beginner401,
Can you share the complete stand alone code or colab gist to reproduce the issue? Thanks!

@beginner401 https://colab.research.google.com/gist/beginner401/b5ba37ece87af7a32d5b175be547e3fa/github15677.ipynb
Just code like above can trigger this bug. If the link is invalid, just try to run code below:
import tensorflow as tf
import numpy as np
conv2d_transpose = tf.keras.layers.Conv2DTranspose(32, (3, 2), (1, 1), 'valid', dilation_rate=(1, 2))
print(conv2d_transpose(np.ones((100, 28, 28, 1), dtype=np.float32)))

I am able to reproduce the reported issue with Conv2dTranspose. Please find the gist here. Thanks!

Triage notes: we should update the docs. It looks like currently variable rates not supported because the underlying tensorflow op does not support it.


Support for HTMLBars and Handlebars

support for using https://atom.io/packages/language-ember-htmlbars and this package

Ooooh, that's great. When you have the other package installed do you see no ember-template-linter errors?
I have one small style point and then I'm happy to release!

@TNAJanssen having this same issue and happy that you already fixed! Could you make the changes requested by @binhums ?
Thanks guys!

@williamweckl thanks for the bump. I'll get this merged now.

Released in https://github.com/binhums/linter-ember-template/releases/tag/v0.1.5 thanks for being patient.

:D amazing job! thank you!


feat: add oil.nvim extension to show current directory

Show a current directory when opening an oil.nvim buffer
Preview

lgtm. thanks for your contribution.


[Question] Is there a way to access the event from a state that caused the transition to the current state?

I'm looking for the best way to pass data from one state to another. I understand one way to do it is to use the global blackboard but I was wondering if the data can be passed through the events from the source state to the destination state? I think it'll be particularly useful in the following scenario:
The current state acts as an adapter/api for accepting mission goals. It then generates event to transition to the appropriate state (example a state to go to a goal pose) to complete the mission. It would be great if the adapter state can pass additional data in the event (example goal pose) to the destination state.
if its not possible to pass data through events, what is the use of the data fields in some of the default events?
┆Issue is synchronized with this Jira Task by Unito

Hello @sukhrajklair,
Thanks for the excellent question.
Ok, so the general way we've approached this is through the use of components attached to specific clients.
Going with the example you outlined above, let's name the two states StGoalEvaluator and StGoalExecutor. I'm imagining a process where StGoalEvaluator would receive and evaluate a new goal request. If the evaluation of the request succeeds, then the state would throw a success event (which it could transition on to StGoalExecutor) and during onExit, write the accepted goal to a goal queue component attached to the Nav2z Client (for instance) in the Navigation Orthogonal. The next state would select the goal from the queue and navigate to the goal pose.
Here are some components we've written before for the Nav2z Client Behavior Library that may have some of the functionality you're looking for...
https://github.com/robosoft-ai/SMACC2/tree/humble/smacc2_client_library/nav2z_client/nav2z_client/include/nav2z_client/components
This state and client behavior may also give you some inspiration...
https://github.com/robosoft-ai/SMACC2/blob/humble/smacc2_sm_reference_library/sm_dance_bot_warehouse_2/include/sm_dance_bot_warehouse_2/states/st_navigate_undo_motion.hpp
https://github.com/robosoft-ai/SMACC2/blob/humble/smacc2_client_library/nav2z_client/nav2z_client/include/nav2z_client/client_behaviors/cb_undo_path_backwards.hpp
And can be seen in this demo...
https://www.youtube.com/watch?v=A3kmCQS_ww8
Regarding the use of the data fields in the events, the main purpose of the fields is to identify which runtime object threw a given event, and from what Orthogonal (to account for multiple instances of a given runtime object, say for instance in the case of a two arm robot that uses two instances of Moveit) or State (in the case of state reactors) the event was thrown from.
I suppose it would be possible to create different events able to carry other data, but I'd need to hear the specific use case first.

I hadn't thought of using components but now I can see how they can be used to carry data between states. Thanks for the suggestion and examples.


cargo-metadata does not work with Tokio's gated imports

Problem
cargo-metadata --all-features does not list Tokio's modules that are gated behind various feature flags.
Steps

Run cargo-metadata --all-features
Observe abscence of files in the runtime folder.

Notes
Tokio's feature gating is implemented by wrapping imports in macros that contain feature and docs attributes. This is probably the cause of the issue.

cargo metadata doesn't list files in a crate as far as I know - are you using some thing other than cargo's built in subcommand?

Closing since it doesn't look like this is related to Cargo directly.  Feel free to reopen if you can put together a repro, but it is also not clear to me which files you are referring to.  I'm also unclear about the dash in cargo-metadata, cargo's commands are space-separated.


Remove the config_policies_evaluation_duration metric from the test

This was removed as part of making config-policy-controller event-driven.

/test test-e2e-grc-framework

/override test-e2e-grc-framework

/override ci/prow/test-e2e-grc-framework


discuss if it makes sense to remove payment checks inside _handleFunds

if a receiver is a smart contract that rejects the money, the nft can't be sold anymore by anyone

As discussed in #15, removing payment checks doesn't provided any extra security. We therefore keep them to prevent good-faith errors in Ether receiver contracts.


Use getmypid() which also works on Windows

The previous implementation uses posix_getpid, which doesn't work on Windows. Since this package doesn't use any other POSIX features, I'd suggest switching it to a more portable getmypid instead 😃
For more information:

https://secure.php.net/manual/en/function.getmypid.php
https://secure.php.net/manual/en/function.posix-getpid.php
https://stackoverflow.com/questions/1176012/difference-between-getmypid-and-posix-getpid

Hey @ariefwt
Thanks a lot, it is a good reason.
But, I will not to merge it right now, because I need to check back compatibility.
I want to be sure, that it changes will not break something in working projects.
Therefore, I will write tests for it soon.

@cheprasov May be we could develop a bunch of tests and mocks in order to automate this. If you want to talk we could design something.

@ariefwt @manuelbcd
Sorry, I was on vacation.
It is done.


Query action is not suggested

Description:

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This hasn't previously been solved completely. Will be fixed by #29761


TensorFlow Serving ks generate tf-serving-service mnist-service prototype name not found

I am working through the following guide: https://www.kubeflow.org/docs/components/tfserving_new/
The very first step here fails (ks generate tf-serving-service mnist-service).
Firstly, if used exactly as above this will result in the following error:
ERROR finding app root from starting path: : unable to find ksonnet project
So it is necessary to first create a ks project and cd to the project folder:
ks init myproject
cd myproject
ks generate tf-serving-service mnist-service

This will then result in the following error:
ERROR no prototype names matched 'tf-serving-service'

EDIT
I was able to overcome this issue with the following fixes:
Add the kubeflow registry in order to gain access to the necessary prototypes:
ks registry add kubeflow github.com/google/kubeflow/tree/master/kubeflow
export GITHUB_TOKEN=<my generated token> # to avoid "rate limit execeed" error. See https://github.com/ksonnet/ksonnet/blob/master/docs/troubleshooting.md
ks pkg install kubeflow/tf-serving@master # NOTE, this is tf-serving, not tf-serving-service

And then followed by ks generate tf-serving mnist-service

This issue is now resolved, as the guide no longer uses ksonnet.
https://www.kubeflow.org/docs/components/serving/tfserving_new/
/close


Improved error mapping and tightened checks in rdg_process_packet

For a better error description if something with a gateway connection fails.
Fixed redirection with gateway, do not try to resolve FQDN or NETBIOS names

@Olen This might help you diagnosing your issue, as it should now print some details about the error (at least more than the error code)

Great.
I will test it on Monday if the nightly build succeeds

@Olen sorry, not merged yet ;)

Hope this can be merged soon...
Looking forward to testing

@mfleisz the buffers in the bitmap to string functions are large enough to hold all strings values at once. All data is constant, so no external influence can cause an overflow here. (too bad there is no proper strcat version with source and destination length though)

@MartinHaimberger Ok, added functions for each response to map.

LGTM now

After the latest build, ALL security-protocols fails:
Tested with:
[09:08:46:626] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[09:08:46:626] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[09:08:46:626] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: FALSE
[09:08:46:627] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[09:08:46:627] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: FALSE
[09:08:46:627] [17563:17564] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: TRUE
[09:08:46:627] [17563:17564] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_EXT
[09:08:46:627] [17563:17564] [DEBUG][com.freerdp.core.nego] - Attempting NLA extended security

[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: FALSE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[09:08:59:901] [17677:17678] [DEBUG][com.freerdp.core.nego] - Attempting NLA security

[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: FALSE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: FALSE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_TLS
[09:09:16:509] [17804:17805] [DEBUG][com.freerdp.core.nego] - Attempting TLS security

[09:09:27:025] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[09:09:27:025] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[09:09:27:025] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[09:09:27:025] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[09:09:27:026] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: FALSE
[09:09:27:026] [17911:17913] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[09:09:27:026] [17911:17913] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_RDP
[09:09:27:026] [17911:17913] [DEBUG][com.freerdp.core.nego] - Attempting RDP security
No matter what security-settings, they all bail out with the same error:
[09:09:27:029] [17911:17913] [DEBUG][com.freerdp.core] - connecting to peer <IP_ADDRESS>
[09:09:27:047] [17911:17913] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[09:09:27:047] [17911:17913] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[09:09:27:051] [17911:17913] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[09:09:27:058] [17911:17913] [DEBUG][com.freerdp.core.gateway.rdg] - RDG_OUT_DATA authorization result: 200
[09:09:27:059] [17911:17913] [DEBUG][com.freerdp.core] - connecting to peer <IP_ADDRESS>
[09:09:27:075] [17911:17913] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[09:09:27:075] [17911:17913] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[09:09:27:080] [17911:17913] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[09:09:27:086] [17911:17913] [DEBUG][com.freerdp.core.gateway.rdg] - RDG_IN_DATA authorization result: 200
[09:09:27:090] [17911:17913] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[09:09:27:090] [17911:17913] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[09:09:27:090] [17911:17913] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

@Olen looks like this one slipped through, fixed with #5064

Thanks.
Waiting for another nightly RPM then...

Just tested the latest nightly build, and now it comes one (or a couple of) step(s) further, but still no cigar...
Trying to connect with options that works fine in freerdp-2.0.0-41.20180405gita9ecd6a
[12:28:35:856] [11494:11497] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[12:28:35:856] [11494:11497] [DEBUG][com.freerdp.core.nla] - nla_client_init 349 : packageName=Kerberos ; cbMaxToken=48000
[12:28:35:856] [11494:11497] [TRACE][com.freerdp.core.nla] -  InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[12:28:35:856] [11494:11497] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[12:28:35:856] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0000 4e 54 4c 4d 53 53 50 00 01 00 00 00 b7 82 08 e2 NTLMSSP.........
[12:28:35:856] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[12:28:35:856] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0020 06 01 b1 1d 00 00 00 0f                         ........
[12:28:35:861] [11494:11497] [DEBUG][com.freerdp.core.nla] - CredSSP protocol support 6, peer supports 6
[12:28:35:861] [11494:11497] [TRACE][com.freerdp.core.nla] - InitializeSecurityContext  SEC_I_COMPLETE_NEEDED [0x00090313]
[12:28:35:861] [11494:11497] [ERROR][com.winpr.sspi] - EncryptMessage status SEC_E_INVALID_TOKEN [0x80090308]
[12:28:35:861] [11494:11497] [ERROR][com.freerdp.core.nla] - EncryptMessage status SEC_E_INVALID_TOKEN [0x80090308]
[12:28:35:861] [11494:11497] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[12:28:35:861] [11494:11497] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[12:28:35:861] [11494:11497] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[12:28:35:861] [11494:11497] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]

Here it hangs for about 1,5 minutes while I see that cpu-usage spikes, before it errors out with:

[12:30:06:020] [11494:11497] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
[12:30:06:020] [11494:11497] [DEBUG][com.freerdp.core.transport] - transport_check_fds: transport_read_pdu() - -1
[12:30:06:020] [11494:11497] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: FALSE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[12:30:06:046] [11494:11497] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[12:30:06:048] [11494:11497] [DEBUG][com.freerdp.core] - connecting to peer <IP_ADDRESS>
[12:30:06:064] [11494:11497] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[12:30:06:064] [11494:11497] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[12:30:06:072] [11494:11497] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[12:30:06:085] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - RDG_OUT_DATA authorization result: 200
[12:30:06:085] [11494:11497] [DEBUG][com.freerdp.core] - connecting to peer <IP_ADDRESS>
[12:30:06:101] [11494:11497] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[12:30:06:101] [11494:11497] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[12:30:06:106] [11494:11497] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[12:30:06:112] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - RDG_IN_DATA authorization result: 200
[12:30:06:116] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - Handshake response received
[12:30:06:116] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - errorCode=RPC_S_OK [0x00000000], verMajor=1, verMinor=0, serverVersion=0, extendedAuth=HTTP_EXTENDED_AUTH_NONE [0x0000]
[12:30:06:120] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - Tunnel response received
[12:30:06:120] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - serverVersion=0, errorCode=RPC_S_OK [0x00000000], fieldsPresent=HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]
[12:30:06:141] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - Tunnel authorization received
[12:30:06:141] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - errorCode=RPC_S_OK [0x00000000], fieldsPresent=HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]
[12:30:06:159] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - Channel response received
[12:30:06:159] [11494:11497] [DEBUG][com.freerdp.core.gateway.rdg] - channel response errorCode=RPC_S_OK [0x00000000], fieldsPresent=HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]|HTTP_TUNNEL_RESPONSE_FIELD_TUNNEL_ID|HTTP_TUNNEL_RESPONSE_FIELD_CAPS|HTTP_TUNNEL_RESPONSE_FIELD_SOH_REQ| [0007]|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_REDIR_FLAGS|HTTP_TUNNEL_AUTH_RESPONSE_FIELD_IDLE_TIMEOUT| [0003]|HTTP_CHANNEL_RESPONSE_FIELD_CHANNELID|HTTP_CHANNEL_RESPONSE_OPTIONAL|HTTP_CHANNEL_RESPONSE_FIELD_UDPPORT [0007]
[12:30:06:159] [11494:11497] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[12:30:06:178] [11494:11497] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP
[12:30:06:178] [11494:11497] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[12:30:06:178] [11494:11497] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[12:30:06:178] [11494:11497] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[12:30:06:178] [11494:11497] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[12:30:06:193] [11494:11497] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[12:30:06:194] [11494:11497] [DEBUG][com.freerdp.core.nla] - nla_client_init 349 : packageName=Kerberos ; cbMaxToken=48000
[12:30:06:194] [11494:11497] [TRACE][com.freerdp.core.nla] -  InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[12:30:06:194] [11494:11497] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[12:30:06:194] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0000 4e 54 4c 4d 53 53 50 00 01 00 00 00 b7 82 08 e2 NTLMSSP.........
[12:30:06:194] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[12:30:06:194] [11494:11497] [DEBUG][com.freerdp.core.nla] - 0020 06 01 b1 1d 00 00 00 0f                         ........
[12:30:06:198] [11494:11497] [DEBUG][com.freerdp.core.nla] - CredSSP protocol support 6, peer supports 6
[12:30:06:198] [11494:11497] [TRACE][com.freerdp.core.nla] - InitializeSecurityContext  SEC_I_COMPLETE_NEEDED [0x00090313]
[12:30:06:198] [11494:11497] [ERROR][com.winpr.sspi] - EncryptMessage status SEC_E_INVALID_TOKEN [0x80090308]
[12:30:06:198] [11494:11497] [ERROR][com.freerdp.core.nla] - EncryptMessage status SEC_E_INVALID_TOKEN [0x80090308]
[12:30:06:198] [11494:11497] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[12:30:06:198] [11494:11497] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
[12:30:06:198] [11494:11497] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[12:30:06:198] [11494:11497] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[12:30:06:198] [11494:11497] [ERROR][com.freerdp.core] - freerdp_post_connect failed

@Olen Ok, now I need your full command line and gateway configuration.
Best open a new issue for that with all the information required as this seems to be another issue than the one discussed here (although from your point of view the outcome is the same)


Enable tp ops needed in ViT model with unit test

FYI this is the torch_function addition, I hope we can move contiguous and view_with_sharding_dim_change to the functional op instead. https://github.com/pytorch/PiPPy/pull/328


Swagger UI is sending request as http instead of https after upgrading Swashbuckle.AspNetCore nuget package to 5.6.0

Hi,
I'm experiencing this issue after I upgraded the Swashbuckle.AspNetCore nuget package to 5.6.0 from 5.5.0. Swagger UI seems to be sending the request over http protocol instead of https, although the swagger page itself is hosted on https.

It throws TypeError: Failed to fetch.
The difference that I noticed on swagger page before and after upgrading the package is as below:
Before:

After:

Before upgrading the package, it didn't have the servers array in the response which, I believe, might be related to the change that was released in 5.6.0:
Better support for reverse proxy environments, incl. assigning servers metadata based on the presence of common reverse proxy headers

Also, notice that the server url has the http scheme instead of https. Please let me know if there is any other information needed.

I've been seeing the same issue, it's throwing CORs errors on the console

I am seeing the same issue after updating

Same issue here

By updating the version to 6.1.1 resolved the issue for me.

I have the same issue on 6.1.1

I just added a
                options.PreSerializeFilters.Add((document, request) =>
                {
                    var scheme = request.Host.Host.StartsWith("localhost", StringComparison.OrdinalIgnoreCase)
                        ? "http"
                        : "https";
                    document.Servers = new[]
                    {
                        new OpenApiServer
                        {
                            Url = $"{scheme}://{request.Host}"
                        }
                    };
                });

to get around the issue

Encountered the same issue on v6.2.1

Closing this out due to age - if you're still experiencing this problem with the latest version of Swashbuckle please open a new issue.


lndconnect doesn't connect with iOS app.

Description
QR will not connect node to the iOS app., it doesn't do anything. I have copied and pasted the info to connect and it still won't.

Zap version: 0.4.0 beta
Operating System and version: windows 10

@luvarado please can you provide exact steps to replicate your issue? Please include:

exactly what you are trying to do
what you think should happen
what is actually happening
as many details as you can about the lnd node that you are connected to

I am trying to connect to my node remotely using the same network.

It should connect to the IOS app by the camera picking up on the QR code.

As i hold camera to the lndconnect QR it doesn't do anything, it will not recognize the QR.

@luvarado which QR code are you trying to scan? One that you generated yourself using lndconnect, or the one that we display from within the desktop app?

I am trying to connect to my node remotely using the same network.

What IP address is your lnd node on?
What IP address is Zap Desktop running on?
What network is your iPhone connected to (The Internet or the same LAN where your lnd node is running)?
Does your phone have access to the lnd node?
Can you connect using https://github.com/LN-Zap/lndconnect directly?

It is the one from the desktop app.
On Tuesday, April 2, 2019, 3:29:05 PM CDT, Tom Kirkpatrick<EMAIL_ADDRESS>wrote:
@luvarado which QR code are you trying to scan? One that you generated yourself using lndconnect, or the one that we display from within the desktop app?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@luvarado please can you share the Lnd Connect QR Code string with me (found directly under the QR code).
Please be sure to delete the macaroon part of the string as this is sensitive data.
You can DM to me in Slack if you prefer not to paste here.
The main thing I want to know is what IP address and host it is using.
Thanks/

Closing this issue due to inactivity. Please reopen if this is still an issue for you. Thanks.


[BUG]: Autoscroll Does Not Scroll To Newline

Description
Auto scroll does not scroll left when returning to a newline.
(optional) What browsers are you seeing the problem on?
Firefox

Find a snippet with multiple lines.
Reduce window size.
Type to end of line without enter
Type to newline.
Backspace to previous line.
Type to newline without enter.

Play around with it. You will find the issue.


improve documentation about source map for libraries

Feature to document

The sourcemaps have some crazy webpack://rxjs/./src/... URLs in them. I'm not sure what that's about, but I'd like to be able to clean that up to just be relative URLs like ./src/...

I think we need provide example how configure webpack to generate source map for libraries on this page https://webpack.js.org/guides/author-libraries/
Author(s)
No matter
Additional information
Ref: https://github.com/webpack/webpack/issues/8352#issue-378520725

Hello, is this open to work on?

@dhuang612 yes please!

Looking into it.

Is there any progress on this content?  I may should have time for contributions.

@chrisVillanueva , since it is not being worked on by anyone , you most welcome to open a pr
Welcome :)


2 versions available on osx while choosing open with

On OSX 10.11.6 (15G1611)
When I right-click and choose open with I get this

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
[Description of the issue]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/11047. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


MRTK-Quest prefab instance problems with Unity 2020.3.24

Describe the bug
After importing MRTK 2.7.2 into Unity 2020.3.24 and trying to open one of the MRTK-Quest prefabs I get these error messages:
Prefab instance problem: MRTK-Quest_OVRCameraRig (Missing Prefab with guid: 126d619cf4daa52469682f85c1378b4a)
Prefab instance problem: MRTK-Quest_HandsPrefab (Missing Prefab with guid: 835e735ca71bf78459fb2cababd74112)
Prefab instance problem: MRTK-Quest_LocalAvatar (Missing Prefab with guid: 84c8b8609f9bb434eaf5248f17ff1293)

To reproduce

Import MRTK 2.7.2 into a Unity 2020.3.24 project
Open one of the MRTK-Quest prefabs
Observe errors about missing components

Expected behavior
I'd expect all the prefab components to exist.
Your setup (please complete the following information)

Unity Version 2020.3.24
MRTK Version 2.7.2

Target platform (please complete the following information)

Unity Editor

I believe this is expected if Oculus' Unity integration package isn't installed, but @RogPodge would know best!

Yeah, those MRTK prefabs utilize prefabs that are located in the Oculus Integration package. Be sure to follow these steps to configure MRTK to deploy to the oculus quest

Let us know if those steps are out of date or if you are still encountering issues afterwards!

Oh, alright. We don't deploy to Quest right now so I guess that's why I never noticed this before.
Wouldn't it be better if those prefabs lived in the Oculus integration package then? It'd prevent some confusion for sure, because once I got these error messages right after importing MRTK into a blank project. Doesn't happen always though.

We're not directly plugged into the decision making on Oculus Quest's side of things, and because those prefabs take a dependency on MRTK packages I don't think it's quite feasible.


Split big map into smaller pcd files

I understand that the question has been discussed here #319 . However, the answer was not conclusive to me. I have a big bag file and it has been split into several smaller bag files. I can produce pcd files from the these smaller bag files. Based on the discussion of #319 , I will need to transform pcd files manually.
Here is my question: how do I transform the pcd files. Assuming I have pcd1 and pcd2, what I am thinking is that I use ndt of PCL to determine the rigid transformation between pcd1 and pcd2, and then apply the transformation to pcd2 and save it as a new pcd (transformed pcd). Is this approach correct? Thanks a lot for the help.

Your approach is correct. I think that local2global node in ndt_localizer package may help you. The node does similar things you mentioned.

Thanks a lot for the answer. I am trying to figure out how to use the local2global node but still facing some issues. Assuming I have 5 pcd fils generated from 5 separate bag files, 001.pcd, 002.pcd, ... 005.pcd. First, I run
rosrun ndt_localizer local2global ~/002.pcd 0 0 0 0 0 0
And then, I use Autoware to load the map 001.pcd. local2gloabl node will generate a "global_map.pcd", which is the transformed version of 002.pcd, and  parameters.
After that, I run
rosrun ndt_localizer local2global ~/003.pcd
and use Autoware to load map "global_map.pcd". The local2global node will generate a new "global_map.pcd" which is the transformed version of 003.pcd, and a new set of . This continues until 005.pcd. Are these steps correct? Thanks a lot!

If you have five separate PCD files, you have to run local2global five times. You can modify the source code for convenience.

@Benjaminmar8 I'm try to use your method above to stitching the pcd mapps, but  I can't get correct map, have you get a correct map?

@Benjaminmar8 @kitsukawa  @thomas3016 is the problem resolved? I am going to submit a patch to resolve the problem, i.e. split a large PCD file (1 GB) to small files (tens of MB). Please let me know if you want my solution, or there is already a solution there.

@yiakwy I think you can solve the problem using PCD Grid Divider in Autoware.
https://github.com/CPFL/Autoware/tree/master/ros/src/util/packages/map_tools

Roger. I will try to use it later. However, we are currently using PCL to process PCD data and I have little ideas about Autoware.
I just scanned the codes and find that the following codes do the job.
    for (int i = 0; i < grid_num; i++) {
      if (grids[i].cloud.points.size() > 0) {
        pcl::io::savePCDFileBinary(grids[i].filename, grids[i].cloud);
        std::cout << "Wrote " << grids[i].cloud.points.size() << " points to "
                  << grids[i].filename << "." << std::endl;
        points_num += grids[i].cloud.points.size();
      }
    }
    std::cout << "Total points num: " << points_num << " points." << std::endl;

Could you tell me more about the relationship between PCL and Autoware?

Autoware uses PCL to process point cloud data. i.e. loading pcd, writing point cloud to PCD and so on.

Thank you.

Please see my discussion:
https://github.com/PointCloudLibrary/pcl/issues/2652
Yuki Kitsukawa<EMAIL_ADDRESS>于2018年11月26日周一 下午1:15写道：

Autoware uses PCL to process point cloud data. i.e. loading pcd, writing
point cloud to PCD and so on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CPFL/Autoware/issues/428#issuecomment-441521527, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIHdeNomFn_4186Rv3FAGOuaL7BoR8SSks5uy3kNgaJpZM4Jsp0C
.


cmd: allows full path with cid in ipfs cat

just allows the CID to also include a path
textile ipfs cat QmRmxd8CkXCunorEDmPBpRbB7Qcs6KV9sLfWekCGV2EEKv
or
textile ipfs cat QmbDmGbJmCDwZqjP6wPC7Vh69tbAeQEyp8bBj6rCH79REb/0/f

Whoa, the machine speaks!

ha! that would be amaz. i ran make docs, perhaps that did it?


PLEASE UPDATE FOR GODOT 4.4

please if mybe UPDATE FOR new GODOT

it should be pretty straight forward to port to godot 4.4 .
may be you could try it yourself.

I gotchu friend
also works in 4.4dev2


add featureslist to pluralExceptions

Adds FeaturesList to exceptions.
/cc @deads2k @sjenning

This must merge in openshift/origin


Feature request: agent deploy

Enable client use terraform to deploy any agent on their infra
The reference on this point me to do via elastic cloud console (UI interface) or via API.
It would be great to keep sticky on usual terraform at that time as a client I deploy my infra (EKS, ec2, ...)
Context
The racional behind this is to make an easy landing for that new clients that are looking for a solution like this but consider to have not this feature as -1 at evaluation point.
Thank you for having a look on this request, hope it is useful

@agomezvidalee is the intention here to use the provider to install the Elastic Agent? If so that's outside the scope of this provider, which is solely expected to managed Elastic Cloud resources.

closing as per comment above, this is outside the scope of this provider.


Add hack/release.sh script for release

Description
Release setup for plugin
Changes

Remove build flags as they are not needed for plugin
remove hack/build-flags.sh
update hack/build.sh and remove -ldflags arg
Add hack/release.sh script for release
Run e2e tests against eventing v0.18.6 and serving v0.18.3

/retest
      ┃  34.267s Ingress has not yet been reconciled.
    ┃
    🔥 Error: timeout: service 'sinksvc' not ready after 600 seconds


RESTful actions prefix configuration in blueprints

Fix for #2031 and #2473

Thanks @konstantinzolotarev, looks good!


Translate setup/release/version-skew-policy into Korean

This is a Feature Request

What would you like to be added

Translate setup/release/version-skew-policy into Korean
Why is this needed
No translation setup/release/version-skew-policy into Korean
Comments

Page to Update:
https://kubernetes.io/docs/setup/release/version-skew-policy/

/language ko
/assign

/triage accepted

/close


JAVA-3142: Improving the documentation for remote local dc's feature

This PR is to address code review comment in merged PR

https://github.com/apache/cassandra-java-driver/pull/1896#discussion_r1585228162
https://github.com/apache/cassandra-java-driver/pull/1896#discussion_r1585228162

Thanks for the follow-up @nitinitt !


Revert "drivers: serial: stm32: Make it compatible with runtime PM ....

This reverts commit 1c2d326579ee8cea4c809eb737585537e3482677. which was limited to CONFIG_UART_ASYNC_API=y case and causing regression otherwise.
Fixes #63885

cc @coran21

I can confirm that removing these lines fixed my issue.


initial value as "yyyymmdd" not recognized?

I need to handle the "hidden" value of the control as "yyyymmdd" (as both initial value and also as the value returned to the server) while showing "dd/mm/yyyy" to the user. However when I set, for example date-value='20160504', the initial displayed format reverts to 01/01/1970..
Can this be accomplished?
Relevant Code:
<input           id="input_01" class="datepicker" value="20140808"           name="dtp" type="text" data-value="20140808">
and
var $input = $( '.datepicker' ).pickadate({             format: 'dd/mm/yyyy',             formatSubmit: 'yyyymmdd',             container: '#container',             closeOnSelect: false,             closeOnClear: false,         })

Seems it depends on what type of object the javascript interpreter thinks data-value is. In this case, a yyyymmdd format can be a true number, and my browser was casting it as such. Pickadate's parser is expecting only a string. Adding a '' + num in picker.date.js fixed my case.

@cdsaenz That's a very dangerous pattern to follow. You should always have delimiters in between the formatting units otherwise it's difficult to assert with 100% certainty that it was parsed correctly (for instance if the format is yyyymd and the value is 2014112).
For that reason, this isn't and won't be supported.

@amsul I think the parsability of a format one chooses to use is their own problem. I agree that delimiters are great insurance against misformatted data, but I also do work elsewhere to ensure my dates are formatted accurately.
There may be some valid reasons to use numbers over delimited strings. For example, I am using integers because they're faster to sort and filter.
My simple proposed fix would do nothing to the parser except bring more objects to it. It should have no effect on delimited formats.

@joraff consider it saving developers from themselves 😉 .
Besides, sorting should be done by the actual date time, not the formatted date. I don't see any good reason why delimiters would not be used.


Error reading specification file on 0.13.0

Hey folks,
Pulled down the new gem version today, and it is failing with:
cfndsl-0.13.0/lib/cfndsl/specification.rb:83:in `read': No such file or directory @ rb_sysopen - <HOMEPATH>/.cfndsl/resource_specification.json (Errno::ENOENT)

The magic that happens here: https://github.com/stevenjack/cfndsl/blob/master/bin/cfndsl#L75 only works if directly using the executable CLI. I'm using CfnDsl.eval_file_with_extras directly within ruby, leading to this file not existing.
Thoughts? It seems odd to have this magic configuration in the bin file. Perhaps move the check into https://github.com/stevenjack/cfndsl/blob/d31ba4b82f4f0ecaa83af6060e42b157be3678d4/lib/cfndsl.rb#L58?

Good catch, let me take a look.

@arothian are you happy this issue is now resolved?

Yeah, the fix looks good. Thanks for checking back.


Removed redundancy from control group pages

Microsoft Reviewers: Open in CodeFlow

Closing this for now. Will pick up the necessary fixes and create a new PR.


Rework render engine

Mod version
latest
Minecraft version
1.19.3
Mod loader
Both
Description of the request
I think it's important to recreate the render engine of the Xray itself.
For the story, I've done this one years ago with a basic implementation I remembered from the original Xray, so from a code before the 1.0.0, so before all the optimization.
The new renderer would have these options:

Block ESP (not only entity/block-entity)
Non-xray blocks overlay, to know where we are
Ignore block entities in Xray (but keep them with the previous point)
All-in-one mode list, no difference between the Xray mode and the ESP modes

I'm not working a lot on Xray, so I have no clue when it will be done.
Do I want to contribute to make it?
Yes
Something else?
No response

I like this idea, i've desired a stand alone block esp mod for fabric however the last time i looked for one i couldn't find one on the latest version, i also desire an xray mod in which the environment within my immediate vicinity is visible {4-8 blocks}.


Get Quote of the day by click on the button

Issue Type:

[ ] Bug Report
[x] Feature Request
[ ] Documentaion

Describe the bug
My simple project gives a quote when the user clicks on the button.
Possible solution

Describe the solution you thought of.

Screenshots

Please assign me this issue so I can add the project to your repository.

This project is also already present in the repo