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

[FLINK-23111][runtime-web] Bump angular's and ng-zorro's version to 12 #16603

Closed
wants to merge 7 commits into from

Conversation

yangjunhan
Copy link
Contributor

@yangjunhan yangjunhan commented Jul 27, 2021

What is the purpose of the change

Step-by-step modernize flink-runtime-web, i.e. Flink UI.

Brief change log

Bump to the latest version of Angular and NG-Zorro.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): yes
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit afabfeb (Tue Jul 27 08:23:31 UTC 2021)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!
  • This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

Mention the bot in a comment to re-run the automated checks.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@yangjunhan yangjunhan changed the title [FLINK-23110][runtime-web] Bump angular's and ng-zorro's version to 8 [FLINK-23111][runtime-web] Bump angular's and ng-zorro's version to 8 Jul 27, 2021
Copy link
Contributor

@Airblader Airblader left a comment

Choose a reason for hiding this comment

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

Changes look good to me, thanks!

@flinkbot
Copy link
Collaborator

flinkbot commented Jul 27, 2021

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run travis re-run the last Travis build
  • @flinkbot run azure re-run the last Azure build

@Airblader
Copy link
Contributor

BTW, I'm also totally fine with doing the upgrades all the way to Angular 12 on the same PR. Just separating by commit to make it easier to review would be appreciated, but we don't need to wait on merges every single time that way.

@yangjunhan
Copy link
Contributor Author

BTW, I'm also totally fine with doing the upgrades all the way to Angular 12 on the same PR. Just separating by commit to make it easier to review would be appreciated, but we don't need to wait on merges every single time that way.

Sure, I will continue to push commits to this PR.

@yangjunhan
Copy link
Contributor Author

@Airblader I believe this PR is ready for reviews now. BTW, since there is little modifications while bumping from v11 to v12, I have merged those two updates in one commit.

@yangjunhan yangjunhan changed the title [FLINK-23111][runtime-web] Bump angular's and ng-zorro's version to 8 [FLINK-23111][runtime-web] Bump angular's and ng-zorro's version to 12 Jul 30, 2021
Copy link
Contributor

@Airblader Airblader left a comment

Choose a reason for hiding this comment

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

Thanks for working on this! Overall it looks great. I left a couple minor comments. There is one main thing we need to do still, however; we need to update the pom.xml to use a compatible node version (12.14.x/14.15.x or later minor version) during a Maven build.

"zone.js": "~0.8.26"
"monaco-editor": "^0.20.0",
"ng-zorro-antd": "^12.0.1",
"rxjs": "^6.5.3",
Copy link
Contributor

Choose a reason for hiding this comment

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

"@angular/forms": "~12.1.3",
"@angular/platform-browser": "~12.1.3",
"@angular/platform-browser-dynamic": "~12.1.3",
"@angular/router": "~12.1.3",
"@antv/g2": "^3.4.10",
"core-js": "^2.5.4",
"d3": "^5.9.1",
"d3-flame-graph": "^4.0.6",
"d3-tip": "^0.9.1",
"dagre": "^0.8.4",
Copy link
Contributor

Choose a reason for hiding this comment

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

We should add dagre to allowedCommonJsDependencies in angular.json to avoid a warning.

Copy link
Contributor

@Airblader Airblader left a comment

Choose a reason for hiding this comment

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

Thanks! Let's wait for the CI, but LGTM now.

@yangjunhan
Copy link
Contributor Author

@Airblader I believe the CI has finished. Once this PR is merged, I can start working on the eslint migration.

@Airblader
Copy link
Contributor

Sounds great. Do you have someone who can merge this PR for you? Otherwise I can find someone who can take care of it.

@yangjunhan
Copy link
Contributor Author

Sounds great. Do you have someone who can merge this PR for you? Otherwise I can find someone who can take care of it.

Please do so. I have no one to do it for me currently.

@Airblader
Copy link
Contributor

That's fine. We'll take care of it.

Copy link
Contributor

@twalthr twalthr left a comment

Choose a reason for hiding this comment

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

Thanks for improving the web UI @yangjunhan. I can help merging this but have to rely on @Airblader judgement for a review. One thing that we should check though is whether we need to update NOTICE files. I see flink-runtime-web/src/main/resources/META-INF/NOTICE maybe also in flink-dist?

@yangjunhan
Copy link
Contributor Author

Hi, @Airblader @twalthr. How is the reviewing going? Could you kindly confirm whether I need to update the NOTICE file as well?

@Airblader
Copy link
Contributor

@yangjunhan Yes, the NOTICE file @twalthr mentioned needs to be updated as well.

@yangjunhan
Copy link
Contributor Author

@yangjunhan Yes, the NOTICE file @twalthr mentioned needs to be updated as well.

Okay, I will handle it @Airblader . However, I am not very sure the tool and exact steps to auto-update the NOTICE file, and I do not think that I should manually update the file 😂.

BTW, would it be possible to invite me to the Veverica Slack workspace so that we can communicate there in a more convenient way? I am currently a team member of VVP Front-end in Hangzhou, China.

@Airblader
Copy link
Contributor

I actually think the NOTICE files are maintained manually (unfortunately). There is a license checker to verify some basic things, but I am not sure it even runs for the npm dependencies.

I'll try to ask someone about Slack and will get back to you.

@Airblader
Copy link
Contributor

@yangjunhan Can you give us your email address with which to invite you to Slack?

@yangjunhan
Copy link
Contributor Author

@yangjunhan Can you give us your email address with which to invite you to Slack?

My email address: yangjunhan1234@gmail.com. Thanks.

@Airblader
Copy link
Contributor

supersedes #14960

Copy link
Contributor

@twalthr twalthr left a comment

Choose a reason for hiding this comment

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

LGTM

twalthr pushed a commit to twalthr/flink that referenced this pull request Aug 16, 2021
@twalthr twalthr closed this in 6451a1f Aug 16, 2021
hhkkxxx133 pushed a commit to hhkkxxx133/flink that referenced this pull request Aug 25, 2021
@yangjunhan yangjunhan deleted the build/runtime-web-bump-8 branch November 1, 2021 09:43
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.

5 participants