Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-04-17 Thread Tobi Knaup
Great to see the early crew coming out of the woodwork. You guys are awesome! On Wed, Apr 17, 2024 at 16:30 Marcel Neuhausler wrote: > Very very happy to see Benjamin and team at X contributing those patches, > including urgently needed support for cgroups v2, to the open-source > version. > >

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-04-03 Thread Benjamin Mahler
Just an update here, in late January we finished upstreaming our internal patches that were upstreamable. This amounted to 35 patches. The cgroups v2 work is ongoing, we're hoping to be mostly code complete by the end of this month. On Fri, Jan 12, 2024 at 6:01 PM Benjamin Mahler wrote: >

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-16 Thread Samuel Marks
Yeah it should be possible; things can get a little hacky but if you're not afraid to monkeypatch this can be solved. Send over the versions of each thing you're using, from Java JVM version (and vendor) for JNI to shared library versions. Ditto for CPython versions, architecture, and OS kernel

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-16 Thread Benjamin Mahler
> The Python 3 upgrade shouldn't be too difficult; happy to help out. Make > sure you duplicate your configuration so that CMake still works (happy to > help there also). Just message (privately or publicly). Yeah I think shatil mentioned the source translation was rather straightforward, but the

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-13 Thread Qian Zhang
Thanks Ben! I have let Shane know this to hold off on going into the attic, and happy to help on the Cgroups v2 support :-) Regards, Qian Zhang On Sat, Jan 13, 2024 at 8:48 AM Samuel Marks wrote: > On latest commit 5109b9069b62510ab6d0cc0c78a9ed8327d3986a `fd -epy | wc -l` > shows 73 files.

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Samuel Marks
On latest commit 5109b9069b62510ab6d0cc0c78a9ed8327d3986a `fd -epy | wc -l` shows 73 files. mesos/src/python/cli/src/mesos/http.py requires a trivial change to support Python 2 & 3. Everything else in that dir is fine. mesos/src/python/cli_new/lib/cli/util.py requires two lines to be conditioned

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Shatil Rafiullah
Do you require both Python 2 and 3 bindings to work, or can we make a clean migration to 3? I ask because there are breaking changes in C/C++ bindings going from 2 to 3, and supporting both will require conditionals rather than replacements of code blocks here and there. Dependencies may also end

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Samuel Marks
The Python 3 upgrade shouldn't be too difficult; happy to help out. Make sure you duplicate your configuration so that CMake still works (happy to help there also). Just message (privately or publicly). Good to see interest in Mesos remaining, Samuel Marks Charity

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Andreas Peters
Awesome, thanks so much Ben. :-) Am 12.01.24 um 23:55 schrieb Benjamin Mahler: As part of upgrading to CentOS 9 at X/Twitter, Shatil / Devin (cc'ed) will be working on: * Upgrading to Python 3 * Cgroups v2 support We will attempt to upstream this work for the benefit of other users. In

Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Benjamin Mahler
+user@ On Fri, Jan 12, 2024 at 5:55 PM Benjamin Mahler wrote: > As part of upgrading to CentOS 9 at X/Twitter, Shatil / Devin (cc'ed) will > be working on: > > * Upgrading to Python 3 > * Cgroups v2 support > > We will attempt to upstream this work for the benefit of other users. > > In

Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches

2024-01-12 Thread Benjamin Mahler
As part of upgrading to CentOS 9 at X/Twitter, Shatil / Devin (cc'ed) will be working on: * Upgrading to Python 3 * Cgroups v2 support We will attempt to upstream this work for the benefit of other users. In addition, we have several long-standing internal patches that should have been