Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Invalid RFC-3339 date-time value when using client-medialive DescribeChannelCommand #6782

Open
3 of 4 tasks
brako opened this issue Jan 8, 2025 · 2 comments
Open
3 of 4 tasks
Assignees
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. p2 This is a standard priority issue

Comments

@brako
Copy link

brako commented Jan 8, 2025

Checkboxes for prior research

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

@brako brako added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 8, 2025
@zshzbh zshzbh self-assigned this Jan 8, 2025
@zshzbh zshzbh added the p2 This is a standard priority issue label Jan 8, 2025
@ptgamr
Copy link

ptgamr commented Jan 14, 2025

+1

1 similar comment
@harrietwaters
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

4 participants