Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[BUG][code-analyzer] Flow engine isn't producing results file

未关闭
#1,958 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python, typescript
领域
devtools, tooling

调研方向

从 FlowScannerCommandWrapper.js 中的 runFlowScannerRules 以及 stack trace 中提到的入口点 FlowScannerEngine.runRules 开始。使用提供的 sf code-analyzer 命令在 Windows 上复现该问题,并追踪 flowScannerResultsFile.json 缺失的原因。当 Flow 引擎在没有 ENOENT 错误的情况下生成预期报告时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

Have you tried to resolve this issue yourself first?
  • I confirm I have gone through the above steps and still have an issue to report.
Bug Description

flow:UnexpectedEngineError null:undefined:undefined no such file or directory,open 'C:\Users\DANIEL~1.GAL\AppData\Local\Temp\code-analyzer-Tea130\run-2025_12_19_13_39_40_449\flow\flowScannerResultsFile.json'

Output / Logs
1   1 (Critical)   flow:UnexpectedEngineError   null:undefined:undefined   The engine with name 'flow' threw an unexpected error: Error: ENOENT: no such file or directory, open 'C:\Users\DANIEL~1.GAL\AppData\Local\Temp\code-analyzer-Tea130\run-2025_12_19_13_39_40_449\flow\flowScannerResultsFile.json'
                                                                             at async open (node:internal/fs/promises:642:25)
                                                                             at async Object.readFile (node:internal/fs/promises:1279:14)
                                                                             at async RunTimeFlowScannerCommandWrapper.runFlowScannerRules (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-flow-engine\dist\python\FlowScannerCommandWrapper.js:52:36)
                                                                             at async FlowScannerEngine.runRules (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-flow-engine\dist\engine.js:104:34)
                                                                             at async CodeAnalyzer.runEngineAndValidateResults (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:389:35)
                                                                             at async C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:276:29
                                                                             at async Promise.all (index 0)
                                                                             at async CodeAnalyzer.run (C:\Users\daniel.gallo\AppData\Local\sf\node_modules\@salesforce\plugin-code-analyzer\node_modules\@salesforce\code-analyzer-core\dist\code-analyzer.js:283:38)
                                                                             at async RunAction.execute (file:///C:/Users/daniel.gallo/AppData/Local/sf/node_modules/@salesforce/plugin-code-analyzer/lib/lib/actions/RunAction.js:39:25)
                                                                             at async RunCommand.run (file:///C:/Users/daniel.gallo/AppData/Local/sf/node_modules/@salesforce/plugin-code-analyzer/lib/commands/code-analyzer/run.js:86:9)



=== Summary

Found 1 violation(s) across 0 file(s):
    1 Critical severity violation(s) found
Steps To Reproduce

sf code-analyzer run --rule-selector flow --target C:\xxxxx\unpackaged\main\default\flows\Test_Security_Flow.flow-meta.xml --output-file C:\xxxx\Test_Security_Flow.flow-meta.xml.pmd.html --view table

Expected Behavior

THE CORRECT REPORT WITHOUT DE ISSUE FROM PLUGIN ENGIE FLOW

Operating System

windows 11

Salesforce CLI Version

@salesforce/cli/2.116.6 win32-x64 node-v24.11.1

Code Analyzer Plugin (code-analyzer) Version

flow 1.0.5

Node Version

24.11.1 (Currently using 64-bit executable)

Java Version

openjdk 25.0.1 2025-10-21 LTS OpenJDK Runtime Environment Temurin-25.0.1+8 (build 25.0.1+8-LTS) OpenJDK 64-Bit Server VM Temurin-25.0.1+8 (build 25.0.1+8-LTS, mixed mode, sharing)

Python Version

Python 3.14.2

Additional Context (Screenshots, Files, etc)
59.0 Check_Permission Check Permission 200 100 Default Outcome Admin_Only and true Allowed Admin Only Check_Permission Admin_Only Test Security Flow BuilderType Flow Flow
Workaround

No response

Urgency

Hight

主要语言
TypeScript
星标
241
派生
51
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

forcedotcom/code-analyzer 的其他 Issue

查看 forcedotcom/code-analyzer 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。