fz0x1/HPI
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

general: switch to make_logger in a few modules, use a bit more consistent logging, rely on default INFO level

Browse source
This commit is contained in:
Dima Gerasimov 2023-06-21 18:01:51 +01:00 • committed by karlicoss
parent 661714f1d9
commit dff31455f1
8 changed files with 27 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

8
my/bluemaestro.py
View file

@ -10,15 +10,13 @@ import re
import sqlite3
from typing import Iterable, Sequence, Set, Optional
from my.core import get_files, LazyLogger, dataclass, Res
from my.core import get_files, make_logger, dataclass, Res
from my.core.sqlite import sqlite_connect_immutable
from my.config import bluemaestro as config
# todo control level via env variable?
# i.e. HPI_LOGGING_MY_BLUEMAESTRO_LEVEL=debug
logger = LazyLogger(__name__, level='debug')
logger = make_logger(__name__)
def inputs() -> Sequence[Path]:
@ -63,7 +61,7 @@ def measurements() -> Iterable[Res[Measurement]]:
# tables are immutable, so can save on processing..
processed_tables: Set[str] = set()
for f in dbs:
logger.debug('processing %s', f)
logger.info('processing %s', f)
tot = 0
new = 0
# todo assert increasing timestamp?