Closed Bug 278238 Opened 20 years ago Closed 20 years ago

recurrence stops after 2037

Categories

(Calendar :: Internal Components, defect)

Product:
Calendar
Component:
Internal Components
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mvl, Assigned: vlad)

Details

Attachments

(2 files)

testcase
962 bytes, text/plain
Details
patch
1.03 KB, patch
vlad
: first-review+
Details | Diff | Splinter Review 
when an event recurs yearly, it stops after 2037. testcase coming
Attached file testcase — 

    
    

    
  

      
      
      
      

        Attached patch
          
          
        patch
        — 
          — Splinter Review
      

    


  
This patch removed the check to stop after 2037 from libical. I can't find a
real reason for that check, since everything else there looks safe. No use of
time_t.

        Attachment #171293 -
        Flags: first-review?(vladimir)

    
    

    
  
Comment on attachment 171293 [details] [diff] [review]
patch

Looks fine to me; I'm guessing the check was there since any dates > 2037 won't
be convertable to time_t.  Perhaps the icaltime_* functions that convert to
time_t should check for > 2037 and bomb out?

        Attachment #171293 -
        Flags: first-review?(vladimir) → first-review+

    
    

    
  
patch checked in
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: