<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr/src, branch arti-v1.1.12</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-14T01:12:10Z</updated>
<entry>
<title>ChannelState::ready_to_expire: return true when rem time is zero</title>
<updated>2023-12-14T01:12:10Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-12-14T01:00:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=197c5c8b804ed81c6081472ffea84c95a7f621a7'/>
<id>urn:sha1:197c5c8b804ed81c6081472ffea84c95a7f621a7</id>
<content type='text'>
This fixes a race condition that would normally be fairly benign -
it would result in scheduling to check for expired channels again
immediately, and assuming non-zero time passes would then remove the
channel.

In Shadow's default time model though, zero time passes in this case,
so we just keep scheduling to check again immediately forever; i.e.
deadlock.
</content>
</entry>
<entry>
<title>ChannelState::ready_to_expire: refactor using let-else</title>
<updated>2023-12-14T01:12:10Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-12-14T00:56:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cc2cbad83958373a5ada310f3d3cab0a49de656d'/>
<id>urn:sha1:cc2cbad83958373a5ada310f3d3cab0a49de656d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>continually_expire_channels: don't round off expiration delay</title>
<updated>2023-12-14T00:51:39Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-12-14T00:51:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cc9d656ca88d75970cc527af1299e9a1e292b008'/>
<id>urn:sha1:cc9d656ca88d75970cc527af1299e9a1e292b008</id>
<content type='text'>
Without this change, if the delay is less than one second, the code will
effectively busy-loop until the delay has elapsed. This
potentially leads to deadlock in shadow simulations, and
wastes CPU in real usage.

https://shadow.github.io/docs/guide/limitations.html?highlight=busy#busy-loops
</content>
</entry>
<entry>
<title>continually_expire_channels: refactor using let-else</title>
<updated>2023-12-14T00:50:32Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2023-12-14T00:50:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=10aff4d04e1a404f7f04fde93980184d5b613fb2'/>
<id>urn:sha1:10aff4d04e1a404f7f04fde93980184d5b613fb2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>oneshot: Apply deferred rustfmt churn</title>
<updated>2023-10-11T15:19:46Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-10-11T15:09:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=665ba4f6b6ed2de6f723177d5472e7ee1440599e'/>
<id>urn:sha1:665ba4f6b6ed2de6f723177d5472e7ee1440599e</id>
<content type='text'>
cargo fmt, precisely.
</content>
</entry>
<entry>
<title>oneshot: Use veneer in tor-chanmgr</title>
<updated>2023-10-11T15:19:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-10-11T14:08:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d8a600113c37499dd05ef99c1c6e30a9d3fa10a7'/>
<id>urn:sha1:d8a600113c37499dd05ef99c1c6e30a9d3fa10a7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add initial support for running a PT in server mode</title>
<updated>2023-08-24T17:03:38Z</updated>
<author>
<name>Saksham Mittal</name>
<email>gotlouemail@gmail.com</email>
</author>
<published>2023-08-24T17:03:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bbed17ba4a44a4690ad68e34844329d6542cc184'/>
<id>urn:sha1:bbed17ba4a44a4690ad68e34844329d6542cc184</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run maint/add_warning to add lint block everywhere</title>
<updated>2023-08-23T09:34:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-08-22T14:28:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac'/>
<id>urn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Resolve a pair of warnings about redundant closures.</title>
<updated>2023-08-22T16:24:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-22T13:18:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c0e050b640c7922a649c4bf8bc08fb862235a36e'/>
<id>urn:sha1:c0e050b640c7922a649c4bf8bc08fb862235a36e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run add_warnings on all files.</title>
<updated>2023-08-04T11:45:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-04T11:45:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cec6d0ce33b4b5cebbce57f55faec83397e9c953'/>
<id>urn:sha1:cec6d0ce33b4b5cebbce57f55faec83397e9c953</id>
<content type='text'>
</content>
</entry>
</feed>
