sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Performing GET request to registry.ollama.ai/v2/ returns 404 page not found
Labels: bug

### What is the issue?

Background:

Kubernetes 1.31 introduced a new feature: [Read-Only Volumes Based on OCI Artifacts](https://kubernetes.io/blog/2024/08/16/kubernetes-1-31-image-volume-source/). I believe this feature could be very useful for deploying a dedicated model alongside Ollama in Kubernetes.

The currently supported container runtime is [CRI-O](https://github.com/cri-o/cri-o), which relies on [containers/image](https://github.com/containers/image) for all image-related operations. It uses a `GET` request to the following URL to [determine](https://github.com/containers/image/blob/main/docker/docker_client.go#L903) the appropriate schema: e.g. https://registry.ollama.ai/v2/.

I hardcoded the schema to `HTTPS` and used the Ollama image `registry.ollama.ai/library/tinyllama:latest` as the OCI image volume. After making some modifications to the modules consumed by CRI-O, I was able to get the pod and container running without any issues.

Please see the following logs:

```bash
❯ sudo crictl --timeout=200s --runtime-endpoint unix:///run/crio/crio.sock run ./container.json ./sandbox_config.json
INFO[0005] Pulling container image: registry.docker.com/ollama/ollama:latest 
INFO[0005] Pulling image registry.ollama.ai/library/tinyllama:latest to be mounted to container path: /volume 
7e437894449f6429799cc5ef236c4a4570a69e3769bf324bbf700045e383cae8
❯ sudo crictl --timeout=200s --runtime-endpoint unix:///run/crio/crio.sock ps
CONTAINER           IMAGE                                        CREATED             STATE               NAME                ATTEMPT             POD ID              POD
7e437894449f6       registry.docker.com/ollama/ollama:latest     8 seconds ago       Running             podsandbox-sleep    0                   4d1766fdf286b       unknown
❯ sudo crictl --timeout=200s --runtime-endpoint unix:///run/crio/crio.sock exec -it 7e437894449f6 bash
root@crictl_host:/# cd volume/
root@crictl_host:/volume# ls -l
total 622772
-rw-r--r-- 1 root root 637699456 Aug 26 08:32 model
-rw-r--r-- 1 root root        98 Aug 26 08:32 params
-rw-r--r-- 1 root root        31 Aug 26 08:32 system
-rw-r--r-- 1 root root        70 Aug 26 08:32 template
root@crictl_host:/volume# 
```

I'm wondering if the Ollama model registry could be slightly updated to handle requests to `registry.ollama.ai/v2/`. This would allow certain container runtimes to seamlessly integrate Ollama's OCI models without any issues.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.6
Repository: ollama
Issue: Embedding model     text2vec-large-chinese
Labels: model request

www.modelscope.cn/Jerry0/text2vec-large-chinese
Repository: material-ui
Issue: [code-infra] Clean up bundle size names
Labels: scope: code-infra

From https://www.notion.so/mui-org/code-infra-Cleanup-bundle-size-tracker-names-af489e26331c4faa9e44a81ee4e1f06f

Assuming https://github.com/mui/material-ui/blob/92ff1fc67c1c999a9c92bdeb0f3ce6bbc173ee58/scripts/sizeSnapshot/webpack.config.js#L72-L73 is not useful for us anymore.

- Rename the bundle ids:
  - `@material-ui/core` => `@mui/material`
  - etc...

- Remove https://github.com/mui/material-ui/blob/92ff1fc67c1c999a9c92bdeb0f3ce6bbc173ee58/scripts/sizeSnapshot/webpack.config.js#L13-L20

**Search keywords**:
Repository: PowerToys
Issue: Keyboard chatter blocker
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Include keyboard chatter blocker, similar to the https://github.com/mcmonkeyprojects/KeyboardChatterBlocker

### Scenario when this would be used?

Any mechanical keyboard can produce chatter

### Supporting information

_No response_
Repository: material-ui
Issue: [system] Remove createUseThemeProps, RtlProvider, DefaultPropsProvider, useDefaultProps API
Labels: priority: important,package: system

### Summary

From https://github.com/mui/material-ui/pull/40648#issuecomment-1961591574

> This PR aims to remove the usage of React context to make some components RSC compatible while having backward compatible with emotion.

What's the use case to have RSC compatible components? We use the Badge in the PR, but I guess it's not the objective (I don't see why a developer would want this with his component, there would be no state change animations, the onClick listener wouldn't works, etc.), but I guess the Badge is meant as a supplement for layout components. For instance, it makes a lot of sense to me with a `<Container>` with a different default layout mode propagated with the context or for a static content: https://github.com/mui/mui-x/issues/12180).

Now, I don't think this change is needed, we can have context (maybe with nesting support but not sure) https://github.com/emotion-js/emotion/issues/2978#issuecomment-1935131675. 

> Trade-off

But them, how can we support theme nesting? I don't see this mentioned, but I think it matters. For example, how is the documentation of Material UI supposed to be able to show components in their default form while the docs has a MUI branded theme?

At first sight, I would recommend:

- We revert this PR.
- We introduce a server side theme, to live in the server bundle, alongside the a client bundle theme. We need this anyway to get RSC support with Emotion. 
- We update the theme provider and theme customer to support both theme locations.

This way, we get:

- No theme propagation feature regression on the client bundle, theme nesting continues to work. On the server bundle, the theme nesting mighty not work, it depends on how React calls the cache API, but I wouldn't expect it to be achievable. Maybe one-day if React introduce a true context RSC API.
- The foundations for Emotion with RSC.

Opportunity moved to https://github.com/mui/material-ui/issues/43443 


**Search keywords**: 

**Search keywords**:
Repository: rust
Issue: `#[repr()]` is allowed where it shouldn't
Labels: A-attributes,T-lang,T-compiler,C-bug,A-repr

<!--
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.
-->

I tried this code:

```rust
#[repr()] const CONST: u32 = 8;
#[repr()] struct Struct;
#[repr()] trait Trait {}
#[repr()] impl Trait for Struct {}
#[repr()] fn func() { #[repr()] let a = 4; }
```

I expected to see this happen: #[repr] doesn't make sense on other than struct/enum/union, so it shouldn't be permitted. Every case except the `struct` should be an error. Not sure if that one ought to be legal either, but I guess the current warning is enough there.

Instead, this happened: Plenty of unused attribute warnings, but it compiles.

### Meta
Tested on [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=bef7acb458748796dba32d5be738999f), both `1.80.1` and `1.82.0-nightly (2024-08-24 f167efad2f51088d8618)`.
Repository: godot
Issue: after update to Godot 4.3 frequent in-game freezes
Labels: bug,needs testing

### Tested versions

Reproducible in: 4.3.0
Not reproducible in: 4.2.x

### System information

Linux, X11 Godot 4.3.0 using Forward+

### Issue description

After update to Godot 4.3, my game project is starting to randomly freeze in-game (never the editor, even if it has a lot of `@tool`)
it just stops drawing and hitting pause to open the debugger (or opening remote explorer) in the editor has no effect, while the stop button works.

the only visible thing that might give some information, is that when it freezes it starts to output on log (when starting godot from the terminal) the message:

    Object was deleted while awaiting a callback.

this message is repeated thousands upon thousands of times, which seems to happen in message_queue.cpp, line 406

### Steps to reproduce

just start playing the game for a while, and the total freeze happens after one-two minutes

### Minimal reproduction project (MRP)

Unfortunately it seems to happen only in my project, which is rather big, so i wouldn't know exactly how to do a minimal project that shows the problem (doesn't seem to happen on the official example projects)

I can rebuild Godot itself and add more debug or breakpoints in godot itself, if it might help.
Repository: deno
Issue: DX: Permissions prompts don't have "deny all" setting
Labels: permissions

When you first run something with Deno, you'll likely encounter a permission prompt. In this case I've been running the `npm:create-next-app` package and the first thing it asks is for permission to access environment variables.

```sh
$ deno run npm:create-next-app@latest my-next-app
┏ ⚠️  Deno requests env access to "NO_COLOR".
┠─ Learn more at: https://docs.deno.com/go/--allow-env
┠─ Run again with --allow-env to bypass this prompt.
┗ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all env permissions) >
```

The prompt gives me three options:

1. Allow
2. Deny
3. Allow all

But there is not `Deny All` option. I can deny it for this particular env variable, but since it's asking for 20 more it's a bit tedious. The only way a user can address this is by clicking on the link, (hopefully) learning about `--deny-env` and passing that to the command prompt.

This makes me wonder if it would be easier if we had a `deny all` option in the prompt.
Repository: flutter
Issue: New Material 3 `Slider` specs breaks overlay
Labels: framework,f: material design,c: proposal,P2,team-design,triaged-design,dependency: material

### Use case

New Material 3 `Slider` specs doesn't provide overlay color anymore and it is also missing the tokens database.

<img width="955" alt="image" src="https://github.com/user-attachments/assets/932c9347-14e1-4ccc-b75b-555dc64c4030">

I can confirm Android components Slider also missing overlay in light mode and but not in dark mode on Android. However, when running the same demo on Android 15, overlay is also missing in dark mode.

In Flutter, without Slider overlay there is no way to indicate the user if a Slider is hovered, focused, highlighted. I decided to NOT remove overlay in https://github.com/flutter/flutter/pull/152237 to avoid breaking such visual indicators and accessibility support.

### Proposal

Update `Slider` overlay when there is more information on the Slider overlay design and it's implications in Flutter.
Repository: terminal
Issue: Getting a large dump of "^[[D" to the terminal on click in WSL Ubuntu Dev
Labels: Issue-Bug,Area-TerminalControl,Product-Terminal

### Windows Terminal version

1.22.2371.0

### Windows build number

10.0.22635.4076

### Other Software

_No response_

### Steps to reproduce

Running WSL2 C:\Windows\system32\wsl.exe -d Ubuntu.

Having "Automatically mark prompts on pressing Enter" enabled.  

Have long running job. "find ." or "docker-compose up"

Clicking the terminal.


### Expected Behavior

Nothing to be added.

### Actual Behavior

Clicking the terminal causes a large dump to terminal. 

If I turn "Automatically mark prompts on pressing Enter" off it goes away.

![image](https://github.com/user-attachments/assets/1ad2cc4d-a80e-415c-98af-4fa20636b3de)
Repository: next.js
Issue: Next 14 App router AsyncLocalStorage From middleware to server component
Labels: bug,Middleware

### Link to the code that reproduces this issue

https://github.com/KevinEonix/next-asyncLocalStorage

### To Reproduce

1. start npm run dev
2. access the default page
3. message rendered is `Context is undefined :(`

### Current vs. Expected behavior

The phrase should be `test value in store is test value`

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32370
  Available CPU cores: 12
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.6 // Latest available version is detected (14.2.6).
  eslint-config-next: 14.2.6
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Middleware

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I tested that on an other project and have the same problem (same machine sane versions)
Repository: pytorch
Issue:  linalg.lu_factor: LU without pivoting is not implemented on the CPU
Labels: module: cpu,triaged,module: linear algebra,actionable

### 🐛 Describe the bug

```python

import torch
print(torch.__version__)
A = torch.tensor([
        [1,1,1],
        [1,2,2],
        [1,2,3]
    ], dtype=torch.float32)
l, u = torch.linalg.lu(A, pivot = False)
```

returns 
```bash
2.4.0+cpu
Traceback (most recent call last):

  File C:\Python\Python39\lib\site-packages\spyder_kernels\py3compat.py:356 in compat_exec
    exec(code, globals, locals)

  File untitled0.py:18
    l, u = torch.linalg.lu(A, pivot = False)

RuntimeError: linalg.lu_factor: LU without pivoting is not implemented on the CPU
```
Would there be a difference between GPU and CPU implementation?
### Versions

2.4.0+cpu


cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: ui
Issue: [feat]: tree view component with drag & drop
Labels: area: request

### Feature description

A tree view component with drag & drop functionality (to move around files and folders), something like [minop1205/react-dnd-treeview](https://minop1205.github.io/react-dnd-treeview/?path=/docs/basic-examples-custom-drag-preview--custom-drag-preview-story)

I see that it's been requested before in the past as well
https://github.com/shadcn-ui/ui/issues/1875 and https://github.com/shadcn-ui/ui/issues/355

### Affected component/components

_No response_

### Additional Context

[@atlassian/pragmatic-drag-and-drop](https://github.com/atlassian/pragmatic-drag-and-drop) seems like a good contender to implement this kind of functionality.

Checkout their [tree view](https://atlassian.design/components/pragmatic-drag-and-drop/examples/#tree) example.

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: opencv
Issue: How to build static library for iOS?
Labels: category: documentation

### Describe the doc issue

Hi there. 

The [Doc](https://docs.opencv.org/4.x/d5/da3/tutorial_ios_install.html) only shows how to build a framework. Is there any way to build static library?

### Fix suggestion

_No response_
Repository: PowerToys
Issue: Something went wrong.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0.0

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

Apparently something went wrong while I was not using the system. I signed on and saw this message.
![image](https://github.com/user-attachments/assets/574a5722-fd81-4195-baeb-01cca6beea77)
[2024-08-22.txt](https://github.com/user-attachments/files/16748725/2024-08-22.txt)


### ✔️ Expected Behavior

Not to see an error message when I logged onto my PC.

### ❌ Actual Behavior

No additional information available.

### Other Software

_No response_
Repository: material-ui
Issue: [material-ui] [Stepper] Connecting line issues when label is a long string
Labels: support: question,waiting for 👍,component: stepper,customization: css

### Steps to reproduce

Link to live example: https://stackblitz.com/edit/react-cemc8z?file=Demo.tsx

Resize the preview to a small mobile size


### Current behavior

![image](https://github.com/user-attachments/assets/6c9bc1cd-dd09-484f-b289-860cbaeedccc)

### Expected behavior

- The first connecting line does not clip into the first step button
- The connecting line after step 2 has some more spacing
- The connecting line after step 3 starts sooner

Basically that it looks like if it was on desktop, just with shorter lines/more compressed.

### Context

I'm trying to use the stepper with horizontal scrolling, which works fine, just causes these visual artifacts

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.6.1
  Binaries:
    Node: 22.7.0 - /opt/homebrew/bin/node
    npm: 10.8.2 - /opt/homebrew/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Chromium: 130.0.6677.0 <-- used
    Edge: Not Found
    Safari: 17.6 <-- used
    Firefox: 129.0.2 <-- used
```
</details>


**Search keywords**: stepper, alternativeLabel, lines
Repository: next.js
Issue: [15.0.0-canary.111+] Infinite loading page when fetch has "force-cache" in generateMetadata layout.tsx
Labels: bug,Metadata

### Link to the code that reproduces this issue

https://github.com/aXenDeveloper/next-app-canary

### To Reproduce

1. Clone repo,
2. `pnpm i`,
3. Start app with `pnpm dev`

or

1. `pnpm create next-app@canary`
4. In `src/app/layout.tsx` replace `metadata` to:   
    ```tsx
    export const generateMetadata = async (): Promise<Metadata> => {
      await fetch("http://localhost:8080/graphql", {
        cache: "force-cache"
      });
    
      return {
        title: "Create Next App",
        description: "Generated by create next app"
      };
    };
    ```

### Current vs. Expected behavior

Loaded home page.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:36 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: N/A
  pnpm: 9.10.0
Relevant Packages:
  next: 15.0.1-canary.2 // Latest available version is detected (15.0.1-canary.2).
  eslint-config-next: N/A
  react: 19.0.0-rc-45804af1-20241021
  react-dom: 19.0.0-rc-45804af1-20241021
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

When fetch has "force-cache" inside `generateMetadata()` and API has fetch error then page will have infinite loading.

```tsx
export const generateMetadata = async (): Promise<Metadata> => {
  await fetch("http://localhost:8080/graphql", {
    cache: "force-cache"
  });

  return {
    title: "Create Next App",
    description: "Generated by create next app"
  };
};
```

It happens from `15.0.0-canary.111`+.
`15.0.0-canary.110` works fine.
Repository: terminal
Issue: We should recurse upwards when looking for local snippets
Labels: Product-Terminal,Issue-Task,Needs-Tag-Fix,Area-Suggestions

#17388 only supported the exact current directory for looking for snippets. 

We should instead support looking for snippets recursively from the CWD, and layering top-down (so snippets in subdirs overwrite ones in higher dirs). 
(as spec'd in #17329)
Repository: material-ui
Issue: [code-infra] Migrate `aws-sdk` to v3
Labels: priority: low,scope: code-infra

### Steps to reproduce

Check CI output: https://app.circleci.com/pipelines/github/mui/material-ui/137230/workflows/fcd89719-5dcd-4394-aac0-9bc600d5519b/jobs/739730/parallel-runs/0/steps/0-105?invite=true#step-105-2740_89

```
.../node_modules/aws-sdk postinstall: ╔═════════════════════════════════════════════════╗
.../node_modules/aws-sdk postinstall: ║ The AWS SDK for JavaScript (v2) will reach      ║
.../node_modules/aws-sdk postinstall: ║ -> maintenance mode on September 8, 2024.       ║
.../node_modules/aws-sdk postinstall: ║ -> end-of-support on September 8, 2025.         ║
.../node_modules/aws-sdk postinstall: ║                                                 ║
.../node_modules/aws-sdk postinstall: ║ To continue receiving updates to AWS services,  ║
.../node_modules/aws-sdk postinstall: ║ bug fixes, and security updates please upgrade  ║
.../node_modules/aws-sdk postinstall: ║ to AWS SDK for JavaScript (v3).                 ║
.../node_modules/aws-sdk postinstall: ║                                                 ║
.../node_modules/aws-sdk postinstall: ║ More info: https://a.co/cUPnyil                 ║
.../node_modules/aws-sdk postinstall: ╚═════════════════════════════════════════════════╝
```

### Current behavior

_No response_

### Expected behavior

_No response_

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: aws-sdk
Repository: tailwindcss
Issue: Duplicate ellipsis in Safari when using `<sup>` or `<sub>` tags
Labels: browser bug

<!-- Please provide all of the information requested below. We're a small team and without all of this information it's not possible for us to help and your bug report will be closed. -->

**What version of Tailwind CSS are you using?**

v3.4.10

**What build tool (or framework if it abstracts the build tool) are you using?**

N/A

**What version of Node.js are you using?**

N/A

**What browser are you using?**

Safari

**What operating system are you using?**

macOS

**Reproduction URL**

https://play.tailwindcss.com/cUuJcAdOkx

**Describe your issue**

When loading the above reproduction in Safari, the text is truncated with multiple sets of ellipsis. It appears to be happening due to the `position: relative` styling of the `<sup>` and `<sub>` tags.

Screenshot:
![image](https://github.com/user-attachments/assets/6075dbe7-f8f7-48d2-ba08-9ad890345661)
Repository: ui
Issue: Docs: Add categories to components
Labels: area: request

### Feature description

Currently it is hard to browse components from the list:
![component_list](https://github.com/user-attachments/assets/63b8f291-81ee-4e1b-9037-3d020d940fb8)

We can divide the components into categories for easy navigation.
Can take inspirations from [Material UI](https://mui.com/material-ui/)

![mui_components](https://github.com/user-attachments/assets/362f1c87-e52d-4a9f-ac10-9f4aaaea41ab)


### Affected component/components

N/A

### Additional Context

_No response_

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs