Skip to content

Type checker error during run extension in npm:watch #1969

Open

Description

@ZA139

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
Image

Best Regards
Charles

Activity

  1. changed the title [-]original error during npm:watch[/-] [+]Type error during unit tests in npm:watch[/+] on Oct 29, 2025
  2. changed the title [-]Type error during unit tests in npm:watch[/-] [+]Type checker error during unit tests in npm:watch[/+] on Oct 29, 2025
  3. changed the title [-]Type checker error during unit tests in npm:watch[/-] [+]Type checker error during run extension in npm:watch[/+] on Oct 29, 2025
  4. rchiodo commented on Oct 29, 2025

    @rchiodo
    Contributor

    Eleanor Boyd (@eleanorjboyd) this would be a build error in the extension. This has nothing to do with debugpy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    externalThe issue is caused by external component interacting with debugpy

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions