Pcie atomics not enabled, hostcall not supported on gfx1100 RX7900

I tried to use pytorch with ROCm, however it fails with
:1:rocvirtual.cpp           :2902:<PHONE_NUMBER> us: 7740 : [tid:0x7f5681dfb6c0] Pcie atomics not enabled, hostcall not supported
:1:rocvirtual.cpp           :3235:<PHONE_NUMBER> us: 7740 : [tid:0x7f5681dfb6c0] AQL dispatch failed!
HIP error: the operation cannot be performed in the present state

From previous issues in this repository, it seems like PCIe atomics were only a problem with gfx8 GPUs and old CPUs, so I'm wondering why I have this problem. I couldn't find much information about which CPUs support this feature and which don't. Is there a compatibility list somewhere?
ROCm version: 5.6
PyTorch: version: 2.1.0.dev20230901+rocm5.6
GPU: RX 7900 XT
CPU: i5-11400F
dmesg | grep atomic
amdgpu 0000:03:00.0: amdgpu: PCIE atomic ops is not supported

However, I don't get the infamous kfd: PCI rejects atomics

lspci -tv
-[0000:00]-+-00.0  Intel Corporation Device 4c53
           +-01.0-[01-03]----00.0-[02-03]----00.0-[03]--+-00.0  Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX]
           |                                            \-00.1  Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 HDMI/DP Audio
           +-06.0-[04]----00.0  Micron/Crucial Technology P5 Plus NVMe PCIe SSD
           +-14.0  Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller
           +-14.2  Intel Corporation Tiger Lake-H Shared SRAM
           +-15.0  Intel Corporation Tiger Lake-H Serial IO I2C Controller #0
           +-16.0  Intel Corporation Tiger Lake-H Management Engine Interface
           +-17.0  Intel Corporation Device 43d2
           +-1c.0-[05]--
           +-1d.0-[06]--
           +-1f.0  Intel Corporation B560 LPC/eSPI Controller
           +-1f.3  Intel Corporation Tiger Lake-H HD Audio Controller
           +-1f.4  Intel Corporation Tiger Lake-H SMBus Controller
           +-1f.5  Intel Corporation Tiger Lake-H SPI Controller
           \-1f.6  Intel Corporation Ethernet Connection (14) I219-V

The device 00:01.0 is the PCIe x16 root port to which the GPU is connected, but it apparently does not support PCIe atomics (note the flags '32bit' and '64-bit'):

lspci -vvvs 00:01.0
...
DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
                         10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
                         AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, ARIFwd-
                         AtomicOpsCtl: ReqEn+ EgressBlck+
...

I tried setting those bits with a udev rule which caused the error messages to disappear, but then it just freezes whenever any ROCm operation is performed on the GPU. Is there some BIOS setting or driver configuration required to enable PCIe atomics? Or is it simply that my CPU or mainboard doesn't support them?

There are all kinds of reasons this might not work, especially on a consumer board, and since this is for bug reports on ROCm (and this issue is documented with consumer boards specifically mentioned as being iffy) you'd probably be way better off
a) Asking Intel on their forums, they actually respond so you'll probably get a quick answer on CPU support
b) Asking the motherboard manufacturer if it's not one of the consumer focused ones.  Supermicro will get you extensive responses to any questions within a business day,  Tyan or Gigabyte are likely going to be pretty quick too.  OTOH Asus will never respond or respond with irrelevant garbage links to FAQ searches and you'll end up on spam mailing lists in Chinese for a cloud storage service, so use this option carefully.
c) Try messing with IOMMU settings and any PCIe DMA mitigation settings in the BIOS that might be forcing devices to not communicate.
I don't think switch chips necessarily show up in the tree unless something is running off of them so if there's one of those (to deal with the needed retimer as well) handling a second slot further down the board when it's populated and run both slots in x8 mode it could be a blocking component if I'm not mistaken about the visibility thing.
If your GPU is on a riser cable so it can be mounted vertically, none of those cables are in-spec for PCIe 4.0 (usually the cable length alone is enough to violate SNR / signal strength requirements, and the ones short enough to not violate them probably still do by having the extra connection.)  and it might be getting dropped to a lower feature set because of bad signal, install directly in the PCIe slot and try again.  If that turns out to be a problem the only compliant way to manage that mounting situation is with a 2x8i oculink card in the slot the gpu was in and both cables leading to a 2x8i Oculink -> PCIe 4.0 x16 card so you get retimers in the path.   Ironically this solution is the same price as the "pretty" cables which don't and can't reliably work, but it wasn't available until recently and will probably require slight amounts of case modding to get the card with the slot lined up correctly and at the right height.
My first assumption though is that a mid to low tier consumer CPU from an era where Intel has been dropping features from their non-Xeons more and more that only supports 20 PCIe lanes might not have bothered implementing it.  There's probably not a lot of call for ensuring atomic update of memory on PCIe devices when you can install at most 3 of them connected directly to the CPU depending on the board.  The reason Haswell-E and Broadwell-E are still selling and being used was that they're really just stripped down Xeons that (most) boards disable ECC RDIMMs on (most) models of, the 6960x being an exception on some boards, so the BIOSes had all of the higher end features and you didn't have to deal with guesswork nonsense.

I tried using that wheel with a simple python script:
import torch
print(torch.version.hip)
a = torch.Tensor([1, 2, 3, 4]).cuda()
q = torch.sum(a)
print('sum:', q)

However, now I get a different error instead: RuntimeError: HIP error: invalid device function
It prints 5.7.31921-d1770ee1b as the HIP version. Running it with AMD_LOG_LEVEL=3 I get a lot of
hipErrorNoBinaryForGpu: Unable to find code object for all current devices!
  Devices:
    amdgcn-amd-amdhsa--gfx1100 - [Not Found]
  Bundled Code Objects:
    host-x86_64-unknown-linux-- - [Unsupported]
    hipv4-amdgcn-amd-amdhsa--gfx1030 - [code object targetID is amdgcn-amd-amdhsa--gfx1030]
[out.log](https://github.com/RadeonOpenCompute/ROCm/files/13394495/out.log)

    hipv4-amdgcn-amd-amdhsa--gfx900 - [code object targetID is amdgcn-amd-amdhsa--gfx900]
    hipv4-amdgcn-amd-amdhsa--gfx906 - [code object targetID is amdgcn-amd-amdhsa--gfx906]
    hipv4-amdgcn-amd-amdhsa--gfx908 - [code object targetID is amdgcn-amd-amdhsa--gfx908]
    hipv4-amdgcn-amd-amdhsa--gfx90a - [code object targetID is amdgcn-amd-amdhsa--gfx90a]

Running it with MD_LOG_LEVEL=3 HSA_OVERRIDE_GFX_VERSION="11.0.0" PYTORCH_ROCM_ARCH="gfx1100" HIP_VISIBLE_DEVICES=0 didn't change anything.
It seems to me that the wheel does not support gfx1100.
Full log:
out.log

Right, we did not build for gfx1100. For the short term, would you mind trying to build from source using below instruction I wrote in the other similar issue related to atomics.
(1) start another terminal, start a new container of (rocm/pytorch:latest-base) with the parameters using the instruction above
sudo docker run -it --network=host --device=/dev/kfd --device=/dev/dri --group-add=video --ipc=host --cap-add=SYS_PTRACE --security-opt seccomp=unconfined --shm-size 8G -u root rocm/pytorch:latest-base

(2) clone the pytorch inside your docker environment
git clone --recursive https://github.com/ROCmSoftwarePlatform/pytorch.git
cd pytorch
git checkout rocm57_hostcall

(3) run this:
python tools/amd_build/build_amd.py

(4) run rocm-info to check your GPU GFX Arch
rocminfo
for example, gfx1100
(5) build pytorch by source (replace with your gfx arch).
PYTORCH_ROCM_ARCH="$YOUR_GFX_ARCH" python setup.py develop

(6) run the torch.sum test again.
Details:
https://github.com/pytorch/pytorch/issues/103973#issuecomment-1743678566

I compiled pytorch according to your instructions. Running a simple python program
import torch
a = torch.Tensor([1, 2, 3, 4]).cuda()
print(torch.sum(a))

crashes my graphics driver. Sometimes the crash happens on the second line and sometimes on the third. I have to manually kill the python process, CTRL+C does not work. Also the GPU usage goes up to 100% and stays there until a system reboot.
This is similar to what I experienced with blender. As soon as I switch to Cycles, the GPU usage goes up to 100%, core clock 2,9GHz and stays there until closing blender.

I tried torch.sum() in a python shell with AMD_LOG_LEVEL=3:
Python 3.9.18 (main, Sep 11 2023, 13:41:44)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> a = torch.Tensor(range(8))
>>> b = a.cuda()
:3:rocdevice.cpp            :442 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Initializing HSA stack.
:3:comgrctx.cpp             :33  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Loading COMGR library.
:3:rocdevice.cpp            :208 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Numa selects cpu agent[0]=0x492a0f0(fine=0x75f3bc0,coarse=0x7750e80) for gpu agent=0x7751460 CPU<->GPU XGMI=0
:3:rocdevice.cpp            :1680:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Gfx Major/Minor/Stepping: 11/0/0
:3:rocdevice.cpp            :1682:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] HMM support: 1, XNACK: 0, Direct host access: 0
:3:rocdevice.cpp            :1684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Max SDMA Read Mask: 0x0, Max SDMA Write Mask: 0x0
:3:hip_context.cpp          :48  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Direct Dispatch: 1
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b5a0 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7f54a5733194 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device.cpp           :381 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceProperties ( 0x7ffcaf46b2c0, 0 )
:3:hip_device.cpp           :383 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceProperties: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b5d8 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b344 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b0c0 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b158, 0x7ffcaf46b15c )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b3a4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b1b8, 0x7ffcaf46b1bc )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b334 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b148, 0x7ffcaf46b14c )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b804 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aa34 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a914 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a904 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_stream.cpp           :395 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDeviceGetStreamPriorityRange ( 0x7ffcaf46a6d8, 0x7ffcaf46a6dc )
:3:hip_stream.cpp           :403 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDeviceGetStreamPriorityRange: Returned hipSuccess :
:3:hip_error.cpp            :27  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetLastError (  )
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a104 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_graph.cpp            :887 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipStreamIsCapturing ( stream:<null>, 0x7ffcaf46a148 )
:3:hip_graph.cpp            :888 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipStreamIsCapturing: Returned hipSuccess :
:3:hip_memory.cpp           :566 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMalloc ( 0x7ffcaf46a238, 2097152 )
:3:rocdevice.cpp            :2230:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] device=0x77baaa0, freeMem_ = 0x4fee00000
:3:hip_memory.cpp           :568 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipMalloc: Returned hipSuccess : 0x7f52ad200000: duration: 51 us
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a934 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a934 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_memory.cpp           :652 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMemcpyWithStream ( 0x7f52ad200000, 0x75edf40, 32, hipMemcpyHostToDevice, stream:<null> )
:3:rocdevice.cpp            :2732:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] number of allocated hardware queues with low priority: 0, with normal priority: 0, with high priority: 0, maximum per priority is: 4
:3:rocdevice.cpp            :2810:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] created hardware queue 0x7f53ae300000 with size 16384 with priority 1, cooperative: 0
:3:rocdevice.cpp            :2902:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] acquireQueue refCount: 0x7f53ae300000 (1)
:3:devprogram.cpp           :2684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Using Code Object V5.
:3:rocvirtual.hpp           :66  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Host active wait for Signal = (0x7f53b1858800) for -1 ns
:3:hip_memory.cpp           :663 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipMemcpyWithStream: Returned hipSuccess : : duration: 163388 us
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
>>> c = torch.sum(b)
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b1f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46af04 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aed4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aae4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device.cpp           :381 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceProperties ( 0x7ffcaf46a7b0, 0 )
:3:hip_device.cpp           :383 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceProperties: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aaf4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aaf4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a7f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a7f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_platform.cpp         :193 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  __hipPushCallConfiguration ( {1,1,1}, {8,1,1}, 0, stream:<null> )
:3:hip_platform.cpp         :197 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] __hipPushCallConfiguration: Returned hipSuccess :
:3:hip_platform.cpp         :202 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  __hipPopCallConfiguration ( {0,0,0}, {0,0,0}, 0x7ffcaf46a840, 0x7ffcaf46a838 )
:3:hip_platform.cpp         :211 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] __hipPopCallConfiguration: Returned hipSuccess :
:3:hip_module.cpp           :678 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipLaunchKernel ( 0x7f54e318f2d8, {1,1,1}, {8,1,1}, 0x7ffcaf46a830, 0, stream:<null> )
:3:devprogram.cpp           :2684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Using Code Object V5.
:3:rocvirtual.cpp           :781 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Arg0:   = val:4150904307
:3:rocvirtual.cpp           :2897:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] ShaderName : _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIfNS0_14func_wrapper_tIfZNS0_11sum_functorIfffEclERNS_14TensorIteratorEEUlffE_EEjfLi4EEEEEvT1_
:3:hip_module.cpp           :679 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipLaunchKernel: Returned hipSuccess :
:3:hip_error.cpp            :27  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetLastError (  )
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
>>> d = c.cpu()
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a974 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a974 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_memory.cpp           :652 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMemcpyWithStream ( 0x7c1d7c0, 0x7f52ad200200, 4, hipMemcpyDeviceToHost, stream:<null> )
:3:rocvirtual.hpp           :66  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Host active wait for Signal = (0x7f53b1858780) for -1 ns

torch.sum() works fine, but copying it back to RAM (like for printing its contents) seems to hang indefinitely.

I tried torch.sum() in a python shell with AMD_LOG_LEVEL=3:
Python 3.9.18 (main, Sep 11 2023, 13:41:44)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> a = torch.Tensor(range(8))
>>> b = a.cuda()
:3:rocdevice.cpp            :442 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Initializing HSA stack.
:3:comgrctx.cpp             :33  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Loading COMGR library.
:3:rocdevice.cpp            :208 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Numa selects cpu agent[0]=0x492a0f0(fine=0x75f3bc0,coarse=0x7750e80) for gpu agent=0x7751460 CPU<->GPU XGMI=0
:3:rocdevice.cpp            :1680:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Gfx Major/Minor/Stepping: 11/0/0
:3:rocdevice.cpp            :1682:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] HMM support: 1, XNACK: 0, Direct host access: 0
:3:rocdevice.cpp            :1684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Max SDMA Read Mask: 0x0, Max SDMA Write Mask: 0x0
:3:hip_context.cpp          :48  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Direct Dispatch: 1
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b5a0 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7f54a5733194 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device.cpp           :381 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceProperties ( 0x7ffcaf46b2c0, 0 )
:3:hip_device.cpp           :383 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceProperties: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b5d8 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b344 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :546 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceCount ( 0x7ffcaf46b0c0 )
:3:hip_device_runtime.cpp   :548 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceCount: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b158, 0x7ffcaf46b15c )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b3a4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b1b8, 0x7ffcaf46b1bc )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b334 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_context.cpp          :355 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDevicePrimaryCtxGetState ( 0, 0x7ffcaf46b148, 0x7ffcaf46b14c )
:3:hip_context.cpp          :369 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDevicePrimaryCtxGetState: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b804 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aa34 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a914 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a904 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_stream.cpp           :395 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipDeviceGetStreamPriorityRange ( 0x7ffcaf46a6d8, 0x7ffcaf46a6dc )
:3:hip_stream.cpp           :403 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipDeviceGetStreamPriorityRange: Returned hipSuccess :
:3:hip_error.cpp            :27  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetLastError (  )
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a104 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_graph.cpp            :887 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipStreamIsCapturing ( stream:<null>, 0x7ffcaf46a148 )
:3:hip_graph.cpp            :888 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipStreamIsCapturing: Returned hipSuccess :
:3:hip_memory.cpp           :566 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMalloc ( 0x7ffcaf46a238, 2097152 )
:3:rocdevice.cpp            :2230:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] device=0x77baaa0, freeMem_ = 0x4fee00000
:3:hip_memory.cpp           :568 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipMalloc: Returned hipSuccess : 0x7f52ad200000: duration: 51 us
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a934 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a934 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_memory.cpp           :652 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMemcpyWithStream ( 0x7f52ad200000, 0x75edf40, 32, hipMemcpyHostToDevice, stream:<null> )
:3:rocdevice.cpp            :2732:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] number of allocated hardware queues with low priority: 0, with normal priority: 0, with high priority: 0, maximum per priority is: 4
:3:rocdevice.cpp            :2810:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] created hardware queue 0x7f53ae300000 with size 16384 with priority 1, cooperative: 0
:3:rocdevice.cpp            :2902:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] acquireQueue refCount: 0x7f53ae300000 (1)
:3:devprogram.cpp           :2684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Using Code Object V5.
:3:rocvirtual.hpp           :66  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Host active wait for Signal = (0x7f53b1858800) for -1 ns
:3:hip_memory.cpp           :663 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipMemcpyWithStream: Returned hipSuccess : : duration: 163388 us
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
>>> c = torch.sum(b)
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46b1f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46af04 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aed4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aae4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device.cpp           :381 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDeviceProperties ( 0x7ffcaf46a7b0, 0 )
:3:hip_device.cpp           :383 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDeviceProperties: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aaf4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46aaf4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a7f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a7f4 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_platform.cpp         :193 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  __hipPushCallConfiguration ( {1,1,1}, {8,1,1}, 0, stream:<null> )
:3:hip_platform.cpp         :197 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] __hipPushCallConfiguration: Returned hipSuccess :
:3:hip_platform.cpp         :202 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  __hipPopCallConfiguration ( {0,0,0}, {0,0,0}, 0x7ffcaf46a840, 0x7ffcaf46a838 )
:3:hip_platform.cpp         :211 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] __hipPopCallConfiguration: Returned hipSuccess :
:3:hip_module.cpp           :678 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipLaunchKernel ( 0x7f54e318f2d8, {1,1,1}, {8,1,1}, 0x7ffcaf46a830, 0, stream:<null> )
:3:devprogram.cpp           :2684:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Using Code Object V5.
:3:rocvirtual.cpp           :781 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Arg0:   = val:4150904307
:3:rocvirtual.cpp           :2897:<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] ShaderName : _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIfNS0_14func_wrapper_tIfZNS0_11sum_functorIfffEclERNS_14TensorIteratorEEUlffE_EEjfLi4EEEEEvT1_
:3:hip_module.cpp           :679 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipLaunchKernel: Returned hipSuccess :
:3:hip_error.cpp            :27  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetLastError (  )
:3:hip_device_runtime.cpp   :561 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipSetDevice ( 0 )
:3:hip_device_runtime.cpp   :565 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipSetDevice: Returned hipSuccess :
>>> d = c.cpu()
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a974 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_device_runtime.cpp   :531 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipGetDevice ( 0x7ffcaf46a974 )
:3:hip_device_runtime.cpp   :539 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] hipGetDevice: Returned hipSuccess :
:3:hip_memory.cpp           :652 :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280]  hipMemcpyWithStream ( 0x7c1d7c0, 0x7f52ad200200, 4, hipMemcpyDeviceToHost, stream:<null> )
:3:rocvirtual.hpp           :66  :<PHONE_NUMBER> us: [pid:16    tid:0x7f54f7603280] Host active wait for Signal = (0x7f53b1858780) for -1 ns

torch.sum() works fine, but copying it back to RAM (like for printing its contents) seems to hang indefinitely.

@MattisBergmann
If torch.sum() gave the correct result, it means it also worked for you.
Regarding the hanging:
I saw your previous note when you report the problem, you mentioned it started to freeze after below change:

lspci -vvvs 00:01.0
I tried setting those bits with a udev rule which caused the error messages to disappear, but then it just freezes whenever any >ROCm operation is performed on the GPU. Is there some BIOS setting or driver configuration required to enable PCIe >atomics? >Or is it simply that my CPU or mainboard doesn't support them?

Is the hanging potentially related to the above change? Will you be able to revert the above change? It seems to me that the atomics issue is solved by the wheel, but because of the above change, you have been experiencing hanging since then.

The PCIe configuration change was only temporarily, it got reverted automatically by amdgpu after rebooting. The hanging also happened on older rocm versions (before 5.5).

what is your iommu setting?

Try to disable iommu (iommu=off) in /etc/default/grub append to GRUB_CMDLINE_LINUX, then
sudo update-grub
then reboot.
See whether this helps.

IOMMU is enabled on my motherboard, but I didn't enable it in grub. Maybe it is enabled by default? I will try turning it off tomorrow, if that doesn't help, I will install a fresh Ubuntu, maybe some broken packages cause these problems.

Hello, I have the same issue and I am following the same steps indicated in this thread (recompiling pytorch from rocm57_hostcall, note that I forgot to run docker, so I am running in a simple venv).
My system also hangs after torch.sum() (with reported cpu and gpu usage stuck at 100%).
I noticed that torch.sum()  triggers some error that eventually ends with a gpu reset a few seconds later:

gpu error dmesg log

[Nov19 10:33] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[  +0.000388] amdgpu: failed to remove hardware queue from MES, doorbell=0x1002
[  +0.000002] amdgpu: MES might be in unrecoverable state, issue a GPU reset
[  +0.000002] amdgpu: Failed to evict queue 1
[  +0.000001] amdgpu: Failed to evict process queues
[  +0.000001] amdgpu: Failed to quiesce KFD
[  +0.000050] amdgpu 0000:0e:00.0: amdgpu: GPU reset begin!
[  +0.046245] amdgpu: Failed to remove queue 0
[  +0.851431] amdgpu 0000:0e:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[  +0.000026] amdgpu 0000:0e:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[  +0.000010] amdgpu 0000:0e:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B3A
[  +0.000008] amdgpu 0000:0e:00.0: amdgpu:       Faulty UTCL2 client ID: CPC (0x5)
[  +0.000007] amdgpu 0000:0e:00.0: amdgpu:       MORE_FAULTS: 0x0
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       WALKER_ERROR: 0x5
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       PERMISSION_FAULTS: 0x3
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       MAPPING_ERROR: 0x1
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       RW: 0x0
[  +0.125083] amdgpu 0000:0e:00.0: amdgpu: IP block:gfx_v11_0 is hung!
[  +0.001089] amdgpu 0000:0e:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[  +0.000025] amdgpu 0000:0e:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[  +0.000010] amdgpu 0000:0e:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B5B
[  +0.000008] amdgpu 0000:0e:00.0: amdgpu:       Faulty UTCL2 client ID: CPC (0x5)
[  +0.000007] amdgpu 0000:0e:00.0: amdgpu:       MORE_FAULTS: 0x1
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       WALKER_ERROR: 0x5
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       PERMISSION_FAULTS: 0x5
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       MAPPING_ERROR: 0x1
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       RW: 0x1
[  +0.000018] amdgpu 0000:0e:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[  +0.000011] amdgpu 0000:0e:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[  +0.000007] amdgpu 0000:0e:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       Faulty UTCL2 client ID: CB/DB (0x0)
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       MORE_FAULTS: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       WALKER_ERROR: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       PERMISSION_FAULTS: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       MAPPING_ERROR: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       RW: 0x0
[  +0.000031] amdgpu 0000:0e:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:173 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[  +0.000009] amdgpu 0000:0e:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       Faulty UTCL2 client ID: CB/DB (0x0)
[  +0.000006] amdgpu 0000:0e:00.0: amdgpu:       MORE_FAULTS: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       WALKER_ERROR: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       PERMISSION_FAULTS: 0x0
[  +0.000005] amdgpu 0000:0e:00.0: amdgpu:       MAPPING_ERROR: 0x0
[  +0.000004] amdgpu 0000:0e:00.0: amdgpu:       RW: 0x0
[  +0.000100] [drm] kiq ring mec 3 pipe 1 q 0
[  +1.011759] amdgpu 0000:0e:00.0: amdgpu: IP block:gfx_v11_0 is hung!
[  +0.000903] amdgpu 0000:0e:00.0: amdgpu: soft reset failed, will fallback to full reset!
[  +0.777591] [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
[  +0.047552] amdgpu 0000:0e:00.0: amdgpu: MODE1 reset
[  +0.000007] amdgpu 0000:0e:00.0: amdgpu: GPU mode1 reset
[  +0.000288] amdgpu 0000:0e:00.0: amdgpu: GPU smu mode1 reset
[  +0.507334] amdgpu 0000:0e:00.0: amdgpu: GPU reset succeeded, trying to resume
[ +16.673468] amdgpu 0000:0e:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
[ +16.675458] amdgpu 0000:0e:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
[  +0.000020] [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
[  +0.000242] [drm] VRAM is lost due to GPU reset!
[  +0.000007] [drm] PSP is resuming...
[  +0.061697] [drm] reserve 0x1300000 from 0x81fc000000 for PSP TMR
[  +0.106287] amdgpu 0000:0e:00.0: amdgpu: RAS: optional ras ta ucode is not available
[  +0.008244] amdgpu 0000:0e:00.0: amdgpu: RAP: optional rap ta ucode is not available
[  +0.000007] amdgpu 0000:0e:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[  +0.000008] amdgpu 0000:0e:00.0: amdgpu: SMU is resuming...
[  +0.000016] amdgpu 0000:0e:00.0: amdgpu: smu driver if version = 0x00000035, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00524b00 (82.75.0)
[  +0.000013] amdgpu 0000:0e:00.0: amdgpu: SMU driver if version not matched
[  +0.053036] amdgpu 0000:0e:00.0: amdgpu: SMU is resumed successfully!
[  +0.002450] [drm] DMUB hardware initialized: version=0x07002100
[Nov19 10:34] amdgpu 0000:0e:00.0: amdgpu: failed to write reg 291c wait reg 292e
[  +0.000665] [drm] kiq ring mec 3 pipe 1 q 0
[  +0.006090] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[  +0.000820] amdgpu 0000:0e:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
[  +0.002109] amdgpu 0000:0e:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[  +0.000004] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[  +0.000002] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[  +0.000002] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[  +0.000002] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[  +0.000002] amdgpu 0000:0e:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[  +0.000002] amdgpu 0000:0e:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[  +0.000001] amdgpu 0000:0e:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
[  +0.005158] amdgpu 0000:0e:00.0: amdgpu: recover vram bo from shadow start
[  +0.000382] amdgpu 0000:0e:00.0: amdgpu: recover vram bo from shadow done
[  +0.000065] [drm] Skip scheduling IBs!
[  +0.000006] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000003] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000004] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000003] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000005] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000004] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000003] [drm] Skip scheduling IBs!
[  +0.000003] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000002] [drm] Skip scheduling IBs!
[  +0.000001] [drm] Skip scheduling IBs!
[  +0.000671] [drm] ring gfx_32773.1.1 was added
[  +0.000744] [drm] ring compute_32773.2.2 was added
[  +0.000848] [drm] ring sdma_32773.3.3 was added
[  +0.000091] [drm] ring gfx_32773.1.1 ib test pass
[  +0.000041] [drm] ring compute_32773.2.2 ib test pass
[  +0.000268] [drm] ring sdma_32773.3.3 ib test pass
[  +0.001278] amdgpu 0000:0e:00.0: amdgpu: GPU reset(1) succeeded!

I don't know if this can be useful. I will retry later to recompile in a clean env.

This might be relevant:
https://github.com/RadeonOpenCompute/ROCm/issues/2625

To exclude an hardware issue I tried to run an similar testcase to sum() using opencl:
https://gist.github.com/GbGp/120d4f15e021ce0917e24470fa534ec1
This runs perfectly fine on my gpu.

In my previous attempts, I found out, that it got stuck in
https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/6fdf759273a098829dfd642fb730ea410f33b152/src/core/runtime/interrupt_signal.cpp#L139
Looking at the stacktrace, this seems to be the same problem. Back then, I thought that would be because ROCm 5.4.2 didn't yet support gfx11.
Here is the link to the issue:
https://github.com/evshiron/rocm_lab/issues/4#issuecomment-1584740343

After some more tests, I found out that this program somehow works:
import torch
t1 = torch.Tensor(range(256)).cuda()
t2 = torch.Tensor(range(256, 512)).cuda()
q_gpu = t1 + t2
q_cpu = q_gpu.cpu()

It seems to have problems with copying scalars back to host.

I managed to run this huggingface example by recompiling PyTorch with NumPy support.
https://huggingface.co/docs/diffusers/using-diffusers/write_own_pipeline
However, more complex pipelines tend to freeze on hipMemcpyWithStream.

Not sure whether you have turned off iommu or not with the above progress?

I turned iommu off in the bios (intel vt-d) as well as in grub (iommu=off in kernel commandline)

Can you check this documentation and perform the pre-requisites steps?
https://rocm.docs.amd.com/projects/radeon/en/latest/docs/prerequisites.html

@GbGp Please use docker and exact step to test again. Also, what is your gfx target. Please run
rocminfo

@hongxiayang sure, gfx1102 RX7600

rocminfo
ROCk module is loaded
=====================
HSA System Attributes
=====================
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
Mwaitx:                  DISABLED
DMAbuf Support:          YES

==========
HSA Agents
==========
*******
Agent 1
*******
  Name:                    Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Uuid:                    CPU-XX
  Marketing Name:          Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Vendor Name:             CPU
  Feature:                 None specified
  Profile:                 FULL_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        0(0x0)
  Queue Min Size:          0(0x0)
  Queue Max Size:          0(0x0)
  Queue Type:              MULTI
  Node:                    0
  Device Type:             CPU
  Cache Info:
    L1:                      32768(0x8000) KB
  Chip ID:                 0(0x0)
  ASIC Revision:           0(0x0)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   4000
  BDFID:                   0
  Internal Node ID:        0
  Compute Unit:            8
  SIMDs per CU:            0
  Shader Engines:          0
  Shader Arrs. per Eng.:   0
  WatchPts on Addr. Ranges:1
  Features:                None
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: FINE GRAINED
      Size:                    16105164(0xf5becc) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 2
      Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
      Size:                    16105164(0xf5becc) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
    Pool 3
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    16105164(0xf5becc) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       TRUE
  ISA Info:
*******
Agent 2
*******
  Name:                    gfx1102
  Uuid:                    GPU-XX
  Marketing Name:          AMD Radeon RX 7600
  Vendor Name:             AMD
  Feature:                 KERNEL_DISPATCH
  Profile:                 BASE_PROFILE
  Float Round Mode:        NEAR
  Max Queue Number:        128(0x80)
  Queue Min Size:          64(0x40)
  Queue Max Size:          131072(0x20000)
  Queue Type:              MULTI
  Node:                    1
  Device Type:             GPU
  Cache Info:
    L1:                      32(0x20) KB
    L2:                      2048(0x800) KB
  Chip ID:                 29824(0x7480)
  ASIC Revision:           0(0x0)
  Cacheline Size:          64(0x40)
  Max Clock Freq. (MHz):   2283
  BDFID:                   3584
  Internal Node ID:        1
  Compute Unit:            32
  SIMDs per CU:            2
  Shader Engines:          2
  Shader Arrs. per Eng.:   2
  WatchPts on Addr. Ranges:4
  Features:                KERNEL_DISPATCH
  Fast F16 Operation:      TRUE
  Wavefront Size:          32(0x20)
  Workgroup Max Size:      1024(0x400)
  Workgroup Max Size per Dimension:
    x                        1024(0x400)
    y                        1024(0x400)
    z                        1024(0x400)
  Max Waves Per CU:        32(0x20)
  Max Work-item Per CU:    1024(0x400)
  Grid Max Size:<PHONE_NUMBER>(0xffffffff)
  Grid Max Size per Dimension:
    x<PHONE_NUMBER>(0xffffffff)
    y<PHONE_NUMBER>(0xffffffff)
    z<PHONE_NUMBER>(0xffffffff)
  Max fbarriers/Workgrp:   32
  Packet Processor uCode:: 528
  SDMA engine uCode::      16
  IOMMU Support::          None
  Pool Info:
    Pool 1
      Segment:                 GLOBAL; FLAGS: COARSE GRAINED
      Size:                    8372224(0x7fc000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 2
      Segment:                 GLOBAL; FLAGS:
      Size:                    8372224(0x7fc000) KB
      Allocatable:             TRUE
      Alloc Granule:           4KB
      Alloc Alignment:         4KB
      Accessible by all:       FALSE
    Pool 3
      Segment:                 GROUP
      Size:                    64(0x40) KB
      Allocatable:             FALSE
      Alloc Granule:           0KB
      Alloc Alignment:         0KB
      Accessible by all:       FALSE
  ISA Info:
    ISA 1
      Name:                    amdgcn-amd-amdhsa--gfx1102
      Machine Models:          HSA_MACHINE_MODEL_LARGE
      Profiles:                HSA_PROFILE_BASE
      Default Rounding Mode:   NEAR
      Default Rounding Mode:   NEAR
      Fast f16:                TRUE
      Workgroup Max Size:      1024(0x400)
      Workgroup Max Size per Dimension:
        x                        1024(0x400)
        y                        1024(0x400)
        z                        1024(0x400)
      Grid Max Size:<PHONE_NUMBER>(0xffffffff)
      Grid Max Size per Dimension:
        x<PHONE_NUMBER>(0xffffffff)
        y<PHONE_NUMBER>(0xffffffff)
        z<PHONE_NUMBER>(0xffffffff)
      FBarrier Max Size:       32
*** Done ***

sorry for the dalay, I can confirm that I have the same issue after repeating all steps in the docker container

I've installed ubuntu 22.04.3 and follwed the ROCm installation guide step by step. Yet I still get the same problem: It freezes at some point. Upon killing the python process, the gpu driver crashes and my system locks up.

The current nightly wheel has fixed the Initial problem "Pcie atomics not enabled, hostcall not supported", but the torch.sum() program still does not work, but instead always crashes amdgpu with a lot of messages similar to
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
[drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait

Sometimes it shows also a page fault.

I've installed ROCm 6.0.0 and PyTorch 5.7 on my ubuntu installation and it surprisingly works.


Create a parser for .kaz file

Description
Build a parser for .kaz files, a syntax specifically designed for building UI components. The parser should be able to parse the .kaz file and return an object that conforms to the ITransformerInput interface.
Acceptance Criteria

The parser should able to parse all valid syntaxes of .kaz files
The parser should return an object fitting the ITransformerInput schema

Tasks

Instructions

[x] import
[x] prop
[x] state
[x] computed
[x] watch
[x] on

Template

[x] @for
[ ] @each
[x] @if
[x] @else if
[x] @else
[x] tags
[x] text
[x] expression

[x] Write tests for the parser

Additional Information
Example of the .kaz syntax:
- prop name: string
- state counter: number = 1
- computed mul2: number = counter * 2
- watch (counter) => {
    console.log(counter)
  }
- on:ready () => {
    console.log('App ready!')
  }

p (class='red'; data-counter={counter}) {
  Numbers:
  @for (let i = 0; i < counter; i++) {
    ${i}
  }
}

The .kaz syntax includes special directives such as @for, @each, @if, @else if, and @else that allow for iteration and conditional rendering. These directives follow the syntax of the corresponding statements in JavaScript, including for, for...in, for...of, Array.prototype.forEach, and if...else.

@each was finally not implemented to stay as close to TypeScript as possible.


Add your favourite news source

What would you like to share?
As an ice-breaker, I’d like to invite any newcomers to take a look through our list of news sources in data/sources.json.
Following the same format, please add a site of your choice by providing the name and a url. Leave the third key value pair as “base”: “”.
We will assess at a later date whether the base needs any attention.
Additional information
This issue will remain open as it will be ongoing to try and help as many contributors as possible get involved.
Thanks for taking a look, and this is a pretty friendly place so ask any questions you think of and someone will be there to help.
Sam

Hello,
I am a complete beginner and would like to contribute to this issue. Will you assign this to me first or I can just go ahead and create a PR?

Hello,
I am a complete beginner and would like to contribute to this issue. Will you assign this to me first or I can just go ahead and create a PR?

Hi @snehashish-ghosh98 ! This particular issue is a wide open one so just go ahead and create a PR. We're not too strict on whether you reference this issue or not, but use the opportunity to play around with linked PRs and issues etc.
Very happy to have you on board!
Also thanks for asking a question, we'd really like to encourage others to do the same whenever anything is unclear.

This can stay open for any newcomers.


Custom resolvers are removed when the mock server is stopped

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
4.45.2
What operating system are you using?
mac
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
I've created a custom resolvers to overwrite a standard resolver and placed it in
<rootDir>mplify/backend/api/rcv/resolvers

Then I started the local backend server with
amplify mock

The server added its own resolver templates into this directory, and when I stopped it, all the templates were gone, including my custom template.
Expected behavior
See the description
Reproduction steps

Add a custom template to the resolvers dir
Start the mock server
Stop the mock server
Observe that all templates are gone.

Log output
# Put your logs below this line

Hi @volkanunsal , thanks for taking the time to submit. I was able to reproduce on my end following your steps above.

Add a custom override template to the resolvers dir
Start the mock server
Stop the mock server
templates are removed

Labeling as a bug.
https://user-images.githubusercontent.com/634958/111163690-b2a7b280-8573-11eb-8b79-086812ec89ef.mov

The issue seems to generate from the resolver-overrides.ts file.
I would like to work on this issue.

/cc @edwardfoyle for awareness

@volkanunsal Could you provide info on the custom resolvers? Can you provide a sample which is reproducible?
@siegerts was able to repro this with an empty file. However I tested this on version 4.45.2 and it did not delete non-empty files.

I can definitely say the files weren't empty when I encountered the issue.

Try this. Copy a default resolver and use the same file name and content to create a new one when the server is not running. Then start the server. And stop it again. All files are gone.
Is the server checking the md5 hash of the file to decide whether to remove it? Because that might explain it. I'd copied over the default file but may not have changed its contents yet.

@volkanunsal Either empty or the same file as the default one. If the file is the same without a single change or customization, then it results in getting rid of it. As you mentioned above it does a string comparison and deletes based on it.


GCP Support

Pentagon should be able to create a cluster in GCP using GKE as easily or more easily than in AWS
https://github.com/reactiveops/pentagon-internal/issues/70

closed by #71


rxjs-compat NOT automatically installed

Per the paragraph on the announcement blog page:

For example, the command ng update @angular/core will update all of the Angular framework packages as well as RxJS and TypeScript, and will run any schematics available on these packages to keep you up to date. As part of this one command, we’ll automatically install rxjs-compat into your application to make the adoption of RxJS v6 smoother.

However, after running the ng upgrade commands, rxjs-compat was NOT automatically installed. When I ran my app, there were several errors related to rxjs
node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'.
src/app/students/students.component.ts(2,10): error TS2305: Module '"/Users/john/Dev/DotNet/TimeTracker/node_modules/rxjs/Observable"' has no exported member 'Observable'.
src/app/students/students.service.ts(3,10): error TS2305: Module '"/Users/john/Dev/DotNet/TimeTracker/node_modules/rxjs/Observable"' has no exported member 'Observable'.

Versions
Angular CLI: 6.0.0
Node: 10.0.0
OS: darwin x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

Update an existing app, per directions on update.angular.io

Observed behavior
rxjs-compat was not added to package.json automatically
Desired behavior
Per the docs, rxjs-compat should have been installed.
Mention any other details that might be useful (optional)

same issues here

same here

Same here.

same

Same - I tried to run as well ng update rxjs, but it did not add rxjs-compat to the package.json, neither added it to the npm list.

I too have the same issue but resolved by
npm install<EMAIL_ADDRESS>

@here removing rxjs-compat after the migration still throw the same error

npm i rxjs-compat
Add these on o your root folder

rxjs-compat should not longer be needed.  However if this issue is still occurring for anyone, the rxjs package itself contains the necessary migrations to install the rxjs-compat package.  Please open an issue with rxjs if the update migrations are not being properly executed when updating from a pre-6.0 version of rxjs to a new version via the ng update command.


RPG c spec comments broken

     C           *IN77     DOWEQ'0'
     C                     EXSR GETDTA
     C           ERRCDE    IFEQ ' '                        NO ERROR

VS Code slightly changed the TextMate interpreter. Fixed in https://github.com/barrettotte/vscode-ibmi-languages/issues/45


Private constructor issue?

It's probably a stupid question, but trying to use the library with your simple example from the Readme, I run every time into this error:
Fatal error: Call to private Transliterator::__construct() from invalid context ...
One explanation for this error I found here, but I could not figure out a solution in this case:
https://stackoverflow.com/questions/1997721/fatal-error-call-to-private-myobject-construct-from-invalid-context
Can you please give a more detailed example, how to use the library? Thanks ...

sorry, please delete it. You already answered this ....
https://github.com/umpirsky/Transliterator/issues/4


Change "File not in project" status bar item when we're still restoring/loading projects

When you open a project that hasn't been restored or cached it may take a while before we parse all projects.
During this time we can report open filed as "not in project" while in reality we just don't know about it yet - the message is misleading. We should probably change a message a bit while any project is still restoring/loading.

This should be worked on 4.0 branch

So, I actually cannot reproduce this.
I created 20 project files in one directory, opened two files, one from the first project and one from the last. I looked at the status bar and I saw the message "Project loading" but the message "Not in a F# project" never came up.
How can I reproduce this?

Create an sln file and just don't add the project to it. Ionide 4 is
parsing the sln if it exists and only loads projects that are listed over
there
Tomas Leko<EMAIL_ADDRESS>schrieb am So., 16. Juni 2019, 10:49:

So, I actually cannot reproduce this.
I created 20 project files in one directory, opened two files, one from
the first project and one from the last. I looked at the status bar and I
saw the message "Project loading" but the message "Not in a F# project"
never came up.
How can I reproduce this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ionide/ionide-vscode-fsharp/issues/1130?email_source=notifications&email_token=AAAOANBEW7HT6MLDVBNNPC3P2X5CZA5CNFSM4HX3SXI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZIMSY#issuecomment-502433355,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOANCWDUQLE32XT7N4GG3P2X5CZANCNFSM4HX3SXIQ
.

OK, this I can reproduce but I guess in such a case the message should be there. The tooltip also says "Library.fs is not in any project known to ionide" which is correct I guess.
Sorry, but I just don't understand what is current behaviour and what is expected behaviour of this issue.
Please correct me if I am wrong. I understood this issue as:

Open an ionide workspace (Solution or directory) in VSCode
Ionide starts to parse all projects from the workspace
While ionide is loading all the projects open an F# file which is in some of the currently loading projects
Look at status bar and see the message "Not in a F# project" which is actually incorrect and should not be shown at this point in time

Maybe I complicate to much and maybe this issue is just changing of the message "Not in a F# project" to something else?
Sorry, but I am new to contributing and I don't know how this works. I hope I am not taking to much of your time.

I think #1130 was all we needed. Eventually we can try handling situation where workspace is not yet loaded, and file is not in project (yet?) with some other message.


Diet app settings screen

Created Settings screen of diet app .
fixes issue #71
Settings screen:

Everything is smooth  with no overflow.

@Jaideep25-tech  @naveeramesh  approve this pr thanks, and close issue #71

@Jaideep25-tech good to merge


Failed to build App from source

I'm testing the #152 but I get the following error, which makes me think the build instructions are not complete.
Errors     << tango_ros_streamer:cmake /home/rsmits/tango_ros_ws/logs/tango_ros_streamer/build.cmake.003.log
CMake Warning at /opt/ros/kinetic/share/catkin/cmake/catkinConfig.cmake:76 (find_package):
  Could not find a package configuration file provided by
  "rosjava_build_tools" with any of the following names:

    rosjava_build_toolsConfig.cmake
    rosjava_build_tools-config.cmake

I resolved this by running rosdep install --from-path src --ignore-src --rosdistro kinetic -r
On kinetic rosdep install complains about the following missing packages:
tango_ros_native: Cannot locate rosdep definition for [opencv2]
glog_catkin: Cannot locate rosdep definition for [gflags_catkin]

Ithink this is solved with the new doc. See #176.

Yes you are right. Marking as closed.


Edit profile

Related Issue

#19

Proposed Changes

Added Iconbutton in home_screen.dart.
Route added in routes.dart.
edit_profile.dart in edit_profile/
body.dart in edit_profile/components/
image_picker.dart in edit_profile/components/
Added image_picker dependency in pubspec.yaml

Checklist

[x] ✅ My code follows the code style of this project.
[ ] 📝 My change requires a change to the documentation.
[x] 🎀 I have updated the documentation accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[ ] ✨ I have added tests to cover my changes.
[ ] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Edit Profile Page
Edit Profile Page

Demo
https://user-images.githubusercontent.com/53931644/158020284-1f08c74f-5580-4774-ab9c-f364ea856e8c.mp4

Resolve the issue which are failing this checks.

LGMT

@VrishtiGupta11  Something error has come, update it. Your PR will soon be merged.

Could you please guide about how can I resolve this issue? Do I need to add more commits to edit-profile branch?

Once everything seems good we will merge your Pr for sure ✅

@all-contributors please add @VrishtiGupta11  code ,


Add reverse selection button

What is happening
Currently the start and target asteroids are entered in their individual pillbox. Removing asteroids requires backspaces or clicking the X's manually.

Why is this an issue
It's annoying to switch the start and target selection around
Proposed change
Add a reverse button in between the pillboxes that switches the selection
Related issues
None

see my pull req.


ui: Add bulk/int/iso/cntl type to endpoint summary info

The Endpoint summary line in the Interface descriptor list currently contains the address and direction data:
Endpoint 3 IN
This change adds the endpoint type too, as derived from the attribute data:
Endpoint 3 BULK IN
- by defining std::fmt::Display for EndpointType, and using that in the summary data.

Bikeshed opportunity: should it be CNTL or CTRL?

With this, the endpoint info looks like:

Nice! This is a good addition, thank you.
I don't think it's necessary to capitalise or abbreviate the endpoint types, though. Just bulk, interrupt, isochronous or control should be fine here, and that matches how we label transfers in the traffic view.
We capitalise IN and OUT because those direction identifiers are always specifically capitalised in the USB 2.0 standard.
It would also make more sense to put the number and direction together. The direction and the endpoint number together form a single value, the endpoint address. There can be both a 1 IN (address 0x81) and 1 OUT (address 0x01).
Overall I think what I'd prefer to see for your example is:
Endpoint 1 IN (interrupt)
Endpoint 2 OUT (bulk)
Endpoint 3 IN (bulk)

Sure thing, can do. I'm not sure where I saw the BULK IN endpoint naming formats previously (or whether I'm just imagining that as a convention!)

With ffa5061b1:

Great, thank you!


Slate json without the text node throwing error.

Problemtic code
{
      "type": "span",
      "children": []

 }

if someone copying and pasting from another website we might run in this type of json. During saving it doesn't give any problem but when we are saveing and try to edit the page it is throwing the error.
Schema
Blocks

{
 "2e77ee8c-2689-45b0-9dd9-fb81289e2a2e": {
  "@type": "slate",
  "plaintext": " aber auch von Fahrzeugen ausgetauscht werden.",
  "value": [
   {
    "children": [
     {
      "children": [
       {
        "text": ""
       }
      ],
      "type": "span"
     },
     {
      "children": [
       {
        "text": "aber auch von Fahrzeugen ausgetauscht"
       }
      ],
      "type": "span"
     },
     {
      "children": [
       {
        "text": "werden."
       }
      ],
      "type": "span"
     },
     {
      "type": "span",
      "children": []
     }
    ],
    "type": "p"
   }
  ]
 },
 "9e986f19-5327-47fb-9fb4-95f7ee58fbde": {
  "@type": "title"
 }
}

Blocks layout

{
 "items": [
  "9e986f19-5327-47fb-9fb4-95f7ee58fbde",
  "2e77ee8c-2689-45b0-9dd9-fb81289e2a2e"
 ]
}

@tiberiuichim can you guide me in the correct path to how we can handle this empty children array during the saving of page?

https://github.com/plone/volto/blob/master/packages/volto-slate/src/editor/extensions/insertData.js#L40

@tiberiuichim can this type of JSON be generated by migration also or it could happen only by copy-paste? I am not pretty sure how in the first place we are able to get this JSON in Plone's backend. Do you have any guesses because reading insertdata.js code and I think it is handling the null case for spanTagDeserializer

I checked the page that @iFlameing was debugging here. I am pretty sure it came from an old version of blocks-conversion-tool and is not a bug in volto.

I am closing this since we know how it got at first place.


change queue submission for sling-job-acquistion_localizer_single

By default, these jobs are submitted to system-job_worker-small. It should be submitted to system-jobs-queue.

Updated: https://github.com/hysds/multi_acquisition_localizer/commit/47901a50db6b817634865a9e6e92aa157b777f86.


[WFLY-11128] added ref to jboss-modules

https://issues.jboss.org/browse/WFLY-11128
Added jboss-module reference in jaxws-client module.xml to resolve classNotFound Exception
to org.jboss.modules.ModuleLoadException.

IIRC, there was an issue building feature-packs related to org.jboss.modules being provided by default and not present in the modules dir. That was fixed later in galleon-plugins. Sorry for the regression!


Memory leak in Jint caused by DomFunctionInstance

I'm currently writing a web automation library, and a large set of NUnit unit tests to go with it. Each test loads several pages and runs several scripts inside a BrowsingContext, which gets released as soon as the test finishes (all paths from roots to BrowsingContext are nullified). Despite this, the memory usage of the ReSharper test runner process grows astronomically as the automation tests are processed. Upon taking a heap snapshot, I can see that the majority of memory used is used for AngleSharp.Scripting.JavaScript.DomFunctionInstance. Below is a screenshot showing the reference counts for this class.
Dictionary<String, Jint.Runtime.MruPropertyCache> References
Every time I load a new IDocument into the BrowsingContext, I call .Dispose() on the currently loaded one to ensure it properly releases any unmanaged resources, and as soon as the new document is loaded, all references to the old document should be collected by the GC. However, even if I manually call GC.Collect(); at the end of each test, the process memory grows by about 200-400 MB for every test that runs. By the time I'm halfway through my test session, the process is using 15 or so of the 16 GB of RAM I have, and the machine becomes unresponsive.
I know that the Jint Engine instance for each IWindow is stored in a weak reference table, so when I dispose of my browsing context (by releasing all references to my class that stores the only instance of it), the BrowsingContext's IWindow should become stale and be collected by the GC, thus also releasing the Engine instance. For some reason, however, it doesn't appear that this frees up the DomFunctionInstance instances.
The top of the Paths to Root for Jint.Runtime.Descriptors.PropertyDescriptor is Jint.Native.JsValue, leading me to believe there are references stored somewhere that can still be accessed once the Engine instance is disposed of, or that the Engine instance is somehow not being disposed of when the BrowsingContext goes out of scope.

Yeah that caching is hitting us hard here I guess.
I think we need a good and well-though out proposal to improve the situation here (i.e., keep the performance and avoid memory leaks).

dotMemory now has some APIs to test for memory stuff, perhaps it could be
of help?
On Thu, 25 May 2017 at 00:44, Florian Rappl<EMAIL_ADDRESS>wrote:

Yeah that caching is hitting us hard here I guess.
I think we need a good and well-though out proposal to improve the
situation here (i.e., keep the performance and avoid memory leaks).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AngleSharp/AngleSharp.Scripting/issues/41#issuecomment-303860432,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmDdjQkDqGRSN7m41ZXq5aBTiM5mKVLks5r9KSjgaJpZM4NleWD
.

I think this is a great idea @georgiosd!

I don't have any experience with it but if you add anything, please comment here and I'll have a play too :)

I've been doing some more looking into this with the VS2017 memory diagnostic tools. I can't get a ton of useful information with them, but it seems there are a lot of multi-circular/spaghetti references between DomEventInstance, DomFunctionInstance, DomPrototypeInstance, and EngineInstance. Even after I've completely Disposed of all my IDocuments, BrowsingContexts, etc, there is still a ton of memory consumed by the process. If I run 20-30 of my unit tests, the process memory is up to 12+ GB and my workstation starts choking from all the swapping going on. Each unit test opens up a BrowsingContext, runs some workflows which load anywhere between 5-15 pages (by following links, clicking buttons, etc), then disposes the BrowsingContext. As each Unit Test is a top-level function entry point, the whole chain of BrowsingContexts and IDocuments created by each unit test goes out of scope as soon as the unit test finishes, but the GC doesn't seem to be able to identify that certain instances are truly out of scope, which is probably why the memory climbs half a gig for each test. Right now, it looks like the only way I can solve the memory leak problem is by launching a new AppDomain from each unit test so that I can unload it and release the memory completely when the test finishes, but I would really rather not do that. That solution won't solve the problem in production, either.

I don't know what kind of tests you have, but 12 GB after just 20-30 of them does not sound right at all. The tests in this lib do not come remotely close to this number and each one uses jQuery (plus of course the whole DOM which is already quite heavyweight).

There seems to be something holding circular references to Window, which would explain the high memory usage. The weak reference table used to hold Engine instances is keyed on Window instances. Here's a screenshot of a memory dump after running my workflow tests. Keep in mind my workflows involve navigating through a lot of pages (dozens), and it seems each page gets stored in memory instead of being released once it is unloaded. I don't hold any permanent references to IDocument or IWindow in my code; just a BrowsingContext.
Screenshot

For some more information, the memory leaks only seem to occur when I have resource loading enabled (automatic downloading and executing of <script> tags). If I disable resource loading for script files, it appears the memory is properly cleaned up and doesn't climb exponentially as my workflows run. However, this means my workflows don't work properly as the pages obviously require their external scripts in order to work correctly.

I see - thanks for the info!

Okay...I've been doing some more digging yesterday and today. Everything I've found boils down to ScriptRequestProcessor, HtmlScriptElement, and TaskEventLoop. This coincides with my observation that the leak only happens when external script resources are being loaded.
I'm wondering if there's a closure leak here...I found one in my own code earlier where I was capturing an IDocument in a JavaScript handler (Action passed to Jint that captured an IDocument). I'm still trying to find out if this leak is caused by something I'm doing while calling AngleSharp or Jint, or if it's definitely a bug in AngleSharp.Scripting, but there are definitely an inexplicably high number of ScriptRequestProcessor instances left over after my workflows are finishing.

I don't think this is a bug in Jint. I think we can optimize AS.Scripting definitely, but I would not exclude a leak some closure of AS core.

Big discovery incoming!
I think I have solved the biggest culprit of this memory leak. It seems the websites I am scripting are setting copious amounts of timeouts with setTimeout or setInterval with excessively long timeout values, which is not something I am able to avoid. I don't know which scripts are doing this so I can't pick-and-choose which to run.
Due to these long-running timeouts, all of the long Task.Delay calls on Window.cs:642 are causing Task.DelayPromise instances to hang around, which in turn hold references to Action<Window> which of course hold references to Window in their closure. This causes the Window and all of its Jint values to stay in memory until these DelayPromises are resolved.
Thankfully, the solution is relatively simple:

First I made AngleSharp.Dom.IWindow extend IDisposable.
Next, I made Window implement the inherited Dispose method from IDisposable, and inside it, I simply cancel all tasks associated with the Window's Document:

#region Disposal

public void Dispose()
{
    var timeoutTasks = _document.GetAttachedReferences<CancellationTokenSource>();

    foreach ( var task in timeoutTasks )
        task.Cancel();
}

#endregion

This causes any waiting Task.DelayPromise instances to resolve into the cancelled state, which falls into the continuation in Window.DoTimeoutAsync and eventually releases the Task.Delay reference chain, meaning the Window is no longer referencing itself due to unexpired timeouts.
Now, in Document's implementation of Dispose, I simply dispose of the Document's view if it exists:
public void Dispose()
{
    //Important to fix #45
    ReplaceAll(null, true);
    _loop.CancelAll();
    _loadingScripts.Clear();
    _source.Dispose();
    _view?.Dispose();
    _view = null;
}

(the last line requires removing the readonly keyword from Document._view...it may not be necessary to forcefully nullify the reference to the Window but I am doing that in my case to be safe).
After making these modifications, my application's memory is properly collected after I dispose the BrowsingContext as all references to Document are released, which propagates down now that Window is no longer dominating itself.
My AngleSharp workspace is slightly off-branch from devel because I changed the xproj to a .NET Core csproj to work with VS2017, so I'm not sure if a pull request from my fork would merge 100% correctly, but hopefully there's enough information here to implement a fix if this is indeed a valid solution.

That is indeed super useful information.
As far as the new csproj is concerned: I think we actually want to migrate from xproj + project.json to the new csproj (i.e., go back to csproj with the new abilities there). So if you think that would be a blocker - it wouldn't be (actually it would be another helpful thing).
Much appreciated for the insights 👍 🏅 !


Solved the two title issue

add word website in the end of "Click me to visit official melon squad"


Update to babel6 (also updates some deps)

things are generally working, but the travis installed firefox is not working properly...

submitted https://github.com/cibernox/ember-native-dom-helpers/pull/35 to attempt to unblock


Multiple race conditions

My urfave/cli version is
v2.25.0 / v3.0.0-alpha2.0.20230307054335-e55fb61e7a9e
Checklist

[x] Are you running the latest v2 release? The list of releases is here.
[x] Did you check the manual for your release? The v2 manual is here
[x] Did you perform a search about this problem? Here's the GitHub guide about searching.

Dependency Management

My project is using go modules.

Describe the bug
There are several race conditions happening in both v2 and in v3.
These issues seem to have appeared in versions past v2.19.2.
To reproduce
package main

import (
	"time"

	// "github.com/urfave/cli/v2" // Uncomment if testing against v2
	"github.com/urfave/cli/v3" // Uncomment if testing against v3
)

var demoFlag = &cli.StringFlag{
	Name:    "demo",
	Value:   "demo",
	Usage:   "demo",
	EnvVars: []string{"RACE_DEMO"},
}

var appCommands = []*cli.Command{
	{
		Name:  "race",
		Usage: "Start the demo",
		Flags: []cli.Flag{demoFlag},
		Action: func(c *cli.Context) error {
			return cmd1(c)
		},
	},
}

func cmd1(_ *cli.Context) error {
	time.Sleep(1 * time.Second)
	return nil
}

func newApp() *cli.App {
	app := cli.App{
		Name:            "demo",
		HideHelpCommand: true,
		HideVersion:     true,
		HideHelp:        true,
		Commands:        appCommands,
	}
	return &app
}

func main() {
	go func() {
		startArgs := []string{
			"demo",
			"race",
		}
		err := newApp().Run(startArgs)
		if err != nil {
			panic(err)
		}
	}()

	var err error

	for i := 0; i < 3; i++ {
		startArgs := []string{
			"demo",
			"race",
		}
		err = newApp().Run(startArgs)
		if err == nil {
			return
		}
		time.Sleep(500 * time.Millisecond)
	}
	if err != nil {
		panic(err)
	}
}

Observed behavior
What did you see happen immediately after the reproduction steps
above?
See the races files:

racesv2.txt
racesv3.txt

Expected behavior
Run the code above with:
go run -race main.go

Run go version and paste its output here
go version go1.19.5 linux/amd64

Run go env and paste its output here
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/florin/.cache/go-build"
GOENV="/home/florin/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/florin/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/florin/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/florin/go-sdks/go1.19.5"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/florin/go-sdks/go1.19.5/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.5"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/florin/projects/demo/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build4197316836=/tmp/go-build -gno-record-gcc-switches"

Duplicate of #1242

@dlsniper In general this library is NOT intended to be thread safe. For most use cases it isnt required. We dont intend to fix this as there are many other ramifications


Added the Decoder part to svm decoding

More user-friendly approach to decoding.

I propose to do one more thing:  add the Frem estimator for better maps

Thanks a lot for this @bthirion!

Please check whether the whole thing compiles. I'm still struggling with it.


aws-partition not found

when im using the command (make build-android) it gives me a error like aws-partition not found..can anyone know about this?any help ?

Hi @cibinstark123 you need to install fastlane..
change directory to the fastlane folder, run bundle install and it should be good to go as long as you  have all the requirements.
more info here https://developers.mattermost.com/contribute/mobile/build-your-own/

@cibinstark123 Were you able to run this? Can we close the issue?

We haven't received an update so we'll assume that the problem is fixed or is no longer valid.
If the issue persists, reopen this issue with the relevant information and we'd be glad to help you where we can.


layers/meta-balena: Update to v2.44.0

Update meta-balena from 2.31.0 to 2.44.0
Changelog-entry: Update meta-balena from v2.31.0 to v2.44.0
Signed-off-by: Vicentiu Galanopulo<EMAIL_ADDRESS>

Can one of the admins verify this patch?

The board is discontinued


Terraform state support

Add support to save the terraform state for a plan and apply with an existing tfstate file

This issue was fixed in Release 0.5.0-beta.1


TPC benchmark for odp hive tez/llap

Hi,
Have you done any testing on TPC benchmark for odp stack?
I'm comparing bigtop and odp on TPC-DS benchmark, for some queries, odp is faster but for some queries, odp is either so slow or does not return any results.

Hi @lucasbak
Any benchmark?


mesa: fix drivers being ignored on aarch64 linux

Description of changes
Fix the list of drivers being built for aarch64 Linux.
When gallim-drivers, vulkan-drivers, or platforms is passed the "auto" value, then all other values are silently ignored. This will also likely be disallowed in mesa 22.3 specifically because of this issue.
See: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20210 for more information
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

As mesa causes lots of rebuild (this time just on aarch64-linux), the changes take some time to reach master.


[REQUEST] Comments Sorting

is it possible to have comments sorting, if it is then that would be great.

Sorting how? Alphabetical by Youtube display name? By time posted? Most thumbs up?
I think what you're asking is a lot more work that you might realize. I don't see this request getting finished anytime in the near future unfortunately. I also don't see much value added by having it versus the amount of effort required to develop it.


A progress bar for s3_bionty_assets

@Zethson Not urgent! Could you add a progress bar to the s3_bionty_assets function when download occurs?

We can only create a progressbar for things that are Iterable easily. Think this one is on @Koncopd who maintains our UPath implementation I guess


The initial set of for Joxa

This is not complete functionality at all. However, these individual commits are complete and should make it into the code base.

so that is a print out of the ast that the compiler compiles into. Its compilable with normal erlang compiler. Its basically generated code, and is regenerated each release. If we dont have this a joxa user will need joxa to compile itself. That can get hairy so this makes that bootstrap process much much easier.

But what about the fact that it is hard coded? Example:
{c_module,
[11,{file,"/home/emerritt/workspace/joxa/src/joxa/compiler.jxa"}],
{c_literal,


untested yet but easy check to remove a seg fault when a custom stl r…

…eader doesn't provide an mitk::Surface
Signed off by Ingmar!

I just improved on this workaround, created https://github.com/MITK/MITK/pull/184

Closing old pull requests. Please leave a comment if you think that this pull request still really needs to be addressed , thank you. I guess #184 is the updated version of this PR?


[24.05] nixos/regreet: Unclear NixOS rebuild failure wiith regreetd package.

Describe the bug
A clear and concise description of what the bug is.
I updated my Flake lockfile for 24.05, and started having this error:
error: The option `programs.regreet.cursorTheme' does not exist. Definition values:
       - In `/nix/store/k5zm4zdrgbn0483a4pxgz1pb49a266hm-modules/regreet/nixos.nix':
           {
             _type = "if";
             condition = false;
             content = {
               name = "Vanilla-DMZ";
           ...

I've disabled greetd and switched back to GDM, but no joy. I can't get any other context, even with --show-trace. Due to restrictions, I am unable to release the source code to my NixOS flake.
I'm not actually sure what commit caused this regression, but when I did have greetd enabled, I used gtkgreet.
Steps To Reproduce
Unable to provide sources at this time.
Expected behavior
The NixOS configuration is to build correctly.
Screenshots
Logs provided above.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.48-xanmod1, NixOS, 24.05 (Uakari), 24.05.20240925.759537f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.7`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Apologies for not being able to provide configuration. I can try to extract sources if requested.

It'd be best if you did that. Give us the minimal config that makes the error appear.

It's a very complex config. Even a minimal config would take a while to create.
However, I've rolled back the Nixpkgs inputs, and I've got a known working Flake on this 24.05 commit. There's no issues building on that commit. All of my configs use 24.05 as a base, and greetd is enabled in conjunction with the linked SHA-1.

Yep, will do as soon as I'm back at my workstation. Thank you, apologies for any confusion with my tests.

You're going to have to figure out which part of your config sets the option anyways btw.

I just noticed that the option set here does not exist on 24.05 yet. It's obviously going to fail if you try to set it. (Note that the module system intentionally checks for options definitions even if you "disable" them via mkIf.)
This looks like an error in your config to me.

Right, but I don't have any settings relating to regreetd. That's what is puzzling. Attached is my greetd config:
Can we re-open this?
default.nix.txt

I am not able to repro this issue by including that config into mine (modulo duplicate settings).
Please cut your config down to the minimum config that actually reproduces the issue. In that process you're likely going to find an error in your config.
I'd start by grepping your config for cursorTheme. If it's any more than 0 results, there's your issue.
I closed this issue because the issue you're seeing could not possibly be caused by NixOS 24.05 because the option simply does not exist in that version. Attempting to use a non-existant option is user error no matter how you look at it.

@shymega If you are using stylix it looks like your problem is being caused by the interaction of nixpkgs updates and stylix's inclusion of said updates: https://github.com/danth/stylix/issues/577

Sorry for my silence. I was preparing a repo which has two branches for working out where the issue is - but, I would never have guessed it was Stylix.
It does appear to build now, thank you for the heads-up @aswan89! I think there's a lesson to be learned on my side here - cut down on dependencies.
I think we can close this as Resolved, given we've found a fix.

This never was a nixpkgs issue to begin with.

Fair enough. Apologies.