- Previously this would have been handled by WriteArray, now Plugins and Modules are a List and ToArray is called, the check needs to be moved up.
#rb rob.cannaday
[FYI] ben.marsh
#jira none
#ROBOMERGE-SOURCE: CL 11723339 in //UE4/Release-4.25/... via CL 11723340
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11723343 by anthony bills in Main branch]
#rb none
#jira UE-89684
#rnx
#ROBOMERGE-SOURCE: CL 11661535 in //UE4/Release-4.25/... via CL 11661587
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11661659 by ben marsh in Main branch]
#rb none
#jira UE-88824, UE-89676
#ROBOMERGE-SOURCE: CL 11658206 in //UE4/Release-4.25/... via CL 11658244
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11658322 by ben marsh in Main branch]
Additionally allow monolithic programs inside platform extensions to ouput to the Binaries directory in the extension.
[at]brian.white, [at]josh.adams, [at]ben.marsh
#jira UE-81798
#rb ben.marsh
#ROBOMERGE-SOURCE: CL 11655119 in //UE4/Release-4.25/... via CL 11655234
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11655284 by anthony bills in Main branch]
#jira UE-88545
#rb JeanLuc.Corenthin
#ROBOMERGE-SOURCE: CL 11647759 in //UE4/Release-4.25/... via CL 11647760
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11647762 by emil kirichev in Main branch]
#jira UE-89634
#ue4
#android
#rb Jack.Porter
#ROBOMERGE-SOURCE: CL 11646388 in //UE4/Release-4.25/... via CL 11646389
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11646391 by chris babcock in Main branch]
#jira UE-89658
#ue4
#android
#rb trivial
#ROBOMERGE-SOURCE: CL 11645559 in //UE4/Release-4.25/... via CL 11645563
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11645565 by chris babcock in Main branch]
#rb none
#jira
#ROBOMERGE-SOURCE: CL 11645538 in //UE4/Release-4.25/... via CL 11645541
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v656-11643781)
[CL 11645543 by ben marsh in Main branch]
#rb none
#jira
#ROBOMERGE-SOURCE: CL 11640359 in //UE4/Release-4.25/... via CL 11640368
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11640414 by ben marsh in Main branch]
#rb none
#jira UE-75445
#ROBOMERGE-SOURCE: CL 11638471 in //UE4/Release-4.25/... via CL 11638491
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11638504 by ben marsh in Main branch]
-Comment out clustering tests until the api is working again.
#rb none
#jira nojira
#ROBOMERGE-SOURCE: CL 11637934 in //UE4/Release-4.25/... via CL 11637944
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11637999 by brice criswell in Main branch]
#rb none
#jira UE-88824
#ROBOMERGE-SOURCE: CL 11637884 in //UE4/Release-4.25/... via CL 11637925
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11637942 by ben marsh in Main branch]
- Added the ability to copy and restore a live session, preventing the need to archive it in first place, making the server exist fast (releasing the session lock very quickly) before showing the crash UI and before the next Editor instance could starts.
Details:
This bug could manifest if various ways. An issue causing this bug was fixed in 11252374. This bug can also be observed if the crash reporting process doesn't release its lock on the crashed session quickly. Archiving a session may takes several minutes (depending on the session size) and while a session is archiving, its database is locked and cannot be restored until the archiving process complets. When the Editor reboots after a crash, it searches for a session to recover, but skip over any session that is mounted/locked assuming the session is concurrently used by a concurrent Editor process, potentially preventing it from restoring. The optimal way to work around this problem is to skip the archiving step. Instead, the live session is never archived (saving a copy), which allows the recovery service to shutdown and release the session lock very quickly ensuring that the session will be unlocked when the Editor restarts. On Editor start, it a crashed session is found and the user decides to restore it, the live session is copied into a new live session.
This changelist also affect those other jira in the following ways:
#jira UE-87899 - Disaster recovery prevents showing the crash reporting UI in a timely manner if the session is large
- This CL changes execution order to shut down the recovery service ASAP to release the lock, but the optimization above make it super fast, so the UI should always be shown in a timely manner.
#jira UE-87927 - Disaster Recovery doesn't restore a crash from a restored session
- This CL ensures the recovery service release the session lock faster than the next instance of the Editor can start.
#jira UE-87900 - Disaster Recovery stops recording transactions if the UDP transport layer restarts or auto-repair
#jira UE-88517 - Concert Log Spam - (ConcertKeepAlive) discarded
- This CL fixes an issues with endpoints timeout logic.
#jira UE-81049 - Clean up the DisasterRecovery Intermediate directory
- This CL added code to clean up the intermediate directory left over by crashed client.
#rb Francis.Hurteau
#ROBOMERGE-SOURCE: CL 11632069 in //UE4/Release-4.25/... via CL 11632084
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11632094 by patrick laflamme in Main branch]
#rb none
#jira UE-89552
#ROBOMERGE-SOURCE: CL 11632049 in //UE4/Release-4.25/... via CL 11632050
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11632058 by ben marsh in Main branch]
#rb none
#rnx
#jira
#ROBOMERGE-SOURCE: CL 11631935 in //UE4/Release-4.25/... via CL 11631941
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11631949 by ben marsh in Main branch]
#rb none
#jira UE-89364
#ROBOMERGE-SOURCE: CL 11631903 in //UE4/Release-4.25/... via CL 11631909
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11631916 by ben marsh in Main branch]
#rb none
#jira UE-89548
#ROBOMERGE-SOURCE: CL 11631033 in //UE4/Release-4.25/... via CL 11631036
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11631049 by ben marsh in Main branch]
#rb none
#jira UE-82398
#ROBOMERGE-SOURCE: CL 11630897 in //UE4/Release-4.25/... via CL 11630908
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11630926 by ben marsh in Main branch]
#rb none
#jira UE-88446
[FYI] Martin.Sevigny
#ROBOMERGE-SOURCE: CL 11625250 in //UE4/Release-4.25/... via CL 11625255
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11625268 by ben marsh in Main branch]
#rb none
#jira UE-88446
#ROBOMERGE-SOURCE: CL 11624846 in //UE4/Release-4.25/... via CL 11624849
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11624868 by ben marsh in Main branch]
#rb none
#rnx
#jira
#ROBOMERGE-SOURCE: CL 11624709 in //UE4/Release-4.25/... via CL 11624720
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11624754 by ben marsh in Main branch]
#jira
#rb none
#ROBOMERGE-SOURCE: CL 11619452 in //UE4/Release-4.25/... via CL 11619471
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11619492 by ben marsh in Main branch]
To embed a custom manifest, set the WindowsPlatform.ManifestFile to a vaild path in a *.Target.cs file. To disable the embedding of the default manifest, set it to null.
#rb none
#jira UE-88825, UE-87398
#ROBOMERGE-SOURCE: CL 11619014 in //UE4/Release-4.25/... via CL 11619045
#ROBOMERGE-BOT: RELEASE (Release-4.25Plus -> Main) (v655-11596533)
[CL 11619057 by ben marsh in Main branch]
