Better OTel and use Pull Diagnostics for tests#1341
Better OTel and use Pull Diagnostics for tests#1341TheAngryByrd wants to merge 3 commits intoionide:mainfrom
Conversation
| jaeger: | ||
| profiles: | ||
| - jaeger | ||
| image: jaegertracing/all-in-one |
There was a problem hiding this comment.
OMG travesty - not using the Aspire Dashboard? 😱
|
|
||
| let! (server, events) = serverInitialize path analyzerEnabledConfig state | ||
| let scriptPath = Path.Combine(path, "Script.fsx") | ||
| do! Async.Sleep(TimeSpan.FromSeconds 5.) |
There was a problem hiding this comment.
ooh it's very promising to remove the random sleeps
TheAngryByrd
force-pushed
the
better-otel-tests
branch
from
6d3a406 to
a37da74
Compare
|
🤖 This is an automated response from Repo Assist. Hi @TheAngryByrd! This draft PR ("Better OTel and use Pull Diagnostics for tests") has been quiet since December 2025 — just checking in to see if it's still in progress. Better OTel tracing and pull-based diagnostics for tests would be a great improvement. If you'd like to continue it, need a review of the current state, or would like help rebasing against If the approach has changed or there are blockers, it'd be helpful to know so maintainers can plan accordingly. Thanks for all the work you've put in here! 🙂
|
2 participants
No description provided.