14 Commits (dev)

Author	SHA1	Message	Date
Jason Rhinelander	0fe7153f6e	Fix client latency bug; De-shared_ptr IHopHandler queues ... - Replace m_FlushWakeup with a call to the router's god mode pump method. m_FlushWakeup apparently isn't enough to get things out, and we can end up with incoming packets that don't get properly handled right away without it. - The shared_ptr around the ihophandler queues isn't needed and is just adding a layer of obfuscation; instead just exchange the list directly into the lambda. - Use std::exchange rather than swap - A couple other small code cleanups.	3 years ago
Jeff Becker	07eaeb681a	try fixing deadlock	3 years ago
Thomas Winget	7caa87862e	standardize include format and pragma once ... All #ifndef guards on headers have been removed, I think, in favor of #pragma once Headers are now included as `#include "filename"` if the included file resides in the same directory as the file including it, or any subdirectory therein. Otherwise they are included as `#include <project/top/dir/relative/path/filename>` The above does not include system/os headers.	3 years ago
Jeff Becker	f25e9bb01f	use std::list here too	4 years ago
Jeff Becker	00143e63f4	put replay filters on transit hops to reduce retransmissions.	4 years ago
Stephen Shelton	273270916e	The Great Wall of Blame ... This commit reflects changes to clang-format rules. Unfortunately, these rule changes create a massive change to the codebase, which causes an apparent rewrite of git history. Git blame's --ignore-rev flag can be used to ignore this commit when attempting to `git blame` some code.	4 years ago
Jeff Becker	1244ad83ad	fix include file use	4 years ago
Jeff Becker	73e07ef2d0	client side replay filter	4 years ago
Jeff Becker	5863e33825	move it arround	5 years ago
jeff	14c9ef15ed	try calling stuff in logic thread from event loop	5 years ago
Jeff Becker	4bf6882c8a	more async cryptography	5 years ago
Michael	16cdfbd5f0	clang-tidy modernize pass	5 years ago
Thomas Winget	38fd0552d3	Adds Link-Relay Status Messages ... Success case: - the path endpoint creates and sends a LR_StatusMessage upon successful path creation Failure case: - an intermediate hop creates and sends a LR_StatusMessage upon failure to forward the path to the next hop for any reason Both cases: - transit hops receive LR_StatusMessages and add a frame to them reflecting their "status" with respect to that path - the path creator receives LR_StatusMessages and decrypts/parses the LR_StatusRecord frames from the path hops. If all is good, the Path does as it would when receiving a PathConfirmMessage. If not, the Path marks the new path as failed. LR_StatusMessage is now used/sent in place of PathConfirmMessage	5 years ago
Michael	b89689fec3	Refactor path build code	5 years ago