| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
This type comes from the specification and indicates overload
information about a relay. We will use it in router descriptors at one
point, hence why we are adding it already.
|
| |
|
|
|
| |
This commit adds a test to verify the 10x4 character requirement for
SpFingerprint.
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit introduces FixedB16U which is a FixedB64 pedant for B16U.
It will be required for ExtraInfoDigests.
|
| |
|
|
|
| |
This commit adds a round-trip test for NumericBoolean to ensure that 0
is false and 1 is true.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a new type, NumericBoolean, which implements
NormalItemArgument in order to be parseable with parse2.
It works very simple, namely it can be used to decode/encode a boolean
as a `0` (false) or `1` (true) which is found in a few places around
tor-netdoc.
The reason why this is its own type instead of implementing
NormalItemValue for the bool primitive is, that booleans are special
numerical types and to be future-proof against other oddities, a
separate wrapper type makes most sense.
|
| |\
| |
| |
| |
| | |
Fix new warnings from Rust 1.95
See merge request tpo/core/arti!3902
|
| | | |
|
| | |
| |
| |
| |
| | |
See torspec#401 and
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3864#note_3397715
|
| | |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3864#note_3397714
|
| | |
| |
| |
| |
| |
| |
| | |
Now it follows, rather than precedes, the parse2_impls and
encode_impls modules that it imports things from.
Pure code motion apart from deleting the todo.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This is going to be used for encoding too.
|
| | |
| |
| |
| | |
We don't need the helper struct for this.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We're going to want this macrology to generate a encoder
implmeentation too. It's most convenient to make this its own module,
separating it from parse2_impls.
Enable the module if encoding is enabled, decorating its
parsing-related contents with the appropriate cfg.
Use pub(super) to export the encoding-related imports, so that we
don't end up with endlessly duplicated import lists.
Now there is place where we can put the encoder.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Start a new encode_impls module.
The pub(super) will be used in a moment.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This is what we did for authcert.rs and it worked well there.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Add debugging support to ItemValueParseable derive
See merge request tpo/core/arti!3881
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With
cargo test --all-features -p tor-netdoc -- --no-capture test2
the output now contains, amongst many other things:
netdoc TestItem parse: item start, "test-item", "N", Some("TEST OBJECT")
netdoc TestItem parse: field needed, normal, args=1, "N"
netdoc TestItem parse: field optional, normal, args=Option<_>, ""
netdoc TestItem parse: field rest, normal, args=Vec<_>, ""
netdoc TestItem parse: field object, object, object=1, Some(("TEST OBJECT", Ok(5)))
netdoc TestItem parse: item complete Ok
|
| | | | |
|
| | | |
| | |
| | |
| | | |
So far this just abolishes a duplicate P.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We're going to want tio reuse dtrace from here in the
ItemValueParseable derive (which doesn't use
NetdocSomeItemsParseableCommon because it derives for one item type,
not a document containing multiple items).
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Without this adding `#[deftly(netdoc(debug))]` can fail to build,
because the encoding module doesn't have `io::Write` in its `pub use`.
(Unlike parse2, it doesn't have a separate macro prelude.)
|
| | | |
| | |
| | |
| | | |
Ie for "arguments" that don't actually appear.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will let us use it in more places, more sensibly.
Sadly it means a lot of syntactic vinegar at many of the call sites in
the old parser, which has very janky ideas about how errors should
work.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Tests will come in a moment.
|
| | | |
| | |
| | |
| | | |
Tests will come in a moment.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-netdoc: derives: Three small improvements
See merge request tpo/core/arti!3887
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This can't trigger, but when messing about with some new features,
I messed up and got a syntax error here. Let's try this feature out,
here.
|
| | | |
| | |
| | |
| | | |
No functional change.
|
| | |/
| |
| |
| | |
T_SIGNATURES is false, just above.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-netdoc: parse2: Fix error for invalid item argument
See merge request tpo/core/arti!3879
|