[rl.cli.net] logs are not generated when configured to produce them locally.

[kumpera]

I'm using this rl.net.cli command:

dotnet .\Rl.Net.Cli.dll perf --actions 50 --shared-features 3 --action-features 10  --data 1 --config client.json

With the following client.json:

{
    "ApplicationID": "cf8a74ffaa1f4d1a872d251909bfa77d",
    "observation.file.name": "C:\\joiner-data\\observations.fb",
    "interaction.file.name": "C:\\joiner-data\\interactions.fb",
    "model.source": "NO_MODEL_DATA",
    "interaction.sender.implementation": "INTERACTION_FILE_SENDER",
    "observation.sender.implementation": "OBSERVATION_FILE_SENDER",
    "decisions.sender.implementation": "INTERACTION_FILE_SENDER",
    "InitialExplorationEpsilon": 1.0,
    "LearningMode": "Online",
    "queue.mode" : "BLOCK",
    "protocol.version": "2",
    "send.batchintervalms": "10000"
  }

No data is produced and no error is reported after 10 minutes.

[ataymano]

logger is turned off by default.
adding:
"trace.logger.implementation": "CONSOLE_TRACE_LOGGER"
should help you to get more logs

[kumpera]

I did troubleshoot it further and here my findings.

This happens on windows only.
The issue is a mix of the following:

• rlclientlib opens the result file in exclusive mode, which leads to windows not showing the file size until the end.
• rl.net.cli even when in data size mode, it reports progress in terms of number of decisions.

This means there's no reasonable way to assess how far a run is, which is not particularly helpful when you have a run that could take close to an hour.

The outcome of this investigation is that rl.net.cli should report progress by the same unit it will terminate execution and maybe show completion percentages for those of us that are both impatient and anxious.

Whether rl.client.lib should open the output file in shared more or not is a more complex question as it deviates from the standard open mode in windows and I can't easily tell what could go wrong.