sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Provide an updated OpenAPI Specification file (a/k/a "swagger file") with each release
Labels: documentation,api

### What are you trying to do?

Development and debugging of applications that call APIs require the use of tools to call the APIs to simulate actions that the applications would take.  Some of these tools include Postman and (arguably the best one now) Bruno. Additionally, API security testing tools, such as OWASP OFFAT, need to be able to call the APIs and exercise all of their functions in order to detect security bugs/vulnerabilities.
There is a standard for the developers of APIs, such as the Ollama maintainers, to document their APIs in a machine-readable format that is understood by these tools.  Ollama needs to provide such a description of the Ollama API, updated each time it changes. The standard format is the OpenAPI Specification, maintained by the OpenAPI Initiative, under the Linux Foundation.  Details can be found at: https://www.openapis.org/
Note: This was originally developed by a company called "Swagger", and later donated to the OpenAPI Initiative. Hence, files containing an OpenAPI description are sometimes referred to as "Swagger files".

### How should we solve this?

Fully document the ollama API in an OpenAPI format file, published and maintained as part of the ollama distribution in this repository. 

### What is the impact of not solving this?

It's necessary to either handcraft every request to the API, or build an OpenAPI format file to use with the tools. Some examples of these files crafted by people outside of the project exist, however, they at best represent the state of the API at the time that the file was made, and at worst, are both out of date, and inaccurate. It is the inaccuracy that is most concerning, since missing/incompletely described APIs inhibit the ability of security testing tools to test the entire attack surface presented by the API. 
An examination of the help messages on Discord, and the issues posted here in Github, show that Ollama's popularity as the backend of applications used by multiple people, across networks or the Internet, underscores the importance of making security testing as friction-free as possible, and a complete, maintained OpenAPI file is a key part of that.


### Anything else?

OpenAPI spec for OpenAI api -- https://github.com/openai/openai-openapi
OpenAPI Specification -- https://github.com/OAI/OpenAPI-Specification
A third party OpenAPI spec file for Ollama (last updated 2024-02-02; accuracy unknown) -- https://github.com/davidmigloz/langchain_dart/blob/main/packages/ollama_dart/oas/ollama-curated.yaml
Repository: tensorflow
Issue: Aborted (core dumped) with `tf.raw_ops.LoadAndRemapMatrix`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.tf.raw_ops.LoadAndRemapMatrix` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

num_rows = 7
num_cols = 16
max_rows_in_memory = -1
ckpt_path = tf.constant("/tmp", shape=[1], dtype=tf.string)
old_tensor_name = tf.constant("/tmp", shape=[1], dtype=tf.string)
row_remapping = tf.constant(-1, shape=[7], dtype=tf.int64)
col_remapping = tf.constant(0, shape=[], dtype=tf.int64)
initializing_values = tf.constant(42, shape=[112], dtype=tf.float32)
tf.raw_ops.LoadAndRemapMatrix(ckpt_path=ckpt_path, old_tensor_name=old_tensor_name, row_remapping=row_remapping, col_remapping=col_remapping, initializing_values=initializing_values, num_rows=num_rows, num_cols=num_cols, max_rows_in_memory=max_rows_in_memory)
```


### Relevant log output

```shell
2024-03-28 07:29:28.849010: F tensorflow/core/framework/tensor_shape.cc:45] Check failed: NDIMS == dims() (1 vs. 0)Asking for tensor of 1 dimensions from a tensor of 0 dimensions
Aborted (core dumped)
```
Repository: kubernetes
Issue: NodeRestriction Admission Controller Plugin: Update and Patch Pod Permissions
Labels: sig/node,sig/auth,triage/accepted

Hello, community! We've encountered the following issue: in our Kubernetes cluster, there was a need to grant certain plugin the same rights as kubelet to add specific annotations to a pod, depending on which node it has been scheduled to. The plugin works if we create a cluster role and a service account with rights to update/patch a pod. However, the problem is that, in such a case, it has the ability to modify pods across the entire cluster, which is unsafe. To solve this problem, so that annotations could be changed only on the node where it is running, we decided to use the NodeRestriction plugin, just as it works out of the box for kubelet (using a certificate in the system:nodes group and common name system:node:node_name). The issue is that, out of the box, the system:node only has rights to create/delete pods. But even if I add the system:nodes group rights on update/patch verbs, the NodeRestriction admission controller still intervenes and forbids pod updates, with this error:
`Failed due to pods "pod-name" is forbidden: unexpected operation "UPDATE", node "node123" can only create and delete mirror pods. `
I looked into the documentation and also studied the source code, and it seems that NodeRestriction lacks ways to add additional allowed verbs for pod modifications. Dear community, has anyone solved this problem? Is there a way to deal with this issue out of the box, without rewriting the NodeRestriction code?
Repository: opencv
Issue: static cv::Mutex in function getPooledInstance() hurt multithreading perfermance
Labels: bug,optimization,category: flann

### System Information

OpenCV version: 4.8.0
Operating System / Platform: Ubuntu 20.04
Compiler & compiler version: GCC 9.3.0

### Detailed description

https://github.com/opencv/opencv/blob/a132fd401ec459a722b2dd793c3b44d8f3f001a1/modules/flann/include/opencv2/flann/heap.h#L188
```
static cv::Mutex mutex;
const cv::AutoLock lock(mutex);
```
block multi-threads, making FlannBasedMatcher perform worse than BFMatcher, degrading the CPU usage from 2000% to 300%
![flamegraph](https://github.com/opencv/opencv/assets/8348898/e4402d1d-9288-425b-8196-83f302d8d5b8)


### Steps to reproduce

```
#pragma omp parallel for collapse(3) default(shared)
    for (int i = 0; i < grid_num.x(); ++i) {
        for (int j = 0; j < grid_num.y(); ++j) {
            for (int k = 0; k < grid_num.z(); ++k) {
                ...
                descriptor_matcher->radiusMatch(descriptors_new, cv_matches, (float) max_metric_dist_);
                ...
            }
        }
    }
```

### 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: TypeScript
Issue: Shorter tuple inference gets picked over longer inference when both come from rests
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

inference contravariant covariance rest shorter longer tuples

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.5.0-dev.20240327#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVNQB4BBeEADwxFWAGd44pg8IBPeNAa1RwHdUA2gF0AfAAoAsACh48WAHMAXPDEA6dQtrLiASngBeEfABuOLMAA002etWbt0ndoDc0sHloZ4WVIhAw4YAMCMTEoZVRkAFsAI389Q3gAbwBfC3gARnSAJh1neAB6AvgAUXIAB3AqIOy5GHlo6gxadJjkL3kcLwBmVTFsgFYBgBYdaSLZWQA9AH54d1RPb19-QOUBcPhI2P8hNw8vHz8AkGBa-RCwiOi4mFaZ652YBKNU9Iy8wuKcTnHiydm8wOy2OgWy622tz2UgWSyOq1O3WCiFQoU2kP890etxeyTSmTk9FhGE+Ex+f0m8EBxJBCOA3XWGWhQA

### 💻 Code

```ts
declare function fn<A extends readonly unknown[]>(
  arg: (...args: A) => void,
  ...args: A
): A;
const inferred = fn((a: number) => {}, 1, 2); // Expected 2 arguments, but got 3.(2554)
//    ^? const inferred: [a: number]
const inferred2 = fn((a: number, b?: number) => {}, 1); // ok
//    ^? const inferred2: [number]
const inferred3 = fn((a: number, b?: number) => {}, 1 as const); // ok
//    ^? const inferred3: [1]
```


### 🙁 Actual behavior

`inferred` is `[a: number]` and the function call fails

### 🙂 Expected behavior

`inferred` should be `[number, number]` and the function call should succeed. 

### Additional information about the issue

Based on `inferred2` and `inferred3` we can see that the covariant inference is preferred in a situation like this. The problem is the `.length` mismatch between those 2 candidates but since the contravariant candidate comes from a rest position it should be ignored when comparing those 2 candidates and the covariant inference should be preferred
Repository: ant-design
Issue: The first few submenu items are not available
Labels: Inactive,improvement

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-hr8nfr?file=demo.tsx)

### Steps to reproduce

Create a menu with a sufficiently large number of items (as in the demo)

Preview link https://react-hr8nfr.stackblitz.io

### What is expected?

It is possible to view all the items in the submenu

### What is actually happening?

The first items of the submenu are hidden (not available)

| Environment | Info |
| --- | --- |
| antd | 5.15.4 |
| React | 18.x |
| System | macOS |
| Browser | google chrome 116.0.5845.140 |

---
CSS attribute `inset` of the submenu container has a negative value of `top` which leads to the problem

![image](https://github.com/ant-design/ant-design/assets/7424691/42735991-23de-4aa8-ad3e-d5a8c411df91)

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: `trailingSlash` setting not honored for next/image with placeholder="blur"
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/gabrielf/nextjs-image-blur-trailingslash

### To Reproduce

1. Clone the repo
2. Run `npm i` and `npm run dev`
3. Visit <http://localhost:3000> and check the network tab in the developer tools

### Current vs. Expected behavior

### Expected
Setting `trailingSlash: true` should add slashes to all image paths including the one to the blurred placeholder image. The example app should be served with no redirects.

### Actual
The blurred placeholder has an image path without trailing slash which leads to an extra request (see screenshot below)

![image](https://github.com/vercel/next.js/assets/137649/a556b5a4-bb92-4034-a088-4615354b15a2)

The path to the blurred image is generated as `/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ftest.fab2915d.jpg&w=8&q=70` (no trailing slash) when it should be `/_next/image/?url=%2F_next%2Fstatic%2Fmedia%2Ftest.fab2915d.jpg&w=8&q=70` (with trailing slash)

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:31:00 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: N/A
  pnpm: 8.15.5
Relevant Packages:
  next: 14.2.0-canary.46 // Latest available version is detected (14.2.0-canary.46).
  eslint-config-next: 14.1.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.3
Next.js Config:
  output: N/A
```


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

Image optimization (next/image, next/legacy/image)

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

next dev (local)

### Additional context

The problem only seems to exist when running with `npm run dev`.
Repository: vscode
Issue: Normal text in chat input doesn't work well in HC themes
Labels: bug,inline-chat,panel-chat,terminal-chat

https://github.com/microsoft/vscode/issues/208708

* any chat UI (inline, panel, quick, terminal)
* use HC theme (dark or light)
* type a query
* select the text
* poor/no contrast between background and foreground
Repository: go
Issue: x/pkgsite: Deprecation annotation for packages isn't displayed
Labels: FeatureRequest,pkgsite

<!--
Please answer these questions before submitting your issue. Thanks!

If you would like to have your package removed, please file an issue at https://golang.org/s/pkgsite-package-removal.
-->
 
### What is the URL of the page with the issue?
 
 https://pkg.go.dev/google.golang.org/api@v0.171.0/sql/v1beta4
 
### What is your user agent?
 
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
 [Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:99.0) Gecko/20100101 Firefox/99.0](https://explore.whatismybrowser.com/useragents/parse/?analyse-my-user-agent=yes)
 
### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
-->
 
I opened the page above. 
 
### What did you expect to see?
 
A prominent deprecation warning next to the package description. I expect this, because the [package comment](https://github.com/googleapis/google-api-go-client/blob/v0.171.0/sql/v1beta4/sql-gen.go#L43) for the source file starts with "// Deprecated: ".
 
### What did you see instead?

No mention of the package being deprecated.
Repository: PowerToys
Issue: Cannot open PowerToys, after a flash white the app crashed
Labels: Issue-Bug,Product-Settings,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

When I opened PowerToys, it just showed a flash white then disapper.
And I found windows event viewer said there is an error then crashed.
![powertoys_flashing_white](https://github.com/microsoft/PowerToys/assets/31677847/cc9d2eeb-2f94-4b29-9606-25f4be6f44d9)
![powertoys_crash_event](https://github.com/microsoft/PowerToys/assets/31677847/27636284-36dc-4dd2-a50b-7dc17f91fe5e)
[PowerToysReport_2024-03-28-16-59-18.zip](https://github.com/microsoft/PowerToys/files/14786943/PowerToysReport_2024-03-28-16-59-18.zip)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: rust
Issue: error: Error loading target specification: Could not find specification for target "riscv64-unknown-linux-gnu".
Labels: T-compiler,O-riscv,C-discussion,A-targets

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/flake-pilot/standard/riscv64

+ make compile_sci_static
cd firecracker-pilot/guestvm-tools/sci && RUSTFLAGS='-C target-feature=+crt-static' cargo build -v --profile static --target riscv64-unknown-linux-gnu
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -C target-feature=+crt-static --target riscv64-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "riscv64-unknown-linux-gnu". Run `rustc --print target-list` for a list of built-in targets

make: *** [Makefile:72: compile_sci_static] Error 101
Repository: material-ui
Issue: [material-ui][Autocomplete] Using limitTags prevents clicking buttons outside of autocomplete while autocomplete is focused
Labels: package: material-ui,component: autocomplete

### Steps to reproduce

Link to live example: [issue is also in the MUI docs](https://mui.com/material-ui/react-autocomplete/#limit-tags)

Steps:
1. Select options until there are more than limitTags options selected
2. Try to click a button outside of the autocomplete (e.g. the 'expand code' button)


### Current behavior

The autocomplete is unfocused, but the click on the button is ignored.

### Expected behavior

The click is also propagated to the button.

### Context

We have a form with an AutoComplete where we set `limitTags` to prevent the AutoComplete from growing indefinitely. When people make a change to the selection in the AutoComplete and immediately click our 'Save changes' button, the click is not propagated to the button and the changes are not saved.

### Your environment

Tested on latest Chrome (linux and mac) and Firefox (linux).

**Search keywords**: Autocomplete limitTags
Repository: angular
Issue: Add further documentation about TestBed.override features
Labels: P3,docsarea: testing,area: docs

### Describe the problem that you experienced

Lack of documentation and code samples on `TestBed.overrideComponent/overrideDirective/overrideModule` makes it difficult to use these features.

### Enter the URL of the topic with the problem

https://angular.dev/guide/testing/components-scenarios#override-component-providers

### Describe what you were looking for in the documentation

It would be great to have detailed documentation on `TestBed.override` together with code samples.

### Describe the actions that led you to experience the problem

I am trying to implement a test suite that relies on `TestBed.override` but I am struggling with it. Lack of documentation about this topic doesn't help.

I opened a post on SO here: https://stackoverflow.com/questions/78233992/issues-with-overriding-an-ngrx-store-setup-in-a-test-with-testbed-overridemodule that demonstrates the exact issue.

### Describe what you want to experience that would fix the problem

Updated documentation on `TestBed.override`.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_
Repository: flutter
Issue: Add state restoration to `LicensePage`
Labels: framework,f: material design,c: proposal,P2,a: state restoration,team-design,triaged-design

### Use case

I'm setting up state restoration for my app, but `LicensePage` doesn't have support for it. For instance, if I scroll down in the `LicensePage` and then leave the app while "Don't keep activities" is enabled, the scroll position is lost. And if I press on one of the list tiles, opening a new page with the licenses of a specific package, then I leave the app and open it again, I'm thrown back to the main `LicensePage`.

To be clear, I'm not using `showLicensePage` here, because I'm aware that it uses `Navigator.push` to push the `LicensePage` route, where `Navigator.push` doesn't support state restoration. So I used `Navigator.restorablePush` manually to push the page route:

```dart
class FooWidget extends StatelessWidget {
  @pragma('vm:entry-point')
  static Route<void> _buildLicensePageRoute(
      BuildContext context, Object? arguments) {
    return MaterialPageRoute(
      builder: (context) => LicensePage(
        applicationName: 'foo',
        applicationVersion: 'v1.0.0',
      ),
    );
  }

  @override
  Widget build(BuildContext context) {
    // ...
    return TextButton(child: Text('foo'), onPressed: () => Navigator.restorablePush(context, _buildLicensePageRoute));
  }
}
```

Which is why the main `LicensePage` route itself is still restored.

### Proposal

Add state restoration support in `LicensePage` and its subpages.
Repository: tauri
Issue: [bug] Teared Up Screen on starting the tauri application in Raspberry Pi
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

I've generated the tauri template using the following commands -  
```
cargo install create-tauri-app --locked
cargo create-tauri-app
```
I've not changed the code in the demo template.
By following the official docs for cross-compilation, I've successfully generated the output bundle of the app for arm64 device but when I run the application on Raspberry Pi 4 B the following screen shows up -

![photo_2024-03-28_13-09-47](https://github.com/tauri-apps/tauri/assets/86215447/b39f16a4-985d-4bf2-bac9-328fb8452e5e)

Note that I've changed the screen size on both the tauri.conf.json and style.css file according to the Raspberry Pi screen size.

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Ubuntu 22.4.0 X64
    ✔ webkit2gtk-4.0: 2.42.5
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.77.0 (aedd173a2 2024-03-17)
    ✔ cargo: 1.77.0 (3fe68eabf 2024-02-29)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 12.22.9
    - npm: 8.5.1

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.8
    - tauri-cli [RUST]: 1.5.11
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src
    - devPath: ../src
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: godot
Issue: Setting a CanvasTexture inside AnimatedTexture spams debug with errors
Labels: bug,topic:rendering,needs testing

### Tested versions

Reproducible in 4.2.1 and 4.3 dev 4

### System information

Godot v4.3.dev4 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon RX 7800 XT (Advanced Micro Devices, Inc.; 31.0.24002.92) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

Trying to set an empty CanvasTexture as the first frame in a AnimatedTexture resource spams the console with errors:
![image](https://github.com/godotengine/godot/assets/47953199/62908222-6341-4860-8517-47ba147a5be3)

### Steps to reproduce

1. Add a Sprite2D node
2. Set the texture to AnimatedTexture
3. Set `Frame 0` texture to CanvasTexture

![image](https://github.com/godotengine/godot/assets/47953199/0edb62d9-7454-46fa-aa6b-41357fe23c3d)

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Consider enabling terminal sticky scroll by default in stable
Labels: feature-request,terminal-sticky-scroll

It's been on by default in Insiders for a few months now and there haven't been many complaints

fyi @meganrogge
Repository: vscode
Issue: Edit language configuration files for C++ in order to indent after if/for/while statement with no brace
Labels: bug,editor-autoindent

This issue is in relation to https://github.com/microsoft/vscode/issues/43244#issuecomment-2024859814

We would like to indent after if/for/while statements with no brace for C++ and potentially other languages too