Giuseppe
Giuseppe
Edit: @johscheuer my tab wasn't refreshed and I didn't notice your reply, thanks! > I would need to look inside the code to answer your question properly (I'll try to...
I built some automation for this ~9 months ago: https://github.com/gm42/fdb-build-support See also the scripts I added in https://github.com/gm42/foundationdb But of course upstream support would be great & better.
> We now have binaries for linux arm64 as part of the release process. Are these going to be part of some future release? I cannot find them in recent...
Thanks @johscheuer @ammolitor! Would it be possible to get them built also for the next non-pre-release? I am trying to stick to stable versions due to that big disclaimer: >...
It must be a race. I can reproducibly cause this panic, but when I add an atomic integer to sequence the calls to pgx, it disappears.
> I'd like to get rid of all of the finalizers first. I second this; there's no clean way to map C++ destructors to Go finalizers and obtain reliable behavior...
@glycerine if it can be of any help, I have submitted all my PRs to `main`. I think that needs to be done anyways before any backport on release branches.
I have created a PR #12052 to start discussing the removal of finalizers; feel free to chip in the discussion there.
@jzhou77 any suggestion? First it should established whether a whitespace formatting check in CI is desirable or not, then we can focus on how to do that.
There are still some `e` for `element` renamed to `err`, and the whitespaces change. Aside from that, LGTM; thanks!