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

Upgrade traverse to address CVE-2023-45133, resolve debug for CVE-2017-16137 #221

Merged
merged 2 commits into from
Oct 18, 2023

Conversation

derek-ho
Copy link
Collaborator

@derek-ho derek-ho commented Oct 18, 2023

Description

Upgrade traverse to address CVE-2023-45133, resolve debug for CVE-2017-16137

Issues Resolved

[List any issues this PR will resolve]

Check List

  • New functionality includes testing.
    • All tests pass, including unit test, integration test and doctest
  • New functionality has been documented.
    • New functionality has javadoc added
    • New functionality has user manual doc added
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@derek-ho derek-ho changed the title Traverse Upgrade traverse to address CVE-2023-45133, resolve debug for CVE-2017-16137 Oct 18, 2023
@derek-ho derek-ho merged commit 9a37d7a into opensearch-project:main Oct 18, 2023
9 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-reporting/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/dashboards-reporting/backport-2.x
# Create a new branch
git switch --create backport/backport-221-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9a37d7a22c7d919a04f7b67b4ebe04d7469c459b
# Push it to GitHub
git push --set-upstream origin backport/backport-221-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-reporting/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-221-to-2.x.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.11 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/dashboards-reporting/backport-2.11 2.11
# Navigate to the new working tree
pushd ../.worktrees/dashboards-reporting/backport-2.11
# Create a new branch
git switch --create backport/backport-221-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9a37d7a22c7d919a04f7b67b4ebe04d7469c459b
# Push it to GitHub
git push --set-upstream origin backport/backport-221-to-2.11
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/dashboards-reporting/backport-2.11

Then, create a pull request where the base branch is 2.11 and the compare/head branch is backport/backport-221-to-2.11.

@joshuali925
Copy link
Member

removing backport failed labels, ported by #222 and #223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants