sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: API: ring buffer of previous windows / tabs / buffers
Labels: enhancement,api

### Problem

i currently have two usecases need to get this value:
* `setloclist(prevwin)`
* `nvim_win_call(prevwin, nvim_win_set_config)`

for the first usecase, 0 can be used, and nvim will convert it to previous window internally.
but for the second, which is actually [a workaround for this issue](https://github.com/neovim/neovim/issues/24129), i have no appropriate way to get the handle of prevwin, and `nvim_win_set_config` indicates the cursor is currently in a floating window, i dont want to use `wincmd p` x2 here as sometime floatwins will just be closed when them lost focus. (well of course, i can store the previous window when opening the floatwin for later use)

### Expected behavior

so i want an lua api to get the handle of previous window directly.

--- updates
(sorry, i mixed up 'last window' and 'previous window' here)
Repository: storybook
Issue: [Bug]: 🐞🔥🐞 "Show Code" for stories written using CSF is not displaying arrow functions
Labels: bug,block: source

### Describe the bug

I have several components written using Component Story Format that contain arrow functions as prop values passed into the component. However, they are not being shown in the "Show Code" area in Storybook.

I know there is a workaround using JSX formatting to create a functional component instead of CSF and passing in docs.source.type: "code" into the component's parameters. However, I would prefer CSF formatting since it hides the "args" parameter and "{...args}" prop. I would prefer this since I'd like for users to copy the pure HTML or at the very least a functional component with no parameters that could break their code.

For example, I have the Link BasicUsage Story which is written in CSF as:
```
export const BasicUsage = {
  args: {},
  render: (args) => (
    <Link onClick={() => alert("basic link clicked")} {...args}>
      This is a basic link
    </Link>
  ),
};
```

However, in "Show Code" the onClick arrow function is empty:
![image](https://github.com/storybookjs/storybook/assets/75461349/c73ef23a-b74c-441c-84c5-3fc7dc549bcf)

If I write it using JSX like so:
```
export default {
  title: "Navigation/Link",
  component: Link,
  autodocs: "auto",
  tags: ["autodocs"],
  argTypes: {
    kind: {
      options: ["default", "red"],
      control: { type: "inline-radio" },
    },
    disabled: {
      control: { type: "boolean" },
    },
  },
  parameters: {
    docs: {
      source: {
        type: "code",
      },
    },
  },
};

export const BasicUsage = (args) => {
  return (
    <Link onClick={() => alert("basic link clicked")} {...args}>
      This is a basic link
    </Link>
  );
};
```

Then, the arrow function is being displayed but it also displays the "args" parameter and "{...args}" prop which I do not want:
![image](https://github.com/storybookjs/storybook/assets/75461349/d98becee-ffca-4066-ac4d-394b03d92696)

Overall, I'd like for the CSF formatting to allow for arrow functions to be displayed in the "Show Code" section like this:
```
<Link onClick={() => alert("basic link clicked")} >
      This is a basic link
</Link>
```

### To Reproduce

1. Create a story using CSF
2. Pass in an arrow function as a prop value to the component in the story
3. Run the Storybook, navigate to the component and click "Show Code"

It can also be viewed in Storybook 7 by clicking "Show Code" in the sample Button component provided by Storybook. The onClick prop's arrow function is empty.

### System

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Make Canvas.drawShadow work on multiple views
Labels: engine,P2,a: multi window,team-engine,triaged-engine

`Canvas.drawShadow` requires DPR to calculate shadow length, and currently it gets the DPR implicitly from the first window:
```cpp
// lib/ui/painting/canvas.cc
  SkScalar dpr = static_cast<float>(UIDartState::Current()
                                        ->platform_configuration()
                                        ->get_window(0)
                                        ->viewport_metrics()
                                        .device_pixel_ratio);
```

This is not compatible with multi-view, because in multi-view there might not be a window 0 if the platform disables implicit view. This DPR should come from the target view of this drawing command.

However, the `drawShadow` signature does not allow inserting a view ID or DPR anywhere. There's an `elevation` parameter, but it's a pre-DPR length. 
```cpp
  void drawShadow(Path path, Color color, double elevation, bool transparentOccluder);
```

To solve this in a non-breaking way, we can either 
* create a new `drawShadowWithDpr` that has an additional parameter `float dpr`, or 
* create a new `drawShadowOnView` that has an additional parameter `int viewId`.

Either way, we'll need to deprecate `drawShadow` afterwards.
Repository: pytorch
Issue: Use `isinstance` instead of `type` when checking for `torch.nn.Parameter`
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

From comment https://github.com/pytorch/pytorch/pull/104069?notification_referrer_id=NT_kwDOAhpHxbM2ODUxNzMzMDg5OjM1Mjc2NzQx#discussion_r1256262813

```
p = torch.nn.Parameter(t)
type(p) is torch.nn.Parameter
```

only works if `t` (the data passed to nn.Parameter) is a regular `torch.Tensor` and not a tensor subclass. However `isinstance(p, torch.nn.Parameter)` will work for both regular tensors and tensor subclasses. We should update all instances of type(t) is Parameter to be `isinstance(t, Parameter)` within PyTorch core.



### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr
Repository: vscode
Issue: Incorrect brackets color in JSDoc comments
Labels: help wanted,feature-request,editor-bracket-matching

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.80.0
- OS Version: Windows 10 22H2 19045.3086

Steps to Reproduce:

1. Change color of JSDoc comments' brackets in your theme file for scopes "punctuation.definition.bracket.curly.begin.jsdoc" and "punctuation.definition.bracket.curly.end.jsdoc".
2. Reload window or restart editor. And you'll see no difference. Brackets's color is the same as for all the code. Theme JSDoc color doesn't affect global color, and it looks ugly. 

3. If you inspect colors by "Inspect Editor Tokens And Scopes" function, you'll see that inspector show the right color, but editor shows the global color as at the screenshot. Comment's brackets' color must be the same as "string" and "object" words' color as I made them the same in my theme:
```
{
      "name": "JSDoc Instance and brackets",
      "scope": [
        "entity.name.type.instance.jsdoc",
        "punctuation.definition.bracket.curly.begin.jsdoc",
        "punctuation.definition.bracket.curly.end.jsdoc",
      ],
      "settings": {
        "foreground": "#8e4a91"
      }
}
```
![Screenshot](https://github.com/microsoft/vscode/assets/38814473/d65c650e-ea0b-4c73-bbaf-224ca1a3d581)
Repository: pytorch
Issue: [BE] Evaluate and improve eager for-loop optimizer memory perf
Labels: module: optimizer,triaged,better-engineering,actionable

We are not the most careful with using the least amount of memory in our for-loop implementations of our optimizers. For example, we have `max_exp_avg_sqs[i].copy_(torch.maximum(max_exp_avg_sqs_i, exp_avg_sq))` in adam.py which could be `torch.maximum(max_exp_avg_sqs_i, exp_avg_sq, out = max_exp_avg_sqs[i])` to save an allocation. Motivated by this comment: https://github.com/pytorch/pytorch/pull/104781#issuecomment-1625621945

This issue is to track the task of going through each of our for-loop (single_tensor) optimizers and ensuring that we are clean and minimal with our memory footprint.
- [ ] Adam
- [ ] AdamW
- [ ] Adagrad
- [ ] Adadelta
- [ ] Adamax
- [ ] NAdam
- [ ] RAdam
- [ ] ASGD
- [ ] SGD
- [ ] Rprop
- [ ] RMSprop
- [ ] LBFGS
- [ ] SparseAdam

cc @vincentqb @jbschlosser @albanD
Repository: vscode
Issue: Group Editor Accessibility Options
Labels: debt,editor-core

Currently there are
* EditorOptions.accessibilitySupport
* EditorOptions.accessibilityPageSize
* EditorOptions.ariaLabel
* EditorOptions.screenReaderAnnounceInlineSuggestion

And now also an option for the `aria-required` property.

I think they should be grouped into `EditorOptions.accessibility`
Repository: TypeScript
Issue: Error elaboration says nothing due to circularity
Labels: Suggestion,Help Wanted,Experience Enhancement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior.
  This should have the same code as the code snippet below, and use whichever settings are relevant to your report.

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?target=99#code/PTAEAEBcEMCcHMCmkBcpEGcB2iAekAoAvABwHtZJQBLLSRWAM2gGNFQAlRaAEzKwA2ATwDKJOBkQBBWLGhCAPABUAfKADeRUNtAYB1NgAoMMSgH40WAK4BbAEYMANOiw8Loa-YYBKNGInSsvLKKgDcBNoROogAbgyKIuj4iK4YoKqGUTo6JLCIPAbQ9GiGMdACVohoSs60PHiWtg6w3qAAvGplFezUaSKOWaC+oJAAFr00aVy8-ML+sJIycglhUYOMAkUAstAkCgCqKoYs5QJ2rADWJV2V1bWuDR5NPu1q+6AAPqB5M4JCoPsANoAXU+nG4fD+80WQUUh2GQOB4W0AF81qQKFRaPQmKx2NDAssQkl6Klwb85uIFoTgqoNGiCCx+CZQAB9aBoaaQykBJbBEywWjwNRtUCAgDk0HFSMZzKorLsfipMKJAqFIrFkuloSAA)

### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->
```ts
// @target: esnext

export interface ReadonlySparseArray<T> {

    slice(start?: number, end?: number): SparseArray<T>;
  
    every<S extends T>(
        predicate: (value: T, index: number) => value is S,
    ): this is ReadonlySparseArray<S>;
  
    flatMap<U>(callback: (value: T, index: number) => U | readonly U[] | ReadonlySparseArray<U>): U[];
  }
  
export interface SparseArray<T> extends ReadonlySparseArray<T> {}

const _a: ReadonlySparseArray<string> = ['a'];
const _b: SparseArray<string> = ['a'];
```

### 🙁 Actual behavior

`_b`:

```
Type 'string[]' is not assignable to type 'SparseArray<string>'.
  Types of property 'slice' are incompatible.
    Type '(start?: number | undefined, end?: number | undefined) => string[]' is not assignable to type '(start?: number | undefined, end?: number | undefined) => SparseArray<string>'.ts(2322)
```

In trying to tell you why `string[]` is not assignable to `SparseArray<string>`, the elaboration references two signatures which are identical except for their return types: `string[]` and `SparseArray<string>`, which lands you right back where you started.

This particular example occurs in #50351, which is a separately buggy behavior, so this repro may stop reproing if that gets fixed.
Repository: storybook
Issue: [Bug]: HMR does not work with Tailwind together with @storybook/builder-vite and Vite (preact)
Labels: bug,needs triage

### Describe the bug

HMR does only work for .stories files, eg. changing the label of a button will cause the preview to re-render.
But when you try to update a Tailwind class name in eg. a button component the HMR does not trigger the updated style.

### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: macOS 12.6.7
    CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
  Binaries:
    Node: 18.16.0 - ~/.asdf/installs/nodejs/18.16.0/bin/node
    Yarn: 1.22.19 - ~/Documents/dev/projects/ollebergkvist-turborepo/node_modules/.bin/yarn
    npm: 9.5.1 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.5.1
```


### Additional context

_No response_
Repository: terminal
Issue: SGR Blinking doesn't work in conjunction with Faint
Labels: Area-VT,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version

1.17.11461.0

### Windows build number

 10.0.19045.3086

### Other Software

_No response_

### Steps to reproduce

use ansi codes to render blinking faint text

### Expected Behavior

text blinks, but is fainter than non-faint blinking text

### Actual Behavior

text doesn't blink at all

see video

https://github.com/microsoft/terminal/assets/789591/177ec6c5-cbbe-4842-80a0-ae16a61f3ab9
Repository: flutter
Issue: [web] Parse browser Languages using Intl.Locale
Labels: engine,platform-web,P2,c: tech-debt,team-web,triaged-web

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

The current version of the web engine is doing some manual String parsing to convert `navigator.locales` into a `List<ui.Locale>` that Flutter can use.

However, the parsing is being done by hand:

* https://github.com/flutter/engine/blob/b39e6fe4b3bf98fdf20862c68177c2ed8a2785ec/lib/web_ui/lib/src/engine/platform_dispatcher.dart#L915-L922


### Proposal

The **parsing** of the locale should instead be done with the `Intl.Locale` Constructor:

* [MDN Intl.Locale constructor](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/Locale)

Once it is sufficiently supported:

* https://caniuse.com/mdn-javascript_builtins_intl_locale_locale (Safari 14+)
Repository: react-native
Issue: Transparent sectionListHeader is overlaped by renderItem (Updated RN)
Labels: Component: SectionList,Needs: Triage :mag:

### Description

Problem still persists after react native upgrade
When creating a SectionList component, if prop stickySectionHeadersEnabled=true, and it has no background, the child renderItem overlaps the header.
There seems to be no prop or logic that can resolve this problem.
So unfortunately, I must open this issue(or improvement)
[untitled.webm](https://github.com/facebook/react-native/assets/51801745/8813c5c6-1b43-4866-a587-e4b9e22c1318)


### React Native Version

0.72.1

### Output of `npx react-native info`

System:
  OS: Windows 10 10.0.22000
  CPU: "(12) x64 AMD Ryzen 5 5600X 6-Core Processor             "
  Memory: 7.40 GB / 15.89 GB
Binaries:
  Node:
    version: 16.15.1
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.19
    path: ~\AppData\Roaming\npm\yarn.CMD
  npm:
    version: 8.11.0
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-222.4459.24.2221.10121639
  Visual Studio: Not Found
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.1
    wanted: ^0.72.1
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

### Steps to reproduce

Simply create a SectionList with sticky headers and no background color

### Snack, code example, screenshot, or link to a repository

https://snack.expo.dev/@squidarrested/db76a1
Repository: create-react-app
Issue: CRA 5 upgrade
Labels: needs triage

Hi,

I recently upgraded react-scripts to v5, which added bunch of breaking changes, including to jest. My **useFakeTimers** no longer work. When I run my tests it stops running it throws the error "Exceeded timeout of 10000". If add timeout to longer time, my test just hangs. I tried to upgrade jest to 29 but now I am getting "ReferenceError: TextEncoder is not defined". Does anyone have similar issues? Seems breaking happens for jest27 just like documentation mentions? I tried to downgrade to previous jest version but my fakeTimers still not working. Can anyone help to figure it out?
Repository: flutter
Issue: cocoon dashboard for engine showing framework results
Labels: team-infra,P3,c: tech-debt,triaged-infra

There seems to be a block of results from framework runs showing up on the engine dashboard (https://flutter-dashboard.appspot.com/#/build?repo=engine&branch=main):

![image](https://github.com/flutter/flutter/assets/91688203/046d3994-58e8-4033-a51c-53cd8c74b1fd)
Repository: rust
Issue: transmute + tuple access + eq on `repr(simd)`'s inner value seems UB to valgrind
Labels: A-SIMD,C-bug,requires-nightly

I tried this code:

```rust
#![feature(repr_simd)]
use std::mem::transmute;

#[derive(Clone, Debug)]
#[repr(simd)]
struct CustomSimd<T, const LANES: usize>([T; LANES]);

fn main() {
    let mut input : CustomSimd<u8, 10> = CustomSimd([0u8; 10]);
    input.0[0] = u8::MAX;
    let data = unsafe { transmute::<_, CustomSimd<u8, 10>>(input).0 };
    assert_eq!(data, [u8::MAX, 0, 0, 0, 0, 0, 0, 0, 0, 0]);
}
```

I expected to see this happen: I expected this test to succeed since the destination type is the same as the source type.

Instead, this happened: This test fails. When running it with valgrind, I get errors such as:
```
Conditional jump or move depends on uninitialised value(s)
```

### 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.
-->

I used the playground version:
```
Nightly channel
Build using the Nightly version: 1.72.0-nightly
(2023-07-06 85bf07972a1041b9e253)
```
Repository: deno
Issue: [Bug] `callback` in `https.request().end(callback)` from `node:https` is never fired
Labels: bug,node compat,node API,node:http

Hello,

Here's a fire-and-forget HTTP request method that works on Node :

```js
import https from 'node:https';

const fireAndForget = ({
    url,
    method = 'GET',
    headers = {},
    data
}) => new Promise((resolve, reject) => {
    const
        _data = JSON.stringify(data),
        request = https.request(url, {
            method,
            headers: _data ? {
                ...headers,
                'Content-Type': 'application/json',
                'Content-Length': Buffer.byteLength(_data)
            } : headers
        });
    request.on('error', reject);
    if(_data)
        request.write(_data);
    request.end(resolve);
});
```

When running on Deno, the request is successfully sent, but the callback from `request.end` is never fired.

Thanks
Repository: go
Issue: x/telemetry/internal/counter: allow StackCounter to skip custom call depth
Labels: NeedsInvestigation,telemetry

Currently `StackCounter.Inc` captures the `Inc` caller's stack using `runtime.Callers(2, ...)`.
One use case we want to explore is to have a StackCounter to track calls to [`gopls/internal/bug.report`](https://cs.opensource.google/go/x/tools/+/refs/tags/gopls/v0.12.4:gopls/internal/bug/bug.go;l=66).

If we call `StackCounter.Inc` from this `report` function (wrapper of `StackCounter.Inc`), the first couple of entries are always the functions in this `gopls/internal/bug` package, which isn't very interesting while taking up a good fraction of the counter name which already has pretty small max limit (https://github.com/golang/go/issues/61181). 

Can we allow the api to configure custom skip depth like `runtime.Callers` or `log.Logger.Output`?

Or alternatively, can we have `StackCounter.Inc` take `pcs` ?

cc @golang/tools-team @rsc
Repository: next.js
Issue: Templates don't rerender when using route groups
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.13.0
      npm: 8.13.2
      Yarn: 1.22.19
      pnpm: 8.6.6
    Relevant Packages:
      next: 13.4.10-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/tom-sherman/nextjs-template-route-group-bug

### To Reproduce

1. Add a template in the same route as a route group
2. Navigate between pages in the group

### Describe the Bug

Template should rerender. In the linked reproduction, we should see new random numbers rendered to the screen when navigating between A & B using the links.

### Expected Behavior

Template doesn't rerender. Numbers don't change on navigation between A & B

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: Alert when task pending time is greater than SLO
Labels: team-infra,P2,triaged-infra

We have SLO for task pending time on different platforms.
Example: 5 mins (90th%) for linux/windows VMs and 10 mins (90th%) for Mac host only bots.

It is not uncommon when the pending time increases to >1h for a short time. This happens when
1) release branch commits land
2) bot capacity drops due to unhealthy bots
3) github incidents which caused PRs accumulating and a large number of presubmit targets triggered in a short time
4) codes regression which caused steps/builds timing out
5) dependencies like gradle, xcode issues

It would be useful for gardeners to triage if we have such alerts when tree is red. Some alerting metrics could be
1) max_pending_time
2) number_of_pending_tasks with pending time > 30mins

These metrics should be pool/os specific.
Repository: flutter
Issue: `examples/layers/widgetsspinning_mixed.dart` is busted
Labels: d: examples,P3,team-framework,triaged-framework

On problem is that because the sample never calls `WidgetsBinding.attachRootWidget` the binding never enables frame production because `_readyToProduceFrames` is never set to true:

https://github.com/flutter/flutter/blob/2b6492426e5c9a17f3597f40323ce902d4540396/packages/flutter/lib/src/widgets/binding.dart#L994-L996

Another problem is that the usage of a persistentFrameCallback dirties the render tree at the end of every frame so hit testing between frames always fails. Maybe it should be using a transient callback instead to for updating the render tree?