Fork me on GitHub
#admin-announcements
<
2016-02-03
>
crocket04:02:35

What is EuroClojure good for other than some fun? Arguably, people learned already or can learn the contents of presentations on the internet. Also, it is more expensive in terms of time, money, and energy than learning on the internet.

crocket04:02:43

Probably, the bandwidth of information exchanges could be wider in conferences than on the internet.

crocket04:02:04

I tend to stay home as part of optimization. Asynchronous communication is usually superior to synchronized communication.

seancorfield05:02:30

Perhaps discussion of the pros and cons of events belongs in #C03RZRRMP ? (this is an unpartable channel and 4,800 people have to read this)

glenjamin08:02:53

at the risk of sending an unpartable message to those 5k people - you can change notification settings in #C03RZGPG1 to “mute”, which causes it to never be marked unread. I find this a good way of not having to read every message

samflores12:02:49

thanks to @rbf, clojurebot now runs Clojure 1.8.0 👏:skin-tone-2:

reefersleep14:02:05

How does clojurebot work?

reefersleep14:02:31

I mean, you can get it to eval stuff, right? simple_smile

reefersleep14:02:50

@clojuretwbot: (+ 1 3)

solicode14:02:46

I think there’s a bit of a delay though

reefersleep14:02:48

Keeps timing out

solicode14:02:52

There we go

samflores15:02:12

@reefersleep: it's deployed on Heroku using a free dyno... it sleeps from time to time 😞

samflores15:02:14

I think I'll try to port the keepalive thing from hubot

glenjamin15:02:50

if you want to avoid paying, you have to stay under 16 hours a day

samflores15:02:35

I have a hubot bot running on a free dyno 24/7 using the keepalive

rbf16:02:41

big thanks to @samflores for the generosity to allow in a fair way the clojure-bot dyno to be 24/7 awake and quickly responsive 😃 :+1: certainly very useful for a 5K users slack community 🎉

jaen16:02:23

@samflores: huh, 24/7? Are you 100% sure of that? I was pretty sure Heroku changed free dynos to force them to sleep 8 hours a day.

akiva16:02:13

They run constantly but the free dynos reboot automatically once a day.

jaen16:02:07

@akiva, @samflores: this seems to suggest that's not true - https://devcenter.heroku.com/articles/dyno-sleeping#quota > Applications running a free dyno can be active for no more than 18 hours in a rolling 24 hour period. If the app reaches 18 hours of activity, the app enters a recharging state.

jaen16:02:38

Basically what made me choose Openshift instead (until I learned they have outdated PostgreSQL there)

jaen16:02:45

If that's inaccurate would be nice to know.

akiva16:02:47

Okay, yeah, I remember that now. It’s one of the many reasons why I fled to Digital Ocean.

jaen16:02:45

It's paid though, sometimes you can't/don't want to.

jaen16:02:04

Openshift (if you're content with PSQL 9.2) is a good alternative though in that case.

akiva16:02:45

I don’t mind paying. I run a bot there, my blog runs from there, and it’s a really solid service that allows me to customize to my heart’s content.

samflores16:02:52

@jaen in the same page: There is a web dyno that is receiving traffic. I assume a very low traffic bot like the one I mentioned would not be considered active even when the dyno is not sleeping (but I'm just guessing)

codefinger16:02:59

@jean yes that's the correct policy (i work at heroku)

codefinger16:02:55

i suppose it make sense to switch to DO and save $2 if you like spending your weekending updating system packages simple_smile

codefinger16:02:06

when the free dyno is not used (i.e. does not receive traffic) it goes to sleep. during a 24 hours period it must sleep for at least 8 hours

jaen16:02:42

@akiva: in general would not mind paying; but paying for a server to run a university project doesn't make sense to me. And it had to be running 24/7 because the project was about monitoring another system and reacting to changes in it.

jaen16:02:33

Fortunately at some later point it turned out someone still didn't redeem their github credit at DO so we moved there (some later stage required persistence and wrote that with 9.4 in mind before I realised only 9.2 was supported).

akiva16:02:32

Yeah. Makes sense.

a_covar21:02:29

hey guys ! we just launch an http://experiment.com campaign https://experiment.com/projects/can-data-management-tools-improve-research-efficiency-and-reproducibility … I hope you can support us and help us spread the word .

reefersleep22:02:47

@samflores: I think we'll manage, even with the sleep simple_smile

reefersleep22:02:58

It's just nice to have!

meow22:02:10

love that name @reefersleep metal

reefersleep23:02:25

awesome, @meow ! 😄

reefersleep23:02:24

I don't get it.

reefersleep23:02:26

Can anyone see my mistake?

reefersleep23:02:09

ah, I get it.

akiva23:02:21

Actually, (get (vec args) random) is what you want. You can’t access a list by index and args comes as a list.

reefersleep23:02:07

yeah I figured it out too simple_smile

reefersleep23:02:40

I've made this mistake before, thinking I could use a list as a vec.

meow23:02:19

someone should create a clojurebot channel