No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Untitled.txt

I'm getting this when running `pulumi logs -f` on a beefy machine while following logs from 2 lambda functions in one stack.

It works for a while, then seems to break when there are new log entries. Running w/ a single function didn't break a thing for 12+ hours

Interesting - I don't think we've ever seen that before - could you open an issue so we can investigate?

I can open an issue but my Ubuntu kvm VM I was working from went down last night so I won't have much detail about the context to share. I'll try to get it up then will post more details or see if I can replicate it in another environment.