\x19 seems like the apostrophe character, which might got converted from some of the IDE. I'm trying to fix this but I can't make this test fail in Cucumber:
Scenario: User pushes gem with bad description
Given I am signed up and confirmed as "email@example.com/password"
And I have a gem "PGem" with version "1.0.0" and summary "There\x91s nothing."
And I have an api key for "firstname.lastname@example.org/password"
When I push the gem "PGem-1.0.0.gem" with my api key
And I visit the gem page for "PGem"
Then I should see "PGem"
And I should see "1.0.0"
And I should see "There\x91s nothing."
It's to happen like this: And I have a gem "PGem" with version "1.0.0" and a bogus summary
And I have a gem "PGem" with version "1.0.0" and a bogus summary
Given /^I have a gem "([^\"]*)" with version "([^\"]*)" and a bogus summary$/ do |name, version|
build_gem(name, version, "There\x91s nothing.")
And that blows up psych it seems:
That's actually not even on the POST though, that's just trying to build the gem.
That stack trace is kind of useless too. It actually blows up in rubygems in builder.rb trying to dump to yaml:
Add test for bad characters in description/summary. Case #275
Had to build a broken gem by hand.