Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

jsvd
Copy link
Member

@jsvd jsvd commented Nov 18, 2024

No description provided.

@donoghuc donoghuc self-assigned this Nov 19, 2024
@donoghuc
Copy link
Contributor

Assigned myself to look in to the failures in the RUFUS_SCHEDULER_VERSION=3.0.9 cells.

From ruby/uri#107:

```
This pull-request switched URI::DEFAULT_PARSER to URI::RFC3986_Parser. And I added switch-back feature for URI::RFC2396_Parser.

URI.parser = URI::RFC2396_PARSER
```
If the `URI::RFC2396_PARSER` constant is not defined (using an older URI lib) then fall back to using the default.
Copy link
Contributor

@donoghuc donoghuc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the 7.x tests it looks like the environment had an old uri lib without the new constant defined. Tests were failing with:

logstash-1  |        Failure/Error: raise LogStash::ConfigurationError, "Invalid URL #{url}" unless URI::RFC2396_PARSER.regexp[:ABS_URI].match(url)
logstash-1  |
logstash-1  |        NameError:
logstash-1  |          uninitialized constant URI::RFC2396_PARSER
logstash-1  |          Did you mean?  URI::RFC2396_Parser
logstash-1  |                         URI::RFC3986_Parser
logstash-1  |                         URI::RFC3986_PARSER

I pushed to the commit updating the constant to handle both cases by determining if the new constant is defined. If not defined, it uses the old value.

@donoghuc donoghuc removed their assignment Nov 20, 2024
@donoghuc
Copy link
Contributor

@jsvd I will wait for you to get a chance to double check my addition to your commit before merging.

@jsvd jsvd merged commit b0c82dc into main Nov 21, 2024
3 checks passed
@jsvd jsvd deleted the jsvd-patch-2 branch November 21, 2024 13:05
@jsvd
Copy link
Member Author

jsvd commented Nov 21, 2024

@donoghuc thanks for that addition, merged 🚢

@robbavey
Copy link
Contributor

@jsvd Should this be released, given the URI gem change? Is this something that could bite actual users of the plugin, or just relevant in tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants