OrMemphis

**Describe the bug** See title **To Reproduce** 1. Bring a memphis cluster/server up 2. Create a station 3. Send a message without a header using nats cli `nats pub stationName.final...

### Current behavior in standalone mode - the broker waits until it is possible to create a stream and then creates it and all logs from that point onwards are...

### Current behavior the broker is subscribing to "memphis" sdk requests, when a message arrives a handler is invoked in a new goroutine. Thus, a decent amount of these requests...

When using Stations with the Memory storage type and with a single replica, if we kill the broker and start it again the Station(stream) will perish. although the DB still...

Changes to the logging mechanism: 1. Waiting indefinitely for cluster to be ready, if not ready in 2 minutes - write Error to logs. 2. until the publish activation, logs...

### Describe the bug Downloaded logs do not include broker identifier per log. ### Steps to reproduce (In cluster mode oc) 1. Enter the logs page (have some logs written...

Testing framework

2

Currently we use only Go's testing, but we rely on running a docker container that runs Memphis in the background. we need to either mock Memphis or introduce a testing...