-
Notifications
You must be signed in to change notification settings - Fork 634
Closed
Labels
bugThis issue is a bug.This issue is a bug.closed-for-stalenessp2This is a standard priority issueThis is a standard priority issueservice-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.
Description
Checkboxes for prior research
- I've gone through Developer Guide and API reference
- I've checked AWS Forums and StackOverflow.
- I've searched for previous similar issues and didn't find any solution.
Describe the bug
The DescribeChannelCommand throws an error Invalid RFC-3339 date-time value. The request itself is successful with an http code 200, but the response body fails to deserialize due to an invalid date format.
Regression Issue
- Select this option if this issue appears to be a regression.
SDK version number
@aws-sdk/[email protected]
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v20.17.0
Reproduction Steps
import {
MediaLiveClient,
DescribeChannelCommand
} from '@aws-sdk/client-medialive';
const mediaLiveClient = new MediaLiveClient({
region: 'region' // <= replace here with a aws region
});
const input = {
ChannelId: 'id' // <= replace here with a channel ID
};
// Throws an exception
await mediaLiveClient.send(new DescribeChannelCommand(input));
Observed Behavior
TypeError: Invalid RFC-3339 date-time value
Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.
at parseRfc3339DateTimeWithOffset (...\node_modules\@aws-sdk\client-medialive\node_modules\@smithy\smithy-client\dist-cjs\index.js:631:11)
at ExpirationDate (...\node_modules\@aws-sdk\client-medialive\dist-cjs\index.js:8524:127)
at applyInstruction (...\node_modules\@aws-sdk\client-medialive\node_modules\@smithy\smithy-client\dist-cjs\index.js:1105:27)
at take (...\node_modules\@aws-sdk\client-medialive\node_modules\@smithy\smithy-client\dist-cjs\index.js:1073:5)
at de_ChannelEngineVersionResponse (...\node_modules\@aws-sdk\client-medialive\dist-cjs\index.js:8523:40)
at ChannelEngineVersion (...\node_modules\@aws-sdk\client-medialive\dist-cjs\index.js:9973:37)
at applyInstruction (...\node_modules\@aws-sdk\client-medialive\node_modules\@smithy\smithy-client\dist-cjs\index.js:1105:27)
at take (...\node_modules\@aws-sdk\client-medialive\node_modules\@smithy\smithy-client\dist-cjs\index.js:1073:5)
at de_PipelineDetail (...\node_modules\@aws-sdk\client-medialive\dist-cjs\index.js:9968:40)
at ...\node_modules\@aws-sdk\client-medialive\dist-cjs\index.js:8055:12 {
'$metadata': { attempts: 1, totalRetryDelay: 0 }
Expected Behavior
Expected behavior is to receive the description of the channel.
Possible Solution
As a workaround we can use the ListChannelsCommand
and filter the result manually with the channel id. The ListChannelsCommand
is not affected by the issue.
Additional Information/Context
No response
torrottum
Metadata
Metadata
Assignees
Labels
bugThis issue is a bug.This issue is a bug.closed-for-stalenessp2This is a standard priority issueThis is a standard priority issueservice-apiThis issue is due to a problem in a service API, not the SDK implementation.This issue is due to a problem in a service API, not the SDK implementation.