DioxusLabs/dioxus · error

1 issue found.

Error message

1 issue found.

What it means

Sentinel exit-code error from check_files_and_report: the diagnostics themselves were already logged via tracing::info; this Err is deliberately returned when total_issues == 1 so the `dx check` command exits nonzero. It signals 'check found a problem', not a crash — there is nothing to recover from.

Solutions

1. dx check found an issue. Read the printed issue and fix it in the reported file.

When it happens

Trigger: Thrown at packages/cli/src/cli/check.rs:121 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23). Data as JSON: /api/errors/69b45b6a285d3982. Report an issue: GitHub.

Appendix: 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 24f6a829df)