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.

Sign up for GitHub

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

Jump to bottom

Remove database related stuff from the che-server component #22107

Closed
vinokurig opened this issue Mar 29, 2023 · 3 comments
Closed

Remove database related stuff from the che-server component #22107

vinokurig opened this issue Mar 29, 2023 · 3 comments
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@vinokurig
Copy link
Contributor

vinokurig commented Mar 29, 2023 •
edited
Loading

Is your task related to a problem? Please describe

Che-server has com.h2database:h2 dependency, wich according to the trivy report, brings a HIGH vulnerability.
Upstream issue: h2database/h2database#3686

Describe the solution you'd like

Get rid of the com.h2database:h2 dependency, by removing the database stuff, since we don't use the database related stuff from che-server.

Describe alternatives you've considered

No response

Additional context

No response
@vinokurig vinokurig added kind/task Internal things, technical debt, and to-do tasks to be performed. area/che-server labels Mar 29, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 29, 2023
@vinokurig vinokurig mentioned this issue Mar 29, 2023
Merged
9 tasks
@amisevsk amisevsk added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 31, 2023
@che-bot
Copy link
Contributor

che-bot commented Sep 27, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2023
@vinokurig
Copy link
Contributor Author

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2023
@vinokurig
Copy link
Contributor Author

is fixed by eclipse-che/che-server#630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vinokurig @amisevsk @che-bot