sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Pod starting order after restart doesn't follow pod priorities
Labels: kind/bug,priority/backlog,sig/node,triage/accepted

### What happened?

Currently, after kubelet is restarted, pods are brought up in the order of creation, which can be completely random. This behaviour has been documented previously in #118452. What this causes is that the priorities of pods are ignored completely, and that pods that can't start until other pods are up can be started first, causing them to be stuck crashing and restarting for a while. While this eventually clears up, the process is wasting resources and time. 



### What did you expect to happen?

The pods should be started in the order determined by their priorities, pod with the highest priority being started first.

### How can we reproduce it (as minimally and precisely as possible)?

The cause is visible in the code, and can be observed in the logs after a restart. 

### Anything else we need to know?

The suggested fix is to change the starting order of the pods, sorting them firstly by the priority order and secondarily by the creation time. With this, the pods with dependencies are started after the pods they require, which should mean less crashes and restarts. This would also follow the expected behavior when using pod priorities.

I acknowledge that using the priority order won't solve the problem completely, which is why the author of #118452 closed that issue, but argue that with larger scale environments, there is a noticeable benefit to be gained from just this partial fix. 

If this is okay, I'd be willing to start working on the fix. 

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: tensorflow
Issue: tf.matmul gives inconsistent results for same data
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.8

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.8.0

### Custom code

Yes

### OS platform and distribution

windows 11

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

cuda 11.8

### GPU model and memory

_No response_

### Current behavior?

I want to do matmul(A,transpose(A)) and matmul(B,transpose(B)). Here, B is just matrix A with additional rows. A is 8 by 512 and b is 64 by 512 with first 8 rows exactly as that of A.

let’s call
A_out = A matmul transpose(A), this is 8 by 8,
B_out = B matmul transpose(B), this is 64 by 64.

So the above matmul just dots each row of a matrix with all the other rows of the same matrix. So if the first 8 rows in B are same as A then the top-left, 8 by 8 sub matrix of B_out should exactly be same as A_out.

tf.matmul operation doesnt produce this. however numpy does.

Please look into this

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
from tensorflow.keras.layers import Embedding

# Set up
embedding = Embedding(36711,512,mask_zero=True)
example_sequence = tf.constant([36710,  5095,   466, 16678,     5,     3,  5152, 36711] + [0]*(64-8))

pad_embed    = example_sequence # input with padding       # has shape (64,)
no_pad_embed = example_sequence[:8] # input without padding # has shape (8,)

no_pad_embed = embedding(no_pad_embed) # shape (8,512)  # A
pad_embed    = embedding(pad_embed)    # shape (64,512) # B : has same first 8 rows as A


# Real problem: I want to use matmul to do A @ A.T and B @ B.T
pad_out    = tf.matmul(pad_embed,pad_embed, transpose_b=True)
no_pad_out = tf.matmul(no_pad_embed,no_pad_embed, transpose_b=True)
#print(pad_out[:8,:8])
#print(no_pad_out)

print(tf.reduce_all(pad_out[:8,:8]==no_pad_out)) # False, meaning that the upper left 8 by 8 submatrix of pad_out is not equal to no_pad_out

import numpy as np

# Real problem: I want to use matmul to do A @ A.T and B @ B.T
pad_embed   = pad_embed.numpy()
no_pad_embed= no_pad_embed.numpy()

pad_out    = np.matmul(pad_embed,pad_embed.T)
no_pad_out = np.matmul(no_pad_embed,no_pad_embed.T)
#print(pad_out[:8,:8])
#print(no_pad_out)

print(tf.reduce_all(pad_out[:8,:8]==no_pad_out)) # True, meaning 8 by 8 submatrix of pad_out equals no_pad_out
```


### Relevant log output

```shell
tf.Tensor(False, shape=(), dtype=bool)
tf.Tensor(True, shape=(), dtype=bool)
```
Repository: puppeteer
Issue: [Feature]: Support extra args from Network.setUserAgentOverride
Labels: feature,P3

### Feature description

`Page.setUserAgent` only supports the `userAgent` and `userAgentMetadata` args from [Network.setUserAgentOverride](https://vanilla.aslushnikov.com/?Network.setUserAgentOverride). Would it be possible to get support for the `platform` and `acceptLanguage` args too? Although it's possible to set these with a raw `CDPSession`, it'd be nice to have it supported by Puppeteer so it  easily propagates to attached CDP sessions.

I'm keen on making a PR for this - curious whether you'd prefer to have the args added to the `Page.setUserAgent` function, or as separate `Page.setPlatform` and `Page.setAcceptLanguage` functions. The former feels preferable, but could be a breaking change.
Repository: godot
Issue: Resources referencing arrays of sub-Resources will break when the child resource script file is moved
Labels: enhancement,discussion,topic:gdscript,topic:editor

### Tested versions

4.2.2

### System information

Godot v4.2.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 Ti (NVIDIA; 32.0.15.5599) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)

### Issue description

Resource .tres files which reference an array of sub-resources are not automatically updated when the script file for the sub resource file is moved. For example:

```
[resource]
script = ExtResource("1_lnayw")
cards = Array[Resource("res://ResourceScripts/StaticData/CardData.gd")]([])
```

Needs to manually be updated to

```
[resource]
script = ExtResource("1_lnayw")
cards = Array[Resource("res://ResourceScripts/StaticData/Cards/CardData.gd")]([])
```

If the CardData script is moved into the Cards folder. This can be very hard to understand and to fix, and moving files around as a project gets bigger is vital for maintaining a coherent project structure.

### Steps to reproduce

1. Load the attached project
2. Run it
3. Note the lack of error
4. Drag the script ChildResourceScript.gd into the folder MoveChildResourceScriptHereToBreakProject
5. Run the project again
6. Note that it crashes

[MigrationTest.zip](https://github.com/user-attachments/files/16048959/MigrationTest.zip)


### Minimal reproduction project (MRP)

[MigrationTest.zip](https://github.com/user-attachments/files/16048959/MigrationTest.zip)
Repository: vscode
Issue: Recognize paths with ~ on Windows
Labels: feature-request,workbench-cli

<!-- ⚠️⚠️ 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. -->

## Current status

On Windows, using PowerShell, autocompletion usually adds `~` in front of the path, e.g., I type `.ssh` press <kbd>TAB</kbd> and it autocompletes to `~\.ssh`. 

However, when opening code with `code ~\.ssh` it fails to recognize `~` as the `$HOME` directory and always tries to generate a new file:
![Opening with ~\.ssh](https://github.com/microsoft/vscode/assets/6493651/b633b561-5bc9-4488-ae7e-33754f20242a)

Instead, I have to open it with `code C:\Users\<my_username>\.ssh` which is a hassle because PowerShell doesn't autocomplete `~` to `C:\Users\<my_username>` any more. This is the same directory opened with `C:\Users\<my_username>\.ssh`: 
![Opening with C:\Users\<my_username>\.ssh](https://github.com/microsoft/vscode/assets/6493651/6eeb52d7-ceba-4c8c-b8e9-bcf7a4df6b10)

## Feature request

Recognize `~` inside a path submitted on the command line on Windows as the user HOME directory.
Repository: three.js
Issue: Significant Performance Drop and High CPU Usage with BatchedMesh
Labels: Needs Investigation

### Description

Hello,

I exported a building model from Revit in glTF format and merged meshes with the same materials to manage their visibility in Three.js using the BatchedMesh class. However, I've encountered a significant performance issue when rendering these merged meshes with BatchedMesh compared to using Mesh.

**Performance Comparison:**

* **BatchedMesh Rendering:**
  * CPU Usage: ~40%
  * GPU Usage: ~30%
  * Frame Rate: ~20 FPS
* **Mesh Rendering:**
  * CPU Usage: ~15%
  * GPU Usage: ~90%
  * Frame Rate: ~60 FPS

This drastic difference in performance is concerning, especially the high CPU load and low frame rate when using BatchedMesh. I've already set `.perObjectFrustumCulled` and `.sortObjects` to `false` in BatchedMesh, which, if set to `true`, leads to an even more severe frame rate drop.

Additionally, I'm using `three-csm` and `postprocessing` frameworks alongside Three.js.

**System Configuration:**

* CPU: Intel i7-10700
* GPU: NVIDIA RTX 2080 Super

Could someone help me understand why BatchedMesh increases the CPU overhead so significantly and suggest any possible optimizations or solutions to improve the frame rate?



Thank you!

### Reproduction steps

Using BatchedMesh to render more than 10 million triangles and vertices, there are about 100,000 different geometries.

### Code

Code in the project
[batched-mesh-performance-test](https://github.com/lanvada/batched-mesh-performance-test)

### Live example

Code in the project
[batched-mesh-performance-test](https://github.com/lanvada/batched-mesh-performance-test)

### Screenshots

_No response_

### Version

r165

### Device

_No response_

### Browser

_No response_

### OS

_No response_
Repository: ant-design
Issue: DirectoryTree component not working when expandedKeys=undefined
Labels: help wanted,Inactive

### Reproduction link

[https://antd-reproduce-5x-7veb3c.stackblitz.io](https://antd-reproduce-5x-7veb3c.stackblitz.io)

### Steps to reproduce

When, in Tree (DirectoryTree) component the prop expandedKeys is specified and set to either undefined or [], the tree nodes are not expandable anymore

### What is expected?

When expandedKeys is set to undefined, you should still be able to expand any node you like

### What is actually happening?

The nodes are not expandable

<img width="1362" alt="Screenshot 2024-07-01 at 11 16 16" src="https://github.com/ant-design/ant-design/assets/172485993/b11003df-24dc-4041-bb21-381c3d421163">


| Environment | Info |
| --- | --- |
| antd | 5.18.3 |
| React | 18.3.1 |
| System | Macos - latest |
| Browser | Chrome - latest |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Formatting notebook cells with Black leads to random blank lines
Labels: bug,info-needed,notebook-format

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: it needs black formatter extension enabled.

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.90.2
- OS Version: Win10 22H2

This issue is I think linked to #200503 but somehow it has been closed and i can't participate, there's also mention of people still having this problem on that issue.

I had the exact same problem as #200503 @CanePlayz example once but didn't manage to reproduce that specific condition, what i got to reproduce is an extra blank line between a comment and the definition of a function.


Steps to Reproduce:

1. Create a .ipynb notebook file with black formatter extension from Microsoft
2. Create a cell with a comment and a def function ex:
```python
# this is a test function

def test_function(x):
    x = x + 1
    return x

test_function(1)
```

The expected result is that this cell shouldn't be necessarily reformatted as it is. You can verify with using black from the terminal with the command black [filename] `1 file left unchanged.`

but with the Black formatter extension (that uses the same black.exe) that i have on format on save, it will reformat adding an extra blank line.
```python
# this is a test function


def test_function(x):
    x = x + 1
    return x

test_function(1)
```
Repository: storybook
Issue: [Bug]: expect.toThrow does not work
Labels: bug,sev:S2,test utilities

### Describe the bug

Getting this error when calling expect.toThrow()

```tsx
export const LoggedIn: Story = {
  play: async ({ canvasElement }) => {
    await expect(() => {
      throw new Error('throw');
    }).toThrowError();
  },
};
```

```
Caught exception in play function
TypeError: Cannot redefine property: not
    at Function.defineProperty (<anonymous>)
    at https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/node_modules/.cache/storybook/1c3385a5d25e538d10b518b310c74d3ca2690b6aaffeadccd74da79736171f86/sb-vite/deps/chunk-ICANM5TM.js?v=455c4f60:1577:23
    at Array.reduce (<anonymous>)
    at Instrumenter.instrument (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/node_modules/.cache/storybook/1c3385a5d25e538d10b518b310c74d3ca2690b6aaffeadccd74da79736171f86/sb-vite/deps/chunk-ICANM5TM.js?v=455c4f60:1570:29)
    at Instrumenter.track (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/node_modules/.cache/storybook/1c3385a5d25e538d10b518b310c74d3ca2690b6aaffeadccd74da79736171f86/sb-vite/deps/chunk-ICANM5TM.js?v=455c4f60:1588:17)
    at Proxy.toThrowError (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/node_modules/.cache/storybook/1c3385a5d25e538d10b518b310c74d3ca2690b6aaffeadccd74da79736171f86/sb-vite/deps/chunk-ICANM5TM.js?v=455c4f60:1580:262)
    at play (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/src/stories/Page.stories.ts:23:8)
    at playFunction (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/sb-preview/runtime.js:113:6184)
    at https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/sb-preview/runtime.js:149:3903
    at StoryRender.runPhase (https://kkvilmnmwpgithub-soxc--6006--70dbe416.local-credentialless.webcontainer.io/sb-preview/runtime.js:149:943)
```

### Reproduction link

https://stackblitz.com/edit/github-qlgvbq?file=src%2Fstories%2FPage.stories.ts

### Reproduction steps

_No response_

### System

```bash
torybook Environment Info:

  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.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/addon-interactions: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/addon-links: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/addon-onboarding: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/blocks: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/react: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/react-vite: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    @storybook/test: ^8.2.0-alpha.10 => 8.2.0-alpha.10 
    storybook: ^8.2.0-alpha.10 => 8.2.0-alpha.10
```


### Additional context

_No response_
Repository: vscode
Issue: WSL cannot reach Windows localhost as proxy
Labels: feature-request,proxy

Hello,

I am experiencing an issue with Visual Studio Code when working on a Windows 11 system using WSL Arch Linux. It appears that VSCode's JSON schema loading process is using the proxy settings configured for Windows rather than those set for WSL.

System Information
Operating System: Windows 11
WSL Distribution: Arch Linux
VSCode Version: 1.90.2
Proxy Settings
Windows Proxy: 127.0.0.1:7890 (Configured via Clash)
WSL Proxy: 172.24.0.1:7890 (WSL Gateway Address)
Issue Description
When I try to load JSON schemas, it seems that VSCode is attempting to use the Windows proxy settings (127.0.0.1:7890). However, WSL uses a different proxy address (172.24.0.1:7890), causing connection failures and errors in schema loading.

Steps to Reproduce
Configure Clash on Windows with the proxy address 127.0.0.1:7890.
Set up WSL Arch Linux with a different proxy address (e.g., 172.24.0.1:7890).
Open VSCode and attempt to load JSON schemas.
Expected Behavior
VSCode should respect the proxy settings configured for WSL when operating within the WSL environment, allowing JSON schema loading to succeed.

Actual Behavior
VSCode uses the Windows proxy settings, leading to connection failures and schema loading errors.

Additional Information
Please let me know if there are any logs or additional details I can provide to assist in troubleshooting this issue.

Thank you for your assistance.
![image](https://github.com/microsoft/vscode/assets/49502869/d6d7c4e2-f85d-4964-bb9d-b33c7bd03b7e)
Repository: pytorch
Issue: `saved_tensors_hooks`/`_pop_saved_tensors_default_hooks` API extension
Labels: module: checkpoint,module: autograd,triaged,module: multithreading,needs research

### 🚀 The feature, motivation and pitch

I want to implement gradient checkpointing API where I want to specify some tensors which are not stored for backpropagation. The current `checkpoint` API does not allow for that. Only intermediate tensors are not stored, but the final tensor will likely be stored, as this would be outside of what `checkpoint` handles.

Related discussions:
* https://discuss.pytorch.org/t/gradient-checkpointing/205416
* https://github.com/rwth-i6/returnn/issues/1552

To implement what I want, I however need to extend the `saved_tensors_hooks` scope up to a future point once the relevant tensor goes out of scope. I can of course do that for some specific models, but I don't really see any good way to do this in a general way. For that, the `saved_tensors_hooks` API somehow would need to be extended.

My current very hacky solution is:

* Manually call `saved_tensors_hooks.__enter__` when I need to enter.
* Detect when the relevant `tensor`s go out of scope. At that point, call `saved_tensors_hooks.__exit__`.

This hacky solution is very problematic for multiple reasons:

* Detecting when the tensors go out of scope is tricky.
* Calling `saved_tensors_hooks.__exit__` from a different thread does not work because the scope is thread-local. (E.g. when I put some logic in `__del__` somewhere to do this, I can potentially run into this problem.)
* Calling `saved_tensors_hooks.__exit__` when there was another unrelated `saved_tensors_hooks.__enter__` in the meantime will lead to wrong behavior.

Also, actually a more fine-grained hook would be even nicer: Basically whenever `pack_hook` is called on my relevant tensors, I want to execute my hook, but otherwise not.

cc @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7


### Alternatives

_No response_

### Additional context

_No response_
Repository: rust
Issue: Wrong codegen for simd_select_bitmask on big-endian targets
Labels: A-LLVM,A-codegen,T-compiler,A-SIMD,C-bug

Given the testcase
```rust
#![feature(repr_simd, intrinsics)]

extern "rust-intrinsic" {
    fn simd_bitmask<T, U>(v: T) -> U;
    fn simd_select_bitmask<T, U>(m: T, a: U, b: U) -> U;
}

#[repr(simd, packed)]
#[allow(non_camel_case_types)]
#[derive(Copy, Clone, Debug, PartialEq)]
pub struct i32x10([i32; 10]);
impl i32x10 {
    fn splat(x: i32) -> Self {
        Self([x; 10])
    }
}

pub fn main() {
    // Non-power-of-2 multi-byte mask.
    unsafe {
        let mask = i32x10([-1, -1, 0, -1, 0, 0, -1, 0, -1, 0]);
        let mask_bytes =
            if cfg!(target_endian = "little") { [0b01001011, 0b01] } else { [0b11, 0b01001010] };

        let selected2 = simd_select_bitmask::<[u8; 2], _>(
            mask_bytes,
            i32x10::splat(-1), // yes
            i32x10::splat(0),  // no
        );

        assert_eq!(selected2, mask);
    }
}
```
on a big-endian target, this passes with optimizations but fails without. LLVM optimizations correctly implement the semantics of the IR this generates (so the resulting program is trivial), but without optimizations all the IR reaches the backend and somewhere in the LLVM machine backend, things go wrong.

See [here](https://github.com/rust-lang/rust/pull/126171#issuecomment-2199863295) for some analysis.

Cc @uweigand @nikic