Expand list of common pitfalls

mdh1418 · mdh1418 · commit 59fb983a47e3 · 2024-10-25T13:10:33.000-04:00
diff --git a/docs/core/diagnostics/eventsource-collect-and-view-traces.md b/docs/core/diagnostics/eventsource-collect-and-view-traces.md
@@ -274,7 +274,7 @@ this isn't required. Following is an example `EventListener` implementation that
    ```
 
 > [!WARNING]
-> Potential Deadlocks with EventSource Callbacks
+> Potential Pitfalls when implementing EventSource Callbacks via EventListener include deadlocks, infinite recursions, and uninitialized types.
 >
 > When implementing EventSources, be cautious with invoking lock-acquiring APIs within EventSource callbacks. EventSource instances are initialized early in the runtime, before some core features are fully initialized. As a result, the re-entrant behavior of EventSource callbacks may cause deadlocks if the callback attempts to acquire locks already held by the thread that triggered the callback.
 >

Original file line number	Diff line number	Diff line change
@@ -274,7 +274,7 @@ this isn't required. Following is an example `EventListener` implementation that
`274`	`274`	```
`275`	`275`
`276`	`276`	`> [!WARNING]`
`277`		`-> Potential Deadlocks with EventSource Callbacks`
	`277`	`+> Potential Pitfalls when implementing EventSource Callbacks via EventListener include deadlocks, infinite recursions, and uninitialized types.`
`278`	`278`	`>`
`279`	`279`	`> When implementing EventSources, be cautious with invoking lock-acquiring APIs within EventSource callbacks. EventSource instances are initialized early in the runtime, before some core features are fully initialized. As a result, the re-entrant behavior of EventSource callbacks may cause deadlocks if the callback attempts to acquire locks already held by the thread that triggered the callback.`
`280`	`280`	`>`