sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [DevTools Bug]: React profiler reporting false rendering times
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://codesandbox.io/p/sandbox/suspicious-darkness-zpfcld

### Repro steps

Visit sandbox: https://codesandbox.io/p/sandbox/suspicious-darkness-zpfcld?file=%2Fsrc%2FApp.js%3A19%2C22
(This is a modified version of a sandbox from Dan Abramov's blog https://overreacted.io/before-you-memo/) 

Observe that ExpensiveTree does not actually render when you type in the text input. I confirmed this with the Chrome CPU profiler (basically 100% idle):
<img width="341" alt="Screenshot 2024-10-24 at 1 36 54 PM" src="https://github.com/user-attachments/assets/e6444e4a-1543-4122-b9f4-5b22e41312b0">

Also, ExpensiveTree waits a random amount of time every time it updates. It renders the resulting delay, and you can observe that the value never changes.

However, React Profiler falsely reports that ExpensiveTree is actually rendering:

<img width="1590" alt="Screenshot 2024-10-24 at 1 38 06 PM" src="https://github.com/user-attachments/assets/8d09c18e-2a5f-473e-b65a-13d4c6b92449">

The times are all the same, which suggests that the Profiler UI is:

- falsely marking ExpensiveTree as rendered when it wasn't
- probably using the initial render time as the value



### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: flutter
Issue: [camera] Integration tests fail when Android example app targets SDK >=31
Labels: a: tests,platform-android,p: camera,package,P2,c: flake,team-android,triaged-android

Upon expecting an image to be at a resolution of 240, it receives 1080 instead. This is both `camera_android` and `camera_android_camerax`.

Related to https://github.com/flutter/flutter/issues/152929
Repository: react-native
Issue: Unhandled JS Exception: Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'DevMenu'
Labels: Needs: Repro,Newer Patch Available,Needs: Attention

### Description

Hi, Guys. 

Im stuck in this error for a while. It only happens in release mode. I dont know if it is a react native bug or not. Can any one help me please?

The error: 

Unhandled JS Exception: Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'DevMenu' when app will run on any device.



### Steps to reproduce

1 - Change schema to Release
2 - Run

### React Native Version

0.74.2

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.2.1
  CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
  Memory: 77.69 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.17.0
    path: /usr/local/bin/node
  Yarn:
    version: 3.6.4
    path: /usr/local/bin/yarn
  npm:
    version: 6.14.18
    path: ~/DevFontes/SarApp/node_modules/.bin/npm
  Watchman:
    version: 2024.08.26.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2021.2 AI-212.5712.43.2112.8512546
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /Users/alanmachado/.jenv/shims/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.6
    wanted: 0.74.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

info React Native v0.76.0 is now available (your project is running on v0.74.6).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.76.0
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.74.6
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".
```


### Stacktrace or Logs

```text
Unhandled JS Exception: Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'DevMenu' could not be found. Verify that a module by this name is registered in the native binary.Bridgeless mode: false. TurboModule interop: false. Modules loaded: {"NativeModules":["UIManager","PlatformConstants","DeviceInfo","SourceCode","BlobModule"],"TurboModules":[],"NotFound":["NativePerformanceCxx","NativePerformanceObserverCxx","RedBox","BugReporting","HeadlessJsTaskSupport","DevMenu"]}, js engine: hermes
```


### Reproducer

personal code

### Screenshots and Videos

_No response_
Repository: kubernetes
Issue: cloud-provider HasClusterID related functionality should have better documentation in the code
Labels: sig/storage,help wanted,sig/cloud-provider,triage/accepted

_note from @elmiko, i am transferring this issue from its original location https://github.com/kubernetes/cloud-provider/issues/71_

originally posted by @guettli 

Looking at the basic_main.go

```go
	if !cloud.HasClusterID() {
		if config.ComponentConfig.KubeCloudShared.AllowUntaggedCloud {
			klog.Warning("detected a cluster without a ClusterID.  A ClusterID will be required in the future.  Please tag your cluster to avoid any future issues")
		} else {
			klog.Fatalf("no ClusterID found.  A ClusterID is required for the cloud provider to function properly.  This check can be bypassed by setting the allow-untagged-cloud option")
		}
	}
```
[basic_main.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cloud-provider/sample/basic_main.go#L90)

But where is ClusterID actually used?

Afaik allow-untagged-cloud is deprecated, but afaik ClusterID does not get used.

The current state is confusing.

Please explain how a ccm should implement a ClusterID.

/sig cloud-provider
Repository: flutter
Issue: [in_app_purchase_storekit] ☂️ StoreKit2 Feature Tracker
Labels: c: new feature,platform-ios,platform-mac,P2,team-ios,triaged-ios

Now that in_app_purchase has been [migrated from StoreKit to StoreKit 2](https://github.com/flutter/flutter/issues/116383), incrementally add missing StoreKit 2 features:

### StoreKit 2 Features 😄 
- Restore Purchaes/Syncing Purchases
  - [ ] https://github.com/flutter/flutter/issues/118960
    - This may or not be covered by restorePurchases in the StoreKit2 implementation. 
    - https://developer.apple.com/documentation/storekit/transaction/3851204-currententitlements/
  - [ ] https://github.com/flutter/flutter/issues/159631
- [ ] Subscription Management 
  - [ ] https://github.com/flutter/flutter/issues/147698
  - [ ] https://github.com/flutter/flutter/issues/143514
  - [ ] https://github.com/flutter/flutter/issues/159664
  - [ ] https://github.com/flutter/flutter/issues/160826
  - [ ] https://github.com/flutter/flutter/issues/161393
- [ ]  StoreKitTest
  - [ ] https://github.com/flutter/flutter/issues/65082
    - This may be able to be closed as is, but maybe documentation should be written about how to use StoreKitTest first
- [ ] Transaction properties 
  - [ ] https://github.com/flutter/flutter/issues/158225
  - [x] https://github.com/flutter/flutter/issues/158882

### Package Level Issues 📦 
- [x] https://github.com/flutter/flutter/issues/158894
- [ ] https://github.com/flutter/flutter/issues/159871

### Bugs 🐛 
- [x] https://github.com/flutter/flutter/issues/159080
- [x] https://github.com/flutter/flutter/issues/159843
- [x] https://github.com/flutter/flutter/issues/160148
- [ ] https://github.com/flutter/flutter/issues/159807
Repository: storybook
Issue: [Bug]: @storybook/react - @types/estree is outdated
Labels: bug,dependencies,help wanted,sev:S3

### Describe the bug

Getting this error when building a image snapshot plugin for vitest browser mode integration:

```sh
node_modules/rollup/dist/rollup.d.ts (4:0): "BaseNode" is not exported by "node_modules/@types/estree/index.d.ts", imported by "node_modules/rollup/dist/rollup.d.ts".
DTS Build failed
```

This happen as I need to augment the `BrowserPage` type in `@vitest/browser/context`.

`rollup` is using `@types/estree` 1.0.6, while `@storybook/react` is using `0.0.51`

### Reproduction link

https://github.com/repobuddy/storybook-image-snapshot

### Reproduction steps

- Checkout branch `sb-estree`
- `npm i`
- `npm build`

Should observe: 

```sh
DTS ⚡️ Build success in 802ms
DTS dist/preview.d.ts 61.00 B
node_modules/rollup/dist/rollup.d.ts (4:0): "BaseNode" is not exported by "node_modules/@types/estree/index.d.ts", imported by "node_modules/rollup/dist/rollup.d.ts".
Error: error occured in dts build
```

### System

```sh
Storybook Environment Info:

  System:
    OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 20.10.0 - /run/user/1000/fnm_multishells/962_1729806910856/bin/node
    Yarn: 1.22.21 - /run/user/1000/fnm_multishells/962_1729806910856/bin/yarn
    npm: 10.2.3 - /run/user/1000/fnm_multishells/962_1729806910856/bin/npm <----- active
    pnpm: 9.12.1 - /run/user/1000/fnm_multishells/962_1729806910856/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.6 => 8.3.6 
    @storybook/addon-interactions: ^8.3.6 => 8.3.6 
    @storybook/addon-links: ^8.3.6 => 8.3.6 
    @storybook/blocks: ^8.3.6 => 8.3.6 
    @storybook/experimental-addon-test: ^8.3.6 => 8.3.6 
    @storybook/icons: ^1.2.10 => 1.2.10 
    @storybook/react: ^8.3.6 => 8.3.6 
    @storybook/react-vite: ^8.3.6 => 8.3.6 
    @storybook/test: ^8.3.6 => 8.3.6 
    storybook: ^8.3.6 => 8.3.6
```

### Additional context

_No response_
Repository: godot
Issue: In ParticleEmitters (at least CPU2D), the particles' gradient breaks if the parent has an animation playing.
Labels: bug,topic:animation,topic:particles

### Tested versions

Reproducible in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 SUPER (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i9-10900F CPU @ 2.80GHz (20 Threads)

### Issue description

When using CPUParticles2D (I have not tested other particles) and making the colour a gradient, the colour works as expected - shifting further right the longer its lifespan goes on. However, if the particle node or one of its parents has an animationPlayer playing an animation on it, it causes the gradient to seemingly break, and instead the colour of the particles seem to be based on when the particles spawn, which is wrong. I have attached an example below. They fix themselves instantly once the animation ends.

https://github.com/user-attachments/assets/b3bba603-b261-4795-8da8-08e3ac277778



### Steps to reproduce

1) Create a CPUParticles2D
2) Place a gradient on the particles (increase the amount of particles to make it easier to see)
3) Create an AnimationPlayer
4) Make an animation that manipulates the particles (what the animation does doesn't matter). Making the animation long or loop will make it easier to see)
5) Play the animation, and see the gradient freak out

### Minimal reproduction project (MRP)

N/A, follow the above steps
Repository: vscode
Issue: Multi-diff editor is not screen reader accessible
Labels: accessibility,multi-diff-editor

1. Enable a screen reader
2. Open the multi=diff editor
3. Navigate the diff

4. 🐛 , only the modified line is accessible, a user cannot navigate to the original line

 
![Image](https://github.com/user-attachments/assets/f33a158c-1ea8-4530-914a-197fae4365e1)
Repository: ui
Issue: [bug]: command clicks are ignored (although enter works as expected
Labels: bug

### Describe the bug

Given this component:

```jsx
const SatelliteSearch = () => {
  const satellites = useAtomValue($satellites);
  const [selectedSatelliteIndexes, setSelectedSatelliteIndexes] = useAtom(
    $selectedSatellitesIndexes
  );

  const [isFocused, setIsFocused] = useState(false);
  return (
    <div className="absolute top-2 right-2 z-50 w-96">
      <Command className="rounded-lg border shadow-md">
        <CommandInput
          placeholder="Search for a satellite by name or NORAD ID"
          onFocus={() => setIsFocused(true)}
          onBlur={() => setIsFocused(false)}
        />
        <CommandList>
          {isFocused && (
            <>
              <CommandEmpty>No results found.</CommandEmpty>
              {satellites.map((satellite) => (
                <CommandItem
                  key={`${satellite.name} (${satellite.satnum})`}
                  value={`${satellite.name} (${satellite.satnum})`}
                  onSelect={() => {
                    // if the satellite is already selected, remove it from the list
                    if (selectedSatelliteIndexes.has(satellite.index!)) {
                      selectedSatelliteIndexes.delete(satellite.index!);
                      setSelectedSatelliteIndexes(
                        new Set(selectedSatelliteIndexes)
                      );
                    } else {
                      setSelectedSatelliteIndexes(
                        new Set([satellite.index!, ...selectedSatelliteIndexes])
                      );
                    }
                  }}
                >
                  <span className="flex flex-row items-center w-full">
                    {satellite.name} ({satellite.satnum})
                  </span>

                  {selectedSatelliteIndexes.has(satellite.index!) ? (
                    <CheckIcon className="ml-2 h-4 w-4 text-green-500" />
                  ) : null}
                </CommandItem>
              ))}
            </>
          )}
        </CommandList>
      </Command>
    </div>
  );
};
```

Selecting via Enter works, but clicks do nothing (the list is just closed with no action and nothing I logs). 

### Affected component/components

Command, Command Item

### How to reproduce

Provided in the description. 

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
Nothing in the logs
```


### System Info

```bash
package.json:


"cmdk": "^1.0.0",

```

These two issues are both closed without an actual fix.

- https://github.com/shadcn-ui/ui/issues/2944
- https://github.com/shadcn-ui/ui/issues/2963
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: three.js
Issue: KTX2Loader: Improve transcoder target format selection
Labels: Suggestion,Loaders

### Description

Related:

- https://github.com/mrdoob/three.js/pull/29730

As described in the issue above, Firefox may indicate support for compressed formats that it actually emulates in drivers, decompressing or transcoding to another format. This emulation has much higher cost than just transcoding to the 'right' format in KTX2Loader, but we don't necessarily know what the right format is because Firefox doesn't say. We don't have this problem on ANGLE, but currently we are preserving a less-optimal choice of target transcoding format for ANGLE because of the Firefox issue.

### Solution

- [ ] Consider detecting the Firefox user agent and adjusting format selection as a special case, if we can do so reliably
    - For Linux+Firefox+RadeonSI we should prefer BCn formats over ETC2 as the target from ETC1S, when both are "supported"
    - For other platforms, is the reverse happening? Would Firefox report BCn support when only ETC2 is actually available?
- [ ] Test major browsers on multiple platforms, check target format selection, and implement unit tests for transcoder target formats if possible (WASM in tests may be tricky...)
- [ ] Consider preferring BC1/3 over BC7 for ETC1S transcoding
    - See https://github.com/KhronosGroup/3D-Formats-Guidelines/issues/25
- [ ] File an issue with Firefox about the emulated support
- [ ] Fix invalid WebGPU feature detection in KTX2Loader for (non-existent) texture-compression-bptc and texture-compression-etc1

### Alternatives

n/a

### Additional context

_No response_
Repository: node
Issue: dns.lookup timeout / cancellation
Labels: dns,feature request

### What is the problem this feature will solve?

I'm working on some dev tools that require the user to set up a local DNS record in their `/etc/hosts` file, and I'd like to check if this lookup of `some.custom.local` is resolving correctly to localhost.

If I understand correctly, dns `Resolver` does not hit the local OS dns stack, so I must use `dns.lookup`, however 
the resolver methods have options for timeout/retries and cancellation, and lookup does not.

If successful, the dns lookup returns very quickly, yet if it fails it hangs for quite a long time while it probably retries and waits for a timeout. I understand the lookup method is doing very different things to the resolver method and this may be challenging, but nonetheless, I would like to be able to set a very short timeout or cancel the lookup if it does not succeed immediately.

### What is the feature you are proposing to solve the problem?

I'd like to be able to set timeout/retry options on `dns.promises.lookup`, or to receive a promise that can be cancelled.

### What alternatives have you considered?

Current workaround is to use `Promise.race`, but the process still hangs until the dns lookup finishes.
```
const raceResult = await Promise.race([
  sleep(10, false),
  dns.promises.lookup(devHost),
]);
if (raceResult === false) {
  throw new Error('DNS LOOKUP FAILED');
  proces.exit(1);
}
```
Repository: pytorch
Issue: [torch.export] round is not an allowed operator type
Labels: triaged,oncall: pt2,oncall: export

### 🐛 Describe the bug

Hi team, just want to report that round isn't supported in export. This can be bypassed with `math.trunc(x + 0.5)`, which is supported.

repro:
```
class M(torch.nn.Module):
    def forward(self, x):
        ori_size = (
            round(x.shape[-2] / 1),
            round(x.shape[-1] / 1),
        )
        x = F.interpolate(x, size=ori_size, mode="bilinear")
        return x

input1 = (torch.rand(1, 3, 28, 28, device="cuda"),)
input2 = (torch.rand(1, 3, 56, 56, device="cuda"),)
inputs = [input1, input2]
model = M().cuda()

_ = model(*input1)

dynamic_shapes = {
    "x": {2: torch.export.Dim.DYNAMIC, 3: torch.export.Dim.DYNAMIC},
}
ep = torch.export.export(model, input1, dynamic_shapes=dynamic_shapes, strict=False)
path = torch._inductor.aot_compile(ep.module(), input1)
aot_model = torch._export.aot_load(path, device="cuda")
for input in inputs:
    torch.testing.assert_close(aot_model(*input), model(*input))
```

error:
```
torch/_export/verifier.py", line 197, in _check_valid_op
    raise SpecViolationError(
torch._export.verifier.SpecViolationError: Operator '<built-in function round>' is not an allowed operator type: (<class 'torch._ops.OpOverload'>, <class 'torch._ops.HigherOrderOperator'>)
Valid builtin ops: [<built-in function getitem>, <built-in function add>, <built-in function mul>, <built-in function sub>, <built-in function truediv>, <built-in function ge>, <built-in function le>, <built-in function gt>, <built-in function lt>, <built-in function eq>, <built-in function ne>, <built-in function floordiv>, <built-in function mod>, <built-in function and_>, <built-in function or_>, <built-in function not_>, <built-in function pow>, <built-in function neg>, <built-in function abs>, <built-in function ceil>, <built-in function floor>, <built-in function trunc>]Valid torch functions: (<class 'torch.autograd.grad_mode.set_grad_enabled'>, <function sym_int at 0x7fae060e30a0>, <function sym_float at 0x7fae060e3010>, <function sym_ite at 0x7fae060e3370>, <function sym_max at 0x7fae060e3130>, <function sym_min at 0x7fae060e3250>, <function sym_not at 0x7fae06305240>, <function _sym_sqrt at 0x7fae060e3400>, <built-in function _set_grad_enabled>, <function _enter_autocast at 0x7fae0127a950>, <function _exit_autocast at 0x7fae0127ac20>)
```

### Versions

trunk

cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: ui
Issue: [feat]: close sidebar on item click (mobile)
Labels: area: request

### Feature description
On mobile devices, where the sidebar is displayed as a drawer, clicking on a menu item navigates to the corresponding page but leaves the drawer open. This behavior is not ideal because the drawer continues to cover the main content area, preventing users from seeing the page they've navigated to.

### Current Implementation
```
<SidebarMenuButton asChild isActive={currentPath === "/analytics"}>
  <Link href="/analytics">
    <ChartSpline />
    <span>Analytics</span>
  </Link>
</SidebarMenuButton>
```

### Expected Behavior
When a user selects a menu item in the sidebar drawer on a mobile device, the drawer should automatically close after navigation. This allows the new page content to be immediately visible to the user.

### Question/Suggestion
Should we introduce an additional prop to the Sidebar component that enables the drawer to close when a SidebarMenuButton is clicked? Alternatively, is there another workaround or best practice we can implement to achieve this behavior?

### Affected component/components

Sidebar

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: pytorch
Issue: Using int(shape) in export would result in silent specialization
Labels: triaged,oncall: pt2,oncall: export

### 🐛 Describe the bug

Hi team, just reporting this problem. I can bypass it if I replace int with `math.trunc`.

repro:
```
class M(torch.nn.Module):
    def forward(self, x):
        ori_size = (
            int(x.shape[-2] / 1),
            int(x.shape[-1] / 1),
        )
        x = F.interpolate(x, size=ori_size, mode="bilinear")
        return x

input1 = (torch.rand(1, 3, 28, 28, device="cuda"),)
input2 = (torch.rand(1, 3, 56, 56, device="cuda"),)
inputs = [input1, input2]
model = M().cuda()

_ = model(*input1)

dynamic_shapes = {
    "x": {2: torch.export.Dim.DYNAMIC, 3: torch.export.Dim.DYNAMIC},
}
ep = torch.export.export(model, input1, dynamic_shapes=dynamic_shapes, strict=False)
path = torch._inductor.aot_compile(ep.module(), input1)
aot_model = torch._export.aot_load(path, device="cuda")
for input in inputs:
    torch.testing.assert_close(aot_model(*input), model(*input))
```

error:
```
torch/testing/_comparison.py", line 1530, in assert_close
    raise error_metas[0].to_error(msg)
AssertionError: The values for attribute 'shape' do not match: torch.Size([1, 3, 28, 28]) != torch.Size([1, 3, 56, 56]).
```

### Versions

trunk

cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4