Add documentation/scheme to HTTP API for EdgeDB Auth

I followed the example from the documentation on using EdgeDB Auth with FastAPI and made one change in the configuration — I set require_verification=true for EmailPasswordProvider. As a result, the /register endpoint did not return the code parameter (which is generally expected), but I found out about this from the source code (here).
Proposal
Add documentation/scheme for the HTTP API for EdgeDB Auth to understand what data and in what format needs to be sent, and what to expect in response in different cases.

I created an OpenAPI schema for the main endpoints. Feel free to use it as a base for inclusion in the documentation, but the schema needs review.
OpenAPI schema

openapi: 3.0.0
info:
  title: EdgeDB Auth API
  version: 1.0.0
  description: API for EdgeDB authentication and authorization

paths:
  /branch/{branch}/ext/auth/authorize:
    get:
      summary: Initiate OAuth authorization
      description: Initiates the OAuth authorization process for a specified provider
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: provider
          in: query
          required: true
          schema:
            type: string
        - name: redirect_to
          in: query
          required: true
          schema:
            type: string
        - name: redirect_to_on_signup
          in: query
          required: false
          schema:
            type: string
        - name: challenge
          in: query
          required: true
          schema:
            type: string
          description: PKCE challenge (also known as code_challenge)
      responses:
        '302':
          description: Redirect to OAuth provider's authorization page
          headers:
            Location:
              schema:
                type: string
              description: URL of the OAuth provider's authorization page
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InvalidData
                  message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred.
  /branch/{branch}/ext/auth/callback:
    get:
      summary: Handle OAuth callback
      description: Processes the OAuth callback from the authentication provider
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: state
          in: query
          required: false
          schema:
            type: string
        - name: code
          in: query
          required: false
          schema:
            type: string
        - name: error
          in: query
          required: false
          schema:
            type: string
        - name: error_description
          in: query
          required: false
          schema:
            type: string
      responses:
        '302':
          description: Successful authentication redirect
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after successful authentication
            Set-Cookie:
              schema:
                type: string
              description: Session cookie
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingState:
                  value:
                    error:
                      type: InvalidData
                      message: Provider did not include the 'state' parameter in callback
                missingCode:
                  value:
                    error:
                      type: InvalidData
                      message: Provider did not include the 'code' parameter in callback
                invalidState:
                  value:
                    error:
                      type: InvalidData
                      message: Invalid state token
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred.
    post:
      summary: Handle OAuth callback (POST)
      description: Processes the OAuth callback from the authentication provider using POST method
      requestBody:
        required: true
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                state:
                  type: string
                code:
                  type: string
                error:
                  type: string
                error_description:
                  type: string
      responses:
        '302':
          description: Successful authentication redirect
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after successful authentication
            Set-Cookie:
              schema:
                type: string
              description: Session cookie
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingState:
                  value:
                    error:
                      type: InvalidData
                      message: Provider did not include the 'state' parameter in callback
                missingCode:
                  value:
                    error:
                      type: InvalidData
                      message: Provider did not include the 'code' parameter in callback
                invalidState:
                  value:
                    error:
                      type: InvalidData
                      message: Invalid state token
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred.
  /branch/{branch}/ext/auth/token:
    get:
      summary: Exchange PKCE code for authentication token
      description: Exchanges a PKCE code for an authentication token
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: code
          in: query
          required: true
          schema:
            type: string
        - name: verifier
          in: query
          required: true
          schema:
            type: string
          description: PKCE verifier (also known as code_verifier)
      responses:
        '200':
          description: Successful token exchange
          content:
            application/json:
              schema:
                type: object
                properties:
                  auth_token:
                    type: string
                  identity_id:
                    type: string
                  provider_token:
                    type: string
                    nullable: true
                  provider_refresh_token:
                    type: string
                    nullable: true
              example:
                auth_token: "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
                identity_id: "1234567890abcdef"
                provider_token: "access_token_from_provider"
                provider_refresh_token: "refresh_token_from_provider"
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidVerifierLength:
                  value:
                    error:
                      type: InvalidData
                      message: Verifier must be at least 43 characters long
                invalidVerifierLengthMax:
                  value:
                    error:
                      type: InvalidData
                      message: Verifier must be shorter than 128 characters long
                invalidData:
                  value:
                    error:
                      type: InvalidData
                      message: Code is not associated with an Identity
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: NoIdentityFound
                  message: Could not find a matching PKCE code
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/register:
    post:
      summary: Register a new user
      description: Registers a new user with the specified provider
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - email
                - password
              properties:
                provider:
                  type: string
                email:
                  type: string
                  format: email
                password:
                  type: string
                redirect_to:
                  type: string
                challenge:
                  type: string
                verify_url:
                  type: string
                redirect_on_failure:
                  type: string
      responses:
        '201':
          description: User registered successfully
          content:
            application/json:
              schema:
                oneOf:
                  - type: object
                    properties:
                      verification_email_sent_at:
                        type: string
                        format: date-time
                  - type: object
                    properties:
                      code:
                        type: string
                      provider:
                        type: string
              examples:
                verificationRequired:
                  value:
                    verification_email_sent_at: "2024-09-23T12:00:00Z"
                verificationNotRequired:
                  value:
                    code: "abc123"
                    provider: "email_password"
        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after registration
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
                missingProvider:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "provider" in register request
                missingChallenge:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "challenge" in register request
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: UserAlreadyRegistered
                  message: User with this email is already registered
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/authenticate:
    post:
      summary: Authenticate a user
      description: Authenticates a user with the specified provider
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - challenge
                - email
                - password
              properties:
                provider:
                  type: string
                challenge:
                  type: string
                email:
                  type: string
                  format: email
                password:
                  type: string
                redirect_to:
                  type: string
                redirect_on_failure:
                  type: string
      responses:
        '200':
          description: Successful authentication
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: string
              example:
                code: "abc123"
        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after authentication
            Set-Cookie:
              schema:
                type: string
              description: Session cookie
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingProvider:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "provider" in register request
                missingChallenge:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "challenge" in register request
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: VerificationRequired
                  message: Email verification required
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/verify:
    post:
      summary: Verify user email
      description: Verifies a user's email address using a verification token
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - verification_token
                - provider
              properties:
                verification_token:
                  type: string
                provider:
                  type: string
      responses:
        '200':
          description: Successful verification with challenge
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: string
              example:
                code: "abc123"
        '204':
          description: Successful verification without challenge or redirect
        '302':
          description: Successful verification with redirect
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after verification
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidVerificationToken:
                  value:
                    error:
                      type: InvalidData
                      message: Invalid verification token
                noIdentityFound:
                  value:
                    error:
                      type: NoIdentityFound
                      message: Could not verify email for identity {identity_id}. This email address may not exist in our system, or it might already be verified.
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                value:
                  error:
                    type: VerificationTokenExpired
                    message: The 'iat' claim in verification token is older than 24 hours
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/resend-verification-email:
    post:
      summary: Resend verification email
      description: Resends the verification email for a user
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              oneOf:
                - type: object
                  required:
                    - provider
                    - verification_token
                  properties:
                    provider:
                      type: string
                    verification_token:
                      type: string
                    verify_url:
                      type: string
                - type: object
                  required:
                    - provider
                    - email
                  properties:
                    provider:
                      type: string
                    email:
                      type: string
                      format: email
                    challenge:
                      type: string
                      description: PKCE challenge (also known as code_challenge)
                    redirect_to:
                      type: string
                    verify_url:
                      type: string

      responses:
        '200':
          description: Verification email sent successfully
          content:
            application/json:
              schema:
                type: object
        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after sending the verification email
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingProvider:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "provider" in register request
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
                missingTokenOrEmail:
                  value:
                    error:
                      type: InvalidData
                      message: Missing 'verification_token' or 'email'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: NoIdentityFound
                  message: Could not find a matching identity
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/send-reset-email:
    post:
      summary: Send password reset email
      description: Sends a password reset email to the specified email address
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - email
                - reset_url
                - challenge
              properties:
                provider:
                  type: string
                email:
                  type: string
                  format: email
                reset_url:
                  type: string
                challenge:
                  type: string
                redirect_to:
                  type: string
      responses:
        '200':
          description: Password reset email sent successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  email_sent:
                    type: string
              example:
                email_sent<EMAIL_ADDRESS>        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after sending the reset email
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: Failed to send the email, please try again later.
  /branch/{branch}/ext/auth/reset-password:
    post:
      summary: Reset user password
      description: Resets the password for a user using a reset token
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - reset_token
              properties:
                provider:
                  type: string
                reset_token:
                  type: string
                redirect_to:
                  type: string
      responses:
        '200':
          description: Password reset successful
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: string
              example:
                code: "abc123"
        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after password reset
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingProvider:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "provider" in register request
                missingResetToken:
                  value:
                    error:
                      type: InvalidData
                      message: Missing "reset_token" in register request
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/magic-link/register:
    post:
      summary: Register a new user using magic link
      description: Registers a new user and sends a magic link for authentication
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - email
                - challenge
                - callback_url
                - redirect_on_failure
              properties:
                provider:
                  type: string
                email:
                  type: string
                  format: email
                challenge:
                  type: string
                callback_url:
                  type: string
                redirect_on_failure:
                  type: string
                redirect_to:
                  type: string
      responses:
        '200':
          description: User registered successfully and magic link sent
          content:
            application/json:
              schema:
                type: object
                properties:
                  email_sent:
                    type: string
              example:
                email_sent<EMAIL_ADDRESS>        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after sending the magic link
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidCallbackUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Callback URL does not match any allowed URLs.
                invalidErrorRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Error redirect URL does not match any allowed URLs.
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
                missingJsonAccept:
                  value:
                    error:
                      type: InvalidData
                      message: Request must accept JSON or provide a redirect URL.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/magic-link/email:
    post:
      summary: Send magic link email
      description: Sends a magic link email for authentication
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - email
                - challenge
                - callback_url
                - redirect_on_failure
              properties:
                provider:
                  type: string
                email:
                  type: string
                  format: email
                challenge:
                  type: string
                callback_url:
                  type: string
                redirect_on_failure:
                  type: string
                redirect_to:
                  type: string
      responses:
        '200':
          description: Magic link email sent successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  email_sent:
                    type: string
              example:
                email_sent<EMAIL_ADDRESS>        '302':
          description: Redirect to specified URL
          headers:
            Location:
              schema:
                type: string
              description: URL to redirect the user after sending the magic link email
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidCallbackUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Callback URL does not match any allowed URLs.
                invalidErrorRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Error redirect URL does not match any allowed URLs.
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
                missingRequiredField:
                  value:
                    error:
                      type: InvalidData
                      message: Missing required field in request
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/magic-link/authenticate:
    get:
      summary: Authenticate using magic link
      description: Authenticates a user using a magic link token
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: token
          in: query
          required: true
          schema:
            type: string
        - name: redirect_on_failure
          in: query
          required: false
          schema:
            type: string
      responses:
        '302':
          description: Successful authentication, redirect to callback URL
          headers:
            Location:
              schema:
                type: string
              description: Callback URL with authentication code
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                invalidToken:
                  value:
                    error:
                      type: InvalidData
                      message: Invalid 'magic_link_token'
                invalidRedirectUrl:
                  value:
                    error:
                      type: InvalidData
                      message: Redirect URL does not match any allowed URLs.
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/webauthn/register:
    post:
      summary: Register a new WebAuthn credential
      description: Registers a new WebAuthn credential for a user
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - provider
                - challenge
                - email
                - credentials
                - verify_url
              properties:
                provider:
                  type: string
                challenge:
                  type: string
                email:
                  type: string
                  format: email
                credentials:
                  type: string
                verify_url:
                  type: string
                user_handle:
                  type: string
      responses:
        '201':
          description: WebAuthn credential registered successfully
          content:
            application/json:
              schema:
                oneOf:
                  - type: object
                    properties:
                      verification_email_sent_at:
                        type: string
                        format: date-time
                  - type: object
                    properties:
                      code:
                        type: string
                      provider:
                        type: string
              examples:
                verificationRequired:
                  value:
                    verification_email_sent_at: "2024-09-25T12:00:00Z"
                verificationNotRequired:
                  value:
                    code: "abc123"
                    provider: "webauthn"
          headers:
            Set-Cookie:
              schema:
                type: string
              description: Clears the edgedb-webauthn-registration-user-handle cookie
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingUserHandle:
                  value:
                    error:
                      type: InvalidData
                      message: Missing user_handle from cookie or request body
                invalidUserHandle:
                  value:
                    error:
                      type: InvalidData
                      message: Failed to decode user_handle
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/webauthn/register/options:
    get:
      summary: Get WebAuthn registration options
      description: Retrieves WebAuthn registration options for a given email
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: email
          in: query
          required: true
          schema:
            type: string
            format: email
      responses:
        '200':
          description: Successful retrieval of WebAuthn registration options
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OptionsResponse'
          headers:
            Set-Cookie:
              schema:
                type: string
              description: Sets the edgedb-webauthn-registration-user-handle cookie
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InvalidData
                  message: Missing required email parameter
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/webauthn/authenticate:
    post:
      summary: Authenticate using WebAuthn
      description: Authenticates a user using WebAuthn credentials
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - challenge
                - email
                - assertion
              properties:
                challenge:
                  type: string
                email:
                  type: string
                  format: email
                assertion:
                  type: string
      responses:
        '200':
          description: Successful authentication
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: string
              example:
                code: "abc123"
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InvalidData
                  message: Missing required field in request
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: VerificationRequired
                  message: Email verification required
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InternalServerError
                  message: An unexpected error occurred
  /branch/{branch}/ext/auth/webauthn/authenticate/options:
    get:
      summary: Get WebAuthn authentication options
      description: Retrieves WebAuthn authentication options for a given email
      parameters:
        - name: branch
          in: path
          required: true
          schema:
            type: string
        - name: email
          in: query
          required: true
          schema:
            type: string
            format: email
      responses:
        '200':
          description: Successful retrieval of WebAuthn authentication options
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OptionsResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  type: InvalidData
                  message: Missing required email parameter
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                missingConfiguration:
                  value:
                    error:
                      type: MissingConfiguration
                      message: WebAuthn provider is not configured
                internalServerError:
                  value:
                    error:
                      type: InternalServerError
                      message: An unexpected error occurred
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: object
          properties:
            type:
              type: string
            message:
              type: string

    OptionsResponse:
      oneOf:
        - $ref: '#/components/schemas/PublicKeyCredentialCreationOptionsResponse'
        - $ref: '#/components/schemas/PublicKeyCredentialRequestOptionsResponse'

    PublicKeyCredentialCreationOptionsResponse:
      type: object
      properties:
        rp:
          type: object
          properties:
            name:
              type: string
            id:
              type: string
          required:
            - name
        user:
          type: object
          properties:
            id:
              type: string
            name:
              type: string
            displayName:
              type: string
          required:
            - id
            - name
            - displayName
        challenge:
          type: string
        pubKeyCredParams:
          type: array
          items:
            type: object
            properties:
              type:
                type: string
              alg:
                type: integer
            required:
              - type
              - alg
        timeout:
          type: integer
        excludeCredentials:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              type:
                type: string
              transports:
                type: array
                items:
                  type: string
            required:
              - id
              - type
        authenticatorSelection:
          type: object
          properties:
            authenticatorAttachment:
              type: string
            residentKey:
              type: string
            requireResidentKey:
              type: boolean
            userVerification:
              type: string
        attestation:
          type: string
      required:
        - rp
        - user
        - challenge
        - pubKeyCredParams

    PublicKeyCredentialRequestOptionsResponse:
      type: object
      properties:
        challenge:
          type: string
        timeout:
          type: integer
        rpId:
          type: string
        allowCredentials:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              type:
                type: string
              transports:
                type: array
                items:
                  type: string
            required:
              - id
              - type
        userVerification:
          type: string
      required:
        - challenge


Wrong NodePath in tool mode

Godot version
3.5.2 stable
System information
Kubuntu 22.04
Issue description
An attempt to get a node using an absolute path in an editor with tool mode fails. The node has a strange path that doesn't match the scene hierarchy.
The path looks like this:  /root/EditorNode/@@596/@@597/@@605/@@607/@@611/@@615/@@616/@@617/@@633/@@634/@@643/@@644/@@6618/@@6450/@@6451/@@6452/@@6453/@@6454/@@6455/Node2D/Icon
Instead of:  /root/Node2D/Icon
Steps to reproduce
Open MRP and look at the output, then run the scene and compare the output with the previous one
Minimal reproduction project
path_in_editor.zip

The editor is a scene, and the scene you are editing is instanced inside of it.
Although I understand it is unexpected, this is the way it works.
My opinion on the matter is that I'd rather not have this hidden, as having access to the editor scene can be very powerful for plugins. I believe it would a big change to offer means to hide it anyway.
Workaround by using relative NodePaths.

It looks useful. A little description in the documentation could clarify this point.
I would imagine that a separate property might exist to access the editor scene. It seems more logical for me to have the same behavior in the first place, and have access to the editor itself if necessary.


Feature Request: Git Worktree: Add: Match remote branch name and make new branch name optional

First off thanks for this awesome tool!
Feature Request:
I find that specifying the new branch name every time I want to add a new worktree is quite annoying. It would be much nicer if that flow works similar to the gitlens worktree feature in that it just shows me the remotes and I can choose one right away and then use the branch name as the folder name. You would need to process the branch name and replace / with - in order to keep all clones just one folder deep. However, it would be fine to do it like git lens and create subfolders that match the branch name.
E.g:

Command Palette -> Git Worktree: Add
(Optional) new branch name if the user specifies one then it works just as how it does right now. However, if they leave this empty, then use the selection in step 3 to create the folder structure.
Select a remote branch -> feature/upgrade-libs
If no new branch name is specified then match the remote by creating {worktree_root}/feature-upgrade-libs/{repo_cloned_here}

I hope this is clear. I think it would be an easier way to clone remotes that match the remote branch name by default.
Thanks
EDIT:
I realize now that maybe the intent of this is different. Maybe this would be a difference command called Git Worktree: Checkout.

Hi @tomoum, I am glad you like the extension.
Sorry for the delay, but I've been on the run for the past few days.
Concerning the level of the worktrees, your idea about replacing / with - is good. I will look into it as another feature where users would be able to create a worktree based on their preferences. It will be configurable based on the vscode properties.
From my understanding, one solution would be the Git Worktree: Checkout you suggested. The other one would be to change the flow of the Git Worktree: Add operation to show you first the remote branches, select a remote branch, then type the new worktree name or press ESC to cancel the operation.
Would that be something you like? Or have I misunderstood something?

yes, that would be amazing. Either of those would be great additions! that would be much appreciated! thanks, @alexiszamanidis

I am also interested in the suggested feature!
"to change the flow of the Git Worktree: Add operation to show you first the remote / existing branches"
Sometimes i think this will be just a small change, so i don't create a worktree for it, but later the change requires more rework, and i want to create a worktree with an existing feature branch.
I also like the suggestion to use a remote branch for creating a new worktree!

Hi @grooc,
This is an excellent idea.
So, in the first step, we will list all the local and remote branches and have something like this: master, origin/master.
I'm definitely tweaking it in the implementation.

This is perfect now. Works like a charm. This is exactly what I wanted. Thanks @alexiszamanidis !! great job!

I'm glad you liked it.
Thank you for your time and contribution.


Properly marshal event time to RFC-3339 format

In event_marshal.go, time.String() is currently used to marshal the time to a string: https://github.com/cloudevents/sdk-go/blob/ba92a5c9a1e2508d855930049999ccd75636f0cb/v2/event/event_marshal.go#L76-L79
However, in the go time.Time documentation, it says about the method time.Time.String():

The returned string is meant for debugging; for a stable serialized representation, use t.MarshalText, t.MarshalBinary, or t.Format with an explicit format string.

In the Spec, it is required that the time is serialized to RFC-3339, so we should be using time.Time.MarshalText instead

Or time.Format() with RFC3339 - wanna submit a PR?

Happy to open a PR, but I know @MaryamTaj has been wanting to make some contributions so I'll see if she is interested in this one first :)

@duglin I would love to work on this!

Commented in the PR to discuss whether this must be considered a breaking change.


Type inference when a function is overloaded and the input param is a union of possible inputs

If we define a function and two interfaces like this:
    interface A {

    }

    interface B {

    }

    func(type: 'A'): A;
    func(type: 'B'): B;
    func(type: string) {
     /// this function returns an object of type A or B depending on the string input
    }

I would like to be able to call the function like this
var input = <"A"|"B">getInput();
var output = func(input);

And have the return type be A | B. it seems to me this is logicaly consistent. No idea if it is hard to implement.
Syntactic
Does not change the syntax.
Semantic
Error	TS2345	Argument of type '"A" | "B"' is not assignable to parameter of type '"B"'.
Type '"A"' is not assignable to type '"B"'.
The compiler is checking if all possible types of input match all the overloads, when in fact we just need
each type to match a single overload.
Emit
No change past the point of inference.
Compatibility
Should not break anything as this example code does not compile at the moment
Other
Can the feature be implemented without negatively affecting compiler performance?
Might even make it marginally faster as we can stop checking when we find the first overload matching the first type in the union and move on to the next.

While this makes sense for a functions with single parameters it does not work for the general case.
consider:
declare function push(list: number[], value: number);
declare function push(list: string[], value: string);

push(Math.random() ? numberList : stringList, 2);

Please see discussion in https://github.com/Microsoft/TypeScript/issues/10620.

It could work, you just need to check the combinations to make sure they are all correct and then you infer the return type as a union of all the return types of the overloads that matches any of the possible inputs .
In the example you gave these are the the two possible inputs.
number[] * number
string[] * number
The function does not take  string[] * number so you get an error.

Doing the overload resolution on the cartesian product of the types of all parameters is not something that would scale. we recommend adding a signature with the union type.

It will scale, it will just do so none linearly :)
However think it's not going to be a problem in 99.999% of the cases and even if it is a problem you can cap the number of combinations and at some point give an error telling the developer functions with 100 overloads that gets passed 100 params that are all union types is not what the language builders had in mind.
fs 3.1


Unable to docker pull selenoid/vnc_chrome

Hello. I am unable to execute the docker command to grab the latest vnc_chrome image from:
https://hub.docker.com/r/selenoid/vnc_chrome
docker pull selenoid/vnc_chrome
The below response is returned:
Using default tag: latest
Error response from daemon: manifest for selenoid/vnc_chrome:latest not found

Could I ask if this is expected behaviour?

There is no latest tag for that image, please use tag 73.0.
ср, 20 мар. 2019 г., 9:29 timothyjmtan<EMAIL_ADDRESS>
Hello. I am unable to execute the docker command to grab the latest
vnc_chrome image from:
https://hub.docker.com/r/selenoid/vnc_chrome
docker pull selenoid/vnc_chrome
The below response is returned:
Using default tag: latest
Error response from daemon: manifest for selenoid/vnc_chrome:latest not found
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aerokube/selenoid/issues/701, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWNbSKdcGKFcXWNueZYlbtFixa9d-TXks5vYdVSgaJpZM4b-khs
.

Thanks for the quick reply, it works!

@timothyjmtan Why there's no latest tag, actually? This way we have to keep up with the release tags, if we want to run only on, say, the latest three or four releases. I might be missing something though. Could you elaborate? Thanks,

@rvvincelli because on some browsers like Firefox latest will simply not work.

@rvvincelli because on some browsers like Firefox latest will simply not work.

Ok @vania-pooh ! Say that we want to run our tests only on the latest supported browser version, for each browser. Right now it is 96.0 for Chrome. I thought to get smart with the tag, but I see this is not possible. How would you suggest to go about it? Is manually bumping up to 96.0 in the user section in the config map the best option, or do you see a better way?
Thank you,

@rvvincelli e.g. CM tools is fetching image tags from Docker Hub. So doing something like this could help:
$ cm selenoid configure --force --last-versions 2 --browsers "firefox;chrome"
$ docker kill -s HUP selenoid

@vania-pooh Thank you for this oneliner! We are actually using Moon on DigitalOcean (free plan), as managing our own grid was too much work really :) I guess I can automate out some kubectl apply to update the map with the desired versions.

@rvvincelli next Moon version will have versions auto-update. E.g. for Chrome version X it will automatically try to pull image like browsers/chrome:X.

@vania-pooh Sorry for the repo confusion, I just piggybacked the first issue from the search. Awesome news! Last question: will we have to reinstall the Moon cluster? Coming from Azure, not sure how "managed" is a managed solution in Digitalocean.
Many thanks for Moon and your team contributions to the community.

@rvvincelli yes, new version will be a major upgrade and will require configuration.`


Update AddEventCommandSequence diagram for DG

Help me see if the diagram has any mistakes. This is a lower priority PR

LGTM


Learn and Teach: Mutexes

All the things like mutex are very simple to understand but may look puzzling due to jargon. Solve this by learning about what a mutex is and prepare a doc for others to learn.  Here we are all about learning
A little Introduction
Often in low level programming languages like rust,golang you come across multi threading. It is everywhere from web servers handling multiple requests to databases managing concurrent transactions to video games processing physics and rendering simultaneously. Mutexes  they're used to prevent something called a  race conditions . For example, when multiple users try to reserve the same airline seat or update their social media profile simultaneously, mutexes help maintain data consistency. They are primitive to the operating system and a must learn.
Objective
create a docs/MUTEX.md file and write about mutexes as if you are explaining to a child. Maybe cover different mechanisms also like a semaphore!. Also talk about them in context of golang and how they are used in the project!
Scoring
This is marked as Easy but if i see some amazing stuff you may get something more out of it (a chapo by chopra sir)

Sir, please review my changes on the issue #8 Learn and Teach: Mutexes.


toolbarEnabled doesn't work still

Bug
toolbarEnabled={true} in MapView doesn't bring Google toolbar up as expected.
There was corresponding issue but it was closed long ago while problem still persists. None of the offerd there hacks worked for me with the most recent version of RNM
Environment info
React native info output:
 ystem:
    OS: Windows 8.1
    CPU: (4) x64 Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
    Memory: 891.43 MB / 7.93 GB
  Binaries:
    Node: 10.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.3.2 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-191.8<IP_ADDRESS>91312

Library version: 0.25.0
"react-native": "0.60.5",
Steps To Reproduce

put toolbarEnabled={true} in MapView
draw markers, tap any

Describe what you expected to happen:
Toolbar appears
Reproducible sample code

<
View style={styles.container}>
          <MapView
            style={styles.map}
            region={this.state.mapDimensions}
            mapType='standard'
            zoomEnabled={true}
            zoomControlEnabled={true}
            toolbarEnabled={true}
            showsCompass={false}
          >
            {this.state.markers2show.map((marker) => this._renderMarker(marker))}
          </MapView>
 </View>

const styles = StyleSheet.create({
  rootContainer: {
    flex: 1
  },

  container: {
    width: cWidth,
    height: cHeight,
    justifyContent: 'flex-end',
    alignItems: 'center',
    backgroundColor: '#ffffff',
    marginHorizontal: 0,
    marginTop: globalStyles.viewMarginTop,
    marginBottom: globalStyles.viewMarginBottom,
  },

  map: {
    ...StyleSheet.absoluteFillObject,
  },

the same problem!

Same issue. I am not able to enable toolbar for maps.

As I noticed, toolbar starts to appear on marker press only after parent component's size (e.g. , , etc.) updated at least one time after finish of map loading. So, the solution is just to change the size of map container by -1 or 1 (seems, that user won't notice that):
`class Locations extends Component {
constructor(props) {
super(props);
this.state = {
bottom: -1
}
}
   fixToolbar = () => {
      if(this.state.bottom === -1){
        this.setState({
          bottom: 0
        })
      }
    }

render() {

  return (
    <View style ={styles.container}>
      <MapView
        style={ [styles.map, { bottom:this.state.bottom}] }
        region={region}
        toolbarEnabled={true} >

        {
          this.props.markers.map((marker) =>
           (<MapView.Marker
               onPress={() => this.fixToolbar()}
              />
              ))
              }
      </MapView>
    </View>
  );
}

}`

As I noticed, toolbar starts to appear on marker press only after parent component's size (e.g. , , etc.) updated at least one time after finish of map loading. So, the solution is just to change the size of map container by -1 or 1 (seems, that user won't notice that):
class myMap extends Component {
    constructor(props) {
        super(props);
        this.state = {
              bottom: -1
               }
    }
       fixToolbar = () => {
          if(this.state.bottom === -1){
            this.setState({
              bottom: 0
            })
          }
        }
    render() {
      return (
        <View style ={styles.container}>
          <MapView
            style={ [styles.map, { bottom:this.state.bottom}] }
            region={region}
            toolbarEnabled={true} >
            {
              this.props.markers.map((marker) =>
               (<Marker
                   onPress={() => this.fixToolbar()}
                  />
                  ))
                  }
          </MapView>
        </View>
      );
    }
  }

I just tested using onMarkerPress event from <MapView /> component which is no need to pass fixToolbar method on each <Marker /> component. Hope it works for you too. :bow:
<MapView initialRegion={initialRegion} style={[styles.map, { bottom: this.state.bottom}]} onMarkerPress={this.fixToolbar}>
  ... // Polygon, Polyline, Marker components here.
</MapView>


Pylance client: couldn't create connection to server.Message: Pending response rejected since connection got disposed

Type: Bug
c:\Users\MM.vscode\extensions\ms-python.vscode-pylance-2022.10.10\dist\server.bundle.js:1
SyntaxError: Invalid or unexpected token
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1086:15)
at Module._compile (node:internal/modules/cjs/loader:1121:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1220:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
[Info  - 09:48:40] Connection to server got closed. Server will restart.
[Error - 09:48:40] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:40] Pylance client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
c:\Users\MM.vscode\extensions\ms-python.vscode-pylance-2022.10.10\dist\server.bundle.js:1
SyntaxError: Invalid or unexpected token
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1086:15)
at Module._compile (node:internal/modules/cjs/loader:1121:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1220:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
[Info  - 09:48:41] Connection to server got closed. Server will restart.
[Error - 09:48:41] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Pylance client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
c:\Users\MM.vscode\extensions\ms-python.vscode-pylance-2022.10.10\dist\server.bundle.js:1
SyntaxError: Invalid or unexpected token
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1086:15)
at Module._compile (node:internal/modules/cjs/loader:1121:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1220:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
[Info  - 09:48:41] Connection to server got closed. Server will restart.
[Error - 09:48:41] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Pylance client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Restarting server failed
Message: Pending response rejected since connection got disposed
Code: -32097
c:\Users\MM.vscode\extensions\ms-python.vscode-pylance-2022.10.10\dist\server.bundle.js:1
SyntaxError: Invalid or unexpected token
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1086:15)
at Module._compile (node:internal/modules/cjs/loader:1121:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1220:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
[Info  - 09:48:41] Connection to server got closed. Server will restart.
[Error - 09:48:41] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Pylance client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Restarting server failed
Message: Pending response rejected since connection got disposed
Code: -32097
c:\Users\MM.vscode\extensions\ms-python.vscode-pylance-2022.10.10\dist\server.bundle.js:1
SyntaxError: Invalid or unexpected token
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1086:15)
at Module._compile (node:internal/modules/cjs/loader:1121:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1220:10)
at Module.load (node:internal/modules/cjs/loader:1035:32)
at Module._load (node:internal/modules/cjs/loader:876:12)
at c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47
[Error - 09:48:41] The Pylance server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 09:48:41] Server initialization failed.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Pylance client: couldn't create connection to server.
Message: Pending response rejected since connection got disposed
Code: -32097
[Error - 09:48:41] Restarting server failed
Message: Pending response rejected since connection got disposed
Code: -32097
Extension version: 2022.10.10
VS Code version: Code 1.72.0 (64bbfbf67ada9953918d72e1df2f4d8e537d340e, 2022-10-04T23:20:39.912Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i9-12900H (20 x 2918)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.67GB (21.00GB free)

Process Argv
--crash-reporter-id e5ced29c-af9c-457d-ad18-dd5b91e83f73

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903
vscccc:30566498
pyindex848cf:30577861
fc301958:30573243

pylance package is corrupted.


⚠ Bofrost.at has degraded performance

In 6b9436c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 816 ms

Resolved: Bofrost.at performance has improved in 03a2e3a.


Load different models command on windows

Really love the repo here and the approach you're taking.  I'm trying to get it to work and found one suggestion for your instructions.  Your command to use a different model returns an error if you try and run it on windows:
export USE_13B_MODEL=true && export USE_4BIT=true && uvicorn servers.vicuna_server:app
The export and && isn't supported.  I found that you can use the set command and format it like this:
set USE_13B_MODEL=true; set USE_4BIT=true;uvicorn servers.vicuna_server:app

Added these instructions to the README.md, thanks again.


Models in tf.keras.applications should have provision for custom naming

See #16037. The error is caused because the user cannot assign custom name to the layers from models from tf.keras.applications. I am opening this issue to rectify that.
If it is okay, I would like to open a few PRs adding a minor naming system to all the models, as in RegNets (1) (2).
/cc @qlzh727 @sushreebarsa @jvishnuvardhan @gbaned @parthsr5

PRs are more than welcome! Thanks for contributing!


fix(deps): Updating dependencies

:tada: This PR is included in version 1.1.2 :tada:
Your semantic-release bot :package::rocket:


Feel conditional expression shows "Invalid Syntax Error"

Problem you would like to solve

Feel Conditional Expression shows "Invalid Syntax Error".
Reproducible in web and desktop modeler.
See diagram github-pr-to-slack.bpmn.txt
Expected Behavior
Expression parses correctly.
Alternatives considered
No alternatives.
Additional context
This is required for the Inbound Connectors implementation ( https://github.com/camunda/product-hub/issues/174).

Depends on https://github.com/nikku/lezer-feel/issues/12.

As a workaround remove the () and the expression parses just fine.

Fixed with<EMAIL_ADDRESS>to be incorporated via upstream releases.

fixed through dependency update, testable in the latest nightly


redirects http to https traffic

This deployed ok, but it still doesn't seem to be redirecting. I'm wondering if that's because there's already a listener setup for port 80 in the console or if something else is going on there.


Create mergeSort.js

I was going to make those changes today as I ran out of time yesterday, but it looks like you already did.
Thank you for letting me contribute to this project, by the way.

Hey @jorgegonzalez, no problem! The changes were non-trivial as I had to write a deepEqual function, so I decided to do it for you, hope you don't mind!


some obstacle configurations seem to break path planning

Consider this example:
    grid_size, cell_size, domain_size = 20, 1, 1

    static_obstacles = [(0, 0), (10, 8), (10, 10), (10, 12), (12, 12), (grid_size-1, grid_size-1)]

    dynamic_obstacles = {}
    for seed in (8, 10, 16, 18):  # create dynamic obstacles
        random.seed(seed)
        x0, y0, x1, y1 = [random.randint(2, grid_size-3) for _ in (0, 1, 2, 3)]
        start, goal = (x0, y0), (x1, y1)
        planner = Planner(cell_size, domain_size, static_obstacles)
        path = planner.plan(start, goal, dynamic_obstacles)
        for step, coord in enumerate(path):
            if step not in dynamic_obstacles:
                dynamic_obstacles[step] = []
            dynamic_obstacles[step].append(coord)

    start, goal = (3, 3), (17, 17)
    planner = Planner(cell_size, domain_size, static_obstacles)
    path = planner.plan(start, goal, dynamic_obstacles, debug=True)

    print(path)

Path plan found after 43 iterations (works as expected):
[[3 3] [4 4] [5 5] [6 5] [7 6] [8 7] [8 8] [8 9] [8 10] [8 11] [7 12] [8 13] [9 14] [10 15] [11 16] [12 17] [13 17] [14 17] [15 17] [16 17] [17 17]]

Now I just remove the static obstacle at (10, 10), everything else remains the same:
    grid_size, cell_size, domain_size = 20, 1, 1

    static_obstacles = [(0, 0), (10, 8), (10, 12), (12, 12), (grid_size-1, grid_size-1)]

    dynamic_obstacles = {}
    for seed in (8, 10, 16, 18):  # create dynamic obstacles
        random.seed(seed)
        x0, y0, x1, y1 = [random.randint(2, grid_size-3) for _ in (0, 1, 2, 3)]
        start, goal = (x0, y0), (x1, y1)
        planner = Planner(cell_size, domain_size, static_obstacles)
        path = planner.plan(start, goal, dynamic_obstacles)
        for step, coord in enumerate(path):
            if step not in dynamic_obstacles:
                dynamic_obstacles[step] = []
            dynamic_obstacles[step].append(coord)

    start, goal = (3, 3), (17, 17)
    planner = Planner(cell_size, domain_size, static_obstacles)
    path = planner.plan(start, goal, dynamic_obstacles, debug=True)

    print(path)

Path plan found after 28 iterations (weird things happen at t=8):
[[3 3] [4 4] [5 5] [6 4] [7 5] [8 6] [9 6] [10 6] [11 6] [2 17] [3 17] [4 17] [5 17] [6 17] [7 17] [8 17] [9 17] [10 17] [11 17] [12 17] [13 17] [14 17] [15 17] [16 17] [17 17]]

Any ideas on this?

Python 3.8.9
scipy 1.6.2
numpy 1.20.2

I haven't looked at the code myself for a while, but I am fairly convinced that the bug is caused by:
hash() function in neighbour_table.py
There are hash collisions, in the new release (v0.8), I replaced the function:
https://github.com/GavinPHR/Space-Time-AStar/blob/28b1f96279658f62d2daad097df518430116dad6/stastar/neighbour_table.py#L30-L33
with:
@staticmethod
def hash(grid_pos: np.ndarray) -> int:
    return tuple(grid_pos)

This should fix the issue, let me know if not.

I confirm that d9cd44b64078b56bb7b2f6d7c0c1bf0b2682f571 solves the issue. Thank you for responding so quickly and solving.


Return token from hole punch and don't deregister fd

This change is

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

Don't merge this, I'm going to add the same changes to another commit.


ctx.user is undefined

Hi there, I am making use of ctx.user at my webtask code. Meanwhile seems it's empty when executed with sandboxjs and there is no way to inject such param. Is it make sense to have that included or are there any workaround?

Hi @vincentlaucy,
Sorry for the very late response to this issue. I am attempting to get us caught up and responding to all of our old tickets. This one is close to two years old. I am going to close it. If you are still having this issue, please feel free to respond and reopen it.
Thanks for using webtask!


Default configuration of ssl_ca_file is only set on Windows, but not on any other platforms

Description
Default configuration of ssl_ca_file is only set on Windows, but not on any other platforms
Related Issue
https://github.com/chef/customer-bugs/issues/102
Replication Case
Execute the recipe locally on any non-Windows platform. Contents of /tmp/env.log will be empty after the run completes.
file '/tmp/env.log' do
  content "#{Chef::Config['ssl_ca_file']}"
end

Expected Results
Both Windows and non-Windows will return a valid path, when executing the above recipe.
Actual Results:
The above recipe when executed on a Windows node, It returns C:/opscode/chef/embedded/ssl/certs/cacert.pem
When executed on Linux it returns empty (nil)

Closing based on https://github.com/chef/chef/pull/10100#discussion_r482012014


[BYOC][ACL] removed ACL 20.05 limitations

This PR removes checks for padding in according with changes in ACL 20.11 which currently does not require padded data.

@mbaret

@mbaret

Correct. Tests were restored to initial state (before padding limitations). Now each test always resulted to ACL-partitioned IR so there is no need to have this variations.

Correct. Tests were restored to initial state (before padding limitations). Now each test always resulted to ACL-partitioned IR so there is no need to have this variations.

Ping. How we can make a progress here?

Ping. How we can make a progress here?

Thanks @d-smirnov

Thanks @d-smirnov