Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

oad runtime exception caused by retry-after header with integer value

Open
#271 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, openapi
Domain
cli, tooling

Research direction

Start by reproducing the Breaking Change (Cross-Version) check from PR 21841 with an example response containing an integer retry-after header. Trace the runtime exception in the openapi-diff tool and verify that the check completes successfully while preserving the integer header value.

Written by the indexing model from the issue text.

Description

The Breaking Change (Cross-Version) check in PR 21841 fails with an oad runtime exception:

image

Through local experimentation I found that the runtime exception is caused by examples that contain a retry-after header in the response with an integer value.

The retry-after header is defined in the REST API as type: integer, format: int32 so it makes sense to specify it in the example as an integer value.

Dominant language
C#
Stars
290
Forks
50
Avg merge
2d 21h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/openapi-diff

All issues in Azure/openapi-diff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.