Unable to get WorkQueuePolicy stream/subject pending messages

[vultj]

Hello! Just started using NATS with Python and Go. I am publishing messages from Go, and consuming them with Python. Once I changed the stream over to jetstream.WorkQueuePolicy I can no longer pull pending messages size with info.NumPending. I also cannot seem to pull messages from workqueue either with python. I tried with latest release and v1.33.1 and its same issue. So I think it's just user error :)

Go code to pull pending message count:

nc, err := nats.Connect(url)
if err != nil {
	return nil, err
}

js, err := jetstream.New(nc)
if err != nil {
	return nil, err
}

s, err := js.CreateOrUpdateStream(ctx, jetstream.StreamConfig{
	Name:      "msgs",
	Retention: jetstream.WorkQueuePolicy,
	Subjects:  []string{subj},
})
if err != nil {
	log.Error(err)

	return 0
}

// get consumer handle
c, err := s.CreateOrUpdateConsumer(ctx, jetstream.ConsumerConfig{
	Name:          "size-subj",
	FilterSubject: subj,
})
if err != nil {
	log.Error(err)

	return 0
}
defer func() {
	if err := s.DeleteConsumer(ctx, "size-subj"); err != nil {
		log.Error(err)
	}
}()

// get info from consumer
info, err := c.Info(ctx)
if err != nil {
	log.Error(err)

	return 0
}

return info.NumPending

The code always returns 0 but no error is logged. I have tried logging before return and its 0, always. This only started occurring when I switched over to work queue policy. So, I think I'm just consuming and checking pending messages incorrectly for this queue?

On the python side I cannot pull the messages either:

nc = await nats.connect(args.nats_url,
    error_cb=error_cb,
    reconnected_cb=reconnected_cb,
    disconnected_cb=disconnected_cb,
    closed_cb=closed_cb,
)

js = nc.jetstream()

sub = await js.pull_subscribe(args.nats_subject, durable=args.nats_subject, stream=args.nats_stream)

while True:
    msgs = await sub.fetch(1, 5)
    for msg in msgs:
        print("data: %s" % (msg.data))
        await msg.ack()

await nc.close()

I think that I am using the work queue incorrectly? But not sure.

There are messages in the stream/subjects from the go code that's pushing messages:

╭──────────────────────────────────────╮
│      1 Subjects in stream msgs     │
├──────────────────────────────┬───────┤
│ Subject                      │ Count │
├──────────────────────────────┼───────┤
│ msgs.test                   │ 28    │
╰──────────────────────────────┴───────╯