Skip to content

fix: correct duration type comparison in environment variable processing #4979

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 9, 2025

Conversation

geekeryy
Copy link
Contributor

@geekeryy geekeryy commented Jul 1, 2025

  • Prevent confusion between duration and other int64 types in env var processing
  • Add test case for int64 environment variable handling

This fixes a bug where duration fields could be incorrectly processed as regular int64 fields when using environment variables, leading to type mismatch errors.

Copy link

codecov bot commented Jul 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.90%. Comparing base (8690859) to head (383bdc0).
Report is 372 commits behind head on master.

Additional details and impacted files
Files with missing lines Coverage Δ
core/mapping/unmarshaler.go 96.21% <100.00%> (-0.27%) ⬇️

... and 20 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@geekeryy
Copy link
Contributor Author

geekeryy commented Jul 9, 2025

@kevwan Can this fix be merged?

- Prevent confusion between duration and other int64 types in env var processing
- Add test case for int64 environment variable handling

This fixes a bug where duration fields could be incorrectly processed as regular
int64 fields when using environment variables, leading to type mismatch errors.
@kevwan kevwan force-pushed the fix/unmarshaler branch from 558c07f to 383bdc0 Compare July 9, 2025 15:15
@kevwan
Copy link
Contributor

kevwan commented Jul 9, 2025

@kevwan Can this fix be merged?

Sure, thanks!

I was digging into this PR changes for a while. And I'll make some changes after it's merged.

@kevwan kevwan added this pull request to the merge queue Jul 9, 2025
Merged via the queue into zeromicro:master with commit bca7bbc Jul 9, 2025
6 checks passed
@kevwan kevwan mentioned this pull request Jul 9, 2025
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