sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Windows 11 Crashes Just opening a project/create node
Labels: bug,needs testing,crash

### Tested versions

4.3 stable

### System information

Windows 11

### Issue description

Constant errors in console showing the following:

```
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
OpenGL API 3.3.0 NVIDIA 560.94 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 3080

Editing project: C:/Users/Joshua/Documents/tutorial
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
Vulkan 1.3.280 - Forward+ - Using Device #0: NVIDIA - NVIDIA GeForce RTX 3080

ERROR: Condition "err != VK_SUCCESS && err != VK_SUBOPTIMAL_KHR" is true. Returning: FAILED
   at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2344)
ERROR: Condition "err != VK_SUCCESS && err != VK_SUBOPTIMAL_KHR" is true. Returning: FAILED
   at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2344)
ERROR: Condition "err != VK_SUCCESS && err != VK_SUBOPTIMAL_KHR" is true. Returning: FAILED
   at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2344)
ERROR: Condition "err != VK_SUCCESS && err != VK_SUBOPTIMAL_KHR" is true. Returning: FAILED
   at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2344)
```

### Steps to reproduce

Open a project, click + Add Node

### Minimal reproduction project (MRP)

A brand new empty project
Repository: langchain
Issue: safe_mode Parameter in ChatMistralAI Class Should Not Be Set to False by default or safe_prompt body parameter not sent to mistral api
Labels: 🤖:bug,investigate,🔌: mistralai

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

```python
        llm = ChatMistralAI(
            client=httpx.Client(
                base_url=llm_creds.api_base,
                headers={
                    "Content-Type": "application/json",
                    "Accept": "application/json",
                },
                timeout=120,
            ),
            temperature=temperature,
            max_tokens=max_tokens,
            model_name="mistral-large",
            safe_mode=False,
            mistral_api_key=llm_creds.api_key,
            max_retries=5,
        ), None
```

### Error Message and Stack Trace (if applicable)

error 422 from Mistral API called through langchain

### Description

I am encountering an issue with the ChatMistralAI class where the `safe_mode` parameter, which corresponds to the `safe_prompt` parameter in the [Mistral documentation](https://docs.mistral.ai/capabilities/guardrailing/), is set to False by default or sent by default to false. According to the Mistral API the safe_prompt parameter cannot be set to False. If this parameter is set to False, the API returns a 422 error. to disable the safe_prompt feature it should not be sent

## Steps to Reproduce:
Initialize an instance of the ChatMistralAI class with the default settings.
Call a method that triggers an API request with the safe_prompt parameter set to False.
Observe the 422 error returned by the Mistral API.
Expected Behavior:
The safe_mode parameter should not be set to False by default or sent by default. Instead, it should either be set to True by default or omitted from the request altogether, unless explicitly set by the user.

## Actual Behavior:
When the safe_mode parameter is set to False (the current default) or sent by default, the Mistral API returns a 422 error, indicating that the safe_prompt parameter should not be False.

## Suggested Fix:
Update the ChatMistralAI class to ensure that the safe_prompt body parameter is omitted from the request unless explicitly specified by the user with `safe_mode` enabled.

### System Info

mac and linux, and last version of langchain
Repository: PowerToys
Issue: Screen Ruler Black Screen
Labels: Issue-Bug,Needs-Triage,Product-Screen Ruler

### Microsoft PowerToys version

0.84.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Screen ruler

### Steps to reproduce

Using the shortcut to launch the screen ruler and then selecting a ruler type. As soon as the measurements start showing up the screen goes completely black, apart from the line and values the Screen Ruler provides.

### ✔️ Expected Behavior

No black screen.

### ❌ Actual Behavior

Ruler is engaging with applications in the background and my wallpaper. But its all hidden behind a black screen. I can scroll to change the pixel sensitivity, and i can see the ruler find contrast in different part of screen where an application's window might have ended. 

### Other Software

softwares running in BG
- Netflix (installed via Edge)
- Thorium 
- Whatsapp
- Windows Phone Link
Repository: deno
Issue: Feat: simplify lint configuration
Labels: config,lint

From time to time a user mixes up `lint.exclude` with `lint.rules.exclude`. The most recent case of that is here https://discord.com/channels/684898665143206084/1280845408758927401/1280845408758927401

```json
{
  "lint": {
    "exclude": ["no-window"]
  }
}
```

instead of:

```json
{
  "lint": {
    "rules": {
      "exclude": ["no-window"]
    }
  }
}
```

It's an easy mistake to make given that we use the same schema for files and lint rules. I wonder if we can avoid that confusion. One idea could be to make the config more like other linters:

```json
{
  "lint": {
    "rules": {
      "no-window": false
    }
  }
}
```
Repository: go
Issue: proposal: image: add (Rectangle).PointsBy for iterating over points as iter.Seq[Point]
Labels: Proposal

### Proposal Details

## Summary

I propose adding a new method `PointsBy` to `image.Rectangle`
that returns an `iter.Seq[image.Point]` for points within the rectangle.
This function would allow developers to directly iterate over points in a rectangle,
making the code more straightforward and reducing potential errors.

The `PointsBy` can be implemented as follows.

```go
func (r Rectangle) PointsBy(delta Point) iter.Seq[Point] {
    return func(yield func(Point) bool) {
        for y := r.Min.Y; y < r.Max.Y; y += delta.Y {
            for x := r.Min.X; x < r.Max.X; x += delta.X {
                if !yield(image.Pt(x, y)) {
                    return
                }
            }
        }
    }
}
```

By this function, the common pattern with a `image.Rectangle` `r`

```go
for y := r.Min.Y; y < r.Max.Y; y++ {
    for x := r.Min.X; x < r.Max.X; x++ {
        p := image.Pt(x, y)
        // Do something with p.
    }
}
```

could be simplified to

```go
for p := range r.PointsBy(image.Pt(1, 1)) {
    // Do something with p.
}
```

## Background

- Iterating over points within a rectangle is a common operation in image processing tasks.

- This operation requires manually writing nested loops every time.
    While not complex, it can indeed be cumbersome and repetitive.

- Since `image.Rectangle` does not necessarily start at `(0, 0)`, it's crucial to loop from `Min` to `Max`, as documented.
    However, there are cases where developers mistakenly start from `0`.

Given this background, it may be beneficial to provide a dedicated API from the `image` package 
to better address this demand for iterating over points.

## Benefits

- Provides a direct API for iterating **over `image.Point`s** not over Xs and Ys within an `image.Rectangle`.

- Eliminates the need for additional labels when breaking out of nested loops under specific conditions, such as

```go
pointsLoop:
    for y := r.Min.Y; y < r.Max.Y; y++ {
        for x := r.Min.X; x < r.Max.X; x++ {
            // if (x, y) meets a certain condition
            break pointsLoop
        }
    }

    // then
```

- Supports non-unit steps (e.g., `y += 2`, `x += 3`) by taking a `delta` parameter, keeping flexibility.

- Aligns well with the `iter` package, enhancing integration with the iterator-based approach.

## Considerations

Beyond this proposal, a few additional considerations might be relevant.

- Whether to use `image.Point` to express delta (as `image.Rectangle.Size` does with `func() image.Point`) or `x, y int` (as `image.Image.At` does with `func(x, y int) color.Color`).

- The `iter` package was added recently, and its adoption and consensus within the community might still be evolving.
Repository: vscode
Issue: [Accessibility] The dragging movement in split panel functionality needs a single pointer trigger.
Labels: bug,accessibility,sash-widget

- VS Code Version: 1.88.0
- OS Version: MacOS Sonoma (v14.6.1) 

**[Issue]**
The split panel functionality uses a dragging movement with no other single-pointer trigger. 

**[User Impact]**
Users with dexterity and mobility disabilities may be unable to perform dragging movements to use this functionality.

[Code Reference]
```
<div class="monaco-sash vertical" style="left: 288px;"></div>
```

**[Recommendation]**
Ensure all functionality that uses a dragging movement can be operated by a single pointer without dragging. One way to meet this requirement is to require users to perform a series of single-pointer, non-path-based interactions instead of dragging. Keyboard alternatives are not sufficient to meet this requirement. Exceptions include freeform drawing or games that require dragging.

Screenshot:
![Screenshot 2024-09-04 at 5 48 55 AM](https://github.com/user-attachments/assets/1542c750-d002-48ff-b4d4-0f6d79a2c2a0)
![Screenshot 2024-09-04 at 5 49 50 AM](https://github.com/user-attachments/assets/1e094ad7-37fc-4bd7-8313-32fe0cf17392)
Repository: vscode
Issue: [Accessibility] The Explorer section view needs role and name information.
Labels: bug,accessibility

- VS Code Version: 1.88.0
- OS Version: MacOS Sonoma (v14.6.1) 

**[Issue]**
The tab panel for "Explorer (Ctrl+Shift+E) - You have 1 unsaved changes" tab lacks name and role information. 

**[User Impact]**
Screen reader users will be unable to determine that these controls reveal panels of content and which panel is currently revealed.

**[Code Reference]**
```
<div class="part sidebar left pane-composite-part" id="workbench.parts.sidebar" **role="none"** 
(...)>
</div>
```
**[Recommendation]**
Ensure page tabs provide state and role.

For tabs, the following information is expected:
- Each panel container must have role="tabpanel".
- If the tablist has a visible label, the tablist element must have aria-labelledby set to the ID of the labelling element. Otherwise, the tablist element must have aria-label set to the accessible name.
- Each tab must have aria-controls set to the ID of its corresponding tabpanel.
- Tabpanel elements must have aria-labelledby set to the ID of their corresponding tab.
- If the tablist is vertically oriented, it must have aria-orientation="vertical".

**Note**: Also when contributes any new extension webviews/tree views, ensure to have aria attributes corresponding to the Explorer tabpanel section.

**Steps to Reproduce:**
1. Open VSCode.deva and under Explorer panel section, the accessible `role="tabpanel"` and `aria-labelledby` is missing.

Screenshot:

![Screenshot 2024-09-04 at 6 08 19 AM](https://github.com/user-attachments/assets/4c685726-7a6e-4c88-b1af-e8f7a40772bd)
Repository: PowerToys
Issue: PowerToys Workspaces: a shortcut per workspace.
Labels: Needs-Triage,Needs-Team-Response,Product-Workspaces

### Description of the new feature / enhancement

It would be useful to be able to have a specified shortcut for each Workspace.
For example, by pressing Windows+Ctrl+1 my 1st workspace launches directly, by pressing Windows+Ctrl+2 my 2nd workspace launches directly (by first closing all apps opened by any previous workspace?), etc.

### Scenario when this would be used?

This is very practical since I can go directly from powering on my system to launching my workspace with the press of a single shortcut. Now that I think of it, along with the above, why not have the option of launching a specific Workspace on startup?

### Supporting information

_No response_
Repository: vscode
Issue: Underscores not visible in search in Ubuntu 24.04.1 LTS
Labels: upstream,upstream-issue-pending

<!-- ⚠️⚠️ 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. -->
Version: 1.92.2
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Linux x64 6.8.0-40-generic snap

Steps to Reproduce:

1. Use underscores in search in the lower fields
2. See screencast

[Screencast from 2024-09-04 16-24-34.webm](https://github.com/user-attachments/assets/5b0a92fb-1f79-4fca-ac5b-b07e068c7321)
Repository: ui
Issue: Add Success Variant to Toast Component
Labels: area: request

### Feature description

This contribution introduces a new success variant to the toast notification component. The success variant is designed to provide visual feedback for successful actions by displaying a green background with white text. This enhancement allows developers to easily use a predefined style for success messages within the toast component, improving the consistency and usability of notifications across the application.

### Affected component/components

Toast

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: opencv
Issue: Make proper layers implementations to support the new dnn engine in 5.x
Labels: feature

See https://github.com/opencv/opencv/pull/26056

The layers are the following:

- [x] Concat
- [x] ConstantOfShape
- [x] [WIP] Einsum (done by @Abdurrahheem)
- [x] Expand
- [x] Gather
- [ ] GatherND
- [ ] GatherElements
- [ ] GRU
- [ ] [WIP] Flatten
- [x] Hardmax
- [ ] [WIP by Abdurrahheem] LSTM
- [x] Mish
- [x] Neg
- [ ] Normalize
- [x] Pad
- [x] Range
- [x] Reshape
- [x] Resize (implementation has been just fixed to pass all tests, but it can be significantly improved)
- [ ] Scatter
- [ ] ScatterND
- [x] Shape
- [x] Slice
- [x] Split
- [x] Squeeze
- [x] Transpose (a.k.a. Permute)
- [x] Tile
- [ ] TopK
- [x] Unsqueeze
- [ ] [WIP] Deconvolution (mostly done, there are just 2 remaining failures)
- [x] DequantizeLinear
- [x] QuantizeLinear
- [ ] QLinearConv

the new implementations must:
1. conform with ONNX specification (https://onnx.ai/onnx/operators/index.html), different opset's
2. not rely on the shape inference being done in ONNX importer
3. preferably, be 'stateless'. In particular, forget about Layer::finalize(). Don't rely on it, leave it empty.
4. support different data types. All the layers that just move tensor elements around without arithmetic operations on them may just have branches for 1-byte, 2-byte, 4-byte and 8-byte elements, then they will support all possible data types, except for the recently added to ONNX specs int4/uint4/float4, which OpenCV does not support anyway (yet)
Repository: next.js
Issue: Catch all route within dynamic segment breaks dynamic params
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/optimistic-brahmagupta-qcqflx

### To Reproduce

1. Start dev server
2. Change locale to be anything but en
3. Page is being rendered / no 404 even though there is dynamicParams = false on the locale's segment level

### Current vs. Expected behavior

Following the steps from the previous section, I expected /de to render a 404, as dynamicParams is false and de ist not listed within the segment's static params. Somehow the nested catch all route breaks this behaviour and makes it fall back to a dynamic behaviour, trying to render the given locale, running into errors because the locale does not exist.

### Provide environment information

```bash
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.0-canary.140 // Latest available version is detected (15.0.0-canary.140).
  eslint-config-next: N/A
  react: 19.0.0-rc-7771d3a7-20240827
  react-dom: 19.0.0-rc-7771d3a7-20240827
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: go
Issue: runtime/race:race: TestOutput failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "runtime/race:race" && test == "TestOutput"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8737753588363053073)):

    === RUN   TestOutput
        output_test.go:83: failed test case wrappersym, expect:
            ==================
            WARNING: DATA RACE
            Write at 0x[0-9,a-f]+ by goroutine [0-9]:
              main\.T\.f\(\)
                  .*/main.go:15 \+0x[0-9,a-f]+
              main\.\(\*T\)\.f\(\)
                  <autogenerated>:1 \+0x[0-9,a-f]+
              main\.main\.gowrap1\(\)
    ...
              main.main.gowrap1()
                  /home/swarming/.swarming/w/ir/x/t/TestOutput26943986/013/main.go:9 +0x68
            
            Goroutine 6 (finished) created at:
              main.main()
                  /home/swarming/.swarming/w/ir/x/t/TestOutput26943986/013/main.go:9 +0x98
            ==================
            Found 1 data race(s)
            exit status 66
    --- FAIL: TestOutput (8.52s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: Movie Writer Colors differ significantly from Rendered Output
Labels: topic:rendering,documentation,needs testing

### Tested versions

Reproducible in 4.3 stable on Windows 11 Pro, with a reasonably recent version of VLC

The color discrepancy exists in VLC Media Player even if all preferences are reset to default.
The color discrepancy is visible in HandBrake preview, but is goine in H.264 output.


### System information

Windows 11 - Godot v4.3.stable.mono.official [77dcf97d8]

### Issue description

Recording a movie results in a movie file whose color grading is quite different from the output shown, both while recording or while playing the scene normally.

![explorer_BOuhoWV6LM](https://github.com/user-attachments/assets/5ba8bcdc-4672-4469-bb6c-b3ff6178e120)


### Steps to reproduce

1. Run the attached Reproduction Project, enabling the movie writer
2. Run it again without recording, and bring the video up in a player on the same screen to compare 
3. Observe: Differences in colors and brightness even with a world environment derived from the default (color differences are somewhat subtle, but usually noticeable, you can use an image capture program to compare)

![image](https://github.com/user-attachments/assets/c74e46e1-5e84-4ddd-b55d-e6a2c09bf4b9)
Screenshot with locally sampled color values in image editor and annotated)




### Minimal reproduction project (MRP)

## Reference Project
[movie-color-grading-bug-repro.zip](https://github.com/user-attachments/files/16872372/movie-color-grading-bug-repro.zip)


## Reference Project Movie File:
[movie.avi.zip](https://github.com/user-attachments/files/16872297/movie.avi.zip)

## "Repaired" Movie after Re-Encoding to H.264 with HandBrake 1.8.1
https://github.com/user-attachments/assets/b29fea98-6fab-4af9-b01d-cf800bd8a55f
Repository: next.js
Issue: Next.js App Router: Server Component with Context Provider and Tailwind causes rendering issues
Labels: create-next-app,bug,Runtime

### Link to the code that reproduces this issue

https://github.com/jmderby/min-repro-next-render-issue

### To Reproduce

1. run `pnpm i`
2. run `pnpm dev`
3. visit localhost:3000, see console logs not display on the client browser console.
Caveat: Issue will reproduce intermittently, to repro successfully, restart the Next.js server. 

### Current vs. Expected behavior

- Expected: App mounts and re-renders allowing the `TestProvider`'s console log to print client-side.
- Actual: Server hangs after initial render, blocking further updates and does not print `TestProvider`'s console log client-side. There is sometimes an error that prints which is: `Uncaught SyntaxError: Invalid or unexpected token (at layout.js)`


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.16.0
  npm: 10.8.1
  Yarn: N/A
  pnpm: 9.7.1
Relevant Packages:
  next: 14.2.7 // Latest available version is detected (14.2.7).
  eslint-config-next: 14.2.7
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
  tailwindcss: 3.4.1,
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app, Developer Experience, Runtime

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

This issue seems to be related to the interaction between Server Components, Client Components with Context Providers, and importing `globals.css` which contains the Tailwind directives from the `layout.tsx` Server Component. It persists even when following Next.js best practices for mixing Server, Client Components, and Context Providers.

The issue is most noticeable immediately after starting the development server. If you refresh the page after the initial load, the app typically functions as expected. The problem primarily affects the first render following server startup.

A minimal reproduction repository has been created to demonstrate this issue.

This minimal reproduction was inspired by this Vercel guide of using React Context with Next.js: https://vercel.com/guides/react-context-state-management-nextjs
Repository: bitcoin
Issue: cmake: passing options from depends build to main build
Labels: Brainstorming,Build system

_Originally posted by @hebasto in https://github.com/bitcoin/bitcoin/issues/30800#issuecomment-2326899886_

>I think we should first prioritize coordinating the optimization and debugging flags between the depends subsystem and the main build system:
>1. Should the optimization and debugging flags coincide, or are they allowed to differ?
>2. If the optimization and debugging can differ between the depends subsystem and in the main build system, which should take precedence?