Leo Fang
IIUC this is what conda-forge uses https://github.com/conda-forge/conda-forge-webservices/blob/8270ca82920d7585ef20c0670d3b97351b20f353/conda_forge_webservices/feedstock_outputs.py#L276-L313 For security reasons, conda-forge first pushes a package to the `cf-staging` channel, then copies it to `cf-post-staging`, finally to `conda-forge`: https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens
@copilot let's do the following steps to resolve this issue: 1. Fix the bug that Ben mentioned above. It should be as simple as removing the type assertion and adding...
`ltoir` tests are added in #890, but not `fatbin`, `object`, or `library`
@isVoid added nvFatbin bindings in #1467. We can test the fatbin coverage now!
/ok to test [78092f0](https://github.com/NVIDIA/cuda-python/pull/1479/commits/78092f09be6841e873e2cf65ab04734bc772dba8)
/ok to test [2fde90e](https://github.com/NVIDIA/cuda-python/pull/1479/commits/2fde90e9186a6b0b0d0cb4df50b9117c82934d77)
`CUDA_ERROR_UNKNOWN` seems to be new.
The linked comment had `CUDA_ERROR_INVALID_VALUE`.
> What could explain that? I.e. does the 581 driver support RDMA, but the 591 driver does not, for the exact same hardware? Yes most likely it's the case. Please...