imp/dnsmasq 94
Mirror of the upstream dnsmasq repository
Extends cargo to execute the given command on multiple crates - upstream is at
Human friendly time expressions. This is a mirror of the upstream, found at
Solaris device mapper
Mirror of the gitlab cargo-info project. Please file issues here -
Native Solaris smf(5) support for dnsmaq
Mirror of the https://bitbucket.org/jimplank/gf-complete
Actix web is a small, pragmatic, and extremely fast rust web framework.
the design doc tool made for developers
:lipstick: Beautification abstraction package for Atom editor
issue commenttummychow/git-absorb
panicked at 'attempted to zero-initialize type `libgit2_sys::git_diff_options`, which is invalid'
Correct - it was compiled with nightly. I will retest with stable shortly
comment created time in 16 days
issue openedtummychow/git-absorb
panicked at 'attempted to zero-initialize type `libgit2_sys::git_diff_options`, which is invalid'
Hit this today when using git absorb
thread 'main' panicked at 'attempted to zero-initialize type `libgit2_sys::git_diff_options`, which is invalid', /export/home/imp/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:623:9
stack backtrace:
0: 0x5620217d21e0 - std::backtrace_rs::backtrace::libunwind::trace::h622bab51c72c4e69
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/../../backtrace/src/backtrace/libunwind.rs:100:5
1: 0x5620217d21e0 - std::backtrace_rs::backtrace::trace_unsynchronized::h7e820b882ebd41ee
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x5620217d21e0 - std::sys_common::backtrace::_print_fmt::h64d46258114db92f
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/sys_common/backtrace.rs:79:5
3: 0x5620217d21e0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h47111d0c1b5f0da5
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/sys_common/backtrace.rs:58:22
4: 0x5620217f638c - core::fmt::write::h1857a60b204f1b6a
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/core/src/fmt/mod.rs:1076:17
5: 0x5620217cf412 - std::io::Write::write_fmt::h4604516fed3e5731
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/io/mod.rs:1516:15
6: 0x5620217d460d - std::sys_common::backtrace::_print::h785e7a78d5ef272c
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/sys_common/backtrace.rs:61:5
7: 0x5620217d460d - std::sys_common::backtrace::print::h108047ac5c4555d5
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/sys_common/backtrace.rs:48:9
8: 0x5620217d460d - std::panicking::default_hook::{{closure}}::h1d0c271f0d087ebf
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:208:50
9: 0x5620217d42b8 - std::panicking::default_hook::h692753e26f11b7b7
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:227:9
10: 0x5620217d4cf1 - std::panicking::rust_panic_with_hook::h74ddc20305301cd9
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:577:17
11: 0x5620217d4899 - std::panicking::begin_panic_handler::{{closure}}::h1a9ca6427ceee1d0
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:484:9
12: 0x5620217d269c - std::sys_common::backtrace::__rust_end_short_backtrace::h97e27b7ab754adde
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/sys_common/backtrace.rs:153:18
13: 0x5620217d4859 - rust_begin_unwind
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:483:5
14: 0x5620217f3a81 - core::panicking::panic_fmt::hb15d6f55e8472f62
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/core/src/panicking.rs:85:14
15: 0x5620217f39cd - core::panicking::panic::h5d1c61fed2502a5f
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/core/src/panicking.rs:50:5
16: 0x5620216f1c2c - git2::diff::DiffOptions::new::ha319e7a3849a1f4f
17: 0x5620216dce67 - git_absorb::run::h50a372252ec0d033
18: 0x5620216a9ce5 - git_absorb::main::h7beeecfb29e61dd3
19: 0x5620216a71f3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h9f7afc2555467067
20: 0x5620216aade9 - std::rt::lang_start::{{closure}}::h1d2d197bbdab08fc
21: 0x5620217d5117 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h5867dc20a6af6cac
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/core/src/ops/function.rs:259:13
22: 0x5620217d5117 - std::panicking::try::do_call::h32e8dcce59f53a45
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:381:40
23: 0x5620217d5117 - std::panicking::try::h7d7b073280e6de2f
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panicking.rs:345:19
24: 0x5620217d5117 - std::panic::catch_unwind::h801333b3e4e7d79f
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/panic.rs:382:14
25: 0x5620217d5117 - std::rt::lang_start_internal::h2c157bf657c6892a
at /rustc/b1af43bc63bc7417938df056f7f25d456cc11b0e/library/std/src/rt.rs:51:25
26: 0x5620216aa202 - main
27: 0x7ffa63daf840 - __libc_start_main
28: 0x5620216a4ec9 - _start
29: 0x0 - <unknown>
created time in 16 days
startedctaggart/autorust
started time in 17 days
push eventimp/tokio
commit sha 0f70530ee7cda68b68f2f8131b5866cfa937ee1f
sync: add `get_mut()` for `Mutex,RwLock` (#2856)
commit sha f25f12d57638a2928b3f738b3b1392d8773e276e
rt: Allow concurrent `block_on`'s with basic_scheduler (#2804)
commit sha a0557840eb424e174bf81a0175c40f9e176a2cc2
io: use intrusive wait list for I/O driver (#2828) This refactors I/O registration in a few ways: - Cleans up the cached readiness in `PollEvented`. This cache used to be helpful when readiness was a linked list of `*mut Node`s in `Registration`. Previous refactors have turned `Registration` into just an `AtomicUsize` holding the current readiness, so the cache is just extra work and complexity. Gone. - Polling the `Registration` for readiness now gives a `ReadyEvent`, which includes the driver tick. This event must be passed back into `clear_readiness`, so that the readiness is only cleared from `Registration` if the tick hasn't changed. Previously, it was possible to clear the readiness even though another thread had *just* polled the driver and found the socket ready again. - Registration now also contains an `async fn readiness`, which stores wakers in an instrusive linked list. This allows an unbounded number of tasks to register for readiness (previously, only 1 per direction (read and write)). By using the intrusive linked list, there is no concern of leaking the storage of the wakers, since they are stored inside the `async fn` and released when the future is dropped. - Registration retains a `poll_readiness(Direction)` method, to support `AsyncRead` and `AsyncWrite`. They aren't able to use `async fn`s, and so there are 2 reserved slots for those methods. - IO types where it makes sense to have multiple tasks waiting on them now take advantage of this new `async fn readiness`, such as `UdpSocket` and `UnixDatagram`. Additionally, this makes the `io-driver` "feature" internal-only (no longer documented, not part of public API), and adds a second internal-only feature, `io-readiness`, to group together linked list part of registration that is only used by some of the IO types. After a bit of discussion, changing stream-based transports (like `TcpStream`) to have `async fn read(&self)` is punted, since that is likely too easy of a footgun to activate. Refs: #2779, #2728
commit sha c29f13b7a5cc68fa2dfe52991d8b7497b2497725
docs: use #[doc(no_inline)] on re-exports (#2874)
commit sha 4dfbdbff7e260eb7f046a8dc91ec0c84ae7ab2e8
rt: Allow concurrent `Shell:block_on` calls (#2868)
commit sha a1d0681cd2e581b1f6767126858d2f3d5d8992f5
process: do not publicly turn on `signal` when enabled (#2871) This change will still internally compile any `signal` resources required when `process` is enabled on unix systems, but it will not publicly turn on the cargo feature
commit sha ffa5bdb22db066b531e45b42d0cb236c3916eee2
chore: remove internal io-readiness cargo feature (#2878)
commit sha 56acde069fe7fc57259e72de612f0c91c1320972
chore: remove internal io-driver cargo feature (#2881)
commit sha 760ae89401d9addb71ebf19674980577b5501edd
chore: Use IoSlice's Copy impl to clean up some repetitive code (#2875) As we go into 0.3 we no longer need to support older versions of Rust where IoSlice did not implement Copy and Clone, so we can more easily initialize the IoSlice array in net::tcp::stream. Co-authored-by: Bryan Donlan <[email protected]>
commit sha 4186b0aa38abbec7670d53882d5cdfd4b12add5c
io: remove poll_{read,write}_buf from traits (#2882) These functions have object safety issues. It also has been decided to avoid vectored operations on the I/O traits. A later PR will bring back vectored operations on specific types that support them. Refs: #2879, #2716
commit sha cf025ba45f68934ae2138bb75ee2a5ee50506d1b
sync: support mpsc send with `&self` (#2861) Updates the mpsc channel to use the intrusive waker based sempahore. This enables using `Sender` with `&self`. Instead of using `Sender::poll_ready` to ensure capacity and updating the `Sender` state, `async fn Sender::reserve()` is added. This function returns a `Permit` value representing the reserved capacity. Fixes: #2637 Refs: #2718 (intrusive waiters)
commit sha 444660664b96f758610a0e7201a6a1a31a0f2405
chore: handle std `Mutex` poisoning in a shim (#2872) As tokio does not rely on poisoning, we can avoid always unwrapping when locking by handling the `PoisonError` in the Mutex shim. Signed-off-by: Zahari Dichev <[email protected]>
commit sha 55d932a21fd4c5fa298ca3cfdcb1388dbbf43dd0
sync: add `mpsc::Sender::closed` future (#2840) Adding closed future, makes it possible to select over closed and some other work, so that the task is woken when the channel is closed and can proactively cancel itself. Added a mpsc::Sender::closed future that will become ready when the receiver is closed.
commit sha dfdfd61372cca02087c0e2773dc978d03235bc51
Fix readiness future eagerly consuming entire socket readiness (#2887) In the `readiness` future, before inserting a waiter into the list, the current socket readiness is eagerly checked. However, it would return as a `ReadyEvent` the entire socket readiness, instead of just the interest desired from `readiness(interest)`. This would result in the later call to `clear_readiness(event)` removing all of it. Closes #2886
commit sha 99d4061203aa5dbf79b06352b06bc9818a293665
bench: fix unused_mut lint in benches (#2889)
commit sha 078d0a2ebc4d4f88cb6bce05c8ac4f5038dae9be
sync: Add `is_closed` method to mpsc senders (#2726) Co-authored-by: Alice Ryhl <[email protected]>
commit sha c6fc35aadf2cfb65e51d4a6ff5e56faf1599b670
Seal ToSocketAddrs methods with an internal argument (#2892) Closes #2891
commit sha 3403be5e2ea81eb971f38c180dac729b21c30fa8
stream: add iter and iter_mut methods to StreamMap (#2890)
commit sha dcb11118d2c7260e75c059a89b40eab3e35de53d
test: fix spelling error in documentation (#2895) Fixes: #2754
commit sha 971ed2c6df9cb3bf3543a9c780662a0b4d1a8d40
Seal FromStream methods with an internal argument (#2894)
push time in 20 days
push eventimp/tokio
commit sha 7ae010f0f3b22d1f3c9bc47732988b2e35fcf253
async-await: Use Context instead of Waker in poll (#1041) Rust nightly std::future::Future recently changed Waker to Context. Change to use Context Co-Authored-By: Kintaro <[email protected]>
commit sha b4fe517a16f1596f5c483256a4bd36551812d16d
trace-core: add a function to rebuild cached interest (#1039) ## Motivation Currently, `tokio-trace-core` permits `Subscriber`s to indicate that they are "always", "sometimes", or "never" interested in a particular callsite. When "always" or "never" is returned, then the interest is cached and the subscriber will not be asked again about that callsite. This is much more efficient than requiring the filter to be re-evaluated every time the callsite is hit. However, if a subscriber wishes to change its filter configuration dynamically at runtime, it cannot benefit from this caching. Instead, it must always return `Interest::sometimes`. Even when filters change very infrequently, they must still always be re-evaluated every time. In order to support a use-case where subscribers may change their filter configuration at runtime (e.g. tokio-rs/tokio-trace-nursery#42), but do so infrequently, we should introducing a new function to invalidate the cached interest. ## Solution This branch adds a new function in the `callsite` module, called `rebuild_interest_cache`, that will invalidate and rebuild all cached interest. ## Breaking Change In order to fix a race condition that could occur when rebuilding interest caches using `clear_interest` and `add_interest`, these methods have been replaced by a new `set_interest` method. `set_interest` should have the semantics of atomically replacing the previous cached interest, so that the callsite does not enter a temporary state where it has no interest. Closes #1038 Co-Authored-By: yaahallo <[email protected]>
commit sha 847fb59b17d8e9786abfdac474ad59e120a94254
trace-core: Introduce callsite classification in metadata (#1046) ## Motivation To ease the implementation of `Subscriber::register_callsite`, a field should be added to `Metadata` to indicate if this callsite is an event or a span. ## Solution A new struct, `Kind`, is added to the `metadata` module in `tokio-trace-core`, and a `Kind` field is added to the `Metadata` struct. Macros which construct `metadata` now require a `Kind`. `Kind` is represented as a struct with a private inner enum to allow new `Kind`s to be added without breaking changes. However, the _addition_ of the kind field _is_ a breaking change. While this could be done in a backward-compatible way, it would permit the construction of metadata with unknown kinds, and since the next `tokio-trace-core` release will be a breaking change, I opted to make the breaking change instead. New API tests for the `callsite!` and `metadata!` macros have been added to guard against future API breakage. Fixes: #986 Closes: #1008 Co-Authored-By: csmoe <[email protected]>
commit sha 5029e80a897edabef99a90989a8aea12c91fdd4d
async-await: update to new futures_api (#1049)
commit sha 88b942652c69c290656a33e0f3c9f9241e822ca4
async-await: fix examples (#1050) * Fix crate path in `Cargo.toml` of examples * Add `edition2018` to examples in the documentation to make it compiled on Rust 2018 * Fix an example in the documentation
commit sha 4bfa4ffcdfefd767d30a27fab603db29c1841508
trace-core: Dispatchers unset themselves (#1033) This branch changes `dispatcher::get_default` to unset the thread's current dispatcher while the reference to it is held by the closure. This prevents infinite loops if the subscriber calls code paths which emit events or construct spans. Note that this also means that nested calls to `get_default` inside of a `get_default` closure will receive a `None` dispatcher rather than the "actual" dispatcher. However, it was necessary to unset the default in `get_default` rather than in dispatch methods such as `Dispatch::enter`, as when those functions are called, the current state has already been borrowed. Before: ``` test enter_span ... bench: 3 ns/iter (+/- 0) test span_no_fields ... bench: 51 ns/iter (+/- 12) test span_repeatedly ... bench: 5,073 ns/iter (+/- 1,528) test span_with_fields ... bench: 56 ns/iter (+/- 49) test span_with_fields_record ... bench: 363 ns/iter (+/- 61) ``` After: ``` test enter_span ... bench: 3 ns/iter (+/- 0) test span_no_fields ... bench: 35 ns/iter (+/- 12) test span_repeatedly ... bench: 4,165 ns/iter (+/- 298) test span_with_fields ... bench: 48 ns/iter (+/- 12) test span_with_fields_record ... bench: 363 ns/iter (+/- 91) ``` Closes #1032 Signed-off-by: Eliza Weisman <[email protected]>
commit sha 7e51ab05e95cef00204ab18523de45f37d9687d3
buf: Add IntoStream (#1048) * buf: Add IntoStream * Add debug implementation for IntoStream * Add get_ref, get_mut and into_inner
commit sha cf0662199822c848b376db4973c7dbae30303c4e
tokio-sync: Add async mutual exclusion primitive (#964) This PR introduces `Lock`: A concurrency primitive built on top of `Semaphore` that provides a `Mutex`-like primitive that interacts nicely with futures. Specifically, `LockGuard` (in contrast to `MutexGuard`) does _not_ borrow the `Lock`, and can thus be passed into a future where it will later be unlocked. This replaces #958, which attempted to introduce a less generic version. The primitive proposed there will instead live in [`async-lease`](https://github.com/jonhoo/async-lease).
commit sha 712ca840336c67a61e822036607289c22ea5a2c3
trace-core: prepare for 0.2 release (#1047)
commit sha fea1f780bc1c6a6e6db821572226a662fd98c450
threadpool: add panic_handler (#1052)
commit sha 3ebca76a9a3c67cb1a654c7dc0a0af851cfe14ca
trace: prepare tokio-trace for release (#1051)
commit sha 62f34e15ce6294f6273c33548772a70d76f2ea61
Bump `tokio` to 0.1.19. (#1053) This also bumps: - tokio-async-await (0.1.7) - tokio-buf (0.1.1) - tokio-sync (0.1.5) - tokio-threadpool (0.1.14)
commit sha e5cf0cc717396d8131e3c8825667648fd7f17013
Introduce `tokio-test` crate (#1030)
commit sha abb014efc2dad72baed6375fa81c58f8abed3cb2
tokio: Bump min version of tokio-sync (#1054) It is needed for lock functionality which tokio now uses.
commit sha b2b796a228a0c1a2bf62ab7613e1b55c149e434f
rt: forward panic_handler to tokio::runtime::Builder (#1055)
commit sha 949adbb887cd05c51e17bc8e5528d8bc349e0959
chore: remember to remove path deps on release (#1057)
commit sha df702130d6b3d0c9a84b3cc3851423d99f8274bc
tcp: fix some tests that spuriously fail (#1060) This does not remove all cases of using a fixed port in doc tests, but removing some should reduce the likelihood of spurious failures.
commit sha 0e400af78c049c4b52fa4cb346237b43218b0ec9
Async/await polish (#1058) A general refresh of Tokio's experimental async / await support.
commit sha 6a8934e897f71a36ee07a818e86a7629bf787db4
Fix threadpool dependency (#1061)
commit sha 927eb80ad44b3fd37739fbb776c2ba1914c848f9
Fix an error in the mit-url in the README.md (#1068)
push time in a month
pull request commentsvenstaro/miniserve
Show "now" when last modification time less than 11 seconds
Took me some time to realize that your input is std::time::SystemTime. Once I did I went ahead and added
impl Humanize for SystemTime (much as that of the other types in chrono)
So now you can directly call it on SystemTime like this:
use chrono_humanize::Humanize;
fn humanize_systemtime(time: Option<SystemTime>) -> Option<String> {
time.map(|time| time.humanize())
}
- requires
chrono-humanize>= 0.1.1
comment created time in a month
created tagimp/chrono-humanize-rs
Human friendly time expressions. This is a mirror of the upstream, found at
created time in a month
push eventimp/chrono-humanize-rs
commit sha 494c3e62f5c66cde920a0bee8edff6b355cc5184
Update README.md for Rust 2018
commit sha 1dadb9f0b975c522d17f1c2b7fb60808614f4031
clippy::enum_glob_use
commit sha aac96492b0fcfed8df8785d45a47f3f7d2003cbb
impl Humanize for SystemTime Fixes #8
commit sha 56a58299e3501b0f6553dca30e3c96eecb691453
Derive more traits on public enums
commit sha 9227c7e9ad1ad6e0d32e6191ecd9edae5544d1b6
Document public methods
commit sha 20e5ba30127b27ceeac1534af1f307c27bde48ca
Cleanup
commit sha c90feb94af949bd0839a2947dc97bb3d88e3be08
Bump version to 0.1.1
push time in a month
push eventimp/chrono-humanize-rs
commit sha 56a58299e3501b0f6553dca30e3c96eecb691453
Derive more traits on public enums
commit sha 9227c7e9ad1ad6e0d32e6191ecd9edae5544d1b6
Document public methods
commit sha 20e5ba30127b27ceeac1534af1f307c27bde48ca
Cleanup
commit sha c90feb94af949bd0839a2947dc97bb3d88e3be08
Bump version to 0.1.1
push time in a month
push eventimp/chrono-humanize-rs
commit sha aac96492b0fcfed8df8785d45a47f3f7d2003cbb
impl Humanize for SystemTime Fixes #8
push time in a month
push eventimp/chrono-humanize-rs
commit sha 1dadb9f0b975c522d17f1c2b7fb60808614f4031
clippy::enum_glob_use
push time in a month
push eventimp/chrono-humanize-rs
commit sha 494c3e62f5c66cde920a0bee8edff6b355cc5184
Update README.md for Rust 2018
push time in a month
push eventimp/chrono-humanize-rs
commit sha ca2061b69c4a5c2a3fea85b2d4499b974515dd54
Use ..= syntax instead of deprecated ...
commit sha e53ca430f80f8f8bd00dc48afcbfa47bb0c9684c
Add tests for rough +/- 10s duration
commit sha 0591a1164066fe322dcb94be4efd265ae676e4f6
It's 2020 - time to switch to Rust 2018
commit sha ae58b2340a093259d715fb1f2cb1d5b05f147b22
Pass `Copy` argument by value
commit sha fb258021e8f784b222342bb231ab9b5280cbacea
Convert internal String manipulation to Cow Saves some allocations Close !1
commit sha 08fc19808733b6076dddb99a5a9474fd51668b54
Bump version to 0.1.0
push time in a month
created tagimp/chrono-humanize-rs
Human friendly time expressions. This is a mirror of the upstream, found at
created time in a month
push eventimp/chrono-humanize-rs
commit sha 08fc19808733b6076dddb99a5a9474fd51668b54
Bump version to 0.1.0
push time in a month
push eventimp/chrono-humanize-rs
commit sha fb258021e8f784b222342bb231ab9b5280cbacea
Convert internal String manipulation to Cow Saves some allocations Close !1
push time in a month
push eventimp/chrono-humanize-rs
commit sha fb258021e8f784b222342bb231ab9b5280cbacea
Convert internal String manipulation to Cow Saves some allocations Close !1
push time in a month
push eventimp/chrono-humanize-rs
commit sha ca2061b69c4a5c2a3fea85b2d4499b974515dd54
Use ..= syntax instead of deprecated ...
commit sha e53ca430f80f8f8bd00dc48afcbfa47bb0c9684c
Add tests for rough +/- 10s duration
commit sha 0591a1164066fe322dcb94be4efd265ae676e4f6
It's 2020 - time to switch to Rust 2018
commit sha ae58b2340a093259d715fb1f2cb1d5b05f147b22
Pass `Copy` argument by value
push time in a month
pull request commentsvenstaro/miniserve
Show "now" when last modification time less than 11 seconds
As mentioned in the chrono-humanize issue - the expected usage is to print Humantime value directly instead of going through to_text_en - this will do the right thing for all possible values of the Duration
comment created time in a month
push eventimp/iso8601
commit sha 606b017c4134577b754d1f946e75f83e10e46707
Add tests for conversion to core::time::Duration
push time in a month
pull request commentbadboy/iso8601
The number of seconds in year in month used for the conversion is (of course) negotiable :)
comment created time in 2 months
push eventimp/iso8601
commit sha 57cea39912b6d97bace791f73683a2efe4c4aebf
Add impl From<Duration> for core::time::Duration
commit sha 3b3b1b6bb89b272934621132b93fddde7bfb894b
Add tests for conversion to core::time::Duration
push time in 2 months
push eventruaze/ruaze
commit sha fe4db92d2f286ce4e981e05270c57fd98d4e452f
Update Azure REST API specs
push time in 2 months
issue commentbadboy/iso8601
I believe the OP wanted compatibility with std::time::Duration and/or chrono::Duration. I would like to add my +1 for this issue.
comment created time in 2 months
pull request commentdjc/quinn
Derive Debug for TlsSession and SessionKind
Commit message updated. Let me know if anything else is need to be done.
comment created time in 2 months
push eventimp/quinn
commit sha 84f18ee7d788681e35d936baaec45f2317d1bedc
Derive Debug for TlsSession and SessionKind Fixes #841
push time in 2 months
push eventimp/quinn
commit sha f212256435754503ce248495b6b65ee6f2211f80
Clean up warnings/errors
commit sha fe90ad8cf6053df1c63617eadd321769744ea412
Increase type length limit for interop crate
commit sha 2b78366cf0d06d184bec8c6b3bcfa2a6f4c6fea4
Schedule CI run every Friday
commit sha 476db97e98cd9949cd56c703e590a3796b3ea2b1
impl Debug for TlsSession and SessionKind Fixes #841
push time in 2 months
PR opened djc/quinn
This enables deriving Debug for other structures used in quinn that use TlsSession as a session type (for example Incoming, Endpoint etc), which in turn enables 3rd parties structures to derive Debug easily when they use said structures in their code.
pr created time in 2 months
issue commentdjc/quinn
It looks like simply deriving Debug on TlsSession and SessionKind does the trick. Is that ok with you?
comment created time in 2 months
push eventimp/quinn
commit sha 498bd15b9922d5ecf4271e3f0281236cbcf014fa
Fixes #841
push time in 2 months
push eventimp/quinn
commit sha a8f403bc9b197250f350409ca741743190b7e256
Improve stream opening behavior documentation
commit sha 15b8692dcf5bc32ccc35008ef78cef2cf63d4223
Fix spurious ZeroRttRejected on outgoing 0.5-RTT streams
commit sha eadc5d3fcfea9894c44580d98d2f6c6b7663a03f
Bump version to 0.4.0
commit sha 472a091e22bf28464d09fd80c597907e271accc8
Improve malformed frame handling
commit sha 94b7eff2611159ad57b117e29a67c84e5e5ac0f5
Don't duplicate retransmitted handshake data
commit sha 88dfacfcc608552cb9cff30afe5b9b83b37b9f06
Fix corruption of long client Initial packets
commit sha f247b2f5e5a6a739e707c79eaef7ddac56179cd0
Upgrade rcgen to 0.3
commit sha 6bd4e8e48b84998560ea0d07becbecd6dce9c8bc
Move populate_packet() below poll_transmit()
commit sha 0453f5548a8dfbb97b83cdc6a4132305ddd80d10
Pass slice into encrypt() function
commit sha 1552cb62b2791fb86d68524ed1cf64ce2c87f256
Use PartialEncode for payload lengths and crypto
commit sha c739bd8cf1c29a64cc0ed029c6a1a77f2e329b6e
Check space-independent amplification prevention first
commit sha b9649ceab77b8cb808478bfc83b896e132397f0d
Keep space order intact and filter in one go
commit sha 8e6087145435a3858110caca141d94b7bbad4647
Set the connection's remote as the default
commit sha 0ddce80652df7e4f05ace8a16a088d78cd1b6137
Initialize datagram buffer with MTU-sized allocation
commit sha d9632138fe1181facd8d2ad6248e62f9547f0ae7
Rename Transmit::packet to contents
commit sha 39db9e12e640dc463c2073068820cb631e8dd43a
Simplify server handshake retransmit test We can no longer trivially test anti-amplification, but a simplified test for losing the server's initial flight is still useful.
commit sha dee6d6a1e1e90f5c980e6c8511485f9365e5ad7f
Implement packet coalescing on outgoing packets
commit sha 00f5b26d84960b649f9e373d6948337174b53e12
Handle stream cleanup after reading inside Streams
commit sha f49de82658a8f22ac84e8140502dfd293d96ebaa
Order dependencies
commit sha 22c9a0136adf805747aeeb83d9dbb9a4cae3a768
Move space-related code into PacketSpace method
push time in 2 months
issue commentdjc/quinn
Well, here is the partial list:
ClientConfigConnectingConnectionDatagarmsEndpointEndpointBuilderIncomingNewConnectionRecvStreamSendStream
comment created time in 2 months
issue openeddjc/quinn
implementing Debug for TlsSession
Please derive (or implement) Debug for crypto::rustle::TlsSession. TlsSession is default session type parameter for many other structs, and their derive(Debug) doesn't work while TlsSession is missing Debug impl.
created time in 2 months
push eventruaze/ruaze
commit sha deddb8801700129ae89f35b2b9ae08e89692f6b2
Update azure specs
commit sha 1ee701b7fa44e6fa79e178cbedd8784e15b072d3
Update Azure API specs
push time in 2 months