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

[BUG] Change time format to UTC in notification message preview (#1183) #1184

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

vikhy-aws
Copy link
Contributor

Description

Backport 47800b7 to 2.x.

Link to original PR - #1183

Changes notification preview message to have time in UTC format. Fix an improper import

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.

…search-project#1183)

* fix: change notification preview message to have time in UTC format. fix an improper import

Signed-off-by: vikhy-aws <[email protected]>

* fix: add unit tests. change timezone to UTC

Signed-off-by: vikhy-aws <[email protected]>

* fix: remove log statements

Signed-off-by: vikhy-aws <[email protected]>

* fix: update timeout for loadSampleEcommerceData to 60secs to handle failing cypress test

Signed-off-by: vikhy-aws <[email protected]>

* fix: update timeout for monitor creation to 60secs to handle failing cypress test

Signed-off-by: vikhy-aws <[email protected]>

* fix: update timeout for monitor creation to 60secs to handle failing cypress test

Signed-off-by: vikhy-aws <[email protected]>

* fix: revert timeout increases. Handle monitors page load properly.

Signed-off-by: vikhy-aws <[email protected]>

* fix: revert changes to timeouts

Signed-off-by: vikhy-aws <[email protected]>

* fix: increase timeouts to ensure proper loading of pages

Signed-off-by: vikhy-aws <[email protected]>

---------

Signed-off-by: vikhy-aws <[email protected]>
@AWSHurneyt AWSHurneyt merged commit 960923c into opensearch-project:2.x Jan 8, 2025
27 of 46 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.0 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/alerting-dashboards-plugin/backport-2.0 2.0
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.0
# Create a new branch
git switch --create backport-1184-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.0

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.1 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/alerting-dashboards-plugin/backport-2.1 2.1
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.1
# Create a new branch
git switch --create backport-1184-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.1
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.1

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.2 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/alerting-dashboards-plugin/backport-2.2 2.2
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.2
# Create a new branch
git switch --create backport-1184-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.2
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.2

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.3 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/alerting-dashboards-plugin/backport-2.3 2.3
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.3
# Create a new branch
git switch --create backport-1184-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.3

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.4 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/alerting-dashboards-plugin/backport-2.4 2.4
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.4
# Create a new branch
git switch --create backport-1184-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.4
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.4

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.5 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/alerting-dashboards-plugin/backport-2.5 2.5
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.5
# Create a new branch
git switch --create backport-1184-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.5
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.5

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.6 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/alerting-dashboards-plugin/backport-2.6 2.6
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.6
# Create a new branch
git switch --create backport-1184-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.6
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.6

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.7 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/alerting-dashboards-plugin/backport-2.7 2.7
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.7
# Create a new branch
git switch --create backport-1184-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.7
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.7

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.8 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/alerting-dashboards-plugin/backport-2.8 2.8
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.8
# Create a new branch
git switch --create backport-1184-to-2.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.8
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.8

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.9 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/alerting-dashboards-plugin/backport-2.9 2.9
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.9
# Create a new branch
git switch --create backport-1184-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.9

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.10 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/alerting-dashboards-plugin/backport-2.10 2.10
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.10
# Create a new branch
git switch --create backport-1184-to-2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.10
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.10

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

@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/alerting-dashboards-plugin/backport-2.11 2.11
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.11
# Create a new branch
git switch --create backport-1184-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.11
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.11

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.12 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/alerting-dashboards-plugin/backport-2.12 2.12
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.12
# Create a new branch
git switch --create backport-1184-to-2.12
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.12
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.12

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.13 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/alerting-dashboards-plugin/backport-2.13 2.13
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.13
# Create a new branch
git switch --create backport-1184-to-2.13
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.13
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.13

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.14 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/alerting-dashboards-plugin/backport-2.14 2.14
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.14
# Create a new branch
git switch --create backport-1184-to-2.14
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.14
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.14

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.15 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/alerting-dashboards-plugin/backport-2.15 2.15
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.15
# Create a new branch
git switch --create backport-1184-to-2.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.15
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.15

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.16 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/alerting-dashboards-plugin/backport-2.16 2.16
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.16
# Create a new branch
git switch --create backport-1184-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.16
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.16

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.17 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/alerting-dashboards-plugin/backport-2.17 2.17
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.17
# Create a new branch
git switch --create backport-1184-to-2.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.17
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.17

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.18 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/alerting-dashboards-plugin/backport-2.18 2.18
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.18
# Create a new branch
git switch --create backport-1184-to-2.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 960923ca582e5411cfad276cabd7e6a4d8b5f978
# Push it to GitHub
git push --set-upstream origin backport-1184-to-2.18
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.18

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

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