sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Build CPU only image
Labels: feature request,linux,docker

### What is the issue?

I'd be interested in only building a CPU docker image for ppc arch. I tried to do that for arm64 but it doesn't work perfectly either so I'm wondering if that is possible at all with only one big Dockerfile as it is now?

Ideally I'd like to have something like `PLATFORM=linux/arm64 TARGETARCH=arm64 DEVICE=cpu scripts/build_docker.sh`

Maybe someone can enlighten me how to do this.

Thank you!

### OS

Linux, Docker

### GPU

_No response_

### CPU

Other

### Ollama version

0.3.11
Repository: go
Issue: x/tools/gopls: source.doc code action: missing NewT func that returns unexported type t
Labels: gopls,Tools

The "Show documentation" code action has missing functions. Specifically, a function NewT that returns an instance of a type is grouped under that type as a "constructor" function. But if the type is unexported, neither the type nor its constructors are shown, even if they are exported.

Repro:

```
package a

type A int

func NewA() A { return 0 }

type a int

func Newa() a { return 0 }
```
<img width="800" alt="Screenshot 2024-09-20 at 10 24 36 AM" src="https://github.com/user-attachments/assets/9bd63356-2c76-450b-948f-423138fa8b82">
Repository: rust
Issue: wasm32-wasip1 depends on libc memset with no_std
Labels: T-compiler,O-wasm,C-discussion,O-wasi

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->

I've looked high and low between the WASM/WASI specifications and can't find what is the "correct" behavior here but the current rust behavior seems wrong to me.

I don't believe we should be trying to import memset from the "env" module:
```
(func $import0 (import "env" "memset") (param i32 i32 i32) (result i32))
```

[wasm3](https://github.com/wasm3/wasm3) engine can't run this code either due to this:

```bash
$ wasm3 target/wasm32-wasip1/release/wasm_br_test.wasm 
Error: missing imported function ('env.memset')
```

### Code

```Rust
#![no_std]
#![no_main]

#[no_mangle]
pub fn _start() {
    let _asdf = [0; 40];
}

#[panic_handler]
fn panic(_info: &core::panic::PanicInfo) -> ! {
    loop {}
}
```

### Cargo.toml
```toml
[lib]
crate-type = ["cdylib"]

[profile.release]
lto = true
#opt-level = 's'
opt-level = 0
codegen-units = 1
panic = "abort"
strip = true
```

### .cargo/config.toml
```toml
[build]
target = "wasm32-wasip1"


[target.wasm32-wasip1]
rustflags = ["-C", "link-arg=-zstack-size=65520",]
```


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.83.0-nightly (f79a912d9 2024-09-18)
binary: rustc
commit-hash: f79a912d9edc3ad4db910c0e93672ed5c65133fa
commit-date: 2024-09-18
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```

### wasm generated binary

```
(module
  (type $type0 (func (param i32 i32 i32) (result i32)))
  (type $type1 (func))
  (func $import0 (import "env" "memset") (param i32 i32 i32) (result i32))
  (table $table0 1 1 funcref)
  (memory $memory0 1)
  (global $global0 (mut i32) (i32.const 65520))
  (export "memory" (memory $memory0))
  (export "_start" (func $func1))
  (func $func1
    (local $var0 i32) (local $var1 i32) (local $var2 i32) (local $var3 i32) (local $var4 i32) (local $var5 i32) (local $var6 i32)
    global.get $global0
    local.set $var0
    i32.const 160
    local.set $var1
    local.get $var0
    local.get $var1
    i32.sub
    local.set $var2
    local.get $var2
    global.set $global0
    i32.const 160
    local.set $var3
    i32.const 0
    local.set $var4
    local.get $var2
    local.get $var4
    local.get $var3
    call $import0
    drop
    i32.const 160
    local.set $var5
    local.get $var2
    local.get $var5
    i32.add
    local.set $var6
    local.get $var6
    global.set $global0
    return
  )
)
```
Repository: ui
Issue: [feat]: Use tailwindcss-radix plugin for styling components
Labels: area: request

### Feature description

Use https://www.npmjs.com/package/tailwindcss-radix for styling components depending on the radix attributes
Using the plugin will improve intellisense and readability 

### Affected component/components

Tabs, sheet, toast, select, switch, toggle, popover, dialog, etc...

### Additional Context

I'm ready to contribute this

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: rust
Issue: rustdoc reports diagnostics against `very/../long/PATH.md` instead of normalizing to `PATH.md`
Labels: A-diagnostics,T-compiler,C-bug

The same repro as #130470 can be used here: https://github.com/fasterthanlime/readme-md-error-reporting

When running `cargo +stage1 t`, the output is:

```
---- src/../README.md - (line 5) stdout ----
error: expected `;`, found `}`
 --> src/../README.md:7:16
  |
3 |     let x = 234 // no semicolon here! oh no!
  |                ^ help: add `;` here
4 | }
  | - unexpected token
```

But I would argue it should be this:

```
---- README.md - (line 5) stdout ----
error: expected `;`, found `}`
 --> README.md:7:16
  |
3 |     let x = 234 // no semicolon here! oh no!
  |                ^ help: add `;` here
4 | }
  | - unexpected token
```

I would caution against using [canonicalize](https://doc.rust-lang.org/stable/std/fs/fn.canonicalize.html) — which resolves symbolic links etc. and requires the path to exist on disk right now, and rather advise that y'all simply have a state machine working on a stack of path elements, going through:

  * []
  * ["src"]
  * [] // just popped due to ".."
  * ["README.md"]
Repository: kubernetes
Issue: PodScheduled status.conditions field does not have an entry in `managedFields` for Pod
Labels: kind/bug,sig/node,triage/accepted

### What happened?

In the managed fields ownership for a Pod, no owner entry is present for `f.conditions: k:{"type":"PodScheduled"}`

### What did you expect to happen?

Based on https://github.com/kubernetes/kubernetes/blob/v1.31.1/pkg/kubelet/status/status_manager.go#L639-L640 I expect all these conditions to be owned by the `kubelet` manager.

### How can we reproduce it (as minimally and precisely as possible)?

Schedule a pod
`kubectl get pod -o yaml --show-managed-fields`
Look for `k:{"type":"PodScheduled"}` and it will not be present

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.29.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0
```

</details>


### Cloud provider

<details>
running on my local machine
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ uname -a
# paste output here
Linux kind-control-plane 6.6.26-linuxkit #1 SMP Sat Apr 27 04:13:19 UTC 2024 aarch64 GNU/Linux

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>
kind create cluster
</details>


### Container runtime (CRI) and version (if applicable)

_No response_

### Related plugins (CNI, CSI, ...) and versions (if applicable)

_No response_
Repository: deno
Issue: UX: Successful `deno install` should print something to terminal
Labels: feat

Currently, when a `deno install` command completes successfully you get no output. Whilst this is common in the unix ecosystem, it's uncommon in the JS one. Most JS developers likely expect a command to print out that it did something.

```sh
$ deno install 
$
```

We should print some sort of success message. Example

```sh
$ deno install
+ package-1
+ package-2
```

pnpm's output is quite good in that case.

Version: Deno x.x.x
Repository: vscode
Issue: Window is often its minimum size after starting VS Code
Labels: bug,windows,multi-monitor

On Windows I have a setup where my left monitor is 100% scale and my right monitor is 200% scale. I frequently move windows between the two, including moving maximized windows via win+shift+left/right.

Related: https://github.com/microsoft/vscode/issues/229154
Repository: pytorch
Issue: [pipelining] output shape validation / lazy inference
Labels: oncall: distributed

1) specific question about this function: is it even working for multi-stage schedules, or only single-stage schedules? what are its semantics?  it needs to be updated for stages that return more than one output tensor, also

```
def _validate_stage_shapes(pipeline_stages: List[PipelineStage]):
    """
    Check that the buffer shapes match between stages was expected by performing an all_gather between
    all stages.
    """
```

2) what is our plan for output shape handling? We may want validation logic if users optionally pass output shapes.  Or we may want to always use lazy shape inference and delete validation.  Currently we only support manual shape passing?

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @d4l3k @c-p-i-o
Repository: godot
Issue: FileDialog unable to be interacted with when launched from PopupWindow
Labels: bug,needs testing,topic:dotnet,topic:gui

### Tested versions

- Reproducible in 4.2.2 stable and 4.3 stable, untested in other versions

### System information

Godot v4.3.stable.mono - Windows 10.0.19045 - GLES3 (Compatibility) - Intel(R) UHD Graphics 620 (Intel Corporation; 25.20.100.6577) - Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz (4 Threads)

### Issue description

When launched from a PopupWindow, either directly or via callback, the FileDialog window cannot be closed, moved, or meaningfully interacted with.

### Steps to reproduce

In the MRP, click the "save" button to directly launch the FileDialog window (this should work). Click the "save with popup" button to launch a PopupWindow which can launch the FileDialog. This FileDialog exhibits the strange behavior.

### Minimal reproduction project (MRP)

[FileDialogIssueMRP.zip](https://github.com/user-attachments/files/17078093/FileDialogIssueMRP.zip)
Repository: vscode
Issue: opening inline chat near the top of a notebook editor will push cell content above scrollable viewport
Labels: bug,notebook-layout,notebook-cell-editor


Steps to Reproduce:

1. open a notebook with some content and scroll to the top
2. focus in the middle of the first cell and open the inline chat (ctrl + i)

:bug: part of the cell content can no longer be scrolled to
![image](https://github.com/user-attachments/assets/e6b61c4e-dfe3-406b-a9e1-ec0e81d52093)
Repository: go
Issue: x/tools/go/ssa: stop using deprecated x/tools/go/loader in unit tests
Labels: NeedsFix,Tools,Analysis,FixPending

```
ssa - @timothy-king
go/ssa/ssautil/switch_test.go
go/ssa/ssautil/load.go
go/ssa/example_test.go
go/ssa/interp/interp_test.go
go/ssa/builder_generic_test.go
go/ssa/builder_test.go

refactor/rename - these are deprecated anyway - see https://github.com/golang/go/issues/69538
refactor/rename/rename.go
refactor/rename/mvpkg.go
refactor/rename/spec.go
refactor/rename/check.go

eg - in progress https://go.dev/cl/616215
refactor/eg/eg_test.go

gcimporter - in progress https://go.dev/cl/614676
internal/gcimporter/iexport_test.go

objectpath - in progress https://go.dev/cl/614678 
go/types/objectpath/objectpath_test.go
go/types/objectpath/objectpath_go118_test.go

callgraph - https://go.dev/cl/614679
go/callgraph/cha/cha_test.go
go/callgraph/vta/helpers_test.go
go/callgraph/callgraph_test.go
go/callgraph/static/static_test.go
```
Repository: PowerToys
Issue: Crop And Lock
Labels: Needs-Triage

### Description of the new feature / enhancement

Hello,

I would like to suggest an improvement to the Crop and Lock feature. Currently, when I crop a window, the cropped section appears in a new window. However, I would prefer that the cropped area remains within the original window instead of generating a new one. To control this feature, an extra button could be added to the top bar of the window, allowing users to easily toggle the crop functionality on or off.

### Scenario when this would be used?

This feature would be particularly useful for users who work on a single screen and want to minimize distractions by focusing on a specific part of a window. The current functionality is likely designed with dual-screen or presentation setups in mind, but many users aim to improve their workflow by focusing on one screen while clearing away unnecessary elements. The ability to manage everything within one window would make the experience smoother and more efficient.

### Supporting information

If the option to keep the cropped area within the original window is not feasible or too complex, an alternative improvement could be to ensure that the second window is not just a visual display. The cropped section should remain functional, allowing users to interact with that area. For example, in the cropped section, users should be able to start or pause a video, or scroll through messages in a form. This would provide both a visual and functional experience for users.
Repository: pytorch
Issue: Runbook for GCP A100 runners should be updated
Labels: high priority,triaged,module: infra

### 🐛 Describe the bug

Right now there isn't anything in runbook about GCP runners and no alerts for it either
Current queue for linux.gcp.a100 is over a day and there are 0 runners with that label available although machines are up and running
![image](https://github.com/user-attachments/assets/edf71f0e-233a-4ed0-952a-1df3c540bd1f)


### Versions

Infra

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim
Repository: fastapi
Issue: Sponsor Badge CSS overflow issue on the docs
Labels: question

### Discussed in https://github.com/fastapi/fastapi/discussions/12218

<div type='discussions-op-text'>

<sup>Originally posted by **nat236919** September 19, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google "How to X in FastAPI" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
announce-wrapper .sponsor-badge {
    display: block;
    position: absolute;
    top: -10px;
    right: 0;
    font-size: 0.5rem;
    color: #999;
    background-color: #666;
    border-radius: 10px;
    padding: 0 10px;
    z-index: 10;
}
```


### Description

![image](https://github.com/user-attachments/assets/0b9cc528-d268-4e2f-b073-0988228ebd55)

Due to its absolute position and overflow setting, the text is trailing down creating an expected scroll. I think we can simply solve the issue by removing **position: absolute;**

### Operating System

Windows

### Operating System Details

_No response_

### FastAPI Version

NA

### Pydantic Version

NA

### Python Version

NA

### Additional Context

_No response_</div>
Repository: deno
Issue: node:child_process.kill(0) throws
Labels: bug,node compat

It should just do a `kill -0`, which just does error checking for the PID and doesn't actually send a signal. From https://man7.org/linux/man-pages/man2/kill.2.html:

>       If sig is 0, then no signal is sent, but existence and permission
>        checks are still performed; this can be used to check for the
>        existence of a process ID or process group ID that the caller is
>        permitted to signal.

This issue causes `nuxt dev` to error on exit:

```
 ERROR  [unhandledRejection] Unknown signal: 0                                                                                                                                                                                                                                                                                                                12:33:59 PM

  at toDenoSignal (ext:deno_node/internal/child_process.ts:387:11)
  at ChildProcess.kill (ext:deno_node/internal/child_process.ts:296:53)
  at kill (node_modules/nuxi/dist/chunks/dev.mjs:246:17)
  at Process.<anonymous> (node_modules/nuxi/dist/chunks/dev.mjs:291:7)
  at Object.onceWrapper (ext:deno_node/_events.mjs:518:26)
  at Process.emit (ext:deno_node/_events.mjs:405:35)
  at Process.emit (node:process:416:40)
  at Process.exit (node:process:61:13)
  at Process.<anonymous> (node_modules/nuxi/dist/chunks/index2.mjs:29886:42)
  at Object.onceWrapper (ext:deno_node/_events.mjs:516:28)
```
Repository: go
Issue: proposal: container/unordered: a generic hash table with custom hash function and equivalence relation
Labels: Proposal,Proposal-Hold

**Background:** In https://github.com/golang/go/issues/69420 I proposed to promote the [golang.org/x/tools/go/types/typeutil.Map](https://pkg.go.dev/golang.org/x/tools/go/types/typeutil#Map) data type to the go/types package, modernizing it with generics. @jimmyfrasche pointed out that really the only part of that proposal that needs to be in go/types is the `types.Hash` function, which should have semantics consistent with `types.Identical`: that is, identical types must have equal hashes. So, I reduced that proposal to just the hash function, and this proposal governs the table.

**Proposal:** the standard library should provide a generic hash table that allows the user to specify the hash function and equivalence relation. Here is a starting point for the API:


```go
package unordered // "container/unordered"

import "iter"

// Map[K, V] is a mapping from keys of type K to values of type V.
// Map keys are considered equivalent if they are.
type Map[K, V any] struct { ... }

// NewMap returns a new mapping.
// Keys k1, k2 are considered equal if eq(k1, k2); in that case hash(k1) must equal hash(k2).
type NewMap[K, V any](hash func(K) uint64, eq func(K, K) bool) *Map[K, V]

// All returns an iterator over the key/value entries of the map in undefined order.
func (m *Map[K, V]) All() iter.Seq2[K, V]

// At returns the map entry for the given key. It returns zero if the entry is not present.
func (m *Map[K, V]) At(key K) V

// Delete removes th//e entry with the given key, if any. It returns true if the entry was found.
func (m *Map[K, V]) Delete(key K) bool

// Keys returns an iterator over the map keys in unspecified order.
func (m *Map[K, V]) Keys() iter.Seq[K]

// Values returns an iterator over the map values in unspecified order.
func (m *Map[K, V]) Values() iter.Seq[V]

// Len returns the number of map entries.
func (m *Map[K, V]) Len() int

// Set updates the map entry for key to value, and returns the previous entry, if any.
func (m *Map[K, V]) Set(key K, value V) (prev V)

// String returns a string representation of the map's entries in unspecified order.
// Values are printed as if by fmt.Sprint.
func (m *Map[K, V]) String() string
```

Open questions:
- Should At and Set distinguish the "present but zero" and "missing" cases?
- Should we defend against hash flooding, complicating the hash function?
- Should we guarantee randomized iteration order?

Related:
- https://github.com/golang/go/issues/69420
- https://github.com/golang/go/issues/60630, its ordered cousin. The APIs should harmonize.
- https://github.com/golang/go/issues/69230, a generic set type. Again the APIs should harmonize.
Repository: pytorch
Issue: [pipelining] Improve recv buffer management
Labels: oncall: distributed

First, in #136243 it is annoying that I have to pass n_microbatches to prepare_forward/backward, since that value is only known by the Schedule class but I logically want to prepare the recv buffers lazily / later on inside stage._forward/backward APIs.

Second, it's not clear to me that we want to allocate N buffers when we are using an N microbatch schedule.  Better, couldn't we keep a maximum of Y buffers allocated, where Y <= N is the number of recvs that are active at a time in the schedule?  When we complete a recv and wait it, we could restore the buffer to the queue and then reuse it when receiving for another microbatch.    We'd store the in-use buffers in a dict, keyed by the active microbatch / chunk ID, and then move them from the dict into a queue of inactive buffers once they are out of use.

If we do this, then I think I can kill 2 birds- better peak memory, and delete the copypasta 'prepare_*_infra' calls from all the schedule classes.

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @d4l3k @c-p-i-o
Repository: material-ui
Issue: [Autocomplete] dropdown/popper fails to render when wrapped with a ThemeProvider setting default input slotProps on TextField.
Labels: package: material-ui,component: autocomplete

### Steps to reproduce

Steps:
1. Wrap `Autocomplete` with a `ThemeProvider` with the following theme defined:

```
let theme = createTheme({
  components: {
    MuiTextField: {
      defaultProps: {
        slotProps: {
          input: {
            sx: {
              margin: "10px",
            },
          }
        },
      },
    },
  },
});

<ThemeProvider theme={theme}>
  <Autocomplete
    disablePortal
    options={['hello']}
    renderInput={(params) => (
      <TextField
        {...params}
        label="type something"
      />
    )}
  />
</ThemeProvider>
```
2. Click on the input for Autocomplete and no dropdown/popper is displayed with the provided options.

### Current behavior

No dropdown/popper is displayed with the provided options. No runtime errors are incurred either.

### Expected behavior

Able to style `Autocomplete` `TextField` input at the theme level without negatively affecting its popper/dropdown from displaying.

### Context

I want the `Autocomplete` `TextField` input to be styled like every other `TextField` input within my application by using a given `ThemeProvider` to do so.

A similar issue was also encountered with [`DatePicker`](https://github.com/mui/mui-x/issues/14684).

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
  Binaries:
    Node: 22.9.0 - /usr/local/bin/node
    npm: 10.8.3 - /usr/local/bin/npm
    pnpm: Not Found
  Browsers:
    Microsoft Edge
      Version 129.0.2792.52 (Official build) (arm64)
    Google Chrome
      Version 128.0.6613.139 (Official Build) (arm64)
  npmPackages:
    @emotion/react: ^11.13.0 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/core-downloads-tracker:  6.1.1
    @mui/icons-material: ^6.1.1 => 6.1.1
    @mui/material: ^6.1.1 => 6.1.1
    @mui/private-theming:  6.1.1
    @mui/styled-engine:  6.1.1
    @mui/system:  6.1.1
    @mui/types:  7.2.17
    @mui/utils:  6.1.1
    @mui/x-date-pickers: ^7.18.0 => 7.18.0
    @mui/x-internals:  7.18.0
    @types/react:  18.3.8
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
```
</details>


**Search keywords**: Autocomplete popper ThemeProvider theme input slotProps