ES /docs

PanoPostprocessorService::run | end - {"stack":"Error: Blur script exited with code 1:

Service
cupixworks-pano-postprocessor-instance
Occurrences
5
Status
Reported
Confidence
80%
Actionability
44%
Cluster ID
76eafe31-2f79-4f96-8e23-3c6bdf3bb8a8
First Seen
2026-07-31 18:04 UTC
Last Seen
2026-08-03 17:58 UTC
Actions

PanoPostprocessorService::run | end - {"stack":"Error: Blur script exited with code 1:

What Happened#

2026-08-01 03:04 KST 에 cupixworks-pano-postprocessor-instance (production, us-west-2) 에서 pano 마스킹 파이프라인이 blur script 종료 코드 1 로 실패했다. 원인은 bundled Python 스크립트 /tmp/lib/face-body-detector/cupix_inference.py 에서 cv2.imread 호출 시 OpenCV 의 pixel 상한 (CV_IO_MAX_IMAGE_PIXELS, 기본 2^30 ≈ 1.073B pixels) 을 초과하는 pano 이미지가 있었기 때문이다. MaskWork::maskPanos 는 배치 스크립트 하나로 전체 pano 를 처리하므로 단 하나의 대용량 이미지가 스크립트를 중단시키고, 상위 PanoPostprocessorService::run 의 catch 블록이 capture 전체를 Error 상태로 전이시킨다.

Quick Facts#

Field Value
exception.class cv2.error (OpenCV assertion) — Node 측에서는 Error: Blur script exited with code 1
exception.message OpenCV(4.10.0) /io/opencv/modules/imgcodecs/src/loadsave.cpp:79: error: (-215:Assertion failed) pixels <= CV_IO_MAX_IMAGE_PIXELS in function 'validateInputImageSize'
top_frame /tmp/lib/face-body-detector/cupix_inference.py:333 in detect (img_original = cv2.imread(image_filepath))
runtime Python 3.11, opencv-python 4.10.0.84 (Dockerfile pin)
env production, us-west-2, tenant cupix

Affected Teams#

Team / Domain Error Count Impact
cadscans (pano postprocessor) 2 (동일 capture 내 중복 emit) 해당 capture 의 pano_postprocessor_state 가 Error 로 전이되어 마스킹/blurriness/resize 단계 전체가 미완료 상태로 남는다 (pano-postprocessor-service.ts:190)

Timeline#

  1. 2026-08-01 03:04:50 KSTPanoPostprocessorService::run | end - {"stack":"Error: Blur script exited with code 1: ...cv2.error ..."} 두 번 기록됨 (동일 순간, 두 로그 라인 emit) — cluster first_seen == last_seen
  2. 2026-08-01 03:04:50 KSTrun() catch 블록이 updatePanoPostprocessorState(captureId, Error)updateJobState(Stopped) 실행 (pano-postprocessor-service.ts:188-197)

Scoring#

Confidence 80% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 23 code refs, 5 log queries
Code path explicitness 3/3 23 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 27 file(s)
Single repo 1/3 5 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 3/3 no migration