Weird Subscriptions problem...

[darkwatchuk]

OK, so this is weird.. or is it me?

If I use the Connection.NewInbox() to make a subject prefix, and run the following code I get no message even if I publish directly to the inbox wild card using nats cli or anything else.

However, if I swap the first two lines over, everything works fine..... ?!?!

Subscribing in the CLI for both subject wildcards also works fine......

     //string flowControlSubjectPrefix = $"_INBOX.flowcontrol.{Guid.NewGuid()}";

     string flowControlSubjectPrefix = _connection.NewInbox();

     Console.WriteLine($"flow control subject prefix : {flowControlSubjectPrefix}");

     _ = Task.Run(async () =>
     {
         string flowControlSubjectWildcard = $"{flowControlSubjectPrefix}.>";

         Console.WriteLine($"Started FlowControl Loop on {flowControlSubjectWildcard}");
         try
         {
             await foreach (var response in _connection.SubscribeAsync<byte[]>(flowControlSubjectWildcard, opts : new NatsSubOpts { StopOnEmptyMsg = false },  cancellationToken: cts.Token))
             {
                 Console.WriteLine($">>> Received response on {response.Subject}");
             }
         }
         catch (OperationCanceledException opCancelled)
         {

         }
         finally
         {
             Console.WriteLine("Finished Flow Control Loop");
         }                                
     });

[mtmk]

ah it's hitting the connection's inbox subscription 👀 ...

[darkwatchuk]

yup - just got there same time as you.... :-)

[darkwatchuk]

Don't worry, if there's a good reason for this that's fine. Just was a more convenient way to create a custom prefix. No rush, could do a PR on this at a later date.... just thought it was really strange I wasn't getting any responses!!!