sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: JSR: no-slow-types mixing type/value namespaces?
Labels: bug,jsr

Version: deno 1.42.2

When using Zod, it's common to (ab)use the fact that TypeScript keeps types and values in separate namespaces. (Not to be confused with the Typescript "namespaces" feature, confusingly. 😣) This makes sense, since the types are thrown away at runtime, and only the values remain.

So, for example:
```typescript
// lib.ts (NOT exported from deno.json)
import { z } from "npm:zod@3.22.4"

export type Foo = z.infer<typeof Foo>
export const Foo = z.object({
    foo: z.string().min(1)
})
```

If I try to use this code in a project targeting JSR, like this:

```typescript
// main.ts (exported from deno.json)
import { Foo } from "./lib.ts"

export function parseFoo(value: unknown): Foo {
  return Foo.parse(value)
}
```

Then `deno lint` gives this error:
```
error[no-slow-types]: missing explicit type in the public API
 --> …/zod-example/lib.ts:4:14
  |
4 | export const Foo = z.object({
  |              ^^^ this symbol is missing an explicit type
  = hint: add an explicit type annotation to the symbol
```

I assumed this meant that Deno/JSR isn't happy w/ using `z.infer` so I updated to:

```typescript
export type Foo = {
    foo: string
}

export const Foo = z.object({
    foo: z.string().min(1)
})
```

But that gives the exact same error.

I can work around this by giving the type and the `const` value separate names:

```typescript
export type FooType = {
    foo: string
}

export const Foo = z.object({
    foo: z.string().min(1)
})
```

… but that makes using them a bit more cumbersome.

This seems to be a bug w/ the no-slow-types check. My public API only exposes type **type** `Foo`, not the `const` value, so the first modification should work.
Repository: awesome-mac
Issue: 🎉 Add Devkits
Labels: addition

### 🪩 Provide a link to the proposed addition

https://devkits.dev

### 😳 Explain why it should be added

A very practical offline developer tool

### 📖 Additional context

_No response_

### 🧨 Issue Checklist

- [ ] I have checked for other similar issues
- [ ] I have explained why this change is important
- [ ] I have added necessary documentation (if appropriate)
Repository: godot
Issue: Debug window opens behind editor
Labels: bug,platform:linuxbsd,topic:porting

### Tested versions

v4.3.dev5.official [c9c17d6ca]

### System information

Godot v4.3.dev5 - Ubuntu 22.04.4 LTS 22.04 - X11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 Ti (nvidia; 535.171.04) - AMD Ryzen 5 5600 6-Core Processor (12 Threads)

### Issue description

The debug window opens behind the Godot editor. If I switch to the window manually, it works as expected, but when repeatedly running the same scene many times, it becomes a chore.

I found a similar issue in https://github.com/godotengine/godot/issues/57831. But I noticed the issue was fixed and the OS is different from mine, so maybe the root cause is different.

### Steps to reproduce

Click the "Run Current Scene" button.

### Minimal reproduction project (MRP)

N/A
Repository: ant-design
Issue: 在`flex`布局下，处于`justifyContent: 'space-between'`右侧的加宽度过渡动画的`<TreeSelect>`组件，在下拉展开时，下拉会先在右侧展开，再移到左侧
Labels: Inactive,🧶 Low Priority,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-hbntxf?file=demo.tsx)

### Steps to reproduce

1. 代码
```tsx
<TreeSelect
  style={{
    width: expand ? '200px' : '100px',
    transition: 'width 0.4s ease-in-out',
  }}
>
```
2. 点击`TreeSelect`组件

### What is expected?

下拉可以跟着过渡动画效果，平滑的增加宽度

### What is actually happening?

下拉会先在相对于搜索框偏右的位置展开，再移到左侧

| Environment | Info |
| --- | --- |
| antd | 5.16.2 |
| React | 18.2.0 |
| System | MacOS |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ant-design
Issue: TreeSelect Popup未对齐
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/~/github.com/TMRnoMEM/antd-treeselect-issue)

### Steps to reproduce

点击显示Popup即可看到未对齐

### What is expected?

Popup与TreeSelect对齐

### What is actually happening?

产生了偏移

| Environment | Info |
| --- | --- |
| antd | 5.16.2 |
| React | 18 |
| System | Windows 11 23H2 |
| Browser | Microsoft Edge 123 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
![image](https://github.com/ant-design/ant-design/assets/18340287/40f3604c-7fb3-4d69-a28f-cb5530861f6a)
Repository: PowerToys
Issue: 增加全局搜索功能后，可直接调用搜索到的应用使用该应用的功能
Labels: Needs-Triage

### Description of the new feature / enhancement

全局搜索功能升级：输入文本搜索到应用后，可直接调用搜索到的应用使用该应用的功能

### Scenario when this would be used?

翻译、听歌、看视频、搜索网页等等......

### Supporting information

mac插件支持这项功能
Repository: yt-dlp
Issue: postprocess with --skip-download
Labels: question

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

Ok so first, `--write-subs --use-postprocessor "subs_converter" --print "after_move:%(requested_subtitles.:.filepath)s"` works fine.  
But let's skip download cuz we are just for subs. `--write-subs --use-postprocessor "subs_converter" --print "after_move:%(requested_subtitles.:.filepath)s" --skip-download`.
No print no postprocess.  
So I tried before_dl. `--write-subs --use-postprocessor "subs_converter:when=before_dl" --print "before_dl:%(requested_subtitles.:.filepath)s" --skip-download`. Sub is converted but the print happened before the postprocess so the output is wrong.  
But if I move the print to post_process it won't print `--write-subs --use-postprocessor "subs_converter:when=before_dl" --print "post_process:%(requested_subtitles.:.filepath)s" --skip-download`
Now... what should I do, to download subs only and call the postprocessor and print the converted filename?
Is there a stage between before_dl and post_process so I can print the result after the postprocess?

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: tensorflow
Issue: `Segmentation fault` in `tf.raw_ops.CollectiveGather` when `input` is empty.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`Segmentation fault` in `tf.raw_ops.CollectiveGather` when `input` is empty.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1lx42HhXrkx5BPwSxLg-bGuJMMCTEIQyt?usp=sharing
```


### Relevant log output

```shell
segmentation fault (core dumped)
```
Repository: pytorch
Issue: Use online softmax for just softmax by itself
Labels: triaged,module: inductor

### 🚀 The feature, motivation and pitch

torch.compile currently uses the standard 3 pass algorithm for computing softmax. It would be neat for Inductor to codegen using the online softmax algorithm for sufficiently large softmaxes.

Could be done using similar infra to https://github.com/pytorch/pytorch/pull/102486

### Alternatives

_No response_

### Additional context

_No response_

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames @desertfire @chauhang
Repository: tensorflow
Issue: `Segmentation fault` in `tf.raw_ops.RaggedRange` and `tf.ragged.range` when `starts` or `limits` has large (postive/negative) values.
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.10

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

`Segmentation fault` in `tf.raw_ops.RaggedRange` and `tf.ragged.range` when `starts` or `limits` has large (postive/negative) values.

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/drive/1c5J_tSNwLdPmi0TXMaJNNhUb-Ha__dw8?usp=sharing
```


### Relevant log output

```shell
segmentation fault (core dumped)
```
Repository: rust
Issue: `-Zprint-llvm-passes` lies on recent rustc
Labels: A-LLVM,T-compiler,C-bug

`-Zprint-llvm-passes`, best I can tell, is equivalent to `clang -cc1 -mdebug-pass=Structure`, which is the wrong way to print out the pass order in the new PM. I found a relevant LLVM bug: https://github.com/llvm/llvm-project/issues/28692.

The best way to actually get which passes ran is `-Ztime-llvm-passes`, which unfortunately does not provide a pass order.

I don't know how rustc actually actuates LLVM, but it may be worthwhile to figure out a way to get a handle on the PM and print the pass order directly. Ideally, LLVM should have a "what passes and analyses did you actually run" setting, but that will require actually bodging that into the new PM (which the aforementioned issue suggests doing).

I also kind of hate `-mdebug-pass=Structure`, since it doesn't use the either the `opt` names or the LLVM type names for the passes, which makes it hard to actually figure out what passes the pass order actually refers to.

cc @workingjubilee
Repository: godot
Issue: Godot 4 3d stutter in exclusive fullscreen mode
Labels: bug,topic:rendering,needs testing,performance

### Tested versions

- Tested in godot stable 4.2.1

### System information

Windows 11, Ryzen 5600x, Radeon RX6750XT, 165hz 1440p monitor, Vulkan, Forward+, Godot 4.2.1

### Issue description

Godot 4 seems to stutter pretty consistently in exclusive fullscreen mode. I first noticed this issue in a project I was working on, where it still happens around half the time I run it or more, making my project unplayable, but it also appears in [this gameplay video of buckshot roulette](https://www.youtube.com/watch?v=zaWPFbX7Q8A&t=289s) most noticable at the 4:40 mark when picking up the shotgun. I'm currently making a project now and this issue was happening very bad in my loading screen and test scene, until I stopped using exclusive fullscreen mode. my project runs fine now, just with an annoying border which has been addressed here before.

### Steps to reproduce

Make a new project, add some moving object, and enable exclusive fullscreen. May need to have some meshes in scene to increase gpu load to see issue

### Minimal reproduction project (MRP)

N/A
Repository: create-react-app
Issue: Dependency Packages introduced vulnerabilities associated with react-scripts 5.0.1
Labels: needs triage,issue: bug report

# nth-check 1.0.2	        JavaScript (Yarn)

Incorrect Comparison     
Description
nth-check is vulnerable to Inefficient Regular Expression Complexity
Severity:
  High
Tool: Dependency Scanning
Scanner: Gemnasium
 
Links
            https://huntr.dev/bounties/8cf8cc06-d2cf-4b4e-b42c-99fafb0b04d0           
            https://nvd.nist.gov/vuln/detail/CVE-2021-3803           
Identifiers
            CVE-2021-3803           
            Gemnasium-3284fc8f-f377-4fcf-95dd-270a8b922329           
     
Solution
 
Upgrade to version 2.0.1 or above.
 




# express 4.18.2	                JavaScript (Yarn)
Express.js Open Redirect in malformed URLs     
Description
 
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode [using encodeurl](https://github.com/pillarjs/encodeurl) on the contents before passing it to the location header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.
The main method impacted is res.location() but this is also called from within res.redirect().
 
Severity:
  Medium

Identifiers
            CWE-1035           
            CWE-937
 

# webpack-dev-middleware 5.3.3	JavaScript (Yarn)
Path traversal in webpack-dev-middleware     
Description
 
The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine.
 
Severity:
  High

Identifiers
            CWE-22           
            CWE-1035           
            CWE-937



# postcss 7.0.39	                JavaScript (Yarn)
PostCSS line return parsing error     
Description
 
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
 
Severity:
  Medium
Identifiers
            Gemnasium-7a2fe254-d605-4097-a4e3-7eafeb60045e           
            CVE-2023-44270
Repository: vscode
Issue: setting `editor.autoClosingBrackets` to `beforeWhitespace` no longer works
Labels: polish,editor-autoclosing

<!-- ⚠️⚠️ 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.88.1
- OS Version: windows 11

Steps to Reproduce:

1. add the following to `settings.json`:
    ```json
    {
        "editor.autoClosingBrackets": "beforeWhitespace"
    }
    ```
2. open a python file and type an open bracket before a non-whitespace character:
    
    https://github.com/microsoft/vscode/assets/57028336/38f49474-0099-46d4-91b7-27b3475a5f46


this seems to have been broken in a recent update
Repository: vscode
Issue: option for `editor.autoClosingBrackets` to not auto-close if there's a syntax error in the file
Labels: polish

<!-- ⚠️⚠️ 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. -->

a very common cause of syntax errors are open brackets without a closing bracket, or vice versa:

```ts
const foo = }
```

attempting to fix this is always extremely annoying because it inserts another closing bracket, preventing the syntax error from being fixed:

https://github.com/microsoft/vscode/assets/57028336/162cea8c-3fab-4b93-92a6-1652e64d57c8

setting it to `beforeWhitespace` makes it a bit less annoying (at least it used to, see #210436), but it can still sometimes insert closing brackets in cases where it causes a syntax error.

i think an option to only insert an auto-closing bracket when there are no syntax errors in the file would be a massive improvement
Repository: pytorch
Issue: DISABLED test_torchvision_models_efficientnet_v2_m (__main__.TestVisionTracing)
Labels: triaged,module: flaky-tests,skipped,module: fx

Platforms: asan, linux, rocm, slow



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_torchvision_models_efficientnet_v2_m&suite=TestVisionTracing&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/23855559409).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_torchvision_models_efficientnet_v2_m`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_fx.py`

cc @clee2000 @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv
Repository: langchain
Issue: LLM with_fallbacks function not work with create_tool_calling_agent
Labels: Ɑ: agent,🤖:bug,Ɑ:  Runnables

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code


self.llm = self.llm.with_fallbacks(fallbackModels)
 
self.agent = create_tool_calling_agent(self.llm.llm, self.tools, self.promptTemplate.getAgentPrompt(self.tools))




### Error Message and Stack Trace (if applicable)

    self.agent = create_tool_calling_agent(self.llm.llm, self.tools, self.promptTemplate.getAgentPrompt(self.tools))
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/langchain/agents/tool_calling_agent/base.py", line 85, in create_tool_calling_agent
    raise ValueError(
ValueError: This function requires a .bind_tools method be implemented on the LLM.

### Description

My code work well create_tool_calling_agent without call with_fallbacks function.


### System Info

langchain==0.1.16
langchain-community==0.0.33
langchain-core==0.1.43
langchain-experimental==0.0.49
langchain-google-genai==1.0.1
langchain-openai==0.1.3
langchain-text-splitters==0.0.1
langchainhub==0.1.14

platform linux
python 3.11
Repository: angular
Issue: The CSP nonce remains in the DOM after being read by Angular
Labels: area: security,cross-cutting: CSP

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

core

### Is this a regression?

No

### Description

When I use the `ngCspNonce`  attribute in order to inject a nonce that is used by the framework to meet the browser's criteria for `script` and `style` tags, I expect it to disappear from the DOM after the framework has retrieved it.

As an attacker, its very easy for me to detect if an application is built with Angular, and retrieve the nonce in the DOM. It would be much harder for me if the nonce was encapsulated into JavaScript closures with no global reference to it.

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

_No response_

### 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: 16.2.9
Node: 20.9.0 (Unsupported)
Package Manager: npm 10.1.0
OS: win32 x64

Angular: 16.2.12
... animations, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1602.9
@angular-devkit/build-angular      16.2.9
@angular-devkit/core               16.2.9
@angular-devkit/schematics         16.2.9
@angular/cdk                       16.2.11
@angular/cli                       16.2.9
@angular/material                  16.2.11
@angular/material-moment-adapter   16.2.11
@schematics/angular                16.2.9
rxjs                               7.8.1
typescript                         5.1.6
zone.js                            0.13.3
```


### Anything else?

_No response_
Repository: rust
Issue: rust-gdb set breakpoints in all the functions in a file
Labels: C-discussion,WG-debugging

In gdb we can do

```
rb hello.cc:.
```
which will set a breakpoint for every function in hello.cc

but in rust-gdb `rb hello.rs:.` doesn't do anything.
Repository: vscode
Issue: Unlucky slow diffs in merge editor
Labels: bug,diff-editor

Here's the JSON export: 
[merge-editor-export.json](https://github.com/microsoft/vscode/files/14994694/merge-editor-export.json)