sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Lua: writefile() "fast", Blob argument should accept Lua string
Labels: enhancement,api,vimscript,complexity:low,lua

### Problem

1. `writefile()` is not marked as `fast`
2. writefile() does not appear to accept Lua strings for the first arg (which accepts Blob type). AFAIK, we marshal Lua strings to Blobs in the API already, so I would expect this here too.
```
nvim --clean
:lua vim.fn.writefile('foo\nbar', 'foo.txt', 'b')


5108: Error executing lua Vim:E475: Invalid argument: writefile() first argument must be a List or a Blob                                                               
stack traceback:                                                                                                                                                         
        [C]: in function 'writefile'                                                                                                                                     
        [string ":lua"]:1: in main chunk  
```

### Expected behavior

1. do the above
2. create a dummy help tag at `:help vim.fs.write()` which points users to writefile().
    - update writefile() docs to show a quickstart example near the top.
Repository: vscode
Issue: font ligatures that span several textmate scopes assume the font settings of last character (last component of the composite symbol)
Labels: font-rendering,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.94.2
- OS Version: Windows 10

Steps to Reproduce:

1. Pick a font family that supports ligatures (like "Fira Code") and turn on font ligatures in settings.
2. See that characters that belong to different syntax scopes but happen to form a ligature are not colored as expected — examples below.

### Proposed solution: disallow ligatures to span across textmate scopes.

Python syntax: `]#` is a ligature in Fira Code, but `#` starts a comment.  Confusingly, `]` is also colored as comment.
![Image](https://github.com/user-attachments/assets/7e8ef464-5ff9-46bc-90fc-8e0a52d409d7)

HTML syntax: `/>` is a ligature in Fira Code, but `/` is invalid to self-close a tag.  Confusingly, `/` is not colored red to help see the error.
![Image](https://github.com/user-attachments/assets/d018a6f0-5cc2-4139-a922-245b172213a8)
Repository: ui
Issue: [feat]: Json field. A dynamic (sub) form from a json schema
Labels: area: request

### Feature description

dynamic form from json schema

### Affected component/components

form

### Additional Context

given a json schema, create a form and save the output into a json
Perhaps a simple JsonField component inside a form where the field is a json or stringified version of a json which needs to confirm a json schema. Example: a configuration field.

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Advanced paste option - “menu follows mouse cursor”
Labels: Needs-Triage

### Description of the new feature / enhancement

I love the tool and have the key stroke, macro programmed to a mouse gesture (i.e. [Strokes Plus](https://www.strokesplus.net/)). It makes generating the menu and selection of the desired option much quicker. It would be fantastic if there was an option or maybe a second key stroke assignment that caused the **Advanced Paste** menu to generate at the mouse cursor. 

### Scenario when this would be used?

When pulling the menu up, currently, via a mouse gesture, I might be in a completely different space on the screen and moving my mouse back over to the middle of the screen to find the menu and select the option I want breaks focus. Frankly, even if you don’t use mouse gestures, or assign it to a mouse button, it’s nice to have The menu pop up at the cursor of the application you’re actively in.

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: missing props in controls tab when using pnpm
Labels: bug,argtypes,pnpm,docgen

### Describe the bug

We are trying to create a story for a custom themed mui Button but are unable to get any ButtonProps from mui in the Story. 


### Reproduction link

https://codesandbox.io/p/devbox/syq2z7

### Reproduction steps

1. create nextJs project
1. install mui
2. install storybook
3. follow setup guide for mui -> https://storybook.js.org/recipes/@mui/material
4. create story for mui component 
5. enable autodocs
6. start storybook
7. -> mui component story does not show mui component propertys

### System

Storybook Environment Info:

  System:
    OS: macOS 15.0.1
    CPU: (12) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.15.0 - ~/Library/pnpm/node
    npm: 10.7.0 - ~/Library/pnpm/npm
    pnpm: 9.11.0 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Chrome: 129.0.6668.91
    Edge: 129.0.2792.89
    Safari: 18.0.1
  npmPackages:
    @storybook/addon-essentials: ^8.3.5 => 8.3.5 
    @storybook/addon-interactions: ^8.3.5 => 8.3.5 
    @storybook/addon-links: ^8.3.5 => 8.3.5 
    @storybook/addon-onboarding: ^8.3.5 => 8.3.5 
    @storybook/addon-themes: ^8.3.5 => 8.3.5 
    @storybook/blocks: ^8.3.5 => 8.3.5 
    @storybook/nextjs: ^8.3.5 => 8.3.5 
    @storybook/react: ^8.3.5 => 8.3.5 
    @storybook/test: ^8.3.5 => 8.3.5 
    eslint-plugin-storybook: ^0.9.0 => 0.9.0 
    storybook: ^8.3.5 => 8.3.5 

### Additional context

_No response_
Repository: PowerToys
Issue: Streaming a FancyZones zone over Teams or Discord as Application
Labels: Needs-Triage

### Description of the new feature / enhancement

Being able to stream a FancyZone over Teams or Discord as an application. This feature would allow users to choose and stream only a specific portion of their monitor, improving readability and focus.

### Scenario when this would be used?

In cases where users have ultrawide screens, streaming the entire screen can result in unreadable content for others in the meeting, especially those with smaller or 16:9 aspect ratio monitors. By allowing the user to stream just a specific FancyZone region, they can ensure better visibility. This is particularly helpful during meetings or presentations when users need to share only a part of their screen without losing the important details due to the smaller resolution on the receiver’s end.

### Supporting information

_No response_
Repository: deno
Issue: Suggestion: UnixSocket option for `deno serve` command
Labels: suggestion,serve

Would be more convenient if `deno serve` command could listen on UnixSocket like `Deno.serve()` method :)

For example, like this:

- `--socket <file>` or `--path <file>` ... Path to socket file.
(Which name is better?)

```sh
deno serve --socket ./server.sock ./server.ts
```
Repository: deno
Issue: Add coverage guided fuzzing into to Deno's tool kit.
Labels: cli,suggestion,testing

I really appreciate all the effort that has been put into having all tooling natively supported by Deno. The only thing that I feel is missing at this point is a built-in coverage guided fuzzing solution. Golang for example included one in their standard library a couple years ago as part of their 1.18.0 release and is something my company uses heavily. I would like to be able to write server code with Deno, and the last sticking point I have at this point is "how do I fuzz test?", so hopefully others also find this a worthwhile addition.
Repository: stable-diffusion-webui
Issue: [Bug]: OSError: Cannot find empty port in range: 7860-7860. You can specify a different port by setting the GRADIO_SERVER_PORT environment variable or passing the `server_port` parameter to `launch()`
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

OSError: Cannot find empty port in range: 7860-7860. You can specify a different port by setting the GRADIO_SERVER_PORT environment variable or passing the `server_port` parameter to `launch()`

### Steps to reproduce the problem

I encountered this error when starting Stable Diffusion WebUI.
with the arguments:
--api --listen --cors-allow-origins '*' --port=7860 --no-gradio-queue --skip-torch-cuda-test --nowebui.


### What should have happened?

If I restart the Stable Diffusion WebUI, it works fine. However, since it's currently running in a production environment, I can't keep restarting it like that. Can you tell me why?

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

I am running on an EC2 Linux environment.

### Console logs

```Shell
OSError: Cannot find empty port in range: 7860-7860. You can specify a different port by setting the GRADIO_SERVER_PORT environment variable or passing the `server_port` parameter to `launch()`
```


### Additional information

_No response_
Repository: kubernetes
Issue: feature(kubectl): add renewTime field when using kubectl get lease -owide
Labels: sig/scalability,kind/feature,sig/cli,needs-triage

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:
add renew field when using kubectl get lease -owide
like this
```go
NAMESPACE         NAME                        HOLDER                       AGE    RENEWTIME                    
kube-node-lease   cluster1-control-plane      cluster1-control-plane       11h    2006-01-02 15:04:05
kube-node-lease   cluster1-worker             cluster1-worker              11h    2006-01-02 15:04:05
```

**Why is this needed**:
We use the Lease resource object in the cluster. When SREs troubleshoot issues, they need to quickly check if the leases have been updated. Using -owide would make it easier to view multiple lease objects for updates.
According to the [comment](https://github.com/kubernetes/kubernetes/pull/128004#discussion_r1797118321), we should use issue tracking and refer to the suggestions of sig-scalability
Repository: tauri
Issue: [docs] There is a problem with Window Customization mentioned in the v2 document
Labels: type: documentation

Document link: https://v2.tauri.app/plugin/window-customization/
```
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "main-capability",
  "description": "Capability for the main window",
  "windows": ["main"],
  "permissions": ["core:window:default", "core:window:allow-start-dragging"]
}
```
Adding permissions has no effect
![image](https://github.com/user-attachments/assets/3746ccd0-6825-4bd8-9d2b-653900d32a78)

Including core:window:allow-minimize, etc., all have the same problem.

The configuration in tauri.conf.json is as follows: It will take effect. I don't quite understand

![image](https://github.com/user-attachments/assets/fbd10602-84df-48d3-bf5d-83a77601c333)
Repository: react-native
Issue: In native code, there is no way to determine unset `selected` vs `selected: false`
Labels: Issue: Author Provided Repro,p: Microsoft,Partner

### Description

From the JS, the developer has the choice to specify the `accessibilityState` prop. Then, they can specify any subset of 'busy', 'expanded', 'selected', 'disabled', and 'checked'. 

In the JS `selected' can be undefined or a boolean value. However, once the data is passed to the native code, accessibilityState->selected always takes a boolean value. There is no way to determine in the native code if the user has not set the 'selected' state (i.e. the control does not have selectable behavior) or if they have set 'selected' to false (i.e. the control does have selectable behavior but it is not selected)

Could we change the 'selected' value in the accessibilityState to be an std::optional, so the 'undefined' state of `selected` could be preserved on the native side? This change is needed to implement correct accessibility behavior on Windows.

### Steps to reproduce

Set a control to have accessibilityState={{}} and accessibilityState={{selected: false}}. Both show the same data for props->accessibilityState

### React Native Version

nightly

### Affected Platforms

Other (please specify)

### Output of `npx react-native info`

```text
N/A
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://snack.expo.dev/5HM2iIVtfaUY5z1FeHDgm

### Screenshots and Videos

_No response_
Repository: PowerToys
Issue: New+ Modified Date / Auto Select
Labels: Resolution-Fix Committed

### Description of the new feature / enhancement

Files created using a template should change the modified date to today as if it was created immediately and automatically select the newly created file.

### Scenario when this would be used?

The reason is that in a long list of files, one had to then go find that file. Sorting by modified date should show that newly created file from template to the top, however, it doesn't because the modified date is the modified date of the template.

### Supporting information

_No response_
Repository: TypeScript
Issue: Allow decorated accessor properties to have a different type
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

I was pretty sure an issue already existed for this, but I couldn't find it. Hopefully opening a new issue (to maybe be closed again) will improve SEO.
 
Here is what I searched for:

- decorators change type
- decorators accessor type
- decorators change type accessor

I did find this related issue:
- https://github.com/microsoft/TypeScript/issues/52559

### ✅ 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

Allow decorator's return type, `ClassAccessorDecoratorResult` to specify a different Value-type than what is on the right-hand side of the equals.

[Here is how TS 5.6.3 handles this situation today](https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgUwB5mQYxgFQJ4YDyAZnAL5zFQQhwDkaG2AtDAcnQNwBQ3wAdjGRRiAQ0zI4AJWQBnCAFcoEgDwA1UQBsFyAHyJucI5QgQAXHA3bkPMr0wR+s+AGUYCzAGsrOizPlKqvwKIABGwvoAvIgm5nAATOQ89pqisrJwACLIIBAGxnAA9IVwACZY0KIw0GXIQtgZdMFhwnRwABSlOnDVllrdCrLIpXACcFB1Svw97ACUcIbGxXChCvDAGQBEAgBuWsClm4tGAAIK-ADuUKJgcOIS6TXOHp5w0W4vPjbcdtxsGHAAKqXa5gFQADSicHBKFQQn4pQy-kUymQKgExGEcAA6qCMKV9AB+HF44ZwCzg5KMLC4dgkFTAq43FTIwJo5rhKC6bntWYAOmqAFEAI4KLT4IjEFQciK85LEc7YYCOODnJlgnAACw2ABoSTcMFA9V83kCQczcQaIrp2osYKIoABzOoWADCqXSAEFMA95FBsg5rtUoDgHc6YCotbr9WBDbodYsHII0DA3R7ZN7fdAA5Vg67HEI4ZHtbI9ZbYxEE7M02kMz65H6c0HoP4FJoI1HS31rPoEInHM4YuHyKb7U66skjMBSO0k4WYHzPAIRgBCSLRTb3BvQTbzPsFGCa6gXOD8ZAnwVQahQdoAA0F6BpZN64VVQxGKtE0y3jygcDA1CGmwt6zDwRi-EYEzuFA0z7sY4a8hYJpwQUmh1LUxACMAMDKtM0ThnymBaJo7SHhsoHHEsJQuJ6ABigo4AAmhYAEQNU-wCHQlFGMsBQFERmiaHA4ZfJ0yCYfw2G4bM3HjJMMEdOUElSZ+GRfng-LEKYdwZOcnj8BAFzfhkXxgcYZAJpRWEwO0ezWEh-TIHusnLDR9FMSx1DsQQnEuSUfHGJqyCaIazAgF+ojOn+FzAFAAiOnAIDAI6mrwI6eRBRMhJ+QFxhQVMPRBRh1m4SYf6HpIQUhcIYURVFoz8FQohmQU+UKXZOgteQCbgbYQA).

### 📃 Motivating Example

For example, it should be possible to author this with 0 errors:
```ts
class Demo {
  @unwrap accessor num = { wrapped: 2 };
  //               ^? => number

  get usage() {
    expectTypeOf(this.num).toEqualTypeOf<number>();
  }
}
```

### 💻 Use Cases

1. Reactivity
2. Hiding complex behaviors from the user
3. Unwrapping private objects into public API (the example in the playground link)
Repository: neovim
Issue: termopen() invoked with "nvim -u" stores wrong 'channel'
Labels: bug,terminal,has:workaround,has:repro,startup

### Problem

Using the python provider during initialization, I appear to be encountering an issue with the `jobpid()` function returning the "wrong" pid for a terminal started with `termopen()`. I get that this doesn't make sense. The way I'm identifying it's the wrong pid is by examining the name of the buffer created by `termopen()`.

I've currently only tested it in a non-development environment, and I believe my distro's package manager is a version behind. I'll follow-up in a bit with a test against the most recent commit. I've also attached the output of the current version along with the results of `:checkhealth`.

[versioninfo-checkhealth.txt](https://github.com/user-attachments/files/17346093/versioninfo-checkhealth.txt)

### Steps to reproduce

Place the following script inside a file:

```
pythonx cwd = vim.eval("fnamemodify({!r}, ':~')".format(__import__('os').getcwd()))
pythonx print('work', [cwd])
pythonx cmd = '/usr/bin/python -i'
pythonx job = vim.eval("termopen({!r}, {{}})".format(cmd))
pythonx print('got', [job])
pythonx pid = vim.eval("jobpid({!s})".format(job))
pythonx print('pid', [pid])
echomsg ' '
pythonx print('expected-buffer-name', ["term://{cwd}//{pid}:{command}".format(cwd=cwd, pid=pid, command=cmd)])
echomsg ' '
echomsg 'buffer-list:'
ls!
echomsg ' '
if has('linux')
    echomsg 'process-tree:'
    let out = system('pgrep nvim | xargs -n1 -t pstree -cagplt')
    for line in split(out, "\n") | echomsg "    ".line | endfor
    echomsg ' '
endif
call input('Press <RETURN> to exit editor...')
exit
```

Run it with `nvim --clean -u whatever.vim` it should emit the current working directory, use `termopen()` to open up another terminal, output its pid, and then list the currently available buffers. The extra crap is just for emitting the process tree. Specifically in its output, the pid being returned is different from the one in the buffer name being emitted by `:ls!`.

In my environment, the output looks like:
```
work ['~/work/vim-incpy']
got ['4']
pid ['2280138']

expected-buffer-name ['term://~/work/vim-incpy//2280138:/bin/sh -i']

buffer-list:
  1 %aR  "term://~/work/vim-incpy//2280139:/bin/sh -i" line 1

...

                                                                                                                                                                                    
Press <RETURN> to exit editor...                                                                                                                                                    
```

In this output, the pid returned by `jobpid()` is 2280138, whereas the buffer name suggests 2280139.

### Expected behavior

I was expecting the pid used for the terminal buffer name to be the same as returned by `jobpid()`. However, it appears to be different.

### Nvim version (nvim -v)

0.10.1

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

no

### Operating system/version

Fedora Linux 40

### Terminal name/version

console

### $TERM environment variable

screen-256color

### Installation

system package manager
Repository: rust
Issue: `rustc_codegen_llvm` should mark more of its internal methods as `unsafe`
Labels: A-LLVM,P-low,T-compiler,C-bug

Just following up from this comment I made here: https://github.com/rust-lang/rust/issues/85532#issuecomment-2406526841

While LLVM compiled with asserts ensures that no undefined behaviour occurs when calling methods, it does not when compiled *without* asserts, and this should really be reflected in the signatures for all the various internal methods that just call out to LLVM FFI.

Right now, it's very easy to trigger UB when you're writing an intrinsic, and while it's common for C functions to have all sorts of undocumented preconditions, we should not extend this habit into Rust.

For example, `const_array` will trivially trigger UB if any of the `Value`s passed into it are not actually constant:
* https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_llvm/builder/struct.Builder.html#method.const_array
* https://llvm.org/doxygen/group__LLVMCCoreValueConstantComposite.html#ga3e37d5cc97d6e4da63f6eaa22e469075

And `extract_value` will trigger UB if the index is out of bounds for the given `Value`:
* https://doc.rust-lang.org/nightly/nightly-rustc/src/rustc_codegen_llvm/builder.rs.html#978-981
* https://llvm.org/doxygen/group__LLVMCCoreInstructionBuilder.html#ga21935fb1e744e161e726611778ac1618

Whereas something like `type_i1` is fine and will always be safe to call:
* https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_llvm/context/struct.CodegenCx.html#method.type_i1
* https://llvm.org/doxygen/group__LLVMCCoreTypeInt.html#ga390b4c486c780eed40002b07933d13df

Sure, this will "introduce" unsafe code to, for example, the intrinsics lowering, but the code was already unsafe, and this is just documenting that.

@rustbot label T-compiler
Repository: vscode
Issue: "Publish server archive" can't pass on rerun
Labels: bug,vscode-build

This build flaked, and is stuck on rerun
https://dev.azure.com/monacotools/Monaco/_build/results?buildId=298457&view=logs&j=04a1dd9d-62ef-537a-ed01-63d944c25bb6&t=54f64d10-f81f-5fb8-77f4-a469d7ec00a8&l=32

`##[error]Artifact vscode_server_darwin_arm64_archive-unsigned already exists for build 298457`

So step this should be tolerant to failure
Repository: flutter
Issue: ☂️ Google Maps for Flutter package roadmap
Labels: p: maps,package,team-ecosystem,P2,triaged-ecosystem

This umbrella issue is to track the individual features that are part of the ongoing work to improve the [Google Maps for Flutter plugin](https://pub.dev/packages/google_maps_flutter). It is a continuation of the [2023 roadmap](https://github.com/flutter/flutter/issues/131284). The features listed here are based on the most [popular feature requests](https://github.com/flutter/flutter/issues?q=is%3Aissue+is%3Aopen+label%3A%22p%3A+maps%22+sort%3Areactions-%2B1-desc) (by 👍 vote and/or comments) and a goal to provide feature parity between the Flutter plugin and the underlying SDKs:

- [x] #34657 
- [x] #26863 
- [x] #33586 
- [ ] #117907 
- [ ] #39810 
- [ ] #155526 
  - [ ] #130472 
- [ ] #27550
  - [ ] #29181
- [ ] #28493
- [ ] #146920 
- [ ] #26479 
- [ ] #41731

Beyond the features listed above, we are also triaging and fixing bugs as we go.