Chutney issueshttps://gitlab.torproject.org/tpo/core/chutney/-/issues2022-02-07T19:31:40Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/17011chutney doesn't verify using IPv6 addresses2022-02-07T19:31:40Zteorchutney doesn't verify using IPv6 addressesEven when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.
When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.
This is a significant cover...Even when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.
When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.
This is a significant coverage gap that I think is easily fixed by slight modifications to the chutney templating and verification code.https://gitlab.torproject.org/tpo/core/chutney/-/issues/19019When chutney fails because of ports, tell the user2021-11-15T16:53:51ZteorWhen chutney fails because of ports, tell the userChutney can fail because old tors (or other processes) are already occupying the ports it wants to use.
We should make this more obvious, so developers don't blame tor code.Chutney can fail because old tors (or other processes) are already occupying the ports it wants to use.
We should make this more obvious, so developers don't blame tor code.https://gitlab.torproject.org/tpo/core/chutney/-/issues/30182IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv62022-02-07T19:30:49ZteorIPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6So maybe we're not actually testing IPv6 traffic?
Here are the symptoms of this bug:
* Travis Linux VMs don't have IPv6
* Travis macOS VMs have IPv6
* Most IPv6 tests succeed on Travis macOS, but fail on Travis Linux
* The IPv6 exit tes...So maybe we're not actually testing IPv6 traffic?
Here are the symptoms of this bug:
* Travis Linux VMs don't have IPv6
* Travis macOS VMs have IPv6
* Most IPv6 tests succeed on Travis macOS, but fail on Travis Linux
* The IPv6 exit test succeeds on Travis Linux, but it should nothttps://gitlab.torproject.org/tpo/core/chutney/-/issues/31833Make chutney fail if Tor logs a bug warning2022-02-07T19:31:30ZteorMake chutney fail if Tor logs a bug warningWe've missed bug warnings in our CI, because chutney succeeds even if Tor logs a bug warning.
For example legacy/trac#31793.We've missed bug warnings in our CI, because chutney succeeds even if Tor logs a bug warning.
For example legacy/trac#31793.https://gitlab.torproject.org/tpo/core/chutney/-/issues/33598chutney does not fail on some SOCKS errors2022-02-07T19:32:13Zteorchutney does not fail on some SOCKS errorsWhen tor can't make a connection, and sends back a SOCKS error, chutney keeps on rapidly sending SOCKS requests. Instead, chutney should fail.
I think we introduced this bug when we started using asyncore.
I have worked around the bug...When tor can't make a connection, and sends back a SOCKS error, chutney keeps on rapidly sending SOCKS requests. Instead, chutney should fail.
I think we introduced this bug when we started using asyncore.
I have worked around the bug using a 5 second asyncore timeout, but we should come up with a permanent fix.
I think nickm might be able to help with this issue, because he wrote that code.https://gitlab.torproject.org/tpo/core/chutney/-/issues/33825Make Environ handle "in" and "get()" like a dict2022-02-07T19:31:36ZteorMake Environ handle "in" and "get()" like a dictSome standard Python dict code doesn't work on chutney's Environ class:
```
is_in_env = 'foo' in self._env
value_or_none = self._env.get('foo')
```
"in" should return a boolean, and "get()" should return the value (or None).
But instea...Some standard Python dict code doesn't work on chutney's Environ class:
```
is_in_env = 'foo' in self._env
value_or_none = self._env.get('foo')
```
"in" should return a boolean, and "get()" should return the value (or None).
But instead, when the key is missing, sometimes they throw a KeyError. (It seems to happen in certain contexts, but not others.)
We should work out if Environ is missing some of the required dict implementation functions. Or if there is some issue with Environ's lookup code.
Then we should implement unit tests, to make sure we don't break Environ in future.https://gitlab.torproject.org/tpo/core/chutney/-/issues/40020Not found error2022-07-25T03:24:47ZPulkit ChandelNot found errorFileNotFoundError: [Errno 2] No such file or directory: '/home/eict/chutney/net/nodes.1657278323/006r/torrc'
</pre>
Why am I Getting this error. The file 006r was never made when I executed tor chutney command, then why is it looking for...FileNotFoundError: [Errno 2] No such file or directory: '/home/eict/chutney/net/nodes.1657278323/006r/torrc'
</pre>
Why am I Getting this error. The file 006r was never made when I executed tor chutney command, then why is it looking for it.And how to solve it