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

IsLatest set to multiple versions for some packages #2514

Open
bhuvak opened this issue May 27, 2015 · 5 comments
Open

IsLatest set to multiple versions for some packages #2514

bhuvak opened this issue May 27, 2015 · 5 comments

Comments

@bhuvak
Copy link
Contributor

bhuvak commented May 27, 2015

We had a customer reporting issue around viewing profile page : #2494

On debugging, it turned out to be an issue with IsLatest being set on multiple versions on one of packages owned by the user and hence exception is thrown by "FindPackagesByOwner" in packageservice. We need fix the existing data and also see how we end up in that state.

@bhuvak bhuvak added this to the 3.0.0 RTM milestone May 27, 2015
@bhuvak bhuvak modified the milestones: S2, 3.0.0 RTM Jun 1, 2015
@bhuvak bhuvak self-assigned this Jun 1, 2015
@maartenba
Copy link
Contributor

I can take this one if you want? Feel free to reassign.

@yishaigalatzer
Copy link

@ryuyu can you check if this is still a thing?

@skofman1
Copy link
Contributor

skofman1 commented Jan 6, 2017

@chenriksson , can you please cost this?

@skofman1 skofman1 added this to the 2.13.2017 milestone Feb 9, 2017
@skofman1 skofman1 added this to the S115 - 2017.3.6 milestone Mar 4, 2017
@skofman1 skofman1 removed this from the S114 - 2017.2.13 milestone Mar 4, 2017
@joelverhagen joelverhagen reopened this Mar 20, 2017
chenriksson added a commit that referenced this issue Mar 25, 2017
…dateIsLatest calls on same package (#3548)"

This reverts commit 27ea9bc.
@chenriksson
Copy link
Member

Re-opening; reverted since fix wasn't complete, and need to do more testing.

@scottbommarito
Copy link
Contributor

We have an OPS task that runs a script on the DB to resolve any of these problems.

Can we run this script periodically automatically and remove it from the on-call tasks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants