sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Need update to amazing peek tool
Labels: Issue-Bug,Product-Peek

### Description of the new feature / enhancement

## Needs updates to peek tools

***Peek tools is an amazing feature***
But it lacks some features like it is unable to view excel files , ppt files etc. It must be able to do so for it to be more functional we and if the option to peek into folders it will be much more interesting 

***Finally I would also prefer to change dark to light tool directly from the peek preview***  

### Scenario when this would be used?

We work just like many with a lot of excel files and I believe most of us do and use excel and hence in them it is easy to get lost and hence if powertoys extends its support is very much appreciatable thankyou!

### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Log seed immediately before generation starts
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

I'm sure we've all been there, SD starts to render something brilliant, and WHAM...out of memory %$!@!  
What was the seed, so I can try again?  
(I know you can sometimes recover the seed with the recycle button, but not always.  Or sometimes you don't immediately realize how brilliant it was and keep clicking generate, so the seed is lost.)
So my proposal is to simply write the seed value to the log before anything VRAM intensive begins.  That should be easy enough, right?  

### Proposed workflow

1. Go to the txt2img tab 
2. Press Generate
3. Presumably the code picks a random seed and then passes it to SD to do its thing.  Just log it before the call to SD.


### Additional information

_No response_
Repository: PowerToys
Issue: Peek : Add support to preview `.apk` format
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

### Description of the new feature / enhancement

Add support for previewing APK (Android Package) files in Peek.

![image](https://github.com/microsoft/PowerToys/assets/60868965/6978cb65-51c8-4bb5-a257-7cf416875e2b)




### Scenario when this would be used?

Developers frequently work with APK files during the app development process. Having a quick preview of the APK content without needing to install it on a device would streamline the debugging and testing process. This feature would save time and effort, as developers can verify the resources, manifest details, and other essential components within the APK right from the explorer itself.

### Supporting information

The preview may content the application logo, minSdkVersion, targetSdkVersion, permission, package name etc.

Example using [Quicklook for Windows](https://github.com/QL-Win/QuickLook):

![image](https://github.com/microsoft/PowerToys/assets/60868965/d0f1f57c-c956-4b69-a2ec-a0280d9cced1)
Repository: svelte
Issue: Animations & Transitions are not working on display:contents
Labels: transition/animation

### Describe the bug

Animations & Transitions are not working on HTML element with `display: contents`.
 
It's normal since `display: contents` replaces the element with its contents, so the element isn't really an element anymore.
But it gives strange and unexpected behavior for a basic feature of Svelte.


Expected behavior : it should work (e.g. animations/transitions could be applied to all its children).

### Reproduction

This demo display a list of user using an `ul/li` and `display:grid` on each `<li>` :

https://svelte.dev/repl/fefc7e40d4264fb7af10130fb2c52fa3?version=4.1.2

Click on *"SHUFFLE"*, *"DROP ONE"* or *"ADD ONE"* to trigger animations/transitions on the `<li>` elements.
All is ok.

Now check the checkbox *"Use display:contents"* to change the CSS in order to use `display:contents` on the `<li>` elements.
This allows, with `display:grid` is set on the `<ul>`, to have an alignment of each parts of the list.

Now click on *"SHUFFLE"*, *"DROP ONE"* or *"ADD ONE"* to trigger animations/transitions on the `<li>` elements.
The animations/transitions are not triggered...

Animation is just ignored.
Transition do nothing, but delay the deletion of the element, which causes lag.

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 10 10.0.22621
    CPU: (12) x64 Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
    Memory: 7.63 GB / 15.78 GB
  Binaries:
    Node: 16.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.7.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 7.26.1 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Spartan (44.22621.1992.0), Chromium (115.0.1901.183)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    svelte: file:../svelte/packages/svelte => 4.1.2 
```


### Severity

annoyance
Repository: rust
Issue: unused_variables should explain the drop order implication of removing the binding
Labels: A-diagnostics,T-compiler

### Code

```Rust
let window: winit::window::Window = WindowBuilder::new().build(&event_loop).unwrap();
```


### Current output

```Shell
warning: unused variable: `window`
  --> src/main.rs:15:9
   |
15 |     let window: winit::window::Window = WindowBuilder::new().build(&event_loop).unwrap(); // Opens
   |         ^^^^^^ help: if this is intentional, prefix it with an underscore: `_window`
   |
   = note: `#[warn(unused_variables)]` on by default
```


### Desired output

```Shell
Although "window" is not used in the scope textually, it is there in spirit (so to speak) and needs to be there otherwise the code doesn't work.

My first reaction was "Oh, yeah - it's not used", so do this instead.

WindowBuilder::new().build(&event_loop).unwrap();

However, when doing this, no window appears. It's been dropped behind the scenes.
```


### Rationale and extra context

Main context: Hello World code for "winit".

There's something false about the phrase "unused variable: `window`" because in some very real sense it was being used.

I was completely thrown off as to why

let unused = sideEffect() was semantically different from sideEffect()

In the error message (What error? It makes the code work!) there's no mention of the fact that you might need the variable to keep it alive.

### Other cases

_No response_

### Anything else?

_No response_
Repository: next.js
Issue: Revalidate not working nextjs@13.4.12. Requires manual refresh
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: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.12
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/SharmaTushar1/nextjs-v-13.4.12-issue

### To Reproduce

For nextjs@13.4.12 (no need to change it's in the the git repo)

- Install dependencies `npm install`

- Build the app `npm run build`

- `npm start`

- After the app is running try to move the file `new.md` from root directory to blogposts directory to check for revalidation

- The revalidation is set to 10 (page.tsx of root/app). Wait for 10 secs and visit other posts.

- The `new.md` post is not visible after 10 seconds. And is only visible after a manual refresh.

For next@13.2.4 (change in package.json)

`npm install next@13.2.4`

- Now repeat the same steps as did previously

- In this case the post from the file `new.md` is visible and revalidation works as expected.

### Describe the Bug

The revalidate in next js for version 13.4.12 isn't working. 
```ts
// Inside app/page.tsx
export const revalidate = 10; // should revalidate after 10 seconds 
```
When I try to create a new file (the app is built and running on port 3000) the new Post won't show up. I have to manually refresh the page to see the result. 
This works completely fine and the post gets shown automatically without the need of refreshing for an older version of next js (13.2.4)

### Expected Behavior

The app should be able to render the `new.md` blog without the need for a refresh. Just like how it is happening in nextjs@13.2.4. But, it requires a manual refresh.

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

_No response_

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

_No response_
Repository: next.js
Issue: Error Running Next.js Project on Multiple Ports in Windows Environment
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
next info

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.17.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.12
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A
```


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

_No response_

### Link to the code that reproduces this issue or a replay of the bug

Can only reproduce in local development.

### To Reproduce

Navigate to the project directory in the command prompt.
Open the first terminal instance and execute the command: npm run dev -- --port 3000.
Open the second terminal instance and execute the command: npm run dev -- --port 3001.

### Describe the Bug

When attempting to run a Next.js project on multiple ports simultaneously in a Windows 10 environment with Node.js v18.17.0, an error is encountered. The project is started using two separate terminal instances, each specifying a different port using the npm run dev command. However, the project fails to run due to an "EPERM: operation not permitted" error when attempting to open the D:\Development\next-app\.next\trace file.

npm run dev -- --port 3001

> next-app@0.1.0 dev
> next dev --port 3001 

- ready started server on 0.0.0.0:3001, url: http://localhost:3001
- event compiled client and server successfully in 177 ms (18 modules)
node:events:492
      throw er; // Unhandled 'error' event
      ^

Error: EPERM: operation not permitted, open 'D:\Development\next-app\.next\trace'
Emitted 'error' event on WriteStream instance at:
    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) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'open',
  path: 'D:\\Development\\next-app\\.next\\trace'
}

Node.js v18.17.0

The project fails to run on the second port (3001) due to an "EPERM: operation not permitted" error when attempting to open the D:\Development\next-app\.next\trace file.

### Expected Behavior

The Next.js project should run successfully on both ports 3000 and 3001, enabling access through the URLs: http://localhost:3000 and http://localhost:3001.

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

Chrome 115.0.5790.111

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

_No response_
Repository: pytorch
Issue: Will torch.sparse.mm support multiplying two boolean matrices?
Labels: module: sparse,triaged,module: boolean tensor

### 🚀 The feature, motivation and pitch

I have two huge matrices. They are sparse Boolean matrices. I call torch.sparse.mm and found that it cannot be successful. Will the multiplication of bool sparse matrices be supported in the future?

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer
Repository: deno
Issue: Unable to find napi_register_module_v1 on mac m1
Labels: bug,node compat,node native extension

I am having a hard time installing sharp npm module with Deno. I am currently using Deno 1.36 and mac m1 chip, also following the steps from sharp [https://github.com/lovell/sharp/issues/2583](https://github.com/lovell/sharp/issues/2583), but I am getting the error below.

```
error: Uncaught Error: 
Something went wrong installing the "sharp" module

Unable to find napi_register_module_v1 symbol in /Users/velingeorgiev/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.32.4/build/Release/sharp-darwin-arm64v8.node

Possible solutions:
- Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
- Install for the current darwin-arm64v8 runtime: "npm install --platform=darwin --arch=arm64v8 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install
    at Object.<anonymous> (file:///Users/velingeorgiev/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.32.4/lib/sharp.js:37:9)
    at Object.<anonymous> (file:///Users/velingeorgiev/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.32.4/lib/sharp.js:40:4)
    at Module._compile (node:module:731:36)
    at Object.Module._extensions..js (node:module:745:12)
    at Module.load (node:module:656:34)
    at Function.Module._load (node:module:539:16)
    at Module.require (node:module:675:23)
    at require (node:module:789:20)
    at Object.<anonymous> (file:///Users/velingeorgiev/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.32.4/lib/constructor.js:11:1)
    at Object.<anonymous> (file:///Users/velingeorgiev/Library/Caches/deno/npm/registry.npmjs.org/sharp/0.32.4/lib/constructor.js:441:4)
Watcher Process failed. Restarting on file change...
```

Is this by design, or will future support be provided?
Repository: PowerToys
Issue: FancyZones ~ APP DEFINED LAYOUTS
Labels: Needs-Triage

### Description of the new feature / enhancement

If you open an app, FanzyZones will apply either a default preset zone or one that the user has specified. 

### Scenario when this would be used?

I want to work easier. This would enable me to spend less time having to open all my applications, then have to go and move each one to their prespective zone. This would cut back on time... 

### Supporting information

The process... 

1. You make a preset zone for all your apps
2. You snap all apps to their prospective zones so its enabled in their zone. 
3. You assign an app to their zone and "register" the zone to its app. 
4. You save the zone... 
5. In settings: you can give conditions... 
A) if app A is locked in zone, change all presets
B) if app A + B is in a certain zone, adjust zone to preset zone that was established. 
6. you then launch app A or B, or ETC... All adjustments have been made, no need to redrag/resnap all apps again to their zones.
Repository: flutter
Issue: Support translation of text in Flutter Web
Labels: c: new feature,engine,a: internationalization,platform-web,has reproducible steps,P2,found in release: 3.10,team-web,triaged-web,found in release: 3.13

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

When flutter web text uses the translation plug-in of the browser, when it is translated into other languages, the word spacing is messy, some are very large, and some are stacked together. How to translate into other languages ​​like a js web page, the text word spacing is the same as the original text

### Expected results

**### **This is our flutter web project, currently only supports English****
![origin](https://github.com/flutter/flutter/assets/13296347/82d895e7-fb04-415f-9aef-d959a94a4643)



**### It is expected to use the google translation plug-in with the js native page, and the performance will be consistent after translation.    Similar to this, translate English into Chinese、Spanish  with normal word spacing**

![20230805-181547](https://github.com/flutter/flutter/assets/13296347/8b9a1aed-9915-46ea-9119-522c5300074d)





### Actual results

### **Using the google translation plug-in in the chrome browser, the word spacing layout has been messed up**

![real](https://github.com/flutter/flutter/assets/13296347/0a24f932-1e17-466c-b18c-8a99ae8ffe38)
![xby](https://github.com/flutter/flutter/assets/13296347/a02f1de5-f08e-43cd-836f-87e82927ee0a)



### Code sample

```
class TextView extends StatelessWidget {
  // text = "Multi-LLM Power"
  String text;
  TextView(this.text,{Key? key,) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Text(text);
  }
}
```

### Screenshots or Video

![origin](https://github.com/flutter/flutter/assets/13296347/607ceb4d-8f35-4fb3-b942-5b17105100f7)


### Logs

_No response_

### Flutter Doctor output

➜  ~ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.6, on Ubuntu 20.04.6 LTS 5.15.0-78-generic, locale zh_CN.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.80.2)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!
Repository: neovim
Issue: vim.system: support "pty" (and "term")
Labels: enhancement,job-control,system

# Problem

- `vim.system` does not support `pty` option, unlike `jobstart`.
- Neither `jobstart` nor `pty` support a `term` option. Supporting `term` would eliminate the need for `termopen`.

# Expected behavior

`vim.system(..., { pty = true })` works like `jobstart(..., { pyt = true })`.

## Technical notes

- jobstart's "pty" option is handled as a special case (not delegated to libuv): https://github.com/neovim/neovim/blob/cc87dda31a5b5637ade7ddcfe5199f2df5fd47df/src/nvim/os/pty_process_unix.c#L163

via @bfredl : 

> last time I checked `uv_spawn` lacked some wiring to be used together with `openpty()` (instead of using `forkpty()` ), maybe we could convince libuv to add that..
> ie you can already open a pty master/slave pair and send the slave fd's to `uv_spawn`, but it doesn't become the controlling terminal then.
> `TIOCSCTTY` needs to be done in the child before `execve()` the new process.
Repository: PowerToys
Issue: Host Editor Features  Buton or Context Menu (import/export list, DNS cache clear(ipconfig/flush),Dns Service Reload) 
Labels: Idea-Enhancement,Needs-Triage,Product-Hosts File Editor

### Description of the new feature / enhancement

Export/Impoart Host list
DNS cache clear ipconfig /flushdns
DNS service reload button

![image](https://github.com/microsoft/PowerToys/assets/1008226/4e912c63-cabc-4b95-9d57-6c486bd28858)


### Scenario when this would be used?

When a new record is added to the host editor, sometimes entering the host file may not work. The reason is DNS cache, explorer restart or ipconfig/flush dns for this, 
we also need to export/import the list to backup, ideal for small users

### Supporting information

The host editor, which I have used for a long time, can be examined for ideas.
https://www.sordum.org/8266/bluelifehosts-editor-v1-5/
Repository: pytorch
Issue: [docs] URL and link format proposal to make function page URLs more concise
Labels: module: docs,triaged,enhancement

### 🐛 Describe the bug

These links end up copy-pasted in messengers for chat with colleagues, so making them have less bloat would be nice.

If the links are concise, one can also do quick lookups without going to relatively slower loading https://pytorch.org/docs - e.g. by typing https://pytorch.org/docs/torch.div or https://pytorch.org/docs/div https://docs.pytorch.org/torch.div or https://docs.pytorch.org/div. These pages can also be auto-generated or symlinked for all function names at least for the torch/tensor functions (and such pages can list all functions with the same name e.g. torch.sigmoid, F.sigmoid which may be good by itself https://github.com/pytorch/pytorch/issues/105318 or https://discuss.pytorch.org/t/various-quantized-quantizable-intrinsic-modules-purpose/183562 for LinearReLU)
<hr>
If we go to https://pytorch.org/docs/stable/torch.html, we have links like https://pytorch.org/docs/stable/generated/torch.div.html#torch.div

I'm proposing that instead these function links should be more concise and not include the hash. Going further, there should be symlinks https://pytorch.org/docs/torch.div.html or https://pytorch.org/docs/torch.div or even https://docs.pytorch.org/torch.div (and https://docs.pytorch.org/div)

When doing simple search like `torch.div` we get:
<img width="517" alt="image" src="https://github.com/pytorch/pytorch/assets/1041752/1612511a-0941-43c7-8514-18d763b2946b">
Clicking the first hit will get us to https://pytorch.org/docs/stable/generated/torch.div.html?highlight=torch+div#torch.div

Also, the highlight seems to have no effect now (as opposed to the Google's https://pytorch.org/docs/stable/generated/torch.div.html#:~:text=torch.div https://stackoverflow.com/questions/62161819/what-exactly-is-the-text-location-hash-in-an-url). So maybe worth dropping the highligh part from the Sphinx search hit URLs too? 

### Versions

N/A

cc @svekars @carljparker
Repository: rust
Issue: Can Weak be null?
Labels: T-libs-api,A-docs,T-opsem

There is a discrepancy between the docs of `Weak` and its implementation, originally found by @Urgau in https://github.com/rust-lang/rust/pull/114494#discussion_r1285009958 .

On one hand, the [docs of Weak::as_ptr](https://doc.rust-lang.org/stable/std/rc/struct.Weak.html#method.as_ptr) state:

> The pointer is valid only if there are some strong references. The pointer may be dangling, unaligned or even [null](https://doc.rust-lang.org/stable/std/ptr/fn.null.html) otherwise.

On the other hand, the implementation of `Weak` uses `NonNull`:

https://github.com/rust-lang/rust/blob/1cabb8ed2301faf193132e71ca5b10f82913e48a/library/alloc/src/rc.rs#L2681-L2693

From what I know, it is okay for `NonNull` pointers to be dangling or unaligned, but, staying true to their name, they are [never allowed to be null pointers](https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#safety-2).

I think this discrepancy should be resolved, but I wonder, which way? Should the docs be adjusted, or the implementation?

The issue exists both with `alloc::sync::Weak` as well as `alloc::rc::Weak`.