feat: log to file #967

Merged
thesimplekid merged 4 commits from log_file into main 2025-08-19 13:57:15 +00:00
thesimplekid commented 2025-08-15 13:53:06 +00:00 (Migrated from github.com)

Description


Notes to the reviewers


Suggested CHANGELOG Updates

CHANGED

ADDED

REMOVED

FIXED


Checklist

### Description <!-- Describe the purpose of this PR, what's being adding and/or fixed --> ----- ### Notes to the reviewers <!-- In this section you can include notes directed to the reviewers, like explaining why some parts of the PR were done in a specific way --> ----- ### Suggested [CHANGELOG](https://github.com/cashubtc/cdk/blob/main/CHANGELOG.md) Updates <!-- Please do not edit the actual changelog but note what you changed here. --> #### CHANGED #### ADDED #### REMOVED #### FIXED ---- ### Checklist * [ ] I followed the [code style guidelines](https://github.com/cashubtc/cdk/blob/main/CODE_STYLE.md) * [ ] I ran `just final-check` before committing
crodas (Migrated from github.com) reviewed 2025-08-15 13:53:06 +00:00
asmogo (Migrated from github.com) requested changes 2025-08-15 17:39:07 +00:00
@ -705,7 +804,7 @@ async fn start_services_with_shutdown(
tracing::info!("Mint info already set, not using config file settings.");
}
} else {
asmogo (Migrated from github.com) commented 2025-08-15 17:38:30 +00:00
pub async fn run_mintd(

This got me confused. I would prefer calling the function run_mintd with enable_logging as an arg, or remove the arg / else statement.

```suggestion pub async fn run_mintd( ``` This got me confused. I would prefer calling the function `run_mintd` with `enable_logging` as an arg, or remove the arg / else statement.
thesimplekid (Migrated from github.com) reviewed 2025-08-16 09:42:55 +00:00
@ -705,7 +804,7 @@ async fn start_services_with_shutdown(
tracing::info!("Mint info already set, not using config file settings.");
}
} else {
thesimplekid (Migrated from github.com) commented 2025-08-16 09:42:55 +00:00
Yeah thats better applied in https://github.com/cashubtc/cdk/pull/967/commits/3cd4669e5a03a241baeb200382c4b9810f80b930
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cashubtc/cdk!967
No description provided.