-
Notifications
You must be signed in to change notification settings - Fork 2
release 0.4.0 #80
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
release 0.4.0 #80
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,6 +6,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). | |
|
|
||
| ## [Unreleased] | ||
|
|
||
| ## [0.4.0] - 2026-05-18 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please ensure the package version is updated in the project metadata (e.g., |
||
|
|
||
| ### Added | ||
|
|
||
| - **`WorkflowEngine.workflow_scope(workflow_id=None)`** — new async context | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release 0.4.0 contains a critical bug in the data dependency resolution logic. In
src/radical/asyncflow/workflow_manager.pyat line 1140, the code attempts to accessitem["target"], whereitemis the result ofself.backend.link_explicit_data_deps. However, insrc/radical/asyncflow/backends.py,LocalExecutionBackend.link_explicit_data_depsreturnsNone(line 410), which will cause aTypeErrorwhenever explicit data dependencies are used with the local backend. Additionally,LocalExecutionBackend.shutdown(line 404) performs a blocking call toexecutor.shutdown(wait=True)within an async context, which will block the event loop.