chunlin xiao

I had the same problem on the master branch. env files successfully created! [+] Building 16.6s (0/1) [+] Building 17.2s (1/1) FINISHED => ERROR [internal] booting buildkit 17.2s => =>...

after setting ENV variables, run DOCKER_BUILDKIT=0 docker-compose up --build manually, it succed to start. but there were still many warnings during image building.

I added some print to jit.py if not re.search(r"^def\s+\w+\s*\(", self.src, re.MULTILINE): print(f"\n\n========src=========\n|{self.src}|\n\n=============\n") print(f"\n=========fn=========\n|{fn}||{fn.__name__}|\n\n=============\n") print(f"\n=========module=====\n|{fn.__module__}|\n\n=============\n") and the outputs are ========src========= |d| ============= =========fn========= |||_fwd_kernel_splitK| ============= =========module===== |xformers.ops.fmha.triton_splitk| ============= It seams that...

> As a workaround, and if you don't need any triton kernel from xformers, you can try setting this env variable: `XFORMERS_FORCE_DISABLE_TRITON=1` this workaround did work. I am using vllm...

I did some investigation. I add some prints to /xformers/triton/vararg_kernel.py ``` @functools.lru_cache(None) def unroll_varargs(kernel, N: int): """ Specializes a triton kernel with variable number of inputs to a specific number...