Skip to content
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

Bump async from 2.8.2 to 2.17.0 #39

Merged
merged 1 commit into from
Oct 6, 2024
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 1, 2024

Bumps async from 2.8.2 to 2.17.0.

Release notes

Sourced from async's releases.

v2.14.2

Full Changelog: socketry/async@v2.14.1...v2.14.2

v2.12.0

What's Changed

Full Changelog: socketry/async@v2.11.0...v2.12.0

v2.11.0

What's Changed

Full Changelog: socketry/async@v2.10.2...v2.11.0

v2.10.2

What's Changed

New Contributors

Full Changelog: socketry/async@v2.10.1...v2.10.2

v2.10.1

What's Changed

Full Changelog: socketry/async@v2.10.0...v2.10.1

v2.10.0

What's Changed

Full Changelog: socketry/async@v2.9.0...v2.10.0

v2.9.0

What's Changed

  • Introduce Scheduler#load and Async::Idler for load shedding and saturation. (socketry/async#309)

Full Changelog: socketry/async@v2.8.2...v2.9.0

Changelog

Sourced from async's changelog.

v2.17.0

  • Introduce Async::Queue#push and Async::Queue#pop for compatibility with ::Queue.

v2.16.0

Better Handling of Async and Sync in Nested Fibers

Interleaving bare fibers within Async and Sync blocks should not cause problems, but it presents a number of issues in the current implementation. Tracking the parent-child relationship between tasks, when they are interleaved with bare fibers, is difficult. The current implementation assumes that if there is no parent task, then it should create a new reactor. This is not always the case, as the parent task might not be visible due to nested Fibers. As a result, Async will create a new reactor, trying to stop the existing one, causing major internal consistency issues.

I encountered this issue when trying to use Async within a streaming response in Rails. The protocol-rack uses a normal fiber to wrap streaming responses, and if you try to use Async within it, it will create a new reactor, causing the server to lock up.

Ideally, Async and Sync helpers should work when any Fiber.scheduler is defined. Right now, it's unrealistic to expect Async::Task to work in any scheduler, but at the very least, the following should work:

reactor = Async::Reactor.new # internally calls Fiber.set_scheduler
This should run in the above reactor, rather than creating a new one.
Async do
puts "Hello World"
end

In order to do this, bare Async and Sync blocks should use Fiber.scheduler as a parent if possible.

See socketry/async#340 for more details.

Commits
  • 988ccec Bump minor version.
  • 7f105aa Add Queue#push and Queue#pop for compatibility with ::Queue.
  • 6ecace9 Modernize gem.
  • 10fa816 Bump patch version.
  • c13ad8a Add timeout to timeout error message.
  • fc3fe3b Bump minor version.
  • d410bc0 Update readme.md.
  • 9d77c1f Update titles.
  • b5494cc Better handling of bare Async and Sync blocks when a scheduler is defined...
  • fc6b5d7 Add releases.md.
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file ruby Ruby labels Oct 1, 2024
@torrocus torrocus removed the request for review from womanonrails October 2, 2024 07:09
Bumps [async](https://github.com/socketry/async) from 2.8.2 to 2.17.0.
- [Release notes](https://github.com/socketry/async/releases)
- [Changelog](https://github.com/socketry/async/blob/main/releases.md)
- [Commits](socketry/async@v2.8.2...v2.17.0)

---
updated-dependencies:
- dependency-name: async
  dependency-type: indirect
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot-bundler-async-2.17.0 branch from 74d3caf to 5436ff2 Compare October 2, 2024 07:09
@torrocus torrocus merged commit b1b976a into main Oct 6, 2024
2 checks passed
@torrocus torrocus deleted the dependabot-bundler-async-2.17.0 branch October 6, 2024 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file ruby Ruby
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants