Can't Repro
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
kh...@google.com <kh...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
```
gcloud beta logging write --payload-type=json test-errors-log '{
"message": "Error: New Error.\n at process._tickCallback (internal/process/next_tick.js:68:7)",
"serviceContext": {
"service": "test-service",
"version": "latest"
}
}'
```
Whereas if I change `process._tickCallback` (e.g. add an s to process), add another line, the error is reported. Changing the location (inside the parens) does not affect this. I would venture that there is some kind of filter for this specific function, as it's internal to node? Unfortunately, we see it often at the bottom of the stack if async code fails somehow.