gocbcore.Agent with WaitUntilReady(..) continuously logs in case source doesn't exist

When I try to set up a gocbcore.Agent and use a WaitUntilReady(..) with 10s against a source that doesn't exist, the WaitUntilReady(..) responds back in 10s with the timeout as expected. 

However, gocbcore seems to continuously be attempting to connect behind the scenes even after WaitUntilReady(..) has responded to the caller.

I see several logs coming in from GOCBCORE indicating this ..

2020-06-01T13:36:13.758-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615

2020-06-01T13:36:23.763-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615

2020-06-01T13:36:33.772-07:00 [WARN] (GOCBCORE) Config block decode failure (invalid character 'R' looking for beginning of value) -- cbgt.GocbcoreLogger.Log() at gocbcore_helper.go:615

...

Note that the message `invalid character 'R" looking for beginning of value)` is a json marshaling error of the response returned from ns_server in the event that a source doesn't exist (non-json text) -> "Requested resource not found".