tag:help.rubygems.org,2010-01-19:/discussions/problems/34216-unable-to-edit-newly-published-gem-server-errorRubyGems.org: Discussion 2018-12-25T16:16:44Ztag:help.rubygems.org,2010-01-19:Comment/464055032018-11-01T14:42:04Z2018-11-01T14:42:04ZUnable to edit newly published gem - Server Error.<div><p>The spec looks ok to my quick scan of it, and I'm actually not seeing anything in our logs about an error.. hmm, I'm wondering, did you add or change the homepage link but not publish a new version of the gem? The last version payload I have a record for is for <code>1.0.0.beta3</code> and that payload did <em>not</em> include a homepage URL.. perhaps try publishing <code>1.0.0.beta3.1</code> and see if it updates?</p>
<p>In the meanwhile, I'll poke around a bit more and see if I can locate some kind of error log that would've been recorded when you received that <code>server error</code> message; we did have a minor service degradation a few hours ago, but I doubt it is related.</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/464055032018-11-01T22:11:22Z2018-11-01T22:43:45ZUnable to edit newly published gem - Server Error.<div><p>Hi kerrizor,</p>
<p>Thanks for responding!</p>
<blockquote>
<p>The last version payload I have a record for is for 1.0.0.beta3 and that payload did not include a homepage URL</p>
</blockquote>
<p>That's strange. How did you figure this out? The homepage URL is in the gemspec and I can see it when I <code>unpack</code> the gem file for beta3. Actually, it has been there in all releases so far. Here are the steps I have been following:</p>
<pre>
<code>gem build ffmpeg-screenrecorder.gemspec
gem push ffmpeg-screenrecorder-1.0.0.beta3.gem</code>
</pre>
<p>The server error is happening to me every time I click the "Edit" link. I have attached a GIF recording so you can see the server error (Timestamp should be around 15:10 PDT) in action and my steps to <code>unpack</code> and verify the homepage url in the gemspec.</p>
<p><strong>EDIT</strong>: I used <code>bundle exec rake release</code> with the beta4 release and I get the same results - server error and no homepage URL. Wasn't sure if it made a difference and it apparently does not.</p></div>kapoorlakshyatag:help.rubygems.org,2010-01-19:Comment/464055032018-11-03T01:34:21Z2018-11-03T01:34:21ZUnable to edit newly published gem - Server Error.<div><p>Found it! It'll take me a few days to get a fix together, just due to scheduling.. I'll update this issue when its working -- thanks!</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/464055032018-11-04T00:21:20Z2018-11-04T00:21:21ZUnable to edit newly published gem - Server Error.<div><p>Oh, awesome! Please do share what the issue was - I am curious now.</p>
<p>Did you figure out a fix for both the Server Error and the homepage issue? Thanks!</p></div>kapoorlakshyatag:help.rubygems.org,2010-01-19:Comment/464055032018-12-08T17:25:16Z2018-12-08T17:25:16ZUnable to edit newly published gem - Server Error.<div><p>Apologies for the delay in responding - RubyConf got in the way, and then the holiday season kicked into gear here in the US... I'm working on a small patch for the Rubygems.org website, but I wanted to theorize if you'd tried removing the line split (<code>\</code>) on <a href="https://github.com/kapoorlakshya/ffmpeg-screenrecorder/blob/master/ffmpeg-screenrecorder.gemspec#L12">https://github.com/kapoorlakshya/ffmpeg-screenrecorder/blob/master/...</a> - it /shouldn't/ be the culprit, but worth trying?</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/464055032018-12-08T18:03:59Z2018-12-08T18:03:59ZUnable to edit newly published gem - Server Error.<div><p>Quick PR up here: <a href="https://github.com/rubygems/rubygems.org/pull/1844">https://github.com/rubygems/rubygems.org/pull/1844</a></p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/464055032018-12-24T04:57:34Z2018-12-24T04:57:35ZUnable to edit newly published gem - Server Error.<div><p>Looks like the Edit feature was removed altogether to fix the bug .</p>
<p>I'll update the homepage URL to not have the slashes and see if that works. Thanks for responding!</p></div>kapoorlakshyatag:help.rubygems.org,2010-01-19:Comment/464055032018-12-24T05:50:17Z2018-12-24T05:50:18ZUnable to edit newly published gem - Server Error.<div><p>I pushed <code>beta7</code> without the slashes in the <code>description</code> and the Homepage URL still doesn't show up. I compared my gemspec to other gems with a working URL, and I haven't noticed anything obvious.</p></div>kapoorlakshyatag:help.rubygems.org,2010-01-19:Comment/464055032018-12-25T16:16:43Z2018-12-25T16:16:43ZUnable to edit newly published gem - Server Error.<div><p>The edit functionality has been removed by a different PR (<a href="https://github.com/rubygems/rubygems.org/pull/1815">https://github.com/rubygems/rubygems.org/pull/1815</a>) so my patch did not go into effect. The issue with your gem appears to be that we don't update the metadata on "beta" versions. Once you publish a non-beta release (without alphas in the version, if I'm understanding the explanation and code) the data will be updated correctly.</p></div>kerrizor