test: data_explorer::format::tests::test_truncation failed on Japanese characters
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 337
- Forks
- 32
- Avg merge
- 8d 17h
- Merged PRs (30d)
- 11
Description
I found the following test case failed in the ark crate while I'm trying to create a nix package for ark 0.1.220
running 1 test
test data_explorer::format::tests::test_truncation ... FAILED
failures:
failures:
data_explorer::format::tests::test_truncation
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 402 filtered out; finished in 0.47s
stderr ---
thread 'data_explorer::format::tests::test_truncation' (9048) panicked at crates/ark/src/data_explorer/format.rs:776:13:
assertion `left == right` failed
left: [FormattedValue("<U+")]
right: [FormattedValue("ボルテ")]
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
The test case resulting in this error are related to Japanese characters trimming as described here:
Cargo nextest argument:
--target x86_64-unknown-linux-gnu --offline -j 16 --cargo-profile release --
Package versions:
rustc 1.91.1 (ed61e7d7e 2025-11-07) (built from a source tarball)
cargo 1.91.0 (ea2d97820 2025-10-10)
cargo-nextest 0.9.114
release: 0.9.114
My system info:
OS: NixOS 26.05 (Yarara) x86_64
Host: 83E3 (Yoga Pro 7 14AHP9)
Kernel: Linux 6.12.60
CPU: AMD Ryzen 7 8845HS (16) @ 5.14 GHz
GPU 1: NVIDIA GeForce RTX 3050 6GB Laptop GPU [Discrete]
GPU 2: AMD Radeon 780M Graphics [Integrated]
Locale: en_US.UTF-8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with crates/ark/src/data_explorer/format.rs around the test_truncation test at lines 774-778. Reproduce the failure with the reported cargo nextest arguments and inspect the truncation behavior for Japanese characters. Done means the test passes with the expected Japanese output and existing truncation tests remain passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100