Test PyPI failing due to accidental publishes from another branch

[JessicaS11]

Since the transition to pyproject.toml(#539), we routinely get failures of the testPyPI action after it's merged into development (e.g. here):

 Uploading icepyx-1.1.1.dev11-py3-none-any.whl
WARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/          
         File already exists. See https://test.pypi.org/help/#file-name-reuse   
         for more information.  

Anyone know why these are happening (even after #541)?

[mfisher87]

Uploading icepyx-1.1.1.dev11-py3-none-any.whl ... File already exists

The file for dev11 was uploaded on August 12 -- our CI should be trying to upload dev12 instead, correct?

https://test.pypi.org/project/icepyx/1.1.1.dev11/

[mfisher87]

Would you like to have a zoom chat tomorrow? I know you're preparing for the hack week and I want to take as much load off your plate on this as I can. Apologies for the inconvenience of whatever it was we missed here!

[weiji14]

Hmm, I'm looking at the publish_to_pypi.yml and see that the trigger should only be on pushes to the development branch, on release, or workflow_dispatch:

icepyx/.github/workflows/publish_to_pypi.yml

Lines 4 to 13 in c85baec

	# Only run for tagged releases and pushes to the development branch
	on:
	release:
	types:
	- published
	push:
	branches:
	- development
	# Trigger manually at https://github.com/icesat2py/icepyx/actions/workflows/publish_to_pypi.yml
	workflow_dispatch:

But the Actions tab is showing the workflow running on both development and v2 branches?

Did someone trigger the GitHub Action manually on the v2 branch? That could be why there were duplicate .devXX TestPyPI builds.

[mfisher87]

Ahh shoot. Thanks for figuring that out! That was my mistake. I deliberately set some actions to run on the v2 branch, because it will be long-running, but I should not have done so with this action.

[JessicaS11]

That could be why there were duplicate .devXX TestPyPI builds.

Thanks for figuring that out, @weiji14!

I deliberately set some actions to run on the v2 branch, because it will be long-running, but I should not have done so with this action.

Makes sense - I assume that if we disable this action from the ones you have running on v2 we'll be all set?

[mfisher87]

Yes, I did that immediately when @weiji14 realized my mistake. Should be good going forward! Apologies all 😬

[mfisher87]

I think we're good to close this as resolved