You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Processing a control message causes the outbox to throw a null reference exception (#738) (#752)
* Reproduce the bug
* Cleanup
* Improve requesting partition key not to be mapped
* Fix bug
* Move test and align configs
* Flip around logic
* Move the test file
* Add tests and checks for missing table name
* Share table name check test and fix validation
* Make missing partition key test shared as well
* Move to extension method
* More succinct check
---------
Co-authored-by: danielmarbach <[email protected]>
# Conflicts:
# src/LogicalOutbox.StorageTable.AcceptanceTests/ConfigureAzureTablePersistence.cs
# src/NServiceBus.Persistence.AzureTable/Outbox/LogicalOutboxBehavior.cs
# src/NServiceBus.Persistence.AzureTable/Outbox/OutboxPersister.cs
# src/PhysicalOutbox.StorageTable.AcceptanceTests/ConfigureAzureTablePersistence.cs
Co-authored-by: Andreas Öhlund <[email protected]>
thrownewException($"For the outbox to work a table name must be configured. Either configure a default one using '{nameof(ConfigureAzureStorage.DefaultTable)}' or set one via a behavior calling `context.Extensions.Set(new {nameof(TableInformation)}(\"SomeTableName\"))`");
config.Pipeline.Register(newControlMessageBehavior(runDescriptor.ScenarioContextasContext),"Checks that the control message was processed successfully");
0 commit comments