Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Training: Advanced Debugging I #11855

Open
amaltaro opened this issue Jan 9, 2024 · 0 comments
Open

Training: Advanced Debugging I #11855

amaltaro opened this issue Jan 9, 2024 · 0 comments
Assignees

Comments

@amaltaro
Copy link
Contributor

amaltaro commented Jan 9, 2024

Impact of the new feature
WM in general

Is your feature request related to a problem? Please describe.
Sharing knowledge and empowering WM/Ops to understand and debug the system. Sub-task of #11837

Describe the solution you'd like
Topic of this ticket is: Advanced Debugging I.
Specific debugging items in the current issue are to be elated to the process of deploying and utilizing a common debugging environment:

  • Deploying a WMAgent virtual environment

  • Take one particular use case and address it during the session: WorkflowUpdater component should not crash on container DID not found error #12033

  • Run standard services from source and from Pypi package - stress the difference

  • Run a WMAgent component in standalone mode with wmagent-component-standalone

    • Explore Modules && Objects in the global scope during interactive session
    • Execute the main algorithm for a component
    • Execute a module's/component's methods standalone
    • Execute a specific DAO from inside the interactive session of wmagent-component-standalone
    • Execute a DAO from the virtual environment
    • Set a break point within the code
    • Run with iPdb mode activated within the interactive session
    • Run the code through Pdb
    • Search one DID with the current module's Rucio instance
    • Try to simulate the behavior explained at the issue chosen for this session WorkflowUpdater component should not crash on container DID not found error #12033
    • Provide a few line solution to the issue
    • Test the solution interactively
    • Create a PR from the so tested solution
  • Extra (if the time allows):

    • Patch components on a running/active agent with the so created PR, using: patchComponent.sh
    • Patch a central services instances, using: patchCluster.sh
    • Run/Create unit tests within the environment

For the expected solution, please refer to the meta-issue for further details (in short: documentation + recorded presentation).

Describe alternatives you've considered
None

Additional context
None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

3 participants