sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: react-scripts has a very low version dependency mini-css-extract-plugin : 0.9.0
Labels: stale,needs triage

react-scripts has a very low version dependency mini-css-extract-plugin : 0.9.0
i want to use version over mini-css-extract-plugin : 1.1.0,  what should i do
is there any solution except eject?
Repository: create-react-app
Issue: JS and CSS files not loading in the react build 
Labels: stale,needs triage,issue: bug report

I built a react app , it works fine when i run it usinfg the command 'serve -s build' but as soon as i start my index.html using a live server , nothing loads . I am only able to see my favicon.ico and my background color ,apart from that nothing is visible as no js and css files are getting loaded . I even tried giving the homepage:"."  and homepage:"./ " in my package.json , but still nothing happened . The CSS and JS file path in my index.html are correct as I am getting redirected to them if i CNtrl+click on the link using vscode . I am unable to understand the issue . It would be a great help if somebody could guide me forward .
Repository: godot
Issue: Baking GIProbe causes the whole scene to flash white temporarily
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

3.3stable

### System information

Xubuntu 21.04, Intel UHD Graphics 620

### Issue description

When re-baking GIProbe after geometry with emissive materials has been changed, the whole scene flashes white (or weirdly colored). My best guess is that GIProbe is using "uninitialized" GI data while baking is in progress.

My workaround is to set GIProbe energy to zero for a few frames after baking. This obviously causes the scene to darken  due to missing GI but it's a lot less visible.

### Steps to reproduce

Re-bake GIProbe in a scene mostly lit by emission from materials.

### Minimal reproduction project

[GIProbeFlash.zip](https://github.com/godotengine/godot/files/6906706/GIProbeFlash.zip)

Run project, press any key to re-bake GI.
Repository: godot
Issue: `core/project_settings.cpp` attempts to get modified time for `godot.project` in exported project
Labels: bug,topic:core,topic:export

### Godot version

3.3.stable

### System information

Windows 10

### Issue description

When using `override.cfg` or `user://custom_settings.cfg` in an exported build, the Godot instance attempts to get a modified time for a non-existing `res://godot.project`-file, resulting in following error:

![Capture](https://user-images.githubusercontent.com/42484461/127654531-616fef9e-3e48-4f2a-b0a4-a43831f2b21e.PNG)

On exported builds the `godot.binary` should be used instead...
The offending line is found on line 565 in the `core/project_settings.cpp`-file:
https://github.com/godotengine/godot/blob/7f4eafa6f28e3aa3f36eb358ec3e0b69b1803240/core/project_settings.cpp#L565

This line should in some way or form address the fact that the Godot instance could be an exported build.

### Steps to reproduce

1. Create a new Godot project
2. Create a new empty Node2D scene (or similar)
3. Define this scene as the project's `application/run/main_scene` in the ProjectSettings
4. Export the project to Windows in DEBUG mode (other platforms probably have similar issues, but I can't test this)
5. Create a `override.cfg` file, put it next to the exported EXE and add following content to this file:

```
[display]

window/size/fullscreen=true
```

6. Run the EXE and check the console for errors.


### Minimal reproduction project

[override_testing.zip](https://github.com/godotengine/godot/files/6907625/override_testing.zip)
Repository: frp
Issue: Allow multiple HTTP proxies on different ports
Labels: future

<!-- From Chinese to English by machine translation, welcome to revise and polish. -->

**The solution you want**
<!--A clear and concise description of the solution you want. -->
The ability to have multiple HTTP proxies on different remote ports.

**Alternatives considered**
<!--A clear and concise description of any alternative solutions or features you have considered. -->
Giving the HTTPS type proxy the same options as HTTP type proxies, but that would still only allow 2 remote ports.

**How to implement this function**
<!--Implementation steps for the solution you want. -->
Remove `vhost_http_port` and replace it with `remote_port` on the client, like with TCP proxies.

**Application scenarios of this function**
<!--Make a clear and concise description of the application scenario of the solution you want. -->
Anything requiring multiple HTTP proxies on different ports, (e.g. a Synapse server)
Repository: PowerToys
Issue: Feature Request: Mirror desktop in specific zone
Labels: Idea-Enhancement,FancyZones-Layouts,Product-FancyZones

I love that I can create a zone that is 1920x1080. Makes screen sharing a breeze on my ultrawide. It would be amazing if I could mirror my whole desktop inside that zone. That would allow sharing the whole desktop.
Repository: flutter
Issue: PaginatedDataTable and paginated data from the server
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

Hi!!
Does it make any sense that the PaginatedDataTable widget doesn't support paginated data from the server instead of fetching all the data?
When the tables on the server are very large, which happens most of the time, the correct thing to do is to take the data as it is being displayed. 
Thanks a lot.
Repository: flutter
Issue: Proposal to provide option to adjust height of its container of PaginatedDataTable 
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

Hi!
The PaginatedDataTable widget should have the option to take the full height of the display area and be able to put the header row fixed.
Now that Flutter has web and desktop support, the logical and correct thing is that the table, if desired, be adjusted to the height and size of the window in which it is located. 
Regards,
Repository: godot
Issue: EditorInspector for Sprite/Sprite3D: tabbing after typing in Hframes/Vframes shows LineEdit in wrong location
Labels: bug,topic:editor

### Godot version

3.3.2.stable, 3.4.beta2

### System information

Windows 7

### Issue description

Title. In action:
![XMjfMjs4P8](https://user-images.githubusercontent.com/9283098/127687940-db0b6d9e-db28-499a-b686-b06ec8fe5ae3.gif)


### Steps to reproduce

See GIF above.
Create new `Sprite`/`Sprite3D` node, in inspector click its `SpinSlider` for `Hframes` for gaining focus.
Type in a valid value different than the current one (e.g. `2`) and press <kbd>Tab</kbd>.

### Minimal reproduction project

Not needed, just create a `Sprite`/`Sprite3D` anywhere.
Repository: rust
Issue: Explain Fn+Sync requirement
Labels: A-diagnostics,T-compiler

Given the following code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=4bc0c9d55bf6300037e374443f31290a)):

```rust
use rayon::prelude::*;

fn main() {
    let mut v = vec![];

    (0..1024).into_par_iter().for_each(|i| v.push(i));
}
```

The current output is:

```
error[E0596]: cannot borrow `v` as mutable, as it is a captured variable in a `Fn` closure
 --> src/main.rs:6:44
  |
6 |     (0..1024).into_par_iter().for_each(|i| v.push(i));
  |                                            ^ cannot borrow as mutable

error: aborting due to previous error
```

While technically correct, this doesn't guide the beginner in understanding what "a `Fn` closure" is, why this specific closure is "a `Fn` closure", and what the actual underlying problem is, in domain-specific rather than language-specific terms.

Ideally the output would look something like this:

```
error[E0596]: cannot borrow `v` as mutable, as it is a captured variable in a `Fn` closure
 --> src/main.rs:6:44
  |
6 |     (0..1024).into_par_iter().for_each(|i| v.push(i));
  |                               --------     ^ cannot borrow as mutable
  |                               |
  |           expects `Fn` instead of `FnMut`

note: the closure is required to implement `Fn` here
 --> rayon-1.5.1/src/rayon/iter/mod.rs:367:8
    |
    |    fn for_each<OP>(self, op: OP)
    |    where
367 |        OP: Fn(Self::Item) + Sync + Send
    |        ------------------

help: the closure may be invoked concurrently from multiple threads, consider using some
      means of synchronization
```

* It would indicate where the requirement for the closure to implement `Fn` even comes from
* It would state, in straightwordward terms, what the underlying problem is: the code is trying to modify `v` from several threads concurrently. I believe it's safe to say a closure that is required to be `Fn + Sync` "may be invoked concurrently from multiple threads" without special-casing Rayon.

Note: this is a simplified version of a real-life error a beginner has struggled with. Once I told her the actual issue was she was trying to mutate the vector form several threads, she was able to fix it.
Repository: transformers
Issue: Weird behavior with mBART-50 and Spanish
Labels: WIP

## Environment info
- `transformers` version: 4.9.1
- Platform: Linux-5.4.0-1054-aws-x86_64-with-debian-buster-sid
- Python version: 3.7.10
- PyTorch version (GPU?): 1.9.0+cu102 (True)

## Who can help
@patrickvonplaten

## Information
I am seeing weird behavior with mBART-50 and Spanish. Please look at the code below:
```
from transformers import MBartForConditionalGeneration, MBart50TokenizerFast

text = "http://www.ted.com/talks/stephen_palumbi_following_the_mercury_trail.html"

model = MBartForConditionalGeneration.from_pretrained("facebook/mbart-large-50-many-to-one-mmt")
tokenizer = MBart50TokenizerFast.from_pretrained("facebook/mbart-large-50-many-to-one-mmt")
tokenizer.src_lang = "es_XX"

encoded = tokenizer(text, return_tensors="pt")
generated_tokens = model.generate(**encoded, forced_bos_token_id=tokenizer.lang_code_to_id["en_XX"])
tokenizer.batch_decode(generated_tokens, skip_special_tokens=True)
```
The output is:
```
['(b) To continue to cooperate closely with the Special Rapporteur on extrajudicial, summary or arbitrary executions, the Special Rapporteur on torture and other cruel, inhuman or degrading treatment or punishment, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special Rapporteur on torture and other cruel, inhuman or degrading treatment or punishment, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special Rapporteur on violence against women, its causes and consequences, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special Rapporteur on the sale of children, child prostitution and child pornography, the Special']
```

However if I change the source language to french `tokenizer.src_lang = "fr_XX"` or any other language, I get the following output (which is what you expect):
```
['http://www.ted.com/talks/stephen_palumbi_following_the_mercury_trail.html']
```

This behavior is similar with other texts as well (e.g., "888"). Do you know why this behavior is unique to Spanish? Also, do you have any idea how to correct this behavior?

Thanks!
Repository: flutter
Issue: Figure out a way to make diagnostic numbers print the same when running on the web.
Labels: team,framework,platform-web,P2,c: tech-debt,team: skip-test,team-web,triaged-web

As part of the skip test audit (#86396), there is a problem with `debugFillProperties` on the web that causes a couple of tests to fail.

Dart doubles and ints are backed by the same kind of object because JavaScript does not support integers. So, the Dart double "4.0" is identical to "4", which results in the web evaluating to the value "4" regardless of which one is used. This results in a difference for doubles in debugFillProperties between the web and the rest of Flutter's target platforms.

So when we are testing diagnostic strings in tests they will fail even though the data is almost identical. For example if we turn off the skip on:

https://github.com/flutter/flutter/blob/1f067aea1b745d81898ceb9ce362b90a264ac774/packages/flutter/test/painting/decoration_test.dart#L327

It will fail with a difference in the error strings that are generated:

```
  Expected: 'FlutterError\n'
              '   DecorationImage.matchTextDirection can only be used when a\n'
              '   TextDirection is available.\n'
              '   When DecorationImagePainter.paint() was called, there was no text\n'
              '   direction provided in the ImageConfiguration object to match.\n'
              '   The DecorationImage was:\n'
              '     DecorationImage(SynchronousTestImageProvider(),\n'
              '     Alignment.center, match text direction, scale: 1.0)\n'
              '   The ImageConfiguration was:\n'
              '     ImageConfiguration(size: Size(100.0, 100.0))\n'
              ''
    Actual: 'FlutterError\n'
              '   DecorationImage.matchTextDirection can only be used when a\n'
              '   TextDirection is available.\n'
              '   When DecorationImagePainter.paint() was called, there was no text\n'
              '   direction provided in the ImageConfiguration object to match.\n'
              '   The DecorationImage was:\n'
              '     DecorationImage(SynchronousTestImageProvider(),\n'
              '     Alignment.center, match text direction, scale: 1)\n'
              '   The ImageConfiguration was:\n'
              '     ImageConfiguration(size: Size(100.0, 100.0))\n'
              ''
     Which: is different.
            Expected: ... , scale: 1.0)\n   Th ...
              Actual: ... , scale: 1)\n   The  ...
                                    ^
             Differ at offset 381
```

We should find a way to fix this or workaround it.

Another test that is turned off because of this is:

https://github.com/flutter/flutter/blob/bdca3391b4af2f903599a08bcbc098656cc8281b/packages/flutter/test/material/app_bar_theme_test.dart#L489
Repository: pytorch
Issue: meta tensor `set_` seems fishy
Labels: module: internals,triaged,module: meta tensors

## 🐛 Bug

```
import torch

x = torch.randn(3, 3, device='meta')
y = torch.randn(2, 2, device='meta')

y.set_(x)
print(x.shape, y.shape)
```
produces: `(3, 3)` and `(2, 2)`. Not sure if this is intentional, if it is intentional it should probably be documented some way

## Additional context

I'm brainstorming workarounds for https://github.com/pytorch/pytorch/issues/62182

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh
Repository: rust
Issue: LLVM error while building Rust Crypto's AES-GCM usage example code for target x86_64-unknown-none-linuxkernel
Labels: A-LLVM,T-compiler,C-bug,requires-nightly

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
#![no_std]

use aes_gcm::Aes256Gcm;
use aes_gcm::aead::{Aead, NewAead};

use generic_array::GenericArray;

pub fn encrypt_data() {
    let key = GenericArray::from_slice(b"an example very very secret key.");
    let cipher = Aes256Gcm::new(key);

    let nonce = GenericArray::from_slice(b"unique nonce"); // 96-bits; unique per message

    let ciphertext = cipher.encrypt(nonce, b"plaintext message".as_ref())
        .expect("encryption failure!"); // NOTE: handle this error to avoid panics!

    let plaintext = cipher.decrypt(nonce, ciphertext.as_ref())
        .expect("decryption failure!"); // NOTE: handle this error to avoid panics!

    assert_eq!(&plaintext, b"plaintext message");
}
```
Build command: 
```
cargo build -Z build-std=core,alloc --release --target=x86_64-unknown-none-linuxkernel
```
Alternate build command (with AES and AVX2 explicitly enabled):
```
-Ctarget-cpu=native -Ctarget-feature=+aes,+ssse3,+avx2" cargo build -Z build-std=core,alloc --release --target=x86_64-unknown-none-linuxkernel
```

I expected to see this happen: Compilation without an LLVM error, as this is usage example code from the AES-GCM documentation (https://docs.rs/aes-gcm/0.9.3/aes_gcm/index.html).

Instead, this happened: I got this LLVM error (same error for both commands):
```
   Compiling encryption v0.1.0 (/home/prathik/Code/encryption)
LLVM ERROR: Do not know how to split the result of this operator!

error: could not compile `encryption`
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
The issue disappears if I don't set the target to the linuxkernel target. I'm stumped since this is an LLVM error rather than a rustc/cargo error with line numbers. The maintainer of AES-GCM suggested explicitly enabling AES and AVX2 target support, but to no avail (see above).

`rustc --version --verbose`:
```
rustc 1.53.0-nightly (968425893 2021-04-26)
binary: rustc
commit-hash: 9684258936dabda2ba49d4c67f041a6baf388348
commit-date: 2021-04-26
host: x86_64-unknown-linux-gnu
release: 1.53.0-nightly
LLVM version: 12.0.0

```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
prathik@prathiks-buntobox:~/Code/encryption$ RUST_BACKTRACE=1 cargo build -Z build-std=core,alloc --release --target=x86_64-unknown-none-linuxkernel
   Compiling encryption v0.1.0 (/home/prathik/Code/encryption)
LLVM ERROR: Do not know how to split the result of this operator!

error: could not compile `encryption`

To learn more, run the command again with --verbose.
```

</p>
</details>
Repository: create-react-app
Issue: Deploy To GH-Pages Doesn't Work
Labels: stale,needs triage,issue: bug report


there is loads of conflicting advice on the internet, but none of it works...

Run react built, gh-pages deploy, and all I get is 404 errors. smh
Repository: rust
Issue: WASM float to int performance regression since 1.53.0
Labels: O-wasm,C-bug

Both Rust and WASM introduced saturating float to int casts. However WASM originally only had trapping float to int casts. LLVMs internal float casts are speculatable, i.e. it can execute them early, assuming no trap ever happens. This however means LLVM needs to protect itself from WASM's trapping casts by emitting some more code around it. Once Rust introduced saturating float to int casts, rustc itself started emitting a bunch of code around the casts to saturate the values. This then led to both rustc and LLVM emitting this guard code around each cast. However since rustc already protected itself some dangerous values, LLVM didn't need to emit any of these additional instructions. This was eventually implemented. Check this previous issues and related PRs: https://github.com/rust-lang/rust/issues/73591

However with the switch to LLVM 12, it was possible to throw out a lot of the manual codegen in rustc:
https://github.com/rust-lang/rust/pull/84339 which acknowledges a regression in those casts

and then a follow up PR:
https://github.com/rust-lang/rust/pull/84654 which supposedly fixes the regression

However it seems like there's still a regression: https://rust.godbolt.org/z/W18vGcv9T

cc @alexcrichton
Repository: vscode
Issue: Simple split editor should show the full file path in an editor tab tooltip
Labels: bug,settings-editor

https://github.com/microsoft/vscode/issues/125952#issuecomment-881169386

> The open settings.json tab now has no path name. Not in the title bar, not in the tab tooltip.

I need to create a custom editorinput to override this
Repository: pytorch
Issue: torch.prod internal asserts when passed a tensor that requires_grad (and a dtype)
Labels: module: autograd,triaged,module: assert failure

## 🐛 Bug

```
import torch
x = torch.randn(2, 3, requires_grad=True)
x.prod(dtype=torch.long)
```

```
RuntimeError: isDifferentiableType(variable.scalar_type())INTERNAL ASSERT FAILED at "../torch/csrc/autograd/functions/utils.h":65, please report a bug to PyTorch.
```

## Expected behavior

Maybe there should be an error when `dtype=long` is thrown? Or this should not internal assert


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: terminal
Issue: Multi-line paste with WSL omits and splices together lines
Labels: Resolution-External,Area-Input,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version (or Windows build number)

Windows Terminal version 1.9.1942.0, WSL version 1, Windows 10 21H1 Build 19043.985

### Other Software

_No response_

### Steps to reproduce

Paste the following 50 lines of text into your bash prompt using Ctrl + Shift + V, with the terminal height set to the default of 30 rows:

```
line 1
line 2
line 3
line 4
line 5
line 6
line 7
line 8
line 9
line 10
line 11
line 12
line 13
line 14
line 15
line 16
line 17
line 18
line 19
line 20
line 21
line 22
line 23
line 24
line 25
line 26
line 27
line 28
line 29
line 30
line 31
line 32
line 33
line 34
line 35
line 36
line 37
line 38
line 39
line 40
line 41
line 42
line 43
line 44
line 45
line 46
line 47
line 48
line 49
line 50
```

### Expected Behavior

_No response_

### Actual Behavior

It only pastes as many lines as the height of the terminal, and then skips everything until the last line. For instance, if I paste into the terminal when it's 30 lines high (the default), it prints line 1 through line 30 and then skips to line 50:

![image](https://user-images.githubusercontent.com/7513967/127721415-fa5aa608-9bcc-44ed-be72-81a68f297510.png)

If I then maximize, it looks fine... except that line 9 is incorrectly printed as "line 90":

![image](https://user-images.githubusercontent.com/7513967/127721559-b76b31af-4e08-4d6b-b79c-25589a28ed97.png)

and if I then re-minimize, it incorrectly prints line 2 as line 22, line 3 as line 33, ... and line 9 as line 99. There was no line 99 in my original text, so it seems to be splicing together bits of different lines.

![image](https://user-images.githubusercontent.com/7513967/127721618-7aba3fd7-3e55-4516-afe4-dd9997a25396.png)

Interestingly, if I copy-paste the terminal contents into Sublime Text, it pastes the incorrect text, including the line 99 thing:

![image](https://user-images.githubusercontent.com/7513967/127721694-57ce93a8-ed4e-4fa2-93c5-19a9d1b1677d.png)

Another test I tried is pasting the original "line 1", "line 2", ... "line 50" text when the terminal is 30 lines tall, and then expanding it to 32 lines. Now it prints lines 31 and 32 before skipping to line 50. It also incorrectly prints line 8 as "line 80" and line 9 as "line 90" - the 0 is probably coming from "line 10" immediately below:

![image](https://user-images.githubusercontent.com/7513967/127721961-4b29fab3-3781-427f-8deb-67e3320f3fe9.png)
Repository: deno
Issue: Make DENO_COVERAGE_DIR public
Labels: suggestion,testing

The `DENO_UNSTABLE_COVERAGE_DIR` is the environment variable that actually controls if coverage collection takes place or not. It has a terrible name and is not documented anywhere as it is not considered public at the moment.

Using an environment variable is the most common way to determine if coverage should be collected and where it should be collected too.

This implies that we remove `deno test --coverage` which was kept for backwards compatibility in 1.x.
The removal of the coverage flag would probably have to be a 2.0 change.

Usage would be:

```shell
export DENO_COVERAGE_DIR="some/path"
deno run ...
deno test ...
deno test ...
deno coverage --lcov > cov.lcov
```