Fork Sync: Update from parent repository #4
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
* Updated SQS queue access policy to be less permissive in granting access to appropriate SNS topic * Updated to set queue access policy statement condition to use the topic's ARN without a wild-card * Removed option of wild-carded topic ARN * Revert "Removed option of wild-carded topic ARN" This reverts commit 96324a8.
#4737) * Bugfix to make rabbitmq_delayed_message_exchange works with other exchange types * Including unit tests * Changing the tests to generate different names for each exchange type --------- Co-authored-by: paulohumberto <paulo@acerto.com.br>
…SagaDbContex Simplify using a protected constructor
…ck hint by default
… ActiveMQ ReplyTo destinations
…for SQS, no other transports do this validation though.
… in ASB client SDK but who knows.
…s value despite allowing it to be set (#4788) * Fixed failure status setting for healthcheck * Extended health check documentation: added information about options * Fixed getters and setters in health check options and also fixed docs about tags * Fixed getter again
* Add net8.0 TFM * Update to .NET 8 for unit tests * Fix unit tests * Disable CS9191 * Obsolete formatter-based serialization * Disabled more CS9191 * Remove out of support netcoreapp3.1 TFM from benchmark project
…nversion to a dictionary.
* remove promotion of Quartz's Newtonsoft based Quartz.Serialization.Json * remove unused Quartz.Plugins.TimeZoneConverter * fix XML doc comments * remove unnecessary compiler warnings suppression * remove usage of obsolete UseMicrosoftDependencyInjectionJobFactory
* SqlTransport -> Use configured schema when listening to notifications Hi @phatboyg I found an issue with the Listen (postgres) notifications part where the schema is hardcoded to be "transport" Since it is allowed to have a different schema that is passed via options and the PostgresDatabaseMigrator uses it for creating the trigger script, we should have it aligned in the C# code. * Sanitize schema name to fit postgres channel requirements * Surround schema name with double quotes to prevent dbMigrator failures
…h concurrent readers the way SQL can
…es should now work properly.
…ransport with job saga endpoints. Also added inline endpoint configuration ability.
…ed from the batch. Empty batches should be "ignored."
…th other frameworks.
…hen not found.
…nerable package.json packages.
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.
No description provided.