> :mega: Release Candidate I just published `0....
# general
t
📣 Release Candidate
I just published
0.45.3-next.16
which contains the new speed improvements on invoking your local functions. I'm hoping this can be our release candidate - I fixed the issue with the native dependencies preventing it from running on MacOS. Would appreciate giving it a shot and letting me know if there are any issues.
k
I will try it now 🙂
Ok this is very cool 😮
@thdxr one thing that I am noticing that is different is the logs, for some reason they are not correct
Some of the logs have
/n
and for some reason they show up all wrong and mixed
E.x Before
Copy code
2021-10-08T14:27:13 DEBUG item: Querying items{
  "properties": {
    "PK1": "organization:nLguHGdi8W2NjaUnLRji5B:program:oaJooS3moo7yEp1UBvUga8:item:D-F-26"
  },
  "params": {
    "index": "GSI1",
    "limit": 1
  }
}
Now
Copy code
} } "limit": 100I1",tion:nLguHGdi8W2NjaUnLRji5B:program:oaJooS3moo7yEp1UBvUga8:item:D-F-2"T16:24:08 DEBUG item: Querying items{
t
Ah think I noticed that as well, let me take a look
r
Ran a very quick check and looks to work well on MacOS
t
@Kujtim Hoxha I was having a tough time replicating your issue but I pushed a guess fix to 0.45.3-next.17 - let me know if that solves it
k
This fixed it 🤩
you are awesome man
t
nice!
Then looks like we're gonna be releasing this week 🚀
k
O one other thing I noticed that might just be me is if the connection breaks up (internet connection or the aws access tokens expire) there is an infinite loop that shows errors and you can not stop them without closing the terminal completely
It happened twice to me and I do not know if it is just my setup
d
Is this part of the v0.46 release?
j
@Dennis Dang I think it’ll be in 0.47. @thdxr not sure if you noticed Kujtim’s issue here.
t
yep fixed that today
j
Right on 👌
t
And yeah planning for 0.47 if I can get the broken tests fixed
k
Awesome 😎 I have been using the release candidate for a while now and I don't want to switch back 😂 it is just orders of magnitudes better
j
That’s amazing to hear!
d
@thdxr have you shared somewhere why it's so much faster?
t
I wrote a little bit about the underlying mechanism: https://thdxr.com/post/how-aws-lambda-runs-your-code Doesn't go into full detail but the gist of it is 1. We're using the same API clients aws uses (with some modifications) 2. We used to get rid of the function after invocation and start fresh again. Now we do it more like how AWS does it in production and keep the function around for subsequent invocations