G2.1: Adopt new ServiceX frontend version 3.0

[matthewfeickert]

https://github.com/ssl-hep/ServiceX_frontend

• ServiceX API 3.0 Design notes from 2024-02-15
• https://github.com/ssl-hep/ServiceX_frontend/milestone/9
• Client 3.0 Release Checklist ssl-hep/ServiceX_frontend#347
• Update pydantic to v2 API ssl-hep/ServiceX_frontend#363

[matthewfeickert]

From the 2024-06-10 Executive Board meeting, we're going to need to have a more definite roadmap here. @bbockelm suggested a strategy meeting, which is realistically needed.

[matthewfeickert]

The ServiceX client v3.0.0 release is now out.

[matthewfeickert]

@ponyisi @gordonwatts @BenGalewsky Can you comment on the overall integration status of the v3.0.0 release of the client into existing workflows, like the AGC demonstrators or public demos?

[ponyisi]

Hi @matthewfeickert - I would also ping @alexander-held and @oshadura - what I do know is that we have a PR (pending a few small cleanups) for integrating this in the AGC repo with ATLAS and CMS examples. But I think that is more or less what has been done from the ServiceX side.

[matthewfeickert]

I'm also noticing that in the ServiceX client docs for FuncADL Query Type that the full user docs are listed as @gordonwatts's https://github.com/gordonwatts/xaod_usage Jupyter Book. However, that Jupyter Book isn't using the v3.0.x API, so this will be important to update for us to be able to say that the v3.0.x client has been adopted.

Cross reference issues:

• docs: FuncADL Query Type documentation links to reference not using current API ssl-hep/ServiceX_frontend#493
• Update to ServiceX client v3.0.x API xaod_usage#23