#hypothes.is

<sheetaluk> great. thx @seanh @nick

<nick> and then as Sean says, you just need to make sure the database are created

<seanh> nick: How does a `.env` file work? You just source it from your shell?

<nick> @sheetaluk: you can do that with something like:

<nick> `brew install postgresql`

<sheetaluk> i did something like that

<nick> `createdb -h docker -U postgres h`

<nick> and then put in the default docker postgres password (which i think is just `postgres` again)

<nick> and then do the same with `h_test`

<nick> @seanh: pretty much

<nick> I use https://github.com/kennethreitz/autoenv, but that's all it does

<seanh> Cool, was wondering if there was something special about the name or if it was just a convention. I should make one of those

<sheetaluk> oh look!

<sheetaluk> https://www.dropbox.com/s/qyidvhc1g5su0x8/Scree...

<nick> wooot!

<nick> nice work

<nick> sorry it's a bit of a faff on a Mac

<sheetaluk> umm. wait. https://www.dropbox.com/s/qyidvhc1g5su0x8/Scree...

<sheetaluk> argh. how do i make it show my img preview

<sheetaluk> actually that was relatively simple

<sheetaluk> except for docker's localhost vs my real loclahost and the h db issue

<seanh> You can actually upload them straight to Slack with the + button to the left

<nick> @sheetaluk: all praise to @robertknight for doing SO MUCH AMAZING WORK to make the frontend build nice

<sheetaluk> i have a keyboard shortcut that copies the preview link

<sheetaluk> ok great. im going to continue on now. i think from here it should be easier

<nick> @sheetaluk: you do know we're not expecting you to start until March, right ;)

<nick> of course, we're very happy to have you here! :)

<sheetaluk> @nick: i know... i really hate todos. setup dev env in my mind is a todo... its in the way of doing real work (i think this is real work too)

<nick> but I hear you might have one or two other things to occupy your time these days... :)

<sheetaluk> i really enjoy checking off things on my list

<nick> great, ok then

<nick> dev env :heavy_check_mark:

<sheetaluk> oh yeah. that is true too. i have a HUGE list of things to accomplish before i start work. haha

<sheetaluk> how did you do that check mark

<nick> I think it's an emoji

<nick> although I have a keyboard expansion set up for it

<sheetaluk> did you actually sift through them visually

<nick> yeah, `:heavy_check_mark:`

<sheetaluk> ok.

<sheetaluk> ha

<nick> I have all kinds of weird textexpander things set up :clubs:∇

<nick> ❡

<nick> why do I even have this stuff?

<sheetaluk> hahaha

<nick> a lot of it dates back to when I was taking notes on a computer

<sheetaluk> dates back to? how back?

<sheetaluk> wait. and how to you take notes now?

<nick> look, @wyan: Σ a_i |ψ_i⟩

<nick> :)

<sheetaluk> pysics student(s)!

<nick> back when I was a student, in... 2007-11

<nick> and yes :)

<sheetaluk> (clearly im not even an english major - can't spell)

<nick> and now I like paper

<nick> because it doesn't break as often

<sheetaluk> haha!

<nick> or ever

<sheetaluk> i love old paper. i can smell it for hours

<sheetaluk> Does anyone know who maintains the iannotate website?

<nick> us!

<nick> in particular @conor, the lucky guy

<conor> Uh oh, what have I done wrong

<conor> I am but a simple novice

<sheetaluk> haha. i signedup for iannotate

<conor> I saw

<seanh> Hmm, now I want textexpander for linux

<sheetaluk> oh btw! Here is some cake that I promised:

<sheetaluk> https://s-media-cache-ak0.pinimg.com/236x/47/1d...

<sheetaluk> real cake when we meet

<nick> CAEK

<nick> I <3 CAEK

<chdorner> @seanh: by the way, when you run the postgres migration, make sure to do it from master, it might be broken in the `postgres-read-write` branch. will try and fix it today

<nick> my previous jobs convinced me that cake is the glue that holds a team together

<chdorner> @nick: I don't know, I heard cake is so much better than caek

<nick> CAEK

<nick> http://friendlydigital.co.uk/long-live-gds/

<nick> Ctrl-F "caek"

<nick> sorry

<nick> it's a habit

<sheetaluk> hahaha!

<sheetaluk> i had to look up caek

<sheetaluk> and i found this:

<sheetaluk> eye leik pieh, but caek is better.

<sheetaluk> i really love wfh. if i dont get something i can look it up immedietly. but in person, its awkward when i run to my computer!

<nick> that happens to me a lot with references @conor makes

<conor> Bleeding. Edge.

<nick> Folks, this is amazing.

<chdorner> @nick: is this the Pythonic way? ``` # h/api/models/elastic.py class Document(document.Document): __analysis__ = {} def __init__(self, d, annotation=None): super(self.__class__, self).__init__(d) self.annotation = annotation ``` Since I want to use the `elastic` models in the migration, so I need to pass the annotation around (and for DocumentURI/Meta the document as well)

<nick> `Document` rather than `self.__class__`, but otherwise yep.

<nick> why does the document object need an annotation?

<chdorner> the uri and meta need it for the claimant

<chdorner> (those are ES documents, not PG)

<nick> and why do the ES documents need to know claimant URIs?

<nick> (sorry, I've probably missed some context here)

<dwhly> Welcome to my ridiculously early morning.

<nick> holy crapballs @dwhly go back to bed!

<chdorner> nick: so we have exactly the same API, meaning we can use the elastic.Document/DocumentURI/DocumentMeta for the migration, and everything will work when we run the elastic.Annotation through the new JSON presenters

<nick> are you up for a flight to BOS?

<nick> @chdorner: ok, fair enough -- only thought would be just pass the claimant URI rather than the whole annotation?

<nick> @dwhly: you're already at SFO!? did you even go to bed?

<chdorner> nick: sure, that works as well, haven't checked yet if we need anything else from it

<dwhly> Till 3:30am! Yay!

<chdorner> nick: need it for the created/updated as well, but it's probably cleaner to add three kw args instead of passing the whole annotation arouynd

<sheetaluk> @nick qq: when i run make test i see nothing but Es. Am I missing something here?

<sheetaluk> E OperationalError: (psycopg2.OperationalError) FATAL: database "h_test" does not exist

<sheetaluk> actually, \list show htest

<sheetaluk> not h_test

<nick> ah, right

<nick> so just update your TEST_DATABASE_URL, then

<sheetaluk> yeah

<sheetaluk> ok. So all tests pass and i have the app running on http://127.0.0.1:5000/

<sheetaluk> is there anything else I need to do?

<sheetaluk> @nick: ^

<nick> @sheetaluk: not right now :)

<nick> that's awesome, though

<nick> working dev env, passing tests, minimal help :ok_hand:

<sheetaluk> ok. great! im so happy. so see you on Thirsday then :)

<sheetaluk> actually the docs are really good

<sheetaluk> its never happened to me that setup has been so easy!

<nick> see you on Thursday!

<nick> Have a lovely couple of days of freedom!

<sheetaluk> haha

<sheetaluk> okies. bye guys!

<nick> byeeee!

<seanh> nick Shall I add this codecov thing to bouncer as well then? I had been wanting to add coveralls

<nick> yep!

<nick> it's much better put together than coveralls

<seanh> Ok, yeah it looks better

<nick> and it doesn't require access to private repos to work

<wyan> ohai teh interwebs are back with me. caek is good :browsers:

<wyan> @nick: reading your comments on `csp` now, my plan for the rest of the day is implement those and what's remaining of the ones related to sentry

<nick> :+1:

<nick> @wyan: grafana now starts on boot :)

<wyan> excellent! :)

<robertknight> nick: I have a PR with the tools to submit JS bundles and sourcemaps to Sentry as part of the release process. There is a Gulp task that gets API keys and other info (Sentry org, Sentry project, release version) from env vars and then uploads JS bundles and sourcemaps as part of the release. I've tested with my personal Sentry account. To enable it for H we'll need to set the env vars and run `gulp upload-sourcemaps` during tagged release bui

the assets have been built.

<nick> @robertknight: sounds great!

<robertknight> Hmm, I have JSHint configured to allow ES6 syntax in that PR (used lightly in the Gulp scripts for template strings). Hound isn't picking that up that config change though.

<wyan> what's the preferred way to do `a = cond ? b : c` in python?

<wyan> `a = b if cond else c` ?

<wyan> or rather should I unwind the `if`?

<nick> @wyan: if it's readable, the ternary is fine

<nick> but if the condition or `b` or `c` are long and complicated then just use a couple of lines

<wyan> I've gone for splitting it, cause otherwise I have to split the line using `\`

<wyan> cause `b` and `c` are rather long strings

<nick> yep