Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider having `showMessage` et al be associated with a request id

See original GitHub issue

LSP has a showMessage notification, as well as others that serve a similar purpose, to notify the clients (editors) about what’s happening in the server.

BSP builds upon this infrastructure, but there is a key difference between BSP and LSP in terms of requirements: BSP needs to handle parallel requests, while LSP doesn’t.

This means that when clients (in our case, IDEs, editors and users) want to run tests of different modules in parallel (or similar tasks that require parallel execution) there is no way to know which request trigger certain logs.

We need to figure out what to do to allow clients to separate logs coming from different requests. Should we add another showMessage notification that is associated with a request id?

This question came up when thinking about the Intellij integration with @jastice.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

jasticecommented, Feb 27, 2018

builds and tests may merit special support, but in the case of generic tasks with unspecified semantics, the same considerations can apply.

For instance I could create a deploy task for my project that uploads binaries to several target servers in parallel, and I would like to get a updates on which of these have started, completed successfully, with error, etc.

This is a bit academic since I don’t think most build tools support this kind of structured logging in their APIs, but this lack has been one of my favorite pain points for a long time.

olafurpgcommented, Feb 27, 2018

To clarify, I think it’s a better idea to introduce custom notification messages to report test/build progress instead of extending showMessage.

Related, there is a related LSP ticket on “Add support to report progress for a running request” I think it would make sense to draw inspiration from there.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Methods for De-identification of PHI -
This page provides guidance about methods and approaches to achieve de-identification in accordance with the Health Insurance Portability and Accountability ...
Read more >
eRA Commons Frequently Asked Questions
What are the options for obtaining an eRA Commons username (Commons ID) for a senior/key person who isn't affiliated with a registered ...
Read more >
ID Token and Access Token: What Is the Difference? - Auth0
An ID token is an artifact that proves that the user has been authenticated. It was introduced by OpenID Connect (OIDC), an open...
Read more >
Questions and Answers for School Districts and Parents
A - 4. No. Even where a district has valid proof of residency requirements, it must exempt from those requirements all children and...
Read more >
Legal - iCloud - Apple
The participants in the Shared Library all have access to the Shared ... location of the device back to the Apple ID associated...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found