|
35 | 35 | cached. |
36 | 36 |
|
37 | 37 | At the end of document build, `codebraid` now exits with a non-zero exit |
38 | | - code if there are errors in the document (#24). This is triggered by using |
39 | | - invalid settings or by executing code that causes errors. It is also |
40 | | - triggered by loading cached output from code that caused errors when it was |
41 | | - originally executed (error state is cached). An exit code of 64 indicates |
42 | | - an error serious enough to prevent or interrupt code execution. An exit |
43 | | - code of 65 indicates an error that does not affect code execution, such as |
44 | | - invalid settings related to displaying code output. An exit code of 1 still |
45 | | - indicates that `codebraid` itself exited unexpectedly and failed to complete |
46 | | - document build. |
| 38 | + code if there are errors or warnings (#24). This is triggered by using |
| 39 | + invalid settings or by executing code that causes errors or warnings. It is |
| 40 | + also triggered by loading cached output from code that caused errors or |
| 41 | + warnings when it was originally executed (error and warning state is |
| 42 | + cached). Exit codes are between 4 and 60 inclusive. The bits in the exit |
| 43 | + code are assigned value as follow: |
| 44 | + ``` |
| 45 | + 0b00<doc_warn><exec_warn><doc_error><exec_error>00 |
| 46 | + ``` |
| 47 | + Nonzero values for `<doc_warn>` and `<exec_warn>` indicate the presence of |
| 48 | + warnings from document build and from code execution, respectively. |
| 49 | + `<doc_error>` represents an error in document build that was not so severe |
| 50 | + that build was canceled with exit code 1, such as invalid settings related |
| 51 | + to displaying code output. `<exec_error>` represents an error from code |
| 52 | + execution. An exit code of 1 still indicates that `codebraid` itself exited |
| 53 | + unexpectedly or otherwise failed to complete document build. |
47 | 54 |
|
48 | 55 | * Reimplemented built-in code execution system and Jupyter kernel support as |
49 | 56 | async. This makes possible new progress tracking and `live_output` |
|
0 commit comments