facebook/infer

Capture only the files needed for the analysis (reactive capture)

Open

#656 opened on May 25, 2017

View on GitHub
 (5 comments) (0 reactions) (0 assignees)HTML (1,688 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (12,410 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Separate analyze and capture phase,i wonder to know how to reduce the capture phase time at iOS project ,i just want to analyze the changed files,but in capture phase Infer must run the translation file action,it translate the whole project files,can i just translate the changed files that i want to analyze?

below is what my command step 1.

infer capture -- xcodebuild -workspace demo.xcworkspace -scheme Debug -sdk iphonesimulator10.1 -configuration Debug build

step 2.

infer --fail-on-issue -a infer --changed-files-index ./index.txt -- analyze

In step 1 waste about 25 mins translate about 1900 files. Assuming that I just modified a file, but wasted 25 minutes during the capture phase, this situation was obviously unreasonable.

Contributor guide

Research direction
Investigate the Infer codebase to understand how the capture phase works for iOS projects. Look at the source files related to capture, possibly in the `infer/src` directory. The issue requests a reactive capture that only processes changed files. Explore the possibility of integrating with tools like `fsmonitor` or using file modification timestamps to skip unchanged files. Also consider the existing ` changed files index` option and how it could be extended to the capture phase.
Tech stack
iosobjective c
Domain
mobiletooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Familiarity with Infer architectureiOS build process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15