sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: (Bulk) Folder creation / Folder structure
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Create multible folders, including subfolders

### Scenario when this would be used?

Example:

- I have a 100 folders named "folder1" to "folder100", now i want all those folders to have a subfolder "subfolder".
- I have a 100 folders named "folder1" to "folder100", they all have the same subfolder structure, "subfolder1" to "subfolder 10". Those subfolders have subfolders, ...and so on. Now i want to change something about that folder structure and add "folderX" to folder\subfolder1\subfolder2\... for all 100 folders.

### Supporting information

The way i would do this right now through **cmd** or a .txt turned .**bat** file:
@ ECHO OFF (without the spacing after @ )
md Folder1\Subfolder1
md Folder2\Subfolder1
md Folder3\Subfolder1
md Folder4\Subfolder1
md Folder5\Subfolder1
... (and so on)

md Folder101\Subfolder1\Subfolder1
md Folder101\Subfolder1\Subfolder2
md Folder101\Subfolder1\Subfolder3
md Folder101\Subfolder1\Subfolder4
md Folder101\Subfolder1\Subfolder5
... (and so on)

If i already have a folder structure i and want to change i can use **PowerRename**.
If i want to copy all the folders names (because they are obviously not called folder1...) to create a .txt i can use **Text Extractor**. Then i use **regexp** `^md ` to add it to the .txt file. After that i turn it into a .bat file, put it in an empty folder, start it and then move and integrate the updated folder structure. 

The only part of this, that could use some Quality of Life features is the creation of the structure itself in textform and it would work well together with the Features PowerToys already has.

Last example of how it could look:
**Foldername Field**: 
Folder1
**Subfolder1 Field**:
Subfolder1, Subfolder2, Subfolder3, Subfolder4 (these are inside Folder1)
**Subfolder03 Field**:
Subfolder01, Subfolder02, Subfolder03 (these are inside Subfolder3)

I hope i explained it well enough.

Thank you for reading this.

(Edit: I checked **is:issue is:open label:Idea-Enhancement folder** before posting this)
Repository: tensorflow
Issue: [Question] - Extend some GPU op
Labels: stat:awaiting tensorflower,type:feature,comp:gpu,comp:core

### Issue type

Others

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

Yes

### Source

source

### TensorFlow version

v2.17.0-rc1-2-gad6d8cc177d 2.17.0

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.6 LTS

### Mobile device

_No response_

### Python version

3.9.19

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

A30

### Current behavior?

I'm running tensorflow_model_server with the sample saved_model_half_plus_two_gpu model. One of the layers there is Mul

"Mul" op: "Mul" input: "a/read" input: "_arg_x_0_0/_7" device: "/job:localhost/replica:0/task:0/device:GPU:0" attr { key: "T" value { type: DT_FLOAT } } attr { key: "_XlaHasReferenceVars" value { b: true } }

I would like to add some custom code before/after the code runs on the GPU (I have a docker with TensorFlow serving, it downloads the TensorFlow code and comiles it via bazel). I am able to add a print in the OpKernel::OpKernel code, but I would like to do so in the relevant GPU operator compute's function. That I am unable to find/do.

Tried to print/log to file in either of the following places but it did **NOT** work:
- tensorflow/core/util/gpu_kernel_helper.h               in GpuLaunchKernel function
- tensorflow/core/kernels/cwise_ops_common.h     in BinaryOp::Compute

Any idea what am I missing? Obviously my code adds catch as they compile and the code in OpKernel::OpKernel  does work.


### Standalone code to reproduce the issue

```shell
Not relevant...
```


### Relevant log output

_No response_
Repository: rust
Issue: Add diagnostic hint when or-ing values which may be missing an equality comparison
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    let x = 1;
    if x == 1 || 2 {
        println!("Was 1 or 2");
    }
}
```


### Current output

```Shell
error[E0308]: mismatched types
 --> src/main.rs:3:18
  |
3 |     if x == 1 || 2 {
  |        ------    ^ expected `bool`, found integer
  |        |
  |        expected because this is `bool`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `rustplay` (bin "rustplay") due to 1 previous error
```


### Desired output

```Shell
error[E0308]: mismatched types
 --> src/main.rs:3:18
  |
3 |     if x == 1 || 2 {
  |        ------    ^ expected `bool`, found integer
  |        |
  |        expected because this is `bool`
  |
  |  note: If you're trying to check whether x is one of several values,
  |        you need to repeat the `x ==` check for each possible value.
  |
  |  hint: Try `if x == 1 || x == 2 {`.

For more information about this error, try `rustc --explain E0308`.
error: could not compile `rustplay` (bin "rustplay") due to 1 previous error
```


### Rationale and extra context

I teach people software engineering who don't have a software engineering background, and have noticed that a surprising number of people try to write this kind of code (perhaps because in their head they're thinking "I need to check if x is 1 or 2" and "||" translates directly to "or", where in reality they need to be thinking "I need to check if x is 1 or x is 2".

This has come up often enough that I think it would be a useful hint to provide - as things stand, I haven't found a really easy way of guiding people to make this realisation themself other than just telling them, so the compiler hinting it to them feels useful.

It feels like this could be useful to trigger in any condition (i.e. place expecting a boolean) where:
1. There is at least one `||`
2. The first LHS of a || is an `==` (or possibly `!=` comparison)
3. Every type on the RHS of a `||` has a type which is comparable to the LHS of the first `==` (or perhaps, has the same type as the RHS of the first `==`)

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.79.0 (129f3b996 2024-06-10)
binary: rustc
commit-hash: 129f3b9964af4d4a709d1383930ade12dfe7c081
commit-date: 2024-06-10
host: aarch64-apple-darwin
release: 1.79.0
LLVM version: 18.1.7
```


### Anything else?

_No response_
Repository: flutter
Issue: Enable building for a single arch in macOS
Labels: c: new feature,tool,platform-mac,c: proposal,a: desktop,P3,team-macos,triaged-macos

### Use case

I want to link to `libjvm.dylib` on the host machine to spawn JVM and use JNI. When running on my arm64 machine using `flutter run` things work because the app is built for arm64 and the dynamic library is arm64 as well. However `flutter build macos` fails as it can't find a suitable x64 dylib.

I want to be able to only build for my host architecture in this case.

### Proposal

Have `flutter build macos` take an optional `--target-platform` option.

cc/ @vashworth @jmagman
Repository: kubernetes
Issue: Empty `NodeSelectorTerm` is confusing in pod.nodeAffinity
Labels: kind/bug,sig/api-machinery,sig/apps,triage/accepted

### What happened?

Pod node affinity with empty `NodeSelectorTerm`, result in pod `Pending`.
```
apiVersion: v1
kind: Pod
metadata:
  name: with-node-affinity
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - {}
  containers:
  - name: with-node-affinity
    image: nginx:1.7.9
```

k apply -f pod.yaml
```
k get po
                                 
NAME                                     READY   STATUS    RESTARTS   AGE
with-node-affinity                       0/1     Pending   0          5m3s

Events:
  Type     Reason             Age    From                Message
  ----     ------             ----   ----                -------
  Warning  FailedScheduling   2m52s  default-scheduler   0/3 nodes are available: 3 node(s) didn't match Pod's node affinity/selector. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
```

### What did you expect to happen?

Empty `NodeSelectorTerm` represents no selector, should select all nodes available.
Or empty `NodeSelectorTerm` should not be allowed in pod.nodeAffinity.

### How can we reproduce it (as minimally and precisely as possible)?

See above yaml.


### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.30.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0
```

</details>
Repository: vscode
Issue: Unicode: 🖍️ renders but ✏️ fails
Labels: font-rendering,under-discussion


Type: <b>Bug</b>

I use VSCode as my goto text-editor these days.

It is vexing that certain "more-common" unicode characters don't render properly, while other "less-common" ones DO.

After several years of waiting for a fix, I'm filing an issue.

See attached screenshot.

VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:07:46.768Z)
OS version: Darwin arm64 23.5.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 (8 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|24.00GB (2.46GB free)|
|Process Argv|--crash-reporter-id f10d97cd-2115-4dba-a34a-07be9312995a|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
dvt-remote-ssh|ami|1.0.0
nestedtext|bma|2.0.0
githistory|don|0.6.20
copilot|Git|1.214.1003
copilot-chat|Git|0.17.2024062801
vsc-python-indent|Kev|1.18.0
rainbow-csv|mec|3.12.0
vscode-docker|ms-|1.29.1
debugpy|ms-|2024.8.0
python|ms-|2024.10.0
vscode-pylance|ms-|2024.7.1
jupyter|ms-|2024.6.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.18
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-containers|ms-|0.375.1
remote-ssh|ms-|0.112.0
remote-ssh-edit|ms-|0.86.0
remote-explorer|ms-|0.4.3
yaml-cloudformation-highlighter|paq|2.0.4

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31094925
refactort:31101459
ccplc:31098109
pythonrstrctxt:31093869

```

</details>

<!-- generated by issue reporter -->
Repository: ollama
Issue: Support token embeddings for  `v1/embeddings`
Labels: feature request,api

### What is the issue?



When encoding with `tiktoken`, the interface is no longer compatible

```
tiktoken.get_encoding("cl100k_base").encode(text)
```

```json
{
    "input": [30624,99849,64479,51392,31809,29207,233,45829],
    "model": "nomic-embed-text"
}
```

```
{
    "error": {
        "message": "invalid input type",
        "type": "api_error",
        "param": null,
        "code": null
    }
}
```

I hope it can be compatible, thank you



### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

ollama version is 0.2.7
Repository: vscode
Issue: Add a `when` property to `QuickInputButton`
Labels: feature-request,quick-pick,api-proposal

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Created https://github.com/microsoft/vscode/issues/221397#issuecomment-2225357158 as requested by @TylerLeonhardt.

I would like an optional `when` property to be added to [QuickInputButton](https://code.visualstudio.com/api/references/vscode-api#QuickInputButton) so extension developers can hide/show buttons on quickpicks and quickinputs depending on whether the when clause they set the property to evaluates false or true.

At the moment we have to try and modify the contents of the `buttons` array as conditions change.
Repository: electron
Issue: [Bug]: Crash when trying to save a document
Labels: platform/windows,crash :boom:,bug :beetle:,component/dialog,31-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

31.2.0

### What operating system(s) are you using?

Windows

### Operating System Version

10.0.19042

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

No crash

### Actual Behavior

According to the crash dump it seems that the app is crashing at the point when the file save dialog is supposed to be shown.
[b88d83e7-1bb6-4a6b-b258-06e3834fd33c.zip](https://github.com/user-attachments/files/16361758/b88d83e7-1bb6-4a6b-b258-06e3834fd33c.zip)
![image](https://github.com/user-attachments/assets/31496b61-0502-4659-85db-25b235ffd493)


### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: go
Issue: cmd/go: TestNewReleaseRebuildsStalePackagesInGOPATH failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestNewReleaseRebuildsStalePackagesInGOPATH"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741593271352983073)):

    === RUN   TestNewReleaseRebuildsStalePackagesInGOPATH
    === PAUSE TestNewReleaseRebuildsStalePackagesInGOPATH
    === CONT  TestNewReleaseRebuildsStalePackagesInGOPATH
        go_test.go:877: running testgo [list -deps runtime]
        go_test.go:877: standard output:
        go_test.go:877: internal/goarch
            unsafe
            internal/abi
            internal/cpu
            internal/bytealg
    ...
        go_test.go:970: running testgo [list -f {{.Stale}}:{{.StaleReason}} p1]
        go_test.go:970: standard output:
        go_test.go:970: true:not installed but available in build cache
            
        go_test.go:971: running testgo [install p1]
        go_test.go:972: running testgo [list -f {{.Stale}}:{{.StaleReason}} p1]
        go_test.go:972: standard output:
        go_test.go:972: false:
            
    --- FAIL: TestNewReleaseRebuildsStalePackagesInGOPATH (41.79s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: material-ui
Issue: [docs-infra] Lock versions on Codesandbox examples
Labels: docs,scope: docs-infra

### Summary 💡

In order to provide clarity and remove misunderstandings, it would be great if we can lock the versions in the Codesadnbox examples. The main reason is that sometimes it can happen that an issue is reported but by the time we check the reproduction case it has already been fixed.
If we have locked versions in the examples listed in the docs we can know exactly the versions the problem has occurred and compare it with the current latest.

**Search keywords**:
Repository: go
Issue: cmd/dist: internal import detection is generating false positives
Labels: OS-OpenBSD,NeedsInvestigation

After updating the Go port for OpenBSD to start testing 1.23rc2, the build fails with:

```
===>  Building for go-1.23rc2
Building Go cmd/dist using /usr/ports/pobj/go-1.23rc2/go-openbsd-amd64-bootstrap. (go1.22.5 openbsd/amd64)
Building Go toolchain1 using /usr/ports/pobj/go-1.23rc2/go-openbsd-amd64-bootstrap.
go tool dist: /usr/ports/pobj/go-1.23rc2/go/src/cmd/internal/obj/x86/asm_test.go.orig.port:10: bootstrap-copied source file cannot import internal/testenv
```

This appears to be a result of code added in 805f6b3f5db, combined with the fact that the OpenBSD ports build applies patches (and hence `patch` produces a backup `.orig.port` file). This approach has worked without issue for Go 1.22 (and every earlier version) - the new code seems to be unnecessarily excessive since this is not a `.go` file, does not have any build tags and is additionally test code.

In order to avoid packaging complications, can we restrict this check to files that Go will actually compile?
Repository: ant-design
Issue: Table column get flickered while using loading for the first time
Labels: Inactive,improvement,🧶 Low Priority

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/ant-design-react-18-forked-k7rtrw?file=%2Fsrc%2FSiderDemo.js%3A34%2C25)

### Steps to reproduce
in sandbox antd v-4 but same issue also happening on v5
Keep the data-source empty (no rows).
you can reproduce this issue while refreshing the page 2-3 times.

### What is expected?

It should have work normal

### What is actually happening?

- column title is moving right to left via left to right after refreshing the page.
- one more issue is showing column title after rows data. (when we have rows data)

| Environment | Info |
| --- | --- |
| antd | 5.19.3 |
| React | 18.2 |
| System | window |
| Browser | crome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: material-ui
Issue: [docs] Implement MUI Block examples in the paid offering
Labels: docs,discussion



<!--
  Thank you very much for contributing to Material-UI X by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [x] I have searched the [issues](https://github.com/mui-org/material-ui-x/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

This is more of a general suggestion, perhaps for the longer term vision/roadmap.  MUI's docs really great overall, but the [examples](https://material-ui.com/getting-started/templates/) are pretty basic.  I think there's a gap between what's there, and full blown templates/themes (which may go 'too far') that could be included in the paid offering, even as an additional tier or something.  I think the cost/benefit would be a no brainer for a lot of devs

## Examples 🌈
Good examples are [TailwindUI](https://tailwindui.com/) and [ChakraUI Pro](https://pro.chakra-ui.com/).  

## Motivation 🔦

Reducing the work necessary to build common, higher level UI components. Also, if provided as [code](https://pro.chakra-ui.com/components/application-ui/authentication)/ui examples would serve as a learning resource for creating more complex layouts components of your own

## Order id 💳
18042



**Search keywords**:
Repository: react
Issue: Remove references to legacy class-based component architecture in error messages
Labels: Status: Unconfirmed

We've moved to function-based components using hooks a very long time ago, yet we still see error messages such as these:

```
Maximum update depth exceeded. This can happen when a component repeatedly calls 
setState inside componentWillUpdate or componentDidUpdate. React limits the 
number of nested updates to prevent infinite loops.
```

I don't even know how to debug and resolve an error like this, because we're not using class-based components. It's really very annoying, because we don't have a single instance of `setState`, `componentWillUpdate` or `componentDidUpdate` in our code. These are remnants of the legacy class-based component architecture.

Copilot AI suggested something like this:

```
Maximum update depth exceeded. This can happen when a component repeatedly updates 
state using the useState hook inside the useEffect hook. React limits the 
number of nested updates to prevent infinite loops.
```

or

```
Maximum update depth exceeded. This can happen when a component repeatedly updates 
state using the useState hook directly inside the component body. React limits the 
number of nested updates to prevent infinite loops.
```

I'm not sure if either one is correct, but it's definitely a start.

Related:
* #12811
Repository: storybook
Issue: [Bug]: PanelPosition on mobile Viewports not working / is alway bottom
Labels: bug,question / support,ui

### Describe the bug

On mobile Viewports the panelPosition is always on bottom. It is not possible to change it. 

Config is set to this:
```
addons.setConfig({
  panelPosition: 'right',
});
```

Is this intended behaviour? Any way to change this? 

![Screenshot 2024-07-24 at 14 54 08](https://github.com/user-attachments/assets/07d31917-c798-41ad-ad56-9d45af89537d)


### Reproduction link

https://stackblitz.com/edit/github-vnuyk1?file=.storybook%2Fmanager.js

### Reproduction steps

1. Go to the link, let SB start
2. Click the button story
3. Open Dev Console / Resize Browser Window until Storybook Mobile Layout is showing
4. Open / Close the Panel. Always open on bottom

### System

```bash
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-interactions: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-links: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-onboarding: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/blocks: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/nextjs: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/react: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/test: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    storybook: ^8.3.0-alpha.2 => 8.3.0-alpha.2
```


### Additional context

Seems to be like this since Storybook 7 or 8
Repository: PowerToys
Issue: Mouse Without Borders
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.82.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Move mouse cursor to another display...

### ✔️ Expected Behavior

When we want to "move mouse cursor to another PC", it should disappear from current PC screen.

### ❌ Actual Behavior

Cursor location resets to    new Point(SCREEN_WIDTH / 2, 5);    and stays there up until we reenter that PC screen again...
What is weird though is that it doesn't happen every time as I primarily thought.

### Other Software

_No response_