sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: PinJoint2D Motor has weird units
Labels: discussion,topic:editor,documentation,topic:physics,needs testing,topic:2d

### Tested versions

4.2.1

### System information

Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org OpenGL API 4.6 (Core Profile) Mesa 23.2.1-1 - Compatibility - Using Device: AMD - AMD Radeon RX 5600 XT (navi10, LLVM 16.0.6, DRM 3.49, 6.1.0-5-amd64)

### Issue description

PinJoint2D's `motor_target_velocity` has units of either radians per second (if you believe the documentation) or degrees per second (if you believe the inspector).

Given these units, I would expect a constant rotation at that speed.  Instead, a force seems to be applied.  That force seems to be proportional to the supplied `motor_target_velocity`.  But it is not proportional to the mass of the attached PhysicsBody2D objects -- nor does it seem to consider the distance of their CG from the joint.  (I see in the code something about the inverse inertia, but I don't understand how that could possibly be correct -- surely if you wanted a constant speed, you would want to have a force proportional to the non-inverse inertia).

So at minimum, the bug is that the units are not correct (that is, they are not off by a constant factor; they are the entirely wrong sort of unit). 

Of course, if I want truly constant motion, I could use a KinematicBody2D and do the rotation myself.  But that wouldn't help if I want the motorized item to push other PhysicsBody2D objects (I think?).   

What I think I really want is a motor which applies a certain maximum amount of force, and aims for a certain maximum speed.  Of course, I could (and probably will) do this myself by hooking up a PID controller to this value -- but that would still leave the documentation/description of this feature wrong.

### Steps to reproduce

The attached file (based on one by @Ughuuu, author of this motor stuff) shows four motors:  the top-left is set to 4,000 deg/s (which would be over 600 RPM); it's actually just barely making it over the top until it gets up some momentum.  The top-right is set to 3,000 deg/s but doesn't have enough power to push the ball over the top, so it's actually not rotating at all at a steady state.  The bottom left is too heavy -- it's the same as top-left but the ball weighs 2kg instead of 1.  Bottom right is just like bottom left except the ball is closer to the center, so it can make it over the top.  

### Minimal reproduction project (MRP)

[PinJointMotorWrong.zip](https://github.com/godotengine/godot/files/14028186/PinJointMotorWrong.zip)
Repository: vscode
Issue: Git - Apply Stash a second time brings up warning with empty file list
Labels: bug,git

Testing #203040

* Git: View Stash
* Pick a Stash
* Apply the Stash, note that diffs are present in the SCC view
* Git: View Stash again
* Pick another Stash that would modify files that already have changes (e.g., those applied from first stash)
* Apply the Stash

Result: Warning message that the "...following files would be overwritten by merge:" but there is no list of files

![image](https://github.com/microsoft/vscode/assets/1487073/67bf65eb-8541-4e54-93d6-2ec9a7fa770e)

The Command Output shows the file(s) that would be overwritten, so either the dialog should show the files or the text could be modified to something like "Click Command Output to view the files that would be overwritten" or something like that :). 

![image](https://github.com/microsoft/vscode/assets/1487073/6fdbe1f5-e12f-41fd-a151-71fb1540c51a)
Repository: pytorch
Issue: [Tracker] Nested tensor op coverage requests
Labels: triaged,enhancement,module: nestedtensor

This issue tracks op coverage requests for nested tensors. If you'd like a specific op to be implemented for nested tensors, please add a comment here so we can prioritize effectively.

Prior requests:
* Conv2d: https://github.com/pytorch/pytorch/issues/114090
* KV-cache related ops: https://github.com/pytorch/pytorch/issues/115978
    * Includes ops that mutate in-place
* Slicing of NTs across constant dimension: https://github.com/pytorch/pytorch/issues/108567
* EmbeddingBag: https://github.com/pytorch/pytorch/issues/93843
* Loss functions
    * Cross-entropy, log_softmax, NLL loss): https://github.com/pytorch/pytorch/issues/99142
    * Binary cross-entropy: https://github.com/pytorch/pytorch/issues/89125
* `eq`, `to`, `masked_select`, `index_select`, `narrow`: https://github.com/pytorch/pytorch/issues/88137 
* LayerNorm on non-contiguous (transposed) NJT: https://github.com/pytorch/pytorch/issues/130538

cc @cpuhrsch @bhosmer @drisspg @soulitzer
Repository: PowerToys
Issue: Add Crop & Lock to PowerToys Quick Launch Menu
Labels: Help Wanted,Product-Settings,Area-Flyout,Product-CropAndLock

### Description of the new feature / enhancement

Simple request, I would like for Crop & Lock to be available on the PowerToys quick menu so it can be invoked by mouse instead of only keyboard shortcut (many other similar tools like text extractor are already here)

<img width="379" alt="image" src="https://github.com/microsoft/PowerToys/assets/4219926/fdf45023-90af-4213-a030-b995692172f7">


### Scenario when this would be used?

Sometimes I'm in a situation where mouse would be more convenient, in particular when I'm using touch or when remote machines and keyboard shortcuts may or may not be forwarded.

### Supporting information

It'd be nice if every feature you can launch
Repository: vscode
Issue: Extension viewlet should indicate when there are newer extension versions available if you update your VS Code
Labels: feature-request,extensions

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

It's a common case that user's use VS Code in an environment which they do not control updates or where they don't realize their VS Code is not completely up to date.

This is especially difficult to notice with extensions which you could be many versions behind on due to VS Code engine incompatibilities and not notice that you're missing out on key extension features which you would receive by updating your VS Code. My proposal is to add some indication when you click on an extension in the extension view that there are newer versions on the marketplace that can be accessed by updating VS Code.
Repository: flutter
Issue: Deprecate DDC's AMD module system in Flutter Web
Labels: P2,team-tool,triaged-tool

DDC currently supports three different formats for handling modules: DDC, AMD, and ES6. Flutter Web externally uses the AMD module system, but all of google3 and Flutter Web internally use the DDC module system (due to its greater configurability).

Consolidating module systems will give us more granular control over how libraries are loaded/updated, allowing us to better support features like hot restart, hot reload, and multi-app configurations. We don't expect any major user-visible changes from this.

This will be a multi-step process that will involve:
* Adding DDC module system support to Dart Web tooling (such as DWDS)
* Plumbing DDC module system support through flutter_tools and the engine and locking it behind a flag
* Extending core functionality (hot restart, test runners, etc.) to support the DDC module system to reach feature parity with AMD.
* Enabling the new module system and watching for unexpected changes.
* Cleaning up AMD module system code artifacts

See related issue in the Dart SDK: https://github.com/dart-lang/sdk/issues/52361
Repository: pytorch
Issue: DISABLED test_inductor_all_to_all_single (__main__.C10DFunctionalNativeTest)
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%22distributed%2Ftest_c10d_functional_native.py%3A%3AC10DFunctionalNativeTest%3A%3Atest_inductor_all_to_all_single%22%5D)).

This distributed tests is failing on ROCm, i.e. https://hud.pytorch.org/pytorch/pytorch/commit/905a7cc340bf7aaa44ba64142cfd0f68b7b403c5

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: storybook
Issue: [Bug]: RouterModule.forRoot() is imported twice when loading a story
Labels: bug,help wanted,angular

### Describe the bug

When importing the RouterModule and using the `forRoot()` pattern for routing storybook seems to import this twice causing `NG04007: The Router was provided more than once`.

You can see this in the screenshot below:
![image](https://github.com/storybookjs/storybook/assets/108286406/883e6ed6-d25e-4489-9f25-654ad98444da)


I see this error in:
storybook 7.4.3 Angular 15
storybook 7.5 Angular 16.
I even upgraded to 7.6.10 with Angular 15 and still had the same issue.

I do not have this error in storybook 7.4.3 Angular 14.

### To Reproduce

Stackblitz: https://stackblitz.com/edit/github-vrpkro-pu8ckn?file=src%2Fstories%2FPage.stories.ts

Code change on line 22 in Page.Stories.ts
Reproduction:
1. Load project
2. Navigate to page example
3. The error will appear in place of story

You can navigate to the other examples and see that without the RouterModule.forRoot() imported you will not have the same issue.

### System

```bash
Local project: 7.4.3
StackBlitz: 7.5.0-alpha
chrome: Version 120.0.6099.234
```


### Additional context

I found a similar issue that has been resolved here: https://github.com/storybookjs/storybook/issues/21284
Repository: vscode
Issue: Allow Extensions to contribute to DebugHoverContext/DebugWatchContext
Labels: feature-request,debug

#125763 is nice, but unfortunately doesn't enable extensions to contribute commands. Would be nice if extensions could do that.
Repository: pytorch
Issue: Rprop does not work in MPS for noncontiguous tensors
Labels: module: optimizer,triaged,module: mps

### 🐛 Describe the bug

RProp does not update noncontiguous params. I haven't dug into the why, but our simplest directional test case on test_forloop_goes_right_direction fails:

```
======================================================================
FAIL: test_forloop_goes_right_direction_contiguous_False_Rprop_mps_float32 (__main__.TestOptimRenewedMPS)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/janeyx/pytorch/torch/testing/_internal/common_utils.py", line 2689, in wrapper
    method(*args, **kwargs)
  File "/Users/janeyx/pytorch/torch/testing/_internal/common_device_type.py", line 416, in instantiated_test
    result = test(self, **param_kwargs)
  File "/Users/janeyx/pytorch/torch/testing/_internal/common_utils.py", line 1366, in wrapper
    fn(*args, **kwargs)
  File "/Users/janeyx/pytorch/torch/testing/_internal/common_optimizers.py", line 181, in test_wrapper
    return test(*args, **kwargs)
  File "/Users/janeyx/pytorch/test/test_optim.py", line 94, in test_forloop_goes_right_direction
    self.assertLess(closure().item(), initial_value)
AssertionError: 135.77398681640625 not less than 135.77398681640625

To execute this test, run the following from the base repo dir:
     python test/test_optim.py -k test_forloop_goes_right_direction_contiguous_False_Rprop_mps_float32

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

### Versions

on main

cc @vincentqb @jbschlosser @albanD @crcrpar @kulinseth @malfet @DenisVieriu97 @razarmehr
Repository: PowerToys
Issue: Image Resizer: window size doesn't render as set
Labels: Issue-Bug,Product-Image Resizer

### Microsoft PowerToys version

Dev build

### Installation method

Dev build in Visual Studio

### Area(s) with issue?

Image Resizer

### Steps to reproduce

https://github.com/microsoft/PowerToys/blob/172db3af639d09a4872809de03cc441de535608c/src/modules/imageresizer/ui/Views/MainWindow.xaml#L11-L12

### ✔️ Expected Behavior

A window with these dimensions.
I'm guessing this is a [WPF-UI](https://github.com/lepoco/wpfui) problem?

### ❌ Actual Behavior

ActualWidth: **460**
ActualHeight: **600** while Debugging, **505** for installed version
![image](https://github.com/microsoft/PowerToys/assets/65828559/90d82cdd-e71c-4373-a4c1-0f0e38df03aa)
Repository: storybook
Issue: [Documentation]: Essentials Actions references @storybook/action-addons both in the current documentation and in the advanced/legacy documentation
Labels: question / support,addon: actions,documentation

### Describe the problem

Essentials Actions documentation references @storybook/action-addons both in the [current documentation](https://storybook.js.org/docs/essentials/actions#action) and in the [advanced/legacy documentation](https://github.com/storybookjs/storybook/blob/master/addons/actions/ADVANCED.md#manually-specified-actions).

Should we stop using the action function exported from @storybook/action-addons? And, will the action function from @storybook/action-addons be deprecated in v8 of storybook like the advanced/legacy documentation seems to suggest?



### Additional context

_No response_
Repository: angular
Issue: Formcontrol essential features
Labels: area: forms,forms: Controls API

### Which @angular/* package(s) are relevant/related to the feature request?

@angular/forms

### Description

1. Formcontrol should know whether it is focused, submitted.
2. We should be able to add multiple updateOn values not just one.
3. We should be able to set if we want to propagate valueChanges and/or statusChanges


### Proposed solution

1. add focused:boolean property to Formcontrol class, and focus$ submit$ streams we can subscribe to
2. rewrite updateOn so it accepts arrays like: ['blur','submit'], and also extend it with 'focus', 'click', 'dblclick' etc.
3. extend Formcontrol so we can add { propagateValueChanges : false , propagateStatusChanges: true } at declaration


### Alternatives considered

wouldn't have written the issue if had found any
Repository: transformers
Issue: GPT2 cannot be used with device_map='auto'; Report "found at least two devices"
Labels: Good Difficult Issue,Accelerate

### System Info

- `transformers` version: 4.36.2
- Platform: Linux-5.15.0-89-generic-x86_64-with-glibc2.35
- Python version: 3.9.18
- Huggingface_hub version: 0.20.2
- Safetensors version: 0.4.1
- Accelerate version: 0.26.1
- Accelerate config: 	not found
- PyTorch version (GPU?): 2.1.2+cu118 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed


### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [X] My own task or dataset (give details below)

### Reproduction

A simple reproducer here:
```python
from transformers import GPT2LMHeadModel
# create a sample input:
batch_ids = {
    'input_ids': torch.tensor([[312, 134, 56, 712, 351, 89, 63, 550, 971, 2]]),
    'attention_mask': torch.tensor([[1, 1, 1, 1, 1, 1, 1, 1, 1, 1]]),
}

gpt2_large = GPT2LMHeadModel.from_pretrained('gpt2-large', cache_dir='./cache_dir', device_map='auto')
gpt2 = GPT2LMHeadModel.from_pretrained('gpt2', cache_dir='./cache_dir', device_map='auto')

loss_gpt2_large = gpt2_large(**batch_ids, labels=batch_ids['input_ids']).loss
loss_gpt2 = gpt2(**batch_ids, labels=batch_ids['input_ids']).loss
``` 

### Expected behavior

It works well to generate `loss_gpt2_large`, but it will report error when generating `loss_gpt2`: 
`RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:7 and cpu! (when checking argument for argument index in method wrapper_CUDA__index_select)`

I am not sure why this behaves differently with the same model class. Could you please provide any comments on this? Thanks in advance!
Repository: tauri
Issue: [bug] keychain prompt on MacOS
Labels: type: bug,status: needs triage

### Describe the bug

I develop tauri app on `MacOS` and every time the app restart in `dev mode` it opens a dialog and asking for password:
![image](https://github.com/tauri-apps/tauri/assets/61390950/98e4aad5-fdf7-44e4-92fe-d9743026eecb)

Important info:
1. It happens on dev mode only, not in production build which I install and open.
2. I authenticate with [twitter.com](https://twitter.com) which uses `indexedDB` / secure storage
3. It happens from the second run in dev mode (after the first restart). in the first time it doesn't happen
4. I can reproduce it in 2 different MacOS computers.
5. It doesn't happen in regular `tauri` app, so most probably it's from the use of `twitter.com`
6. It's very hard to develop with it as I need to enter my password every reload.



### Reproduction

Create tauri app, navigate to twitter and log in. restart the app and navigate to twitter again.

### Expected behavior

After the first time you click "Save always" it shouldn't prompt again in dev mode.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.19.0
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: git+https://github.com/Glitch752/tauri/?branch=feat/multiwebview#e51ea29913f995f03d1f7d3332013c4d1321cb7b (2.0.0-alpha.20)
    - tauri-build [RUST]: no manifest (2.0.0-alpha.13, 2.0.0-alpha.13, 2.0.0-alpha.13)
    - wry [RUST]: 0.35.1
    - tao [RUST]: 0.24.0
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src
    - devPath: ../src
```


### Stack trace

_No response_

### Additional context

I tried to change settings in keychain app, and allow everything, it didn't helped.
I tried also to delete the keys in keychain and restart the app and it didn't helped.

An option to disable secure storage in webkit can help. but I can't find such option
Repository: go
Issue: x/build: add LUCI linux-arm builder
Labels: OS-Linux,Builders,new-builder,arch-arm

Planned hostname prefix is `linux-arm-aws`, with the individual builders having a `--nn` suffix.

Edit: This builder will also serve as a security trybot. A separate set of instances will be used for that, using `linux-arm-aws-security` as their hostname prefix.
Repository: flutter
Issue: Use different CAS archives for second-layer engine caches across different pools
Labels: team-infra,P3,triaged-infra

On top of LUCI named cache `[cache]/builder`, we have a second layer of caches used to boost source checkout when crash happens with the named cache.

The second layer of cache is maintained by CAS: after targets finish building, we upload the `builder` to CAS and use a metadata to store the CAS archive hashes:
https://flutter.googlesource.com/recipes/+/refs/heads/main/recipe_modules/cache/api.py#77

Now different pools are sharing the same hash, which could potentially cause issues like https://github.com/flutter/flutter/issues/141688

We should distinguish them based on pools.
Repository: flutter
Issue: Collect non-benchmark tests which use a physical device
Labels: team-infra,P2,triaged-infra

Most non-benchmark tests should be able to run without a physical device, and an emulator should be used instead to save limited DeviceLab resources and potentially improve the test execution time.

This bug tracks to collect the list.

/cc @matanlurey @jonahwilliams @jmagman
Repository: vscode
Issue: Running an extension via debugging does not include it in the Issue Reporter Dropdown
Labels: bug,issue-reporter

Testing #203094

* Debug an extension
* Report Issue
* dropdown for extension

My "test-issue-reporter" extension is not there:
![image](https://github.com/microsoft/vscode/assets/2644648/9d290d83-09cc-4165-b0ee-fa73ccd95fd4)

This is probably not super important but would be easier to test my extension's issue reporting.
Repository: flutter
Issue: [web] Use `EngineScene` logic in CanvasKit renderer.
Labels: engine,platform-web,e: web_canvaskit,P2,c: tech-debt,team-web,triaged-web

### Use case

There is significant code duplication in `EngineScene` rendering and CanvasKit rendering. For example the Layer system in the EngineScene scheme: https://github.com/flutter/engine/blob/f720a03ede2c9821006fb1f21fb2917eb757b9d5/lib/web_ui/lib/src/engine/layers.dart and the CanvasKit renderer: https://github.com/flutter/engine/blob/1d2fd46d01da499578ffd180da04ad60f299bfc8/lib/web_ui/lib/src/engine/canvaskit/layer.dart

I also plan to duplicate the logic to only render one frame at a time and drop frames when multiple are queued before the current frame is done rendering from `EngineSceneView`: https://github.com/flutter/engine/blob/3837195399c4c002e874dae34f4305b4f3eb7d09/lib/web_ui/lib/src/engine/scene_view.dart

### Proposal

`EngineScene` is written to be renderer-agnostic, so we should attempt to port CanvasKit rendering to use this Layer logic instead. This will reduce code duplication and our maintenance burden.
Repository: PowerToys
Issue: Fancy Zones - Burp suite pro or community is not fitting in any Zone of Fancy Zone Layouts
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.70.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Install Burp suite pro of community edition 
Enabled fancy zones then move burp suite to any Fancy Zone layout

### ✔️ Expected Behavior

like every window burp suite windows should be fitted in zones layout

### ❌ Actual Behavior

not working 

### Other Software

_No response_
Repository: vscode
Issue: Provide API for skipped ranges in test coverage
Labels: feature-request,testing,test-coverage

              We currently use gcovr for our C projects. The JSON output (as well as the HTML output) both support also skipped/excluded lines (see [https://gcovr.com/en/stable/output/json.html](https://gcovr.com/en/stable/output/json.html)).

With the Test Coverage API coming up, I can also think of creating extensions which can provide the results for static code analysis - so in terms of ESLint for example you could report per line whether there are faults, everything is fine or whether a line has been ignored. The same could also apply for ts-ignore ...
Also the [SARIF standard](https://sarifweb.azurewebsites.net) can give some more insights: Chapter 3.27.23 describes the mechanism for excluding several rules. I found the definition [here](https://github.com/oasis-tcs/sarif-spec/blob/123e95847b13fbdd4cbe2120fa5e33355d4a042b/Schemata/sarif-schema-2.1.0.json#L2183). An example for a suppression can be seen [here](https://github.com/microsoft/sarif-tutorials/blob/819b0f62f47ecde9a8f24dfc387c41926f5edabe/samples/Suppressions.sarif).

_Originally posted by @bigbug in https://github.com/microsoft/vscode/issues/123713#issuecomment-1902726181_
Repository: pytorch
Issue: Better test disabling system
Labels: triaged,needs design,module: devx

## Motivation

We just added a lot of failing tests (10000+) to CI. I put in a lot of work to actually skip the failing tests, so that CI is actually green. We anticipate doing this more (adding a lot of failing tests to CI) in the future:
- Adding Dynamo testing for python 3.12, which will likely add even more failing tests
- CUDA Dynamo testing (we test CPU-only right now) which will add more failing tests

It would be nice if we had a way to mass-disable tests per configuration (e.g. dynamo 3.11 vs dynamo 3.8), perhaps with a single issue instead of one issue per test?

cc @ZainRizvi @kit1980 @huydhn @clee2000 @pytorch/pytorch-dev-infra