Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 173.1
edited by CarlijnKokkeler
on 2023/12/21 16:12
Change comment: There is no comment for this version
To version 240.1
edited by Erik Bakker
on 2025/04/04 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +241.1 - Wild West
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,10 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4 -
5 -=====New features=====
6 -
7 -
8 -
9 -=====Minor changes=====
10 -
11 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
12 -
13 -
14 -
15 15  ====Bug fixes====
16 16  
5 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release.
6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release.
17 17  
8 +====Remarks====
18 18  
19 -
10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.