Type checker error during run extension in npm:watch
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start at src/test/unittest/noConfigDebugInit.unit.test.ts line 220 and reproduce the TypeScript error through npm:watch. Compare the callback types reported there with the surrounding test and determine whether the error is environmental or requires a code change; done means npm:watch completes without the reported type error and the existing nox lint and nox tests still pass.
Written by the indexing model from the issue text.
Description
Hi
I encountered an npmwatch error while developing a process attacher.
I downloaded the distribution code, but the issue persists.
Wanna make sure this error is my local environment or common. Should I ignore this with @ts-expect-error, or should someone fix this?
BTW, the nox lint and nox tests both passed
Argument of type '(_path: any, callback: (arg0: null, arg1: Buffer) => void) => void' is not assignable to parameter of type '(path: PathOrFileDescriptor, callback: (err: ErrnoException | null, data: NonSharedBuffer) => void) => void'.
Types of parameters 'callback' and 'callback' are incompatible.
Type '(err: ErrnoException | null, data: NonSharedBuffer) => void' is not assignable to type '(arg0: null, arg1: Buffer<ArrayBufferLike>) => void'.
Types of parameters 'data' and 'arg1' are incompatible.
Type 'Buffer<ArrayBufferLike>' is not assignable to type 'NonSharedBuffer'.
Type 'ArrayBufferLike' is not assignable to type 'ArrayBuffer'.
Type 'SharedArrayBuffer' is not assignable to type 'ArrayBuffer'.
Types of property '[Symbol.toStringTag]' are incompatible.
Type '"SharedArrayBuffer"' is not assignable to type '"ArrayBuffer"'.ts(2345)
which in https://github.com/microsoft/vscode-python-src/test/unittest/noConfigDebugInit.unit.test.ts line 220
Best Regards
Charles
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·