0
Solucionado

Object reference not set to an instance of an object.

Anónimo hace 3 años en Studio actualizado por Pieter hace 3 años 7
Email Address : tedwardc@gmail.com Steps to follow : No Steps Provided at Warewolf.Studio.ViewModels.EnvironmentViewModel.d__258.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Warewolf.Studio.ViewModels.EnvironmentViewModel.d__254.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Warewolf.Studio.ViewModels.ExplorerViewModelBase.d__50.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_0(Object state) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
En revisión

Hi,


We have been unable to reproduce this bug. Can you provide us with any more information? Or has this error occurred again, if so what activity where you performing inside Warewolf when the error occured?


Thanks

Genie a través de Jira hace 3 años

Properly handle server disconnects. Message shown to the user when the server disconnects. Ensure that if the user refreshes after the server is up again the Studio connects and refreshes.

En revisión
Genie a través de Jira hace 3 años
Solucionado
Pieter a través de Jira hace 3 años