Question: PowerShell and GE

[eosfor]

Hello colleagues, i'm trying to play around with GE using PowerShell. Actually I'm trying to make a module to work with GE using PowerShell.

So far i got a question. I have the following piece of code, which performs kid of initialization.

TrinityConfig.LogEchoOnConsole = LogEchoOnConsole;
LoggingConfig.Instance.LogDirectory = LogDirectory;
StorageConfig.Instance.StorageRoot = StorageRoot;

Global.Initialize();

LambdaDSL.SetDialect("MAG", "StartFrom", "VisitNode", "FollowEdge", "Action");
FanoutSearchModule.SetQueryTimeout(-1);

TrinityServer server = new TrinityServer();
server.RegisterCommunicationModule<FanoutSearchModule>();
server.Start();

However, when this runs as part of PowerShell module i see some noise on the PowerShell console, like this:

What do i do. How can i properly initialize an avoid any output to console? Or control this output?

[yatli]

hi @eosfor !
If you have set LogEchoOnConsole but still observe the 'noise' being scattered, you could try to work it around by setting LogLevel to Off.

[eosfor]

Hello @yatli,

I've updated the call a bit.

This part passes the parameters from cmdlet to initialization routine and generates verbose output (in yellow)

if (!GlobalState.Instance.IsInitialized)
{
    WriteVerbose($"Setting LogDirectory to: {LogDirectory}");
    WriteVerbose($"Setting StorageRoot to: {StorageRoot}");
    WriteVerbose($"Setting LogEchoOnConsole to: {LogEchoOnConsole}");
    WriteVerbose($"Setting LogLevel to: {LogLevel}");

    GlobalState.Instance.Initialize(LogDirectory, StorageRoot, LogEchoOnConsole, LogLevel);
}

And this part is initialization itself

public void Initialize(string LogDirectory, string StorageRoot, bool LogEchoOnConsole, Trinity.Diagnostics.LogLevel LogLevel)
{
    if (!_isInitialized )
    {
        TrinityConfig.LogEchoOnConsole = LogEchoOnConsole;
        LoggingConfig.Instance.LogDirectory = LogDirectory;
        LoggingConfig.Instance.LoggingLevel = LogLevel;
        StorageConfig.Instance.StorageRoot = StorageRoot;

        Global.Initialize();

        LambdaDSL.SetDialect("MAG", "StartFrom", "VisitNode", "FollowEdge", "Action");
        FanoutSearchModule.SetQueryTimeout(-1);

        TrinityServer server = new TrinityServer();
        server.RegisterCommunicationModule<FanoutSearchModule>();
        server.Start();

        _isInitialized = true;
    }
}

And here is the output.

As you can see it still outputs stuff to a console for some reason.

[yatli]

Hmm, I think the options are flushed by initialization. I'll look into it shortly.
@leasunhy got time to take a look?

[eosfor]

This is how it is happening

https://www.screencast.com/t/7zS7XjjHD7E

[yatli]

Looking into this now.

[yatli]

@eosfor could you please pull master and try again? That should be a drop-in fix.

[eosfor]

Sure @yatli, will do and let you know

[eosfor]

@yatli, it works better now

However, there is an output left (marked on a screeshot), generated by this call:

[yatli]

Uh oh, this is probably from the storage composition module. It must be another Console.WriteLine...

Will fix this really soon!

cc @thautwarm

[yatli]

@eosfor should be alright now