sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [flutter_adaptive_scaffold] documentation clarification about nested scaffolds
Labels: d: api docs,package,team-ecosystem,P3,p: flutter_adaptive_scaffold,triaged-ecosystem

### 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

AdaptiveScaffold is useful for displaying a collection of elemens in one panel (like a ListView) and the opened element in the other panel.

I'd like to achive follwing layout as defined in M3

<img width="2048" alt="ld4wxkhh-3p_whats new_2x" src="https://user-images.githubusercontent.com/25266387/236845657-35e85e5c-393e-4eca-bd57-ef1644bfd082.png">

In that screen both panels have their own `AppBar` and a `FloatingActionButton` is used to create new items.

According to the `Scaffold` docs nesting them is discuraged.

>Nested Scaffolds
>
>The Scaffold is designed to be a top level container for a MaterialApp. This means that adding a Scaffold to each route on a Material app will provide the app with Material's basic visual layout structure.
>
>It is typically not necessary to nest Scaffolds. For example, in a tabbed UI, where the bottomNavigationBar is a TabBar and the body is a TabBarView, you might be tempted to make each tab bar view a scaffold with a differently titled AppBar. Rather, it would be better to add a listener to the TabController that updates the AppBar

But that's the only way of doing this layout.

### Proposal

Either support FABs or adjust the documentation that nesting Scaffolds is not an issue in this case (if it isn't. I don't really know).

While doing a custom SplitAppBar is not that that straight forward  it's possible contrary to the FAB.
Repository: vscode
Issue: Cannot see the diff anymore in the Light Modern theme
Labels: bug,themes,accessibility

Type: <b>Feature Request</b>

I've setup the new Light Modern theme and wanted to see the changes I've made via a diff. But since I'm colorblind, I cannot see the difference anymore between the old (reds) and new (greens). Can you maybe adjust the colors a bit so I - and other people that are colorblind - are able again to see the diffs. Thanks! :)

VS Code version: Code 1.78.1 (6a995c4f4cc2ced6e3237749973982e751cb0bf9, 2023-05-04T09:48:08.683Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes


<!-- generated by issue reporter -->
Repository: next.js
Issue: Images are loaded based on bandwidth
Labels: bug,Image (next/image)

### 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: x64
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
    Relevant packages:
      next: 13.4.1
      eslint-config-next: 13.0.3
      react: 18.2.0
      react-dom: 18.2.0
```


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

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/youthful-leftpad-edrrez

### To Reproduce

Open Developer tools on Network tab and you can see which images are loaded on first load.

### Describe the Bug

Test loading the site with the normal connection and the images are loaded one at a time and the lazy loading works fine.

<img width="807" alt="image" src="https://github.com/vercel/next.js/assets/36002130/5a7bdff2-a598-45f1-afe2-528e0616eb74" />

While if we do a test in "Slow 3G" we can see that on the first loading the images are all loaded and therefore the lazy loading is not working.

<img width="804" alt="image" src="https://github.com/vercel/next.js/assets/36002130/f8f34151-2cb6-40b4-99c1-277b1f8a81ed" />


### Expected Behavior

What I expect is that the images are loaded respecting the lazy loading principle. More in case the connection is lower, Instead in this case the opposite happens and when the connection is lower more images are loaded.

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

_No response_

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

_No response_
Repository: next.js
Issue: Translations not showing on Next Link click using 'en' locale (i18next loses instance) only on Vercel
Labels: bug,Runtime

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
Binaries:
      Node: 18.8.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
Relevant packages:
      next: 13.4.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


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

Internationalization (i18n), Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/miguel-sg-dev/next-app

### To Reproduce

Go to https://next-app-delta-azure.vercel.app/en and click on the FAQ link. The new page does not load the translations

### Describe the Bug

When I'm on the **en** locale (https://next-app-delta-azure.vercel.app/en) and click on the FAQ link, it should load the faq page with the translated title but instead it shows the key "faq.title".

The only message I get in the console after I click on the link is this warning:
![image](https://github.com/vercel/next.js/assets/125872328/bf3b11d9-e4db-4cf6-8547-f5726d176f8d)

Couldn't try on canary version because it conflicts with the next-i18next dependency.

This issue just happens on Vercel. When I run the build and start the production server locally it works fine.

### Expected Behavior

When clicking on the Link, the page should load with the translations, as it does when you click from https://next-app-delta-azure.vercel.app/ or https://next-app-delta-azure.vercel.app/es

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

_No response_

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

Vercel
Repository: godot
Issue: Frame Selection (2D) / Focus Selection (3D) shortcut doesn't work reliably when focusing Scene tree (and if shortcut is a letter, selects node starting with that letter instead)
Labels: discussion,topic:editor,usability

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Linux Ubuntu 22.04 with Unity desktop

### Issue description

Moved from https://github.com/godotengine/godot-proposals/discussions/6853

Most of the time, when I use the 2D Frame Selection shortcut F (or Shift+F, apparently the new default) or 3D Focus Selection F, I have just selected the node in the Scene tree (otherwise I would already have it in scene view), so the Scene tree is focused. Pressing the shortcut at that moment will fail to focus on selection. If the shortcut is one letter (optionally with Shift), the Scene tree panel will focus the next node whose name starts with that letter (e.g. Floor) instead.

Inconsistency:
- sometimes, esp. after repeating letter presses, it would stop searching nodes by name
- sometimes, mapping Focus to another shortcut like F4 or Ctrl+Alt+F can help working more reliably even when Scene tree is focused; but not always (it worked yesterday, not today)

To make Focus truly work, you must click on the Scene view first, then use the shortcut, but it's cumbersome.

I think we should give priority to any meaningful shortcut when Scene tree is focused. The only feature we'd "lose" is if the user _really_ wants to search for a node whose name starts with F. But I suppose the default for 2D was switched to Shift+F precisely to distinguish the two use cases (and reversely, a user could decide to revert it to F as it's the most common operation, and only press "Shift+F" to search for a node whose name starts with F).

I suppose this could then be documented somewhere.

Also, if we really want to support first letter searching we should fix the bug that blocks it sometimes, to make it work reliably.

### Steps to reproduce

1. Create a scene with nodes with various names, some starting with F like "Floor", and at different positions, in 2D and/or 3D
2. Move the scene view away
3. Verify your current shortcut for Frame Selection (2D) / Focus Selection (3D): it should be F or Shift+F (you can try other letters too, or even F4).
4. Select a node and press the corresponding shortcut for the dimension (below, we assume the shortcut is F to simplify)
=> the nodes whose name start with F are selected
5. Press F more times => selection iterates over more nodes whose name start with F, but does not focus
6. Try various letters and press them multiple times => it may select nodes based on their names, but sometimes the selection just fails and nothing happens
7. Focus the scene view and press F => this time, the view frames / focus on the selected node or group of nodes
8. Repeat 4-7 with various shortcuts, letters or not

### Minimal reproduction project

N/A
Repository: storybook
Issue: [Bug]: Storybook.js installation is not working in angular
Labels: question / support,cli,angular,windows

### Describe the bug

TypeError: Cannot read properties of undefined (reading 'stack')
    at installStorybook (C:\Users\gantala\Documents\Angular\nefco-extranet\node_modules\@storybook\cli\dist\generate.js:354:39)
    at async doInitiate (C:\Users\gantala\Documents\Angular\nefco-extranet\node_modules\@storybook\cli\dist\generate.js:359:125)
    at async withTelemetry (C:\Users\gantala\Documents\Angular\nefco-extranet\node_modules\@storybook\core-server\dist\index.js:35:3422)
    at async initiate (C:\Users\gantala\Documents\Angular\nefco-extranet\node_modules\@storybook\cli\dist\generate.js:370:109)

### To Reproduce

Simple storybook.js steps are not working. I have windows 11 system

I tried by running these commands but still its throwing the same error

npm install @storybook/angular --save-dev
npm install babel-loader @babel/core --save-dev
npx storybook@latest init
npm run storybook

### System

_No response_

### Additional context

_No response_
Repository: puppeteer
Issue: [Feature]: allow configuring the output of @puppeteer/browsers install
Labels: feature,good first issue,@puppeteer/browsers

### Feature description

Sometimes one only needs the browser spec or the executable path so there should be a flag to configure that. cc @mathiasbynens
Repository: next.js
Issue: Typescript impot alias `!/*` doesn't work
Labels: bug,TypeScript

### 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.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.6.0
      npm: 8.13.2
      Yarn: 1.22.19
      pnpm: 8.4.0
    Relevant packages:
      next: 13.4.2-canary.5
      eslint-config-next: 13.4.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


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

TypeScript (plugin, built-in types)

### Link to the code that reproduces this issue

https://github.com/oscartbeaumont/next-tsconfig-bug

### To Reproduce

Run `pnpm build` on the repository linked above or, `pnpm create next-app` and answer yes to change `Would you like to customize the default import alias` then set it to `!/*` in the next prompt.

Changing the `!` to `@` in the `pages/index.tsx` and `tsconfig.json` will cause it to start working so I don't think this is an issue with my tsconfig setup.

### Describe the Bug

When doing `next build` or `next dev` it fails to resolve the files with this alias.

<img width="588" alt="image" src="https://github.com/vercel/next.js/assets/21004798/9df80c81-b1ef-4558-9706-8bd450cc3e5b">


### Expected Behavior

I would expect `!/*` to be a valid import alias.

I have been using it on another project that isn't built on Next.js so I don't think this is a Typescript issue.

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

_No response_

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

_No response_
Repository: PowerToys
Issue: Disable Dead keys
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage,Resolution-Built into Windows

### Description of the new feature / enhancement

It would be nice if  the Keyboard manager had the option to disable all Dead keys. 

### Scenario when this would be used?

Layout that don´t need to make diacritical characters like German or the US layout.  

### Supporting information

_No response_
Repository: angular
Issue: Allow angular elements to support extends feature of customElements.define
Labels: area: elements

### Which @angular/* package(s) are relevant/related to the feature request?

elements

### Description

Today we can convert angular component into WebComponent using `createCustomElement` API from `@angular/elements`
However this only creates WebComponent extending `HTMLElement` interface internally.

WebComponent specification also allows us to create WebComponent by extending specific HTMLElement (https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/is). 

e.g
```ts
class MyWebComponent extends HTMLParagraphElement {}
```
Angular's `createCustomElement` should also provide a way to do similar.

This will allow developers to use angular component as a webcomponent in following manner as well.
`<p is="my-angular-webcomponent"></p>`






### Proposed solution

add another generic type with `createCustomElement<P, T>` which can be used to extend the WebComponent class.

```ts
export abstract class NgElement<P> extends P {
}
```

### Alternatives considered

Currently there is no alternate to this problem
Repository: vscode
Issue: Allow to target a setting in a workspace file to one of the roots
Labels: feature-request,config,workbench-multiroot,keep


> I had discussions about this with others from the team in the past, even in the context of https://github.com/microsoft/vscode/issues/45177 and I think what is missing is some variable you can use as part of the glob pattern to point to one of the entries in the workspace file. If someone has good ideas how to do that, we can have a discussion in a separate issue.

_Originally posted by @bpasero in https://github.com/microsoft/vscode/issues/4873#issuecomment-1543953520_

A previous suggestion from @roblourens is at https://github.com/microsoft/vscode/issues/70438#issuecomment-739003804

This aligns with the existing feature for scoping variables per workspace folder:

https://code.visualstudio.com/docs/editor/variables-reference#_variables-scoped-per-workspace-folder
Repository: rust
Issue: Tracking Issue for `cfg(overflow_checks)`
Labels: C-tracking-issue

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

The feature gate for the issue is `#![feature(cfg_overflow_checks)]`.

It allows write code that detects if compiler emits code for integer overflow checks similarly to how `cfg(debug_assertions)` allow to detect if debug assertions enabled.

Example:

```rust
#[cfg(overflow_checks)]
#[track_caller]
fn cast(v: i64)->u32{
    v.try_into().unwrap()
}

#[cfg(not(overflow_checks))]
fn cast(v: i64)->u32{
    v as _
}
```


### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement feature.
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
https://github.com/rust-lang/rust/pull/111096
https://github.com/rust-lang/reference/pull/1355
Repository: pytorch
Issue: `dense -> sparse compressed` to work with empty batches.
Labels: module: sparse,triaged

### 🚀 The feature, motivation and pitch

Currently, it is not possible to convert an empy-batched dense tensor to a sparse compressed tensor.
```python
In [1]: import torch

In [2]: torch.rand(0, 4, 4).to_sparse_bsr(2)
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Input In [2], in <cell line: 1>()
----> 1 torch.rand(0, 4, 4).to_sparse_bsr(2)

RuntimeError: to_sparse_bsr: Expected product of batch dimensions to be non-zero.

In [3]: torch.rand(0, 4, 4).to_sparse_csr()
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Input In [3], in <cell line: 1>()
----> 1 torch.rand(0, 4, 4).to_sparse_csr()

RuntimeError: to_sparse_csr: Expected product of batch dimensions to be non-zero.
```

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @pearu @cpuhrsch @amjames @bhosmer
Repository: pytorch
Issue: custom_op API follow-ups
Labels: triaged

@soulitzer, @bdhirsh, @ezyang if I missed any:

Tracking here so I don't need to keep all of them in my head
- [ ] way to mark operator as non-differentiable
- [x] ctx.needs_input_grad is wrong for TensorList inputs
- [ ] how to wrap triton kernel with this API 
- [ ] custom_op and randomness (need to ban, likely through testing)
- [ ] custom_op and cuda graphs (Elias tells me not all custom ops work with cuda graphs)
Repository: pytorch
Issue: AOTAutograd export path does not support training graphs with parameters that do not receive gradients.
Labels: triaged,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

See the comment [here](https://github.com/pytorch/pytorch/pull/100587/files#diff-df954bbf954d2dcb81f687876053267ffa4ddb36ed86b7d2bd76319ff2b94416R3786): today, the AOTAutograd export path expects that every parameter in the module you export will receive some sort of gradient. It's possible to create a case where this doesn't happen. We can support it, but I'd like to gauge how much request there is for this first, since it's more of an edge case.

Example:

```
def f(p1, p2):
    # p1 will never receive any gradients. p2 will though
    return p1.detach() * p2
```

cc @ezyang @msaroufim @wconstab @anijain2305 @zou3519
Repository: storybook
Issue: [Bug]: Typecast fails in stories files
Labels: bug,needs triage

### Describe the bug

Whenever a `<>` brackets type cast in stories.ts files is used, the build fails with
```
WARN 🚨 Unable to index ./src/stories/Button.stories.ts:
WARN   SyntaxError: Unexpected token, expected "}" (12:21)
WARN     at instantiate (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:653:32)
WARN     at constructor (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:946:12)
WARN     at TypeScriptParserMixin.raise (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:3270:19)
WARN     at TypeScriptParserMixin.unexpected (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:3300:16)
WARN     at TypeScriptParserMixin.expect (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:3642:28)
WARN     at TypeScriptParserMixin.jsxParseExpressionContainer (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:6872:10)
WARN     at TypeScriptParserMixin.jsxParseElementAt (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:6946:36)
WARN     at TypeScriptParserMixin.jsxParseElement (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:6990:17)
WARN     at TypeScriptParserMixin.parseExprAtom (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:7002:19)
WARN     at TypeScriptParserMixin.parseExprSubscripts (C:\Work\test-sb\test-sb\node_modules\@babel\parser\lib\index.js:10872:23)
```

example code snippet (the problematic part being the `<ICollection>` typecast):
```
const meta: Meta<Button> = {
  title: 'Example/Button',
  component: Button,
  tags: ['autodocs'],
  render: (args: Button) => ({
    props: <ICollection>{
      backgroundColor: null,
      ...args,
    },
  }),
  argTypes: {
    backgroundColor: {
      control: 'color',
    },
  },
};

export default meta;
```
The same problem occurs when a typecast of the Meta object is used, therefore there seems to be a global problem of not accepting the typecast.

### To Reproduce

1. Create a storybook 7 with Angular 15+ project
2. Update Button story to contain a `<>` Type Cast
3. Run storybook

or
https://stackblitz.com/edit/github-penzjy?file=src%2Fstories%2FButton.stories.ts&preset=node

### System

```shell
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
  Binaries:
    Node: 18.16.0
    npm: 9.5.1
  Browsers:
    Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)
  npmPackages:
    @storybook/addon-essentials: ^7.0.10 => 7.0.10
    @storybook/addon-interactions: ^7.0.10 => 7.0.10
    @storybook/addon-knobs: ^7.0.2 => 7.0.2
    @storybook/addon-links: ^7.0.10 => 7.0.10
    @storybook/angular: ^7.0.10 => 7.0.10
    @storybook/blocks: ^7.0.10 => 7.0.10
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

_No response_
Repository: neovim
Issue: vim.lsp.tagfunc does not support regex
Labels: lsp

### Problem

The built-in LSP-aware tagfunc seems to pass the pattern directly to `workspace/symbol`: https://github.com/neovim/neovim/blob/e124672ce9a81e0ca32e6c30ea3730ad5fe981af/runtime/lua/vim/lsp/tagfunc.lua#L46-L48

This is probably great for performance, but also means that regex patterns always return empty.

This is related #22376 — currently tag completion doesn't use `tagfunc` at all, but as tag completion uses a regex pattern for searching tags, this would also need to be fixed for #22376 to work when `tagfunc` is set to `vim.lsp.tagfunc`.

### Steps to reproduce using "nvim -u minimal_init.lua"

In any workspace that supports `workspace/symbol`, with `set tagfunc=v:lua.vim.lsp.tagfunc`:

```vim
:tselect /.
E433: No tags file
E426: tag not found: .
```


### Expected behavior

In any workspace that supports `workspace/symbol`, with `set tagfunc=v:lua.vim.lsp.tagfunc`:

```vim
:tselect /.
" All tags are shown
```

### Neovim version (nvim -v)

NVIM v0.10.0-dev-313+g9d306ac6b

### Language server name/version

Any, but tested on Apple clangd version 14.0.3 (clang-1403.0.22.14.1)

### Operating system/version

macOS 13.3.1

### Log file

https://gist.github.com/Qyriad/766ce65a742742bf931764a8c03a9ff8