112 Commits (175ae4d3d1676d9607934086a0697ef280c0b8ad)

Author	SHA1	Message	Date
Jeff Becker	32e768d7dd	change log	5 years ago
Jeff Becker	bf0416cab8	remove Time_t, add operator overload for printing llarp_time_t and add to_json function for serializing llarp_time_t to json	5 years ago
Jeff Becker	d2d109e92c	llarp_time_t is now using std::chrono	5 years ago
Jason Rhinelander	089056ca5b	Remove all ABSL_ATTRIBUTE_UNUSED uses	5 years ago
Jason Rhinelander	f84ce61d66	Removed empty cpp files ... These aren't needed: CMake already knows how to follow #includes and rebuild when headers change as long as the headers are included *somewhere*. The extra .cpp files here just require building a bunch of .cpp files with just header content that we just end up throw away during linking (since the same things will also be compiled in whatever other compilation units include the same headers).	5 years ago
Jason Rhinelander	b4440094b0	De-abseil, part 2: mutex, locks, (most) time ... - util::Mutex is now a std::shared_timed_mutex, which is capable of exclusive and shared locks. - util::Lock is still present as a std::lock_guard<util::Mutex>. - the locking annotations are preserved, but updated to the latest supported by clang rather than using abseil's older/deprecated ones. - ACQUIRE_LOCK macro is gone since we don't pass mutexes by pointer into locks anymore (WTF abseil). - ReleasableLock is gone. Instead there are now some llarp::util helper methods to obtain unique and/or shared locks: - `auto lock = util::unique_lock(mutex);` gets an RAII-but-also unlockable object (std::unique_lock<T>, with T inferred from `mutex`). - `auto lock = util::shared_lock(mutex);` gets an RAII shared (i.e. "reader") lock of the mutex. - `auto lock = util::unique_locks(mutex1, mutex2, mutex3);` can be used to atomically lock multiple mutexes at once (returning a tuple of the locks). This are templated on the mutex which makes them a bit more flexible than using a concrete type: they can be used for any type of lockable mutex, not only util::Mutex. (Some of the code here uses them for getting locks around a std::mutex). Until C++17, using the RAII types is painfully verbose: ```C++ // pre-C++17 - needing to figure out the mutex type here is annoying: std::unique_lock<util::Mutex> lock(mutex); // pre-C++17 and even more verbose (but at least the type isn't needed): std::unique_lock<decltype(mutex)> lock(mutex); // our compromise: auto lock = util::unique_lock(mutex); // C++17: std::unique_lock lock(mutex); ``` All of these functions will also warn (under gcc or clang) if you discard the return value. You can also do fancy things like `auto l = util::unique_lock(mutex, std::adopt_lock)` (which lets a lock take over an already-locked mutex). - metrics code is gone, which also removes a big pile of code that was only used by metrics: - llarp::util::Scheduler - llarp:🧵:TimerQueue - llarp::util::Stopwatch	5 years ago
Jason Rhinelander	ac1486d0be	Replace absl::optional with optional-lite ... Step 1 of removing abseil from lokinet. For the most part this is a drop-in replacement, but there are also a few changes here to the JSONRPC layer that were needed to work around current gcc 10 dev snapshot: - JSONRPC returns a json now instead of an optional<json>. It doesn't make any sense to have a json rpc call that just closes the connection with returning anything. Invoked functions can return a null (default constructed) result now if they don't have anything to return (such a null value won't be added as "result").	5 years ago
Jeff Becker	9efd796145	initial wack at 0.7.0 dht fixes	5 years ago
Jeff Becker	4185d47d4b	link layer message priority	5 years ago
Jeff Becker	ecf2685aa3	use optional	5 years ago
Jeff Becker	d7c78b0c71	comments	5 years ago
Jeff Becker	f3e96e06b2	propagate error to client	5 years ago
Jeff Becker	a9c9fe9c24	limit client side path builds per ip	5 years ago
Stephen Shelton	66a058a2af	Make format	5 years ago
Stephen Shelton	93b8832026	Merge branch 'dev' into private-keys-backup-support	5 years ago
Jeff Becker	56dce90de9	add trace log level for tracking logic thread jobs	5 years ago
Stephen Shelton	db56e17c23	Rename bencode function for clarity	5 years ago
Stephen Shelton	1666498405	Replace bencode_write_version_entry with a more general-purpose function for writing bencoded dictionary entries	5 years ago
Jason Rhinelander	d96d33329b	Merge pull request #912 from majestrate/logic-thread-fix-2019-11-13 ... fix logic thread behavior	5 years ago
Jason Rhinelander	6524563d33	Merge pull request #897 from majestrate/bencode-seek-for-version-2019-11-03 ... seek for version and set it before deserializing	5 years ago
Jeff Becker	b34caa3e26	make unit tests pass for iwp	5 years ago
Thomas Winget	75512b1b58	ban zero id for pathid; clarity and cleanup	5 years ago
Thomas Winget	9d3e7d349c	Add per-path queues, prioritize control messages over traffic	5 years ago
Jeff Becker	9d266dbec7	meh	5 years ago
Jeff Becker	bdb0b847f8	seek for version and set it before deserializing	5 years ago
Jeff Becker	5cdd92e2a3	remove more locking and make it safe	5 years ago
Michael	edd0ec398f	Move thread stuff to subdirectory	5 years ago
Michael	0950571313	Move metrics to subdirectory	5 years ago
Michael	4d8fe2a8a8	Move meta programming to subdirectory	5 years ago
Michael	1aec0dfa2b	Move logging to subdirectory	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	697ece64cc	make TransitHop self-destruct if path is invalidated	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	488695047f	Remove redundant else blocks	5 years ago
Michael	08609f9e5a	Rename message files	5 years ago
Michael	68063b320c	Rename InboundMessageParser to LinkMessageParser	5 years ago
Michael	8884d0d9d4	Merge changes from upstream	5 years ago
Michael	333b23b59c	Tweak link message parser	5 years ago
Michael	8a058fcb34	Move other messages	5 years ago
Michael	83bd9227a7	Move exit messages	5 years ago
Michael	d6751e3eeb	Move subset of messages to right directory	5 years ago
Michael	2291d48bcc	Move remaining messages around	5 years ago
Michael	66cf5cc73d	Move exit messages to match header	5 years ago
Michael	b89689fec3	Refactor path build code	5 years ago
Michael	95646d2d87	Publish metric tags	5 years ago
Michael	75430a234c	Convert to use memFn	5 years ago
Michael	491fee206b	Port code to use CryptoManager over passing Crypto pointers	5 years ago
Michael	3f53965b71	Remove all use of IBEncodeMessage	5 years ago
Jeff Becker	64c7ed42fc	make format	5 years ago