sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Use `rustc` attrs in `dangling_pointers_from_temporaries` lint
Labels: E-easy,C-cleanup,A-lints,E-mentor,T-compiler

> > If you want to do it in this PR (otherwise in a follow-up), we could add an `rustc` attribute to those `as_ptr`/`as_mut_ptr` methods.
>
> You can follow https://github.com/rust-lang/rust/pull/132146/commits/afcb09b8c765bf2c5b1362b433725f57af51aaad and https://github.com/rust-lang/rust/pull/132146/commits/2a930d3818d1f4dcaf7a06ed7fc12c102268755d (from a PR of mine) with `check_applied_to_fn_or_method` instead, and something similar to this to check the attribute https://github.com/rust-lang/rust/blob/e454c45f1397e382cfb59f0b8970445c8efa875f/compiler/rustc_lint/src/ptr_nulls.rs#L49-L50

_Originally posted by @Urgau in https://github.com/rust-lang/rust/pull/128985#discussion_r1818068264_
            

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"gavincrawford"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Update minimum recommended CocoaPods version to support Xcode 16 synchronized groups
Labels: platform-ios,tool,platform-mac,P1,fyi-infra,team-ios,triaged-ios

https://github.com/CocoaPods/Xcodeproj/pull/985 fixed critical CocoaPods issue https://github.com/CocoaPods/CocoaPods/issues/12456 which impacted adding new iOS and macOS targets (like test targets and extensions) and add-to-app customers.

The fix is in CocoaPods [1.16.2](https://github.com/CocoaPods/CocoaPods/releases/tag/1.16.2).


- [x] Upload new 1.16.2 CocoaPods cipd package. https://github.com/flutter/cocoon/pull/4010
- [ ] Update CocoaPods cipd version in packages CI
- [x] Update CocoaPods cipd version in flutter CI https://github.com/flutter/flutter/pull/136929
- [x] Update minimum recommended version. https://github.com/flutter/flutter/pull/158206 https://github.com/flutter/flutter/blob/ab256e5caff0f3ba5c8d0b3375697344e7a1b79f/packages/flutter_tools/lib/src/macos/cocoapods.dart#L77-L78
- [x] Update version on website https://github.com/flutter/website/pull/11346
- [ ] Cherry-pick to beta.  See https://github.com/flutter/flutter/pull/157022. 

See related https://github.com/flutter/flutter/issues/133584.
Repository: ui
Issue: [bug]: unable to resolve dependency tree for Command componnent NextJS
Labels: bug

### Describe the bug

When using `npx shadcn@latest add command` in a nextjs 15 project, the dependency tree is not met:

`Command failed with exit code 1: npm install cmdk@1.0.0 @radix-ui/react-dialog
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: not-another-dashboard@0.1.0
npm ERR! Found: react@19.0.0-rc-69d4b800-20241021
npm ERR! node_modules/react
npm ERR!   react@"19.0.0-rc-69d4b800-20241021" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from cmdk@1.0.0
npm ERR! node_modules/cmdk
npm ERR!   cmdk@"1.0.0" from the root project`


### Affected component/components

Command

### How to reproduce

install nextjs 15.
install shadcn

try to install the Command component

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
npx shadcn@latest add command

✔ Checking registry.
⠦ Installing dependencies.
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: npm install cmdk@1.0.0 @radix-ui/react-dialog
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: not-another-dashboard@0.1.0
npm ERR! Found: react@19.0.0-rc-69d4b800-20241021
npm ERR! node_modules/react
npm ERR!   react@"19.0.0-rc-69d4b800-20241021" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from cmdk@1.0.0
npm ERR! node_modules/cmdk
npm ERR!   cmdk@"1.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
```


### System Info

```bash
Mac OS
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: excalidraw
Issue: feature request: quick color selection using number keys (1-5) while using the drawing tool
Labels: enhancement,shortcuts

i would like to request a feature that allows users to quickly select colors using the number keys (1-5) while using the drawing tool in excalidraw. 

**current workflow issue**:
- the current flow of changing tools is messy. for instance, when i enter color select mode using 's', but then try to select a color via the 'asdfg' hotkeys, it changes tools after 2-3 clicks on the color. this disrupts my drawing flow and makes it frustrating to switch colors efficiently.

**use case**:
- implementing a quick color selection method would enhance my workflow, especially in zen mode where i prefer a more focused experience.

**proposed solution**:
- allow users to assign specific colors to the number keys (1-5) for quick access while drawing, without changing the drawing tool.
- this way, i can easily change colors without interrupting my drawing flow.

thank you for considering this request!
Repository: excalidraw
Issue: feature request: voice annotations in excalidraw
Labels: enhancement

i would like to propose a feature that allows users to add voice annotations directly to their drawings in excalidraw.

#### current limitation:
currently, users must rely on text notes to convey ideas and context within their drawings. this can be time-consuming and may not effectively capture the nuances of spoken explanations, especially when trying to convey complex concepts or emotional nuances.

#### use case:
the ability to record and attach voice annotations would greatly enhance the usability of excalidraw for educators, students, and professionals. for instance, a teacher could record a brief explanation of a diagram while creating it, providing students with immediate context. similarly, a team could record discussions about specific elements of a project as they design collaboratively, ensuring that everyone is on the same page.

#### proposed solution:
- integrate a voice recording feature that allows users to record audio directly within the excalidraw interface.
- users should be able to attach these audio notes to specific elements or areas of their drawings.
- provide playback controls for users to listen to their recordings while reviewing or presenting their drawings.

#### why this matters:
implementing voice annotations would significantly improve the user experience by combining visual and auditory elements in a single workspace. this is particularly beneficial for:
- **enhanced learning**: voice annotations can provide additional context that text alone cannot convey, aiding comprehension and retention for students.
- **dynamic presentations**: presenters can use voice annotations to explain their diagrams or ideas more effectively, creating a richer experience for their audience.
- **accessibility**: voice notes can help those who may struggle with writing or typing to express their ideas more freely.

by adding this feature, excalidraw can become an even more powerful tool for interactive learning and collaboration, making it appealing to a broader audience. 

thank you for considering this request! i believe that voice annotations would greatly enhance the functionality of excalidraw and improve the overall user experience.
Repository: rust
Issue: Document what a "dangling pointer" is
Labels: E-hard,E-help-wanted,A-docs,T-libs,T-opsem

## Location

There are several places this applies, e.g.:

 - [`std::ptr::dangling`](https://doc.rust-lang.org/nightly/std/ptr/fn.dangling.html)
 - [`std::ptr::from_ref`](https://doc.rust-lang.org/nightly/std/ptr/fn.from_ref.html) *(in the examples)*
 - `dangling_pointers_from_temporaries` lint

## Summary

We have several place in the standard library or as part of lints where we use the term "dangling pointer" without defining it anywhere.

We should have a place where we define what that is, ideally in the standard library, in it's own section, maybe under `std::ptr`, so it can be referenced elsewhere.

It should probably have a definition, followed by some bad examples (and maybe how to fix them).

[Wikipedia has article](https://en.wikipedia.org/wiki/Dangling_pointer) on the subject, *I don't know if it could serve as a base for our documentation but it may be worth checking it.*

## Steps

 - [ ] Add std documentation
 - [ ] Update existing std docs
 - [ ] Update lints diagnostics
Repository: flutter
Issue: [flutter_svg] Bring up web tests
Labels: a: tests,team,package,P2,team-engine,triaged-engine,p: flutter_svg

Currently `flutter_svg` unit tests don't compile on web due to using non-web-only golden methods in a small number of tests. For now I've opted out the entire package from web Dart unit tests via `dart_test.yaml`, because refactoring is out of scope for the initial import, but we should make it so that the tests compile on web, and only the golden tests don't *run* on web, and remove `dart_test.yaml`, so we are testing all the platforms the package supports.

`rfw` had the same problem, and solved it [like this](https://github.com/flutter/packages/blob/85c4934bda545beff36133dc63e47de5b5c5c56b/packages/rfw/test/material_widgets_test.dart#L12-L13).
Repository: godot
Issue: Sequential Input.parse_input_event() calls ignore all previous ones when checking Input.is_input_pressed()
Labels: bug,needs testing,topic:input

### Tested versions

4.3 stable-official

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 32.0.15.6590) - Intel(R) Core(TM) i7-14700K (28 Threads)

### Issue description

When simulating input by generating InputEventAction in code, if two or more sequential actions are trying to be sent within the same function, only the last one will be read as pressed in `Input.is_action_pressed()`.

### Steps to reproduce
```
var ev_left = InputEventAction.new()
ev_left.action = "push_left"
var ev_right = InputEventAction.new()
ev_right.action = "push_right"
	
ev_left.pressed = true
ev_right.pressed = true
	
Input.parse_input_event(ev_left)
Input.parse_input_event(ev_right)

print("push_left %s, push_right %s" % [ Input.is_action_pressed("push_left"), Input.is_action_pressed("push_right")] )
# Will print: push_left false, push_right true
```

Expected: both `is_action_pressed()` calls return true.
Simply run the included project and you will see two Label sprites setting visibility based on the code above.

### Minimal reproduction project (MRP)


[parse_input_event_issue.zip](https://github.com/user-attachments/files/17547826/parse_input_event_issue.zip)
Repository: go
Issue: cmd/go: document interaction of go.work with GODEBUG
Labels: Documentation,NeedsInvestigation

We recently encountered this confusing scenario when working in the x/tools repository

- In order to use a go.work file to work on gopls (which has go 1.23.1 in its go.mod file), one has to have at least go1.23.1 in the go.work file.
- x/tools assumes that it's default GODEBUG behavior implies gotypesalias=0, and has tests such ./internal/aliases.TestNewAlias that assume this.

Therefore, there's no way to have a go.work file for which both x/tools and x/tools/gopls tests pass. This is a problem in x/tools, because these tests also fail when run from a different main module that uses go1.23 (see #70082).

Nevertheless, [go.dev/blog/compat](http://go.dev/blog/compat) says the following:

> A program’s GODEBUG settings are configured to match the Go version listed in the main package’s go.mod file. If your program’s go.mod file says go 1.20 and you update to a Go 1.21 toolchain, any GODEBUG-controlled behaviors changed in Go 1.21 will retain their old Go 1.20 behavior until you change the go.mod to say go 1.21.

We should update that documentation to explain how godebug interacts with go.work files.

CC @timothy-king @matloob @samthanawalla
Repository: rust
Issue: `assembler label '' cannot be undefined` on Windows ARM
Labels: O-windows,A-inline-assembly,T-compiler,C-bug,E-needs-mcve,O-AArch64


Whenever I try compiling [turborepo](https://github.com/vercel/turborepo) on Windows ARM, I get the following error when rustc tries to build tokio:

```rust
error: assembler label '' can not be undefined
```

I'd expect this code to compile, since it works fine on other platforms (macOS/Linux/Windows x86).

### Meta
`rustc --version --verbose`:
```
rustc 1.82.0-nightly (0d634185d 2024-08-29)
binary: rustc
commit-hash: 0d634185dfddefe09047881175f35c65d68dcff1
commit-date: 2024-08-29
host: aarch64-pc-windows-msvc
release: 1.82.0-nightly
LLVM version: 19.1.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

I don't seem to get a backtrace on Windows, even when setting via `set RUST_BACKTRACE=1`

Here's all I get:
```
error: assembler label '' can not be undefined
   Compiling hyper v1.4.1
   Compiling console v0.15.7
   Compiling proc-macro-crate v3.1.0
   Compiling async-graphql-parser v7.0.7
   Compiling crossterm v0.27.0
   Compiling turborepo-vercel-api v0.1.0 (C:\Users\nicholas\turbo\crates\turborepo-vercel-api)
   Compiling turborepo-ci v0.1.0 (C:\Users\nicholas\turbo\crates\turborepo-ci)
   Compiling itertools v0.12.0
   Compiling stability v0.1.1
   Compiling lru v0.12.2
   Compiling memoffset v0.7.1
   Compiling encoding_rs v0.8.32
error: could not compile `tokio` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
```

</p>
</details>
Repository: PowerToys
Issue: Relative shortcut paths with New+
Labels: Needs-Triage

### Description of the new feature / enhancement

Can New+ add the feature to create a complete path shortcut based on the relative part shortcut in New+ template. Currently the tricks to add a relative path shortcut (via another explorer thread) is not being recognize by the application when prompting the diretory. (you cannot see the relative path when "Save as"....)

### Scenario when this would be used?

With relative parth shortcut, we can duplicate the shortcut per directory template

### Supporting information

![Image](https://github.com/user-attachments/assets/658efea7-7793-4b81-9ba1-834d49251ce2)
Repository: ollama
Issue: Feature request: Add CLI argument to specify a system prompt
Labels: feature request

I'd like to be able to set the system prompt from the call to `ollama` in my shell, rather than in the conversation. For example:

```sh
ollama run llama3.1 --system="Your nickname is 'Grass' now"
```

...or...

```sh
ollama run llama3.1 -s "system" "Your nickname is 'Grass' now"
```

With this ability, I could set up aliases in my shell profile so that I can run system-prompt-customized versions of a model with a single command.

```sh
alias grass="ollama run llama3.1 --system=\"Your nickname is 'Grass' now\""
```

It'd be even better if I could also specify a path to a text file with a system prompt (e.g. `ollama run llama3.1 --system-file="~/system_prompts/grass.txt"`, but that wouldn't be necessary.

This is unique from #807, whose fix only works in the conversation.
Repository: terminal
Issue: ENHANCED_KEY flag missing when releasing RightAlt
Labels: Help Wanted,Area-Input,Issue-Bug,Product-Terminal

### Windows Terminal version

current main

### Windows build number

10.0.19045.4894

### Other Software

_No response_

### Steps to reproduce

1. Run the following c++ code:
  ```c++
  #include <iostream>
  #include <windows.h>
  int main()
  {
      INPUT_RECORD rec;
      DWORD count;
      while (true)
      {
          ::ReadConsoleInputW(::GetStdHandle(STD_INPUT_HANDLE), &rec, 1, &count);
          if (rec.EventType == KEY_EVENT)
          {
              std::cout << "type: KEY_EVENT" << std::hex
                        << ", down: " << rec.Event.KeyEvent.bKeyDown
                        << ", ENHANCED_KEY: " << !!(rec.Event.KeyEvent.dwControlKeyState & ENHANCED_KEY)
                        << ", ctrl: 0x" << rec.Event.KeyEvent.dwControlKeyState
                        << ", vcod: 0x" << rec.Event.KeyEvent.wVirtualKeyCode
                        << ", scod: 0x" << rec.Event.KeyEvent.wVirtualScanCode
                        << ", wchr: 0x" << rec.Event.KeyEvent.uChar.UnicodeChar << '\n';
          }
      }
  }
  ```
2. Press LeftCtrl key, press RightCtrl key, check ENHANCED_KEY flag.
3. Press LeftAlt key, press RightAlt key, check ENHANCED_KEY flag.

### Expected Behavior

The ENHANCED_KEY flag is present when RightAlt is pressed and released.

The current conhost.exe is not affected by this issue.

### Actual Behavior

The ENHANCED_KEY flag is absent when RightAlt is released, but is present when RightAlt is pressed.
Repository: rust
Issue: Tracking issue for ergonomic reference counting
Labels: T-lang,C-tracking-issue,F-ergonomic_clones

This is a tracking issue for ergonomic reference counting, including:

- https://github.com/rust-lang/rfcs/pull/3680
- https://github.com/rust-lang/rust-project-goals/issues/107

...and other work.

The feature gate for this issue is `#![feature(ergonomic_clones)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.  They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.  A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.  Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [ ] Approve as lang experiment.
- [ ] Accept an RFC.
- [ ] Implement in nightly.
- [ ] Add documentation to the [dev guide][].
  - See the [instructions][doc-guide].
- [ ] Add documentation to the [reference][].
  - See the [instructions][reference-instructions].
- [ ] Add formatting for new syntax to the [style guide][].
  - See the [nightly style procedure][].
- [ ] Stabilize.
  - See the [instructions][stabilization-instructions].

[dev guide]: https://github.com/rust-lang/rustc-dev-guide
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[edition guide]: https://github.com/rust-lang/edition-guide
[nightly style procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md
[reference]: https://github.com/rust-lang/reference
[reference-instructions]: https://github.com/rust-lang/reference/blob/master/CONTRIBUTING.md
[stabilization-instructions]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[style guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

* Name of `UseCloned` trait which signals `x.use` to `clone`
* Precise set of `UseCloned` impls -- in particular any blanket impls we ought to be concerned about?

### Related

- https://github.com/rust-lang/rust-project-goals/issues/107

cc @spastorino @jkelleyrtp @rust-lang/lang
Repository: tauri
Issue: [bug] assertion failed: `!bitmap.is_null()`
Labels: type: bug,status: needs triage

### Describe the bug

```
thread 'main' panicked at C:\Users\Rose\.cargo\registry\src\index.crates.io-6f17d22bba15001f\softbuffer-0.4.6\src\backends\win32.rs:99:9:
assertion failed: !bitmap.is_null()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1028/172140.698:ERROR:window_impl.cc(121)] Failed to unregister class Chrome_WidgetWin_0. Error = 1412
```

Crash occured during `pnpm tauri dev`. Happy to provide any other information needed.

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22621 x86_64 (X64)
    ✔ WebView2: 130.0.2849.52
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Build Tools 2022
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 22.9.0
    - pnpm: 9.12.2
    - yarn: 1.22.19
    - npm: 10.8.3
    - bun: 1.1.31
    - deno: deno 2.0.2

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.3
    - @tauri-apps/cli : 2.0.5

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../build
    - devUrl: http://localhost:1420/document/00192d1c97c09-000-T0000000000000-00
    - framework: Svelte
    - bundler: Vite
```


### Stack trace

```text
processes was not running with `RUST_BACKTRACE=1` when the crash occured.
```


### Additional context

_No response_