Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

evaluate: Error result is truncated

Open
#343 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
devtools

Research direction

Start by tracing the evaluate request's error handling and the formatting that produces the truncated "format" value shown in the issue. Confirm how longer evaluation failures are shortened, then verify that the response exposes the full error message without losing the existing error context.

Written by the indexing model from the issue text.

Description

ai-triaged needs more info question

When an evaluate request fails due to an error in the code being evaluated, the language server reports an unhelpful truncated message:

{
  "id": 1010,
  "format": "Cannot evaluate because of org.eclipse.debug.core.DebugException: com.sun.jdi.InvocationException occurred invoking method.."
}

Sometimes this is long enough to be useful, but for errors with longer stack traces, it's often not clear what the error actually was. Is there any way to always get the full error message?

Dominant language
Java
Stars
409
Forks
204
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/java-debug

All issues in microsoft/java-debug

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.