Anaconda Cloud now causes error and package removal for upload of package version of same name #702
Comments
|
This behavior also seems to be invalidating the $ anaconda --version
anaconda Command line client (version 1.12.1)
$ anaconda upload --help
usage: anaconda upload [-h] [-c CHANNELS] [-l LABELS] [--no-progress] [-u USER] [--keep-basename] [-p PACKAGE] [-v VERSION] [-s SUMMARY] [-t PACKAGE_TYPE] [-d DESCRIPTION] [--thumbnail THUMBNAIL]
[--private] [--no-register | --register] [--build-id BUILD_ID] [-i | -f | --force | --skip-existing | -m]
files [files ...]
Upload packages to your Anaconda repository
positional arguments:
files Distributions to upload
options:
-h, --help show this help message and exit
-c CHANNELS, --channel CHANNELS
[DEPRECATED] Add this file to a specific channel. Warning: if the file channels do not include "main", the file will not show up in your user channel
-l LABELS, --label LABELS
Add this file to a specific label. Warning: if the file labels do not include "main", the file will not show up in your user label
--no-progress Don't show upload progress
-u USER, --user USER User account or Organization, defaults to the current user
--keep-basename Do not normalize a basename when uploading a conda package.
--no-register Don't create a new package namespace if it does not exist
--register Create a new package namespace if it does not exist
--build-id BUILD_ID Anaconda repository Build ID (internal only)
-i, --interactive Run an interactive prompt if any packages are missing
-f, --fail Fail if a package or release does not exist (default)
--force Force a package upload regardless of errors
--skip-existing Skip errors on package batch upload if it already exists
-m, --force-metadata-update
Overwrite existing release metadata with the metadata from the package.
...which is being used in the relevant code of scientific-python/upload-nightly-action#57. |
|
@csoja @yshmatov-anaconda @vshevchenko-anaconda Can you please comment here, or tag people on the relevant teams? This is API breaking behavior changes and so quite serious. |
|
@kenodegard @dholth as you're currently reviewing PRs for the project, can you please either comment on this or notify the relevant teams? |
|
We have notified the relevant teams. |
Thanks very much @dholth. I appreciate it. |
|
What is intersting about scikit-hep/awkward#3012 (comment) though, where you are attempting to upload mutliple wheels that have the same name each run of the uploader (no vcs information in the wheel name), is that it seems that for repeated uploads things aren't fully replicable. In the case of Awkward uploading to the first run of workflow However, if I then trigger a rerun of the workflow through GitHub Actions, the upload of second run of workflow This is quite strange. (cc @jpivarski) |
|
@dholth Ah. I think I understand what is happening now (summarized in scientific-python/upload-nightly-action#57 (comment)). This might already have been obvious to you/the relevant teams. The package directory is getting removed by the backend in mid-upload as it detects that the only file in the package has been removed. This somehow changed in January 2024(?). Is it possible to have this cleanup logic know that it got triggered during an upload attempt and have it wait until after the upload finishes to see if it should delete the package from the registry? In the where to interact with https://api.anaconda.org (where I guess the API behavior change that we're seeing took place?). |
|
Closed as release |
Copying scientific-python/upload-nightly-action#57 here to get feedback from the Anaconda team. This is a breaking behavior change, so advice on how to proceed would be quite welcome.
The text was updated successfully, but these errors were encountered: