Repository navigation
Conversation
get_parsons_help replaced every "\n" in the student code, the test code and the example with a real newline, left over from when these arrived escaped. Callers now pass real text, so the replace broke any string literal containing \n -- e.g. a CSAwesome test's String expect = "5\n10\n10" no longer compiled, every generated fix failed its tests, and CodeTailor silently fell back to the example solution. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
get_parsons_helpran.replace("\\n", "\n")on the student code, the test code and the backup example. Callers now pass real text, so this turned every\nescape inside a string literal into an actual line break. A CSAwesome test withString expect = "5\n10\n10";then fails to compile (RunestoneTests.java:18: error: unclosed string literal), every generated fix "fails" its tests, and CodeTailor silently falls back to the example solution.This affects any CodeTailor question whose tests, student code or example contain
\nin a string, which is common in CSAwesome tests (e.g. expected output"Bill\nDot\n"), and Python tests too.Found while piloting new Unit 3 CSAwesome problems: 4 of 5 fell back to
example_solutioneven though the LLM's fixed code passed the tests when run on JOBE directly. With this change all 5 returnAI_personalized. The problem description still gets the replace; only the code fields change.🤖 Generated with Claude Code