-
Notifications
You must be signed in to change notification settings - Fork 186
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
Fix error when clicking on the multiple agent selector #5094
Fix error when clicking on the multiple agent selector #5094
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.16 4.4-7.16
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.16
# Create a new branch
git switch --create backport-5094-to-4.4-7.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c10704529b4351e3d8b2fe7fed0c8b35734e53d9
# Push it to GitHub
git push --set-upstream origin backport-5094-to-4.4-7.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.16 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.10 4.4-7.10
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.10
# Create a new branch
git switch --create backport-5094-to-4.4-7.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c10704529b4351e3d8b2fe7fed0c8b35734e53d9
# Push it to GitHub
git push --set-upstream origin backport-5094-to-4.4-7.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.10 Then, create a pull request where the |
* fix(): fix console error when clicking in multiple agents selector * changelog: add entry Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com> (cherry picked from commit c107045)
* fix(): fix console error when clicking in multiple agents selector * changelog: add entry Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com> (cherry picked from commit c107045)
…gent selector (#5095) Fix error when clicking on the multiple agent selector (#5094) * fix(): fix console error when clicking in multiple agents selector * changelog: add entry Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com> (cherry picked from commit c107045) Co-authored-by: Antonio <34042064+Desvelao@users.noreply.github.com>
Description
This pull request fixes a console error displayed when clicking in the multiple agent selector to manage the agents in a group
Issues Resolved
Closes #5091
Evidence
[Provide screenshots or videos to prove this PR solves the issues]
Test
Scenario 1 Clicking on the multiple selector (Available agents) of the group agents management doesn't display any error in the console of the browser dev tools
Given a group without agents
When the user goes to Manage agents
And clicking on selector of the Available agentsCurrent agents in the group panel
Then it should not appear an error in the console of the browser dev tools
Scenario 2 Clicking on the multiple selector (Current agents in the group) of the group agents management doesn't display any error in the console of the browser dev tools
Given a group without agents
When the user goes to Manage agents
And clicking on selector of the Current agents in the group panel
Then it should not appear an error in the console of the browser dev tools
Check List
yarn test:jest