Clojurians Log v2

Invoke API has LogType parameter, which set to Tail (when InvokeType is RequestResponse) returns last 4kB of logs https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html#API_Invoke_RequestSyntax

That might do it

aws cli has this wrapped, but we can use our lib :)

a bit shortened version of this instruction could help https://docs.aws.amazon.com/lambda/latest/dg/with-userapp-walkthrough-custom-events-invoke.html

but I guess people might already know how to get logs from Cloudwatch, in this particular case it might be that we swallow the actual cause

or say the java crypto classes, a field isn’t serialized (I think) and stack just says “npe”: https://circleci.com/gh/portkey-cloud/portkey/62

ahh

love to see portkey growing 😄

so whipped a test for instaparse, similar serialization issue I think

maybe I’m pessimist but at least it breaths and is kind of warm 🙂

lol

long term view

@viesti uploaded a file: https://clojurians.slack.com/files/U06QSF3BK/FB4CXRJ20/null.clj

so far it’s still growing

yeah, along these lines https://twitter.com/richhickey/status/1004757794183106560

last summer had many more of these exceptions, should not forget my veteran status 🙂

lol, true !

https://circleci.com/gh/portkey-cloud/portkey/65

so, you will find an example of the generated fns ser and resp in here

https://github.com/dupuchba/aws-clj-sdk/blob/4d02a66171d606d342f522715e441ce76081efe5/src/portkey/aws/lambda.clj

it compiles but there is an error in resp generation (quick fix, I just don’t destructure the input)

and we still have ser-create-function-request somehow 😞

nope fixed

sorry for spaming

=> https://github.com/dupuchba/aws-clj-sdk/blob/8679e7a4b42a1c65860a44b5cd4f4db238457798/src/portkey/aws/lambda.clj

next step => 1) fix destructuring for resp 2) integrate with the existing -rest-json-call

and make it work 😄

@baptiste-from-paris had a quick glance: dudn’t you switch resp and req?

no no, reload the file

ser does serialization & resp gather inputs by request type and required inputs

(clojure.core/defn resp-list-event-source-mappings-request [resp-input48914] (clojure.core/cond-> {} (clojure.core/contains? resp-input48914 "EventSourceArn") (clojure.core/assoc-in [:query-string "EventSourceArn"] (ser-arn resp-input48914)) (clojure.core/contains? resp-input48914 "FunctionName") (clojure.core/assoc-in [:query-string "FunctionName"] (ser-function-name resp-input48914)) (clojure.core/contains? resp-input48914 "Marker") (clojure.core/assoc-in [:query-string "Marker"] (ser-string resp-input48914)) (clojure.core/contains? resp-input48914 "MaxItems") (clojure.core/assoc-in [:query-string "MaxItems"] (ser-max-list-items resp-input48914))))

for example

Resp is for response not for request > resp gather inputs by request type

looool

it’s just a little typo

😄

That’s what I said :-)

req/resp, who cares ? 😄

loool

I really need to leave paris for few days 👌

Only us who deal with code gen. Let’s all agree to mentally switch request and response.

lol, I’ll fix it immediatly, was it req<- ?

Iirc yes

https://github.com/dupuchba/aws-clj-sdk/blob/6f47f0df1d689ab4d25d8dffd76fb06984e66118/src/portkey/aws/lambda.clj

so I just fixed destructuring for req<-*, it should be close to something working

https://github.com/dupuchba/aws-clj-sdk/blob/55212103876761d61afd0c5b387afbf3c77b730f/src/portkey/aws/lambda.clj

so this function request =>

(req<-create-alias-request {:function-name "The Name" :name "kikoulol" :function-version 3})

gives =>

{:uri {"FunctionName" "The Name"}, :body {"Name" "kikoulol", "FunctionVersion" 3}}

all this work for this 😂

portkey setting hair on fire? :)

lol