-
Notifications
You must be signed in to change notification settings - Fork 51
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
Fix socket leak #55
Fix socket leak #55
Conversation
Hey @Nick-Triller, just built from your branch and deployed in sandbox, but I started getting these errors:
The exporter is returning some of the metrics, but looks like some collectors are failing. Any ideas? |
Hi @dkulchinsky, that's interesting, I am not seeing anything like that. Before I start looking into this, could you please test head of master, too? |
Hey @Nick-Triller, thanks for replying! my bad here... sorry for the noise 🤦 had an issue with password injection, so no more 401 errors. though I'm confused why the exporter was still able to retrieve "some" of the data, I suppose some api endpoints do not require auth? anyway, will monitor memory usage for a while and report back. this seems unrelated but was still getting this error on every scrape:
managed to "fix" it by reducing pageSize:
name: page_size
in: query
type: integer
format: int64
required: false
description: The size of per page
default: 10
maximum: 100 I'll open a separate issue for this. |
@Nick-Triller this has been running for 12 hours now and seems solid to me, great job 👍 @c4po would be awesome if this could be merged 🙏 |
@Nick-Triller @dkulchinsky thanks for your help. I'll try to get on this tonight or tomorrow. |
Hi,
this MR fixes the socket leak reported in #52 and #45
Additionally, I refactored some of the code minimally. I took care to create succinct commits.
Thanks
Nick