selenium测试ie11 anyproxy报错 Error: write ECONNRESET
- Dominant language
- JavaScript
- Stars
- 7.9k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Windows 平台
anyporxy version=4.1.3 nodejs version=v16.3.0
报错信息:
[AnyProxy ERROR][2021-07-13 17:50:44]: got an uncaught exception, is there anything goes wrong in your rule file ?
Error: write ECONNRESET
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:769:11)
at Socket._write (node:net:781:8)
at writeOrBuffer (node:internal/streams/writable:389:12)
at _write (node:internal/streams/writable:330:10)
at Socket.Writable.write (node:internal/streams/writable:334:10)
at C:\Users\95406\AppData\Roaming\npm\node_modules\anyproxy\lib\requestHandler.js:564:21
at new Promise ()
at C:\Users\95406\AppData\Roaming\npm\node_modules\anyproxy\lib\requestHandler.js:562:16
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the Windows Selenium IE11 case with AnyProxy 4.1.3 and Node.js v16.3.0. Start at lib/requestHandler.js around lines 562-564 and trace the ECONNRESET write path. Done means the cause is understood and the reported uncaught exception no longer occurs in this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100