duplicate upload

[beckermr]

There appears to have been a duplicate upload.

See this job: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=289075&view=logs&j=4f922444-fdfe-5dcf-b824-02f86439ef14&t=b2a8456a-fb11-5506-ca32-5ccd32538dc0

this is the relevant text:

+ upload_package --validate --feedstock-name=point_cloud_utils-feedstock /home/conda/feedstock_root /home/conda/recipe_root /home/conda/feedstock_root/.ci_support/linux_64_numpy1.16python3.7.____cpython.yaml
Found git SHA 2418755fc2e47d9982c5d34e536a430f7b964010 for this build!
Using STAGING_BINSTAR_TOKEN for anaconda.org uploads to cf-staging.
No numpy version specified in conda_build_config.yaml.  Falling back to default numpy value of 1.16
Adding in variants from internal_defaults
Adding in variants from /home/conda/feedstock_root/.ci_support/linux_64_numpy1.16python3.7.____cpython.yaml
copy results:
{
  "errors": [
    "output linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2 does not have a valid md5 checksum"
  ],
  "valid": {
    "linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2": false
  },
  "copied": {
    "linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2": false
  }
}
Failed to upload due to copy from staging to production channel failed. Trying again in 10 seconds
Using STAGING_BINSTAR_TOKEN for anaconda.org uploads to cf-staging.
INFO:binstar:Using Anaconda API: https://api.anaconda.org

and this gitter discussion:

Daniel Bast @dbast 04:22
Hi… what is the canonical process to delete duplicated files on anaconda.org? … https://anaconda.org/conda-forge/point_cloud_utils/0.17.1/download/linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2 … one version has 0 downloads https://anaconda.org/conda-forge/point_cloud_utils/files

Matthew R. Becker @beckermr 05:39
^ @chenghlee should we file a bug report somewhere? I didn't think this was possible on anaconda.org and I am pretty sure our CI servers don't do duplicate uploads. I could be wrong though.

Cheng H. Lee @chenghlee 08:00
Weird. Looks like a UI issue? The links point to the same URL and the file that comes back has the same etag and modification time. In any case, I've opened a ticket on our internal bug tracker.

Chris Burr @chrisburr 08:02
They have slightly different upload times so I guess the copy request got duplicated somehow
I don't think the URL would have a way to distinguish between them

cc @chenghlee @chrisburr @dbast

We may not be able to diagnose this, but worth starting an issue.

[beckermr]

I found the duplicate upload on anaconda.org

cf-staging added the conda file linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2 to cf-staging/point_cloud_utils | 22 hours and 56 minutes ago
-- | --
cf-staging added the conda file linux-64/point_cloud_utils-0.17.1-py37h6dcda5c_2.tar.bz2 to cf-staging/point_cloud_utils | 22 hours and 56 minutes ago

[jakirkham]

One case where duplicate uploads occur is 2 jobs that upload the same package name around the same time. This is arguably a bug in the feedstock for having 2 duplicate builds and a bug in Anaconda.org for allowing them to happen

[beckermr]

So I looked at the feedstock and there was only one job uploading that package. The webserver rejected the first upload but then somehow it got triggered again.

[jakirkham]

Ok so this is another case. The former is common, but yeah there may be other ways to trigger this issue