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

Release 5.14.0 #548

Merged
merged 67 commits into from
Nov 14, 2023
Merged

Release 5.14.0 #548

merged 67 commits into from
Nov 14, 2023

Conversation

mclift
Copy link
Member

@mclift mclift commented Nov 8, 2023

As suggested by @HenningNT, this PR is for release 5.14.0.

mclift and others added 30 commits December 30, 2022 18:26
Enable Source Link and Determnistic Builds; don't attempt to publish package from forks.
Enable Source Link & Deterministic Builds
…ync version. Fix bug where trigger information is missing from the StateMachine.GetInfo.
… only initialised by a call to AddRelationships.

However, for StateMachineInfo.InitialState, this never happens. Therefore StateMachineInfo.InitialState.Transitions
throws a System.ArgumentNullException. 
The StateInfo object should not throw if "half initialised"
…State.Transitions-throws

StateMachineInfo.InitialState.Transitions throws if AddRelationships not called
Fix spelling mistake "fireing" to "firing"
…-trigger-information

Trigger information is missing for OnEntryFromAsync
mclift and others added 14 commits June 2, 2023 16:19
…-async-if

fix: InternalTransitionAsyncIf guard parameters
Implemented an example for an alarm
Remove obsolete TargetFrameworks
…erationException

Bugfix: execute OnEntryFromAsync actions from FireAsync
…tion-async-if

fix: InternalTransitionAsyncIf guard parameters (update)
This is async counterpart to existing Fire(TriggerWithParameters, params object[]) method. Required for firing triggers with more than 3 parameters asynchronously.
…a substate, if the machine is already in that substate then the entry action shouldn't trigger again
docs: Update README.md dead link for simplestatemachine
In the case of a superstate having a trigger that moves the state to …
@mclift mclift requested review from crozone and HenningNT November 8, 2023 16:48
@crozone
Copy link
Collaborator

crozone commented Nov 13, 2023

Test failure, going to take a look:

Stateless.Tests.SynchronizationContextFixture.Multiple_OnEntry_on_Reentry_should_retain_SyncContext [FAIL]
Failed Stateless.Tests.SynchronizationContextFixture.Multiple_OnEntry_on_Reentry_should_retain_SyncContext [47 ms]
Error Message:
Assert.NotEqual() Failure
Expected: Not MaxConcurrencySyncContext { }
Actual: MaxConcurrencySyncContext { }

@mclift
Copy link
Member Author

mclift commented Nov 13, 2023

Copy link
Contributor

@HenningNT HenningNT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve, but didn't check anything :-D

@HenningNT
Copy link
Contributor

Might I suggest releasing as soon as possible after a useful change has been merged?

@crozone
Copy link
Collaborator

crozone commented Nov 14, 2023

@mclift It looks like the issue is in the testing harness itself that tries to lose the sync context. There was an attempt to fix this here:

https://github.com/dotnet-state-machine/stateless/pull/528/files

But it looks like there still may be an issue with this strategy.

So Stateless isn't responsible for the failing test but the actual testing code. I think it's safe to proceed.

@mclift
Copy link
Member Author

mclift commented Nov 14, 2023

Thanks for checking that out, @crozone!

@mclift mclift merged commit 4a4ac06 into master Nov 14, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants