[CONJS-60] handling pipe error for stream Created: 2019-01-30 Updated: 2019-01-31 Resolved: 2019-01-30 |
|
| Status: | Closed |
| Project: | MariaDB Connector/node.js |
| Component/s: | other |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.3-GA |
| Type: | Bug | Priority: | Major |
| Reporter: | Diego Dupin | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
see https://github.com/MariaDB/mariadb-connector-nodejs/issues/40 The problem is when "piping", to handle the stream when writable stream fails How to handle writable that stop for any reason ( for example a ClientRequest that has ended): I don't see any other solution but to document piping properly to indicate to resume. example :
|
| Comments |
| Comment by Diego Dupin [ 2019-01-30 ] |
|
Correction is done with https://github.com/MariaDB/mariadb-connector-nodejs/commit/ddb208003cd942b3551cc0cd7cd28df29163db3e, simplifying implementation, using basic TCP Back Pressure. |