~missm_signed

Recent activity

Re: [PATCH radicle-link v4 1/3] Add integration test for bins and fix git version checks 5 months ago

From to ~radicle-link/dev

No, 


As a developer -

It is our job to choose the right tool for the job -

Re-using is one of the core competencies of ours -

I don't see even attempts to evaluate the options I gave you.

Don't expect anyone else to effectively do your work after for you.

Correcting mistakes is one but not even looking at the list and engaging in technical merits is another.

Re: [PATCH radicle-link v1 0/1] unlink UNIX socket before bind 5 months ago

From to ~radicle-link/dev

It would be nice to get rid of the signal handles, unix sockets etc.

Doesn't make it much portable I mean... ?

Can't we just link to git2-rs instead of running all these pipes ?

------- Original Message -------
On Friday, August 12th, 2022 at 9:16 PM, Fintan Halpenny <fintan.halpenny@gmail.com> wrote:


> LGTM
> 

> I'll just note that this is being caused by gitoxide under the hood

Re: A seed architecture for the link network 5 months ago

From to ~radicle-link/discuss

rust-libp2p essentially do S/Kademlia 


https://git.gnunet.org/bibliography.git/plain/docs/SKademlia2007.pdf

Last time I checked they even added circuit information in there

I would think the hopepunchr lib can be used to do all that

It doesn't yet support WebRTC transport from browsers but looking forward to that

------- Original Message -------
On Friday, August 12th, 2022 at 8:14 PM, Kim Altintop <kim@eagain.io> wrote:

Test strategy - CLI Integration testing framework 5 months ago

From to ~radicle-link/dev

Hi all

It would be nice to have a discussion around what design / framework we choose for initial CLI integration testing / validation -

This decision has big ramifications further on and is much harder to change the further we attach ourselves to it / add stuff on top of techdebt / status quo we create -

I feel that now we may be jumping to rolling our own when somebody has already solved many things for us -

Problem with hardcoded tests -

 1) Not maintainable

 2) The thing that runs these tests steals the show from the actual tests

Link - Test strategy - Framework Discussion 5 months ago

From to ~radicle-link/discuss

Hi all

It would be nice to have a discussion around what design / framework we choose for initial CLI integration testing / validation -

This decision has big ramifications further on and is much harder to change the further we attach ourselves to it / add stuff on top of techdebt / status quo we create -

I feel that now we may be jumping to rolling our own when somebody has already solved many things for us -

Problem with hardcoded tests -

 1) Not maintainable

 2) The thing that runs these tests steals the show from the actual tests