-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support ssb-tribes #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have skimmed over this while half awake, left a couple comments
I guess the test of this is if you try and use the fixtures. Might be good to list what you expect a person to be able to do with these fixtures (and what they won't be able to do /see if anything) Eg are there feeds in here which aren't in group and so cannot decrypt? Which ones are they |
Yes
It's probabilistic |
I think what I'm wondering is if it would be good to have an output at the end which summarises who is in each group (and what dm groups exist) so you know if your tests are working when you decrypt. Do you have that? |
Great idea! We already have a "report" module, but it doesn't report on tribes, and it could |
I was testing this using the instructions posted and ran into this problem:
it was spitting out a ton of debug I could see. |
@arj03 how many authors do you configure it to run with? |
I just ran it with the defaults. |
Weird, then I'm a bit lost what is the problem... could try to figure it out together in a screen share |
I think you can merge this. Still need to test it properly with ssb-db2. It's up to you. |
Well, when this is merged, it would be a breaking change, so leading to |
Maybe we could try getting this one merged this week? |
Yes, I will schedule this for friday for me to test. |
I'm testing this, I can't get my code to decode the groups but I see there is something wrong with the way they are created. I added some debug to tribe creation and what I see is this:
So this means that all groups are creating by the hops0 user. |
Oooh, I see the problem now. ssb-tribes does the Do you have any ideas how we could solve this without changes in ssb-tribes? Or do we need changes in ssb-tribes? @mixmix ? |
I don't use createFeed (and I notice it's marked as deprecated but also in use in places?). Anyway no idea what it would do with tribes. My approach to starting many different groups from many different authors is use scuttle-testbot to easily spin up many instances and perform operations from there. Might not be fastest, but it works well (and no semi - supported methods!) Look in the tests of ssb-tribes for a helper test bot file which is the form you want |
I updated this PR to be based on scuttle-testbot (pending on PR ssbc/scuttle-testbot#13 being merged). @arj03 can you test? |
I ran the new code. Tried deleting the data dir to make sure everything was fresh, then I got a small error because there seems to be a missing mkdir? After creating the dir and running this I get an error:
I wonder if its the same error as Henry ran into. |
Indeed, lots of errors. Gonna fix them. |
Updated this branch to fix a bunch of errors, but now I'm getting a deterministic error, would need help from @mixmix maybe: PS: I removed some console.logs from
|
Did you make it so some of those are disabled or disableable? Many of those logs are quite important / useful for understand what's happening in tests. The key not found in db is something I've seen before and don't know what it is. I'm in holiday at Bob's at the moment. Can pair on this if you'd like when I'm back in Wellington. Feel free to dm on signal |
Pushed up the changes @mixmix and I paired on. This now closer to working but is dependant on this bug in tribes. And this bug:
and this one:
|
Thanks for doing it! Cool to see you dabbling with TypeScript |
I have seen that core dump before. |
The unhandled promise rejection... looks bad. Is it a seq 1 message with a non null previous? |
Bye bye PR |
@arj03 @cryptix @mixmix I think fixtures now can generate: (1) tribe creation, (2) tribe invitation to other feeds, (3) post a message inside tribes, all using
ssb-tribes
. I think it's working, but it would be good to be sure.How to test this out:
git clone
tribes
npm install
npm run compile
node lib/bin.js
./data
dir when it's doneNote, you can get the
secret
of the 3 most popular feeds, they are in the generated./data/
.