Skip to content

feat: Migrating pilot client toward DiracX#8233

Draft
Robin-Van-de-Merghel wants to merge 3 commits intoDIRACGrid:integrationfrom
Robin-Van-de-Merghel:robin-migrate-client
Draft

feat: Migrating pilot client toward DiracX#8233
Robin-Van-de-Merghel wants to merge 3 commits intoDIRACGrid:integrationfrom
Robin-Van-de-Merghel:robin-migrate-client

Conversation

@Robin-Van-de-Merghel
Copy link
Copy Markdown
Contributor

@Robin-Van-de-Merghel Robin-Van-de-Merghel commented Jun 26, 2025

BEGINRELEASENOTES

*PilotManager
CHANGE: Migrate pilot client toward DiracX

ENDRELEASENOTES

@Robin-Van-de-Merghel Robin-Van-de-Merghel changed the title feat: Migrating client toward DiracX feat: Migrating pilot client toward DiracX Jun 27, 2025
@fstagni fstagni changed the title feat: Migrating pilot client toward DiracX [9.0] feat: Migrating pilot client toward DiracX Jun 27, 2025
@Robin-Van-de-Merghel
Copy link
Copy Markdown
Contributor Author

Issue with GetPilotOutput: as of now, we cannot use the new client with the old client at the same time (to help migrating a client bit by bit).

So, if a user calls GetPilotOutput, it will responds with an error because my new client does not have it.

@fstagni
Copy link
Copy Markdown
Contributor

fstagni commented Jul 15, 2025

Issue with GetPilotOutput: as of now, we cannot use the new client with the old client at the same time (to help migrating a client bit by bit).

So, if a user calls GetPilotOutput, it will responds with an error because my new client does not have it.

I think it's fine. This functionality (storing the pilot output in a MySQL blob) is already borderline useful, and given that we are finally getting somewhere with the pilot logging in diracx, I am thinking it would be OK to remove it. If for the moment replying with an error is OK.

@Robin-Van-de-Merghel Robin-Van-de-Merghel force-pushed the robin-migrate-client branch 6 times, most recently from 8114684 to 2410060 Compare August 5, 2025 08:08
@Robin-Van-de-Merghel Robin-Van-de-Merghel marked this pull request as ready for review August 5, 2025 09:42
@Robin-Van-de-Merghel Robin-Van-de-Merghel force-pushed the robin-migrate-client branch 2 times, most recently from d3a37ac to 5af196f Compare August 6, 2025 10:47
diracAdmin = DiracAdmin()
exitCode = 0
errorList = []
print("This command is not supported anymore with DIRAV V9.")
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
print("This command is not supported anymore with DIRAV V9.")
print("This command is not supported anymore with DIRAC V9.")


@classmethod
def export_deletePilots(cls, pilotIDs):
# Used by no one. We keep it for tests.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nah, if it is not used just remove it.

@fstagni fstagni force-pushed the robin-migrate-client branch from 1110fb2 to 3a2745d Compare March 25, 2026 14:14
- name: Building wheels
run: |
# Clone diracx
git clone --single-branch --branch robin-pilot-management https://github.com/Robin-Van-de-Merghel/diracx.git $GITHUB_WORKSPACE/diracx
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reminder to remove this

@fstagni fstagni marked this pull request as draft March 25, 2026 14:19
@fstagni fstagni changed the title [9.0] feat: Migrating pilot client toward DiracX feat: Migrating pilot client toward DiracX Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants