Re: [Dev] Feedback on first build and test of the code

[Michael Lamb]

>
> Another person was looking at cleaning up Sdm/getting rid of the need for 
> using
> sudo. I encourage any work in that direction.


That was me. But I don't have a heck of a lot of time to work on it (which
is why I'm hesitant to click "claim" on SD-492
). I intend to keep
improving it when I can and eventually complete that ticket but I'm happy
if anybody else swoops in and takes over.
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev

[Dev] Feedback on first build and test of the code

[Victor]

Hi,

Here is some feedback from my first steps toward working on the code.
I'll make another email about the tests issues with more details (I can 
now make fail dozens of tests when stressing the system)


 Forwarded Message 
Subject:Re: Volunteering for Snowdrift.coop
Date:   Tue, 18 Aug 2015 23:39:53 +0200
From:   Victor 
To: aa...@snowdrift.coop


On 17/08/2015 03:13, Aaron Wolf wrote:

Thanks for volunteering! The process of getting involved in a project
like this isn't necessarily as clear as we wish. We're working on
organizing and there's so much to do, lots to juggle.

What I read in the wiki and the repo for getting involved is really well
organized and complete. I found everything I wanted to know for now.



As a developer, the first thing you should do is go to
https://git.gnu.io/snowdrift/snowdrift and follow the instructions at
the README. It's a help just to have you go through testing that. Let me
know how it goes.

The build went as smooth as butter, and from what I read on the blog, I
arrived just in time to avoid trouble ^^
For the tests I've seen issues when running the DB-setup script
(permissions denied to create a folder) but it doesn't seem to have
caused any related problem. I should investigate that though.

The first launch of the tests blocked on one the firsts tests (without
CPU or HDD activity). After maybe 10 minute, I had to Ctrl-C the run.
The second run (which required me to kill remaining stack instances, if
I recall correctly when had to do this) was a failure.
The third run was a success. So I found a flaky test, after running the
tests suite in a loop, I can re trigger sporadically the failure on the
same test.
I'll ask on #snowdrift if it's known and where can I document more I
details on those issues.


Note: I blessed your user on the site. You should have gotten a
notification about the honor-pledge. Once that's accepted, you can edit
wiki pages, comment freely etc.

I want to do everything I can to help you get comfortable and get to
where you are able to really contribute. Please please please do not
hesitate to let me know any questions.

Thank you for your warm welcoming, I'm really happy that you wrote me
about the project on Reddit comments.


 END Forwarded Message 



--
Victor

___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev

Re: [Dev] Feedback on first build and test of the code

[Bryan Richter]

Hi Victor, welcome! Thanks for sending some feedback.

On Wed, Aug 19, 2015 at 10:42:40PM +0200, Victor wrote:
>
>  > As a developer, the first thing you should do is go to
>  > [3]https://git.gnu.io/snowdrift/snowdrift and follow the instructions at
>  > the README. It's a help just to have you go through testing that. Let me
>  > know how it goes.
>  The build went as smooth as butter, and from what I read on the blog, I
>  arrived just in time to avoid trouble ^^
>
>  For the tests I've seen issues when running the DB-setup script
>  (permissions denied to create a folder) but it doesn't seem to have
>  caused any related problem. I should investigate that though.

Yep, there are some spurious(?) error messages from Sdm. Another
person was looking at cleaning up Sdm/getting rid of the need for
using sudo. I encourage any work in that direction.

>  The first launch of the tests blocked on one the firsts tests (without
>  CPU or HDD activity). After maybe 10 minute, I had to Ctrl-C the run.
>  The second run (which required me to kill remaining stack instances, if
>  I recall correctly when had to do this) was a failure.
>  The third run was a success. So I found a flaky test, after running the
>  tests suite in a loop, I can re trigger sporadically the failure on the
>  same test.

The tests, to be honest, are kind of in a state. I am just ripping a
bunch of them out right now. They have been outdated by new work I'm
doing on implementing a new funding mechanism. You may have caught
them at a bad time.

Thanks again, see you around!


signature.asc
Description: Digital signature
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev

Re: [Dev] FunBot updates

[Aaron Wolf]

On 08/17/2015 02:05 AM, fr33domlover wrote:
> Hello,
> 
> I've been working on FunBot, the IRC bot running in #snowdrift under
> the nick 'fpbot', a lot lately. I went over the IRC bot related tickets
> in snowdrift's ticket page and decided I'd summarize a bit of the new
> things the bot can do, in case it helps anyone.
> 
> While there's no persistent state yet (and a lot of features are
> waiting for that), useful things that work are:
> 
> (1) Announcing git commits and merge request events
> (2) Announcing news feed items (experimental)
> (3) Receiving events from custom clients via HTTP/JSON (experimental)
> 
> News regarding these features:
> 
> - I temporarily disabled MR update event announcements because GitLab
>   is very verbose. While this is being debugged, there's a log of all
>   MR events at http://bot.rel4tion.org/log
> - RSS/Atom feeds are a new feature being tested, last time I tried it
>   didn't work with Snowdrift's project newsfeed but made a lot of mess
>   with Wikipedia's change feed - so still not stable
> - Now that the bot can receive events both by pushing them into a
>   'Chan' and by sending them as JSON over HTTP, perhaps Snowdrift can
>   use an instance of it to integrate an IRC bot into the server,
>   announcing money related events and so on. I know you already have
>   Snowbot and Snowcaster and at least 1 bot Peter has been working on,
>   so this is just a random suggestion.
> - There was an issue in which when pushing many commits, all get
>   announced instantly and it fills the channel with spam. Also, all
>   repo branches' commits were announced. I fixed these, still needs
>   testing though: 1) Branches to announce/block can now be set in bot
>   config per-repo; 2) There is an option to shorter big pushes in a
>   friendly way, you'll see this in action in #snowdrift eventually
> 
> --fr33domlover


Following up on this: we're happy to potentially host that bot / replace
snowbot, etc. — I'm not sure how active Peter is with his bot, maybe not
at all.

Could you look into pulling in the code from snowbot into fpbot perhaps?
Then we could just deprecate snowbot potentially. Right now, I think all
snowbot does is provide optional missed messages log to known folks, and
there's a never-deployed function for telling absent people something
when they show up again…

Feel free to redo / close / comment on specific items on snowbot's
discussion page etc.

Thanks for all your work!

-- 
Aaron Wolf Snowdrift.coop 
___
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev