-
-
Notifications
You must be signed in to change notification settings - Fork 422
docs: add a clear message uppon ban #3225
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3225 +/- ##
==========================================
- Coverage 68.69% 68.69% -0.01%
==========================================
Files 231 231
Lines 19214 19216 +2
==========================================
+ Hits 13199 13200 +1
- Misses 6015 6016 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
a906496
to
822412b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor wordsmithing, but otherwise looks all good. Thanks!
822412b
to
c297de9
Compare
This is ready for merging, I applied your language corrections and asked XMatch's maintainer to validate the message 🙂 |
Co-authored-by: Adam Ginsburg <[email protected]>
Thank you! |
Hi astroquery's devs 🙂
An abusive XMatch user with astroquery's user agent was banned from our servers today. This made me realize that there are no warnings nor explanations in the documentation about DDoS attacks in this module.
Our support email is also added to the error message and to the documentation so that we can un-ban the astronomers after helping improving their workflows.
The section in the documentation can be removed when there will be a new release, as people won't see the 403: Forbidden error anymore.