repo string | pull_number int64 | instance_id string | issue_numbers sequence | base_commit string | patch string | test_patch string | problem_statement string | hints_text string | created_at string | version string | environment_setup_commit string | FAIL_TO_PASS sequence | PASS_TO_PASS sequence | FAIL_TO_FAIL sequence | PASS_TO_FAIL sequence | __index_level_0__ int64 | updated_at string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
algesten/ureq | 324 | algesten__ureq-324 | [
"321"
] | b246f0a9d2e6150b29b5504924edc090d2bf9168 | diff --git a/src/response.rs b/src/response.rs
--- a/src/response.rs
+++ b/src/response.rs
@@ -537,14 +537,16 @@ fn read_next_line(reader: &mut impl BufRead) -> io::Result<String> {
));
}
- if !s.ends_with("\r\n") {
+ if !s.ends_with("\n") {
return Err(io::Error::new(
io::Err... | diff --git a/src/response.rs b/src/response.rs
--- a/src/response.rs
+++ b/src/response.rs
@@ -644,6 +646,16 @@ mod tests {
assert_eq!("application/json", resp.content_type());
}
+ #[test]
+ fn content_type_without_cr() {
+ let s = "HTTP/1.1 200 OK\r\n\
+ Content-Type: appli... | "Header field didn't end with \r" error on some websites
On some websites, e.g. etihad.com, ureq fails with the following error:
> Header field didn't end with \r
Firefox and curl work fine.
There's 295 such websites in the top million (I'm using [Tranco list generated on the 3rd of February](https://tranco-li... | This is per spec: https://tools.ietf.org/html/rfc7230#section-3.1.2
> The first line of a response message is the status-line, consisting
> of the protocol version, a space (SP), the status code, another
> space, a possibly empty textual phrase describing the status code,
> and ending with CRLF.
>
>... | 2021-02-15T20:59:07Z | 2.0 | 9ec4e7192aa80d38d968e5989742ba10fbbbe575 | [
"response::tests::content_type_without_cr",
"test::timeout::read_timeout_during_body"
] | [
"proxy::tests::parse_proxy_http_user_pass_server_port",
"request::request_implements_send_and_sync",
"proxy::tests::parse_proxy_server",
"response::short_read",
"response::tests::charset",
"header::name_and_value",
"error::error_is_send_and_sync",
"proxy::tests::parse_proxy_socks_user_pass_server_port... | [
"test::timeout::overall_timeout_reading_json",
"test::range::read_range",
"tests::connect_http_google",
"tests::connect_https_google",
"tls_client_certificate"
] | [] | 370 | 2021-02-21T08:06:27Z |
hyperium/hyper | 3,275 | hyperium__hyper-3275 | [
"2872"
] | a45d5d5a04369f93334fc893875d8d1a49054e04 | diff --git a/src/body/incoming.rs b/src/body/incoming.rs
--- a/src/body/incoming.rs
+++ b/src/body/incoming.rs
@@ -201,7 +201,16 @@ impl Body for Incoming {
ping.record_data(bytes.len());
return Poll::Ready(Some(Ok(Frame::data(bytes))));
... | diff --git a/tests/client.rs b/tests/client.rs
--- a/tests/client.rs
+++ b/tests/client.rs
@@ -1338,7 +1338,7 @@ mod conn {
use bytes::{Buf, Bytes};
use futures_channel::{mpsc, oneshot};
use futures_util::future::{self, poll_fn, FutureExt, TryFutureExt};
- use http_body_util::{BodyExt, Empty, StreamBo... | Client: handle `RST_STREAM` with `NO_ERROR` set for the reason
**Version**
```
hyper = "0.14.18"
h2 = "0.3.13"
```
**Platform**
```
> uname -a
Linux <REDACTED> 5.17.5-76051705-generic #202204271406~1651504840~22.04~63e51bd SMP PREEMPT Mon May 2 15: x86_64 x86_64 x86_64 GNU/Linux
```
**Description**
I've ... | Yea, I think we've talked about this in a previous issue, but don't remember where. `h2` is making the "error" (the reset) trump any other frames that have been received. It should likely be changed to return all other received frames, and *then* return the error.
But _somewhere_ in the stack it should probably just su... | 2023-07-23T01:01:36Z | 1.0 | 6fd696e10974f10b2c6b9d16393bbbfa21c2333f | [
"conn::http2_responds_before_consuming_request_body"
] | [
"client_always_rejects_http09",
"client_allows_http09_when_requested",
"client_error_parse_status_out_of_range",
"client_connect_method_with_absolute_uri",
"client_get_req_body_implicitly_empty",
"client_h1_rejects_http2",
"client_get_req_body_chunked_http10",
"client_get",
"client_error_unexpected_... | [] | [] | null | 2023-07-26T19:47:07Z |
hyperium/hyper | 3,261 | hyperium__hyper-3261 | [
"2730"
] | d92d3917d950e4c61c37c2170f3ce273d2a0f7d1 | diff --git a/src/proto/h1/conn.rs b/src/proto/h1/conn.rs
--- a/src/proto/h1/conn.rs
+++ b/src/proto/h1/conn.rs
@@ -175,6 +175,13 @@ where
}
}
+ #[cfg(feature = "server")]
+ pub(crate) fn has_initial_read_write_state(&self) -> bool {
+ matches!(self.state.reading, Reading::Init)
+ ... | diff --git a/tests/server.rs b/tests/server.rs
--- a/tests/server.rs
+++ b/tests/server.rs
@@ -31,6 +31,7 @@ use hyper::body::{Body, Incoming as IncomingBody};
use hyper::server::conn::{http1, http2};
use hyper::service::{service_fn, Service};
use hyper::{Method, Request, Response, StatusCode, Uri, Version};
+use to... | Connection::graceful_shutdown always waits for the first request.
**Version**
hyper 0.14.16
**Platform**
Linux DESKTOP-DHO88R7 4.19.104-microsoft-standard #1 SMP Wed Feb 19 06:37:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
**Description**
If you gracefully shut down a server connection future before the first r... | Yea, I think this is behavior is currently on purpose. Whether it _should_ be is a fair question. I think at the time, I assumed that a _new_ connection would usually have a request incoming ASAP, whereas an idle connection might not, and so it was better to allow that request to come in.
We could alter that behavio... | 2023-07-06T18:47:14Z | 1.0 | 6fd696e10974f10b2c6b9d16393bbbfa21c2333f | [
"graceful_shutdown_before_first_request_no_block"
] | [
"get_with_body",
"empty_parse_eof_does_not_return_error",
"expect_continue_accepts_upper_cased_expectation",
"disable_keep_alive_post_request",
"h2_connect_multiplex",
"disable_keep_alive_mid_request",
"header_name_too_long",
"h2_connect_empty_frames",
"disconnect_after_reading_request_before_respon... | [] | [] | null | 2023-09-12T15:35:35Z |
serde-rs/serde | 2,802 | serde-rs__serde-2802 | [
"2801"
] | 1b4da41f970555e111f471633205bbcb4dadbc63 | diff --git a/serde/src/private/de.rs b/serde/src/private/de.rs
index c402d2c66..c146539ee 100644
--- a/serde/src/private/de.rs
+++ b/serde/src/private/de.rs
@@ -2710,6 +2710,17 @@ where
visitor.visit_unit()
}
+ fn deserialize_unit_struct<V>(
+ self,
+ _name: &'static str,
+ visit... | diff --git a/test_suite/tests/test_annotations.rs b/test_suite/tests/test_annotations.rs
index 1174be6d2..63cb3dd1b 100644
--- a/test_suite/tests/test_annotations.rs
+++ b/test_suite/tests/test_annotations.rs
@@ -1815,6 +1815,32 @@ fn test_flatten_unit() {
);
}
+#[test]
+fn test_flatten_unit_struct() {
+ #[d... | Flattening a unit struct should work like flattening unit itself
https://github.com/serde-rs/serde/pull/1874 landed support for flattening the unit type after a report in https://github.com/serde-rs/serde/issues/1873. However, it did not override `deserialize_unit_struct` and `serialize_unit_struct`, so while flattenin... | 2024-08-15T13:51:17Z | 1.20 | 1b4da41f970555e111f471633205bbcb4dadbc63 | [
"test_flatten_unit_struct"
] | [
"ser::impls::test_format_u8",
"internals::case::rename_fields",
"internals::case::rename_variants",
"tests/ui/borrow/bad_lifetimes.rs",
"tests/ui/borrow/duplicate_lifetime.rs",
"tests/ui/borrow/duplicate_variant.rs",
"tests/ui/borrow/empty_lifetimes.rs",
"tests/ui/borrow/no_lifetimes.rs",
"tests/ui/... | [] | [] | null | 2024-08-15T21:12:38Z | |
dtolnay/proc-macro2 | 236 | dtolnay__proc-macro2-236 | [
"235"
] | ee2554d3fa4214164a0b23006008dcbf9e82769f | diff --git a/build.rs b/build.rs
index 89e2ab39..153e13f5 100644
--- a/build.rs
+++ b/build.rs
@@ -61,6 +61,10 @@ fn main() {
println!("cargo:rustc-cfg=span_locations");
}
+ if version.minor < 39 {
+ println!("cargo:rustc-cfg=no_bind_by_move_pattern_guard");
+ }
+
if version.minor >= 4... | diff --git a/tests/test.rs b/tests/test.rs
index a0133f60..39e0c789 100644
--- a/tests/test.rs
+++ b/tests/test.rs
@@ -117,6 +117,27 @@ fn literal_suffix() {
assert_eq!(token_count("b'b'b"), 1);
}
+#[test]
+fn literal_iter_negative() {
+ let negative_literal = Literal::i32_suffixed(-3);
+ let tokens = Tok... | Fallback handling of negative integer literals is different to proc_macro
This crate's fallback implementation of `From<TokenTree>` for `TokenStream` treats negative integer literals as one token, however `rustc`'s implementation treats negative integer literals as an alone `-` followed by the positive integer literal.... | 2020-05-31T06:56:23Z | 1.0 | 1edd1b993b79d16f60a85f32a320d9430dfde8a8 | [
"literal_iter_negative"
] | [
"carriage_return",
"closed_immediately",
"incomplete",
"lit",
"Delimiter",
"Group",
"Ident",
"LexError",
"Literal",
"Punct",
"Spacing",
"Span",
"TokenStream",
"TokenTree",
"default_tokenstream_is_empty",
"fail",
"ident_empty - should panic",
"ident_invalid - should panic",
"ident... | [
"lifetime_invalid - should panic",
"src/lib.rs - Ident (line 813)"
] | [] | null | 2020-05-31T07:03:58Z | |
tokio-rs/tokio | 3,965 | tokio-rs__tokio-3965 | [
"3964"
] | aef2d64b0a519ff6726f8c139ee1d3e6b1959b0b | diff --git a/tokio/src/runtime/task/harness.rs b/tokio/src/runtime/task/harness.rs
index 7f1c4e4cb0c..9f0b1071130 100644
--- a/tokio/src/runtime/task/harness.rs
+++ b/tokio/src/runtime/task/harness.rs
@@ -420,7 +420,7 @@ fn poll_future<T: Future>(
cx: Context<'_>,
) -> PollFuture<T::Output> {
if snapshot.is_... | diff --git a/tokio/tests/task_abort.rs b/tokio/tests/task_abort.rs
index c524dc287d1..8f621683faa 100644
--- a/tokio/tests/task_abort.rs
+++ b/tokio/tests/task_abort.rs
@@ -1,6 +1,7 @@
#![warn(rust_2018_idioms)]
#![cfg(feature = "full")]
+use std::sync::Arc;
use std::thread::sleep;
use std::time::Duration;
@@ -... | JoinHandle::abort has no effect if the handle is immediately dropped
**Version**
Broken versions: 1.8.1, 1.5.1
Working versions: 1.8.0, 1.4.0
Likely culprit: https://github.com/tokio-rs/tokio/pull/3934/files
**Description**
JoinHandle::abort appears to have no effect if the handle is immedaitely dropped.
ht... | ~~Actually, I think this may be a miscompilation 😦 - if I turn the `async move` into an async function, it works as expected 😱~~
The problem occurs when the two tasks are scheduled on the same thread, which is why it always occurs with tokio::test, but only sometimes occurs with tokio::main.
Argh, I just realised ... | 2021-07-18T15:22:33Z | 1.8 | aef2d64b0a519ff6726f8c139ee1d3e6b1959b0b | [
"test_abort_task_that_panics_on_drop_returned",
"test_abort_task_that_panics_on_drop_contained",
"test_abort_wakes_task_3964"
] | [
"test_abort_without_panic_3662",
"remote_abort_local_set_3929",
"test_abort_without_panic_3157"
] | [] | [] | null | 2021-07-18T20:48:07Z |
tokio-rs/tokio | 3,860 | tokio-rs__tokio-3860 | [
"3837"
] | 2c24a028f6e4f2aea2b3975deeba92142f3d149b | diff --git a/tokio/CHANGELOG.md b/tokio/CHANGELOG.md
index f6537a5be81..9becb130165 100644
--- a/tokio/CHANGELOG.md
+++ b/tokio/CHANGELOG.md
@@ -1,3 +1,11 @@
+# 1.6.2 (June 14, 2021)
+
+### Fixes
+
+- test: sub-ms `time:advance` regression introduced in 1.6 ([#3852])
+
+[#3852]: https://github.com/tokio-rs/tokio/pull/3... | diff --git a/tokio/tests/time_pause.rs b/tokio/tests/time_pause.rs
index d1834af2157..02e050a2dc4 100644
--- a/tokio/tests/time_pause.rs
+++ b/tokio/tests/time_pause.rs
@@ -4,7 +4,7 @@
use rand::SeedableRng;
use rand::{rngs::StdRng, Rng};
use tokio::time::{self, Duration, Instant, Sleep};
-use tokio_test::{assert_el... | time::advance advances too far when given a Duration of sub-millisecond granularity
**Version**
```
tokio-repro v0.1.0 (/Users/hallmaxw/tokio-repro)
└── tokio v1.6.1
└── tokio-macros v1.2.0 (proc-macro)
```
**Platform**
Darwin Kernel Version 19.6.0
**Description**
`time::advance` advances time too fa... | We should probably have had a test for this. Thanks for spotting it.
I believe this behavior was designed because the driver does this https://github.com/tokio-rs/tokio/blob/master/tokio/src/time/driver/mod.rs#L111? So technically during normal operation (not in test mode) tokio would round up and I think it makes sene... | 2021-06-15T00:52:09Z | 1.6 | 2c24a028f6e4f2aea2b3975deeba92142f3d149b | [
"advance_multi_with_timer",
"advance_once_with_timer",
"regression_3710_with_submillis_advance",
"test_time_advance_3ms_and_change",
"test_time_advance_sub_ms"
] | [
"advance_after_poll",
"exact_1ms_advance",
"pause_time_in_main",
"interval",
"pause_time_in_task",
"pause_time_in_main_threads - should panic",
"sleep_no_poll",
"pause_time_in_spawn_threads",
"sleep_same_task",
"sleep_same_task_no_poll",
"paused_time_is_deterministic"
] | [] | [] | null | 2021-06-15T04:01:16Z |
tokio-rs/tokio | 3,852 | tokio-rs__tokio-3852 | [
"3837"
] | 1baea398c4ee9361c72dc7829331366ed1d1c7f0 | diff --git a/tokio/src/time/clock.rs b/tokio/src/time/clock.rs
index c5ef86be4e0..a0ff62139d3 100644
--- a/tokio/src/time/clock.rs
+++ b/tokio/src/time/clock.rs
@@ -7,7 +7,7 @@
//! configurable.
cfg_not_test_util! {
- use crate::time::{Duration, Instant};
+ use crate::time::{Instant};
#[derive(Debug, C... | diff --git a/tokio/tests/time_pause.rs b/tokio/tests/time_pause.rs
index d1834af2157..02e050a2dc4 100644
--- a/tokio/tests/time_pause.rs
+++ b/tokio/tests/time_pause.rs
@@ -4,7 +4,7 @@
use rand::SeedableRng;
use rand::{rngs::StdRng, Rng};
use tokio::time::{self, Duration, Instant, Sleep};
-use tokio_test::{assert_el... | time::advance advances too far when given a Duration of sub-millisecond granularity
**Version**
```
tokio-repro v0.1.0 (/Users/hallmaxw/tokio-repro)
└── tokio v1.6.1
└── tokio-macros v1.2.0 (proc-macro)
```
**Platform**
Darwin Kernel Version 19.6.0
**Description**
`time::advance` advances time too fa... | We should probably have had a test for this. Thanks for spotting it.
I believe this behavior was designed because the driver does this https://github.com/tokio-rs/tokio/blob/master/tokio/src/time/driver/mod.rs#L111? So technically during normal operation (not in test mode) tokio would round up and I think it makes sene... | 2021-06-10T22:00:52Z | 1.6 | 2c24a028f6e4f2aea2b3975deeba92142f3d149b | [
"advance_once_with_timer",
"advance_multi_with_timer",
"regression_3710_with_submillis_advance",
"test_time_advance_3ms_and_change",
"test_time_advance_sub_ms"
] | [
"exact_1ms_advance",
"pause_time_in_main",
"advance_after_poll",
"interval",
"pause_time_in_task",
"pause_time_in_main_threads - should panic",
"sleep_no_poll",
"sleep_same_task",
"pause_time_in_spawn_threads",
"sleep_same_task_no_poll",
"paused_time_is_deterministic"
] | [] | [] | null | 2021-06-14T23:36:05Z |
tokio-rs/tokio | 3,712 | tokio-rs__tokio-3712 | [
"3710"
] | d6da67b2e612455e16c11967c762ae802c2ac428 | diff --git a/tokio/src/time/clock.rs b/tokio/src/time/clock.rs
index 8957800cbb5..c5ef86be4e0 100644
--- a/tokio/src/time/clock.rs
+++ b/tokio/src/time/clock.rs
@@ -120,22 +120,11 @@ cfg_test_util! {
/// Panics if time is not frozen or if called from outside of the Tokio
/// runtime.
pub async fn advance... | diff --git a/tokio/tests/time_pause.rs b/tokio/tests/time_pause.rs
index bc84ac578d0..835db12f0b2 100644
--- a/tokio/tests/time_pause.rs
+++ b/tokio/tests/time_pause.rs
@@ -3,8 +3,29 @@
use rand::SeedableRng;
use rand::{rngs::StdRng, Rng};
-use tokio::time::{self, Duration, Instant};
-use tokio_test::assert_err;
+u... | `time::advance` advances timer wheel too far when called after `time::Sleep` is `poll`ed
**Version**
tokio v1.5.0
tokio-macros v1.1.0 (proc-macro)
tokio-stream v0.1.5
tokio-test v0.4.1
tokio-util v0.6.6
└── tokio v1.4.0
├── tokio v1.4.0
├── tokio-stream v0.1.5
└── tokio-test v0.4.1
├── tokio v1.4.0
└... | I tried running your examples, but they are missing a lot of imports and helper functions (e.g. `poll_next`), so I gave up.
Can you try running it against older versions, e.g. 1.1.0?
I tested every tag from 1.0.0 to 1.5.0, and they all exhibited the same behavior. If this helps, my full test suite looks like this:
... | 2021-04-17T17:50:57Z | 1.5 | 05c3cf3a0a93e79b8243577859c67f5b24708120 | [
"advance_after_poll",
"interval",
"sleep_same_task"
] | [
"pause_time_in_main",
"pause_time_in_task",
"sleep_same_task_no_poll",
"pause_time_in_main_threads - should panic",
"pause_time_in_spawn_threads",
"sleep_no_poll",
"paused_time_is_deterministic"
] | [] | [] | null | 2021-04-21T22:23:36Z |
tokio-rs/tokio | 6,752 | tokio-rs__tokio-6752 | [
"6751"
] | ab53bf0c4727ae63c6a3a3d772b7bd837d2f49c3 | diff --git a/tokio-util/src/time/delay_queue.rs b/tokio-util/src/time/delay_queue.rs
index 2b33e36188d..55dd311a03e 100644
--- a/tokio-util/src/time/delay_queue.rs
+++ b/tokio-util/src/time/delay_queue.rs
@@ -766,6 +766,12 @@ impl<T> DelayQueue<T> {
}
}
+ if self.slab.is_empty() {
+ ... | diff --git a/tokio-util/tests/time_delay_queue.rs b/tokio-util/tests/time_delay_queue.rs
index 6616327d41c..9915b11b58a 100644
--- a/tokio-util/tests/time_delay_queue.rs
+++ b/tokio-util/tests/time_delay_queue.rs
@@ -880,6 +880,19 @@ async fn peek() {
assert!(queue.peek().is_none());
}
+#[tokio::test(start_paus... | DelayQueue not woken when last item removed
**Version**
` tokio-util v0.7.11`
**Platform**
`Linux 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64`
**Description**
When `DelayQueue::poll_expired` returns `Pending` it grabs a `Waker` and stores it in [self.waker](https://github.com/tokio-... | 2024-08-06T13:16:59Z | 1.39 | ab53bf0c4727ae63c6a3a3d772b7bd837d2f49c3 | [
"wake_after_remove_last"
] | [
"time::wheel::level::test::test_slot_for",
"util::maybe_dangling::maybedangling_runs_drop",
"time::wheel::test::test_level_for",
"either::tests::either_is_async_read",
"either::tests::either_is_stream",
"any_delimiter_decoder_discard_repeat",
"any_delimiter_decoder_max_length_bursts",
"any_delimiter_d... | [] | [] | null | 2024-08-06T14:22:35Z | |
tokio-rs/tokio | 6,724 | tokio-rs__tokio-6724 | [
"6575"
] | ee8d4d1b0546c67198af3cd053d6b7b8b4fd26c3 | diff --git a/tokio/src/io/util/write_all_buf.rs b/tokio/src/io/util/write_all_buf.rs
index 05af7fe99b3..dd4709aa810 100644
--- a/tokio/src/io/util/write_all_buf.rs
+++ b/tokio/src/io/util/write_all_buf.rs
@@ -3,7 +3,7 @@ use crate::io::AsyncWrite;
use bytes::Buf;
use pin_project_lite::pin_project;
use std::future::F... | diff --git a/tokio/tests/io_write_all_buf.rs b/tokio/tests/io_write_all_buf.rs
index 7c8b619358d..52ad5965c09 100644
--- a/tokio/tests/io_write_all_buf.rs
+++ b/tokio/tests/io_write_all_buf.rs
@@ -94,3 +94,52 @@ async fn write_buf_err() {
Bytes::from_static(b"oworld")
);
}
+
+#[tokio::test]
+async fn wri... | Vectored IO for `write_all_buf`
**Is your feature request related to a problem? Please describe.**
The `AsyncWriteExt` trait provides the `write_all_buf` function to write the entire contents of a `Buf` type to the underlying writer. However, if the buf is fragmented (eg a VecDeque<u8> or Chain), then it can have po... | This seems reasonable to me. | 2024-07-25T12:07:33Z | 1.39 | ab53bf0c4727ae63c6a3a3d772b7bd837d2f49c3 | [
"write_all_buf_vectored"
] | [
"write_all_buf",
"write_buf_err"
] | [] | [] | null | 2024-07-30T11:05:45Z |
tokio-rs/tokio | 6,593 | tokio-rs__tokio-6593 | [
"6527"
] | 8e15c234c60cf8132c490ccf03dd31738cfeaca8 | diff --git a/tokio-macros/src/entry.rs b/tokio-macros/src/entry.rs
index 8858c8a1674..acdc2610f44 100644
--- a/tokio-macros/src/entry.rs
+++ b/tokio-macros/src/entry.rs
@@ -25,11 +25,37 @@ impl RuntimeFlavor {
}
}
+#[derive(Clone, Copy, PartialEq)]
+enum UnhandledPanic {
+ Ignore,
+ ShutdownRuntime,
+}
+
... | diff --git a/tests-build/tests/fail/macros_invalid_input.rs b/tests-build/tests/fail/macros_invalid_input.rs
index 85b4924f225..425b274ff7f 100644
--- a/tests-build/tests/fail/macros_invalid_input.rs
+++ b/tests-build/tests/fail/macros_invalid_input.rs
@@ -41,6 +41,9 @@ async fn test_crate_not_path_int() {}
#[tokio::t... | Allow setting `unhandled_panic` behavior as option on `tokio::test`
**Is your feature request related to a problem? Please describe.**
I have several unit tests that run some handler code that is under test in a `tokio::spawn`ed task, and sends/receives bytes to/from that handler code from the main task. My AsyncRead ... | I’m fine adding this feature. | 2024-05-28T15:57:02Z | 1.38 | 8e15c234c60cf8132c490ccf03dd31738cfeaca8 | [
"compile_fail_full"
] | [
"tests/pass/forward_args_and_output.rs [should pass]",
"tests/pass/macros_main_return.rs [should pass]",
"tests/pass/macros_main_loop.rs [should pass]",
"tests/fail/macros_dead_code.rs [should fail to compile]",
"tests/fail/macros_type_mismatch.rs [should fail to compile]",
"test_with_semicolon_without_re... | [] | [] | null | 2024-06-07T11:48:57Z |
tokio-rs/tokio | 6,414 | tokio-rs__tokio-6414 | [
"5080"
] | 1846483f1953f6ac4dd89f434e78ff99eb0c92f9 | diff --git a/tokio-util/src/codec/length_delimited.rs b/tokio-util/src/codec/length_delimited.rs
index a182dcaec0c..92d76b2cd28 100644
--- a/tokio-util/src/codec/length_delimited.rs
+++ b/tokio-util/src/codec/length_delimited.rs
@@ -386,6 +386,10 @@ use std::{cmp, fmt, mem};
/// `Builder` enables constructing configur... | diff --git a/tokio-util/tests/length_delimited.rs b/tokio-util/tests/length_delimited.rs
index ed5590f9644..091a5b449e4 100644
--- a/tokio-util/tests/length_delimited.rs
+++ b/tokio-util/tests/length_delimited.rs
@@ -689,6 +689,66 @@ fn encode_overflow() {
codec.encode(Bytes::from("hello"), &mut buf).unwrap();
}
... | LengthDelimitedCodec::length_field_type()/length_field_len() should also update max_frame_length
**Version** tokio-util v0.7.2
**Platform** Win7
**Description**
Currently `LengthDelimitedCodec`s `Encoder`truncates frame length, which leads to corrupted data (e.g. 6Mb frame prefixed with 2-bytes length).
I exp... | Hmm... maybe the best approach would be to validate params in `Builder::new_codec()` and fail if some params are incompatible/invalid? | 2024-03-19T20:02:49Z | 1.36 | 1846483f1953f6ac4dd89f434e78ff99eb0c92f9 | [
"frame_does_not_fit",
"pos_adjusted_frame_does_not_fit",
"neg_adjusted_frame_does_not_fit"
] | [
"time::wheel::test::test_level_for",
"time::wheel::level::test::test_slot_for",
"either::tests::either_is_async_read",
"either::tests::either_is_stream",
"util::maybe_dangling::maybedangling_runs_drop",
"any_delimiter_decoder_discard_repeat",
"any_delimiter_decoder_max_length_bursts",
"any_delimiter_d... | [] | [] | null | 2025-01-18T13:10:28Z |
tokio-rs/tokio | 6,231 | tokio-rs__tokio-6231 | [
"4782"
] | 4aa7bbff4c70b7c43c931b1e18af5048da191f40 | diff --git a/README.md b/README.md
index a9e348756fe..00979b4dfa3 100644
--- a/README.md
+++ b/README.md
@@ -56,7 +56,7 @@ Make sure you activated the full features of the tokio crate on Cargo.toml:
```toml
[dependencies]
-tokio = { version = "1.35.0", features = ["full"] }
+tokio = { version = "1.35.1", features =... | diff --git a/tokio/tests/coop_budger.rs b/tokio/tests/coop_budger.rs
new file mode 100644
index 00000000000..0c4cc7e6497
--- /dev/null
+++ b/tokio/tests/coop_budger.rs
@@ -0,0 +1,77 @@
+#![warn(rust_2018_idioms)]
+#![cfg(all(feature = "full", target_os = "linux"))]
+
+use std::sync::atomic::{AtomicUsize, Ordering};
+us... | Tokio in current_thread not releasing open file handles once the limit is reached.
**Version**
`cargo tree | grep tokio`
```
└── tokio v1.19.2
└── tokio-macros v1.8.0 (proc-macro)
```
**Platform**
The output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
```
Linux pdebian 5.10.0-10-amd64 #1 ... | @nohupped this reproduces more reliably:
`bin/server.rs`
```rust
use std::fs::remove_file;
use tokio::net::{UnixListener, UnixStream};
use ulimit_echo::SOCK;
#[tokio::main(flavor = "current_thread")]
async fn main() {
let _ = remove_file(SOCK);
let sock = UnixListener::bind(SOCK).unwrap();
l... | 2023-12-19T17:13:52Z | 1.35 | f80bbec28ff790d15481a29583c9b778bf0cc40e | [
"coop_budget_udp_send_recv"
] | [] | [] | [] | null | 2023-12-19T17:52:22Z |
tokio-rs/tokio | 5,914 | tokio-rs__tokio-5914 | [
"5913"
] | 51cffbb74f1d2d09fff4e3431199641620c1b3b5 | diff --git a/tokio/src/io/split.rs b/tokio/src/io/split.rs
index f067b65a826..63f0960e4f3 100644
--- a/tokio/src/io/split.rs
+++ b/tokio/src/io/split.rs
@@ -35,9 +35,12 @@ cfg_io_util! {
where
T: AsyncRead + AsyncWrite,
{
+ let is_write_vectored = stream.is_write_vectored();
+
let inn... | diff --git a/tokio/tests/io_split.rs b/tokio/tests/io_split.rs
index 77b77a3a04c..9f17c9eb14e 100644
--- a/tokio/tests/io_split.rs
+++ b/tokio/tests/io_split.rs
@@ -1,7 +1,9 @@
#![warn(rust_2018_idioms)]
#![cfg(all(feature = "full", not(target_os = "wasi")))] // Wasi does not support panic recovery
-use tokio::io::... | `WriteHalf<T>` does not delegate `poll_write_vectored` and `is_write_vectored` to its inner struct.
**Version**
```
├── tokio v1.29.1
├── tokio v1.29.1
└── tokio-util v0.6.10
└── tokio v1.29.1 (*)
```
**Platform**
```
Darwin mac-Y50M4FT459 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:22... | 2023-08-05T15:08:53Z | 1.29 | 51cffbb74f1d2d09fff4e3431199641620c1b3b5 | [
"method_delegation"
] | [
"is_send_and_sync",
"split_stream_id",
"unsplit_err1 - should panic",
"unsplit_err2 - should panic",
"unsplit_ok"
] | [] | [] | null | 2023-08-10T08:11:01Z |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 5