Skip to content

⚡ Bolt: 정적 에셋 및 파일 I/O 캐싱을 통한 디렉토리 순회 최적화 - #178

Closed
seonghobae wants to merge 4 commits into
masterfrom
bolt-optimize-css-hash-13633495468796739194
Closed

⚡ Bolt: 정적 에셋 및 파일 I/O 캐싱을 통한 디렉토리 순회 최적화#178
seonghobae wants to merge 4 commits into
masterfrom
bolt-optimize-css-hash-13633495468796739194

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

💡 What:

  • process_dir 내에서 매번 생성되던 정적 CSS 텍스트와 비싼 SHA-256 연산을 파일 최상단으로 옮겼습니다.
  • process_ignore_file에서 중복 실행되던 파일시스템 디렉토리 목록 읽기 오버헤드를 dirListing 지역 변수를 캐싱하여 제거했습니다.

🎯 Why:

  • 큰 디렉토리 트리를 순회할 때, 똑같은 CSS 문자열의 해시를 매번 구하는 것은 비효율적이었습니다.
  • 파일 무시 목록 구성과 숨김 파일 필터링 시 한 디렉토리에 대해 OS 수준의 I/O 리스트업이 두 번 발생하는 병목이 있었습니다.

📊 Impact:

  • go 함수 등을 통해 깊은 폴더 트리를 처리할 때 중복 I/O가 줄고 메모리 할당 및 CPU 사용(특히 해시 암호화)이 줄어 전체적인 실행 속도가 향상됩니다.

🔬 Measurement:

  • ./gradlew test를 통해 100% 명령어 커버리지가 유지됨을 확인하였으며, 단위 테스트에서 정적 변수가 정상 접근됨을 검증했습니다.

PR created automatically by Jules for task 13633495468796739194 started by @seonghobae

- `process_dir` 루프 외부로 `cssContent`, `css`, `styleHash`를 추출하여 불필요한 문자열 생성 및 비싼 SHA-256 암호화 연산 반복 방지
- `process_ignore_file`에서 디렉토리 목록을 호출할 때 발생하는 O(N) I/O 낭비 방지를 위해 `dirListing` 변수로 캐싱
- 관련 테스트 코드 수정으로 100% 테스트 커버리지 유지
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

- `process_dir` 루프 외부로 `cssContent`, `css`, `styleHash`를 추출하여 불필요한 문자열 생성 및 비싼 SHA-256 암호화 연산 반복 방지
- `process_ignore_file`에서 디렉토리 목록을 호출할 때 발생하는 O(N) I/O 낭비 방지를 위해 `dirListing` 변수로 캐싱
- 관련 테스트 코드 수정으로 100% 테스트 커버리지 유지
- `process_dir` 루프 외부로 `cssContent`, `css`, `styleHash`를 추출하여 불필요한 문자열 생성 및 비싼 SHA-256 암호화 연산 반복 방지
- `process_ignore_file`에서 디렉토리 목록을 호출할 때 발생하는 O(N) I/O 낭비 방지를 위해 `dirListing` 변수로 캐싱
- 관련 테스트 코드 수정으로 100% 테스트 커버리지 유지
- `process_dir` 루프 외부로 `cssContent`, `css`, `styleHash`를 추출하여 불필요한 문자열 생성 및 비싼 SHA-256 암호화 연산 반복 방지
- `process_ignore_file`에서 디렉토리 목록을 호출할 때 발생하는 O(N) I/O 낭비 방지를 위해 `dirListing` 변수로 캐싱
- 관련 테스트 코드 수정으로 100% 테스트 커버리지 유지

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 2545783cd3e764e3edcd4654235258bc024cf7be.

  • Head SHA: 2545783cd3e764e3edcd4654235258bc024cf7be

  • Workflow run: 30424170163

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (3 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (3 files)"]
  R1 --> V1["required checks"]
Loading

@opencode-agent

Copy link
Copy Markdown

OpenCode Review Overview

  • Head SHA: 2545783cd3e764e3edcd4654235258bc024cf7be
  • Workflow run: 30424170163
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 2545783cd3e764e3edcd4654235258bc024cf7be.

  • Head SHA: 2545783cd3e764e3edcd4654235258bc024cf7be

  • Workflow run: 30424170163

  • Workflow attempt: 1

Coverage evidence

Coverage evidence job did not run or did not publish coverage evidence.

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (3 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (3 files)"]
  R1 --> V1["required checks"]
Loading

Copy link
Copy Markdown
Collaborator Author

Closing as superseded by two bounded canonical paths. #363 owns the stylesheet/hash hoist together with exact CSP byte identity, real generated-output verification, APA 7 doctoring, changelog, and fresh exact-head quality/security evidence. #170 separately owns the directory-listing reuse and blank-matcher optimization on a current base. Combining those independent surfaces makes this stale head unsuitable as evidence for either. No review or check is reused.

@seonghobae seonghobae closed this Aug 5, 2026
@google-labs-jules

Copy link
Copy Markdown

Closing as superseded by two bounded canonical paths. #363 owns the stylesheet/hash hoist together with exact CSP byte identity, real generated-output verification, APA 7 doctoring, changelog, and fresh exact-head quality/security evidence. #170 separately owns the directory-listing reuse and blank-matcher optimization on a current base. Combining those independent surfaces makes this stale head unsuitable as evidence for either. No review or check is reused.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant