sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Initialized DETR backbone weights do not match with actual pretrained weights 
Labels: Good Second Issue

Hello everybody! 

My task is to initialize DETR Object Detection model with my own pretrained backbone (for example, ResNet-50). So, in Detr class (I took the code from [this Hugging Face tutorial](https://github.com/NielsRogge/Transformers-Tutorials/blob/master/DETR/Fine_tuning_DetrForObjectDetection_on_custom_dataset_(balloon).ipynb) as a basis), I create model from DetrConfig:
```
class Detr(pl.LightningModule):

    def __init__(self, lr, lr_backbone, weight_decay, backbone_name):
        super().__init__()

        self.model = DetrForObjectDetection(DetrConfig(num_labels=len(id2label)
                                                      ,ignore_mismatched_sizes=True
                                                      ,backbone=backbone_name
                                                       ))
    ...
```
Then I create model:
```
model = Detr(lr=1e-4, lr_backbone=1e-5, weight_decay=1e-3, backbone_name='resnet50')
```
And I want to see, for example, first layer weights in backbone:
```
model.model.model.backbone.conv_encoder.model.conv1.weight
```
Output:
```
Parameter containing:
tensor([[[[-1.0862e-02,  5.6558e-02, -2.5807e-02,  ..., -1.8801e-03,
            2.1483e-02, -1.1144e-02],
...
```
And I notice that this weights are different from timm backbone model, which is [fed to the input](https://github.com/huggingface/transformers/blob/68dec6bffd68e62d151758d8ac7378bf9b40ac20/src/transformers/models/detr/modeling_detr.py#:~:text=backbone%20%3D%20create_model(name%2C%20pretrained%3DTrue%2C%20features_only%3DTrue%2C%20out_indices%3D(1%2C%202%2C%203%2C%204)%2C%20**kwargs)) of the Detr model:
```
backbone_model = timm.create_model('resnet50', pretrained=True, features_only=True, out_indices=(1, 2, 3, 4))
backbone_model.conv1.weight
```
Output:
```
Parameter containing:
tensor([[[[-2.6017e-02, -1.7312e-02, -1.0648e-02,  ...,  1.1380e-02,
           -1.0471e-02, -1.1242e-02],
...
```

So... My question is, how can this happen? Why are the weights of the model that is fed into the Detr input differ from the weights of the same model in the already initialized Detr? Is this a bug or am I missing something?

One more detail: If I create model again, weights will also change! But when I restart Kernel and create Detr model, weights will be the same as in my first model creation at previous Kernel! So, the weights are initialized differently, but with a certain cycle? Why is this happening? In my understanding, backbone weights should always be the same and equal to the original ResNet weights.

Maybe, I'm setting the configuration wrong, but it could be a bug. I would really appreciate an answer and possible clarification!
Repository: vscode
Issue: Introduce Sound Theme, similar like Product Icon Themes
Labels: feature-request,accessibility,accessibility-signal

Some users want more customisation towards what sounds are being used.
I think in the future we should consider introducing Sound Themes similar to Icon Themes. So they can be extensions and users can choose which one is applied.

For now assigning this to the backlog.
fyi @aeschli @hediet 

@gino-scarpino to try out the product icon experience do F1 > Preferences Product Icon Themes > Browse Additional Product Icon Themes...
Repository: three.js
Issue: Points billboard not working as expected in VR on r137
Labels: Regression,Needs Investigation

<!-- Ignoring this template may result in your bug report getting deleted -->

**Describe the bug**

I’m building a simple scene with multiple particles (points). It works great in browser, but not in VR. When I try it in VR some strange distortion appears on screen. To see it you need to look at specific angles.

*It's is difficult to describe it so please take a look at the screenshots.*

[Topic on discourse.threejs.org](https://discourse.threejs.org/t/points-are-rendered-wrong-in-vr/35487)

**To Reproduce**

Steps to reproduce the behavior:
1.Create a simple scene with points or open provided example in your VR headset (not the WebXR emulator)
2. Enter VR mode
3. See how points are billboarding 

***Live example***

* [Codesandbox example](https://codesandbox.io/s/threejs-points-playground-25dum)
* App link: https://25dum.csb.app/

**Expected behavior**

An identical rendered scene as without VR  

**Screenshots**
![image](https://user-images.githubusercontent.com/20124129/158580966-9d74190c-0eab-4235-9345-3077a413078f.png)
![image](https://user-images.githubusercontent.com/20124129/158580992-a878525c-a77e-414a-9abd-500b2fe3e41c.png)

**Platform:**

 - Device: [Oculus Quest 2]
 - Browser: [Oculus Browser]
 - Three.js version: [r137]

**Additional notes:**
 - I was able to "bypass" this issue by downgrading from r137(0.137.5) to r132 (0.132.2)
 - Haven't tested on other releases of threejs 
 - Haven't tested on other devices except Oculus Quest 2
 - The scene is rendered correctly in WebXR emulator
Repository: storybook
Issue: See code warnings on console when running Storybook
Labels: feature request,needs triage

**Is your feature request related to a problem? Please describe**
I am using React and Storybook to build a components library. I noticed that when I run the library locally, I don't see the warnings on the console as when I run my react projects. I think that allowing seeing warnings on the console will be really useful for us in order to have a clearer code. I am using React and Storybook latest versions.

**Describe the solution you'd like**
I would like to see code warnings on the console when I run Storybook with npm run storybook.
Repository: storybook
Issue: TypeError: compilation.getAssetPath is not a function
Labels: bug,needs triage

**Describe the bug**

I ran into this in my Storybook build job today.

```
npx build-storybook --output-dir storybook-static/src
```

Errors:

```
TypeError: compilation.getAssetPath is not a function
```

Resolved it by manually adding this dependency:

```
npm install html-webpack-plugin --save-dev
```

Feels like a bandaid, but it works for now.

Perhaps related: https://github.com/jantimon/html-webpack-plugin/issues/1546

**Extra context**
This seemed to crop up after I added `webpack` as a `devDependency` in some of the packages that my Storybook is importing as a `dependency` (they need to webpack themselves for asset publishing to s3, unrelated to Storybook).  I think that perhaps their versions of webpack are interfering with Storybook in some way. They're using `"webpack": "5.70.0"`.

Not sure if this is a Storybook bug per se, but adding this here just in case it rings a bell with one of the SB devs.
Repository: transformers
Issue: Gpt2 large for onnx exportation and int8 quantization
Labels: New model

Hi, for model big as 7GB, does transformers support export to onnx?? Any tutorial about big model?
Repository: pytorch
Issue: TypeError: new_empty(): argument 'size' (position 1) must be tuple of ints, not list
Labels: module: error checking,triaged

### 🐛 Describe the bug

new_empty gives a bad error message if you pass it a list of things that are not ints; reporting that you expected a tuple of ints not list (but the real problem is one of the inner elements in the list). This probably applies to all argument parsers that take tuple of ints.

### Versions

master
Repository: pytorch
Issue: Time Gated Lstm
Labels: feature,module: nn,module: rnn,triaged

### 🚀 The feature, motivation and pitch

today i'm working with time series; in this area Time-Gated Lstm ( an implementation of the paper 'Nonuniformly Sampled Data Processing Using LSTM Networks' ) are very used.
obviously a my implementation can't perform well as the LSTM already present on Pytorch.
is possible a future implementation of this architecture?

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @zou3519
Repository: go
Issue: cmd/go: exclude vendor directories when using `go work use -r .`
Labels: help wanted,NeedsFix,modules

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/hakim/Library/Caches/go-build"
GOENV="/Users/hakim/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/hakim/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/hakim/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/hakim/projects/delve/go.mod"
GOWORK="/Users/hakim/projects/delve/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bw/6r6k9d113sv1_vvzk_1kfxbm001py5/T/go-build2599549157=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

* Checked out any project with `vendor` directory. (I used github.com/go-delve/delve)
* Ran `go work init; go work use -r .` from the root of the directory

### What did you expect to see?

go.work file without modules from vendor directories.

### What did you see instead?

```
$ cat go.work
go 1.18

use (
	.
	./vendor/github.com/cilium/ebpf
	./vendor/github.com/cosiner/argv
	./vendor/github.com/creack/pty
	./vendor/github.com/google/go-dap
	./vendor/github.com/konsorten/go-windows-terminal-sequences
	./vendor/github.com/peterh/liner
	./vendor/github.com/russross/blackfriday/v2
	./vendor/github.com/shurcooL/sanitized_anchor_name
	./vendor/github.com/sirupsen/logrus
	./vendor/github.com/spf13/cobra
	./vendor/github.com/spf13/pflag
	./vendor/golang.org/x/xerrors
	./vendor/gopkg.in/yaml.v2
)
```

cc @matloob
Repository: storybook
Issue: @storybook/web-components overrides properties with slots if they share a name
Labels: bug,web-components

**Describe the bug**
Using `@storybook/web-components` with `setCustomElements` from a schema created by something like `web-component-analyzer` with the Lit library, if you have a **property** and a **slot** with the same name, the slot will take precedence and override the other resulting in only showing the documentation for the slot.

That means when the custom-elements.json file looks like this, I would expect to see both in the docs table in Storybook, but only the slot is shown.

```custom-elements.json
[
  {
    "properties": [
      {
        "name": "headline",
        "description": "The headline property"
      }
    ],
    "slots": [
      {
        "name": "headline",
        "description": "This is the description of the headline slot"
      }
    ]
  }
]
```

One other thing to mention: If you have a default slot it goes into the custom-elements.json with an empty "name" property and as a result is not shown in Storybook at all. I believe this should show up some how, but I don't know how one could interact with such a thing without a name. Perhaps it could have a common name like "slot"?

**To Reproduce**

Repository with reproduction using web-component-analyzer:

https://github.com/iOvergaard/storybook-webcomponents-repro

There is a single web component which has:
1. A property named "label"
2. A slot named "label"
3. A default slot (no name)

**Expected result**
All three items should show up in the "Docs" section at least with a separate row in the documentation table.

**Actual result**
Only no. 2 (a slot named label) shows up:
![image](https://user-images.githubusercontent.com/752371/158606160-c8bbd057-42a4-4574-a442-19a9bcfddac7.png)


**System**
```
Environment Info:

  System:
    OS: macOS 12.3
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.3.0 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 99.0.4844.74
    Safari: 15.4
  npmPackages:
    @storybook/addon-a11y: 6.4.19 => 6.4.19 
    @storybook/addon-actions: 6.4.19 => 6.4.19 
    @storybook/addon-essentials: 6.4.19 => 6.4.19 
    @storybook/addon-links: 6.4.19 => 6.4.19 
    @storybook/web-components: 6.4.19 => 6.4.19 
```

**Additional context**
Looks like the error starts here: https://github.com/storybookjs/storybook/blob/1d36b02969fcf3d05543e5d9ae846949a6f45c6e/addons/docs/src/frameworks/web-components/custom-elements.ts#L145
Repository: go
Issue: x/sys/unix: UnixCredentials etc. missing on FreeBSD
Labels: NeedsDecision

On Linux, the definitions to pass Unix credentials over sockets via `SCM_CREDENTIALS` like [Ucred](https://pkg.go.dev/golang.org/x/sys/unix#Ucred) are exposed and there are helper functions like [UnixCredentials](https://pkg.go.dev/golang.org/x/sys/unix#UnixCredentials) to convert between raw and structured representations. FreeBSD has a similar capability via `SCM_CREDS` (see its [unix manpage](https://www.freebsd.org/cgi/man.cgi?query=unix&sektion=4)), which is not part of `x/sys` right now. This is not POSIX-standardized as far as I can tell.

At the minimum, we could include `struct cmsgcred` as part of the Go types (I'm happy to contribute here). Ideally we'd also add matching FreeBSD-implementations for `UnixCredentials` and `ParseUnixCredentials`, though signature and semantics would be slightly different (on FreeBSD, it's recommended to pass a zeroed buffer since the kernel apparently fills the fields, while on Linux the sender can explicitly set the fields as long as it has appropriate privileges).
Repository: go
Issue: x/tools/gopls: translate go.work conflicting replacement errors to quickfixes or a command to run.
Labels: FeatureRequest,gopls,Tools,gopls/workspace

![Screen Shot 2022-03-16 at 9 54 23 AM](https://user-images.githubusercontent.com/4999471/158605692-da378944-f608-4f47-ad95-0984107c5e99.png)

### What did you do?

Checkout kubernetes repo, and create a go.work file including all modules in the repo except those in vendor.
A better, simpler repro case can be constructed by creating a workspace with conflicting modules (I will take a look if I can create a simpler repro with gopls test setup later if gopls experts cannot help with it).

### What did you expect to see?

Notifications popup with "Fix This" button :-) or
Diagnostics with quickfix associated.

### What did you see instead?

Verbose error messages.

Go command is giving a specific command to run already. I wonder if we can parse the message, replace [override] part, and suggest it as a quickfix.

cc @findleyr @matloob
Repository: go
Issue: cmd/go: work edit help text
Labels: Documentation,NeedsInvestigation,GoCommand

In the following two lines, should the text "writing it back to go.mod." be "writing it back to go.work."

https://github.com/golang/go/blob/1eb1f621da20d7c93ac0312e59c08afbde4d9f56/src/cmd/go/internal/workcmd/edit.go#L61

https://github.com/golang/go/blob/1eb1f621da20d7c93ac0312e59c08afbde4d9f56/src/cmd/go/internal/workcmd/edit.go#L64

using `go version go1.18 windows/amd64`
Repository: pytorch
Issue: Gradients tests are very time consuming
Labels: module: autograd,module: ci,triaged

Per the discussion in https://github.com/pytorch/pytorch/issues/72368 the `TestGradientsCPU` tests generated by `test_ops` are almost an hour long.
I would expect the other device version to be similar cost but will run on much more expensive machines.

While it is expected as a lot of things run there, we should double check:
- Are there any particular test that are especially slow?
- Are there features from gracheck that we would like to move to periodic?
- Are there devices that could be moved to periodic?
- More?

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: repeat_interleave is not meta friendly; not transform friendly either
Labels: triaged,tensor subclass

### 🐛 Describe the bug

AutogradImplicitComposite looks like this:

```
Tensor repeat_interleave(
    const Tensor& self,
    int64_t repeats,
    c10::optional<int64_t> dim,
    c10::optional<int64_t> output_size) {
  at::Tensor repeats_ =
      at::empty(1, self.options().dtype(at::kLong)).fill_(repeats);
  return at::native::repeat_interleave(self, repeats_, dim, output_size);
}
```

Use of options in a composite means bad for transforms and subclasses. Also because the statically known repeats gets turned into a tensor there is no way for this to be run with meta tensors (int64_t repeats we know what the output size is, but we lose it when it becomes a meta tensor).

https://github.com/pytorch/pytorch/pull/51869 probably would have helped but the PR died on the vine.

### Versions

master
Repository: godot
Issue: Distracting coloured text on Output Panel
Labels: discussion,topic:editor

### Godot version

3.5 betas

### System information

Windows 10, Nvidia

### Issue description

The output panel now has coloured text for the 'Debugger' section. 
The text is yellow if a warning is found, red if an error.
Yet this was already  indicated more elegantly by a small circle to the left of the 'Debugger' text. 
It was yellow/red if errors or warnings were found. There is no need really for the text to be coloured.
The new way is more distracting if one spends hours on the editor.


### Steps to reproduce

Run project, make some debiberate syntax error in code. 
Observe outpanel text 'Debugger' in colour red.
Note the circle to the left of the text (it was the previous elegant way of notifing of error)

### Minimal reproduction project

Any project with some syntax error.
Repository: go
Issue: x/website: SumNumbers depends on map iteration order with float64
Labels: Documentation,NeedsDecision,website

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

Go 1.18 via playground.

### What did you do?

I added extreme float64 values to the input of the `SumNumbers` function from https://go.dev/doc/tutorial/generics.

https://go.dev/play/p/aQ1cotOVsEc

### What did you expect to see?

The function returns the same value consistently.

### What did you see instead?

Across 4 runs:
```
0 62.97 35.98 0
```
Re-running this may provide different results.

The function works correctly with `int64` because integer addition is associative. Addition is not associative with `float64` values, so the map order changes the result dramatically.
Repository: kubernetes
Issue: kube-proxy: We should be able to override bind addresses for healthz and metrics 
Labels: kind/bug,sig/network,lifecycle/rotten,needs-triage

### What happened?

When we use config for kube-proxy we cannot override the bind addresses for healthz and metrics.

### What did you expect to happen?

I expect the kube-proxy CLI argument to override the value from the configuration file.

### How can we reproduce it (as minimally and precisely as possible)?

A typical use case is, I want to expose the kube-proxy metrics only on the host IP, then I want to use the following pod template:

```yaml
      containers:
      - command:
        - /usr/local/bin/kube-proxy
        - --config=/var/lib/kube-proxy/config.conf
        - --hostname-override=$(NODE_NAME)
        - --healthz-bind-address=$(HOST_IP):10256
        - --metrics-bind-address=$(HOST_IP):10249
        env:
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName
        - name: HOST_IP
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: status.hostIP
```

But today it does not work kube-proxy will just ignore the `healthz-bind-address` and `metrics-bind-address` arguments

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:38:05Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:32:02Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>

</details>


### 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>
Repository: ant-design
Issue: TreeNode的过滤属性filterTreeNode，在设定treeData后初始默认不调用。导致展示出不需要的值
Labels: help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/checkable-antd-4-19-2-forked-z748e4?file=/index.js)

### Steps to reproduce
filterTreeNode应该是表示用户可控的筛选（过滤树状结构麻烦不说，大一点的数据还要涉及到内存里存在两份）
应该有如下默认逻辑。
```
useEffect(() => {
  if(typeof filterTreeNode === 'function') {
     invokeFilter();
  }
}, [treeData]);
```
现在我的最小复现例子，写了return false，表示现在一个都不需要展示。结果默认还是都展示出来了；

### What is expected?
同上

### What is actually happening?
默认没有过滤。确保展示的是用户设定过的筛选逻辑筛过的内容

| Environment | Info |
|---|---|
| antd | undefined |
| React | 18 |
| System | mac |
| Browser | chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: DispatchTimer is constantly running
Labels: Area-Performance,Issue-Bug,Product-Terminal,Priority-2

From an internal mail conversation titled "Terminal is always ticking":
> I notice that Terminal on my machine is constantly ticking, meaning XAML Tick. It looks like there is a DispatcherTimer constantly running, even when the app isn't in the foreground and even when it is minimized.

We should stop any DispatchTimers when Terminal is minimized.