Commit 4a768bc
doc: upgrade stability status of report API
The property `process.report.reportOnFatalError`
was deemed experimental, as it was not honored
under certain scenarios (for example out of memory
conditions). The report configuration were previously
stored on the `environment` structure which was not
available on these types of fatal error cases.
The referenced PR has addressed this case (sometime
back), and the property is working as intended.
Refs: #32207
PR-URL: #35654
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>1 parent 01ba1c9 commit 4a768bc
1 file changed
Lines changed: 4 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1898,10 +1898,12 @@ Additional documentation is available in the [report documentation][]. | |||
| 1898 | 1898 | ### `process.report.reportOnFatalError` | |
| 1899 | 1899 | <!-- YAML | |
| 1900 | 1900 | added: v11.12.0 | |
| 1901 | + changes: | ||
| 1902 | + - version: | ||
| 1903 | + - REPLACEME | ||
| 1904 | + description: This API is no longer experimental. | ||
| 1901 | 1905 | --> | |
| 1902 | 1906 | ||
| 1903 | - > Stability: 1 - Experimental | ||
| 1904 | - | ||
| 1905 | 1907 | * {boolean} | |
| 1906 | 1908 | ||
| 1907 | 1909 | If `true`, a diagnostic report is generated on fatal errors, such as out of | |
0 commit comments