-
Notifications
You must be signed in to change notification settings - Fork 25
Comparing changes
Open a pull request
base repository: ruby/timeout
base: v0.4.1
head repository: ruby/timeout
compare: v0.4.2
- 15 commits
- 9 files changed
- 8 contributors
Commits on Nov 7, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 3acb0ed - Browse repository at this point
Copy the full SHA 3acb0edView commit details -
Co-authored-by: Benoit Daloze <eregontp@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 56fde15 - Browse repository at this point
Copy the full SHA 56fde15View commit details
Commits on Nov 8, 2023
-
Merge pull request #43 from jjb/patch-1
fixed check for error bubble up test
Configuration menu - View commit details
-
Copy full SHA for d1d2263 - Browse repository at this point
Copy the full SHA d1d2263View commit details
Commits on Dec 18, 2023
-
Configuration menu - View commit details
-
Copy full SHA for b41f33d - Browse repository at this point
Copy the full SHA b41f33dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 301ad4c - Browse repository at this point
Copy the full SHA 301ad4cView commit details
Commits on Dec 20, 2023
-
Provide a 'Changelog' link on rubygems.org/gems/timeout
By providing a 'changelog_uri' in the metadata of the gemspec a 'Changelog' link will be shown on https://rubygems.org/gems/timeout which makes it quick and easy for someone to check on the changes introduced with a new version. Details of this functionality can be found on https://guides.rubygems.org/specification-reference/
Configuration menu - View commit details
-
Copy full SHA for 47a6f03 - Browse repository at this point
Copy the full SHA 47a6f03View commit details -
Merge pull request #46 from mark-young-atg/provide_changelog_link_on_…
…rubygems Provide a 'Changelog' link on rubygems.org/gems/timeout
Configuration menu - View commit details
-
Copy full SHA for a7e91a5 - Browse repository at this point
Copy the full SHA a7e91a5View commit details
Commits on May 30, 2024
-
Make test_nested_timeouts less flaky
This test randomly fails due to the bug reported in [Bug #20314], where the two timeouts are too close so that they can expire at the same time. As a workaround, this change increases the time difference between timeouts. This will reduce the probability of simultaneous expirations and lower flakiness.
Configuration menu - View commit details
-
Copy full SHA for cb5ee35 - Browse repository at this point
Copy the full SHA cb5ee35View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6c99460 - Browse repository at this point
Copy the full SHA 6c99460View commit details
Commits on Aug 27, 2024
-
Global #timeout was remove 5 years ago
* Also update Timeout::timeout to the more common format of Timeout.timeout
Configuration menu - View commit details
-
Copy full SHA for 213f4e2 - Browse repository at this point
Copy the full SHA 213f4e2View commit details
Commits on Aug 28, 2024
-
Merge pull request #49 from jpcamara/fix-documentation-for-timeout-me…
…thod Global #timeout was removed 5 years ago
Configuration menu - View commit details
-
Copy full SHA for 6b445fc - Browse repository at this point
Copy the full SHA 6b445fcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 683fdb4 - Browse repository at this point
Copy the full SHA 683fdb4View commit details
Commits on Sep 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1f0a0fb - Browse repository at this point
Copy the full SHA 1f0a0fbView commit details
Commits on Nov 6, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 87edf95 - Browse repository at this point
Copy the full SHA 87edf95View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2f52522 - Browse repository at this point
Copy the full SHA 2f52522View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.4.1...v0.4.2