sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Crash when overriding _set (?)
Labels: bug,topic:gdscript,topic:editor,confirmed,crash

<!-- Please search existing issues for potential duplicates before filing yours:	
https://github.com/godotengine/godot/issues?q=is%3Aissue	
-->

**Godot version:**
v3.2.2.stable.official / Steam
<!-- Specify commit hash if using non-official build. -->


**OS/device including version:**
Windows 10 / 2004
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->


**Issue description:**
Godot crashs, it is almost reproduceable everytime. It crashs when executing the example project.
I override `_set(property, value)`, which may lead to that crash.

Error message:
```
ERROR: get: FATAL: Index p_index = 7 is out of bounds (size() = 7).
   At: ./core/cowdata.h:152
```
<!-- What happened, and what was expected. -->


**Steps to reproduce:**
Execute the main scene.

**Minimal reproduction project:**
[gd_crash.zip](https://github.com/godotengine/godot/files/4921701/gd_crash.zip)
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->

Another example replace the `_read():` function with this
```gdscript
func _ready():
    #self.my_dict["_"] = MyType.new("1", 1)
    self._non_existent
``` 
Will lead to a crash too.
Repository: pytorch
Issue: [JIT][to-backend] `selective_to_backend` infra
Labels: oncall: jit

Now that #41146 has landed, we need to create and make available some utility functions to help users write code that selectively lowers some modules in a module hierarchy. The main consideration here is that the JIT type of the lowered module and all of its ancestors needs to be updated after lowering to a backend.

cc @suo @gmagogsfm
Repository: PowerToys
Issue: Touchscreen Gesture Customization
Labels: Idea-New PowerToy

I feel with how many touchscreen devices out there we would benefit from customizable touch gestures. There are many different touch gestures that could be implemented.

- swipe up from the bottom to go to desktop (similar to iPhone/Android)
- swipe from the sides to switch desktops/applications
- swipe to display multi-view of currently open apps
- swipe and hold to quick split screen apps
Repository: rust
Issue: Documentation for stdout does not mention flushing
Labels: C-enhancement,T-libs-api,A-docs

From https://github.com/rust-dc/fish-manpage-completions/pull/96#discussion_r453728093.

The documentation for [`std::io::stdout()`](https://doc.rust-lang.org/stable/std/io/fn.stdout.html) does not mention "flush" anywhere, neither does `Stdout` or `StdoutLock`. I think it would be helpful for the documentation to indicate the behaviour, i.e. if it should be flushed manually or it's flushed once it goes out of scope.

The same would apply for `stderr`. I'm not sure if the behaviour of #23205 has changed since, or whether not documenting flushing was an oversight or intended to allow breakage in that regard.
Repository: youtube-dl
Issue: --datebefore now-1day doesn't download videos which are 24 hours old or older
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [ ] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

WRITE QUESTION HERE

I used --datebefore now-1day when downloading all videos on this channel: https://www.youtube.com/channel/UCfwE_ODI1YTbdjkzuSi1Nag/videos

However instead of downloading videos which were created 24 hours ago or older, it downloaded videos which were created 4 hours ago or older.  I have to use this instead which does indeed download videos created 2 days ago or older:
--datebefore now-1day
Repository: vscode
Issue: User settings for language configurations
Labels: feature-request,languages-basic

<!-- ⚠️⚠️ 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. -->
Please add functionality to: set all Autoclosing, Surrounding, Indentation settings and enable Intendation Folding (if possible, on top of language specific one); so they could not be overwritten by Language configs.

When multiple languages are used, the kaleidoscope switching of these settings are disturbing and/or loading the memory for no use. And editing the config files for each language is inconsistent and long.
Repository: create-react-app
Issue: Creat react app script not working in vscode
Labels: stale,needs triage

PS E:\jitsi\MERN> create-react-app MERN
create-react-app : File C:\Users\marsec developer\AppData\Roaming\npm\create-react-app.ps1 cannot be loaded because running scripts is disabled   
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ create-react-app MERN
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS E:\jitsi\MERN> create-react-app mern
create-react-app : File C:\Users\marsec developer\AppData\Roaming\npm\create-react-app.ps1 cannot be loaded because running scripts is disabled   
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ create-react-app mern
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS E:\jitsi\MERN> create-react-app
create-react-app : File C:\Users\marsec developer\AppData\Roaming\npm\create-react-app.ps1 cannot be loaded because running scripts is disabled 
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ create-react-app
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

If you're looking for general information on using React, the React docs have a list of resources: https://reactjs.org/community/support.html

If you've discovered a bug or would like to propose a change please use one of the other issue templates.

Thanks!
Repository: godot
Issue: Cryptic GDScript Error Message for A Beginner Programming Mistake - "Unexpected token"
Labels: enhancement,topic:gdscript,usability

**Godot version:** v3.2.2 stable
**OS/device including version:** Windows 7

**Issue description:**

This 1-line beginner program throws a cryptic error message:

> print("Hello World")

Corresponding error message:
> "Unexpected token: Built-In Func:"

And it's elaborated on in the Errors tab as:
> "get_token_identifier: Condition "tk_rb[ofs].type != TK_IDENTIFIER" is true. Returned: StringName()"

**Expected Behavior**: GDScript is advertised to new users for its similarity to Python. So it's bad when trivial code doesn't work for incomprehensible reasons - nobody should have to check documentation or have to google to debug a "Hello World" program.

**How to Fix it**: GDScript doesn't like the code above because you aren't allowed to do much of anything but define variables or functions at the base level of a script. So either make the reason for this specific error message crystal clear, or make the "Unexpected token" error message in general more clear.

**Elaboration**: Comprehensible error messages are very important for programming. Personally, I tried Godot Engine and GDScript for the reasons mentioned above, then got this bizarre error even when following basic, community-approved programming tutorials. For instance, I followed this tutorial by GDQuest (https://www.youtube.com/watch?v=UcdwP1Q2UlU ), and copying the code on most of the slides in that video causes the error mentioned in this issue, unless you code inside a function like _ready. Naturally, an incomprehensible error message in that situation is *really bad*.
Repository: realworld
Issue: Bearer Authentication
Labels: help wanted,good first issue,Status: Approved,v2 changelog

In the API spec `swagger.json`, the authentication scheme is defined as:
```
"Token": {
      "description": "For accessing the protected API resources, you must have received a a valid JWT token after registering or logging in. This JWT token must then be used for all protected resources by passing it in via the 'Authorization' header.\n\nA JWT token is generated by the API by either registering via /users or logging in via /users/login.\n\nThe following format must be in the 'Authorization' header :\n\n    Token: xxxxxx.yyyyyyy.zzzzzz\n    \n",
      "type": "apiKey",
      "name": "Authorization",
      "in": "header"
    }
```

Shouldn't it be of `"type": "http"`, `"scheme": "bearer"`, `"bearerFormat": "JWT"`?
Repository: electron
Issue: WebAuthn FIDO/FIDO2 Support
Labels: enhancement :sparkles:

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 --> 8.4.0, 9, 10, (added 07.04.2021) 11, 12
* **Operating System:**
  * <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 --> macOS 10.15.5
* **Last Known Working Electron version:**
  * <!-- (if applicable) e.g. 3.1.0 --> -

It is not clear how to make [WebAuthn](https://w3c.github.io/webauthn/) works in Electron app if page is local not from webserver.

### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->

WebAuthn works if page loaded from `standard` and `secure` scheme: https://www.electronjs.org/docs/api/protocol#protocolregisterschemesasprivilegedcustomschemes

### Actual Behavior
<!-- A clear and concise description of what actually happened. -->

I've faced with the following error:

```
Uncaught (in promise) DOMException: Public-key credentials are only available to HTTPS origin or HTTP origins that fall under 'localhost'. See https://crbug.com/824383
```

### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->

https://gist.github.com/mahnunchik/165a117564ebc632a3723d2666f5024c

<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->

<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->

<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->

### Additional Information
<!-- Add any other context about the problem here. -->

Related issues:

* [WebAuthn Support #15404](https://github.com/electron/electron/issues/15404)
* [protocol.intercept{Any}Protocol handler ability to call original handler #15434](https://github.com/electron/electron/issues/15434)
Repository: pytorch
Issue: Implement backend fallback for Tracer
Labels: module: internals,triaged

Now that @ljk53 has extracted tracing functionality into a separate dispatch key, we should now be able to write a single generic fallback for tracing. This is in two parts:

1. Write the generic fallback. This will give us automatic support for tracing custom ops
2. Remove all code generated tracing for anything that is subsumed by the fallback

cc @ezyang @bhosmer @smessmer @ljk53
Repository: pytorch
Issue: GLOO infiniband with PyTorch
Labels: oncall: distributed,feature,triaged

## 🚀 Feature


## Motivation

* From https://discuss.pytorch.org/t/gloo-and-infiniband/89303. Some GPUs like RTX2080ti GPUs do not support GPUDirect/RDMA anyway.
* With GPUs w/ GPUDirect/RDMA, in some scenarios we still would like to do CPU RDMA to avoid DtoH memory copy which causes certain synchronicity and breaks the pipelining.

For these use cases, GLOO infiniband could help achieve lower latency and higher bandwidth, and remove host/device synchronicity.

## Pitch

GLOO has an ibverbs transport in place https://github.com/facebookincubator/gloo/tree/master/gloo/transport/ibverbs. However it was not tested or used with PyTorch. We would like to test and integrate with PyTorch c10d library.


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jiayisuse @agolynski
Repository: rust
Issue: Emit noundef LLVM attribute
Labels: A-LLVM,T-compiler

LLVM 11 introduces a new `noundef` attribute, with the following semantics:

> This attribute applies to parameters and return values. If the value representation contains any undefined or poison bits, the behavior is undefined. Note that this does not refer to padding introduced by the type’s storage representation.

In LLVM 11 itself it doesn't do anything yet, but this will become important in the future to reduce the impact of `freeze` instructions.

We need to figure out for which parameters / return values we can emit this attribute. We generally can't do so if any bits are unspecified, e.g. due to padding. More problematic for Rust is https://github.com/rust-lang/unsafe-code-guidelines/issues/71, i.e. the question of whether integers are allowed to contain uninitialized bits without going through something like MaybeUninit.

If we go with aggressive emission of noundef, we probably need to ~~punish~~ safe-guard `mem::uninitialized()` users with liberal application of `freeze`.

cc @RalfJung
Repository: pytorch
Issue: Make torch.iinfo/torch.finfo torchscriptable
Labels: triage review,oncall: jit,days

It would be helpful for torch.iinfo, torch.finfo, and other dtype attributes like is_floating_point to be torch scriptable.

## Motivation

Information like `torch.iinfo(dtype).max` (and `dtype.is_floating_point`) can be helpful in image transformations, but can't be used in transformations that need to be scriptable.

E.g.:
https://github.com/pytorch/vision/blob/master/torchvision/transforms/functional.py#L164

## Alternatives

for dtype.is_floating_point we can workaround by using torch.empty(0, dtype=dtype).is_floating_point(), but I'm not aware of a scriptable alternative for getting other dtype info like `max`.

## Additional context

This came up as part of this PR:
https://github.com/pytorch/vision/pull/2459


cc @ezyang @gchanan @zou3519 @suo @gmagogsfm
Repository: rust
Issue: Should include crate name in error message for E0391 (and perhaps others) 
Labels: A-diagnostics,T-compiler,C-bug

While doing a bootstrap build of the compiler with some other build artifacts lying around, I saw the following error message (a small snippet from whole output):

```
[RUSTC-TIMING] cfg_if test:false 0.035
   Compiling lock_api v0.3.4
[RUSTC-TIMING] scopeguard test:false 0.068
   Compiling crossbeam-utils v0.6.5
   Compiling tracing-core v0.1.10
   Compiling log_settings v0.1.2
error[E0391]: cycle detected when running analysis passes on this crate
  |
  = note: ...which again requires running analysis passes on this crate, completing the cycle

error: aborting due to previous error

For more information about this error, try `rustc --explain E0391`.
error[E0391]: cycle detected when running analysis passes on this crate
  |
  = note: ...which again requires running analysis passes on this crate, completing the cycle

[RUSTC-TIMING] lazy_static test:false 0.079
error: aborting due to previous error
```

It is sub-optimal to say "on this crate" in a diagnostic like this.

Multiple crates can be compiled in parallel, and thus it can be ambiguous which crate a diagnostic like that is associated with.

In general it would be better to extract a crate name, if possible, and include that in the message, rather than using the simpler-but-potentially-ambiguous "on this crate."
Repository: opencv
Issue: Moves for basic types have copy semantics
Labels: category: build/install,RFC

PR 11899 manually implemented moves for types like Point and Rect. std::move() leaves source POD values unchanged, so all this extra code has no apparent effect.

A better idiom would be e.g. `width(std::exchange(r.width, 0))`.
Repository: pytorch
Issue: Helping test example code blocks in the docs
Labels: module: docs,feature,module: tests,triaged

## 📚 Documentation

<!-- A clear and concise description of what content in https://pytorch.org/docs is an issue. If this has to do with the general https://pytorch.org website, please file an issue at https://github.com/pytorch/pytorch.github.io/issues/new/choose instead. If this has to do with https://pytorch.org/tutorials, please file an issue at https://github.com/pytorch/tutorials/issues/new -->

Hello, I noticed this older issue https://github.com/pytorch/pytorch/issues/6662 is still open and looked through this PR https://github.com/pytorch/pytorch/pull/24435 about adding `doctest` to jit. If it would be helpful I can work on other parts of the docs to convert code blocks to use `doctest`. Currently it seems there are over 400 code blocks in the docs using the format `Example::` that are not being tested, e.g. a bunch are in this [file](https://github.com/pytorch/pytorch/blob/master/torch/_torch_docs.py). 

cc @jlin27 @mruberry @VitalyFedyunin
Repository: vscode
Issue: Allow tooltips/hovering on symbols in outline view and breadcrumbs
Labels: feature-request,outline,breadcrumbs

<!-- ⚠️⚠️ 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. -->

Currently, the information which breadcrumbs and the outline view can provide is limited to two strings: the title and the "detail" (breadcrumbs are not even able to display the detail string). For the underlying complexity of the information being presented, this seems quite limiting.

In order to optionally provide more information about a symbol (and without cluttering the UI), it would be really nice if if symbols could at least provide a tooltip, through an extremely simple `DocumentSymbol.tooltip: string` property (basically identical to the underlying tooltip property of `TreeItem`).

If this feature were to be taken all the way, hovering over symbols in the breadcrumbs or outline view could display information about the symbol from the document's registered HoverProvider for the symbol's selectionRange. This could be enabled/disabled on a symbol-by-symbol basis (something along the lines of `DocumentSymbol.triggerhoverprovider: boolean`). This would make the breadcrumbs and outline view significantly more useful for understanding the structure of a document without fully diving into the code. 

### Bad behaviour

![image](https://user-images.githubusercontent.com/42496508/87610503-cd383c00-c705-11ea-9706-1509849d2ca7.png)

*unhelpful, repetitive, ugly: i already know the name of the symbol, it's just there*

### Good behaviour

![betterhover](https://user-images.githubusercontent.com/42496508/87610792-9d3d6880-c706-11ea-97f8-a708f3793195.png)

*helpful, useful, and pretty: the only way I could know what this part of the document does is by clicking the symbol and hovering over it in the editor*



DocumentSymbols help explain the structure of the code - why limit this explanation to the name, especially when there's more information about them so readily available?
Repository: pytorch
Issue: Tensor.new_tensor is not supported
Labels: oncall: jit,days,TSUsability,TSRootCause:BetterEngineering

This comes up as a common error in Parity Bench.  (scripting)

Here is the error message:

```
Tried to access nonexistent attribute or method 'new_tensor' of type 'Tensor (inferred)'.:
  File ""/tmp/paritybench1zfkgifq/pbqmuageme.py"", line 15
        :param x: Long tensor of size ``(batch_size, num_fields)``
        """"""
        x = x + x.new_tensor(self.offsets).unsqueeze(0)
                ~~~~~~~~~~~~ <--- HERE
        xs = [self.embeddings[i](x) for i in range(self.num_fields)]
        ix = list()
```

[Concrete example](https://github.com/jansel/pytorch-jit-paritybench/blob/570400b612332ecaec0cf850cdc70a6d4ddc374b/generated/test_rixwew_pytorch_fm.py#L126)

cc @suo @gmagogsfm
Repository: pytorch
Issue: Python object None check not supported
Labels: oncall: jit,days,TSUsability,TSRootCause:UnsupportedConstructs

This comes up as a common error in Parity Bench.

It is common to check for the None-ness of an object to determine next steps of calculation in a dynamic model. But this is not supported well in JIT today.

Error message:
```
compile,97,RuntimeError: Could not cast value of type __torch__.torch.nn.modules.instancenorm.InstanceNorm2d to bool:,"RuntimeError: 
Could not cast value of type __torch__.torch.nn.modules.instancenorm.InstanceNorm2d to bool:
  File ""/tmp/paritybench819sw5wj/pbzmu661cu.py"", line 41
    def forward(self, x):
        x = self.conv(self.pad(x))
        if self.norm:
           ~~~~~~~~~ <--- HERE
            x = self.norm(x)
        if self.activation:
```

Concrete [example](https://github.com/jansel/pytorch-jit-paritybench/blob/570400b612332ecaec0cf850cdc70a6d4ddc374b/generated/test_junyanz_VON.py#L685)


cc @suo @gmagogsfm
Repository: rust
Issue: LLVM unrolls loops fully, leading to non-linear compilation time
Labels: A-LLVM,P-medium,T-compiler,C-bug,I-hang,ICEBreaker-LLVM

<!--
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
#[derive(Copy, Clone)]
pub enum Foo {
    A,
    B(u8),
}

pub fn foo() -> Box<[[[Foo; 50]; 50]; 50]> {
    Box::new([[[Foo::A; 50]; 50]; 50])
}
```

I expected to see this happen:

```sh
cargo build --release
```

(Above command eventually should terminate)

Instead, this happened: Compiler doesn't terminate.

### 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.
-->

`rustc --version --verbose`:
```
rustc 1.44.1 (c7087fe00 2020-06-17)
rustc 1.46.0-nightly (346aec9b0 2020-07-11)
```

A crate with the repro can be found here: https://github.com/io12/llvm-rustc-bug-repro.

It seems like this is an LLVM bug.