jupyter-resource-usage
jupyter-resource-usage copied to clipboard
Allow users to opt out of prometheus metrics
Poor mans fix for #123
Thanks for submitting your first pull request! You are awesome! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.
You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
@kevin-bates good suggestion! done!
Hi @jtpio - I'm hoping you might be able to give this PR some attention relative to its review/merge/release as it will alleviate some heartburn for others.
In looking into this, I found that the lint tooling must have changed over (I'm assuming) its last major release and have provided PR #138 to address the linting failures evident on the various PRs - so it might be helpful to review/merge that PR prior to others.
I you need help, or I should be reaching out to someone else, please let me know. Thank you.
Thanks @kevin-bates for the ping, this looks good.
I used the GitHub button to rebase the branch to make sure to grab the fixes from https://github.com/jupyter-server/jupyter-resource-usage/pull/138:

Also this repo is compatible with the Jupyter Releaser so we can make a 0.6.2 release after merging this.
Actually @kevin-bates if you would like to make the release feel free to proceed. You should have publish access to PyPI already. And I can add you to npm if you give me your username (the JupyterLab extension is also published to npm for consistency): https://www.npmjs.com/package/@jupyter-server/resource-usage
Congrats on your first merged pull request in this project! :tada:
Thank you for contributing, we are very proud of you! :heart:
Hi @jtpio. I'm sorry, I don't currently have the bandwidth to revisit the jupyter-releaser stuff (I've used it once, probably late last year) and wouldn't want to mess things up. If you're unable to get to this in the next couple of days, I could probably spend some time with it on Friday. FWIW, my npm username is kbates.