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.

Sign up for GitHub

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

Jump to bottom

sendgrid example memory potential leaks #416

Closed
uschen opened this issue Jul 5, 2017 · 1 comment
Closed

sendgrid example memory potential leaks #416

uschen opened this issue Jul 5, 2017 · 1 comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged.

Comments

@uschen
Copy link

uschen commented Jul 5, 2017 •
edited
Loading

testing the sendgrid example in cloud function. Basically only the web hook function (saving to the storage, not the bigquery) here is the graph:

screen shot 2017-07-05 at 10 45 57 am

# of calls:
screen shot 2017-07-05 at 10 46 43 am
@uschen uschen changed the title sendgrid example memory potential leak? sendgrid example memory potential leaks? Jul 5, 2017
@uschen uschen changed the title sendgrid example memory potential leaks? sendgrid example memory potential leaks Jul 5, 2017
@fhinkel
Copy link
Contributor

fhinkel commented Nov 8, 2018

Closed due to inactivity. Feel free to reopen if needed.

@fhinkel fhinkel closed this as completed Nov 8, 2018
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 6, 2020
This was referenced Dec 23, 2020
Open
Open
Open
Open
Open
This was referenced Sep 5, 2021
Open
Open
Open
Open
Open
@snyk-bot snyk-bot mentioned this issue Dec 16, 2021
Open
@snyk-bot snyk-bot mentioned this issue Mar 11, 2022
Open
NimJay pushed a commit that referenced this issue Nov 9, 2022
@release-please
chore(main): release 4.1.0 (#416)
4172a73 
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
This was referenced Nov 9, 2022
Closed
Closed
Merged
Closed
ace-n pushed a commit that referenced this issue Nov 17, 2022
@JustinBeckwith @bcoe
refactor: use explicit mocha imports (#416)
ee56d2c
@ace-n ace-n mentioned this issue Nov 17, 2022
Merged
ace-n pushed a commit that referenced this issue Nov 17, 2022
@JustinBeckwith
refactor: use explicit mocha imports (#416)
762a799
unforced pushed a commit that referenced this issue Nov 17, 2022
@release-please
chore: release 5.4.1 (#416)
ff2c0ca 
🤖 I have created a release \*beep\* \*boop\*
---
### [5.4.1](https://www.github.com/googleapis/nodejs-security-center/compare/v5.4.0...v5.4.1) (2021-08-17)


### Bug Fixes

* **deps:** google-gax v2.24.1 ([#415](https://www.github.com/googleapis/nodejs-security-center/issues/415)) ([aa77ac3](https://www.github.com/googleapis/nodejs-security-center/commit/aa77ac33ed9e20e75505fb4d31183a0f1f0d1f76))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
@unforced unforced mentioned this issue Nov 17, 2022
Merged
ace-n pushed a commit that referenced this issue Nov 17, 2022
@JustinBeckwith
refactor: use explicit mocha imports (#416)
cd8ff0b
ace-n pushed a commit that referenced this issue Nov 17, 2022
@JustinBeckwith
refactor: use explicit mocha imports (#416)
9a45d1d
ace-n pushed a commit that referenced this issue Nov 17, 2022
@JustinBeckwith
refactor: use explicit mocha imports (#416)
19c65e9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🚨 This issue needs some love. triage me I really want to be triaged.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fhinkel @uschen @yoshi-automation