sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Godot Crash When Use 3d In android editor.
Labels: bug,platform:android,topic:editor,needs testing,crash

### Tested versions

4.2.1.stable

### System information

Godot v4.2.1.stable - Android - GLES3 (Compatibility) - PowerVR Rogue GE8320 -  (8 Threads)

### Issue description

Hi, i use godot in mobile, godot in 2d works fine , but when use 3d models, engine crash.
When i import 3d model first time all things work fine but when i second time open scene or run project it crashes note - i use .gItf models. Other formats crash engine instantly.

https://github.com/godotengine/godot/assets/161741769/6e1cc2cd-caa3-491e-ab8e-ae15f611e515



### Steps to reproduce

Create godot porject in android with compatibility render.
Import 3d aniamted character and run scene.
Try to close and reopen scene.

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Output does not display prints after push_warning/push_error calls in EditorScript
Labels: bug,topic:editor,confirmed

### Tested versions

- Reproducible in v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Linux Mint 21.1 (Vera) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6700 XT (RADV NAVI22) () - 12th Gen Intel(R) Core(TM) i5-12400 (12 Threads)

### Issue description

I am making editor scripts. I use prints in order to display informations in the output. But from the moment a warning (or an error) is raised, the console stops from updating.

### Steps to reproduce

1. Create an EditorScript with this code : 

```gdscript
@tool
extends EditorScript

func _run() -> void :
	print("1")
	print("2")
	push_warning("WARNING") # could be push_error instead
	print("3")
	print("4")
```
2. Right click on the script, then execute it
3. See the console : 
```
 core/variant/variant_utility.cpp:1091 - WARNING
1
2
```
**The 3 and 4 do not appear in the console. In order to see them, I have to refresh the console by clicking on filter buttons**. Also, I don't know if it is the intended behavior, but the warning appears first, even though it was called after prints.





### Minimal reproduction project (MRP)

[MRP_RefreshOutput.zip](https://github.com/godotengine/godot/files/14450437/MRP_RefreshOutput.zip)
Repository: godot
Issue: RenderingDevice.draw_list_begin_for_screen() causes crash without errors.
Labels: bug,topic:rendering,crash

### Tested versions

- Reproducible in: 4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1050 Ti () - Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 Threads)

### Issue description

I'm trying to draw a triangle to the screen by using RenderingDevice, and no matter how much i try, the function draw_list_begin_for_screen() causes a crash when i run the project with no explanation whatsoever.
It doesn't crash the editor however, only the game when you hit the "Run Project" button.

If i replace this by adding a custom framebuffer and using a draw_list_begin(), it works fine (but of course it doesn't display anything, so i don't know if its displaying correctly in the first place)

Am i doing something wrong, missing something or is this a bug? If the solution is having to make a custom framebuffer, how do i display the result to the screen?

The full code is just "rendering_test.gd", which contains the entire shader, vertex buffer and index buffer initialization, and the draw process where the crash occurs.

### Steps to reproduce

- Open the MRP (project.zip).
- Open "test.tscn" scene.
- Hit F5 or press the "Run Project" button.

### Minimal reproduction project (MRP)

[project.zip](https://github.com/godotengine/godot/files/14450481/project.zip)
Repository: go
Issue: x/net/internal/quic: TestUDPECN consistently failing with EINVAL on Android
Labels: OS-Android,NeedsInvestigation

### Go version

0784fd1b2f6050b8fb91c88c1d02107258a1651a

### Output of `go env` in your module/workspace:

```shell
N/A
```


### What did you do?

https://build.golang.org/log/6433940bdb66eb651712997e88c329a447a33e15

### What did you see happen?

```
--- FAIL: TestUDPECN (0.01s)
    --- FAIL: TestUDPECN/udp4/udp/unspec (0.00s)
        udp_test.go:89: Write: write udp4 127.0.0.1:42859->127.0.0.1:44007: sendmsg: invalid argument
    --- FAIL: TestUDPECN/udp4/udp4/unspec (0.00s)
        udp_test.go:89: Write: write udp4 127.0.0.1:55776->127.0.0.1:41537: sendmsg: invalid argument
    --- FAIL: TestUDPECN/udp4/udp4/spec (0.00s)
        udp_test.go:89: Write: write udp4 127.0.0.1:45943->127.0.0.1:55286: sendmsg: invalid argument
FAIL
FAIL	golang.org/x/net/quic	22.172s
```

### What did you expect to see?

Tests passing. 

The symptoms are superficially similar to #65907, but in this case the affected builders are little-endian Android.

(attn @dneil, @jba, @golang/android)
Repository: flutter
Issue: macOS build failures are not parsed for common causes
Labels: platform-ios,tool,P2,team-ios,triaged-ios

When a macOS build fails, we don't parse the build output for common causes like we do with iOS. We should do something similar for macOS, or better yet - unify the two to use the same build method and do error parsing within it.

macOS:
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/macos/build_macos.dart#L136-L163
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/macos/macos_device.dart#L69-L80
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/commands/build_macos.dart#L62-L76

iOS:
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/ios/devices.dart#L489-L503
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/commands/build_ios.dart#L662-L681
https://github.com/flutter/flutter/blob/8a11703c6cfc1269aa9ef2789621177f7fed0982/packages/flutter_tools/lib/src/ios/simulators.dart#L565-L575
Repository: PowerToys
Issue: Better Border on Active Application Window
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

The active application window will have a bold border added similar to how _Always On Top_ functions.

### Scenario when this would be used?

Windows 11 looks great but does poorly when trying to quickly determine which application is active due to extremely narrow border even when enabling a drop shadow.

### Supporting information

- https://superuser.com/questions/1749048/how-to-make-it-obvious-if-a-window-has-focus-in-windows-11
- https://answers.microsoft.com/en-us/windows/forum/all/window-borders/e039f5dd-a84f-411b-a94a-02c24566fdfa
- https://answers.microsoft.com/en-us/windows/forum/all/how-to-make-active-window-border-color-color/e563876a-9b3c-4c4a-b58c-824052b6c467
Repository: storybook
Issue: [Bug]: Try to avoid JsPackageManager.retrievePackageJSON usage
Labels: bug,core,monorepos,sev:S2

### Describe the bug

The `JsPackageManager.retrievePackageJSON` method in `@storybook/core-common` returns currently a package.json file which is looked up in the current working directory. 

The `package.json` is used to figure out, 

- whether specific dependencies are installed (for example, which renderer or framework is used).
- to add the Storybook scripts during installation or to manipulate it during automigration
- to remove/add dependencies in the case where we want to skip installation (otherwise JSPackageManager.runAddDeps or JsPackageManager.runRemoveDeps is called, which uses the package manager CLI to remove/add dependencies)
- to evaluate the installed Storybook version

All the mentioned use cases might run into issues when Storybook is used, initialized, or upgraded in a mono repo setup. The folder into which Storybook should be initialized or is already initialized might 

- not have a `package.json`, because dependencies are handled at the root (e.g. NX's one-version policy).
- might have a `package.json`, but only scripts are defined because dependencies are still installed at the root.
- The root (cwd) doesn't have a package.json, but each app does (This case is already more or less handled if the `--config-dir` argument is passed to the CLI (not all CLI commands support --config-dir, e.g. `npx storybook add` doesn't))

When adding or removing dependencies or asking for a particular dependency, we should use always the package manager's CLI commands to get this information, because we simply cannot rely on the package.json, which is defined at the root.

## Acceptance criteria

- Go through the monorepo and figure out, whether `JsPackageManager.retrievePackageJSON` is used in scenarios, which aren't mentioned above.
- Replace each `JsPackageManager.retrievePackageJSON` usage by methods, which call the package manager's CLI directly to get all the necessary information.
- 
### Related issues

- https://github.com/storybookjs/storybook/issues/26259

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: ollama
Issue: keeps loading but never success
Labels: bug,create

ollama run renxin_query_type_classify "hello"
![image](https://github.com/ollama/ollama/assets/16278392/a7ee2375-3493-4d41-b5a6-aa4481e53baf)

I successfully generate a model from gguf file. however keeps loading but never succeed... Any idea what's happening?

FROM ./model_query_type_classify.gguf
PARAMETER temperature 0
SYSTEM """
classify user type
"""
Repository: go
Issue: x/build: LUCI post-submit dashboard known issues
Labels: Builders,NeedsInvestigation,DevExp,umbrella

We're aware of some issues on the LUCI post-submit dashboard (https://ci.chromium.org/p/golang/g/go-gotip/console). This is an umbrella tracking issue to collect most critical ones that affect the Go project's migration to LUCI.

- [ ] row misalignment - in some cases, rows aren't correctly aligned ([crbug.com/41484350](https://crbug.com/41484350), [screenshot](https://github.com/golang/go/assets/1924134/342e89a2-853b-4c89-8ff8-3be740372bea))
- [ ] accessibility issues ([crbug.com/40262374](https://crbug.com/40262374))
- [ ] no paging (only links for up to the 200 latest commits are available)
    - a workaround to see beyond 200 commits: can modify the ?limit=nnn in the URL directly

The LUCI team is working on improvements to this UI. We'll update this as progress is made.
Repository: stable-diffusion-webui
Issue: [Feature Request]: SUPIR upscaler
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 ?

Integrate SUPIR to the list of current upscalers !

SUPIR code : https://github.com/Fanghua-Yu/SUPIR
ComfyUI node : https://github.com/kijai/ComfyUI-SUPIR

It would be pretty awesome to have this feature in webui :) 

### Proposed workflow

Same as current upscalers in extra tab and in hi-res fix

### Additional information

_No response_
Repository: tauri
Issue: [bug] Tauri v2 has constrained compatibility on Linux
Labels: type: bug,status: needs triage

### Describe the bug

(I guess this is just that the minimal version requirements for v2 are > RHEL9 and this is probably wontfix)?

With Tauri v1 we were building with CentOS7. I have just tried to update to Tauri v2 and have had to confront a couple of problems.

1. Tauri v2 requires node v18+ (which seems fair), installing this on CentOS7 is not easy since nodejs dropped support for CentOS 7 in v18 in their upstream builds. There are some unsupported builds, but only for x86_64, not aarch64.
2. Tauri v2 uses a more recent webkit (https://github.com/tauri-apps/tauri-docs/blob/425563db3849ceed10fcc5d1b6d73ea6bc7f1ec4/src/content/docs/blog/tauri-2-0-0-alpha-3.md?plain=1#L32)

In order to fix the first problem I decided to build on CentOS9 stream, which is quite similar to our target platform. However CentOS9 stream uses glib2 2.68.4. Unfortunately the rust crate soup3 requires gio 2.70 and so I can no longer build without moving to Fedora or Ubuntu. (Ubuntu 20.04 which is still in support has the same issue).

### Reproduction

Try to build an example app on CentOS 9 Stream, or Rocky 9, or Ubuntu 20.04.

### Expected behavior

I would expect Tauri v2 to be capable of building on modern enterprise Linux and/or this stuff to be listed in the `What other breaking changes we are going to expect?` section here https://github.com/tauri-apps/tauri-docs/blob/425563db3849ceed10fcc5d1b6d73ea6bc7f1ec4/src/content/docs/blog/tauri-2-0-0-alpha-3.md?plain=1#L32

### Full `tauri info` output

```text
$ yarn tauri info
yarn run v1.22.21
$ tauri info

[✘] Environment
    - OS: CentOS 9.0.0 X64
    ✘ webkit2gtk-4.1: not installed
      Visit https://tauri.app/v1/guides/getting-started/prerequisites to learn more about tauri prerequisites
    ✔ rsvg2: 2.50.7
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ⚠ rustup: not installed!
      If you have rust installed some other way, we recommend uninstalling it
      then use rustup instead. Visit https://rustup.rs/
    ⚠ Rust toolchain: couldn't be detected!
      Maybe you don't have rustup installed? if so, Visit https://rustup.rs/
    - node: 20.9.0
    - yarn: 1.22.21
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.7
    - tauri-build [RUST]: 2.0.0-beta.5
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.3
    - @tauri-apps/cli [NPM]: 2.0.0-beta.6

[-] App
    - build-type: bundle
    - CSP: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src data:; connect-src ipc: http://ipc.localhost
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
Done in 6.22s.
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Improve localization experience of WebViews
Labels: feature-request,l10n-platform

I progress to develoment webview-panel using react. 
(see. https://github.com/microsoft/vscode-webview-ui-toolkit-samples/tree/main/frameworks/hello-world-react-vite )

Couldn't work `l10n.t()` in react app. 
I think that don't load `l10n/bundle.l10n.xx.json`. 

Can I initialize l10n in react app with the same locale as extension?

--
sorry, i'm not good at English.
Repository: pytorch
Issue: make_graphed_callables doesn't turn off autocast for backward
Labels: triaged,module: amp (automated mixed precision),module: cuda graphs

### 🐛 Describe the bug

The `make_graphed_callables` api for applying cuda graphs records both forward and backward kernels in cuda graphs. However, if `make_graphed_callables` is called within an autocast context to use AMP for the forward pass, it will also use autocast for the backward pass. [Pytorch docs](https://pytorch.org/docs/stable/amp.html#torch.autocast) recommends not using autocast for the backward pass. If users run backward outside of autocast during eager training, the ops can be different from the backward cuda graph recorded by `make_graphed_callables`.

Here's an example repro:
```Python
import torch
from torch.cuda.graphs import make_graphed_callables
from torch.testing import assert_close


class Repro(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, a, b):
        scale = 10
        return torch.bmm(a * scale, b * scale)


if __name__ == "__main__":
    baseline_in = (
        torch.randn(2, 576, 1536, device="cuda").requires_grad_(),
        torch.randn(2, 1536, 1536, device="cuda").requires_grad_(),
    )
    candidate_in = tuple(t.detach().clone().requires_grad_() for t in baseline_in)

    half_dtype = torch.bfloat16
    baseline = Repro()
    candidate = Repro()

    with torch.autocast(device_type="cuda", enabled=True, dtype=half_dtype, cache_enabled=False):
        make_graphed_callables(candidate, candidate_in)
    assert all(cc.grad is None for cc in candidate_in)

    with torch.autocast(device_type="cuda", enabled=True, dtype=half_dtype, cache_enabled=False):
        bloss = baseline(*baseline_in).mean()
    bloss.backward()

    with torch.autocast(device_type="cuda", enabled=True, dtype=half_dtype, cache_enabled=False):
        closs = candidate(*candidate_in).mean()
    closs.backward()

    for i in range(len(baseline_in)):
        assert_close(baseline_in[i].grad, candidate_in[i].grad)
```
The assert_close should fail. Interestingly, the assert_close passes if we change the autocast dtype to torch.float16.

Here is a similar issue: https://github.com/pytorch/pytorch/issues/71631

To fix the bug locally, I copied `make_graphed_callables` and disabled autocast when calling `autograd.grad`, and the repro script passes.

We could add this change to `make_graphed_callables`, or, at least provide an option to disable autocast for backward. Happy to make a PR if either option sounds good.




### Versions

Pytorch 2.1, H100 GPU

cc @mcarilli @ptrblck @leslie-fang-intel @jgong5 @ezyang @eellison
Repository: next.js
Issue: fetch with cache: 'no-store' makes output: 'export' ignoring the page
Labels: bug

### Link to the code that reproduces this issue

https://github.com/dominicbachmann/next14-no-store-output-export-bug

### To Reproduce

1. Add `output: 'export'` to next.config.js
2. Use fetch with the `cache: 'no-store'` option on a page 
1. Build the application (npm run build)
3. Check the output
4. /some-page is marked as dynamic

### Current vs. Expected behavior

I expect that some-page is still generated statically

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
  Available memory (MB): 9949
  Available CPU cores: 16
Binaries:
  Node: 18.19.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.81 // Latest available version is detected (14.1.1-canary.81).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: export
```


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

Static HTML Export (output: "export")

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

next build (local)

### Additional context

_No response_
Repository: go
Issue: net: TestVariousDeadlines failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestVariousDeadlines"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/18dec2585c88ccf0ef664b01da8f36118dc09b69)):

    --- FAIL: TestVariousDeadlines (39.58s)
        timeout_test.go:1006: 1ns 0/1
        timeout_test.go:1022: 1ns 0/1: good timeout after 10.811µs; 0 bytes
        timeout_test.go:1006: 2ns 0/1
        timeout_test.go:1022: 2ns 0/1: good timeout after 10.534µs; 0 bytes
        timeout_test.go:1006: 5ns 0/1
        timeout_test.go:1010: dial tcp 127.0.0.1:51510: connect: operation timed out


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/tools/gopls: ignore gopackagesdriver in PATH
Labels: gopls,Tools

There special logic in go/packages to find an external driver from PATH: https://cs.opensource.google/go/x/tools/+/master:go/packages/external.go;l=101;drc=a987ef7aeab9e20797ce48cced2bceb815601f67

This logic continually causes problems for Googlers using gopls, because Google has an internal go/packages driver and certain gopls logic gives up when it encounters an external driver.

We should fix this once and for all. I propose that if GOPACKAGESDRIVER is not explicitly set, gopls sets GOPACKAGESDRIVER=off. Either that, or we remove the PATH lookup from go/packages, though that would require more analysis.

CC @adonovan
Repository: pytorch
Issue: DISABLED distributed/_composable/fsdp/test_fully_shard_training.py::TestFullyShard1DTrainingCompose::test_train_parity_with_activation_checkpointing
Labels: oncall: distributed,module: rocm,module: fsdp

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://www.torch-ci.com/failure?failureCaptures=%5B%22distributed/_composable/fsdp/test_fully_shard_training.py::TestFullyShard1DTrainingCompose::test_train_parity_with_activation_checkpointing%22%5D)).

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: pytorch
Issue: DISABLED test_tp_transform_with_uncovered_op_use_native_funcol_False (__main__.TensorParallelTest)
Labels: oncall: distributed,module: rocm,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2F_tensor%2Fexperimental%2Ftest_tp_transform.py%3A%3ATensorParallelTest%3A%3Atest_tp_transform_with_uncovered_op_use_native_funcol_False%22%5D)).

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: PowerToys
Issue: [Idea] Keyboard-oriented emoji chooser like in Slack system-wide usage
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

I would like to see a new feature in PowerToys, which, when user types colon (`:`) with no following space, will show small tooltip with emoji suggestions on top. 

This feature will be similar to Rocket app for MacOS. Demonstration from their website: 
![bigdemo](https://github.com/microsoft/PowerToys/assets/37851576/373d2cd7-08bd-43b8-8e2b-5dd5bc2c0a27)


Additional suggestions for the feature: 
- Parse emoji codes no matter the input language (transliterate letters in non-enlish locales to show proper emoji suggestions as if the text was inputted in English) 
- Configurable trigger symbol (`:` `::` `\`)
- Configurable codes for specific emojis
- Excluded apps list
 

### Scenario when this would be used?

This will be useful to get ability to quickly insert emojis in apps which don't support keyboard-based emojis. 

### Supporting information

_No response_
Repository: flutter
Issue: Speed up engine `flutter/tools/gn` by not running python code
Labels: P2,team-engine,triaged-engine

This script can take anywhere from 1.5 to >10 seconds to run on an M1 mac, which is too slow.

It is slow because our GN files spawn python scripts using the `exec_script()` function, and those python scripts can be slow for various reasons.

The slow scripts can be identified by examining the traces in chrome tracing format that are written under the root build output directory, e.g. `out/host_debug_unopt/gn_trace.json`.

In many cases, it should be possible to shift these scripts to run as gclient hooks as in https://github.com/flutter/engine/pull/50957 and https://github.com/flutter/buildroot/pull/825.

cc @johnmccutchan
Repository: flutter
Issue: Track the size of the slimmed down engine variant as a benchmark.
Labels: P2,team-engine,triaged-engine,slimpeller
Repository: vscode
Issue: Add "discover" action in the test tree
Labels: feature-request,testing

Currently the test explorer's welcome view has useful buttons for the user to hook up their tests, as contributed by extensions, but it goes away as soon as one test is discovered. We could have a persistent action in the Test Explorer view to allow users to rediscover these actions