fix: replace printStackTrace with RecordLog in ConfigUtil

[lxcxjxhx]

Problem

ConfigUtil.java uses e.printStackTrace() in 3 places (lines 80, 107, 122) for error handling, which bypasses Sentinel's logging framework (RecordLog).

Impact

• Stack traces go directly to stderr instead of through the configured logging system
• Cannot control log level, format, or output destination for these errors
• Inconsistent with the rest of the codebase which uses RecordLog

Fix

Replace all 3 occurrences of e.printStackTrace() with RecordLog.warn() calls that include contextual information (file name or URL being loaded).

Local environment limitations, relying on CI/CD automated testing.

[yichao0824]

Hi! I'd like to work on this issue. Could you assign it to me? Thanks!

[oss-sentinel-ai]

Issue Evaluation

Category: enhancement | Status: Confirmed

Verified against the current codebase on branch 1.8. ConfigUtil.java contains 3 e.printStackTrace() calls (lines 78, 105, 120) that bypass Sentinel's RecordLog framework:

• Line 78: loadFromClasspath() — resource loading failure
• Line 105: loadFromFile() — file path loading failure
• Line 120: loadFromFile() — URL loading failure

These should use RecordLog.warn() with contextual information (file path / URL) for consistency with the rest of the codebase.

Impact: Low — logging consistency improvement, no functional behavior change.
Severity: Low — no security or correctness impact.

This is a good first contribution. Note: someone has already expressed interest in working on this issue.

---

Automated evaluation by oss-sentinel-ai