sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Command line option to override alwaysOnTop
Labels: Product-Terminal,Issue-Task,Area-Commandline

 Is there a way to override these (maybe even others) when creating a new window?

`-w -1 -M` and `-w -1 -F` are limited versions of what I want to do.

I've read a few (old) threads on specifying a settings file on the command line (valid only if creating a new window).  That would seem to be the most robust way to override anything and I'm surprised it hasn't been implemented.

Another thought (hardly well thought-out) ... allow (possibly multiple) command line options like
`--option (-o) global_option_name value`, again only for new windows.
Repository: next.js
Issue: Data fetching strategy fallback: "loading" behavior is no longer achievable in Next.js 13
Labels: bug,Pages Router

### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release


### Which area(s) of Next.js are affected?

Data fetching (gS(S)P, getInitialProps)


### To Reproduce

```
import React from "react"

async function simulateAPICallGetCurrentDate() {
  return new Promise(resolve => {
       setTimeout(() => {
           resolve(new Date().toString())
      }, 1000)
   })
}

export default async function Page() {
  const date = await simulateAPICallGetCurrentDate()
  return (
    <div>{date}</div>
  );
}

export const revalidate = 10
```

### Describe the Bug

After 20 seconds, if you refresh the page you will see the value from twenty seconds ago even though the valid cache window is 10 seconds. 

### Expected Behavior

Ideally, the app would **not** immediately serve the cached page. Since we are outside the valid revalidate window, I do not want to serve the cached value any longer. That's what we used to use `fallback: 'loading'` to achieve. It seems no longer possible to do this.
Repository: vscode
Issue: Support data driven unit tests in the vscode test runner
Labels: feature-request,engineering,testing

Some duplication in test code could be reduced by allowing for data driven tests or suites. As of now, test or suite names with a non-static string won't be recognized.

```
[true, false].forEach((isScratchpad) => {
	suite(`UntitledFileWorkingCopy${isScratchpad ? ' - scratchpad' : ''}`, () => {
```
Repository: vscode
Issue: Simple browser will be opened multiple times with race
Labels: bug,help wanted,good first issue,webview

<!-- ⚠️⚠️ 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.78.2
- OS Version: macOS Ventura Version 13.4 Beta

Steps to Reproduce:

1. Download or package extension yourself in reproduce repo https://github.com/mustard-mh/test/tree/vscode/simple-browser-bug
    - Extension will exec open Simple Browser api when active [[1](https://github.com/mustard-mh/test/blob/63d37d3d66289adfa87b86c429b58107f15fa677/extension.js#L8-L12)]
    - Active extension with event `*` [[1](https://github.com/mustard-mh/test/blob/63d37d3d66289adfa87b86c429b58107f15fa677/package.json#L14)]
2. Install extension in your VSCode Desktop
3. Reload window without Simple Browser tab focus

![May-18-2023 02-39-18](https://github.com/microsoft/vscode/assets/20944364/5cefa34d-992c-4dd3-abec-59c1d8016e09)
Repository: rust
Issue: `try_into` invalid suggestion
Labels: A-diagnostics,T-compiler,D-invalid-suggestion

### Code

```Rust
use std::ops::Deref;

struct Foo();

impl Deref for Foo {
    type Target = [u8];

    fn deref(&self) -> &Self::Target {
        &[0, 0, 0, 0]
    }
}

fn main() {
    let f = Foo();
    let i = i32::from_le_bytes(f.try_into().unwrap());
}
```


### Current output

```Shell
Compiling tmp v0.1.0 (/home/ubuntu/tmp)
error[E0277]: the trait bound `[u8; 4]: From<Foo>` is not satisfied
  --> src/main.rs:19:34
   |
19 |     let i = i32::from_le_bytes(f.try_into().unwrap());
   |                                  ^^^^^^^^ the trait `From<Foo>` is not implemented for `[u8; 4]`
   |
   = help: the following other types implement trait `From<T>`:
             <&'input [u8] as From<gimli::read::endian_slice::EndianSlice<'input, Endian>>>
             <[T; 10] as From<(T, T, T, T, T, T, T, T, T, T)>>
             <[T; 11] as From<(T, T, T, T, T, T, T, T, T, T, T)>>
             <[T; 12] as From<(T, T, T, T, T, T, T, T, T, T, T, T)>>
             <[T; 1] as From<(T,)>>
             <[T; 2] as From<(T, T)>>
             <[T; 3] as From<(T, T, T)>>
             <[T; 4] as From<(T, T, T, T)>>
           and 7 others
   = note: required for `Foo` to implement `Into<[u8; 4]>`
   = note: required for `[u8; 4]` to implement `TryFrom<Foo>`
   = note: required for `Foo` to implement `TryInto<[u8; 4]>`
help: convert the array to a `&'input [u8]` slice instead
   |
19 |     let i = i32::from_le_bytes(f.&try_into[..]().unwrap());
   |                                  +        ++++
```


### Desired output

```Shell
help: deference `f`
   |
19 |     let i = i32::from_le_bytes((*f).try_into().unwrap());
   |                                ++ +
```


### Rationale and extra context

The help suggestion is invalid syntax.

### Other cases

_No response_

### Anything else?

Given the nature of traits and Deref impls, it may be impossible to get the error message that I supply above, but the suggested fix is invalid syntax.
Repository: electron
Issue: [Feature Request]: File API - get relative paths instead of absolute paths when selecting files
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Currently, when using the renderer File API, Electron provides a path value that includes the absolute path to the selected files.  This is fine in most cases, but there are times when the relative path is needed.  For example, we may want to know what location the user selected and drop a set of files from their host system.

In my case, I want to re-construct the folder structure of the selected files, but because I get the absolute paths of each file, it is not possible to determine the starting directory of the items chosen by the user.  If given relative paths, this would be trivial.

This is also how the file API in a typical browser works as well - if a user drops files and folders into the browser, the file API returns the list of files with relative paths.  This makes it easy to determine the starting path for the selected files based on what the user selected.


### Proposed Solution

I would like some kind of option to enable to disable relative paths in the Electron renderer File API.  Or at least add an additional file value that has the original relative path that a browser would normally provide.  

This would also be helpful for those who create apps that exist both in the browser and as an electron application.

### Alternatives Considered

I do not know of any alternative approaches to this, but I may be missing a feature that already exists in Electron.

### Additional Information

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: Interface becomes unresponsive on remote devices when using --listen
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

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

### What happened?

The webui works fine on my desktop computer, but when I try to use another device on my network, such as my phone or a laptop, it works for a while and then starts to hang on 'waiting' and becomes unresponsive. 

### Steps to reproduce the problem

1. Run webui.bat with --listen
2. Generate a few pictures on another device
3. Observe that it's stopped working after 2-5 generations

### What should have happened?

It should have kept generating and responding.

### Commit where the problem happens

89f9faa63388756314e8a1d96cf86bf5e0663045

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

Windows, Android

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

_No response_

### Command Line Arguments

```Shell
--listen --api --xformers --medvram
```


### List of extensions

clip-interrogator-ext, sd-dynamic-thresholding, sd-extension-aesthetic-scorer, sd-webui-controlnet, sd_dreambooth_extension, sd_smartprocess, stable-diffusion-webui-dataset-tag-editor, stable-diffusion-webui-images-browser, stable-diffusion-webui-two-shot

### Console logs

```Shell
Nothing in log after bug.
```


### Additional information

Have tried various commits and disabling various extensions. It used to work but hasn't worked reliably for some weeks. Fine on the central computer, just not devices connected with --listen.
Repository: rust
Issue: "error[E0519]: the current crate is indistinguishable from one of its dependencies" does not always accurately describe the problem
Labels: A-diagnostics,A-metadata,C-bug

We were seeing `error[E0519]: the current crate is indistinguishable from one of its dependencies` in our build and couldn't really make sense of it because it was complaining about things like `log` crate inside `html5ever`. It turns out that chromium added https://source.chromium.org/chromium/chromium/src/+/main:build/rust/cargo_crate.gni;l=102?q=rustc_metadata&ss=chromium
```
_rustc_metadata = ""
  if (defined(invoker.rustc_metadata)) {
    _rustc_metadata = invoker.rustc_metadata
  } else if (defined(invoker.epoch)) {
    _rustc_metadata = invoker.epoch
  }
```
which defaults to using the epoch in `-Cmetadata=${_rustc_metadata}`
If you happen to have two different crates with the same symbol and same epoch (but different crate names), you'll get this error, but the description of the problem is confusing because it actually has nothing to do with crate names in this case `it has the same crate-name log and was compiled with the same -C metadata arguments` 
The crate name appears to be irrelevant if you supply the same metadata arguments because we fixed it with this
```
_metadata = "0"
  if (defined(invoker.epoch)) {
    _metadata = invoker.epoch
  }
  if (defined(invoker.crate_name)) {
    _metadata += invoker.crate_name
  }
```
Repository: rust
Issue: Rustc recommends wrong fix for wrongly passing a slice over references instead of slice over geneirc type.
Labels: A-diagnostics,T-compiler,D-invalid-suggestion

### Code

```Rust
fn test<T: Trait>(a: &[T]){}

trait Trait {}
struct Concrete(i32);

impl Trait for Concrete {}

fn main(){
    let a = &Concrete(5);
    test(&[a]);
}
```


### Current output

```Shell
...
help: consider removing the leading `&`-reference
   |
10 -     test(&[a]);
10 +     test([a]);
   |
```


### Desired output

```Shell
...
help: consider removing the leading `&`-reference
   |
9  -     let a = &Concrete(5);
9  +     let a = Concrete(5);
   |
```


### Rationale and extra context

the suggested help message, when applied, will cause another issue: "expected reference found array" as it changes the argument from a slice to a array

### Other cases

_No response_

### Anything else?

Issue exists in Release 1.69.0 and Nightly 1.71.0-nightly 2023-05-16 e77366b57b799dfa3ce1

playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=0f65b317e31cdba4454d8f60cb41cbf2
Repository: TypeScript
Issue: Autocompletion is not working for TypeScript paths alias in import statements when omitting "baseUrl"
Labels: Needs Investigation,Rescheduled

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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: Version: 1.79.0-insider
- OS Version: Darwin arm64 22.4.0

Steps to Reproduce:

1. Create a tsconfig.json with paths alias without specifying a "baseUrl":
```json
{
  "compilerOptions": {
    "paths": {
      "~/*": ["./src/*"],
    },
  },
}
```

2. Try to trigger the autocompletion:
<img width="620" alt="image" src="https://github.com/microsoft/vscode/assets/1443499/394c750a-fa3e-4850-9b12-85db01b52bb0">

If `baseUrl` is set like `"baseUrl": "."`, here is the result of the autocompletion:
<img width="592" alt="image" src="https://github.com/microsoft/vscode/assets/1443499/75cd3e0f-1708-499e-8c9f-a2988d838889">

As `baseUrl` is optional since TypeScript 4.1, shouldn't VS Code set it to the same folder path where the `tsconfig.json` is located if omitted?
Repository: storybook
Issue: Better document testing-library's queries, e.g. `getByRole`
Labels: documentation

Related discussions: https://github.com/storybookjs/storybook/discussions/22429#discussioncomment-5819924 and https://github.com/storybookjs/storybook/discussions/22429#discussioncomment-6083738

I don't think we should document the full API, but we should point to https://testing-library.com/docs/queries/about in a clear and obvious manner, perhaps with one key example demonstrating a reasonably-full usage of their API.
Repository: node
Issue: ibmi: test.parallel/test-net-autoselectfamily-commandline-option fails
Labels: ibm i

https://ci.nodejs.org/job/node-test-commit-ibmi/nodes=ibmi73-ppc64/1159/testReport/(root)/test/parallel_test_net_autoselectfamily_commandline_option/



```
node:assert:125
  throw new AssertionError(obj);
  ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected

+ 'Unknown system error -42'
- 'EADDRNOTAVAIL'
    at Socket.<anonymous> (/home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi73-ppc64/test/parallel/test-net-autoselectfamily-commandline-option.js:89:18)
    at Socket.<anonymous> (/home/IOJS/build/workspace/node-test-commit-ibmi/nodes/ibmi73-ppc64/test/common/index.js:463:15)
    at Socket.emit (node:events:511:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: 'Unknown system error -42',
  expected: 'EADDRNOTAVAIL',
  operator: 'strictEqual'
}

Node.js v21.0.0-pre
```
Repository: go
Issue: proposal: math: Reflect, Least, Greatest
Labels: Proposal

```go
package math

func Reflect[T Number]() Kind
type Kind uint
func (Kind) Size() int
func (Kind) Ordered() bool
func (Kind) Float() bool
func (Kind) Complex() bool
func (Kind) Signed() bool
func (Kind) Unsigned() bool
func (Kind) Integer() bool

func Least[T Ordered]() T
func Greatest[T Ordered]() T

func Convert[S, T Number](T) (S, bool)
```

Reflect returns a Kind bitset that provides information about the properties of a numeric type. The bool returning methods correspond with the constraints and Size returns 8, 16, etc. Since this is about the properties of the type not its identity `Reflect[int]() == Reflect[int64]()` on platforms where int is 64 bits.

Least (Greatest) return the element that is `<=` (`>=`) every element in T. For example, `Greatest[float64]()` is `math.Inf(0)`, `Least[uint]()` is 0, and `Greatest[int16]` is `math.MaxInt16`.

Convert performs the conversion between numeric types S and T and the boolean reports whether the conversion was lossless, returning false if there was any truncation or wrapping.

Future versions of the language may allow `Reflect` to be written using type switches but this would still provide a more convenient interface.

<hr>

For convenience, I've assumed #52427 is accepted and that `Unsigned`, `Signed`, `Integer`, `Float`, and `Complex` have been moved into package math.

I have also assumed that these additional constraints are defined:
```go
type Ordered Integer | Float
type Number Ordered | Complex
```
The `Ordered` constraint is similar to that in package `cmp` except that it does not include `~string`. The package qualification should be sufficient to disambiguate.

If this api is too much or too different for math, it, and all the constraints, could go into a new package, `math/number` or the like.
Repository: go
Issue: x/vulndb: improve internal/proxy package
Labels: vulncheck or vulndb

- Refactor to make it easier to test
- Add unit tests
- Cache proxy lookups
Repository: storybook
Issue: Add example of using `useArgs` in a decorator to update arg values
Labels: documentation

Related discussions: https://github.com/storybookjs/storybook/discussions/22507#discussioncomment-5863792 & https://github.com/storybookjs/storybook/discussions/22640#discussioncomment-5948053 & https://github.com/storybookjs/storybook/discussions/22507#discussioncomment-6683435

This technique can be used to make a story reactive to _both_ controls and the component's interactions itself. E.g. in React, a controlled checkbox could become checked by clicking it (and the control's value would update to reflect that) or by toggling the control to `true`.
Repository: neovim
Issue: API for cmdline history
Labels: enhancement,api

### Problem

Currently, there is a nice internal history for `search`,`input`,`cmdline` user input. These are lists that all plugins changing the end user experience have to copy (`fzf-lua`,`telescope`,`dressing`...), creating a history file for each plugin in user's cache although they don't change functionality but only looks.

(The only way to access the history of any kind is with `:his` which is user-only, not usable for plugins)

### Expected behavior

It would be nice, if there were functions in the API that would allow for querying the respective histories and also add to them, just like the builtin behaviour does. In theory this should just mean exposing the internal functions and in return have a unified access to history for each respective function, making transition between different interfaces keep the history.

An extra benefit could be if a history type could be added by a plugin (I am not sure how the internal saving works and if this would be possible), acting basically as a simple database.
Repository: flutter
Issue: Can't scroll left or up with iOS floating cursor (dragging spacebar to move cursor)
Labels: a: text input,c: new feature,platform-ios,framework,engine,a: fidelity,P2,team-ios,triaged-ios

Originally reported by @Curvel as part of #89228.

**Repro:**
1. Have a `TextField()`. (Probably an `EditableText` will do.)
1. Use iOS.
1. Type a bunch of text into the input, so that it doesn't fit and has to scroll.
1. Long-press the spacebar, then drag around the keyboard to move the cursor (the "floating cursor" feature; Apple calls it "Turn the onscreen keyboard into a trackpad").
1. Try to move the cursor to the edges of the input, to scroll through the text.

**Expected:**
The text scrolls. This is the native iOS behavior.

**Actual:**
If you move to the end of the visible text — the bottom in a multiline input, or the right/end in a single-line input ­— then it scrolls. But if you move to the beginning — the top in a multiline input, or the left/start in a single-line input — then it doesn't.

### Further context
This is the behavior I see on a recent version from master/main, on iOS 16.

Originally reported in 2021 in #89228, so it isn't new. It's possible details have changed, though: that report only looks at a single-line input, and it says "the TextField doesn't scroll horizontally" without mentioning specifically left/start vs. right/end.
Repository: tauri
Issue: key states not set on onwheel event in Linux [bug]
Labels: type: bug,platform: Linux,status: needs triage,type: rfc

### Describe the bug

Previously I was able to get key state from javascript `onwheel` events. After updating my Arch Linux system it appears that this functionality is now missing. Trying the same code (see reproduction) in Chrome or Firefox still works just not in Tauri.

### Reproduction

Put the following in the html, test on both Tauri, Chrome, and Firefox

```
<div onwheel="console.log('wheel', event.ctrlKey)" onclick="console.log('click', event.ctrlKey)">Test</div>
```

When holding "control" down expect the `ctrlKey` to be `true` when using scroll wheel on the word "Test". Found `ctrlKey` is `false` only on Tauri.

### Expected behavior

`onwheel` event sets `ctrlKey` to `true` if control key held down.  `onclick` works as expected.

### Platform and versions

```text
[✔] Environment
    - OS: Arch Linux Rolling Release X64
    ✔ webkit2gtk-4.0: 2.40.1
    ✔ rsvg2: 2.56.0
    ✔ rustc: 1.68.2 (9eb3afe9e 2023-03-27)
    ✔ Cargo: 1.68.2 (6feb7c9cf 2023-03-26)
    ✔ rustup: 1.25.2 (17db695f1 2023-02-01)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 16.14.2
    - pnpm: 7.1.6
    - yarn: 1.22.15
    - npm: 9.4.0

[-] Packages
    - tauri [RUST]: 1.3.0
    - tauri-build [RUST]: 1.2.1
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.1
    - @tauri-apps/api [NPM]: not installed!
    - @tauri-apps/cli [NPM]: 1.3.1

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src/build
    - devPath: http://localhost:8081/
```


### Stack trace

_No response_

### Additional context

_No response_