You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a response generated by a worker is too big, a log is displayed indicating that the worker has finished the processing and returned the result but the client never receives it.
Expected behavior
If the response is too big, either an error message should be received by the client or the worker should fail and should be able to catch the error to handle it.
Minimal reproduction of the problem with instructions
Create a new project
In the worker code, do a loop to generate a string with 1000000 concatenated 'hello'
Run both worker and client
Client calls the worker
=> no answer and no error at all
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Operating System:
Node Version: any
Npm Version: any
@angular/* Version: any
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Scope (check one with "x")
Current behavior
When a response generated by a worker is too big, a log is displayed indicating that the worker has finished the processing and returned the result but the client never receives it.
Expected behavior
If the response is too big, either an error message should be received by the client or the worker should fail and should be able to catch the error to handle it.
Minimal reproduction of the problem with instructions
=> no answer and no error at all
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: