Jetstream publish without stream stalls on core listener

[plank-p]

Observed behavior

Clients stall forever when attempting to do a jetstream publish to a non existent stream with a core listener.

Expected behavior

A stream does not exist error, or a successful publish

Server and client version

Server Version: 2.12.2

Host environment

No response

Steps to reproduce

package main

import (
	"fmt"
	"log"
	"time"

	"github.com/nats-io/nats.go"
	"github.com/nats-io/nats.go/jetstream"
)
func main() {
	nc, err := nats.Connect(nats.DefaultURL)
	if err != nil {
		log.Fatal(err)
	}
	defer nc.Close()
	js, err := jetstream.New(nc)
	if err != nil {
		log.Fatal(err)
	}
	nc.Subscribe("test2.hello", func(m *nats.Msg) {})

	fmt.Println("About to publish")
	fut, err := js.PublishAsync( "test2.hello", []byte("world"))
	if err != nil {
		log.Fatal("publish (matching subject):", err)
	}
	fmt.Println("publish (matching subject) sent")
	select {
	case <-fut.Ok():
		fmt.Println("publish (matching subject) succeeded")
	case err:=<-fut.Err():
		fmt.Printf("publish (matching subject) failed: %v\n", err)
	case <-time.After(5 * time.Second):
		fmt.Println("publish (matching subject) timed out")
	}
}

Prints

About to publish
publish (matching subject) sent
publish (matching subject) timed out

[neilalexander]

This is intended behaviour. The JetStream publishes wait for an ack. If you subscribe on the ingest subject instead but don't return acks then you will time out waiting for acks.

[plank-p]

@neilalexander Perhaps my adding of the defect label was too hasty

As a user it would be cool if the jetstream publish had a way of distinguishing between:

1. we are waiting on a reply from the expected jetstream/system consumer
2. there are no system jetstream consumers, only random user consumers, so we will never get an ack

And/or it would be nice if it were possible for jetstream publish to return "no stream exists", even in the face of a user listener.

I guess it comes down to is what is the meaning of jetstream publish?! I have understood it to mean that I am publishing to a stream, but perhaps that is an over inference on my part. The current meaning seems to be closer to "publish somewhere and wait for an ack"