sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: function object parameter destructure field without default value will be ignored
Labels: Bug

### 🔎 Search Terms

js, function, parameter, destructure, required

### 🕗 Version & Regression Information

- This changed between versions 5.6 and latest nightly
- We use ts 5.5 no this issue, after upgrade this issue occur.

### ⏯ Playground Link

- [ts playground](https://www.typescriptlang.org/dev/bug-workbench/?allowJs=true&ts=5.7.0-dev.20240904#code/PTAEAEEMBtoewO4CkDOAuUAXATgVwKYBQhIEAZgJbT4B2kAtvhrplSgHQBWKx+AHgAc42TKADGcGilEBzfJgCqKfNgAK2OJWoAhAJ5KVdRqAC8oABQBvQqFC5l2I-gA0N0AgqYAFgFF6kKlNQMhhlV1sPbwA5OFZKMUhWSQBleVYaGRQgkOgwwgBfIMt8gEpTAD5Qa1tseVxHKvyAbgKWkjBwLVoGJlB-Chp2TB5CCnohESrQOUUHdU0qfD0DRx7QQrINelAAcnZgFjYdtpmV+a7lhycrN3tDHowd6F0d11KmoA)
- [stackblitz](https://stackblitz.com/edit/vitejs-vite-usm5mx
)
### 💻 Code

```js
// utils.js

export const getUserProfileByUsername = ({
  username,
  withEmail = false,
  withNotificationSettings = false,
} = {}) => {
  return {};
};
```

```ts
// main.ts
import { getUserProfileByUsername } from './utils';

getUserProfileByUsername({
  username: 'ly',
});
```


### 🙁 Actual behavior

```node
src/main.ts:4:3 - error TS2353: Object literal may only specify known properties, and 'username' does not exist in type '{ withEmail?: boolean | undefined; withNotificationSettings?: boolean | undefined; }'.

4   username: 'ly',
    ~~~~~~~~


Found 1 error in src/main.ts:4
```

### 🙂 Expected behavior

no ts validate error

### Additional information about the issue

ts 5.x not this issue, must be introduced by 5.6
Repository: svelte
Issue: Svelte 5: using `bind:this` in `$derived`
Labels: documentation

### Describe the bug

```svelte
<script lang="ts">
  let a: HTMLParagraphElement;
  let b: HTMLParagraphElement | undefined = undefined;
</script>

<p bind:this={a} bind:this={b}></p>
```

```ts
// Variable 'a' is used before being assigned.ts(2454)
const a2 = $derived(a.children);

// Property 'children' does not exist on type 'never'.ts(2339)
const b2 = $derived(b?.children);
```

```ts
// let a2: HTMLCollection
$: a2 = a.children;

// let b2: HTMLCollection | undefined
$: b2 = b?.children;
```

### Reproduction

See above.

### Logs

_No response_

### System Info

```shell
System:
  OS: macOS 14.6.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 665.30 MB / 16.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 22.8.0 - ~/.local/state/fnm_multishells/8044_1725946328522/bin/node
  npm: 10.8.2 - ~/.local/state/fnm_multishells/8044_1725946328522/bin/npm
  pnpm: 9.9.0 - ~/.local/state/fnm_multishells/8044_1725946328522/bin/pnpm
Browsers:
  Chrome: 128.0.6613.120
  Edge: 128.0.2739.67
  Safari: 17.6
npmPackages:
  svelte: 5.0.0-next.244 => 5.0.0-next.244
```


### Severity

annoyance
Repository: flutter
Issue: RPCError: getVM: (-32000) Service connection disposed
Labels: c: crash,P1,team-tool,triaged-tool

Parent issue: https://github.com/flutter/flutter/issues/153471.

Thrown by a `VMService.getVM` call from `FlutterDevice.initLogReader`.

## Stack traces (from version 3.24.2)

```
RPCError: getVM: (-32000) Service connection disposed
at VmService._call(vm_service.dart:1769)
at VmService.getVM(vm_service.dart:1245)
at FlutterDevice.initLogReader(resident_runner.dart:428)
at HotRunner.attach(run_hot.dart:266)
at <asynchronous gap>(async)
at RunCommand.runCommand(run.dart:867)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1408)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:420)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:364)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:130)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at main(executable.dart:93)
at <asynchronous gap>(async)
```

```
RPCError: getVM: (-32000) Service connection disposed
at new _OutstandingRequest(vm_service.dart:261)
at VmService._call.<anonymous closure>(vm_service.dart:1778)
at VmService._call(vm_service.dart:1790)
at VmService.getVM(vm_service.dart:1245)
at FlutterDevice.initLogReader(resident_runner.dart:428)
at HotRunner.attach(run_hot.dart:266)
at <asynchronous gap>(async)
at RunCommand.runCommand(run.dart:867)
at <asynchronous gap>(async)
at FlutterCommand.run.<anonymous closure>(flutter_command.dart:1408)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at CommandRunner.runCommand(command_runner.dart:212)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand.<anonymous closure>(flutter_command_runner.dart:420)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at FlutterCommandRunner.runCommand(flutter_command_runner.dart:364)
at <asynchronous gap>(async)
at run.<anonymous closure>.<anonymous closure>(runner.dart:130)
at <asynchronous gap>(async)
at AppContext.run.<anonymous closure>(context.dart:153)
at <asynchronous gap>(async)
at main(executable.dart:93)
at <asynchronous gap>(async)
```
Repository: vscode
Issue: ESM: restore support for ASAR
Labels: upstream,debt,electron,confirmed,ESM

For ESM we have disabled ASAR but we should investigate bringing it back.

We used to have this code to inject the lookup path:

https://github.com/microsoft/vscode/blob/789c320a1c67bb0547cdef2b8b82634bf93929a3/src/bootstrap-node.js#L210-L233

But going forward, Electron should expose a way for us to enlist a path as ASAR path so that it can internally handle this as early as possible.
Repository: flutter
Issue: RPCError: readyToResume: (-32000) Service connection disposed
Labels: P1,team-tool,triaged-tool

Parent issue: https://github.com/flutter/flutter/issues/153471

```
RPCError: readyToResume: (-32000) Service connection disposed
at new _OutstandingRequest(vm_service.dart:261)
at VmService._call.<anonymous closure>(vm_service.dart:1778)
at VmService._call(vm_service.dart:1790)
at VmService.callServiceExtension(vm_service.dart:1729)
at VmService.callMethod(vm_service.dart:1712)
at DdsExtension._callHelper(dds_service_extensions.dart:346)
at DdsExtension.readyToResume(dds_service_extensions.dart:304)
at <asynchronous gap>(async)
at IsolateManager._readyToResume(isolate_manager.dart:409)
at <asynchronous gap>(async)
at IsolateManager.readyToResumeThread(isolate_manager.dart:301)
at <asynchronous gap>(async)
at IsolateManager._handlePause(isolate_manager.dart:646)
at <asynchronous gap>(async)
at IsolateManager.handleEvent(isolate_manager.dart:202)
at <asynchronous gap>(async)
at DartDebugAdapter.handleDebugEvent(dart.dart:2473)
at <asynchronous gap>(async)
at DartDebugAdapter._withErrorHandling(dart.dart:2821)
at <asynchronous gap>(async)
```

```
RPCError: readyToResume: (-32000) Service connection disposed
at VmService._call(vm_service.dart:1769)
at VmService.callServiceExtension(vm_service.dart:1729)
at VmService.callMethod(vm_service.dart:1712)
at DdsExtension._callHelper(dds_service_extensions.dart:346)
at DdsExtension.readyToResume(dds_service_extensions.dart:304)
at <asynchronous gap>(async)
at IsolateManager._readyToResume(isolate_manager.dart:409)
at <asynchronous gap>(async)
at IsolateManager.readyToResumeThread(isolate_manager.dart:301)
at <asynchronous gap>(async)
at IsolateManager._handlePause(isolate_manager.dart:656)
at <asynchronous gap>(async)
at IsolateManager.handleEvent(isolate_manager.dart:202)
at <asynchronous gap>(async)
at DartDebugAdapter.handleDebugEvent(dart.dart:2473)
at <asynchronous gap>(async)
at DartDebugAdapter._withErrorHandling(dart.dart:2821)
at <asynchronous gap>(async)
```

```
RPCError: getIsolate: (-32000) Service connection disposed
at new _OutstandingRequest(vm_service.dart:261)
at VmService._call.<anonymous closure>(vm_service.dart:1778)
at VmService._call(vm_service.dart:1790)
at VmService.getIsolate(vm_service.dart:896)
at IsolateManager._sendLibraryDebuggables(isolate_manager.dart:1030)
at IsolateManager._configureIsolate(isolate_manager.dart:553)
at IsolateManager._handlePause(isolate_manager.dart:645)
at IsolateManager.handleEvent(isolate_manager.dart:202)
at <asynchronous gap>(async)
at DartDebugAdapter.handleDebugEvent(dart.dart:2473)
at <asynchronous gap>(async)
at DartDebugAdapter._withErrorHandling(dart.dart:2821)
at <asynchronous gap>(async)
```
Repository: flutter
Issue: RPCError: getIsolate: (-32000) Service connection disposed
Labels: c: crash,P1,team-tool,triaged-tool

On 3.24.2

```
RPCError: getIsolate: (-32000) Service connection disposed
at new _OutstandingRequest(vm_service.dart:261)
at VmService._call.<anonymous closure>(vm_service.dart:1778)
at VmService._call(vm_service.dart:1790)
at VmService.getIsolate(vm_service.dart:896)
at IsolateManager._sendLibraryDebuggables(isolate_manager.dart:1030)
at IsolateManager._configureIsolate(isolate_manager.dart:553)
at IsolateManager.registerIsolate(isolate_manager.dart:246)
at IsolateManager.handleEvent(isolate_manager.dart:189)
at DartDebugAdapter.handleIsolateEvent(dart.dart:2504)
at <asynchronous gap>(async)
at DartDebugAdapter._withErrorHandling(dart.dart:2821)
at <asynchronous gap>(async)
```
Repository: ollama
Issue: Can you specify a graphics card in the ollama deployment model?
Labels: feature request

For example, qwen2 is in CUDA_VISIBLE_DEVICE=2 and glm4 is in CUDA_VISIBLE_DEVICE=4
Repository: material-ui
Issue: [question] How to combine the two different Joy-UI themes. 
Labels: on hold,support: question,package: material-ui,package: joy-ui,support: commercial

### The problem in depth

```
const oneTheme: CssVarsThemeOptions = {
  colorSchemes: {
    light: {
      palette: {
        primary: {
          500: '#1976d2',
        },
      },
    },
  },
  components: {
    JoyButton: {
      styleOverrides: {
        root: {
          borderRadius: '8px',
        },
      },
    },
  },
};

// Second theme
const twoTheme: CssVarsThemeOptions = {
  colorSchemes: {
    light: {
      palette: {
        secondary: {
          500: '#dc004e',
        },
      },
    },
  },
  components: {
    JoyInput: {
      styleOverrides: {
        root: {
          backgroundColor: '#f0f0f0',
        },
      },
    },
  },
};

const combinedThemes = extendTheme({
    ...oneTheme,
    ...twoTheme,
    components: {
        ...oneTheme.components,
        ...twoTheme.components,
    },
} as Theme)

```

but I found that xxx.components cannot be recognized, Can you please help me solve it? I need to combine this two different theme together and also let the JoyButton and JoyInput working together as well

### Your environment

next.js v14, typescript, Joy-Ui

**Search keywords**: Joy-UI  extendTheme
**Order ID**: 97037

**Search keywords**:
Repository: next.js
Issue: Server-side request forgery (SSRF)
Labels: bug,Output (export/standalone),Instrumentation

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/next-js-forked-slktwp

### To Reproduce

When start my application, my header is visible in the browser. This is causing the below vulnerability issue

This application allows user-controlled URLs to be passed directly to HTTP client libraries.  This can result in Server-Side Request Forgery (SSRF). SSRF refers to an attack where the attacker can abuse functionality on  the server to force it to make requests to other internal systems within your  infrastructure that are not directly exposed to the internet.  This allows the attacker to access internal resources they do not have direct access to.\nSome risks of SSRF are:\n- Access and manipulation of internal databases, APIs, or administrative panels - Ability to scan internal network architecture and services - Can be used to pivot attacks into the internal network - Circumvent network segregation and firewall rules\nTo avoid this, try using hardcoded HTTP request calls or a whitelisting object to  check whether the user input is trying to access allowed resources or not.\nHere is an example: ``` var whitelist = [\n  "https://example.com", \n  "https://example.com/sample"\n]\napp.get('/ssrf/node-ssrf/axios/safe/3', function (req, res) {\n  if(whitelist.includes(req.query.url)){\n      axios.get(url, {})\n          .then(function (response) {\n              console.log(response);\n          })\n          .catch(function (response) {\n              console.log(response);  \n          })\n  }\n}); ```  For more information on SSRF see OWASP: https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html\n

### Current vs. Expected behavior

Current behavior: vulnerability scan failed because of injection of headers in the URL

Expected behavior: Vulnerability scan should pass

### Provide environment information

```bash
Operating system :Windows 11
Binaries :
Node : 20.11.1
npm : 10.2.4
Yarn : 1.22.19

Relevant packages
next : 14.2.7
eslint-config-next : 14.1.0
react :18
react-dom:18
typescript : 5
```


### Which area(s) are affected? (Select all that apply)

Instrumentation, Output (export/standalone)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), Other (Deployed)

### Additional context

Getting critical issue for this
Repository: PowerToys
Issue: Workspaces does not detect Thunderbird
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

Create workspace

### ✔️ Expected Behavior

Thunderbird to be detected.

### ❌ Actual Behavior

Thunderbird is now being incorrectly detected as Explorer (a step up from not being detected at all in 0.84.0). So when launching the workspace I get a file explorer window where Thunderbird should be.

### Other Software

Thunderbird 115.14.0
Repository: PowerToys
Issue: PowerRename not appearing in both context menus
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

_[This bug has been present for me for years but was gone in 0.84.0 - and then re-appeared in 0.84.1]_

Show PowerRename in: Standard and Extended context menu
![Skärmbild 2024-09-10 091430](https://github.com/user-attachments/assets/2854d0c7-ecb9-4326-97d6-b6fd376b03fd)
[PowerToysReport_2024-09-10-09-14-56.zip](https://github.com/user-attachments/files/16940919/PowerToysReport_2024-09-10-09-14-56.zip)


### ✔️ Expected Behavior

PowerRename should be visible in both Standard and Extended context menu.

### ❌ Actual Behavior

PowerRename is only visible in Extended context menu.

### Other Software

_No response_
Repository: opencv
Issue: Point within bounds of an image
Labels: feature,category: core

We quite often need to check if a particular point lies within the bounds of an image.
There are currently two ways to do it:

- `cv::Rect{cv::Point{0, 0}, mat.size()}.contains(point)`
- `point.x() >= 0 && point.x() < mat.cols && point.y() >= 0 && point.y() < mat.rows`

Both are cumbersome to write, error prone and cause a lot of noise for such a trivial check.

It would be obvious to add

```
bool cv::Size contains(const cv::Point& p) { return 0 <= p.x() && p.x() < width && 0 <= p.y() && p.y() < height; }
```

or maybe free functions with a shortcut to enter `cv::Mat` directly:

```
bool cv::contains(const cv::Mat&, const cv::Point&);
bool cv::contains(const cv::Size&, const cv::Point&);
```

But I don't like the name, neither image nor size "contain" a point.
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] Static CPU management policy alongside InPlacePodVerticalScaling
Labels: kind/bug,sig/node,triage/accepted

### What happened?

Container CPUset allocations not updated for Guaranteed QoS Pod ( Integer CPU limits = CPU requests, after Inplace Pod updates with Static CPU Management policy alongside InPlacePodVerticalScaling. 

Static CPU management policy is not supported with this feature, known issue ( ref: https://kubernetes.io/blog/2023/05/12/in-place-pod-resize-alpha/#known-issues )

### What did you expect to happen?

Container CPU set container allocation to be updated if accepted

### How can we reproduce it (as minimally and precisely as possible)?

From https://github.com/kubernetes/enhancements/issues/2838

Tested the changes being done as a part of KEP --> In Place update of Pod resources (https://github.com/kubernetes/enhancements/issues/1287)

Added the below kubernetes flag before building k8s locally to the hack/local_cluster_up.sh script file. (Note i had created a vm machine with 8 cpus...)

kuberneted flags :-
"--topology-manager-policy=best-effort"
"--cpu-manager-policy=static"
"--reserved-cpus=0,1"

I then created a pod with limit and cpu both assigned as 2.. the pod got successfully created. I then logged in the pod and then checked its cpu set...there it was showing cpu core 3-4 assigned to the pod.. which is fine/correct.

Now i updated the pod limit and cpu to 3 each.. the pod got successfully updated as well...However cpuset assigned to the container was not updated in this case when i logged into the pod and verified..It was same as previous...Not sure if you have checked this thing at your end ??

Thanks & Regards,
ANkit Nigam

### Anything else we need to know?

As decided in SIG Node meeting, this issue replaces https://github.com/kubernetes/enhancements/issues/2838

### Kubernetes version

<details>
Kubernetes versions with InPlacePodVerticalScaling > 1.27
</details>


### Cloud provider

<details>
Independent  of Cloud provider
</details>

### OS version

<details>
Independent of OS
</details>


### Install tools

<details>
Independent of install tools
</details>
Repository: ollama
Issue: MiniCPM3 support
Labels: model request

[MiniCPM3-4B](https://huggingface.co/openbmb/MiniCPM3-4B) is the 3rd generation of MiniCPM series. The overall performance of MiniCPM3-4B surpasses Phi-3.5-mini-Instruct and GPT-3.5-Turbo-0125, being comparable with many recent 7B~9B models.
Repository: tauri
Issue: [feat] about Tauri support for RISC-V platform
Labels: type: feature request

### Describe the problem

I am evaluating the possibility of using Tauri to build desktop applications for the RISC-V platform. I would like to know if Tauri currently supports the RISC-V architecture, and whether there are any success stories or documentation available that could help me compile Tauri applications for RISC-V?

### Describe the solution you'd like

If there is any relevant information or advice, could you please share it? Thank you!

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: godot
Issue: Unintentional code selection
Labels: bug,topic:gui

### Tested versions

v4.4.dev1.official [28a72fa43]
v3.6.stable.official [de2f0f147]

### System information

w10 64

### Issue description

Watch the video.
Place the cursor at the top or in an area that leaves code to be able to reproduce the problem.
Select the second digit of the code line.
The caret moves to the bottom line and the text on the top line is selected

v4.4.dev1.official [28a72fa43]

https://github.com/user-attachments/assets/c5585171-2e98-4ed9-9e29-dc350ab36100

This also happens in 3.6 stable in a different way.
In 3.6 stable, select the area where breakpoints are created.
With the click held down, drag a little.

v3.6.stable.official [de2f0f147]

https://github.com/user-attachments/assets/33a8a367-354f-4c8f-a47f-6f98fc8b023f



### Steps to reproduce

See the videos

### Minimal reproduction project (MRP)

...
Repository: kubernetes
Issue: kube api audit log to a file
Labels: kind/bug,kind/support,sig/api-machinery,help wanted,triage/accepted

### What happened?

Hello,

Im configuring kube-apiserver to send the logs to the file so that I can see the audit events. But after adding the required details the kube-apiserver got restarted but the log was not created.  Below are the rule I have added for logging

```yaml
    - --audit-policy-file=/etc/kubernetes/audit-policy.yaml
    - --audit-log-path=/var/log/kubernetes-apiserver.log
    - --audit-log-maxsize=100
    - --audit-log-maxbackup=3
    - --audit-log-format=json
```

I have added the policy as below
```yaml 
# Log all requests at the Metadata level.
apiVersion: audit.k8s.io/v1
kind: Policy
rules:
- level: Metadata
```

After that pod git restarted  but there is no log was writing into the file

kubernetes version 1.29.8

### What did you expect to happen?

It was supposed to write audit events to the file specified in the kube-apiserver.yaml file but it is not happened

### How can we reproduce it (as minimally and precisely as possible)?

To reproduce configure audit loggin with the kubernetes version 1.29.8

### Anything else we need to know?

When I tested the same configuration on 1.27.x version kubernetes  it worked.

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.29.8
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.8
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
RHEL8.8
$ uname -a
4.18.0-477.27.1.el8_8.x86_64 #1 SMP Thu Aug 31 10:29:22 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>
containerd
</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>