Repository navigation
Fix vibe-check-runner concurrency bug and update commit message - #339
beginwebdev2002 wants to merge 1 commit into
Conversation
Co-authored-by: beginwebdev2002 <102213457+beginwebdev2002@users.noreply.github.com>
|
馃憢 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Fixed an issue in
vibe-check-runner.jswhere processing multiple files concurrently viaPromise.allwould lead to overwritten "Golden Prompts" in state and thus incorrect simulation generations. Now correctly processes each file sequentially in a grouped structure. Also modified the success commit message to[chore: fidelity-pass]per the required specifications, and replaced synchronousfs.existsSyncwith the asynchronousawait fileOrDirExistshelper for better non-blocking loop handling, preventing source files from overwriting each other by giving them unique names.PR created automatically by Jules for task 6966803299815935143 started by @beginwebdev2002