@requence/task 0.8.3-edge.1221 → 0.8.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +16 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,21 @@
|
|
|
1
1
|
# @requence/task
|
|
2
2
|
|
|
3
|
+
## 0.8.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- f52da80: `watchTasks` calls `onConnect` only when the stream really opened.
|
|
8
|
+
|
|
9
|
+
`eventsource-client` calls its `onConnect` for every response, before it checks
|
|
10
|
+
the status. So one failed attempt — for example a gateway `502` — was reported
|
|
11
|
+
as `onConnect` → `onReconnecting` → `onError(502)` in the same millisecond, and
|
|
12
|
+
consumer logs read as a stream that connects and drops again (#351).
|
|
13
|
+
|
|
14
|
+
`onConnect` is now passed on only for a 2xx response. A failed attempt reports
|
|
15
|
+
`onReconnecting` and `onError` (and `onUnreachable` for a gateway status), as
|
|
16
|
+
before, and no longer claims a connection it never had. A consumer that uses
|
|
17
|
+
`onConnect` as a liveness signal now sees the truth.
|
|
18
|
+
|
|
3
19
|
## 0.8.2
|
|
4
20
|
|
|
5
21
|
### Patch Changes
|