| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use pointee's cookie, add convenience BufferedReader::as_mut_reader.
Name is up for discussion:
- cannot be as_mut, because that conflicts with Box::as_mut (a lot!)
- shouldn't be as_mut because get_mut is so similar and does
something completely different
|
|
|
|
|
|
- We add a buffered-reader-based function to trait Parse. Then, we
can use it in combination with buffered_reader::Mut to peel off
single objects (like MPIs) from an input stream.
|
|
- This can be used like PacketHeaderParser::ok, but in situations
where we constructed a PacketHeaderParser using
PacketHeaderParser::new_naked.
|
|
- This is a non-owning mutable reference type for the buffered
reader framework. It can be used to retain ownership of the
reader when using interfaces that consume the reader.
|
|
|
|
- This is an internal interface that uses our reader stack's
cookie. We need this to traverse the buffered reader stack. We
did not, however, expose it as an external interface, because we
didn't want to bake in the cookie type into the API.
- Having a public API that operates on buffered readers is
convenient: the current Parser::from_reader operates on
io::Readers, and will most likely construct a
buffered_reader::Generic from it. This will eagerly buffer some
data, making this interface unsuitable if you want to read in one
artifact (e.g. an MPI) without consuming more data.
- Renaming the internal functions gives us a chance to add a more
general buffered reader interface.
|
|
Closes #129.
Sponsored-by: pep.foundation
|
|
- Improve the readability of the generated documentation, by using
the full name of external types in public API.
|
|
- When using tokio 1, the socket needs to be non-blocking otherwise
the server hangs.
|
|
- Use the latest versions of capnp and tokio.
- The ipc crate exposes capnp and tokio symbols via its public
API (sequoia_ipc::Handler). Thus any user of the ipc crate has
to use the same version. Upgrade the dependencies so that
downstream users can use the latest features.
|
|
- Convert `encrypted` to `processed`.
- Since `set_encrypted` is internal API it was directly renamed without
forwarder stub.
- `encrypted()` is public API thus the old function is converted to a
forwarder of the negation of `processed()`.
- `unprocessed()` marked as deprecated.
- Update docs and NEWS file.
- Fixes #845.
|
|
- Deprecate the enum variant in preparation for v2 removal to let API
clients adjust their code as early as possible.
- Update NEWS.
- See #863.
|
|
- The documentation got out of sync with ReaderMode.
- Describe various available modes in terms of ReaderMode.
- Fixes #847.
|
|
|
|
- Closes #868.
|
|
- In 207d4ba7, the text was changed by mistake.
|
|
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- The changes in sq_usage.rs are formatting fixes. I avoided the
additional effort of preserving formatting issues for the sake of
exact equivalence.
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- Extract input and output arguments, including help texts, so they
can be easily reused by other sq subcommands.
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
- This is part of the effort of moving to clap3's derive API and
profit from the added type safety.
|
|
|
|
|
|
- Make the previously long description available using the "alternate"
(#) format specifier.
- Make the default description short.
- Update subplot tests to use short algorithm names.
- Fixes #803.
|
|
|
|
- In contrast to UnsupportedCert, this variant carries all the
packets that we failed to parse into a cert. Notably, this
includes primary keys that we don't understand. Keeping the
packets with the errors allows us to at least roundtrip the
packets.
|
|
- Fixes #834.
|
|
- We validate certificate structures based on packet tags. In the
past, this lead to problems where a secret key packet was parsed
to an unknown packet because the secret bits were malformed. This
lead to a crash in the generated parser because it was assuming to
see a secret key packet, but got an unknown packet.
- This was changed in cd5eb82edfb326d7cbde29ee105f9f88e045c240 so
that we validate the certificate structure based on packet kinds,
i.e. we would only consider a packet a secret key packet if we
managed to parse it into one. However, this caused the parser to
be overly strict, causing problems with forward compatibility, and
the parser to return an Error::MalformedCert instead of an
Error::UnsupportedCert (see #170).
- Return to validating on packet tags, but make the parser code
aware that we may have parsed some packets (like secret key
packets) to unknown packets.
- This effectively reverts commit
cd5eb82edfb326d7cbde29ee105f9f88e045c240.
- Fixes #170.
|
