sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for release notes of #133820: Stabilize `derive(CoercePointee)`
Labels: T-lang,relnotes,needs-triage,F-derive_coerce_pointee,relnotes-tracking-issue


This issue tracks the release notes text for #133820.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Stabilize `derive(CoercePointee)`](https://github.com/rust-lang/rust/pull/133820)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @dingxiangfei2009, @joboet -- origin issue/PR authors and assignees for starting to draft text
Repository: godot
Issue: class_name doc comments edited with external editor don't update until editor restart
Labels: bug,topic:gdscript,topic:editor,needs testing

### Tested versions

Reproducible in v4.3.stable.official [77dcf97d8]

Class doc comments were added in d1231be1c8f8f2c16fd1047adcd3c7f997a07c1f, but I haven't checked if it occurred in that build.

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; 32.0.15.6590) - Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 Threads)

### Issue description

When you use an external editor to modify a class_name doc comment, the old value is still displayed (in Create New Node) until you restart Godot.

I have auto reload scripts enabled:
 ![Image](https://github.com/user-attachments/assets/09d0da6c-5525-49ca-a18c-5edbccb262bf)

### Steps to reproduce

1. Enable external editor (I use vim).
2. Existing script nilrotation.gd:
```gdscript
## Sometimes you don't want rotation to change.
class_name NilRotation
extends Node2D


func _process(_dt):
    global_rotation = 0
```
3. Confirm Create New Node shows the correct docstring
![missing the first line](https://github.com/user-attachments/assets/a95b7b34-219f-43f2-8c3f-d18e728d0191)

5. In external editor, change the line to `## Force the global rotation to stay at 0 (never rotate).`
6. Check docstring shown in Create New Node.

**Expected:** It's updated.
**Actual:** It hasn't changed.





### Minimal reproduction project (MRP)

trivially reproducible in new project.
Repository: ollama
Issue: Enhanced aria2c download support with optimized configurations
Labels: feature request

the install script uses curl for downloading Ollama components. While there is value in adding aria2c support for faster downloads, we can further optimize it with additional aria2c configurations for better reliability and performance.
Repository: youtube-dl
Issue: Abema TV support
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://abema.tv/channels/fighting-sports2/slots/C3K1gmnm9FchM1?lang=en


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

https://abema.tv/channels/fighting-sports2/slots/C3K1gmnm9FchM1?lang=en
trying to download this video but i get this error:

ERROR: No video formats found; please report this issue on https://github.com/ytdl-org/youtube-dl/issues , using the appropriate issue template. Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose option and include the complete output.
Repository: ollama
Issue: docker installation failure due to your installation failure...
Labels: bug

### What is the issue?

=> [vps2_core 23/28] RUN curl -fsSL https://ollama.com/install.sh | sh                                                                                                                                  5432.3s
 => => # >>> Installing ollama to /usr/local
 => => # >>> Downloading Linux amd64 bundle
 => => # #############################################                             63.8%
 => => # [output clipped, log limit 2MiB reached]


### OS

Linux, Docker, WSL2

### GPU

_No response_

### CPU

Intel

### Ollama version

?
Repository: ui
Issue: [bug]: monorepo CLI fails to create project `BUN`
Labels: bug

### Describe the bug

When attempting to create a new Next.js monorepo project using the shadcn CLI (canary version), the process fails due to missing workspace dependencies.

### Affected component/components

CLI

### How to reproduce

## Steps to Reproduce

1. Run the following command: `bunx --bun shadcn@canary init`
2. Choose "Next.js (Monorepo)" when prompted to start a new project
3. Enter a project name (e.g., "test-monorp-shadcn")

## Expected Behavior

The CLI should successfully create a new Next.js monorepo project with all necessary dependencies and configurations.

## Actual Behavior

The CLI fails to create the project, reporting missing workspace dependencies:

```shell
✖ Something went wrong creating a new Next.js monorepo.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

# Logs section...
```

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
PS C:\Users\Jozef\Desktop> bunx --bun shadcn@canary init
√ The path C:\Users\Jozef\Desktop does not contain a package.json file.
  Would you like to start a new project? » Next.js (Monorepo)
√ What is your project named? ... test-monorp-shadcn
✖ Something went wrong creating a new Next.js monorepo.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Command failed with exit code 1: bun install
error: Workspace dependency "@workspace/eslint-config" not found

Searched in "..\..\..\..\..\C:\Users\Jozef\Desktop\test-monorp-shadcn\*"

Workspace documentation: https://bun.sh/docs/install/workspaces


error: Workspace dependency "@workspace/typescript-config" not found

Searched in "..\..\..\..\..\C:\Users\Jozef\Desktop\test-monorp-shadcn\*"

Workspace documentation: https://bun.sh/docs/install/workspaces

error: @workspace/eslint-config@* failed to resolve
error: @workspace/typescript-config@* failed to resolve
bun install v1.1.42 (50eec002)
```


### System Info

```bash
- Operating System: Windows 11 version 23H2 (SO 22631.4602)
- Node.js version: v22.11.0
- Bun version: 1.1.42
- shadcn CLI version: canary
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: go
Issue: all: CI's enforcement of clean `go generate` is lacking
Labels: help wanted,NeedsInvestigation

### Go version

go version devel go1.24-110ab1aaf4 Sat Dec 21 08:22:08 2024 -0800 linux/amd64

### Output of `go env` in your module/workspace:

```shell
AR='ar'
CC='gcc'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_ENABLED='1'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
CXX='g++'
GCCGO='gccgo'
GO111MODULE=''
GOAMD64='v3'
GOARCH='amd64'
GOAUTH='netrc'
GOBIN=''
GOCACHE='/tmp/go-build'
GODEBUG=''
GOENV='/home/hugo/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFIPS140='off'
GOFLAGS=''
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build610608568=/tmp/go-build -gno-record-gcc-switches'
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMOD='/home/hugo/k/go/src/go.mod'
GOMODCACHE='/home/hugo/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/hugo/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/hugo/k/go'
GOSUMDB='sum.golang.org'
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/hugo/.config/go/telemetry'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/home/hugo/k/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.24-110ab1aaf4 Sat Dec 21 08:22:08 2024 -0800'
GOWORK=''
PKG_CONFIG='pkg-config'
```


### What did you do?

In the go repo:
```bash
cd src
./make.bash
cd internal/goexperiment/ && go generate .
git status
```

### What did you see happen?

```
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	exp_synctest_off.go
	exp_synctest_on.go

nothing added to commit but untracked files present (use "git add" to track)
```

### What did you expect to see?

```
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
```
Repository: ollama
Issue: MultiGPU ROCm
Labels: bug,amd,gpu

### What is the issue?

System:
CPU AMD Ryzen 9950X
RAM 128 GB DDR5
GPU0 AMD Radeon PRO W7900
GPU1 AMD Radeon RX7900XTX
ROCM: 6.3.1
Ubuntu 24.04 LTS (currently patched)

ERROR:
I start a large LLM (e.g. Llama-3.3-70B-Instruct-Q4_K_L) with open webui and a context window of 32678 and get the following error in ollama:
Dec 22 03:52:04 ollama ollama[6345]: time=2024-12-22T03:52:04.990Z level=INFO source=server.go:589 msg="waiting for server to become available" status="llm server error"
Dec 22 03:52:41 ollama ollama[6345]: ROCm error: out of memory
Dec 22 03:52:41 ollama ollama[6345]: llama/ggml-cuda/ggml-cuda.cu:96: ROCm error

=========================================== ROCm System Management Interface ==========================================
==================================================== Concise Info ====================================================
Device Node IDs Temp Power Partitions SCLK MCLK Fan Perf PwrCap VRAM% GPU%
 (DID, GUID) (Edge) (Avg) (Mem, Compute, ID)
========================================================== ==========================================================
0 1 0x7448, 54057 59.0°C 56.0W N/A, N/A, 0 651Mhz 96Mhz 20.0% auto 241.0W 0% 82%
1 2 0x744c, 53541 40.0°C 75.0W N/A, N/A, 0 1301Mhz 456Mhz 0% auto 327.0W 0% 39%
========================================================== ==========================================================
================================================ End of ROCm SMI Log ================================================

The VRAM on both cards is never fully utilized and the normal RAM is almost completely free. SWAP is not used.

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.5.4
Repository: flutter
Issue: Laggy First Keyboard Open (Physical iOS Device)
Labels: a: text input,platform-ios,a: quality,has reproducible steps,team-ios,fyi-text-input,found in release: 3.27,found in release: 3.28

### Steps to reproduce

checkout https://github.com/willsmanley/flutter-textfield-keyboard-ios-bug

run on a physical ios device (with either impeller or skia)

press the textfield to focus it and trigger a keyboard open. the first time during app run takes 2 second lag. every subsequent time is immediate.

note: it only happens the very first time you open the keyboard. hot restarting and hot reloading will not reset this. only by rebuilding can you experience the lag again.

### Expected results

should open immediately like native swift apps

### Actual results

opens keyboard after 1-2 second delay

### Code sample

https://github.com/willsmanley/flutter-textfield-keyboard-ios-bug

### Screenshots or Video

_No response_

### Logs

n/a

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.0, on macOS 15.1 24B2082 darwin-arm64, locale en-US)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/to/macos-android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] Connected device (6 available)
[✓] Network resources

! Doctor found issues in 2 categories.
```

</details>
Repository: godot
Issue: GPU Particles 3D: New particles not emitting with specific Lifetime + Scale Curve settings
Labels: bug,topic:particles

### Tested versions

Occurs in 4.3

Tested in 4.2, but can't get the specific particle system to work, in general

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated GeForce GTX 1060 6GB - Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz (12 Threads)

### Issue description

The current Particle settings in the provided MRP result in no new particles being spawned. 

This persists when the Lifetime settings is 16 seconds, or any value greater than that

When Lifetime is less than 16 seconds or the Scale Curve settings are altered, the system spawns new particles. Did I manage to find a perfect, broken balance or something?



### Steps to reproduce

Mess with the Lifetime and Scale Curve values in the MRP.

Or other settings- perhaps something else is adding to it.

### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/18219866/mrp.zip)
Repository: flutter
Issue: Ancient Unicode character on Windows not visible
Labels: platform-windows,a: typography,P3,a: adaptivity,team-engine,triaged-engine

### Steps to reproduce

1. Create a Text widget with the Unicode characters 133FA-13402

### Expected results

I expect to see 9 the ancient Egyptian hieroglyph Z015-Z015H which represent the digits 1-9.

### Actual results

I see only 8 hieroglyphs. The digit 3 ("𓏼" Z015B) is missing.

### Code sample

<details open><summary>Code sample</summary>

```dart
Text('''
1=\u{133FA}
2=\u{133FB}
3=\u{133FC}
4=\u{133FD}
5=\u{133FE}
6=\u{133FF}
7=\u{13400}
8=\u{13401}
9=\u{13402}
''',
  style: Theme.of(context).textTheme.displayLarge,
);
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![grafik](https://github.com/user-attachments/assets/dd661125-c3dc-4885-857a-4c02038e17a6)

</details>


### Logs

<details open><summary>Logs</summary>

```console
Launching lib\main.dart on Windows in debug mode...
Building Windows application...
√ Built build\windows\x64\runner\Debug\digits.exe
Debug service listening on ws://127.0.0.1:63341/iDV28gHmAgY=/ws
Syncing files to device Windows...
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.27.1, on Microsoft Windows [Version 10.0.22631.4460], locale de-DE)
[√] Windows Version (Installed version of Windows is version 10 or higher) [Spoiler it is Windows 11]
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.3)
[√] Android Studio (version 2024.2)
[√] Connected device (3 available)
[√] Network resources

• No issues found!
```

</details>
Repository: ollama
Issue: Documentation for manual Linux installation is outdated/doesn't work for AMD GPU setup
Labels: bug

### What is the issue?

[The documentation for manual Linux installation](https://github.com/ollama/ollama/blob/d8bab8ea4403d3fb05a9bf408e638195b72bebf9/docs/linux.md) provides the following instructions to set up AMD gpu: download an additional archive and extract it using
```
sudo tar -C /usr -xzf ollama-linux-amd64-rocm.tgz
```

However, this will put the libraries under `/usr/lib/ollama/` directory. This seems to be wrong, as the ollama binary searches for compatible libraries in the following directories, according to debug output:
```
/usr/local/lib/ollama
/opt/rocm/lib
/usr/lib64
/usr/share/ollama/lib/rocm
```

I'm not sure if the `/usr/lib/ollama` is ever used for anything, but only after moving `usr/lib/ollama` to `/usr/local/lib/ollama`, I get working amd gpu support. This is highly annoying because the documentation suggests that I need to install ROCm, which I did and which didn't help either

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.5.4
Repository: PowerToys
Issue: Quick Accent doesn't have "È" symbol and others, that are important in most languages, in UTF-8
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

Quick Accent

### Steps to reproduce

1. Open any text editor or application where text input is required.
2. Use PowerToys to access the character set.
3. Attempt to insert an accented uppercase letter (e.g., "È").
4. Observe that the selected character does not appear in the text.





### ✔️ Expected Behavior

The accented uppercase letter should be displayed correctly in the text.

### ❌ Actual Behavior

The accented uppercase letter does not appear in the text, causing issues with accurate typing.

### Other Software

_No response_
Repository: PowerToys
Issue: Support ability to configure/place independent "activation zones" in FancyZones
Labels: Needs-Triage

### Description of the new feature / enhancement

I would like to see support for small "activation zones" representing a larger zone that can be manually placed during layout configuration. This is a crude drawing showing what this might look like:

![Image](https://github.com/user-attachments/assets/99b067c9-0de2-48d4-a57f-7e3ae9c79b87)

The black box is the desktop. The blue outlines are the configured zones. The red boxes are what the user would actually see on the desktop when dragging a window around. These are the zone activation areas. The user would have to drag their window to the smaller zone, and then it would resize and fit into the blue area. 

### Scenario when this would be used?

This would allow a user to disable hotkey activation of zone snapping and still have some freedom to manually place windows even if the entire display is filled with zones. In the current implementation, if a user has zones filling all usable space and disables hotkey activation, it's near impossible to manually place a window without having it snap to a zone.

This also allows more complex overlapping zones while still keeping most of the usability of the desktop without needing any hotkeys. If the activation area is independent of the zone, a user could configure multiple "layouts" in the same layout with overlapping zones. 

Ideally, the zones would be able to be "named" to make it clear what area does what. Building on the example before, this would allow configuration of something like this, splitting the right side of the screen to allow optionally using the full right side or the top/bottom halves.

![Image](https://github.com/user-attachments/assets/a8896016-35ba-412c-a226-2153c9be0697)

Here, I could drop my window onto the "Full" activation area and it would fill the brown colored zone. If I drop it in the yellow "Top" area, it filles the yellow zone in the top right. Same with the green zone which would fill the "Bottom" area. 


### Supporting information

_No response_
Repository: PowerToys
Issue: PowerToys Run does not show when Brave Browser or Terminal has focus
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Set PowerToys run shortcut to "Windows Key" + "Spacebar"
Open Brave browser or Open Windows Terminal
Try and open Run. Nothing happens

Only way to get it kind of working is to press "Windows Key" wait for that to show and take focus then press shorcut command. Even then PowerToys Run is behind the Windows search, so its not being placed on top of everything


### ✔️ Expected Behavior

When Browser ior terminal has focus and the PowerToys Run shortcut is pressed the Run window should show. It works as expected with Notepad++ and other applications

### ❌ Actual Behavior

Nothing shows for PowerToys Run command

### Other Software

_No response_
Repository: rust
Issue: Always show the lint name involved in a diagnostic?
Labels: A-lints,A-diagnostics,T-compiler,WG-diagnostics,C-discussion

### Description

After the first occurrence of a lint, the name of the lint is not displayed anymore.

That is a real annoyance:
  - When the diagnostics are shown in a console, one has to find out the first occurrence of the error.
  - When the diagnostics are shown in an IDE, there is not such a thing as the first diagnostics so it is almost impossible to find out the name of the lint.

I do not see any good reason to optimize one line of such a useful information. (Or maybe there are still hobbyist using teleprinter and Altair 8800???).



### Version

```text

```

### Additional Labels

_No response_
Repository: godot
Issue: 3D viewport camera freelook doesn't work anymore with hold rotate + WASD
Labels: bug,topic:editor,topic:3d

### Tested versions

- Reproducible in: 4.4 dev3 and above
- Not reproducible in: 4.3 and earlier

### System information

Godot v4.4.dev7.mono - Windows 10 (build 19045) - Multi-window, 2 monitors

### Issue description

In version 4.3 and before, I could move 3D viewport camera with holding camera rotate button and using WASD keys.
In 4.4, it's not possible anymore and I can only enter WASD navigation by using freelook hotkey.

### Steps to reproduce

- Enter 3D viewport
- Hold camera rotate button
- Press WASD keys

### Minimal reproduction project (MRP)

-