sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: crypto/x509: parser should error on Subject Information Access and Policy Constraints being makred as critical
Labels: NeedsInvestigation

### Go version

go version go1.23.2 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/liu/.cache/go-build'
GOENV='/home/liu/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/liu/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/liu/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/snap/go/10730'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/snap/go/10730/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.2'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/liu/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3084352486=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Use x509.ParseCertificate(derBytes) to parse the der certificate

### What did you see happen?

A critical examine of the aia extension：authority info access incorrectly marked critical
Authority Information Access is described in RFC5280: Conforming CAs MUST mark this extension as non-critical.
Other extensions with the same description in RFC5280 are not checked, such as:
Subject Information Access: Conforming CAs MUST mark this extension as non-critical.
Policy Constraints: Conforming CAs MUST mark this extension as non-critical.

### What did you expect to see?

For certificates marked as critical, such as Subject Information Access and Policy Constraints, parsing errors will also occur.
Repository: ollama
Issue: Please add microsoft/OmniParser model
Labels: model request

OmniParser is a general screen parsing tool, which interprets/converts UI screenshot to structured format, to improve existing LLM based UI agent. Training Datasets include: 1) an interactable icon detection dataset, which was curated from popular web pages and automatically annotated to highlight clickable and actionable regions, and 2) an icon description dataset, designed to associate each UI element with its corresponding function.

https://huggingface.co/microsoft/OmniParser

Thanks!
Repository: vscode
Issue: `editor.wordWrap: "bounded"` don't work when inside a settings block for multiple languages
Labels: bug,editor-wrapping

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95.2
- OS Version: Windows 11 (10.0.22631)

Steps to Reproduce:

1. Use the following settings:

```json
{
  "[markdown][plaintext]": {
    "editor.wordWrap": "bounded",
  },
}
```

2. Open a markdown or plaintext file and type some text. The text won't wrap at 80th column, but wrap at the viewport edge.

Note that if you launch VSCode to open a file, the file will be correctly wrapped. However, it stops working when you switch to another tab and switch back.
Repository: go
Issue: proposal: log/slog: export Source method in Record to support custom handler implementations
Labels: Proposal

### Go version

go version go1.23.1 linux/amd64

### Output of `go env` in your module/workspace:

```shell
Not relevant
```


### What did you do?

Implement a custom handler for the log/slog package. My custom handler requires access to the source location (file and line) of log entries for detailed logging.

### What did you see happen?

The source method in slog.Record is not exported, meaning it’s inaccessible to custom handlers. As a result, I had to re-implement logic to retrieve source location information, which led to redundant code and reduced consistency with Go's built-in logging behavior.

### What did you expect to see?

Expected an accessible Source method in slog.Record that allows custom handlers to retrieve source location information without re-implementing the existing internal logic. This would simplify the creation of custom handlers and ensure consistent behavior when accessing log entry sources.
Repository: stable-diffusion-webui
Issue: [Bug]: WebUI not startting with --listen
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Webui crash when trying to start with --listen flag


### Steps to reproduce the problem

Go to webui-user.sh
Add --listen flag to COMMANDLINE_ARGS

### What should have happened?

Webui should start

### What browsers do you use to access the UI ?

Mozilla Firefox

### Sysinfo

[sysinfo-2024-11-11-09-02.json](https://github.com/user-attachments/files/17699866/sysinfo-2024-11-11-09-02.json)


### Console logs

```Shell
https://pastebin.com/zZQJqvQj
```


### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [HELP]: replacement for supermerger
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?


a merger that merge FLUX models and loras
option cosine and so one like supermerger

https://github.com/hako-mikan/sd-webui-supermerger/issues/415#issuecomment-2467196960


### Proposed workflow

123

### Additional information

_No response_
Repository: vscode
Issue: Improve contrast of +/- type zoom buttons
Labels: polish,editor-hover

The contrast on these buttons is very low:

![Image](https://github.com/user-attachments/assets/54e89d16-f06e-416d-840f-9fe04cf59f84)

Compare this to that in context menus for example which use light grey/white instead of blue for active:

![Image](https://github.com/user-attachments/assets/e0b822a8-d12a-4bb6-b9a3-636465807997)
Repository: vscode
Issue: Increase hit target of +/- type zoom buttons
Labels: polish,editor-hover

The hit target is very small:

![Image](https://github.com/user-attachments/assets/c1cc40c2-70a4-489b-94e3-1b7a7e5a8690)

This is actually much smaller than the breakpoint hit target:

![Image](https://github.com/user-attachments/assets/4a7177e2-b3a7-4f1f-a341-1fb091812635)
Repository: vscode
Issue: Zooming into types moves the +/- buttons off screen
Labels: feature-request,ux,polish,editor-hover

Awkward UX:

![Image](https://github.com/user-attachments/assets/1a69cab7-aeb7-4b64-9281-36220974bfb8)
Repository: vscode
Issue: Zoomed types truncates too quickly
Labels: bug,editor-hover

The content gets truncated too quickly imo, considering this is an explicit user action to get more information about the type:

![Image](https://github.com/user-attachments/assets/f6d8fcd1-86bd-4c62-b34f-be89c74437c6)
Repository: vscode
Issue: Zooming types syntax highlighting doesn't look good
Labels: bug,editor-hover

I think this is because we use the tmGrammar and hope for the best:

![Image](https://github.com/user-attachments/assets/dc5ffc07-23b2-43e3-8b7b-f82113d01828)

Some ideas:

- Perhaps we could we leverage tree sitter here instead?
- Experiment with changing the language
- Should we color the RHS of the : differently if it's not perfect TS?
- Create a custom grammar which worked well?
Repository: deno
Issue: Env support for Jupyter kernel
Labels: bug,deno jupyter

I'd love for a cell like this to work:

```ts
const a = Deno.env.get("PATH")

a
```

The use-case would be to provide secrets (i.e., API keys) to the notebook.
Repository: deno
Issue: Jupyter kernel - relative import
Labels: bug,needs investigation,deno jupyter

It'd be nice to write some helper functions in my local project  (for example that fetches/downloads data, in `./data.ts`) and then use that somehow in a cell like this:

```ts
const { getData } from './data.ts'  // or 'from ./data'

await getData()
```

But that seems to crash the deno kernel.
Repository: godot
Issue: Inconsistent/incorrect result for 'is_valid_hex_number()' when using signed '0x' prefix
Labels: bug,topic:core

### Tested versions

4.4

### System information

Godot v4.4.dev (0f5f3bc95) - Windows 10.0.18363 - Multi-window, 4 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 970 (NVIDIA; 32.0.15.6590) - Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 threads)

### Issue description

The  [is_valid_hex_number](https://docs.godotengine.org/en/stable/classes/class_string.html#class-string-method-is-valid-hex-number)-method have inconsistent behavior when provided with strings like `"0x"`, `"-0x"`, and `"+0x"`. The cases with plus/minus signs currently return `true`, even though they do not contain any hexadecimal digits after the `"0x"` prefix. 



Example tests for the method, it has inconsistent returns for the following inputs:

```gdscript
print("-0x".is_valid_hex_number(true))  # Returns true (expected: false)
print("0x".is_valid_hex_number(true))   # Returns false (expected: false)
print("+0x".is_valid_hex_number(true))  # Returns true (expected: false)
```


Example (MRP screenshot):
![ad2331acf234681c6f9af7346c444f80](https://github.com/user-attachments/assets/642b2b35-c099-4e4d-9c5d-325886584c3b)




### Steps to reproduce

N/A

### Minimal reproduction project (MRP)


[hex_issue.zip](https://github.com/user-attachments/files/17700015/hex_issue.zip)
Repository: deno
Issue: Unexpected `code: ERR_MODULE_NOT_FOUND` on module linking errors
Labels: bug

Version: Deno 2.0.5

**Input code**
```js
// entrypoint.js
import("./mod.js").catch(console.log);
```
```js
// mod.js
import { x } from "./mod.js"
```

**Actual behavior**

The logged error has a `code: ERR_MODULE_NOT_FOUND` property.

```
deno run entrypoint.js 
[SyntaxError: The requested module './mod.js' does not provide an export named 'x' at .../mod.js:1:10] {
  code: "ERR_MODULE_NOT_FOUND"
}
```

**Expected behavior**

This error is an error defined by the ES spec, and not an error that hosts can define. It's defined at step 7.c.ii of https://tc39.es/ecma262/#sec-source-text-module-record-initialize-environment and it has no extra properties.

**Other info**

On the other hand, it's perfectly fine to add a `code` property to errors that are thrown when resolving an import specifier and fetching/reading the file fails, since that's host defined behavior and https://tc39.es/ecma262/#sec-HostLoadImportedModule defines no requirements on which error is thrown.
Repository: rust
Issue: ReferencePropagation introduces UB into code that is accepted by Stacked Borrows
Labels: T-compiler,C-bug,A-mir-opt,I-miscompile,E-needs-investigation,WG-mir-opt

This program is accepted by Stacked Borrows:
```rust
fn main() {
    struct Foo(u64);
    impl Foo {
        fn add(&mut self, n: u64) -> u64 {
            self.0 + n
        }
    }

    let mut f = Foo(0);
    let alias = &mut f.0 as *mut u64;
    let res = f.add(unsafe {
        *alias = 42;
        0
    });
    assert_eq!(res, 42);
}
```
That is a Stacked Borrows limitation; it is caused by the fact that 2-phase borrows cannot be modeled properly with just a Stack.
However, it also shows that defining an aliasing model that rejects this code is non-trivial, and we should be very careful with optimizations on such code until we have a clear plan for how to model this.

And yet, it turns out that running this code with `mir-opt-level=2` introduces UB:
```
error: Undefined Behavior: trying to retag from <1484> for Unique permission at alloc702[0x0], but that tag does not exist in the borrow stack for this location
  --> 2phase.rs:4:16
   |
4  |         fn add(&mut self, n: u64) -> u64 {
   |                ^^^^^^^^^
   |                |
   |                trying to retag from <1484> for Unique permission at alloc702[0x0], but that tag does not exist in the borrow stack for this location
   |                this error occurs as part of function-entry retag at alloc702[0x0..0x8]
   |
   = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
   = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <1484> was created by a SharedReadWrite retag at offsets [0x0..0x8]
  --> 2phase.rs:11:15
   |
11 |     let res = f.add(unsafe {
   |               ^
help: <1484> was later invalidated at offsets [0x0..0x8] by a write access
  --> 2phase.rs:14:9
   |
14 |         *alias = 42;
   |         ^^^^^^^^^^^
   = note: BACKTRACE (of the first span):
   = note: inside `main::Foo::add` at 2phase.rs:4:16: 4:25
note: inside `main`
  --> 2phase.rs:11:15
   |
11 |       let res = f.add(unsafe {
   |  _______________^
12 | |         // This is the access at fault, but it's not immediately apparent because
13 | |         // the reference that got invalidated is not under a Protector.
14 | |         *alias = 42;
15 | |         0
16 | |     });
   | |______^
```


This is quite surprising, I thought we were very conservative in terms of doing optimizations that rely on the aliasing model. I have not yet figured out where exactly this comes from.
Cc @rust-lang/opsem @rust-lang/wg-mir-opt  @cjgillot
Repository: ui
Issue: [bug]: Unable to add/install toast
Labels: bug

### Describe the bug

`npx shadcn@latest add toast`

is not working, I am getting the following error

`Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Command failed with exit code 1: npm install @radix-ui/react-toast
npm ERR! Cannot read properties of null (reading 'matches')`

### Affected component/components

toast

### How to reproduce

`npx shadcn@latest add toast`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Mac M1, "react": "^18.2.0", shadcn": "^2.1.6",
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: When searching rtl letters in Arabic using `Ctrl+F` the word gets reversed and disconnected
Labels: bug,editor-RTL

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.95.2
- OS Version: Linux x64 6.11.6-arch1-1

Steps to Reproduce:

1.  Open A file with Arabic text
2. click `Ctrl+F`
3. search for a part of the word
4. observe the word being reversed and incorrectly aligned

Wrong behavior below:
![Image](https://github.com/user-attachments/assets/38d614a4-29bf-4140-800b-06d091532277)


How it looks when highlighted using side search bar (correct)
![Image](https://github.com/user-attachments/assets/37f98147-f2be-4c71-aed9-4a18a129dec1)
Repository: godot
Issue: Editor remote debugger should allow to listen on all interfaces
Labels: enhancement,topic:editor,topic:network

### Tested versions

- Reproducible in 4.4.dev4 / current master

### System information

Tested on Windows, doubt its relevant though

### Issue description

As of right now (before https://github.com/godotengine/godot/pull/98282/), the docs for the editor setting `network/debug/remote_host` state: `This can be set to 0.0.0.0 to allow external clients to connect to the remote debugger (instead of restricting the remote debugger to connections from localhost).`

However, in the editor this is exposed as a dropdown selection of available local network interface adressses. "All" is not an option, but I'd indeed expect it to work, as the case described above makes sense (and is probably what I'd use more often rather than restricting this to, say, a specific IPv4 interface).

As this setting is a string, it may work when set from code, in which case this is more of a Editor UI issue, where we need to inject an additional wildcard/any setting for the dropdown.

### Steps to reproduce

- Open editor, browse editor (not project) settings, search for "remote host", notice the dropdown doesn't allow selectin all interfaces

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: ErrorCompile
Labels: I-ICE,T-compiler,A-incr-comp,C-bug,S-needs-repro

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

### Code
```
#![warn(clippy::all, clippy::pedantic)]
fn main() {
  let arr = [1, 2, 3, 4, 5];
    for num in arr.iter() {
    println!("{} is unique", num);
  }
}
```

### Meta

`rustc --version --verbose`:
1.82.0
```
<version>
```

### Error output

error: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: rustc 1.82.0 (f6e511eec 2024-10-15) running on x86_64-pc-windows-gnu
note: compiler flags: --crate-type bin -C embed-bitcode=no -C debuginfo=2 -C incremental=[REDACTED]
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
end of query stack

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Backtrace</strong></summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: angular
Issue: Support for ElementInternals in Angular Elements
Labels: area: elements

### Which @angular/* package(s) are relevant/related to the feature request?

elements

### Description

To participate in HTML form submission, a custom element must have its element internals defined. Example from [MDN](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/attachInternals):
```
class CustomCheckbox extends HTMLElement {
  static formAssociated = true;

  constructor() {
    super();
    this.internals_ = this.attachInternals();
  }

  // …
}
```
Are there any plans to incorporate this part of the Custom Elements API into Angular Elements?

### Proposed solution

Add a new property to `NgElementConfig` called `"isFormElement"`. Then, modify the `createCustomElement` function to set `this.internals_ = this.attachInternals();` in the constructor and add the `static formAssociated = true;` property if the flag is set.

```typescript
export interface NgElementConfig {
  injector: Injector;
  isFormElement: boolean;
  strategyFactory?: NgElementStrategyFactory;
}
```

### Alternatives considered

Use decorator-based approach for example: `@FormAssociated`
Repository: deno
Issue: Deno fails to find alpha package versions unless explicitly specified
Labels: jsr

Version: Deno 2.0.6

Doing `deno run -A jsr:@fresh/init` fails unless you specify the exact version number.
Repository: deno
Issue: `Deno.connect()` can't be canceled if unreachable hostname and port specified
Labels: bug,ext/net

If unreachable hostname and port pair is specified in `Deno.connect`, it can't be canceled until it times out with OS Error.

```js
const conn = await Deno.connect({ hostname: "104.20.22.46", port: 50000 });
// This times out with os error 60 in about 75 sec on mac os.
```

This situation is inconvenient for some of the node.js compat unit test cases (for example, a case in `tests/node_compat/test/parallel/test-net-autoselectfamily.js` connects to the above server and the above hang happens, which wastes about 1 min before the connection is closed from the server (See #26661))
Repository: material-ui
Issue: Customizing the theme in nextjs: responsiveFontSizes, fontFamily and allVariants don't work with custom Typography variants
Labels: docs,support: question,package: material-ui,customization: theme

### Steps to reproduce

[Link to live example: (required)](https://github.com/Susannah-Parsons/mui-theme-bug)

Steps:
1. Run the program from the mui-theme-bug respository
2. Check the styles for the body3 typography
3. Note that the styles don't include the fontFamily nor the styles from allVariants
4. Note that none of the typography variants have responsive fonts


### Current behavior

Custom typography variants don't include the fontFamily nor the styles in allVariants.
None of the typography variants have responsiveFontStyles

### Expected behavior

All the typography variants should use the fontFamily and allVariants properties. All the typography variants should have responsive font sizes.

### Context

Custom typography variants that work properly with the fontFamily, allVariants and responsiveFontStyles features of custom theming in MUI

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
  Binaries:
    Node: 20.17.0 - /usr/bin/node
    npm: 10.8.2 - /usr/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3 
    @emotion/styled: ^11.13.0 => 11.13.0 
    @mui/core-downloads-tracker:  6.1.6 
    @mui/material: ^6.1.6 => 6.1.6 
    @mui/private-theming:  6.1.6 
    @mui/styled-engine:  6.1.6 
    @mui/system:  6.1.6 
    @mui/types:  7.2.19 
    @mui/utils:  6.1.6 
    @types/react: ^18 => 18.3.12 
    react: 19.0.0-rc-66855b96-20241106 => 19.0.0-rc-66855b96-20241106 
    react-dom: 19.0.0-rc-66855b96-20241106 => 19.0.0-rc-66855b96-20241106 
    typescript: ^5 => 5.6.3 

I used Microsoft Edge
Version 130.0.2849.68 (Official build) (64-bit)
to view the app
```
</details>


**Search keywords**: responsiveFontSizes fontFamily, allVariants, custom, typography, theme