repo string | pull_number int64 | instance_id string | issue_numbers list | base_commit string | patch string | test_patch string | problem_statement string | hints_text string | created_at string | version string | updated_at string | environment_setup_commit string | FAIL_TO_PASS list | PASS_TO_PASS list | FAIL_TO_FAIL list | PASS_TO_FAIL list | source_dir string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
imsnif/bandwhich | 23 | imsnif__bandwhich-23 | [
"16"
] | 408ec397c81bb99d6727f01d5dc058e814012714 | diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ Windows is not supported at the moment - if you'd like to contribute a windows p
### Usage
```
USAGE:
- what [FLAGS] --interface <interface>
+ what [FLAGS] [OPTIONS]
FLAGS:
-h, --help Prints help information
d... | diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -46,14 +46,14 @@ Note that since `what` sniffs network packets, it requires root privileges - so
### raw_mode
`what` also supports an easier-to-parse mode that can be piped or redirected to a file. For example, try:
```
-what -i eth0 --raw | grep ... | Listen on all interfaces
`what` now listens on the interface given by the `-i` flag. The default behaviour should probably be "listen on all interfaces", with the -i flag being an optional override.
Things that are needed to do this:
1. The OS layer (eg. `os/linux.rs`) needs to be adjusted.
2. The `OsInputOutput` ... | 2019-12-10T22:07:27Z | 0.4 | 2019-12-22T09:53:02Z | 408ec397c81bb99d6727f01d5dc058e814012714 | [
"tests::cases::ui::basic_startup",
"tests::cases::ui::layout_under_120_width_under_30_height",
"tests::cases::ui::layout_under_150_width_under_30_height",
"tests::cases::ui::layout_full_width_under_30_height",
"tests::cases::ui::layout_under_120_width_full_height",
"tests::cases::raw_mode::multiple_packet... | [] | [] | [] | auto_2025-06-07 | |
imsnif/bandwhich | 118 | imsnif__bandwhich-118 | [
"100"
] | e6bb39a5e992498e00bc3af47d92352865e3223d | diff --git a/.gitignore b/.gitignore
--- a/.gitignore
+++ b/.gitignore
@@ -11,4 +11,4 @@ debian/*
!debian/control
!debian/copyright
!debian/rules
-!debian/source
+!debian/source
\ No newline at end of file
diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,9 @@ The format is ba... | diff --git a/src/tests/cases/snapshots/ui__basic_only_addresses.snap b/src/tests/cases/snapshots/ui__basic_only_addresses.snap
--- a/src/tests/cases/snapshots/ui__basic_only_addresses.snap
+++ b/src/tests/cases/snapshots/ui__basic_only_addresses.snap
@@ -51,5 +51,5 @@ expression: "&terminal_draw_events_mirror[0]"
│ ... | Option to change the default 'window' when terminal is small
Is it possible to implement an option for default 'window' to display when the terminal size is small?
I'd love to be able to get 'Utilization by connection' as default information, for example, instead of 'Utilization by process name'.
And even more, an ... | I'd be open to adding `--connections`, `--remote-ips` and `--processes` flags.
These would have to be mutually exclusive, and picking one of them would only display that window regardless of terminal size.
If anyone wants to pick this up and is unsure how to proceed, give me a ping here or privately.
Hello @imsni... | 2020-01-14T23:51:55Z | 0.14 | 2020-05-17T20:40:05Z | e6bb39a5e992498e00bc3af47d92352865e3223d | [
"tests::cases::ui::basic_processes_with_dns_queries",
"tests::cases::ui::basic_startup",
"tests::cases::ui::basic_only_connections",
"tests::cases::ui::basic_only_processes",
"tests::cases::ui::basic_only_addresses",
"tests::cases::ui::two_windows_split_vertically",
"tests::cases::ui::layout_under_120_w... | [
"tests::cases::raw_mode::bi_directional_traffic",
"tests::cases::raw_mode::multiple_connections_from_remote_address",
"tests::cases::raw_mode::multiple_packets_of_traffic_from_different_connections",
"tests::cases::raw_mode::one_process_with_multiple_connections",
"tests::cases::raw_mode::one_ip_packet_of_t... | [] | [] | auto_2025-06-07 |
rust-fuzz/cargo-fuzz | 388 | rust-fuzz__cargo-fuzz-388 | [
"386"
] | a608970259c3b0d575e70b0748c1c4cf79081031 | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -165,6 +165,20 @@ pub struct BuildOptions {
/// and the fuzzer can store an input to the corpus at each condition that it passes;
/// giving it a better chance of producing an input that reaches `res = 2;`.
pub disa... | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -265,6 +279,7 @@ mod test {
no_cfg_fuzzing: false,
no_trace_compares: false,
disable_branch_folding: None,
+ no_include_main_msvc: false,
};
let opts = vec![
| Fuzzing Windows DLL (cdylib) - Unresolved External Symbol Main
Hi cargo-fuzz devs! I am working on fuzzing a Windows DLL with cargo-fuzz and have been hitting a wall with a particular linker error. I've reproduced the problem in a small & simple Cargo project to demonstrate the issue.
## Problem Description
The i... | 2024-10-16T17:58:54Z | 0.12 | 2024-11-05T18:55:01Z | a608970259c3b0d575e70b0748c1c4cf79081031 | [
"rustc_version::tests::test_parsing_future_stable",
"rustc_version::tests::test_parsing_nightly",
"rustc_version::tests::test_parsing_stable",
"options::test::display_build_options",
"help",
"init_defines_correct_dependency",
"init_finds_parent_project",
"add_twice",
"init_twice",
"list",
"tmin"... | [] | [] | [] | auto_2025-06-12 | |
rust-fuzz/cargo-fuzz | 344 | rust-fuzz__cargo-fuzz-344 | [
"343"
] | abb7a67c5b2e1263c3e5c7abfa8c70bb4dec7796 | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -126,6 +126,13 @@ pub struct BuildOptions {
#[arg(long)]
pub no_cfg_fuzzing: bool,
+ #[arg(skip = false)]
+ /// Add the 'cfg(fuzzing-repro)' compilation configuration. This build
+ /// option will be automatic... | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -232,6 +239,7 @@ mod test {
coverage: false,
strip_dead_code: false,
no_cfg_fuzzing: false,
+ cfg_fuzzing_repro: false,
no_trace_compares: false,
};
diff --... | Detect when code is reproducing a crash vs when it is fuzzing
Hi all,
I have a lot of fun using `cargo fuzz` on my projects! It lowers the barrier enough that fuzzing becomes simple, so well done :+1:
When I find a crash, I often need to debug it by adding extra `dbg!` or `eprintln!` calls to my code. Is there a... | I would be in support of a `cfg(fuzz_repro)` or something. | 2023-06-16T13:28:04Z | 0.11 | 2023-06-18T17:12:28Z | abb7a67c5b2e1263c3e5c7abfa8c70bb4dec7796 | [
"options::test::display_build_options",
"help",
"init_finds_parent_project",
"init_twice",
"add_twice",
"list",
"tmin"
] | [] | [] | [] | auto_2025-06-12 |
rust-fuzz/cargo-fuzz | 264 | rust-fuzz__cargo-fuzz-264 | [
"263"
] | 2e496ca9cfe11de7cfb3d89b2299e93359ebc72f | diff --git a/src/project.rs b/src/project.rs
--- a/src/project.rs
+++ b/src/project.rs
@@ -822,6 +830,10 @@ impl FuzzProject {
targets: Vec::new(),
})
}
+
+ fn fuzz_dir_is_default_path(&self) -> bool {
+ self.fuzz_dir.ends_with(DEFAULT_FUZZ_DIR)
+ }
}
fn collect_targets(value... | diff --git a/src/project.rs b/src/project.rs
--- a/src/project.rs
+++ b/src/project.rs
@@ -459,14 +459,22 @@ impl FuzzProject {
eprintln!();
}
+ let fuzz_dir = if self.fuzz_dir_is_default_path() {
+ String::new()
+ } else {
+ format!(" ... | [`fuzz run`] Bad discovered input should display custom fuzz dir
Currently, when `fuzz run someTarget` discovers a bad input, it doesn't take into consideration custom `--fuzz-dir` directories.
Actual:
```
RUST_BACKTRACE=1 cargo fuzz run --fuzz-dir someDirectory someTarget
...
Reproduce with:
cargo fuzz... | 2021-05-23T01:27:42Z | 0.10 | 2021-05-25T17:16:22Z | 78965346c161a3800166c41304f61717e9d7e85c | [
"options::test::display_build_options",
"help",
"init_finds_parent_project",
"init_twice",
"add_twice",
"list"
] | [] | [] | [] | auto_2025-06-12 | |
rust-fuzz/cargo-fuzz | 262 | rust-fuzz__cargo-fuzz-262 | [
"238"
] | 089dfae55534ae29a6323b4e0368ae6ebe9b34f8 | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -13,8 +13,8 @@ pub use self::{
run::Run, tmin::Tmin,
};
-use std::fmt as stdfmt;
use std::str::FromStr;
+use std::{fmt as stdfmt, path::PathBuf};
use structopt::StructOpt;
#[derive(Debug, Clone, Copy, PartialEq)]
diff... | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -186,6 +186,23 @@ impl stdfmt::Display for BuildOptions {
}
}
+#[derive(Clone, Debug, StructOpt, PartialEq)]
+pub struct FuzzDirWrapper {
+ /// The path to the fuzz project directory.
+ #[structopt(long = "fuzz-dir")... | Support for non-standard project directories
`fuzz` is currently the only possible directory name and it would be nice to have something like `cargo fuzz run --path some_fuzz_project_dir someTarget`
| That the directory containing the fuzzing code _has to be_ called "fuzz" (and cannot be renamed nor moved deeper in the directory structure) is a limitation that is not documented anywhere. Is there a reason for it? | 2021-05-08T19:52:56Z | 0.10 | 2021-05-13T17:23:13Z | 78965346c161a3800166c41304f61717e9d7e85c | [
"options::test::display_build_options",
"help",
"init_finds_parent_project",
"list",
"init_twice",
"add_twice"
] | [] | [] | [] | auto_2025-06-12 |
rust-fuzz/cargo-fuzz | 234 | rust-fuzz__cargo-fuzz-234 | [
"228"
] | 9f2f36888d10504f0a219bf1a91b72837d9fba56 | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -15,7 +15,7 @@ use std::fmt as stdfmt;
use std::str::FromStr;
use structopt::StructOpt;
-#[derive(Debug, Clone, Copy)]
+#[derive(Debug, Clone, Copy, PartialEq)]
pub enum Sanitizer {
Address,
Leak,
diff --git a/src/o... | diff --git a/src/options.rs b/src/options.rs
--- a/src/options.rs
+++ b/src/options.rs
@@ -110,3 +110,125 @@ pub struct BuildOptions {
/// Unstable (nightly-only) flags to Cargo
pub unstable_flags: Vec<String>,
}
+
+impl stdfmt::Display for BuildOptions {
+ fn fmt(&self, f: &mut stdfmt::Formatter) -> stdf... | Recommended reproduction command ignores arguments
When running the fuzzer with specific sanitizer, time or memory settings and an issue is found then the output for reproduction is not complete. In particular the recommended command line for reproducing the issue misses any of these parameters as well as the used `car... | Thanks for reporting! Here's the code that needs to change:
https://github.com/rust-fuzz/cargo-fuzz/blob/2fb3bd85c0dd57ea7f3d5c29174c26a5550d0aa8/src/project.rs#L426-L436
We need to incorporate [the arguments](https://github.com/rust-fuzz/cargo-fuzz/blob/2fb3bd85c0dd57ea7f3d5c29174c26a5550d0aa8/src/options/run.rs... | 2020-07-02T12:19:45Z | 0.8 | 2020-07-06T18:55:01Z | 9f2f36888d10504f0a219bf1a91b72837d9fba56 | [
"help",
"init_finds_parent_project",
"add_twice",
"init_twice",
"list"
] | [] | [] | [] | auto_2025-06-12 |
rust-fuzz/cargo-fuzz | 231 | rust-fuzz__cargo-fuzz-231 | [
"230"
] | 87c36a1deee8ca9b550fe034623a7445d7e8c770 | diff --git a/src/main.rs b/src/main.rs
--- a/src/main.rs
+++ b/src/main.rs
@@ -40,7 +40,11 @@ fuzz/fuzz_targets/, i.e. the name picked when running `cargo fuzz add`.
This will run the script inside the fuzz target with varying inputs until it
finds a crash, at which point it will save the crash input to the artifact
... | diff --git a/src/project.rs b/src/project.rs
--- a/src/project.rs
+++ b/src/project.rs
@@ -182,7 +183,7 @@ impl FuzzProject {
// performance, we're taking a huge hit relative to actual release mode.
// Local tests have once showed this to be a ~3x faster runtime where
// otherwise functions l... | Fuzzing with default settings is much slower than it needs to be
`cargo fuzz run` currently defaults to debug mode with Address Sanitizer. Debug mode in Rust is needlessly slow, easily 20x slower than release mode, and for fuzzing performance is critical. It would be a much better idea to default to release mode, but w... | For reference, AFL already defaults to release mode with overflow checks and debug assertions: https://github.com/rust-fuzz/afl.rs/blob/d156adfb072aad655342a1a04cdbe4d9ac2ffc9e/src/bin/cargo-afl.rs#L294 | 2020-06-20T21:45:55Z | 0.7 | 2020-11-11T18:48:06Z | 87c36a1deee8ca9b550fe034623a7445d7e8c770 | [
"help",
"init_finds_parent_project",
"add_twice",
"init_twice",
"list"
] | [] | [] | [] | auto_2025-06-12 |
rust-lang/chalk | 75 | rust-lang__chalk-75 | [
"74"
] | f4f9dfa86c497aa222864fd6abc9e955ca23ce80 | diff --git a/chalk-parse/src/ast.rs b/chalk-parse/src/ast.rs
--- a/chalk-parse/src/ast.rs
+++ b/chalk-parse/src/ast.rs
@@ -177,6 +177,7 @@ pub struct Identifier {
pub enum WhereClause {
Implemented { trait_ref: TraitRef },
+ Normalize { projection: ProjectionTy, ty: Ty },
ProjectionEq { projection: Proj... | diff --git a/src/lib.rs b/src/lib.rs
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -2,6 +2,7 @@
#![cfg_attr(test, feature(test))]
#![feature(conservative_impl_trait)]
#![feature(catch_expr)]
+#![feature(crate_visibility_modifier)]
#![feature(match_default_bindings)]
#![feature(specialization)]
#![feature(step_trait)]
diff... | fallback clauses considered harmful / how to handle projection equality
In working on https://github.com/rust-lang-nursery/chalk/pull/73, I encountered a problem with the concept of a "fallback clause", which is currently a key part of how we handle normalization. The idea of a fallback clause is that it is a clause th... | 2018-01-19T09:17:56Z | 0.1 | 2018-01-20T12:30:20Z | 154020e4884e7b9fe41a93a6970cfff78783cdcc | [
"lower::test::goal_quantifiers",
"lower::test::atc_accounting",
"solve::test::mixed_indices_normalize_application",
"solve::test::atc1",
"solve::test::normalize_fallback_option",
"solve::test::normalize_basic",
"solve::test::normalize_under_binder"
] | [
"lower::test::concrete_impl_and_blanket_impl",
"lower::test::nonoverlapping_assoc_types",
"lower::test::multiple_parameters",
"solve::infer::test::universe_error",
"solve::infer::test::cycle_indirect",
"solve::infer::test::universe_error_indirect_1",
"lower::test::multiple_nonoverlapping_impls",
"lowe... | [] | [] | auto_2025-06-13 | |
rust-lang/chalk | 55 | rust-lang__chalk-55 | [
"25"
] | 7eb0f085b86986159097da1cb34dc065f2a6c8cd | diff --git a/src/fold/instantiate.rs b/src/fold/instantiate.rs
--- a/src/fold/instantiate.rs
+++ b/src/fold/instantiate.rs
@@ -39,7 +39,7 @@ macro_rules! subst_method {
subst_method!(Goal);
subst_method!(Ty);
-impl<'b> Folder for Subst<'b> {
+impl<'b> FolderVar for Subst<'b> {
fn fold_free_var(&mut self, depth... | diff --git a/src/solve/infer/test.rs b/src/solve/infer/test.rs
--- a/src/solve/infer/test.rs
+++ b/src/solve/infer/test.rs
@@ -65,7 +65,7 @@ struct Normalizer<'a> {
table: &'a mut InferenceTable,
}
-impl<'q> Folder for Normalizer<'q> {
+impl<'q> FolderVar for Normalizer<'q> {
fn fold_free_var(&mut self, de... | refactor occurs check into a folder
The occurs check code in `src/solve/infer/unify.rs` (specifically, the methods defined on `OccursCheck`) follows a very folder-like pattern. Unfortunately, it can't quite use the `Folder` trait (as defined in `fold.rs`) because that trait only contains "callback methods" for processi... | Working on it.
@fabric-and-ink cool, feel free to come to gitter channel with questions, if any arise
Slow but steady progress... :)
I followed your suggestion to implement a bridge trait. Now I am stuck at connecting both kinds of folders at this point:
```rust
fn fold_lifetime(&mut self, lifetime: &Lifetime, ... | 2017-08-05T18:28:06Z | 0.1 | 2017-10-10T11:21:48Z | 154020e4884e7b9fe41a93a6970cfff78783cdcc | [
"solve::infer::test::cycle_error",
"solve::infer::test::cycle_indirect",
"solve::infer::test::universe_promote_bad",
"lower::test::type_parameter_bound",
"solve::infer::test::universe_error_indirect_2",
"lower::test::invalid_name",
"solve::infer::test::universe_promote",
"solve::infer::test::infer",
... | [] | [] | [] | auto_2025-06-13 |
rust-lang/chalk | 282 | rust-lang__chalk-282 | [
"275"
] | f9658ca506598fd711e89972b88721ce3afa5382 | diff --git a/chalk-solve/src/infer/instantiate.rs b/chalk-solve/src/infer/instantiate.rs
--- a/chalk-solve/src/infer/instantiate.rs
+++ b/chalk-solve/src/infer/instantiate.rs
@@ -58,35 +58,33 @@ impl InferenceTable {
}
/// Variant on `instantiate_in` that takes a `Binders<T>`.
- #[allow(non_camel_case_ty... | diff --git /dev/null b/tests/test/existential_types.rs
new file mode 100644
--- /dev/null
+++ b/tests/test/existential_types.rs
@@ -0,0 +1,198 @@
+//! Tests related to the implied bounds rules.
+
+use super::*;
+
+#[test]
+fn dyn_Clone_is_Clone() {
+ test! {
+ program {
+ trait Clone { }
+ }... | unification under binders is broken
The current logic for unifying under binders as broken in two ways. First off, it's specific (rather unnecessarily) to `for<'a>` types, when it should be applicable to any zippable things. Secondly, it only tests one half of the necessary conditions! In fact, we've got a comment to t... | 2019-11-11T22:36:17Z | 0.1 | 2019-11-14T10:30:40Z | 154020e4884e7b9fe41a93a6970cfff78783cdcc | [
"test::existential_types::dyn_Clone_Send_is_Send",
"test::existential_types::dyn_Foo_Bar",
"test::existential_types::dyn_Clone_is_Clone",
"test::existential_types::dyn_binders_reverse",
"test::unify::equality_binder2",
"test::unify::forall_equality",
"test::existential_types::dyn_higher_ranked_type_argu... | [
"lowering::fundamental_multiple_type_parameters",
"lowering::invalid_name",
"lowering::gat_higher_ranked_bound",
"lowering::type_parameter",
"lowering::lower_success",
"lowering::type_parameter_bound",
"test::coherence::multiple_nonoverlapping_impls",
"lowering::upstream_items",
"test::coherence::ge... | [] | [] | auto_2025-06-13 | |
rust-lang/chalk | 237 | rust-lang__chalk-237 | [
"235",
"235"
] | c9314e425e49969c33cabcb8fac7da6eac3c5073 | diff --git a/chalk-solve/src/clauses/program_clauses.rs b/chalk-solve/src/clauses/program_clauses.rs
--- a/chalk-solve/src/clauses/program_clauses.rs
+++ b/chalk-solve/src/clauses/program_clauses.rs
@@ -52,7 +52,7 @@ impl ToProgramClauses for AssociatedTyValue {
///
/// Then for the following impl:
/// `... | diff --git a/src/test.rs b/src/test.rs
--- a/src/test.rs
+++ b/src/test.rs
@@ -549,6 +549,62 @@ fn normalize_basic() {
}
}
+#[test]
+fn normalize_into_iterator() {
+ test! {
+ program {
+ trait IntoIterator { type Item; }
+ trait Iterator { type Item; }
+ struct Vec<T>... | Normalization doesn't take into account which impl actually applied
Split off from #234:
```rust
#[test]
fn normalize_into_iterator() {
test! {
program {
trait IntoIterator { type Item; }
trait Iterator { type Item; }
struct Vec<T> { }
struct u32 { }
... | 2019-09-03T11:54:34Z | 0.1 | 2019-09-03T22:39:44Z | 154020e4884e7b9fe41a93a6970cfff78783cdcc | [
"test::normalize_into_iterator"
] | [
"lowering::test::invalid_name",
"lowering::test::lower_success",
"test::coherence::concrete_impl_and_blanket_impl",
"lowering::test::fundamental_multiple_type_parameters",
"lowering::test::upstream_items",
"lowering::test::not_trait",
"lowering::test::gat_higher_ranked_bound",
"lowering::test::type_pa... | [] | [] | auto_2025-06-13 | |
rust-lang/chalk | 780 | rust-lang__chalk-780 | [
"777"
] | a0e4882f93436fe38a4940ea92c4745121878488 | diff --git a/chalk-solve/src/clauses.rs b/chalk-solve/src/clauses.rs
--- a/chalk-solve/src/clauses.rs
+++ b/chalk-solve/src/clauses.rs
@@ -624,7 +624,10 @@ pub fn program_clauses_that_could_match<I: Interner>(
if let Some(well_known) = trait_datum.well_known {
builtin_traits::add... | diff --git a/tests/test/existential_types.rs b/tests/test/existential_types.rs
--- a/tests/test/existential_types.rs
+++ b/tests/test/existential_types.rs
@@ -406,6 +406,31 @@ fn dyn_associated_type_binding() {
}
}
+#[test]
+fn dyn_assoc_in_super_trait_bounds() {
+ test! {
+ program {
+ tra... | Unable to deduce projection types of dyn types from supertrait bounds
Context: https://github.com/rust-lang/rust-analyzer/issues/13169
It seems chalk is unable to deduce projection type of trait object types when it's not specified in `dyn` notation but the trait has supertrait with its projection type specified.
... | 2022-10-21T08:27:01Z | 7.1 | 2023-06-13T17:06:29Z | a0e4882f93436fe38a4940ea92c4745121878488 | [
"test::existential_types::dyn_assoc_in_super_trait_bounds",
"test::opaque_types::opaque_assoc_in_super_trait_bounds",
"test::projection::projection_from_super_trait_bounds"
] | [
"display::built_ins::test_empty_tuple",
"display::assoc_ty::test_impl_assoc_ty",
"display::assoc_ty::test_assoc_type_bounds",
"display::built_ins::test_array_types",
"display::assoc_ty::test_simple_assoc_type",
"display::assoc_ty::test_assoc_type_in_generic_trait",
"display::assoc_ty::test_assoc_type_wh... | [] | [] | auto_2025-06-13 | |
rust-lang/chalk | 755 | rust-lang__chalk-755 | [
"734"
] | f470f2f493203f58d493c7221863bca2ce1a6dad | diff --git a/chalk-solve/src/clauses.rs b/chalk-solve/src/clauses.rs
--- a/chalk-solve/src/clauses.rs
+++ b/chalk-solve/src/clauses.rs
@@ -161,14 +161,16 @@ pub fn push_auto_trait_impls<I: Interner>(
TyKind::Foreign(_) => Ok(()),
// closures require binders, while the other types do not
- TyK... | diff --git a/tests/test/closures.rs b/tests/test/closures.rs
--- a/tests/test/closures.rs
+++ b/tests/test/closures.rs
@@ -280,3 +280,35 @@ fn closure_implements_fn_traits() {
}
}
}
+
+#[test]
+fn closures_propagate_auto_traits() {
+ test! {
+ program {
+ #[auto]
+ trait S... | Auto traits are not handled for generic closures
The following test fails with both solvers (returning ambiguous).
```rust
program {
#[auto]
trait Send { }
closure with_ty<T>(self,) { T }
}
goal {
forall<T> { if (T: Send) { with_ty<T>: Send } }
} yields {
"Unique"
}
```
The empty substs... | I'm interested in learning more about chalk, so I'll @rustbot claim. | 2022-03-12T14:17:16Z | 7.1 | 2022-07-28T21:05:13Z | a0e4882f93436fe38a4940ea92c4745121878488 | [
"test::closures::closures_propagate_auto_traits"
] | [
"display::assoc_ty::test_simple_assoc_type",
"display::assoc_ty::test_assoc_type_and_trait_generics_coexist",
"display::assoc_ty::test_simple_generic_assoc_type_with_where_clause",
"display::built_ins::test_empty_tuple",
"display::assoc_ty::test_assoc_type_bounds",
"display::assoc_ty::test_simple_generic_... | [] | [] | auto_2025-06-13 |
rust-lang/chalk | 392 | rust-lang__chalk-392 | [
"306"
] | 154020e4884e7b9fe41a93a6970cfff78783cdcc | diff --git a/chalk-solve/src/solve/slg.rs b/chalk-solve/src/solve/slg.rs
--- a/chalk-solve/src/solve/slg.rs
+++ b/chalk-solve/src/solve/slg.rs
@@ -348,9 +348,7 @@ impl<I: Interner> TruncatingInferenceTable<I> {
impl<I: Interner> context::TruncateOps<SlgContext<I>> for TruncatingInferenceTable<I> {
fn goal_needs... | diff --git a/tests/test/projection.rs b/tests/test/projection.rs
--- a/tests/test/projection.rs
+++ b/tests/test/projection.rs
@@ -712,8 +712,8 @@ fn rust_analyzer_regression() {
PI: ParallelIterator
}
}
- } yields_all[SolverChoice::slg(4, None)] {
- ... | deferred: can we / should we truncate the environment, and how to avoid loops?
In https://github.com/rust-lang/chalk/pull/294, we opted to stop truncating the environment. The problem was due to an infinite loop that arose in some rust-analyzer cases. The scenario [was described on Zulip](https://rust-lang.zulipchat.co... | Thinking more about this, now that truncation in general just leads to `Floundering`, we should also just check if the `Environment` is too large. I think this question is still *valid* if we ever add truncation back in, but I'm not sure it should be an open issue, rather than just a note when `Environment` truncation ... | 2020-04-13T14:38:34Z | 0.1 | 2020-04-14T19:19:57Z | 154020e4884e7b9fe41a93a6970cfff78783cdcc | [
"test::projection::rust_analyzer_regression"
] | [
"lowering::invalid_name",
"lowering::not_trait",
"lowering::gat_higher_ranked_bound",
"lowering::lower_success",
"test::coherence::overlapping_negative_positive_impls",
"test::coherence::two_impls_for_same_type",
"lowering::upstream_items",
"lowering::fundamental_multiple_type_parameters",
"lowering... | [] | [] | auto_2025-06-13 |
atuinsh/atuin | 747 | atuinsh__atuin-747 | [
"745"
] | d46e3ad47d03e53232269973806fb9da2248ba19 | diff --git a/atuin-client/src/import/bash.rs b/atuin-client/src/import/bash.rs
--- a/atuin-client/src/import/bash.rs
+++ b/atuin-client/src/import/bash.rs
@@ -1,8 +1,10 @@
-use std::{fs::File, io::Read, path::PathBuf};
+use std::{fs::File, io::Read, path::PathBuf, str};
use async_trait::async_trait;
+use chrono::{Da... | diff --git a/atuin-client/src/import/bash.rs b/atuin-client/src/import/bash.rs
--- a/atuin-client/src/import/bash.rs
+++ b/atuin-client/src/import/bash.rs
@@ -70,18 +89,47 @@ impl Importer for Bash {
}
}
+#[derive(Debug, Clone)]
+enum LineType<'a> {
+ NotUtf8,
+ /// A timestamp line start with a '#', foll... | Bash history import issues
I spotted two issues while trying to import my Bash history:
1. Import ordering is incorrectly reversed.
2. `.bash_history` can be configured to store timestamps, a case not handled.
---
## Ordering
In the following snippet, lines from the top of the file will receive the newest ... | 2023-03-01T16:30:56Z | 13.0 | 2023-04-05T15:22:17Z | edcd477153d00944c5dae16ec3ba69e339e1450c | [
"encryption::test::test_encrypt_decrypt",
"import::zsh::test::test_parse_extended_simple",
"import::zsh::test::test_parse_file",
"import::fish::test::parse_complex",
"import::zsh_histdb::test::test_env_vars",
"import::zsh_histdb::test::test_import",
"database::test::test_search_prefix",
"database::tes... | [] | [] | [] | auto_2025-06-06 | |
atuinsh/atuin | 1,238 | atuinsh__atuin-1238 | [
"691"
] | 15abf429842969e56598b1922a21693a7253f117 | diff --git a/atuin-client/src/api_client.rs b/atuin-client/src/api_client.rs
--- a/atuin-client/src/api_client.rs
+++ b/atuin-client/src/api_client.rs
@@ -1,5 +1,6 @@
use std::collections::HashMap;
use std::env;
+use std::time::Duration;
use eyre::{bail, Result};
use reqwest::{
diff --git a/atuin-client/src/api_c... | diff --git a/atuin-client/src/api_client.rs b/atuin-client/src/api_client.rs
--- a/atuin-client/src/api_client.rs
+++ b/atuin-client/src/api_client.rs
@@ -106,7 +107,12 @@ pub async fn latest_version() -> Result<Version> {
}
impl<'a> Client<'a> {
- pub fn new(sync_addr: &'a str, session_token: &'a str) -> Result... | atuin hangs at first start in bad network environments
This issue can be reproduced with the following preconditions:
- a really (as in awfully) bad network environment with a rather large-ish (>=98%) packet loss rate
- using atuin to browse the history the first time after boot
Atuin hangs for an indefinite amo... | Thanks for the report. I reckon I can rewrite this part to get the version lazily
https://user-images.githubusercontent.com/6625462/216926816-fd536a1c-8f35-4a89-b097-8224638960bd.mov
There we go :)
This issue is sort of fixed but there's a related problem. There were 2 issues here:
1. Atuin _was_ blocking on that... | 2023-09-17T17:26:20Z | 16.0 | 2023-09-18T07:39:20Z | 1735be05d71ec21ffb8648866fca83e210cfe31a | [
"encryption::test::test_decode_old",
"encryption::test::test_decode",
"encryption::test::key_encodings",
"encryption::test::test_decode_deleted",
"encryption::test::test_encrypt_decrypt",
"kv::tests::encode_decode",
"import::zsh::test::test_parse_extended_simple",
"import::bash::test::parse_with_parti... | [] | [] | [] | auto_2025-06-06 |
atuinsh/atuin | 2,058 | atuinsh__atuin-2058 | [
"1882"
] | 4d74e38a515bc14381e1342afdf5ee2ec345f589 | diff --git a/crates/atuin-history/src/stats.rs b/crates/atuin-history/src/stats.rs
--- a/crates/atuin-history/src/stats.rs
+++ b/crates/atuin-history/src/stats.rs
@@ -92,7 +92,7 @@ fn split_at_pipe(command: &str) -> Vec<&str> {
"\\" => if graphemes.next().is_some() {},
"|" => {
... | diff --git a/crates/atuin-history/src/stats.rs b/crates/atuin-history/src/stats.rs
--- a/crates/atuin-history/src/stats.rs
+++ b/crates/atuin-history/src/stats.rs
@@ -396,4 +396,20 @@ mod tests {
["git commit -m \"🚀\""]
);
}
+
+ #[test]
+ fn starts_with_pipe() {
+ assert_eq!(
+ ... | [Bug]: atuin stats panics when faced with unusual string in history
### What did you expect to happen?
No panic! ;]
### What happened?
When running `atuin stats` it panics with:
```
❯ RUST_BACKTRACE=1 atuin stats
thread 'main' panicked at atuin/src/command/client/stats.rs:56:41:
begin <= end (1 <= 0) when slic... | seconding this- here's another fun string this happens with.
```console
$ RUST_BACKTRACE=1 atuin stats
thread 'main' panicked at atuin/src/command/client/stats.rs:56:41:
begin <= end (1 <= 0) when slicing `|_| |____||___||_| |_| |___||_|_`
stack backtrace:
0: 0x1054a29d0 - <std::sys_common::backtrace... | 2024-05-30T14:26:22Z | 18.2 | 2024-05-30T14:58:06Z | 4d74e38a515bc14381e1342afdf5ee2ec345f589 | [
"stats::tests::starts_with_pipe"
] | [
"stats::tests::escaped_pipes",
"stats::tests::interesting_commands_spaces",
"stats::tests::split_multi_quoted",
"stats::tests::starts_with_spaces_and_pipe",
"stats::tests::interesting_commands",
"stats::tests::split_simple_quoted",
"stats::tests::split_multi",
"stats::tests::split_simple",
"stats::t... | [] | [] | auto_2025-06-06 |
atuinsh/atuin | 1,739 | atuinsh__atuin-1739 | [
"1054"
] | 2a65f89cd54b8b8187240a1fdc288867b35f6b01 | diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -217,6 +217,7 @@ dependencies = [
"tracing",
"tracing-subscriber",
"tracing-tree",
+ "unicode-segmentation",
"unicode-width",
"uuid",
"whoami",
diff --git a/Cargo.lock b/Cargo.lock
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -3937,9 +3938,9 ... | diff --git a/atuin/src/command/client/stats.rs b/atuin/src/command/client/stats.rs
--- a/atuin/src/command/client/stats.rs
+++ b/atuin/src/command/client/stats.rs
@@ -189,7 +266,7 @@ mod tests {
use time::OffsetDateTime;
use super::compute_stats;
- use super::interesting_command;
+ use super::{interes... | Enable multiple command stats to be shown
These changes extend the `stats` subcommand with an `--ngram-size` argument, which supports providing statistics for combinations of commands. I have found this useful for identifying the most common combinations of commands as candidates for further automation.
| 2024-02-20T05:51:10Z | 18.0 | 2024-02-27T19:41:41Z | 2a65f89cd54b8b8187240a1fdc288867b35f6b01 | [
"command::client::search::cursor::cursor_tests::back",
"command::client::search::cursor::cursor_tests::left",
"command::client::search::cursor::cursor_tests::pop",
"command::client::stats::tests::interesting_commands",
"command::client::search::cursor::cursor_tests::test_emacs_get_prev_word_pos",
"command... | [] | [] | [] | auto_2025-06-06 | |
atuinsh/atuin | 1,722 | atuinsh__atuin-1722 | [
"1714"
] | 063d9054d74c0c44781507eed27378415ab9fef5 | diff --git a/atuin-client/config.toml b/atuin-client/config.toml
--- a/atuin-client/config.toml
+++ b/atuin-client/config.toml
@@ -171,3 +171,6 @@ enter_accept = true
## Set commands that should be totally stripped and ignored from stats
#common_prefix = ["sudo"]
+
+## Set commands that will be completely ignored f... | diff --git a/atuin/src/command/client/stats.rs b/atuin/src/command/client/stats.rs
--- a/atuin/src/command/client/stats.rs
+++ b/atuin/src/command/client/stats.rs
@@ -176,10 +184,36 @@ fn interesting_command<'a>(settings: &Settings, mut command: &'a str) -> &'a str
#[cfg(test)]
mod tests {
+ use atuin_client::hi... | `ignore_commands` option for stats
Would you be open to having an `ignore_commands` option for `atuin stats`? `cd`, `ls`, and `vi` are my three top commands by nearly an order of and I don't find this particularly informative; I'd be interested in filtering these out entirely from my stats.
If you're interested in... | I'd be interested!
Otherwise, you can see more commands with the -c arg, if you find them a waste of space
eg
`atuin stats -c 100` will show the top 100, rather than top 10
OK I will see how hard this is and take a stab at a PR.
The issue is not so much a waste of space, but that it makes the histogram kin... | 2024-02-14T17:42:21Z | 18.0 | 2024-02-15T18:52:19Z | 2a65f89cd54b8b8187240a1fdc288867b35f6b01 | [
"command::client::search::cursor::cursor_tests::test_emacs_get_next_word_pos",
"command::client::search::cursor::cursor_tests::test_subl_get_prev_word_pos",
"command::client::search::cursor::cursor_tests::right",
"command::client::search::cursor::cursor_tests::pop",
"command::client::search::cursor::cursor_... | [] | [] | [] | auto_2025-06-06 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.