Bump json5 from 1.0.1 to 1.0.2 in /webapp

[dependabot[bot]]

Bumps json5 from 1.0.1 to 1.0.2.

Release notes

Sourced from json5's releases.

v1.0.2

• Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295). This has been backported to v1. (#298)

Changelog

Sourced from json5's changelog.

Unreleased [code, diff]

v2.2.3 [code, diff]

• Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299)

v2.2.2 [code, diff]

• Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

v2.2.1 [code, diff]

• Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)

v2.2.0 [code, diff]

• New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. (#236, #244)

v2.1.3 [code, diff]

• Fix: An out of memory bug when parsing numbers has been fixed. (#228, #229)

v2.1.2 [code, diff]

... (truncated)

Commits

• a62db1e 1.0.2
• e0c23fe docs: update CHANGELOG for v1.0.2
• 62a6540 fix: add proto to objects and arrays
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[jyoungyun]

Thank you for reporting. This issue should be modified in ONE project. This is known issue. I have fixed this issue in a simple way because I don't have more resources. I will improve this feature as soon as possible.

Related issue: #1553 https://github.com/Samsung/ONE/issues/10773

[dayo09]

It is expected that https://github.com/Samsung/ONE/pull/11049 resolves this problem.

[dayo09]

Tested on 2023-07-20

1. The daily-distribution of debian onecc-docker package onecc-docker_0.1.0-0~202307190231~ubuntu20.04.1_amd64.deb is installed.

• From the log during prerequisite installation:

(데이터베이스 읽는중 ...현재 333284개의 파일과 디렉터리가 설치되어 있습니다.)
Preparing to unpack .../onecc-docker_0.1.0-0~202307190231~ubuntu20.04.1_amd64.deb ...
Unpacking onecc-docker (0.1.0-0~202307190231~ubuntu20.04.1) ...
onecc-docker (0.1.0-0~202307190231~ubuntu20.04.1) 설정하는 중입니다 ...

2. Run onecc succeeds on every SECOND trial

• (1) On the first run, it takes forever (more than 2 min, doesn't finish)
• (2) On the second run, after refreshing the window it completes in 30 sec.

[onecc-docker] Build docker image ...
[onecc-docker] Docker image is built successfully.
[2023. 7. 20. 오후 1:50:16][ToolRunner][info] child process exited with code 0
[2023. 7. 20. 오후 1:50:16][ToolRunner][info] Build Success.

[2023. 7. 20. 오후 1:50:16][JobRunner][info] All jobs have been completed.

[jyoungyun]

(1) On the first run, it takes forever (more than 2 min, doesn't finish)

This is because it takes a very long time to generate new docker image. We can provide some logs so that users can recognize them.