-
Notifications
You must be signed in to change notification settings - Fork 0
release/0.4.1-alpha #272
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
Merged
release/0.4.1-alpha #272
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n read a component
…ng Boolean toggle
…change bugs with Boolean toggle (#268) ## Description This PR addresses several critical issues in `StatefulAsyncComponentBase`: - **Stuck Components with Boolean Toggle (#260):** Fixes a bug where components using a Boolean toggle for the Run parameter would not retrigger processing when other inputs changed while Run remained true. The logic now ensures that input changes with persistent `Run=true` correctly transition the component to the Processing state, matching expected toggle behavior. - **Metrics Not Output:** Resolves a problem where output metrics were cleared prematurely in toggle scenarios, resulting in missing metrics output. The fix ensures metrics are only cleared when starting a truly new processing run, not on every state transition. - **Prevent False Positives on Input Change Calculation:** Fixes an issue where the component would incorrectly detect input changes due to object instance comparisons rather than value comparisons. Now, changed inputs are calculated based on actual values, preventing unnecessary recomputation. - **Prevent Unnecessary Transitions to NeedsRun (#113):** Fixes a bug where components would transition to the "NeedsRun" state unnecessarily when reading a component with existing results. Now, components correctly transition to the "Done" state in these scenarios. These changes improve reliability, correctness, and user experience when using toggles and input changes for component execution. ## Breaking Changes None. ## Testing Done - Verified both button and Boolean toggle Run inputs trigger correct processing and metrics output. - Regression tested with various input change scenarios. - Confirmed components transition to correct states when reading files with existing results. ## Checklist - [x] This PR is focused on a single feature or bug fix - [x] Version in Solution.props was updated, if necessary, and follows semantic versioning - [x] CHANGELOG.md has been updated - [x] PR title follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.1.0/) format - [x] PR description follows [Pull Request Description Template]([https://github.com/architect](https://github.com/architect)
This PR updates the version badge in the README.md to match the current version in Solution.props. This is an automated PR created by the Update Version Badge workflow.
## Description Fixes #208. ## Breaking Changes None ## Testing Done gh_toggle_preview call on chat. ## Checklist - [x] This PR is focused on a single feature or bug fix - [x] Version in Solution.props was updated, if necessary, and follows semantic versioning - [x] CHANGELOG.md has been updated - [x] PR title follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format - [x] PR description follows [Pull Request Description Template](#pull-request-description-template)
… fixes (#271) This PR prepares the release for version 0.4.1-alpha with version update and code style fixes: - Updated version in Solution.props - Updated changelog with closed-solved issues - Updated README badges
marc-romu
approved these changes
Jul 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prepares the release for version 0.4.1-alpha with version update and code style fixes: