Key error

[robmck1995]

Description

• Improved error handling by checking for KeyError and returning an empty array to prevent crashes.
• Added logging to capture detailed error information when an error is received.
• Cloned the error object to prevent borrowing issues, ensuring smoother error processing.

---

Changes walkthrough

	Relevant files
Bug fix	client.rs Improve error handling and logging in LSP client                              lsproxy/src/lsp/client.rs Added logging for received errors. Implemented handling for KeyError by returning an empty array. Cloned the error object to avoid borrowing issues. +5/-1

💡 Usage Guide

### Checking Your Pull Request Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. ### Talking to CodeAnt AI Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ### Retrigger review Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

### Check Your Repository Health To analyze the health of your code repository, visit our dashboard at [app.codeant.ai](https://app.codeant.ai). This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai[bot]]

Things to consider 🐛

• The line 115 returns an empty JSON array when the error message starts with "KeyError". This handling might not be appropriate for all cases where a "KeyError" occurs. It assumes that an empty array is a valid response, which might not be the case depending on the context of the API or function call. This could lead to unexpected behavior or bugs if the caller expects a different kind of response or error handling.