using HA getting errors in log:

would love to resolve the following issues :
http://hastebin.com/munoxoxube.sql

Having the same issue with Nighthawk X4 R7500v2 router

Same issue with Nighthawk R8000 on firmware V<IP_ADDRESS>_1.1.18

Same issue with R6300v2 on firmware V<IP_ADDRESS>_1.0.63CH. It does display devices if calling pynetgear and providing the password only. In HA there are no more exceptions if providing the password only but HA still fails to login.

Dear @balloob I could really use your help on this one... I've been getting errors on the pynetgear code from a few months now and device tracking is really bad - none working...
I am trying to figure out what's wrong and I made some extra debug notification which you can see in the following link: https://hastebin.com/tejidamija.swift
What am I doing wrong ?
(tried with host as IP / URL... different ports... removed from configuration and tried all sorts of combinations - it's either my configuration that's messing things up or something in the code I guess...
(I see 0.3.3 on the deps folder)
hope you get around to this soon ;)
and thanks for all your hard work on this project (HA) !

I've learned not to trust the netgear component and using nmap as "permanent backup" although I'd much prefer to use something dedicated to my router...
(Currently on 48.1)
If there is anything I can provide to assist in making this component work - please do not hesitate to ask.
This is what is currently setup with (tried many variation but never got it working properly and reliably) followed by the log messages (device tracker component set to debug)
device_tracker:
  - platform: netgear
    host: <IP_ADDRESS>
    username: !secret netgear_user
    password: !secret netgear_pass

2017-07-12 07:10:53 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.netgear
2017-07-12 07:10:53 INFO (Thread-10) [homeassistant.components.device_tracker.netgear] Logging in
2017-07-12 07:10:53 ERROR (Thread-10) [homeassistant.components.device_tracker.netgear] Failed to Login
2017-07-12 07:10:53 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform netgear

@Amir974
The nmap "workaround" seems to be like driving through every street in town instead of asking for an address/map  😩
To isolate the problem: Is it possible for you to connect to the router via pynetgear only?
pip3 install pynetgear
python3 -m pynetgear [<pass>] [<host>] [<user>] [<port>]
If this does not work:
@pgross41 suggested to provide a password and NO User (which should default to user admin).
HA-Related:
Please be aware that in HA 0.48.1 there seems to be a conflict with the autodiscovery/manual config. This can be solved by adding this to you config.yml:
(See HA Issue #4318)
discovery:
ignore:
- netgear_router

I was able to get my netgear nighthawk (Nighthawk X4 R7500v2) router
working with the below configuration:
device_tracker:

platform: netgear
host: routerlogin.net
username: !secret netgear_user
password: !secret netgear_password
port: 80

David Halladay
Email<EMAIL_ADDRESS>Mobile:<PHONE_NUMBER>
On Wed, Jul 12, 2017 at 3:45 AM, ArneCL<EMAIL_ADDRESS>wrote:

@Amir974 https://github.com/amir974
The nmap "workaround" seems to be like driving through every street in
town instead of asking for an address/map 😩
To isolate the problem: Is it possible for you to connect to the router
via pynetgear only?
pip3 install pynetgear
python3 -m pynetgear [] [] [] []
If this does not work:
@pgross41 https://github.com/pgross41 suggested to provide a password
and NO User (which should default to user admin).
HA-Related:
Please be aware that in HA 0.48.1 there seems to be a conflict with the
autodiscovery/manual config. This can be solved by adding this to you
config.yml:
(See HA Issue #4318)
https://github.com/home-assistant/home-assistant/issues/4318
discovery:
ignore:

netgear_router

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/balloob/pynetgear/issues/9#issuecomment-314683304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnXZAXfhfh_kfJGJpOWeS1yKqq5jWuaks5sNHmJgaJpZM4KsoeV
.

I still have the issues with HA I believe. I have not looked lately. However, I dont have the port set. Everything works fine I believe. It just gives random error messages in the HA logs. I will try adding the port reference tonight for kicks.

@ArneCL  After installing pynetgear and attempting to run i got the following:
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear [123456] [192.1681.1] [abcdefg] [80]
Error talking to API
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/models.py", line 374, in prepare_url
    scheme, auth, host, port, path, query, fragment = parse_url(url)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/url.py", line 199, in parse_url
    raise LocationParseError(url)
requests.packages.urllib3.exceptions.LocationParseError: Failed to parse: :[80]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/pynetgear/__init__.py", line 113, in _make_request
    self.soap_url, headers=headers, data=message, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 112, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 504, in request
    prep = self.prepare_request(req)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 436, in prepare_request
    hooks=merge_hooks(request.hooks, self.hooks),
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/models.py", line 302, in prepare
    self.prepare_url(url, params)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/models.py", line 376, in prepare_url
    raise InvalidURL(*e.args)
requests.exceptions.InvalidURL: Failed to parse: :[80]
Error communicating with the Netgear router
(homeassistant) homeassistant@rpi-3:/home/pi $ exit
exit

Running without port produced the following:
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear [123456] [192.1681.1] [abcdefg]
Error talking to API
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/lib/python3.4/socket.py", line 530, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 356, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1090, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 859, in send
    self.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.HTTPConnection object at 0x7636ec90>: Failed to establish a new connection: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 649, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.1681.1', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7636ec90>: Failed to establish a new connection: [Errno -2] Name or service not known',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/pynetgear/__init__.py", line 113, in _make_request
    self.soap_url, headers=headers, data=message, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 112, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 502, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.1681.1', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7636ec90>: Failed to establish a new connection: [Errno -2] Name or service not known',))
Error communicating with the Netgear router

Running with routerlogin.net and no port produced the following:
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear [123456] [routerlogin.net] [abcdefg]
Error talking to API
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 83, in create_connection
    raise err
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
OSError: [Errno 101] Network is unreachable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 356, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1090, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 859, in send
    self.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.HTTPConnection object at 0x76378c90>: Failed to establish a new connection: [Errno 101] Network is unreachable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 649, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='routerlogin.net', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76378c90>: Failed to establish a new connection: [Errno 101] Network is unreachable',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/pynetgear/__init__.py", line 113, in _make_request
    self.soap_url, headers=headers, data=message, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 112, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 502, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='routerlogin.net', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76378c90>: Failed to establish a new connection: [Errno 101] Network is unreachable',))
Error communicating with the Netgear router

@Amir974
Thanks for your efforts - I think there is an error in the command you tried:
Instead of:
$ python3 -m pynetgear [123456] [192.1681.1] [abcdefg] [80]

it should be:
$ python3 -m pynetgear 123456 192.1681.1 abcdefg 80

No brackets!
(I should have included an example - sorry! 🙈 )

@ArneCL
Thanks for looking deeper,
unfortunately removing the "[]" did not help as you can see below,
However, I do see improvement in the HA log with some success calls - but still see lots of warnings over time about failed scans --- I've taken a sample from the log - see the following hastebin  - it continues with such warnings from that point on
https://hastebin.com/exalilohep.css
command line error for the correct input:
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear 123456 192.1681.1 abcdefg 80                                                               Error talking to API
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/lib/python3.4/socket.py", line 530, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 356, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1090, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 859, in send
    self.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.HTTPConnection object at 0x76313cd0>: Failed to establish a new connection: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 649, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.1681.1', port=80): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76313cd0>: Failed to establish a new connection: [Errno -2] Name or service not known',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/pynetgear/__init__.py", line 113, in _make_request
    self.soap_url, headers=headers, data=message, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 112, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 502, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.1681.1', port=80): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76313cd0>: Failed to establish a new connection: [Errno -2] Name or service not known',))
Error communicating with the Netgear router

wrong paste : see here...
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear 123456 <IP_ADDRESS> abcdefg
Error talking to API
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 83, in create_connection
    raise err
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/connection.py", line 73, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 356, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/lib/python3.4/http/client.py", line 1090, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1128, in _send_request
    self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1086, in endheaders
    self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 924, in _send_output
    self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 859, in send
    self.connect()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 166, in connect
    conn = self._new_conn()
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.HTTPConnection object at 0x76378cb0>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 438, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py", line 649, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
requests.packages.urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='<IP_ADDRESS>', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76378cb0>: Failed to establish a new connection: [Errno 111] Connection refused',))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/pynetgear/__init__.py", line 113, in _make_request
    self.soap_url, headers=headers, data=message, timeout=10)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 112, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 518, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/sessions.py", line 639, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/requests/adapters.py", line 502, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=5000): Max retries exceeded with url: /soap/server_sa/ (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x76378cb0>: Failed to establish a new connection: [Errno 111] Connection refused',))
Error communicating with the Netgear router

@Amir974: When running
python3 -m pynetgear 123456 <IP_ADDRESS> abcdefg you need to add the Port (80) - in the logs you posted, the default-value for the port (i.e. 5000) is used.
As @davehalladay already confirmed, pynetgear seems to generally work for HA & Nighthawk routers.
With regards to polluted HA-Logs, please note the comment from earlier on:

HA-Related:
Please be aware that in HA 0.48.1 there seems to be a conflict with the autodiscovery/manual config. This can be solved by adding this to you config.yml:
(See HA Issue #4318)
discovery:
ignore:
- netgear_router

Got it,
I've added the discovery ignore and this is the (short) outcome of running the command line with the port:
(homeassistant) homeassistant@rpi-3:/home/pi $ python3 -m pynetgear 123456 <IP_ADDRESS> abcdefg 80
Error communicating with the Netgear router

HA Log looks like this:

2017-07-14
  19:47:30 INFO (MainThread) [homeassistant.components.device_tracker] Setting
  up device_tracker.netgear
--
2017-07-14 19:47:31 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Logging in
2017-07-14 19:47:34 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:47:46 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:47:59 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:48:12 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:48:12 INFO
  (MainThread) [homeassistant.components.device_tracker] Setting up
  device_tracker.netgear
2017-07-14 19:48:12 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Logging in
2017-07-14 19:48:12 ERROR
  (Thread-1) [homeassistant.components.device_tracker.netgear] Failed to Login
2017-07-14 19:48:12 ERROR
  (MainThread) [homeassistant.components.device_tracker] Error setting up
  platform netgear
2017-07-14 19:48:24 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:48:37 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:48:50 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:49:03 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:49:16 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:49:40 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:49:53 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:50:06 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:50:19 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:50:32 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:50:45 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:50:58 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:51:11 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:51:24 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:51:37 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:51:50 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:52:03 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:52:16 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:52:29 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:52:42 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:52:55 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:53:08 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:53:21 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:53:34 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:53:47 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:54:00 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:54:13 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:54:26 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:54:38 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:54:51 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:55:04 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:55:17 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:55:30 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:55:43 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:55:56 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:56:09 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:56:22 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:56:35 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:56:48 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:57:01 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:57:14 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:57:27 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:57:40 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:57:53 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:58:06 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:58:19 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:58:32 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:58:45 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:58:58 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:59:11 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:59:24 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:59:37 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 19:59:50 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:00:03 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:00:16 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:00:29 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:00:42 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:00:55 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:01:08 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:01:21 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:01:34 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:01:47 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:01:59 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:02:12 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:02:25 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:02:38 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:02:51 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:03:04 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:03:17 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:03:30 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:03:43 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:03:56 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:04:09 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:04:22 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:04:35 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:04:48 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:05:01 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:05:14 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:05:27 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:05:40 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:05:53 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:06:06 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:06:19 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:06:32 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:06:45 INFO
  (Thread-1) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:06:58 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:07:11 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:07:24 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:07:37 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:07:50 INFO
  (Thread-12) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:08:03 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:08:16 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:08:29 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:08:42 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:08:55 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:09:08 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:09:21 INFO
  (Thread-5) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:09:34 INFO
  (Thread-9) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:09:47 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:10:00 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:10:13 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:10:26 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:10:39 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:10:52 INFO
  (Thread-6) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:11:05 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:11:18 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:11:31 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:11:44 INFO
  (Thread-3) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:11:57 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:12:10 INFO
  (Thread-10) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:12:23 INFO
  (Thread-4) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:12:36 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:12:49 INFO
  (Thread-8) [homeassistant.components.device_tracker.netgear] Scanning
2017-07-14 20:13:02 INFO
  (Thread-7) [homeassistant.components.device_tracker.netgear] Scanning


M1 Mac Build issue

Problem
Follow the wiki here: https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/BUILDING.md
at ninja -C out/host see the following: https://rentry.co/b5nu4
It appears my laptop wants to target the x86_64 architecture even though I am running an arm64 architecture. I tried setting the target_cpu option to no avail. Any suggestions on how to resolve?

Duplicate of #19134

thanks for the heads up, I will track this in the other issue


Incomplete sentence?

Regarding

You can create custom configurations from different entry points, such as from the Apache Spark configurations page, from the Apache Spark configuration page of an existing spark pool.

This sentence seems incomplete / the options listed seem the same. Can you please clarify and reword as appropriate?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: ab637373-71e0-ef91-db1b-2f9d4141a93c
Version Independent ID: fa643994-52c8-0c94-4438-05ad4b17e9d7
Content: Manage Apache Spark configuration - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/apache-spark-azure-create-spark-configuration.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @Jejiang
Microsoft Alias: jejiang

@VitalyMCT
Thanks for your feedback! We will investigate and update as appropriate.

@VitalyMCT
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.

@VitalyMCT
PR has been done. Please see this reference
https://github.com/MicrosoftDocs/azure-docs-pr/pull/234819


[bug] CLI install method creates conflicting "guardrails" directories

Description:
I cloned the Guardrails AI repository and attempted to install a validator using the CLI. However, I noticed the following issue:
The install method created an additional "guardrails" folder in the site-packages directory inside my virtual environment.
This new folder contains the installed validator along with its dependencies, but it leads to an import conflict. There are now two directories named "guardrails" (one in the cloned repo and another in site-packages).
Due to this conflict, I’m unable to import the validator directly without ambiguity.
Expected Behavior:
I’d like to install the validator within the original "guardrails" repository directory instead of creating a new "guardrails" directory in site-packages.
Environment:
OS: Windows
Python version: 3.12

you should only need to install guardrails from pypi. See more info here https://www.guardrailsai.com/docs/getting_started/quickstart

The directory conflict is a known limitation of the python module system.  The flow described the in "Expected Behavior" section is not supported.  As @dtam mentioned, the correct usage is described in the quickstart guide in the docs and starts with installing guardrails in an environment separate from the guardrails repository.


ci: remove duplicates in CI scripts

Description

Currently, there are many duplicates in CI scripts, which has high maintenance costs.
I'd like to improve it by using Reusable Workflows.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Mm, it's difficult to commonize the workflows of GitHub-hosted and self-hosted (the matrix condition makes things more complicated).
It might be better to create a pre-commit hook like sync-files. :thinking:

I'll close this for now.


Fix Issue 21337: Join can iterate ranges multiple times

Great catch. Part of me cringes at the bludgeon used here (changing anything that's not the target array type into the target array type), but that's a different fix.


There are some problems when caching vcpkg on windows-2016

I want to cache vcpkg, it is successful on windows-2019, but there are some problems on windows-2016.
 - name: Cache Depends
        id: cache-depends
        uses: actions/cache@v2
        with:
          path: C:\vcpkg\installed\x64-windows
          key: ${{ matrix.os }}-vcpkg

Run action for the first time
https://github.com/wangsongc/action-test/runs/715286404?check_suite_focus=true
Post job cleanup.
"C:\Program Files\Git\usr\bin\tar.exe" --use-compress-program "zstd -T0" -cf cache.tzst -P -C D:/a/action-test/action-test --files-from manifest.txt --force-local
/usr/bin/tar: C\:\vcpkg\\installed\\x64-windows: Cannot stat: No such file or directory
/usr/bin/tar: Exiting with failure status due to previous errors
[warning]Tar failed with error: The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2

Run action for the second time
https://github.com/wangsongc/action-test/runs/715319270?check_suite_focus=true
Post job cleanup.
[warning]reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: windows-2016-vcpkg, Version: f43601b869e409297d844610c90c97a34e4dcf31116c5b1ab37d82956a75fda4

+1

I can reproduce this.

I see this too.

I see this too.


feat(ingest): Glue jobs

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable)

LGTM. Thanks!


Review required changes for private endpoints configuration

I have confirmed the solution can work with Private endpoints. No issues. Have to document details.

Tested and documented


Frontend builds broken

What is it?
This is a post-hoc issue.
Frontend builds were broken due to some issues related to some marts changes. This is related to #1211 and #1212 which were also part of the fixes for this.

Closed by: #1187 #1186 #1183 #1189
Also #1211 and #1212


(graphviz) new updater for cmake/msbuild & stable/development

@AdmiringWorm @gep13 @pascalberger @majkinetor
/cc @smattr @magjac
Description

This will introduce the new package of graphviz-cmake along with --pre builds for the msbuild & cmake
This is still an embedded package.
Motivation and Context

This will fix issue #1528 plus add new package graphviz-cmake
How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[ ] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[x] Issue 1 #1528
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

:white_check_mark: Package verification completed without issues. PR is now pending human review

Thanks for updating this, @RedBaron2. Some initial high level comments:

It's great that the whitespace changes are gone. Thanks for addressing this. However, this PR now doesn't touch the license files at all. Is there an established Chocolatey procedure for what to do when the upstream license changes between releases?
The PR contains a number of .tmp files that get renamed/copied to filenames with other extensions. Is there a reason these don't have the destination extension to begin with? Maybe this is a Chocolatey convention. My level of understanding of Chocolatey is very minimal.
The verification files now have no files or checksums listed. Is this the norm? It seems unclear what a user would do with these files or what they would learn by reading them.

@Smattr
I'll try to address your concerns in order

The license files are the same ones used currently in the repository. Since these are unchanged. I saw no need to replace/reupload them with my PR.

The.tmp files are renamed because they are template files. These are only used by AU to make the files required to make a proper chocolatey package. These are not included in the final packaged .nupkg file.

The blanked out verification files will be filled with the proper information when ran by AU update. Please, take a look at the appveyor run and download the .nupkg file to find out how it looks when finished. The .nupkg files are nothing more the a fancy named .zip file.

Thanks, @RedBaron2. I think that explains (2) and (3) to me. When you say "currently in the repository," you mean this repository? My point was that automatic/graphviz/legal/LICENSE.txt does not match the upstream Graphviz license. Surely these are intended to agree?

Surely these are intended to agree?

Yes, if so, the latest license should be added in the package.

@Smattr @majkinetor
The latest License file is now uploaded and part of this PR

:white_check_mark: Package verification completed without issues. PR is now pending human review

@majkinetor @AdmiringWorm
Just a reminder that this needs to be checked.
Thanks for the assistance.

I believe you need to call dot -c after installation to generate config file.

I believe you need to call dot -c after installation to generate config file.

Correct, although in next release we will remove this need.

OK, then no change is needed.

Why would users care for cmake vs msbuild ? Users want tool that works, not tool built in particular engine. I think cmake should become next version and msbuild should be abandoned. Furthermore, this separation makes package code needlessly complex.

Why would users care for cmake vs msbuild ?

Historically, MSBuild was used to build Graphviz for Windows, but a couple of years ago it was decided that there were too many problems with it and a build system based on CMake was developed. The CMake build system produces both 32-bit and 64-bit binaries as opposed to the MSBuild build system that only produces 32-bit binaries. OTOH, the CMake build system does not yet produce all tools, only the most essential ones. We plan to improve this in future.
If you have too choose I would recommend you to use only the CMake builds. For the vast majority of users, they are probably sufficient.
More info:

https://forum.graphviz.org/t/new-simplified-installation-procedure-on-windows/224
https://forum.graphviz.org/t/the-story-of-windows-releases-since-2-38/236
https://gitlab.com/graphviz/graphviz/-/issues/1753 and other issues detailing differences between the builds.
https://gitlab.com/graphviz/graphviz/-/issues/1218 for the reasoning behind developing a build system based on CMake

If you have too choose

We don't have to do anything.  We are just talking and planning for the sake of maintenance and better end result.
The graphviz 2.38 is embedded and will work forever. People can install it using cinst graphviz --version 2.38 if they need all the tools missing in newer versions for now.
Msbuild seems to be backward compatibility moment, and it looks its only there as there is no feature parity yet, which will be resolved in the future, and thus msbuild will certainly be removed fully. Furthermore, cmake version has x64 bit build.
Thats why I think we should continue with cmake version only. This decision, along with what it means should be explained in package notes.

@majkinetor
Going forward with on the cmake only version will make the current version depreciated.
If this is the decision of the Chocolatey-CoreTeam  I have now problems with it.

This decision, along with what it means should be explained in package notes.

I will gladly update this PR with the required text, but I don't want to put in "a wall of text" for the community to read. Please mention what changes are needed text for the readme.
Conflicting files
automatic/graphviz/Graphviz.nuspec
IMHO This should never have been in the package from the start, and should not be a point to hold this PR.

I will gladly update this PR with the required text, but I don't want to put in "a wall of text" for the community to read. Please mention what changes are needed text for the readme.

Starting from version X.Y.Z. this package contains cmake build of the graphwiz. If you encounter problem with missing executables for the time being continue using the last msbuild version M.N.K.

Going forward with on the cmake only version will make the current version depreciated.

Not sure what you mean here - we don't need any package deprecation.

Starting from version X.Y.Z. this package contains new cmake build of the graphviz. If you encounter problem with missing executables for the time being continue using the last msbuild version M.N.K.

I presume from this Note that you want to make the newest release of the graphviz package be the cmake built version.
Might I propose the following as an Example of what will happen when this is done.
Community user has been using the graphviz version previously. Now they use the upgrade command  for chocolatey upgrading graphviz. This will install the 64-bit version of the cmake built graphviz program. All plugins/settings are not preserved when the user runs the program again. User will post to the Disqus or open a GitHub Issue here complaining about plugin/settings not being preserved when upgrading to the latest version.
If I'm wrong in your intention @majkinetor please let me know, but a lot of confusion is going to be caused by this build change with reusing the graphviz package name.

And such is the price of progress.
Anytime people update anything, there is a risk.
Also, we prioritize maintenance here, given that we maintain 300+ packages for free.

There is also a contra argument. Majority of tools that depend on graphviz will, if we create new package, continue to use the old one, which is not maintained any more. We also create confusion with multiple package names. The current one is essentially 5 years old.

I agree this is the logical progression, but I just wanted it noted in writing that this was discussed, and this will be the out come for the discussion.
@majkinetor
Do you want me to adjust the update to not do the msbuild updates?

I don't have a good solution to the above, but I just wanted to acknowledge the upstream problems that led to this. The asymmetry between the CMake and MSBuild artifacts and the fact that neither is a superset has plagued Graphviz for sometime. We're working on fixing it, but unfortunately Graphviz is an under-resourced project, with @magjac being the only brave Windows maintainer.

Does anyone know how to write post install actions for Windows?  If so, then hard linking the layout programs could solve a large fraction of the problems.  (There is just one layout program, but it checks argv[0] to select a particular layout algorithm. "For historical reasons".  This means dot, neato, sfdp, fdp, circo, twopi, osage, patchwork.) Someone would have to actually try this out, too.  I think in the past we may have brute forced this by just making N copies of the same executable.

@magneticnorth Yes, I think I know how to do that. It's on my TODO, but so far there's been more important stuff to do since users have an simple workaround by doing e.g. dot -Kneato ... instead of neato ....
For the record; these are the tools that are missing from the Windows CMake builds:

circo
cluster
diffimg
dot2gxl
dot_builtins
dotty
edgepaint
fdp
gc
gv2gml
gv2gxl
gvedit
gvmap
gvmap.sh
gvpr
gxl2dot
lefty
lneato
mingle
neato
osage
patchwork
prune
sfdp
smyrna
twopi
vimdot

These are the tools that are missing from the Windows MSBuild builds (a strict subset of the missing from the CMake builds):

circo
cluster
dot2gxl
dot_builtins
fdp
gv2gxl
gvedit
gvmap.sh
gxl2dot
neato
osage
patchwork
sfdp
twopi
vimdot

So this is even more complicated :)
@magjac , does dot depends on any of those missing tools since it is used mostly ?

since users have an simple workaround by doing e.g. dot -Kneato ... instead of neato ....

Wait a minute
Tools are not there but they can actually be used via dot -K ?
If so, we can actually create shims during installation to produce missing exes ! Shim is tiny wrapper around executable and one can also hardcode some params into it (i.e. shim neato.exe would be wrapping dot.exe -kneato).

@magjac , does dot depends on any of those missing tools since it is used mostly ?

No.

Tools are not there but they can actually be used via dot -K ?

Not in general, but some of the tools are just shortcuts for running dot -K. These tools are:

circo
fdp
neato
osage
patchwork
sfdp
twopi

If so, we can actually create shims during installation to produce missing exes ! Shim is tiny wrapper around executable and one can also hardcode some params into it (i.e. shim neato.exe would be wrapping dot.exe -kneato). This would ofc. be specific to choco install (although you can trivially recreate such thing).

You could do this for the shortcut tools mentioned above, but it wouldn't add any functionality that is not already available in dot.

You could do this for the shortcut tools mentioned above, but it wouldn't add any functionality that is not already available in dot

The only benefit would be if somebody relied on those tools on the PATH. Although, I honestly think people should fix their scripts then rather then us doing all kind of stuff.

The only benefit would be if somebody relied on those tools on the PATH. Although, I honestly think people should fix their scripts, rather then us doing all kind of weird stuff.

Agreed and since the Graphviz docs documents that these tools exist, it's us (the Graphviz maintainers) that should implemented it in the Graphviz releases. Which we will in the semi-near future.

OK, guys, thx for discussion. I would proceed with my original intent:

Reuse current package name
Use cmake build
Add note about it, and even link to this discussion, which we will remove once parity with old version exists.

If anyone has any objection, voice it here.

@majkinetor
I will work on updating the PR next week

@majkinetor
The files are updated to just process the cmake build as per the reviews. The Uppercase conflict of the nuspec file is blocking the appveyor builds.
Enjoy the weekend 👍

Looks legit. Does it add it to the PATH since shims are removed ?

Looks legit. Does it add it to the PATH since shims are removed ?
This would be a good question for @Smattr or @magjac to possibly answer.

Also please resolve conflicts.
@majkinetor @gep13
It has been mentioned earlier in this WIP PR about the non Linux conforming nuspec file. All the other packages in this repository follow the rules of lowercase names. This shouldn't be a deal breaker for this PR.

Looks legit. Does it add it to the PATH since shims are removed ?

This would be a good question for @Smattr or @magjac to possibly answer.

The CMake installer can add to the user's or the system's PATH, but it's not the default. The user has to explicitly select it by radio buttons. How this works when running from the CLI I don't know and I cannot tell how the installer is invoked from the chocolatey installer.

@RedBaron2 dot has to be on the PATH one way or another. Please check.

dot has to be on the PATH one way or another. Please check.

I'll check this week.

@majkinetor
The dot file will now be on the path, like in the original package.
@magjac
Just FYI:
The basics of the chocolatey call to install the software is similar to if the user typed
C:\Users\Owner\Downloads\graphviz-install-2.44.2~dev.20201020.0210-win64.exe /S
in a  (Administrator)  command line or powershell prompt.

Please rebase and lets merge this.

@majkinetor
I'll see what I can do about a re-base, but I will make no promises about this working out well.
I might just close this PR and submit a re-freshed PR for merge Tuesday or  Wednesday.

Closing this PR to submit #1571

FYI, I think this one behaves correctly now. I fixed problems with path and added more detailed note:
https://chocolatey.org/packages/Graphviz/<IP_ADDRESS>01124

@majkinetor
Thanks, I appreciate your help. I will probably work on making a function helper for the un/install of the bin for the Chocolatey Core extensions on the future.


[ALLUXIO-3251] Cherry pick journal association fix

https://alluxio.atlassian.net/browse/ALLUXIO-3251

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20695/
Test PASSed.


Janapese -> Japanese

 You should sign our Contributor License Agreement in order to get your pull request merged.

Thank you very much, @raylai!
Merged as 49c2761 (master) and be6e75b (v0.15.docs).