vsx-registry: add hint to fetching extensions error

[SamuelBergSTM]

What it does

When browsing the VSX registry while having network configuration issues (e.g. proxy issues), the error message is a bit vague. E.g:
"Error fetching extensions. getaddrinfo ENOTFOUND open-vsx.org"

This PR addresses the issue by changing the user message to the following:
"Error fetching extensions. getaddrinfo ENOTFOUND open-vsx.org This could be caused by network configuration issues."

Clarifies the error by suggesting it could be caused by network configuration issues.

Contributed by STMicroelectronics
Signed-off-by: Samuel BERG [email protected]

How to test

1. Produce a network issue. E.g. adding the line "127.0.0.1 open-vsx.org" to C:\Windows\System32\drivers\etc\hosts (Windows) / /etc/hosts (Linux).
2. Launch a Theia application.
   Option A: Launch a Theia example with an invalid ovsx-router-config path (e.g. --ovsx-router-config=invalid-path) to exclude the local mock VSX registry.
   Option B: Launch Theia Blueprint as-is.
3. Open the Extensions view.
4. Enter a search term (e.g. "C++").
5. Ensure that the error message is the following:
   "Error fetching extensions. {ERROR} {IP_ADDRESS} This could be caused by network configuration issues."

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[msujew]

Looks quite good to me. @vince-fugnitto your opinion?

[vince-fugnitto]

Looks quite good to me. @vince-fugnitto your opinion?

Seems fine to me as well, there will be a trailing whitespace in the header if the error is not ENOTFOUND but it should be fine.

[msujew]

Alright, I'd be fine with merging this then. @SamuelBergSTM do you mind updating the changelog to correctly reflect this change? I'll merge this afterwards.

[SamuelBergSTM]

Alright, I'd be fine with merging this then. @SamuelBergSTM do you mind updating the changelog to correctly reflect this change? I'll merge this afterwards.

I can update the changelog message, yes.
I will also rebase since there are now conflicts in the changelog.

[msujew]

@SamuelBergSTM You've added the changelog entry to 1.41 which was released last month. Please update it to 1.42.

[SamuelBergSTM]

@SamuelBergSTM You've added the changelog entry to 1.41 which was released last month. Please update it to 1.42.

@msujew Good catch. I overlooked this. I created a new v1.42.0 heading and placed the entry there. Does this look OK?