sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Windows plugin registrants should be ephemeral
Labels: tool,platform-windows,P2,a: plugins,team-windows,triaged-windows

See discussion in https://github.com/flutter/flutter/issues/71762 and https://github.com/flutter/flutter/issues/76726. We should fix Windows (and the other desktop platforms, thus those issues) to have ephemeral registrants instead of checking in a generated file that changes.
Repository: TypeScript
Issue: Narrowing for constant indexed access fails on array getter
Labels: Needs More Info

### 🔎 Search Terms

constant indexed access, array

### 🕗 Version & Regression Information

- This changed between versions `5.4.5` and `5.5.beta`
- This changed in commit or [PR](https://github.com/microsoft/TypeScript/pull/57847)


### ⏯ Playground Link
_I could not repro this in playground, due to the lib import_ 

### 💻 Code

```ts
import crypto from 'crypto-js'

const bar = "abc"
const foo: crypto.lib.WordArray = crypto.enc.Utf8.parse(bar) // Returns type: { words: number[], ... }
for (let i = 0; i < foo.words.length; i++) {
  foo.words[i] += 1
//~~~~~~~~~~~~ error TS2532: Object is possibly 'undefined'.

  // Alternatively:
  foo.words[i] = foo.words[i] + 1
//               ~~~~~~~~~~~~ <same error>
}
```

Adding suitable checks in the loop-body for falsey values does _not_ fix it, eg:
```ts
if (foo && foo.words && foo.words[i]) {
 // Same code as above, same error
}
```

However the following _does_ fix it:
```ts
const word = foo.words[i]
if (word) {
  foo.words[i] = word + 1 // OK
}
```

### 🙁 Actual behavior

error TS2532: Object is possibly 'undefined'.

### 🙂 Expected behavior

No error - this type-checked fine previously

### Additional information about the issue

This issue is new since the new `Control Flow Narrowing for Constant Indexed Accesses` feature. Rolling back to the previous typescript version 'fixes' it
Repository: bitcoin
Issue: Erlay Project Tracking
Labels: Feature,P2P

This issue will be edited frequently to reflect the current status of the project.

**What should I review now?**
👇 👇 👇 👇 👇 👇 👇
#30116 
☝️ ☝️ ☝️ ☝️ ☝️ ☝️ ☝️

- [x] Minisketch in Bitcoin Core
    - [x] Main feature: #23114
    - [x] #23670
    - [x] #23496
    - [x] #26272
    - [x] Subtree updates: #24262, #25502, #26373
- [ ] Peer-to-peer
Full implementation: #30277 
    - [x] Main feature: #23443 
    - [x] Follow-up: #26359
    - [x] #27797 
    - [ ] Main feature: #26283
        - [ ] #28765
        - [ ] Tx reconciliation request
    - [ ] Main feature: Tx reconciliation response (sending and handling)
    - [ ] Main feature: Tx reconciliation extension request
    - [ ] Main feature: Tx reconciliation extension response (sending and handling)
    - [ ] Test: Full integration functional test 

**Performance research results**
- [How to understand bandwidth savings](https://github.com/naumenkogs/txrelaysim/issues/7)
- @kcalvinalvin [40% announcement-related bandwidth reduction](https://github.com/naumenkogs/txrelaysim/issues/8#issuecomment-1016075657)
- @0xB10C [31.3% overall bandwidth reduction](https://github.com/naumenkogs/txrelaysim/issues/8#issuecomment-920852514)
- @hebasto: [23.8% overall bandwidth reduction](https://github.com/naumenkogs/txrelaysim/issues/8#issuecomment-1016307869)
- @hebasto: [0.9% overall bandwidth overhead for running 12 connections instead of 8](https://github.com/naumenkogs/txrelaysim/issues/8#issuecomment-1018834268)
- @naumenkogs older experiments — note the current version is less efficient (needed for better security)
    - 8 conns [overall 40% bandwidth savings](https://github.com/bitcoin/bitcoin/pull/18261#issuecomment-599241490)
    - 16 conns [1.8x erlay; 2.23x non-erlay — overall bandwidth increase compared to 8 conns](https://github.com/bitcoin/bitcoin/pull/18261#issuecomment-600388543)

**Supplementary materials**
[BIP 330](https://github.com/bitcoin/bips/blob/master/bip-0330.mediawiki)
[erlay paper](https://arxiv.org/pdf/1905.10518.pdf)
[minisketch repo](https://github.com/sipa/minisketch)
Ancient PR: #18261
Notes from the review club: [on the main PR](https://bitcoincore.reviews/18261), [on the support signaling PR](https://bitcoincore.reviews/23443).

<details><summary><b>F.A.Q.</b></summary>
<i>1. Are these bandwidth savings worth the added code complexity?</i>

The project has received Concept ACK from many contributors, and no NACKs. I am unlikely to invent a bulletproof argument, so I leave it up to each reviewer to compare the risks and review costs to the benefits.

I personally think that the added code is pretty straightforward because it communicates with a legacy code through a thin interface (100 LOC in `net_processing.cpp` to collect transactions instead of relaying them immediately, although the reconciliation code is 500 LOC -- excluding comments and minisketch). Hence it is acceptable to pay for the given optimization.

If you suggest any experiment that will convince you, I will do my best to execute it.

</details>
Repository: material-ui
Issue: [examples] Migrate Next.js config.next.js to config.next.mjs
Labels: ready to take,examples,enhancement,nextjs

### Steps to reproduce

See https://github.com/mui/material-ui/blob/master/examples/material-ui-nextjs-pages-router-ts/next.config.js

### Current behavior

next.config.js file

### Expected behavior

next.config.mjs

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: -
Repository: go
Issue: x/tools/gopls: typeDefinition: support more kinds of syntax
Labels: help wanted,FeatureRequest,gopls,Tools

The LSP typeDefinition query reports the location of the definition of a type. Currently, it requires a symbol, whose type it computes, and from which it then tries to pick the most salient named type. But there are lots of other expressions for which it could give useful information:
- any expression
- a struct field
- imported package names.

gopls should support more of these.

(Unfortunately the LSP provides no way to support the "describe type" feature of the late [cmd/guru](https://pkg.go.dev/golang.org/x/tools/cmd/guru), which reported the type of the selected expression: TypeDefinition only returns a location, and Hover [does not accept a selection](https://github.com/microsoft/language-server-protocol/issues/1466). So there's no way to ask the type of just the "f(x)" portion of f(x).y. We should lobby for LSP to add a selection to Hover.)
Repository: ui
Issue: [bug]: Drawer ScrollArea frezzes swiping on ios
Labels: bug

### Describe the bug

Im using the drawer component as below:

      <Drawer open={isDrawerOpen} onOpenChange={setIsDrawerOpen}>
        <aside className="sticky bottom-0 w-full bg-white text-center shadow-summaryStroke md:hidden">
          <DrawerTrigger className="flex w-full flex-col items-center">
            <ChevronUp className="mt-2 size-6 animate-bounce text-personalizedOrange" />
            <div className="flex w-full justify-around">
              <h4 className="text-2xl font-semibold">Pay Now</h4>
              <div className="flex flex-col items-center">
                <h4 className="text-2xl font-semibold">Total</h4>
                {showLoader ? (
                  <LoaderCircle className="h-7 w-7 animate-spin text-personalizedOrange" />
                ) : (
                  <p className="text-xl">{totalAmount} $</p>
                )}
              </div>
            </div>
          </DrawerTrigger>
          <DrawerContent className="mx-2 max-h-[85vh] px-4 pb-2">
            <ScrollArea className="mt-4 overflow-y-auto">
              <SummaryBooking
                pickUpFee={form.watch("pickUpLocation")}
                dropOffFee={form.watch("dropOffLocation")}
                nightsSelected={nightsSelected}
                serviceFee={serviceFee}
                dates={form.watch("dateRange")}
                values={values}
                totalAmount={totalAmount}
                isFormValid={form.formState.isValid}
                setIsDrawerOpen={setIsDrawerOpen}
                selectedExtras={selectedExtras}
              />
            </ScrollArea>
          </DrawerContent>
        </aside>
      </Drawer>
      
      The issue that im having is that the scrolling inside the dreawer doesnt work always in safari sometimes it stucks and you cant scroll. you can remove unblock it only when you close the drawer.
      
      this issue seams to happen only on safari on ios.
      on chrome, firefox, opera it works perfectly.

https://github.com/shadcn-ui/ui/assets/58825526/55524f45-72ed-494b-ac65-193169226231

in this video is the drawer, the first time that i open it it works as it should the second time after the first vertical swipe it frezzed and you can only close it when you click the continue button or out of the drawer screen.

### Affected component/components

Drawer, ScrollArea

### How to reproduce

in this video is the drawer, the first time that i open it it works as it should the second time after the first vertical swipe, it frezzes and you can only close it when you click the continue button or out of the drawer screen.

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
no logs
```


### System Info

```bash
ios 17.5.1
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: Overriding LTO option in global config.toml release profile causes bootstrap failure
Labels: O-windows-msvc,T-bootstrap,A-contributor-roadblock,A-LTO

This is on MSVC Windows 10, I'm unsure if that matters.

1. Have a global config.toml that overrides the release profile with `lto = " fat"` or `lto = " thin"`

So for example `~/.cargo/config.toml` with
```toml
[profile.release]
lto = "thin"
... other settings that don't matter as much
```

3. Run `x.py build`
4. Wait for build failure
```log
C:\Users\rsmyth\Documents\rust> python .\x.py build
Building bootstrap
    Finished `dev` profile [unoptimized] target(s) in 2.11s
Building stage0 library artifacts (x86_64-pc-windows-msvc)
   Compiling compiler_builtins v0.1.109
   Compiling core v0.0.0 (C:\Users\rsmyth\Documents\rust\library\core)
   Compiling std v0.0.0 (C:\Users\rsmyth\Documents\rust\library\std)
   Compiling rustc-std-workspace-core v1.99.0 (C:\Users\rsmyth\Documents\rust\library\rustc-std-workspace-core)
   Compiling alloc v0.0.0 (C:\Users\rsmyth\Documents\rust\library\alloc)
   Compiling cfg-if v1.0.0
   Compiling rustc-demangle v0.1.24
   Compiling unwind v0.0.0 (C:\Users\rsmyth\Documents\rust\library\unwind)
   Compiling rustc-std-workspace-alloc v1.99.0 (C:\Users\rsmyth\Documents\rust\library\rustc-std-workspace-alloc)
   Compiling panic_unwind v0.0.0 (C:\Users\rsmyth\Documents\rust\library\panic_unwind)
   Compiling panic_abort v0.0.0 (C:\Users\rsmyth\Documents\rust\library\panic_abort)
   Compiling std_detect v0.1.5 (C:\Users\rsmyth\Documents\rust\library\stdarch\crates\std_detect)
   Compiling hashbrown v0.14.5
   Compiling rustc-std-workspace-std v1.99.0 (C:\Users\rsmyth\Documents\rust\library\rustc-std-workspace-std)
   Compiling proc_macro v0.0.0 (C:\Users\rsmyth\Documents\rust\library\proc_macro)
error: linker plugin based LTO is not supported together with `-C prefer-dynamic` when targeting Windows-like targets

error: could not compile `rustc-std-workspace-std` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `proc_macro` (lib) due to 1 previous error
Build completed unsuccessfully in 0:00:41
```

Luckily I know what this is caused by. But for other people, this may be confusing if they have a custom release profile.
Repository: pytorch
Issue: Use of standard library math functions vs global namespace 
Labels: module: cuda,module: rocm,triaged

## Issue description

Recently, it was discovered that some hip kernels prefer to use global namespace vs std namespace for various math functions.  There was a recent issue being discussed where the use of global namespace math functions was causing minor accuracy issues on ROCm. Please reference said issue comment for more background: https://github.com/pytorch/pytorch/issues/96560#issuecomment-2151063723

After some internal investigation it was found that the global namespace was chosen in accordance CUDA documentation:
https://docs.nvidia.com/cuda/cuda-math-api/index.html
```
Note also that due to implementation constraints, certain math functions from std:: namespace may be callable in device code even via explicitly qualified std:: names. However, such use is discouraged, since this capability is unsupported, unverified, undocumented, not portable, and may change without notice.
```

There have also been other issues related to this where the std namespace seems to be generally prioritized when, according to the above documentation, it shouldn't
https://github.com/pytorch/pytorch/pull/127812

So I wanted to open a discussion as to why CUDA kernels are prioritizing the std namespace over the global namespace?

Should we standardize to global namespace for consistency?


cc @ptrblck @msaroufim @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: PowerToys
Issue: FancyZones settings are not remembered 
Labels: Issue-Bug,Product-FancyZones

### Microsoft PowerToys version

0.81.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Reboot PC. PowerToys is among the startup applications. Laptop is connected to two external monitors and all three monitors are configured with FancyZone layouts. Shift-drag a window to where a FancyZone was previously created. FancyZone layouts for the two external monitors are switched. However, the monitors are numbered as they were when the layouts were originally configured.

### ✔️ Expected Behavior

I expect the FancyZone layouts I select for each monitor to remain unchanged the next time I boot my laptop.

### ❌ Actual Behavior

The FancyZone layouts for the two external monitors are swapped.

### Other Software

None.
Repository: TypeScript
Issue: Typescript 5.5 performance regression on arktype
Labels: Bug,Domain: Performance

It seems likely it was #58337 that was responsible for the performance hit in https://github.com/arktypeio/arktype

```ts
{
    "checkTime": 9.68,
    "types": 483415,
    "instantiations": 2629152
}

devDependencies:
- typescript 5.5.0-dev.20240429
+ typescript 5.5.0-dev.20240430

{
    "checkTime": 12.2,
    "types": 514846,
    "instantiations": 2819487
}
```

(previously incorrectly attributed it to https://github.com/microsoft/TypeScript/pull/58372)

_Originally posted by @ssalbdivad in https://github.com/microsoft/TypeScript/issues/58337#issuecomment-2154832204_
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] Race condition setting pod resize status
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

The kubelet updates the pod status by first generating the pod status based on its internal representation, and then [merging](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/status/status_manager.go#L1049) that with the latest status from the API, based on whether the Kubelet should be the source of truth for those fields.

Currently, the PodResizeStatus is not synced with the API server status, which means that whatever the Kubelet thinks the resize status should be will overwrite whatever PodResizeStatus is currently stored in the API server. This can lead to a race condition where the Kubelet has not yet seen a resize update, and clobbers the `Proposed` resize status.

I'm not sure exactly what the right behavior is here, but it probably needs to be an intelligent state transition, or may require comparing resource versions.

/sig node
/kind bug
/cc @vinaykul @thockin
Repository: godot
Issue: Theme should not be popping up every time you click on a node in the tree scene.
Labels: bug,topic:editor,needs testing,topic:gui

### Tested versions

v4.3.dev5.official [c9c17d6ca]

### System information

Linux Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8

### Issue description

If you create a scene and add a theme to a node, and close it,  it pops up the theme panel at the bottom when you click on a node in the scene. Happens even if you are viewing a different pane (E.g. Output or Debug). 

![image](https://github.com/godotengine/godot/assets/930478/62dbcb78-d9d9-484b-90f1-e8390c6660b4)


### Steps to reproduce

See sample project attached

1. Create a scene
2. Add a Control and nodes such as Label and Button
3. Create/Assign a theme to nodes.
4. Close theme panel
5. Click back on any node, whether in the Scene tree or Scene Editor.
6. Theme panel will open up

### Minimal reproduction project (MRP)

[Archive.zip](https://github.com/user-attachments/files/15745890/Archive.zip)
Repository: godot
Issue: VehicleBody3D completely annihilates itself when freezing and unfreezing the underlying RigidBody3D physics when any wheels are touching the ground.
Labels: topic:physics,needs testing,topic:3d

### Tested versions

Reproducible in Godot 4.2.2.


### System information

Windows 10 Godot 4.2.2 Forward +

### Issue description

The actual effect is difficult to ascertain, but when viewing from a camera that is not in any way attached to the vehicle and continuously resetting the position of the vehicle, the wheels are stuck floating in the air, and the moment the collision shape touches anything all physics related values like `global_position`, `linear_velocity`, `angular_velocity`, and quite a few other values all become Vector3's filled with `nan`.

Expected behavior:
The vehicle should unfreeze from the physics pause and work normally.

If no wheels are touching the ground when the vehicle is frozen and unfrozen, then this issue does not present. The duration the vehicle is frozen and unfrozen does not seem to matter.

### Steps to reproduce

Steps to reproduce:
1. Download the Truck Town starter sample.
2. Run the game and select any vehicle.
3. Open the remote node tree view and navigate to `/root/TownScene/InstancePos/car/Body`
4. While the vehicle is on the ground (resting or otherwise) check and uncheck the Freeze property under the RigidBody3D section.

Observe that your speed becomes -nan and the game's ability to render is completely destroyed. The audio listener also freaks out and the engine sound is lost as well.

### Minimal reproduction project (MRP)

The Truck Town sample project is sufficient as a minimal repro project.
Repository: ollama
Issue: Dictionary learning and concept extraction for model tuning
Labels: feature request

Described in Anthropic's [Mapping the Mind of a Large Language Model](https://www.anthropic.com/news/mapping-mind-language-model) and OpenAI's [Extracting Concepts from GPT-4](https://openai.com/index/extracting-concepts-from-gpt-4/).

Once we can identify the neurons associated with certain concepts for the publicly available model weights, we would benefit from the capability of changing their values for a higher degree of control
Repository: godot
Issue: Position marker not instantly updating in editor
Labels: bug,topic:editor,needs testing

### Tested versions

- Reproducible in v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 Ti (nvidia; 535.171.04) - AMD Ryzen 7 4800H with Radeon Graphics (16 Threads)

### Issue description

I have a simple script which updates the position of the child node in tool mode

```
@tool
extends Node2D

@export var btn := false : set=set_btn

func set_btn(new_val):
	if !new_val:
		return
	
	$ChildNode.global_position=Vector2(-100, -100)
```

when the function executes the position of the child node changes as evident by the Icon (green) changing it's position:

![image](https://github.com/godotengine/godot/assets/73928607/384ac4a8-2e01-436b-9692-9f16e112d053)


https://github.com/godotengine/godot/assets/73928607/1e126504-ccf0-488e-8d38-b21d58bfc561


but as you see the position marker gizmo (red) of the node still remains at the previous position and doesn't update until the mouse is dragged into the grey viewport area


Also if this is not a bug then is there a workaround ?

### Steps to reproduce

1. Recreate the scene tree as shown in the image
2. Attach the given code to the Main node
3. Press `btn` in the inspector 
4. Before you drag the mouse into the grey viewport area see that the position marker has not updated

### Minimal reproduction project (MRP)

[Demo.zip](https://github.com/user-attachments/files/15746447/Demo.zip)
Repository: next.js
Issue: Double redirected to basePath if the application is initially loaded not at the root.
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/inspiring-dan-fzvjxl

### To Reproduce

1. Install nextjs 14 with app router & typescript
2. Create about page in app/about/page.tsx
3. Create Link to home page (/) and about page (/about)
```
<ul>
  <li><Link href={'/'}>Home</Link></li>
  <li><Link href={'/about'}>About</Link></li>
</ul>
```
4. Add basePath `/admin` in file `next.config.mjs` 
```
const nextConfig = {
  basePath: '/admin'
};

export default nextConfig;
```
5. Run App, `yarn dev`
6. In the browser, access `http://localhost:3000/admin`
so running well

### Current vs. Expected behavior

**First Condition**:
1. If initially I access `http://localhost:3000/admin` and then 
2. I hover about link in Link component, I see `http://localhost:3000/admin/about` (its true) 
3. When I click it so next js will redirect to `http://localhost:3000/admin/about` (its true) then
4. I hover home link in Link component, I see `http://localhost:3000/admin` (its true) 
5. When I click it so next js will redirect to `http://localhost:3000/admin` (its true)

Good!

**BUT**

**Second Condition**:
1. If initially I access `http://localhost:3000/admin/about` and then 
2. I hover home link in Link component, I see `http://localhost:3000/admin` (its true) but when
3. I click it so next js will redirect to `http://localhost:3000/admin/admin` (its wrong) why??
4. I hover about link in Link component, I see `http://localhost:3000/admin/about` (its true) 
5. When I click it so next js will redirect to `http://localhost:3000/admin/about` (its true)

**Expected**:

Should hover link same with redirect link.. 

**Temporary my solution**

I change Link to home page (/) with html link for example
```
<ul>
  <li><a href={'/admin'}>Home</a></li>
  <li><Link href={'/about'}>About</Link></li>
</ul>
```


### Provide environment information

```bash
`npx next info`

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 9.1.4
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

-