Bump rexml from 3.3.7 to 3.3.9 in /examples/ruby

[dependabot]

Bumps rexml from 3.3.7 to 3.3.9.

Release notes

Sourced from rexml's releases.

REXML 3.3.9 - 2024-10-24

Improvements

• Improved performance.
  • GH-210
  • Patch by NAITOH Jun.

Fixes

• Fixed a parse bug for text only invalid XML.

  • GH-215
  • Patch by NAITOH Jun.

• Fixed a parse bug that &#0x...; is accepted as a character reference.

Thanks

• NAITOH Jun

REXML 3.3.8 - 2024-09-29

Improvements

• SAX2: Improve parse performance.
  • GH-207
  • Patch by NAITOH Jun.

Fixes

• Fixed a bug that unexpected attribute namespace conflict error for the predefined "xml" namespace is reported.
  • GH-208
  • Patch by KITAITI Makoto

Thanks

• NAITOH Jun

• KITAITI Makoto

Changelog

Sourced from rexml's changelog.

3.3.9 - 2024-10-24 {#version-3-3-9}

Improvements

• Improved performance.
  • GH-210
  • Patch by NAITOH Jun.

Fixes

• Fixed a parse bug for text only invalid XML.

  • GH-215
  • Patch by NAITOH Jun.

• Fixed a parse bug that &#0x...; is accepted as a character reference.

Thanks

• NAITOH Jun

3.3.8 - 2024-09-29 {#version-3-3-8}

Improvements

• SAX2: Improve parse performance.
  • GH-207
  • Patch by NAITOH Jun.

Fixes

• Fixed a bug that unexpected attribute namespace conflict error for the predefined "xml" namespace is reported.
  • GH-208
  • Patch by KITAITI Makoto

Thanks

• NAITOH Jun

• KITAITI Makoto

Commits

• 38eaa86 Add 3.3.9 entry
• ce59f2e parser: fix a bug that &#0x...; is accepted as a character reference
• a09646d test: fix indent
• cf0fb9c Fix IOSource#readline for @pending_buffer (#215)
• 1d0c362 Optimize IOSource#read_until method (#210)
• 622011f Bump version
• 036d508 test: avoid using needless non ASCII characters
• 4197054 Add 3.3.8 entry
• 78f8712 Fix handling with "xml:" prefixed namespace (#208)
• 2e1cd64 Optimize SAX2Parser#get_namespace (#207)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	095735b
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/67249ac84c409e000829e884
😎 Deploy Preview	https://deploy-preview-2019--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit 9f02679)

Action: tests (ubuntu, stable)

Failed stage: Run tests [❌]

Failed test name: Mouse move by offset offset from viewport

Failure summary: The action failed because the test Mouse move by offset offset from viewport did not pass. The specific failure was due to an expectation mismatch: The test expected the x_coord to be within 1 of 8, but the actual value was 630. This failure occurred in the file ./spec/actions_api/mouse_spec.rb at line 119. The test was retried multiple times, but it failed consistently.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 282: timeout_minutes: 20 283: max_attempts: 3 284: command: cd examples/ruby 285: bundle exec rspec 286: 287: retry_wait_seconds: 10 288: polling_interval_seconds: 1 289: warning_on_retry: true 290: continue_on_error: false ... 457: �[0KDownloading selenium-server-4.25.0.jar: 97% (37224066 / 38290466) 458: �[0KDownloading selenium-server-4.25.0.jar: 97% (37469826 / 38290466) 459: �[0KDownloading selenium-server-4.25.0.jar: 98% (37715586 / 38290466) 460: �[0KDownloading selenium-server-4.25.0.jar: 99% (37961346 / 38290466) 461: �[0KDownloading selenium-server-4.25.0.jar: 99% (38207106 / 38290466).......*******..........**************............................. 462: Pending: (Failures listed here are expected and do not affect your suite's status) 463: 1) Keys copy and paste 464: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 465: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 593: 43) Element Locators with relative locators finds near element 594: # These are reference following the documentation example 595: # ./spec/elements/locators_spec.rb:55 596: 44) Element Locators with relative locators chains relative locators 597: # These are reference following the documentation example 598: # ./spec/elements/locators_spec.rb:59 599: Failures: 600: 1) Mouse move by offset offset from viewport 601: Failure/Error: expect(x_coord).to be_within(1).of(8) 602: expected 630 to be within 1 of 8 603: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 604: Finished in 4 minutes 16.9 seconds (files took 16.39 seconds to load) 605: 185 examples, 1 failure, 44 pending 606: Failed examples: 607: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 608: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 1 609: ......*..........F.........2024-10-30 02:00:21 INFO Selenium [:logger_info] Details on how to use and modify Selenium logger: 610: https://selenium.dev/documentation/webdriver/troubleshooting/logging 611: 2024-10-30 02:00:21 WARN Selenium [:devtools] Could not load selenium-devtools v130. Trying older versions. 612: 2024-10-30 02:00:21 WARN Selenium [:devtools] Using selenium-devtools version v129, some features may not work as expected. 613: .....................................................***...*****************.....*........*.......*******..........**************............................. 614: Pending: (Failures listed here are expected and do not affect your suite's status) 615: 1) Keys copy and paste 616: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 617: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 745: 43) Element Locators with relative locators finds near element 746: # These are reference following the documentation example 747: # ./spec/elements/locators_spec.rb:55 748: 44) Element Locators with relative locators chains relative locators 749: # These are reference following the documentation example 750: # ./spec/elements/locators_spec.rb:59 751: Failures: 752: 1) Mouse move by offset offset from viewport 753: Failure/Error: expect(x_coord).to be_within(1).of(8) 754: expected 630 to be within 1 of 8 755: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 756: Finished in 3 minutes 25.4 seconds (files took 1.33 seconds to load) 757: 185 examples, 1 failure, 44 pending 758: Failed examples: 759: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 760: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 1 761: ......*..........F.........2024-10-30 02:03:58 INFO Selenium [:logger_info] Details on how to use and modify Selenium logger: 762: https://selenium.dev/documentation/webdriver/troubleshooting/logging 763: 2024-10-30 02:03:58 WARN Selenium [:devtools] Could not load selenium-devtools v130. Trying older versions. 764: 2024-10-30 02:03:58 WARN Selenium [:devtools] Using selenium-devtools version v129, some features may not work as expected. 765: .....................................................***...*****************.....*........*.......*******..........**************............................. 766: Pending: (Failures listed here are expected and do not affect your suite's status) 767: 1) Keys copy and paste 768: # Test guarded; Guarded by {:browser=>:chrome, :reason=>"https://bugs.chromium.org/p/chromedriver/issues/detail?id=4264"}; 769: Failure/Error: expect(driver.find_element(id: 'textInput').attribute('value')).to eq 'SeleniumSelenium!' ... 897: 43) Element Locators with relative locators finds near element 898: # These are reference following the documentation example 899: # ./spec/elements/locators_spec.rb:55 900: 44) Element Locators with relative locators chains relative locators 901: # These are reference following the documentation example 902: # ./spec/elements/locators_spec.rb:59 903: Failures: 904: 1) Mouse move by offset offset from viewport 905: Failure/Error: expect(x_coord).to be_within(1).of(8) 906: expected 630 to be within 1 of 8 907: # ./spec/actions_api/mouse_spec.rb:119:in `block (3 levels) in <top (required)>' 908: Finished in 3 minutes 25.7 seconds (files took 1.34 seconds to load) 909: 185 examples, 1 failure, 44 pending 910: Failed examples: 911: rspec ./spec/actions_api/mouse_spec.rb:111 # Mouse move by offset offset from viewport 912: ##[error]Final attempt failed. Child_process exited with error code 1

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[A1exKH]

LGTM.
Those test are failed in other PRs too (#2020).