novox/mesh-controller
13
0
Fork 0
Code Issues Pull Requests 3 Releases Wiki Activity

The connections request asks for user names, which the server leaves out otherwise (issue 1147)

Browse Source
This commit is contained in:
jschoubben
2026-10-18 19:27:12 +02:00
parent eba864dc5f
commit 0520773412
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
internal/broker/system_exports_live_test.go
+4 -2
View File
@@ -116,8 +116,10 @@ func TestNatsTheSystemAccountsExportsReachMeshOnAReload(t *testing.T) { // 1147/
} }
} }
hears(connects, "connect") hears(connects, "connect")
// The answer to the connections request lists the open connections, the shop's among them. // The answer to the connections request lists the open connections, the shop's among them. The server names the
reply, err := watchman.Request(BusConnzSubject, []byte(`{}`), 5*time.Second) // account from the subject the export clamps (MESH), but leaves the user's name out unless the request asks for it
// with "auth": true (monitor.go ConnzOptions.Username), so the watchman asks so.
reply, err := watchman.Request(BusConnzSubject, []byte(`{"auth":true}`), 5*time.Second)
if err != nil { if err != nil {
t.Fatalf("mesh.bus.connz is not answered: %v", err) t.Fatalf("mesh.bus.connz is not answered: %v", err)
} }