10:10 <raz> hmm, is there a way to get proper backtraces out of a static release binary

10:10 <raz> i compiled with --release --static --link-flags "-static -lunwind"

10:10 <raz> but still seeing '???' :(

10:12 <raz> to be precise: ex.backtrace is ["???","???","???","???","???","???","???"]

10:13 <raz> (which confuses me a bit, i could've sworn i saw near-complete backtraces printed to the console when originally testing the compile flags. hm)

11:32 <alex``> does `crystal build` generate the binary in the current directory or the directory of the source file?

11:32 <alex``> https://crystal-lang.org/reference/using_the_compiler/

11:33 <alex``> not sure if it would have been `crystal build src/hello_world.cr`

13:03 <FromGitter> <yxhuvud> It lands in the current dir

14:36 <FromGitter> <Blacksmoke16> https://play.crystal-lang.org/#/r/8gp9 does it make sense this works?

14:36 <FromGitter> <Blacksmoke16> i guess a module is considered a parent type?

14:37 <FromGitter> <straight-shoota> @Blacksmoke16 Exactly

14:40 <FromGitter> <Blacksmoke16> makes sense

15:03 <FromGitter> <Nicolab> Hello, ⏎ ⏎ I can't figure out how to compare 2 dates: ⏎ ⏎ ```Time.utc.shift(seconds: 10) > Time.utc ⏎ => true``` ... [https://gitter.im/crystal-lang/crystal?at=5e2efbb4a420263e03ab2daf]

15:03 <FromGitter> <Blacksmoke16> thats the right way

15:04 <FromGitter> <Nicolab> It doesn't work

15:04 <FromGitter> <Blacksmoke16> why should that be false? you're shifting the current UTC time 10 seconds into the future

15:04 <FromGitter> <Blacksmoke16> so its going to be "greater" than the time it actually is

15:04 <FromGitter> <Nicolab> Time.utc.shift(seconds: 10) is before utc (now)

15:04 <FromGitter> <tenebrousedge> no

15:05 <FromGitter> <tenebrousedge> Time.utc.shift(seconds: -10)

15:05 <FromGitter> <Blacksmoke16> https://play.crystal-lang.org/#/r/8gpe

15:05 <FromGitter> <Nicolab> Oooh !

15:05 <FromGitter> <Blacksmoke16> ^

15:05 <FromGitter> <Nicolab> ^^ I check

15:05 <FromGitter> <Blacksmoke16> https://crystal-lang.org/api/master/Time.html#shift(seconds:Int,nanoseconds:Int):Time-instance-method

15:05 <FromGitter> <Blacksmoke16> > Positive values result in a later time, negative values in an earlier time.

15:06 <FromGitter> <Nicolab> I wasn't paying attention, thanks, guys :)

15:06 <FromGitter> <Blacksmoke16> np

17:26 <repo> does someone know if crystal-pg has issues with pg 12?

17:26 <repo> ["SELECT log_messages.id, log_messages.timestamp, log_messages.message, log_messages.level, log_messages.meta FROM log_messages WHERE ts_message @@ websearch_to_tsquery('foobar') AND ( timestamp > 2020-01-13 18:24:04 +01:00 OR timestamp < 2020-01-20 18:24:04 +01:00 ) AND meta @> {\"foo\" => {\"bar\" => 15}}"]

17:27 <repo> Unhandled exception: syntax error at or near "18" (PQ::PQError)

17:27 <repo> seeing this

17:27 <FromGitter> <tenebrousedge> should the timestamp be in quotes?

17:27 <repo> i'm not writing that query

17:28 <repo> hm maybe it's also an avram issue

17:28 <FromGitter> <tenebrousedge> right, but is that what the syntax error is?

17:28 <repo> yeah i guess

17:28 <repo> same for the jsonb value

17:28 <repo> i'm using a prepared statement

17:28 <repo> where(sql, args: args)

17:29 <repo> (with avram)

17:29 <repo> so sql in this case is just ts_message @@ ? AND ( timestamp > ? OR timestamp < ? ) AND meta @> ?

17:30 <repo> ah actually ts_message @@ websearch_to_ts_query(?) AND ...

17:33 <repo> hm there's this line: params = args.map { |arg| PQ::Param.encode(arg) }

17:33 <repo> in pg/src/pg/statement

17:33 <FromGitter> <tenebrousedge> hmm

17:34 <repo> so not sure, could be that the to_sql method is giving me just a text reprensentation of the actual query

17:35 <raz> both crystal-db and crystal-pg are unfortunately still riddled with problems (conn pool fails under various conditions, prep statements mem leak etc.) . wouldn't be surprised if they haven't gotten to fully test with pg12 yet

17:35 <repo> mmh

17:35 <FromGitter> <tenebrousedge> sounds rough :/

17:36 <FromGitter> <tenebrousedge> is there a PG12 feature you need?

17:36 <raz> it was when i last tried :( but it's being worked on i think

17:36 <repo> teardown: no

17:36 <repo> tenebrousedge:

17:36 <repo> i can use 11

17:36 <FromGitter> <tenebrousedge> :plus1:

17:37 <repo> but it's obviously not a solution :D

17:37 <repo> just a workaround

17:38 <raz> maybe try filing a ticket on crystal-pg

17:38 <raz> perhaps it's an easy fix - and in any case they should be made aware of it :)

17:41 <raz> in their defense, pg is really pumpin' out those major versions lately

17:41 <raz> we had 9.x for 7 years

17:42 <raz> and now they bump it up ever year

18:00 <FromGitter> <straight-shoota> repo, what makes you think this isssue is with psql 12 only?

18:01 <FromGitter> <straight-shoota> Did you actually test the query on 11? I doubt it would work there either.

19:04 <sorcus> Crystal has `promise` in stdlib like JS Promise?

19:05 <FromGitter> <Blacksmoke16> not that i know of

19:06 <jhass> we have a future

19:10 <sorcus> Hmm...

19:11 <jhass> https://crystal-lang.org/api/0.32.1/toplevel.html#future(&exp:-%3E_)-class-method

19:12 <jhass> https://crystal-lang.org/api/0.32.1/toplevel.html#lazy(&block:-%3E_)-class-method

19:12 <jhass> https://crystal-lang.org/api/0.32.1/toplevel.html#delay(delay,&block:-%3E_)-class-method

19:13 <sorcus> jhass: Cool B-)

20:16 <Stephie> future has been a bit neglected though

20:16 <Stephie> would be nice if it had a bit of a rework

20:21 <raz> ohhh that looks handy <3

20:21 <raz> how is it neglected, you mean the internal impl?

20:24 <raz> lazy() looks neat too. i gotta find me some excuses to use them

20:32 <FromGitter> <watzon> Future doesn't work great if you're looking for something like JS promises, and unfortunately neither do any of the current promise implementations

20:54 <FromGitter> <tenebrousedge> js 😬

21:11 <raz> hum. but why would anyone look for anything JS to begin with?

21:13 <raz> in languages with an actual concurrency model promises can be a convenience for certain special cases. in JS they're merely the least horrible syntax available to do concurrency at all. ¯\_(ツ)_/¯

22:15 <FromGitter> <dscottboggs_gitlab> o/

23:14 <FromGitter> <Blacksmoke16> o/

23:35 <FromGitter> <jesfre_gitlab> o/