[feat|fix] : SDE frontend : Hotfix 3.2 with pcf - rel:2.3.0

[sachinargade123]

Description

Fixed

• Code optimisation for download file from server, Generic error handling, UI improvement .
• trivy workflow updated.
• version bump for chart release.
• PCF documentation update

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[ajithsimons]

@almadigabor Could you please help us create dependency review tickets for the below libraries?
npm/npmjs/@babel/code-frame/7.23.4
npm/npmjs/@babel/helper-string-parser/7.23.4
npm/npmjs/@babel/highlight/7.23.4

Thanks!

[carslen]

Done:

[main] INFO Querying Eclipse Foundation for license data for 500 items.
[main] INFO Found 145 items.
[main] INFO Querying Eclipse Foundation for license data for 500 items.
[main] INFO Found 94 items.
[main] INFO Querying Eclipse Foundation for license data for 290 items.
[main] INFO Found 51 items.
[main] INFO Querying ClearlyDefined for license data for 500 items.
[main] INFO Found 500 items.
[main] INFO Querying ClearlyDefined for license data for 500 items.
[main] INFO Found 500 items.
[main] INFO License information could not be automatically verified for the following content:
[main] INFO
[main] INFO npm/npmjs/@babel/code-frame/7.23.4
[main] INFO npm/npmjs/@babel/helper-string-parser/7.23.4
[main] INFO npm/npmjs/@babel/highlight/7.23.4
[main] INFO
[main] INFO This content is either not correctly mapped by the system, or requires review.
[main] INFO A review is required for npm/npmjs/@babel/highlight/7.23.4.
[main] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11658 .
[main] INFO A review is required for npm/npmjs/@babel/code-frame/7.23.4.
[main] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11659 .
[main] INFO A review is required for npm/npmjs/@babel/helper-string-parser/7.23.4.
[main] INFO A review request was created https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11660 .

Tickets created:

• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11658
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11659
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11660

[ajithsimons]

@carslen thanks for the quick support! Dependencies file has been updated. Please verify!

[MehranRoshandel]

@carslen, can you please help us to merge this PR by today?

[adityagajbhiye9]

Updated.
#41 Legal documents updated for docker image.

[adityagajbhiye9]

fixed
#41 Updated Docker file for legal information.

[hzierer]

@carslen Dockerfile LGTM now

[FaGru3n]

Hi all,

in my opinion this is really hard to verfiy and IMHO i would reject this PR.

This looks for me to one PR to fix all problems... 👎🏼 not a good practice in my perspective.

Reason:

• Hard to review
• No transparency on what change fixed which issue without dedicated commit messages, etc.
• Hard/impossible to create a proper changelog

The Best practices we nomally use 1 problem like docs / 1 pr / dedicated commit messages why to change and what to improve.

if i read the description correctly that would be at least 6 PR´s like:

1. Code optimisation for download file from server
2. Generic error handling
3. UI improvement
4. trivy workflow updated
5. version bump for chart release
6. PCF documentation update

Only guessing is it possible for you @sachinargade123 to split all your changes in separate PR´s or generating new ones? This is also the reason why we as a system team generate multible issues for each TRG section.

[FaGru3n]

This PR is too big as followed our guidelines.
https://www.eclipse.org/projects/handbook/#ip-project-content

[sachinargade123]

We are closing this PR. We will create new PR's.