sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Consider providing an plugin abstraction for intents
Labels: c: new feature,platform-android,engine,c: proposal,P2,a: plugins,team-android,triaged-android

The Android intent system is based on request codes, which means that distributing handling of responses among plugins that don't know about each other is problematic. https://github.com/flutter/flutter/issues/124309 is a recent example of this, and I've seen people ask before how they are intended to avoid it.

While there are reasonable mitigations (as noted in my comment), plugin authors have to know to do them, and all it takes is for two not to, and to instead assign their codes in sequence from 0 or 1 (or to both pick "clever" special values instead of random ones, and have the same clever idea), for those options to break when combined.

Since the underlying problem is that we don't know about the request so can't route the responses, we could provide a wrapper API for plugins to use for intents, which could handle it internally (e.g., by taking half the intent code size for a per-plugin, Flutter generated value, then letting each plugin use the other half-size for its codes in the wrapper API, then using the generated half to route responses).

A counterargument here would be that people would also have to know to use the wrapper instead of doing intents directly, but we could potentially deprecate the API to register the current listener.
Repository: pytorch
Issue: Higher order derivatives not working when setting compute device to `torch.device("mps")`
Labels: module: autograd,triaged,module: mps

### 🐛 Describe the bug

I have a code example that performs fast updates, similar to what we have in MAML, to a perform inner updates and then computes the meta-loss to backpropagate through the optimization trajectory. When computing gradients in the fast updates, we can set `create_graph=True` to enable second-order derivatives when call backward on the meta-loss. When using `torch.device("mps")`, it throws an error that `derivative for aten:linear is not implemented`. It works fine when you set `create_graph=False` in the inner updates but then it wouldn't compute the higher order derivatives. I don't get the error when using `torch.device("cpu")` and `torch.device("cuda")`. Here is the code to reproduce the error:

```python

device = torch.device("mps")
model = nn.Sequential(nn.Linear(10, 5), nn.ReLU(), nn.Linear(5, 1))
model.to(device)

# Initial fast parameters
fast_params_0 = {n: deepcopy(p) for (n, p) in model.named_parameters()}

# First inner update
x = torch.randn(10, 10, device=device)
y = torch.randn(10, 1, device=device)
logits_0 = torch.func.functional_call(model, fast_params_0, x)
loss = nn.MSELoss()(logits_0, y)
grads_0 = torch.autograd.grad(loss, fast_params_0.values(),
                              create_graph=True,
                              retain_graph=True)

# Compute fast parameters after the first inner update
fast_params_1 = {n: p - 0.1 * g for ((n, p), g) in zip(fast_params_0.items(), list(grads_0))}

# Compute meta-loss and backprop through the optimization trajectory
x = torch.randn(10, 10, device=device)
y = torch.randn(10, 1, device=device)
logits_1 = torch.func.functional_call(model, fast_params_1, x)
met_loss = nn.MSELoss()(logits_1, y)
met_loss.backward()

```

And, the error I get:
```
RuntimeError: derivative for aten::linear_backward is not implemented
```

*I get the same error for any layer type. 

### Versions

```
[pip3] numpy==1.23.5
[pip3] pytorchcv==0.0.67
[pip3] torch==2.0.0
[pip3] torchaudio==2.0.0
[pip3] torchmetrics==0.11.4
[pip3] torchvision==0.15.0
[conda] numpy                     1.23.5           py39h1398885_0  
[conda] numpy-base                1.23.5           py39h90707a3_0  
[conda] pytorch                   2.0.0                   py3.9_0    pytorch
[conda] pytorchcv                 0.0.67                   pypi_0    pypi
[conda] torchaudio                2.0.0                  py39_cpu    pytorch
[conda] torchmetrics              0.11.4                   pypi_0    pypi
[conda] torchvision               0.15.0                 py39_cpu    pytorch
```

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @kulinseth @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: storybook
Issue: [Docs]: The migration from Preview/old Canvas Doc block to the new Canvas API is undocumented
Labels: question / support,addon: docs,block: other

### Describe the bug

Not sure if it's a bug or by design. There is [this mention in the migration docs](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-docs-removed-deprecated-blocksjs-entry) about removal of deprecated blocks entry.

I'm currently trying to migrate from 6.5. to 7 and we have a collection of MDX files that make use of the `<Preview />` component from `@storybook/addon-docs/blocks` to render code. e.g.

```
import { Meta, Preview } from '@storybook/addon-docs/blocks';
{/* OR import from blocks 
import { Meta, Preview } from '@storybook/blocks';
*/}

{/* Some Meta stuff and the such */}

<Preview>
  <Card>
    <Card.Heading>Filter by name</Card.Heading>
    <Card.Description>Filter data by query.</Card.Description>
  </Card>
</Preview>
```

This worked fine in SB6.5 but in SB7 it will throw an error as `@storybook/addon-docs`now appears to re-export everything from `@storybook/blocks`. However `@storybook/blocks` (where the [Preview component lives](https://github.com/storybookjs/storybook/blob/next/code/ui/blocks/src/components/Preview.tsx)) doesn't expose the `<Preview />` component for consumption.

If this is by design what is the suggested approach for SB7 to render previews?

### To Reproduce

https://stackblitz.com/edit/github-drg86u?file=src/stories/Introduction.mdx

### System

```shell
Environment Info:

  System:
    OS: macOS 13.3
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 18.14.0 - /private/var/folders/pg/ckvqm5nj3yv6l9n88t7cdk880000gn/T/xfs-ba42e0ce/node
    Yarn: 3.4.1 - /private/var/folders/pg/ckvqm5nj3yv6l9n88t7cdk880000gn/T/xfs-ba42e0ce/yarn
    npm: 9.3.1 - ~/.nvm/versions/node/v18.14.0/bin/npm
  Browsers:
    Chrome: 111.0.5563.146
    Firefox: 111.0.1
    Safari: 16.4
```


### Additional context

_No response_
Repository: PowerToys
Issue: New Feature - Autohide Windows with Edge Peek to recall on mouseover
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Basically the idea is that similar to the autohiding taskbar in windows, you could autohide a window off an edge of the screen and then recall it by putting your mouse in side of a zone directly correlating to the size or docked area of the window.

Here's a quick animation example:
![window-edge-dock-visible-edge](https://user-images.githubusercontent.com/34664355/230397658-b9be2b14-2a82-438a-8544-60f3988ec552.gif)

Here's another example with the edge option disabled so its purely a memory, hover. Sort of like autohide taskbar but not limited to an entire edge of your screen.
![window-edge-dock-invisible-edge](https://user-images.githubusercontent.com/34664355/230397977-ee7b6fc4-e630-4ad6-bd5b-bd0c4bc76e66.gif)

Please try a prototype I created here:
https://xd.adobe.com/view/785b08d5-e8a9-4ad4-b5d5-18f8c32a15b6-2d08/?hints=off

Here is a prototype the alternate with completely hidden window edge:
https://xd.adobe.com/view/20b5e226-a03c-4e57-b183-74e2b26eeff3-75e6/?hints=off

I am no software developer so all I can do is propose and supply UI/UX feedback. Happy to do anything within my capabilities to make this happen.

Would love to hear thoughts!

### Scenario when this would be used?

I typically use my display with FancyZones, an absolute must for me at this point, but often there are windows which are there that I don't necessarily need to be looking at constantly. So currently I have something like email just always present when I'd like to have access but have that real estate available for maybe a more actively used document or window. Could I just minimize the window and recall it like a normal user? Sure.. but the beauty of this idea is it requires no clicks. Hover is such a convenient way to pull out a window very fast to see or check something, even interact, but then have it tuck away when the mouse leaves the active area of that window. It even allows you to actively use the app while it is revealed from its 'drawer' but then when you're finished it automatically tucks away nicely.

### Supporting information

_No response_
Repository: terminal
Issue: The close all tab warning could prompt the user to enable "persist window layout" if it's disabled
Labels: Issue-Feature,Area-UserInterface,Area-Settings,Product-Terminal

_An off-the-cuff suggestion from @chendrixson_

If the user doesn't have "remember window layout" enabled, and they close more than one tab, maybe we could add a checkbox to that dialog to ask them if they want to turn that setting _on_.

Thoughts:
* Turning the setting on and saving the window layout at this point in teardown might be tricky
* Is there a way for users to say "No I absolutely do not want to save the layout and **stop asking**?" Does that even matter? It's just a checkbox...
* Is there a way to remember the layout _once_, like, for just the next launch? 
* How does this play with the "close multiple panes" warning / multiple processes? 
* Should we put this in the quit dialog? (we should put it there too)
Repository: pytorch
Issue: Power VSX vectorization support disabled
Labels: module: build,triaged,module: regression,module: POWER

### 🐛 Describe the bug

During cmake cleanup VSX vectorization support for power was disabled as well:

https://github.com/pytorch/pytorch/commit/847dbb8684f9d9bbf59cae629d07bff3ede0c4a2#diff-12e8125164bbfc7556b1781a8ed516e333cc0bf058acb7197f7415be44606c72L1729

ZVECTOR support for s390x was removed as well, but it's not part of this issue, it's already being worked on separately.
For ZVECTOR it takes more than just 1 cmake line to properly restore vectorization support, thus I assume it might be also the case for VSX.

### Versions

pytorch master branch

cc @malfet @seemethere
Repository: rust
Issue: Rustdoc-Json: Reexported items don't appear in `paths`
Labels: T-rustdoc,A-rustdoc-json,S-has-mcve

```rust
#![feature(no_core)]
#![no_core]

mod bytes {
    pub struct Bytes;
}

pub use bytes::Bytes;
```

```json
{
  "crate_version": null,
  "external_crates": {},
  "format_version": 24,
  "includes_private": false,
  "index": {
    "0:0:1024": {
      "crate_id": 0,
      "docs": null,
      "id": "0:0:1024",
      "inner": {"is_crate": true, "is_stripped": false, "items": ["0:4-0:2:1596"]},
      "kind": "module",
      "name": "path"
    },
    "0:2:1596": {
      "crate_id": 0,
      "docs": null,
      "id": "0:2:1596",
      "inner": {"generics": {"params": [], "where_predicates": []}, "impls": [], "kind": "unit"},
      "kind": "struct",
      "name": "Bytes"
    },
    "0:4-0:2:1596": {
      "crate_id": 0,
      "docs": null,
      "id": "0:4-0:2:1596",
      "inner": {"glob": false, "id": "0:2:1596", "name": "Bytes", "source": "bytes::Bytes"},
      "kind": "import",
      "name": null
    }
  },
  "paths": {"0:0:1024": {"crate_id": 0, "kind": "module", "path": ["path"]}},
  "root": "0:0:1024"
}
```

`0:2:1596` should appear in `paths`
Repository: kubernetes
Issue: support node taints owned by different fieldManagers
Labels: area/api,sig/node,sig/api-machinery,kind/feature,triage/accepted

### What happened?

When working with the TF-provider-kubernetes, i noticed how when attempting to set multiple fieldManagers, it will overwrite the previous fieldManager with the newly configured one. Making it not possible to have multiple fieldManagers.

Tested this with `kubectl` and also ran into the same issue.

### What did you expect to happen?

I should be able to have multiple fieldManagers as part of node taints

### How can we reproduce it (as minimally and precisely as possible)?

set the `--field-manager` field when working with node taints. You'll see in the yaml file how it will get overwritten with whatever new fieldManager is set.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:51:43Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-10-12T10:49:09Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/arm64"}
```

</details>


### Cloud provider

None

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

/sig cli
Repository: go
Issue: proposal: net/http: decide and document accepted HTTP methods in FileServer
Labels: Documentation,NeedsInvestigation

Now that the [fix](https://go-review.googlesource.com/c/go/+/413554) got [reversed](https://github.com/golang/go/issues/59375), the documentation should at least inform/warn about it's broken by default.
Repository: Web-Dev-For-Beginners
Issue: [TRANSLATIONS] in Urdu
Labels: translations

- [ ] Base README.md
- [X] for-teachers.md
- [ ] Quizzes
- [ ] 1-getting-started-lessons base README
   - [ ] intro-to-programming-languages README
   - [ ] intro-to-programming-languages assignment
   - [ ] github-basics README
   - [ ] accessibility README
   - [ ] accessibility assignment
- [ ] 2-js-basics base README
   - [ ] data-types README
   - [ ] data-types assignment
   - [ ] functions-methods README
   - [ ] functions-methods assignment
   - [ ] making-decisions README
   - [ ] making-decisions assignment
   - [ ] arrays-loops README
   - [ ] arrays-loops assignment
- [ ] 3-terrarium base README
   - [ ] intro-to-html README
   - [ ] intro-to-html assignment
   - [ ] intro-to-css README
   - [ ] intro-to-css assignment
   - [ ] intro-to-DOM-and-closures README
   - [ ] intro-to-DOM-and-closures assignment
- [ ] 4-typing-game base README
   - [ ] typing-game README
   - [ ] typing-game assignment
- [ ] 5-browser-extension base README
   - [ ] about-browsers README
   - [ ] about-browsers assignment
   - [ ] forms-browsers-local-storage README
   - [ ] forms-browsers-local-storage assignment
   - [ ] background-tasks-and-performance README
   - [ ] background-tasks-and-performance assignment
   - [ ] solution base README
   - [ ] start base README
- [ ] 6-space-game base README
   - [ ] introduction README
   - [ ] introduction assignment
   - [ ] drawing-to-canvas README
   - [ ] drawing-to-canvas  assignment
   - [ ] moving-elements-around README
   - [ ] moving-elements-around  assignment
   - [ ] collision-detection README
   - [ ] collision-detection assignment
   - [ ] keeping-score README
   - [ ] keeping-score assignment
   - [ ] end-condition README
   - [ ] end-condition assignment
- [ ] 7-bank-project base README
   - [ ] template-route README
   - [ ] template-route assignment
   - [ ] forms README
   - [ ] forms  assignment
   - [ ] data README
   - [ ] data assignment
   - [ ] state-management README
   - [ ] state-management  assignment
   - [ ] solution base README
   - [ ] API base README
Repository: angular
Issue: reflectComponentType should include inputs and outputs from hostDirective
Labels: area: core,state: has PR,core: host directives

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

_No response_

### Description

`reflectComponentType` does not include inputs and outputs added using host directive.

We are creating dynamic component and using `component.setInput(key, value)`. We do not know before hand if `key` will be available as input and if it is not defined we get the following error

<img width="566" alt="image" src="https://user-images.githubusercontent.com/6323787/230426535-15bbed66-80cd-409f-acdc-70c86289f9b6.png">

So, we where checking if `key` is a valid input for the component using `reflectComponentType` function.

This does not work when the input is added to the dynamic component through directive composition.

Even try, catch is not supressing the error. In prod mode the error is not there

### Proposed solution

Solution
1. `reflectComponentType` should include inputs from host directive
2. try, catch should supress error 
3. Provide alternatve way to get inputs

### Alternatives considered

--
Repository: kubernetes
Issue: GetLogs doesn't have support for Reactors in fake client
Labels: sig/api-machinery,kind/feature,help wanted,triage/accepted

### What would you like to be added?

GetLogs should be supported just like any other `entity` and `verb` in fakeClient, so that we can mock the GetLogs for unit test.
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/kubernetes/typed/core/v1/fake/fake_pod_expansion.go#L66

### Why is this needed?

Allows for unit testing of GetLogs function
Repository: pytorch
Issue: torch.cond should work with expressions involving SymInt
Labels: triaged,module: functorch

### 🐛 Describe the bug

If x.size(0) is an unbacked symint (because x came from nonzero), it is useful to say `torch.cond(x.size(0) > 5, do_true, do_false)`.

I believe @tugsbayasgalan will indirectly finish this off with https://github.com/pytorch/pytorch/pull/98453 because with symbool, we can then do `scalar_to_tensor(x.size(0) > 5)` and then pass that as a tensor argument to torch.cond.

### Versions

master

cc @zou3519 @Chillee @samdow @soumith @kshitij12345 @janeyx99
Repository: flutter
Issue: Document dependency graph for Cupertino widgets
Labels: framework,f: cupertino,d: api docs,team-design,triaged-design

I expect that many Flutter developers leverage Material widgets as ancestors to Cupertino widgets in their app (i.e. MaterialApp, Scaffold). However, our documentation assumes that developers use pure Cupertino apps.

It's unclear what the impact of using Cupertino widgets with Material parents is. Therefore, there may be theme attributes or specific behaviors that don't match what developers expect. 

We should consider creating a dependency graph to better understand how Cupertino widgets inherit properties from their parents, or how the parent influences its behavior.
Repository: flutter
Issue: WebGPU Backend for Flutter Web
Labels: c: new feature,engine,platform-web,c: proposal,P3,team-web,triaged-web

WebGPU is shipping in Chrome 113 without any flags:

https://developer.chrome.com/blog/webgpu-release/

Is there a current issue tracking the ETA or blockers for the WebGPU backend for Flutter? Trying to get an idea of the plan and see what people can do to help.
Repository: storybook
Issue: [Bug]: v7, builder-vite not working.
Labels: bug,needs reproduction,needs triage,builder-vite

### Describe the bug

I apologize in advance if my words sound strange as I'm using a translator.

I made a project with `yarn create vite` and did an `npx storybook init`, but there was a problem.
It doesn't work because there's no command.

I downgraded the Storybook packages to version `6.5.16`, but kept builder-vite at version `7.0.2`.
However, now I'm getting errors like the one below. The command works, but the execution doesn't.
![스크린샷 2023-04-07 오전 2 50 59](https://user-images.githubusercontent.com/45786387/230457065-9d9260b2-10f7-4ae6-8712-5a025ddc56f6.png)

So this time, I tried downgrading builder-vite to version `0.4.2`.

I finally got Storybook to run, but it's not displaying anything due to an error.
I'm not sure if it's a problem with vite or not. I'm a bit confused.
![스크린샷 2023-04-07 오전 2 53 07](https://user-images.githubusercontent.com/45786387/230457519-3470b510-2630-4a10-b531-e14d91dccfda.png)


### To Reproduce

https://github.com/hwookim/storybook-with-vite

### System

```shell
Environment Info:

  System:
    OS: macOS 12.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.18.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 111.0.5563.146
    Safari: 15.5
  npmPackages:
    @storybook/addon-actions: ^6.5.16 => 6.5.16 
    @storybook/addon-essentials: ^6.5.16 => 6.5.16 
    @storybook/addon-interactions: ^6.5.16 => 6.5.16 
    @storybook/addon-links: ^6.5.16 => 6.5.16 
    @storybook/builder-vite: ^0.4.2 => 0.4.2 
    @storybook/react: ^6.5.16 => 6.5.16 
    @storybook/testing-library: ^0.1.0 => 0.1.0 
```


### Additional context

Interestingly, when I tested it on another repository I was working on, it worked!
If possible, please take a look here as well. I'm not sure what the difference is.
https://github.com/hwookim/wil/tree/storybook
This is a monorepo consisting of `lerna` and `yarn workspace`. 
At first, there was another module with Storybook version `6.5.9` here, so there were other errors that occurred at [5ab441b](https://github.com/hwookim/WIL/commit/5ab441b1faa4e8eee1176490a9e8f82f583146f2).
Like this.
![스크린샷 2023-04-07 오전 2 04 12](https://user-images.githubusercontent.com/45786387/230459995-d2bb6fb6-19cb-47a1-88be-18a7230b82d1.png)
The target module is `packages/react-with-vite`.


Thank you for always creating great products. :)
Repository: rust
Issue: Run tests via miri for compiler crates that use `unsafe`
Labels: A-testsuite,T-compiler,T-bootstrap

#109971 made it so `compiler/rustc_data_structures` pass tests under miri. We should add testing under miri to CI in order to prevent future unsound bugs that can be detected with it.

Running the whole compiler through miri seems impossible, but running tests of crates that use `unsafe` code (like `rustc_data_structures`) seems both plausible and useful.