Ensure a value for noarch_platform when rerendering

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #98.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

• Bump the build number if needed

Fixes #98

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try [rerendering locally](https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-with-conda-smithy-locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11149177857.}

[jakirkham]

The error message above is a bit confusing. The actual error is this

conda_build.exceptions.CondaBuildUserError: Failed to render jinja template in /tmp/tmpc1uu4vku/jupyter_core-feedstock/recipe/meta.yaml:
'noarch_platform' is undefined

However that part of the workflow is shown as passing

Is there some way to bubble up the error/traceback for the user?

cc @beckermr

[jakirkham]

@conda-forge-admin , please re-render

[beckermr]

Yes we likely can but it will take some work.

[beckermr]

Also there is a formatting bug I need to fix.

[jakirkham]

Thanks Matt! 🙏

For the 1st one, filed issue: conda-forge/conda-forge-webservices#721

For the 2nd one, filed PR: conda-forge/conda-forge-webservices#723

[Carreau]

@conda-forge-admin , please re-render

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11158669815.}

[bollwyvl]

Seems like a fine change, in line with other things we've had to do elsewhere. Will set to auto-merge... any other context here?

[bollwyvl]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11162152818.}

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[bollwyvl]

Should the 10 other meta.yaml also do this?

[jakirkham]

That or we should file a conda-build issue

A different option would be to try rattler-build and see if that works