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.

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

check for raw["description"]["text"] for mc servers >= 1.9 #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

edwardslabs
Copy link
Member

No description provided.

@@ -139,8 +139,13 @@ def __init__(self, raw):

if "description" not in raw:
raise ValueError("Invalid status object (no 'description' value)")
self.description = raw["description"]
self.description_clean = re.sub(r'\u00A7.', '', raw["description"])
if "text" not in raw["description"]:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this attempt to subscript the value if raw["description"] was a string that contained the word "text"? I think an explicit type check may be safer in this case

@daboross
Copy link

Thank you for making this! I think this is covered by #1 though (if it's merged).

@astrutt
Copy link

astrutt commented May 31, 2017

Upgraded to the latest version, this issue is still not fixed. .mcping is non-functional, and a long standing bug.

.rekt get's merged in, and that spreads by default malicious links, but we can't seem to get .mcping fixes merged... that is strange...

Is that what this project has become? a malicious IRC bot?

@daboross
Copy link

@astrutt In honesty this IRC bot has not been the most supported, as none of the main contributors are working on this project anymore.

I'm attempting to at least do what I can, but I do not have access to all the repositories (mainly I don't have write access to mcstatus), and I don't have too much free time.

@astrutt
Copy link

astrutt commented May 31, 2017 via email

@daboross
Copy link

daboross commented May 31, 2017

Yeah, it's unfortunate. I can't really make that decision for you, I mean I'll support it as much as I can but that's not much. The other contributors that are semi-active now may be more available, but I don't believe there's anyone really providing full support for this.

I do apologies for the rekt urls, that was entirely my fault.

@edwardslabs
Copy link
Member Author

@astrutt There are several forks of CloudBot that are actively developed and maintained. Because @lukeroge was the original project owner those of us on the CloudBot development team have opted to maintain a steady state rather than introduce lots of new features that some of the other forks have implemented that may or may not fall outside of the scope of the original CloudBot.

@astrutt
Copy link

astrutt commented Jun 4, 2017 via email

@edwardslabs
Copy link
Member Author

I don't think any of the current maintainers have write access to the CloudBotIRC/mcstatus repo. You can however either fork the repo and add the fix yourself then update the CloudBot requirements.txt file to point to your fork, or you can change your requirements.txt file to point to my fork which has the fix.

replace https://github.com/CloudBotIRC/CloudBot/blob/master/requirements.txt#L3
with
git+https://github.com/edwardslabs/mcstatus.git@master

Of course this isn't the best solution but hopefully it will help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants