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 Revamp #91

Merged
merged 9 commits into from
Jun 18, 2024
Merged

Dashboard Revamp #91

merged 9 commits into from
Jun 18, 2024

Conversation

MVarshini
Copy link
Collaborator

Type of change

  • Refactor
  • New feature
  • Bug fix
  • Optimization
  • Documentation Update

Description

This PR revamps the current Dashboard

  • Updated the Layout
  • Added Table component with Sorting, Pagination
  • Integrated with CPT_JOBS API
  • Updated the Doc file Readme.md

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please describe the System Under Test.
  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@MVarshini MVarshini requested a review from chentex April 10, 2024 09:49
@MVarshini MVarshini self-assigned this Apr 10, 2024
@vishnuchalla
Copy link
Collaborator

vishnuchalla commented Apr 11, 2024

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@MVarshini
Copy link
Collaborator Author

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

@vishnuchalla
Copy link
Collaborator

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

I still come across this error when I run sh local-compose.sh

[1/4] Resolving packages...
[2/4] Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^18.0.0 || >=20.0.0". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: building at STEP "RUN yarn install": while running runtime: exit status 1
87f2197c97e62613568d0ee74158e85d4318c95da5152a2275b5244e79e1b474
Trying to pull localhost/frontend:latest...
WARN[0000] Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
WARN[0001] Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
WARN[0002] Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

@MVarshini MVarshini mentioned this pull request Apr 26, 2024
7 tasks
@vishnuchalla
Copy link
Collaborator

@MVarshini Can you please update the local-compose.sh file so that we can verify these changes? Looks like the existing one is not compatible.

@vishnuchalla Updated the file.

I still come across this error when I run sh local-compose.sh

[1/4] Resolving packages...
[2/4] Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^18.0.0 || >=20.0.0". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: building at STEP "RUN yarn install": while running runtime: exit status 1
87f2197c97e62613568d0ee74158e85d4318c95da5152a2275b5244e79e1b474
Trying to pull localhost/frontend:latest...
WARN[0000] Failed, retrying in 1s ... (1/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
WARN[0001] Failed, retrying in 1s ... (2/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
WARN[0002] Failed, retrying in 1s ... (3/3). Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
Error: initializing source docker://localhost/frontend:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

Checked again. Works fine.

@vishnuchalla vishnuchalla self-requested a review April 29, 2024 17:57
Copy link

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale label May 29, 2024
Copy link

github-actions bot commented Jun 3, 2024

This PR was closed because it has been stalled for 6 days with no activity.

@github-actions github-actions bot closed this Jun 3, 2024
@vishnuchalla vishnuchalla reopened this Jun 3, 2024
@github-actions github-actions bot removed the Stale label Jun 4, 2024
@jtaleric
Copy link
Member

What is our status on this integration?

@vishnuchalla
Copy link
Collaborator

@chentex and I had to chat to get these in after the telco changes. @MVarshini would you mind updating this PR please?

Copy link
Member

@jtaleric jtaleric left a comment

Choose a reason for hiding this comment

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

@MVarshini I am unable to test this change, local-compose seems to run, however the frontend pod doesn't seem to be serving out anything?


> [email protected] dev
> vite


  VITE v5.2.7  ready in 156 ms

  ➜  Local:   http://localhost:3000/
  ➜  Network: use --host to expose

Is the containerfile for the frontend up to date?

@chentex chentex changed the base branch from main to revamp June 13, 2024 12:32
@MVarshini
Copy link
Collaborator Author

@MVarshini I am unable to test this change, local-compose seems to run, however the frontend pod doesn't seem to be serving out anything?


> [email protected] dev
> vite


  VITE v5.2.7  ready in 156 ms

  ➜  Local:   http://localhost:3000/
  ➜  Network: use --host to expose

Is the containerfile for the frontend up to date?

@jtaleric The container file is up to date. Try to hit http://localhost:3000/ on the browser if it doesn't work let's it offline and check.

@jtaleric
Copy link
Member

@MVarshini Thanks for the fix to the local-compose -- in the past we never needed hostNetwork.

There are still aspects of the new dashboard that seem broken for me.
image
When I select OCP, the list of tests are not updating to just OCP workloads.

image
When I click the menu button, I see a "hello" message.

I don't want to rush things, but is this PR ready?

@MVarshini
Copy link
Collaborator Author

@MVarshini Thanks for the fix to the local-compose -- in the past we never needed hostNetwork.

There are still aspects of the new dashboard that seem broken for me. image When I select OCP, the list of tests are not updating to just OCP workloads.

image When I click the menu button, I see a "hello" message.

I don't want to rush things, but is this PR ready?

It has only the Home Page Table and OCP page hasn't been included here.

Also, Side menu toggle is a bug and it has been fixed in this PR #102 which has both Home and OCP pages with Filter and Summary Tab

const dispatch = useDispatch();
const onSidebarToggle = () => {
dispatch(toggleSideMenu(false));
dispatch(showToast("success", "Hello"));
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: Please remove this message.

Copy link
Collaborator Author

@MVarshini MVarshini Jun 18, 2024

Choose a reason for hiding this comment

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

Addressed in PR #102

Copy link
Collaborator

@vishnuchalla vishnuchalla left a comment

Choose a reason for hiding this comment

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

Considering as this revamp has to go in multiple PRs, I am okay with merging this PR into separate branch as an initial step and having rest of the parts integrated in the upcoming ones. For example this PR only has home page and the layout set but doesn't actually filter out stuff and show product specific data (.i.e OCP, Quay etc) which is fine. Hopefully all these items will get addressed in #102.
cc: @chentex

Copy link
Member

@chentex chentex left a comment

Choose a reason for hiding this comment

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

Thank you @MVarshini, merging this one to the revamp branch and test the #102

@chentex chentex merged commit 5ea688b into cloud-bulldozer:revamp Jun 18, 2024
1 check passed
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.

4 participants