Mine is definitely sticky. Happens on other operations (e.g. Verify) and jobs.
Commandline vacuum gives a stack to me. It evades StartScope somehow.
Running commandline entry
Finished!
System.Exception: Unable to find log in lookup table, this may be caused by attempting to transport call contexts between AppDomains (e.g. with remoting calls)
at Duplicati.Library.Logging.Log.get_CurrentScope()
at Duplicati.Library.Logging.Log.StartScope(ILogDestination log, ILogFilter filter, Boolean isolating)
at Duplicati.Library.Main.Controller.RunAction[T](T result, String[]& paths, IFilter& filter, Action`1 method)
at Duplicati.Library.Main.Controller.RunAction[T](T result, Action`1 method)
at Duplicati.Library.Main.Controller.Vacuum()
at Duplicati.CommandLine.Commands.Vacuum(TextWriter outwriter, Action`1 setup, List`1 args, Dictionary`2 options, IFilter filter)
at Duplicati.CommandLine.Program.ParseCommandLine(TextWriter outwriter, Action`1 setup, Boolean& verboseErrors, String[] args)
at Duplicati.CommandLine.Program.RunCommandLine(TextWriter outwriter, TextWriter errwriter, Action`1 setup, String[] args)
Return code: 100
I can leave this up a bit for more test, especially since I’ve moved to 2.1.0.105.