For gem edit pages, build a new linkset if gem is missing one#1844
Closed
kerrizor wants to merge 1 commit into
Closed
For gem edit pages, build a new linkset if gem is missing one#1844kerrizor wants to merge 1 commit into
kerrizor wants to merge 1 commit into
Conversation
We have a few places where we work around the issue of a gem not having an associated linkset record, so this at least is in that genre of change. This was reported to us via the support site; something about that user's gemspec is funky, and a linkset isn't being created. The unusual thing is that this user attempted to edit via the web UI, and I wouldn't be surprised if this is a low-traffic action, which would explain why we wouldn't have seen this error crop up previously. http://help.rubygems.org/discussions/problems/34216-unable-to-edit-newly-published-gem-server-error
Contributor
Author
|
@sonalkr132 and I chatted and we're not going to merge this at this time, as the entire linkset form is going away |
kerrizor
deleted the
kerrizor/build-new-linkset-if-missing-for-gem-edit-pages
branch
Member
|
See #1815 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We have a few places where we work around the issue of a gem not having
an associated linkset record, so this at least is in that genre of
change.
This was reported to us via the support site; something about that
user's gemspec is funky, and a linkset isn't being created. The unusual
thing is that this user attempted to edit via the web UI, and I wouldn't
be surprised if this is a low-traffic action, which would explain why we
wouldn't have seen this error crop up previously.
http://help.rubygems.org/discussions/problems/34216-unable-to-edit-newly-published-gem-server-error