-
Notifications
You must be signed in to change notification settings - Fork 128
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
globalid is broken with Ruby 3.4 / URI 1.0.2 #190
Comments
So after analysis, I believe that this is the culprit:
The easy fix could be to keep using the |
voxik
added a commit
to voxik/globalid
that referenced
this issue
Dec 13, 2024
The default parser in URI 1.0.0 / Ruby 3.4 has been changed to RFC3986 [[1]]. This causes test failures such as: ~~~ ... snip ... Failure: GlobalIDTest#test_invalid_app_name [test/cases/global_id_test.rb:13]: ArgumentError expected but nothing was raised. rails test test/cases/global_id_test.rb:8 F ... snip ... ~~~ where underscores / ampersands are now allowed in host. Keep using `URI::RFC2396_PARSER` for compatibility. Fixes rails#190 [1]: ruby/uri#107
voxik
added a commit
to voxik/globalid
that referenced
this issue
Dec 13, 2024
The default parser in URI 1.0.0 / Ruby 3.4 has been changed to RFC3986 [[1]]. This causes test failures such as: ~~~ ... snip ... Failure: GlobalIDTest#test_invalid_app_name [test/cases/global_id_test.rb:13]: ArgumentError expected but nothing was raised. rails test test/cases/global_id_test.rb:8 F ... snip ... ~~~ where underscores / ampersands are now allowed in host. Keep using URI RFC2396 parser for compatibility. Fixes rails#190 [1]: ruby/uri#107
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing globalid against Ruby 3.4, I observe errors such as:
Looking into root cause, it seems that this is due to change in URI, which now accepts underscore / ampersand as a host. I have reported the issue here
The text was updated successfully, but these errors were encountered: