4 Commits (a681c28e5fcb23335f97430959ce591913ad6be9)

Author	SHA1	Message	Date
Jeff Becker	5cdd92e2a3	remove more locking and make it safe	5 years ago
Michael	16cdfbd5f0	clang-tidy modernize pass	5 years ago
Michael	4763888d2c	Add fail-able docker build for gcc trunk	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