sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Make indices of IndexedJob pods configurable
Labels: area/batch,priority/awaiting-more-evidence,kind/feature,sig/apps,lifecycle/frozen,needs-triage,wg/batch

### What would you like to be added?

As a user I would like to be able to configure with which index the pods of a IndexedJob are getting created. 

By introducing a new field to the job spec API (possible name: `indices` -> TBD) we can influence with which index the controller would create pods.

This field then has a mutually exclusive relation to the `completions` field.

Ideally, we could also have a new status field called `failedIndices` which contains the indices of the failed pods. 
,

### Why is this needed?

This is especially helpful when running large batch jobs where some of them are failing. 
The user would now have an easy interface to just recreate the failed job and only rerun the failed indices by specifying them via the newly introduced field.
If we also introduce the status field `failedIndices` the user could easily pick the failed indices from that status and recreate the job with those indices. Introducing this status field also allows automating this workflow
Repository: svelte
Issue: Media element's `buffered` binding doesn't update frequently enough to match native `TimeRange` object
Labels: media elements

### Describe the bug

It seems that the current [`buffered`](https://svelte.dev/docs#template-syntax-element-directives-bind-property-media-element-bindings) binding [relies on the `progress` event](https://github.com/sveltejs/svelte/pull/819#issuecomment-328282736) to update its `TimeRange` object (or rather, its "array of `{start, end}` objects"). 

In my experience, however, the `progress` event doesn't actually fire frequently enough to reflect the state of the native `HTMLMediaElement.buffered`'s `TimeRange` object.

### Reproduction

https://svelte.dev/repl/a7c0417e5a204ef8b3a295e5c7881645?version=3.46.4

Note: swapping line 11 for line 10 is actually a more accurate representation of the native players buffer state. In line 11 the reactive statement has `buffered` as a dependency as well.

### Logs

_No response_

### System Info

```shell
System:
  OS: macOS 12.3
  CPU: (8) arm64 Apple M1
  Memory: 820.17 MB / 16.00 GB
  Shell: 5.8 - /bin/zsh
Binaries:
  Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
  Yarn: 1.22.17 - /opt/homebrew/bin/yarn
  npm: 8.5.2 - ~/.nvm/versions/node/v16.13.0/bin/npm
Browsers:
  Chrome: 99.0.4844.84
  Firefox: 98.0.2
  Safari: 15.4
npmPackages:
  rollup: ^2.3.4 => 2.70.1 
  svelte: ^3.0.0 => 3.46.4
```


### Severity

annoyance
Repository: godot
Issue: Vulkan: `CanvasItem.draw_polygon()` no longer has `normal_map` and `antialiased` parameters
Labels: discussion,topic:rendering,regression,topic:2d

### Godot version

v4.0.alpha5.official [d7d528c15]

### System information

Linux Pop!_OS 21.10, Nvidia GT710, Nvida X Server Settings 470.75.01

### Issue description

I'm porting a project from Godot 3.4.4 to Godot 4, and when I needed to write the method draw_polygon() it complained about having too much parameters. I needed to remove the "normal_map" and "antialiased" parameters to make it work.
Other draw methods lack the those parameters too.
For my project it is ideal to have the anti-alias enabled to make it look better.


### Steps to reproduce

Basically just try to call draw_polygon() with the same amount of parameters as you would do in version 3.x

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: [docs] RandomSampler has unrendered back-ticks
Labels: module: docs,triaged

### 🐛 Describe the bug

![image](https://user-images.githubusercontent.com/1041752/160730297-831a4079-e894-4d53-916f-b6fd90c94b28.png)
It may be nice to have a linter about unredered backticks

### Versions

N/A

cc @brianjo @mruberry
Repository: pytorch
Issue: Feature Request: Add J0 J1 J2 H0 H1 H2 Bessel functions
Labels: feature,triaged,module: special

### 🚀 The feature, motivation and pitch

There is modifed bessel function I0 and I1 in  special.h.
But it seems still lack some other bessel function.


### Alternatives

_No response_

### Additional context

_No response_

cc @mruberry @kshitij12345
Repository: pytorch
Issue: Store SourceDataset in MapDataset using pointer
Labels: module: cpp,module: dataloader,triaged

### 🚀 The feature, motivation and pitch

I'm using the c++ frontend and generating custom dataset classes through a factory. I'm getting pointers to my BaseDataset class from the factory and I cannot use `MapDataset` on the produced datasets because MapDataset stores classes instead of pointers at this line https://github.com/pytorch/pytorch/blob/master/torch/csrc/api/include/torch/data/datasets/map.h#L94 . There will be object slicing problems.

### Alternatives

Store dataset pointers instead.

### Additional context

_No response_

cc @jbschlosser @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: go
Issue: cmd/compile: defer of embedded method resolves pointer too early
Labels: NeedsInvestigation,compiler/runtime

Consider this test case:

```Go
package main

type CloseSetter interface {
	Set()
	Close() error
}

type S1 struct {
	f int
}

func (p *S1) Close() error {
	if p.f != 0 {
		panic(p.f)
	}
	return nil
}

type S2 struct {
	*S1
}

func (p *S2) Set() {
	p.S1 = &S1{0}
}

func F1(p CloseSetter) {
	p.Set()
	p.Close()
}

func F2() {
	s2 := &S2{}
	defer s2.Close()
	F1(s2)
}

func main() {
	F2()
}
```

When run with the gc compiler, this crashes:

```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x455534]

goroutine 1 [running]:
main.(*S1).Close(0xc000096000?)
	/home/iant/foo10.go:13 +0x14
main.F2()
	/home/iant/foo10.go:36 +0x7c
main.main()
	/home/iant/foo10.go:39 +0x17
exit status 2
```

When run with the gccgo compiler it exits successfully without printing anything.

I think the difference is that with the gc compiler the `defer` statement is resolving the embedded pointer at the point of the `defer`, and thus deferred a call to a nil pointer.  If that is correct, then that seems wrong.  A `defer` statement resolves all the arguments, but it shouldn't resolve `s2` into `s2.S1`.

Or maybe gccgo is incorrectly not crashing, but I don't yet see it.

CC @randall77 @griesemer @mdempsky
Repository: material-ui
Issue: [TabList] Add drag and drop feature
Labels: new feature,component: tabs

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Hi, requesting for drag & drop feature in MUI TabList as this is a standard requirement in many TabList use cases. For example - browser tabs.

### Examples 🌈

_No response_

### Motivation 🔦

I have been working on an application with this requirement. I tried implementing this feature using [react-beautiful-dnd](https://www.npmjs.com/package/react-beautiful-dnd), but I'm facing [this issue](https://stackoverflow.com/questions/71306336/auto-scroll-horizontal-mui-tablist-on-drag-with-react-beautiful-dnd/). Therefore, added the feature request as it has it's use cases in various applications. Also, could you please help me resolve the mentioned issue?
Repository: excalidraw
Issue: Couldn't connect to the collab server. Please reload the page and try again
Labels: docker

I have deployed excalidraw project, run it on my server. Then I try to share with others, I found this info, I need your help, thank you.
![image](https://user-images.githubusercontent.com/3354569/160757835-279d22b9-1e3a-4696-ad87-78c03e01e7a1.png)
Repository: godot
Issue: [GDExtension]Some types of static variables can't be initialized.
Labels: discussion,topic:gdextension

### Godot version

v4.0.alpha5.official [d7d528c15]

### System information

Windows 11, Vulkan, GeForce GTX 1060

### Issue description

Some types of static variables can't be initialized, and will lead to load error as follow.

```
 Can't open dynamic library: G:/godot-cpp/test/demo/bin/libgdexample.windows.debug.64.dll, error: Error 1114: 动态链接库(DLL)初始化例程失败。
  .
  Failed loading resource: res://example.gdextension. Make sure resources have been imported by opening the project in the editor at least once.
```

I haven't test many types.

Some test result as follow:    
  1. Can be initialzed types: bool, float, Vector2.
  2. Types which will lead to GDExtension's load error: String, StringName, Object.
  3. Not only class's static variables. but also global static variables.
  4. By the way, initialize a static const will lead to this error, too.




### Steps to reproduce

The custom class source code like this：

```C++
#ifndef TEST_H
#define TEST_H

/*
    A simple test for static variable initialization.
    I haven't test many types.
    
    Can be initialzed types: bool, float, Vector2
    Types which will lead to GDExtension's load error: String, StringName, Object
 */

#include <godot_cpp/classes/object.hpp>

using namespace godot;

class StaticTest: public Object{
    GDCLASS(StaticTest, Object)
public:
    // Define a static variable.
    static Object staticTest;
protected:
    static void _bind_methods(){

    }
};
// This line to initialize static variable.
Object StaticTest::staticTest = Object();


#endif
```

Then register it into ClassDB.

### Minimal reproduction project

_No response_
Repository: flutter
Issue: Flutter Integration testing fail when moving between tests
Labels: a: tests,c: crash,tool,framework,platform-mac,platform-linux,f: integration_test,has reproducible steps,P2,found in release: 2.10,found in release: 2.13,team-framework,triaged-framework

There seems to be issues running multiple integration tests in separate files on desktop applications, where it crashes when moving between tests.  It opens the second application to start testing but will be blank and the test will fail.

I have tested this on both macOS (M1) and Linux (ARM). The tests do work on an iOS emulator so it seems to definitely be a desktop specific issue.

 ## Steps to Reproduce

1. Have separate files for each test
2. Execute `flutter integration test` 
3. First test will run fine
4. Second app will open and the test will fails 

 ## Error Results

![Screenshot 2022-03-30 at 10 13 17](https://user-images.githubusercontent.com/43554905/160797521-379ba11c-a798-41b3-8a7a-dfd9ea450c26.png)

![Screenshot 2022-03-30 at 10 13 26](https://user-images.githubusercontent.com/43554905/160797547-7bc5c6ab-bfc4-4d07-8d68-602d6a02b7c7.png)
Repository: storybook
Issue: Show thrown errors from a play function in interactions debugger panel or somewhere else
Labels: feature request,addon: interactions

**Is your feature request related to a problem? Please describe**
Hi. I'd like to discuss the idea to don't cover rendered story by the error's red box when error is thrown from a play function. The reason of that request is when user got an error from a play function they might want to inspect or debug the story markup or even be able to interact with story. And the red box prevents any possibilities for that.

**Describe the solution you'd like**
My suggestion is to show an error from a play function in interactions debugger panel, no matter is the `interactionsDebugger` feature enabled or not. So storybook should catch an error and instead of showing the red box, send it to intreactions debugger.

**Describe alternatives you've considered**
We can discuss other alternatives, because as I know interactions debugger panel is hidden by default, so user might not see if something goes wrong in a play function. So maybe we should show the error somewhere else.

**Are you able to assist to bring the feature to reality?**
I could try

**Additional context**
In our use case we have an addon that wraps our interactions to the instrumenter `track` method https://github.com/thefrontside/interactors/pull/164. And the problem is, when we throw an error it is caught in two places, by instrumenter itself and by story renderer, so we get an error's message in interactions debugger and in the red box which covers current story. It happens because we wrap interactions in runtime and our interactions are promise-like objects.

It also be useful to don't cover current story if users get an error outside the `@storybook/testing-library` code. For example if they search elements by query or do something with elements directly.
Repository: angular
Issue: `HostListener`: Add wildcard to keyboard pseudo-event
Labels: feature,area: core,core: event listeners,feature: under consideration

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

## Preface:
To listen to keydown of `ArrowRight` we can use
```ts
@HostListener('keydown.arrowRight')
```
It will be triggered on every pressing of the right arrow.
But it will not be triggered if we press keystroke combination `Shift` + `ArrowRight`.

To listen to this keystroke combination we can use:
```ts
@HostListener('keydown.shift.arrowRight')
```

## Problem
I want to listen any pressing of `ArrowRight` (even if it is a part of keystroke combination).
It can become difficult to cover all possible combinations:
```ts
@HostListener('keydown.arrowRight')
@HostListener('keydown.shift.arrowRight')
@HostListener('keydown.control.arrowRight')
@HostListener('keydown.meta.arrowRight')
…
```

Of course, I can use 
```
fromEvent(nativeElement, 'keydown’).pipe(filter(onlyRightArrow), …).subscribe(…)
```
But it is not «angular-way»
___


### Proposed solution

Add wildcard for to keyboard pseudo-event.
For example:
```ts
@HostListener('keydown.*.arrowRight')
```
It means: listen to all keystroke combination with `ArrowRight`.

### Alternatives considered
–
Repository: material-ui
Issue: [system] Move layout components to the System package
Labels: package: system

The layout components are not specific to Material Design and can be used in any design system.
Therefore it makes sense to move them from @mui/material to the design-agnostic @mui/system.
It would allow them to be used from Joy and in Base demos without having to import @mui/material.

The components should be reexported from @mui/material for convenience (and to avoid introducing breaking changes).

Components to move:

- [x] Box
- [x] Container
- [x] Grid
- [x] Stack
- [ ] ImageList

---

cc @mui/core
Repository: storybook
Issue: Populate Search Input Field via URL
Labels: feature request,needs triage

I couldn't find a feature request for this one, but it would be great to have it: In the sidebar we have an input field for searching stories. It would be great to pass a query param in the URL (e.g. `https://www.domain?search=button`) which populates the search field and show the filtered result in the sidebar.
Repository: flutter
Issue: [go_router] Can't use ThemedPage from animations package
Labels: package,p: animations,has reproducible steps,P2,found in release: 2.10,p: go_router,found in release: 2.13,team-go_router,triaged-go_router

I am trying to use an OpenContainer from a Page, that has been built with the GoRouter:

```dart
final router = GoRouter(
 ...
 routes:[
    GoRoute(
     path: 'themedRoute'
     builder: (context,state) => PseudoThemeProvider(child: ThemedPage()); //I "injecting" a new theme for the page here
    )
 ]
);
```

the Problem is, when I am on `ThemedPage` and use the `OpenContainer` from the [AnimationsPackage](https://pub.dev/packages/animations) like this : 

```dart
//Pseudocode to show relation
ThemedPage(
   child: OpenContainer(.
      openBuilder: (context, action) => NewPage(),
      closedBuilder: (context, action) => ListTile(),
    );
)
```

the `NewPage` is not inside the `ThemedPage` but on top of it, loses the ThemeData of the `ThemedPage` and gets built with the default theme. 

How can I fix this behavior?
Repository: tauri
Issue: [feat] Mouseup events do not take effect when the data-tauri-drag-region attribute is added
Labels: type: bug,status: upstream

### Describe the problem

Mouseup events do not take effect when the data-tauri-drag-region attribute is added

### Describe the solution you'd like

Mouseup events can take effect when the data-tauri-drag-region attribute is added

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Flutter web does not support BlendMode.clear or BlendMode.dst using html renderer
Labels: c: new feature,engine,platform-web,e: web_html,has reproducible steps,P3,found in release: 2.10,found in release: 2.13,team-web,triaged-web

<h1>Flutter version :2.10.4</h1>›
`Doctor summary (to see all details, run flutter doctor -v):

- [✓] Flutter (Channel stable, 2.10.4, on macOS 12.3 21E230 darwin-arm, locale en-RO)
- [✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
- [✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
- [✓] Chrome - develop for the web
- [✓] Android Studio (version 2021.1)
- [✓] IntelliJ IDEA Community Edition (version 2021.3)
- [✓] VS Code (version 1.65.2)
- [✓] Connected device (1 available)
- [✓] HTTP Host Availability

`
<h1>Steps to reproduce</h1>


1. import 'dart.ui' as ui
2. `Paint _clearPaint = ui.Paint()..blendMode=BlendMode.clear` // it can also be BlendMode.dst
3.  flutter run -d chrome --web-renderer html


<h1> Expected behavior</h1>
App should run normally.

<h1> Current Behavior </h1>
App crashes with the current error: Flutter web does not support BlendMode.clear

If we decide to use only --web-renderer canvaskit the app will run very glitchy on mobile web
Repository: pytorch
Issue: [feature request] `coalesce` to support `dim` argument.
Labels: module: performance,module: sparse,feature,triaged

### 🚀 The feature, motivation and pitch

`coalesce`, when run on a sparse tensor, not only removes duplicates, but it also sorts indices in the first dimension (`dim=0`).
Having indices sorted in a specific dimension with coalesced values provides an additional structure that could be exploited to dramatically speed up functions that operate over this dimension (no need to sort to perform intersections, relevant for reductions/indexing or the count tables could be obtained in a cache-friendly and parallel way).

With that said, it would be great to have an option to have COO indices sorted in a specific dimension (i.e. having `coalesce(dim=...)`, such that the user could benefit from additional performance boosts provided that the operation that the user uses takes advantage of the structure.

### Alternatives

Alternatively, this could be achieved with a composition of `transpose` + `coalesce`, but `coalesce` is a very expensive operation to be performed repeatedly (sync + serial implementation on the CPU side afair), and the sorting could be done in-place to save on memory while `transpose` is not a view and creates a copy.

### Additional context

In my benchmarking of `index_select` from https://github.com/pytorch/pytorch/pull/72710 I could see a 4-20x speed-up of `dim==0 && self.is_coalesced()` compared to other dimensions.

cc @VitalyFedyunin @ngimel @nikitaved @pearu @cpuhrsch
Repository: electron
Issue: [Feature Request]: allow to validate IPC before handling it centrally
Labels: enhancement :sparkles:,component/ipc

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

The new security topic https://github.com/electron/electron/blob/main/docs/tutorial/security.md#17-validate-the-sender-of-all-ipc-messages suggests to validate IPC messages. We need a way to do this validation in a central place without changing each and every IPC handler that gets installed. 

### Proposed Solution

Introduce a new event in `app` that enables to `preventDefault()` the IPC handling in case validation fails. Similar to the `web-contents-created` event that allows to validate web contents and web views.

### Alternatives Considered

Introducing a utility method that wraps around the `ipcMain` module would be our workaround which is not so nice because it is easy to forget this utility when new code is added.

//cc @deepak1556
Repository: pytorch
Issue: [feature request] Make `index_select` parallel.
Labels: module: performance,feature,triaged,module: advanced indexing

### 🚀 The feature, motivation and pitch

As per title. The implemented algorithm is serial and could be improved to exploit the benefits of multicore environments.

As an alternative, `gather` could be used with a proper expansion of the index (luckily, memory-efficient). This definitely is going to solve the parallelization issue but is less clear/beautiful code-wise.

```python
In [32]: %timeit res2 = x.index_select(1, idx)
78.6 ms ± 111 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [33]: %timeit res1 = x.gather(1, idx.unsqueeze(0).expand(5000, 10000))
17 ms ± 33.1 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

In [34]: x.shape
Out[34]: torch.Size([5000, 5000])

In [35]: idx.shape
Out[35]: torch.Size([10000])

In [36]: res1 = x.gather(1, idx.unsqueeze(0).expand(5000, 10000))

In [37]: res2 = x.index_select(1, idx)

In [38]: (res1 == res2).all()
Out[38]: tensor(True)

```

Would it actually make sense to implement `index_select` with `gather`? Like it is done in https://github.com/pytorch/pytorch/pull/72710, for example
https://github.com/pytorch/pytorch/blob/f29cc653e90bffe5d941e0199d962daeb9d50973/aten/src/ATen/native/TensorShape.cpp#L1369-L1380

cc @VitalyFedyunin @ngimel
Repository: pytorch
Issue: LSTM quantization fails if proj_size > 0
Labels: oncall: quantization,low priority,triaged

### 🐛 Describe the bug

Hi, dynamic quantization of LSTM fails if `proj_size > 0`. Reproducible example:
```
import torch
import torch.nn as nn
from torch.quantization import quantize_dynamic



def quantize(
    model, backend = "qnnpack"
):

    assert backend in ["qnnpack", "fbgemm"]

    qconfig = torch.quantization.get_default_qconfig(backend)
    torch.backends.quantized.engine = backend

    qconfig_spec = {
        nn.Linear: qconfig,
        nn.LSTM: qconfig,
        nn.GRU: qconfig,
        nn.LSTMCell: qconfig,
    }

    return quantize_dynamic(
        model,
        qconfig_spec=qconfig_spec,
    )


cells = nn.Sequential(nn.LSTM(
    input_size=12,
    hidden_size=1200,
    proj_size=400,
    num_layers=1,
),nn.LSTM(
    input_size=400,
    hidden_size=1200,
    proj_size=400,
    num_layers=1,
),)

cells = quantize(cells, "fbgemm")

x = torch.randn(10, 2, 12)

hc = None
for c in cells:
    x, _ = c(x)
````

The error is
```
    358 _all_params = ([m.param for m in self._all_weight_values])
    359 if batch_sizes is None:
--> 360     result = torch.quantized_lstm(input, hx, _all_params, self.bias, self.num_layers,
    361                                   float(self.dropout), self.training, self.bidirectional,
    362                                   self.batch_first, dtype=self.dtype, use_dynamic=True)
    363 else:
    364     result = torch.quantized_lstm(input, batch_sizes, hx, _all_params, self.bias,
    365                                   self.num_layers, float(self.dropout), self.training,
    366                                   self.bidirectional, dtype=self.dtype, use_dynamic=True)

RuntimeError: The number of rows in the packB should be equal to K: 1200
```

### Versions

Running `torch==1.11.0` but also happens on `torch.1.10.0`

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @albanD @mruberry @jbschlosser @walterddr @kshitij12345