Skip to content

IcingaDB::TimestampToMilliseconds(): limit output to four year digits #10059

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
Oct 2, 2024

Conversation

Al2Klimov
Copy link
Member

Too high timestamps may overflow uint64_t (and the YYYY format) and negative ones don't fit into uint64_t. Those may crash our Go daemon.

@Al2Klimov Al2Klimov added bug Something isn't working area/icingadb New backend labels May 14, 2024
@cla-bot cla-bot bot added the cla/signed label May 14, 2024
@Al2Klimov Al2Klimov requested a review from yhabteab June 10, 2024 15:47
@Al2Klimov Al2Klimov self-assigned this Aug 20, 2024
@Al2Klimov Al2Klimov changed the title IcingaDB::TimestampToMilliseconds(): limit output to [1970..8307] AD IcingaDB::TimestampToMilliseconds(): limit output to four year digits Aug 20, 2024
@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from 8c05158 to a2caaf4 Compare August 20, 2024 15:39
@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from a2caaf4 to d93f955 Compare September 3, 2024 12:10
@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from d93f955 to 9e2d6aa Compare September 16, 2024 10:55
@Al2Klimov Al2Klimov requested a review from yhabteab September 17, 2024 09:26
yhabteab
yhabteab previously approved these changes Sep 17, 2024
Copy link
Member

@yhabteab yhabteab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from 9e2d6aa to c436e8d Compare September 26, 2024 16:41
@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from c436e8d to d51ae84 Compare September 30, 2024 14:26
Too high timestamps may overflow uint64_t (and the YYYY format) and negative
ones don't fit into uint64_t. Those may crash our Go daemon.
@Al2Klimov Al2Klimov force-pushed the IcingaDB-TimestampToMilliseconds-limit branch from d51ae84 to dc4869c Compare September 30, 2024 14:54
@julianbrost julianbrost merged commit 5e9e0bb into master Oct 2, 2024
26 checks passed
@julianbrost julianbrost deleted the IcingaDB-TimestampToMilliseconds-limit branch October 2, 2024 07:19
@Al2Klimov Al2Klimov added this to the 2.15.0 milestone Oct 23, 2024
@Al2Klimov Al2Klimov added the backported Fix was included in a bugfix release label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/icingadb New backend backported Fix was included in a bugfix release bug Something isn't working cla/signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants