Open jakirkham opened 1 year ago
During the recent CircleCI incident, noticed several maintainers were confused about what was actionable for invalid tokens.
Several tried re-rendering (which is what the bot suggests). For example please see this exchange ( https://github.com/conda-forge/jupyter_core-feedstock/issues/67#issuecomment-1376436421 ). However this can add to the problem by oversubscribing CI.
https://github.com/conda-forge/artifact-validation/blob/c3f2eed12918b3d6fed9874f6c18699e8ba59acd/conda_forge_artifact_validation/validate.py#L235
Others didn't know what to do ( https://github.com/conda-forge/magic-feedstock/issues/59#issuecomment-1379781308 )
Think we could add a link to these steps for invalid tokens
This message is from the webservices right now. We didn't finish the artifact validation stuff since it was too flaky.
During the recent CircleCI incident, noticed several maintainers were confused about what was actionable for invalid tokens.
Several tried re-rendering (which is what the bot suggests). For example please see this exchange ( https://github.com/conda-forge/jupyter_core-feedstock/issues/67#issuecomment-1376436421 ). However this can add to the problem by oversubscribing CI.
https://github.com/conda-forge/artifact-validation/blob/c3f2eed12918b3d6fed9874f6c18699e8ba59acd/conda_forge_artifact_validation/validate.py#L235
Others didn't know what to do ( https://github.com/conda-forge/magic-feedstock/issues/59#issuecomment-1379781308 )
Think we could add a link to these steps for invalid tokens