Skip to content

Code should guard against there not yet being a "next" ietf meeting in the database #3370

@ietf-svn-bot

Description

@ietf-svn-bot

resolution_fixed type_defect | by rjsparks@nostrum.com


At the moment, the submit and expire-id functions are breaking because IETF 112 is not yet in the database.

The code should handle that case with more grace


Issue migrated from trac:3370 at 2022-03-04 09:10:17 +0000

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions