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

improvement: use tableV2 in the alert page #3669

Merged
merged 1 commit into from
Feb 7, 2022

Conversation

gaudiauj
Copy link
Contributor

Component:

AlertPage

Context:

fix bad formating of alerts by using new table

@gaudiauj gaudiauj requested a review from a team as a code owner January 19, 2022 12:31
@gaudiauj gaudiauj self-assigned this Jan 19, 2022
@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2022

Hello gaudiauj,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2022

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge bugfix/alertpage into
    development/2.11
  • w/123.0/bugfix/alertpage will be merged into development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@bert-e
Copy link
Contributor

bert-e commented Jan 19, 2022

History mismatch

Merge commit #a41bb40034d4681aa9aa7f8b0a9e32abda037077 on the integration branch
w/123.0/bugfix/alertpage is merging a branch which is neither the current
branch bugfix/alertpage nor the development branch
development/123.0.

It is likely due to a rebase of the branch bugfix/alertpage and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@gaudiauj
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2022

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2022

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge bugfix/alertpage into
    development/2.11
  • w/123.0/bugfix/alertpage will be merged into development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

const leafAlerts = useMemo(
() => alerts?.alerts.filter((alert) => !alert.labels.children) || [],
// eslint-disable-next-line react-hooks/exhaustive-deps
[JSON.stringify(alerts?.alerts)],
[alerts?.alerts],
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should keep the previous code.

React uses “referential equality” for object and array within the dependencies array.
so even we have the same content of alerts, it will still re-run the effect. That's why we stringify.

A pretty good article to read about.
https://www.benmvp.com/blog/object-array-dependencies-react-useEffect-hook/

@bert-e
Copy link
Contributor

bert-e commented Jan 21, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

@bert-e
Copy link
Contributor

bert-e commented Jan 24, 2022

History mismatch

Merge commit #1f238dd02845ae341eac4efaeded1e958ab18456 on the integration branch
w/123.0/bugfix/alertpage is merging a branch which is neither the current
branch bugfix/alertpage nor the development branch
development/123.0.

It is likely due to a rebase of the branch bugfix/alertpage and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@gaudiauj
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge bugfix/alertpage into
    development/2.11
  • w/123.0/bugfix/alertpage will be merged into development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

History mismatch

Merge commit #da45c767229ae18f42868fde130c220d9b23beb5 on the integration branch
w/123.0/bugfix/alertpage is merging a branch which is neither the current
branch bugfix/alertpage nor the development branch
development/123.0.

It is likely due to a rebase of the branch bugfix/alertpage and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@gaudiauj
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge bugfix/alertpage into
    development/2.11
  • w/123.0/bugfix/alertpage will be merged into development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 25, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

ChengYanJin
ChengYanJin previously approved these changes Jan 26, 2022
const leafAlerts = useMemo(
() => alerts?.alerts.filter((alert) => !alert.labels.children) || [],
// eslint-disable-next-line react-hooks/exhaustive-deps
Copy link
Contributor

Choose a reason for hiding this comment

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

You will need to keep this line, otherwise Eslint will complain about about the missing dependency :(

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh my bad will fix this :)

@bert-e
Copy link
Contributor

bert-e commented Jan 26, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@ChengYanJin
Copy link
Contributor

/status

@bert-e
Copy link
Contributor

bert-e commented Jan 27, 2022

Status

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jan 27, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@gaudiauj
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jan 28, 2022

Build failed

The build for commit did not succeed in branch w/123.0/bugfix/alertpage.

The following options are set: approve

@ChengYanJin
Copy link
Contributor

/status

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

Status

Status report is not available.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

Build failed

The build for commit did not succeed in branch w/123.0/bugfix/alertpage.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

History mismatch

Merge commit #fe730ebb380b349462ee182e6580fee21a0d8a55 on the integration branch
w/123.0/bugfix/alertpage is merging a branch which is neither the current
branch bugfix/alertpage nor the development branch
development/123.0.

It is likely due to a rebase of the branch bugfix/alertpage and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve

@ChengYanJin
Copy link
Contributor

/reset

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

Integration data created

I have created the integration data for the additional destination branches.

  • this pull request will merge bugfix/alertpage into
    development/2.11
  • w/123.0/bugfix/alertpage will be merged into development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 5, 2022

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 7, 2022

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.11

  • ✔️ development/123.0

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Feb 7, 2022

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.11

  • ✔️ development/123.0

The following branches have NOT changed:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue None.

Goodbye gaudiauj.

@bert-e bert-e merged commit 27ea007 into development/2.11 Feb 7, 2022
@bert-e bert-e deleted the bugfix/alertpage branch February 7, 2022 12:32
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.

3 participants