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

dashboard: add pages to display specific errors for upperbound and convergence errors for a given version of g-c-b #850

Open
stephaniewang526 opened this issue Aug 21, 2020 · 2 comments
Assignees
Labels
priority: p4 type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@stephaniewang526
Copy link
Contributor

stephaniewang526 commented Aug 21, 2020

The current dashboard only shows cards to display number of errors but does not show any further details on what dependencies/artifacts are causing them. It would be helpful for developers to be able to see the artifacts causing problems.

@stephaniewang526 stephaniewang526 self-assigned this Aug 21, 2020
@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Aug 22, 2020
@danoscarmike danoscarmike added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed triage me I really want to be triaged. labels Aug 25, 2020
@stephaniewang526
Copy link
Contributor Author

As we caught up, we don't currently have a way to look into why there are still convergence errors reported even when we are using the same version of google-cloud-shared-dependencies so it would be good to find out why:
image

@Neenu1995
Copy link
Contributor

Status update: The convergence errors are coming from google-cloud-nio and google-cloud-resourcemanager. Both depends on it's own version of apiary clients which transitively depends on an older version of google-api-client, causing convergence failure. Looking into a solution now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p4 type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

6 participants