|
| 1 | +`7.3.19 (2024-02-23) <https://github.com/neos/flow-development-collection/releases/tag/7.3.19>`_ |
| 2 | +================================================================================================ |
| 3 | + |
| 4 | +Overview of merged pull requests |
| 5 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 6 | + |
| 7 | +`BUGFIX: Dont log stack trace for `InvalidHashException` in Production <https://github.com/neos/flow-development-collection/pull/3247>`_ |
| 8 | +---------------------------------------------------------------------------------------------------------------------------------------- |
| 9 | + |
| 10 | +This configures an ``invalidHashExceptions`` exception handler rendering group and configures it to not dump stack traces in ``Production`` context. For ``Development`` context stack traces are still written to ease debugging. |
| 11 | + |
| 12 | +* See: `#3159 <https://github.com/neos/flow-development-collection/issues/3159>`_ |
| 13 | + |
| 14 | +**Upgrade instructions** |
| 15 | + |
| 16 | +In case you need trace dumps for ``InvalidHashException`` in production context, override the settings as needed. |
| 17 | + |
| 18 | +**Review instructions** |
| 19 | + |
| 20 | +* See: `#3159 <https://github.com/neos/flow-development-collection/issues/3159>`_ for ways to trigger those exceptions. Then check if a trace is dumped. |
| 21 | + |
| 22 | + |
| 23 | +* Packages: ``Flow`` |
| 24 | + |
| 25 | +`BUGFIX: Fix documentation of `maximumThrowableDump` defaults <https://github.com/neos/flow-development-collection/pull/3269>`_ |
| 26 | +------------------------------------------------------------------------------------------------------------------------------- |
| 27 | + |
| 28 | +* Related: `#3158 <https://github.com/neos/flow-development-collection/issues/3158>`_ |
| 29 | + |
| 30 | +* Packages: ``Flow`` |
| 31 | + |
| 32 | +`TASK: Scripts.php avoid use of same references for exec <https://github.com/neos/flow-development-collection/pull/3171>`_ |
| 33 | +-------------------------------------------------------------------------------------------------------------------------- |
| 34 | + |
| 35 | +Followup to https://github.com/neos/flow-development-collection/pull/3116 |
| 36 | + |
| 37 | +I debugged with @dlubitz a problem and we found that in theory? $output _might_ be possibly already filled? |
| 38 | +I dont know if that can happen but just to be sure we set it to empty as its also a bad practice. |
| 39 | + |
| 40 | + |
| 41 | +**Upgrade instructions** |
| 42 | + |
| 43 | +**Review instructions** |
| 44 | + |
| 45 | + |
| 46 | +* Packages: ``Flow`` |
| 47 | + |
| 48 | +`TASK: Fix errors in Middleware code example <https://github.com/neos/flow-development-collection/pull/3299>`_ |
| 49 | +-------------------------------------------------------------------------------------------------------------- |
| 50 | + |
| 51 | +I found two small errors in the Middleware code example in the documentation. |
| 52 | + |
| 53 | + |
| 54 | +* Packages: ``Flow`` |
| 55 | + |
| 56 | +`Detailed log <https://github.com/neos/flow-development-collection/compare/7.3.18...7.3.19>`_ |
| 57 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
0 commit comments