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

ASCII-incompatible escape #1239

Closed
wants to merge 1 commit into from

Conversation

nobu
Copy link
Member

@nobu nobu commented Feb 5, 2016

  • lib/cgi/util.rb (escapeHTML, unescapeHTML): consider
    ASCII-incompatible encodings.

Fix GH-333

@xibbar
Copy link

xibbar commented Feb 5, 2016

Thanks @nobu, please merge and close.

@nobu nobu force-pushed the bug/CGI.ASCII-incompatible-escapeHTML branch from 1bec0de to 71bca70 Compare February 6, 2016 13:11
* lib/cgi/util.rb (escapeHTML, unescapeHTML): consider
  ASCII-incompatible encodings.  [Fix rubyGH-1239]
@nobu nobu force-pushed the bug/CGI.ASCII-incompatible-escapeHTML branch from 71bca70 to aff08f0 Compare February 6, 2016 13:13
@nobu nobu closed this Feb 6, 2016
@nobu nobu deleted the bug/CGI.ASCII-incompatible-escapeHTML branch February 6, 2016 13:31
hsbt pushed a commit that referenced this pull request Feb 6, 2016
* lib/cgi/util.rb (escapeHTML, unescapeHTML): consider
  ASCII-incompatible encodings.  [Fix GH-1239]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@53754 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
mrkn pushed a commit to mrkn/ruby that referenced this pull request Apr 17, 2016
* lib/cgi/util.rb (escapeHTML, unescapeHTML): consider
  ASCII-incompatible encodings.  [Fix rubyGH-1239]

git-svn-id: svn+ssh://svn.ruby-lang.org/ruby/trunk@53754 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
hsbt pushed a commit that referenced this pull request May 8, 2020
…ed again.

Originally, the call to `.stubs_for` allowed to incrementally populate
the `@@stubs_by_name` (especially see the `"#{name}-*.gemspec"` pattern
in 4fa03bb7aac9f25f44394e818433fdda9962ae8d). Now it looks like it
expects that all stubs are loaded, but the `.stubs_for` still matches
the .gemspec files by the `name` pattern:

https://github.com/rubygems/rubygems/blob/6d45e0f7ac1caca22900e39f703e226c4cfdebf7/lib/rubygems/specification.rb#L845

I think this was done by mistake incrementally by PR #1239 and
4cee8ca9199ac7b3ab8647e0b78615f55d3eb02b. I think the best option is to
get back to the original implementation, to let RubyGems incrementally
populate the array. Other option would be to replace the logic in
`.stub_for` by call to `.stubs`, but the means the performance
improvement from the original commit was lost.

rubygems/rubygems@4d0e18185a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants