Fixed truncation message test failuresPublic

Agent

Model

Claude Opus 4.5 (latest)

Started

Jan 25, 6:05 PM

Messages92

Downloads0

Summary

Closed, Completed

Understand
Investigated test failures and read tool behavior.
Understand
Understand
Reviewed truncation utility and git history.
Understand
Edit
Fixed regex in test expectations to match actual output.
Edit
Verify
Ran tests and full test suite to confirm fix.
Verify
Cleanup
Committed and pushed test fixes.
Cleanup

https://github.com/badlogic/pi-mono/actions/runs/21336434027 build fails, figure out why

The build is failing due to 4 test failures in packages/coding-agent/test/tools.test.ts. The tests are expecting truncation messages in the read tool output, but the read tool is returning raw content without the truncation hints. Let me look at the test file and the read tool implementation:

Let me find the read tool:

Now let me check the truncate utility to understand how truncation works:

Now I understand the issue. The tests expect truncation messages, but when looking at the read.ts code more closely, the condition for no truncation seems correct. Let me check if there was a recent change that broke this by looking at git history:

The recent commit added trailing periods to the messages, but the test expectations should have been updated. Let me check the test more closely:

I see. The tests expect the messages without the trailing period (. at the end), but the code was updated to include them. Let me look at the test expectations more closely:

The failures are:

should truncate files exceeding line limit - expects Use offset=2001 to continue] (no period)
should truncate when byte limit exceeded - expects Use offset=\d+ to continue] (the regex does have the period, so this one might be failing for another reason)
should handle limit parameter - expects Use offset=11 to continue] (no period)
should handle offset + limit together - expects Use offset=61 to continue] (no period)

Wait, looking at the git diff again, the recent commit 89636cfe added the trailing periods to the messages. But the tests didn't get updated. However, looking at the CI output:

This suggests the output doesn't contain ANY truncation message at all, not just a period mismatch. The file is returning all content without truncation. This is strange.

Let me run the test locally to see what's happening:

So the test is returning ALL lines (Line 1 through Line N) without any truncation. The truncation is not happening at all. Let me write a minimal test to debug this:

Good, the truncation function works correctly. The issue must be in how the read tool is using it. Let me check if the test is importing the right tool or something else is going on:

Interesting! When I run this with the correct cwd handling via the dist file, it works. The issue is that the test imports readTool directly, which is created with process.cwd() at module load time. Let me check:

I see. The readTool is using process.cwd(). The test is passing absolute paths, so this should work. Wait, let me look at the test more carefully again:

The test is passing an absolute path (testFile) to readTool.execute. Since it's an absolute path, it should work regardless of cwd.

Let me check if there's something different in the import. The test imports from ../src/core/tools/read.js (TypeScript source), not from dist. Let me check if the code runs properly from source:

There are build errors in the project. This is unrelated to the test failure though since the test doesn't depend on those specific files.

Let me check if vitest is using the built dist files or the source files:

Let me check the issue more carefully by looking at an actual run with debug:

Now I can see it clearly! The output does include the message [Showing lines 1-2000 of 2500. Use offset=2001 to continue.] (with a trailing period), but the test expects:

(without the period at the end)

This is the mismatch: the code was updated to add the period in commit 89636cfe, but the tests weren't updated.

The fix is to update the test expectations to include the trailing period. Let me fix the 4 failing tests:

Now I can see all the tests. I need to fix 4 tests by adding the trailing period:

Line 69: [Showing lines 1-2000 of 2500. Use offset=2001 to continue] → add . at end
Line 81: Already uses regex that includes the period, so it should pass
Line 108: [90 more lines in file. Use offset=11 to continue] → add . at end
Line 123: [40 more lines in file. Use offset=61 to continue] → add . at end

Now let me run the tests to verify the fix:

There's one more test failing. Looking at the output, the actual message is:

But the regex expects:

The issue is that the regex is missing the trailing . before the closing bracket. Let me check the test:

I see. The regex currently ends with to continue\] but the actual output ends with to continue.] (with a period before the ]). Let me fix the regex:

All tests pass now. Let me run the full test suite for the coding-agent package to make sure nothing else broke:

looks good commit and push,

Done. The fix updated 4 test expectations in packages/coding-agent/test/tools.test.ts to include the trailing period that was added to the read tool truncation messages in commit 89636cfe.