DioxusLabs/dioxus · warning
1 issue found.
Error message
1 issue found.
What it means
dx check lints every .rs file of the crate (respecting .gitignore, skipping target/) for RSX issues and prints each non-empty issue report via tracing::info before summarizing. If the summed issue count is exactly one, the command returns Err(anyhow!("1 issue found.")), so the process exits non-zero while the concrete details were already printed above this line.
Source
Thrown at packages/cli/src/cli/check.rs:121
.into_iter()
.flatten()
.flatten()
.collect::<Vec<_>>();
let total_issues = issue_reports.iter().map(|r| r.issues.len()).sum::<usize>();
for report in issue_reports.into_iter() {
if !report.issues.is_empty() {
tracing::info!("{}", report);
}
}
match total_issues {
0 => {
tracing::info!("No issues found.");
Ok(())
}
1 => Err(anyhow!("1 issue found.")),
_ => Err(anyhow!("{total_issues} issues found.")),
}
}
pub(crate) fn collect_rs_files(folder: &Path, files: &mut Vec<PathBuf>) {
for entry in ignore::Walk::new(folder).flatten() {
if entry.path().extension() == Some("rs".as_ref()) {
files.push(entry.path().to_path_buf());
}
}
}
View on GitHub (pinned to 393d190a80)
Solutions
- Scroll up in the output: the specific file, span, and issue are printed before the summary
- Re-run on a single file with dx check --file src/foo.rs to isolate the one issue
- Fix the reported RSX issue and re-run until 'No issues found.' appears
Defensive patterns
Strategy: validation
Validate before calling
# Isolate the file before the project-wide run dx check --file src/recently_edited.rs
Prevention
- Run dx check locally before pushing so CI never sees the aggregate failure
- Read the printed per-file reports above the '1 issue found.' line — the summary carries no details
- Check recently edited files first with --file to keep signal high
When it happens
Trigger: Running dx check (whole project) or dx check --file path.rs on code whose RSX contains exactly one lint issue; the aggregate '1 issue found.' error is returned after the per-file reports are printed.
Common situations: Adding dx check to CI and hitting a single legacy-RSX warning; converting a project where only one file still uses an outdated RSX idiom.
Related errors
- Syntax Error in line {line} column {column}: {err}
- Package type '{invalid:?}' is not supported for bundle forma
- Component '{}' not found in registry
- Couldn't retrieve cargo metadata: {:?}
- failed to parse toml at {}: {}
AI-assisted analysis of DioxusLabs/dioxus@393d190a80 (2026-08-16).
Data as JSON: /api/errors/69b45b6a285d3982.
Report an issue: GitHub.