sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: build: unrecognized failures on netbsd-amd64-9_3
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "netbsd-amd64-9_3" && pkg == "" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/c9964bb47c259167e1c373d5efa6c535b4af6ba0)):



— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/website/cmd/golangorg: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/website/cmd/golangorg" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/6f5f4f0bc787a89d0bf7ccdec4f7f0ccf67189c9)):

    2022/11/20 10:09:26 newDirTree reading src: open src: no file system
    2022/11/20 10:09:56 https://go.dev/
    2022/11/20 10:10:07 newDirTree reading src: open src: no file system
    PASS
    testing: can't write /var/gobuilder/buildlet/tmp/go-build431852774/b317/testlog.txt: write /var/gobuilder/buildlet/tmp/go-build431852774/b317/testlog.txt: no space left on device


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: storybook
Issue: [Bug]: MDX styles not working with @storybook/mdx2-csf
Labels: bug,has workaround,mdx

### Describe the bug

Hi team, here's s small reproduction repo using the following:

- Node `v18.0.0`
- `@storybook/mdx2-csf` 
-  `previewMdx2: true` 
- ` builder: '@storybook/builder-webpack5'`

The introduction story does render but there's no font and code block / inline code block styling on elements created using markdown. 


Here's s screen shot: [Storybook + MDX 2](https://res.cloudinary.com/www-paulie-dev/image/upload/v1669051305/Temp%20Stuff/storybook-mdx-2_geefi8.png)

![Storybook + MDX 2](https://res.cloudinary.com/www-paulie-dev/image/upload/v1669051305/Temp%20Stuff/storybook-mdx-2_geefi8.png)




### To Reproduce

```shell
- Clone the reproduction repo: [reproduction-storybook-gatsby-5-mdx-2](https://github.com/PaulieScanlon/reproduction-storybook-gatsby-5-mdx-2)
- Install dependancies `yarn`
- Start Storybook, `yarn storybook`
```


### System

```shell
System:
    OS: macOS 11.6.8
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Binaries:
    Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Firefox: 105.0.3
    Safari: 15.6.1
  npmPackages:
    @storybook/addon-actions: ^6.5.13 => 6.5.13
    @storybook/addon-essentials: ^6.5.13 => 6.5.13
    @storybook/addon-interactions: ^6.5.13 => 6.5.13
    @storybook/addon-links: ^6.5.13 => 6.5.13
    @storybook/builder-webpack5: ^6.5.13 => 6.5.13
    @storybook/manager-webpack5: ^6.5.13 => 6.5.13
    @storybook/mdx2-csf: ^0.0.3 => 0.0.3
    @storybook/react: ^6.5.13 => 6.5.13
    @storybook/testing-library: ^0.0.13 => 0.0.13
```


### Additional context

n/a, but I think you all are great!
Repository: pytorch
Issue: Allow `low` and `high` to be tensors in `torch.randint`
Labels: feature,triaged,module: random

### 🚀 The feature, motivation and pitch

In `torch.randint`, allow `low` and `high` to be tensors (currently, only int are allowed), like in `numpy.random.randint`. 

```python
from torch import randint, tensor
randint(3)  # ERROR
randint(3, 7)  # ERROR
randint(3, 7, (3,))  # OK
randint(tensor([0, 1]), tensor([5, 4]))  # ERROR
```

```python
from numpy.random import randint
from numpy import array
randint(3)  # OK
randint(3, 7)  # OK
randint(3, 7, (3,))  # OK
randint(array([0, 1]), array([5, 4]))  # OK
```


### Alternatives

Keep using the following syntax

```python
from torch import concatenate, tensor, randint

lows, highs = tensor([0, 1]), tensor([5, 4])
concatenate([randint(low, high, (1,)) for low, high in zip(lows, highs)])
```

### Additional context

It would require to make the parameter `size` optional.

cc @pbelevich
Repository: create-react-app
Issue: Support additional WDS_SOCKET_* options
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I am always frustrated with the limited pass through of WDS_SOCKET_ variables.  Ideally I wish there was a WDS_SOCKET_URL={url} and potentially WDS_SOCKET_PROTOCOL.

### Describe the solution you'd like

Expand the logic in websocketDevServer.config.js to support alternative options from webpack-dev-server, such as `webSocketURL: ${WDS_SOCKET_URL}` and the protocol options in the object notation.

### Describe alternatives you've considered

Ejecting is the only viable solution currently given the hardcoded nature of the current WDS_SOCKET variable support.

### Additional context

This would be useful for me when running the CRA/WDS behind a local reverse proxy in a development mode.  I can't use the WDS's proxy values due to the applications requiring mutual-TLS authentication, hence the reverse proxy.
Repository: godot
Issue: Velocity is not exposed for CharacterBody2D (to use in AnimationPlayer)
Labels: enhancement,discussion,topic:physics,topic:2d

### Godot version

4.0 beta 5

### System information

Windows 11

### Issue description

When trying to animate velocities of CharacterBody2Ds using AnimationPlayer, we see that the property is not exposed for usage. 

![image](https://user-images.githubusercontent.com/1243371/203128232-623b60dd-38cd-4af4-bbe2-aa7cddadc6d9.png)

Not sure if this is by design. We can animate the property via code just fine. 

### Steps to reproduce

Add a property track to the animation, chose the CharacterBody as the subject, and try to pick velocity. 



### Minimal reproduction project

[MRP.zip](https://github.com/godotengine/godot/files/10059370/MRP.zip)
Repository: storybook
Issue: [Feature Request]: Allow embedding component + code view (snippet)
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

We are writing documentation for our internal component library. We use Storybook to handle core component functionality, props, settings, etc. and have a separate system to document setup instructions, use cases, examples, etc.

We're not seeing the desired behavior when embedding a story within our docs, being restricted to either `viewMode`:
* story
* docs

We'd like a potential 3rd option: `snippet`.

### Describe the solution you'd like

It would be fantastic if Storybook would allow us to embed the native component + code (snippet) view from the Docs tab, as shown below:
<img width="1043" alt="Basic Button example" src="https://user-images.githubusercontent.com/108944348/203132761-9d192197-6db2-4a30-aee5-25b30a6a8f22.png">

### Describe alternatives you've considered

Currently we write the code sample externally and then add the Storybook embed under it, using `viewMode=story`, however this is not ideal since we now have the snippet duplicated between Storybook and the documentation system.

We could embed the Docs page, but that also brings in all other stories that are part of this component. Ideally, we could link to a specific story and nothing else.

### Are you able to assist to bring the feature to reality?

no

### Additional context

_No response_
Repository: vscode
Issue: Opening walkthroughs automatically feels jarring
Labels: under-discussion,getting-started

Ref #165846

Installing extensions can sometimes lead to a walkthrough opening up unexpectedly. In extreme cases, 2+ walkthroughs are opened at the same time. There are two possible areas of improvement to consider:
- Should walkthroughs pop up automatically in the first place? If so, how can we make this less jarring?
- If so, should we limit to a single walkthrough opening up at once?

Here's an example installing Python from scratch:

https://user-images.githubusercontent.com/25163139/203135459-1b11b710-dd28-46d1-83c4-8e002bf359c7.mp4

@bhavyaus @digitarald @esonnino
Repository: go
Issue: cmd/go: pass the `-x` output as a `Context` key instead of hard-coding `os.Stderr`
Labels: NeedsFix,GoCommand

When we run `go build -x`, we send a bunch of extra logging to `os.Stderr`. That's fine in production code, but it makes unit-testing unpleasant: if tests run in parallel with `cfg.BuildX` set to true, the logging from the tests ends up all jumbled together.

We're already threading through a `context.Context` argument to many functions for tracing (see `cmd/go.maybeStartTrace`). We should also use that argument for output streams in order to better isolate tests.
Repository: vscode
Issue: Explore a lightweight notification UI to display confirmation feedback for actions to users
Labels: feature-request,ux

Motivating scenarios:
- Remote Repositories has a use case for displaying a one-off message on save to let the user know that their uncommitted changes will be saved in browser storage (similar to the Figma save toast). 
- Another use case is to provide confirmation that actions like copying a GitHub permalink to clipboard succeeded. 

Since this could get visually noisy IMO there should be a global toggle for this so that users can opt out.
Repository: rust
Issue: Changing order compilation errors to be under warnings?
Labels: A-diagnostics,T-compiler

Hi, I'm just teaching rust, and I think its very annoying when on build I have to scroll really a lot to get error message:

![image](https://user-images.githubusercontent.com/19526670/203138714-9e41b58c-9f50-4abc-b706-619750f03f9b.png)

For example in my case VS code totaly crashed code completion and I'm working like with plain text, and I always scroll like an idiot upside across all warnings to find the error. Could be nice if error was on bottom side of console (Yeah I will remove warnings later,.... I have to prototype first,...).

![image](https://user-images.githubusercontent.com/19526670/203138947-7893a6a1-6d3f-4d98-b27f-a6331df8441b.png)
Repository: vscode
Issue: Explore UX to explain vscode.dev differences compared to desktop app
Labels: feature-request,ux

When on vscode.dev, users are often deeplinked into specific content (PR diffs, editor deeplinks), which means that a first-time user of vscode.dev may not see our getting started walkthroughs and are not set up for success when using the product. We'd like to create a way for first-time users to learn about how to use the product, e.g. by showing info about how uncommitted changes are persisted in a lightweight overlay that is dismissed as soon as the user interacts with the UI. (Possible alternatives: surface this info in banner, integrate this info into the GitHub auth dialog since all users must already sign in, always open Getting Started editor for new users)

There are similar use cases e.g. wanting to spotlight new features in the product. We've done prior exploration on integrated walkthroughs: https://github.com/microsoft/vscode/issues/106717#issuecomment-698627820
Repository: rust
Issue: AFIT: impl can't add extra lifetime restrictions, unlike non-async
Labels: F-async_fn_in_trait

In a non-async trait, the impl is allowed to add a lifetime param that forces the lifetime of the two args to be the same:

```rust
trait Trait {
    fn write(&mut self, words: &[u8]);
}

impl Trait for () {
    fn write<'a>(&'a mut self, words: &'a [u8]) {}
}
```

However, with async traits it's not:

```rust
trait Trait {
    async fn write(&mut self, words: &[u8]);
}

impl Trait for () {
    async fn write<'a>(&'a mut self, words: &'a [u8]) {}
}
```

It results in this error:

```
error: `impl` item signature doesn't match `trait` item signature
  --> src/lib.rs:22:59
   |
18 |         async fn write(&mut self, words: &[u8]);
   |         ---------------------------------------- expected `fn(&'1 mut (), &'2 [u8]) -> _`
...
22 |         async fn write<'a>(&'a mut self, words: &'a [u8]) {}
   |                                                           ^ found `fn(&'1 mut (), &'1 [u8]) -> impl Future<Output = ()>`
   |
   = note: expected `fn(&'1 mut (), &'2 [u8]) -> _`
              found `fn(&'1 mut (), &'1 [u8]) -> impl Future<Output = ()>`
   = help: the lifetime requirements from the `impl` do not correspond to the requirements in the `trait`
   = help: verify the lifetime relationships in the `trait` and `impl` between the `self` argument, the other inputs and its output
```

I arrived at this code by accident. The obvious fix (removing the lifetime param) should always work. (At least, I can't think of any case where you'd explicitly want it). So I don't think this is a big issue, but the inconsistency feels weird so I thought I'd share.

[playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=a0cbfd186158c5df1ae10a512b5a5ba1)
Nightly version: 1.67.0-nightly (2022-11-20 a28f3c88e50a77bc2a91)
@rustbot label F-async_fn_in_trait
Repository: transformers
Issue: Add FlexiBERT
Labels: New model

### Model description

FlexiBERT is a suite of *flexible* and *heterogeneous* models. The design space was proposed in this [paper](https://arxiv.org/abs/2205.11656) accepted for publication in the Journal of Artificial Intelligence Research.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

The weights are available [here](https://huggingface.co/shikhartuli/flexibert-mini).
Repository: stable-diffusion-webui
Issue: [Bug]: `img2img alternative test` broken
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Followed this guide: https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Features#img2img-alternative-test

Nothing worked when following it. Only when I unchecked all the `Override` checkboxes and set the values manually it worked.

Mainly works if you disable the checkbox ```Override `Sampling method` to Euler?(this method is built for it)```


https://user-images.githubusercontent.com/10195356/203159874-0bd1fd17-190d-4569-acf9-8f6c2bda2bff.mp4



### Steps to reproduce the problem

Follow this guide: https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Features#img2img-alternative-test

### What should have happened?

Should work properly as illustrated in the guide

### Commit where the problem happens

828438b4a190759807f9054932cae3a8b880ddf1

### What platforms do you use to access UI ?

Windows

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

_No response_

### Additional information, context and logs

_No response_
Repository: pytorch
Issue: Higher order derivatives of sinc explode
Labels: triaged,module: derivatives,actionable

### 🐛 Describe the bug

First order derivatives of `torch.sinc(x)` are fine at `x=0`: they were previously reported as exploding in https://github.com/pytorch/pytorch/issues/56760 and https://github.com/pytorch/pytorch/issues/53989 and were fixed in https://github.com/pytorch/pytorch/pull/56763.

However, higher order derivatives or `torch.sinc(x)` at `x=0` still explode:

```python
zero = torch.zeros(1, requires_grad = True)
dx = torch.autograd.grad(torch.sinc(zero), zero, create_graph=True)[0]
torch.autograd.grad(dx, zero)[0]
tensor([nan])
```

By reading off the Taylor series of `sinc(x) = sin(x)/x = 1- x^2/3! + x^4/5! ...`, we get that the second derivative should have of limit of `-1/3`.

### Versions

PyTorch version: 1.12.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 12.5.1 (x86_64)
GCC version: Could not collect
Clang version: 12.0.5 (clang-1205.0.22.11)
CMake version: version 3.22.1
Libc version: N/A

Python version: 3.10.4 (main, Mar 31 2022, 03:38:35) [Clang 12.0.0 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.1
[pip3] torch==1.12.1
[conda] Could not collect


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: flutter
Issue: Replace the `DlImageSampling` enum with finer grained `DlSamplingOptions` struct
Labels: engine,c: proposal,P2,team-engine,triaged-engine

We should have a struct more like `SkSamplingOptions` to handle the combinatorial explosion of possible sampling configurations, all of which both Impeller and Skia are able to support just fine (except for cubic resampling in Impeller).

As part of `FragmentProgram`, we allow users to create arbitrary samplers -- translating to this enum would back us into a corner for supporting the full gamut of sampling configurations in the future.

The data in the `SkSamplingOptions` is:
```
    const int              maxAniso = 0;
    const bool             useCubic = false;
    const SkCubicResampler cubic    = {0, 0};
    const SkFilterMode     filter   = SkFilterMode::kNearest;
    const SkMipmapMode     mipmap   = SkMipmapMode::kNone;
```

The presets made available by `DlSamplingOptions` are:
```
enum class DlImageSampling {
  kNearestNeighbor,
  kLinear,
  kMipmapLinear,
  kCubic,
};
```

(This enum landed as part of https://github.com/flutter/engine/pull/34024)
Repository: flutter
Issue: Show similar information to `Rendered fonts` from Chrome inspector
Labels: engine,dependency: skia,a: typography,a: debugging,d: devtools,P3,team-engine,triaged-engine

It'd be really nice to know what fonts actually got picked for a Flutter application. chrome has this:

![image](https://user-images.githubusercontent.com/8620741/203171246-ffcfa032-79f3-4b6b-93dd-d17f8fed7d89.png)

In the inspector. It'd be great to have similar functionality in devtools.

/cc @jason-simmons @rusino
@kenzieschmoll
Repository: flutter
Issue: Consider decoupling navigator and PageTransitionsTheme
Labels: framework,a: animation,f: material design,f: routes,c: proposal,team-design,triaged-design

Currently the PageTransitionsTheme returns the builder that builds transition around Route. This forces the customer to use navigator if they want to use platform adaptive transition.

We should consider refactoring this theme to provide builder that does not rely on Route
Repository: neovim
Issue: vim.ui_attach: document the effect of return value of callback
Labels: documentation,lua,ui-extensibility

In the current implementation, if `vim.ui_attach()` callback returns `true`, the event is not passed to UI, otherwise it is still passed to UI. For `ext_popupmenu` this difference is unnoticeable in TUI because TUI doesn't not support `ext_popupmenu`, but it is noticeable in a UI that supports `ext_popupmenu`. Anyway, this behavior is neither documented nor tested.
Repository: flutter
Issue: [flutter_tools] the tool should catch missing Flutter/ephemeral/FlutterInputs.xcfilelist with helpful message
Labels: tool,platform-mac,a: first hour,P2,team-tool,triaged-tool

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. `cd integration_test/flavors`
2. `flutter create --platforms=macos .`
3. `xed macos/Runner.xcodeproj`
4. Hit the play button in XCode. 


**Expected results:** <!-- what did you want to see? -->
The project should build just fine.

**Actual results:** <!-- what did you see? -->
The project fails to build.

The project will run with `flutter run`, just not from XCode.
Repository: deno
Issue: Support npm:pm2
Labels: needs investigation,node compat,node API

        > @iugo how is it same error? What command are you trying to run?

run command `deno run -A npm:pm2 --help`.

same error, error info is `x.y.z is not a function`.

_Originally posted by @iugo in https://github.com/denoland/deno/issues/16679#issuecomment-1322852714_
Repository: excalidraw
Issue: details popup container
Labels: enhancement,discussion

As the title, Whether hyperlinks can link pictures ?  

Whether to consider adding multiple links? 

The desired effect is shown in the picture

![image](https://user-images.githubusercontent.com/41370387/203198247-676463f9-ce17-42d8-9896-8c4f49986cb1.png)
Repository: vscode
Issue: Outline view for workspace but not only current file
Labels: feature-request,outline

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Hi VSCode Team:
Currently there is already outline for current file (on side panel or 2nd side panel)
but no outline view for whole workspace symbols.
Can your team add the feature so it would be easier for workspace symbol searching, filtering, .....
view can be added also in side panel like outline for current file.

I know there has been a quick open window for global symbol searching, but：
1) quick open is a temporary but not consistent view and would be closed when losing its focus, ----  this behavior is not convenient for symbol search when you can't decide which symbol is the one you want before you go to symbol's details( e.g. function definition code) 
2) for workspace symbol search, currently VSCode not support fuzzy search yet, please ref [https://github.com/microsoft/vscode/issues/109548 ] (url)
I think this is a little bit stupid - why uses different filter rules for symbol searching in current file and workspace?
Repository: terminal
Issue: Quake does not open unless I go into settings and click Save
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

### Windows Terminal version

1.15.2874.0

### Windows build number

10.0.19041.928

### Other Software

_No response_

### Steps to reproduce

1. Boot Windows
2. Launch Windows Terminal
3. Press Windows+`

### Expected Behavior

The quake menu should pop up.

### Actual Behavior

On the first launch after boot, It doesn't work unless I go into the Terminal's settings and then click "Save". Interestingly enough, if I close all my Terminal windows, including the `_quake` window, then I open Terminal again, Quake opens without me needing to click on "Save"
Repository: pytorch
Issue: torch.split: argument 'split_sizes' (position 1) must be tuple of ints, not list
Labels: triaged,module: sorting and selection

### 🐛 Describe the bug

torch.split(tensor, split_sizes, dim=0)   :  split_sizes data type is int or list(int)

    import torch
    tensor = torch.rand([5, 5], dtype=torch.float64)
    split_sizes = [True, 3, False, True]
    out = torch.split(tensor, split_sizes)
    print(out)

result : TypeError: split_with_sizes(): argument 'split_sizes' (position 1) must be tuple of ints, not list

The value of input split_sizes is [True, 3, False, True], which is a list type. Although the value in the list is not necessarily legal, the exception thrown by the following code does not meet the actual requirements. The exception information says split_sizes must be tuple of ints, not list, does not match the official document description.

### Versions

pytorch: 1.12.1
Python version: 3.8
CUDA/cuDNN version: cuDNN 11.3
GPU models and configuration: RTX3060
Operating System：Windows