Fork me on GitHub
#alda
<
2016-03-02
>
djtango15:03:14

Hi I'm really keen to help out with Alda (I'm passionate about Clojure and about music..)

djtango15:03:23

I saw this issue https://github.com/alda-lang/alda/issues/160 which sounds pretty straightforward to pick up and will be (hopefully!) an easy way to help out while I get to know the codebase - is it a case of changing most/all defs to defonce? If so is there anything rigorous I can do to test that it's worked beyond leaving it on for a few hours?

dave15:03:30

hi @djtango -- that would be super helpful, thanks so much for offering to help out!

dave15:03:48

this is probably a great issue to start with

dave15:03:02

it could definitely be an issue of using defonce instead of def

dave15:03:45

we have a bunch of things (mostly defined as dynamic vars) that are reused that should probably be defonce'd instead of def

djtango15:03:17

oh the dynamic vars can be defonce'd?

dave15:03:19

particularly in the alda.server and alda.sound namespaces

dave15:03:35

i'm thinking of things like the *midi-synth*

djtango15:03:36

wasn't familiar enough with the inner workings to know whether it would be safe to change those

dave15:03:47

yeah, they should be able to be defonced

djtango15:03:53

I'll take a look the

dave15:03:23

one way that i've typically been able to reproduce the issue is to start a server and play around with it, then shut my laptop and come back later and re-open it and interact with the same server

dave15:03:34

my theory is that the shutting of the laptop has something to do with it

dave15:03:50

perhaps things are being somehow re-def'd when my computer comes out of standby?

djtango20:03:43

I'll take a look at that

dave22:03:35

@djtango: in case you weren't aware, you can run an alda server in the foreground (to see stacktraces, etc.) by running boot dev

dave22:03:17

or if you have a local build of alda (say in /tmp), /tmp/alda server will run a server in the foreground