sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Replace FLANN w. nanoflann/Annoy and merge it with Features[2D]
Labels: feature,cleanup

### Describe the feature and motivation

Approximate nearest-neighbor search is very important research and development area of today's AI technologies. Besides computer vision (e.g. in face or scene recognition applications), they are actively used for recommendation systems, e.g. https://www.benfrederickson.com/approximate-nearest-neighbours-for-recommender-systems/.

There are high-profile specialized packages for this task, mentioned in the above paper, such as Annoy, NMSLib, Faiss.

By comparison, FLANN, a fork of it integrated into OpenCV, looks very old and it's not maintained. It is suggested that in OpenCV 5, since we have an opportunity to clean the library, we will remove a separate module FLANN.

The following two options are suggested:
1. use single-header BSD-licensed nanoflann: https://github.com/jlblancoc/nanoflann/tree/master/include. It implements essential subset of FLANN functionality, so it should be a smooth replacement.
2. use Apache-2 licensed Spotify's Annoy library: https://github.com/spotify/annoy. Annoy contains just a few files and so it can also be put directly to OpenCV, without creating explicit opencv/3rdparty entry.

The upgraded 'mini FLANN' (nanoflann or Annoy) can be put to features2d where it logically belongs.

**Probably, features2d should be renamed to features** to reflect that it can be used not just for features extracted from 2D images. The current modern way to compute features is to run a deep learning model.
 


### Additional context

_No response_
Repository: material-ui
Issue: [material-ui][SpeedDial] Bug with right/left direction in persistent action tooltips 
Labels: bug 🐛,component: speed dial,package: material-ui,ready to take

### Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/sad-voice-hnlnfk?file=%2Fsrc%2FDemo.js%3A41%2C24

Steps:
1. Go to the example link
2. Hover over SpeedDial to open Speed Dial Actions

### Current behavior

Speed Dial Actions are over Tooltips, covering them, and don't look good:
![SpeedDial bug](https://github.com/mui/material-ui/assets/60741741/03fd728b-fd49-421d-8036-dbde7b9531e9)



### Expected behavior

Tooltips should be visible and styled correctly when the direction is horizontal.

With **SpeedDial** `direction="right"` or `direction="left"`, Tooltips should be placed on top or bottom of action buttons. I've tried passing `tooltipPlacement="top"` to **SpeedDialAction**, but it doesn't work

### Context

_No response_

### Your environment

<details>

Using Chrome browser.

```
  System:
    OS: macOS 13.5.1
    CPU: (8) x64 Apple M1 Pro
    Memory: 26.90 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 14.18.2 - ~/.nvm/versions/node/v14.18.2/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.12.1 - ~/.nvm/versions/node/v14.18.2/bin/npm
  Managers:
    Homebrew: 4.2.3 - /usr/local/bin/brew
    pip2: 19.2.3 - /Library/Frameworks/Python.framework/Versions/2.7/bin/pip2
    pip3: 21.2.4 - /Library/Frameworks/Python.framework/Versions/3.9/bin/pip3
    RubyGems: 3.0.3.1 - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 15.0.0 - /usr/bin/gcc
    Git: 2.37.3 - /usr/local/bin/git
    Clang: 15.0.0 - /usr/bin/clang
    Curl: 8.1.2 - /usr/bin/curl
  Servers:
    Apache: 2.4.56 - /usr/sbin/apachectl
  Virtualization:
    Docker: 24.0.6 - /usr/local/bin/docker
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
  IDEs:
    IntelliJ: 2020.3.1
    VSCode: 1.85.1 - /usr/local/bin/code
    Vim: 9.0 - /usr/bin/vim
    Xcode: 15.2/15C500b - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Java: 15.0.2 - /usr/bin/javac
    Perl: 5.30.3 - /usr/bin/perl
    Python: 2.7.18 - /Library/Frameworks/Python.framework/Versions/2.7/bin/python
    Python3: 3.9.10 - /Library/Frameworks/Python.framework/Versions/3.9/bin/python3
    Ruby: 2.6.10 - /usr/bin/ruby
  Databases:
    SQLite: 3.39.5 - /usr/bin/sqlite3
  Browsers:
    Chrome: 121.0.6167.160
    Edge: 121.0.2277.112
    Safari: 16.6
```
</details>

**Search keywords**: This issue has not been reported
Repository: next.js
Issue: After cancelling navigation once all future renders of a page component fail to emit routeChangeComplete
Labels: bug,Navigation

### Link to the code that reproduces this issue

n/a

### To Reproduce

I haven't provided code reproducing this because:
- it involves race conditions clicking between links which is hard to replicate
- I think the description of the bug below is hopefully enough to show that there is an issue

To find this error in our app we clicked between tabs on a page (the same route) until eventually clicking the tab does nothing because we don't get the `routeChangeComplete` event to trigger updates to the data shown on the page.

### Current vs. Expected behavior

In `Router.getRouteInfo` (which is called when using `useRouter().push`) previous `routeInfo` for a component is reused https://github.com/vercel/next.js/blob/94c0152f673a70a492e72e7e84591e403fed918c/packages/next/src/shared/lib/router/router.ts#L1957-L1962
Some properties are overwritten https://github.com/vercel/next.js/blob/94c0152f673a70a492e72e7e84591e403fed918c/packages/next/src/shared/lib/router/router.ts#L2167-L2171 but `error` is not.
If a previous navigation has been cancelled, `error` will be set on `routeInfo` and all future renders for that component will throw an error and not emit `routeChangeComplete` https://github.com/vercel/next.js/blob/94c0152f673a70a492e72e7e84591e403fed918c/packages/next/src/shared/lib/router/router.ts#L1758-L1779

This may also impact other failed renders and actions taken after successful navigation but I haven't seen those in our application.

Because the `routeInfo` caching is only used in production, this was quite difficult to debug in development.

### Provide environment information

```bash
n/a
```


### Which area(s) are affected? (Select all that apply)

Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

I considered opening a PR for this, but I'm not sure what the best fix is - whether the cache shouldn't be used when there was previously an error, whether the error should be cleared, or something else.
Repository: opencv
Issue: Move G-API to opencv_contrib or into a separate repository at github/opencv
Labels: feature,RFC,cleanup

### Describe the feature and motivation

G-API is quite interesting technology following a long tradition of graph engines. It's targeted for efficient streaming video/image processing on a variety of devices.

On the other hand, during all this time while G-API is included into OpenCV, it does not look connected or integrated with other parts. It uses different API for video capturing beyond VideoCapture/VideoWriter, it uses different API for inferencing, not OpenCV DNN, it reoptimizes some basic image processing operations without contributing it back to imgproc. It uses quite different coding style. It's quite heavy.

Now, in OpenCV 5 we are going to seriously revise DNN module, where there will be convenient API (similar to PyTorch) to construct graph out of operations. And, of course, it will support pre-recorded and pre-tained graphs in ONNX, TF and other formats. It will also, just like G-API, support GPUs and other accelerators. In other words, with sufficent set of operations OpenCV 5 DNN can play the role of G-API and yet be more practical because of deep learning model support w/o 3rd-party dependencies.

So, to make OpenCV 5 cleaner and smaller it's suggested to move G-API to opencv_contrib or maybe to a separate repository to let it develop separately from OpenCV, as it's logically not a part of OpenCV but rather an engine on top of OpenCV since the very beginning.

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Can't access `parameters` on renderLabel item (SB 7.6.14)
Labels: bug,ui

### Describe the bug

Previously in SB 6, we added custom labels to our stories depending on the `badge` parameters within stories.

After upgrading to SB 7, the parameter object always returns undefined, even when parameters are actually set.

The type `API_HashEntry` tells us that a parameter object should exist, however, that is not actually the case.

I'm aware that `tags` have been added, but unfortunately they don't apply to our usecase

### To Reproduce

https://stackblitz.com/edit/github-hcugjq?file=.storybook%2Fmanager.ts - provided by @JReinhold, thank you.

Or,

In manager.js, simply add 

```js
sidebar: {
    renderLabel: item => {
      console.log(item.parameters)
      return <span>{item.name}</span>
    },
  },
```

to your addons.setConfig().

Watch it show as `undefined` in console.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.3
    CPU: (12) arm64 Apple M2 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn <----- active
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
  Browsers:
    Chrome: 121.0.6167.160
    Edge: 121.0.2277.112
    Safari: 17.3
  npmPackages:
    @storybook/addon-actions: ^7.6.14 => 7.6.14
    @storybook/addon-designs: ^7.0.9 => 7.0.9
    @storybook/addon-docs: ^7.6.14 => 7.6.14
    @storybook/addon-essentials: ^7.6.14 => 7.6.14
    @storybook/addon-links: ^7.6.14 => 7.6.14
    @storybook/addon-mdx-gfm: ^7.6.14 => 7.6.14
    @storybook/addon-styling-webpack: ^0.0.6 => 0.0.6
    @storybook/react: ^7.6.14 => 7.6.14
    @storybook/react-webpack5: ^7.6.14 => 7.6.14
    @storybook/theming: ^7.6.14 => 7.6.14
    chromatic: ^9.1.0 => 9.1.0
    eslint-plugin-storybook: ^0.5.6 => 0.5.12
    storybook: ^7.6.14 => 7.6.14
```


### Additional context

_No response_
Repository: opencv
Issue: Clean Imgproc module
Labels: feature,cleanup

### Describe the feature and motivation

Image processing (imgproc) is one of OpenCV flagship modules, actively used by many people, even in deep-learning era. Most of the stuff it contains is quite useful, but there is some old, obsolete functionality.

Let's clean it up a bit in OpenCV5. Namely:

* Move old corner detectors to opencv_contrib/ximgproc: cornerMinEigenVal, cornerHarris, cornerEigenValsAndVecs, preCornerDetect. Those functions are all well replaced with goodFeaturesToTrack.
* Move accumulate*() to opencv_contrib (or to some compatibility header). accumulate() and accumulateWeighted() are already covered by add() and addWeighted(). The other 2 can be replaced with slightly less efficient combination of 2 functions: multiply() and add(). There is no much use for those functions currently. 
* move EMD (Earth mover distance) to opencv_contrib.
* possibly remove compeltely pyrMeanShiftFiltering. It's very old algorithm for image segmentation that gives very poor quality by today's standards.
* move moments() and HuMoments() to opencv_contrib.
* move HoughLines (all variations), HoughCircles(), GeneralizedHoughTransform and LSD (line segment detector) to opencv_contrib. Currently there are significantly, incomparably better deep learning methods to detect lines, circles and other simple objects that with proper optimizations and some tricks can be made as efficient as the traditional methods (or even more efficient when using dedicated accelerators). See https://arxiv.org/pdf/2003.04676.pdf for example
* not to remove, but we need to normalize color conversion API. The new cvtColor() should take 2 color spaces, input and output, and choose the proper conversion algorithm. It should cover different variations of YUV color space, including subsampled options like 4:2:0, 4:2:2 etc. Color space conversion should also be able to convert the result to proper data type (e.g. FP16 or FP32) with or without scaling. All steps of a complicated color space transformation can likely be fused into a single parallel loop. See also #25012 

### Additional context

_No response_
Repository: PowerToys
Issue: [FancyZones] Windows forced opened on second monitor instead of their previous position on main monitor
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Example with Explorer but it happened with telegram too :
- Set Explorer to any zone
- Switch to another FancyZones Layout and close the Explorer window (or vice versa, doesn't matter)
- Open a new Explorer window
(Bug happens)
- Repeat first two steps but then close Power toys (or disable FancyZones) before repeating third step
(Bug doesn't happen)

### ✔️ Expected Behavior

App's window (explorer in this example) to open in the same position as the one it was in was closed or at the very least, on the same monitor - main one in this case.

### ❌ Actual Behavior

App's window initially opens in the expected position but somehow instantly gets moved to secondary monitor.

### Other Software

_No response_
Repository: rust
Issue: Disabling particular unsafe precondition checks under `-Cdebug-assertions=y`
Labels: C-enhancement,T-compiler,T-libs

From https://github.com/rust-lang/rust/issues/85122#issuecomment-1938599162 and https://github.com/rust-lang/rust/issues/85122#issuecomment-1938688741.

After https://github.com/rust-lang/rust/pull/120594 (1.78), unsafe precondition checks always apply under `-Cdebug-assertions=y`, but there is currently no way to disable particular cases in debug builds:

> They will make things too slow for somebody sooner or later -- it is not uncommon in projects to have a "fast debug" build where a few checks need to be explicitly bypassed in hot paths. And it is not just the branch/call itself, it can also break other optimizations like vectorization: https://godbolt.org/z/MMTordabn.
>
> I really like the unsafe precondition checks, but I would like to make sure there is an escape hatch for `-Cdebug-assertions=y` builds. Perhaps we need a `core::hint::unreachable_unchecked_even_in_debug`-like (even if it does not solve the "there is no checked API" case, but I don't know if that is an issue). For me, `core::hint::unreachable_unchecked` was that in the past, and things like `unwrap_unchecked()` were the "checked in debug" ones.
>
> I also just noticed that using the intrinsic for slice indexing is not enough to remove the check in a debug build and get vectorization back (included in the link).

Cc https://github.com/rust-lang/rust/issues/120848.
Cc @saethlin.
Repository: opencv
Issue: Clean Core module
Labels: feature,cleanup

### Describe the feature and motivation

core module is the cornerstone of OpenCV. It implements basic functionality and so it's used in any OpenCV-based application. Therefore it makes sense to clean it up in OpenCV 5.0 in order to reduce footprint as much as possible. Sometimes this footprint is not just about the consumed space, but also about the compile time overhead.

Here are the suggested items (these are not all the changes proposed for core module in OpenCV 5, a part of them):

* clean modules/core/include/opencv2/core directory as much as possible. Currently there are some obsolete items there and generally the stuff is quite poorly organized. Note that all the programs include many of those headers indirectly, and so it makes compile time longer. Besides, it creates a lot of confusion for people who explore OpenCV source code. These are some examples of headers that can be combined with other headers or removed or moved to other modules or to src directory:
  * neon_utils.cpp, sse_utils.cpp, vsx_utils.cpp. Clearly, they should be removed or duplicated in those .cpp files where the functionality is needed. No need to make this stuff public across modules.
  * quaternion and dualquaternion can be combined. It's just one little and rarely used feature in OpenCV.
  * parallel/ subdirectory - those details should not be exposed outside of the core module. All modules should use cv::parallel_for_().
  * llapi.h name is misleading, the content must be edited and probably revised, merged with some other headers.
  * private/* must be removed
  * the whole stuff in detail/* can be combined with other headers or moved to src.
  * cuda* and cuda/* contain way more stuff than needed. In a separate feature request (TBD) it's suggested to move CUDA completely to 3rdparty/cuda HAL module.
  * affine.hpp should probably be moved to 3d module.
  * etc.
* Remove IPP, OpenVX and CUDA as described in separate tickets (https://github.com/opencv/opencv/issues/24995, https://github.com/opencv/opencv/issues/24996, (TBD for CUDA))
* Probably remove optim.hpp and all the functionality defined in it. Move it to some module in opencv_contrib (or maybe to 3d module if some of this functionality is needed there)
* Remove old data structures (MemStorage etc.) We don't need them anymore (maybe except for Chessboard corner detector)
* Remove SparseMat data structure that we don't need apparently.
* Retain Algorithm, but remove ParamType<> trait.
* Possibly move kmeans, PCA to the refreshed 'Features' module



### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Load any model in specified floating point precision on the fly
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 ?

* Load any model in any floating point precision into specified precision.
* Usecase
  * Load SD1.5 FP32 model into FP16 on the fly, and compute using FP16 instead of FP32 in torch.
  * Load SDXL FP16 model into FP8 on the fly, and compute using FP16 in torch. << (another up coming FP8 feature)

### Proposed workflow

1. Go to model selector and select desired model in any precision
2. The system should load the original model and convert it into specific floating point precision. (can be configured in WebUI or startup argument)


### Additional information

Inspired by the up coming FP8 support.
And think it will be more flexible if we can adjust the desired precision instead of only FP8 option.
Repository: vscode
Issue: Unexpected call to getParent
Labels: bug,error-telemetry,scm

```javascript
Error: Unexpected call to getParent
at Xe.getParent in src/vs/workbench/contrib/scm/browser/scmViewPane.ts:3571:10
at J.expandTo in src/vs/base/browser/ui/tree/asyncDataTree.ts:666:30
at <anonymous> in src/vs/workbench/contrib/scm/browser/scmViewPane.ts:2934:25
at promiseTask in src/vs/base/common/async.ts:239:49
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=31c37ee8f63491495ac49e43b8544550fbae4533&bH=f2f12e0c-70aa-d7b2-f9c5-1c64f5b6068f)
Repository: vscode
Issue: TextModelPart is disposed!
Labels: error-telemetry

```javascript
Error: TextModelPart is disposed!
at h.g in src/vs/editor/common/model/textModelPart.ts:17:10
at h.getWordAtPosition in src/vs/editor/common/model/tokenizationTextModelPart.ts:210:8
at U.getWordAtPosition in src/vs/editor/common/model/textModel.ts:1965:42
at C.h in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:112:22
at new $ in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:98:26
at new C in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:152:3
at M in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:246:10
at computeOccurencesAtPosition in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:708:11
at N.E in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:693:31
at new N in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:342:9
at x in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:791:29
at createWordHighlighterIfPossible in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:799:4
at o.y in src/vs/base/common/event.ts:1127:13
at o.z in src/vs/base/common/event.ts:1138:9
at o.fire in src/vs/base/common/event.ts:1162:9
at x.setModel in src/vs/editor/browser/widget/codeEditorWidget.ts:523:26
at <anonymous> in src/vs/editor/browser/widget/diffEditor/diffEditorWidget.ts:420:29
at fn in src/vs/base/common/observableInternal/utils.ts:179:4
at <anonymous> in src/vs/editor/browser/widget/diffEditor/diffEditorWidget.ts:418:25
at fn in src/vs/base/common/observableInternal/base.ts:281:3
at $Hd in src/vs/base/common/observableInternal/base.ts:319:3
at R.setModel in out/vs/workbench/workbench.desktop.main.js:756:35959
at C.setInput in src/vs/workbench/browser/parts/editor/textDiffEditor.ts:129:12
at async f.S in src/vs/workbench/browser/parts/editor/editorPanes.ts:445:4
at async f.L in src/vs/workbench/browser/parts/editor/editorPanes.ts:270:34
at async f.openEditor in src/vs/workbench/browser/parts/editor/editorPanes.ts:146:12
at async in src/vs/workbench/browser/parts/editor/editorGroupView.ts:1124:49
at async in src/vs/workbench/browser/parts/editor/editorCommands.ts:693:3
at async Tt.sc in src/vs/workbench/contrib/scm/browser/scmViewPane.ts:2856:5
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=31c37ee8f63491495ac49e43b8544550fbae4533&bH=3fafd51d-88cd-90ae-1075-60779e2e40a5)
Repository: vscode
Issue: Cannot read properties of null (reading 'modelInfo')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of null (reading 'modelInfo')
at N.E in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:686:45
at N.B in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:530:8
at a.value in src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts:310:9
at o.y in src/vs/base/common/event.ts:1127:13
at o.z in src/vs/base/common/event.ts:1138:9
at o.fire in src/vs/base/common/event.ts:1162:9
at a.value in src/vs/editor/browser/widget/codeEditorWidget.ts:1720:38
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at E.s in src/vs/editor/common/viewModelEventDispatcher.ts:64:18
at E.endEmitViewEvents in src/vs/editor/common/viewModelEventDispatcher.ts:109:8
at d.S in src/vs/editor/common/viewModel/viewModelImpl.ts:1106:26
at d.setCursorStates in src/vs/editor/common/viewModel/viewModelImpl.ts:1001:15
at W.runCoreEditorCommand in src/vs/editor/browser/coreCommands.ts:676:14
at W.runEditorCommand in src/vs/editor/browser/coreCommands.ts:43:8
at <anonymous> in src/vs/editor/browser/editorExtensions.ts:321:109
at runner in src/vs/editor/browser/editorExtensions.ts:316:11
at fn in src/vs/platform/instantiation/common/instantiationService.ts:68:11
at x.invokeWithinContext in src/vs/editor/browser/widget/codeEditorWidget.ts:439:37
at r.runEditorCommand in src/vs/editor/browser/editorExtensions.ts:309:17
at W.runCommand in src/vs/editor/browser/editorExtensions.ts:321:24
at handler in src/vs/editor/browser/editorExtensions.ts:155:38
at fn in src/vs/platform/instantiation/common/instantiationService.ts:68:11
at k.n in src/vs/workbench/services/commands/common/commandService.ts:95:46
at k.executeCommand in src/vs/workbench/services/commands/common/commandService.ts:60:17
at x.M in src/vs/platform/keybinding/common/abstractKeybindingService.ts:370:29
at x.J in src/vs/platform/keybinding/common/abstractKeybindingService.ts:225:15
at <anonymous> in src/vs/workbench/services/keybinding/browser/keybindingService.ts:281:38
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=31c37ee8f63491495ac49e43b8544550fbae4533&bH=8d887813-ec84-6cc9-3467-9d834fa6044e)