billt-hlit
commented
6 years ago I can't get attachments to work, so I'm going to have to paste them into comments. This is the patch I used.
diff --git Development/nmos-cpp-node/main.cpp Development/nmos-cpp-node/main.cpp
index 33cf1f6..85a377c 100644
--- Development/nmos-cpp-node/main.cpp
+++ Development/nmos-cpp-node/main.cpp
@@ -155,6 +155,19 @@ int main(int argc, char* argv[])
slog::log<slog::severities::info>(gate, SLOG_FLF) << "Ready for connections";
+ sleep(1);
+
+ const auto& seed_id = nmos::experimental::fields::seed_id(node_model.settings);
+ auto node_id = nmos::make_repeatable_id(seed_id, U("/x-nmos/node/self"));
+ web::json::value clock;
+ clock["name"] = web::json::value{"clk0"};
+ clock["ref_type"] = web::json::value{"internal"};
+ nmos::modify_resource(node_model.resources, node_id, [&] (nmos::resource &node)
+ {
+ push_back(node.data["clocks"], clock);
+ });
+ node_condition.notify_all();
+
// Wait for a process termination signal
nmos::details::wait_term_signal();```
garethsb
I started using node-cpp-registry instead of the BBC's registry and am running into problems with node reregistrations not working. In short, I get a "409 Conflict" error when I try to update the node's registration.
I'll attach detailed logs of some sample changes I made to the node's main.cpp to demonstrate the problem and the output of both the node and the registry. I didn't have this problem when working against the BBC registry in Wuppertal last month.
Any suggestions? I'm not able to use the BBC registry here because I can't run it on the machine that the node is running on, and can't get the registry to be exposed to the LAN.