sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for io_error_inprogress
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(io_error_inprogress)]`

This is a tracking issue for the `InProgress` variant on `std::io::Error`, equivalent to the Unix `EINPROGRESS` (no equivalent on other platforms).

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// std::io

pub enum ErrorKind {
    // ...
    InProgress,
    //
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] ACP: https://github.com/rust-lang/libs-team/issues/92
- [x] Implementation:
  - #130789
  - #130842
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: godot
Issue: Editor inspector issue - filename not updating when resource filename changed.
Labels: discussion,topic:editor,usability

### Tested versions

Godot 4*

### System information

Windows

### Issue description

If rename resource file (tres, res), - this changes not updated name this resource in inspector.
![image](https://github.com/user-attachments/assets/e804f24d-c691-4c96-9e45-8e2bd3dbb600)
![image](https://github.com/user-attachments/assets/6bbee97c-e16d-4d14-a8e1-3fd7b98f4d86)
i rename file to `BronzeSword`, but in inspector still old name - `Sword.tres`
Not critical issue, just QOL, but i make mistake based on wrong name :(

### Steps to reproduce

Make resource, save to file, open in inspector, rename resource in file explorer, check name in inspector.

### Minimal reproduction project (MRP)

-
Repository: langchain
Issue: Python kernel crashes when using Chroma's from_texts from langchain
Labels: Ɑ: vector store,🤖:bug,investigate

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

from langchain_community.vectorstores import Chroma
embed_model_path = '.././AI-ModelScope/bge-small-en-v1___5'
from langchain_huggingface import HuggingFaceEmbeddings
embedding = HuggingFaceEmbeddings(model_name=embed_model_path)
texts = [
    "Test"
]
try:
    smalldb_chinese = Chroma.from_texts(texts, embedding=embedding)
except Exception as r:
    print('%s' %(r))

### Error Message and Stack Trace (if applicable)

Process finished with exit code -1073741819 (0xC0000005)

### Description

When using the from_texts method of Chroma from langchain, the Python kernel crashes without any error messages. The process finishes with exit code -1073741819 (0xC0000005). This issue occurs consistently and makes it impossible to use this method effectively. I am using the latest version of Chroma from langchain and have tried on different environments but still encounter the same problem. Any help or suggestions to resolve this issue would be greatly appreciated.

### System Info

System Information
------------------
> OS:  Windows
> OS Version:  10.0.22631
> Python Version:  3.12.4 | packaged by Anaconda, Inc. | (main, Jun 18 2024, 15:03:56) [MSC v.1929 64 bit (AMD64)]

Package Information
-------------------
> langchain_core: 0.3.5
> langchain: 0.3.0
> langchain_community: 0.3.0
> langsmith: 0.1.125
> langchain_experimental: 0.3.0
> langchain_huggingface: 0.1.0
> langchain_text_splitters: 0.3.0

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.9.5
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> httpx: 0.27.0
> huggingface-hub: 0.24.5
> jsonpatch: 1.33
> numpy: 1.26.4
> orjson: 3.10.6
> packaging: 23.2
> pydantic: 2.8.2
> pydantic-settings: 2.5.2
> PyYAML: 6.0.1
> requests: 2.32.2
> sentence-transformers: 3.0.1
> SQLAlchemy: 2.0.30
> tenacity: 8.5.0
> tokenizers: 0.19.1
> transformers: 4.44.0
> typing-extensions: 4.11.0
Repository: PowerToys
Issue: Active Directory Does not show up on workspace
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

When creating a workspace, all my windows except my 2 active directory windows are added. Is there a reason that the RSAT tool for Active Directly Users and Groups is not being added to the workspace?
Repository: ollama
Issue: molmo by allen ai support 
Labels: model request

![GYVKif8XoAAFLAw](https://github.com/user-attachments/assets/74dead10-7370-4360-a326-41e40446f5b0)
https://huggingface.co/allenai/Molmo-7B-D-0924
https://huggingface.co/allenai/Molmo-72B-0924
This models are really good and have potential and fully open-source please give support for them.

thanks.
Repository: kubernetes
Issue: Inconsistent error message when attempting SSA with the wrong uid
Labels: sig/api-machinery,kind/feature,triage/accepted

### What happened?

I am specifying uid in a Server-Side Apply transaction to ensure that the object I am patching is the object I am expecting to patch, and to ensure I am not accidentally creating a new object. When specifying the wrong uid, the error message is:
```
The ConfigMap "foo" is invalid: metadata.uid: Invalid value: "014dbd28-1f25-42cb-a79c-955b98409d02": field is immutable
```

This is an error message about attempting to modify a value. Compare this to the error message from specifying an out-of-date resourceVersion:
```
error: Operation cannot be fulfilled on configmaps "foo": the object has been modified; please apply your changes to the latest version and try again
```

This is explicit about what has occurred.

### What did you expect to happen?

An error message which is clearer that an attempt was made to patch the wrong object. Maybe:
```
error: Operation cannot be fulfilled on configmaps "foo": patch specifies a different uid
```

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

`cm-test.yaml`:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: foo
  namespace: default
```

```
$ kubectl apply -f cm-test.yaml --server-side
```

Update `cm-test.yaml` with a uid different to whatever was generated:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: foo
  namespace: default
  uid: e5a88576-fcda-43ae-88af-4ca2a6087a16
```

```
$ kubectl apply -f cm-test.yaml --server-side
The ConfigMap "foo" is invalid: metadata.uid: Invalid value: "e5a88576-fcda-43ae-88af-4ca2a6087a16": field is immutable
```

### Anything else we need to know?

There may be additional context in https://kubernetes.slack.com/archives/C0EG7JC6T/p1727274176568809

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.28.4
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0
WARNING: version difference between client (1.28) and server (1.30) exceeds the supported minor version skew of +/-1
```

</details>


### Cloud provider

<details>
N/A
</details>


### OS version

<details>
N/A
</details>


### Install tools

<details>
N/A
</details>


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

<details>
N/A
</details>


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

<details>
N/A
</details>
Repository: vscode
Issue: repl multi-line input shrinks to 1 line after reloading editor
Labels: bug,interactive-window

(existing issue for the IW)

1. open the python native repl
2. put multiple lines in the input
3. switch tabs to hide the editor and switch back

:bug:
![image](https://github.com/user-attachments/assets/75c106b1-01e6-4f0b-8a5f-c2b7bc53a768)
Repository: godot
Issue:  (MacOS) Dropdowns in the setting menu are opened behind the settings window
Labels: bug,platform:macos,topic:gui

### Tested versions

- Tried in 4.3

### System information

Currently using macOS 12.7.6 21H1320 x86_6 with Intel i5-6360U (4) @ 2.00GHz CPU. 

### Issue description

Issue description: Dropdowns in the setting menu are opened behind the settings window

I was trying the 2d tutorial on the starting up docs. When changing the Stretch mode, I noticed the dropdown opened behind the setting window. I can select the options by moving with the arrow keys, but not with the mouse.

### Steps to reproduce

To replicate, I downloaded the latest version of Godot for Mac, created a new project, opened the edit in full screen and opened the settings.

### Minimal reproduction project (MRP)

<img width="1440" alt="Screenshot 2024-09-25 at 17 15 09" src="https://github.com/user-attachments/assets/1f6e2496-375d-4460-91b8-0dc84b1ca88f">
Repository: vscode
Issue: `vscode://settings/foo.bar` links do not work in chat window
Labels: feature-request,panel-chat


Type: <b>Bug</b>

We have a need to refer to some settings in the chat responses. Ideally we could use the `[Link Notation](vscode://settings/setting.id)`, but this does not work in the chat response--for whatever reason the link is just rendered as plain text instead of a link.

Other links (like web links) work just fine so I'm not sure why it's not working.

VS Code version: Code - Insiders 1.94.0-insider (be2747e47e127ec674148b78dd9556c6317d18bd, 2024-09-25T05:04:31.141Z)
OS version: Windows_NT x64 10.0.22631
Modes:

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (20 x 3696)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|126.84GB (95.28GB free)|
|Process Argv|--log ms-azuretools.vscode-azure-github-copilot=debug --crash-reporter-id a639fe75-6727-46d4-bc6c-acdb3cb6366a|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (19)</summary>

Extension|Author (truncated)|Version
---|---|---
tsl-problem-matcher|amo|0.6.2
esbuild-problem-matchers|con|0.0.3
vscode-eslint|dba|3.0.10
codespaces|Git|1.17.3
copilot|Git|1.234.1124
copilot-chat|Git|0.21.2024092501
azure-dev|ms-|0.8.3
vscode-azure-github-copilot|ms-|0.2.74
vscode-azureresourcegroups|ms-|0.9.5
vscode-docker|ms-|1.29.3
vscode-dotnet-runtime|ms-|2.1.6
debugpy|ms-|2024.11.2024092501
python|ms-|2024.15.2024092501
remote-containers|ms-|0.387.0
remote-wsl|ms-|0.88.4
extension-test-runner|ms-|0.0.12
vscode-selfhost-test-provider|ms-|0.3.25
vscode-yaml|red|1.15.0
fugio|Tyl|0.0.7


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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vscod805:30301674
vsaa593:30376534
py29gd2263:31024238
c4g48928:30535728
vscrpc:30624061
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
945dj816:31013170
a69g1124:31018687
dvdeprecation:31040973
dwnewjupytercf:31046870
nb_pkg_only:31057982
nativerepl1:31134653
refactort:31084545
pythonrstrctxt:31093868
flighttreat:31119334
wkspc-onlycs-t:31132770
nativeloc1:31118317
wkspc-ranged-c:31125598
cf971741:31144450
e80f6927:31120813
fje88620:31121564
12bdf347:31141542
iacca1:31144502
notype1:31143044
c9j82188:31138334
showchatpanel:31139797
f8igb616:31140137

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: torch.compile HUD dashboard should have repro commands 
Labels: module: ci,triaged,enhancement

For each of the models in https://hud.pytorch.org/benchmark/torchbench/inductor_no_cudagraphs?dashboard=torchinductor&startTime=Wed,%2018%20Sep%202024%2017:29:36%20GMT&stopTime=Wed,%2025%20Sep%202024%2017:29:36%20GMT&granularity=hour&mode=inference&dtype=bfloat16&deviceName=cuda%20(a100)&lBranch=main&lCommit=1cb265fafae115cc8acec28205e6244179a6b9c1&rBranch=main&rCommit=a0207c8471989f13b0a30d7b532545793fc20cc1

we should be able to generate a repro command. Right now I'm just blindly trying to figure out how to use the test runner (from instructions in  https://docs.google.com/document/d/1Nwt8vISn6uh_2TKEWsVMBB8u_LEs3NVTPfnQHAlB_yQ/edit)

cc @seemethere @malfet @pytorch/pytorch-dev-infra @huydhn
Repository: vscode
Issue: Improve Language Model Access declaration
Labels: bug,lm-access

<img width="669" alt="image" src="https://github.com/user-attachments/assets/e4f3cab6-0a8c-431a-a775-91ea5ec0f96e">

I've gotten a lot of feedback that this "GitHub Copilot Chat" entry is very confusing. It has nothing to do with Authentication... but it actually the gate for Language Model Access - the language models that GitHub Copilot Chat provides.

This really needs to be made clear.
Repository: pytorch
Issue: [TorchScript] typing_extensions.deprecated doesn't work
Labels: oncall: jit

### 🐛 Describe the bug

From S441024

repro

```python
import torch

from typing_extensions import deprecated

@deprecated("asdf")
def fn():
    return torch.compiler.is_compiling()

torch.jit.script(fn)
```

error:

```
Traceback (most recent call last):
  File "/data/users/dberard/scripts/torchscript_deprecated.py", line 9, in <module>
    torch.jit.script(fn)
  File "/data/users/dberard/pytorch/torch/jit/_script.py", line 1429, in script
    ret = _script_impl(
          ^^^^^^^^^^^^^
  File "/data/users/dberard/pytorch/torch/jit/_script.py", line 1205, in _script_impl
    fn = torch._C._jit_script_compile(
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError:
undefined value torch:
  File "/home/dberard/.conda/envs/pytorch311/lib/python3.11/site-packages/typing_extensions.py", line 7

@deprecated("asdf")
def fn():
    return torch.compiler.is_compiling()
           ~~~~~ <--- HERE
```

### Versions

viable/strict, CPU build

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: pytorch
Issue: [NJT] Dropout(0.0) with NJT increments cuda rng_state (only for no-compile)
Labels: triaged,module: nestedtensor

### 🐛 Describe the bug

**This only happens without compile**, so might be more of an edge case.

I ran into this while trying to implement a causal self attn + ffn with NJT and validating the results (the rng_state increment here somehow seemed to affect the output, can share a larger repro if this sounds odd).

Conventionally running `Dropout(0.0)` should not bump cuda rng state



```python
# 1. Dense tensor with no compile
import torch
import torch.nn as nn

m = nn.Dropout(0.0)
inp = torch.randn(2, 3, device='cuda')
gpu_rng_state = torch.cuda.get_rng_state()
m(inp)
assert torch.equal(torch.cuda.get_rng_state(), gpu_rng_state)  # passes


# 2. Nested tensor with compile
m = nn.Dropout(0.0)
sentence_lengths = torch.tensor([2, 3], device='cuda')
nested_inp = torch.nested.nested_tensor([
                torch.randn(l.item(), 3, device='cuda')
                for l in sentence_lengths
            ], layout=torch.jagged)
compiled_m = torch.compile(m)
gpu_rng_state = torch.cuda.get_rng_state()
compiled_m(nested_inp)
assert torch.equal(torch.cuda.get_rng_state(), gpu_rng_state) # passes


# 3. Nested tensor with no compile
m = nn.Dropout(0.0)
sentence_lengths = torch.tensor([2, 3], device='cuda')
nested_inp = torch.nested.nested_tensor([
                torch.randn(l.item(), 3, device='cuda')
                for l in sentence_lengths
            ], layout=torch.jagged)
gpu_rng_state = torch.cuda.get_rng_state()
m(nested_inp)
assert torch.equal(torch.cuda.get_rng_state(), gpu_rng_state)  # fails
```

### Versions

2.6.0.dev20240925+cu124

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: rust
Issue: Tracking Issue for mem_reshape
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(mem_reshape)]`

This is a tracking issue for `core::mem::reshape`.

`core::mem::reshape` allows modifying a mutable reference with its moved underlying value.  

### Public API

```rust
// core::mem

let mut x = "some_string".to_string();
reshape(&mut x, |x|  x + " that is reshaped");

println!("{x}");
```

### Steps / History

- [x] Implementation: #130849
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: deno
Issue: WebGPU: Deno Panics when a destroyed texture is used in a render pass 
Labels: webgpu

Hi! 

The following WebGPU program panics when a destroyed texture is used in a render pass. I think the correct behaviour is to throw some sort of validation error instead. 

I've tested this on v1.46.3 and 2.0.0-rc.5, and both versions produce the same error. I've only tested this on macOS. 

Here is the WebGPU program: 
```js
const adapter = await navigator.gpu.requestAdapter();
const device = await adapter.requestDevice();
const encoder = device.createCommandEncoder();
const texture = device.createTexture({
  dimension: "2d",
  format: "rg16float",
  size: {
    width: 1540,
  },
  usage: GPUTextureUsage.RENDER_ATTACHMENT,
});

const textureView = texture.createView();
const renderPassEncoder = encoder.beginRenderPass({
  colorAttachments: [
    {
      r: 1.0,
      loadOp: "load",
      storeOp: "store",
      view: textureView,
    },
  ],
});
texture.destroy();

renderPassEncoder.end();
```

This is how I ran the program:
```console
RUST_BACKTRACE=1 DENO_WEBGPU_BACKEND=metal deno run --allow-read --unstable-webgpu --allow-write webgpu.js
```

And here is the backtrace:
```console
thread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.21.1/src/storage.rs:113:39:
TextureView[Id(0,1,mtl)] does not exist
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: wgpu_core::storage::Storage<T>::get
   3: wgpu_core::track::stateless::StatelessTracker<T>::add_single
   4: wgpu_core::command::render::<impl wgpu_core::global::Global>::command_encoder_run_render_pass_impl
   5: wgpu_core::command::render::<impl wgpu_core::global::Global>::command_encoder_run_render_pass
   6: deno_webgpu::render_pass::op_webgpu_render_pass_end::op_webgpu_render_pass_end::v8_fn_ptr
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
Repository: kubernetes
Issue: [golang/go] x/net/http2: configurable server pings 
Labels: sig/network,sig/api-machinery,kind/feature,priority/important-longterm,triage/accepted

### What would you like to be added?

Add support to the apiserver send http2 ping frames to detect idle connections,[ it will be available in golang 1.24 ](https://github.com/golang/go/issues/67812)



### Why is this needed?

One of the most complex networking problems to troubleshoot are caused by stale connections, network hiccups or intermediate devices that lose the connection state can make connections to go idle without both endpoints noticing it.

The most common solution is for the application to implement network keepalives to detect the problems, http2 uses pings frames. We are already setting by default the http2 ping frames mechanism for clients with great success

https://github.com/kubernetes/kubernetes/blob/e542d9c8caa2c514a1e0c215f8c8a97386715777/staging/src/k8s.io/apimachinery/pkg/util/net/http.go#L179-L189

but adding it server side, will allow us improve our reliability extending this capabilities to all clients that are connected to the apiserver

/sig network
/sig api-machinery
/cc @ericlin
Repository: three.js
Issue: WebGPURenderer: Concurrency issue.
Labels: Enhancement

### Description

I believe @sunag is working on this, but posting here for reference:

This code block is leading to a concurrency problem.

https://github.com/mrdoob/three.js/blob/7b9a543a488cd842c41d9cee4fd4a826082475f2/src/renderers/common/PostProcessing.js#L69-L85

While awaiting `renderAsync()` to resolve, other asychronous calls to `renderer.render()` can occur -- in a loader callback, for example.

Adding some print statememts to the above block, I get results like this:

```
renderer.toneMapping temporarily set to:  0
renderer.toneMapping temporarily set to:  0

renderer.toneMapping restored to:  2
renderer.toneMapping restored to:  0

renderer.toneMapping temporarily set to:  0
renderer.toneMapping restored to:  0

renderer.toneMapping temporarily set to:  0
renderer.toneMapping restored to:  0

         .
         .

```


### Reproduction steps

see above

### Code

see above


### Live example

n/a

### Screenshots

_No response_

### Version

r169dev

### Device

_No response_

### Browser

_No response_

### OS

_No response_