3 ms·
Your python sdk's <https://pypi.org/project/sift-dev-logger https://pypi.org/project/sift-dev-logger> GH link is 404: <https://github.com/sift-dev/python-sdk ht
by mdaniel 2y ago
Your python sdk's <https://pypi.org/project/sift-dev-logger https://pypi.org/project/sift-dev-logger> GH link is 404: <https://github.com/sift-dev/python-sdk https://github.com/sift-dev/python-sdk> Navigating upward shows the fork of SigNoz which I think is funny
There was no GH link for your npm dep so maybe they're both private. Although npmjs shows your npm one as ISC licensed, likely because of the default in package.json
- Akula112233 2y agoAh, any particular reason to want these SDKs public? Happy to, especially since you can see source on install anyway. Just curious! And Kudos to SigNoz as well - have to check out other folks in the space :)
- mdaniel 2y agoMy initial concern was what transitive deps it was pulling in, but the other answer to your question is the thing that most GH repos are good for: submitting bugs and submitting fixes It is also good for finding out what the buffering story is, because I would want to know if I'm dragging in an unbounded queue into my app (putting memory pressure on me) or knowing that your service returning 503s is going to eat logs. The kind of thing that only looking at the source would say for sure because the docs don't even hint at such operational concerns Anyway, the only reason I mentioned the dead link is because your PyPI page linked to GH in the first place. So if you don't intend people to think there's supposed to be a repo, then I'd suggest removing the repo link
- Akula112233 2y agoNoted, thank you! Will make some changes accordingly.