orangeCatDeveloper opened a new pull request, #4333:
URL: https://github.com/apache/hertzbeat/pull/4333

   Fixes #3052
   
   A public status page cannot show more than 90 days of availability history.
   
   ## What's changed?
   
   PR #4222 added the 1-90 day dropdown; this raises the backend cap to 365 
(both query paths in `StatusPageServiceImpl`) and adds 60/180/365 options.
   
   Rendering: history blocks use `flex: 1` with a 2px gap, so 365 blocks mean 
~728px of pure gap in a ~900px wide container - sub-pixel, invisible blocks. 
Spans over 90 days now render as a contiguous strip (no gap, no rounding); 90 
days and below keep the exact current look.
   
   Note: the unauthenticated public endpoint's lazy history merge (deleteAll + 
save per missing day) runs up to 365 write rounds on the first query of a long 
span - pre-existing pattern, idempotent, later queries take the size==1 fast 
path.
   
   30 / 90 days (unchanged look):
   
   <img width="1512" height="736" alt="after-30days" 
src="https://github.com/user-attachments/assets/c957dbe5-379e-494d-806b-ff987d52e2e4";
 />
   <img width="1512" height="736" alt="after-90days" 
src="https://github.com/user-attachments/assets/ecb3d343-3afe-4f87-9cb4-bbee76765580";
 />
   
   180 / 365 days (contiguous strip):
   
   <img width="1512" height="736" alt="after-180days" 
src="https://github.com/user-attachments/assets/160bac20-5a42-47cd-b6e1-9d5dbc4b32ac";
 />
   <img width="1512" height="736" alt="after-365days" 
src="https://github.com/user-attachments/assets/777d563f-5da1-4ece-9a54-a564c8ed609c";
 />
   
   ## Checklist
   
   - [x] I have read the [Contributing 
Guide](https://hertzbeat.apache.org/docs/community/code_style_and_quality_guide)
   - [ ] I have written the necessary doc or comment.
   - [x] I have added the necessary unit tests and all cases have passed.
   
   ## Add or update API
   
   - [ ] I have added the necessary [e2e 
tests](https://github.com/apache/hertzbeat/tree/master/e2e) and all cases have 
passed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to