Skip to content

Conversation

@overlookmotel
Copy link
Member

@overlookmotel overlookmotel commented Aug 18, 2025

Partially revert #13186. Linter had suggested to parallelize this code, but that was a bad idea as it makes the output of the codegen non-deterministic.

@github-actions github-actions bot added the C-bug Category - Bug label Aug 18, 2025
Copy link
Member Author


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@overlookmotel overlookmotel marked this pull request as ready for review August 18, 2025 14:48
Copilot AI review requested due to automatic review settings August 18, 2025 14:48
@overlookmotel
Copy link
Member Author

Merging without review, as this mistake (my mistake) has screwed everything up.

@overlookmotel overlookmotel merged commit 4f8506e into main Aug 18, 2025
18 checks passed
@overlookmotel overlookmotel deleted the 08-18-fix_traverse_fix_codegen branch August 18, 2025 14:53
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes a non-deterministic codegen issue by reverting parallel processing back to sequential processing. The change ensures deterministic output from the traverse codegen by processing files one at a time instead of using Promise.all with concurrent processing.

  • Reverts parallelization of file processing to prevent non-deterministic codegen output
  • Adds oxlint disable comment to suppress the no-await-in-loop warning

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

const types = Object.create(null);
await Promise.all(FILENAMES.map(async (filename) => {
for (const filename of FILENAMES) {
// oxlint-disable-next-line no-await-in-loop
Copy link

Copilot AI Aug 18, 2025

Choose a reason for hiding this comment

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

The disable comment uses 'oxlint' but should likely be 'eslint' based on standard linting tool naming conventions.

Suggested change
// oxlint-disable-next-line no-await-in-loop
// eslint-disable-next-line no-await-in-loop

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C-bug Category - Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants