Isuru Fernando comments

Results 928 comments of


                                            Isuru Fernando

AttributeError: '_OpNamespace' 'fbgemm' object has no attribute 'jagged_2d_to_dense'

> When building latest Pytorch from src and install fbgemm_nightly via pip This is not expected to work as Pytorch will be compiled with C++11 ABI when you build from...

jinja2 variable named like global pin causes it to be included in rerender CI yaml

> Of course, this is trouble for the repo that provides libpq itself! How so?

jinja2 variable named like global pin causes it to be included in rerender CI yaml

In any case, this is not a conda-smithy issue, but a conda-build issue.

jinja2 variable named like global pin causes it to be included in rerender CI yaml

> The postgresql-feedstock provides libpq How is adding the `libpq=15` pin a problem here? It's harmless.

jinja2 variable named like global pin causes it to be included in rerender CI yaml

> the metadata of the built artifact ends up including libpq=15. Which metadata?

jinja2 variable named like global pin causes it to be included in rerender CI yaml

> see [build log](https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/639277/logs/54) As I said before, that's harmless.

jinja2 variable named like global pin causes it to be included in rerender CI yaml

Ok. This is still a conda-build issue and not a conda-smithy issue.

Define the `cache` key for v1 multi-output recipes

Another option is ```yaml requirements: ignore_run_exports: from_cache: - ``` which feels natural given we have `from_package` and `by_name`

Define the `cache` key for v1 multi-output recipes

IMO inheriting requirements is a bad idea in general because it will result in cryptic solve errors. 1 and 3 of @wolfv's suggestions will lead to solve errors. I don't...

Adding `host_exports` (like `run_exports` except between `build` & `host` only)

Overall I like the idea. I proposed the same thing when v1 was being developed, but there was no interest. I'm having a hard time finding the conversation though. More...