sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: `alert`, `confirm`, `prompt` when used in Deno.test expects input before printing the message
Labels: bug,runtime,testing

Prelude. I know... Who is using input in tests. But consistency is nice.

Expected behaviour:

Messages provided to alert, confirm or prompt methods should print before user input is expected in all cases.

Actual behaviour:

When used in tests, user input is expected before the message of the functions.

Here is the 3 tests I wrote. 

```ts
Deno.test({ name: 'input - confirm', async fn (){
	const result = confirm('this should print first');
	console.log('result was:', result);
}})

Deno.test({ name: 'input - prompt', async fn (){
	const result = prompt('this should print first');
	console.log('result was:', result);
}})

Deno.test({ name: 'input - alert', async fn() {
	const result = alert('this should print first');
	console.log('result was:', result);
}})
```

I ran this command `deno --version && deno test tests/input.test.ts`

and got this output

```
$ deno --version && deno test -A tests/input.test.ts --filter input
deno 1.36.1 (release, x86_64-pc-windows-msvc)
v8 11.6.189.12
typescript 5.1.6
running 3 tests from ./tests/input.test.ts
input - confirm ...   
------- output -------
y  
this should print first [y/N] result was: true
----- output end -----
input - confirm ... ok (3s)
input - prompt ...
------- output -------
asd
this should print first result was: asd
----- output end -----
input - prompt ... ok (1s)
input - alert ...
------- output -------

this should print first [Enter] result was: undefined
----- output end -----
input - alert ... ok (787ms)

ok | 3 passed | 0 failed (6s)
```
Repository: transformers
Issue: Transformers documentation translation to Macedonian
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 @ArthurZucker, @sgugger 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) 
- [ ] [quicktour.md](https://github.com/huggingface/transformers/blob/main/docs/source/en/quicktour.md)
- [ ] [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: vscode
Issue: Color conversion to HSL lacks precision
Labels: bug,editor-color-picker

<!-- ⚠️⚠️ 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.81.1
- OS Version: Linux x64 6.2.0-27-generic

Steps to Reproduce:

1. On a css file use the color picker on a color `rgb(167,169,188)`
2. Click on the picker header and convert it to hsl - results in `hsl(234, 14%, 70%)`
3. Convert again to rgb - results in `rgb(168,170,189)`

There should be a way to configure the color picker to have precision on the conversion (or always have better precision), to allow the converted value to be `hsl(234.29, 13.56%, 69.61%)` like it happens browsers when converting the color using the developer tools (e.g. in Edge, Firefox, and Safari). This way we can convert the color back and forth between formats without changing the color.
Repository: vscode
Issue: Inactive notebook editor does not indicate dirty state in this case
Labels: bug,notebook

**Steps:**
* close all instances of vscode
* from the command line run `~/Desktop/test-js/new.ipynb ~/Desktop/test-ts/new.ipynb`
* this should open 2 tabs with 2 notebooks

=> 🐛 only the active editor reports dirty although the explorer shows a "2"

See image:



![Image](https://github.com/microsoft/vscode/assets/900690/ea91d4a5-8aac-4ff7-bcab-6f3b2ec0b2b8)
Repository: vscode
Issue: Multiple untitled notebook editors with same name but different associated path do not distinguish
Labels: bug,notebook

**Note:** this may well be related to https://github.com/microsoft/vscode/issues/190703 and https://github.com/microsoft/vscode/issues/191052

**Steps:**
* close all instances of code
* from the command line `code ~/foo/new.ipynb ~/bar/new.ipynb`

=> 🐛 2 notebooks open as tabs but do not distinguish each other from the description property


Here is how it should look like (with text files):



![Image](https://github.com/microsoft/vscode/assets/900690/e7484e56-38a7-48a2-b925-ed8f0373a99b)


And here is notebooks:



![Image](https://github.com/microsoft/vscode/assets/900690/b84ddb89-b999-4a13-b3ca-3c6e6fead9ed)


Once you have clicked the inactive tab and then back to the first tab, the issue resolves itself magically.

Tabs conditionally show the description part if multiple tabs have the same name. For that to work, the editor input needs to return a description:

https://github.com/microsoft/vscode/blob/ad94cf18189746d2e942fda257950901049b3af3/src/vs/workbench/contrib/notebook/common/notebookEditorInput.ts#L137-L143
Repository: excalidraw
Issue: Vim motions or keybindins
Labels: enhancement,richtext

Can we add vim motions and key bindings for text edition
Repository: pytorch
Issue: libtorch infer error : CUDNN_STATUS_INTERNAL_ERROR
Labels: oncall: jit

### 🐛 Describe the bug

# code for model export
```
traced_script_module = torch.jit.trace(model, \
  (data_dict['voxels'], data_dict['voxel_num_points'], data_dict['voxel_coords']))
traced_script_module.save(args.output_path)
```

# code for model infer
```
std::vector<torch::Tensor> output =
    net_.forward(torch_inputs).toTensorVector();
```

# question
model init is ok:
```
torch::Device device(device_type_, device_id_);
net_ = torch::jit::load(model_file_, device);
net_.eval();
```
The error occurs when running the forward function:
![image](https://github.com/pytorch/pytorch/assets/39874362/7610a502-774f-42b3-98ba-fc7b030e47a0)


### Versions

pytorch 1.7.0

libtorch 1.7.0
cudnn 8.0.4.30
cuda 11.1

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: storybook
Issue: [Bug]: React component seems to be mounted twice when a story render function uses the args parameter
Labels: bug,has workaround,sev:S2

### Describe the bug

When using the `args` parameter in the render function of a Storybook story, the React component appears to be mounted twice. This behavior is causing issues, especially when using a custom hook directly in the story.

### To Reproduce

1. Go to the provided [StackBlitz link](https://stackblitz.com/edit/github-56csk3?file=stories%2FButton.stories.tsx).
2. Open the the Button stories `Working` and `Not Working` and observe the browser console to see the different behaviour of the two stories.

- **Working:** The hook in the render function works as expected, it logs a message to the console on each second click on the button
- **Not Working:** The component seems to get mounted twice. One instance seems to behave correctly the other one does not update it's state. As a result it logs once on each click and twice on each second click. The only difference between the two stories seems to be the args parameter gets passed into the render function.

https://stackblitz.com/edit/github-56csk3?file=stories%2FButton.stories.tsx


### System

```shell
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-essentials: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/addon-interactions: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/addon-links: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/addon-onboarding: ^1.0.8 => 1.0.8 
    @storybook/blocks: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/nextjs: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/react: ^7.4.0-alpha.0 => 7.4.0-alpha.0 
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

I understand that the observed behavior might be intentional or could potentially be influenced by the implementation of the custom hook. While I've tried to isolate the issue to the best of my ability, it's possible that there are factors I'm not aware of that could contribute to this behaviour.

Any assistance, guidance, or ideas on how to approach this issue would be highly valued. Thank you in advance for your help.
Repository: material-ui
Issue: [Select][joy-ui] Increase max-height
Labels: bug 🐛,component: select,design

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. 
2.
3.


### Current behavior 😯

_No response_

### Expected behavior 🤔

_No response_

### Context 🔦

https://github.com/mui/material-ui/pull/36156/files#r1302777804

It also feels like on Material UI and Joy UI, we should have a min-width set, it can feel too narrow when all the values are short.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: pytorch
Issue: DISABLED test_conv_stride_constraints (__main__.CPUReproTests)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](http://torch-ci.com/failure/inductor%2Ftest_cpu_repro.py%3A%3ACPUReproTests%3A%3Atest_conv_stride_constraints)).

I will take a look at this further locally, currently unsure why this shows up on ROCm for a CPU test.

cc: @jithunnair-amd 

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @hongxiayang
Repository: node
Issue: Structured log package in node core
Labels: feature request

### What is the problem this feature will solve?

To have a structured log package available in stdlib so that all npm modules can log in a single fashion instead of 

 - logging to console
 - not logging 
 - Having some arbitrary logger interface
 - Emitting random log events 
 - Worst case: they literally depend on Winston and it’s 200 transitive dependencies

### What is the feature you are proposing to solve the problem?

Implement something like https://go.dev/blog/slog

### What alternatives have you considered?

_No response_
Repository: next.js
Issue: Importing next/dynamic with a .js extension removes chunks from head
Labels: bug,Lazy Loading

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:               
      Platform: win32               
      Arch: x64                     
      Version: Windows 10 Enterprise
    Binaries:                       
      Node: 18.16.0                 
      npm: N/A                      
      Yarn: N/A                     
      pnpm: N/A                     
    Relevant Packages:              
      next: 13.4.20-canary.2         
      react: 18.2.0                 
      react-dom: 18.2.0             
      typescript: 5.1.6             
    Next.js Config:                 
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Dynamic imports (next/dynamic), Metadata (metadata, generateMetadata, next/head), TypeScript

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/tgrassl/next-dynamic-head-bug-poc

### To Reproduce

1. Switch to moduleResolution `nodeNext` or `node16` in the tsconfig
2. Add the `.js` file extension to your imports as required by typescript in this moduleResolution mode
3. Run `next build`
4. Observe the following inside the build output:
	- the react-loadable-manifest includes the dynamically loaded chunks
	- The generated css + js chunks for the dynamic module are not included in the `head` of `index.html`
6. Remove the `.js` extension from `import dynamic from 'next/dynamic.js'`
7. Run `next build`
4. Observe the following inside the build output:
	- the react-loadable-manifest includes the dynamically loaded chunks
	- The generated css + js chunks for the dynamic module are now included in the `head` of `index.html`

### Describe the Bug

If you add the `.js` file extension to the `next/dynamic` import in an ESM project with moduleResolution `nodeNext` or `node16` next ignores the generated chunks when collecting the required scripts/styles for the head of the page. This leads to hydration errors in dev mode and FOUC as the styles/scripts are only added to the head after the client hydrates.

This could be the culprit: https://github.com/vercel/next.js/blob/a759711cab5d842c4b83b00988432f4fe3324170/packages/next-swc/crates/next-transform-dynamic/src/lib.rs#L134C42-L134C42

**Possible Fixes**

1. Remove the `.js` extension from `next/dynamic` imports and ignore the error for typescript
2. Use moduleResolution `bundler`, so no `.js` extensions are required (Would be the more appropriate solution for next, but some IDEs like IntelliJ don't support it properly yet)


### Expected Behavior

The dynamically loaded module chunks/styles should always be included in the head tag of the generated page.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: angular
Issue: Animation glitch when state changes before :enter animation is done
Labels: area: animations

### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

I noticed it quite a while ago when loading something super fast in a modal right after opening it.
The loader with :enter and :leave opacity animation would "exit the scene" in a very glitchy way.

I was able to build a reproduction after facing a similar issue, again involving a modal, a loader and another animated component.

The best I can describe this is if you load something quick enough and the data state and/or loader state affect rendering of animated elements that have :enter and :leave animation, the :leave animation doesn't work smoothly most of the time.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-6xqxh4

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 14.2.10
Node: 16.13.1
Package Manager: yarn 1.22.15
OS: win32 x64

Angular: 14.2.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker       

Package                            Version        
------------------------------------------------------------
@angular-devkit/architect          0.1402.10      
@angular-devkit/build-angular      14.2.10        
@angular-devkit/core               14.2.10        
@angular-devkit/schematics         14.2.10        
@angular/cdk                       14.2.7
@angular/cli                       14.2.10        
@angular/fire                      7.5.0
@angular/material                  14.2.7
@angular/material-moment-adapter   14.2.7
@schematics/angular                14.2.10        
rxjs                               7.8.0
typescript                         4.8.4
webpack                            5.76.0
```


### Anything else?

Found way before Angular 14 and reproduced with Angular 16.

I'm not sure if this is a regression.

P. S. The content of the glitching `<app-expand-y *ngIf="!list.length"></app-expand-y>` doesn't really matter, you can uncomment other lines inside of it and see it yourself.

Play around with the reproduction.
**The glitch only appears when you press the button "Open modal that loads data quickly".**
Also it may not appear every time, so try at least few times.
Also playing around with animation timing and fake API call timing can help.
Repository: angular
Issue: Element loses animation style on route animation
Labels: area: animations

### Which @angular/* package(s) are the source of the bug?

animations, router

### Is this a regression?

No

### Description

I have a route animation between 2 components (A and B).  Component A has a element which can be toggled between collapsed or expanded which also uses a Angular animation. 

The issue is that when I collapse the element on component A and then navigate to component B the collapsed element becomes expanded, because it looses the styling (height: 40px) set by the angular animation on enter.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-vkfgng

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
"@angular/cli": "~14.0.0",
"@angular/core": "^16.2.1",
"typescript": "~4.7.2"
```


### Anything else?

_No response_
Repository: pytorch
Issue: Add caffe2 ideep/onednn tests to OSS CI
Labels: oncall: releng,module: ci,triaged,module: mkldnn

### 🐛 Describe the bug

Following PR https://github.com/pytorch/pytorch/pull/97957 that updates ideep have failed in these tests internally:
https://github.com/pytorch/pytorch/tree/main/caffe2/python/ideep

caffe2 module is still used intrnally a lot. Hence we want to enable OSS CI execute ideep tests from time to time.
Perhaps we should be adding these tests as periodic.


### Versions

2.1.0

cc @seemethere @malfet @pytorch/pytorch-dev-infra @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen
Repository: tensorflow
Issue: tf.linalg.pinv isn't 
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

binary

### TensorFlow version

2.6.22

### Custom code

No

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Pinv should give similar gradient to inv. Here's the code snippet and result.
![image](https://github.com/tensorflow/tensorflow/assets/10631563/de9cdb82-1c93-4a18-a79e-95c0b0834ae6)


![image](https://github.com/tensorflow/tensorflow/assets/10631563/cfdadbb9-5506-4181-a868-69830c5ee96b)


### Standalone code to reproduce the issue

```shell
See figures in behavior section.
```


### Relevant log output

_No response_
Repository: godot
Issue: Change window size to monitor resolution cause stuck  if borderless is set to true
Labels: bug,topic:gui

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Godot v4.1.1.stable - Windows 10.0.22000 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 30.0.14.7212) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)

### Issue description

**issue requires two conditions**  
- set Borderless to true
- window size is equal to monitor resolution(in my case, it is `1920×1080`)

**when conditions are met， project will stuck**

### Steps to reproduce

- Set `Borderless` to true in project settings,
-  and then run the project, 
-  select `1920×1080` in optionbutton, 
- window size switch to `1920×1080` from the default size `1152 ×648`,  
- and then it will stuck, if not, change `1920×1080` to whatever your monitor resolution is.

**How optionsbutton controls window size**
```
func _on_option_button_item_selected(index: int) -> void:
	var base_window_size : Vector2
	match index:
		0:  # 915 × 515
			base_window_size = Vector2(915, 515)
		1:  # 1152 × 648
			base_window_size = Vector2(1152, 648)
		2:  # 1920 × 1080
			base_window_size = Vector2(1920, 1080)
	DisplayServer.window_set_size(base_window_size)
```

### Minimal reproduction project

[godot4.1-minimal-reproduction.zip](https://github.com/godotengine/godot/files/12419799/godot4.1-minimal-reproduction.zip)
Repository: ant-design
Issue: 【cascader】同一省份中选中某个位于底部的某个市，然后切换到另一个省份时，市的一列没有默认回到顶部
Labels: help wanted,Inactive,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/lucid-framework-8cczdv)

### Steps to reproduce

同一省份中选中某个位于底部的某个市，然后切换到另一个省份时，市的一列没有默认回到顶部

### What is expected?

切换到另一个省份时，市的一列能够默认回到顶部

### What is actually happening?

切换到另一个省份时，市的一列没有默认回到顶部

| Environment | Info |
| --- | --- |
| antd | 5.8.4 |
| React | 18.2.0 |
| System | Mac |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->