Re: [Dev] More test speedup?

On Tue, Aug 18, 2015 at 12:24:30PM -0700, Curtis Gagliardi wrote: I meant to follow up earlier, but for the record I couldn't figure how to apply these changes to the tests. From what I remember his speedups came from flushing and closing stdin, while we never even create a handle for stdin

Re: [Dev] Concerns regarding the mechanism

On Sat, Aug 01, 2015 at 03:08:47AM +0300, Nikita Karetnikov wrote: Oh, wow. Thanks for the tip. I will probably do that. Even after spending a few hours on this esqueleto, it will still save me time to switch. Just gotta figure out how to share database connection information... Is it

[Dev] More test speedup?

I have a suspicion we might speed up tests with this one trick. From Gabriel Gonzalez on twitter: I finally fixed the silly delays running external commands... His original tweet (with some discussion): https://twitter.com/GabrielG439/status/624405459370311681 His inspiration:

Re: [Dev] Bake on Gitlab

On Thu, Jul 30, 2015 at 07:38:45PM +0300, Nikita Karetnikov wrote: So I'm looking into Bake integration with Gitlab. Here's the rough plan: 1. Setup web hooks as described here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md 2. Parse that on the Bake

Re: [Dev] Concerns regarding the mechanism

On Fri, Jul 31, 2015 at 02:41:41PM -0700, Curtis Gagliardi wrote: I'd probably drop down to postgres-simple and run that query as is. I don't think the lack of typing needs to be a deal breaker if it's going to be easier to write and easier to test. Oh, wow. Thanks for the tip. I will

Re: [Dev] Bake on Gitlab

On Mon, Aug 10, 2015 at 11:29:36AM +0300, Nikita Karetnikov wrote: FYI, I renamed the project to snowdrift-ci because I'm no longer planning to use Bake: https://github.com/ndmitchell/bake/issues/15#issuecomment-129343416 I have a lot of concerns about this. I am concerned about starting yet

[Dev] vim foldmarkers in Snowdrift.cabal

Would there be any complaints if I added vim foldmarkers to Snowdrift.cabal? They make it a *lot* easier to navigate, at the expense of a small amount of extra whitenoise that is presumably useless to non-vimmers (unless emacs has folding compatibility). The change:

Re: [Dev] GitLab CI

On Thu, Jul 09, 2015 at 10:40:39PM -0700, Aaron Wolf wrote: So, we've been chatting about Continuous Integration… I didn't know before about this: https://about.gitlab.com/gitlab-ci/ — fully FLO CI designed for GitLab… is there a chance we could use that? The free version seems to only work

[Dev] New design launch: walkthrough of remaining steps

I've merged together all the groundwork that mray, jazzyeagle, and I have accomplished the last couple weeks: https://git.gnu.io/chreekat/snowdrift/merge_requests/1 At this point, I don't think it's ready to go live at *all*. What I would like to do is walk through the pages and discuss what

[Dev] Current dev work

Hi all, There have been a few video chats recently, and I wanted to briefly summarize some of the discussion to make sure everyone is included. * We set a psuedo-random goal of having an "alpha" release before the SCALE conference[1] on January 21–26. * We have been clarifying the goal for

Re: [Dev] Bug: Ticket page: Help link goes 404

On Tue, Feb 16, 2016 at 08:42:28AM -0800, Aaron Wolf wrote: > On 02/16/2016 03:23 AM, Victor (tuxayo) wrote: > > Hi, > > > > To report another problem I wanted to create a ticket. > > But I forgot how to do it. > > And on the ticket page: > > https://snowdrift.coop/p/snowdrift/t > > The link

Re: [Snowdrift-dev] DB admin code

On Wed, Mar 09, 2016 at 08:58:51PM +0200, fr33domlover wrote: > I found this in Keter, maybe we can (re)use it somehow instead of hacking our > own? > > http://haddock.stackage.org/lts-5.6/keter-1.4.3.1/Keter-Plugin-Postgres.html#v:setupDBInfo The whole point of sdb.hs was to avoid using sudo.

Re: [Snowdrift-dev] Mechanism implementation

On Tue, Mar 15, 2016 at 09:13:53AM -0600, Peter Harpending wrote: > On 03/15/2016 12:50 AM, Peter Harpending wrote: > > code that requires one to use the feature, so I vote that > > Silly me, I forgot to mention how I vote. I vote that we leave it for > now, because it's unlikely to cause any

[Snowdrift-dev] A note on Yesod Forms and Widgets

I think there is some confusion about how Widgets are used for Yesod Forms. Yesod Forms (I'll just use capital 'F' when I mean a "Yesod Form") hare pretty fancy. Some might say... TOO fancy. They take care of a lot of things: 1. Defining the Haskell data that comes out of them 2. Defining what

Re: [Snowdrift-dev] A note on Yesod Forms and Widgets

On Tue, Mar 15, 2016 at 09:13:49PM -0700, Aaron Wolf wrote: > > Are you saying that correct use of Yesod Forms will always generate > the html element? I think I may be misunderstanding your question, but I would say the precise opposite is true. Yesod Forms do not generate elements. If a

Re: [Snowdrift-dev] A note on Yesod Forms and Widgets

On Tue, Mar 15, 2016 at 09:23:44PM -0700, Aaron Wolf wrote: > On 03/15/2016 09:20 PM, Bryan Richter wrote: > > On Tue, Mar 15, 2016 at 09:13:49PM -0700, Aaron Wolf wrote: > >> > >> Are you saying that correct use of Yesod Forms will always generate > >> the h

[Snowdrift-dev] sw architecture drawing

I took a first pass at drawing the software architecture: http://flurry.snowdrift.coop:2040/shared/pnv4YSuKmLQtfG6ZYHcBSeVng5TfRFwNtnRxL1vYVn_ I must stress that this is inaccurate and includes some wishful thinking. It is also incomplete. I think there are some components that will arise, like

Re: [Snowdrift-dev] Mechanism implementation

On Tue, Mar 15, 2016 at 12:50:00AM -0600, Peter Harpending wrote: > I need to go to bed, but tomorrow, I'll try to work on gluing the > mechanism to the rest of Snowdrift. I would hold off on doing this, or at least run your plan past me first. It involves core architecture decisions. Thanks!

Re: [Snowdrift-dev] Code reboot going into master

On Sat, Mar 19, 2016 at 06:12:39PM +0200, fr33domlover wrote: > > On Fri, 18 Mar 2016 15:01:12 -0700 Bryan Richter wrote: > > > > We *could* keep going, and update the basic scaffold code to the > > latest version coming out of the yesod-scaffold library, but I'm > >

Re: [Snowdrift-dev] [PATCH] User nicknames as public user IDs: Change UserR route

On Tue, Mar 08, 2016 at 04:39:11AM +0200, fr33domlover wrote: > On Mon, 7 Mar 2016 16:39:11 -0800 > Bryan Richter <br...@snowdrift.coop> wrote: > > > Can I pass the tasks on to someone else who can take the time to > > figure out the best way to use OpenProject? >

Re: [Snowdrift-dev] [PATCH] Add new route /u/

On Mon, Mar 07, 2016 at 03:30:00AM +0200, fr33domlover wrote: > On Tue, 1 Mar 2016 16:27:41 -0800 Bryan Richter wrote: > > > ** Tech action items > > > > - UserHandle should be redefined to Text > > - The existing route should be renamed getUserByIdR and s

Re: [Snowdrift-dev] [PATCH] User nicknames as public user IDs: Change UserR route

Before I comment on this patch, I think we should make sure that Snowdrift.coop at large is ok with this change, and that that "ok" is made real by adding the feature to OpenProject. I want to get in the habit of doing feature-work that is in OpenProject, and only that is in OpenProject. From the

Re: [Snowdrift-dev] Updating to work with github-0.14 (in LTS)

On Sun, Mar 06, 2016 at 12:09:07PM +0200, fr33domlover wrote: > On Wed, 2 Mar 2016 13:31:59 -0800 > Bryan Richter <br...@snowdrift.coop> wrote: > > > The github package is in LTS now, but it changed its interface to use > > better types (Text, Vector, and vani

Re: [Snowdrift-dev] [PATCH] User nicknames as public user IDs: Change UserR route

On Mon, Mar 07, 2016 at 02:39:07PM -0800, Aaron Wolf wrote: > In this case, I'm fine with moving forward but only if it's otherwise > clean progress. Ok, if design is fine with it (which was expected) we come to a bigger problem. Right now I'm working to strip out unnecessary features and

Re: [Snowdrift-dev] /p/snowdrift

On Wed, May 18, 2016 at 12:39:32PM -0600, Peter Harpending wrote: > On Wed, May 18, 2016 at 02:23:01PM -0400, Stephen Michel wrote: > > I don't understand exactly why it's a corner case. Under the current system, > > wouldn't /p/snowdrift/ eventually be coded the exact same way as any other > >

Re: [Snowdrift-dev] [PATCH] Make Snowdrift project wiki search redirect to the gitit wiki

On Tue, May 17, 2016 at 12:25:08PM -0600, Peter Harpending wrote: > On Tue, May 17, 2016 at 09:12:30PM +0300, fr33domlo...@riseup.net wrote: > > From: fr33domlover > > > > --- > > website/Snowdrift.cabal | 1 + > > website/config/routes | 1 + > >

Re: [Snowdrift-dev] What are the folders to purge to fix or prevent build issues?

On Fri, May 06, 2016 at 01:09:10PM +0200, Victor Grousset wrote: > On 04/05/2016 19:48, Aaron Wolf wrote: > > There are no other directories to purge unless you already ran the site > > and have database stuff to deal with. To clean out database stuff, it's > > better to use the sdb.hs tool rather

Re: [Snowdrift-dev] What are the folders to purge to fix or prevent build issues?

On Sat, May 07, 2016 at 02:15:22PM +0200, Victor/tuxayo wrote: > On 06/05/2016 19:44, Aaron Wolf wrote: > > While this stuff about purging is documented at the Stack docs and > > otherwise, I could see adding to BUILD a statement referencing that the > > total list of things to possibly purge

Re: [Snowdrift-dev] hlint on commit

On Sat, Jul 23, 2016 at 03:11:36PM -0700, Aaron Wolf wrote: > > I have vim set up to automatically run hlint whenever I save a file > (via syntastic I believe), but I don't know how to make that use the > -XQausiQuotes argument. > :help syntastic That'll probably get you headed in the right

Re: [Snowdrift-dev] Taiga: request for issue comment permission

On Tue, Aug 02, 2016 at 11:59:14PM +0200, Victor/tuxayo wrote: > Hi, > > I tried IS-400 and would like to share progress. And Taiga seems the > most appropriate place to do so. Therefore I need the comment permission > on the issues. > > Taiga account handle: tuxayo Unfortunately, Taiga doesn't

Re: [Snowdrift-dev] Mechanism

On Tue, Aug 09, 2016 at 01:35:55PM -0600, Peter Harpending wrote: > Hi, everyone, > > I wrote a mechanism library a few months ago, which I don't believe > was ever merged into the main code tree. Then, I had summer classes, > and several deaths in my family, so I haven't been paying much >

Re: [Snowdrift-dev] Taiga: request for issue comment permission

On Wed, Aug 03, 2016 at 11:23:39PM +0200, tuxayo wrote: > On 03/08/2016 08:22, Bryan Richter wrote: > > Unfortunately, Taiga doesn't let me add people by their account > > handle. I sent an invite to your email address instead. > > > > So there are two problems: (

[Snowdrift-dev] Taiga backups

Now that there are a multiplicity of Taiga projects, automating the Taiga backups has become high severity. I don't have the time to click through all the projects and have all the dumps emailed to me. :) The best long-term solution is to use the Taiga API to streamline the process. I think there

Re: [Snowdrift-dev] ghci & Snowdrift.coop

On Fri, Jan 27, 2017 at 09:15:11PM -0600, Jason Harrer wrote: > Hello, all - > > During my adventures of troubleshooting the discourse-sso branch, I tried > to access GHCi using both "./build.sh ghci" and "stack ghci". Neither of > them fully loaded the website as I anticipated, which made my

[Snowdrift-dev] Fwd: [GitLab, Inc.] Re: comment on issues via email?

. :) - Forwarded message from "Chris Wilson (GitLab Support)" <supp...@gitlab.com> - Date: Thu, 19 Jan 2017 19:36:29 + From: "Chris Wilson (GitLab Support)" <supp...@gitlab.com> To: Bryan Richter <br...@snowdrift.coop> Subject: [GitLab, Inc.] Re: comment on issues

Re: [Snowdrift-dev] Hello

On August 22, 2016 2:10:22 AM GMT+01:00, Tim Lim wrote: > Hello everyone! Just wanted to say hi -- My name is Tim and I've been > wanting to work on actual software written in Haskell ever since I > learned a little bit of it in a programming languages class last year. > I'll mostly be poking

[Snowdrift-dev] Merge: Adding Stripe

Feedback appreciated: https://git.snowdrift.coop/sd/snowdrift/merge_requests/20/diffs signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop https://lists.snowdrift.coop/mailman/listinfo/dev

[Snowdrift-dev] adding the mechanism

I'm ready for the mechanism to get added to the code now. Here's what I want. 1. Let's not create a separate Cabal package, after all. Based on the success (so far) of AuthSite.hs, I think it's enough abstraction to have distinct tests and a good module interface. 2. All actions should be

[Snowdrift-dev] code feedback please!

Hi everyone, The crowdmatch mechanism code is still a work in progress, and I want to talk about what I've done so far to get some feedback. This email has become rather long! Feel free to skim it to find parts that sound interesting. This was written for my benefit as much as yours, and in the

[Snowdrift-dev] Crowdmatch mechanism ready to merge

https://git.snowdrift.coop/sd/snowdrift/merge_requests/25 STATUS == What this currently does: - Enables configuring payment info - Enables registering/unregistering a pledge. - Tracks a history of pledges and unpledges. What this does not do: - It does not reintegrate the

[Snowdrift-dev] Fwd: Issues with Snowdrift.coop's Production Branch

Moving this to the Dev mailing list (Jason, are you on it?) Jason wrote: > > Hi, Bryan - > > As you requested, I was working on the code to put up a banner for > when a member logs in but their e-mail is not yet verified. Also, as > you requested, I created this code on top of the production

Re: [Snowdrift-dev] Issues with Snowdrift.coop's Production Branch

On Thu, Oct 20, 2016 at 08:47:00AM -0500, Jason Harrer wrote: > On Wed, Oct 19, 2016 at 8:03 PM, Bryan Richter <br...@snowdrift.coop> wrote: > > > Moving this to the Dev mailing list (Jason, are you on it?) > > > > Jason wrote: > > > > > > Hi, Bry

[Snowdrift-dev] my weekend dev progress and next steps

Hi all, I'm really glad Snowdrift got mentioned on the reditwittersphere recently - lots of new people around! Having people around, doing work and asking questions, has helped me get focused and energized. I got two solid days of programming in this weekend. I've merged the ability to process

Re: [Snowdrift-dev] [PATCH] Add a real Stripe runner to crowdmatch test module, using test key

On Tue, Jul 11, 2017 at 01:43:49AM +0300, fr33domlover wrote: > From: fr33domlover > > The runner isn't being used, I just added it there so that we can start > writing tests with it. May wish to move it to a TestImport module once > we split crowdmatch tests into

Re: [Snowdrift-dev] [PATCH] Use appStripe as stripe client in handlers

To whom it may concern: fr33domlover and I know this doesn't compile.. it was submitted for discussion. Now, on with the discussing: On Tue, Jul 11, 2017 at 03:57:31AM +0300, fr33domlover wrote: > From: fr33domlover > > --- > crowdmatch/crowdmatch.cabal| 3

Re: [Snowdrift-dev] my weekend dev progress and next steps

On Mon, Jul 10, 2017 at 09:34:56PM +0200, tuxayo wrote: > Hi, thanks for these news :) ! > > On 2017-07-10 02:28, Bryan Richter wrote: > > Other steps and potential work are here: > > > > https://git.snowdrift.coop/groups/sd/issues=label_priority Oops, missed a

Re: [Snowdrift-dev] [PATCH] Override Stripe secret key in test settings

On Tue, Jul 11, 2017 at 01:05:28AM +0300, fr33domlover wrote: > From: fr33domlover > > --- > website/config/test-settings.yml | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/website/config/test-settings.yml > b/website/config/test-settings.yml >

Re: [Snowdrift-dev] [PATCH] crowdmatch: Use (SqlPersistT env) monad to allow combining queries

On Sun, Jul 09, 2017 at 04:56:29AM +0300, fr33domlover wrote: > > Before this commit, crowdmatch actions run database queries separately > inside them like a black box. That means in practice many applications > of `runDB`, one per query, so a transaction per query. This is an > unnecessary

Re: [Snowdrift-dev] [PATCH] Use appStripe as stripe client in handlers

Much of this patch makes sense to me. I'm pretty sure I know where the type errors are originating from, too. Throw rocks at me if I don't get to this in the next 24 hours or so... On Tue, Jul 11, 2017 at 06:16:58AM +0300, fr33domlover wrote: > From: fr33domlover > >

Re: [Snowdrift-dev] [PATCH] Use appStripe as stripe client in handlers

On Tue, Jul 11, 2017 at 06:57:03PM -0700, Bryan Richter wrote: > Much of this patch makes sense to me. I'm pretty sure I know where the > type errors are originating from, too. I looked at this yesterday, and I realized what really needs to happen is we get rid of StripeI. It is comp

Re: [Snowdrift-dev] Shakespeare splice support for SASS

On Tue, Jul 25, 2017 at 01:30:10AM +0300, fr33domlover wrote: > Hello people, > > > > I made a patch for shakespeare-sass which makes it support > splices like the other shakespeare languages. I'd like to explain > why and how because it's not easy to understand from my still >

[Snowdrift-dev] connecting model data to the front end with splices

I've heard some questions and concerns about front end development waiting on back end variables. I can understand why these questions might arise. The final version of a page's template must use #{..} splices that get read and compiled to Haskell. The values referred to in those splices need to

Re: [Snowdrift-dev] [PATCH] Advice for starting a project

On Mon, May 08, 2017 at 07:29:17PM -0700, Alyssa Rosenzweig wrote: > As per a discussion with wolftune. > --- > community/team-engagement.page | 10 ++ > 1 file changed, 10 insertions(+) > > diff --git a/community/team-engagement.page b/community/team-engagement.page > index

[Snowdrift-dev] weeder: a neat tool to try out

https://hackage.haskell.org/package/weeder Maybe someone wants to give it a spin on Snowdrift and see what it reports? signature.asc Description: Digital signature ___ Dev mailing list Dev@lists.snowdrift.coop

[Snowdrift-dev] Life in the post-October Rest world

Hi all, Here's another long email! (When I said my emails would become more irregular, I guess that could mean *more* frequent...) This email is about what to do now that I've reset the code base and starting doing deploys again. In short, let's continue making a world where more people support

[Snowdrift-dev] Weekly dev status, 2017-09-11

== Last week. Code changes: some updates and fixes to the snowdrift project page, thanks to Iko. == This month. My goal for this month is to finish the website and crowdmatch mechanism for Alpha. Maybe a bit optimistic. :) But we seem close. The mechanism is functional; it just needs testing.

Re: [Snowdrift-dev] Attacked by Space Bug

> On 09/11/2017 08:00 AM, Peter Harpending wrote: >> On Sep 10, 2017 11:27 PM, "jake" wrote: >> >> Hello, I'm Jake. I'm brand new here. In summary, I want "real >> world" Haskell experience. (Long version sent to >> commun...@snowdrift.coop .) >> >>

Re: [Snowdrift-dev] Weekly dev status, 2017-09-11

On 09/11/2017 03:16 PM, Stephen Michel wrote: > > > On September 11, 2017 5:19:29 AM EDT, Bryan Richter <br...@snowdrift.coop> > wrote: >> == Last week. >> >> Code changes: some updates and fixes to the snowdrift project page, >> thanks to Iko. >>

Re: [Snowdrift-dev] Weekly dev status, 2017-09-11

On 09/11/2017 05:56 PM, Stephen Michel wrote: > On Mon, Sep 11, 2017 at 10:50 AM, Bryan Richter wrote: >> On 09/11/2017 03:16 PM, Stephen Michel wrote: >>> >>> >>> When we reach alpha, maybe it's time to run our first crowdmatch? >>> It'll be below

Re: [Snowdrift-dev] Anyone knowledgeable on spam filtering?

On 09/02/2017 02:58 AM, Stephen Michel wrote: > I do my hosting through hcoop.net. They commit the same folly we do > (running our own mail server), but at least have SpamAssassin set up. > Maybe we could send our email through them? If we're interested in that, > I could be the liaison and handle

[Snowdrift-dev] Weekly dev update, 2017-09-03

Weekly update, 2017-09-03 = Code developments - - Page styling is now implemented with Sass. See https://git.snowdrift.coop/sd/snowdrift/blob/master/BUILD.md#adding-and-updating-sass-files for some usage notes. - CI is up and running:

Re: [Snowdrift-dev] Go to Definition?

On 11/14/2017 11:04 AM, Samuel Tay wrote: > Hasktags generates pretty much all the tags you want relevant to > your project. If you have git submodules, forks of other projects > locally, etc. then you can pass these directly via the CLI, e.g. > > hasktags -b "src deps/package1 deps/package2

Re: [Snowdrift-dev] Go to Definition?

On 11/14/2017 12:02 PM, David Thomas wrote: > While the general case for TH is intractable, it would probably be > pretty simple to write a script that can generate tags locations for > identifiers generated by specific, known cases - particularly > Persistent. > > At work I took a bit of a

Re: [Snowdrift-dev] Brainstorm for implementing multiple projects

On 12/13/2017 03:16 PM, Aaron Wolf wrote: > On 12/13/2017 11:28 AM, Bryan Richter wrote: > > > > Two comments: > >> Buffers can't exist in a system that has no account balances. The >> volatility gets pushed to the question of "Does the patron have >>

Re: [Snowdrift-dev] errors trying to build from arch linux

On 12/13/2017 09:29 PM, Jason Harrer wrote: > Schwt > > All we need now is confirmation from someone on *bunts/Debian. > > Bryan, you may want to test on MixOS as well. > Just to confirm on this thread, the fix is in master and seems to work for everybody. Thanks, Jason!

Re: [Snowdrift-dev] Brainstorm for implementing multiple projects

On 11/16/2017 12:29 AM, Aaron Wolf wrote: > On 11/07/2017 04:34 AM, Bryan Richter wrote: >> >> Having multiple projects means it becomes more complicated to see if >> someone has gone over their budget. We'll need to account for that. > > We discussed this a while b

Re: [Snowdrift-dev] Go to Definition?

Hi! On 11/13/2017 06:30 AM, jake wrote: > In Haskell code, I'd like the ability to click an identifier and go > to its definition. How do I do this? You're not alone in your frustration. I think the only people who have a really good answer to this question are users of emacs + intero (+

[Snowdrift-dev] Brainstorm for implementing multiple projects

Hi all, Here are some initial ideas for implementing multiple projects in the crowdmatch library. (This is not about the website.) Please take some time to read this and provide any feedback or fresh ideas, since I dreamed this up on my own, and I could use some second opinions. Thanks! ---