v1.4.10 Stable Release #4547
Merged
v1.4.10 Stable Release #4547
Conversation
This file contains 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
…on (#4523) * Add live and current variant to AllEvents query * Update documentation * Move the batching tests to its appropriate namespace/folder * Fix copy-paste error
Bumps [Google.Protobuf](https://github.com/protocolbuffers/protobuf) from 3.12.3 to 3.12.4. - [Release notes](https://github.com/protocolbuffers/protobuf/releases) - [Changelog](https://github.com/protocolbuffers/protobuf/blob/master/generate_changelog.py) - [Commits](protocolbuffers/protobuf@v3.12.3...v3.12.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
…ng RemotingTerminator startup (#4532)
* Enhance OpenCircuitException to include what caused the circuit breaker to open * Add unit test * Update API approver list * Move LastCaughtException from `IAtomicState` to the abstract `AtomicState` class * Move LastCaughtException to CircuitBreaker. Make sure CircuitBreaker wwith null cause stays stored as null. * Revert `CircuitBreaker.Fail()` function signature for binary compatibility. * Update API approver list Co-authored-by: Aaron Stannard <aaron@petabridge.com>
`You should use clustering in any scenario where you have....Non-Trivial to perform.` didn't make sense to me. I'm actually taking a guess as to what this condition is, but I propose that you're saying that we should use clustering when there is a non-trivial task to perform (because you want complex tasks to be fault-tolerant?).
* Bump LightningDB from 0.12.0 to 0.13.0 Bumps [LightningDB](https://github.com/CoreyKaylor/Lightning.NET) from 0.12.0 to 0.13.0. - [Release notes](https://github.com/CoreyKaylor/Lightning.NET/releases) - [Commits](CoreyKaylor/Lightning.NET@v0.12.0...v0.13.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> * Adapt to changes in LightningDB API changes Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> Co-authored-by: Gregorius Soedharmo <arkatufus@yahoo.com>
…en customizable for plugins. (#4544)
Currently the router documentation is missing information about management messages. These message are supported according to the Routing test spec. This change adds information about these messages
…ation behavior (#4531) * Rebase to new dev * Re-implement PersistenceIds Query * Fix copy-paste error * Make sure APIs are as backward compatible as possible, update API approver list. * Add unit test for publisher (cache) deallocation. * Move onTerminate callback from AllPersistenceIdsPublisher to FanoutProcessorImpl * Update API approver list * Remove redundant `as` cast * Remove reference to Akka.Persistence.Query.Sql from Akka.Persistence.TCK * Add concurrency locking on the internal persistence ids publisher. * Make PersistenceIds to query both Journal and Metadata table. Add test for snapshot and journal case. * Change IStreamBuffer access to internal. * Update API approver list * Go back to using ordeting column to filter the journal table for performance reasons * Change synchronization to a simpler lock * Change test to reflect changes in synchonization * Update persistence ids SQL in BatchingSqlJournal * Change how SubscribeManager checks for available data. * Change confusing `Count()` to `AvailableData` property * Update API approver list * Make sure that tests are never run in parallel * Prune excessive test * Append a GUID on the db filename to make doubly sure that db never get used twice Co-authored-by: Aaron Stannard <aaron@petabridge.com>
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.
1.4.10 August 20th 2020
Maintenance Release for Akka.NET 1.4
Akka.NET v1.4.10 includes some minor bug fixes and some major feature additions to Akka.Persistence.Query:
To see the full set of fixes in Akka.NET v1.4.10, please see the milestone on Github.