Log file sometimes not made

[rzellem]

For some users, even when using the latest version of EXOTIC, the log file is not being made. Is it hiding somewhere or is there a more evil problem lurking about?

[tamimfatahi]

Do you know who specifically? Maybe we can get in touch with them. Generally, log files should be created in the same directory they launch exotic.py from (at least for me). I've also noticed it goes into other folders as well, but that could just be me because I'm launching it in different directories as well when I use my IDE or terminal.

[rzellem]

Right now, just @pearsonkyle

[jpl-jengelke]

Are they launching from the PyPi distribution. I seem to recall that may bury the log in the Py internals. It was a sort of known glitch.

[rzellem]

@jpl-jengelke - So if a user installs via pip install exotic, the log file will not be written?

[jpl-jengelke]

It will be written, just not easy to find. I think we need to specify a default directory somewhere but it won't necessarily be in the directory where it is running. What we could do is detect if it is running as a module and then change the log file location to /logs/ (be sure to make the dir first.

https://stackoverflow.com/a/57977441/325452
https://stackoverflow.com/q/14050281/325452

[rzellem]

Is this something you'd like to tackle, @jpl-jengelke, after next week's roll-out of CITISENS? or could @pearsonkyle help you out here?

[jpl-jengelke]

Given the LOE to get into all the logging minutiae, it's probably better if I do it. I can let you know next week. ...

[jpl-jengelke]

I assigned this to Tamim and myself (only based on earlier comments) as it seems the work is taking place right now.

[tamimfatahi]

Adding onto this issue that not all logging files appear to be getting timestamps. Could be due to OS possibly as the error resulted from Ubuntu 20.04/WSL2/Windows 10, Python 3.8.5.

[tamimfatahi]

@jpl-jengelke What's the status on this? Is this still an issue we should deal with?