sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: No further instruction regarding "Results order tuning" setting in PT Run
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

Regarding Powertoys Run application, I intend to change the order of my search results. However, I am unable to find a great documentation and instruction of this setting in your GitHub or on the internet.
Repository: pytorch
Issue: Torchscript with dynamic quantization produces inconsistent model outputs
Labels: oncall: jit,oncall: quantization,low priority,triaged

### 🐛 Describe the bug

Hello, I've been experimenting with torchscript and dynamic quantization and often have the issue that results of the models that are dynamically quantized are not consistent between Python and Java.
To reproduce the issue I created a fork of the python java-demo: https://github.com/westphal-jan/java-demo.

To setup you need to download libtorch and set its the location in `build.gradle` (https://github.com/westphal-jan/java-demo/blob/master/build.gradle#L16)
Download Link: https://download.pytorch.org/libtorch/cpu/libtorch-shared-with-deps-1.13.1%2Bcpu.zip

I created a simple dummy model with one linear layer and export it unquantized and quantized here: https://github.com/westphal-jan/java-demo/blob/master/create_dummy_models.py
(The code can also be run using the dependencies defined in https://github.com/westphal-jan/java-demo/blob/master/requirements.txt but I also commited the dummy models)

Python:
```
Unquantized model:
[[-2.758167028427124, 2.0038578510284424, -4.114053726196289, -1.2928203344345093, 1.4940322637557983]]
Quantized model:
[[-2.747678756713867, 1.9912285804748535, -4.110795021057129, -1.2891944646835327, 1.4982664585113525]]
```

You can run the java code with `./gradlew run`.
Java:
```
Unquantized model:
data: [-2.758167, 2.0038579, -4.1140537, -1.2928203, 1.4940323]
[W qlinear_dynamic.cpp:239] Warning: Currently, qnnpack incorrectly ignores reduce_range when it is set to true; this may change in a future release. (function apply_dynamic_impl)
Quantized model:
data: [-2.7473624, 1.9966378, -4.110954, -1.283469, 1.4918814]
```

As you can see the output of the unquantized model is perfectly consistent while the output of the dynamically quantized model is slightly inconsistent. It might seem insignificant but with larger models like a transformer it becomes more obvious (differences usually already in the first decimal place). Am I misunderstanding something conceptually? I thought as the code is compiled down to C it should be the same even when using dynamic quantization.

Note: I made sure that Python and Java use the same version of Torch `1.13.1` which is the latest published mvn version (https://mvnrepository.com/artifact/org.pytorch/pytorch_java_only)

### Versions

1.13.1

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @Xia-Weiwen @leslie-fang-intel
Repository: angular
Issue: Default redirect when using multiple named outlets doesn't work if a partial URL is supplied
Labels: area: router,router: aux routes

### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

With a router configuration like:

```
 {
    path: '',
    outlet: 'tab',
    redirectTo: 'first',
    pathMatch: 'full'
  },
  {
    path: 'first',
    outlet:  'tab',
  },
  {
    path: 'second',
    outlet: 'tab',
  },
 {
    path: '',
    outlet: 'caption',
    redirectTo: 'summary',
    pathMatch: 'full'
  },
  {
    path: 'summary',
    outlet:  'caption',
  },
  {
    path: 'action',
    outlet:  'caption',
  }
```

And a URL like: `.../(tab:first)`; with `pathMatch: 'prefix'` it would redirect to `.../details/(tab:first//caption:summary)` (due to the empty path redirect). With `pathMatch: 'full` the redirect no longer occurs, leaving the `caption` outlet empty. If *no* outlet segment is provided, ie. `.../details` then both redirects occur correctly.

I'd like the redirect to still occur; so portions of the page aren't accidentally empty.

Leaving `pathMatch: 'prefix'` in does seem to work (moving to the bottom of the array for safety) but feels like a workaround rather than the intended behavior.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 16.0.5
Node: 16.15.0
Package Manager: npm 8.5.5
OS: win32 x64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1600.2
@angular-devkit/core         16.0.2
@angular-devkit/schematics   16.0.5
@schematics/angular          16.0.5
```


### Anything else?

This was discovered while migrating from Angular 13 due to the runtime error if no `pathMatch` was supplied. It is unclear if `pathMatch: 'full'` would have worked in Angular 13.
Repository: opencv
Issue: Charuco board detection is not suitable for calibration?
Labels: category: objdetect

### System Information

OpenCV python version: 4.7.0
Operating System / Platform: Debian GNU/Linux 11 (bullseye)
Python version: 3.9.2

### Detailed description

It's my first time using charuco and I did not expect to encounter so many problems with this method.

According to the OpenCV docs, the idea of introducing Charuco was to make the classic chessboard pattern robust to partial view. 

But when I ran the charuco corners detection, I realized that the detected chessboard corners did not match the real ones
![image](https://github.com/opencv/opencv/assets/1102205/4b72119b-b64f-4ee4-976a-06c9a1395485)

According to the [documentation](https://docs.opencv.org/4.x/d9/df5/classcv_1_1aruco_1_1CharucoDetector.html#aacbea601612a3a0feaa45ebb7fb255fd) and [source code](https://github.com/opencv/opencv/blob/4.x/modules/objdetect/src/aruco/charuco_detector.cpp#L317) of `cv::CharucoDetector::detectBoard()`, this function doesn't detect chessboard corners. Instead, it detects inner ArUco markers and uses them to estimate the camera pose and project back the chessboard corners. It has two options: when you have camera intrinsic parameters and when you don't (it's our option). For the second option, it uses a homography matrix to estimate the chessboard corners, which means that this method does not account for distortion. Therefore, the reprojected positions of corners may be incorrect. After that, the method calls the `cv::cornerSubPix() `method to refine the corners' positions, and if the initial reprojection position is not far away from the real one, this call could produce accurate detection. That's why not all corners are found incorrectly.

Although this method is mentioned in many tutorials, it is not suitable for calibration.

### Steps to reproduce

I got this problem running my own code, but for baseline I ran the official [example](https://github.com/opencv/opencv_contrib/blob/70f870600addc014a50798d7599950f36e6551c4/modules/aruco/samples/calibrate_camera_charuco.cpp)
```
./example_aruco_calibrate_camera_charuco -v=<...>/frame-%03d.png -d 0 -h=6 -w=4 --sl=0.3175 --ml=0.2540 --sc --rs
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: TypeScript
Issue: Function's attached JSDoc is not preserved when using OmitThisParameter
Labels: Suggestion,Awaiting More Feedback

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
JSDoc, types with docs, preserve docs, OmitThisParameter, bind, inherit description

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "Something to do with `this`" and "Strong typing of `Function` members `call`/`bind`/`apply`"

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior.
  This should have the same code as the code snippet below, and use whichever settings are relevant to your report.

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.1.3#code/PQKhFgCgAIWgVAFgSwM7QCYFNUGMBOyADgC7ID2AdtGtADbmolSzQtwACRAhvtwLbQi0AILoA7ljp1o3dCRTpsBYmSrtgUAGYBXSrjXVd+gBQK0ALmgBvAL4AaIVaaFKAcwCUVgG7lkGG1soKFwqJmgtaABeCL1cWXQAeX5kEiQ0AAVeASwSLHwAHhIATyIsckjjXAA+AG4QsJJoN2jY-QA6ACNkSgwTOw96yCA)

### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->
```ts
/**
 * This description is lost
 * 
 * @param p As well as this decription
 */
function func(this: {}, p: string): void {}

const f = func as OmitThisParameter<typeof func>;
const g = func.bind({});
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
Hovering over `f` (or `g`) shows the type but not the descriptions that were attached to `func`.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
`f` and `g` to inherit the descriptions of `func`.

### Clarification

The problem mainly lies with `OmitThisParameter` as `bind`'s declaration uses it.
I'm also not sure if this is considered a bug or a missing feature, so I apologize in advance if this is not the right way to report it.

Might be related to #50715
Repository: storybook
Issue: [Bug]: Property 'default' does not exist on type 'ComponentPropsAndSlots .... vue/slots/ts
Labels: bug,needs triage

### Describe the bug

Hi! im migrationg my project to @7
And i faced with issue - stories failed to parse slots args...
im getiing error in IDE
if vue-typescript server used:
`TS2322: Type '{ default: string; }' is not assignable to type 'Partial<ComponentPropsAndSlots<DefineComponent<....`
if volar server selected:
`Volar: Type '{ default: string; }' is not assignable to type 'Partial  { src: { type: ....`

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: rust
Issue: Optimizer regression from 1.69 to 1.70 on AArch64
Labels: I-slow,P-medium,regression-from-stable-to-stable,C-bug,C-optimization

<p>
My code for advent of code slowed down from 1.69 to 1.70 under release build. The
dev build performance is the same. (main reports the time that the function takes to run.)
</p>

<p>
I've simplified my code down:
https://github.com/omalley/advent_of_code_2022/blob/rust-bug/src/main.rs
</p>

<details>
<p>
- Dev build
  - 1.69: 5.14s
  - 1.70: 5.14s
</p>
<p>
- Release build
  - 1.69: 0.425s
  - 1.70: 0.730s
</p>

The 1.70 release build is much slower than the same program under 1.69.
</p>
</details>
Repository: neovim
Issue: async vim.lsp.buf.code_action for use with BufWritePre autocmd
Labels: enhancement,lsp,async

### Problem

I'm currently using the following autocmd in my `init.lua`. It's purpose is to organize organize the imports which requires modifying the buffer. But when it is triggered by `BufWritePre` the buffer gets saved to the file before `vim.lsp.buf.code_action` applies the changes.

The result is that the changes are made in the buffer but not included in the saved file.

```lua
vim.api.nvim_create_autocmd({ "BufWritePre" }, {
    pattern = "*.go",
    command = "lua vim.lsp.buf.code_action({ context = { only = { 'source.organizeImports' } }, apply = true })"
})
```

### Expected behavior

The [LSP FAQ](https://neovim.io/doc/user/lsp.html) addresses a similar use-case using `vim.lsp.buf.format()` and its `async` option as an example.

I imagine the same async option could be added to `vim.lsp.buf.code_action`.

I don't know any lua and after looking at the code for 5 minutes it seems non-trivial for me to attempt to fix this. I'm therefore making this feature request here.
Repository: Web-Dev-For-Beginners
Issue: Add Bengali Language Translation
Labels: no-issue-activity

 Adding Bengali language translation would greatly benefit the community of Bengali-speaking users
Repository: go
Issue: proposal: testing: flag to continue testing after -failfast failure
Labels: Proposal

### Problem
After using `go test -failfast` to find the first failing test, then fixing the failure, there is no straightforward way to resume the tests from the point of failure. I have to either run all the earlier tests again, or enumerate the list of tests that come after the failing test.

### Goal
Reduce the total time to resolve multiple bugs that each affect one or more tests but not most or all tests. Reduce the number of times each test is run.

### Proposal
Add a flag such that `-run TestFoo` will not only run all tests matching `TestFoo` but all tests after the first such match.

### Example
```
$ go test -failfast
--- PASS: TestA
--- PASS: TestB
--- FAIL: TestC
$ patch -i fix_test_c.patch
$ go test -run TestC
--- PASS: TestC
$ go test -failfast
--- PASS: TestA
--- PASS: TestB
--- PASS: TestC
--- PASS: TestD
--- FAIL: TestE
```
I didn't want to run TestA or TestB again here, or TestC an extra time. I would rather have done something like
```
go test -run TestC -andlatertests -failfast
```
(I acknowledge that's not a good name for the flag)
Repository: godot
Issue: Debugged project crashes when script is edited
Labels: bug,topic:gdscript,topic:editor,needs testing,crash

### Godot version

4.1.dev3

### System information

Ubuntu 22.04.2 LTS 22.04 - Vulkan (Mobile) - integrated Intel(R) HD Graphics 4000 (IVB GT2) () - Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (8 Threads)

### Issue description

I recently updated my main 4.0 project to 4.1, but in all betas I have the same issue: Whenever I edit a script while the project is running, it has a small chance of crashing (especially when I trigger an input event)

### Steps to reproduce

I couldn't reproduce the bug on a new project, I think it's related to converting from 4.0

### Minimal reproduction project

N/A
Repository: flutter
Issue: [Impeller] Take advantage of pre-rotation in the Vulkan swapchain.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

This is performance sensitive and we must follow the guidance in https://developer.android.com/games/optimize/vulkan-prerotation.
Repository: PowerToys
Issue: Task manager does not snap to FancyZones
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.70.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Create a FancyZones layout
2. Open Task manager
3. Try to place the Task Manager window to a zone on a non-primary monitor

### ✔️ Expected Behavior

Task Manager window snaps to the zone

### ❌ Actual Behavior

Task manager window seems to snap to a random other place on the desktop, with a random size

### Other Software

_No response_
Repository: storybook
Issue: [Feature Request]: Allow hooks to be passed in `component` or similar property - React/Typescript
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

Our organization has several hooks documented with storybook, using a component in the story to render them, but on two of them we need to bring in the associated jsdoc commentary which can only be achieved at the moment by passing the hook as the `component` like so:
```
const meta: Meta<typeof useReactHook> = {
  title: 'Hooks/useReactHook',
  component: useReactHook,
};
export default meta;
```
With the goal of a result like:
<img width="667" alt="Screen Shot 2023-06-26 at 4 51 08 PM" src="https://github.com/storybookjs/storybook/assets/90861269/bd963c97-54f5-4f40-bf7d-5647d1047d6f">

however, written in this results in a typescript error, as hooks themselves are not rendered components.

### Describe the solution you'd like

In a React/Typescript environment, we would like to be able to pass hooks either as the `component` or with their own key. 

### Describe alternatives you've considered

The main workaround we've found is the following, but it requires an `as` type assertion:
```
const meta: Meta<typeof useReactHook> = {
  title: 'Hooks/useReactHook',
  component: useReactHook as ComponentType<unknown>,
// or component: useReactHook  as unknown as ComponentType<unknown>,
};
export default meta;
```

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: go
Issue: go/types: expose an API for normalized interface terms
Labels: NeedsInvestigation

This is a placeholder for planning purposes, to be exchanged for a proper proposal at a future date.

As discussed in #60994, there are some missing `go/types` APIs that are currently papered over with the [`x/exp/typeparams`](https://pkg.go.dev/golang.org/x/exp/typeparams) package.

In particular, we should propose a `go/types` API that serves the purpose of the [`NormalTerms`](https://pkg.go.dev/golang.org/x/exp/typeparams#NormalTerms) function -- some way to traverse a normalized representation of the terms of an interface types.

We could expose an equivalent API to `NormalTerms`, or do something simpler. Let's decide early in the go1.22 cycle.

CC @griesemer @adonovan @timothy-king @mdempsky
Repository: deno
Issue: Type error with node compat's Readable.fromWeb()
Labels: bug,node compat,types

This code should be fine, but doesn't pass type check:

```typescript
import { Readable } from "node:stream";
const webStream = new ReadableStream();
Readable.fromWeb(webStream);
```

Running `deno check` gives this output:

```
error: TS2345 [ERROR]: Argument of type 'ReadableStream<any>' is not assignable to parameter of type 'import("stream/web").ReadableStream<any>'.
  Property 'values' is missing in type 'ReadableStream<any>' but required in type 'import("stream/web").ReadableStream<any>'.
Readable.fromWeb(webStream);
                 ~~~~~~~~~
    at file://~/Desktop/type-bug.ts:3:18

    'values' is declared here.
            values(options?: { preventCancel?: boolean }): AsyncIterableIterator<R>;
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        at file://~/Library/Caches/deno/npm/registry.npmjs.org/@types/node/18.11.18/stream/web.d.ts:142:9
```

This is with Deno 1.34.3.

## Details

Deno ships the right type definitions:

https://github.com/denoland/deno/blob/a8d472f88e79703b1890bfdc87d7a3bb20b21428/ext/node/polyfills/_stream.d.ts#L55-L66

But they aren't getting used. Instead Deno is using the third party type definitions in `npm:@types/node/18.11.18`, which now includes the experimental `ReadableStream.values()` method, which Deno's `ReadableStream` doesn't have.
Repository: godot
Issue: Doubles for the gpu should not be used across the platforms
Labels: enhancement,discussion,topic:rendering

### Godot version

https://github.com/godotengine/godot/commit/1f9e540f14edbf2d496a1421f8d37e5b483c4c53

### System information

Mac Mini, Apple Silicon

### Issue description

https://github.com/V-Sekai/godot/blob/dce1acd183390c6cc44697a8a286b8c9cf990592/servers/rendering/renderer_rd/renderer_canvas_render_rd.cpp#L2523-L2544

```c++
vd.format = sizeof(real_t) == sizeof(float) ? RD::DATA_FORMAT_R32G32B32_SFLOAT : RD::DATA_FORMAT_R64G64B64_SFLOAT;
// ...
vd.format = sizeof(real_t) == sizeof(float) ? RD::DATA_FORMAT_R32G32_SFLOAT : RD::DATA_FORMAT_R64G64_SFLOAT;
```

Avoid using doubles on GPUs across all platforms for better compatibility. Use single-precision floats instead, as they're widely supported and provide sufficient precision for graphics tasks.

See also:

https://github.com/godotengine/godot/pull/78729

and this code

https://github.com/godotengine/godot/pull/67853/files

Mirroring the marshalls.h version.
```c++
Vector<float> float64_to_float32_array(const double *float64_arr, size_t count) {
    Vector<float> floats;
    if (count == 0) {
        return floats;
    }
    floats.resize(count);
    float *floats_w = floats.ptrw();
    for (size_t i = 0; i < count; ++i) {
        floats_w[i] = static_cast<float>(float64_arr[i]);
    }
    return floats;
}
```

### Steps to reproduce

Launch the editor on a mac.


### Minimal reproduction project

Steps apply to any Godot Engine project.
Repository: deno
Issue: import local npm packages
Labels: node compat,triage required 👀

I've been working on supporting Deno in an npm package and I'm trying to automate testing that it's compatible with Deno.  I haven't found any good way to do it... Deno has added support for *importing* npm packages, but it still seems to lack intentional support for *authoring* npm packages to work with Deno.

In CI, before publishing to npm, I have my built package the local disk.  I should be able to somehow import this package in a Deno test file and use it.  But I can't use `npm:` imports on a local folder or package tarball, and I can't use import maps or URLs to a local server because the package code has a bunch of non-Deno-style imports.

Also unlike how in `npm` I can install a tarball served by a local server, I don't think I can do that in Deno, because the docs say that `npm:` specifiers have this format:
```
npm:<package-name>[@<version-requirement>][/<sub-path>]
```
which doesn't appear to allow arbitrary URLs.

I had a messy approach of installing a previous version of the package with `--node-modules-dir` and then overwriting it with my local build of the newer version.  This approach failed once I added a new npm dependency to my package - it didn't get installed for the previous version of my package.

I see that Deno supports custom npm registries, so theoretically I could spin up a custom npm registry locally to serve my local build of the package if I could find some tool for doing so...but should it be that hard?

The only way I'm sure I could do it at the moment is to publish a beta version to npm just so I can import it in Deno.  But publishing before testing is totally backwards, even if only a beta version.  If my Deno test fails then I'd have to publish a new beta version just to test again after making changes.

Is there any way of doing this that I'm missing?