sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: clear() is slow for maps with big capacity and small number of items
Labels: Performance,NeedsInvestigation,compiler/runtime

## The issue

The following pattern is frequently used in order to avoid excess memory allocations by re-using the map:

```go
func f() {
  m := make(map[string]int)

  for {
    addSomeItemsToMap(m)
    useMap(m)

    // clear the map for subsequent re-use
    clear(m)
  }
}
```

It has been appeared that `clear(m)` performance is proportional to the number of buckets in `m`. The number of buckets can grow significantly at `addSomeItemsToMap()`. After that the performance of `clear(m)` can slow down significantly (and forever), even if only a few items are added into the map on subsequent iterations.

See https://philpearl.github.io/post/map_clearing_and_size/ for more details.


## The solution

Go runtime must be able to switch between the algorithm, which unconditionally clears all the buckets in `m`, and the algorithm, which clears only the buckets, which contain at least a single item, depending on the ratio between the number of items in the map and the number of buckets in it. This should improve performance of `clear(m)` in the pattern above when every iteration can store widely different number of items in m.
Repository: deno
Issue: Remove usages of `winapi` and consolidate on `windows-sys`
Labels: refactor,chore

We sometimes use `winapi` and sometimes use `windows-sys`. We should consolidate on `windows-sys` since it's maintained by Microsoft and receiving updates.

That said, looks like a lot of our deps use winapi.
Repository: godot
Issue: Script button in connect a signal dialog does nothing when clicked
Labels: bug,topic:editor,usability,topic:gui

### Tested versions

Godot v4.4.dev5

### System information

Fedora Linux 40 (KDE Plasma) on Wayland - X11 display driver, Single-window

### Issue description

Pressed the Script button and thought I selected the correct node to connect to, but it does nothing so ended up connecting to another node.

https://github.com/user-attachments/assets/ce5fa21a-bf1d-434b-b4ed-9de6338e4e81



### Steps to reproduce

Open connect signal dialog and press on the script button

### Minimal reproduction project (MRP)

[signal_connect.zip](https://github.com/user-attachments/files/17963439/signal_connect.zip)
Repository: deno
Issue: Allow multiple prompters in deno_runtime crate (make PERMISSION_PROMPTER thread-local)
Labels: embedder

I'm running `deno_runtime` in multiple threads and trying to use different prompters to manage the permissions independently, but I hit a roadblock because `PERMISSION_PROMPTER` is `static`. This is an example of how I'm using `deno_runtime`: https://github.com/carloslfu/tauri-deno-example.

A solution could be using the `thread_local! {}` macro. I created [this branch](https://github.com/carloslfu/deno/commit/546afe37748fecbcf515855f60d358926a615920) with the necessary changes and will submit a PR.
Repository: transformers
Issue: Only Fine-tune the embeddings of the added special tokens
Labels: Feature request

### Feature request

Hi, I added some new special tokens to the LLMs (specifically I'm using Qwen2-VL) and then I only want to fine-tune the embedding layers of these added tokens while keeping all other parameters (and the embedding layers for other tokens) frozen. I wonder if there is a built-in way to do so instead of fine-tuning the whole embedding matrix?


### Motivation

If we want to maximumly retain the original capabilities of the model while adding new tokens for certain scenarios, this might be needed, especially when we don't have much data and do not want to alter the pretrained weights.

Another question: if we have a considerable amount of data, is it recommended to fine-tune the whole embedding matrix or only the embeddings for the added tokens?

### Your contribution

If it's a reasonable feature and not implemented yet, I'm happy to submit a PR.
Repository: ollama
Issue: There are issues with the upgrade
Labels: bug

### What is the issue?

Why is the version always 0.3.14 during each upgrade, and why can't it be upgraded to the latest version?

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.3~0.4.5
Repository: ollama
Issue: Classify tool call vs. content earlier and stream to user
Labels: feature request

https://github.com/ollama/ollama/issues/5796#issuecomment-2508374342
Repository: PowerToys
Issue: Mouse Pointer Cross Hairs. Automatic disable
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

When typing - temporarily disable the cross hairs

### Scenario when this would be used?

I find that, when I am typing, I manually have to move the mouse cross hairs out of the way.  I am aware that manual enable/disable helps but to have the hairs automatically disable while typing keys and enable when stopping would be valuable

### Supporting information

_No response_
Repository: flutter
Issue: [in_app_purchase_storekit] Comment in example/lib/main.dart may be incorrect.
Labels: platform-ios,d: examples,p: in_app_purchase,package,P2,team-ios,triaged-ios

[packages/packages/in_app_purchase/in_app_purchase_storekit/example/lib/main.dart at main · flutter/packages](https://github.com/flutter/packages/blob/main/packages/in_app_purchase/in_app_purchase_storekit/example/lib/main.dart#L17-L19)

Current:

```dart
// When using the Android plugin directly it is mandatory to register
// the plugin as default instance as part of initializing the app.
InAppPurchaseStoreKitPlatform.registerPlatform();
```

Expected:

```dart
// When using the StoreKit plugin directly it is mandatory to register
// the plugin as default instance as part of initializing the app.
InAppPurchaseStoreKitPlatform.registerPlatform();
```
Repository: ollama
Issue: Add tests for openai response logic - potentially refactor middleware
Labels: feature request
Repository: go
Issue: crypto/tls: TestFIPSCertAlgs failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "crypto/tls" && test == "TestFIPSCertAlgs"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8729882779692073953)):

    === RUN   TestFIPSCertAlgs
    panic: test timed out after 3m0s
    	running tests:
    		TestFIPSCertAlgs (2m58s)
    
    goroutine 255 gp=0x9dc67e8 m=9 mp=0x9e80808 [running]:
    panic({0x83eebe0, 0x9c28050})
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:806 +0x144 fp=0x9c54784 sp=0x9c54730 pc=0x80bacc4
    testing.(*M).startAlarm.func1()
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/testing/testing.go:2456 +0x382 fp=0x9c547f0 sp=0x9c54784 pc=0x815bd72
    ...
    runtime.gopark(0x846f384, 0x9cda4e0, 0x1b, 0xa, 0x0)
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:435 +0x10c fp=0x9d62f8c sp=0x9d62f78 pc=0x80bb16c
    runtime.gcBgMarkWorker(0x9c90b00)
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1423 +0xfd fp=0x9d62fe8 sp=0x9d62f8c pc=0x806104d
    runtime.gcBgMarkStartWorkers.gowrap1()
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1339 +0x27 fp=0x9d62ff0 sp=0x9d62fe8 pc=0x8060f37
    runtime.goexit({})
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/asm_386.s:1393 +0x1 fp=0x9d62ff4 sp=0x9d62ff0 pc=0x80c0ce1
    created by runtime.gcBgMarkStartWorkers in goroutine 25
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1339 +0x12c


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Cannot use Next.js as a transitive dep to build an application
Labels: bug,SWC,Webpack,Script (next/script)

### Link to the code that reproduces this issue

https://github.com/Ethan-Arrowood/next-issue-repro

### To Reproduce

Follow readme in https://github.com/Ethan-Arrowood/next-issue-repro

Or:

1. Generate a new nextjs app, `npx create-next-app`. Called it `my-app`
2. As a sibling to the next app created in step 1, create a new directory `next-transitive`
3. Add a package.json with the content: `{ "dependencies": { "next-app": "file:../my-app" } }`
4. cd into `next-transitive` and run `npm install --install-links` (the option is so that the file: is actually installed instead of symlinked)
5. cd into `node_modules/next-app` and try to run `npx next build` or `npm run build`. They will both fail with the following:

```
> my-app@0.1.0 build
> next build

   ▲ Next.js 15.0.3

   Creating an optimized production build ...
Failed to compile.

./app/page.js
Module parse failed: Unexpected token (6:4)
File was processed with these loaders:
 * ../next/dist/build/webpack/loaders/next-flight-loader/index.js
 * ../next/dist/build/webpack/loaders/next-swc-loader.js
You may need an additional loader to handle the result of these loaders.
| export default function Home() {
|   return (
>     <div className={styles.page}>
|       <main className={styles.main}>
|         <Image

Import trace for requested module:
./app/page.js


> Build failed because of webpack errors
```

### Current vs. Expected behavior

This behavior seems to exist for a few major versions. My assumption is that the build process is not resolving its own dependencies correctly. 

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 12
Binaries:
  Node: 20.16.0
  npm: 10.8.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: N/A
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: N/A
Next.js Config:
  output: N/A
```


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

Developer Experience, Script (next/script), SWC, Webpack

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

next build (local)

### Additional context

_No response_
Repository: godot
Issue: Entire scenes disappearing with MissingNode error
Labels: bug,topic:editor,needs testing

### Tested versions

Godot v4.3.stable

### System information

Godot v4.3.stable (77dcf97d8) - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 2700X Eight-Core Processor (16 Threads)

### Issue description

What seems like for no reason at all, random scenes in my file will completely disappear and turn to MissingNode. If it weren't for git there would be no way to get scene back. This is very bad. It happened to me twice and very far apart. Just reporting because no one has an answer to it online.

 ![Image](https://github.com/user-attachments/assets/6cb993a0-8931-4814-ad5c-031095bdaf8b)


### Steps to reproduce

I have no idea how to reproduce, it seems to be happening randomly. My project is connected to GitHub desktop and it is a larger project. 

### Minimal reproduction project (MRP)

N/A
Repository: deno
Issue: `deno task`: cannot run tsx
Labels: bug,node compat,task runner

Version: Deno 2.1.2

This is the same error as #20625, but not in the same context.

Trying to create an alias for `npx tsx --test` (to test codebase on node js) but for some reason when executed through the task runner there a weird error (see stacktrace below)
```json
{
  "tasks": {
    "test:node": "npx tsx --help"
  }
}
```
```
Task test:node npx tsx --help
tsx

Node.js runtime enhanced with esbuild for loading TypeScript & ESM

Usage:
  tsx [flags...] [script path]
  tsx <command>

Commands:
  watch        Run the script and watch for changes                                                                                                                      

Flags:
  -h, --help                     Show help                                                                                                                               
      --no-cache                 Disable caching                                                                                                                         
      --tsconfig <string>        Custom tsconfig.json path                                                                                                               
  -v, --version                  Show version                                                                                                                            

---------------------------------------------

error: unexpected argument '--require' found

  tip: to pass '--require' as a value, use '-- --require'

Usage: deno run [OPTIONS] [SCRIPT_ARG]...
```

There's a "deno run" mention so I assume there's some kind of shenanigans that alias/replace tsx.

If executed directly in bash the command works as expected
Repository: rust
Issue: Unexpected warning when doc string invokes a macro which is defined within the same module
Labels: A-resolve,A-macros,T-compiler,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

This is a follow-up of https://github.com/rust-lang/rust/issues/124535#issuecomment-2466005846. 

TLDR: it looks like https://github.com/rust-lang/rust/issues/124535 might have not been completely resolved, or at least there are some undetected edge cases in https://github.com/rust-lang/rust/pull/125741/commits/c4c7859e40efcfff640af442fb5d1fab3718d374...


### Issue Description
In the minimal reproduction ([rami3l/repro_rust_124535](https://github.com/rami3l/repro_rust_124535)), we have:

```rust
// lib.rs
macro_rules! pm_mods {
    ( $( $vis:vis $mod:ident; )+ ) => {
        $(
            $vis mod $mod;
            pub use self::$mod::$mod;
        )+
    }
}

pm_mods! {
    dnf;
}
```

```rust
// dnf.rs
#![doc = doc_self!()]

macro_rules! doc_self {
    () => {
        "The Dandified YUM."
    };
}
use doc_self; // <- Please note that the suggested fix has already been applied.

#[doc = doc_self!()]
pub fn dnf() {}
```

**I expected to see this happen**: ✅

**Instead, this happened**:

```console
> cargo check
    Checking repro_rust_124535 v0.1.0 (/path/censored)
warning: cannot find macro `doc_self` in this scope
 --> src/dnf.rs:1:10
  |
1 | #![doc = doc_self!()]
  |          ^^^^^^^^
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #124535 <https://github.com/rust-lang/rust/issues/124535>
  = help: import `macro_rules` with `use` to make it callable above its definition
  = note: `#[warn(out_of_scope_macro_calls)]` on by default

warning: `repro_rust_124535` (lib) generated 1 warning
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.06s
```

Also, it's worth noticing that after inlining the macro invocation in `lib.rs`, i.e.:

```rust
// lib.rs
mod dnf;
pub use self::dnf::dnf;
```

... the error seems gone.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1
```
Repository: PowerToys
Issue: Chinese Pinyin(拼音) search doesn't work when it corresponds to more than two characters (or 3 maybe) in PowerToys Run
Labels: Issue-Bug,Product-PowerToys Run,Area-Localization,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update, GitHub

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/65fc58a4-bf74-40de-a52f-08939e6728b1)
![Image](https://github.com/user-attachments/assets/299fdd57-3fdd-492f-a843-409f5781bcef)
![Image](https://github.com/user-attachments/assets/d9f02cb4-c388-4c7c-b1d3-da136d36ddc6)
![Image](https://github.com/user-attachments/assets/8eb5a110-2603-4039-ae6d-abaaaac4a3d5)
![Image](https://github.com/user-attachments/assets/7aed0cab-c95c-4112-8301-74bdb5108a66)
![Image](https://github.com/user-attachments/assets/c06ee60d-e4b4-4193-973b-f0e08cb617fd)
![Image](https://github.com/user-attachments/assets/a772c46e-dd2b-4cb3-9f8e-e658ab91e372)
![Image](https://github.com/user-attachments/assets/4a9dd1d7-16be-4ad5-b841-91da8f0b56f1)
![Image](https://github.com/user-attachments/assets/ca8390cd-b97b-4cea-9e34-ae3fb9447ad9)

### ✔️ Expected Behavior

baidufanyi -> `百度翻译`
bdfy -> `百度翻译`
baiduwangpan -> `百度网盘`
bdwp -> `百度网盘`
bd -> `百度翻译` and `百度网盘`
baidu -> `百度翻译` and `百度网盘`

### ❌ Actual Behavior

Work as Expected:
- [x] bd -> `百度网盘`
- [x] baidu -> `百度网盘`

Not as Expected:
- [ ] baidufanyi -> `百度翻译`
- [ ] bdfy -> `百度翻译`
- [ ] baiduwangpan -> `百度网盘`
- [ ] bdwp -> `百度网盘`
- [ ] bd -> `百度翻译`
- [ ] baidu -> `百度翻译`


### Other Software

_No response_
Repository: awesome-mac
Issue: 🎉 Add Tran
Labels: addition

### 🪩 Provide a link to the proposed addition

https://github.com/Borber/Tran

### 😳 Explain why it should be added

Tran
简洁, 快速, 划词翻译

### 📖 Additional context

跨平台

### 🧨 Issue Checklist

- [X] I have checked for other similar issues
- [X] I have explained why this change is important
- [X] I have added necessary documentation (if appropriate)
Repository: awesome-mac
Issue: 🎉 Add <Gopeed>
Labels: addition

### 🪩 Provide a link to the proposed addition

https://github.com/GopeedLab/gopeed

### 😳 Explain why it should be added

Gopeed (full name Go Speed), a high-speed downloader developed by Golang + Flutter, supports (HTTP, BitTorrent, Magnet) protocol, and supports all platforms. In addition to basic download functions, Gopeed is also a highly customizable downloader that supports implementing more features through integration with APIs or installation and development of extensions.

### 📖 Additional context

跨平台且简洁

### 🧨 Issue Checklist

- [X] I have checked for other similar issues
- [X] I have explained why this change is important
- [X] I have added necessary documentation (if appropriate)
Repository: ui
Issue: [bug]: ECONNRESET Error When Running `npx shadcn@latest add --all`
Labels: bug

### Describe the bug

Hello,

I'm encountering an issue while trying to use the `shadcn` CLI tool to add all components to my project. The command fails with an `ECONNRESET` error when attempting to fetch certain resources from https://ui.shadcn.com. Here are the details:

**What I Have Tried:**

  - Checked internet connectivity (it's stable).
  - Cleared npm cache using npm cache clean --force.
  - Updated Node.js and npm to the latest versions.
  - Tried using a different network (e.g., mobile hotspot).

**Environment:**

  - Node.js version: v22.11.0 (LTS)
  - npm version: 10.9.0
  - Operating System: Windows 11 Pro

**Additional Information:**

  - I’ve attached screenshots of the terminal errors for reference.
  - Please let me know if this is an issue with the shadcn server or if there are additional steps I should follow.

**Suggested Note for the Issue:**

> I am encountering the `ECONNRESET `error with different components each time I run the command. It seems the issue affects all components fetched via `npx shadcn@latest add --all`. This could indicate a problem with the network/resource fetching mechanism rather than any specific component.

Thank you!

**Attachments:**

![Screenshot 2024-11-30 115133](https://github.com/user-attachments/assets/783fb442-c22b-428b-b2da-3d43a212ab65)




### Affected component/components

potentially all.

### How to reproduce

1. Run the following command in the terminal: 
    ```
    npx shadcn@latest add --all
    ``` 

2. The command fails with the following error: 

    ```
    Something went wrong. Please check the error below for more details.
    request to https://ui.shadcn.com/r/styles/new-york/... failed, reason: read ECONNRESET
    ```

### Codesandbox/StackBlitz link

https://github-production-user-asset-6210df.s3.amazonaws.com/88278303/391216641-783fb442-c22b-428b-b2da-3d43a212ab65.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20241130%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20241130T062805Z&X-Amz-Expires=300&X-Amz-Signature=9212cc08d79e91503bce5c075265c51ba2d70ee4e05fb1c8e8a60f16cd228bf6&X-Amz-SignedHeaders=host

### Logs

_No response_

### System Info

```bash
Microsoft Windows 11 Pro(24H2),
Node.js v22.11.0,
npm v10.9.0,
shadcn CLI v2.1.6
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: Improve documentation of `TextField`'s `decoration` property interplay with `Theme.inputDecorationTheme`
Labels: c: new feature,framework,f: material design,d: api docs,a: quality,c: proposal,P2,team-text-input,triaged-text-input

### Use case

The [current documentation of flutter's `TextField`](https://api.flutter.dev/flutter/material/TextField-class.html) contains no mention of the fact that any explicit `decoration` is merged with whatever additional decorations are defined in the surrounding theme, making it unnecessarily difficult to debug why e.g. trying to remove a field's border (if defined in the theme) is impossible without wrapping the widget with an additional `Theme` containing explicit `InputBorder.none` values.

### Proposal

As a bare minimum, some form of notice should be added to the `decoration` property informing about the potential need for inserting an applied-property-clearing `Theme` wrapper surrounding the widget.

Ideally though, users should have a less verbose way of specifying whether to merge or fully replace the active `InputDecorationTheme` either when creating, or when applying an `InputDecoration`, e.g. with a `bool? mergeWithTheme` on all constructors, while applying more intuitive defaults (looking at [the `InputDecoration.collapsed()` named constructor](https://api.flutter.dev/flutter/material/InputDecoration/InputDecoration.collapsed.html), that would be a `false` rather than a `true`)

EDIT: Note, I got started creating a small example on https://dartpad.dev to illustrate the issue, but writing code containing a textfield over there is an absolute nightmare once "Run" is executed due to the textfield acting as a cursor magnet making further code edits an incredibly frustrating experience :(