mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.3 2023-03-31T12:30:14Z 2023-03-31T12:30:14Z Nick Mathewson nickm@torproject.org 2023-03-31T12:30:14Z urn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e These crates had no changes until just a moment ago. But since we updated the versions on some of their dependents, they have now changed themselves. Thus they get patchlevel bumps. ``` tor-rtmock tor-protover tor-socksproto tor-consdiff tor-chanmgr tor-dirclient tor-hsservice ``` 2023-03-31T12:28:06Z Nick Mathewson nickm@torproject.org 2023-03-31T12:28:06Z urn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c These crates have had breaking changes. They are pre-1.0, so they get a minor bump. ``` tor-basic-utils tor-config ``` 2023-03-31T12:24:39Z Nick Mathewson nickm@torproject.org 2023-03-31T12:24:39Z urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76 For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ``` 2023-03-31T12:20:58Z Nick Mathewson nickm@torproject.org 2023-03-31T12:20:58Z urn:sha1:622c79aaa60e433712a7dc4d7b8900659fc78071 Their dependents are _not_ updated to a more recent version. These bumped the version of a dependency that they don't expose ``` tor-rtcompat fs-mistrust ``` This one had internal refactoring: ``` tor-netdir ``` These had trivial changes only: ``` tor-checkable tor-ptmgr tor-guardmgr arti-hyper arti-bench arti-testing ``` 2023-03-30T14:53:51Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-30T13:37:19Z urn:sha1:577940853f04ee120d4c5e95032e7ee5201a6649 2023-03-30T14:43:48Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-30T13:31:07Z urn:sha1:db968033cfd887e33b52130ac79072b695d46ee9 This eliminates an untyped `usize` index. 2023-03-27T16:32:16Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-27T16:22:31Z urn:sha1:9940bd1eb468d29ab3650a2751c024924f9e5811 There are too many things called "index" here. `idx` could be read to mean the table index `RouterStatusIdx`, the hsdir hash `HsDirIndex`, or an entry in some other one of these tables. Here's, it's just the sequence number of the index in the test netdir. Use `pos` for that. (`seq` would have been another possibility.) 2023-03-27T16:32:16Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-27T16:32:04Z urn:sha1:4da12a26a9d9f874429bed00c6bf5a7f36f51726 2023-03-27T16:31:23Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-27T16:16:08Z urn:sha1:325526a90356aaf11a58660b8f820aeb2b1f1589 The hidden services directory hashring is a ring of hsdir relays, sorted by a hash that the spec calls the "index". That's `HsDirIndex`. This was a bad idea because the word "index" is seriously overused, but in Arti we must use the same terminology. At least, qualify it everywhere. Now one of these hsdir sort position hashes is always, in our code, an `hsdir_index`. I think this is necessary even inside modules called `hsdir_*`, because those can deal with other kind of "index" too. 2023-03-27T16:26:51Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-27T16:20:33Z urn:sha1:a746e17c8eb8f63b433b32e881a2dbb7e1000117 This was removed in c3e74973b4201f71275d8cf4c0c954cfb8d0eba5 netdir: Use an even smaller rep for list of microdescs