-
When using the System.Diagnostics.Tracing EventSource, EventListener and EventCounter classes, it would appear that the fired EventCounter events are not being filtered through the EventSource to the …
-
### Is there an existing issue for the same bug?
- [X] I have checked the existing issues.
### Describe the bug and reproduction steps
`/openhands/events/action/message.py` -> `__str__` outpu…
-
If I use the native EventSource, I can see messages coming through with the type and data listed, however if I use eventsource-polyfill, I don't see this information.
-
We should consider making #452 an opt-in feature in v3.
I've seen backend developers create a POST endpoint for SSE, and then frontend developers point out that they can't use it.
So, it might make …
-
## CVE-2022-1650 - High Severity Vulnerability
Vulnerable Library - eventsource-1.0.7.tgz
W3C compliant EventSource client for Node.js and browser (polyfill)
Library home page: https://registry.npmj…
-
**Describe the bug**
EventSource in (dom-monkeypatch.d.ts) is conflicting with EventSource in Typescript lib.dom.d.ts
**What version are you on?**
Latest version - 11.2.1
**To Reproduce**
Ste…
-
Provide flexibility to suspend and resume the Eventsource
-
### Which tests failed?
sample run: https://github.com/solo-io/gloo/actions/runs/11817756946/job/32923834502?pr=10328
this log line looks particularly salient:
```
ggv2setup_test.go:80: 2024-11-13T…
-
Current proposal would be that the EventSource view must have relations with `tree:path` equal to the `ldes:timestampPath`
-
Updates to common and build options default objects:
```ts
{
define: {
"process.env": JSON.stringify(
getClientEnvironment(proc).stringified["process.env"]
),
"win…