Fork me on GitHub
#portkey
<
2018-04-27
>
viesti12:04:10

making clj-http work would greatly increase usability of portkey 🙂

viesti12:04:42

we need to hijack the part of the brain of @cgrand where the solution for this problem is boiling 🙂

cgrand12:04:58

this peculiar pot used to boil but has been put in the freezer

viesti12:04:19

at times thinking that I need to learn to train my brain to be more efficient, or figure out how to calm the part that makes me do too large amount of context switch 🙂

viesti12:04:08

cold brewing solution

cgrand13:04:55

@viesti I’m struggling digging up init errors from cloudwatch. Could you copy/paste them in the issue?

viesti13:04:59

eek, my aws certification expired, wonder if I’m able to 🙂

viesti13:04:27

hum, there’s a test, which might output even better the error

cgrand13:04:44

planned skills obsolescence

viesti13:04:55

remembering that what ends up into Cloudwatch is the Attempting to call unbound fn: #’clj-http.core/request: java.lang.IllegalStateException

cgrand13:04:59

that’s what ends up in CloudWatch at request time

cgrand13:04:25

the actual error happens when the static init is performed

viesti13:04:44

yes, as far as I rememer, that doesn’t end into Cloudwatch, but let’s see

viesti13:04:04

so made a test, don’t find initialization logs in Cloudwatch

viesti13:04:37

which is a bit odd

viesti13:04:46

maybe the stub swallows it?

cgrand13:04:55

No, I remember reading them. Not in cloud watch then?

viesti17:04:28

Nope. Can't now think of place to look from in AWS. But I remember making the clj-http test so that it reveals kryo errors: https://github.com/portkey-cloud/portkey/blob/e7492b086370bbb5f74032000cd649398d1bcc95/test/portkey/core_test.clj#L223

viesti13:04:18

hmm, didn’t help

viesti13:04:44

we found place that Cloudwatch logging doesn’t cover? 🙂

viesti13:04:15

hmm, might actually be that only requires-time stdout/stderr is logged

viesti13:04:22

but not process start-time output

viesti13:04:17

butbut…

viesti13:04:00

failure in the static initializer would result in handler not being assigned…

cgrand13:04:13

static init recreates vars and populates them, failure occurs during population of vars so some vars are left unassigned

viesti13:04:57

still we get a handler

viesti14:04:13

dealing with errors is error prone