3 ms·
Being able to actually interrupt/cancel would be nice. You can get more feedback by adjusting TF_LOG env var. Logging levels have been getting improvements for
by nijave 3y ago
Being able to actually interrupt/cancel would be nice. You can get more feedback by adjusting TF_LOG env var. Logging levels have been getting improvements for a while (it used to just be TRACE that spammed everything)
- mschuster91 3y ago> You can get more feedback by adjusting TF_LOG env var. yep, but that's often enough useless after the fact. In the PHP world, for example, there's Symfony/Monolog's `fingers_crossed` logger [1]... it keeps logs below the normal threshold in memory, but if there is a single event of a given severity or worse, it dumps out all the logs it has ingested so far for this request. A real lifesaver that one is. [1] https://symfony.com/doc/current/logging.html https://symfony.com/doc/current/logging.html
- nijave 3y agoI used to add TF_LOG_PATH to my shell profile so all TF runs log to disk with a daily cron to truncate the file.