-
Part of #327.
# Improvement
## Currently
All diagnostics rely on users clicking an inline text link to fix the issue we're reporting to them.
## Supporting Information
Example:
### Bef…
-
**Describe the bug**
When using the diagnostics UI for emissary-ingress it calls the stats endpoint which is responsible for parsing out the Envoy provided metrics and matching them to the correct cl…
-
# EventSource
According to [eventsource-getting-started](https://learn.microsoft.com/en-us/dotnet/core/diagnostics/eventsource-getting-started)
Eventone must call like `WriteEvent` or `WriteEve…
-
### I confirm that...
- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq),…
-
This is most likely a long-term improvement, and the boundaries of what should and should not be flagged are relatively blurred.
![image](https://github.com/LuqueDaniel/vscode-language-renpy/assets/4…
-
Currently, [summary](https://github.com/pyro-ppl/numpyro/blob/master/numpyro/diagnostics.py#L219) returns ordinary statistics mean/var/quantiles/n_eff for MCMC samples. It would be nice to extend that…
-
I think this documentation (https://tokio.rs/tokio/topics/tracing) describes what needs to be done here
- [x] research good practices for structured logging in rust
- [x] implement those in ruuste…
-
```haxe
function test(?x:String, ?e:haxe.macro.Expr.ExprDef) {}
function main() {
test(EBreak);
}
```
This complains about `Unknown identifier : EBreak`. Should be very similar to #10633.
-
It would be a bit more readable if file paths in the diagnostics window where relative to the workspace. I think this should be possible, either by doing some magic in the Win or setting the base path…
-
- [x] Migrate LightObserver to shared-ui
- [x] Teach TopGraphObserver about full diagnostics (not just `top`)
- [x] Integrate TopGraphObserver to Visual Editor
- [x] Teach editor about TopGraphObse…