[#107430] [Ruby master Feature#18566] Merge `io-wait` gem into core IO — "byroot (Jean Boussier)" <noreply@...>
Issue #18566 has been reported by byroot (Jean Boussier).
22 messages
2022/02/02
[ruby-core:107659] [Ruby master Bug#18593] URI escape compatibility function?
From:
"kallisti5 (Alexander von Gluck)" <noreply@...>
Date:
2022-02-18 19:33:31 UTC
List:
ruby-core #107659
Issue #18593 has been reported by kallisti5 (Alexander von Gluck).
----------------------------------------
Bug #18593: URI escape compatibility function?
https://bugs.ruby-lang.org/issues/18593
* Author: kallisti5 (Alexander von Gluck)
* Status: Open
* Priority: Normal
* ruby -v: 3.0.3p157
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
It seems like there should have been a compatibility call left in place for the removal of URI escape between stdlib 2.x and 3.x
As seen here:
https://github.com/qoobaa/s3/issues/132
Various projects are breaking due to the move of escape to DEFAULT_PARSER
```
--- /home/kallisti5/.gem/ruby/3.0.0/gems/s3-0.3.29/lib/s3/bucket.rb.original 2022-02-18 13:26:37.247078560 -0600
+++ /home/kallisti5/.gem/ruby/3.0.0/gems/s3-0.3.29/lib/s3/bucket.rb 2022-02-18 13:26:47.707146732 -0600
@@ -151,7 +151,7 @@
# If there are more than 1000 objects S3 truncates listing and
# we need to request another listing for the remaining objects.
while parse_is_truncated(response.body)
- next_request_options = {:marker => URI.escape(objects_attributes.last[:key])}
+ next_request_options = {:marker => URI::DEFAULT_PARSER.escape(objects_attributes.last[:key])}
if max_keys
break if objects_attributes.length >= max_keys
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>