You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The Breaking Change (Cross-Version) check in PR 21841 fails with an oad runtime exception:
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 astype: integer, format: int32
so it makes sense to specify it in the example as an integer value.The text was updated successfully, but these errors were encountered: