sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Windows not appearing when adding node or opening settings in specific Godot Sessions
Labels: bug,platform:windows,topic:editor,needs testing

### Godot version

4.1 Stable

### System information

Windows 10

### Issue description

When trying to add a node in my Godot Project. I get a flash on the screen for a split second, I see a tiny blip of a window opening and closing in my taskbar, and then Godot effectively freezes. There is no mouse input anymore.

However, when adding a node, I am able to hit enter and a Node2D is added in my scene and typing something like "anim" will add an AnimatedSprite2D to the scene as long as I don't click anything

https://github.com/godotengine/godot/assets/38440991/5839857f-ed2a-41e9-bf2b-70153072eb8e



### Steps to reproduce

1. Open the project
2. Load into the test_level scene
3. Try to add a node to the player or test_level scenes
4. Window should not open

### Minimal reproduction project

[SidescrollerTutorial.zip](https://github.com/godotengine/godot/files/12889389/SidescrollerTutorial.zip)
Repository: pytorch
Issue: [ONNX][Exporter] Maintain support for exporter arguments export_params and keep_initializers_as_inputs
Labels: module: onnx,triaged

### 🚀 The feature, motivation and pitch

The [`ExportOptions`](https://pytorch.org/docs/main/onnx_dynamo.html#torch.onnx.ExportOptions) supported by the dynamo based exporter does not support the arguments `export_params` and `keep_initializers_as_inputs` that were previously supported in the torch-script based exporter.

These arguments are useful for scenarios where the data associated with the parameters in the exported model are actually sourced from elsewhere (for example from the `torch.nn.Module` in the case of [`ORTModule`](https://github.com/microsoft/onnxruntime/blob/dad70ad4e80fb6461925d33f331d26ff9c52bb6c/orttraining/orttraining/python/training/ortmodule/ortmodule.py#L27).

The lack of support for these arguments implies that we end up with a duplicated copy of the model parameters and need to manually move remove them in the exported model. This creates a memory bloat. The problem is further magnified if we have a distributed training scenario where the model is exported for each of the devices that share the same host (where we have multiple copies of the same exported model). This can be a bottleneck for large models.

If the exporter supports these arguments, the exported model will be considerably smaller in size and will not lead to a bloat in the host memory.

cc @BowenBao 

### Alternatives

_No response_

### Additional context

_No response_
Repository: transformers
Issue: MaskCLIP
Labels: New model

### Model description


MaskCLIP represents a transformative step in the realm of open-vocabulary universal image segmentation. Built upon the robust foundation of pre-trained CLIP models, it negates the need for additional finetuning or distillation. The core of MaskCLIP is its innovative Transformer-based MaskCLIP Visual Encoder. This encoder is meticulously designed to integrate mask tokens with a pre-trained ViT CLIP model, making it adept at both semantic and instance segmentation, as well as class prediction. One of MaskCLIP's standout features is its ability to efficiently harness the power of pre-trained dense and local CLIP features within its Visual Encoder. This design choice not only streamlines the segmentation process but also sidesteps the traditionally lengthy student-teacher training phase. Demonstrating its prowess, MaskCLIP has consistently outperformed existing methods on renowned datasets like ADE20K and PASCAL, especially in tasks of semantic, instance, and panoptic segmentation.

### Open source status

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

### Provide useful links for the implementation

project page  : https://maskclip.github.io
github : https://github.com/mlpc-ucsd/MaskCLIP
Repository: vscode
Issue: Use state service to cache machine / sqmId in `serverServices.ts`
Labels: debt,telemetry,perf-startup

Every server startup we seem to resolve machine ID and SQM ID without caching it:

https://github.com/microsoft/vscode/blob/4678919d52909efc7c4ab958a2e5c8f45d50ffc3/src/vs/server/node/serverServices.ts#L134-L140

I see no reason why the state service could not be instantiated on the server too to cache this.

//cc @isidorn
Repository: go
Issue: proposal: crypto/tls: Allow setting SignatureSchemes in Config
Labels: Proposal,Proposal-Crypto

It's a little different from the Issue 43549.

We are developing a program targeting multiple old platforms involving hardware smartcard and only PKCS#1 V1.5 Signature Scheme is supported on the client platform. We use only the signing part so it should hold for a while. We need to specify SignatureSchemes on the server side but it seems to be tricky. We can only implement it by specifying it to internal structures of each Certificate within the CertPool and it's ugly and dirty.

We assume it should be a common issue when it comes to old platforms. Please add official support so we can simply use tls.Config to specify it.

Thank you all and the golang, the best lang ever.
Repository: vscode
Issue: Allow to disable atomic writes for user data
Labels: feature-request,config,file-io

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: **yes**

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.83.1
- OS Version: Ubuntu 22.04

Steps to Reproduce:

At a minimum, this issue applies to these two really important files I normally have as symlinks to point into my repo:
```
~/.config/Code/User/keybindings.json
.config/Code/User/settings.json
```

1. In a terminal, run `watch -n 0.5 ls -li ~/.config/Code/User/settings.json` to begin watching the inode number of the settings file. The inode number is the number at the start of the line. This command checks the inode number every 0.5 seconds. If the inode number changes, it means the file cannot be tracked by other programs, because the file was destroyed and recreated entirely, with a new inode number.
2. Open VSCode. 
3. Press Ctrl + P to open the command palette. Search for `Preferences: Open User Settings (JSON)`. Open it. Press Ctrl + S to save the settings file. You don't need to change anything. Just press Ctrl + S. This triggers a settings file save, and instead of just updating the file in-place like a normal program would do, or like VSCode *used to* do, it wipes the file and creates a whole new inode number!

This means there is now no way for me to either symlink *or* hardlink to the settings files to back them up in my git repo like I've been doing. Both types of links get wiped by the save function in VSCode since it's wiping the settings file and creating a new one with an entirely new inode number.
Repository: storybook
Issue: [Bug]: some properties are not working in docs
Labels: bug,needs triage

### Describe the bug

I have boolean property named 'open' to show tooltip, if it is false tooltip should be hide and if its true tooltip should show, in canvas also same control not working. I am getting this issue after upgrading to storybook v7.4.5, in  v6.5 its working fine.

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: material-ui
Issue: [InputBase] Reptitive name of Adornment props for InputBase
Labels: component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

MUI have 2 different Adornment: startAdorment and endAdornment. And while implementation, position of Adornment is actually decided by InputAdornment's position prop. So, I think, MUI can remove this 2 different props (startAdornment and endAdornment) and rather keep a single prop called as "Adornment", This will remove repitition of props. Anyways, position of Adornment is decided by InputAdornment's position prop only.

### Examples 🌈

current Implementation
`<InputBase endAdorment={<InputAdornment position="end"><EventIcon/></InputAdornment>}/>`

 and

`<InputBase startAdorment={<InputAdornment position="start"><EventIcon/></InputAdornment>}/>`

Suggested implementation

`<InputBase adorment={<InputAdornment position="end"><EventIcon/></InputAdornment>}/>`

`<InputBase adorment={<InputAdornment position="start"><EventIcon/></InputAdornment>}/>`

### Motivation 🔦

We have InputBase component for all our TextBox requirement throughout our project. So we are very much dependent on MUI Docs for it

While going through Docs and example implementation, I saw following 2 different variations of implementing on MUI TextField Page

`<TextField
          label="With normal TextField"
          id="filled-start-adornment"
          sx={{ m: 1, width: '25ch' }}
          **InputProps={{
            startAdornment: <InputAdornment position="start">kg</InputAdornment>,
          }}**
          variant="filled"
        />`

And 
`<FilledInput
            id="filled-adornment-amount"
            **startAdornment={<InputAdornment position="start">$</InputAdornment>}**
          />`

To my surprise, second implementation worked right for InputBase after trial and error and surfing through stackoverflow

I already saw one similar issue for first implementation being raised, but it was for docs. I raised this issue for feature addition so that Adornment can be implemented in a simple way. Also requesting your team, if its possible to maintain consistency on implementation throughout the project as you can see 2 different implementations here.

Let me know if I can contribute in this respect and raise PR
Repository: storybook
Issue: [Bug]: Using dates in expect statements with the interactions add-on causes Storybook to crash
Labels: bug,good first issue,help wanted,addon: interactions,sev:S2

### Describe the bug

Using _dates_ in `expect` statements (from @storybook/jest) within interaction tests (@storybook/addon-interactions) causes storybook to crash when running in the browser, resulting in a blank screen and the following error in the console:

> Uncaught TypeError: e.split is not a function or its return value is not iterable

![image](https://github.com/storybookjs/storybook/assets/11296166/41ff0035-f564-4c17-9c7e-e3f6a5b9e844)

The expect in the following play function causes the error for example:
```
  play: () => {
    const date1 = new Date(Date.UTC(2020, 8, 9));
    const date2 = new Date(Date.UTC(2020, 8, 9));
    expect(date1).toEqual(date2);
  }.
```

The tests pass when running in test-runner.

The error looks to originate from this line in @storybook/addon-interactions where the dates are being rendered for display in the addon-interactions panel (the split string function is being called on the date object): https://github.com/storybookjs/storybook/blob/e9f2e1f7112fc5e391b82ff2d871d3656f5cdfee/code/addons/interactions/src/components/MethodCall.tsx#L345

The error occurs in v7.4.6 and the latest, as in the reproduction linked to below. The error did not occur in v6.5.16 which we were previously on.

### To Reproduce

This error occurs in v7.4.6 of Storybook, also in the latest as in the reproduction link below. The error did not occur in v6.5.16.

Line #35 of Button.stories.js in the reproduction results in the error (i.e. white screen and error in console):

https://stackblitz.com/edit/github-pjbwb9?file=stories%2FButton.stories.js

### System

_No response_

### Additional context

_No response_
Repository: kubernetes
Issue: The description of NodeStatusUpdateFrequency is inaccurate.
Labels: kind/bug,sig/node,sig/docs,triage/accepted

### What happened?

```
// nodeStatusUpdateFrequency is the frequency that kubelet computes node
// status. If node lease feature is not enabled, it is also the frequency that
// kubelet posts node status to master. In that case, be cautious when
// changing the constant, it must work with nodeMonitorGracePeriod in nodecontroller.
NodeStatusUpdateFrequency metav1.Duration
```
### What did you expect to happen?

I noticed that the comment about NodeStatusUpdateFrequency is as before, `when NodeLease is enabled by default, it should not automatically post node status to the master.`
but as another description "Remove NodeLease feature gate that was graduated and locked to stable in the 1.17 release."  According to the description, the kubelet after 1.17 will never posts node status to master frequencyly.

However, in the updateNodeStatus function, the kubelet periodically updates the node's status to the API server. The code is as follows:
`updatedNode, _, err := nodeutil.PatchNodeStatus(kl.heartbeatClient.CoreV1(), types.NodeName(kl.nodeName), originalNode, node)
`

So, in my view, the statement, "If the node lease feature is not enabled, it is also the frequency that
// kubelet posts node status to master," should be changed to "it is also the frequency that kubelet posts node status to master."

Is there an issue with my understanding?

### How can we reproduce it (as minimally and precisely as possible)?

no

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</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: deno
Issue: ext/url: start implementing `URLPatternList`
Labels: feat,ext/url,important for fresh

This is a request to follow along https://github.com/WICG/urlpattern/pull/166 and start drafting an experimental implementation of `URLPatternList`.

The topic of an optimized `URLPatternList` surfaced again, triggered by `URLPattern` performance issues at https://github.com/denoland/deno/issues/19861 recently observed in the wild.

As a real world usecase, it was found out that Fresh currently performs a series of `URLPattern.exec(url)` on every request (see https://github.com/denoland/fresh/issues/1931 for more details).
Each time, the `url` argument is the same constant string which has to go through a set of URL patterns to match against, with overall performance costs which are linear in the cardinality of the set of URL patterns.
It looks like this is the exact case for optimization that `URLPatternList` is aiming at.

For reference, there were these previous attempts to start wiring this in Deno in the past:
 * https://github.com/denoland/deno/pull/14502
 * https://github.com/denoland/deno/pull/14500
Repository: next.js
Issue: [ESLINT] "no-before-interactive-script-outside-document" lint error also occurs in layout.tsx
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/busy-varahamihira-72h4sq

### To Reproduce

[code sandbox](https://codesandbox.io/p/sandbox/busy-varahamihira-72h4sq) 
go to layout.tsx file and you can find an lint error

### Current vs. Expected behavior

#### Current
When using the app directory, a "no-before-interactive-script-outside-document" lint error also occurs in layout.tsx.

#### Expected
When using the app directory, there should be no "no-before-interactive-script-outside-document" error anywhere.

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
Binaries:
  Node: 16.18.1
  npm: 8.19.2
  Yarn: 1.22.17
  pnpm: 8.7.1
Relevant Packages:
  next: 13.5.5-canary.2
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

ESLint (eslint-config-next)

### Additional context

When using the app directory, a "no-before-interactive-script-outside-document" lint error also occurs in layout.tsx.

There's already a branch logic for the app directory in the lint config file, but it doesn't work properly. I've found a way to fix it and plan to submit a PR.
Repository: transformers
Issue: [i18n-<te>] Translating docs to <Telugu>
Labels: WIP

<!--
Note: Please search to see if an issue already exists for the language you are trying to translate.
-->

Hi!

Let's bring the documentation to all the <languageName>-speaking community 🌐 (currently 0 out of 267 complete)

Who would want to translate? Please follow the 🤗 [TRANSLATING guide](https://github.com/huggingface/transformers/blob/main/docs/TRANSLATING.md). Here is a list of the files ready for translation. Let us know in this issue if you'd like to translate any, and we'll add your name to the list.

Some notes:

* Please translate using an informal tone (imagine you are talking with a friend about transformers 🤗).
* Please translate in a gender-neutral way.
* Add your translations to the folder called `<languageCode>` inside the [source folder](https://github.com/huggingface/transformers/tree/main/docs/source).
* Register your translation in `<languageCode>/_toctree.yml`; please follow the order of the [English version](https://github.com/huggingface/transformers/blob/main/docs/source/en/_toctree.yml).
* Once you're finished, open a pull request and tag this issue by including #issue-number in the description, where issue-number is the number of this issue. Please ping @stevhliu and @MKhalusova for review.
* 🙋 If you'd like others to help you with the translation, you can also post in the 🤗 [forums](https://discuss.huggingface.co/).

## Get Started section

- [x] [index.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/index.md) https://github.com/huggingface/transformers/pull/20180
- [x] [quicktour.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/quicktour.md) (waiting for initial PR to go through)
- [ ] [installation.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/installation.md).

## Tutorial section
- [ ] [pipeline_tutorial.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/pipeline_tutorial.md)
- [ ]  [autoclass_tutorial.md](https://github.com/huggingface/transformers/blob/master/docs/source/autoclass_tutorial.md)
- [ ]  [preprocessing.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/preprocessing.md)
- [ ]  [training.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/training.md)
- [ ]  [accelerate.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/accelerate.md)
- [ ]  [model_sharing.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/model_sharing.md)
- [ ]  [multilingual.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/multilingual.md)

<!--
Keep on adding more as you go 🔥
-->
Repository: transformers
Issue: [i18n-<hi>] Translating docs to <Hindi>
Labels: WIP

<!--
Note: Please search to see if an issue already exists for the language you are trying to translate.
-->

Hi!

Let's bring the documentation to all the <languageName>-speaking community 🌐 (currently 0 out of 267 complete)

Who would want to translate? Please follow the 🤗 [TRANSLATING guide](https://github.com/huggingface/transformers/blob/main/docs/TRANSLATING.md). Here is a list of the files ready for translation. Let us know in this issue if you'd like to translate any, and we'll add your name to the list.

Some notes:

* Please translate using an informal tone (imagine you are talking with a friend about transformers 🤗).
* Please translate in a gender-neutral way.
* Add your translations to the folder called `<languageCode>` inside the [source folder](https://github.com/huggingface/transformers/tree/main/docs/source).
* Register your translation in `<languageCode>/_toctree.yml`; please follow the order of the [English version](https://github.com/huggingface/transformers/blob/main/docs/source/en/_toctree.yml).
* Once you're finished, open a pull request and tag this issue by including #issue-number in the description, where issue-number is the number of this issue. Please ping @stevhliu and @MKhalusova for review.
* 🙋 If you'd like others to help you with the translation, you can also post in the 🤗 [forums](https://discuss.huggingface.co/).

## Get Started section

- [ ] [index.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/index.md) https://github.com/huggingface/transformers/pull/20180
- [ ] [quicktour.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/quicktour.md) (waiting for initial PR to go through)
- [ ] [installation.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/installation.md).

## Tutorial section
- [ ] [pipeline_tutorial.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/pipeline_tutorial.md)
- [ ]  [autoclass_tutorial.md](https://github.com/huggingface/transformers/blob/master/docs/source/autoclass_tutorial.md)
- [ ]  [preprocessing.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/preprocessing.md)
- [ ]  [training.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/training.md)
- [ ]  [accelerate.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/accelerate.md)
- [ ]  [model_sharing.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/model_sharing.md)
- [ ]  [multilingual.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/multilingual.md)

<!--
Keep on adding more as you go 🔥
-->