sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Custom cursor reverts to system cursor in fullscreen on macOS
Labels: bug,platform:macos,topic:porting

### Godot version

4.0.2 stable

### System information

macOS 13.3.1, any renderer, Apple M1 Pro GPU

### Issue description

When a custom cursor is used in a project and the project is run in fullscreen (no matter if it started in fullscreen or started as windowed and was then switched to fullscreen by the user), the cursor will revert to the system cursor when it is within the window. However, it will appear in a very small area right above and below the game area, where there are black bars since the screen doesn't have the same dimensions as the default scene. When the custom cursor image is changed to another resource with code, the cursor will properly appear again, only to disappear again when it is moved beyond the game area. This bug only appears in fullscreen and is not reproducible on Windows.

| Windowed | Fullscreen |
|----------|------------|
|  https://user-images.githubusercontent.com/64259275/231850009-ef643f31-caa4-4e35-8738-e5ae42e30338.mov  | https://user-images.githubusercontent.com/64259275/231850133-7b4ada15-f480-48d0-aceb-05dafd8fa6ab.mov |

### Steps to reproduce

1. On a (Apple silicon?) macOS device, open a new project and create a new scene
2. Set `display/mouse_cursor/custom_image` in the project settings to another image. Alternatively this can also be done via code with `Input.set_custom_mouse_cursor()`.
3. Set `display/window/size/mode` to fullscreen or exclusive fullscreen.
4. Run the current scene
5. Move the mouse from outside the game area into the game area (as displayed in the videos in the issue description)

### Minimal reproduction project

[Minimal reproduction project](https://github.com/godotengine/godot/files/11225278/Custom.Cursor.Bug.zip)
Repository: deno
Issue: test-child-process-execFile-promisified-abortController.js is flaky
Labels: flaky

```
------- output -------
"parallel/test-child-process-execFile-promisified-abortController.js" failed:

error: Uncaught AssertionError: Values are not equal:


    [Diff] Actual / Expected


-   NotFound
+   AbortError


    at new AssertionError (ext:deno_node/assertion_error.ts:411:15)
    at toNode (ext:deno_node/assert.ts:43:23)
    at deepStrictEqual (ext:deno_node/assert.ts:262:5)
    at validateThrownError (ext:deno_node/assert.ts:614:17)
    at rejects_onRejected (ext:deno_node/assert.ts:377:13)


You can repeat only this test with the command:
  
  ./target/debug/deno test -A cli/tests/node_compat/test.ts -- parallel/test-child-process-execFile-promisified-abortController.js

----- output end -----
  Node.js compatibility "parallel/test-child-process-execFile-promisified-abortController.js" ... FAILED (308ms)
```

https://github.com/denoland/deno/actions/runs/4692127173/jobs/8317459787
https://github.com/denoland/deno/actions/runs/4703617350/jobs/8342330353
Repository: go
Issue: cmd/compile: add intra-line discrimination to PGO profiles
Labels: Performance,NeedsDecision,compiler/runtime

Currently the CPU pprof profiles used for PGO can only break down samples to the source line level. PCs are also included and more precise, but without the original binary they aren't very useful.

This places artificial limitations on the accuracy of optimizations. e.g., if there are two calls to the same function on the same line, we cannot distinguish which one is hot and which one is cold.

This is even more problematic for some potential optimizations. e.g., basic block level optimizations need basic block weights, but there may be multiple basic blocks on the same line.

There are two obvious choices for this: column numbers or ["discriminators"](https://dwarfstd.org/issues/090128.1.html). 

Column numbers have the advantage of being intuitive and with a stable meaning, but have the downside that some constructs that we'd like to differentiate may still share a column number. e.g., I believe that bounds check comparison, success, and failure (panic) cases all share the same column number.

Discriminators have the advantage of flexibility. The compiler can assign them arbitrarily to every construct we care about. The main downside is potential instability. If two compiler versions generate different discriminator values, then profiles aren't fully compatible across the upgrade.

The pprof format itself does not support either column numbers or discriminators, so they will need to be added somehow.

cc @cherrymui @aclements @rajbarik @jinlin-bayarea
Repository: rust
Issue: LLVM name mangling workaround \x01 seems broken
Labels: A-linkage,A-LLVM,O-windows,P-low,T-compiler,regression-from-stable-to-stable,C-bug

I think https://github.com/rust-lang/rust/pull/96444 might have broken the [#[export_name = "\x01..."]](https://github.com/rust-lang/rust/issues?q=%5Cx01+mangle) LLVM workaround for avoiding the "@XYZ" name mangling on x86. Compiling the following with `i686-pc-windows-msvc` results in `error LNK2001: unresolved external symbol _☺test1@0`:

```rust
#[export_name = "\x02test2"]
extern "stdcall" fn test2() {}

#[export_name = "\x01test1"]
extern "stdcall" fn test1() {}
```
I stumbled upon this when trying to use the `\x01` workaround to specify the `_aulldiv` symbol, which the MSVC linker expects to be named `__aulldiv` (instead of `__aulldiv@16`) in `#![no_std]` x86 Windows crates.
Repository: go
Issue: cmd/asm: arm64 assembler generates code that is not execute-only compatible
Labels: NeedsInvestigation,FeatureRequest,arch-arm64,compiler/runtime

The Go assembler for arm64 generates code that is not execute-only compatible, since it stores constants in the text section rather than in rodata, which it then reads during execution.

OpenBSD 7.3 has enabled xonly by default on OpenBSD/arm64 - this means that externally linked Go binaries segfault on execution. This can be worked around in the interim by disabling execute-only when the external linker is invoked.

Longer term, the assembler should store constants in rodata and/or load them via instructions, such that the text section can be marked as execute-only.
Repository: go
Issue: cmd/compile: support for LBR profiles in PGO
Labels: Performance,NeedsInvestigation,compiler/runtime

Branch profiles, aka Last Branch Record (LBR) profiles provide a sample-based profile of branches taken. LBR hardware provides a snapshot of the last N taken branches at each sample point. Subsequent records can be combined to provide basic block execution counts as well as branch counts. e.g., one sample could be: basic block executed from `startpc` to `endpc` and then jumped to `dstpc`.

Today we use CPU profiles for PGO because they are easy to collect (no special hardware support required), while LBR profiles require special hardware support (notably, not exposed by most major cloud VM providers). However, LBR profiles can often be better than CPU profiles for PGO. For instance:

* Iterative stability: a PGO optimization that reduces the cost of a call will make that call use less CPU and thus get fewer samples in the next CPU profile. This could lead to the next compile not identifying that code as hot anymore and no longer performing the optimization. On the other hand, an LBR profile will report the same number of calls despite the optimizations.

* While CPU cycles and number of calls/executions are generally correlated, there can be significant skew particularly on basic block level optimizations. Basic blocks tend not to have many instructions, so more expensive instructions in a basic block (e.g., MUL vs ADD) can skew results making the MUL block look hotter even if the ADD block is executed more often.

One blocker to native LBR support in the compiler is that the pprof format has no canonical way of encoding LBR samples. We either need to pick a custom interpretation that we recognize, pprof should add an official form, or we use a different file format entirely (such as LLVM's PGO format).

cc @cherrymui @aclements @rajbarik @jinlin-bayarea @hoeppi-google
Repository: vscode
Issue: notebook search: output matches not disappearing when dismissed 
Labels: bug,search,confirmed

1. `search.experimental.notebooksearch: true`
2. search something that would have outputs in a notebook and open the notebook
3. try to dismiss the result for the output
4. text decoration for search result (orange by default) doesn't disappear.
Repository: go
Issue: cmd/compile: go:linkname causes "internal compiler error: panic: runtime error: invalid memory address or nil pointer dereference"
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.3 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?
Yes, i downloaded the latest release from https://go.dev/doc/install.


### 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="arm64"
GOBIN=""
GOCACHE="/Users/mark/Library/Caches/go-build"
GOENV="/Users/mark/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/mark/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/mark/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.3"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
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 -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/82/wm5sqy_936zclxgk95t9wghr0000gn/T/go-build3292674194=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?
https://go.dev/play/p/P2iv3ERVhbb
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->


### What did you expect to see?
A regular compiler error, not internal panic.


### What did you see instead?
<pre>
# command-line-arguments
./main.go:6:6: internal compiler error: panic: runtime error: invalid memory address or nil pointer dereference

Please file a bug report including a short program that triggers the error.
https://go.dev/issue/new

</pre>
Repository: kubernetes
Issue: Metric: apiserver filter failure count
Labels: area/apiserver,area/monitoring,sig/api-machinery,sig/instrumentation,triage/accepted

We already track filter latency in the apiserver. It would be useful to have a per-filter metric that tracked failures. In other words, if a filter terminates the request propogation and writes an error response, record that as a failure along with the name of the filter. If the request is propogated and fails in a filter farther down the chain, that should not count as a failure in a parent filter (but if the request fails _after_ it a child filter returns, then it should).

/sig api-machinery instrumentation
/area apiserver monitoring
Repository: go
Issue: x/pkgsite: update retract documentation 
Labels: Documentation,NeedsInvestigation,modules,pkgsite

* improve https://pkg.go.dev/about#removing-a-package by adding practical guides like https://play-with-go.dev/retract-module-versions_go119_en/
* Once https://github.com/golang/go/issues/59622 is done, also add this option to https://pkg.go.dev/about#removing-a-package
* fix the broken links in the blog post https://go.dev/blog/go116-module-changes#module-retraction 
* add link to more examples to https://go.dev/ref/mod#go-mod-file-retract (or create a wiki page that has different cases e.g. cases like https://github.com/golang/go/issues/59577)
* update https://github.com/golang/go/blob/master/.github/ISSUE_TEMPLATE/02-pkgsite-removal.md 

cc @golang/tools-team
Repository: pytorch
Issue: Look into test coverage for `UntypedStorage`
Labels: module: typing,module: tests,triaged

In #94503, there was a mypy error when trying to use `_StorageBase.__setitem__`. Since we don't currently have this mypy error in the main branch, this suggests that `UntypedStorage.__setitem__` is not getting tested anywhere, and a test should be added for it. There might be other tests that `UntypedStorage` is lacking as well

cc @ezyang @malfet @rgommers @xuzhao9 @gramster @mruberry
Repository: vscode
Issue: Support a local dev experience for extensions browsing
Labels: feature-request,marketplace

I feel like the VSCode shell could also enable this feature without marketplace. The pattern I'd love to see is simple and mirrors the concept of local NuGet galleries in the .NET ecosystem.

Scenario:

- Enable VSCode marketplace (via setting) to add other 'endpoints' -- this could be as simple as a folder, as advanced as owning an API, etc -- although I don't think that fully is needed.
- VSCode would look at that directory and expect it to just be a directory of well-structured VSIX packages and enumerate those in the marketplace view in VSCode
- The marketplace view would show a grouping of these items using the path name as the title (could get long so some concatenation)
This would be a lighter 'private marketplace' and would allow a good/rapid local dev experience for these workflows
Repository: PowerToys
Issue: Please bring back the case conversion mode - As in sentences
Labels: Needs-Triage

### Description of the new feature / enhancement

Please bring back the case conversion mode - As in sentences

### Scenario when this would be used?

Examples:

Before:
PLEASE BRING BACK THE CASE CONVERSION MODE - AS IN SENTENCES

After:
Please bring back the case conversion mode - as in sentences

Before:
please bring back the case conversion mode - as in sentences

After:
Please bring back the case conversion mode - as in sentences

Before:
Please Bring Back The Case Conversion Mode - As In Sentences

After:
Please bring back the case conversion mode - as in sentences

### Supporting information

_No response_
Repository: next.js
Issue: Typescript 5 decorators do not build
Labels: bug,SWC,linear: next

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:46 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6020
    Binaries:
      Node: 19.7.0
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


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

SWC transpilation

### Link to the code that reproduces this issue

https://github.com/austinlogo/nextjs-typescript-5

### To Reproduce

Install and build as normal you should see an error in building types. 

When you use the experimental flags in the tsconfig.json

### Describe the Bug

This build Error

```
./src/pages/api/hello.ts
Error:
  × Unexpected token `@`. Expected identifier, string literal, numeric literal or [ for the computed key
    ╭─[/Users/logo/workspaces/scratch/ts5/test-types/src/pages/api/hello.ts:23:1]
 23 │ }
 24 │
 25 │ class Test {
 26 │   @loggedMethod
    ·   ─
 27 │   myMethod() {
 28 │     return "hello";
 29 │   }
    ╰────
```

### Expected Behavior

I would expect it to build.

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

_No response_

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

_No response_

<sub>[NEXT-1559](https://linear.app/vercel/issue/NEXT-1559/typescript-5-decorators-do-not-build)</sub>
Repository: flutter
Issue: `toImage` that does not block the GPU/rasterizer thread, but runs on a separate CPU thread?
Labels: engine,a: images,c: proposal,P3,team-engine,triaged-engine


## Use case

(I am willing to PR!)

Hi thanks for the wonderful Flutter framework! I am proposing to have something like `await layer.toImage(nonBlockingRasterizerThread: true)`.

Firstly, IMHO this feature has general purposes: When people are calling `toImage`, they may not want it to block the main rasterizer. For example, it looks great to take a "screenshot" (by toImage) and at the same time make animations still smooth. However, using the current toImage, I observe it blocks the GPU thread (rasterizer thread). Thus, if toImage takes 200ms, then the UI will jank for 200ms.

My (simplified) use case is as follows: Imagine the page as nothing but a painter app (but with complex rendering). Since I want the rendering to be smooth even when there is 1000 strokes (i.e. `Canvas.drawPath`), I used `toImage` and incremental rendering. More specifically, as suggested in https://github.com/flutter/flutter/issues/122566 by @dnfield, @jason-simmons and @jonahwilliams (thank you!), I call `toImage` periodically and asynchronously to "snapshot" the current scenario, and draw only the few strokes that has not been snapshoted. Code looks like:

```dart
void paint() {
  canvas.drawImage(snapshot);
  for(var stroke in strokesThatHasNotBeenSnapshoted) canvas.drawPath(stroke);
  if (timeHasElapsedForAFewSeconds) layer.toImage().then((x) => snapshot = x);
}
```

Now the problem is: `toImage` takes too long time that blocks the rasterizer thread. As mentioned above, it seems that toImage will block the rasterizer thread.

## Proposal

As mentioned above, it would be great to have a flag that makes toImage not block the GPU/rasterizer thread, but runs on a separate CPU thread.

It may make it slower, but as long as not *that* slow IMHO it is acceptable. toImage is already async and never guarantee it is finished at the current frame.

P.S. Sample timeline if you are interested:

![image](https://user-images.githubusercontent.com/5236035/231906269-5ff9104b-914a-4fba-9c52-7848aaa2a2c5.png)
Repository: deno
Issue: Warn before trying to run `deno fmt` inside the root of a filesystem.
Labels: suggestion,deno fmt

Maybe I'm just incredibly stupid, but this has been the second time (last time was a few months ago) that I tried to run `deno fmt`, thinking I was inside the directory of a repository, only to find out my cwd was actually `/`.
When this happens it doesn't tell you about it, it just keeps hanging for a long time. A time during which I'm mostly just scratching my head over what's causing it to take so long.

It seems like this shouldn't be possible? Or at least should give a warning. I have now changed a whole bunch of files, and I have no idea which ones. Sounds like this could wreak all kinds of havoc.

One solution could be to check the cwd, and warn if it is `/`.

What would also solve this I think, is that the status message saying 'checked n files' when `deno fmt` is done, is updated in real time. That would immediately make it clear that deno is still running and not just hanging.
Repository: godot
Issue: Cant Scroll Long Pop Up Lists
Labels: bug,confirmed,topic:gui

### Godot version

4.02 Stable

### System information

Windows 11, Vulkan Forward +, RTX2080S, Nvidia Game Ready 531.41

### Issue description

When Object selection menu from the inspector opens scrolling using the mouse wheel or the scroll bar is not possible. This may happen with other pop up lists as well.

### Steps to reproduce

1. Create a new Godot project
2. Create a new 3D scene
3. Create a new script and attach it to the root node
4. In the script add 

``` gdscript
@export
var test_array: Array = []
```

5. In the inspector create a new array element and select Object as the type by clicking the pencil button
6. Open the Object selection menu by pressing where it says empty
7. Try to scroll in the pop up

Result: Scrolling using the mouse wheel or the scroll bar is not possible
Expected Result: Scrolling using the mouse wheel or the scroll bar is possible

### Minimal reproduction project

[ScrollIssue.zip](https://github.com/godotengine/godot/files/11227574/ScrollIssue.zip)
Repository: godot
Issue: Fix Silhouette's Filter Array type hint does not work
Labels: enhancement,topic:editor,topic:animation

### Godot version

4.02 Stable

### System information

Windows 11, Vulkan Forward +, RTX2080S, Nvidia Game Ready 531.41

### Issue description

I noticed when on the retargeting menu's Fix Silhouette filters array does not have a working type hint. I am not sure if this affects more than the Fix Silhouette filter array in the inspector.

In the CPP file "post_import_plugin_skeleton_rest_fixer.cpp" I noticed it looks like a type hint is supplied on line 48 but it doesn't seem to do anything.

``` c++
r_options->push_back(ResourceImporter::ImportOption(PropertyInfo(Variant::ARRAY, "retarget/rest_fixer/fix_silhouette/filter", PROPERTY_HINT_ARRAY_TYPE, "StringName"), Array()));
```

Not the right place for this but,

it would be nice to have an invert filter button, Right now it seems to filter the bones you add in the array but it would also be nice to be able to invert the option so it only applies the result onto the bones listed in the array.

### Steps to reproduce

1. Import a model with a skeleton
2. Double click the imported file to open the advanced import window
3. Select the skeleton and in the inspector add a new bone map
4. Find the Fix Silhouette option
5. Open the filters array and click add element

Result: An null item is added and you can select from different types
Expected Result: An item of the correct type is automatically added and you cannot select a different type. In this case it seems the type should be StringName 

### Minimal reproduction project

[ArrayTypeHintIssue.zip](https://github.com/godotengine/godot/files/11227668/ArrayTypeHintIssue.zip)
Repository: PowerToys
Issue: 建议修改左侧边栏显示方式
Labels: Needs-Triage

### Description of the new feature / enhancement

随着功能增加，左侧边栏已经难以承担快速检索的任务，建议增加分组/收藏/过滤功能，缩短查找功能的时间

### Scenario when this would be used?

当希望快速在PowerToys中查找所需或常用功能时

### Supporting information

_No response_
Repository: material-ui
Issue: TextField Validation Style
Labels: discussion,component: text field

### Summary 💡

Please consider changing the error property to inValid and adding isValid, like bootstrap does:
https://getbootstrap.com/docs/5.3/forms/validation/#server-side

### Examples 🌈

_No response_

### Motivation 🔦

_No response_
Repository: PowerToys
Issue: PowerRename Right Menu
Labels: Needs-Triage

### Description of the new feature / enhancement

PowerRename(W) Conflict with New(W)
Could we change the default value?

### Scenario when this would be used?

PowerRename

### Supporting information

_No response_
Repository: transformers
Issue: TypeError: export() got an unexpected keyword argument 'preprocessor'
Labels: New model

### Model description

onnx_inputs, onnx_outputs = export(
            preprocessor=tokenizer, model=model, config=onnx_config, opset=10, output=onnx_model_path
        )

i got error: TypeError: export() got an unexpected keyword argument 'preprocessor'

### Open source status

- [ ] The model implementation is available
- [ ] The model weights are available

### Provide useful links for the implementation

_No response_