sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Vulkan Mobile: LightmapGI baking makes environment light twice as dark as it should be
Labels: bug,topic:rendering,topic:3d

### Tested versions

- Reproducible in: 4.3.beta 92c8e87cd

### System information

Godot v4.3.beta (92c8e87cd) - Fedora Linux 40 (KDE Plasma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 555.58.02) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

LightmapGI baking in Forward Mobile makes environment light twice as dark as it should be.
This means that the visual outcome of lightmap baking is different, even if you view the lightmaps in the same rendering method:

Forward+ bake (seen in Compatibility) | Mobile bake (seen in Compatibility)[^2] | Compatibility bake[^1]
-|-|-
![Screenshot_20240715_220255_forward_plus png webp](https://github.com/user-attachments/assets/097ec109-f7fd-42c1-808d-83b2e2b2580b) | ![Screenshot_20240715_220407_mobile png webp](https://github.com/user-attachments/assets/e16b03d4-8544-4e51-bde7-b782293c74cb) | ![Screenshot_20240715_220232_compatibility png webp](https://github.com/user-attachments/assets/bda6bed4-c6ab-4fc4-b7a6-e4ba894d4d8f)

[^1]: This uses Forward+ for baking on desktop platforms, [Mobile on mobile platforms](https://github.com/godotengine/godot/issues/94297) if I'm not mistaken.
[^2]: Glowing material emission is missing due to https://github.com/godotengine/godot/issues/94406.

Environment baking in Mobile was added in https://github.com/godotengine/godot/pull/85793. I assume it's missing the `2.0` exposure multiplier that we use elsewhere, e.g. for real-time sky reflections: https://github.com/godotengine/godot/issues/55878

cc @Lasuch69 

### Steps to reproduce

- Bake lightmaps in Forward+. Run the scene and look at the results.
- Switch to the Mobile rendering method. Restart the editor and bake lightmaps.
- Switch to the Forward+ rendering method. Run the scene **without baking lightmaps** and look at the results. Notice how the scene now looks darker overall, particularly in areas that only receive baked environment lighting.

### Minimal reproduction project (MRP)

[test_lightmapper_rendering_methods.zip](https://github.com/user-attachments/files/16240035/test_lightmapper_rendering_methods.zip)
Repository: godot
Issue: Audio only plays on one viewport (3D)
Labels: bug,topic:audio,topic:3d

### Tested versions

 v4.2.2 stable.

### System information

Windows 10

### Issue description

I think I have found a problem similar to the one listed on the link, but only for the 3D camera. the sound (AudioStreamPlayer3D) is played only for the camera that was last specified as the current one. regardless of the fact that it is in another subviewport. https://github.com/godotengine/godot/issues/76634

### Steps to reproduce

create a scene without a 3D camera, add Audio Stream Player 3D, two subviewports, each with a 3D camera. move the cameras in turn from the sound playback location. or in the attached project, you can move the cameras or change their current flag to hear it.

### Minimal reproduction project (MRP)

[bug.zip](https://github.com/user-attachments/files/16240098/bug.zip)
Repository: godot
Issue: OpenGL: Baking lightmaps has broken emissive material properties
Labels: bug,topic:rendering,topic:3d

### Tested versions

- Reproducible in: 4.3.beta 92c8e87cd

### System information

Godot v4.3.beta (92c8e87cd) - Fedora Linux 40 (KDE Plasma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 555.58.02) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

Baking lightmaps has broken emissive material properties if done while using the Compatibility rendering method. Rendering lightmaps that were baked while using Forward+ or Mobile looks correct.

Denoising is disabled in the comparisons below, but the issue remains with the denoiser enabled.

*From left to right: Boxes with Emission Energy set to 1.0, then 0.5, then 10.0*

Forward+ bake (seen in Compatibility) | Compatibility bake
-|-
![Forward+](https://github.com/user-attachments/assets/63968b38-cab6-42cf-b2c6-dc35c766530d) | ![Compatibility](https://github.com/user-attachments/assets/78ac8e85-b5a9-459b-b3ef-1ec2aa9d38e2)

This also affects the generated lightmap probes, which you can check in the MRP by looking above the boxes in the editor with the LightmapGI node selected.

This issue can be seen in a less extreme fashion in https://github.com/godotengine/godot/issues/94401, where the green emissive lighting is entirely missing in Compatibility, even though it renders correctly if lightmaps were baked while using Forward+.

### Steps to reproduce

- Create a MeshInstance3D with a PrimitiveMesh that has **Add UV2** enabled, and give it an emissive material.
- Add a second mesh (also with **Add UV2**) so that the result of emissive lighting can be seen on some surface.
- Bake lightmaps while using the Compatibiltiy rendering method.

### Minimal reproduction project (MRP)

[test_lightmap_emissive.zip](https://github.com/user-attachments/files/16240351/test_lightmap_emissive.zip)
Repository: deno
Issue: deno test - default test file pattern no longer works (regression)
Labels: testing

Version: Deno 1.45.2

After upgrade deno from 1.44.4 to 1.45.2 `deno test` default pattern no longer works - as is mentioned in [docs](https://docs.deno.com/runtime/manual/basics/testing/#running-tests).
Now - 1.45.2 it matches everything in particular directory

```
$  deno test --allow-read=__tests__ --allow-write=__tests__ __tests__
Check file:///E:/<fullpath>/__tests__/env-template.ts
Check file:///E:/<fullpath>/__tests__/mockServerLocalConvert_test.ts
Check file:///E:/<fullpath>/__tests__/mockServerLocalResult.js
Check file:///E:/<fullpath>/__tests__/setOptions_test.ts
error: TS2339 [ERROR]: Property 'createEnvConfig' does not exist on type 'Window & typeof globalThis'.
```

with old 1.44.4
```
$  deno test --allow-read=__tests__ --allow-write=__tests__ __tests__
running 1 test from ./__tests__/mockServerLocalConvert_test.ts
mock server local convert test ... ok (7ms)
running 1 test from ./__tests__/setOptions_test.ts
setOptionsByMockServer test ... ok (0ms)

ok | 2 passed | 0 failed (41ms)
```

There is also change in presented path - original was relative, now is full path. I'm in favor of relative - as presented in cli parametr and it's more readable
Repository: godot
Issue: OpenGL: `Condition "t->is_render_target" is true.` is printed every time LightmapGI is baked with Environment mode set to Scene or Custom Sky
Labels: bug,topic:rendering,confirmed,topic:3d

### Tested versions

- Reproducible in: 4.3.beta 92c8e87cd

### System information

Godot v4.3.beta (92c8e87cd) - Fedora Linux 40 (KDE Plasma) - X11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (nvidia; 555.58.02) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

Every time you bake lightmaps with the Scene or Custom Sky environment node in Compatibility, you get this error:

```
 drivers/gles3/storage/texture_storage.cpp:717 - Condition "t->is_render_target" is true.
```

Baking still succeeds and the texture is saved to disk correctly.

This error does not occur when baking using Forward+ or Mobile, or when using another environment mode in LightmapGI.

### Steps to reproduce

- Bake lightmaps with environment mode set to Scene (the default).

### Minimal reproduction project (MRP)

[test_lightmap_environment.zip](https://github.com/user-attachments/files/16240462/test_lightmap_environment.zip)
Repository: pytorch
Issue: Migrate gradcheck with check_batched_grad=True to use the new torch.vmap
Labels: triaged,module: vmap

Otherwise, it's very spammy.
Repository: godot
Issue: OpenGL: Selecting a lightmap EXR texture in the FileSystem dock prints an error about SamplerCubeArray not being supported
Labels: bug,topic:rendering,topic:editor,confirmed

### Tested versions

- Reproducible in: 4.3.beta 92c8e87cd

### System information

Godot v4.3.beta (92c8e87cd) - Fedora Linux 40 (KDE Plasma) - X11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (nvidia; 555.58.02) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

When using Compatibility, the first time you double-click a lightmap EXR texture in the FileSystem dock, you get an error:

```
drivers/gles3/storage/material_storage.cpp:950 - Type: SamplerCubeArray not supported in GL Compatibility rendering backend, please use another type.
```

The editor keeps functioning normally and lightmaps still render correctly.

It's strange that this error appears, as lightmap textures use Texture2DArray, not CubemapArray. Cubemap arrays are generally only used for reflections (and the Compatibility rendering method doesn't use those).

### Steps to reproduce

- Select a lightmap EXR texture in the FileSystem dock while using the Compatibility rendering method.

### Minimal reproduction project (MRP)

[test_lightmap_environment.zip](https://github.com/user-attachments/files/16240462/test_lightmap_environment.zip)
Repository: pytorch
Issue: [Inductor] Add an API to register external callable candidates for inductor's Matmul/Conv tuning choices
Labels: triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

During the lowering of Matmul/Conv into Inductor IR, a group of candidates including external library calls as well as triton template kernel is formed. These candidates will be benchmarked and tuned in the later fusion scheduling stage.

If we want to add a potentially faster third-party/custom kernel to these candidates we can only modify the pytorch source code. This feature suggests exposing an out-of-tree registration API for adding new candidates.

A user will be able to do:
```
from torch._inductor.external_kernels import register_external_matmul

# user specified callable
def custom_matmul_kernel(a, b, c):
...

# out-of-tree registration
register_external_matmul(custom_matmul_kernel)
```

After the registration, when the user calls the Inductor backend, this custom kernel will be among one of the tuning candidates.

There are several kernels that supports tuning including: Convolution, variants of Matmul and Flex attention. I'd like to hear from you guys if we can consider adding registration API for all these kernels.

This is a simple draft PR of this purposal https://github.com/pytorch/pytorch/pull/130774. 

Jason @jansel , I don't know who to CC so please help me assign CCs.

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @anijain2305 @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: deno
Issue: feat: Add support for Cobertura XML coverage reporting
Labels: suggestion,testing

Deno 1.45.2

I have this following script in my `deno.json` file:  
`{"test": "deno test -A --junit-path=./deno-test.xml"}`  

It creates this `xml` file which is nice, however when I open this file there's no code coverage, it only says the amount of time it took to run, here a random line to use as an example:

`<testcase name="zap receipt does not have a &quot;description&quot; tag" classname="./src/pipeline.test.ts" time="0.017" line="60" col="6">`
Repository: PowerToys
Issue: Using Peek in PowerToys Run Interface
Labels: Idea-Enhancement,Product-PowerToys Run

### Description of the new feature / enhancement

I'm suggesting an option to use the **Peek** function via the **PowerToys Run** interface, first selecting a file in the search, then by using the Peek **shortcut** or a **contextual button**. This would be capable of previewing the file in a faster way than searching in the files explorer. Also, a possible behavior of this utility is that if I'm peeking a file, powertoys run wouldn't close until I get back to choose a file.

### Scenario when this would be used?

Let's imagine I'm looking for a file that I need urgently, but there are a lot of files with a similar name. With the peek function in PowerToys Run, I could preview that files until I find the right one easily.

### Supporting information

_No response_
Repository: pytorch
Issue: `with torch.device()` modifies the `as_tensor` intended behavior
Labels: triaged,release notes: python_frontend

### 🐛 Describe the bug

The [documentation for `torch.as_tensor`](https://pytorch.org/docs/stable/generated/torch.as_tensor.html) states

> If data is already a tensor with the requested dtype and device then data itself is returned, but if data is a tensor with a different dtype or device then it’s copied

and

> device ([torch.device](https://pytorch.org/docs/stable/tensor_attributes.html#torch.device), optional) – the device of the constructed tensor. If None and data is a tensor then the device of data is used. If None and data is not a tensor then the result tensor is constructed on the current device.

This is true during normal usage:

```python
# reference storage
>>> x = torch.randn(5)
>>> x.data_ptr()
94796162806080

# a different device triggers a copy as expected
>>> torch.as_tensor(x, dtype=torch.float32, device="cuda").data_ptr()
140593739071488
# same storage
>>> torch.as_tensor(x, dtype=torch.float32).data_ptr()
94796162806080
```

However, when this is done under the `torch.device()` context manager, the device of the input is no longer preferred

```python
# this case now produces a copy
>>> with torch.device("cuda"): torch.as_tensor(x, dtype=torch.float32).data_ptr()
140593739071488
# specifying the device produces the expected result 
>>> with torch.device("cuda"): torch.as_tensor(x, dtype=torch.float32, device=x.device).data_ptr()
94796162806080
```

So clearly, the documentation's description is not correct under this circumstance.

This difference can result in bugs depending on whether the context manager is enabled or not if the rest of the code assumes that the output will share storage.

I'm not sure if `as_tensor` implementation should be changed to fit the documentation, or if the documentation should mention this edge case.

Thank you.



### Versions

torch 2.3.1
Repository: go
Issue: proposal: encoding/xml: reject directives by default
Labels: Proposal

### Proposal Details

`encoding/xml` currently reads XML directives, but it doesn’t process them.  Parsing XML DTDs is far too complex for `encoding/xml`.  Furthermore, DTD processing is a frequent source of security issues.  For instance, they are a required part of Billion Laughs and XML External Entity attacks, and they were also involved in a recent double-free in libxml2.

I propose that `encoding/xml` reject XML directives entirely by default.  This is the only way I can see implementing #68299, and is consistent with recent versions of .NET.
Repository: PowerToys
Issue: More combination for Keyboard Manager
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

# Request for "Keyboard Manager"

# descriptions

Currently, Alt (left) and Alt (right) (and others with left/right) are supported.
But the pushing both left and right button combination is not supported.
I want to use such combinations to switch behaviors since alt is near the spacebar and is usually easy to access.


### Scenario when this would be used?

always

### Supporting information

_No response_
Repository: go
Issue: encoding/xml: accepts ill-formed XML declarations
Labels: NeedsInvestigation

### Go version

Git main

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/user/.cache/go-build'
GOENV='/home/user/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/user/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/user/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/user/go/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/user/go/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-071b8d51c1a70fa6b12f0bed2e93370e193333fd Fri Jul 12 22:42:17 2024 +0000'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/user/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/user/go/go/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1803937823=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Tried to parse XML with various ill-formed XML declarations, such as the following:

1. Wrong order of key/value pairs:

    ```xml
    <?xml standalone="yes" version="1.0"?>
    ```

2. Missing space between key/value pairs:

    ```xml
    <?xml version="1.0"standalone="yes"?>
    ```

3. Junk in data:

    ```xml
    <?xml version="1.0" a standalone="yes"?>
    ```

4. Invalid key:

    ```xml
    <?xml version="1.0" dalone="yes"?>
    ```

5. Invalid encoding:

    ```xml
    <?xml version="1.0" encoding="not valid"?>
    ```

6. Invalid standalone value

    ```xml
    <?xml version="1.0" standalone="not valid"?>
    ```

### What did you see happen?

No error, so long as a `CharsetReader` that can handle the invalid encoding is provided.

### What did you expect to see?

Errors because these documents are ill-formed.
Repository: ollama
Issue: Allow using `"""` in TEMPLATE Modelfile command
Labels: feature request
Repository: pytorch
Issue: Generalizing cross product to hodge star operator
Labels: triaged,enhancement,module: python frontend

### 🚀 The feature, motivation and pitch

Posting here to shop around and get feedback on the idea of generalizing the cross product operations in Pytorch to a hodge star operator: https://en.wikipedia.org/wiki/Hodge_star_operator

Hodge star generalizes the cross-product of 3-dimensions to arbitrary dimensions. It maps a k differential form to a d-k differential form. While it looks involved at first glance, it can likely be computed fairly easily with the existing Pytorch machinery (however whether also efficiently, would have to be investigated).

Conceptually it would make sense for Pytorch if there's not much special about 3 dimensional space (exception here seems to be 3d convolutions and related applications). Indeed, most Pytorch tensor operations operate on arbitrary dimensionality.

Counterargument is the suite of differential geometry operations is not part of the standard deep learning application repertoire, though Lie groups do present more and more in research. For example, here's one google search hit: https://github.com/lucidrains/lie-transformer-pytorch/blob/main/lie_transformer_pytorch/se3.py#L72

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD
Repository: kubernetes
Issue: Projected secrets mounted with a subPath disappear after the secret is updated.
Labels: kind/bug,sig/storage,triage/needs-information,needs-triage

### What happened?

I want to prevent kubernetes from automatically updating my mounted secrets. I project my secrets in a volume and mount them with a subpath to unlink them. In the configuration I see the files I expect and they are unlinked. After I update the secret I mounted the files disappear from the pod.

### What did you expect to happen?

I expect nothing to happen. I have unlinked the secrets and after a update of the secret I expect my pod to be unaffected.

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

```
apiVersion: v1
kind: Pod
metadata:
  name: mypod-no-update
spec:
  containers:
  - name: mycontainer
    image: busybox
    command: ['sh', '-c', 'sleep 3000']
    volumeMounts:
    - name: mysecrets
      mountPath: /etc/secret-volume
      subPath: cert
      # Optional: You can specify read-only here
      readOnly: true
  volumes:
  - name: mysecrets
    projected:
      sources:
      - secret:
          name: mysecret
          items:
            - key: username
              path: cert/mysecret.txt
          # Optional: You can specify defaultMode here, which is reflected in 
          # the file permissions for the files created from the secret
---
apiVersion: v1
data:
  password: bXlwYXNzd29yZA==
  username: bXl1c2Vy
kind: Secret
metadata:
  name: mysecret
type: Opaque
```

Apply these resources check if the file is present in the pod. Edit the secret and see that file disappears.

### Anything else we need to know?

The functionality does work when you created a volume mount per file.

### Kubernetes version

Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.4 and     v1.27.13+e709aa5


### Cloud provider

Locally and also tested on Openshift 

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ uname -a
Linux 6.5.0-41-generic #41~22.04.2-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun  3 11:32:55 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
</details

### Install tools

<details>
microk8s and openshift
</details>


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

<details>
containerd://1.6.28
</details>


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

no
Repository: ant-design
Issue: ConfigProvider包裹的Modal组件设置了destroyOnClose 关闭之后不销毁dom
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/vitejs-vite-gz5i4k?file=package.json,src%2FApp.tsx,src%2Fmain.tsx,src%2Fdemo.tsx,package-lock.json&terminal=dev)

### Steps to reproduce

对照：
- 1.点击open1按钮，关闭open1模态框，重复，dom均被销毁
- 2.点击open2按钮，关闭open2模态框，重复，dom有时被销毁，大多数情况下还是存在，存在就会引起页面再点击无任何反应，点击都点在了弹出层上
    - 2-1.注释掉ConfigProvider包裹，只保留Modal同1，没有问题。

### What is expected?

dom被销毁

### What is actually happening?

dom有时被销毁，大多数情况下还是存在

| Environment | Info |
| --- | --- |
| antd | 5.17.0 |
| React | 18.3.1 |
| System | macOS 14.4.1 |
| Browser | Chrome 126.0.6478.127 |

---
定位问题应该就是ConfigProvider的问题，注释掉就可，但是嵌套使用文档也是这样使用的

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->