Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2015-05-18

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:14 sprang joined #darcs
01:00 mizu_no_oto joined #darcs
01:34 c74d joined #darcs
06:29 amgarchIn9 joined #darcs
09:03 _loic_ joined #darcs
13:20 notdan Hm, darcs complaining about conflicts when I am trying to push to a repo :S
13:22 notdan I did a pull, but I don't have any conflicts in the local  repository
13:34 notdan ah nvm things got fixed by themselves
13:39 maerwald notdan: :D
13:39 maerwald if this would apply for all of them
13:44 notdan maerwald: I like your patches for the run-time config, but unfortunately the default behaviour seems to pretty much ignore the DEV flag
13:45 maerwald notdan: that can probably be fixed
13:46 maerwald just put the inside defSettings in Production.hs
13:47 notdan yeah, I should do that.. eventually :)
13:48 notdan oh you fixed the "branches" feature, nice!
13:50 maerwald ouch, there is another bug I just found in defSettings
13:52 maerwald notdan: I'll push two patches to my branch
14:03 maerwald notdan: http://hub.darcs.net/maerwald/darcsden/patch/20150518135936-0bd70 and http://hub.darcs.net/maerwald/darcsden/patch/20150518140116-0bd70
14:03 notdan thanks :D
14:10 maerwald mh, we don't have mail notification?
14:10 sm hey notdan, maerwald
14:10 sm no, except for the password reminder
14:10 sm maybe the dev flag is no longer needed ?
14:11 maerwald hm
14:11 maerwald well, you could argue that
14:11 maerwald but don't know if it does anything more than config changes
14:13 sm at this point it seems to just put "dev" in the version string and logs to console instead of files
14:14 maerwald sm: can we make it log to console with an empty string in the config file for logs? or does the parser choke
14:14 sm if console logging is useful, maybe we can just do that when log/ doesn't exist
14:14 sm or that
14:14 maerwald I'm not sure if the config parser will allow that, though
14:16 maerwald I think it works
14:16 maerwald yep
14:16 maerwald accessLog =
14:16 maerwald errorLog =
14:17 maerwald notdan: is that good enough for you?
14:18 maerwald you can have a config file darcsden-dev.conf and load it via darcsden --config darcsden-dev.conf
14:18 sm great
14:20 notdan makes sense, thanks maerwald
14:21 maerwald sm: http://hub.darcs.net/maerwald/darcsden/patch/20150518142027-0bd70 this one is kinda important though
14:22 maerwald sshPort was missing from the default settings, so it will choke if it cannot find it in the user cfg
14:22 sm ok, I didn't notice a problem but merging
14:23 maerwald mail notification on issue would really be great
14:24 sm yup, or even irc notification or a per-issue activity feed (which could be announced on irc)
14:25 sm I was thinking darcs hub needs to use a sevice like mandrill for reliable mail delivery, eg when notifying all users, but we could try sending via the local mail server first
14:26 sm it probably needs a bit of thought, how to support it for all kinds of events
14:26 sm and then the user UI
14:27 maerwald are the issue participants encoded somewhere in the database?
14:27 sm it'll add another level of complexity to darcs hub operation.. it'll probably also make it feel more live and useful
14:28 sm I think just embedded in the comments
14:28 maerwald I guess it would make sense to have a table for issue and corresponding accounts that should be CCed
14:31 maerwald so I'd actually start with the database part first, I guess
14:32 sm I guess think big but implement small.. user-configurable per-issue comment notifications to start ?
14:34 maerwald well, something to think about first
14:37 sm maybe smaller than that.. could start with always-on issue comment notifications to a few devs
14:39 maerwald sm: I'd rather do something like "always send mails to issue-participants" with an opt-out, but I am not sure if we can access the accounts without using a DB table
14:39 maerwald so it could start as a quick hack if we can do that
14:41 maerwald maybe parse the html issue page an look for <div class="user-info">
14:51 sm maerwald: here's youtrack's notification settings by the way: http://pasteboard.co/yvWTkii.png (it goes on for 12 more pages)
14:52 sm http://pasteboard.co/yvWTkii.png
14:54 sm I find it a bit confusing to think about the db except in terms of the abstract interface Heffalump added, eg does couchdb have "tables"
14:55 sm it sounds easy enough to add a function to collect an issue's participants though, without db schema changes needed
14:55 sm ignoring github-level scaling issues
16:50 amgarchIn9 joined #darcs
17:24 amgarchIn9 joined #darcs
17:38 * Heffalump appears
17:39 * Heffalump makes encouraging noises about writing tests as things change
18:42 sprang joined #darcs
18:45 fr33domlover joined #darcs
18:48 amgarchIn9 joined #darcs
19:08 sprang joined #darcs
19:30 amgarchIn9 joined #darcs
19:55 sprang joined #darcs
23:04 rieper_ joined #darcs
23:06 lelix joined #darcs
23:09 aristid joined #darcs
23:26 Riastradh joined #darcs

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary