repo stringclasses 2
values | instance_id stringclasses 10
values | base_commit stringclasses 10
values | patch stringclasses 10
values | test_patch stringclasses 10
values | problem_statement stringclasses 10
values | hints_text stringclasses 8
values | created_at stringclasses 10
values | version stringclasses 10
values | FAIL_TO_PASS sequencelengths 1 1 | PASS_TO_PASS sequencelengths 1 60 |
|---|---|---|---|---|---|---|---|---|---|---|
caddyserver/caddy | caddyserver__caddy-5404 | 960150bb034dc9a549ee7289b1a4eb4abafeb30a | diff --git a/caddyconfig/caddyfile/lexer.go b/caddyconfig/caddyfile/lexer.go
index ba8b8798796..1f531f454d1 100644
--- a/caddyconfig/caddyfile/lexer.go
+++ b/caddyconfig/caddyfile/lexer.go
@@ -284,15 +284,17 @@ func (l *lexer) next() (bool, error) {
// and processes the text to strip leading whitespace, returning the ... | diff --git a/caddyconfig/caddyfile/lexer_test.go b/caddyconfig/caddyfile/lexer_test.go
index 3c7e157ea05..801d81e2229 100644
--- a/caddyconfig/caddyfile/lexer_test.go
+++ b/caddyconfig/caddyfile/lexer_test.go
@@ -256,7 +256,7 @@ EOF same-line-arg
`),
expected: []Token{
{Line: 1, Text: `heredoc`},
- {Line:... | fuzz-tokenizer: Slice bounds out of range · caddyfile.(*lexer).next
Detailed Report: https://oss-fuzz.com/testcase?key=5119873601896448
Project: caddy
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-tokenize
Job Type: libfuzzer_asan_caddy
Platform Id: linux
Crash Type: Slice bounds out of range
Crash Address:
... | It's using weird binary data 🙈 I'm not sure what to do with that 😭
Thanks though. I'll look into it. | 2023-02-26 20:33:33 | 5404 | [
"TestLexer"
] | [
"TestDispenser_Val_Next",
"TestDispenser_NextArg",
"TestDispenser_NextLine",
"TestDispenser_NextBlock",
"TestDispenser_Args",
"TestDispenser_RemainingArgs",
"TestDispenser_ArgErr_Err",
"TestFormatter",
"TestParseVariadic",
"TestAllTokens",
"TestParseOneAndImport",
"TestRecursiveImport",
"Tes... |
caddyserver/caddy | caddyserver__caddy-6051 | 4181c79a8130a59c40c76437e15265452422ccb1 | diff --git a/caddyconfig/caddyfile/lexer.go b/caddyconfig/caddyfile/lexer.go
index bfd6c0f50bd..e5026738b4e 100644
--- a/caddyconfig/caddyfile/lexer.go
+++ b/caddyconfig/caddyfile/lexer.go
@@ -313,6 +313,11 @@ func (l *lexer) finalizeHeredoc(val []rune, marker string) ([]rune, error) {
// iterate over each line and s... | diff --git a/caddyconfig/caddyfile/lexer_test.go b/caddyconfig/caddyfile/lexer_test.go
index 92acc4da9f3..6cd568557ba 100644
--- a/caddyconfig/caddyfile/lexer_test.go
+++ b/caddyconfig/caddyfile/lexer_test.go
@@ -445,6 +445,48 @@ EOF same-line-arg
expectErr: true,
errorMessage: "mismatched leading whitespace... | Allow blank lines in Heredoc
I want to send some blank lines in the respond.
```caddyfile
example.com {
handle {
respond <<EOF
The next line is a blank line
The previous line is a blank line
EOF 200
}
}
```
But I got Error: adapting config using caddyfile: mismatched leading whitespace in ... | Yeah you're right we should probably allow fully blank lines. I'll look into that soon. (Unless someone gets to it before me, PRs welcome) | 2024-01-18 22:01:13 | 6051 | [
"TestLexer"
] | [
"TestDispenser_Val_Next",
"TestDispenser_NextArg",
"TestDispenser_NextLine",
"TestDispenser_NextBlock",
"TestDispenser_Args",
"TestDispenser_RemainingArgs",
"TestDispenser_ArgErr_Err",
"TestFormatter",
"TestParseVariadic",
"TestAllTokens",
"TestParseOneAndImport",
"TestRecursiveImport",
"Tes... |
caddyserver/caddy | caddyserver__caddy-6115 | 4512be49a9fa55270e9afa632be9ff6c9560c455 | diff --git a/modules/caddyhttp/reverseproxy/selectionpolicies.go b/modules/caddyhttp/reverseproxy/selectionpolicies.go
index b56c8074cec..b6f807c16d2 100644
--- a/modules/caddyhttp/reverseproxy/selectionpolicies.go
+++ b/modules/caddyhttp/reverseproxy/selectionpolicies.go
@@ -655,12 +655,22 @@ func (s CookieHashSelecti... | diff --git a/modules/caddyhttp/reverseproxy/selectionpolicies_test.go b/modules/caddyhttp/reverseproxy/selectionpolicies_test.go
index 9199f61988c..d7e79626c1b 100644
--- a/modules/caddyhttp/reverseproxy/selectionpolicies_test.go
+++ b/modules/caddyhttp/reverseproxy/selectionpolicies_test.go
@@ -658,6 +658,9 @@ func Te... | Sticky cookie should be Secure and SameSite=None by default
A common legacy-app routing setup looks like this:
```
reverse_proxy tomcat_serverA:8080 tomcat_serverB:8080 {
lb_policy cookie
}
```
The result might be:
```
$ curl -I https://demo.example/portal/
HTTP/2 200
cache-control: no-store, no-cac... | You're probably right.
I'm not sure `Secure` should be set by default if the site might be served over HTTP. Maybe we could only include it if we know the connection is TLS (or `X-Forwarded-Proto: https` if the request is trusted).
For `SameSite`, would this be a breaking change for anyone if we change the defaul... | 2024-02-19 23:57:52 | 6115 | [
"TestCookieHashPolicyWithSecureRequest"
] | [
"TestParseUpstreamDialAddress",
"TestEqualFold",
"TestIsPrint",
"TestRoundRobinPolicy",
"TestWeightedRoundRobinPolicy",
"TestLeastConnPolicy",
"TestIPHashPolicy",
"TestClientIPHashPolicy",
"TestFirstPolicy",
"TestQueryHashPolicy",
"TestURIHashPolicy",
"TestLeastRequests",
"TestRandomChoicePo... |
caddyserver/caddy | caddyserver__caddy-6345 | f6d2c293e752254769efe21c8d06a16ebad4845e | diff --git a/modules/caddypki/acmeserver/caddyfile.go b/modules/caddypki/acmeserver/caddyfile.go
index 7eaaec49a40..c4d11112861 100644
--- a/modules/caddypki/acmeserver/caddyfile.go
+++ b/modules/caddypki/acmeserver/caddyfile.go
@@ -42,6 +42,7 @@ func init() {
// domains <domains...>
// ip_ranges <addresses...>
... | diff --git a/caddytest/integration/caddyfile_adapt/acme_server_sign_with_root.caddyfiletest b/caddytest/integration/caddyfile_adapt/acme_server_sign_with_root.caddyfiletest
new file mode 100644
index 00000000000..9880f282150
--- /dev/null
+++ b/caddytest/integration/caddyfile_adapt/acme_server_sign_with_root.caddyfilet... | Set `sign_with_root` via Caddyfile
Please make the `sign_with_root` option [from the JSON config](https://caddyserver.com/docs/json/apps/tls/automation/policies/issuers/internal/#sign_with_root) available in the Caddyfile
Maybe related: https://github.com/caddyserver/caddy/issues/6290#issuecomment-2090785745
| 2024-05-27 18:46:06 | 6345 | [
"TestCaddyfileAdaptToJSON"
] | [
"TestACMEServerWithDefaults",
"TestACMEServerWithMismatchedChallenges",
"TestACMEServerDirectory",
"TestACMEServerAllowPolicy",
"TestACMEServerDenyPolicy",
"TestAutoHTTPtoHTTPSRedirectsImplicitPort",
"TestAutoHTTPtoHTTPSRedirectsExplicitPortSameAsHTTPSPort",
"TestAutoHTTPtoHTTPSRedirectsExplicitPortDi... | |
caddyserver/caddy | caddyserver__caddy-6411 | 59cbb2c83a03b6fe352ae0b5d05581d9148a4d24 | diff --git a/replacer.go b/replacer.go
index e5d2913e928..65815c92aec 100644
--- a/replacer.go
+++ b/replacer.go
@@ -15,6 +15,7 @@
package caddy
import (
+ "bytes"
"fmt"
"io"
"net/http"
@@ -354,6 +355,8 @@ func (f fileReplacementProvider) replace(key string) (any, bool) {
zap.Error(err))
return nil, tr... | diff --git a/caddytest/integration/testdata/foo_with_multiple_trailing_newlines.txt b/caddytest/integration/testdata/foo_with_multiple_trailing_newlines.txt
new file mode 100644
index 00000000000..75d7bfb873a
--- /dev/null
+++ b/caddytest/integration/testdata/foo_with_multiple_trailing_newlines.txt
@@ -0,0 +1,2 @@
+foo... | file.* global replacements trailing newline interaction with secrets
So basically when you do something like `acme_dns cloudflare {file./path/cool-secret}` it will error out if the secret contains a trailing newline, so you will need to remove the trailing newline from the file for it to work, which is against the unix... | :thinking: good question... Probably makes sense to strip the newline, yeah. How do other "secrets in files" systems do it (Docker secrets, Systemd secrets) I wonder? I figure if users need to re-add the newline they could do so in the config where they use the placeholder, but it's kinda unwieldy cause we don't transf... | 2024-06-19 15:54:34 | 6411 | [
"TestReplacerNew"
] | [
"TestReplacerNewWithoutFile"
] |
tokio-rs/tokio | tokio-rs__tokio-4867 | 53cf021b813c61cdeace26e863c89f65f6e92abd | diff --git a/tokio/src/sync/broadcast.rs b/tokio/src/sync/broadcast.rs
index 69ede8f89ce..426011e79c3 100644
--- a/tokio/src/sync/broadcast.rs
+++ b/tokio/src/sync/broadcast.rs
@@ -336,9 +336,6 @@ struct Slot<T> {
/// Uniquely identifies the `send` stored in the slot.
pos: u64,
- /// True signals the cha... | diff --git a/tokio/tests/sync_broadcast.rs b/tokio/tests/sync_broadcast.rs
index cee888dd2c0..9aa34841e26 100644
--- a/tokio/tests/sync_broadcast.rs
+++ b/tokio/tests/sync_broadcast.rs
@@ -47,7 +47,7 @@ macro_rules! assert_closed {
($e:expr) => {
match assert_err!($e) {
broadcast::error::TryR... | Resubscribing to a closed broadcast receiver will hang on a call to `recv`
**Version**
tokio v1.19.2, tokio master (4daeea8cad1ce8e67946bc0e17d499ab304b5ca2)
**Platform**
Windows 10 64 bit
**Description**
Attempting to resubscribe to a closed broadcast receiver will hang on calls to `recv`.
I tried this cod... | That certainly does sound like a bug.
I don't really understand everything about this channel, but shouldn't [`new_receiver`](https://github.com/tokio-rs/tokio/tree/ad942de2b738c3e2b99cebb0bf71b121980de194/tokio/src/sync/broadcast.rs#L661) update the next field similarly to how `recv_ref` does so [here](https://github.... | 2022-07-26 16:15:07 | 4867 | [
"resubscribe_to_closed_channel"
] | [
"drop_rx_while_values_remain",
"dropping_sender_does_not_overwrite",
"change_tasks",
"lagging_receiver_recovers_after_wrap_closed_1",
"lagging_receiver_recovers_after_wrap_closed_2",
"dropping_tx_notifies_rx",
"lagging_receiver_recovers_after_wrap_open",
"receiver_len_with_lagged",
"resubscribe_lagg... |
tokio-rs/tokio | tokio-rs__tokio-4898 | 9d9488db67136651f85d839efcb5f61aba8531c9 | diff --git a/tokio/src/signal/unix/driver.rs b/tokio/src/signal/unix/driver.rs
index e14a6d77747..ba2edc35167 100644
--- a/tokio/src/signal/unix/driver.rs
+++ b/tokio/src/signal/unix/driver.rs
@@ -74,11 +74,8 @@ impl Driver {
let original =
ManuallyDrop::new(unsafe { std::os::unix::net::UnixStream... | diff --git a/tokio/tests/rt_metrics.rs b/tokio/tests/rt_metrics.rs
index 914723445cd..e4cd7845ec9 100644
--- a/tokio/tests/rt_metrics.rs
+++ b/tokio/tests/rt_metrics.rs
@@ -400,7 +400,7 @@ fn io_driver_ready_count() {
let stream = tokio::net::TcpStream::connect("google.com:80");
let _stream = rt.block_on(asyn... | Unix signal driver signals writable interest without ever writing
**Version**
tokio: 1.20.1
**Platform**
(any Unix with signal feature enabled)
**Description**
https://github.com/tokio-rs/tokio/blob/2099d0bd87fe53aa98a7c02334852d279baeb779/tokio/src/signal/unix/driver.rs#L79
Here the `WRITABLE` interest is ... | 2022-08-10 23:46:15 | 4898 | [
"io_driver_ready_count"
] | [
"num_workers",
"worker_local_schedule_count",
"remote_schedule_count",
"injection_queue_depth",
"worker_steal_count",
"worker_noop_count",
"worker_local_queue_depth",
"worker_poll_count",
"worker_overflow_count",
"worker_total_busy_duration",
"io_driver_fd_count",
"worker_park_count"
] | |
tokio-rs/tokio | tokio-rs__tokio-6724 | 0cbf1a5adae81e8ff86ca6d040aeee67cf888262 | 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-25 12:07:33 | 6724 | [
"write_all_buf_vectored"
] | [
"write_all_buf",
"write_buf_err"
] |
tokio-rs/tokio | tokio-rs__tokio-6752 | 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-06 13:16:59 | 6752 | [
"wake_after_remove_last"
] | [
"expire_second_key_when_reset_to_expire_earlier",
"compact_expire_empty",
"expire_first_key_when_reset_to_expire_earlier",
"delay_queue_poll_expired_when_empty",
"compact_change_deadline",
"compact_remove_empty",
"compact_remove_remapped_keys",
"insert_in_past_fires_immediately",
"item_expiry_greate... | |
tokio-rs/tokio | tokio-rs__tokio-6838 | d6213594ca3767f182e8981fde7a119575e94c65 | diff --git a/tokio/src/net/unix/listener.rs b/tokio/src/net/unix/listener.rs
index ddd9669f6d1..9977020a283 100644
--- a/tokio/src/net/unix/listener.rs
+++ b/tokio/src/net/unix/listener.rs
@@ -81,7 +81,7 @@ impl UnixListener {
let addr = {
let os_str_bytes = path.as_ref().as_os_str().as_bytes();
... | diff --git a/tokio/tests/uds_stream.rs b/tokio/tests/uds_stream.rs
index 626a96fa31e..37e53aafcd2 100644
--- a/tokio/tests/uds_stream.rs
+++ b/tokio/tests/uds_stream.rs
@@ -3,6 +3,10 @@
#![cfg(unix)]
use std::io;
+#[cfg(target_os = "android")]
+use std::os::android::net::SocketAddrExt;
+#[cfg(target_os = "linux")]
... | UnixListener::bind with abstract unix socket path has an extra \0 prefix
**Version**
v1.40.0
**Platform**
Linux VM-66-53-centos 5.4.241-1-tlinux4-0017.12 #1 SMP Fri Aug 2 14:51:21 CST 2024 x86_64 x86_64 x86_64 GNU/Linux
**Description**
Example code:
```rust
let abstract_path = "\0/tmp/mesh/business/mmm... | The bug was introduced from this commit: https://github.com/tokio-rs/tokio/commit/b2ea40bb543a5116109b37e1fd64713c116e4312 by @mox692 , please consider submit a fix.
One possible and straight forward solution:
```rust
StdSocketAddr::from_abstract_name(&os_str_bytes[1..])?
```
Thanks for the report, I'll sub... | 2024-09-11 15:23:25 | 6838 | [
"abstract_socket_name"
] | [
"epollhup",
"accept_read_write",
"shutdown",
"poll_write_ready",
"poll_read_ready",
"try_read_write",
"try_read_buf"
] |
README.md exists but content is empty.
- Downloads last month
- 13