sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Editor crashes very often when running 4.1 (through steam)
Labels: bug,topic:editor,topic:thirdparty,needs testing,crash

### Godot version

4.1

### System information

Godot v4.1.stable - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 31.0.15.3640) - 12th Gen Intel(R) Core(TM) i5-12600K (16 Threads)

### Issue description

My editor crashes very often, be it when I save or when I run my game.

It seems to sometimes corrupt some files though i'm not sure about that causality.

I would say it started around the 4.1 update.

It is now to a point where the editor is near unusable.

### Steps to reproduce

Usually after a few modifications the project crashes when I press play or save.

I tried making a smaller project but it wouldn't crash, so you are stuck with my original project

### Minimal reproduction project

[reproducible.zip](https://github.com/godotengine/godot/files/12089232/reproducible.zip)
Repository: flutter
Issue: Add a configuration for Throttling merges per repository in Autosubmit
Labels: team-infra,P2,triaged-infra

When pull requests are merged in quick succession particularly in the flutter/engine repository it can cause an avalanche of queue post submit task causing the tree to become closed, which also has impacts on other repositories tasks queue times. 

One way around this is to add a mechanism for autosubmit to allow a repository to set a throttling mechanism so that autosubmit merges a pull request say every 30 minutes or so. 

Something like:
```
throttle_merges:
  - flutter/engine: 30m
```

If the repository is not present then it will have no throttling applied.
Repository: godot
Issue: Window mode reverts from MODE_FULLSCREEN back to MODE_WINDOWED after minimizing.
Labels: bug,platform:windows,topic:porting

### Godot version

v4.1.1.stable.official.bd6af8e0e

### System information

Windows 10.0.19045 - Vulkan (Compatibility) - GeForce GT 540M- Intel Core i7-2670QM CPU @ 2.20GHz (8 Threads)

### Issue description

Setting the mode of the root window to MODE_FULLSCREEN, then to MODE_MINIMIZED and then manually maximizing it, causes it to go back to MODE_WINDOWED.

The window was full screen before the minimization happened, and was never set to any other mode since, so it would make sense that is should be full screen again after the minimization ended.

https://github.com/godotengine/godot/assets/84321760/a0ddfa54-96fd-4379-aff7-9b6736132f6e



### Steps to reproduce

0. Use the minimal reproduction project.
1. Run the project.
2. Manually maximize the window (by clicking it on the task bar.)
3. Notice that it is in windowed mode, while it was full screen before minimization.

### Minimal reproduction project

[Window-Mode-Reset-Test-4.1.1.zip](https://github.com/godotengine/godot/files/12089347/Window-Mode-Reset-Test-4.1.1.zip)
Repository: vscode
Issue: View state doesn't seem to be initialized/restored properly anymore
Labels: bug,workbench-views

I'm not sure when this started (maybe around when profiles landed?), but on new windows/workspaces VS Code doesn't seem to apply the view state from a previous window nor does it set the views to their `package.json` defaults. Instead it seems to collapse them all.

I see this with GitLens everytime I open a new worktree (which is a new workspace or folder) and all the views in the SCM sidebar are collapsed.

Related issue: https://github.com/gitkraken/vscode-gitlens/issues/2781
Repository: angular
Issue: warn when default provider overrides custom provider.
Labels: area: core

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

_No response_

### Description

I spent some time debugging why my custom ErrorHandler wasn't being provided, it turns out it was being overridden by a default provider further down in the provider list. It would be nice to have a warning in this situation.

### Proposed solution

n/a

### Alternatives considered

n/a
Repository: next.js
Issue: Playwright tests for Next 13 app using app router fail unless slowMo set fairly high
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 16.14.2
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.11-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/AmyBlankenship/next-contacts-example/tree/feat/add-address

### To Reproduce

- Clone branch above
- yarn install
- npm run test:e2e

Note: if the tests fail, you need to run `posttest:e2e` manually

### Describe the Bug

With the project as committed, the "adding address" test fails in chrome, firefox, and edge (note I disabled safari early on because I was getting failures only in safari and figured it was bc this is a windows machine--not sure if this is relevant).

If you add:

`   launchOptions: {
      slowMo: 1000,
    },`

below line 35 of playwright.config, now chrome and edge pass.

If you change that to
`   launchOptions: {
      slowMo: 2000,
    },`

all three browsers pass.

### Expected Behavior

Should not need to set playwright to slowMo to make tests pass (and if that's necessary, it should be clearly documented). Note that I don't know how to see what the browser versions are in playwright, but I just installed the latest as part of trying to figure this out.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: godot
Issue: Compatibility renderer: V-Sync sets framerate at double the refresh rate
Labels: bug,platform:macos,topic:rendering,topic:porting,confirmed

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Godot v4.1.1.stable - macOS 13.4.1 - OpenGL (Compatibility) - Apple M1 - Apple M1 (8 Threads)

### Issue description

When launching a scene with the Compatibility renderer with V-Sync enabled, the framerate is double the refresh rate. In my case, my display (2020 MacBook Air) has a 60Hz refresh rate, but the framerate is locked at 120 FPS with V-Sync. With both Forward+ and Mobile Vulkan renderers, the framerate is correctly set at 60 FPS.

Previous issues #64475 and #56355 have been posted about this occurring for the Vulkan renderer on macOS prior to 13, but were closed since the issue was resolved with the macOS 13 update. However, this issue is occurring now on macOS 13 for the OpenGL Compatibility renderer.

### Steps to reproduce

1. Create a new project with the Comatibility renderer.
2. Create a new Node2D or Node3D scene.
3. Run the scene with V-Sync enabled (default).

### Minimal reproduction project

I display the FPS by adding a Label to the Node2D or Node3D with the following script:

```GDScript
extends Label

func _process(delta):
	text = "%s: %d" % [get_parent().name, Engine.get_frames_per_second()]
```
Repository: vscode
Issue: PATH mutation using EnvironmentVariableCollection prepend is overwritten in zsh
Labels: bug,macos,terminal-process

- VS Code Version: 1.80.1
- OS Version: Darwin x64 22.5.0

VS Code Go extension  tries to  change the integrated terminals' PATH environment variable using `EnvironmentVariableCollection.prepend` api. 

I verified that the change contribution is known to vscode using  "Terminal: Show Environment Contributions" command.

```
# Terminal Environment Changes

## Extension: golang.go

- `PATH=/Users/hakim/sdk/go1.20.3/bin:${env:PATH}`

## Extension: vscode.git

- `GIT_ASKPASS=/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/askpass.sh`
...
```

When I create a terminal tab with `bash`, I see the PATH change applied and go sdk path prepended as expected.

But, when I create a terminal with `zsh`, it looks like zsh prepends the login shell PATH again after applying our extension's PATH change.

Note all `"terminal.integrated.profiles.*"` settings were default.

A workaround I found is to remove `"-l"` arg from the default `"terminal.integrated.profiles.osx.zsh"` setting. But I don't know if it's ok to recommend this change to all zsh users.  I see the default `"terminal.integrated.profiles.osx.bash"`  also has `"-l"` but this bad interaction doesn't happen.  Is it a known issue, or it is WAI?
Repository: go
Issue: reflect: reflect.StructOf makes types that violate reflect.Type contracts
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sz/.cache/go-build"
GOENV="/home/sz/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/sz/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/sz/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.6"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2006396805=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

Consider the following code: https://go.dev/play/p/6MPHjq0B5km

It invokes `reflect.StructOf` method with two embedded fields, a struct and an interface. The resulting type has three methods, according to `reflect.Type.NumMethod()` function. The method list isn't lexicographically sorted and contains duplicates.

`reflect.StructOf` has its limitations documented in godoc, but it doesn't explain the observed behavior.

### What did you expect to see?

Output:
```
Method 0: M1
Method 1: M2
```


### What did you see instead?

Output:
```
Method 0: M1
Method 1: M2
Method 2: M1
```
Repository: rust
Issue: Missing optimization with `transmute_copy` on enums
Labels: I-slow,T-compiler,C-bug,C-optimization

Similar to #109958, but with `transmute_copy`. Transmuting a fieldless enum to it's integer type causes the optimizer to lose track of it's possible values.

Example:
```rust
#[repr(u32)]
enum E { X = 0 }
fn f(x: E) {
    assert_eq!(unsafe { *core::mem::transmute_copy::<E, i32>(&x) }, 0); // Not optimized out
}
```

cc Lokathor/bytemuck#175
Repository: kubernetes
Issue: k8s.io/client-go: misuse of http.DefaultClient in rest.HTTPClientFor
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

Hello,

I am opening this issue to discuss a potential misuse of `http.DefaultClient` in `k8s.io/client-go/rest.HTTPClientFor`. The function appears to make the assumption that `http.DefaultClient` will always use `http.DefaultTransport`, which may not be the case.

For context, this is the function in question: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/rest/transport.go#L29-L48

### What did you expect to happen?

I would expect to be able to change `http.DefaultTransport` without implicitly impacting the behavior of Kubernetes clients that have a different configuration.

### How can we reproduce it (as minimally and precisely as possible)?

Take this code as example:
```go
package main

func init() {
    // change the default client transport's to something custom
    http.DefaultClient.Transport = &http.Transport{
        ...
    }
}

func main() {
   ...
}
```

In this example, invocations of `rest.HTTPClientFor` which resolve the transport to `http.DefaultTransport` will mistakenly assume that they can use the default client because the configuration of `http.DefaultClient.Transport` may not match `http.DefaultTransport` anymore.

### Anything else we need to know?

The check to fallback to `http.DefaultClient` in `rest.HTTPClientFor` seems to be intended as an optimization. Fixing the implementation could look like this:
```go
if transport != http.DefaultClient.Transport || (transport == http.DefaultTransport && http.DefaultClient.Transport != nil) || config.Timeout > 0 {
    httpClient = &http.DefaultClient{
        Transport: transport,
        Timeout:   config.Timeout,
    }
} else {
    httpClient = http.DefaultClient
}
```

However, this fix example highlights the tight coupling between this optimization and the inner implementation of `http.Client`. I would like to suggest removing it and always creating a new `http.Client` regardless of which transport is resolved from the configuration to simplify the code and avoid regressions that could be difficult to anticipate or track down.

To summarize, the function would be modified to always do:
```go
return &http.Client{
    Transport: transport,
    Timeout:   config.Timeout,
}
```

Happy to submit the fix if there is a consensus on the issue.

### Kubernetes version

All recent k8s.io/client-go versions are affected

### Cloud provider

N/A

### OS version

All OS versions are affected

### Install tools

_No response_

### Container runtime (CRI) and version (if applicable)

_No response_

### Related plugins (CNI, CSI, ...) and versions (if applicable)

_No response_
Repository: opencv
Issue: OpenCV memory management does not support the form of dma buf
Labels: feature,category: core,category: videoio(camera)

### Describe the feature and motivation

opencv is widely used in image processing. Many arm linux devices use opencv to process camera data, while camera data generally uses dma buf. To directly use dma buf for opencv, cpu is required to participate, and dma buf is converted into virtual address buf. Will dma buf support be added in a later release?

### Additional context

_No response_
Repository: vscode
Issue: incorrect indentation detection
Labels: bug,editor-indent-detection

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.81.0-insider (4390ebc406732e5b4eed22a1d7aa4fc0ef4a9460)
- OS Version: Windows 10.0.19045

Steps to Reproduce:

1. using a fresh VS Code, create a new HTML file and paste the content below
```html
<ul>
<li><a href="https://foo.bar">
link - one</a></li>
<li><a href="https://foo.bar">
link - two</a></li>
</ul>
```
2. format the document
3. save the file, close the file, close VS Code, reopen VS Code, reopen the file

Expected: VS Code sets indentation to `Spaces: 4`, as that's what the document was formatted with
Actual: VS Code sets indentation to `Spaces: 8`
Repository: tauri
Issue: [bug] tauri 2.0 is not yet able to recognise the theme used on the phone 
Labels: type: bug,status: needs triage

### Describe the bug



![image](https://github.com/tauri-apps/tauri/assets/47310777/ca775f19-2ef2-453b-9cdb-fd631f91386a)
![image](https://github.com/tauri-apps/tauri/assets/47310777/72163b41-c3c2-4956-8924-ac19127a877a)


### Reproduction

_No response_

### Expected behavior

_No response_

### Platform and versions

```text
adnroid tauri2.0
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: kubernetes
Issue: PodresourceAPI reports about resources of pods in terminal phase
Labels: kind/bug,sig/node,triage/accepted

### What happened?

PodResourcesAPI provide a `List()` endpoint which reports about all the resources that consumed by pods and containers on the node.

The problem is that pods which are in terminal phase (i.e. are in `Failed` or `Succeeded` status) are reported as well. about The internal managers reassign resources assigned to pods in terminal phase, so PodResources should ignore them, because they can still be in used.

### What did you expect to happen?

PodResources should ignore and not reports about resources which are in used by pods which are in terminal phase.

### How can we reproduce it (as minimally and precisely as possible)?

Provided a new test-case that demonstrates the exact problem and can be used as a reproducer:  https://github.com/kubernetes/kubernetes/pull/119402 

### Anything else we need to know?

The docs that describes PodResourceAPI are not refer explicitly to whether `List()` should ignore terminal pod's resources or not, meaning it might not be a bug at all.

OTOH, internal managers reassign resources assigned to pods in terminal phase so it make sense to not account them.

### Kubernetes version

Kubernetes v1.26.2

### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: vscode
Issue: Disposing a webview view when extension host is restarted
Labels: bug,help wanted,webview-views

Originally in https://github.com/microsoft/vscode-pull-request-github/issues/4872#issuecomment-1573555380

Here is what I see happen:
1. Open a folder
2. Have an extension that creates a webview view
3. Keep the webview view open
4. Add a folder to the workspace, which causes the extension host to be restarted. 
5. The extension's `deactivate` gets called as expected. In `deactivate` the extension `dispose`s of the webview view provider. 
6. With this `dispose` I would expect the webview view to hide, but it does not.

You can easily reproduce the above using the GitHub Pull Request extension with the steps linked from the original issue.
Repository: opencv
Issue: Calib3d_SolvePnP.generic fails with ENABLE_FAST_MATH option
Labels: bug,optimization,category: calib3d

### System Information

OpenCV: current 4.x (4.8.0-dev)
Platform: Ubuntu 18.04, GCC 7.5
Hardware: Core i5 2500k (no avx2 and no avx512)

### Detailed description

Accuracy test failure

### Steps to reproduce

```
cmake -DENABLE_FAST_MATH=1 ../opencv
make -j4
./bin/opencv_test_calib3d --gtest_filter=Calib3d_SolvePnP.generic
```

Log:
```
[ RUN      ] Calib3d_SolvePnP.generic
/home/alexander/Projects/OpenCV/opencv-master/modules/calib3d/test/test_solvepnp_ransac.cpp:1490: Failure
Value of: isTestSuccess
  Actual: false
Expected: true
[  FAILED  ] Calib3d_SolvePnP.generic (10 ms)
```

### 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: tensorflow
Issue: Tensorflow and onednn logs
Labels: stat:awaiting tensorflower,type:support,comp:mkl

Hi, 
    I am trying to analyse the call flow of tensorflow and onednn. I am setting up environment vars as 
export ONEDNN_VERBOSE=1
export TF_CPP_MAX_VLOG_LEVEL=1  
export omp_num_threads=1

I am collecting the logs. I was trying to map _mklops with onednn primitive. But here the onednn and mkl calls are random in log that is after 10 mkl calls I am seeing 20 onednn calls. 

Is there any flags need to be set to get logs with correct mapping  or do we need to map manually
[filtered_intel_log.txt](https://github.com/tensorflow/tensorflow/files/12093285/filtered_intel_log.txt)
Repository: tensorflow
Issue: TensorFlow Lite Converter wraps unpack operator with dequantize/quantize
Labels: stat:awaiting tensorflower,type:bug,TFLiteConverter,ModelOptimizationToolkit,TF 2.12

### System information

- Linux Ubuntu 20.04
- TensorFlow installed from: pip source
- TensorFlow versions: 2.12.0-current master 

### Code

Provide code to help us reproduce your issues using one of the following options:

```
import tensorflow as tf
from tensorflow.keras.layers import Layer, Input
from tensorflow.keras.models import Model
import numpy as np

class UnstackLayer(Layer):
    def __init__(self, **kwargs):
        super(UnstackLayer, self).__init__(**kwargs)

    def call(self, inputs):
        unstacked = tf.unstack(inputs, axis=1)
        # only last output is used as input to the add operator
        return unstacked[-1]

input_tensor = Input(shape=(4, 16, 32))
x = UnstackLayer()(input_tensor)
output_tensor = tf.add(x, 1)

model = Model(inputs=input_tensor, outputs=output_tensor)

converter = tf.lite.TFLiteConverter.from_keras_model(model)
converter.optimizations = [tf.lite.Optimize.DEFAULT]

def representative_data_gen():
  for input_value in [np.random.randn(1, 4, 16, 32).astype(np.float32) for _ in range(10)]:
    yield [input_value]
converter.representative_dataset = representative_data_gen

converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS_INT8]
converter.target_spec.supported_types = {tf.int8}

converter.inference_input_type = tf.int8
converter.inference_output_type = tf.int8

tflite_model = converter.convert()


# Save the TFLite model to a .tflite file
with open('model.tflite', 'wb') as f:
    f.write(tflite_model)
```

### Failure after conversion

Input Model:

![Screenshot from 2023-07-19 11-05-35](https://github.com/tensorflow/tensorflow/assets/112401409/dabb3863-54c3-4148-bcab-e4afd39a4ac5)

Output Model:

![Screenshot from 2023-07-19 11-28-39](https://github.com/tensorflow/tensorflow/assets/112401409/f42419d0-0365-4738-bd0c-0bf9dc24b798)


Behaviour in TF 2.11 and below is that no dequantize/quantize ops appear, which is expected.  

### Other info

The conversion started failing with version TF 2.12.0. Note that the conversion succeeds intermittently when converting the same network many times, but on average it fails. This intermittent behaviour is still present if one runs the converter on a single core and keeps the representative dataset constant. Similar issues seems to be present when converting split operators as well.