Fork me on GitHub
#clojure-uk
<
2018-03-21
>
thomas08:03:58

moin moin morning

dominicm08:03:14

@mccraigmccraig do you get a lot of these?

mccraigmccraig09:03:25

i don't see any exceptions at all with "manifold.stream.graph" in the message @dominicm

mccraigmccraig09:03:05

i've no idea why not - my logging filters wouldn't seem to filter them out - https://gist.github.com/mccraigmccraig/2215b44ecebc9c48b2b11b60b6398ecc

mccraigmccraig09:03:12

and it's not because i'm super up-to-date with byte-streams

mccraigmccraig09:03:17

[yada/core "1.2.2"]
     [byte-streams "0.2.2" :exclusions [[org.clojure/clojure]]]

dominicm09:03:29

I just bumped us now.

dominicm09:03:41

inb4 your logging never worked.

dominicm09:03:49

do you have an unhandled exception, uh, handler?

mccraigmccraig09:03:42

yes - it should log and send to sentry... i wonder if it's still working

dominicm09:03:01

@mccraigmccraig I think the .graph part is from something else, our exn_message is just "error in manifold.utils/future-with"

dominicm09:03:25

that might be due to how we log though

mccraigmccraig09:03:00

no future-with occurring in my logging either - i'm going to have a look at our unhandled-exception-handler

yogidevbear09:03:44

Morning. Off for a run :running:

yogidevbear10:03:48

How is everyone doing today?

peterwestmacott10:03:25

a little under the weather tbh, yourself?

yogidevbear12:03:45

It's all this sunny weather that's make you ill @peterwestmacott😉 Hope you feel better soon.

yogidevbear12:03:17

I'm feeling okay. Bit stiff after the morning run, but feeling positive

yogidevbear12:03:30

Been a while since I had a regular running pattern going

chrjs12:03:25

^ Well, now I’m feeling guilty because I haven’t been for a run in months.

chrjs12:03:52

I did couch to 5k at the end of last year, and got to the second last week. Then it got really wet and cold. ¯\(ツ)

chrjs12:03:55

But good on you 💪

mccraigmccraig16:03:35

🚵 is more fun

dominicm18:03:51

@mccraigmccraig is your logging working?

mccraigmccraig19:03:06

apparently not @dominicm ... but i’ve punted fixing it to the next release