microsoft / microsoft/multilspy

request_definition is empty for java

Open
#43 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
610
Forks
111
PR merge metrics
No merged PRs in 30d

Description

I took the repo in tests for java (clickhouse-highlevel-sinker) and cloned it locally and tested it. result is empty. Any reason so ?

import asyncio
from multilspy import SyncLanguageServer, LanguageServer
from multilspy.multilspy_config import MultilspyConfig
from multilspy.multilspy_logger import MultilspyLogger
from pathlib import PurePath

async def main():
    config = MultilspyConfig.from_dict({"code_language": "java"}) 
    logger = MultilspyLogger()
    lsp = LanguageServer.create(config, logger, "/home/saiteja/testing_repos/clickhouse-highlevel-sinker")
    
    async with lsp.start_server():
        result = await lsp.request_definition(
            str(PurePath("/home/saiteja/testing_repos/clickhouse-highlevel-sinker/src/main/java/com/xlvchao/clickhouse/component/ClickHouseSinkManager.java")),
            44,  # Line number of the symbol
            59   # Column number of the symbol
        )
    
        print("result", result)

if __name__ == "__main__":
    asyncio.run(main())

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.

Research direction

Reproduce the Java case using the provided clickhouse-highlevel-sinker path and the request_definition call in the issue. Start by checking the Java language-server configuration and the specified file, line, and column, then compare the returned result with the expected definition response. Done means the cause is identified and request_definition returns the correct definition or the limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, python
Domain
devtools, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.