-
Notifications
You must be signed in to change notification settings - Fork 102
Request response workspace #545
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
base: main
Are you sure you want to change the base?
Conversation
- Add tests for Greengrass samples: IPC and discovery. - Add new CI job for Greengrass tests.
* Bump braces from 3.0.2 to 3.0.3 Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) --- updated-dependencies: - dependency-name: braces dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> * update dependency --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [ws](https://github.com/websockets/ws) from 7.5.9 to 7.5.10. - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@7.5.9...7.5.10) --- updated-dependencies: - dependency-name: ws dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: GitHub Actions <[email protected]>
* Add refresh field to GetSecretValueRequest
Co-authored-by: GitHub Actions <[email protected]>
…on (via test script + npm calls)
} else if (err instanceof CrtError) { | ||
reject(createServiceError("??", err as CrtError)); | ||
} else { | ||
reject(createServiceError((err as Error).toString())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If deserialization fails, the error currently falls into createServiceError((err as Error).toString())
, but this might be misleading since it's not actually a service error. Should we consider handling deserialization errors through a different path or introduce a separate error type for clarity?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.