sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: Svelte 5: structuredClone tries to clone proxy object instead of its contents
Labels: needs discussion

### Describe the bug

Attempting to use `structuredClone` on any stateful object will result in an error with zero indication of a problem before running the code in both JavaScript and TypeScript.

### Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACm2QwUrEQAyGXyVEobtQ2nu3LojiwYvHPTgeujPpOjqblJmMq5S-uwwLHoq35OP7_0BmHH2ghN3rjDycCTu8nyasUX-msqQvCkpYY5IcbSF9stFPujdsNJBCThThDm6TDkqbuWCjpaoDg8_yzvAoZLDwZbszXAYrnCRQE-S0KfntDtoWDhI_E4ye6T-nKZ1rEYYEFwphHUgas9UcyT0EYboeuYafBh_IgQrQN9msBNXKrkAYqoNnJ5eqg5v-5fhBVvdgJQcHLApHAltU1xju27-PYI1ncX705LDTmGl5W34BHhXdL2IBAAA=

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700KF
    Memory: 48.76 GB / 63.85 GB
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.3.0 - ~\AppData\Local\pnpm\pnpm.EXE
    bun: 1.1.30 - ~\.bun\bin\bun.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    svelte: ^5.0.0-next.264 => 5.0.0-next.264
```


### Severity

annoyance
Repository: electron
Issue: [Bug]: HTML select tag not rendering the dropdown
Labels: platform/macOS,31-x-y

I'm reopening as this is consistently still an issue and I know adding comments to old closed issues (https://github.com/electron/electron/issues/29665) isn't very effective in exposing issues that have reoccurred – more details coming shortly.


### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version
31.x

### What operating system are you using?
Mac

### What arch are you using?
x64

### Last Known Working Electron version
30.*.* (See [comment](https://github.com/electron/electron/issues/29665#issuecomment-2250003376))

### Expected behavior
When you add a select tag to your HTML and you click on it should open a dropdown with the options.

### Actual behavior
When you click the select but no dropdown appears. Reported and fixed previously in https://github.com/electron/electron/issues/29665 back in 2021. Some users have reported that disabling then re-enabling hardware acceleration fixed it for them.
Repository: rust
Issue: `rustdoc` lint to flag potential intra-doc links
Labels: T-rustdoc,A-lints,C-feature-request,A-intra-doc-links,A-rust-for-linux

One of the common review comments in the Linux kernel is that there is a missed intra-doc link. It would be nice to have a lint (or two) to flag these cases automatically. In addition, such a lint would help new Rust developers become aware of what intra-doc links are.

There are two cases: the potential intra-doc link has backticks already, or it does not even have backticks (i.e. it was not even formatted properly using Markdown). Examples taken from LKML reviews:

```rust
/// Flags passed to `XArray::new` to configure the `XArray`.
/// Flags passed to [`XArray::new`] to configure the [`XArray`].
```

```rust
/// Converts the whole CString to lowercase.
/// Converts the whole [`CString`] to lowercase.
```

Both cases will probably have false positives and thus projects may want to trigger them as an opt-in build mode (e.g. in the kernel we may run with a bigger set of warnings enabled to spot potential cleanups).

Due to the false positives, it may make sense to allow projects to customize what kind of "kinds" of entities to run it for, especially for the no-backticks case. For instance, for types or constants with multi-word names in projects following the usual naming conventions (e.g. `MyType` or `MY_CONSTANT`), false positives may be unlikely. If someone has written "Returns MyType", then it is likely the lint applies; however, if they wrote "This item may run something" it is likely they didn't mean to link to a function called `run`.

Additionally, users may want to run the no-backtick lint even if they do not want to actually add intra-doc links, since it could spot missing backticks (i.e. bad formatting) with less false positives (since the compiler has more information). Clippy has a related lint, [`doc_markdown`](https://rust-lang.github.io/rust-clippy/master/index.html#/doc_markdown), which helps identifying missing backticks.

These lints could be part of Clippy, but `rustdoc` already knows what could be an intra-doc link or not.

Cc @GuillaumeGomez

@rustbot label T-rustdoc
@rustbot label A-intra-doc-links
@rustbot label A-rust-for-linux
Repository: rust
Issue: Tracking Issue for GPU-offload
Labels: T-lang,T-compiler,T-bootstrap,C-tracking-issue,F-gpu_offload

<!--
Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for the GPU offload experiment.

The feature gate for the issue will be `#![feature(gpu_offload)]`.

This work is part of the [project goal](https://rust-lang.github.io/rust-project-goals/2024h2/Rust-for-SciComp.html) for Scientific Computing in Rust.
This project will use LLVM's offload infrastructure, which is already used to support OpenMP Offload in other languages like C++.


### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->
- [x] Get lang experiment approved.
    - We approved this in the lang triage meeting on 2024-05-01.
- [ ] Land the experimental implementation in nightly. 
    - https://github.com/rust-lang/rust/pull/131527 
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions
TODO.

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
Repository: ollama
Issue: Qwen 2.5 72B missing stop parameter
Labels: bug

### What is the issue?


Often doesn't stop generating... 

![telegram-cloud-photo-size-5-6071353675453939699-x](https://github.com/user-attachments/assets/0e5bb916-068c-44d8-88b8-797fa1e77b0e)

PARAMETER stop 


seems to be missing in the model configuration. Adding it solved the problem. 

### OS

Ubuntu 22.04.5 LTS (but ollama runs in official docker container)

### GPU

2 x RTX 4090

### CPU

AMD Ryzen 9 7950X

### Ollama version

0.3.12
Repository: rust
Issue: Tracking Issue for `const_is_char_boundary`
Labels: T-libs-api,C-tracking-issue

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

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

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

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

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

This is a tracking issue for using `str::is_char_boundary` in `const`, which allows checking that `index`-th byte is the first byte in a UTF-8 code point sequence or the end of the string during const-eval.

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

### Public API

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

```rust
// core::str
impl str {
    pub const fn is_char_boundary(&self, index: usize) -> bool;
}
```

### Steps / History

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

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

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

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

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

### Unresolved Questions

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

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

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: go
Issue: all: end support for macOS 11 in Go 1.25
Labels: Proposal,Proposal-Accepted,early-in-cycle

### Proposal Details

Go added support for macOS 15 that was publicly released this September. After internal discussion, we believe the summer of 2025 will be a good time to drop support for macOS 11. The last security update it received was in [September 2023](https://support.apple.com/en-us/106365).

On behalf of @golang/release, I propose we announce the end of support in the Go 1.24 release notes, and disable the builder for Go 1.25. Go 1.24 (security patches until Feb 2026) will be the last release with macOS 11 support.

For context, https://github.com/golang/go/issues/64207#issuecomment-1843590873 contains some history as well as future patterns if we keep the same cadence.

CC @golang/darwin.
Repository: rust
Issue: Tracking Issue for `const` `str::split_at*`
Labels: T-libs-api,C-tracking-issue

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

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

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

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

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

This is a tracking issue for using `str::split_at`, `str::split_at_mut`, `str::split_at_checked`, `str::split_at_mut_checked` in `const`, which allows dividing one (mutable) string slice into two (fallibly) at an index during const-eval.

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

### Public API

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

```rust
// core::str
impl str {
    pub const fn split_at(&self, mid: usize) -> (&str, &str);
    pub const fn split_at_mut(&mut self, mid: usize) -> (&mut str, &mut str);
    pub const fn split_at_checked(&self, mid: usize) -> Option<(&str, &str)>;
    pub const fn split_at_mut_checked(&mut self, mid: usize) -> Option<(&mut str, &mut str)>;
}
```

### Steps / History

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

- [x] Implementation: #131520
- [ ] Blocked on #131516
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

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

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

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

### Unresolved Questions

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

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

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: deno
Issue: Installing a package with multiple bin entries
Labels: bug,install

I'm installing `pyright`, and it works really well, but it's supposed to install two bin entries and Deno installs only first.

https://github.com/microsoft/pyright/blob/main/packages/pyright/package.json

```json
    "bin": {
        "pyright": "index.js",
        "pyright-langserver": "langserver.index.js"
    }
```

Workaround is to create `bin/pyright-langserver` manually with

```sh
#!/bin/sh
exec deno run --allow-all --no-config --no-lock 'npm:pyright/langserver.index.js' "$@"
```

Can this be fixed?

Version: Deno 2.0.0
Repository: ollama
Issue: Fine-tuned Llama 3.2 1B safe_serialized: Error: json: cannot unmarshal array into Go struct field .model.merges of type string
Labels: bug,create

### What is the issue?

Modelfile:

```
FROM ./model

# set the temperature to 1 [higher is more creative, lower is more coherent]
PARAMETER temperature 0.2
PARAMETER top_p 0.9
PARAMETER stop 

PARAMETER stop 

PARAMETER stop 

```

./model:

´´´
model-00001-of-00003.safetensors
config.json
generation_config.json
model-00002-of-00003.safetensors
model-00003-of-00003.safetensors
model.safetensors.index.json
special_tokens_map.json
tokenizer_config.json
tokenizer.json
´´´

Command: 

```
ollama create llama3.2-1B -f ./Modelfile
```

Error:

```
transferring model data 100% 
converting model 
Error: json: cannot unmarshal array into Go struct field .model.merges of type string
```

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.3.12
Repository: flutter
Issue: Remove software rendering toggles on iOS.
Labels: P2,c: tech-debt,team-engine,triaged-engine

AFAICT, there is no PList flag but there is a command line flag used thats read on iOS. From @jonahwilliams, we exposed software rendering as a faster way to render on simulators when we only had an OpenGL backend and OpenGL on the simulators was a software implementation on macOS. We have since switched to Metal and the minimum requirements specify Metal on macOS.

Since there never was a PList flag, its hard to so how or if this is being used. We should clean up the entries.
Repository: PowerToys
Issue: Advanced Paste Suggestion
Labels: Needs-Triage

### Description of the new feature / enhancement

Much like plain paste i would love if it also has a Paste as Keystrokes Option,

### Scenario when this would be used?

pasting into Paste disabled Forms/locations

### Supporting information

Code i currently use Via AutoHotkey
```
^#Numpad1::
SendRaw %Clipboard%

```
Repository: PowerToys
Issue: powertoys window title background
Labels: Needs-Triage

### Description of the new feature / enhancement

configuration window title is always black background to me, like preset / hardcoded :/ would look better and easier to drag if following the color set in Windows theme / config


### Scenario when this would be used?

Hard to pick powertoys config window to drag it around the screen, when using windows dark mode

### Supporting information

![Image](https://github.com/user-attachments/assets/b2bb5d54-9620-48d7-958d-a91307a4a1fd)
Repository: ollama
Issue: ollama process uses 1 gb of memory when it's idle due to embedded runners
Labels: feature request,linux

### What is the issue?

```
user@magicbook14:~$ ollama --version
ollama version is 0.3.12
user@magicbook14:~$ ollama ps
NAME    ID    SIZE    PROCESSOR    UNTIL 
```
![image](https://github.com/user-attachments/assets/05de0a19-b087-4c5a-ba45-f5ae421ed9a7)

I'm pretty sure it's some kind of regress, because on previous versions I didn't notice that high memory usage when no models were loaded.  The system it's running on is laptop with AMD Ryzen 7 APU - 5700, no discreet GPU is there, just an integrated one in CPU

### OS

Linux

### GPU

AMD

### CPU

AMD

### Ollama version

0.3.12
Repository: kubernetes
Issue: `system:monitoring` lacks access to kubelet /metrics endpoint
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

Discussion began in https://github.com/kubernetes/enhancements/pull/4830#discussion_r1794149005 where it was identified that [`system:monitoring` cluster role](https://github.com/kubernetes/kubernetes/blob/release-1.31/staging/src/k8s.io/apiserver/pkg/authentication/user/user.go#L73) does not allow access to kubelet's /metrics and /metrics/slis endpoint

### What did you expect to happen?

Would have expected the test described [here](https://github.com/kubernetes/enhancements/pull/4830#discussion_r1794426008) to pass

### How can we reproduce it (as minimally and precisely as possible)?

Summarized [here](https://github.com/kubernetes/enhancements/pull/4830#discussion_r1794426008)

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# v1.31.0
```

</details>


### Cloud provider

<details>
GCP
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: react-native
Issue: Inconsistent separator lines
Labels: Issue: Author Provided Repro,Needs: Author Feedback,Newer Patch Available

### Description

The thickness of the separator lines in FlatList is inconsistent on android. Here's another issue related to the separator: [GitHub Issue](https://github.com/facebook/react-native/issues/36408).

<img width="261" alt="Captura de Tela 2024-10-10 às 20 08 25" src="https://github.com/user-attachments/assets/b8cae2cb-d774-49d2-a145-f05b08d6b428">


### Steps to reproduce

Add a separator to a FlatList with hairlineWidth or 1.



### React Native Version

0.73.6

### Affected Platforms

Runtime - Android

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

```text
Expo 51 from snack.
```


### Stacktrace or Logs

```text
import React from 'react';
import {
  SafeAreaView,
  View,
  FlatList,
  StyleSheet,
  Text,
  StatusBar,
} from 'react-native';

const DATA = [...Array(100).keys()]

const Separator = () => <View style={{ height: StyleSheet.hairlineWidth, backgroundColor: '#000' }} />

const Item = ({title}) => (
  <View style={styles.item}>
    <Text style={styles.title}>{title}</Text>
  </View>
);

const App = () => {
  return (
    <SafeAreaView style={styles.container}>
      <FlatList
        data={DATA}
        renderItem={({item}) => <Item title={item} />}
        ItemSeparatorComponent={Separator}
      />
    </SafeAreaView>
  );
};

const styles = StyleSheet.create({
  container: {
    flex: 1,
    marginTop: StatusBar.currentHeight || 0,
  },
  item: {
    backgroundColor: 'white',
    padding: 12,
  },
  title: {
    fontSize: 20,
  },
});

export default App;
```


### Reproducer

https://snack.expo.dev/@diegolmello/f6c27a

### Screenshots and Videos

<img width="261" alt="Captura de Tela 2024-10-10 às 20 08 25" src="https://github.com/user-attachments/assets/5058dc6b-4e4c-4894-afa6-8517ffcbbb67">
Repository: opencv
Issue: How to contribute to OpenCV University?
Labels: feature

I have developed https://opencv.onweb.dev/ an easy to use, zero installation platform for experimenting with OpenCV and Python in the browser. It is based on WebAssembly and hence needs almost zero cloud infrastructure/resources to run. Another advantage is that it makes it possible to learn about and to experiment with OpenCV on platforms such as Chromebooks and on Android mobiles and tablets.

I would like to contribute this to OpenCV University, however, I cannot find the repository for the site...
Repository: godot
Issue: Track of Current Animation Crash
Labels: bug,topic:editor,crash,topic:animation

### Tested versions

4.3.stable

### System information

Godot v4.3.stable (77dcf97d8) - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU (NVIDIA; 32.0.15.6109) - AMD Ryzen 7 6800H with Radeon Graphics (16 Threads)

### Issue description

If you create a property track in animation player, which tracks current animation. It will сrash engine, and if you save it, it will сrash engine in every start or at least when you try to open this Animation Player.




https://github.com/user-attachments/assets/bee6354d-31d5-43bd-a6bc-acce66a60728




### Steps to reproduce

Create Animation Player (AP)
Create Animation in AP
Add new Property Track on Current Animation of Ap.
Add any key to Property Track 
Save file

Crash

If you try to open AP it will Crash 

### Minimal reproduction project (MRP)

[test.zip](https://github.com/user-attachments/files/17335329/test.zip)
Repository: deno
Issue: Deno doesnt load file when importing jsr:x module
Labels: needs investigation,node compat,node resolution

deno 2.0.0 (stable, release, aarch64-unknown-linux-gnu)
v8 12.9.202.13-rusty
typescript 5.6.2

https://github.com/MARCROCK22/deno-bug
please see seyfert.config.mjs and src/main.ts files.

For some reason, if a module imports an file that imports a jsr module, it doesnt work
I dont get any error, process doesnt even stops (it just stays alive?)