Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
Bugfix
The KBDataProducerTask saves the last 50 messages it has sent. The only use for this is in the AbstractTLSyncTest. For this the whole tl:ChangeSet is kept in memory. On a small test dataset, that was 500 KB of memory for 600 new objects combined, in one changeset.
The number of stored messages can be configured. The default is currently 50. Since it is only used in tests, the default should be set to 0 and a higher value should only be configured in tests.
Conversion
The default is removed. This makes the implicit default 0. Nothing needs to be changed for the tests that use this method. They are all located in the project test.com.top_logic.kafka. A value of 5'000 is already explicitly configured there.
Test
- Check in the code if the default of KBDataProducerTask.Config.getCachedEventSize() has been removed or is 0.
Check in a running application:
- Start one of the com.top_logic.sync.demo applications.
- In the debugger set a suitable breakpoint to check that KBDataProducerTask._lastSentEvents is null or has size 0.