Skip to content

fix: use unique logger name per job to prevent log handler conflicts#219

Merged
srmnitc merged 1 commit intoICAMS:mainfrom
keyurrmaniya:fix/melting-log
Mar 2, 2026
Merged

fix: use unique logger name per job to prevent log handler conflicts#219
srmnitc merged 1 commit intoICAMS:mainfrom
keyurrmaniya:fix/melting-log

Conversation

@keyurrmaniya
Copy link
Copy Markdown

  • logging.getLogger(name) returned same singleton for all jobs; each new job cleared previous job's file handler silently. Fixed by using log file path as unique logger name.
  • Propagate MeltingTemp handlers to Solid/Liquid sub-job loggers so all sub-job output also appears in melting_temperature.log.
  • Fix np.NaN -> np.nan for NumPy 2.0 compatibility.
  • Add tests for no handler accumulation and no cross-contamination.

- logging.getLogger(__name__) returned same singleton for all jobs;
  each new job cleared previous job's file handler silently. Fixed by
  using log file path as unique logger name.
- Propagate MeltingTemp handlers to Solid/Liquid sub-job loggers so
  all sub-job output also appears in melting_temperature.log.
- Fix np.NaN -> np.nan for NumPy 2.0 compatibility.
- Add tests for no handler accumulation and no cross-contamination.
@srmnitc srmnitc merged commit 1c9c76e into ICAMS:main Mar 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants