sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: code fence indentation inside JSDoc is removed
Labels: Bug,Help Wanted

### 🔎 Search Terms

github typescript code fence indentation

### 🕗 Version & Regression Information

- This is a crash
- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because ___time____


### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/PQKhCgAIUgBBbAlgD0QO0gWkgFQPIAiek8AhgNYCmkALgBaIDOcSqGNpA5pACYD2kRn3iV66bulp1q-AMaMAdFBixZAG1KNmAZVEcARmurYcDZus3MADgCc+AN0Q9KzUoMTwrRyAANGogAoASh8SUTo+HilSGkhZUgx9agBXfx5lWgF-WPhktRpEL2pbPitKGwKXSD4AM0gEyHRGDjRZahjq1soFSF1qP0CQsPpIjOdGWRtCgr40JWgM0yY4jS1G1xIUdB6AVX9G2LVEKkE+AC5lDJ9rgCtGDIs1gFkATwBhVeZKZBpKNB4dHpSIZKMFIABvDKQSDAYCQBQIjIAXyu10u0GqNnRMGuPjuD0+kFeH0skG+v3+gJoBiMAW0wkoACFNJQSVoghCoTC4Qj5jAURjccpgOBHlSadRwUigA

### 💻 Code

```ts
/**
 * @mixin - TODO make this @mixin tag do something in the docs.
 * @class Settable - This class provides a simple `set()` method that can be used
 * to set multiple properties of an instance at once. See `set()` method
 * description.
 *
 * This class is a mixin. Use it like so:
 *
 * ```js
 * class MyClass extends Settable() {
 *   // ...
 * }
 * ```
 *
 * or
 *
 * ```js
 * class MyClass extends Settable(SomeBaseClass) {
 *   // ...
 * }
 * ```
 */
class Settable {}
```


### 🙁 Actual behavior

<img width="672" alt="Screenshot 2023-11-28 at 10 12 36 PM" src="https://github.com/microsoft/TypeScript/assets/297678/42466cda-0715-4f83-ab27-3363268c2133">


### 🙂 Expected behavior

Expect the `// ...` to be properly indented.

### Additional information about the issue

Here's [another example](https://www.typescriptlang.org/play?#code/PQKhCgAIUgBBjANgQwM6sgUQGbYKbwAu2AropALRQTSQAGAtgJYAeTAdnddZAMIBOeZITyQAygHtETACYA6AFYY8uAoQwlUHAOb1CACyao58QcLw58RABTZ2ASjqRk7GZCFbEAT0ipCEgAdIAzwGHmREcgAjH3gI6XZdOgMjOT9AyzVUa0c5blpMFmQGAMQ8AC58mDoapR4mEol+QkgAbzwyhjx2QgAaLFUiUkQAX0hsfgkGSAByRBIumarIQGMCWA7Q7sJrGYYvCg2unpn7HiQ0DABZL0xOrfcWEVcMTKGyawAJABVLgBlbzY9extHiQVawYSEfhMKIkETjCQSSAAXkgACJsIi0aDwZDobD4VFkPwUeiifxsdAcfAJOx2Go8DJePEifAANY5EG0MFg4DASC-CRJTESJwuNx0cli9g+QgNUR4JghEkSbDBfShSDwfQubR4PLcnkpYymIQiV7bTnIgB8XJgPJ5NPYqCk+sQQp2Iv65PKM36xrkXvVqXJp0NYJGYZo9p5fIFQsgtO89ClzhlwXlkCVWp1iTwxhxYIDpvMFusVttrULjtpLrKcnd2h2Pr9weMoerkZxI2WYJkRid9KIjOZkVZHOBVfDkDjYn8QSiEgMibVIXcg3UBpjRcMxnSAQt2SjPJ7tFP1Rq1GA4DwLACTRapHYRCYtIGVmI70nIyAA).

<img width="550" alt="Screenshot 2023-11-28 at 10 15 31 PM" src="https://github.com/microsoft/TypeScript/assets/297678/92dcb1f6-ad78-4c9e-99ef-d7d6358cc279">


Note that example is using the trick described at https://github.com/microsoft/TypeScript/issues/47679#issuecomment-1763863693 to make decorators render "properly".
Repository: angular
Issue: After upgrade from angular 7 to 15 page rendering fails with error
Labels: area: core,core: di,state: needs more investigation,bug

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

Yes

### Description

After upgrade from angular 7 to 15 page rendering fails with error

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-xejxq3

### Please provide the exception or error you saw

```true
`RangeError: Invalid string length
    at Array.join (<anonymous>)
    at Array.toString (<anonymous>)
    at getOrCreateNodeInjectorForNode (vendor.js:239616:63)
    at initializeDirectives (vendor.js:247200:24)
    at resolveDirectives (vendor.js:247187:7)
    at elementStartFirstCreatePass (vendor.js:249740:3)
    at ɵɵelementStart (vendor.js:249774:41)
    at Module.ɵɵelement (vendor.js:249849:3)
    at PageaccruallistComponent_Template (src_ts_generated-sources_page-accrual-list_module_ts.js:91587:63)
    at executeTemplate (vendor.js:246773:5)`
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 15.2.10
Node: 14.21.1
Package Manager: npm 6.14.17
OS: win32 x64

Angular: 15.2.10
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1502.10
@angular-devkit/build-angular   15.2.10
@angular-devkit/core            15.2.10
@angular-devkit/schematics      15.2.10
@angular/cdk                    15.2.9
@schematics/angular             15.2.10
rxjs                            7.8.1
typescript                      4.9.5
```


### Anything else?

_No response_
Repository: excalidraw
Issue: Issue with Applying Hyperlinks at Text Level in Excalidraw #7357
Labels: enhancement

Hello There!,
Currently, the hyperlink functionality in Excalidraw seems to be associated with the element level. However, for a more granular and user-friendly experience, it would be immensely beneficial if hyperlinks could be applied directly at the text level.

I anticipate that allowing the application of hyperlinks at the text level would enhance the precision and flexibility of linking within the Excalidraw tool.

![image](https://github.com/excalidraw/excalidraw/assets/101344518/f2f73eb6-fada-4644-b91e-08e5c279e63d)

It helps user to be more specific and it is having more use cases when compared with
image

As we cannot add multiple links in the particular text
![image](https://github.com/excalidraw/excalidraw/assets/101344518/2e296ca9-1c52-4159-a195-c3241622931e)
Repository: godot
Issue: PanoramaSkyMaterial: image artefacts in mobile renderer
Labels: topic:rendering,documentation,topic:3d

### Godot version

v4.2.rc1.official [ad72de508]

### System information

Godot v4.2.rc1 - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 31.0.15.3699) - AMD Ryzen 5 3500X 6-Core Processor (6 Threads)

### Issue description

Currently, when I try to use panoramic sky with a mobile renderer the result picture contains a lot of artifacts. 
Moreover if you switch to a “lower quality” gl_compatibility renderer, then it will not have such artifacts. 
I've tried different settings with texture and quality but I just can't remove the artifacts from the "mobile" renderer.
Is it possible to increase quality of panoramic sky for "mobile" mode?

Panoramic texture example: https://drive.google.com/file/d/1udDa23klBzV7jXDeCELdNBWjREDsvfbx/view?usp=drive_link
Sample project: https://drive.google.com/file/d/1uALui1A1GdvKJZiOGqKyJXJ4_yXZ4YEw/view?usp=drive_link


Result screenshots (I increased the Exposure so that artefacts it is clearly visible).
1) mobile: 
![panorama_mobile_renderer](https://github.com/godotengine/godot/assets/31917975/e3321ec4-9e3a-4dd7-8d97-c6f6ceeae29b)

2) gl_compatibility
![panorama_gl_compatibility_renderer](https://github.com/godotengine/godot/assets/31917975/dcd935b3-5708-44a5-9ba2-b9d1719476da)

3) forward 
![panorama_forward_plus_renderer](https://github.com/godotengine/godot/assets/31917975/3ac642f7-b37d-4d3f-adc1-1f390aee2894)


### Steps to reproduce

Here is panorama image file: https://drive.google.com/file/d/1udDa23klBzV7jXDeCELdNBWjREDsvfbx/view?usp=drive_link
1) Create 3d scene with world enviroment
2) Set panorama image to PanoramSkyMaterial
3) Switch "Rendering Method" between mobile and gl_compatibility

### Minimal reproduction project

Sample project with 3d scene: https://drive.google.com/file/d/1uALui1A1GdvKJZiOGqKyJXJ4_yXZ4YEw/view?usp=drive_link
Repository: TypeScript
Issue: Cannot assign readonly statics in static blocks
Labels: Needs Investigation

### 🔍 Search Terms

"assign readonly static in static block", "assign readonly static in static constructor"

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

`static readonly` fields should be assignable within static code blocks, similar to how readonly fields are assignable in constructors. I've had a read through various issues, and those around the MR that introduced support for static blocks, but found no mention of dealing with `readonly` fields.

### 📃 Motivating Example

I'm making a variation on ringbufferjs, here, `this.headerSize = ...` shows an error without the `//@ts-expect-error`

```ts
type TypedArray =
  | Float32Array
  | Float64Array
  | Int8Array
  | Int16Array
  | Int32Array
  | BigInt64Array;
type TypedArrayConstructor =
  | Float32ArrayConstructor
  | Float64ArrayConstructor
  | Int8ArrayConstructor
  | Int16ArrayConstructor
  | Int32ArrayConstructor
  | BigInt64ArrayConstructor;

export default class LiveRingBuffer {
  private static readonly headerSize: number;

  static {
    const writePtrWidth = Uint32Array.BYTES_PER_ELEMENT;
    const readPtrWidth = Uint32Array.BYTES_PER_ELEMENT;
    const lapPtrWidth = Uint32Array.BYTES_PER_ELEMENT;
    //@ts-expect-error
    this.headerSize = writePtrWidth + readPtrWidth + lapPtrWidth;
  }

  static getStorageForCapacity(
    capacity: number,
    type: TypedArrayConstructor,
  ): SharedArrayBuffer {
    if (!type.BYTES_PER_ELEMENT) {
      throw TypeError('Pass in a ArrayBuffer subclass');
    }
    const storageWidth = (capacity + 1) * type.BYTES_PER_ELEMENT;
    const alignedHeaderWidth =
      Math.ceil(this.headerSize / type.BYTES_PER_ELEMENT) *
      type.BYTES_PER_ELEMENT;

    const bytes = alignedHeaderWidth + storageWidth;
    return new SharedArrayBuffer(bytes);
  }

  // ...
}
```

### 💻 Use Cases

1. What do you want to use this for?
    See "Motivating Example"
2. What shortcomings exist with current approaches?
    Current approach suppresses readonly error; alternative is to remove the `readonly` keyword, also not ideal since it really is readonly/const
3. What workarounds are you using in the meantime?
    `//@ts-expect-error` hides the error and emits the desired code.
Repository: ant-design
Issue: 时间选择器 滚动条高度计算错误
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://ant.design/components/time-picker-cn](https://ant.design/components/time-picker-cn)

### Steps to reproduce

时间选择到底下，应该贴底展示，不是空出一大片空白

### What is expected?

时间选择到底下，应该贴底展示，不是空出一大片空白

### What is actually happening?

时间选择到底下，没有贴底展示，空出一大片空白

| Environment | Info |
| --- | --- |
| antd | 5.11.5 |
| React | 18 |
| System | window |
| Browser | 谷歌 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: kubernetes
Issue: The kubelet may print sensitive container information if the container environment variables contain encrypted sensitive information.
Labels: kind/bug,sig/node,needs-triage

### What happened?

When I set the log level of kubelet to 4.And the container environment variable configuration contains encrypted sensitive information.After starting the container, The kubelet prints all sensitive environment variable information.

In kubernetes 1.25，the code is located in method SyncPod of file kuberuntime_manager.go.
`klog.V(4).InfoS("Creating container in pod", "containerType", typeName, "container", spec.container, "pod", klog.KObj(pod))`

### What did you expect to happen?

Environment variable information should not be printed in kubelet logs because it may contain sensitive data.

### How can we reproduce it (as minimally and precisely as possible)?

Set the log level of kubelet to 4. Add sensitive information to the environment variables of the container. Start the container. Searching for 'Creating container in pod' in the log file of kubelet.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: godot
Issue: Format String Grabs Latest Local String Variable when Erroring out due to insufficient arguments.
Labels: bug,topic:gdscript

### Godot version

v4.2.rc2.official [1ba920fad]

### System information

Windows 10

### Issue description

When doing a format string like so "string % [arg1, arg2]" if you have a variable local to the function that is either equal to "str([something])" or a valid format string with it's arguments in an array ex. "testing %s" % ["stuff"] it will steal the most recent one for the erroring format string.

Small note, it seems to grab the str variable (the stolen one that comes first) without any of the logic applied to it.  Ex. "str("stuff and things").uri_encode() gets stolen as just "stuff and things" rather than applying the uri_encode.

### Steps to reproduce

- Create a function
- Add a variable that equals to "str()" or a variable equal to a valid Format String with arguments wrapped in an Array
- Set a variable after the above String Variable to a Format String with insufficient arguments with the arguments wrapped in an Array (ex. "stuff %s %s" % ["things"]
- Check the second variable, print, breakpoint whatever.

Repro Project Steps:
- Run Main Scene
- Click Scene (just runs the function
- Check output
- Repeat with different lines in Format_string_test.test_format uncommented/or commented. 

### Minimal reproduction project

[Format String Access Bug.zip](https://github.com/godotengine/godot/files/13498104/Format.String.Access.Bug.zip)
Repository: neovim
Issue: diagnostics displayed on wrong line after "gq" formatting
Labels: bug,marks,diagnostic

### Problem

I noticed that after formatting by `gqq` some line, diagnostic entries (not related to code style, e.g. _unused variable_) from lua-ls attached to it disappear (or virtual text moves). 

Before `gqq`:
![image](https://github.com/neovim/neovim/assets/11404453/bce571ae-4900-44dc-8572-5e65b8631cf1)
After:
![image](https://github.com/neovim/neovim/assets/11404453/0d6ce631-c17d-4e9f-a44e-490648a97af8)

Please notice that the result of `vim.diagnostic.get(0)` has not changed. 

### Steps to reproduce

diag.lua:
```lua
local thisInitFile = debug.getinfo(1).source:match('@?(.*)')
local configDir = vim.fs.dirname(thisInitFile)

vim.env['XDG_CONFIG_HOME'] = configDir
vim.env['XDG_DATA_HOME'] = vim.fs.joinpath(configDir, '.xdg/data')
vim.env['XDG_STATE_HOME'] = vim.fs.joinpath(configDir, '.xdg/state')
vim.env['XDG_CACHE_HOME'] = vim.fs.joinpath(configDir, '.xdg/cache')
local stdPathConfig = vim.fn.stdpath('config')

vim.opt.runtimepath:prepend(stdPathConfig)
vim.opt.packpath:prepend(stdPathConfig)

local x -- type gqq here
vim.api.nvim_create_autocmd('FileType', {
  pattern = {'lua'},
  callback = function (args)
    vim.treesitter.start(args.buf, 'lua')
    vim.lsp.start({
      name = 'luals',
      cmd = {'lua-language-server'},
      root_dir = vim.uv.cwd(),
      single_file_support = true,
      log_level = vim.lsp.protocol.MessageType.Warning,
    })
  end,
})
```
```sh
nvim --clean -u diag.lua diag.lua
```

### Expected behavior

Diagnostic entries are shown correctly after formatting. 

### Neovim version (nvim -v)

NVIM v0.10.0-dev-1698+g640680ccc

### Vim (not Nvim) behaves the same?

-

### Operating system/version

Debian Sid

### Terminal name/version

kitty + tmux

### $TERM environment variable

tmux-256color

### Installation

from repo
Repository: react
Issue: [DevTools Feature Request]: Full support for RSC server elements (component tree, props, inspect)
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

All Next.js 13/14 Apps

### Repro steps

RSC elements created on the server and sent over the network are not supported by React DevTools. Both `_debugOwner` and `_debugSource` are `null`, which breaks the component tree, props view, and the inspect feature.

According to this thread, https://twitter.com/alvarlagerlof/status/1716927277295120429, it's been considered, but no concrete plans yet.

From the official [server components RFC](https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md#open-areas-of-research):

![image](https://github.com/facebook/react/assets/15837712/62cd61f3-38b8-481d-b47c-308ff2a82bc5)


### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: TypeScript
Issue: MediaStream API should support pan, zoom and tilt
Labels: Bug,Help Wanted,Domain: lib.d.ts

### ⚙ Compilation target

ES2022

### ⚙ Library

TypeScript 5.3.2

### Missing / Incorrect Definition

The interfaces MediaTrackCapabilities and MediaTrackConstraints (MediaTrackConstraintSet) should include the zoom, tilt and pan properties, so control of the camera is accessible via TypeScript. 

In pure JavaScript, this works: https://googlechrome.github.io/samples/image-capture/update-camera-zoom.html

In TypeScript, the necessary properties for camera control are unavailable: https://github.com/microsoft/TypeScript/blob/main/src/lib/dom.generated.d.ts (e.g. search for "zoom" -> no results).

Context: a use case where (optical) zoom is required is where a user needs to scan a very tiny QR code (1 cm2). If you move your phone too far away, it's too small to scan; if you move too close, the camera cannot focus on it. A solution here is to move your phone further away but allow the user to zoom which would 1. enable the camera to focus and 2. make the QR code big enough in screen space. I noticed that on my phone, the native photo app zooms by default, no troubles scanning the QR code here.

### Sample Code

```TypeScript
interface MediaTrackCapabilities {
    aspectRatio?: DoubleRange;
    autoGainControl?: boolean[];
    channelCount?: ULongRange;
    deviceId?: string;
    displaySurface?: string;
    echoCancellation?: boolean[];
    facingMode?: string[];
    frameRate?: DoubleRange;
    groupId?: string;
    height?: ULongRange;
    noiseSuppression?: boolean[];
    sampleRate?: ULongRange;
    sampleSize?: ULongRange;
    width?: ULongRange;
}

interface MediaTrackConstraintSet {
    aspectRatio?: ConstrainDouble;
    autoGainControl?: ConstrainBoolean;
    channelCount?: ConstrainULong;
    deviceId?: ConstrainDOMString;
    displaySurface?: ConstrainDOMString;
    echoCancellation?: ConstrainBoolean;
    facingMode?: ConstrainDOMString;
    frameRate?: ConstrainDouble;
    groupId?: ConstrainDOMString;
    height?: ConstrainULong;
    noiseSuppression?: ConstrainBoolean;
    sampleRate?: ConstrainULong;
    sampleSize?: ConstrainULong;
    width?: ConstrainULong;
}

interface MediaTrackConstraints extends MediaTrackConstraintSet {
    advanced?: MediaTrackConstraintSet[];
}
```


### Documentation Link

_No response_
Repository: flutter
Issue: Improved allowProvisioningUpdates & auth key support 
Labels: c: new feature,platform-ios,tool,t: xcode,c: proposal,P2,team-ios,triaged-ios

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

When running `flutter build ipa`, the `-allowProvisioningUpdates` flag is applied at the _export_ stage, but I think that it isn't being applied when building the initial archive.

I have a project set up for automatic signing, which fails a `flutter build ipa` because there's no signing certificate: ```
Error (Xcode): No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID
"23Z8894VWP" with a private key was found.
/Users/sam/Developer/Projects/mono/client/club/ios/Runner.xcodeproj
```

It does not appear to attempt to repair/create the keys, which is what I would expect if the `-allowProvisioningUpdates` flag was supplied to xcode during the archiving phase.

If I perform a manual xcodebuild and supply that flag (and also an app store api key), it works: ```
    xcodebuild archive \
      -workspace "client/$APP_NAME/ios/Runner.xcworkspace" \
      -scheme Runner \
      -destination generic/platform=iOS \
      -archivePath "$ARCHIVE_NAME" \
      -allowProvisioningUpdates \
      -authenticationKeyID $AUTH_KEY \
      -authenticationKeyIssuerID $AUTH_ISSUER \
      -authenticationKeyPath "~/.private_keys/AuthKey_$AUTH_KEY.p8"
```

It will correctly generate the developer cert/key. Running `flutter build ipa` will subsequently succeed.

I'm not sure that using the authKey is specifically necessary here - it would probably also work without it if the user had an up to date developer signing account signed in with Xcode. Being able to supply the key is useful though.

It would be great to be able to build this behaviour into flutter, particularly for use in CI environments.

### Proposal

Two changes:
- Extend `flutter build ipa` so that authentication key arguments can be passed through to xcode build
- Extend `flutter build ipa` so that the initial archive correctly uses the `-allowProvisioningUpdates` flag

The first would be useful regardless.

The second ought to be happening now, but I believe that there may be a hole in the logic of `buildXcodeProject` which is causing the flag not to be applied in my situation. Either that, or it's the fact that the auth key arguments are required in my case -- I haven't quite figured out which.