Resolves #372 Frameset already completed issues

This will still be an issue if latency in the network varies by more that 3 frames, something that can be resolved by disabling the receive buffer entirely.

components/streams/src/builder.cpp

@@ -5,6 +5,7 @@
 #include <loguru.hpp>
 
 #include <chrono>
+#include <bitset>
 
 using ftl::streams::BaseBuilder;
 using ftl::streams::ForeignBuilder;
@@ -386,7 +387,7 @@ std::shared_ptr<ftl::data::FrameSet> ForeignBuilder::_getFrameset() {
 		f->set(ftl::data::FSFlag::STALE);
 		slk.unlock();
 
-		if (!f->isComplete()) LOG(WARNING) << "Dispatching incomplete frameset: " << f->timestamp();
+		if (!f->isComplete()) LOG(WARNING) << "Dispatching incomplete frameset: " << f->timestamp() << " (" << std::bitset<16>( f->mask ).to_string() << ")";
 
 		// Remove all previous framesets
 		while (framesets_.size() > 0) {