mirrors/arti.git/tor-proto/src/circuit/sendme.rs, branch arti-v0.0.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.02021-05-18T17:45:39ZAdd the "unreachable_pub" lint.2021-05-18T17:45:39ZNick Mathewsonnickm@torproject.org2021-05-18T17:45:39Zurn:sha1:411e1b35e054c8c9b373f6428c7c808ad8039ca0
This is a somewhat obnoxious change in its scope and requirements,
but it makes it easier to understand what the real public and
private parts of our APIs are.
Add tests for correct incoming sendme handling.2021-03-22T15:50:41ZNick Mathewsonnickm@torproject.org2021-03-22T15:50:41Zurn:sha1:886788860a5f7c841001bde14d92d61a3797f02c
At this point I'm going to pause writing tor-proto tests for a
little while and think about refactoring that could make these tests
simpler. I'm doing way too much copy-paste here.
tor-proto API: Use new_ref, not clone.2020-10-29T16:11:36ZNick Mathewsonnickm@torproject.org2020-10-29T16:11:36Zurn:sha1:4cf972d69b38749311d78abf1935e19225340ff2
Semantically, cloning a Channel or Circuit is actually increasing an
internal reference count. We should name the functions to reflect
that, to be more explicit about what we're doing.
Remove a bunch of dbg! calls.2020-10-26T18:33:14ZNick Mathewsonnickm@torproject.org2020-10-26T18:33:14Zurn:sha1:b93e4b76c812509e31d75d7caca8e7bbd3a9244dUse event_listener to find out about sendme replenishment.2020-10-26T18:25:46ZNick Mathewsonnickm@torproject.org2020-10-26T18:25:46Zurn:sha1:a796f7bf6ae53f166dff58fa7177dbd03fba221b
Previously we would fail if a sendme window was exhausted and two
tasks were waiting for it to be replenished at the same time.
Resolve a bunch of XXXM3 comments in tor-proto.2020-10-26T18:03:25ZNick Mathewsonnickm@torproject.org2020-10-26T18:00:39Zurn:sha1:4348faff3c4348443ef181071faa013835e9761etor-proto: Add tests for circuit::sendme2020-10-22T16:07:28ZNick Mathewsonnickm@torproject.org2020-10-22T16:07:28Zurn:sha1:60e7d3f3c15839ac1d2a4802dfdf639c2c8edc48Mark must-resolve XXXX issues with "XXXXM3".2020-10-18T21:38:59ZNick Mathewsonnickm@torproject.org2020-10-18T21:38:59Zurn:sha1:552313460717b7a992f520e4ddc9ec85b92a13bc
"M3" is for "milestone 3" -- my target to fix the technical debt
that I think will be bad if we ship even a pre-alpha with it.
These aren't necessarily _all_ must-resolve, but they're all
must-look-at.
Closes #15
Fix a couple of clippy warnings2020-10-15T12:36:04ZNick Mathewsonnickm@torproject.org2020-10-15T12:36:04Zurn:sha1:ae19caed7d972bc3e60e1058586c0034293d1276Revise DropMark defense to use a better type and match Tor's behavior.2020-10-13T15:52:05ZNick Mathewsonnickm@torproject.org2020-10-13T15:46:21Zurn:sha1:1085ca86dcab1f027ac5c011e496a1770eea6761