Skip to content

Conversation

ZeWaka
Copy link
Collaborator

@ZeWaka ZeWaka commented Aug 2, 2025

No description provided.

@ZeWaka
Copy link
Collaborator Author

ZeWaka commented Aug 2, 2025

dog is this some fucking non printing control characters or some crap

@itsmeow
Copy link
Contributor

itsmeow commented Aug 6, 2025

actually what

@ZephyrTFA
Copy link
Contributor

Screenshot_20250827_190724_Chrome.jpg

@ZephyrTFA
Copy link
Contributor

I dunno

@optimumtact
Copy link
Member

Whitespace or Encoding Differences: There may be invisible differences (e.g., whitespace, newline, UTF-8 BOM).
Type Differences: One value may be a boolean (true) and the other an integer (1). However, in your output both are 1.
Test Assertion Logic: The test may be using a strict comparison (e.g., string equality), which can fail for reasons above.

How to Debug

Add Debug Output: Print the raw bytes or use a hex dump of both strings in your test to spot differences.
Compare as Data Structures: Instead of comparing JSON strings, parse them into objects and compare those.
Check Test Assertion: Review the assertion code at or around tests/dm-tests.rs:188 for how the comparison is performed.

Recommendation

Inspect the test logic and add logging to print the exact bytes being compared.
If possible, switch the test to compare deserialized structures instead of raw JSON strings.
(Optional) Use a JSON diff tool to check for hidden differences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants