sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Indicate in the editor that a type is explicitly `any`
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

any marker editor

### ✅ Viability Checklist

- [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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Types that are explicitly set to `any` are sometimes hard to distinguish from actually typed variables in the editor. You might be adopting types while still having a lot of `any` around and then it would be helpful to call `any` out more explicitly in the editor.

### 📃 Motivating Example

I am now using the extension https://marketplace.visualstudio.com/items?itemName=danvk.any-xray which does this:

![Image](https://github.com/user-attachments/assets/36646902-dc50-4f43-88ac-20c508f21dd0)


### 💻 Use Cases

1. What do you want to use this for?

Seeing explicit `any` types easily so that I can work on adding types.

3. What shortcomings exist with current approaches?

I can disable explicit any by producing errors but that is very aggressive.

5. What workarounds are you using in the meantime?

Hovering over the type.
Repository: next.js
Issue: Using a parallel route slot with dynamic route, in parallel to a catch-all route causes non-turbo dev server and build to fail.
Labels: bug,linear: next,Module Resolution,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/ItsWendell/nextjs-14.2.15-catch-all-parallel-routes-dynamic-segments-build-issues-repo

### To Reproduce

- Create a catch-all route
- Create a parallel route slot somewhere with a dynamic path

Reproduction:

Clone this repository

1. Run npm install
2. Run npm run dev --turbo and visit http://localhost:3000/
3. Press the "Lets visit a blog post that contains a slot with a dynamic parallel route." button, press "Start slotting" to visit a dynamic slot within that blog page / layout
4. See that it works pretty well, now let's make it fail:
5. Run npm run build, the build will fail with error: `ENOENT: no such file or directory, open '/Projects/parallel-routes-catch-all/.next/server/app/(blog)/blog/[slug]/@info/info/[infoId]/page_client-reference-manifest.js'`
6. Run npm run dev (without turbo) see that it fails as soon as you click the "Start slotting" button with a similar error: `ENOENT: no such file or directory, open '/Projects/parallel-routes-catch-all/.next/server/app/(blog)/blog/[slug]/@info/info/[infoId]/page_client-reference-manifest.js'`


### Current vs. Expected behavior

I expect `next build` to compile a valid version, since it works sucessfully in next dev --turbo as I expected. So that I can use the parallel routes together with catch-all routes, as next dev --turbo shows, it should have higher priority than the catch-all route.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Wed Oct  9 05:26:29 UTC 2024
  Available memory (MB): 31561
  Available CPU cores: 8
Binaries:
  Node: 22.8.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: 14.2.15
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Module Resolution, Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

I tested against latest canary `[15.0.0-canary.182](https://www.npmjs.com/package/next/v/15.0.0-canary.182)` too, and the latest stable `14.2.15`.

### Workaround

I found a work around: Instead of using an required catch-all route I've replaced the catch-all route with a non-optional catch all route `[[...slug]]` vs `[...slug]`, this seems to continue the build. Not optimal because in some cases you want to have e.g. a seperate page.tsx and a catch-all for all other pages, but we can work around that. This issue is still relevant,  since this behavior should be the same with an optional catch all route.
Repository: PowerToys
Issue: Have no administrator privileges when starting the Mouse Without Borders service
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/8912b53a-1d15-409c-96ed-dc48af58b71c)
1.Open GitHub in Google Chrome to download.
2.Run the PowerToys installer as an administrator.
3.When opening, right-click and select "Run as administrator."
Why does it show that I don't have administrator privileges when starting the Mouse Without Borders service?

### ✔️ Expected Behavior

I want to open "Use Service" normally.

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: Python
Issue: add travelling salesman problem
Labels: enhancement

### Feature description

adding of travelling salesman problem to learn and understand concepts and algorithms of dynamic programming
Repository: pytorch
Issue: libtroch_cuda.so is missing in TORCH_LIBRARIES and TORCH_CUDA_LIBRARIES in PyTorch CMake
Labels: module: build,module: cuda,triaged

`libtroch_cuda.so` is missing in `TORCH_LIBRARIES` and `TORCH_CUDA_LIBRARIES` in PyTorch [CMake](https://github.com/pytorch/pytorch/blob/575f260229a1e691b70d4aff9bd2d919b902c395/cmake/TorchConfig.cmake.in#L136) if build flag `BUILD_SHARED_LIBS` is enabled, for example
```CMAKE
find_package(Torch REQUIRED)
# libtorch_cuda.so is missing in TORCH_CUDA_LIBRARIES and TORCH_LIBRARIES
message(STATUS ${TORCH_CUDA_LIBRARIES} ${TORCH_LIBRARIES})
```
The impact is the user can't find `libtorch_cuda.so` via PyTorch CMake. They need to find it by themselves. This is not a friendly user experience.

cc @malfet @seemethere @ptrblck @msaroufim
Repository: vscode
Issue: VS Code erroneously registers itself with as a .SVGZ handler
Labels: bug,install-update,windows


Type: <b>Bug</b>

Upon installation on Microsoft Windows, Visual Studio Code registers itself as a handler for `.svgz` files. This is an egregious action because Visual Studio Code cannot handle this binary file type.

**Edit (2024-10-12):** I've found one part of VSCode's source code responsible for this erroneous file association: <https://github.com/microsoft/vscode/blob/main/build/win32/code.iss#L1120-L1124>

**Steps to reproduce:**

1. Create a virtual machine with a clean version of a supported version of Windows 10
2. Download and install `VSCodeSetup-x64-1.94.1.exe`. Use the defaults.
3. Create a `.svgz` file on your desktop.

    The fastest way to that is to open PowerShell 5.1 and issue the following command:

    ```PowerShell
    [Convert]::FromBase64String('H4sIAAAAAAAACxXMMQqEMBBG4av8zPbOGGOKJUlh5RnshN1VIa6iwfH4Krzy4/n9GHDO6b8HGnNe38yqWmhVLNvARkT4FoRj+mqznIEEgsrcUfRrn0f8ppQCvWxd984SPoHm0sGhNDDS2o44+ucRLyei7ABrAAAA') | Set-Content 'Test.svgz' -Encoding Byte
    ```

4. Double-click the newly created `.svgz` file.

**Expected result:** Windows should inform the user that no app has been registered to handle this file type.

**Actual result:** Visual Studio Code launches, attempts to open the file, and fails.

VS Code version: Code 1.94.1 (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z)
OS version: Windows_NT x64 10.0.19045
Modes:


<!-- generated by issue reporter -->
Repository: Python
Issue: New Folder Creation
Labels: enhancement

### Feature description

I plan to create a new folder named 'Binary Search Problems', where I will add important problems solved using Binary Search. 

Please assign this task to me under Hacktoberfest 2024.
Repository: bitcoin
Issue:  scriptpubkeyman fuzz target TopUp is slow (3/N)
Labels: Tests

Follow-up to https://github.com/bitcoin/bitcoin/issues/30476 and https://github.com/bitcoin/bitcoin/issues/30541:

Found by OSS-Fuzz: https://issues.oss-fuzz.com/issues/369374541

Probably a duplicate of, or similarity with https://github.com/bitcoin/bitcoin/issues/30498

File: [clusterfuzz-testcase-scriptpubkeyman-6582005385461760.not.txt](https://github.com/user-attachments/files/17330258/clusterfuzz-testcase-scriptpubkeyman-6582005385461760.not.txt)



```
$ FUZZ=scriptpubkeyman perf record -g --call-graph dwarf  ./bld-cmake/src/test/fuzz/fuzz -runs=1 /tmp/clusterfuzz-testcase-scriptpubkeyman-6582005385461760.not.txt
$ hotspot ./perf.data
```

![Screenshot from 2024-10-10 17-19-24](https://github.com/user-attachments/assets/29918851-b1da-45d2-908f-8264e51a0f53)
Repository: pytorch
Issue: [Intel GPU] The failures do not block new pull request merge if the failures are also in the main branch for Intel GPU
Labels: triaged,module: xpu

### 🚀 The feature, motivation and pitch

In general, the failures do not block new pull request merge if the failures are also in the main branch. For most CI flows, the statement is TRUE. However, it does not work for Intel GPU. We need to enable this feature for Intel GPU to facilitate the process of pull request merge.

### Alternatives

_No response_

### Additional context

_No response_

cc @gujinghui @fengyuan14 @guangyey
Repository: next.js
Issue: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.
Labels: examples

### Verify canary release

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

### Provide environment information

```bash
Using :
nextjs 14
zod
tailwind css
shadcn Ui

app running on digitalocena
```


### Which example does this report relate to?

Server Side Component Error

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

Microsoft Edge

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

Using git action on digital ocean (web app)

### Describe the Bug

An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.

my server action function
![serverside](https://github.com/user-attachments/assets/bc9b33c9-2778-4069-880e-f55571d1161d)

login page function:(client side)
![loginpage](https://github.com/user-attachments/assets/2bf43576-def7-4fae-a7dd-cfa4e099cc3d)

This error only happens in production 

### Expected Behavior

![Screenshot (114)](https://github.com/user-attachments/assets/9a8a5798-6837-461b-a23f-e2be6be15f61)


and this what I get 
![Screenshot (115)](https://github.com/user-attachments/assets/25c4b4d5-e0a4-4f9f-b69f-e9aa62fc4963)


### To Reproduce

This error message is printed in the console

 ⨯ lib\actions\authUserActions.ts (39:15) @ login
 ⨯ Error: Invalid email or password
    at login (./lib/actions/authUserActions.ts:52:15)
digest: "740006343"
  37 |         return {message: "Login successful"}
  38 |     }catch(error: any){
> 39 |         throw new Error(error.message);
     |               ^
  40 |     }
  41 | }
Repository: ant-design
Issue: Support buildOptionText in Pagination
Labels: Inactive,unconfirmed

### What problem does this feature solve?

Hey!

I was trying to solve the problem of localization in Russian. Strings in Russian with 1 and 3 are declined differently than the others, and I need to provide for this.

I saw in the source files that Option has this feature, but I can't use it. This improvement will help those who are interested like me to solve the problem of localization for their own language.

### What does the proposed API look like?

<Pagination {...props} buildOptionText={...}>

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Inline Diff without "Toggle Changes" on is not showing all deleted lines, can be confusing
Labels: feature-request,inline-chat


- VS Code Version: 1.72.2
- OS Version: Linux, macOS, recent versions

Steps to Reproduce:

1. Ask copilot (Cmd+I) to delete lines
2. Get a seemingly empty diff
3. Use the down arrow button, select "Toggle Changes"
4. See the deleted lines

Shouldn't "Toggle Changes" be the default or at least it be an option to keep it on?
Repository: ollama
Issue: I hope Image analyze model, Qwen/Qwen2-VL-72B-Instruct
Labels: model request

Qwen/Qwen2-VL-72B-Instruct



Ollama brothers. plz.
Repository: godot
Issue: Favorite files disappear
Labels: bug,topic:editor

### Tested versions

v3.6.stable.official [de2f0f147]

### System information

w10 64

### Issue description

Files added to favorites as a script disappear from favorites after a few editor restarts and computer shutdowns. I can't say when exactly they do, but it's obvious that they disappear.
Folders can also disappear, although it seems less frequent. It just happened to me right now.

![Captura](https://github.com/user-attachments/assets/8c655e62-fe0d-4ecf-bd4f-bb5c2dbc0eb8)


### Steps to reproduce

Add a script as a favorite.
Use the editor as normal.
Check after a while that the file remains as a favorite.

### Minimal reproduction project (MRP)

...
Repository: godot
Issue: The selected tile is indistinguishable if it uses certain colors
Labels: bug,topic:editor,usability,topic:2d

### Tested versions

v3.6.stable.official [de2f0f147]

### System information

w10 64

### Issue description

As you can see in the video, it is almost impossible to distinguish which tile is selected if the tile uses certain colors, in this case the tile has a color something like mustard.


https://github.com/user-attachments/assets/72639462-6379-44a8-8da0-87032fe6b8c6

Can you tell me which of the two tiles is currently selected?

![Captura2](https://github.com/user-attachments/assets/ec6877b5-05f7-45b0-8c32-2d6344c2eb5f)


### Steps to reproduce

Create a tileset where the tiles use different colors.
Try selecting a tile as you can see in the video using the selection arrows and with the "Region" option activated.

### Minimal reproduction project (MRP)

...
Repository: go
Issue: cmd/vet: improve the frame pointer check
Labels: help wanted,NeedsInvestigation,FeatureRequest,compiler/runtime

The `framepointer` check from `go vet` is currently quite conservative. Since Go 1.21, frame pointers have become more load-bearing in the Go runtime. They're now used on amd64 and arm64 to collect call stacks for the execution tracer and the block & mutex profilers. Now, frame pointer bugs can crash Go programs, whereas before they would merely result in broken call stacks for external profilers like Linux `perf`.

For example, #69629 was ultimately caused by a bug in [programatically-generated amd64 assembly](https://github.com/dgryski/go-metro/blob/adc40b04c140ccfcbb2d243f40ca26a196eccd0d/metro_amd64.s) which clobbered the frame pointer register. As of Go 1.23.2, `go vet` misses that frame pointer bug. This is because the frame pointer is clobbered after a branch instruction, and the check [aborts if it reaches a branch](https://cs.opensource.google/go/go/+/master:src/cmd/vendor/golang.org/x/tools/go/analysis/passes/framepointer/framepointer.go;l=85;drc=7634f0755c98f25228e3904ed760089c3b199c5d).

I think we should try to expand the number of bugs the `framepointer` check can catch. For example, arm64 support would be good. We also might be able to drop that branch check, or flag assembly that writes to `rbp` without a `push rbp` near the beginning and a `pop rbp` before returning. These kinds of ideas should of course be tested against existing open source Go assembly code, since I assume there is little (if any?) tolerance for false positives in `go vet` tools.
Repository: pytorch
Issue: NJT + Flex Attention
Labels: triaged,module: nestedtensor,oncall: pt2,module: higher order operators,module: pt2-dispatcher,module: flex attention

# Issues
I'm working on this support now in #136792. Here's a list of the current issues:
1. The [notebook](https://www.internalfb.com/intern/anp/view/?id=5581056) (internal only) demonstrates the usage of a `(1, 1, sum(seqlen), sum(seqlen))` block mask for NJT. Is this inefficient? I'd expect `(1, 1, max_seqlen, max_seqlen)` as an analogue to what is done for dense, but it's a bit tricky to implement the NJT adapter for this.
    * From offline discussion: if `_compile=True` is used for `create_block_mask()`, the full `(1, 1, sum(seqlen), sum(seqlen))` mask_tensor isn't materialized; this is good and recommended
    * Still some exploration to be done to see if this is the most efficient way to handle NJTs
2. #137255 adds some logic that assumes a constant seqlen. This will have to be hacked around some for NJT.
3. The notebook example builds a `seq_idx` to map an index within `sum(seqlen)` -> the associated beginning offset. It doesn't account for the fact that `Q_LEN` / `KV_LEN` are rounded up to the nearest block size multiple, so out-of-bounds access occurs if `sum(seqlen)` is not a multiple of the block size.
    * Turns out this is a real bug in `create_block_mask()`; should do the mod trick to avoid this (#137801)
5. ~~`create_block_mask(..., _compile=True)` throws `torch._dynamo.exc.Unsupported: Unexpected type in sourceless builder torch.Tensor` (investigating)~~
    * Fixed this by changing the NJT wrapper generator to close over `seq_idx` implicitly instead of explicitly.
6. The way `seq_idx` is built assumes `offsets[0] == 0`. This may not be the case for some non-standard NJT views.
Repository: deno
Issue: deno install --prod
Labels: feat,install

I have a npm monorepo:

- package.json
- deno.lock
- apps/sveltekit-front
  - package.json
- apps/deno-server
  - package.json
- packages/shared
  - package.json

sveltekit-front only has devDependencies because it is built as a static website
deno-server only has "normal" dependencies, no devDependencies.
sveltekit-front has the shared package in devDependencies
deno-server has the shared package in dependencies

I use docker to deploy both apps.

To create the deno-server docker image:
I copy the root package.json, lockfile, apps/deno-server and packages/shared then I run `deno install` inside the root directory (I cannot just run `deno install` inside apps/deno-server because I am in a monorepo, I need the packages/shared symlink)

The problem is that `deno install` installs all dependencies, even devDependencies that are not needed for production.

Maybe I am missing something.
Thanks
Repository: Python
Issue: Wildcard pattern matching with FFT in O((n+m) log (n+m))
Labels: enhancement

### Feature description

[Reference](https://www.informatika.bg/resources/StringMatchingWithFFT.pdf)
Repository: PowerToys
Issue: TEXT EXTRACTOR OCR NOT WORKING
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.85.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

TextExtractor

### Steps to reproduce

 WIN KEY + SHIFT + T=TEXT EXTRACTOR

### ✔️ Expected Behavior

 WIN KEY + SHIFT + T=TEXT EXTRACTOR AUTOMATICALLY OPEN

### ❌ Actual Behavior

 WIN KEY + SHIFT + T=TEXT EXTRACTOR DO [PowerToysReport_2024-10-10-23-09-38.zip](https://github.com/user-attachments/files/17332051/PowerToysReport_2024-10-10-23-09-38.zip)
NOT OPEN AUTOMATIC AND NO THING HAPPEN. I AM USING WINDOWS 11. TEXT EXTRACTOR OCR NOT WORKING. JUST CLICK ON IT AND POWERTOYS AUTOMATIC EXIT. BUT NOT IN OTHER OPTION LIKE RESIZE, MEASURING TOOL ETC....

### Other Software

_No response_
Repository: bitcoin
Issue: Consider making 27.x Long-Term Support (LTS)
Labels: Feature

As mentioned in the patch notes for 28.x, since this release drops support for glibc older than 2.31, it will not run on several widely used Linux distros, including RHEL 8 and the RHELatives that base off of this, such as AlmaLinux 8 and Rocky Linux 8.

In case anyone is unaware, RHEL 8 and its derivatives are still in active support, and will in fact not be EOL until 2029. While I don't have exact install numbers, I would not be surprised if more than half of Bitcoin Core installations that run on dedicated Linux servers will not be able to update to 28.x as a result of this, without first updating to a new OS.

As such, while I'm aware that older release branches usually have important updates backported for some time, I feel it would make sense to "officially" designate 27.x as a LTS with an extended window of backported updates - maybe not for the full four years and change until these OSes are EOL, but at least for a good part of it. Otherwise, considering the new security disclosure policy, I fear there will be a lot of clients with published exploits still running when 27.x advisories start getting published.
Repository: next.js
Issue: Intercepting Routes doesn't works through rewrites
Labels: Parallel & Intercepting Routes

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Next.js 14.2.15 

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:39:07 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.7.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: 14.2.13
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
```


### Which example does this report relate to?

https://github.com/vercel/nextgram

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

Intercepting route does not work because the root goes through a rewrite 

### Expected Behavior

The intercepting route should work as specified in the documentation but through a rewrite.

### To Reproduce

```
// next.config.js

async rewrites() {
  return [
      {
         source: "/:locale/:vacancy/:id",
         destination: "/:locale/vacancy/:id",
      }
   ]
}

```

```
app
   -- [locale]
      -- @modal
         -- (.)vacancy
            -- [id]
               -- page.tsx
      -- vacancy
         -- [id]
            -- page.tsx
         
```
Repository: deno
Issue: 'ArrayBufferView' is not assignable to parameter of type 'string | ArrayBufferView
Labels: needs investigation,types

Version: Deno 2.0

While trying to build an Astro site with Deno 2.0 I hit an error about mismatched types. I have managed to create a reproducible snippet that should help track this down:

```typescript
import { writeFileSync } from "node:fs";

writeFileSync("buffer.txt", returnBuffer());

function returnBuffer(): ArrayBufferView {
    return new Uint8Array([1, 2, 3, 4, 5]);
}
```

This seems to be valid typescript, but `deno check` fails with:

```
error: TS2345 [ERROR]: Argument of type 'ArrayBufferView' is not assignable to parameter of type 'string | ArrayBufferView'.
  Type 'ArrayBufferView' is missing the following properties from type 'DataView': getFloat32, getFloat64, getInt8, getInt16, and 19 more.
writeFileSync("buffer.txt", returnBuffer());
```

This could be a duplicate of https://github.com/denoland/deno/issues/22381