sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: go/doc: NewFromFiles panics on ast.Files that lack ast.Objects due to parser.SkipObjectResolution
Labels: NeedsInvestigation

[`doc.NewFromFiles`](https://pkg.go.dev/go/doc#NewFromFiles) calls `ast.NewPackage` on the specified files. `NewPackage` uses the `Scope` field of `ast.File`. However this field is unset if the syntactic identifier resolution (which was deprecated in https://github.com/golang/go/issues/52463) is disabled, causing it to panic.

It should either not panic (e.g. by skipping the logic if Scope is nil, which I think causes it to work fine for NewFromFiles), or the precondition should be documented.
Repository: PowerToys
Issue: Screen ruler / Request for Lines to stay and update
Labels: Idea-Enhancement,Needs-Triage,Product-Screen Ruler

### Description of the new feature / enhancement for Screen Ruler

i wish if there was a way fore the lines to stay and update if possible .

### Scenario when this would be used?

it would be very useful for any type of designing , especially web design like me where everything should be aligned . ( there are browser extension like this but they are either outdated or too buggy and abandoned )

### Example 

Grid Ruler extension
Page ruler extension
Repository: ollama
Issue: Windows Rocm: HSA_OVERRIDE_GFX_VERSION doesn´t work
Labels: bug,windows,amd

I'm eager to explore the new Windows ROCm compatibility feature, but I'm encountering an issue with forcing the GFX version. Currently, I'm using the 0.1.29 pre-release.

My setup includes an RX 6600 XT (GFX1032), which isn't fully supported in the ROCm library. According to the troubleshooting guide available at https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md, it's recommended to override the version to a similar one (in my case HSA_OVERRIDE_GFX_VERSION="10.3.0"). Despite setting the environment variable, the logs continue to display the following error:

```
rocBLAS error: Cannot read C:\Users\user\AppData\Local\Programs\Ollama\rocm\/rocblas/library/TensileLibrary.dat: No such file or directory for GPU arch : gfx1032.
```

However, based on the overridden version, shouldn't it be looking at gfx1030 instead?
The result is ollama crashing after that.
Repository: godot
Issue: after i use plus button create a scene, and then click other window , godot will show a  Progress bar to save and then i can`t click anything
Labels: bug,topic:editor,needs testing

### Tested versions

4.2.1.stable

### System information

win10 -4.2.1.stable - compatible - fullscreen -OpenGL API 3.3.0 NVIDIA 545.92 - Compatibility - Using Device: NVIDIA - NVIDIA GeForce RTX 4060 Laptop GPU

### Issue description

![image](https://github.com/godotengine/godot/assets/94771015/3c61b9a1-cebf-478a-9180-1cd2f29d9fe2)
![image](https://github.com/godotengine/godot/assets/94771015/9e2d6002-7719-4de4-a712-99a969039bee)
in fullscreen, after i create a scene and then i click other whindow there will show  a  Progress bar quickly,  then every thing can`t click

### Steps to reproduce

in fullscreen, after i create a scene and then i click other whindow there will show  a  Progress bar quickly,  then every thing can`t click

### Minimal reproduction project (MRP)

[example.zip](https://github.com/godotengine/godot/files/14589483/example.zip)
Repository: ollama
Issue: Usability improvement for ollama rm
Labels: feature request

In the current implementation, `ollama rm` removes a model without a prompt for confirmation. Please consider the inclusion of a confirmation prompt, with the customary N/y option to avoid removing models by mistake, with `run` and `rm` being similar.
Repository: tauri
Issue: [macOS] APP crashes when web custom protocol request is aborted before or during response
Labels: type: bug,status: needs triage

### Describe the bug

When initiating a `register_uri_scheme_protocol` request from the web side, if the web aborts the request before or during the response, the macOS APP crashes.


### Reproduction

- Register a `register_asynchronous_uri_scheme_protocol`.
- From the web side, initiate a request using this protocol and abort the request before the response.
- The APP crashes 100% of the time.

### Expected behavior

- Before responding, the `responder` should check if the request has been canceled. If the request has been canceled, do not send the response.
- Or, during the response, catch exceptions to prevent the APP from crashing and quitting abruptly when the request is terminated.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 13.6.3 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 18.17.1
    - pnpm: 8.15.4
    - npm: 9.6.7

[-] Packages
    - tauri [RUST]: 2.0.0-beta.10
    - tauri-build [RUST]: 2.0.0-beta.8
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.5
    - @tauri-apps/cli [NPM]: 2.0.0-beta.9

[-] App
    - build-type: bundle
    - CSP: default-src x-http: x-https: blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline'
    - frontendDist: ../feiyu/dist
    - devUrl: http://localhost:3000/
```


### Stack trace

```text
thread 'tokio-runtime-worker' panicked at /Users/mac/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wry-0.37.0/src/wkwebview/mod.rs:262:28:
Uncaught exception <NSException: 0x10428cf30>
```


### Additional context

Related code: https://github.com/tauri-apps/wry/blob/5789bf759ce94e4dad5ff26a08fe81521658a4e4/src/wkwebview/mod.rs#L272
<img width="1802" alt="图片" src="https://github.com/tauri-apps/tauri/assets/35302658/767b0a0a-3c21-42fa-837f-fc4ed4153f57">
Repository: rust
Issue: Infinite Loop when Evaluating Recursive Type
Labels: A-trait-system,A-associated-items,C-bug,I-hang,T-types,fixed-by-next-solver

<!--
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 the code:

```rs
trait Access {
    type Downcast: Access;
}

trait Mapping<X: Access> {}

trait AllowedMappingLoopback<X: Access> {
    type Chain: AllowedMapping<X::Downcast>;
}
impl<X: Access> AllowedMappingLoopback<X> for X
where
    X: AllowedMapping<X::Downcast>,
{
    type Chain = X;
}

trait AllowedMapping<X: Access>: AllowedMappingLoopback<X, Chain = Self> {}
impl<X: Access, T> AllowedMapping<X> for T where
    T: Mapping<X> + AllowedMappingLoopback<X, Chain = Self>
{
}

fn do_thing_with_allowed<X: Access>(mapping: impl AllowedMapping<X>) {}

struct BasicMapping;

fn test() {
    do_thing_with_allowed(BasicMapping);
}
```

This results in an infinite loop within the compiler, within both the latest nightly (1.78.0 (2024-03-12)) and stable (1.76.0).
(see [playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=0c466e73b115ddcdd21807c6636f58ad))
Repository: PowerToys
Issue: Questionable layout in Keyboard Manager
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Area-Localization,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

WinGet

### Running as admin

None

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When system language is Chinese (Simplified), open Remap Shortcuts window:

![image](https://github.com/microsoft/PowerToys/assets/68100399/0658cdd8-8ae5-4190-a2de-19218b303e22)
![image](https://github.com/microsoft/PowerToys/assets/68100399/5f2411a2-5f54-486c-9e9e-63858611f4b3)


### ✔️ Expected Behavior

Headers of combo boxes should align with the texts in boxes.

When choosing 运行程序 in 操作 combo box,
- All combo box in this section should be left aligned.
- There should have horizontal space between text boxes and buttons.
- There should have vertical space between two lines of combo boxes (I mean the last 3 lines in this section)

### ❌ Actual Behavior

Misalignments

### Other Software

_No response_
Repository: pytorch
Issue: torch._check but trust me
Labels: triaged,module: dynamic shapes

### 🐛 Describe the bug

Version of torch._check which doesn't actually install a runtime assert. Good when you need to make assertions about quantities that come from CUDA tensors and therefore would be expensive to do.

### Versions

main
Repository: ollama
Issue: Integrated Intel GPU support
Labels: feature request,intel

Hello,

Please consider adapting Ollama to use Intel Integrated Graphics Processors (such as the Intel Iris Xe Graphics cores) in the future.
Repository: deno
Issue: The error message like `Unknown export '.' for '@std/fmt@0.219.1'` is unintelligible
Labels: bug,jsr

There was a feedback to deno_std that the error message like `Unknown export '.' for '@std/fmt@0.219.1'` is not quite intelligible. (ref. https://github.com/denoland/deno_std/issues/4480 )

Can we somehow improve this error message to make it easier to understand?
Repository: next.js
Issue: HTML children of MathML render in wrong namespace after routing
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/alexgoff/next-mathml-error

### To Reproduce

1. Start application with `yarn dev`
2. Go to [http://localhost:3000/](http://localhost:3000/)
3. Click "Go to math"
4. See that the equation is missing it's number input
![image](https://github.com/vercel/next.js/assets/11721838/19cc21be-5383-4f3d-af86-238e482f3b9e)
5. Open console and see that the ref attached to the input is reporting a `namespaceURI` of `http://www.w3.org/1998/Math/MathML`
6. Reload the page
7. See that the equation has it's number input
![image](https://github.com/vercel/next.js/assets/11721838/e8f5c729-911e-48b6-bfe1-901284abc1bd)
8. Open console and see that the ref attached to the input is reporting a `namespaceURI` of `http://www.w3.org/1999/xhtml`

### Current vs. Expected behavior

Current: After performing a routing, HTML children of MathML are rendering using the `http://www.w3.org/1998/Math/MathML` namespace. On fresh load, or reload after routing, the children render with the correct namespace

Expected: HTML phrasing elements inside of MathML token elements should always render using the `http://www.w3.org/1999/xhtml` namespace, per HTML5 spec: https://html.spec.whatwg.org/multipage/embedded-content-other.html.



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.6.0: Wed Oct  4 23:54:48 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_ARM64_T8101
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.2.0
  npm: 9.6.6
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.2.0-canary.19 // Latest available version is detected (14.2.0-canary.19).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
```


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

App Router, Routing (next/router, next/navigation, next/link)

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

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

### Additional context

_No response_
Repository: godot
Issue: GPUParticles2D Trails don't align with Animated Velocity.
Labels: discussion,topic:2d,topic:particles

### Tested versions

v4.2.1.stable.official [b09f793f5]
Never worked properly

### System information

N/A

### Issue description

When using 2D particle trails with an animated velocity, such as radial or orbit velocity, they do not align with it, creating a "calligraphy effect". 

![image](https://github.com/godotengine/godot/assets/98223724/f7b43d5e-3b0a-4628-b750-e0a98b9c1732)

This is not an issue with GPUParticles3D Trails, as they need `particle_flag_align_y` to align, and GPUParticles2D don't, which is a different issue on it's own.


### Steps to reproduce

- Add a GPUParticles2D Node, and a process material
- Enable Trails
- Use any animated velocity.

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Skia Gold Client(s) should consider "negative images" a pre-submit (try-job) failure
Labels: dependency: skia,P2,c: tech-debt,team-framework,triaged-framework

Our logic in `Future<void> _tryjobAdd(...)` (read: pre-submit) is as follows:

```dart
final String resultStdout = result.stdout.toString();
if (result.exitCode != 0 &&
    !(resultStdout.contains('Untriaged') || resultStdout.contains('negative image'))) {
  /* throws exception */
```

Compare this with `Future<void> _imgtestAdd(...)` (read: post-submit):

```dart
if (result.exitCode != 0) {
  /* throws exception */
}
```

In other words, that means on pre-submit, errors due to untriaged images or negative images are _not_ exceptions, but they are on post-submit. You can read https://github.com/flutter/flutter/issues/145046 for the context (and a suggestion to change this more broadly), but a smaller and I believe less controversial change is to remove the second half (`resultStdout.contains('negative image')`).

We don't consider negative images to _ever_ be valid in our workflow, but AFAICT there is no reason to treat them specifically - if a user accidentally triages as negative, it will break post-submit. Isn't it better to just break pre-submit? We could even have the error be more specific and link to the Wiki - i.e. "do not mark things as negative".
Repository: ollama
Issue: Api /tags should include type for embedding model or llm
Labels: feature request,api

As the title says, it would be nice to have that information so we can filter out embedd models if we want to allow for model switching on a frontend
Repository: flutter
Issue: [web] Autofill forms aren't updated properly
Labels: a: text input,engine,platform-web,P2,team-web,triaged-web

In the web engine, when we receive a `TextInput.updateConfig` message from the framework, we don't properly update the autofill form and its fields.

Details:
- When the new config is [received](https://github.com/flutter/engine/blob/351470ce31cb4852b826d3ed361369191768f1f8/lib/web_ui/lib/src/engine/text_editing/text_editing.dart#L2145-L2147), we create a [new `EngineAutofillForm`](https://github.com/flutter/engine/blob/351470ce31cb4852b826d3ed361369191768f1f8/lib/web_ui/lib/src/engine/text_editing/text_editing.dart#L978-L981).
- That new `EngineAutofillForm` [creates its own `<form>`](https://github.com/flutter/engine/blob/351470ce31cb4852b826d3ed361369191768f1f8/lib/web_ui/lib/src/engine/text_editing/text_editing.dart#L206) element and all the fields.
- The new `<form>` element isn't appended to the DOM because we only append during initialization (e.g. [here](https://github.com/flutter/engine/blob/351470ce31cb4852b826d3ed361369191768f1f8/lib/web_ui/lib/src/engine/text_editing/text_editing.dart#L1591) and [here](https://github.com/flutter/engine/blob/351470ce31cb4852b826d3ed361369191768f1f8/lib/web_ui/lib/src/engine/text_editing/text_editing.dart#L1749)).
- The previous `<form>` element (that was appended during initialization before the updated config arrived) remains in the DOM with no updates applied to it.

cc @htoor3 @LongCatIsLooong
Repository: PowerToys
Issue: Copy Environment variables + names
Labels: Idea-Enhancement,Cost-Small,Product-Environment Variables

### Description of the new feature / enhancement

I'd like to be able to copy the name or value of an environment variable in an easier way.

The simplest approach I can think of for this would be to add "Copy Name" and "Copy Value" to the `...` menu on each row.

A nicer approach might be to make it part of the context menu for the row, then that same menu pops up - to make it a little more intuitive instead of having to click on the one tiny little button.

It could also be a quick context menu option when you right click the variable name or value to copy the full text, instead of requiring select all then copy.

### Scenario when this would be used?

This scenario is useful for copying over environment variables and/or their names to someone, or filling out WSLENV with the environment variable names.

### Supporting information

This isn't a particularly straight forward task - with multiple menus, or switching from mouse to keyboard and back multiple times:

Currently, you cannot copy the name of the variable without clicking the menu => edit => selecting all (click + ctrl+a | triple clicking | right-click + select all), then copying (ctrl+c | right-click + copy).

If you want to copy the value, then you have to either manually select the full value via mouse click+drag (or the same approaches as mentioned before, except triple clicking doesn't work - due to potential characters that stop that from selecting all (`_`, `.`, `#`, etc.), then copy via ctrl+c or context menu. You could also go through the same edit to copy the value from that popup.
Repository: rust
Issue: Compound assignment operator gives superfluous `warning: variable is assigned to, but never used`
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    let mut foo = 1;
    foo += 1;
}
```


### Current output

```Shell
warning: variable `foo` is assigned to, but never used
 --> src/bin/test.rs:2:13
  |
2 |     let mut foo = 1;
  |             ^^^
  |
  = note: consider using `_foo` instead
  = note: `#[warn(unused_variables)]` on by default

warning: value assigned to `foo` is never read
 --> src/bin/test.rs:3:5
  |
3 |     foo += 1;
  |     ^^^
  |
  = help: maybe it is overwritten before being read?
  = note: `#[warn(unused_assignments)]` on by default
```


### Desired output

```Shell
warning: value assigned to `foo` is never read
 --> src/bin/test.rs:3:5
  |
3 |     foo += 1;
  |     ^^^
  |
  = help: maybe it is overwritten before being read?
  = note: `#[warn(unused_assignments)]` on by default
```


### Rationale and extra context

If you change the 3rd line to `foo = foo + 1`, the first, superfluous warning goes away, and you are left with just the second, correct warning. 

This bug comes up in issue https://github.com/rust-lang/rust/issues/63054, but is different; that one is about whether the last iteration of a loop should trigger the second warning. This bug just confused the issue there.

### Other cases

```Rust
fn main() {
    let mut foo = 1;
    foo = foo + 1;
}
```


### Rust Version

```Shell
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```


### Anything else?

If you change it to `foo.add_assign(1)`, both warnings go away. I found that surprising since I thought `+=` desugared into `add_assign` , so they would have the same output. Is that wrong?
Repository: tauri
Issue: [feat] Support specifying a specific binary in the crate
Labels: type: feature request

### Describe the problem

Right now, one has to name their binary the same as the crate name in order for Tauri's default tooling to work with it

### Describe the solution you'd like

I'd like to set the binary name in `tauri.conf.json` and use that appropriately (`--binary {val}` for Cargo commands and `{name}[.ext]` for the output).

### Alternatives considered

_No response_

### Additional context

Reason I have multiple binaries is because we have multiple deployment/install strategies, one backed by Axum the other by Tauri, each a thin wrapper around the library. It's awkward to have "Project" vs "Project Web" vs "Project API" when we want to treat the first two as equal.
Repository: deno
Issue: `watcher::bench_watch_basic` is flaky
Labels: flaky




https://github.com/denoland/deno/actions/runs/8269072900/job/22624012691?pr=22884#step:39:3155
Repository: tensorflow
Issue: How can I exit the XLAControlFlowContext when inside a jit_compile tf.function? Exit() function take no effect.
Labels: stat:awaiting tensorflower,type:bug,comp:xla,comp:tf.function,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 22.04

### Python version

3.10

### CUDA/cuDNN version

CUDA12.3/cuDNN9.0

### GPU model and memory

GTX4090 24GiB

### Current behavior?

I have a custom op that is a normal OpKernel unable to be compile by XLA cluster. But unfortunately, when the user use this custom op, they have to wrap it into a tf.funtion. So somehow when the use Keras jit_compile or something else, errors happened.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

@tf.function(jit_compile=True)
def test(a):
    b = a + a
    ctx = tf.__internal__.get_enclosing_xla_context()
    ctx.Exit()
    tf.print(b)
    ctx.Enter()
    return b * b

test(tf.constant(1))
```


### Relevant log output

```shell
2024-03-14 02:28:52.720666: W tensorflow/core/framework/op_kernel.cc:1745] OP_REQUIRES failed at xla_ops.cc:296 : INVALID_ARGUMENT: Detected unsupported operations when trying to compile graph __inference_test_9[_XlaMustCompile=true,config_proto=9241198235816212909,executor_type=11160318154034397263] on XLA_GPU_JIT: StringFormat (No registered 'StringFormat' OpKernel for XLA_GPU_JIT devices compatible with node {{node StringFormat}}){{node StringFormat}}
The op is created at: 
File "xla_context_test.py", line 12, in <module>
  test(tf.constant(1))
File "xla_context_test.py", line 8, in test
  tf.print(b)
Traceback (most recent call last):
  File "xla_context_test.py", line 12, in <module>
    test(tf.constant(1))
  File "/usr/local/lib/python3.8/dist-packages/tensorflow/python/util/traceback_utils.py", line 153, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/usr/local/lib/python3.8/dist-packages/tensorflow/python/eager/execute.py", line 54, in quick_execute
    tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
tensorflow.python.framework.errors_impl.InvalidArgumentError: Detected unsupported operations when trying to compile graph __inference_test_9[_XlaMustCompile=true,config_proto=9241198235816212909,executor_type=11160318154034397263] on XLA_GPU_JIT: StringFormat (No registered 'StringFormat' OpKernel for XLA_GPU_JIT devices compatible with node {{node StringFormat}}){{node StringFormat}}
The op is created at: 
File "xla_context_test.py", line 12, in <module>
  test(tf.constant(1))
File "xla_context_test.py", line 8, in test
  tf.print(b) [Op:__inference_test_9]
```
Repository: flutter
Issue: Use singular static const for minimum iOS/macOS version where possible
Labels: platform-ios,tool,P2,c: tech-debt,team-ios,triaged-ios

The minimum iOS/macOS deployment version is hardcoded in a bunch of different places within the tool. It would be nice if we had a single const we can use everywhere.

Would also be nice if we could make it a variable in the templates so we don't have to change each template manually.

Here's some examples of places it's used:

https://github.com/flutter/flutter/pull/140823/files