Make analyzer timeout configurable

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls

[Copilot]

The expansion analyzer timeout was hardcoded at 10 seconds. This PR makes it configurable via CLI flags and test parameters, with a 100ms default for tests to keep them fast.

Changes

Core API

• source-analyze now requires #:timeout-ms parameter (was hardcoded at 10000ms)
• resyntax-analyze and resyntax-analyze-all accept optional #:timeout-ms with 10000ms default
• Timeout logging changed from seconds to milliseconds for precision

CLI

• Added --analyzer-timeout <ms> flag to resyntax analyze and resyntax fix commands
• Defaults to 10000ms when unspecified

Test Infrastructure

• Added current-analyzer-timeout-millis parameter (default: 100ms)
• Implemented @analyzer-timeout-millis test parameter for test:, no-change-test:, and analysis-test: cases

Example

#lang resyntax/test
test: "fast tests use 100ms default"
- (or1 (or23))
- (or123)
test: "override for complex analysis"
@analyzer-timeout-millis 5000
- (complex-code)
- (refactored-code)
analysis-test: "works with all test types"
@analyzer-timeout-millis 500
- (code)
@inspect - (subform)
@property foo

Command line:

resyntax analyze --file myfile.rkt --analyzer-timeout 15000
resyntax fix --directory src/ --analyzer-timeout 5000

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable analyzer timeout</issue_title>
<issue_description>The expansion analyzer timeout should be configurable, both at the command line and in analysis-test: cases. It should be passed to source-analyze explicitly as a mandatory keyword argument. The main.rkt Resyntax code should use the same default timeout that source-analyze currently does, but in #lang resyntax/test the timeout should default to something very short, like 100ms. Test cases should be able to specify a longer timeout with an @analyzer-timeout-millis test parameter, like so:

#lang resyntax/test
header: - #lang racket/base
test: "foo"
@analyzer-timeout-millis 500
- (old-code)
- (new-code)
no-change-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
analysis-test: "foo"
@analyzer-timeout-millis 500
- (old-code)
@inspect - old-code
@property bar
@assert baz
```</issue_description>
## Comments on the Issue (you are @copilot in this section)
<comments>
</comments>

• FixesConfigurable analyzer timeout #733

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Resyntax analyzed 6 files in this pull request and found no issues.

[coveralls]

Pull Request Test Coverage Report for Build #320

Details

• 61 of 82(74.39%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 93.63%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.rkt	17	20	85.0%
test.rkt	8	12	66.67%
cli.rkt	7	21	33.33%

Totals
Change from base Build #317:	-0.05%
Covered Lines:	15140
Relevant Lines:	16170

---

💛 - Coveralls