sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Keyboard Manager mangles CloudPC keys
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.80.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

This is really obscure, but has been a nightmare to track down to PowerToys!

I had a customer running Azure, but when I was running a remote EMACS I discovered the right <ctrl> was adding an <esc> press in (making it unusable) so I used the PowerToys Keyboard manager to map the right <ctrl> to the left <ctrl>.  Solved the problem, great!

Roll on a few months and a new customer is running CloudPC, and my remote desktops are having intermittent keyboard problems.  Sometimes it thinks <ctrl> is pressed all the time, sometimes it thinks <esc> is being pressed when the right <ctrl> key is used and, most bizarrely, sometimes the ")" key stops working completely.  Yep, just that key.  The "0" character works fine.

Note that my local desktop behaves perfectly, only the remote desktop has the problem.

Usually just clicking around in my local desktop solves the remote desktop problem after about 10-20 minutes, and sometimes toggling the CloudPC screen to/from full screen/windowed fixes it (but not always).   Usually it returns after a few hours, or if I log out of the remote system and back in again.  Turning off the local PowerToys keyboard manager solved it.

Steps to reproduce?  It's very intermittent, but this  is what I was doing:

1) Use the PowerToys keyboard manager to map right <ctrl> to left <ctrl>
2) Use the Windows App to launch a remote CloudPC seesion
3) Use the remote desktop manager there to launch a further remote desktop 
4) Use EMACS for a few hours

I'm guessing that step 3 and 4 are not really necessary, but that's what I was doing.

### ✔️ Expected Behavior

They keys to work in remote CloudPC desktops as they do locally

### ❌ Actual Behavior

Intermittently the keys start misbehaving.  Once it starts it usually lasts about 10-20 minutes.  Symptoms are:

1) The remote desktop thinks <ctrl> is pressed continually (not sure which <ctrl>
2) The right <ctrl> adds an <esc> when pressed
3) the ")" character becomes disabled, it is ignored when typed

Bizarre huh?


### Other Software

Microsoft Windows App version 1.3.241.0
Repository: ollama
Issue: `llama3-chatqa` always returns `Empty reponse`
Labels: bug

# Problem
I've been toying around with RAG using `ollama` and `llama-index`. 
The results I am getting with `llama3 8b` are not that good, so I was happy to see `llama3-chatqa` being added in `v0.1.35`.

However, I always get "Empty response" using `llama3-chatqa`. Is there sth I am missing?

## Code
```py
from llama_index.core import VectorStoreIndex, SimpleDirectoryReader, Settings
from llama_index.embeddings.ollama import OllamaEmbedding
from llama_index.llms.ollama import Ollama

documents = SimpleDirectoryReader("data").load_data()

# Tested nomic-embed-text and mxbai-embed-large
Settings.embed_model = OllamaEmbedding(model_name="mxbai-embed-large")

#llama3 instead of llama3-chatqa can provide answers - though sometimes incorrect
Settings.llm = Ollama(model="llama3-chatqa", request_timeout=360.0)

index = VectorStoreIndex.from_documents(
    documents,
)

query_engine = index.as_query_engine()
response = query_engine.query(query)

# "Empty Response" always when using llama3-chatqa
```


### OS

Linux, Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.135, 0.136, 0.138
Repository: deno
Issue: `deno serve`: support using the fetch handler as the default export
Labels: suggestion,serve

In https://val.town, you declare a server by using the fetch handler as your module default export.

```ts
export default function(req: Request) {
   return new Response("hello world")
}
```

One interesting property is that it makes it easy to add middlewares on top of servers:

```ts
// cors.ts
export function cors(handler) {
    return async (req) {
       const resp = await handler(req)
       resp.headers.set("access-control-allow-origin", "*");
       return resp
    }
}

// cors_server.ts
import handler from "./server.ts"

export default cors(handler)
```

What do you think of adding support for this convention in `deno serve` ?
Repository: vscode
Issue: Add navigation buttons to test coverage elements
Labels: polish,testing,test-coverage

Type: <b>Feature Request</b>

When viewing a file containing test coverage lines it could be useful to offer quick navigation to the Test Coverage view and to the test run tree of the Test Results view.

![image](https://github.com/microsoft/vscode/assets/6726799/7763e265-2b72-413a-9a30-088201c0738c)

1. Click on the coverage bar in the Test Coverage Toolbar to reveal the Test Coverage view, which may currently be collapsed or invisible (e.g. in closed secondary side bar, or in view container that is hidden).
2. Add a "Results" button to the Test Coverage Toolbar that reveals the Test Results view if hidden, then focuses on the run whose coverage is currently open.
3. Add a "Results" button to the Test Coverage view's toolbar that reveals the Test Results view if hidden, then focuses on the run whose coverage is currently open.

VS Code version: Code - Insiders 1.90.0-insider (0cd8d6ac480bc5b4e2a2d7f1eb87eaff9f7d47e1, 2024-05-16T05:49:53.998Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: node
Issue: Bare specifiers definition.
Labels: doc,loaders

### Affected URL(s)

https://nodejs.org/docs/latest-v20.x/api/esm.html#terminology

### Description of the problem

"Bare specifiers like 'some-package' or 'some-package/shuffle'. They can refer to the main entry point of a package by the package name, or a specific feature module within a package prefixed by the package name as per the examples respectively. **Including the file extension is only necessary for packages without an "exports" field.**"

Incorrect,  including the file extension in bare specifiers is not necessary for packages with "main" field.

Example:

`index.mjs`:

```js
import * as module from 'mymodule'
module.greet();
```

`node_modules/mymodule/index.mjs`:
```js
export function greet() {
    console.log('Hello from module!');
}
```

`node_modules/mymodule/package.json`:
```json
{
  "name": "mymodule",
  "version": "1.0.0",
  "main": "index.mjs",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "description": ""
}
```

```shell
node index.mjs
```

Hello from module!
Repository: neovim
Issue: release checklist 0.11
Labels: project-management

(previous: https://github.com/neovim/neovim/issues/23235)

- [Release guidelines](https://github.com/neovim/neovim/blob/master/MAINTAIN.md#release-policy)
- [Dependencies](https://github.com/neovim/neovim/blob/master/MAINTAIN.md#third-party-dependencies)

# Blocking issues

<img width="446" alt="image" src="https://github.com/neovim/neovim/assets/1359421/032fc235-ed2e-4ce4-8198-86a9c5b20d84">


# Pre-release (early)

- [ ] run `scripts/download-unicode-files.sh`
- [ ] Bump deps in [cmake.deps/deps.txt](https://github.com/neovim/neovim/blob/master/cmake.deps/deps.txt)
    - [ ] run `scripts/bump_deps.lua` (luajit, luv, libuv, treesitter)
    - [ ] treesitter parsers (C, Lua, Viml, Vimdoc, Query)
        - [ ] update queries from nvim-treesitter
    - [ ] lpeg (also in `neovim/deps`)
    - [ ] libvterm (also in `neovim/deps`)
    - [ ] msgpack
    - [ ] [wintools](https://github.com/neovim/neovim/blob/9319d97679053a219b1701d70abce414d0f6a8b0/cmake.deps/deps.txt#L28-L36)
- [ ] check s930x CI logs for errors pertaining to big-endian systems

# Pre-release

- [ ] Run `make doc` so that prerelease functions are no longer [experimental](https://github.com/neovim/neovim/pull/30660#discussion_r1787852478).
- [ ] Remove deprecated functions marked for removal (`vim.deprecate(…, '0.11')`)
- [ ] Clean up `news.txt` (sorting, [phrasing](https://www.youtube.com/watch?v=Qs8Gohi1e04))
- [ ] Merge `nvim.appdata.xml` changes from the maintenance branch.
- [ ] Run `scripts/release.sh`

# Post-release

- [ ] For major releases, create a new `release-x.y` branch.
    - **Bump the version in CMakeLists.txt** and set `NVIM_VERSION_PRERELEASE`.
- [ ] Move `news.txt` to `news-x.y.txt` (and remove/update tags!). Recreate `news.txt` with "skeleton" from the old one.
- [ ] Review [revisit-at-release issues](https://github.com/neovim/neovim/labels/revisit-at-release)
- [ ] Newsletter https://github.com/neovim/neovim.github.io
- [ ] Update [GitHub Sponsors page](https://github.com/sponsors/neovim) (what was done, what is planned)
- [ ] Update [roadmap](https://neovim.io/roadmap/)
- [ ] Remove deprecated:
    - N/A

# Merge these after release

- N/A
Repository: ui
Issue: [bug]: Error: 'React' is not defined.  no-undef in sonner component
Labels: bug

### Describe the bug

eslint error on build on vercel, 

./src/components/ui/sonner.tsx
6:21  Error: 'React' is not defined.  no-undef
![image](https://github.com/shadcn-ui/ui/assets/81101648/d040a192-f38b-44aa-9326-ad7fb7b6d4c6)


### Affected component/components

Sonner

### How to reproduce

1. Try to deploy on vercel.

### Codesandbox/StackBlitz link

https://github.com/probir-sarkar/probir.dev

### Logs

_No response_

### System Info

```bash
Next.Js, Typescript, Vercel, Hosting
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: Tracking Issue for PanicHookInfo::payload_as_str()
Labels: T-libs-api,C-tracking-issue,disposition-merge,finished-final-comment-period,A-panic

Feature gate: `#![feature(panic_payload_as_str)]`

This is a tracking issue for PanicHookInfo::payload_as_str()

### Public API


```rust
// std::panic

impl PanicHookInfo {
    pub fn payload_as_str(&self) -> Option<&str>;
}
```

Documentation: https://doc.rust-lang.org/nightly/std/panic/struct.PanicHookInfo.html#method.payload_as_str

### Steps / History

- [x] Implementation: part of #115974
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- None yet.
Repository: PowerToys
Issue: pick colour *from palette* tool
Labels: Idea-Enhancement,Product-Color Picker

### Description of the new feature / enhancement

Hi, noob here.
I thought the Color Picker tool would let you pick colours from a palette (or 3 different kinds of palettes)
and was a little disappointed to find that it only picks colours that you can see on your screen.
I was hoping for a tool/feature similar to what you get if you type “color picker” into Google.
Is such a feature/toy somewhere on the horizon?
Thanks!

### Scenario when this would be used?

any time you wanted to pick a colour that wasn't already on your screen.

### Supporting information

_No response_
Repository: ollama
Issue: InternVL
Labels: model request

https://github.com/OpenGVLab/InternVL

thanks
Repository: storybook
Issue: [Bug]: Autodocs not working when a React component returns a portal
Labels: bug,react,has workaround,sev:S3,docgen

### Describe the bug

If a React component returns a portal created by `createPortal` from `react-dom`, Autodocs doesn’t retrieve the type information or JSDoc comments from the file.

### To Reproduce

https://stackblitz.com/edit/github-cj2wcx?file=src%2Fstories%2FButtonPortal.tsx

`ButtonPortal` is the same component as `Button`, but the returned value is wrapped in `createPortal`. See the difference between `Button/Docs` and `ButtonPortal/Docs`

### System

```bash
Local environment:


  System:
    OS: macOS 14.0
    CPU: (10) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
    pnpm: 9.1.1 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Edge: 124.0.2478.105
    Safari: 17.0
  npmPackages:
    @storybook/addon-actions: ^8.1.1 => 8.1.1 
    @storybook/addon-essentials: ^8.1.1 => 8.1.1 
    @storybook/addon-links: ^8.1.1 => 8.1.1 
    @storybook/addon-onboarding: ^8.1.1 => 8.1.1 
    @storybook/manager-api: ^8.1.1 => 8.1.1 
    @storybook/react: ^8.1.1 => 8.1.1 
    @storybook/react-vite: ^8.1.1 => 8.1.1 
    @storybook/theming: ^8.1.1 => 8.1.1 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0 
    storybook: ^8.1.1 => 8.1.1 
```

But it works the same way on Stackblitz
```


### Additional context

Is this normal/documented?
Repository: ollama
Issue: support image with url when chat with vison model
Labels: feature request,api

Hi thanks the Ollama team that made this helpful tool.

recently, chatgpt-4o api also support vision mode. they provide two method for uploading an image to the chat. one is encode the image to base64 that Ollama also use the same way. And another way is with url. with the url, chatgpt chat platform can automatically download the image and add to the chat.

Here is some descriptions about this functions in [offical API docs](https://platform.openai.com/docs/guides/vision)

> [Managing images](https://platform.openai.com/docs/guides/vision/managing-images)
The Chat Completions API, unlike the Assistants API, is not stateful. That means you have to manage the messages (including images) you pass to the model yourself. If you want to pass the same image to the model multiple times, you will have to pass the image each time you make a request to the API.
For long running conversations, we suggest passing images via URL's instead of base64. The latency of the model can also be improved by downsizing your images ahead of time to be less than the maximum size they are expected them to be. For low res mode, we expect a 512px x 512px image. For high res mode, the short side of the image should be less than 768px and the long side should be less than 2,000px.
After an image has been processed by the model, it is deleted from OpenAI servers and not retained. [We do not use data uploaded via the OpenAI API to train our models](https://openai.com/enterprise-privacy).

Is it possible to support this way in Ollama?
Repository: material-ui
Issue: [material-ui] Deprecate system props
Labels: component: Typography,deprecation,component: link,package: system,package: material-ui,component: Box,component: Stack

The RFC https://github.com/mui/material-ui/issues/41539

- [x] Add a codemod #42282 
- [x] Migrate the codebase #42475 
- [x] Update sections like https://mui.com/material-ui/react-stack/#system-props #42475
- [ ] Add deprecations to those components

**Search keywords**:
Repository: rust
Issue: rustdoc-json-types: Rename and document Impl::synthetic
Labels: T-rustdoc,C-enhancement,A-rustdoc-json

"synthetic" impls arn't a really a term that are used, especially in user-facing documentation. It's quite confusing to users that we use this to refer to [impl's of auto trait](https://rust-lang.github.io/rfcs/2963-rustdoc-json.html#kind--impl). It's lead to users beliving (and understandably so) that the JSON output doesn't contain wether an impl is auto or not. ([eg](https://github.com/rust-lang/rust/issues/91609#issuecomment-2111406847), CC @zjp-CN).

We should rename this field to something more descriptive. An ititial proposal would be `is_auto`, but I'm not sure this is quite right, as it's the *trait* that's auto, not the impl. I'm open to suggestions for the field name.

While we're at it, we should document it and add tests.
Repository: deno
Issue: `inspector_profile` integration test is flaky
Labels: flaky

```
---- inspector::inspector_profile stdout ----
command /Users/runner/work/deno/deno/target/debug/deno run --inspect-brk=127.0.0.1:9239 /Users/runner/work/deno/deno/tests/testdata/inspector/memory.js
command cwd /Users/runner/work/deno/deno/tests
STDERR: Debugger listening on ws://127.0.0.1:9239/ws/68e50d37-1787-4928-9746-d2cc1d09f784
STDERR: Visit chrome://inspect to connect to the debugger.
STDERR: Deno is waiting for debugger to connect.
thread 'inspector::inspector_profile' panicked at tests/integration/inspector_tests.rs:170:10:
recv() timeout: Elapsed(())
stack backtrace:
```

https://github.com/denoland/deno/actions/runs/9112777278/job/25052742560?pr=23846#step:44:2813
Repository: pytorch
Issue: Building libtorch for android fails
Labels: module: build,triaged,oncall: mobile,module: vulkan

### 🐛 Describe the bug

Building android fails:

I get errors regarding
```
Cannot find source file:

    ~/Android/Sdk/ndk/25.1.8937393/sources/third_party/vulkan/src/common/vulkan_wrapper.h
```

Apparently `vulkan_wrapper.[h/cpp]` haven't been part of ndk for a few versions...

### Versions

pytorch main branch

cc @malfet @seemethere
Repository: svelte
Issue:  Allow `textContent` / `innerHTML` / `innerText` binding without setting the `contenteditable` attribute
Labels: feature request

### Describe the problem

Svelte already allows you to create read-only bindings (e.g. [`<svelte:window bind:innerWidth />`](https://svelte.dev/docs/special-elements#svelte-window)).
But in the case of element content binding, the `contenteditable` attribute is required. Otherwise we get an error:

```
'contenteditable' attribute is required for textContent, innerHTML and innerText two-way bindings
```

[Svelte 5 (runes) example](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE0WMwQqDMBBEfyUsHhSE3tNU6D94a3qwyQoLuobsKi3iv5f0YI_z5s3sMNKEAvaxAw8zgoV7StCCflIJsuGkCC3IsuZQiJOQKWnn2euEaogZc49vNTdTiQ6KdVO6ilgSBq1Pobl6dpf_nF2kzbyIoz2d322PokWNtHXQwrxEGgkjWM0rHs_jCxQqNru1AAAA)

But this can be easily hacked by adding `contenteditable="false"`.

[Svelte 4 example](https://svelte.dev/repl/084f115cf895484a895ba938d395b676?version=4.2.17) (there is no example with Svelte 5 because of [this](https://github.com/sveltejs/svelte/issues/11653).)

### Describe the proposed solution

Remove the requirement of a mandatory `contenteditable` attribute for binding to element content.

### Importance

would make my life easier
Repository: godot
Issue: Importing a jpg image may result in wrong colors.
Labels: bug,needs testing,topic:import

### Tested versions

4.2.2.stable, 4.2.1.stable, 3.5.2.stable

### System information

Windows 10, Windows 11

### Issue description

When importing this jpg:
![album](https://github.com/godotengine/godot/assets/40838795/1f55b1b6-be32-4553-8edf-8f5fdd23f2f4)
the colors get messed up in the preview/editor and at runtime.
![image](https://github.com/godotengine/godot/assets/40838795/d5686125-3311-4ece-915a-d371bdf96f62)
This happens to any image in the zips downloaded from this site: https://www.enchor.us
The image can be found in the downloaded zip and is named `album.jpg`.

### Steps to reproduce

- Download provided image.
- Import into editor.
- Open image preview or drag into editor window.

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/15337051/MRP.zip)
Repository: opencv
Issue: Switch to FindPython3 in CMake (policy 0148)
Labels: feature,category: python bindings,category: build/install

### System Information

Details: https://cmake.org/cmake/help/latest/policy/CMP0148.html
Related Patch: https://github.com/opencv/opencv/pull/25585

### Detailed description

Current approach was deprecated with CMake

### Steps to reproduce

-

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: flutter
Issue: [webview_flutter] "Video playback policy Auto media playback" drive test failing often and blocking tree
Labels: a: tests,platform-android,p: webview,package,team-ecosystem,P2,c: disabled test,triaged-ecosystem

This test fails seemingly pretty often and is currently blocking the tree. Seems like it's causing the device to die or something
```
00:53 +0: loading /b/s/w/ir/x/w/packages/packages/webview_flutter/webview_flutter/example/integration_test/webview_flutter_test.dart                                                                   
...
01:01 +6: Video playback policy Auto media playback                                                                                                                                                    adb: device offline
 adb uninstall failed: ProcessException: Process exited abnormally with exit code 1:
 adb: device offline
   Command: /b/s/w/ir/cache/android/sdk/platform-tools/adb -s emulator-5554 uninstall io.flutter.plugins.webviewflutterexample
```

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1200/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1201/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1202/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1203/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1204/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20master/1199/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20master/1197/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20android_platform_tests_shard_6%20stable/1192/overview