sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Saving resource does not clear modified state of scene
Labels: bug,topic:editor,usability

### Godot version

3.3.2, 3.x (5d4352fad4), 4.0 (48857194b3)

### System information

macOS 11.4

### Issue description

Modifying a resource in the Inspector gives the current scene a modified state (the asterisk `*` mark on tab).

After saving the resource...

* ... by pressing `CTRL-S`
    * if the scene is an empty scene, the scene will still be marked as modified
    * if the scene is not an empty scene, the modified state will be gone
* ... by clicking the save icon on Inspector panel
    * the scene will still be marked as modified

### Steps to reproduce

Open an empty scene, and modifiy `default_env.tres` in the Inspector.

### Minimal reproduction project

_No response_
Repository: storybook
Issue: click the Demo button then Blocked a frame with origin "http://localhost:9009" from accessing a cross-origin frame.
Labels: bug,needs triage

**Describe the bug**
install: npx -p @storybook/cli sb init
run: start-storybook -p 9009 -s public
click the button then Blocked a frame with origin "http://localhost:9009" from accessing a cross-origin frame.
i didn't do anything more 
*only in chrome*

**System**
chrome version : 92.0.4515.107
![image](https://user-images.githubusercontent.com/60084325/127427138-b3e7b1e8-e247-4faf-84b9-80e8db94e5cc.png)
Repository: scrcpy
Issue: Multilingual keyboard input
Labels: feature request

 - [x] I have checked that a similar [feature request](https://github.com/Genymobile/scrcpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22feature+request%22) does already exist.

**Describe the solution you'd like**
- Just a simple input language switch.
-I type using my mouse and the virtual keyboard on the screen, but I would rather not having to do that.
Repository: react
Issue: React CM Mode (18) stacking app during hydrateRoot
Labels: Type: Discussion,React 18

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 18.0.0-alpha-9f88b5355-20210728

## Steps To Reproduce

See repo https://github.com/maraisr/react-suspense-repro

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

https://github.com/maraisr/react-suspense-repro

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

react hydrateRoot is stacking dom trees

will note here that `Suspense` obviously isnt needed that as nothing is async. I can illustrate here as well if you require a demo with the Suspense needing to do something??

## The expected behavior

react hydrateRoot to not stack dom trees
Repository: tauri
Issue: Allow developers to implement their own Permission Prompts
Labels: scope: core,type: feature request,priority: 2 medium,type: breaking change

**Is your feature request related to a problem? Please describe.**
I am developing an application which is opened via another application. When my application is launched it connects to a WebRTC connection and attempts to share the screen using `navigator.mediaDevices.getUserMedia`. 
This is required to be done with zero user interaction.

**Describe the solution you'd like**
A method for developers to override the permissions dialog, to enable to show our own prompts or other custom logic.
e.g. a config flag, per permission(?), to expose events to both JS and Rust for when the application requires/requests permissions


**Describe alternatives you've considered**
[Electron already does this](https://github.com/electron/electron/issues/27208) but it is opt-out, meaning that **no** dialogs are shown for any permission requests - [very bad for security](https://github.com/electron/electron/issues/12931)

**Additional context**
definitely needs to be an opt-in so that the user is prompted in default configuration
See Electron GH issues above for more context

Related: tauri-apps/wry#81
Repository: vscode
Issue: Disassembly View: Milestone 2 
Labels: feature-request,debug,debug-disassembly

Use this to keep track of work for the next milestone.

**Features**:
- [x] Show/Hide source code between instructions.
- [ ] Horizontal Scrolling
- [ ] Enable/Disable/Condition for Instruction Breakpoints #129571
- [ ] Copy Blocks of instruction
- [ ] ~~Show/Hide/Rearrange Columns~~
- [ ] GoTo Disassembly at a specific address

**Bugs from Test Disassembly View #129161**
- [ ] Disassembly view: after session ends if new session is started the disassembly view is left empty #129526
- [ ] Disassembly view: not possible to set instruction breakpoint with keyboard #129532
- [ ] Instruction breakpoints should maybe use a different breakpoint icon #129543
- [ ] List: Dragging an element causes focus to jump to container when DnD disabled #129582
- [ ] Disassembly View: instruction address is not the same as a memory reference. #129655
Repository: pytorch
Issue: crash in libtorch jit
Labels: oncall: jit

## 🐛 Bug

My libtorch program crashed because of a assertion, an I was asked to report this:
```C
invalid model file: Expected one of cpu, cuda, xpu, mkldnn, opengl, opencl, ideep, hip, msnpu, mlc, xla, vulkan, meta, hpu device type at start of device string: 
[...]
terminate called after throwing an instance of 'c10::Error'
  what():  _ivalue_INTERNAL ASSERT FAILED at "../torch/csrc/jit/api/object.cpp":19, please report a bug to PyTorch. 
Exception raised from _ivalue at ../torch/csrc/jit/api/object.cpp:19 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x69 (0x7f5949d021d9 in ${TORCH_PATH}/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, char const*) + 0xc5 (0x7f5949cfe995 in ${TORCH_PATH}/lib/libc10.so)
frame #2: <unknown function> + 0x38c06cb (0x7f594d8116cb in ${TORCH_PATH}/lib/libtorch_cpu.so)
frame #3: torch::jit::Object::find_method(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const + 0x38 (0x7f594d811bc8 in ${TORCH_PATH}/lib/libtorch_cpu.so)
```

## To Reproduce

Cannot reproduce. The next time I ran the same program with the same jit model, it starts as expected.

## Expected behavior

No crash

## Environment

```
PyTorch version: 1.9.0+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.2 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: 10.0.0-4ubuntu1 
CMake version: version 3.16.3

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1650
Nvidia driver version: 470.57.02
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.2.2
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] lietorch==0.1
[pip3] numpy==1.17.4
[pip3] numpydoc==1.1.0
[pip3] torch==1.9.0
[pip3] torchaudio==0.9.0
[pip3] torchvision==0.10.0
[conda] Could not collect
```

## Additional context

The backtrace contains references to `libtorch_cpu.so`. I think this is supposed to be `libtorch_cuda.so`.

cc @gmagogsfm
Repository: pytorch
Issue: [FX] Does PyTorch want to support for dynamic control flow for torch.fx?
Labels: triaged,module: fx

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Does PyTorch have a plan to make symbolic tracing support dynamic control flow on torch.fx? 

## Motivation

We are proposing a graph_manipulation and visualization tool target for PyTorch model. Our tool is built based on torch.fx for generating IR representation. However, we found torch.fx can not be used for a specific set of models including LTSM and fairseq, and it is caused by the dynamic control flow inside these models. 

Therefore, we want to know whether PyTorch has a schedule to support the dynamic control flow feature on torch.fx? This really matter for our tool.

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

## Pitch

<!-- A clear and concise description of what you want to happen. -->

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @ezyang
Repository: flutter
Issue: [in_app_purchase] Separate official example into multiple easier to digest examples
Labels: d: examples,a: quality,p: in_app_purchase,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Currently, all the purchase type examples are cramped in 1 dart file. It would be nice to separate them so it would be quicker and easier to digest.

E.g. if i am only interested in the upgrade app to pro version, then i do not have to see all other variables that are not needed.
Repository: pytorch
Issue: Make interpolation output size compatible with opencv, scikit-image and scipy for floating scale factor
Labels: triaged,enhancement,module: interpolation

## 🚀 Feature

Interpolation output size is incorrectly computed with `floor` vs opencv/skimage/scipy are using `round`:

```
# pytorch
output_size = floor(input_size * scale)
```
vs
```
# opencv
output_size = round(input_size * scale)
```

### Details

Currently, interpolation output size if using float scale factor and `recompute_scale_factor=False` is computed as 
https://github.com/pytorch/pytorch/blob/c06b6e445f022b062924ae9b49e2739c2992d067/aten/src/ATen/native/UpSample.cpp#L22
https://github.com/pytorch/pytorch/blob/c06b6e445f022b062924ae9b49e2739c2992d067/aten/src/ATen/native/UpSample.cpp#L24
if `recompute_scale_factor=True`:
https://github.com/pytorch/pytorch/blob/9fdf7ec6a21f1bf9fabccb27ff2b54d94a82c3f3/torch/nn/functional.py#L3687-L3695

In both cases, this can lead to -1 pixel output size comparing to opencv, scikit-image or scipy. For example, let's rescale an image of size (32, 32) with different scale factors: `[0.1234, 0.9999, 1.8]`. This gives the following output sizes per library:
```
- check scale_factor=0.1234
Error: different shapes: opencv (4, 4) vs sk-img (4, 4) vs scipy (4, 4) vs pth (3, 3)

- check scale_factor=0.9999
Error: different shapes: opencv (32, 32) vs sk-img (32, 32) vs scipy (32, 32) vs pth (31, 31)

- check scale_factor=1.8
Error: different shapes: opencv (58, 58) vs sk-img (58, 58) vs scipy (58, 58) vs pth (57, 57)

...
```

Here is a gist with details: https://gist.github.com/vfdev-5/a5bd5b1477b1c82a87a0f9e25c727664

## Pitch

It would be helpful to have compatible output size using pytorch interpolate op.

## Alternatives

Use output size argument directly instead of scales.

## Additional context

Here is equivalent code for 
- opencv: 
  - https://github.com/opencv/opencv/blob/68d15fc62edad980f1ffa15ee478438335f39cc3/modules/imgproc/src/resize.cpp#L4049-L4058
  - https://github.com/opencv/opencv/blob/68d15fc62edad980f1ffa15ee478438335f39cc3/modules/core/include/opencv2/core/saturate.hpp#L140
- scikit-image: https://github.com/scikit-image/scikit-image/blob/e128e0743bb2cded104654352a13ed5b4e53efb8/skimage/transform/_warps.py#L286
- scipy: https://github.com/scipy/scipy/blob/44e31b1eb202ef91caad059952ba268d2610a60b/scipy/ndimage/interpolation.py#L768-L769


cc @fmassa
Repository: rust
Issue: Ignored doctests are run with `cargo test -- --ignored`.
Labels: T-rustdoc,A-doctests

If you use `rust,ignore` to ignore doctests which don't compile (often because you want to include example code that's entirely expository in your documentation — something that doesn't compile at all, and should merely syntax highlight as Rust), they still are attempted to compile and run when you pass `--ignored` to the test runner.

This is unfortunate, as this is what you use to run `#[ignore]`d tests, which are good (intended?) for tests that are too slow to complete in normal execution, often ones which are exhaustive. Having doctests that fail to compile be mixed in here means this use of `#[ignore]` is effectively broken.

The workaround I know for this is rather gross, e.g. using a `const _: &str = stringify!{ /* code that doesn't compile here */ }` wrapper ([for example](https://github.com/serde-rs/serde/blob/d9c338ec4abd1dd6fdd305e208bff1fd7faaabff/serde_test/src/lib.rs#L28-L30) — even if using `ignore` wouldn't have been an alternative here since it's large enough that you'd rather ensure it compiles in practice, this is the pattern I'm referring to).

I think it's honestly a bug that this is the effect of `rust,ignore`, and think that instead it should be to just not emit the test.

(This is related to, but distinct from https://github.com/rust-lang/rust/issues/30032)

I bugged @jyn514 about this once and he indicated he thought it might require an RFC to fix, but when I was complaining about it elsewhere recently, someone pointed out that there was no bug on file for it already.
Repository: godot
Issue: Animation player starting pose is not the one in the animation
Labels: discussion,topic:animation

### Godot version

3.3.stable

### System information

Zorin OS 15

### Issue description

Wen launching the game whit a rigged mesh, if the animation is not playing the mesh starts in "T pose", not in the pose of the first frame of the set animation.

This is how it ignores the first frame pose unless playing the animation;
![Screenshot from 2021-07-29 15-30-58](https://user-images.githubusercontent.com/27329423/127501318-ca32f4be-637a-4f14-a793-a0ce6da76702.png)

This is how is supposed to look the pose of the first frame of the character animation:
![Screenshot from 2021-07-29 15-32-27](https://user-images.githubusercontent.com/27329423/127501352-922f2e0d-9d63-44ee-9f0d-720cabdef5a4.png)

This is not good if you just want to spam, E.G., a character in a crouch pose then play an animation wen the player gets close, since the character will spam in T pose unless you play an animation.

### Steps to reproduce

Set a mesh to an animation but don't set it to auto start.


It can be worked around in scripts but this is a pain to set up to all animated characters.
```
var first_frame:bool = false
func _ready():
	$AnimationPlayer.play("AnimationPose")

func _process(delta):
	if not first_frame:
		first_frame = true
		$AnimationPlayer.stop(true)
```

It can be also worked around creating a separated looping animation of a single frame with the pose, but again, a pain to set up.

### Minimal reproduction project

Can't share the project.
Repository: vscode
Issue: Allow to control the sidebar icon size
Labels: feature-request,layout

<!-- ⚠️⚠️ 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. -->
I would like VSCode to expose a setting that would allow me to increase or decrease the size of the icon in the sidebar (without further affecting the UI).

This can greatly improve experience when using icon sets such as material icons which includes semantic icons.
Repository: excalidraw
Issue: Feature: New shared whiteboard with initial content
Labels: discussion

Context:

I'm contributing to [Alkemio](https://alkem.io/), an open (and open source) innovation platform. On this platform, people can collaborate on innovations. Alkemio facilitates the whole process of innovation, from initial definition of problems, to collaborating in concrete projects to work on solutions.

Feature:

We would like to be able to allow people to create a new whiteboard with initial content (for example, actors and key users with their name) depending on the current challenge. We would also like for this whiteboard to be able to be shared with the other participants in this challenge.


Proposal:

Both creating a shared whiteboard and creating one with initial content is possible (the #room= and #url=) construction respectively. However, it doesn't appear to be possible to do both in one url to excalidraw.com. This complicates the workflow for users, since they would have to share the whiteboard with content and then copy the url back into Alkemio.

Enable using both these options at the same time by not anchoring the regexes to the beginning and end of the hash. 

If desired, I would be more than happy to propose a PR that does this.
Repository: pytorch
Issue: Understatement about how running_var is computed in BatchNorm
Labels: module: docs,triaged,module: norms and normalization

## 📚 Documentation

In the current documentation of `BatchNorm` the phrase "The standard-deviation is calculated via the biased estimator, equivalent to torch.var(input, unbiased=False)" is a little confusing. The thing is that according to the [source code](https://github.com/pytorch/pytorch/blob/420b37f3c67950ed93cd8aa7a12e673fcfc5567b/aten/src/ATen/native/Normalization.cpp#L223-L224) of `BatchNorm2d` (and other batchnorms) this layer uses biased variance estimator during training, but accumulates unbiased version in `running_var`. This can lead to misunderstanding for developers who implement their own layers and compare their realizations with the original.


cc @brianjo @mruberry
Repository: pytorch
Issue: DDP
Labels: oncall: distributed,module: ddp

https://pytorch.org/docs/stable/notes/ddp.html

import torch
import torch.distributed as dist
import torch.multiprocessing as mp
import torch.nn as nn
import torch.optim as optim
from torch.nn.parallel import DistributedDataParallel as DDP


def example(rank, world_size):
    # create default process group
    dist.init_process_group("gloo", rank=rank, world_size=world_size)
    # create local model
    model = nn.Linear(10, 10).to(rank)
    # construct DDP model
    ddp_model = DDP(model, device_ids=[rank])
    # define loss function and optimizer
    loss_fn = nn.MSELoss()
    optimizer = optim.SGD(ddp_model.parameters(), lr=0.001)

    # forward pass
    outputs = ddp_model(torch.randn(20, 10).to(rank))
    labels = torch.randn(20, 10).to(rank)
    # backward pass
    loss_fn(outputs, labels).backward()
    # update parameters
    optimizer.step()

def main():
    world_size = 2
    mp.spawn(example,
        args=(world_size,),
        nprocs=world_size,
        join=True)

if __name__=="__main__":
    main()






Exception: process 1 terminated with exit code 1

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: deno
Issue: bug: panic when caching typescript module with trailing slash
Labels: bug,cli

**Description**

When I try to cache this module at `https://bug-repro.deno.dev/hello/` , Deno panics with the following error:

![image](https://user-images.githubusercontent.com/43033058/127515917-684f5c8e-d57e-4ae5-8e0d-ba6f4ddafa57.png)

This only happens when using a trailing slash at end of URL and serving the code with content-type set to application/typescript, so might be related to type checking.

**How to reproduce**

Run `deno cache https://bug-repro.deno.dev/hello/`

**Expected behavior**

Deno shouldn't panic and cache the module normally.

**Additional info**

[backtrace (full)](https://cdn.discordapp.com/attachments/848911908127113296/870320819224592394/backtrace.txt)
[bug-repro server source](https://cdn.discordapp.com/attachments/848911908127113296/870321247194583060/source.js)

Deno: v1.12.2 (same result on canary 4641aacba67d8ad6c80c903c2aa6b2488e3caf49)
Repository: create-react-app
Issue: Start script not listening to stdin
Labels: stale,needs triage,issue: bug report

### Describe the bug

I use Create React App as part of an asset pipeline in a web framework (in my case Phoenix). As part of the development pipeline, I've set up a watcher to run `react-scripts start` whenever my web server starts.

This works fine, but whenever I terminate my web server, Webpack dev server remains running in the background. I want Webpack dev server to listen on stdin for SIGINT and SIGTERM so it can terminate itself.

I noticed in [start.js](https://github.com/facebook/create-react-app/blob/main/packages/react-scripts/scripts/start.js) that there is an event listener set up for SIGINT and SIGTERM, but this didn't work for me. 

Referring to this [documentation](https://nodejs.org/api/process.html#process_signal_events), I can fix the issue on my machine by adding this line;

```js
process.stdin.resume()
```

before any of the process event handlers are added. I think process will exit prematurely and not listen to stdin without that.

If this works for everyone, I'd be happy to put in a PR.

### Did you try recovering your dependencies?

Yes.

### Which terms did you search for in User Guide?

Start, listen, stdin, sigint, and sigterm.

### Environment

```
  System:
    OS: macOS 10.15.7
    CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz
  Binaries:
    Node: 15.8.0 - ~/.asdf/installs/nodejs/15.8.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 7.5.4 - ~/.asdf/installs/nodejs/15.8.0/.npm/bin/npm
  Browsers:
    Chrome: 92.0.4515.107
    Edge: Not Found
    Firefox: 83.0
    Safari: 14.1.1
  npmPackages:
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: 4.0.3 => 4.0.3
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

Described above.

### Expected behavior

`react-scripts start` should listen to stdin for SIGINT and SIGTERM and terminate itself.

### Actual behavior

Webpack dev server keeps running in the background after its spawning process gets terminated.

![screenshot](https://user-images.githubusercontent.com/14489814/127520837-33bdf3f6-8006-4c79-9ac0-b04d89ba583e.png)