sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Webhook support
Labels: feature request

Since Ollama now supports parallel requests since https://github.com/ollama/ollama/issues/358, i would like to suggest support for webhooks on completed generations. 

The reason for this is that because longer running tasks like summarization can take some time, and Ollama will queue up generations if you send more than your server can handle in parallel. This causes my web app having to leave an open handle to the HTTP request which exhausts my server resources since i have to do hundreds of summarizations per day. 

If we could have a simple webhook to report on the status change of a generation (completed, error), parallelisation would be much more useful. I think Replicate does a good job and a first implementation could be inspired by [their API](https://replicate.com/docs/webhooks) and be smaller in scope.
Repository: tensorflow
Issue: Updgraded manylinux support?
Labels: stat:awaiting tensorflower,type:feature,type:build/install,subtype: ubuntu/linux

As per my understanding, manylinux 2014 (infact CentOS Linux 7) went EOL on June 30 2024.

I still see the tf-nightly-cpu wheels and latest 2.17 prerelease wheels use manylinux 2014.
Do you plan to support updated manylinux (probably 2_28). ?

I also see some notes for the same here: https://docs.google.com/document/d/1l6q1qzEyCzEwXloKZqwP7bmVO1SxeVRhPW3A0BeB4KE/edit#heading=h.u7w1oawlfu32

@MichaelHudgins , any thoughts on this? or any relevant contacts to this?

Refer : https://github.com/mayeut/pep600_compliance/blob/master/EOL.rst
Refer : https://www.centos.org/
Repository: stable-diffusion-webui
Issue: [Bug]: calling `%PYTHON%` in webui.bat stops the execution of the rest of the script.
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

The first line where `%PYTHON%` is called stops the execution of the rest of the script.
This happens with any usage of `%PYTHON%`.

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/30209145/ae3ae79d-60f7-47f0-a75a-7c803d9205a8)

You can test this by putting `echo` before and after the `%PYTHON%` call

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/30209145/14fcfdcb-fa87-4b7a-9b4d-832c7969c095)

You can test this further by running `PYTHON --version` and doing the same test

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/30209145/42c43aea-cab7-4f1c-b6fb-c5ea48480de1)


### Steps to reproduce the problem

1. Install Python 3.10.6 via pyenv-win.
2. Get the latest version of webui, latest is commit feee37d on master branch.
3. Set version 3.10.6 as the local version (`pyenv local 3.10.6`).
4. Try to launch webui
5. (optional) run the tests I did above.

### What should have happened?

WebUI should have launched as expected.

### What browsers do you use to access the UI ?

Google Chrome

### Sysinfo

not available

### Console logs

```Shell
none
```


### Additional information

Python 3.10.6 is installed via pyenv-win.
Repository: langchain
Issue: BadRequestError with vllm locally hosted Llama3 70B Model 
Labels: 🤖:bug,stale,🔌: openai

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the [LangGraph](https://langchain-ai.github.io/langgraph/)/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 LangGraph/LangChain rather than my code.
- [X] I am sure this is better as an issue [rather than a GitHub discussion](https://github.com/langchain-ai/langgraph/discussions/new/choose), since this is a LangGraph bug and not a design question.

### Example Code

```python
Following below example with locally hosted llama3 70B instruct model with ChatOpenAI
https://langchain-ai.github.io/langgraph/how-tos/create-react-agent/

Simlar issue with the following example: 
from langchain_core.tools import tool
from langgraph.graph import MessageGraph from langgraph.prebuilt import ToolNode, tools_condition

@tool def divide(a: float, b: float) -> int: """Return a / b.""" return a / b

llm = ChatOpenAI( model_name = 'Meta-Llama-3-70B-Instruct', base_url = "http://172.17.0.8:xxxx/v1/", api_key = "EMPTY", temperature=0).bind( response_format={"type": "json_object"} )

tools = [divide]

graph_builder = MessageGraph() 
graph_builder.add_node("tools", ToolNode(tools)) 
graph_builder.add_node("chatbot", llm.bind_tools(tools)) 
graph_builder.add_edge("tools", "chatbot") 
graph_builder.add_conditional_edges( ... "chatbot", tools_condition ... ) graph_builder.set_entry_point("chatbot") 
graph = graph_builder.compile() 

graph.invoke([("user", "What's 329993 divided by 13662?")])
```


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

```shell
BadRequestError: Error code: 400 - {'object': 'error', 'message': "[{'type': 'extra_forbidden', 'loc': ('body', 'tools'), 'msg': 'Extra inputs are not permitted', 'input': [{'type': 'function', 'function': {'name': 'get_weather', 'description': 'Use this to get weather information.', 'parameters': {'type': 'object', 'properties': {'city': {'enum': ['nyc', 'sf'], 'type': 'string'}}, 'required': ['city']}}}], 'url': 'https://errors.pydantic.dev/2.7/v/extra_forbidden'}]", 'type': 'BadRequestError', 'param': None, 'code': 400}
```


### Description

I have tried instantiating ChatOpenAI as follows:
llm = ChatOpenAI( model_name = 'Meta-Llama-3-70B-Instruct', base_url = "http://172.17.0.8:xxxx/v1/", api_key = "EMPTY", temperature=0)

llm = ChatOpenAI( model_name = 'Meta-Llama-3-70B-Instruct', base_url = "http://172.17.0.8:xxxx/v1/", api_key = "EMPTY", temperature=0).bind( response_format={"type": "json_object"} )

### System Info

Meta's llama 3 70B Instruct locally hosted on vllm.
ChatOpenAI works fine for other application for example RAG and LCEL
Repository: angular
Issue: extract-i18n generating wrong source inside the xfl file when parsing empty elements
Labels: area: i18n

### Command

extract-i18n

### Is this a regression?

- [X] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

We recently upgraded to v16.2.14 from v14 (couldn't update further as we need to fix some dependencies which don't support > v17) and now I discovered by chance that extract-i18n is producing an xlf which would break html once using a language different from the default one.
Debugging a bit, I found out that the parse of empty html elements (like `<svg></svg>` or `<span></span>`) is producing wrong closing tags picking up part of the text after the real closing tag. An example below:
this html
```html
<div>
  <button
    i18n="add line button@myAddLineStringId"
  >
    Add line
    <svg cdsIcon="add" size="20" class="cds--btn__icon"></svg>
  </button>
</div>
```
is producing this entry in the xlf
```xlf
<source> Add line <x id="START_TAG__SVG_SVG" ctype="x-_svg_svg" equiv-text="&lt;svg cdsIcon=&quot;add&quot; size=&quot;20&quot; class=&quot;cds--btn__icon&quot;&gt;"/><x id="CLOSE_TAG__SVG_SVG" ctype="x-_svg_svg" equiv-text="&lt;/button&gt;
&lt;/di"/></source>
```
as you can see, when the translated xlf will take over the default language version, it will produce an svg closing tag `</button></di` which would then break the above html
A simple fix is to add a space inside the empty element, or move the closing tag in a new line, but this might collide with linter setup, so not a great temporary solution.

### Minimal Reproduction

have in a template the following:
```html
<div i18n="description@@stringId">
  A string
  <span></span>
</div>
```

and then run the normal extract-i18n

### Exception or Error

_No response_

### Your Environment

```text
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 16.2.14
Node: 18.20.1
Package Manager: yarn 1.22.19
OS: darwin arm64

Angular: 16.2.12
... animations, common, compiler, compiler-cli, core, elements
... forms, language-service, localize, platform-browser
... platform-browser-dynamic, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1602.14
@angular-devkit/build-angular   16.2.14
@angular-devkit/core            16.2.14
@angular-devkit/schematics      16.2.14
@angular/cdk                    16.2.14
@angular/cli                    16.2.14
@angular/material               16.2.14
@schematics/angular             16.2.14
rxjs                            7.8.1
typescript                      4.9.5
zone.js                         0.13.3
```


### Anything else relevant?

_No response_
Repository: deno
Issue: Bug: Panic when running `moment`'s test suite
Labels: bug,node compat

```sh
Platform: macos aarch64
Version: 1.44.4
Args: ["/Users/marvinh/dev/denoland/deno/target/debug/deno", "run", "--unstable-ffi", "--unstable-fs", "--unstable-webgpu", "--node-modules-dir", "-A", "/Users/marvinh/dev/oss/moment/node_modules/node-qunit/lib/child.js", "grunt", "/Users/marvinh/dev/oss/moment/node_modules/grunt/bin/grunt", "test", ...]

thread 'main' panicked at /Users/marvinh/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.292.0/ops.rs:54:5:
op op_node_ipc_write was not marked as #[op2(reentrant)], but re-entrantly invoked op op_apply_source_map
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

## Steps to reproduce

1. Clone https://github.com/moment/moment
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task test`

Version: Deno 1.44.4 (git 496ea5903 )
Repository: deno
Issue: Bug: No coverage data in `nyc`
Labels: bug,node compat

Noticed that when running moment's test suite that there is no coverage data.

Node:

<img width="796" alt="Screenshot 2024-07-03 at 17 14 59" src="https://github.com/denoland/deno/assets/1062408/0c527488-a8de-41e6-85a4-59c6ac1154cb">

Deno:
<img width="542" alt="Screenshot 2024-07-03 at 17 14 38" src="https://github.com/denoland/deno/assets/1062408/6a0c5574-d9c7-46f1-98fa-05109e0f1eed">


## Steps to reproduce

1. Clone https://github.com/moment/moment
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task coverage`

Version: Deno 1.44.4 (git 496ea5903 )
Repository: next.js
Issue: Redirect in page.tsx shows a white page on client-side navigation
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/Jens-n11/nextjs-redirect-example

### To Reproduce

If you use a `next/navigation` `redirect()` in a page.tsx which is called via a `next/Link` `<Link>` (client side navigation) the browser will show a white page for a part of a second until the redirect happens.

1. Start the app
2. Open the start page (http://localhost:3000)
3. Click on the "Next-Link with redirect"
4. You will see for a short time a white page before the green landing page loads. Its easier to see if you throttle the connection speed.

### Current vs. Expected behavior

I would expect, that next does not start rendering the new page if the page throws a redirect. I would expect the same look-and-feel with `next/Link` like it would be with an `<a>` Tag. See this example video with first the `<a>` Tag and then the `next/link` (with client side navigation):

https://github.com/vercel/next.js/assets/110047537/3fa39af3-d2b5-45b4-80cf-4f0cf3330547



### Provide environment information

```bash
Doesn't really matter, but here they are:

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:13:18 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


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

Navigation

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

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: deno
Issue: Bug: `shx` glob argument not working
Labels: bug,node compat,task runner

```sh
Task prebuild shx rm -rf packages/*/dist/
glob: no matches found '/Users/marvinh/dev/oss/preact-signals/packages/*/dist/'
```

## Steps to reproduce

1. Clone https://github.com/preactjs/signals
2. Run `pnpm i`
3. Run `DENO_FUTURE=1 deno task prebuild`

Version: Deno 1.44.4 (git 496ea5903)
Repository: node
Issue: Special URL schemes for resources within single executable applications
Labels: single-executable

When discussing about the implication of using URLs to register module hooks (so if SEA uses it to override module loading to point loads to within the binary, the SEA need a way to override default module resolution before its own resolution customization is registered) @GeoffreyBooth came up with the idea of adding special URL schemes like `node-sea:` which allows various APIs to point to assets within the binary. Since SEA was designed with a lower-level user-land abstraction layer in mind (for example, turning fs API calls from within the application into an access to `sea.getAssetRaw()` + some additional access), this looks like a good utility for that abstraction layer in general, beyond just module hooks. So opening this issue to see what others think of it.

cc @nodejs/single-executable
Repository: deno
Issue: Bug: wrong `this` binding in `buble`
Labels: bug,node compat

Error doesn't happen in Node.

```sh
[!] (buble plugin) TypeError: this.body.initialise is not a function
build/es5.js (undefined:undefined)
TypeError: this.body.initialise is not a function
    at new Program (file:///Users/marvinh/dev/oss/json5/node_modules/buble/src/program/Program.js:31:12)
    at Object.transform (file:///Users/marvinh/dev/oss/json5/node_modules/buble/src/index.js:90:9)
    at Object.transform (file:///Users/marvinh/dev/oss/json5/node_modules/rollup-plugin-buble/dist/rollup-plugin-buble.cjs.js:20:18)
    at file:///Users/marvinh/dev/oss/json5/node_modules/rollup/dist/rollup.js:20780:41
```

## Steps to reproduce

1. Clone https://github.com/json5/json5
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task build`

Version: Deno 1.44.4
Repository: deno
Issue: Bug: `node:http` invalid url when pathname is absolute url 
Labels: bug,node compat,node:http

This breaks some test cases in Koa's test suite.

Node: `http://example.com/foo`
Deno: `/http://example.com/foo` <- notice the leading `/`

## Steps to reproduce

```ts
import http from "node:http";

const server = http.createServer();

server.on("request", (request, res) => {
  res.end(request.url);
});

server.listen(8000);

http.get({
  host: "localhost",
  // This field is not parsed properly
  path: "http://example.com/foo",
  port: 8000,
}, async (res) => {
  let buf = "";
  res.setEncoding("utf8");
  res.on("data", (s) => {
    buf += s;
  });
  res.on("end", () => {
    console.log(buf);
  });
});
```

Version: Deno 1.44.4
Repository: ollama
Issue: `Ollama` fails to work with `CUDA` after `Linux` suspend/resume, unlike other `CUDA` services
Labels: bug,nvidia

### What is the issue?

Every time Linux resumes from suspension, it fails to correctly reload `CUDA`. However, this issue has been well-resolved using commands like `sudo rmmod nvidia_uvm` and `sudo modprobe nvidia_uvm`. After this, all CUDA-dependent services except `Ollama` can utilize `CUDA` and work normally again (e.g., `torch.randn((2,2)).cuda(0)`). GPU mode for Ollama can only be restored by restarting the Ollama service. This can be done by reloading systemd and restarting Ollama: `systemctl daemon-reload` and `systemctl restart ollama`. I'm not sure if I've missed something, such as specific `Ollama` settings, so I've reported this as a bug.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.1.48
Repository: TypeScript
Issue: TS module not found until server is restarted
Labels: Fixed

In VS Code, using the workspace TS version (5.6.0-dev.20240618)

1. Create a new TS file
2. Try to import an existing module
3. Get a "not found" error until you restart the TS language server

![image](https://github.com/user-attachments/assets/6a20126a-d2c7-4d0a-bcba-821bb8a653be)
Repository: rust
Issue: VecDeque::split_off has unexpectedly poor performance characteristics when splitting off from the front.
Labels: I-slow,C-bug,T-libs

I tried this code:

```rust
use std::collections::VecDeque;

fn huge_queue() -> VecDeque<usize> {
    const HUGE: usize = 1000000;
    let mut queue = VecDeque::with_capacity(HUGE);
    for i in 0..HUGE {
        queue.push_back(i);
    }
    queue
}

const CHUNK: usize = 123;
const FAST: bool = false;

fn main() {
    let mut queue = huge_queue();
    if FAST {
        while queue.len() > CHUNK {
            queue.rotate_left(CHUNK);
            let rest = queue.split_off(queue.len() - CHUNK);
            println!("Chunk of {}", rest.len());
        }
    } else {
        while queue.len() > CHUNK {
            let rest = queue.split_off(CHUNK);
            println!("Chunk of {}", queue.len());
            queue = rest;
        }
    }
    println!("Remaining: {}", queue.len());
}
```

I expected the `FAST` branch and the `else` branch to have comparable performance, instead it seems `VecDeque::split_off` from the front is much slower than expected (as one would expect of e.g. `Vec::split_off` which needs to shift all the elements).
Repository: deno
Issue: Deno panic on file with typo (un-commented URL)
Labels: bug,upstream,swc

The following file reliably panics, rather than throwing a syntax error, on latest deno (v1.44.4), macOS 14.5:

```
$ cat broken.ts
https://fake.com

interface Fake {
}
```

```
$ deno run broken.ts

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos aarch64
Version: 1.44.4
Args: ["deno", "run", "broken.ts"]

thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/swc_ecma_transforms_typescript-0.189.1/src/strip_type.rs:14:5:
internal error: entered unreachable code
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

```
$ RUST_BACKTRACE=1 deno run broken.ts

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos aarch64
Version: 1.44.4
Args: ["deno", "run", "broken.ts"]

thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/swc_ecma_transforms_typescript-0.189.1/src/strip_type.rs:14:5:
internal error: entered unreachable code
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: <swc_ecma_transforms_typescript::strip_type::StripType as swc_ecma_visit::VisitMut>::visit_mut_ts_type
   4: swc_ecma_visit::visit_mut_decl
   5: <swc_ecma_transforms_typescript::strip_type::StripType as swc_ecma_visit::VisitMut>::visit_mut_module_items
   6: <swc_ecma_transforms_typescript::typescript::TypeScript as swc_ecma_visit::VisitMut>::visit_mut_program
   7: <swc_ecma_ast::module::Program as swc_ecma_visit::FoldWith<V>>::fold_with
   8: deno_ast::transpiling::fold_program
   9: deno_ast::transpiling::transpile
  10: deno_ast::transpiling::<impl deno_ast::parsed_source::ParsedSource>::transpile
  11: deno::emit::EmitParsedSourceHelper::transpile
  12: tokio::runtime::task::raw::poll
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
Repository: godot
Issue: CollisionObject2D param type mismatch between _InputEvent method and InputEvent delegate
Labels: enhancement,discussion,topic:physics,breaks compat

### Tested versions

Reproduceable in v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.2.1.stable.mono - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.5152) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)

### Issue description

For CollisionObject2D, _InputEvent accepts a Viewport as the first parameter, while the signal/delegate InputEvent accepts Node as the first parameter. Both seem to do the same thing, and the other params are the same. Node param for InputEvent is also labelled viewport.

So I'm wondering if this was a mistake or if there was a reason that the input event signal may send a Node instead of a Viewport?

### Steps to reproduce

```csharp
using Godot;
using System;

public partial class ExampleCollisionObject2D : Area2D {

  public override void _Ready() {
    base._Ready();

    InputEvent += (Viewport viewport, InputEvent @event, int shapeIdx) => {}; // This throws an error
  }
  
  // This is fine
  public override void _InputEvent(Viewport viewport, InputEvent @event, int shapeIdx) {
    base._InputEvent(viewport, @event, shapeIdx);
  }
}
```


### Minimal reproduction project (MRP)

N/A - this is C# specific.
Repository: pytorch
Issue: autograd.function with `setup_context` has a number of issues with `torch.compile`
Labels: triaged,oncall: pt2,module: pt2-dispatcher

### 🐛 Describe the bug

Issue 1: If we mess up the number of arguments from `autograd.Function` we will often trace out incorrect ops into the graph. In this case, the `getitem` should be on a *tuple*, not the tensor. This can lead to very strange behavior, including CUDA IMA's.

https://pastebin.com/v8EDBsK7
<img width="892" alt="image" src="https://github.com/pytorch/pytorch/assets/6355099/0e5482c1-d0e4-40eb-8dec-f23fd0bfbaf9">

Issue 2: If I set `generate_vmap_rule` on the `autograd.Function`, it results in some kind of hang. I haven't looked more into why.

https://pastebin.com/7ePfTMMg

cc: @zou3519 @ydwu4 

### Versions

N/A

cc @ezyang @anijain2305 @chauhang @penguinwu @zou3519 @bdhirsh