sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: The debugging process fails to start when the code contains an import from npm.
Labels: bug,debugger

The debugging process fails to start when the code contains an import from npm. However, the code runs without errors when debugging is not enabled. 

deno 1.32.3
windows 11 

```
//import ccxt from "https://esm.sh/ccxt";
import ccxt from "npm:ccxt";

import { OHLCVConfig, getUniqueExchangesId } from "./helpers.ts"

interface OHLCVRecord {
  exchangeId: string;
  symbol: string;
  rtimestamp: number;
  timestamp: number;
  open?: number;
  high?: number;
  low?: number;
  close?: number;
  volume?: number;
}


const ohlcvConfig: OHLCVConfig[] = [{
  exchangeId: 'binance',
  symbol: 'BTC/USDT',
  timeframe: '1h',
  since: 0,
  timeOffsetForAction: 0,
  allowedTimeDeviation: 0
},
{
  exchangeId: 'bybit',
  symbol: 'BTC/USDT',
  timeframe: '1h',
  since: 0,
  timeOffsetForAction: 0,
  allowedTimeDeviation: 0
}
];

const uniqueExchangeIds = getUniqueExchangesId(ohlcvConfig)
console.log(uniqueExchangeIds); // Output: ['binance', 'kraken']

let exchanges: any[] = [];


for (const uniqueExchangeId of uniqueExchangeIds) {
  const ExchangeClass = ccxt[uniqueExchangeId];
  const exchangeInstance = new ExchangeClass();
  exchanges[uniqueExchangeId] = exchangeInstance;
}

```
Repository: rust
Issue: E0460 long description is too optimistic about cargo's abilities
Labels: T-bootstrap,A-docs,A-error-codes

### Location

https://github.com/rust-lang/rust/blob/5ecac8ede670ac8045a199cd3bcd58bd940ec8d4/compiler/rustc_error_codes/src/error_codes/E0460.md#L61-L67

### Summary

This makes the claim "using cargo will automatically fix your problem". This is unfortunately not true. Consider the following error found while working on https://github.com/rust-lang/rust/issues/81930:

```
error[E0460]: found possibly newer version of crate `core` which `itoa` depends on
   --> /home/jyn/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/serde_json-1.0.85/src/number.rs:295:49
    |
295 |             N::PosInt(u) => formatter.write_str(itoa::Buffer::new().format(u)),
    |                                                 ^^^^
    |
    = note: perhaps that crate needs to be recompiled?
    = note: the following crate versions were found:
            crate `core`: /home/jyn/src/rust2/build/x86_64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-5670a3f7cd4c9169.rmeta
            crate `itoa`: /home/jyn/src/rust2/build/x86_64-unknown-linux-gnu/stage0-tools/x86_64-unknown-linux-gnu/release/deps/libitoa-c25ddfbc66feadac.rmeta
```

All the dependencies involved here were compiled by cargo, but the error still appears. I am currently trying to figure out why; I think it's related to rebuilding the sysroot, but cargo not noticing that it needs to recompile a crate that depends on `core`? Maybe rustc needs to add a dependency edge to the `.d` files it emits?

cc https://github.com/rust-lang/rust/issues/76720#issuecomment-1369507582, @Ezrashaw
Repository: next.js
Issue: Caching data doesn't work in middleware
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant packages:
      next: 13.3.1-canary.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/wandering-worker-7g6q59

### To Reproduce

1. open codesandbox example
2. open console
3. see such log
<img width="610" alt="image" src="https://user-images.githubusercontent.com/10497370/230794937-f6c398b8-ae9c-4cd5-b9bc-dc891b495112.png">

### Describe the Bug

React cache() doesn't work in middleware.

### Expected Behavior

In middleware should be used cached data for same request.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: x/website/tour: tour packaged not just in website
Labels: NeedsInvestigation

### What did you do?

Tour package is confused on pkg.go.dev.

Start at https://pkg.go.dev/golang.org/x/website#section-directories
click on "tour" at the bottom for
https://pkg.go.dev/golang.org/x/website@v0.0.0-20230405163443-41e922072f17/tour

At the top left just after `Version` click "Go to latest" button for

https://pkg.go.dev/golang.org/x/website/tour

    v0
    v0.0.0-20210616181959-e0d934b43647
    Jun 16, 2021

Why is there a release of tour from website outside of website?

Or perhaps, why is that release not automatically updated with the website releases?

### What did you expect to see?

Just the docs inside the website pkg, or a frequently updated website/tour package doc.

### What did you see instead?

One old version of the website/tour packaged alone.

### Questions I have

Should the single x/website/tour package have ever been made?

Is pkg.go.dev wrong for saying the older, but directly packaged x/website/tour is the latest?
Repository: stable-diffusion-webui
Issue: [Bug]: xyz include sub images not work
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

only include sub grids

![image](https://user-images.githubusercontent.com/167966/230798402-50e29b96-e1ca-45d1-bc99-8bbff9ac73a0.png)


### Steps to reproduce the problem

![image](https://user-images.githubusercontent.com/167966/230798208-cea92d3a-605d-4fec-ac11-aa4a8dfa99ec.png)



### What should have happened?

include sub images

### Commit where the problem happens

22bcc7be

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
.
```


### List of extensions

.

### Console logs

```Shell
.
```


### Additional information

_No response_
Repository: next.js
Issue: Middleware & Headers When deploying outside vercel like AWS
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
middleware not passing data to route handler (edge functions) on production neither on a container or on elastic beanstalk it only works on local and vercel
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://github.com/Storxy/storxy-business-erp

### To Reproduce

middleware not passing data to route handler (edge functions) on production neither on a container or on elastic beanstalk it only works on local and vercel

### Describe the Bug

middleware not passing data to route handler (edge functions) on production neither on a container or on elastic beanstalk it only works on local and vercel

### Expected Behavior

to pass the user id to route handlers

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: TypeScript
Issue: Allow top-level await in namespaces
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

Top, level, await, namespace, export

## ✅ Viability Checklist
My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion
Allow top-level await in namespaces.

Current behaviour:
```typescript
// ok
await 1;

export namespace Example {
	// not ok
	await 1;
}
```

## 📃 Motivating Example
Current:
```typescript
export const _keyValuePair = await idbKeyValuePair.load("name");
export namespace storage {
	export const keyValuePair = _keyValuePair;
}
```

## 💻 Use Cases
```typescript
export namespace storage {
	export const keyValuePair = await idbKeyValuePair.load("name");
}
```
Repository: next.js
Issue: Next app open blank screen on DingTalk app
Labels: create-next-app,bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
┌─[zhuxian@zhuxiandeMacBook-Pro] - [~/Documents/projects/learn/next-app] - [Mon Apr 10, 10:03]
└─[$]> next info      

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 16.17.1
      npm: 9.6.2
      Yarn: 1.22.19
      pnpm: 8.1.0
    Relevant packages:
      next: 13.3.0
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.3.0", newest: "13.3.1-canary.3".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/github/vercel/next.js/tree/canary/examples/reproduction-template-app-dir?file=README.md&selection=%5B%7B%22endColumn%22%3A20%2C%22endLineNumber%22%3A9%2C%22startColumn%22%3A14%2C%22startLineNumber%22%3A9%7D%5D

### To Reproduce

use DingTalk app to open a next blank project which created by create-next-app, page show nothing on Android, and show error "TypeError: undefined is not an object(evaluating 'stream.getReader')" when navigate to other page on IOS

### Describe the Bug

use DingTalk app to open a next blank project which created by create-next-app, page show nothing on Android, and show error "TypeError: undefined is not an object(evaluating 'stream.getReader')" when navigate to other page on IOS

### Expected Behavior

next-app can open and use fine on DingTalk

### Which browser are you using? (if relevant)

DingTalk app with latest version

### How are you deploying your application? (if relevant)

next dev
Repository: godot
Issue: SubViewPort.get_texture.get_image makes Godot stutter/jitter
Labels: discussion,topic:rendering,documentation,performance

### Godot version

4.0.2-stable

### System information

Ubuntu 22.04, RTX 3080, Vulkan API 1.3.224 - Forward+, OpenGL API 3.3.0 NVIDIA 525.60.13, X11, AMD 5900x

### Issue description

![https://i.imgur.com/qgSqlT1.png](https://i.imgur.com/qgSqlT1.png)

Each of these spikes is exactly 0.2sec apart and caused by the `get_image()` call in the following line:

```python3
# runs every 0.2sec
get_node("%subviewport").get_texture().get_image()
```

This micro-stutter is noticeable especially when walking around, moving with the mouse (FPS character, etc)

Some things I have noticed:

1. The size of the subviewport seems of no influence
2. The draw mode of the subviewport seems of no influence, for example `DEBUG_DRAW_UNSHADED` would still stutter
3. I tracked it down to the following call:

https://github.com/godotengine/godot/blob/278fc7538dbd98ff0e06410d69adca49b5326b21/drivers/vulkan/rendering_device_vulkan.cpp#L2844
I patched it with:

```cpp
if(tex->width != 127)
    _flush(true);
```

and set my subviewport size width to `127` so it doesn't `_flush()` for my specific case and the micro-stutter is gone. A flat line:

![https://i.imgur.com/kPVWr1P.png](https://i.imgur.com/kPVWr1P.png)

p.s: that FPS counter is mangohud, e.g: `mangohud ./bin/godot.linuxbsd.editor.x86_64`

### Steps to reproduce

1. Create a 3D scene
2. Create a `SubViewport` with a camera inside it
3. Get the texture of the subviewport via `get_texture()`
4. Call `get_image()` on that texture
5. Observe a stutter

Or download my minimal reproduction project

### Minimal reproduction project

[stutter_image_data.zip](https://github.com/godotengine/godot/files/11187209/stutter_image_data.zip)
Repository: tensorflow
Issue: Anyway to set the attr of operation after added to the gragh in C API?
Labels: stat:awaiting tensorflower,type:support,comp:apis,TF 2.11

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Support

### Have you reproduced the bug with TF nightly?

No

### Source

binary

### Tensorflow Version

tf2.11

### Custom Code

No

### OS Platform and Distribution

Windows and Linux

### Current Behaviour?

Hello, I'm a developer of [Tensorflow.NET](https://github.com/SciSharp/TensorFlow.NET), which is a tensorflow binding for dotnet. When I implemented some feature, I could not find a C API to add attributes to an operation that has already been created and added to the graph. However, there is indeed such C API for python. It's located [here](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/c/python_api.h#L33).

Among exported C APIs of `libtensorflow`, only the following API was found:

```c
TF_CAPI_EXPORT extern void TF_SetAttrValueProto(TF_OperationDescription* desc,
                                                const char* attr_name,
                                                const void* proto,
                                                size_t proto_len,
                                                TF_Status* status);
```



However, `TF_OperationDescription` is released after adding the operation to graph by calling `TF_FinishOperation`. Therefore I can't use the API to add attributes.

Is there any other way for us to add attributes for operations which have been added to graph?


### Standalone code to reproduce the issue

```shell
The code is wrote in csharp. I'll give a minimal example if needed.
```


### Relevant log output

_No response_</details>
Repository: neovim
Issue: `nvim_out_write` truncates messages when sent over RPC.
Labels: bug,api,ui,messages

### Problem

When `nvim_out_write` is sent via RPC, the message is truncated in the display. The message still appears properly in `:messages`. If this behavior is intended it should be documented (and would ideally be configurable).

### Steps to reproduce

1. Open Neovim with an 80 column width (verify with `set columns?`)
2. `let m = "This is a very long string. This is a very long string. This is a very long string.\n"`
3. `call nvim_out_write(m)`
4. Observe that the entire string is outputted (and the hit-enter prompt appears)
5. `let @+ = v:servername`
6. Open a new Neovim instance (make sure the original is still 80 columns wide). Follow the remaining steps in the new one.
7. `let sock = sockconnect("pipe", @+, { "rpc": 1 })`
8. `let m = "This is a very long string. This is a very long string. This is a very long string.\n"`
9. `call rpcrequest(sock, "nvim_out_write", m)`

### Expected behavior

The message is not truncated (and the hit-enter prompt appears).

### Neovim version (nvim -v)

NVIM v0.10.0-dev-19+g339011f59

### Vim (not Nvim) behaves the same?

No

### Operating system/version

Rocky Linux 8.6

### Terminal name/version

xfce4-terminal 1.0.4 

### $TERM environment variable

tmux-256color

### Installation

appimage
Repository: angular
Issue: Provide generic type for http request body
Labels: area: common/http,cross-cutting: types

### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

Now we can specify response type of POST method, but body is defined as `any`. I can't specify type for body.

### Proposed solution

```ts

public createUser(userData: UserDataModel): Observable<User> {
  return this.http.post<User, UserData>(url, userData);
}

```


### Alternatives considered

I doesn't have alternatives.
Repository: flutter
Issue: Not able to fetch placeholder test using appium inspector during automation testing
Labels: a: tests,a: text input,c: regression,framework,f: material design,has reproducible steps,found in release: 3.7,found in release: 3.10,team-design,triaged-design

I am using flutter 3.7.6 version and Appium Inspector Version: 1.22.3-4.20220515.3 , While we are trying to fetch the text placeholder from any of the text field than no value is coming. It was available in the earlier version (up to 3.7.4). Below is the image of error for your reference.

<img width="1512" alt="MicrosoftTeams-image" src="https://user-images.githubusercontent.com/87748782/230849294-407f779a-74f4-4f9f-84ab-6136a90029f0.png">
Repository: storybook
Issue: [Feature Request]: allow to overcome module resolution problems by stabilizing JS CLI entrypoint
Labels: feature request,monorepos

### Is your feature request related to a problem? Please describe

There are many (more than 20) open issues related to resolution (and transpilation) problems in PNPM, Yarn, vite in monorepo, etc.
Some examples are:
-  #21998, #21983, #21710, and others, just run a query `monorepo`

And my error case is:

```sh
@storybook/cli v7.0.2
info => Starting manager..
failed to load config from vite.config.ts
ERR! TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for node_modules/@COMPANY_NAME/SHARED_CONFIGS/vite.config.ts
```

The error above happens, when `vite.config.ts` is configured as follows:

```ts
import { getConfigDev } from "@COMPANY_NAME/SHARED_CONFIGS/vite.config"
import { defineConfig } from "vite"

export default defineConfig(getConfigDev)
```

As a short-term solution for everyone, you could make the CLI entrypoint stable to be executed by tools, such as: `ts-node`, `tsx`, etc. (I tried to use `tsx` and the Storybook's CLI entrypoint failed).

### Describe the solution you'd like

Please fix issues preventing to preprocess the user-defined configs that in turn result in module resolution problems.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

#### Packages used

```
"@storybook/react-vite": "7.0.2",
"storybook": "7.0.2"
```

I could assist in pointing to the problem. [The community solved the exact same problem](https://github.com/vitejs/vite/issues/9202#issuecomment-1255827608) in `vite`'s resolution issues in `vite.config.ts`
Here's an error that happens when you run:

```
$ tsx ../node_modules/@storybook/cli/dist/generate.js dev
```

the above `../node_modules/@storybook/cli/dist/generate.js` is an alternative to `storybook` bin alias

```sh
TypeError: (0 , import_node_url.pathToFileURL).then is not a function
    at getPreviewBuilder (node_modules/@storybook/core-server/dist/index.js:10:1987)
    at buildDevStandalone (node_modules/@storybook/core-server/dist/index.js:48:2082)
    at withTelemetry (node_modules/@storybook/core-server/dist/index.js:35:3422)
    at dev (node_modules/@storybook/cli/dist/generate.js:430:400)
    at Command.<anonymous> (node_modules/@storybook/cli/dist/generate.js:432:225)
 TypeError: (0 , import_node_url.pathToFileURL).then is not a function
    at getPreviewBuilder (node_modules/@storybook/core-server/dist/index.js:10:1987)
    at buildDevStandalone (node_modules/@storybook/core-server/dist/index.js:48:2082)
    at withTelemetry (node_modules/@storybook/core-server/dist/index.js:35:3422)
    at dev (node_modules/@storybook/cli/dist/generate.js:430:400)
    at Command.<anonymous> (node_modules/@storybook/cli/dist/generate.js:432:225)
```
Repository: PowerToys
Issue: [ci] Add script to CI to generate hashes table 
Labels: Area-Build,Cost-Small

              could have the script basically generate these lines to and have direct links 

|  Description   | Filename | sha256 hash |
|----------------|----------|-------------|
| Per user - x64       | [PowerToysUserSetup-0.69.0-x64.exe](https://github.com/microsoft/PowerToys/releases/download/v0.69.0/PowerToysUserSetup-0.69.0-x64.exe)     | D05FC31F137718516C1D792765AAFEC51551FC172064BC3EE170911E455053AC | 
| Per user - ARM64     | [PowerToysUserSetup-0.69.0-arm64.exe](https://github.com/microsoft/PowerToys/releases/download/v0.69.0/PowerToysUserSetup-0.69.0-arm64.exe) | 0B113EAF17EEEA86299DEF7F73E7AF15A9CBFB8033C7F9218E33BDA276F37727 | 
| Machine wide - x64   | [PowerToysSetup-0.69.0-x64.exe](https://github.com/microsoft/PowerToys/releases/download/v0.69.0/PowerToysSetup-0.69.0-x64.exe)             | ADE1E56DF8CC52839FBD9DB6A0BCF34E38B88AAA52544EEAD3C1BB023FDAF29A | 
| Machine wide - ARM64 | [PowerToysSetup-0.69.0-arm64.exe](https://github.com/microsoft/PowerToys/releases/download/v0.69.0/PowerToysSetup-0.69.0-arm64.exe)         | CF13F75F93462BE68CA3E4C90B23F3828BBCAA44E7AA987503E73652DCB9FDF8 |

_Originally posted by @crutkas in https://github.com/microsoft/PowerToys/issues/25257#issuecomment-1500683758_
Repository: rust
Issue: Unable to resolve HRTB/GAT lifetimes trait bounds
Labels: A-lifetimes,A-trait-system,C-bug,T-types,S-needs-repro,A-GATs,A-higher-ranked

I tried this code:

```rust
trait Trait {
    // Trait with a 'normal' type and a GAT
    type gat<'a>;
    type normal;
}

// Struct A and B define the same types

struct StructA;
impl Trait for StructA {
    type gat<'a> = ArrayView2<'a, f64>;
    type normal = Array2<f64>;
}

struct StructB;
impl Trait for StructB {
    type gat<'a> = ArrayView2<'a, f64>;
    type normal = Array2<f64>;
}

struct C<S, T>
where
    S: for<'a> Trait<gat<'a> = T::gat<'a>, normal = T::normal>,
    T: Trait,
{
    a: S,
    b: T,
}

fn test() {
    C {
        a: StructA {},
        b: StructB {},
    };
}
```

I expected that this should compile fine.

Instead, I get a compiler error, which is not helpful (well, to a beginner like me at least)

```
error[E0271]: type mismatch resolving `for<'a> <StructA as Trait>::gat<'a> == <_ as Trait>::gat<'a>`
  --> src/main.rs:51:12
   |
51 |         a: StructA {},
   |            ^^^^^^^^^^ type mismatch resolving `for<'a> <StructA as Trait>::gat<'a> == <_ as Trait>::gat<'a>`
   |
note: expected this to be `<_ as Trait>::gat<'_>`
  --> src/main.rs:30:20
   |
30 |     type gat<'a> = ArrayView2<'a, f64>;
   |                    ^^^^^^^^^^^^^^^^^^^
   = note: expected associated type `<_ as Trait>::gat<'_>`
                       found struct `ndarray::ArrayBase<ndarray::ViewRepr<&f64>, ndarray::Dim<[usize; 2]>>`
   = help: consider constraining the associated type `<_ as Trait>::gat<'_>` to `ndarray::ArrayBase<ndarray::ViewRepr<&f64>, ndarray::Dim<[usize; 2]>>` or calling a method that returns `<_ as Trait>::gat<'_>`
   = note: for more information, visit https://doc.rust-lang.org/book/ch19-03-advanced-traits.html
note: required by a bound in `C`
  --> src/main.rs:42:22
   |
40 | struct C<S, T>
   |        - required by a bound in this
41 | where
42 |     S: for<'a> Trait<gat<'a> = T::gat<'a>, normal = T::normal>,
   |                      ^^^^^^^^^^^^^^^^^^^^ required by this bound in `C`
```

The amazing community already provided me with workarounds [here](https://users.rust-lang.org/t/hrtb-and-gat-lifetimes-in-trait-bounds/92249), but recommended filing an issue

### Meta

`rustc --version --verbose`:
```
rustc 1.68.2 (9eb3afe9e 2023-03-27)
binary: rustc
commit-hash: 9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0
commit-date: 2023-03-27
host: x86_64-unknown-linux-gnu
release: 1.68.2
LLVM version: 15.0.6
```