Model tree is reloaded after making changes to deployments

jsusen · May 12, 2021, 8:38am

The model tree in Architect is reloaded every time a change is made to deployment

jsusen · May 12, 2021, 2:30pm

We should ignore changes in model directory while saving any file. Make sure the system watch dog waits for more changes before reacting.

It would also be good to be able to run atchitect and server on the same model. Changes made in Architect would cause server to reload the updated model.

jsusen · May 13, 2021, 8:27am

The model reloading in architect was caused by orphan external files. These files were not referenced anywhere which means they were not included in the file hash index.

tvavrda · May 13, 2021, 10:33am

Should the model consistency check mention these files? That would be nice.

jsusen · May 14, 2021, 7:30am

jsusen · May 14, 2021, 9:40am

tvavrda · May 14, 2021, 10:15am

Can you please explain why is this important here? Is it only important when creating a package or also in other cases?

github.com

origam/origam-source/blob/9cc579bf2d3424b761f171599e40afbb5fbb416c/Origam.Workbench.Services/PackageHelper.cs#L33


using Origam.Schema;
using System;


namespace Origam.Workbench.Services
{
    public class PackageHelper
    {
        public static void CreatePackage(string packageName, Guid packageId, Guid referencePackageId)
        {
            IPersistenceService persistenceService = ServiceManager.Services.GetService<IPersistenceService>();
            RunWithInactiveFileEventQueue(
                persistenceService: persistenceService, 
                action: () =>
                {
                    CreatePackage(packageName, packageId, referencePackageId, persistenceService);
                });
        }


        private static void CreatePackage(string packageName, Guid packageId,
            Guid referencePackageId, IPersistenceService persistenceService)
        {

jsusen · May 14, 2021, 10:40am

The use of RunWithInactiveFileEventQueue was just a refactoring. The original author @JiriPrajz can probably explain the intent better.

JiriPrajz · May 21, 2021, 5:55am

This was fixed because @zcapkova reported this issue at 2020-01-08.

When creating a new project an error appears after the wizard runs through and you select update deployment scripts.

========================================
Error
Exception on timer
Object reference not set to an instance of an object.
========================================
Stack trace
at Origam.DA.Service.FileEventQueue.FindPersistenceFileHash(FileInfo file)
at Origam.DA.Service.FileEventQueue.NeedsUpdate(FileInfo file)
at Origam.DA.Service.FileEventQueue.ShouldBeUpdated(FileInfo file)
at Origam.DA.Service.FileEventQueue.ProcessAccumulatedEvents()
at Origam.DA.Service.FileEventQueue.TimerElapsedHandler() at Origam.DA.Service.FileEventQueue.<>c__DisplayClass17_0.<TimerElapsedHandler>b__0(Object _)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

jsusen · May 26, 2021, 6:56am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.