sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Add support for GOT-OCR2.0
Labels: New model

### Model description

As an OCR-2.0 model, GOT can handle all artificial optical signals (e.g., plain texts, math/molecular formulas, tables, charts, sheet music, and even geometric shapes) under various OCR tasks. On the input side, the model supports commonly used scene- and document-style images in slice and whole-page styles. On the output side, GOT can generate plain or formatted results (markdown/tikz/smiles/kern) via an easy prompt. Besides, the model enjoys interactive OCR features, i.e., region-level recognition guided by coordinates or colors. 

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Implementation: https://github.com/Ucas-HaoranWei/GOT-OCR2.0/
Paper: https://arxiv.org/abs/2409.01704
Repository: godot
Issue: Setting scale of a control node inside of a container doesn't work if set immediately
Labels: discussion,documentation,topic:gui

### Tested versions

- Reproducible in v4.4.dev3.mono.official

### System information

v4.4.dev3.mono.official [f4af8201b]

### Issue description

When control node is contained by a container (eg. `VBoxContainer`) and its scale is set immediately after node's creation, the scale value doesn't have any effect. If the scale is set afterwards or it is set using a tween with 0 second duration, the scale works as expected.

### Steps to reproduce

Scene:
![kuva](https://github.com/user-attachments/assets/931e9752-1eca-4ebe-a956-58f5ae06db9c)

Code:
```gdscript
extends Node2D

@onready var label: Label = $VBoxContainer/Label
@onready var v_box_container: VBoxContainer = $VBoxContainer

var label_2

func _ready() -> void:
	# this doesn't work:
	label.scale = Vector2(0.4, 1.0)

	label_2 = Label.new()
	v_box_container.add_child(label_2)
	label_2.text = "Another label with some text"
	# this doesn't work:
	label_2.scale = Vector2(1.0, 2.0)

	# setting scale using a tween with zero duration works:
	#create_tween().tween_property(label, "scale", Vector2(0.4, 1.0), 0.0)
	#create_tween().tween_property(label_2, "scale", Vector2(1.0, 2.0), 0.0)


func _on_button_pressed() -> void:
	# this works:
	label.scale = Vector2(0.4, 1.0)
	label_2.scale = Vector2(1.0, 2.0)
```

If the button is clicked or if the two `create_tween()` lines are uncommented, scales are working as expected.

### Minimal reproduction project (MRP)

[scale_test.zip](https://github.com/user-attachments/files/17376934/scale_test.zip)
Repository: ui
Issue: [bug]: error occurring while installing the components
Labels: bug

### Describe the bug

npx shadcn@latest add avatar
⠴ Checking registry.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

request to https://ui.shadcn.com/r/index.json failed, reason: self-signed certificate in certificate chain


### Affected component/components

all

### How to reproduce

1. Go to terminal
2. Try to install any component(eg: button, textarea, input ...)

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
windows 11 pro
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: material-ui
Issue: [TextField][a11y] Add aria-describedby in the input assosiated with the id of the start/end adornment
Labels: accessibility,component: text field

### Summary

When using start/end adornment the input needs to be well associated with the description they provide, by adding an aria-describedby to have the value of the adornment id so that the unsighted users can get the same hint as sighted users.

As a first step, we can likely start with improving this demo, and later we can provide this as a feature out of the box.

### Examples

Check https://mui.com/material-ui/react-text-field/#input-adornments as an example.

### Motivation

_No response_

**Search keywords**: textfield adonrment
Repository: opencv
Issue: GRU parsing is not implemented in the new ONNX parser
Labels: bug,category: dnn (onnx)

### System Information

The implementation is just commented. The old parser makes several preliminary steps to extract constant blobs. The solution should be reworked with the new one.

Reference: https://github.com/opencv/opencv/pull/26056

### Detailed description

-

### Steps to reproduce

-

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: opencv
Issue: QLinear* layers are not implemented in the new DNN engine
Labels: bug,category: dnn (onnx)

### System Information
Platform: any
Reference: https://github.com/opencv/opencv/pull/26056

### Detailed description

-

### Steps to reproduce

-

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: electron
Issue: [Bug]: 'login' event is not emitted when the HTTP request is sent from the 'main' process using 'net.fetch()' on Windows and MacOS
Labels: bug :beetle:,component/net,has-repro-gist,component/utilityProcess,32-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/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 bug report that matches the one I want to file, without success.

### Electron Version

32.1.2

### What operating system(s) are you using?

Other (specify below)

### Operating System Version

MacOS Sonoma, Windows 11, Debian (Docker)

### What arch are you using?

Other (specify below)

### Last Known Working Electron version

_No response_

### Expected Behavior

I have developed some tests to validate the behaviour of `net.fetch()` / `fetch()` on Windows, MacOS and Linux when sending HTTP(S) requests from the `main` process, from a `renderer` process and from a `utility` process. More specifically, I wanted to check the integration with the OS network settings and trust store when dealing with web proxies and self-signed certificates. See [@hackolade/fetch](https://github.com/hackolade/fetch) for more details about my approach.

I expected `net.fetch()` / `fetch()` to behave consistently whatever the process and the operating system.




### Actual Behavior

When sending HTTP requests through a web proxy that requires basic authentication, I observed the following:
- On Linux, [the 'login' event](https://www.electronjs.org/docs/latest/api/app#event-login) is properly emitted for all processes: `main`, `renderer` and `utility`. As a consequence, the request reaches the server in all cases.
- On MacOS and Windows, [the 'login' event](https://www.electronjs.org/docs/latest/api/app#event-login) is only emitted for a `renderer` process and a `utility` process. It is not emitted when sending the request using `net.fetch()` from the `main` process. As a consequence, that request fails with `HTTP 407 Proxy Authentication Required`.

So how am I supposed to deal with that case?

![Image](https://github.com/user-attachments/assets/24b2805b-9001-4a1d-bc6b-d82a73246af8)

Note that I created a separate issue for the problem with setCertificateVerifyProc():  see #44264.

### Testcase Gist URL

https://gist.github.com/thomas-jakemeyn/035c6494d80b3250b992d70584f4c13c

https://github.com/hackolade/fetch/tree/develop

### Additional Information

_No response_
Repository: rust
Issue: target_feature leads to confusing note in rustdoc
Labels: T-rustdoc,C-bug,A-rustdoc-ui,T-rustdoc-frontend

I tried this code:

```rust
#[target_feature(enable = "avx2")]
pub unsafe fn f() {}
```

I expected to see this happen:

Rustdoc says something along the lines of:

> Requires target feature avx2 at runtime.

Instead, this happened:

Rustdoc says:

> Available with target feature avx2 only.

It is not clear what “available” means here. I initially thought it meant the function would not be defined if not compiled with `--codegen target-feature=+avx2` (and concluded it was always safe to call if the calling program compiles). Instead it means the function is always defined but must not be called if the target feature is not available at runtime. Rustdoc gives no other indication that the `target_feature` attribute is used, and the note looks a lot like the “available on create feature … only” notes.

### 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.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```
Repository: react
Issue: [Compiler Bug]: false positive when accessing `window.location` from the props object
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/iamakulov/react-compiler-bug-repro

### Repro steps

1. Clone the repo
2. `yarn && yarn eslint --ext .js,.ts,.tsx src/*`
3. Observe ESLint logging the following (false positive) error:

   ![Screenshot 2024-10-15 at 13 56 31](https://github.com/user-attachments/assets/e46a0bb6-03ce-4cb8-b8e9-942ddd1a8eeb)

4. Open `src/Component.jsx` and inline the `miniCarouselProps` object:

    ```diff
    - const miniCarouselProps = {
    -   ...props,
    -   cards: cardListTransformed,
    -   slug: props.locationSlug,
    -   onCardClick: (card) => {
    -     location.pathname = card.slug;
    -   },
    -   forceAnchorTag: false,
    - };
    -
    - return <MiniCarousel {...miniCarouselProps} />;
    + return (
    +   <MiniCarousel
    +     {...props}
    +     cards={cardListTransformed}
    +     slug={props.locationSlug}
    +     onCardClick={(card) => {
    +       location.pathname = card.slug;
    +     }}
    +     forceAnchorTag={false}
    +   />
    );
    ```
   
5. `yarn eslint --ext .js,.ts,.tsx src/*`
6. Observe ESLint not logging the error anymore

### How often does this bug happen?

Every time

### What version of React are you using?

19
Repository: pytorch
Issue: Inductor's require_stride_order and require_exact_strides should pull from the graph sent to inductor
Labels: triaged,module: custom-operators,oncall: pt2,module: inductor,module: pt2-dispatcher

Custom operators and triton kernels can be marked with "require_stride_order" or "require_exact_strides". This means that during lowering, Inductor will ensure that the inputs to the custom operator have the same strides as observed in the post_grad Inductor graph.

However, Inductor passes are able to muck around with the strides of inputs to custom operators and triton kernels. See https://github.com/pytorch/pytorch/issues/137437 for an example where an mm padding pass changed the strides!

At the very beginning of inductor, we should record the strides of all inputs to nodes that may require_stride_order and require_exact_strides and store that information somewhere (on the node). Later on, during lowering, we should make use of those strides.

https://github.com/pytorch/pytorch/pull/136732 seems like a WIP version of this

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @bdhirsh
Repository: TypeScript
Issue: Certain homomorphic mappings break assignability with exactOptionalPropertyTypes
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

eopt exactOptionalPropertyTypes homomorphic Omit unassignable

### 🕗 Version & Regression Information

- This is the behavior in every version I tried



### ⏯ Playground Link

https://tsplay.dev/w28Qzm

### 💻 Code

```ts
// @exactOptionalPropertyTypes

type T = {
  foo?: true;
  bar?: true;
};

type WrappedT<t extends T> = [t];

// Since Omit is normally treated as homomorphic, should work but errors with:
// Type 'true | undefined' is not assignable to type 'true'.
type OmitBarFromWrapped<t> =
  t extends WrappedT<infer inner> ? WrappedT<Omit<inner, "bar">> : never;

// Even if we directly rewrite Omit to be homomorphic, we still lose assignability with EOPT
type OmitHomomorphicFromWrapped<t> =
  t extends WrappedT<infer inner>
    ? WrappedT<HomomorphicOmit<inner, "bar">>
    : never;

type HomomorphicOmit<t, keyToOmit> = {
  [k in keyof t as k extends keyToOmit ? never : k]: t[k];
};

// Normally in this situation, I have a conform utility to force TS to allow the type
// but this is maybe the first time I've also seen that not work?
type OmitHomomorphicFromWrappedConformed<t> =
  t extends WrappedT<infer inner>
    ? WrappedT<conform<HomomorphicOmit<inner, "bar">, T>>
    : never;

type conform<t, base> = t extends base ? t : base;
```


### 🙁 Actual behavior

Applying a homomorphic mapping to a type can break property assignability with EOPT

### 🙂 Expected behavior

Should preserve assignability

### Additional information about the issue

_No response_
Repository: rust
Issue: Tracking issue for wasm32-emscripten ui test failures
Labels: A-testsuite,C-bug,C-tracking-issue,O-emscripten

These are the tests that are failing after #131705:

- [ ] `abi/numbers-arithmetic/return-float.rs` -- adding `-Cpanic=abort` fixes the failure. [The upstream bug report](https://github.com/emscripten-core/emscripten/issues/22743) has a C++ reproducer. More reason it would be nice to resolve #112195.
- [x] `async-await/issue-60709.rs` -- [Emscripten bug](https://github.com/emscripten-core/emscripten/issues/22742) that occurs when `-lc` and `-Oz` are passed to the linker, can be reproduced with 
  ```sh
  echo "fn main(){}" > a.rs
  rustc -Copt-level=z a.rs -o a.js --target=wasm32-unknown-emscripten
  ```
- [x] backtrace/dylib-dep.rs -- "Not supported", xfailed in https://github.com/rust-lang/rust/pull/131776
- [x] backtrace/line-tables-only.rs -- "Not supported", xfailed in https://github.com/rust-lang/rust/pull/131776
- [ ] no_std/no-std-unwind-binary.rs -- compiler says error: lang item required, but not found: eh_catch_typeinfo
- [ ] structs-enums/enum-rec/issue-17431-6.rs -- One of the two compiler errors is missing
- [ ] test-attrs/test-passed.rs
Repository: react
Issue: [DevTools Bug]: v6.0.0 (9/26/2024) of devtools makes a page extremely slow in dev (even when devtools are closed)
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

difficult to build a repor for now, since 

### Repro steps

I'm unsure what's the best way to reproduce the issue, but I'm loading a page with React Router v6 with React@19.0.0-rc-6cf85185-20241014 (using the latest version of the compiler), and v6.0.0 of devtools. Chrome version 129.0.6668.101 (Official Build) (arm64) on MacOS.

Even with devtools closed, page loads become very sluggish in development. If I run a Chrome performance profiler, it completely stalls on opening a new page for 5 seconds (albeit we're not running the React profiler):
<img width="1249" alt="Screenshot 2024-10-15 at 15 52 16" src="https://github.com/user-attachments/assets/8a61346e-fb56-4611-adab-36b2c0567111">

When I turn off React Developer tools, page loads become instant when devtools are closed, and Chrome profiler is also 10x faster.

The problem is so bad that we thought we had a memory leak in our app somewhere, but it was all good in the built version of the app. Turns out devtools had updated in the background and everything became sluggish in development as a result. After we disabled the extensions, everything became supper snappy in development again.

Would love to provide a repro, but I'm not exactly sure what conditions trigger the issue, as a barebones react router setup doesn't seem to do the trick.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: storybook
Issue: [Bug]: hash navigation does not work
Labels: bug,addon: docs

### Describe the bug

If you click on the anchor tag next to a story title in the autodocs page, it adds a hash parameter to the page url. However, this hash parameter cannot be used again to go to the same story.

### Reproduction link

https://stackblitz.com/github/storybookjs/sandboxes/tree/next/react-webpack/18-ts/after-storybook?file=.storybook%2Fpreview.ts

### Reproduction steps

1. Open the reproduction link
2. Open preview in a new tab
3. Visit /?path=/docs/example-button--docs#secondary
4. See that it doesn't go directly to the `Secondary` story

### System

Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/addon-interactions: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/addon-onboarding: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/addon-webpack5-compiler-swc: ^1.0.5 => 1.0.5 
    @storybook/blocks: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/react: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/react-webpack5: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    @storybook/test: ^8.4.0-alpha.7 => 8.4.0-alpha.7 
    storybook: ^8.4.0-alpha.7 => 8.4.0-alpha.7 

### Additional context

I just used a brand new react 18/webpack5 storybook via storybook.new. No configuration changes were made.
Repository: stable-diffusion-webui
Issue: [Bug]: Unable to create venv in directrory
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?

After cloning the repository using the command line, this error occurs when launching the bat file. Manually creating a venv does not help.

### Steps to reproduce the problem

1. Copying the repository using the command line according to the instructions from the wiki for amd processors
2. Launching the webui-user.bat file

### What should have happened?

Successful launch of webui

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

Google Chrome

### Sysinfo

--dump-sysinfo doesnt work 
![photo_2024-10-15_17-17-30](https://github.com/user-attachments/assets/ca768936-9f24-49ce-9b8c-f4d5dab002c2)


### Console logs

```Shell
Creating venv in directory E:\stable\stable-diffusion-webui-directml\venv using python "C:\Users\└эфЁхщ\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\python.exe"
Unable to create venv in directory "E:\stable\stable-diffusion-webui-directml\venv"

exit code: 3

stderr:
Системе не удается найти указанный путь.

Launch unsuccessful. Exiting.
Для продолжения нажмите любую клавишу . . .
```


### Additional information

I can't find the sysinfo file. 
I have Windows 11. 
Python of the latest version from the Microsoft Store is installed
Repository: rust
Issue: with_exposed_provenance(0).with_addr(addr) is compiled as gep null
Labels: T-compiler,C-bug,A-strict-provenance,T-opsem

Miri executes this program without error, but I believe our lowering to LLVM IR adds UB:
```rust
#![feature(strict_provenance, exposed_provenance)]
#[no_mangle]
pub fn from_exposed_null(addr: usize) -> *const u8 {
    let ptr = 0x0 as *const u8;
    ptr.with_addr(addr)
}

// Main for Miri
fn main() {
    let data = 0u8;
    let addr = std::ptr::addr_of!(data).expose_provenance();
    let ptr = from_exposed_null(addr);
    unsafe {
        println!("{}", *ptr);
    }
}
```
With optimizations enabled, LLVM cleans up `from_exposed_null` to
```llvm
define noalias noundef ptr @from_exposed_null(i64 noundef %addr) unnamed_addr #0 !dbg !7 {
  %0 = getelementptr i8, ptr null, i64 %addr, !dbg !12
  ret ptr %0, !dbg !28
}
```
With `-Cno-prepopulate-passes` I believe the codegen also returns a pointer that definitely has no provenance, though it's just harder to read.
godbolt: https://godbolt.org/z/s414rfK44

I *think* this happens because codegen is implicitly const-propagating through the int-to-pointer cast via `OperandValue`. At least I don't see any other way to get from this MIR:
```
    bb0: {
        _2 = const 0_usize as *const u8 (PointerWithExposedProvenance);
        StorageLive(_3);
        StorageLive(_5);
        StorageLive(_6);
        StorageLive(_4);
        _4 = copy _2 as usize (Transmute);
        _3 = move _4 as isize (IntToInt);
        StorageDead(_4);
        _5 = copy _1 as isize (IntToInt);
        _6 = Sub(copy _5, copy _3);
        _0 = arith_offset::<u8>(move _2, move _6) -> [return: bb1, unwind unreachable];
    }

    bb1: {
        StorageLive(_7);
        _7 = copy _0 as *const () (PtrToPtr);
        StorageDead(_7);
        StorageDead(_6);
        StorageDead(_5);
        StorageDead(_3);
        return;
    }
```
To this LLVM IR
```
define noundef ptr @from_exposed_null(i64 noundef %addr) unnamed_addr #0 !dbg !7 {
start:
  %0 = alloca [8 x i8], align 8, !dbg !12
  %offset = sub i64 %addr, 0, !dbg !12
  call void @llvm.lifetime.start.p0(i64 8, ptr %0), !dbg !28
  %1 = getelementptr i8, ptr null, i64 %offset, !dbg !28
  store ptr %1, ptr %0, align 8, !dbg !28
  %self = load ptr, ptr %0, align 8, !dbg !28
  call void @llvm.lifetime.end.p0(i64 8, ptr %0), !dbg !28
  ret ptr %self, !dbg !34
}
```
godbolt: https://godbolt.org/z/MjPvcdj9h