sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Twisties appear only after the view has loaded for the view
Labels: bug,file-explorer,polish

@sandy081 @isidorn seeing something similar also in the explorer, check how the twistie only appears later:


https://user-images.githubusercontent.com/900690/106712642-88201c80-65f9-11eb-879c-49cec53961e6.mov

I am feel this was not the case before.

_Originally posted by @bpasero in https://github.com/microsoft/vscode/issues/115585#issuecomment-772297308_
Repository: rust
Issue: Methods of core trait that have doc aliases are found twice
Labels: T-rustdoc,C-bug,A-cross-crate-reexports,A-doc-alias

If you search for a method in `core` trait that has an alias it appears twice on the list.

For example:

https://doc.rust-lang.org/nightly/std/?search=length

This shows `core::iter::ExactSizeIterator::len` twice.

![image](https://user-images.githubusercontent.com/1297598/106718144-ebfa1380-6600-11eb-931e-196b955cd73f.png)

This issue is also shown by https://doc.rust-lang.org/nightly/std/?search=reduce.
Repository: svelte
Issue: Transition delay is cached and does not apply until after the next run
Labels: temp-stale

**Describe the bug**
After a transition has already been triggered, changing the delay of a transition does not take effect until after the transition has been triggered at least once.

**To Reproduce**
REPL: https://svelte.dev/repl/48114260160b40d7bcb2f0d2dc148eb6?version=3.38.3

1. Click `Menu` several times to toggle the default transition.
**IMPORTANT:** The bug requires triggering the transition at least once before the delay is cached.
2. Click `Set Delay to 1s`, the `delay` variable is now set to `1000`.
3. Click `Menu` to toggle the transition, delay has not taken effect.
4. Click `Menu` to toggle the transition, delay now takes effect.
5. Click `Set Delay to 0`, the `delay` variable is now set to `0`.
6. Click `Menu` to toggle the transition, 1s delay still applies.
7. Click `Menu` to toggle the transition, delay is now updated.

**Expected behavior**
I expect the delay to apply immediately, or at least applied after I do `await tick()`.

**Information about your Svelte project:**
Svelte: 3.32.1, 3.38.3
Tested Browsers:
- Edge: Chromium (88.0.705.50)
- Chrome: 88.0.4324.104
- Firefox Dev: 86.0b5 (64-bit)

**Severity**
Low
Repository: neovim
Issue: Recursive macro guard without triggering an error
Labels: enhancement

- `nvim --version`: NVIM v0.4.4

When doing recursive macros, you need a guard condition to exit the macro repetition. I usually create a guard by either failing search or checking I can't move the cursor further because of the end of the line/file, which triggers an error and therefore stops the execution. This however, forbids nested recursive macro execution.

An example:
Macro №1: open a file at current line (from a file list) in a new tab, execute recursive macro №2, call macro №1.
Macro №2: search for a pattern (recursion guard condition, which causes an error), fix it, call macro №2.

#### Possible fix 
A possible fix I can think of right now would be creating a normal mode prefix command that would stop the last macro's execution without triggering an error, but this would require a stack for the macro execution, which I'm not sure is present.

E.g. if `mg` would be the macro guard prefix, which would only stop last, not all macro execution, then `mg/pattern` would stop only the last macro upon a failing search.

### Actual behaviour

Macro №1 never recurses, because the guard of macro №2 stops all execution.

### Expected behaviour

Macro №1 recurses until its own guard triggers.
Repository: ant-design
Issue: Scrollbar on top on tables or both
Labels: 💡 Feature Request,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
Our users would like to have the scrollbar on top of the tabel or both if possible, to make it easeier to work with large tables.

Is it possible to do today as a workaround or does it requires new feature? 

### What does the proposed API look like?
NA


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: cmd/link: support c-archive for freebsd/arm and freebsd/arm64
Labels: OS-FreeBSD,NeedsInvestigation,FeatureRequest

This is a request. The buildmode `c-archive` is not supported on `freebsd/arm` and `freebsd/arm64` yet (go1.16-beta)

https://github.com/golang/go/blob/cb84d831c956026f477b52c9f8a7c1ed2b2724ad/src/cmd/link/internal/ld/config.go#L57-L75
Repository: neovim
Issue: swap arbitrary windows
Labels: enhancement,jumps-navigation,editor

https://github.com/neovim/neovim/blob/cc1851c9fdd6d777338bea2272d2a02c8baa0fb1/runtime/doc/windows.txt#L457

It would be nice to have this feature to move windows more freely, while preserving their id, options, variables and other window-local properties.

 1. Allow using `[N]CTRL-W_x` with any window number (now only works with the windows in the same row/column).
 2. Create a function that swaps the position (winnr and tabpage) of two windows by their `window-ID`s (or cycles, if more than 2 ids are provided).
Repository: material-ui
Issue: [dialog] Add imperative methods to display them directly
Labels: new feature,waiting for 👍,component: dialog

Refer to the call and implementation of the `ant-design` dialog box. This solution brings more flexibility and concise code.


Will there be such a solution?
```jsx
import { Dialog } from "@material-ui/core";

Dialog.show({
  type: "info",
  title:  "Message",
  content: "Hello",
  onOk: () => { ... }
});
```

## Benchmark

- https://ant.design/components/modal/#components-modal-demo-hooks
- http://bootboxjs.com/
- https://dev.to/dmtrkovalenko/the-neatest-way-to-handle-alert-dialogs-in-react-1aoe
Repository: godot
Issue: Random visual artifacts with blend shapes on AMD graphics cards (GLES3)
Labels: bug,topic:rendering,confirmed,topic:thirdparty,topic:3d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3 Stable Mono Official


**OS/device including version:**
OS: Manjaro Linux x86_64 
Kernel: 5.9.16-1-MANJARO
CPU: AMD Ryzen 7 1700X (16) @ 3.400GHz
GPU: AMD ATI Radeon RX 5600 XT
Backend: GLES3


**Issue description:**
![image](https://user-images.githubusercontent.com/15730577/106767781-22e91d00-6633-11eb-9160-6ef44ffbcd84.png)

When applying blend shapes, the model accumulates graphical artefacts in the form of distended polygons reaching out from the face. As the render updates, so too does the direction of the polygons. Moving the camera around also causes the artefacts to change shape in a seemingly random manner.

The issue becomes progressively more noticeable as more blend shapes are applied.

To confirm that the model was not the problem, it has been opened in the following game engines and hardware:

  * Windows under Unreal Engine 4 using the same graphics card as the problem hardware configuration.

  * Windows under Unity 2019 and Godot 3.2 using a Nvidia graphics card.

  * Windows under Godot 3.2 using the same graphics card as the problem hardware configuration.

With the above configurations, no problems rendering the model occur. Additionally, the model was exported as GLB, GLTF, and FBX. I have concluded that the file format does not play a role, as they all behaved identically on the hardware tested.

The issue also persists when the game is running, which leads me to believe this is an AMD Linux-specific renderer bug or file format-wide importing bug.

This issue has also been fixed in `master` branch.


**Steps to reproduce:**
Open up the minimal reproduction project and tweak the blend shape sliders in the scene-local instance of the model within Main.tscn.


**Minimal reproduction project:**
[BlendShapes.zip](https://github.com/godotengine/godot/files/5919432/BlendShapes.zip)
Repository: node
Issue: asyncLocalStorage returns undefined if the request body is not empty (post, patch ...)
Labels: async_hooks


node v14.6.0

### Additional information

returns undefined if the request body is not empty (post, patch ...)
when using async localStorage. run ()
but when using async localStorage.enter With() everything works fine
Repository: godot
Issue: C# - Using await toSignal() in exported builds causes crash!
Labels: bug,topic:dotnet,crash

**Godot version:**
3.2.4 beta 6 mono


**OS/device including version:**
Windows 10 x64
OSX catalina

**Issue description:**
When using `await ToSignal()` the game crashes when exported!


**Steps to reproduce:**
* Create a mono project
* call await ToSignal()
* Export

PS: Uncheck "Export with Debug", in case its enabled no error occurs.

**Minimal reproduction project:**
[test.zip](https://github.com/godotengine/godot/files/5919939/test.zip)


**Extra Files:**

Here's the log from OSX: (from another project)
[log (1).zip](https://github.com/godotengine/godot/files/5919816/log.1.zip)

Windows Build:
https://drive.google.com/file/d/1DO2BY289YUhntIyPv0JGtmVp5I9Av7f9/view?usp=sharing

OSX Build:
https://drive.google.com/file/d/10rV4UbFaKdGQ5DnkI536n2NzRpTkVr7-/view?usp=sharing
Repository: deno
Issue: Custom precision on timers in JS
Labels: cli,suggestion

Hello, I am in the process of building a custom lambda platform for my master thesis.

deno and v8 seems to be a perfect candidate for the application level sandbox (good job btw 👍 ).

As far as I know the greater the precision of the timers the faster you can do a Spectre style attack. I see the hp timers are guarded by a flag, but some applications (such as mine) would like to trade precision for an increased degree a security (preferably configurable).

When I say timers I am referring of course to the setInterval/setTimeout and Date.now API.

1. Do you think this is necessary?
2. Would you be open to adding this as a configuration flag (I would be more then happy to make a PR)?

This is even more important if you extend deno with more native code from Rust, or plan to run multiple Isolates in the same process, such as I do (as far as I know, no other problems except security and process crashes can occur here).
Repository: pytorch
Issue: Segmentation Fault: Garbage collector, cuda memory
Labels: module: cuda,triaged

## 🐛 Bug

This bug the result of strange behavior between the garbage collector and checking memory allocated on a specific device.

## To Reproduce

Steps to reproduce the behavior:
```
import torch
import gc

assert torch.cuda.is_available()

gc.collect()
torch.cuda.memory_allocated(0)
```

`Segmentation fault (core dumped)` or if you run it in a notebook your kernel will simply die.

What's really interesting is there's a lot of ways to avoid this error, if you've put anything on cuda than you'll be fine or if you run `torch.cuda.memory_allocated()` first and then `torch.cuda.memory_allocated(0)` then you won't get it either.

cc @ngimel
Repository: rust
Issue: rustdoc: rename doctest imports on re-exported items
Labels: T-rustdoc,E-hard,C-feature-request,A-doctests

Currently, a crate can re-export item(s) from it's dependencies with inline documentation:
```rust
// hyperium/http

/// ```
/// use http::Request;
/// let req = Request::new();
/// ```
pub struct Request;
```
```rust
// hyperium/hyper

#[doc(inline)]
pub use http::{Response, Request};
```

However, documentation tests still display imports from the original crate, meaning if someone goes to the documentation for `hyper::Request`, they will see it being imported from a different crate:
```rust
// docs.rs/hyper/struct.Request.html

use http::Request;
let req = Request::new();
```

This is potentially confusing for users. This issue proposes renaming doctest imports on re-exported items:
```rust
// docs.rs/hyper/struct.Request.html

use hyper::Request;
let req = Request::new();
```

There may also be a way to disable this functionality:
```rust
#[doc(inline, rename = false)]
pub use http::{Response, Request};
```
Repository: flutter
Issue: podhelper uses Ruby 2.5 syntax "Dir.each_child", minimum required is Ruby 2.0
Labels: platform-ios,tool,P3,team-ios,triaged-ios

@ReniDelonzek reported in https://github.com/flutter/flutter/issues/72737#issuecomment-752162231

> the function `Dir.new (configuration_engine_dir).each_child` that is inside the file podhelper.rb was introduced only in ruby ​​2.5, while the version of it on my machine for example is still in 2.0

https://github.com/flutter/flutter/blob/f63055a895b337afd81672cc1ae4499e6aa06a3f/packages/flutter_tools/bin/podhelper.rb#L54

Flutter's Ruby scripts should not use APIs introduced after Ruby 2.0.
Repository: TypeScript
Issue: Opened file added to inferred project instead of configured project
Labels: Needs Investigation,Rescheduled

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

inferredproject
inferredproject1

### 🕗 Version & Regression Information

Observed in 4.1.4 and 3.1.2.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
N/A

### 💻 Repro steps

<!-- Please post the relevant code sample here as well-->
Opened project in VS with tsconfig, observed a configured project being created successfully with one TS root file.
Then added another TS file to the project.

### 🙁 Actual behavior

New TS file was added to the inferred project.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
New TS file is added to the existing configured project.

### Notes:
This issue reproduces inconsistently.

TS 4.1.4 Repro: [tsslog-ConfiguredProject-2021_01_29-09_25_06.07_PM_UTC.ProjectHost.log](https://github.com/microsoft/TypeScript/files/5920737/tsslog-ConfiguredProject-2021_01_29-09_25_06.07_PM_UTC.ProjectHost.log)

TS 3.1.2 Repro: [tsslog-ConfiguredProject-2021_02_03-02_38_00.40_AM_UTC.ProjectHost.log](https://github.com/microsoft/TypeScript/files/5920739/tsslog-ConfiguredProject-2021_02_03-02_38_00.40_AM_UTC.ProjectHost.log)
Repository: excalidraw
Issue: Redirect non existing URL to the root
Labels: enhancement,good first issue

### Examples (broken state)

- https://excalidraw.com/asdf/qwer/
- https://excalidraw.com/test/

### These should stay :)

- https://excalidraw.com/version.json
- https://excalidraw.com/favicon.ico
- etc


### If there is hash maybe we should keep it.. 

https://excalidraw.com/foo/#json=5056763892072448,dS7ZRiP8pj51lM6Qa7CRmA should redirect to https://excalidraw.com/#json=5056763892072448,dS7ZRiP8pj51lM6Qa7CRmA
Repository: flutter
Issue: Clang roll failing missing atomic symbols for android aarch64
Labels: engine,P2,team-engine,triaged-engine

PR: https://github.com/flutter/engine/pull/24155/

CI: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8856359195166542912/+/steps/build_android_profile_arm64/0/stdout

Example error logs:

```
ld.lld: error: undefined symbol: __aarch64_cas8_acq_rel
>>> referenced by atomic:992 (../../third_party/libcxx/include/atomic:992)
>>>               obj/third_party/skia/src/utils/skia.SkEventTracer.o:(bool std::__1::__cxx_atomic_compare_exchange_strong<SkEventTracer*>(std::__1::__cxx_atomic_base_impl<SkEventTracer*>*, SkEventTracer**, SkEventTracer*, std::__1::memory_order, std::__1::memory_order))
>>> referenced by atomic_support.h:100 (../../third_party/libcxx/src/include/atomic_support.h:100)
>>>               obj/third_party/libcxx/src/libcxx.memory.o:(std::__1::__shared_weak_count::lock())
>>> referenced by hb-atomic.hh:72 (../../third_party/harfbuzz/src/hb-atomic.hh:72)
>>>               obj/third_party/harfbuzz/src/harfbuzz_sources.hb-aat-layout.o:(hb_lazy_loader_t<AAT::morx, hb_table_lazy_loader_t<AAT::morx, 25u>, hb_face_t, 25u, hb_blob_t>::get_stored() const)
>>> referenced 38 more times
```

FYI @dnfield , @chinmaygarde
Repository: rust
Issue: #[rustc_inherit_overflow_checks] should be documented instead of replaced with e.g. Add::add calls.
Labels: A-docs,T-libs

(*Note: this was originally posted as a comment on #62429 - also cc #35310 but not sure how relevant*)

In https://github.com/rust-lang/rust/pull/62429#discussion_r300818237 @scottmcm said:
> Might be worth double-checking there's a test for overflow checks here?  I'm never confident in what `rustc_inherit_overflow_checks` does.  (And I hear that one can use `Add::add(count, 1)` instead of using the attribute.)

While adding more tests is better, I don't agree with removing the attribute. If anything the attribute should be better documented, but relying on more implicit mechanisms that internally use the attribute obscures the fact that something *unusual* is happening.
(i.e. that some of the behavior isn't decided by the crate being compiled, but by a downstream using crate)

The reason `Add::add` works at all is because the attribute is used in the `impl`s` for the integer types, e.g.:
https://github.com/rust-lang/rust/blob/186f7ae5b04d31d8ccd1746ac63cdf1ab4bc2354/library/core/src/ops/arith.rs#L92-L107

There's nothing magical about it being a trait call, you're just calling another function with `#[rustc_inherit_overflow_checks]` on it, instead of using `#[rustc_inherit_overflow_checks]` yourself, and relying on generic/`#[inline]` instantiation to get the behavior.

The only reason the trait impls have the attribute is because of things generic over those traits, not to call directly.

**EDIT**: see also documentation issue by @m-ou-se at https://github.com/rust-lang/std-dev-guide/issues/13
Repository: PowerToys
Issue: [FancyZones] Restore Original Size when Unsnapping - UNLESS I resize it while it is Snapped
Labels: Idea-Enhancement,Product-FancyZones,Planning-Consideration

## 📝 Do NOT restore original window size if it has been re-sized while snapped
The new feature would just add a condition to the option known as "Restore the original size of windows when unsnapping". 
New Condition:
If the User "Re-sizes" the window while it is in the "Snapped" state, then it would NOT restore the original size if we move it out of the snapped state.

(In fact, I was surprised that Re-Sizing a Snapped window does not automatically mark the window as being UnSnapped)

---
_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_
### Free Floating Zones
Because Snapping Zones can be "Free-Floating" anywhere on the desktop, and do not prevent me from Re-Sizing my window, I often forget that a window is snapped, and I may re-size the window before moving it somewhere else.

If I Re-Size a window, it is probably safe to assume that the NEW size I just changed it to is the size that I want it to be, so after re-sizing and then immediately moving the window it can be a nuisance if the window gets Auto-Resized AGAIN

Obviously I could disabled the "restore size" Option, but then I couldn't use it when I need it : (

### Full Size Zones
For zones that extend from one end of the screen to the other, I like to have the "restore size" option on in case I need to move the window (usually so that it automatically gets smaller rather than blocking the whole screen)

### Summary
So if I have a combination of "Floating Zones" and "Full Zones" the "restore size" option kind of conflicts with my Use cases, UNLESS there was a condition that prevented it from restoring the size if I have already Re-Sized the window before moving it.

Thanks! 
---
👍 👍 👍 👍
Repository: next.js
Issue: Overwritten Cache-Control headers should include public directive
Labels: bug

**What version of Next.js are you using?**

10.0.7-canary.3

**What version of Node.js are you using?**

15.7.0

**What browser are you using?**

Chrome, Safari, curl

**What operating system are you using?**

macOS

**How are you deploying your application?**

next build, next start

**Describe the Bug**

Cache-Control headers are overwritten to be: `Cache-Control: s-maxage=31536000, stale-while-revalidate`. This header should include the `public` directive so that CDNs will cache the response.

As an aside, headers are not overwritten consistently. If I have the following config:

```js
// next.config.js

module.exports = {
  async headers() {
    const headers = [
      {
        headers: [
          {
            key: "Cache-Control",
            value:
              "public, max-age=3600, s-maxage=60, stale-while-revalidate=86400",
          },
        ],
        source: "/:path*",
      },
    ];
    return headers;
  },
};
```

Making a request to `/` will return the header: `Cache-Control: s-maxage=31536000, stale-while-revalidate` but making a request to `/posts/first-post` returns the header `Cache-Control: public, max-age=3600, s-maxage=60, stale-while-revalidate=86400`.

**Expected Behavior**

The headers should be overwritten consistently across all pages. The overwritten headers should include the `public` directive.

**To Reproduce**

1. Clone https://github.com/nrempel/repro-cache-control-headers
2. npm build && npm start
3. Visit / and look at headers
4. Visit /posts/first-post and look at headers
Repository: pytorch
Issue: [JIT/Futures] Future callbacks/then() APIs should throw the correct exception
Labels: oncall: jit,module: bootcamp,days

## Future callbacks/then() APIs should throw the correct exception

If a future is completed with an error and callbacks are invoked, any exceptions in the callback are caught and a `RuntimeError` with the exception information is raised instead: 
https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/python/pybind_utils.h#L136

We should instead preserve the original exception type so that it can be caught and handled appropriately by the user in python. 

cc @gmagogsfm
Repository: react-native
Issue: Android: Enabled services
Labels: Good first issue,Platform: Android,Accessibility,Accessibility Team - Evaluated

## Description
Similar to issue #30864 and heavily intertwined with #30863, it is sometimes useful to query what accessibility services a user has currently enabled. This would allow your to tailor your app's UI to the specific service. For example, if a user has the "Talkback" screen reader service enabled, you probably don't want videos to auto-play, as the audio would be interruptive to the screen readers announcements, and if auto-played without audio the videos would be playing and taking bandwidth without the user likely  realizing this was happening.

Right now, there *is* a method in the AccessibilityInfo API to detect talkback specifically (isScreenReaderEnabled), but there is not a general purpose method to get a list of all enabled services.

## React Native version:
v0.63

## Expected Behavior
The AccessibilityInfo API should have some general purpose method to get a list of all enabled services.

## Android Details
This functionality is available in the AccessibilityManager class via the getEnabledAccessibilityServiceList method.
https://developer.android.com/reference/android/view/accessibility/AccessibilityManager#getEnabledAccessibilityServiceList(int)