Trevor Hartman

Thanks for reporting @KlavsKlavsen. These suggested settings were generated by the helm chart, but they aren't actually supported (I've never tested them). Yetibot requires write access for logging, at the...

The rolling log appender [can be disabled](https://github.com/yetibot/core/blob/6fa4584e20b7e8adede405a3492dbbfd2237d7f0/src/yetibot/core/logging.clj#L22-L29). Looks like this config option wasn't documented, but I added it in https://github.com/yetibot/core/commit/254da5c7a5c62353da5e7eaeb6ab7066a62dbb25. Agree on the standard to log to stdout/stderr in container...

Looks like Yandex is not free :thinking:

Related https://github.com/yetibot/yetibot/issues/870

Yes! I'm a big fan of the vision of cljdoc and I think it fills part of our docs needs. IIRC you were at the cljdoc talk where I asked...

Bug is around https://github.com/yetibot/yetibot.core/blob/b29c8816e613799bdb4b3662c3f1f0f8ae4c5700/src/yetibot/core/commands/my.clj#L86-L94

It happens when users is empty. Users being empty has to do with a bug where in some channels users are not properly set. when that happens you see logs...

I don't know the exact repro to get yetibot to be not be aware of the users in a channel. Try DMing it, or inviting it to a channel. Maybe...

You could simulate it by setting `users` to `[]` in the functions, for testing, then removing that before committing.

Ah, too bad. I guess we can wait till they add support.