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

Do not assume APM exists #697

Merged
merged 2 commits into from
Mar 12, 2024
Merged

Do not assume APM exists #697

merged 2 commits into from
Mar 12, 2024

Conversation

jpage-godaddy
Copy link
Contributor

@jpage-godaddy jpage-godaddy commented Mar 12, 2024

  • Since gasket.apm is not initialized for the local command, fix its type
  • Do not inject transaction renaming middleware when gasket.apm is undefined
  • Run npm audit fix

Summary

Customer reported that they got a TypeError due to the transaction renaming middleware of @gasket/plugin-elastic-apm. Support thread for context.

Changelog

  • (fix) handle case when APM is not available

Test Plan

Added unit test

- Since `gasket.apm` is not initialized for the `local` command, fix its type
- Do not inject transaction renaming middleware when `gasket.apm` is undefined
@jpage-godaddy jpage-godaddy requested a review from a team as a code owner March 12, 2024 16:22
Copy link
Contributor

package-lock.json changes

Click to toggle table visibility
Name Status Previous Current
ip UPDATED 2.0.0 2.0.1
jsdoc-parse UPDATED 6.1.0 6.2.1
lodash.pick REMOVED 4.4.0 -
lodash.set REMOVED 4.3.2 -
nock UPDATED 13.2.4 13.5.4
search-insights ADDED - 2.13.0
wait-on ADDED - 7.0.1

@kbader-godaddy kbader-godaddy merged commit b70ed25 into main Mar 12, 2024
4 checks passed
@kbader-godaddy kbader-godaddy deleted the no-apm-assumption branch March 12, 2024 16:53
agerard-godaddy pushed a commit that referenced this pull request Apr 17, 2024
(cherry picked from commit b70ed25)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants