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

feat: leverage errors types for tracing #5365

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

4xposed
Copy link
Contributor

@4xposed 4xposed commented Nov 6, 2023

🎉 Thanks for submitting a pull request! 🎉

Summary

Fixes https://linear.app/netlify/issue/COM-91/leverage-error-types-in-netlifybuild

@4xposed 4xposed requested review from a team as code owners November 6, 2023 12:18
@4xposed 4xposed force-pushed the daniel/com-91-leverage-error-types-in-netlifybuild branch from 4962a23 to 4f29043 Compare November 6, 2023 12:18
Copy link
Contributor

github-actions bot commented Nov 6, 2023

This pull request adds or modifies JavaScript (.js, .cjs, .mjs) files.
Consider converting them to TypeScript.

Comment on lines +36 to +41
const {
errorInfo: { location: { packageName } = {} },
message,
title,
type,
} = fullErrorInfo
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +58 to +63
const cancellationAttributes = {
'build.cancellation.title': title,
'build.cancellation.message': message,
'build.cancellation.packageName': packageName,
}
addEventToActiveSpan('build.cancelled', cancellationAttributes)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding a mental note that we'll want to test this out once it lands in prod 👌

@4xposed 4xposed merged commit f6bb421 into main Nov 6, 2023
35 checks passed
@4xposed 4xposed deleted the daniel/com-91-leverage-error-types-in-netlifybuild branch November 6, 2023 13:30
This was referenced Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants