AutoSubscribe fails quietly when event name is too long

[mikeminutillo]

Describe the bug

When event name is too long, autosubscription fails silently.

To Reproduce

Create an event with a long name. Subscribe to it. Start both endpoints (publisher and subscriber) and publish the event. Verify that the subscription has not been created but the subscriber endpoint starts successfully.

Expected behavior

The subscriber endpoint should fail to start if it is unable to create a subscription.

Versions:

• NuGet package: Unknown
• OS: Unknown
• .NET Version Unknown

Additional context
Originally raised in a support case (43171).

Events were not being delivered to a particular subscriber. There were no errors reported. When the customer tried to manually subscribe to the message they discovered that the event name was too long. Implementing a name shortening rule allowed the event to be successfully delivered.

[SeanFeldman]

There is an exception thrown when running ASB Send/Reply sample with Message1 converted to an IEvent and renamed to ThisIsAVeryLongNamedEventThatWillEventuallyCauseAzureServiceBusToBlowUp.

The message is logged, but Core swallows the exception and endpoint continues. See https://github.com/Particular/KeepTheLightsOn/issues/241 for details.

[mikeminutillo]

The transport is correctly throwing an exception and the AutoSubscribe feature in NServiceBus is logging it and swallowing it. I'm connecting with the team internally to try and figure out why it does that and if it's something we can change.

[SeanFeldman]

For NServiceBus issue, see Particular/NServiceBus#5195