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

(Title renamed to remove explicit language) #36095

Closed
emergy opened this issue Feb 13, 2018 · 11 comments

Comments

@emergy
Copy link

commented Feb 13, 2018

command = dict(v4=[route_path, '-n', 'get', '8.8.8.8'],

@ansibot

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2018

@emergy Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

  • issue type
  • ansible version
  • component name

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

@iavael

This comment has been minimized.

Copy link

commented Feb 13, 2018

Don’t be so agitated. It’s just a lookup for route in local routing table, no network queries are actually performed.

@ivladdalvi

This comment has been minimized.

Copy link

commented Feb 13, 2018

Possibly, using a more generic "route -n get 0.0.0.0/0" would be a better way of finding the default route. Using a well-known address is not necessarily a good practice.

@duke66

This comment has been minimized.

Copy link

commented Feb 13, 2018

ipv6 default route lookup is also broken "v6=[route_path, '-n', 'get', '-inet6', '2404:6800:400a:800::1012'])"

@Akasurde Akasurde closed this Feb 13, 2018

@polkovnikov-ph

This comment has been minimized.

Copy link

commented Feb 13, 2018

@Akasurde Wow, was it fixed that fast?

@Akasurde

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@polkovnikov-ph $title seems offensive so I closed it.

@webknjaz

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@emergy Ansible community heavily relies on Code of Conduct being followed, which lets us address issues more effectively and be respectful to each other. Posting issues with offensive content is definitely not going to encourage productive discussion, but normally results in confrontation.
For best outcome please consider writing your messages mindfully and calmly explaining both your problem and what is the suggested resolution or expectation for it.
TIA.

@polkovnikov-ph

This comment has been minimized.

Copy link

commented Feb 13, 2018

@Akasurde I don't see how offensive title makes it less of an issue. The code in the issue seems self-descriptive to several people in this thread. Do you really need any additional feedback from issue author?

@Akasurde

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@polkovnikov-ph I agree that this an issue. But there is a certain way to describe an issue in Open Source Community. Using sexual abusive language is not the way to express your opinion.

@Akasurde

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@polkovnikov-ph Please refer Code of Conduct for more details.

@webknjaz

This comment has been minimized.

Copy link
Member

commented Feb 13, 2018

@polkovnikov-ph please feel free to create a new issue with well-stated problem. Your assumption about that it's self-descriptiveness is only partially correct when you refer to several ppl you mentioned. Still, there are lots of other people who won't understand it. I myself try avoiding to assume that other people see and understand things exactly the same way as me, because every individual has their own unique experience. That said I encourage you to not make such assumptions here.
I'm locking this issue, since I don't see what can be done here to turn it into an effective conversation.

If you'd like to contribute into the issue resolution, I encourage you to file another issue with clear description of the problem. Thanks and have a nice day!

@ansible ansible locked as too heated and limited conversation to collaborators Feb 13, 2018

@mkrizek mkrizek removed the needs_triage label Feb 16, 2018

@sivel sivel changed the title Вы ебанулись?? (Title renamed to remove explicit language) Feb 21, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
9 participants
You can’t perform that action at this time.