damccorm commented on issue #31913: URL: https://github.com/apache/beam/issues/31913#issuecomment-2247637965
Hey @kaushikabhishek87 this should be fixed as part of the next release process (2.59.0). We bump our go version as part of our release process to pick up the latest changes (based on https://go.dev/doc/devel/release). Note that this shouldn't really impact Beam Python since the underlying go logic is just starting the Python executable, and I don't believe we make use of these methods. Passing to @lostluck to resolve once we release 2.59.0 (or at least the version bump is in) > Seems like there are already PR around it but they are closed/no activity, wanted to know if there is any eta on this. Note that these don't actually address the underlying issue which requires a go version bump. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
