Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest version to Zenodo did not get synced #4726

Closed
balopat opened this issue Dec 6, 2021 · 7 comments · Fixed by #5421
Closed

Latest version to Zenodo did not get synced #4726

balopat opened this issue Dec 6, 2021 · 7 comments · Fixed by #5421
Labels
area/ecosystem area/releases kind/health For CI/testing/release process/refactoring/technical debt items triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add

Comments

@balopat
Copy link
Contributor

balopat commented Dec 6, 2021

Description of the issue

The last release(s) did not get synced to Zenodo for some reason, it still shows 0.12.0 as the latest.

image

Cirq version
0.13.1

@balopat balopat added the kind/health For CI/testing/release process/refactoring/technical debt items label Dec 6, 2021
@95-martin-orion 95-martin-orion added the triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add label Dec 10, 2021
@95-martin-orion
Copy link
Collaborator

Pinging @MichaelBroughton for insight. We might have missed a step in the 0.13 release - it's possible that the release doc needs to be updated to include this.

@MichaelBroughton
Copy link
Collaborator

I wasn't able to find any docs for how this was setup. I'm like 40% sure I can't access the Cirq Github Zenodo entry here when I log in on the website. https://zenodo.org/record/5182845#.YdapfnXMKUk It appears to be linked to the quantumlib organization via webhooks (although I can't seem to get history on them for some reason), @balopat would you be able to give a little more information on how to access this and test it ?

@balopat
Copy link
Contributor Author

balopat commented May 13, 2022

Hey @MichaelBroughton,

As, after I left Google, my "owner" status on the project was revoked, it probably removed the authorization for the zenodo github automation integration. Reference docs: https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content.

The bad news is that, surprisingly, Zenodo does not support sharing of uploads between multiple users zenodo/zenodo#151 👎 . The good news is that support is coming soon.

Options I see:

  1. I opened a ticket to ask about transferring the ownership in the meantime. Transfer ownership of project zenodo/zenodo#2324 If this is possible, I'll transfer it to your user account.
  2. If you want this earlier, you might have to re-establish my owner status on the Cirq repos in the interim :/
  3. Just wait until (1) is resolved or they deliver deposit: sharing of uploads zenodo/zenodo#151.

Any other thoughts?

@balopat
Copy link
Contributor Author

balopat commented May 13, 2022

Ah, they replied - through support we can transfer the ownership to one person. Who should that be?

I think I have ownership of Cirq, ReCirq and qsim.

@95-martin-orion
Copy link
Collaborator

Ideally it would be a group account, rather than a person, so that if we encounter this again before their multiple-user support goes through we don't have to do this again. Not sure if there's a good account for that, though.

@dstrain115
Copy link
Collaborator

dstrain115 commented May 13, 2022

I have made an account for quacs at google.com. Can we transfer ownership to that account?

I have stored the password in our lovely internal password tool.

@dstrain115
Copy link
Collaborator

Updated Zenodo to cirq 0.14.1 and added instructions on how to do this in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ecosystem area/releases kind/health For CI/testing/release process/refactoring/technical debt items triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants