• 
      

    Add a new cancelled state for status updates.

    Review Request #14466 — Created June 20, 2025 and submitted

    Information

    Review Board
    release-7.1.x

    Reviewers

    This change adds a new cancelled state that can be set for status
    updates. At the moment, this displays the same as error states, but it
    has a default description of "cancelled" (for updates that do not have
    explicit description text set), and it does not show a "Retry" button
    for services that allow manually triggering retries.

    • Ran unit tests.
    • Used this in conjunction with some code in rbintegrations.
    Summary ID
    Add a new cancelled state for status updates.
    This change adds a new cancelled state that can be set for status updates. At the moment, this displays the same as error states, but it has a default description of "cancelled" (for updates that do not have explicit description text set), and it does not show a "Retry" button for services that allow manually triggering retries. Testing Done: - Ran unit tests. - Used this in conjunction with some code in rbintegrations.
    659f6d13470c75e053c29daafa34b56d77229574
    Description From Last Updated

    This is harder to read. Can we stick to one per line?

    chipx86chipx86

    I don't know what it is but this form of if statement just looks like a syntax error to me …

    chipx86chipx86
    chipx86
    1. 
        
    2. reviewboard/reviews/detail.py (Diff revision 1)
       
       
       
      Show all issues

      This is harder to read. Can we stick to one per line?

    3. 
        
    david
    maubin
    1. Ship It!
    2. 
        
    chipx86
    1. 
        
    2. reviewboard/reviews/detail.py (Diff revisions 1 - 2)
       
       
       
       
       
       
       
      Show all issues

      I don't know what it is but this form of if statement just looks like a syntax error to me every time, like some line got missed.

      We normally use this form for this kind of comparison:

      if state in {...,
                   ...,
                   ...}:
          ...
      

      But I had another thought. Since we're going through this series of lookups and conditionals for every single StatusUpdate on one of the most-used pages in Review Board, perhaps we should just make a type-to-class map and do a direct lookup from that. That'd reduce complexity of this call path a fair amount.

    3. 
        
    david
    maubin
    1. Ship It!
    2. 
        
    chipx86
    1. Ship It!
    2. 
        
    david
    Review request changed
    Status:
    Completed
    Change Summary:
    Pushed to release-7.1.x (bae76d3)