-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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-24737][runtime-web] Update outdated web dependencies #17711
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 80fbcfa (Mon Nov 08 08:29:05 UTC 2021) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
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 commandsThe @flinkbot bot supports the following commands:
|
80fbcfa
to
edcadd9
Compare
@yangjunhan Can you have a look at the failing build and fix it? |
edcadd9
to
15f87a5
Compare
@MartijnVisser Conflicts have been addressed. |
Thanks @yangjunhan The CI unfortunately still fails and reports:
|
15f87a5
to
d143a92
Compare
@flinkbot run azure |
1 similar comment
@flinkbot run azure |
@Airblader Could you have a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR and bringing the dependencies more up to date, @yangjunhan. Overall this looks good to me, but I have a couple questions.
However, it seems that now when making commits unrelated to the UI, there is output that didn't use to exist:
$ git commit …
> flink-dashboard@2.0.0 lint-staged
> lint-staged
→ No staged files match any configured task.
I think this will confuse the majority of developers as most do not work on the UI. Can we do something to restore the old behavior of not producing output unless the commit contains changes to the UI?
@@ -0,0 +1,4 @@ | |||
#!/bin/sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use the more portable
#!/usr/bin/env bash
.on('zoom', ({ transform }: SafeAny) => { | ||
const { x, y, k } = transform; | ||
this.zoom = k; | ||
this.zoomEvent.emit(k); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the additional emit here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seemed to be a mistake while resolving conflicts by rebasing. Let me fix it.
this.zoom = k; | ||
this.zoomEvent.emit(k); | ||
this.containerTransform = transform; | ||
this.transformEvent.emit(transform); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the additional emit here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
@Airblader There is such output because "flink-runtime-web" is introducing husky + lint-staged for linting which essentially uses git hook through pre-commit, and the pre-commit is at the repo level. One way I can think of to restore the older behavior is triggering npm script lint-staged only when |
d143a92
to
b4e9783
Compare
@yangjunhan I apologize for the late response; I was on vacation over the holidays. The changes overall look fine to me, except for the open point around the linting output. I think the solution you proposed sounds good, at least I can't think of anything better either. |
b4e9783
to
01cc7a5
Compare
@Airblader Hope you enjoyed your holidays. Since NG-ZORRO-antd recently released its new version, I am considering bumping Runtime-Web directly to Angular v13 and NG-ZORRO-antd v13 in this PR, if that is ok with you and @MartijnVisser . |
@yangjunhan I'm not sure if it's better to make it a separate PR (since we also have https://issues.apache.org/jira/browse/FLINK-24768 open for this) or if we should do it in a separate commit. Let's see what @Airblader says on that. It would be great do have this update in place! |
I would prefer bumping this in a separate PR using the JIRA issue @MartijnVisser pointed to. I'm happy to review and merge that one as well, of course (no vacation in between this time). |
@Airblader No problems! I can do it in a separate PR. Meanwhile, I fixed the linting output problem as we discussed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I'm rebasing this and letting it run through the CI one more time before merging.
What is the purpose of the change
Update outdated web dependencies and dev-dependencies.
https://issues.apache.org/jira/browse/FLINK-24737
Brief change log
Most dependencies have been updated to the latest versions except Angular (v13) and its dependent Rxjs and TypeScript, etc. According to
npm audit
, the remaining unresolved dependency vulnerabilities are mainly caused by Angular and should be fixed while bumping it to v13.Note: Bumping the Angular framework to v13 should be in another PR once NG-Zorro-Antd releases their compatible v13.
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:
@Public(Evolving)
: noDocumentation