2020-02-12 00:08:19 +01:00
|
|
|
#pragma once
|
2021-01-14 19:37:14 +01:00
|
|
|
#include "oxenmq/oxenmq.h"
|
2020-02-12 00:08:19 +01:00
|
|
|
#include <catch2/catch.hpp>
|
2021-06-23 15:55:47 +02:00
|
|
|
#include <chrono>
|
2020-02-12 00:08:19 +01:00
|
|
|
|
2021-01-14 19:37:14 +01:00
|
|
|
using namespace oxenmq;
|
2020-02-12 00:08:19 +01:00
|
|
|
|
2021-08-05 00:41:16 +02:00
|
|
|
// Apple's mutexes, thread scheduling, and IO handling are garbage and it shows up with lots of
|
|
|
|
// spurious failures in this test suite (because it expects a system to not suck that badly), so we
|
|
|
|
// multiply the time-sensitive bits by this factor as a hack to make the test suite work.
|
|
|
|
constexpr int TIME_DILATION =
|
|
|
|
#ifdef __APPLE__
|
|
|
|
5;
|
|
|
|
#else
|
|
|
|
1;
|
|
|
|
#endif
|
|
|
|
|
2020-02-12 00:08:19 +01:00
|
|
|
static auto startup = std::chrono::steady_clock::now();
|
|
|
|
|
2020-10-15 21:13:37 +02:00
|
|
|
/// Returns a localhost connection string to listen on. It can be considered random, though in
|
2021-10-14 16:03:55 +02:00
|
|
|
/// practice in the current implementation is sequential starting at 25432.
|
2020-10-15 21:13:37 +02:00
|
|
|
inline std::string random_localhost() {
|
2021-10-14 16:03:55 +02:00
|
|
|
static std::atomic<uint16_t> last = 25432;
|
2020-10-15 21:13:37 +02:00
|
|
|
last++;
|
|
|
|
assert(last); // We should never call this enough to overflow
|
|
|
|
return "tcp://127.0.0.1:" + std::to_string(last);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2021-06-23 15:55:47 +02:00
|
|
|
// Catch2 macros aren't thread safe, so guard with a mutex
|
|
|
|
inline std::unique_lock<std::mutex> catch_lock() {
|
|
|
|
static std::mutex mutex;
|
|
|
|
return std::unique_lock<std::mutex>{mutex};
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Waits up to 200ms for something to happen.
|
1.1.0: invocation-time SN auth; failure responses
This replaces the recognition of SN status to be checked per-command
invocation rather than on connection. As this breaks the API quite
substantially, though doesn't really affect the functionality, it seems
suitable to bump the minor version.
This requires a fundamental shift in how the calling application tells
LokiMQ about service nodes: rather than using a callback invoked on
connection, the application now has to call set_active_sns() (or the
more efficient update_active_sns(), if changes are readily available) to
update the list whenever it changes. LokiMQ then keeps this list
internally and uses it when determining whether to invoke.
This release also brings better request responses on errors: when a
request fails, the data argument will now be set to the failure reason,
one of:
- TIMEOUT
- UNKNOWNCOMMAND
- NOT_A_SERVICE_NODE (the remote isn't running in SN mode)
- FORBIDDEN (auth level denies the request)
- FORBIDDEN_SN (SN required and the remote doesn't see us as a SN)
Some of these (UNKNOWNCOMMAND, NOT_A_SERVICE_NODE, FORBIDDEN) were
already sent by remotes, but there was no connection to a request and so
they would log a warning, but the request would have to time out.
These errors (minus TIMEOUT, plus NO_REPLY_TAG signalling that a command
is a request but didn't include a reply tag) are also sent in response
to regular commands, but they simply result in a log warning showing the
error type and the command that caused the failure when received.
2020-04-13 00:57:19 +02:00
|
|
|
template <typename Func>
|
|
|
|
inline void wait_for(Func f) {
|
2021-06-23 15:55:47 +02:00
|
|
|
auto start = std::chrono::steady_clock::now();
|
|
|
|
for (int i = 0; i < 20; i++) {
|
1.1.0: invocation-time SN auth; failure responses
This replaces the recognition of SN status to be checked per-command
invocation rather than on connection. As this breaks the API quite
substantially, though doesn't really affect the functionality, it seems
suitable to bump the minor version.
This requires a fundamental shift in how the calling application tells
LokiMQ about service nodes: rather than using a callback invoked on
connection, the application now has to call set_active_sns() (or the
more efficient update_active_sns(), if changes are readily available) to
update the list whenever it changes. LokiMQ then keeps this list
internally and uses it when determining whether to invoke.
This release also brings better request responses on errors: when a
request fails, the data argument will now be set to the failure reason,
one of:
- TIMEOUT
- UNKNOWNCOMMAND
- NOT_A_SERVICE_NODE (the remote isn't running in SN mode)
- FORBIDDEN (auth level denies the request)
- FORBIDDEN_SN (SN required and the remote doesn't see us as a SN)
Some of these (UNKNOWNCOMMAND, NOT_A_SERVICE_NODE, FORBIDDEN) were
already sent by remotes, but there was no connection to a request and so
they would log a warning, but the request would have to time out.
These errors (minus TIMEOUT, plus NO_REPLY_TAG signalling that a command
is a request but didn't include a reply tag) are also sent in response
to regular commands, but they simply result in a log warning showing the
error type and the command that caused the failure when received.
2020-04-13 00:57:19 +02:00
|
|
|
if (f())
|
|
|
|
break;
|
2021-08-05 00:41:16 +02:00
|
|
|
std::this_thread::sleep_for(10ms * TIME_DILATION);
|
1.1.0: invocation-time SN auth; failure responses
This replaces the recognition of SN status to be checked per-command
invocation rather than on connection. As this breaks the API quite
substantially, though doesn't really affect the functionality, it seems
suitable to bump the minor version.
This requires a fundamental shift in how the calling application tells
LokiMQ about service nodes: rather than using a callback invoked on
connection, the application now has to call set_active_sns() (or the
more efficient update_active_sns(), if changes are readily available) to
update the list whenever it changes. LokiMQ then keeps this list
internally and uses it when determining whether to invoke.
This release also brings better request responses on errors: when a
request fails, the data argument will now be set to the failure reason,
one of:
- TIMEOUT
- UNKNOWNCOMMAND
- NOT_A_SERVICE_NODE (the remote isn't running in SN mode)
- FORBIDDEN (auth level denies the request)
- FORBIDDEN_SN (SN required and the remote doesn't see us as a SN)
Some of these (UNKNOWNCOMMAND, NOT_A_SERVICE_NODE, FORBIDDEN) were
already sent by remotes, but there was no connection to a request and so
they would log a warning, but the request would have to time out.
These errors (minus TIMEOUT, plus NO_REPLY_TAG signalling that a command
is a request but didn't include a reply tag) are also sent in response
to regular commands, but they simply result in a log warning showing the
error type and the command that caused the failure when received.
2020-04-13 00:57:19 +02:00
|
|
|
}
|
2021-06-23 15:55:47 +02:00
|
|
|
auto lock = catch_lock();
|
|
|
|
UNSCOPED_INFO("done waiting after " << (std::chrono::steady_clock::now() - start).count() << "ns");
|
1.1.0: invocation-time SN auth; failure responses
This replaces the recognition of SN status to be checked per-command
invocation rather than on connection. As this breaks the API quite
substantially, though doesn't really affect the functionality, it seems
suitable to bump the minor version.
This requires a fundamental shift in how the calling application tells
LokiMQ about service nodes: rather than using a callback invoked on
connection, the application now has to call set_active_sns() (or the
more efficient update_active_sns(), if changes are readily available) to
update the list whenever it changes. LokiMQ then keeps this list
internally and uses it when determining whether to invoke.
This release also brings better request responses on errors: when a
request fails, the data argument will now be set to the failure reason,
one of:
- TIMEOUT
- UNKNOWNCOMMAND
- NOT_A_SERVICE_NODE (the remote isn't running in SN mode)
- FORBIDDEN (auth level denies the request)
- FORBIDDEN_SN (SN required and the remote doesn't see us as a SN)
Some of these (UNKNOWNCOMMAND, NOT_A_SERVICE_NODE, FORBIDDEN) were
already sent by remotes, but there was no connection to a request and so
they would log a warning, but the request would have to time out.
These errors (minus TIMEOUT, plus NO_REPLY_TAG signalling that a command
is a request but didn't include a reply tag) are also sent in response
to regular commands, but they simply result in a log warning showing the
error type and the command that caused the failure when received.
2020-04-13 00:57:19 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/// Waits on an atomic bool for up to 100ms for an initial connection, which is more than enough
|
|
|
|
/// time for an initial connection + request.
|
|
|
|
inline void wait_for_conn(std::atomic<bool> &c) {
|
|
|
|
wait_for([&c] { return c.load(); });
|
|
|
|
}
|
|
|
|
|
|
|
|
/// Waits enough time for us to receive a reply from a localhost remote.
|
2021-08-05 00:41:16 +02:00
|
|
|
inline void reply_sleep() { std::this_thread::sleep_for(10ms * TIME_DILATION); }
|
1.1.0: invocation-time SN auth; failure responses
This replaces the recognition of SN status to be checked per-command
invocation rather than on connection. As this breaks the API quite
substantially, though doesn't really affect the functionality, it seems
suitable to bump the minor version.
This requires a fundamental shift in how the calling application tells
LokiMQ about service nodes: rather than using a callback invoked on
connection, the application now has to call set_active_sns() (or the
more efficient update_active_sns(), if changes are readily available) to
update the list whenever it changes. LokiMQ then keeps this list
internally and uses it when determining whether to invoke.
This release also brings better request responses on errors: when a
request fails, the data argument will now be set to the failure reason,
one of:
- TIMEOUT
- UNKNOWNCOMMAND
- NOT_A_SERVICE_NODE (the remote isn't running in SN mode)
- FORBIDDEN (auth level denies the request)
- FORBIDDEN_SN (SN required and the remote doesn't see us as a SN)
Some of these (UNKNOWNCOMMAND, NOT_A_SERVICE_NODE, FORBIDDEN) were
already sent by remotes, but there was no connection to a request and so
they would log a warning, but the request would have to time out.
These errors (minus TIMEOUT, plus NO_REPLY_TAG signalling that a command
is a request but didn't include a reply tag) are also sent in response
to regular commands, but they simply result in a log warning showing the
error type and the command that caused the failure when received.
2020-04-13 00:57:19 +02:00
|
|
|
|
2021-01-14 19:37:14 +01:00
|
|
|
inline OxenMQ::Logger get_logger(std::string prefix = "") {
|
2020-02-12 00:08:19 +01:00
|
|
|
std::string me = "tests/common.h";
|
|
|
|
std::string strip = __FILE__;
|
|
|
|
if (strip.substr(strip.size() - me.size()) == me)
|
|
|
|
strip.resize(strip.size() - me.size());
|
|
|
|
else
|
|
|
|
strip.clear();
|
|
|
|
|
|
|
|
return [prefix,strip](LogLevel lvl, std::string file, int line, std::string msg) {
|
|
|
|
if (!strip.empty() && file.substr(0, strip.size()) == strip)
|
|
|
|
file = file.substr(strip.size());
|
|
|
|
|
|
|
|
auto lock = catch_lock();
|
|
|
|
UNSCOPED_INFO(prefix << "[" << file << ":" << line << "/"
|
|
|
|
"+" << std::chrono::duration<double>(std::chrono::steady_clock::now() - startup).count() << "s]: "
|
|
|
|
<< lvl << ": " << msg);
|
|
|
|
};
|
|
|
|
}
|