diegomrsantos
diegomrsantos
We are considering: - Making the TorTransport private - Creating a TorSwitch where it's not possible to add other transports and name resolving is disabled (see Tor design paper section...
does anyone know why this is necessary? @tersec @arnetheduck ?
I'm not familiar with this requirement, could you please elaborate?
I think I get it now, this is to make it possible to run CI on the `nim-libp2p-auto-bump-unstable` branch.
I believe we can achieve the same by adding the branch here https://github.com/status-im/nimbus-eth2/blob/73738c702c13b027ea92858ba921a28989c203fd/.github/workflows/ci.yml#L12 and checking the workflow run here https://github.com/status-im/nimbus-eth2/actions
The bumping happens on a GitHub workflow and is independent of this PR. My question was related to the existence of this PR that can't be merged - something unusual,...
It's possible to make a workflow run every time there's a push to a branch, as I pointed out. I was thinking about removing this PR, not the branch.
Another use case is for Tor transport. We can start a peer with`/unix/xxx/onion3/xxx`. The unix socket is the address configured as a onion service in Tor and the onion address...
I believe installing only`C` `0.1.0` would satisfy both project `A` and `B` constraints on `C` version.
It seems Nimble is satisfying the dependencies' version constraints (and their transitive dependencies) greedily and locally, instead of globally, considering the whole set of constraints.