sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: LSP does not provide import completions for node modules packages with multiple export paths 
Labels: needs investigation,lsp

Deno Version : 2.0.6


LSP does not complete imports for non-index routes. 

![Screenshot 2024-11-14 at 9 54 54 AM](https://github.com/user-attachments/assets/7f0daf87-03e2-4ccd-8cb7-9469c94e11ae)
![Screenshot 2024-11-14 at 9 50 17 AM](https://github.com/user-attachments/assets/277e2c08-519a-413a-9693-1dd65e935a83)
![Screenshot 2024-11-14 at 9 51 41 AM](https://github.com/user-attachments/assets/e3dfea0a-8131-41cf-be23-26c819a60393)
Repository: tauri
Issue: [bug] CSP ignored when running `cargo tauri dev`
Labels: type: bug,status: needs triage

### Describe the bug

The CSP policies specified in the tauri config are not applied when running with `cargo tauri dev`. Running it with `cargo run` on the other hand does correctly apply this.

I checked this by setting `frame-src` and using and `iframe`.

### Reproduction

- Set CSP in config (e.g. `frame-src 'none'`)
- Run with `cargo tauri dev`

### Expected behavior

CSP is applied (e.g. iframe loading is prevented)

### Full `tauri info` output

```text
[✔] Environment
    - OS: Fedora 41.0.0 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.46.3
    ✔ rsvg2: 2.59.1
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 22.11.0
    - npm: 10.9.0

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.0
    - tao 🦀: 0.30.8
    - tauri-cli 🦀: 2.1.0

[-] Plugins
    - tauri-plugin-log 🦀: 2.0.2

[-] App
    - build-type: bundle
    - CSP: frame-src epub:
    - frontendDist: ../src
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: rust
Issue: candidate selection for normalization and trait goals disagree
Labels: A-type-system,P-low,I-types-nominated,T-types

```rust
#![feature(discriminant_kind)]
use std::marker::DiscriminantKind;

fn trait_bound<T: DiscriminantKind>() {}
fn normalize<T: DiscriminantKind<Discriminant = u8>>() {}

fn foo<'a, 'b>()
where
    &'b (): DiscriminantKind<Discriminant = u8>,    
{
    trait_bound::<&'a ()>();
}

fn bar<'a, 'b>()
where
    &'b (): DiscriminantKind<Discriminant = u8>,    
{
    normalize::<&'a ()>();
}
```
`foo`  compiles, `bar`  does not:
```
error: lifetime may not live long enough
  --> src/lib.rs:18:5
   |
14 | fn bar<'a, 'b>()
   |        --  -- lifetime `'b` defined here
   |        |
   |        lifetime `'a` defined here
...
18 |     normalize::<&'a ()>();
   |     ^^^^^^^^^^^^^^^^^^^ requires that `'b` must outlive `'a`
   |
   = help: consider adding the following bound: `'b: 'a`

error: lifetime may not live long enough
  --> src/lib.rs:18:5
   |
14 | fn bar<'a, 'b>()
   |        --  -- lifetime `'b` defined here
   |        |
   |        lifetime `'a` defined here
...
18 |     normalize::<&'a ()>();
   |     ^^^^^^^^^^^^^^^^^^^ requires that `'a` must outlive `'b`
   |
   = help: consider adding the following bound: `'a: 'b`

help: `'b` and `'a` must be the same: replace one with the other
```

Candidate selection for the trait goal prefers the trivial builtin impl. Normalization instead prefers the where-bound. This is inconsistent and means that whether we use the associated items impacts whether a trait bound holds. 

It impacts all trivial builtin traits with associated types, I don't think this effects stable rn as either the trait is unstable or the builtin impls only exist for unnameable types.  Nominating for t-types vibeck
Repository: PowerToys
Issue: after i changed my keybinds i wasnt able to change them back so now i cant use the keys u,h,j,k and i need help to fix it
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.86.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

after i changed my keybinds i wasnt able to change them back so now i cant use the keys u,h,j,k and i need help to fix it

### ✔️ Expected Behavior

for it to be reverted after i turned it off but it didnt

### ❌ Actual Behavior

i can no longer use u,h,j,k on my keyboard permanently 

### Other Software

_No response_
Repository: godot
Issue: CharacterBody3D with `floor_constant_speed` still slightly slower when going uphill
Labels: bug,topic:physics,needs testing,topic:3d

### Tested versions

Reproducible in:
- v4.3.stable.official [77dcf97d8]
- v4.4.dev4.official [36e6207bb]

### System information

Godot v4.3.stable - Debian GNU/Linux trixie/sid trixie - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600 (RADV NAVI33) - AMD Ryzen 5 7600 6-Core Processor (12 Threads)

### Issue description

`CharacterBody3D`s which have `floor_constant_speed` switched on don't quite maintain their ground speed when going uphill.

This causes bodies which are (in theory) moving in a circle to gradually slide down the hill.  The magnitude of the discrepancy seems to vary depending on the collision shape, thus characters which should follow the same path also gradually separate.

![Screenshot_20241114_191143](https://github.com/user-attachments/assets/8e9933f4-ce89-46cc-a0aa-16c4ce8e6c1b)

This is the repro scene, with four constant-speed `CharacterBody3D`s with different collision shapes. The numbers in the top-left are the bodys' speeds (difference in position frame to frame).  The `SeparationRay3D` with `slide_on_slope=false` is the only one which loops back to the start position (but follows a different path because it's not affected by the slope).

https://github.com/user-attachments/assets/840cfff4-84f7-4a76-bbd7-f651bc4b120b

You can see that the speeds are kept at around 4.0 when going downhill, but uphill they're consistently 3.99blah, and even reach 3.97blah.

### Steps to reproduce

1. Have a `CharacterBody3D` with `floor_constant_velocity=true`
2. Watch it move in a circle on a slope
3. :eyes: 

### Minimal reproduction project (MRP)

Self-contained scene:
[floor_constant_speed_isnt.zip](https://github.com/user-attachments/files/17756566/floor_constant_speed_isnt.zip)
Repository: flutter
Issue: [ios][platform_view][admob] Recycle admob banners
Labels: platform-ios,a: platform-views,P2,team-ios,triaged-ios

### Use case

A while back we compared the performance between Flutter and Native ad banners in a scrollable list. On native, it is very easy to recycle the ad banners like this: 

```
func viewDidLoad {
  cachedBanners = (0..<10).map { _ in 
    let banner = GADBannerView()
    banner.loadRequest()
    return banner
  }
}

func cellForRowAtIndexPath() {
  let banner = cachedBanner[indexPath.row];
  ...
}
```

Side note: in this native implementation, I load 10 requests upfront in `viewDidLoad`, which isn't ideal. It'd be great if we can improve it by loading it lazily. 


### Proposal

Recycle ad banners in Flutter. 

Potential work can be either (pending investigation): 

1. No change (maybe we already support it?). Though we will need to document how to do it. 
2. Change to AdMob plugin
3. Change to Flutter's platform view.
Repository: go
Issue: net/http: TestServerKeepAliveAfterWriteError/h1 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestServerKeepAliveAfterWriteError/h1"
```

Issue created automatically to collect these failures.

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

    === RUN   TestServerKeepAliveAfterWriteError/h1
        serve_test.go:4658: saw 2 unique client addresses; want 3
    --- FAIL: TestServerKeepAliveAfterWriteError/h1 (1.51s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: Only CPU is used after rebooting
Labels: linux,nvidia

[I found someone wrote a thread describing only cpu is used after rebooting in windows ](https://github.com/ollama/ollama/issues/4984#issue-2347076913) 
I also had similar problems even in Ubuntu OS. 

I used the latest version(0.4.1). I guess this bug comes from that the ollama service is started faster than the init. of GPUs. So I make an **ad-hoc** solution. Instead of service,  I just make a script delaying start serve(ollama serve). 

```bash
# ollama_run 
echo "Delayed Ollama Runner Start, it delays 10 sec."
sleep 10
ollama serve
```
Then I make this called from *Ubuntu Startup Application Preferences*. I think its delaying may not be needed as it is called after GPUs initialization is finished anyway.  
![capture 2024-11-15 042959](https://github.com/user-attachments/assets/80ca322d-49ea-4baa-991d-15b1413612ef)

**WARNING**: After starting ollama by calling directly `ollama serve`, model storage directory is changed to `~/.ollama/models`.(I don't know why?) So previously dowonloaded model is not loaded. In that case, you can copy or move whole models folder to '[home folder]/.ollama`  from `/usr/share/ollama/.ollama`.

_Originally posted by @3DAlgoLab in https://github.com/ollama/ollama/issues/4984#issuecomment-2477251430_
Repository: deno
Issue: Pass Dprint options directly from deno.json during deno fmt
Labels: suggestion,deno fmt

The Deno doc [here](https://docs.deno.com/runtime/fundamentals/linting_and_formatting/#formatting) says,

> The formatter can be configured in a [deno.json](https://docs.deno.com/runtime/fundamentals/configuration/) file. You can specify custom rules, plugins, and settings to tailor the formatting process to your needs.

but never says how. But it says the underlying formatter is Dprint, so presumably the above can be accomplished with the Dprint options documented [here](https://dprint.dev/plugins/typescript/config/).

But if you add any of those to deno.json, `deno fmt` complains.

This needlessly precludes the use of `deno fmt` for anyone who doesn't like the options it hard-codes outside the tiny subset that's allowed. For example, I can't prevent the formatter from messing up my braces and flow-control statements. But Dprint offers the exact options I want:

```
"bracePosition": "nextLine",
"nextControlFlowPosition": "nextLine"
```
Repository: tailwindcss
Issue: @property isn't supported in shadow roots
Labels: v4

**What version of Tailwind CSS are you using?**

For example: `4.0.0-alpha.34`

**What build tool (or framework if it abstracts the build tool) are you using?**

Web components with shadow roots.

**What version of Node.js are you using?**

v22.2.0

**What browser are you using?**

Chrome

**What operating system are you using?**

macOS

**Reproduction URL**

https://github.com/blittle/tw-shadow

**Describe your issue**

Tailwind v4 uses `@property` to define defaults for custom properties. At the moment, shadow roots do _not support_ `@property`. It used to be explicitly denied in the spec, but it looks like there's talk on adding it: https://github.com/w3c/css-houdini-drafts/pull/1085

I don't know if this is something tailwind should fix, but it took me a while to find the issue, so it's probably worth keeping this issue to document the limitation.

Here is a work-around, [just attaching the `@property` definitions to the base document](https://benfrain.com/using-css-property-inside-shadowroot-web-components-workaround/). It would be nice if tailwind provided an easy way to import just that content.

An easy way to do that with Vite is to create a tailwind css file specifically for the properties and apply a transform:

```js
export default defineConfig(() => {
  return {
    ...
    plugins: [
      tailwindcss(),
      {
        name: "tailwind-properties",
        transform(code, id) {
          if (id.endsWith("tailwind-properties.css?inline")) {
            // Change custom properties to inherit
            code = code.replaceAll("inherits: false", "inherits: true");

            // Remove everything before the property declarations
            code = code.substring(code.indexOf("@property"));

            return code;
          }
        },
      },
    ],
  };
});
```
Repository: react
Issue: [Compiler Bug]: Incorrect "Writing to a variable defined outside a component or hook is not allowed." error
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAgllgQL4EBmMEGBA5GgHYDWrA3ADodMOfERJkAwgEMANjIBGUuFwA04hBIgc8CAB6E6jZmxgIlePoOG5CxUggCiMJjABC0DgBMpMAJ60GJhZWU3MAWgRnXDD5D28-Sw4rbBsxLCYAcxgpDE1tPQNA41YAOgB6Th0YDlkwEoArMETBMoAqVsECVoJyAgAlMzhCAAsICC4GXAIlRDAwTgyiAAEZTgmABUzsjDpOMDwpDkRprwIAAz00PDOGKCO8NC0CPGGpQjQwdU9JmAIwUYA7gsTgRIi4CAAKABuaCkILBU1id3ivgAlCdvpcHhwMiVOq0yoI9CJCPQ7kNHhx1JsIFkchD0cBOgQZAhbH9Ae5kT5-HQALzqJwuLleHkMgRUllssRY5DTKgOXRXAIC+yULDi5ms9npWnbFXqPI6fQQ3V03JaY14VESrXSrEEVWSWQKJRcCHMgiQhEwOV3LgcCAAjjovkAPiInq9BF1szqWM0ngQjoIAEZbZLoxygyKURCfTao16pAqlXh81EYIXM7QVFGANolrCKq5qf45uI8gC6dcl1eZpjwsCpxDN2zUDpoEpoghANCAA

### Repro steps

1. Run ESLint with eslint-plugin-react-compiler enabled on the code from the repro and observe an error "Writing to a variable defined outside a component or hook is not allowed. Consider using an effect".

The error is caused by using `process.exitCode = 1` inside a `useCallback` hook, which does seem like a false positive. Or am I missing something? Thank you.

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

eslint-plugin-react-compiler@19.0.0-beta-a7bf2bd-20241110
Repository: vscode
Issue: Giving files as context to Copilot autocompletion
Labels: feature-request,inline-completions

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

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

I'd love it if it was possible to give files as context to the Copilot autocompletion, like you can for chat. I've found the options around [customizing the prompt](https://code.visualstudio.com/docs/copilot/copilot-settings#_customize-copilot-prompts) but my use case is that a lot of individual files in my codebase have a matching PDF spec, and I'd love to be able to give the spec as context for autocompletion in the individual files.
Repository: deno
Issue: deno compile: npm package node-red seems to not work
Labels: needs investigation,compile,node compat

deno 2.0.6 (stable, release, x86_64-pc-windows-msvc)
v8 12.9.202.13-rusty
typescript 5.6.2
current latest node-red: 4.0.5

# Steps to reproduce:

1. `deno install npm:node-red`
2. `deno run --allow-all npm:node-red --userDir ./nodeRedData` (seems to work fine)
3. delete the ./nodeRedData
4. `deno compile -o nodered.exe --allow-all npm:node-red --userDir ./nodeRedData`
5. `.\nodered.exe`

```powershell
PS F:\programming\deno-compile-test> .\nodered.exe
error: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'getTime')
    at Object.<anonymous> (file:///C:/Users/MY_NAME/AppData/Local/Temp/deno-compile-nodered.exe/.deno_compile_node_modules/localhost/node-red/4.0.5/red.js:145:36)
    at Object.<anonymous> (file:///C:/Users/MY_NAME/AppData/Local/Temp/deno-compile-nodered.exe/.deno_compile_node_modules/localhost/node-red/4.0.5/red.js:565:4)
    at Module._compile (node:module:745:34)
    at Object.Module._extensions..js (node:module:762:10)
    at Module.load (node:module:662:32)
    at Function.Module._load (node:module:534:12)
    at file:///C:/Users/MY_NAME/AppData/Local/Temp/deno-compile-nodered.exe/.deno_compile_node_modules/localhost/node-red/4.0.5/red.js:5:32
```

# My expectation

I expect the compile command to behave the same like the run command before. But it just throws an error.
Repository: svelte
Issue: Feat: `$effect.async`, `$derived.async`
Labels: runes

### Describe the problem

There have been several discussions about the issues of runes and `async`, for example, #13916. Many apps depend on async code, and it can become difficult to migrate to Svelte 5 because of this. 

### Describe the proposed solution

It would be useful to have two asynchronous runes: `$effect.async` and `$derived.async`. These functions would be asynchronous counterparts to `$effect` and `$derived.by`, respectively. Here's an example:
```js
let fetched = $derived.async(async()=>{
    let res = await fetch('./example.json');
    return await res.json(); 
});
$effect.async(async () =>{
    let asyncValue = await getAsyncValue();
    if(asyncValue === preferredAsyncValue) {
        runCallback(); 
    } 
}); 
```
You may notice that these functions do not require `await` to be called to use them, this would be because the `await` would be inserted at compile time:
```js
let thing = $derived.async(asyncValue);
$inspect(thing); 
//turns into
let thing = await $.derived_async(asyncValue); 
$.inspect_async(async() =>[await $.get_async(thing)]); 
```

### Importance

would make my life easier
Repository: react-native
Issue: Emojis inside <Text> increase line-height or stretch the element on iOS
Labels: Platform: iOS,Needs: Triage :mag:,Newer Patch Available

### Description

Reported previously in #18559. Emojis within `<Text>` elements are not aligned with other text in the same text element or other text elements on screen. They also cause the height of the `<Text>` to increase disproportionate to the `fontSize`.

As a workaround, the `fontFamily` of the emoji can be set to `System`. The referenced Snack shows this behavior. The emoji is rendered initially with the `Menlo` font family and overridden to `System` when the override button is pressed. When overridden, the strikethrough more closely aligns with the text, though is not perfectly aligned like on Android.

This issue no longer seems to be reproducible on Android.

### Steps to reproduce

1. Launch the Snack
2. Note that the strikethrough does not align with the emoji nor the text to the right
3. Click Override
4. Note that the strikethrough more closely aligns with the emoji and the text on the right

### React Native Version

0.76.1

### Affected Platforms

Runtime - iOS

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

```text
System:
  OS: macOS 14.7.1
  CPU: (16) arm64 Apple M3 Max
  Memory: 3.73 GB / 48.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.20.5
    path: /opt/homebrew/opt/node@18/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: /opt/homebrew/opt/node@18/bin/npm
  Watchman:
    version: 2024.11.11.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java: Not Found
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.1.2
    wanted: ^15.1.2
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.1
    wanted: 0.76.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
None
```


### Reproducer

https://snack.expo.dev/@mhoran/hazardous-orange-celery

### Screenshots and Videos

|Without override|With override|
|---|---|
|<img width="307" alt="Screenshot 2024-11-14 at 4 02 20 PM" src="https://github.com/user-attachments/assets/93945819-77c4-432d-882a-3d9c696b4d3d">|<img width="299" alt="Screenshot 2024-11-14 at 4 02 27 PM" src="https://github.com/user-attachments/assets/5425aac6-f001-4c3a-9332-01677f2b921d">|
Repository: rust
Issue: “Summary” button in docs doesn’t react to description being collapsed
Labels: T-rustdoc,C-bug,A-rustdoc-ui,T-rustdoc-frontend

<!--
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.
-->

If you collapse the description manually the summary button should change to “Show all” since otherwise it’d do nothing

### Meta

Observed on doc.rust-lang.org/nightly

https://github.com/user-attachments/assets/2bf0da56-ec3d-40a8-b237-90f3d813a144
Repository: next.js
Issue: Docs: Should App/ Page router switcher dropdown redirect to associate pages
Labels: linear: docs

### What is the documentation issue?

# Could this be a more clearer explanation

Hi I am sure this is a small nick pick  but we are in a progress of migrating from `Page router` to `App router `.
While looking through documentation for [route-segment-config](https://nextjs.org/docs/13/app/api-reference/file-conventions/route-segment-config) 

I notice that if you are on a  document page that is for `App` router features and then you select the dropdown to `Page` router. It still keep you at the `App` router related document. I think that could cause confusion on to new comers that some of the features from App router could work be in Pages router. 

Do you think it would be valuable to redirect  you to associate pages between router version switches. 





### Is there any context that might help us understand?

I notice that while comparing cache invalidation methods between pages router and the new app router.

Go to https://nextjs.org/docs/13/app/api-reference/file-conventions/route-segment-config 
In this example below, you are at App dir related docs


![Screenshot 2024-11-14 at 4 22 42 PM](https://github.com/user-attachments/assets/b391d3b2-dfe0-497f-a013-4454d585e9ea)

Try switching to Page router dropdown . 

![Screenshot 2024-11-14 at 4 22 36 PM](https://github.com/user-attachments/assets/64241056-3e3e-46a8-ae1b-86a7e1200f8c)

It will take you to the same page. Which IMO could cause confusion to new comers. 

If this is a issue and is something worth doing please let me know I would love to contribute in some ways. 

Thanks. 

### Does the docs page already exist? Please link to it.

https://nextjs.org/docs/13/app/api-reference/file-conventions/route-segment-config