sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for const_cell
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(const_cell)]`

This is a tracking issue for using `Cell` in a const context.

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// core::cell

impl<T> Cell<T> {
    pub const fn replace(&self, val: T) -> T;
}

impl<T: Copy> Cell<T> {
    pub const fn get(&self) -> T;
}

impl<T: ?Sized> Cell<T> {
    pub const fn get_mut(&mut self) -> &mut T;
    pub const fn from_mut(t: &mut T) -> &Cell<T>;
}

impl<T> Cell<[T]> {
    pub const fn as_slice_of_cells(&self) -> &[Cell<T>];
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #131281
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: react-native
Issue: Multiline controlled input enters an infinite loop on iOS
Labels: Platform: iOS,Issue: Author Provided Repro

### Description

This code enters an infinite loop on iOS.

```js
import React, {useState, memo} from 'react'
import {TextInput} from 'react-native'

let App = () => {
  console.log('render App')
  const [outlet, setOutlet] = useState(null)
  return (
    <>
      <Outlet outlet={outlet} />
      <Child setOutlet={setOutlet} />
    </>
  )
}
export default App

let Child = memo(({setOutlet}) => {
  console.log('render Child')
  const [value, setValue] = useState('')
  return (
    <Portal setOutlet={setOutlet}>
      <TextInput
        onChangeText={text => setValue(text)}
        value={value}
        multiline
        style={{
          backgroundColor: 'red',
          marginTop: 200,
        }}
      />
    </Portal>
  )
})

let Outlet = memo(({outlet}) => {
  console.log('render Outlet')
  return outlet
})

let Portal = memo(({children, setOutlet}) => {
  console.log('render Portal')
  React.useLayoutEffect(() => {
    setOutlet(children)
  }, [children])
  return null
})
```

Removing `multiline` prop fixes the issue.

I suspect this may be related to https://github.com/facebook/react-native/issues/36494 but who knows.

### Steps to reproduce

See above

### React Native Version

0.75.4

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.6.1
  CPU: (16) arm64 Apple M3 Max
  Memory: 53.04 GB / 128.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.8.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2024.09.09.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2412.12266719
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

https://github.com/gaearon/rn-bug-loop

### Screenshots and Videos


https://github.com/user-attachments/assets/9ddf62e5-4322-4d8e-bfd7-c34d94ec773b
Repository: godot
Issue: Skeleton Path is not assigned correctly when importing a glb with bound MeshInstance as a child of BoneAttachment
Labels: bug,confirmed,topic:import

### Tested versions

v4.3.stable.mono.official [77dcf97d8]
v4.4.dev3.mono.official [f4af8201b]

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4080 (NVIDIA; 32.0.15.5599) - AMD Ryzen 9 7950X3D 16-Core Processor (32 Threads)

### Issue description

In Godot 4.3 my imported model is distorted when running the game. I have a model imported as GLB from Blender and added to a 3d scene. I also added a camera. In editor everything looks fine:

![image](https://github.com/user-attachments/assets/ff3b3f55-e493-43f7-bafd-7dfec1ad3cc8)

Also the camera preview looks fine.

![image](https://github.com/user-attachments/assets/561d05eb-7f3a-417d-aa3a-4d849621a180)

But when I run the game, the model is distorted, e.g. the body gets scaled up a lot while the hands and eyes move but retain their scale. 

![image](https://github.com/user-attachments/assets/af85b5f5-4ea8-4b11-b4d9-4e5243138f5f)

This same scene works just fine in Godot 4.2. 

![image](https://github.com/user-attachments/assets/e3fb2ae2-56c9-45aa-8e15-964fbe4193eb)


### Steps to reproduce

Open the MRP in both Godot 4.2 and Godot 4.3, run the `node_3d.tscn` scene to see the  results.

### Minimal reproduction project (MRP)

[bone_problem_reproducer.zip](https://github.com/user-attachments/files/17265753/bone_problem_reproducer.zip)
Repository: godot
Issue: [4.3] Web Export not working via command line
Labels: bug,platform:web,topic:editor,topic:export

### Tested versions

4.3 Stable

### System information

Windows 11

### Issue description

I have tried to export my project to Windows & Web via command line (both locally and via GitHub actions using ubuntu).
The result is a working Windows export and a broken ZIP file for Web.

### Steps to reproduce

1. Create new Project
2. Export > Manage Export Templates > download 4.3 templates
3. "Project > Export > Add..." Web export
4. Name it Web
5. Save everything
6. run `/path/to/your/Godot_v4.3-stable_win64_console.exe --headless --verbose --export-release "Web" ./HTML5.zip --path "./"`
7. Try to open resulting ZIP file
8. Message pops up telling you the zip file is invalid
![image](https://github.com/user-attachments/assets/291ac7f5-b37c-46d5-8a23-85009d30c87b)

I also tried different parameters, like running it in editor instead of headless mode or using export-debug or no path. All the same result

Note that exporting via Export in editor works fine!

### Minimal reproduction project (MRP)

[project.zip](https://github.com/user-attachments/files/17265762/project.zip)
Repository: godot
Issue: Shader Uniforms Documentation comments do not work when used in gdshaderinc files
Labels: bug,documentation,topic:shaders

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 31.0.15.5161) - 12th Gen Intel(R) Core(TM) i7-12650H (16 Threads)

### Issue description

	/**
	* This is a documentation comment.
	*/
	uniform bool something = false;

If this piece of shader code lives inside a gdshader file, it works.
Placed in a gdshaderinc file, it doesn't.

### Steps to reproduce

	/**
	* This is a documentation comment.
	*/
	uniform bool something = false;

If this piece of shader code lives inside a gdshader file, it works.
Placed in a gdshaderinc file, it doesn't.

### Minimal reproduction project (MRP)

N/A
Repository: deno
Issue: Support server without entrypoint for `deno serve`
Labels: suggestion,serve

For local development I often need a simple server that just spits out the files on my system as they are. Some runtimes (for other languages) provide such functionality; usually I end up using `php -S localhost:8080` which does just that. Deno has a `serve` command, which is exciting but doesn't _quite_ reach the use-case I need, since it requires an entry point that defines how the server should behave. I think it'd be nice to have a default server that responds with the files on the system, inferring content type from the file extensions.

This could look like a plain `deno serve` (without entry point) but to protect users from mistakes like accidentally forgetting the entry point, perhaps an additional flag would be good, e.g. `deno serve --plain` (or `--default`, or `--passthrough`, etcetera).

Is this something the Deno team would be interested in?
Repository: neovim
Issue: `jumpoptions=clean` does not work with `nohidden`
Labels: bug,jumps-navigation

### Problem

As the title says, when both `jumpoptions=clean` and `nohidden` are set, doing `:bd<CR>` on a buffer doesn't remove it from the jumplist.

### Steps to reproduce

```
$ nvim --clean A B C
:bn<CR>
:bn<CR>
:bp<CR>
:bd<CR>
<C-o>
=> Observer that you are on A
```

```
$ nvim --clean A B C
:setglobal nohidden<CR>
:bn<CR>
:bn<CR>
:bp<CR>
:bd<CR>
<C-o>
=> Observer that you are on B
```

### Expected behavior

The `<C-o>` in the second case to also skip `B` and jump to `A`.

Or, for this to be explicitly documented behaviour as non-visible buffers are unloaded when `nohidden` is set:
```
$ nvim --clean A B C
:setglobal nohidden<CR>
:bn<CR>
:bn<CR>
:=vim.iter(vim.api.nvim_list_bufs()):map(vim.api.nvim_buf_is_loaded):totable()<CR>
=> { false, false, true }
```

And that would make the jumplist nearly useless if `jumpoptions=clean` behaved the way it claims to:
```
          clean         Remove unloaded buffers from the jumplist.
```

### Nvim version (nvim -v)

NVIM v0.11.0-dev-988482d94

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

N/A

### Operating system/version

nixos unstable

### Terminal name/version

tmux

### $TERM environment variable

tmux-256color

### Installation

Custom nixpkgs overlay
Repository: vscode
Issue: Create untitled notebook sends `textDocument/didChange` for first cell before `notebookDocument/didOpen`
Labels: bug,notebook-api

Initially reported in https://github.com/astral-sh/ruff-vscode/issues/626, see there for more logs.
<!-- ⚠️⚠️ 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.0
- OS Version: Win11 23H2

Steps to Reproduce:

1. open new window of VSCode
2. create new untitled notebook file with `Ctrl+Win+Alt+N`
3. close untitled notebook.
4. Do again step 2
5. 🐛 Vscode sends `textDocument/didChange` for first cell before `notebookDocument/didOpen` event.
Repository: rust
Issue: Further restricting what coercions are allowed on places of type `!`
Labels: T-compiler,A-coercions,F-never_type,C-discussion,T-opsem

In #129392, I fixed a couple [soundness holes](https://github.com/rust-lang/rust/issues/117288) having to do with the distinction between values and places and the `!` type, which has special divergence and coercion behavior in HIR typeck.

To do so, I implemented a heuristic called `expr_guaranteed_to_constitute_read_for_never` (and same for patterns, `pat_guaranteed...`), which determines whether an expression/pattern is *guaranteed* to perform a read of a value of type `!`, which triggers the special divergence and coercion behavior. Read the description of the PR to see what the behavior is after the PR.

There's still some open questions about what expressions and patterns should be considered reads in the HIR (such as reading structs with only field subpatterns that don't read, like `Struct { .. }`), but I'd like to separate that since the PR #129392 is strictly an improvement over the existing behavior.
Repository: rust
Issue: `-Crelocation-model=rwpi` (and possibly others) are unsound due to affecting the ABI
Labels: O-Arm,P-medium,I-unsound,O-AArch64

This is based on the discussion [here](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/-C.20flags.20that.20change.20ABI/near/474829680); I don't understand much of the underlying technical details unfortunately.

It seems like setting `-Crelocation-model=rwpi` on an ARM target compiles code in a way that it expects a particular register to be reserved for data addressing. However, the standard library is not built with that in mind and can use the register for other purposes. That's clearly unsound, we can now get arbitrary misbehavior because the same register is used in conflicting ways.
Repository: tauri
Issue: Windows modal warning sound is heard whenever Tauri app starts, upon first click into app window
Labels: type: bug,platform: Windows,status: needs triage

Follow-up to https://github.com/tauri-apps/tauri/issues/1891
This is still an issue for me, on Windows 11:
The Windows modal warning sound is heard whenever Tauri app starts, upon the first click into the app window. 
This is slightly annoying because it draws attention to it and makes the user think "something is wrong" (even just a little, because if a sound gets played, it should be for a reason, otherwise there's no need to divert the user's attention).

Steps to reproduce:
```
PS D:\dev\proj> cargo create-tauri-app
✔ Project name · tauri-leptos-app
✔ Identifier · com.tauri-leptos-app.app
✔ Choose which language to use for your frontend · Rust - (cargo)
✔ Choose your UI template · Leptos - (https://leptos.dev/)

Template created! To get started run:
  cd tauri-leptos-app
  cargo tauri android init

For Desktop development, run:
  cargo tauri dev

For Android development, run:
  cargo tauri android dev

PS D:\dev\proj> cd .\tauri-leptos-app\
PS D:\dev\proj\tauri-leptos-app> cargo tauri dev
```
- The app window opens
- Now click anywhere into the app window
- The Windows modal warning sound gets played 
(Not sure what the right name for this sound is, it's the sound you usually hear when you click outside of a modal dialog, to make you realize that it wants you to interact with the modal dialog instead of anything behind it.)

Even though this sound is only heard on the first click into the app window after the app starts, it's still slightly annoying and an unnecessary drain on the user's attention.

---

Note that this also happens in release builds, e.g. with `cargo tauri build` and then running `.\target\release\tauri-leptos-app.exe`.
Repository: rust
Issue: Suggest to deref/reborrow to turn scrutinee into the right type for pattern
Labels: A-diagnostics,T-compiler

### Code

```rust
use std::cell::RefCell;

struct Foo {
    content: RefCell::<Option<u64>>,
}

fn main() {
    let foo = Foo {
        content: RefCell::new(Some(5)),
    };

    if let Some(_content) = foo.content.borrow_mut() {
    };
}
```

### Current output

```bash
error[E0308]: mismatched types
  --> src/main.rs:12:12
   |
12 |     if let Some(_content) = foo.content.borrow_mut() {
   |            ^^^^^^^^^^^^^^   ------------------------ this expression has type `RefMut<'_, Option<u64>>`
   |            |
   |            expected `RefMut<'_, Option<u64>>`, found `Option<_>`
   |
   = note: expected struct `RefMut<'_, Option<u64>, >`
                found enum `Option<_>`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `check_ice` (bin "check_ice") due to 1 previous error
```

### Desired output

It can suggest to deref the RefMut: 

```
if let Some(_content) = *foo.content.borrow_mut()
```

### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```
rustc 1.83.0-nightly (7042c269c 2024-09-23)
binary: rustc
commit-hash: 7042c269c166191cd5d8daf0409890903df7af57
commit-date: 2024-09-23
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```

### Anything else?

_No response_
Repository: create-react-app
Issue: Error: EPERM: operation not permitted, mkdir 
Labels: needs triage,issue: bug report


PS F:\ReactYoutubeThapa> npx create-react-app my-app
node:fs:1371
  const result = binding.mkdir(
                         ^

Error: EPERM: operation not permitted, mkdir 'F:\ReactYoutubeThapa\my-app'
    at Object.mkdirSync (node:fs:1371:26)
    at module.exports.makeDirSync (C:\Users\Sukhdev\AppData\Local\npm-cache\_npx\c67e74de0542c87c\node_modules\fs-extra\lib\mkdirs\ma
ke-dir.js:23:13)
    at createApp (C:\Users\Sukhdev\AppData\Local\npm-cache\_npx\c67e74de0542c87c\node_modules\create-react-app\createReactApp.js:257:
6)
    at C:\Users\Sukhdev\AppData\Local\npm-cache\_npx\c67e74de0542c87c\node_modules\create-react-app\createReactApp.js:223:9
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'mkdir',
  path: 'F:\\ReactYoutubeThapa\\my-app'
}

Node.js v20.18.0
PS F:\ReactYoutubeThapa>

Please help me
Repository: neovim
Issue: alternative to C for Nvim core
Labels: enhancement,architecture

This is a *tracking issue*, not a manifesto. Corrections welcome unless they are nit-picks.

# Problem

The C core of nvim has been armored by a lot of static analysis and compiler flags, which has greatly improved quality. But C still has these problems:

- crashes from invalid pointers, arrays not bounds-checked
- nul-terminated strings are awkward and have a perf cost
- memory management takes effort and asan doesn't detect all the leaks
- lack of modern language abstractions (e.g. generics) makes particular parts of the code over complicated and specialized (e.g. marktree, Lua/vimscript bridge).

# Goal

The strategy of Nvim has always been to lift logic out of C and into Lua where possible. And that still looks like a productive path. But if there is a "better C" which allows us to completely *freeze* the remaining C bits and shift to the "better C", at near-zero cost, then we should consider that.

C gives us the following benefits:

- broad cross-platform support
- fast builds
- leverage existing C codebase

# Proposal

This issue evaluates whether we can maintain the above benefits, while gaining new ones, by leveraging:

## rust

- pros
    - tooling
    - rich type system
    - borrow checker gives strong guarantees
    - language level macros
    - large collection of libraries 
- cons
    - slow build times
    - interop with C libraries has nonzero friction
    - mediocre cross-compiling support

## zig

- pros
    - comptime
      - replaces the Lua generator scripts that create C code (e.g. `gen_api_dispatch.lua`).
    - zero-friction interop with legacy C code/libraries
    - can easily cross-compile to mac/linux/win, from a single CI job
    - can replace CMake: https://github.com/neovim/neovim/pull/28344/
- cons
    - still in beta
    - tooling not as good as C or Rust (e.g. LSP)

## c++

- cons
    - conflicts with Lua's garbage collector, because it is garbage



---

previous: https://github.com/neovim/neovim/issues/8669
Repository: go
Issue: build: build failure on x_tools-gotip-openbsd-ppc64
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "x_tools-gotip-openbsd-ppc64" && repo == "tools" && mode == "build"
```

Issue created automatically to collect these failures.

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

    [I2024-10-05T13:11:52.865441Z 44778 0 sink.go:276] SinkServer: warm-up started
    [I2024-10-05T13:11:52.865543Z 44778 0 sink.go:346] SinkServer: starting HTTP server...
    [E2024-10-05T13:12:22.874476Z 44778 0 sink.go:278] SinkServer: warm-up failed: context deadline exceeded
    [I2024-10-05T13:12:22.874620Z 44778 0 sink.go:371] SinkServer: shutdown started
    [I2024-10-05T13:12:22.874708Z 44778 0 sink.go:349] SinkServer: HTTP server stopped with "http: Server closed"
    [I2024-10-05T13:12:22.874733Z 44778 0 sink_server.go:96] SinkServer: draining TestResult channel started
    [I2024-10-05T13:12:22.874778Z 44778 0 sink_server.go:98] SinkServer: draining TestResult channel ended
    [I2024-10-05T13:12:22.874792Z 44778 0 sink_server.go:100] SinkServer: draining Artifact channel started
    [I2024-10-05T13:12:22.874863Z 44778 0 sink_server.go:102] SinkServer: draining Artifact channel ended
    [I2024-10-05T13:12:22.874903Z 44778 0 sink.go:374] SinkServer: shutdown completed successfully
    [E2024-10-05T13:12:22.874964Z 44778 0 cmd_stream.go:405] rdb-stream: failed to run the test command: warm-up: context deadline exceeded
    warm-up: context deadline exceeded


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Peek activate only when keybind hold
Labels: Needs-Triage

### Description of the new feature / enhancement

Add additional setting to Peek that makes it to activate preview only when the keybinding is held down and immediately close when the keybinding is released.

### Scenario when this would be used?

Instead of doing two actions to open and close the file preview user would be able to just hold the key as long as he wants to see the file peek.

### Supporting information

_No response_