[warning] failed package validation and/or copy for commit 95749e707dd1fc59e50e616658d7ae85d4ea656e

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[pavelzw]

2024-11-23T09:12:00.9259790Z ##[group]Inspecting artifacts
2024-11-23T09:12:00.9458530Z + command -v inspect_artifacts
2024-11-23T09:12:00.9640100Z + inspect_artifacts --recipe-dir ./recipe -m ./.ci_support/osx_64_.yaml
2024-11-23T09:12:01.6086040Z WARNING: No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.26
2024-11-23T09:12:01.6570850Z Adding in variants from internal_defaults
2024-11-23T09:12:01.6919280Z Adding in variants from /Users/runner/work/1/s/.ci_support/osx_64_.yaml
2024-11-23T09:12:01.7202210Z ---------------------------------------
2024-11-23T09:12:01.7474770Z osx-64/typstyle-0.12.2-h371c88c_0.conda
2024-11-23T09:12:01.7781570Z ---------------------------------------
2024-11-23T09:12:01.8134110Z -- Size: 591.4KB
2024-11-23T09:12:01.8471550Z -- SHA256: fb33904f13b0c633afca74ecb898d47f55ffeb262f25e89ea20197ae69efb469
2024-11-23T09:12:01.9037010Z -- Contents:
2024-11-23T09:12:01.9494260Z ?rwxrwxr-x 0/0    1663168 2024-11-23 09:11:26 bin/typstyle 
2024-11-23T09:12:01.9844460Z ?rw-r--r-- 0/0       5896 2024-11-23 09:11:36 info/about.json 
2024-11-23T09:12:02.0295660Z ?rw-r--r-- 0/0         13 2024-11-23 09:11:36 info/files 
2024-11-23T09:12:02.0296960Z ?rw-r--r-- 0/0          0 2024-11-23 09:11:36 info/git 
2024-11-23T09:12:02.0330780Z ?rw-r--r-- 0/0        390 2024-11-23 09:11:35 info/hash_input.json 
2024-11-23T09:12:02.0356250Z ?rw-r--r-- 0/0        296 2024-11-23 09:11:35 info/index.json 
2024-11-23T09:12:02.0396420Z ?rw-rw-r-- 0/0      11357 2024-11-23 04:22:06 info/licenses/LICENSE 
2024-11-23T09:12:02.0459650Z ?rw-r--r-- 0/0     680070 2024-11-23 09:09:11 info/licenses/THIRDPARTY_LICENSES.yaml 
2024-11-23T09:12:02.0490490Z ?rw-r--r-- 0/0        231 2024-11-23 09:11:36 info/paths.json 
2024-11-23T09:12:02.0498820Z ?rw-r--r-- 0/0        249 2024-11-23 09:03:22 info/recipe/bld.bat 
2024-11-23T09:12:02.0524400Z ?rw-r--r-- 0/0        197 2024-11-23 09:03:22 info/recipe/build.sh 
2024-11-23T09:12:02.0532970Z ?rw-r--r-- 0/0        871 2024-11-23 09:11:36 info/recipe/conda_build_config.yaml 
2024-11-23T09:12:02.0547550Z ?rw-r--r-- 0/0       2297 2024-11-23 09:11:36 info/recipe/meta.yaml 
2024-11-23T09:12:02.0588420Z ?rw-r--r-- 0/0        727 2024-11-23 09:03:22 info/recipe/meta.yaml.template 
2024-11-23T09:12:02.0622160Z ?rw-r--r-- 0/0       1541 2024-11-23 09:05:18 info/recipe/recipe-scripts-license.txt 
2024-11-23T09:12:02.0639240Z ?rw-r--r-- 0/0         39 2024-11-23 09:11:36 info/test/run_test.sh 
2024-11-23T09:12:02.0652260Z ##[endgroup]
2024-11-23T09:12:02.0671500Z ##[group]Validating outputs
2024-11-23T09:12:02.0686220Z + validate_recipe_outputs typstyle-feedstock
2024-11-23T09:12:02.4349520Z WARNING: No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.26
2024-11-23T09:12:02.4856350Z Adding in variants from internal_defaults
2024-11-23T09:12:02.4887170Z Adding in variants from /Users/runner/work/1/s/.ci_support/osx_64_.yaml
2024-11-23T09:12:02.8138950Z validation results:
2024-11-23T09:12:02.8147010Z {
2024-11-23T09:12:02.8173000Z   "osx-64/typstyle-0.12.2-h371c88c_0.conda": true
2024-11-23T09:12:02.8201890Z }
2024-11-23T09:12:02.8232430Z NOTE: Any outputs marked as False are not allowed for this feedstock. See https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens for information on how to address this error.
2024-11-23T09:12:02.9229620Z ##[endgroup]
2024-11-23T09:12:02.9253400Z ##[group]Uploading packages
2024-11-23T09:12:02.9287740Z + [[ True != \F\a\l\s\e ]]
2024-11-23T09:12:02.9329020Z + [[ False == \F\a\l\s\e ]]
2024-11-23T09:12:02.9363510Z + upload_package --validate --feedstock-name=typstyle-feedstock ./ ./recipe ./.ci_support/osx_64_.yaml
2024-11-23T09:12:04.6036020Z Found git SHA 95749e707dd1fc59e50e616658d7ae85d4ea656e for this build!
2024-11-23T09:12:04.6064210Z Using STAGING_BINSTAR_TOKEN for anaconda.org uploads to cf-staging.
2024-11-23T09:12:04.6679560Z WARNING: No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.26
2024-11-23T09:12:04.7218010Z Adding in variants from internal_defaults
2024-11-23T09:12:04.7252890Z Adding in variants from /Users/runner/work/1/s/.ci_support/osx_64_.yaml
2024-11-23T09:12:08.1613430Z 
2024-11-23T09:12:08.2666530Z   0%|          | 0.00/591k [00:00<?, ?B/s]
2024-11-23T09:12:08.3866460Z   3%|▎         | 16.0k/591k [00:00<00:03, 158kB/s]
2024-11-23T09:12:08.5078250Z  32%|███▏      | 192k/591k [00:00<00:00, 989kB/s] 
2024-11-23T09:12:08.6449200Z  97%|█████████▋| 576k/591k [00:00<00:00, 2.05MB/s]
2024-11-23T09:12:08.6483990Z 597kB [00:00, 1.27MB/s]                           
2024-11-23T09:12:09.7469370Z ERROR getting output validation information from the webservice: JSONDecodeError('Expecting value: line 1 column 1 (char 0)')
2024-11-23T09:12:09.7477810Z copy results:
2024-11-23T09:12:09.7496580Z {}
2024-11-23T09:12:09.7569900Z Failed to upload due to copy from staging to production channel failed. Trying again in 10 seconds
2024-11-23T09:12:19.9579020Z Using STAGING_BINSTAR_TOKEN for anaconda.org uploads to cf-staging.
2024-11-23T09:12:19.9698530Z INFO:binstar:Using Anaconda API: https://api.anaconda.org
2024-11-23T09:12:21.0453950Z Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already exists on cf-staging. Waiting another 15 seconds to try uploading again.
2024-11-23T09:12:36.5076590Z Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already exists on cf-staging. Waiting another 30 seconds to try uploading again.
2024-11-23T09:13:07.2599350Z Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already exists on cf-staging. Waiting another 45 seconds to try uploading again.
2024-11-23T09:13:52.8843000Z Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already exists on cf-staging. Waiting another 60 seconds to try uploading again.
2024-11-23T09:14:53.4493710Z Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already exists on cf-staging. Waiting another 75 seconds to try uploading again.
2024-11-23T09:14:53.4495820Z WARNING: Distribution /Users/runner/miniforge3/conda-bld/osx-64/typstyle-0.12.2-h371c88c_0.conda already existed in cf-staging for a while. Deleting and re-uploading.
2024-11-23T09:14:58.0573600Z 
2024-11-23T09:14:58.2270290Z   0%|          | 0.00/591k [00:00<?, ?B/s]
2024-11-23T09:14:58.3360120Z  27%|██▋       | 160k/591k [00:00<00:00, 967kB/s]
2024-11-23T09:14:58.4863430Z  70%|███████   | 416k/591k [00:00<00:00, 1.66MB/s]
2024-11-23T09:14:58.4864550Z 597kB [00:00, 1.43MB/s]                           
2024-11-23T09:15:06.0413900Z ERROR getting output validation information from the webservice: JSONDecodeError('Expecting value: line 1 column 1 (char 0)')
2024-11-23T09:15:06.0416100Z copy results:
2024-11-23T09:15:06.0416750Z {}
2024-11-23T09:15:06.0417490Z Failed to upload due to copy from staging to production channel failed. Trying again in 10 seconds
2024-11-23T09:15:16.1631600Z Using STAGING_BINSTAR_TOKEN for anaconda.org uploads to cf-staging.
2024-11-23T09:15:16.1695850Z INFO:binstar:Using Anaconda API: https://api.anaconda.org

[pavelzw]

i triggered a rerun https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1089062&view=results

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token

[conda-forge-webservices[bot]]

Hi @conda-forge/typstyle! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock token or your feedstock not having permissions to upload the given package. Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request a feedstock token reset via our admin-requests repo.
• Request that any new packages be added to the allowed outputs for the feedstock via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.). In this case, you can use our admin-requests repo to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax. Output packages that match these patterns will be automatically registered for your feedstock.

If you have any issues or questions, you can find us on Zulip in the community channel or you can bump us right here.

error messages:

• invalid feedstock token