sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Auto complete for "real" text
Labels: feature-request,suggest

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I love the autocompletion for code, however when writing "real" text (comments, docs, a novel), suddenly I need to type every single character.

Basically I would like whatever the bing chat team uses for it's chat-box autocompletion in vscode.

See it in action:
https://github.com/microsoft/vscode/assets/46541492/d5701c89-2152-4832-a855-caac1b4d6140

Why?:

I'm not a native English speaker and for certain words I don't know the right spelling. I have often googled the spelling of words, which breaks my "flow". Right now I use "Code Spell Checker", which helps to keep track of the misspelled words. They can then be corrected in a second pass, however this is still a little awkward and sometimes I manage to misspell so thoroughly even the spell checker can't help.

Similarly would this help native speakers with dyslexia.

Also I'm just used to autocompletion/ fuzzy search everywhere, having to type whole words doesn't feel natural to me, especially when I'm fatigued.
Repository: ant-design
Issue: Calendar日历设置fullscreen为true时，默认是整个屏幕高度，fullscreen为false时，日期展示和组件高度不能调整，期望有方法支持修改组件的高度
Labels: 🐛 Bug,Inactive,unconfirmed

### Reproduction link

[https://4x.ant.design/components/calendar-cn/](https://4x.ant.design/components/calendar-cn/)

### Steps to reproduce

修改高度没有用

### What is expected?

期望可以适配高度

### What is actually happening?

现在不支持高度修改

| Environment | Info |
| --- | --- |
| antd | 4.24.12 |
| React | 16.12.0 |
| System | windows11 |
| Browser | Chrome 120.0.6099.110 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: revalidatePath with nextConfig.trailingSlash [true], not working correctly on Vercel deployment
Labels: bug

### Link to the code that reproduces this issue

https://github.com/LordLafayette/next-revalidate

### To Reproduce


1.  yarn build > yarn start
2.  Go to "/form"
3.  Check the checkbox if you want revalidatePath function to revalidate path with trailingSlash end or not
4.  Click "submit" button
5. Go to "/time"  to check the result

you can try this link > https://next-revalidate-nine.vercel.app/time/

### Current vs. Expected behavior

### Current

**nextConfig.trailingSlash : true**  

-  not revalidate Full Route Cache , Data cache or ISR

### Expected

**nextConfig.trailingSlash : true**  

- will revalidate Full Route Cache , Data cache or ISR

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

### On Local server 
with yarn build & build start ,  i have setting nextConfig.trailingSlash = true
then i want to revalidate static render with revalidatePath with trailingSlash at end , ex : revalidatePath('/time/')
the app working fine with revalidate Full Route cache or ISR

### On Vercel
run at same code at local server, but when  revalidatePath with trailing Slash at end, ex : revalidatePath('/time/') it not working.
but if i try revalidatePath('/time')  (with no trailing Slash at end)  it work correctly.

you can try this link > https://next-revalidate-nine.vercel.app/time/
Repository: flutter
Issue: [iOS][plugin] OpenGL with Texture Widget: Memory leak after unregisterTexture.
Labels: platform-ios,engine,perf: memory,has reproducible steps,P3,team-engine,triaged-engine,a: leak tracking,found in release: 3.16

### Steps to reproduce

[There is the demo.](https://github.com/xzeroplus/opengl_texture_widget_example) 

After creating and destroying multiple FlutterTexture, I found that the memory kept rising. 

(Demo provides buttons to create and destroy Texture)
![image](https://github.com/flutter/flutter/assets/26114106/e77535c8-c83c-4fe2-8034-346e2250aebc)

### Expected results

No leak.

### Actual results

 
![Pasted Graphic](https://github.com/flutter/flutter/assets/26114106/62f3e481-01a0-494c-96ef-1e60f0c71207)
![image](https://github.com/flutter/flutter/assets/26114106/03aad3e9-3487-476b-a47a-37dc27b67d2b)
![Pasted Graphic 1](https://github.com/flutter/flutter/assets/26114106/269fa288-94e0-4b2d-b91f-25ceecd59de8)

I found that FlutterDarwinContextMetalSkia textureCache retain them.

### Code sample

See Demo.

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
❯ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.6, on macOS 14.0 23A344 darwin-arm64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.85.1)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: go
Issue: proposal: x/net/netutil: export netutil.LimitListenerConn
Labels: Proposal

### Go version

go1.21.5

### What operating system and processor architecture are you using (`go env`)?

```shell
% go env
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/user/.cache/go-build'
GOENV='/home/user/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/user/gocode/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/user/gocode'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/user/gocode/src/github.com/spiffe/spire/.build/linux-x86_64/go/1.21.5'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/user/gocode/src/github.com/spiffe/spire/.build/linux-x86_64/go/1.21.5/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.5'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/user/gocode/src/github.com/spiffe/spire/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1677547490=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I was attempting to use the https://pkg.go.dev/golang.org/x/net/netutil#LimitListener to wrap the `*net.UnixListener` in [listener_posix.go](https://github.com/spiffe/spire/blob/main/pkg/common/peertracker/listener_posix.go#L11) to limit connection acceptance at a theshold caclulated as a percentage of https://pkg.go.dev/syscall#Rlimit. The `peertracker` code needs to assert the underlying `*net.UnixConn` type [here](https://github.com/spiffe/spire/blob/main/pkg/common/peertracker/uds.go#L10).

I tested out a proposed fix using a local filesystem replace directive to code with this patch:
```
% git diff -p HEAD~
diff --git a/netutil/listen.go b/netutil/listen.go
index f8b779e..5caf94e 100644
--- a/netutil/listen.go
+++ b/netutil/listen.go
@@ -65,7 +65,7 @@ func (l *limitListener) Accept() (net.Conn, error) {
                l.release()
                return nil, err
        }
-       return &limitListenerConn{Conn: c, release: l.release}, nil
+       return &LimitListenerConn{Conn: c, release: l.release}, nil
 }

 func (l *limitListener) Close() error {
@@ -74,13 +74,13 @@ func (l *limitListener) Close() error {
        return err
 }

-type limitListenerConn struct {
+type LimitListenerConn struct {
        net.Conn
        releaseOnce sync.Once
        release     func()
 }

-func (l *limitListenerConn) Close() error {
+func (l *LimitListenerConn) Close() error {
        err := l.Conn.Close()
        l.releaseOnce.Do(l.release)
        return err
```

### What did you expect to see?

I expected to be able to get at the underlying `*net.UnixConn` after wrapping with the `netutil.LimitListener`.

### What did you see instead?

The `limitListenerConn` was unexported so I couldn't assert the type of the embedded `net.Conn`.
Repository: PowerToys
Issue: TaskTray Icons - Auto Refresh
Labels: Needs-Triage

### Description of the new feature / enhancement

To detect or monitor applications that have a tasktray icon and when they are closed via task manager/cmd/powershell to update the tasktray and update/refresh the tray 

### Scenario when this would be used?

Windows doesn't auto refresh the Task Tray when you force close applications through Task Manager or via a command or when they crash. This can leave the tray cluttered with application icons that require a mouse over to refresh/update that icon.

### Supporting information

_No response_
Repository: godot
Issue: Window Unmovable After Double-Clicking to Maximize on macOS
Labels: bug,platform:macos,topic:porting

### Tested versions

    Godot Version: 4.2
    Platform: macOS 12.7.1 (21G920)

### System information

    Godot Version: 4.2     Platform: macOS 12.7.1 (21G920)

### Issue description

After double-clicking on the Godot window to fill the screen (but not entering full-screen mode), the window becomes unresponsive to movements. It seems like there is a loss of window focus or the inability to drag the window around the screen.

### Steps to reproduce

Open Godot 4.2 on macOS 12.7.1.
    Double-click on the Godot window to maximize it without entering full-screen mode.
    Attempt to move the window around the screen by dragging its title bar.

Expected Behavior:
The window should be draggable and movable around the screen after double-clicking to fill the screen.

Actual Behavior:
After double-clicking to fill the screen, the Godot window becomes unresponsive to movements, and it is not possible to drag it around.

### Minimal reproduction project (MRP)

not required project


https://github.com/godotengine/godot/assets/94618871/26296222-1df4-4c21-8b41-e543bf443820
Repository: deno
Issue: Add "debug" button for test steps in vscode
Labels: suggestion,lsp

`Deno.test` is prefixed with two actions: "Run" and "Debug", to run (with or without debugger) the specific test.

`t.step` only supports running the individual step without the debugger, by clicking on the "play" button on the line number of the `t.step` line. It would be great have a way to easily _debug_ a single step.
Repository: rust
Issue: Tracking issue for refactoring the way we represent function call ABIs
Labels: C-cleanup,T-compiler,C-tracking-issue,A-ABI

This is the issue tracking implementation of https://github.com/rust-lang/compiler-team/issues/672. Note that we do not have a final design yet; the best way to represent call ABI, and to disentangle it from the "storage kind" of a type (which is what the `Abi` type currently largely represents) is yet to be determined.

- [ ] The core need is that a Rust type must have its ABI computed in a manner that is not reimplemented for every target and every codegen backend. e.g. the traversal over types should skip `repr(transparent)` in essentially every case. Then every target architecture must be ported to it:
  - [ ] aarch64
  - [ ] arm
  - [ ] csky
  - [ ] loongarch
  - [ ] loongarch64
  - [ ] mips
  - [ ] mips64
  - [ ] powerpc
  - [ ] powerpc64
  - [ ] riscv32
  - [ ] riscv64
  - [ ] sparc
  - [ ] sparc64
  - [ ] x86
  - [ ] x86_64
- [ ] layout.abi is not about actual ABI, but only about IR codegen: handling the types as SSA values versus handling them as memory locations.
    - [x] Rename it https://github.com/rust-lang/rust/pull/132246
    - [ ] and decouple it from actual ABI handling

See in particular [this comment](https://github.com/rust-lang/compiler-team/issues/672#issuecomment-1751624436).

## Implementation history

- @workingjubilee: the first few PRs are just going to be moving stuff around so that we can actually co-locate as much of the ABI code as possible:
    - https://github.com/rust-lang/rust/pull/131424
    - https://github.com/rust-lang/rust/pull/131473
    - https://github.com/rust-lang/rust/pull/132246
    - https://github.com/rust-lang/rust/pull/132385
Repository: ollama
Issue: shell autocompletion
Labels: feature request

hi, I would like to add shell autocompletion for ollama to my linux distribution. 
I dont know go but the cli parser seems to be using https://github.com/spf13/cobra, the same as github CLI `gh`.
The nix package generates the autocompletion like this:
https://github.com/teto/nixpkgs/blob/dbaa028d61848fda534a04ce21459b722f0bca81/pkgs/applications/version-management/gh/default.nix#L30
so I tried `ollama completion -s zsh`  hoping it was not shown by `ollama --help` because hidden but that failed.
Is there a way to generate those files currently and if yes, how, if not, could you add such a subcommand please ? makes writing commands on the prompt easier.
Repository: go
Issue: encoding/json: better error message for invalid use of ,string struct tag, trying to unmarshal unquoted value into bool
Labels: NeedsInvestigation

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21.5 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/andig/Library/Caches/go-build'
GOENV='/Users/andig/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/andig/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/andig/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.21.5/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.21.5/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.5'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/andig/htdocs/evcc/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/sv/rs_453y57xj86xsbz3kw1mbc0000gn/T/go-build4140977264=/tmp/go-build -gno-record-gcc-switches -fno-common'
GOROOT/bin/go version: go version go1.21.5 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.21.5
uname -v: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:34 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8103
ProductName:		macOS
ProductVersion:		14.2
BuildVersion:		23C64
lldb --version: lldb-1500.0.200.58
Apple Swift version 5.9.2 (swiftlang-5.9.2.2.56 clang-1500.1.0.2.5)
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

Unmarshal json containing mixed quotes and unquoted values (upstream- cannot be changed):

```go
ClimateStatus struct {
	PreClimateActive bool `json:"preClimateActive"` // false,
	Defrost          bool `json:"defrost,string"`   // "false",
}
```


### What did you expect to see?

Error message should include the field this error happens on. There could potentially be more error cases that could benefit from more context.

### What did you see instead?

Field name omitted- making it trial&error to identify the culprit in a bigger struct.
Repository: PowerToys
Issue: Paste as Plain Text: Not working with hidden font effect in MS Word
Labels: Issue-Bug,Needs-Triage,Product-Advanced Paste

### Microsoft PowerToys version

0.76.2

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Paste as Plain Text

### Steps to reproduce

Open Word
Show everything using the CTRL+*
Add a test phrase and go change the property of this font and select "hidden" or "Masqué in french". 
Select the text with a hidden font and then try to copy as plain text in notepad. 
Nothing happen. 


![Hidden hont](https://github.com/microsoft/PowerToys/assets/94852880/8c1d5ae3-52c7-4fbe-8795-d98d87f89107)

### ✔️ Expected Behavior

When I copy a text using a "hidden font" from Microsoft Word and I try to paste this as plain text nothing is happening. 

### ❌ Actual Behavior

I think the text should be paste without the "hidden" feature and be copy anywhere as plain text.

### Other Software

_No response_
Repository: tensorflow
Issue: No tensorflow-cpu meta package
Labels: stat:awaiting tensorflower,type:feature,type:build/install,TF2.14

### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.14 (latest)

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

The tensorflow-cpu package is for cpu only but has only x86 support. Then there is for example tensorflow-cpu-aws that has aarch64 support. It would be good to have a tensorflow-cpu meta package that could support all platforms.
This could for example solve the following issue: https://github.com/tensorflow/tflite-micro/issues/2367


### Standalone code to reproduce the issue

```shell
There is no tensorflow-cpu meta package.
```


### Relevant log output

_No response_
Repository: transformers
Issue: Verify interpolation of image processors
Labels: Good First Issue

### Feature request

As pointed out in https://github.com/huggingface/transformers/pull/27742, some image processors might need a correction on the default interpolation method being used (resampling in Pillow). We could check this on a per-model basis.

### Motivation

Interpolation methods have a slight (often minimal) impact on performance. However it would be great to verify this on a per-model basis.

e.g. [ViT](https://github.com/huggingface/transformers/blob/main/src/transformers/models/vit/image_processing_vit.py#L52)'s image processor defaults to BILINEAR but should use BICUBIC as seen [here](https://github.com/huggingface/pytorch-image-models/blob/main/timm/models/vision_transformer.py#L1062). We can update the default values of the image processors, but can't update the configs on the hub as this would break people's fine-tuned models.

### Your contribution

I could work on this, but this seems like a good first issue for first contributors.

To be checked (by comparing against original implementation):

- [ ] beit
- [ ] bit
- [ ] clip
- [ ] convnext
- [ ] convnextv2
- [ ] cvt
- [ ] data2vec-vision
- [ ] deit
- [ ] dinat
- [ ] dinov2
- [ ] efficientformer
- [ ] efficientnet
- [ ] focalnet
- [ ] imagegpt
- [ ] levit
- [ ] mobilenet_v1
- [ ] mobilenet_v2
- [ ] mobilevit
- [ ] mobilevitv2
- [ ] nat
- [ ] perceiver
- [ ] poolformer
- [ ] pvt
- [ ] regnet
- [ ] resnet
- [ ] segformer
- [ ] siglip
- [ ] swiftformer
- [ ] swin
- [ ] swinv2
- [ ] van
- [ ] vit
- [ ] vit_hybrid
- [ ] vit_msn
Repository: next.js
Issue: Build fails during deployment on Vercel with error `Type error: 'Component' cannot be used as a JSX component.`
Labels: bug

### Link to the code that reproduces this issue

https://github.com/moyscode/playzone/tree/main

### To Reproduce

I have the site "https://vercel.com/moyscode/playzone" deployed on Vercel. This deployment was about 6monhts back & the deployment went just fine.
Now, I am making some style changes & the deployment is failing with the error `Type error: 'Component' cannot be used as a JSX component.`
The file that is causing the issue is "./src/pages/_app.tsx:16:10" . However, I have not changed this file at all in the recent commit!

You can try to deploy the above repo & the error will re-appear

### Current vs. Expected behavior

Build should not fail. `npm run build` does not throw this error on my machine.
![image](https://github.com/vercel/next.js/assets/109787441/7629b7d3-c3be-42ae-b15e-e8cfcbb9c936)


### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
My `Package.json` is as below. On my machine `npm run dev` works just fine!

{
  "name": "playzone",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@tanstack/react-table": "^8.7.9",
    "@types/node": "18.14.2",
    "@types/react": "18.0.28",
    "@types/react-dom": "18.0.11",
    "eslint": "8.35.0",
    "eslint-config-next": "13.2.1",
    "firebase": "^9.22.2",
    "next": "13.2.1",
    "pg-promise": "^11.4.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "typescript": "4.9.5"
  }
}
```
```


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

Not sure

### Additional context

_No response_
Repository: next.js
Issue: Why in App Router mode project initalization can get wrong
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:59:33 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8112
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.11.0
Relevant Packages:
  next: 14.0.5-canary.22
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
```


### Which example does this report relate to?

no

### What browser are you using? (if relevant)

chrome

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

when I try to initialize a new nextJs project in app router mode. I start `npx next dev`. I opened the browser and saw the 404 page for the first time, because the cli didn't create the correct file struct(missed the 'Home' folder）.

### Expected Behavior

Can someone tell me why that happened?

### To Reproduce

`npx create-next-app@latest`
`npx next dev`