Dave Johansen

It's the same output as before: ``` 2022/06/24 03:34:39 INF [RTMP] [conn 172.17.0.1:62286] opened 2022/06/24 03:34:39 INF [RTMP] [conn 172.17.0.1:62286] closed (invalid metadata) ```

I just pulled the latest changes and tried again and this is the line that's returning the error: https://github.com/aler9/rtsp-simple-server/blob/fb5aa7bbf23f89b3754157b4b8f3aa3788d7ae20/internal/rtmp/conn.go#L129

Oh sorry, I didn't realize that it was a branch. I just saw the version number in the builds and assumed it was from there. I did a build from...

Thanks for the effort. I'll take a look at the branch and see if I can get it working.

Ya, I figured that that might be case. It definitely would be nice to clean up, but isn't a major concern right now.

Something like this ``` const a = [{ bogus: true }, { count: 100 }, { missing: true }]; const b = flow([ filter(get('count')), get([0, 'count']), ])(a); ``` Could be...

Also, the number of arguments should be an indication of it being curried (i.e. 2 arguments to `get()` is a "standard call" and 1 argument to `get()` is a "curried...

Also, fixed the handling for of 0 in the path because it was being rejected for being falsy

I added code to fix #24 as well

I no longer have access to the codebase that I wrote this for, so I don't have a way to test/change anything with this PR. if you don't have the...