Reporting fix for node initial Run

[Muntasib-creator]

Summary:

When a zeuz node is downloaded and run for the first time, It might happen that settings.conf inside framework file was imported before the file is created. This invokes an reporting error. The error is fixed

[Antu7]

🔎 ZeuZ PR Review

Open the full report in ZeuZ: Review findings and apply suggestions

Overview	Value
Agents	✅ 4 completed
Suggestions	💡 2

Agent breakdown

→ General Review

Status: ✅ Completed
Suggestions: 0 suggestions

No actionable issues found in the PR diff; the change appears consistent with the reporting fix and updated call sites in CommonUtil.py.

→ Security Review

Status: ✅ Completed
Suggestions: 0 suggestions

No security findings in this PR diff. The changes are limited to refactoring the temp config path helper and updating call sites, with no new auth, injection, or data exposure risks introduced.

→ Performance Review

Status: ✅ Completed
Suggestions: 1 suggestion

The PR introduces a hot-path config lookup regression by turning temp_config into a function that re-reads settings on every log/report call; caching the computed path avoids repeated file I/O in logging-heavy code.

→ Testing Review

Status: ✅ Completed
Suggestions: 1 suggestion

The change fixes a real lazy-evaluation bug, but it adds no regression coverage for the reporting/logging path that depended on temp_config(). A focused test should lock in the new behavior and prevent the original failure from returning.

Open ZeuZ to inspect full findings, continue an agent conversation, or apply safe patch suggestions.

[mahbd]

There are several other files where temp_config is still being used the old way. I think those should be changed in the same way as well.

Those won't cause any problem