sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Consecutive lines are not moved down when issuing the 'Move Line Down' command
Labels: bug,editor-multicursor

<!-- ⚠️⚠️ 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.82.2
- OS Version: Latest archlinux

Steps to Reproduce:

1. Paste the following text:
```
select
select



select


```
2. Select all three words with Ctrl+D
3. Try to move the lines down with Alt+Down arrow


What happens:
The second line gets deselected and doesn't get moved down.


What should happen:
All three lines get moved down.
Repository: nvm
Issue: NVM doesn't know the installed lts version is outdated.
Labels: installing node,needs followup,pull request wanted

```sh
$ nvm use --lts
Now using node v16.17.0 (npm v8.15.0)

$ nvm install --lts
Installing latest LTS version.
Downloading and installing node v18.18.0...
Downloading https://nodejs.org/dist/v18.18.0/node-v18.18.0-linux-x64.tar.xz...
############################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v18.18.0 (npm v9.8.1)
```

I typed `nvm use` while node 16 was installed as the lts version. It used 16 without actually checking whether it was the current LTS version. Would be good if it did the check.
Repository: tensorflow
Issue: `tf.device` context manager does not restore `cudaCurrentDevice` under some conditions
Labels: stat:awaiting tensorflower,type:bug,comp:apis,comp:gpu,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

binary

### TensorFlow version

2.13

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04.5 LTS

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

12.0

### GPU model and memory

_No response_

### Current behavior?

When using `tf.device` context manager, the current device of cuda runtime remains "dirty" even after exiting the context manager. This happens when: 1. tensorflow is initializing GPU context on this line (tf.device), 2. there is no materialization of tensors on GPU.

For context, keeping a clean state of current device context is important to keep tensorflow in sync with other GPU based libraries such as [cuDF](github.com/rapidsai/cuDF). [RMM](github.com/rapidsai/rmm) memory allocators also depends on the assumption that the context stays the same throughout the lifetime of allocations.

### Standalone code to reproduce the issue

```shell
https://gist.github.com/isVoid/9eded87fca35e86a2c2dc85f603383c2
```


### Relevant log output

```shell
# Log output of the first cell. The second and third current device context should be 0.

(<cudaError_t.cudaSuccess: 0>, 0)
(<cudaError_t.cudaSuccess: 0>, 7)
(<cudaError_t.cudaSuccess: 0>, 7)
(<cudaError_t.cudaSuccess: 0>, 0)
```
Repository: deno
Issue: Support `import.meta.url` / `import.meta.resolve` in the REPL
Labels: feat,cli,repl,deno jupyter

Right now these don't work because this is a script context. We should create a fake `__importMeta` at the start of the REPL, and transpile the `import.meta` calls to that. This would be in line with the transpilation that what we do for static import statements.

This is probably also helpful for Jupyter.
Repository: transformers
Issue: A new category for recsys
Labels: Feature request

### Feature request

A new category in HuggingFace (both in datasets and models) for recommendation systems.

### Motivation

HuggingFace has a rich ecosystem of diverse sets of datasets and models. We have model types ranging from

1. Language Models
2. Graph Models 
3. Vision models
4. Multimodal etc

And same goes for datasets. However, the one significant category that I did not find and is missing is the recommendation system. Recommendation systems are very important for enterprises and it is one of the most interesting dynamic fields in Machine Learning. 

We can support recsys in several ways. There are recsys for tabular data, tabular + NLP data, vision data, etc. And the same goes for models too. And while I just started learning and doing some research on recys, I am seeing that I do not have any SOTA models present in huggingface. 

For example, I can not have any method going like this right now. Where, I do not care much about the candidate generator but simply take a SOTA candidate generator and focus on my ranker model. 

```python
from transformers import RecSysVocab
from transformers import CandidateGen


# this can path to csv or a matrix with user's properties 
user_vocab_lookup_table = RecSysVocab.from_pretrained('/path/to/user.csv')
item_vocab_lookup_table = RecSysVocab.from_pretrained('/path/to/item.csv')

# build the candidate generator model
candidate_gen = CandidateGen.from_pretrained('some-sota-candidate-gen')

# now fit the model
candidate_gen.find_top_k_similarity(
    user_id = "some user id",
    user_columns = [...], # a vector with that user's propeties
    user_vocab_lookup_table = user_vocab_lookup_table,
    item_vocab_lookup_table = item_vocab_lookup_table
)
````

The above is a very simple (less accurate) pseudo code, just to have a glimpse of the interface. However it would be awesome to have something specifically for recommendation systems.

### Your contribution

I am not sure, if this issue is never thought of before or not. But it would be awesome on working on this, if the core maintainers and contributors are in the same page. RecSys is very diverse. Some of methods involves sequences well others involves these two stage approaches (candidate gen + filtering). So I feel like some discussion would be required on how to structure the modules and how to create to build those interfaces such that it matches with existing methods of huggingface. 

In terms of my contribution, I can help with these and exited to contribute on this, if I hear back form the community showing similar grounds of interest. Would love to contribute.
Repository: next.js
Issue: Top down generation using `generateStaticParams` only works if exported from parents `layout` component (multiple dynamic segments)
Labels: bug

### Link to the code that reproduces this issue

https://github.com/viktorronnback/generate-static-params-bug/

### To Reproduce

1. next build (npm run build)
2. Check the output in the terminal
3. Notice that only routes in `/layout/[parent]/[slug]/` are generated. Routes in `/no-layout/[parent]/[slug]/` are not being generated

![Screenshot from 2023-09-20 10-08-53](https://github.com/vercel/next.js/assets/30473214/b0f2f4de-ce1f-4eef-bc9a-9c551fd901e0)

### Current vs. Expected behavior

Currently no child pages are generated when exporting `generateStaticParams` from e.g. parents `page` component, only when `generateStaticParams` is exported in the `layout` component of the parent it generates paths. I expect `generateStaticParams` to generate child pages regardless of which parent component it is exported from or at least get an error when building that it must be declared in the layout component.

### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2
Binaries:
  Node: 18.15.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.7.5
Relevant Packages:
  next: 13.4.20-canary.40
  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)

App Router

### Additional context

This likely also relates to #53717 which I have been investigating. I would like to try creating a PR to solve this issue, if the intended behaviour is that it should be possible to export `generateStaticParams` from components other than the `layout` in a parent route. Otherwise I would like to add an error when building if parent routes contain `generateStaticParams`.

Note, it also does not work to export `generateStaticParams` from the parents `template` component.
Repository: godot
Issue: PacketPeerUDP and StreamPeerTCP latency gets higher with more connected clients
Labels: documentation,topic:network,performance

### Tested versions

v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 31.0.15.3742) - Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 Threads)

### Issue description


UDPServer or PacketPeerUDP gets big latency on LAN network
Its 27msec for only PING command between Server and 1 Client
But its about 50msec for only PING command between Server and 3 Clients

### Steps to reproduce

1. Start Project below
2. Run 2 or More Instances
![image](https://github.com/godotengine/godot/assets/129945583/35a0ee1a-2916-4df2-acf6-1b8bd2dd56e6)
3. Choose one windows press F2 to create Server
4. Choose other and press F1 to create Client
5. Get ping 27-50msec on LAN


### Minimal reproduction project (MRP)

[ServerUDP.zip](https://github.com/godotengine/godot/files/13817352/ServerUDP.zip)
Repository: rust
Issue: Build std with panic = "abort" errors with a bunch of duplicated lang items
Labels: A-diagnostics,T-compiler,-Zbuild-std,A-crates

### Code

```Rust
[profile.release]
panic = "abort"
```
```
rustup run nightly-2023-09-17 cargo rustc -p dune --profile release -Z build-std=std,core --target x86_64-pc-windows-msvc
```
The nightly version is not important, it's only what I was testing on.


### Current output
A bunch of these:

```Shell
error[E0152]: duplicate lang item in crate `core`: `sized`.
  |
  = note: the lang item is first defined in crate `core` (which `std` depends on)
  = note: first definition in `core` loaded from \\?\D:\repos\dune\target\x86_64-pc-windows-msvc\release\deps\libcore-8e933d06c178c4de.rlib, \\?\D:\repos\dune\target\x86_64-pc-windows-msvc\release\deps\libcore-8e933d06c178c4de.rmeta
  = note: second definition in `core` loaded from \\?\C:\Users\tachyon\.rustup\toolchains\nightly-2023-08-17-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib\libcore-b86a9ba077d96bbb.rlib
```


### Desired output

A nice message that said `panic_abort` must be included in `build-std` if compiled with `panic = "abort"`.


### Rationale and extra context

From @Nilstrieb:
rustc can't find a `panic_abort` in your self-built standard library, so it falls back to loading `panic_abort` from the sysroot. But that sysroot `panic_abort` then also brings in the rest of the sysroot, including `core`, so now you have two cores, one from your target dir and one from your sysroot. _This is bad._


### Other cases

_No response_

### Anything else?

_No response_
Repository: pytorch
Issue: test_memory_timeline fails on PPC due to extra temopraries
Labels: triaged,module: POWER,OSS contribution wanted,oncall: profiler

### 🐛 Describe the bug

Running the test on PPC64le with `python profiler/test_memory_profiler.py  -k test_memory_timeline` results in a failure. Printing the full diff yields an extra temporary between the first 2:
```
+             create                     TEMPORARY                   11(v0)          0.7 kB
+             destroy                    TEMPORARY                   11(v0)          0.7 kB
```

Raising the minimum size from 256 to 1024 to filter this allocation makes the test pass. So I assume it is to sensitive.

### Versions

PyTorch version: 2.0.1
Is debug build: False
CUDA used to build PyTorch: Could not collect
ROCM used to build PyTorch: N/A

OS: Red Hat Enterprise Linux Server release 7.6 (Maipo) (ppc64le)
GCC version: (GCC) 12.2.0
Clang version: Could not collect
CMake version: version 3.24.3
Libc version: glibc-2.17

Python version: 3.10.8 (main, Jul 25 2023, 10:52:38) [GCC 12.2.0] (64-bit runtime)
Python platform: Linux-4.14.0-115.19.1.el7a.ppc64le-ppc64le-with-glibc2.17


cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @nbcsm @gaoteng-git @tiffzhaofb
Repository: godot
Issue: Handle to add point to line2D does not appear on last line segment in a closed line2D
Labels: enhancement,topic:editor,topic:2d

### Godot version

4.2 Dev 5

### System information

Fedora Linux 38 (Workstation Edition)

### Issue description

 Title explains it its a very minimal and simple issue 

![Screenshot from 2023-09-19 14-52-13](https://github.com/godotengine/godot/assets/74463310/23b35172-2fd6-47dc-969f-b929e8ab3484)

no little green add point thing on the segment.

can probably be solved by using the polygons add point system when a line is closed 

### Steps to reproduce

A closed line2D

### Minimal reproduction project

N / A
Repository: godot
Issue: Error message when using texture from viewport inside itself
Labels: discussion,topic:rendering

### Godot version

4.2

### System information

Windows 11

### Issue description

Implementing a similar effect than describe in : https://www.youtube.com/watch?v=VSwVwIYEypY
I think it's intended but server spams an error :
`
RenderingDeviceVulkan::draw_list_bind_uniform_set: Attempted to use the same texture in framebuffer attachment and a uniform (set: 1, binding: 3), this is not allowed.
`
It's still works as expected, could this error be removed or ignored ?
Maybe it could be a warning clarifying that this has 1 frame delay.

*Maybe doing this is not recommended in that case this issue can be usefull to other people know why*

### Steps to reproduce

Project from the tutorial is raising the error : https://github.com/CBerry22/Godot-Water-Ripple-Simulation-Shader

### Minimal reproduction project

Create a viewport
Inside that viewport use the ViewportTexture from parent in a shader.
Repository: tensorflow
Issue: tf.linalg.cholesky output normal value on a complex64 matrix that is not positive definite.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.13.0

### Custom code

Yes

### OS platform and distribution

_No response_

### 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?

On a randomly generated matrix that is not positive definite, tf.linalg.cholesky outputs nan if the matrix's dtype is float and outputs 0 if the matrix' dtype is complex. It may be not appropriate especially when tf.linalg.cholesky outputs 0 on an invalid input without giving any abnormal behaviors. For your inference, np.linalg.cholesky will directly raises with error message when receiving non-positive definite matrix in float or complex data type.


### Standalone code to reproduce the issue

```shell
import tensorflow as tf
import numpy as np
import warnings
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
warnings.filterwarnings("ignore")
np.random.seed(1234)
array = np.random.rand(4,4).astype("complex64")
try:
    print("Numpy's result: ", np.linalg.cholesky(array))
except:
    print("Numpy crash.")

print("TensorFlow's result: ", tf.linalg.cholesky(tf.constant(array)))

array = np.random.rand(4,4).astype("float64")
try:
    print("Numpy's result: ", np.linalg.cholesky(array))
except:
    print("Numpy crash.")

print("TensorFlow's result: ", tf.linalg.cholesky(tf.constant(array)))
```


### Relevant log output

```shell
Numpy crash.
TensorFlow's result:  tf.Tensor(
[[0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j]], shape=(4, 4), dtype=complex64)
Numpy crash.
TensorFlow's result:  tf.Tensor(
[[nan  0.  0.  0.]
 [nan nan  0.  0.]
 [nan nan nan  0.]
 [nan nan nan nan]], shape=(4, 4), dtype=float64)
```
Repository: PowerToys
Issue: The Swiss Army Knife of WinTools - Plus one more?
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Develop a tool to clone a C: drive so users can upgrade to larger drives easily. I've spent over a week trying out (and $$$$) for tools that simply don't do the job. Is it really that hard?

### Scenario when this would be used?

When software developers (cough, Adobe) create "tools" that are total diskhogs and don't allow the user to place all the needed temp files on a "work" drive.

### Supporting information

_No response_
Repository: godot
Issue: `push_error` is hiding prints in editor output
Labels: bug,topic:editor,confirmed

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 Ti (NVIDIA; 31.0.15.3713) - AMD Ryzen 9 7900X 12-Core Processor (24 Threads)

### Issue description

`push_error` is hiding other prints in the editor output. The output counter are still showing the correct count. Choosing a different  message type filter refreshes the view and will show the hidden message.

### Steps to reproduce

Create a scene with a node and attach a script with content:

```gdscript
@tool
extends Node2D

func _ready():
	print("hello world")
	push_error("test")
	print("bye world")
```

Reload the scene and only
```
  ./core/variant/variant_utility.cpp:905 - test
hello world
```
is shown.

### Minimal reproduction project

N/A
Repository: godot
Issue: Closed Line2D flickers if Width Curve starts at 0.0
Labels: bug,topic:rendering,topic:2d

### Godot version

v4.2.dev5.official [e3e2528ba]

### System information

Godot v4.2.dev5 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Ti (NVIDIA; 31.0.15.3713) - 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz (12 Threads)

### Issue description

When moving the first or last point in a closed Line2D with the width curve starting at exactly 0.0 (the problem does not occur if the width starts at any other value, including 0.001), the connecting part between the start and end appears and disappears, which seems to be based on point position.
https://github.com/godotengine/godot/assets/98223724/60fab824-ec13-48bc-8367-7502ae8fa9c3



### Steps to reproduce

Create a Line2D, enable `Closed` and add a `Width Curve`, and select any preset (except for constant).

### Minimal reproduction project

N/A
Repository: flutter
Issue: [Android] Support Java 20
Labels: platform-android,tool,P2,team-android,triaged-android

Currently, Flutter tooling runs under the assumption that Java 19 is the highest version that Flutter supports (see `oneMajorVersionHigherJavaVersion` definition in [`gradle_utils.dart`](https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/android/gradle_utils.dart)). However, we are fairly certain that Flutter projects can build/run with Java 20 from personal development experience. Thus, we should take the necessary steps to change this assumption to Java 20 (at least) being the highest version that Flutter supports.

See https://github.com/flutter/flutter/pull/131444/files#r1297754683 for context.
Repository: ant-design
Issue: antdv5 组件App  popover、tooltip 等有滚动性能问题
Labels: Inactive,improvement

### Reproduction link

https://github.com/PlasmoHQ/examples/tree/6272c89994cb3a8ceab05c3820a95907e33b7cb2/with-antd 因为我的场景是做 Chrome 插件，所以复现步骤比较复杂，不过基本就是 Plasmo 的这个代码加上 App 组件

### Steps to reproduce

用 plasmo 官方最简单的 with-antd demo，在最外层套一个 antd App 组件
```typescript
import { App as AntdApp } from 'antd';
const MyApp = () => {
  return (
    <StyleProvider container={document.getElementById(HOST_ID).shadowRoot}>
      <AntdApp
        message={{
          getContainer() {
            return document.getElementById(HOST_ID).shadowRoot.querySelector(`#${SIDEBAR_ID}`);
          }
        }}
      >
        <Root pageType="sidebar">
          <App />
        </Root>
      </AntdApp>
    </StyleProvider>
  )
}

export default MyApp
```
然后 pnpm run dev 运行插件，在部分页面下，会一直报 wheel passive 警告，且对应页面的滚动丢帧。。。
比如这个页面  https://nofu20230915074220305.pingcode.com/pjm/projects/TES/backlog/65040b24fc6214f4bb8d9755   （已开放公开访问权限）
![img](https://github.com/ant-design/ant-design/assets/37991688/6a810ff7-e642-485e-9482-dc7a5757489f)

上述 warning 需要开启 chrome devtools all-level log 可以看到

**补充说明**
- 只要去掉 AntdApp 嵌套，然后不使用下面一条提到的部分组件没这个问题，但是去掉之后 message  modal 这些组件的全局使用会有问题，不符合规范
- 经过详细测试验证，去掉  AntdApp 之后，如果羡慕中包含像 tooltip   popover  List  等组件，也还是会有这个性能问题，翻了翻react-component 源码，确实 wheel 事件是未包含对 passive 的处理，https://github.com/react-component/virtual-list/blob/1410c665bf6713caafc81ef0dc7e2ed059535c19/src/List.tsx#L402
- 插件是运行在 shadowRoot 当中




### What is expected?

在 shadowRoot 中引用 App、Popover、tooltip、List 等组件，不会有性能问题，不造成滚动条丢帧卡顿

### What is actually happening?

在 shadowRoot 中引用 App、Popover、tooltip、List 等组件，会有性能问题，不造成滚动条丢帧卡顿

| Environment | Info |
| --- | --- |
| antd | 5.9.2 |
| React | 18.2.0 |
| System | darwin arm64 Darwin Kernel Version 22.5.0 |
| Browser | Chrome/116.0.0.0 |

---
这个 bug 是在 chrome 插件 content_script_ui 在 shadowRoot 时，部分宿主页面下面会有这个问题，比如这个页面  https://nofu20230915074220305.pingcode.com/pjm/projects/TES/backlog/65040b24fc6214f4bb8d9755   （已开放公开访问权限）

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->