sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Editor interface doesn't recover after resuming Suspend - Windows 7
Labels: platform:windows,topic:editor,topic:porting,needs testing

### Tested versions

4.2.2 - reproduceable

### System information

Windows 7; Godot defaults, Forward+
Godot v4.2.2.stable - Windows 6.1.7601 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (; 30.0.14.7304) - AMD Ryzen 7 1700 Eight-Core Processor (16 Threads)

### Issue description

When I resume my computer after suspending, if Godot was running on the main desktop, it will look like this:

![godot after suspend](https://github.com/godotengine/godot/assets/72134064/17dc9a9f-151a-4948-8ac3-5c73308375d9)

Which is the same as happened when it ran out of RAM: https://github.com/godotengine/godot/issues/92084

I can still interact with the UI, and the bits I interact with get refreshed, but it's overall a mess.

But this happens even if Godot is pretty much the only application running.
All other applications resume just fine.

### Steps to reproduce

1) Start godot editor
2) Create/resume a project (empty project is fine).
3) Suspend PC
4) Resume PC


### Minimal reproduction project (MRP)

n/a
Repository: godot
Issue: Editor crashes doesn't recover after resuming Suspend - Windows 7
Labels: platform:windows,topic:editor,topic:porting,needs testing

### Tested versions

Godot 4.2.2 reproduceable

### System information

Godot v4.2.2.stable - Windows 6.1.7601 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (; 30.0.14.7304) - AMD Ryzen 7 1700 Eight-Core Processor (16 Threads)

### Issue description

I use Microsoft's `Desktops` application to have multiple virtual desktops on Windows 7 - https://learn.microsoft.com/en-us/sysinternals/downloads/desktops

If I have godot editor running on a desktop that's _**not**_ the main one when I suspend the machine, when I resume the machine, Godot will crash. It will eat 100% of one CPU core until I kill it. The application is entirely unresponsive.
![godot 2](https://github.com/godotengine/godot/assets/72134064/8a5efc74-c03f-460a-beac-b1cefae0cf11)
![godot 3](https://github.com/godotengine/godot/assets/72134064/6d6af276-5f5c-419f-8746-83f557e427e7)



If Godot is running in the main desktop, the interface breaks: https://github.com/godotengine/godot/issues/92155 but it doesn't crash.

### Steps to reproduce

* Start godot editor in a desktop that's not the main one
* Create/resume a project (empty project is fine).
* Suspend PC
* Resume PC


### Minimal reproduction project (MRP)

n/a
Repository: react
Issue: [Compiler Bug]: Values used as indexes are not memoized
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAwhALYAOhCmOAFMEQG4CGANlAkQL4CURYAB1iROITA4ieTABMEADyIBeIosq0weZggBiWXAUz02nBHxFEi7BFOg5KUKatNcwAbRnyFAXQDclkQA9EH2js7ScooBojC2sMQAPLLaAHzAYU48iUEpzKkxPDEgPEA

### Repro steps

In the code below, the call to `expensiveFunction(value)` does not appear to be memoized (it is preserved as is at the top level in the JS output).

This seems to be due to it being used as an index in `let output = values[index]`, because when setting `output` to be `index` itself instead, it gets memoized properly.

Code:
```js
function Component({ value }) {
  const index = expensiveFunction(value)
  let output = values[index];
  //output = index;
  return <div>{output}</div>;
};
```

**_Edit:_** 
Additionally, if `index` was manually memoized with `useMemo`, the compiler will remove the manual memoization, resulting in potentially much slower code than the original code.

### How often does this bug happen?

Every time

### What version of React are you using?

19
Repository: deno
Issue: LSP: Autocomplete in `deno.json` not working when offline
Labels: lsp

Was somewhere remote the past day where I had no internet connection. I noticed that the LSP isn't able to provide autocompletions in `deno.json` without an active connection. This is the output from the LSP:

```txt
Download https://deno.land/.well-known/deno-import-intellisense.json
  Error fetching registry config for "https://deno.land": Import 'https://deno.land/.well-known/deno-import-intellisense.json' failed: error sending request for url (https://deno.land/.well-known/deno-import-intellisense.json): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known%
```

Version: Deno 1.43.5
Repository: next.js
Issue: NextNodeServer handleNextImageRequest doens't work as expected with assetPrefix and custom next/image loader
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/friendly-montalcini-mc6sg6

### To Reproduce

1. Start the application in development (next dev)
2. Home page doesn't show image (image returns 404)
3. Disabling i18n in config will display image (can be seen here https://codesandbox.io/p/devbox/frosty-fast-wg5kmc)

### Current vs. Expected behavior

Image should be shown correctly.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.3.0-canary.70 // Latest available version is detected (14.3.0-canary.70).
  eslint-config-next: N/A
  react: 19.0.0-beta-04b058868c-20240508
  react-dom: 19.0.0-beta-04b058868c-20240508
  typescript: 5.1.3
Next.js Config:
  output: N/A
Done in 2.08s.
```


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

Image (next/image)

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

next dev (local), next build (local), next start (local)

### Additional context

https://github.com/vercel/next.js/pull/52492 This pull request not just separated routing code from render servers, but changed how next/image requests are recognized. Before, using regex matched if there is `/_next/image` in path. But now `parsedUrl.pathname` needs explicitly to start with `/_next/image`. But when i18n is enabled in next config, now `parsedUrl.pathname` starts with `/{locale}/{assetPrefix}/_next/image` and fails `parsedUrl.pathname.startsWith('/_next/image')`
Repository: PowerToys
Issue: Improve the mouse crosshair pointer functionality
Labels: Needs-Triage

### Description of the new feature / enhancement

I would like to suggest that when the user selects the 'mouse pointer crosshair' functionality and the mouse pointer is moved to a high resolution screen, that the crosshair strokes are thickened by a parameterized value. For example, it could go from 2 pixels to 4 pixels. With this, the mouse pointer would be visible more easily on high-resolution monitors.
I use this feature because I have two 1080p monitors and one 4K monitor on my computer and it is very difficult to locate the mouse pointer when I move it to the 4K monitor.

### Scenario when this would be used?

It would be very useful for users with monitors with different resolutions, helping to quickly locate the mouse pointer.

### Supporting information

_No response_
Repository: ollama
Issue: qwen模型简介未更新110B
Labels: bug

### What is the issue?

qwen模型简介未更新110B，

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: deno
Issue: deno_vscode feature request: copy inferred type
Labels: feat,lsp

the vscode type peek window truncates the type shown. 
from my testing vscode extensions like [TS type to clipboard](https://marketplace.visualstudio.com/items?itemName=lwkchan.make-a-type) do not work with deno. 
typescript has `tsc filename.ts --declaration --emitDeclarationOnly`
for deno I could only find dnt and the configuration needed for this task seems prohibitive. I think it's a useful feature that should be native anyway.
Repository: tauri
Issue: [bug] Hiding taskbar icons on Linux does not work when using wayland
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

I want to hide the  icon from taskbar by using `main_window.set_skip_taskbar(true)`，but this does't work if the app is running with wayland:
```rust
// Prevents additional console window on Windows in release, DO NOT REMOVE!!
#![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]

use tauri::Manager;

// Learn more about Tauri commands at https://tauri.app/v1/guides/features/command
#[tauri::command]
fn greet(name: &str) -> String {
    format!("Hello, {}! You've been greeted from Rust!", name)
}

fn main() {
    tauri::Builder::default()
        .setup(|app|{
            let main_window = app.get_window("main").unwrap();
            main_window.set_skip_taskbar(true).unwrap(); // This doesn't work when using wayland!
            Ok(())
        })
        .invoke_handler(tauri::generate_handler![greet])
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

```

The icon is still visible in the  taskbar:
![图片](https://github.com/tauri-apps/tauri/assets/16934087/35bb825a-2ea9-40c9-b828-83411c1f4b4a)

 I can hide the icon by forcing the app  to run with x11 (using `GDK_BACKEND=x11` environment variable), but I hope that when running it using native wayland, the application icon can also be hidden from the taskbar.


 

### Reproduction

https://github.com/FengZhongShaoNian/tauri-hide-appicon-from-taskbbar

### Expected behavior

I hope that when running it using native wayland, the application icon can also be hidden from the taskbar.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Arch Linux Unknown X64
    ✔ webkit2gtk-4.0: 2.44.2
    ✔ rsvg2: 2.58.0
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 20.13.1
    - pnpm: 9.1.1
    - npm: 10.5.2

[-] Packages
    - tauri [RUST]: 1.6.6
    - tauri-build [RUST]: 1.5.2
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.5.6
    - @tauri-apps/cli [NPM]: 1.5.14

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: rust
Issue: Type inference failing
Labels: A-inference,C-bug,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
fn foo() -> Option<Box<u8>> {
    todo!()
}

fn bar(_: Option<&u8>) {}

fn main() {
    let mut v = vec![];
    bar(v.last().map(|x| &**x));
    v.push(foo());
}
```
I would expect v to have a knowable type but it's failing with this error:

```
error[E0282]: type annotations needed for `&T`
  --> src/main.rs:11:27
   |
11 |         bar(v.last().map(|x| &**x));
   |                           ^   --- type must be known at this point
   |
help: consider giving this closure parameter an explicit type, where the type for type parameter `T` is specified
   |
11 |         bar(v.last().map(|x: &T| &**x));
   |                            ++++

For more information about this error, try `rustc --explain E0282`.
error: could not compile `tests` (bin "tests") due to 1 previous error
```
It's able to infer it if we swap the lines
```rs
    v.push(foo());
    bar(v.last().map(|x| &**x));
```

### Meta
Tried on nightly and stable
Repository: godot
Issue: Godot Export generates build with no main scene selected (no warning or error)
Labels: discussion,topic:editor,usability,topic:export

### Tested versions

- Reproducible in v4.3.dev6.mono.official [89850d553]


### System information

Godot v4.3.dev6.mono - macOS 14.5.0 - Vulkan (Forward+) - integrated Apple M2 Pro - Apple M2 Pro (10 Threads)

### Issue description

With Godot 4.3-dev6, you can create a project and have it build successfully without having a scene chosen. You will get an error when the application launches, but you will not get a warning that you did not choose a main scene during the export process.

### Steps to reproduce

1. Create a new project
2. Create a 3D Node Scene
3. Save the scene
4. Install the Export Templates
5. Add the platform (MacOS in this case)
7. Export the Project

### Minimal reproduction project (MRP)

[Archive.zip](https://github.com/godotengine/godot/files/15378464/Archive.zip)
Repository: next.js
Issue: Opentelemetry - Spans for static resources and API pages not part of page load trace
Labels: bug,Instrumentation

### Link to the code that reproduces this issue

https://github.com/bradleyberwick/reproduction-otel

### To Reproduce

1. Yarn build
2. Yarn start
3. View traces in local Grafana

### Current vs. Expected behavior

**Current behaviour:**
When I do a full page load in my app (I've added my OTEL config in the repo app), spans are created for the page (e.g. GET /), for static resources (e.g. _next/static/chunks/...js , _next/static/{id}/_buildManifest.js, etc) and API pages (e.g. /api/geoip, etc). Currently these spans are separate and part of different trace ID's.

**Expected behaviour:**
Ideally, I want these spans to be part of the same trace as they're loaded as part of the same page load. I don't think this is possible because the other resources (i.e. static resources and API pages) are pre-built on the server-side and they don't know the trace ID at this point. The calls to these other resources are then made from the client and not via the initial page load request and therefore the context is not propagated.

Can I have some further clarification on this please?


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Enterprise
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Instrumentation

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

next start (local)

### Additional context

_No response_
Repository: pytorch
Issue: Python version agnostic C++ extensions
Labels: module: cpp-extensions,triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

Recording some offline discussions with @drisspg and @malfet and also because this came up again in a thread on Slack

Today, C++ extensions in PyTorch need a separate build per python version. This is for two main reasons:
1. they link against libtorch-python, which has a separate build per python version
2. Python C extensions assume that you need to link against cpython, which invoves a separate build per python version.

Pitch: for C++/CUDA custom-operator only C++ extensions (which is the vast majority of them), if we can excise all the python dependencies, then one should be able to have a single build that works for all Python versions.

cc @malfet @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: pytorch
Issue: DISABLED test_non_commutative_scan_op (__main__.CudaReproTests)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22inductor%2Ftest_cuda_repro.py%3A%3ACudaReproTests%3A%3Atest_non_commutative_scan_op%22%5D)).

Caused by newly-added test in https://github.com/pytorch/pytorch/pull/126633.

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: go
Issue: x/tools/gopls: make eglot+gopls awesome
Labels: gopls,Tools,Friction

@stapelberg and I plan to work together to make Emacs+eglot smoother, faster, and better documented.

Some specific items (feel free to add or suggest more):
- [ ] Code Lenses: support them, or, better, make gopls move all those features to Code Actions, which are better anyway.
- [ ] Add a nice "run this test" UI (see #67400 and https://github.com/joaotavora/eglot/discussions/1402)
  - Approach 1: output certain executeCommands to a compilation-mode buffer. Needs no LSP changes initially, just a list of command IDs to treat this way; ultimately the Command would provide this information. Prototype implemented.
  - Approach 2: express it entirely within the WorkDoneProgress mechanism: change the server to indicate that a given progress stream should be directed to a buffer, and formalize the final success/failure protocol.
- [ ] support `didChangeWatchedFiles` for unopened files on macOS (see #62330)
  - This Emacs bug report explains that the underlying cause is a limitation of using kqueue on macOS: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51146 — possibly contributing fsevents support to Emacs’s filenotify package would fix the problem.
- [ ] fix `didChangeWatchedFiles` to work recursively? The underlying Emacs `filenotify` package does not watch directories recursively, but gopls’s glob pattern requests recursive matching.
   - https://github.com/joaotavora/eglot/issues/1411
- [ ] update go-mode.el with various nice short `go-*` helper commands for features otherwise accessible though more cumbersome eglot commands (e.g. go-doc, go-test, go-freesymbols, etc); see https://github.com/dominikh/go-mode.el/issues/436
  - mailed https://github.com/dominikh/go-mode.el/pull/439
- [ ] https://github.com/joaotavora/eglot/discussions/1220#discussioncomment-9321061
  - Awaiting approval to merge the new code.
- [x] Fix bug in `(global-set-key (kbd "s-<mouse-1>") #'xref-find-definitions-at-mouse)`.
  - Already fixed in Emacs 30; see https://lists.gnu.org/archive/html/bug-gnu-emacs/2024-06/msg00550.html
- [ ] Ensure the gopls emacs documentation is accurate, and add useful gopls-specific tips and tricks.
- [ ] use LSP for organize-imports + formatting, not goimports command
  - [ ] https://github.com/joaotavora/eglot/discussions/1409
Repository: pytorch
Issue: TORCH_CHECK used within torch.compile does not throw legible errors
Labels: triaged,oncall: cpu inductor

### 🐛 Describe the bug

At best, you get a
```
terminate called after throwing an instance of 'c10::Error'
terminate called after throwing an instance of 'c10::Error'
terminate called after throwing an instance of 'c10::Error'
terminate called recursively
[1]    2964411 IOT instruction (core dumped)
```
At worst, you just get the "terminate called recursively" with not mention to `c10::Error`

To repro, you can perform any out of bounds error. I got it with
```python
import torch

@torch.compile
def copy(a):
    b = torch.arange(start=1, end=-a.numel() - 1, step=-1, device=a.device)
    return a[b]
x = torch.rand(1024, 128, device="cpu")
copy(x)
```
when testing https://github.com/pytorch/pytorch/pull/114471 (may not repro in master).


### Versions

https://github.com/pytorch/pytorch/pull/114471
Repository: go
Issue: x/build/internal/workflow: TestWatchdog/success failures
Labels: Builders,NeedsInvestigation

```
#!watchflakes
default <- pkg == "golang.org/x/build/internal/workflow" && test == "TestWatchdog/success"
```

Issue created automatically to collect these failures.

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

    === RUN   TestWatchdog/success
        workflow_test.go:605: task sleepy    : started
        workflow_test.go:624: task sleepy    : LOG: *snore*
        workflow_test.go:607: task sleepy    : error: task did not log for 750ms, assumed hung
        workflow_test.go:596: workflow "8e8dcf11-f323-45a1-9c4e-e128fdc0c0c6": stalled
        workflow_test.go:417: w.Run() = _, context deadline exceeded, wanted no error
    --- FAIL: TestWatchdog/success (10.01s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/go: TestScript/test_fuzz_minimize_interesting failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/test_fuzz_minimize_interesting"
```

Issue created automatically to collect these failures.

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

    === RUN   TestScript/test_fuzz_minimize_interesting
    === PAUSE TestScript/test_fuzz_minimize_interesting
    === CONT  TestScript/test_fuzz_minimize_interesting
        script_test.go:135: 2024-05-20T15:45:49Z
        script_test.go:137: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1377988911/tmpdir2066169843/test_fuzz_minimize_interesting4234493639
    2024/05/20 15:45:50 serving /git/tagtests/info/refs?service=git-upload-pack
    2024/05/20 15:45:50 serving /git/tagtests/git-upload-pack
        script_test.go:159: 
            PATH=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1377988911/tmpdir2066169843/testbin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/cache/tools/bin:/home/swarming/.swarming/w/ir/bbagent_utility_packages:/home/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages:/home/swarming/.swarming/w/ir/cipd_bin_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/home/swarming/.swarming/w/ir/cache/cipd_client:/home/swarming/.swarming/w/ir/cache/cipd_client/bin:/home/swarming/.swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
            HOME=/no-home
    ...
            --- FAIL: FuzzMinimizerCrashInMinimization (0.32s)
                --- FAIL: FuzzMinimizerCrashInMinimization (0.00s)
                    fuzz_test.go:16: bad input
                    fuzz_test.go:18: got the minimum size!
                
                Failing input written to testdata/fuzz/FuzzMinimizerCrashInMinimization/582528ddfad69eb5
                To re-run:
                go test -run=FuzzMinimizerCrashInMinimization/582528ddfad69eb5
            FAIL
            [stderr]
    ...
            > stdout -count=1 'EOF'
            > stdout FAIL
            matched: --- FAIL: FuzzMinimizerNonrecoverableCrashInMinimization (0.44s)
            # Check that the input written to testdata will reproduce the error. (2.951s)
            > go run check_testdata/check_testdata.go FuzzMinimizerNonrecoverableCrashInMinimization 1
            [stderr]
            corpus file contained no values
            exit status 1
        script_test.go:159: FAIL: testdata/script/test_fuzz_minimize_interesting.txt:41: go run check_testdata/check_testdata.go FuzzMinimizerNonrecoverableCrashInMinimization 1: exit status 1
    --- FAIL: TestScript/test_fuzz_minimize_interesting (62.35s)


— [watchflakes](https://go.dev/wiki/Watchflakes)