Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 306.1
edited by Carlijn Kokkeler
on 2024/08/26 14:35
on 2024/08/26 14:35
Change comment:
There is no comment for this version
To version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
on 2023/08/29 11:07
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 28-MonitoringMania1 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,19 +1,18 @@ 1 - Duringour recent sprint cycle, wehaveeveralmprovementstothe monitoring graphsinManage.Moreover, wehavedoneseveralimprovementsindeploy architectureandflowtesting. Please find out allour changes& bugxesbelow.1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 28-Monitoring Mania||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]]. 4 4 5 -====Minor changes==== 6 -* Community - Release Notes: The legacy release notes tab has been removed. 7 -* Create - Flow Testing: Test messages can now be edited or removed while in the edit mode of the flow testing functionality. 8 -* Deploy - Architecture: The SSL section in runtime settings has more elaborate helptext. 9 -* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended. 10 -* Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan. 11 -* Deploy - History: We added logging for when properties are deleted from the unused properties screen. 12 -* Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview. 13 -* Manage - Monitoring: We have done many improvements to the Monitoring graphs. Find out all improvements in our [[release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]]. (#866) 5 +=====Minor changes===== 14 14 7 +* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers. 8 + 15 15 ====Bug fixes==== 16 -* Create - Flow Designer: We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. (#1065) 17 -* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392) 18 -* Create - Flow Testing: It is now possible to reuse the test messages from the onramp in the routing and vice versa in flow testing. (#1274) 19 -* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295) 10 + 11 +* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970) 12 +* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 13 +* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release. 14 +* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 15 + 16 +=====Infra and image changes===== 17 + 18 +* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.