.garden/error.log always empty?

Question

It seems in my current setup ` garden error log` is always empty However I find the actual file under ` garden logs error log` Alongside `development log` How can I fix this to not go under logs folder and just stay on the root folder I searched the documents and I could not find a way to influence this via an env variable or some sort of config Thank you

bright-policeman-43626 · Answer

I m not sure about how these logs works do you mind taking a look to this question please < gardenheart 1083685896169209926> < quaint dress 831> < ancient diamond 80011> < curved intern 91221>

quaint-dress-831 · Answer

< aloof lamp 69262> I don t think this is possible

bright-policeman-43626 · Answer

I don t understand why the garden error log is there though perhaps it was intended to be a symlink of garden logs error log

aloof-lamp-69262 · Answer

So you are saying the default is under garden logs error log Your documentation says otherwise It says it is under garden error log directly

ancient-diamond-80011 · Answer

there should be a ` garden error log` but it will only have content if you ran into errors if you have a successful command the contents will be empty

ancient-diamond-80011 · Answer

the ` garden error log` will reflect the most recent run it is not an append only log of all runs or similar

ancient-diamond-80011 · Answer

the ` garden logs` directory will have the logs for each individual command run in separate files with timestamped filenames

bright-policeman-43626 · Answer

Marking this as resolved as I think now it s clear why the file was empty