sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: FR: Add TS config option to disable "<some regex feature> is only available when targeting 'es2018' or later.".
Labels: Suggestion,In Discussion

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

**Search terms for existing issues**

"regex", "regular expressions"

**Problem**

The Google TS build infrastructure runs the TypeScript compiler with a centrally defined `target` language = "ES2016" for edit-refresh & testing. For production, users can still target newer language versions, but for various reasons our edit-refresh setup is stuck on this older language version.

This means that with TS 5.5 we start seeing build errors like "This regular expression flag is only available when targeting 'es2018' or later.".

Our current workaround will be either using the `RegExp` constructor or adding a patch to our compiler fork.

**Proposal**

Add a TS config option to toggle whether these sorts of errors are emitted at all.

**Use cases**

I realize that Google infra's situation is unusual, so this might not be a generally useful proposal & understand if you don't support this.

However, some possibilities I could imagine for someone setting an older `target` language than necessary for the browsers they support might be:

- dependance on some semantics of the transpiled code, e.g. because of https://github.com/angular/angular/issues/31730
- some other part of the build toolchain not supporting newer syntax.
Repository: ollama
Issue: allow temperature to be set on command line ( w/out using a modelfile )
Labels: feature request


would be super helpful to set temperature for models via command line, rather than having to create a separate model file for every model and temperature combination.
Repository: godot
Issue: Landscape and Reverse Landscape orientation in iOS are in opposite direction that they are in Android
Labels: bug,platform:ios,topic:porting,breaks compat

### Tested versions

- Reproducible in: v4.2.2.stable.official

### System information

Godot v4.2.2.stable - macOS 14.5.0 - Vulkan (Mobile) - integrated Apple M3 Pro - Apple M3 Pro (11 Threads)

### Issue description

When you set orientation property in project settings to 'Landscape' or 'Landscape Reverse' iOS and Android have different directions.

![orientation-01](https://github.com/godotengine/godot/assets/33467096/6f13d205-74de-45bc-88c6-618247ded7f8)


### Steps to reproduce

Try changing orientation property between Landscape and Landscape Reverse

### Minimal reproduction project (MRP)

[orientation_issue.zip](https://github.com/user-attachments/files/16034452/orientation_issue.zip)
Repository: go
Issue: x/telemetry/counter/countertest: add countertest.Close
Labels: NeedsFix,telemetry

The countertest package exists to test telemetry instrumentation, with a `countertest.Open(dir)` API to initialize the counter file in a temp directory.

But on Windows, we can't clean up that directory while the counter file is open. I think we should add a `countertest.Close()` function to close the counter file.

This is non-trivial: the file mapping logic is complicated, and likely assumes that the file stays open.
Repository: vscode
Issue: BUG: In process explorer if user has cyrrilic symbols in name it will be displayed by non displayable symbols ("question mark" symbol)
Labels: bug,help wanted,workbench-diagnostics,confirmation-pending

<!-- ⚠️⚠️ 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. -->
Version: 1.90.2
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
OS: Windows_NT x64 10


Steps to Reproduce:

1. Open process explorer
2. Hover mouse cursor over any process (ex. GPU)
3. User with Cyrillic symbols in name is displayed incorrectly (will be displayed by non displayable symbols "question mark" symbol)

![зображення](https://github.com/microsoft/vscode/assets/1023918/81994510-55f7-4620-980e-909b77b43936)
Repository: vscode
Issue: Review docs for issues and triage bot
Labels: under-discussion,issue-bot

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
There are comments in old issues that never got the triage bot review, that ask what should happen then:

> Hey, I saw that issue #198381 got a "[VSCodeTriageBot](https://github.com/VSCodeTriageBot)" response and added to the backlog.  How do we do that for old issues that existed before the TriageBot?
I know it's bad GitHub form, but I'm tempted to re-create this issue (linking to this one) so that we can ping the TriageBot with our votes.  I think this vital feature has fallen into a black hole.

_Originally posted by @J-Sorenson in https://github.com/microsoft/vscode/issues/43026#issuecomment-2142608063_

Some comments in other issues that mention the triage bot closing the issue without anyone revisiting it and reading the new comments for consideration:

> @bpasero  I think you should train your Tiragebot better. Closing this without acknowledging any of the later comment seems questionable

_Originally posted by @escamoteur in https://github.com/microsoft/vscode/issues/203326#issuecomment-2048227865_

As well as a comment raised by me in this same issue questioning what happens when an issue is closed and then _**later**_ gets to the 20 up-votes mark:

> What happens now that it has already gained more than those 20 upvotes? Does it need a new mark? Will this not be considered then? If someone else wants this feature should they forget about it or should they create a new one? Those are not clear to me. Is there some place where these questions are documented (like a FAQ or something)?

_Originally posted by @FMorschel in https://github.com/microsoft/vscode/issues/203326#issuecomment-2151128502_
            
Also, [the docs](https://github.com/microsoft/vscode/wiki/Issues-Triaging#our-triaging-flow) mentioned by the triage bot don't ever say anything related to any of those things.

### Summary

I guess that the questions here would be:

- What happens with old opened issues that never got the triage bot review?
- What happens to issues closed that people are still interested in? Should they get a new mark of up-votes or be recreated (I agree with @J-Sorenson and consider this a bad GitHub behaviour)?

I'm not sure this is the exact place for this, but if it isn't please let me know where it would fit.
Repository: flutter
Issue: [DisplayList] Remove support for inverse-fill path types
Labels: engine,P3,team-engine,triaged-engine

Skia paths, used by native code to implement Flutter paths, supports inverted fill types where the interior of the path is inverted (out to infinity in all directions).

Flutter's Dart APIs do not expose this concept and the only uses within the engine are from test code. The DisplayList recording format only supports such paths to match the (no longer used) SkPicture recording format.

We should delete all references to this path type and instead assert inside the DlBuilder and DlCanvas methods that the flag is false on all paths processed...
Repository: next.js
Issue: `fetch` does not work when using manual suspense
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-zpfjcc?file=app%2Fpage.tsx

### To Reproduce

Enter demo and check terminal/console

### Current vs. Expected behavior

I'm suspending a client component in order to fetch data necessary to render the component, but inside the callback, the window object is not defined, even though at this stage it should very much have access to it.

Removing window.location.origin will lead to another error: TypeError: Failed to parse URL from /multipliers.bin which I believe is because it doesn't have access to the window object in the first place, much like trying to do new URL('/multipliers.bin')

The library being used to suspend (suspend-react) has nothing to do with the problem, I tested without it by manually throwing a Promise and it still happens, kept it in for better code readability.

The versions of Next/React being used in the demo are not the latest ones because I couldn't get them to work on stackblitz, but I did try locally with the latest releases and the error still persists

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 7947
  Available CPU cores: 8
Binaries:
  Node: 20.8.1
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Pages Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

When running build, next throws `Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error`. It seems like it is trying to pre render a client component but I have no idea why.
Repository: stable-diffusion-webui
Issue: [Feature Request]: ZROK for webUI share
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Is there a way to use zrok to share the webUI endpoint as is done with ngrok?

### Proposed workflow

COMANDLINE_ARGS= --zrok .....

### Additional information

_No response_
Repository: vscode
Issue: Quick Pick imprecise filtering breaks after 60 characters
Labels: bug,quick-pick

<!-- ⚠️⚠️ 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.91.0-Insiders, 1.90.2
- OS Version: Windows 11, Ubuntu 18 (in WSL)

The filtering for quick pick items which lets you skip characters or words seems to not work on longer strings.  Filtering does not work after the 60th character in the string (it seems).  

Steps to Reproduce:

1. Create a quick pick menu with these options:

```
await vscode.window.showQuickPick([
	"Alpha Bravo Charlie Delta Echo Foxtrot Golf Hotel India Juliett Kilo Lima Mike November Oscar Papa Quebec Romeo Sierra Tango Uniform Victor Whiskey X-ray Yankee Zulu",
	"alpha bravo charlie delta echo foxtrot golf hotel india juliett kilo lima mike november oscar papa quebec romeo sierra tango uniform victor whiskey x-ray yankee zulu"
], {
	canPickMany: false,
	title: "Example",
});

```

2. In the search bar, type: "Alpha Juli".  Both options will remain unfiltered and the strings "Alpha" and "Juli" will be highlighted separately:

![image](https://github.com/microsoft/vscode/assets/56779108/46da9b93-2cb1-4329-88f5-78b86503c942)

3. Type "e".  Both options now get filtered:

![image](https://github.com/microsoft/vscode/assets/56779108/8fcc4ad8-72b1-454d-917a-3ce11b075178)

4. All imprecise searching seems to break after the 60th character (which is the 'e' in 'Juliett'):

https://github.com/microsoft/vscode/assets/56779108/4b888c64-cb6f-4af0-a876-e6b7d30214c6
Repository: pytorch
Issue: `@pytorchbot merge -i` not ignoring currently failing checks
Labels: module: ci,triaged

See https://github.com/pytorch/pytorch/pull/129721 as the example.

![Screenshot 2024-06-28 at 4 08 27 PM](https://github.com/pytorch/pytorch/assets/31054793/fe668428-fb1a-4aad-a0d4-00b0d94151f3)


cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: opencv
Issue: cv::VideoWriter error: (-215:Assertion failed) !filename_pattern.empty() in function 'open'
Labels: category: videoio,incomplete

### System Information

OpenCV version: 4.10.0
OS: Ubuntu 20.04
Compiler: GCC 11.4

### Detailed description

I have the below code running in a docker container, and I get the following error when is try to create an instance of `cv::VideoWriter`:

```
[ WARN:0@21.400] global cap.cpp:643 open VIDEOIO(CV_IMAGES): raised OpenCV exception:

OpenCV(4.10.0-dev) /OpenCV/opencv-4.x/modules/videoio/src/cap_images.cpp:430: error: (-215:Assertion failed) !filename_pattern.empty() in function 'open'


there was an error opening the video writer
```
this is how I configure cmake to build opencv in my docker image.
```
cmake -DBuild_TIFF=ON \
     -DCMAKE_CXX_STANDARD=17 \
     -DWITH_TIFF=ON \
     -DWITH_GTK=ON \
     -DOPENCV_EXTRA_MODULES_PATH=../opencv_contrib-4.x/modules \
     -DWITH_CUDA=ON \
     -DCUDA_GENERATION=Auto \
     -DWITH_NVCUVID=OFF \
     -DWITH_NVCUVENC=OFF \
     -DBUILD_TESTS=OFF \
     -DBUILD_PERF_TESTS=OFF \
     -DBUILD_EXAMPLES=OFF \
     -DBUILD_opencv_apps=OFF \ 
     -DWITH_FFMPEG=ON\ 
     -DCUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda \
    -DBUILD_LIST=imgcodecs,core,features2d,imgproc,highgui,cudafeatures2d,cudaarithm,cudaimgproc,    cudev,flann,videoio,gapi \
     ../opencv-4.x \
```

I have tried directly putting  the name in the `open()` call, but get the same error. When I replace my cmake build in the dockerfile with `RUN apt install libopencv-dev` the issue goes away. What am I doing wrong? It seems like there is a build flag I am missing, but unsure which one.

### Steps to reproduce

```cpp
  int fourcc=cv::VideoWriter::fourcc('x','v','i','d');
  const std::string name="video_test.avi";
  cv::Size sz(2560,720);
  cv::VideoWriter vid_writer_dummy(name,fourcc,20.0,sz,true);
  if (vid_writer_dummy.isOpened()==false)
  {
      std::cout<<"therer was an error opening the video writer\n";
  }
  else
  {
      std::cout<<"the video writer was opened successfully\n";
  }
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: ui
Issue: [bug]: How to change HTML tag for AccordionTrigger to a div, so that buttons can be nested.
Labels: bug

### Describe the bug

I'm trying to nest buttons inside of the AccordionTrigger to trigger popovers with useful information to my users. By default, AccordionTrigger is an 'HTMLButtonElement'. Is there any way to change this to a 'div' that has an onClick event, while still controlling the open and close state of the Accordion? I'm asking to avoid the attached console error.
<img width="449" alt="Screenshot 2024-06-28 at 2 35 37 PM" src="https://github.com/shadcn-ui/ui/assets/67437978/93301010-059b-41b2-be93-dfd3f5325aae">


### Affected component/components

Accordion, AccordionTrigger

### How to reproduce

Nest a 'Button' element as a child of 'AccordionTrigger'

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Using MacOS, Brave Browser
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: node
Issue: Behavior of `realpath` with an empty string argument
Labels: fs,discuss

Refs: #35403

Currently, the project has 2 outcomes for different `realpath` functions with empty string arguments:
```js
fs.realpathSync('') // Returns CWD
await util.promisify(fs.realpath)('') // Returns CWD

await fs.promises.realpath('') // ENOENT Error
fs.realpathSync.native('') // ENOENT Error
await util.promisify(fs.realpath.native)('') // ENOENT Error
```

IMO, this should be standardized to
(A) Always throw
(B) Always return CWD
(C) Return CWD for non-`.native` calls, throw otherwise
Repository: vscode
Issue: Polish notebook context menu + when clauses
Labels: feature-request,notebook-commands

when clause-ing + context menu 

support for notebook code action discoverability

support for format notebook

focus on improving discoverability and improving notebook ecosystem
Repository: vscode
Issue: moving lines up and down causes formatting corruption 
Labels: bug,editor-autoindent

Type: <b>Bug</b>

when moving text up or down, code and comments have indenting corrupted.


this is most prevalent when moving text across jsdoc comment blocks. it does happen with more complex code blocks as well, i don't have an immediate recordable example ready for that one.

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i9-11980HK @ 2.60GHz (16 x 3302)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|63.71GB (29.20GB free)|
|Process Argv|--crash-reporter-id d8d9b7bf-ea05-4e4f-bddd-e38795583b25|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (27)</summary>

Extension|Author (truncated)|Version
---|---|---
copy-path-unixstyle|bai|2.0.0
vscode-pretty-json|chr|2.0.0
npm-intellisense|chr|1.4.5
path-intellisense|chr|2.9.0
vscode-css-modules|cli|0.5.1
postcss|css|1.0.9
vscode-eslint|dba|3.0.8
gitlens|eam|15.1.0
vscode-html-css|ecm|2.0.10
vscode-diff|fab|2.1.2
lintlens|ghm|7.5.0
vscode-test-explorer|hbe|2.21.1
search-node-modules|jas|1.3.0
svg|joc|1.5.3
vscode-jest-test-adapter|kav|0.8.1
pnpm-vscode-helper|lin|0.3.0
remote-wsl|ms-|0.88.2
test-adapter-converter|ms-|0.1.9
vscode-nvm|noj|0.0.2
indent-rainbow|ode|8.3.1
vscode-subword-navigation|ow|1.2.0
vscode-xml|red|0.27.1
trailing-spaces|sha|0.4.1
vscode-stylelint|sty|1.4.0
explorer-manager|Uro|1.0.1
vscodeintellicode|Vis|1.3.1
html-css-class-completion|Zig|1.20.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
legacy_priority:31082724

```

</details>

<!-- generated by issue reporter -->
Repository: go
Issue: x/tools/go/analysis/passes/stdversion: language vs toolchain version
Labels: NeedsFix,Tools,Analysis

In this example

```
-- go.mod --
module example.com

go 1.23
-- foo.go --
//go:build go1.21

package pkg

import "reflect"

func main() {
	_ = reflect.TypeFor[int]
}
```

stdversion reports `./foo.go:8:14: reflect.TypeFor requires go1.22 or later (file is go1.21)`

I believe that this might be overly strict. Even though the `//go:build` directive downgrades the _language version_ available in the file, it doesn't change the fact that this file will only be built by a _toolchain_ that is at least verison 1.23, because the module as a whole will only be built by a toolchain that satisfies the `go` dependency in `go.mod`. 

I thus believe that the standard library available to a file with a build tag is `max(file's version, module's version)`, and not `min`.

/cc @adonovan
Repository: pytorch
Issue: 3D matrix support in _scaled_mm 
Labels: triaged,enhancement,matrix multiplication,module: float8

### 🚀 The feature, motivation and pitch

3D fp8 matrix multiplication can be useful for fp8 model with 3D matmul (it also can be used to improve accuracy of models with 2D fp8 quantized matrix multiplication).
_scaled_mm is designed for fp8 matrix multiplication, but currently _scaled_mm supports only 2D x 2D matrix multiplication, as shown below.
It would be great to extend _scaled_mm with support of input 3D matrices.

```python
device = 'cuda'
# does not work
x_size = (16, 32, 128)
w_size = (16, 64, 128)

# works ok
# x_size = (32, 128)
# w_size = (64, 128)
dtype = torch.float32
x = torch.rand(x_size, dtype=torch.float32, device=device).to(torch.float8_e4m3fn)
w = torch.rand(w_size, dtype=torch.float32, device=device).to(torch.float8_e4m3fn)
one = torch.tensor([1.0], dtype=torch.float32, device=x.device)

# for reference
y_f32 = torch.matmul(x.to(torch.float32), w.transpose(-1, -2).to(torch.float32))

y, _ = torch._scaled_mm(
    x,
    w.transpose(-1, -2),
    scale_a=one,
    scale_b=one,
    out_dtype=dtype,
    use_fast_accum=False,
)
```

### Alternatives

_No response_

### Additional context

_No response_

cc @yanbing-j @vkuzo @albanD @kadeng @penguinwu