sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: RichTextLabel flickers when changing text while threading is enabled
Labels: bug,topic:gui

### Godot version

v4.1.stable.official [970459615]

### System information

Windows 10 - Vulkan (Forward+) - GTX 970 - i7-10700K

### Issue description

Enabling threading on RichTextLabel causes it to flicker when you update its text property.

At first I thought this was only when BBCode was enabled but when making the MRP it turned out to be any text update. If you change text once a frame the text functionally disappears.

Also happens in v4.2.dev3.official [013e8e3af].

### Steps to reproduce

Enable threading on RichTextLabel and change its text. MRP attached.

A visual example (**flashing lights warning**):

https://github.com/godotengine/godot/assets/3820082/d81b2732-07b3-435e-a9dd-58d96484694c



### Minimal reproduction project

[rtl-threading-mrp.zip](https://github.com/godotengine/godot/files/12334288/rtl-threading-mrp.zip)
Repository: pytorch
Issue: torch.inverse throws error when DP but not in DDP or single GPU
Labels: needs reproduction,triaged,module: data parallel,module: linear algebra,module: edge cases

### 🐛 Describe the bug

## Description
When I use `torch.inverse` function, it throws an error when I train the model in DataParallel mode, but it will not appear if I use only a single GPU or in DDP mode. I use two RTX4090 on one machine and the OS is Ubuntu 22.04.1 LTS.

## Code
```
proj = torch.matmul(src_proj, torch.inverse(ref_proj))
```

## Error
```
Traceback (most recent call last):
  File "train.py", line 345, in <module>
    train(model, model_loss, optimizer, TrainImgLoader, TestImgLoader, start_epoch, args)
  File "train.py", line 49, in train
    loss, scalar_outputs, image_outputs = train_sample(model, model_loss, optimizer, sample, args)
  File "train.py", line 119, in train_sample
    outputs = model(
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 168, in forward
    outputs = self.parallel_apply(replicas, inputs, kwargs)
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 178, in parallel_apply
    return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 86, in parallel_apply
    output.reraise()
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/_utils.py", line 457, in reraise
    raise exception
torch._C._LinAlgError: Caught _LinAlgError in replica 1 on device 1.
Original Traceback (most recent call last):
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/parallel/parallel_apply.py", line 61, in _worker
    output = module(*input, **kwargs)
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/models/mymvsnet.py", line 101, in forward
    outputs_stage = self.StageNet(
  File "/Anaconda3/envs/mymvsnet/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/models/mymvsnet.py", line 151, in forward
    warped_src = homo_warping(src_fea, src_proj_new, ref_proj_new, depth_hypo)  # B C D H W
  File "/models/submodules.py", line 133, in homo_warping
    proj = torch.matmul(src_proj, torch.inverse(ref_proj))
torch._C._LinAlgError: torch.linalg.inv: (Batch element 0): The diagonal element 1 is zero, the inversion could not be completed because the input matrix is singular.
```

### Versions

## Pytorch Version
```
conda install pytorch==1.11.0 torchvision==0.12.0 torchaudio==0.11.0 cudatoolkit=11.3 -c pytorch
```

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: stable-diffusion-webui
Issue: [Feature Request]: Implement support of LoRA in diffusers format (.bin) 
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Implement native support of SDXL LoRA in diffusers format (.bin)

### Proposed workflow

The same as safetensors LoRA. Place a LoRA model.bin into stable-diffusion-webui-master\models\Lora and add <lora:model.bin:1> to prompt.

### Additional information

_No response_
Repository: PowerToys
Issue: Merge the setting page and the welcome page (or whatever that is) into a single screen.
Labels: Idea-Enhancement,Product-Settings,Area-OOBE,Needs-Triage

### Description of the new feature / enhancement

There is always a need to open the settings page. All the information (or at least all of the information I need) are on the settings page. 

I do not get the point of having that additional page that always shows you a 1 page intro for the plugins and the asks you to open the settings page anyway. 

In my opinion the welcome page can be depreciated and it will make it easier and straightforward for the useres as well as developers to deal with just one location.

![Powetoys_extra_screen](https://github.com/microsoft/PowerToys/assets/251768/dd600557-fcef-4ead-8cdf-aeadb3cd16f1)


### Scenario when this would be used?

1. Learning about any plugin
2. turning on / off any plugin
3. changing the preferences of any plugin

### Supporting information

_No response_
Repository: tauri
Issue: [feat] Get notified before getting killed by auto rebuild?
Labels: type: feature request

### Describe the problem

My app depends on a number of background processes. In `app.run` event `RunEvent::Exit`, I shut them down gracefully. However, during an auto-rebuild triggered by *.rs change, it seems that the main process is directly killed without sending a `RunEvent::Exit` event. As a result, all the background processes are left active.

### Describe the solution you'd like

I would like to receive some notification that the auto-rebuild is going to kill the main process soon. Or during the auto-rebuild, give the main process a chance to exit gracefully.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: godot
Issue: Multi caret undo breaks after typing too many characters
Labels: bug,topic:editor,topic:gui

### Godot version

v4.1.stable.official [970459615]

### System information

Windows 10

### Issue description

When replacing many instances of text with multi caret editing, if you replace it by typing too many characters the undo stack breaks with an error message `scene/gui/text_edit.cpp:4002 - Condition "!undo_stack_pos->prev()" is true. Breaking.`

### Steps to reproduce

Multi caret select a lot of text and replace it by typing new text. Attempt to undo.

https://github.com/godotengine/godot/assets/3820082/8b605188-6de3-450c-a9e8-82b2b4ace3f8


### Minimal reproduction project

N/A
Repository: go
Issue: proposal: context: functional interfaces
Labels: Proposal

# Description

The context.Context fulfils 3 different purposes:

- bag of values
- deadline
- cancellation.

These different functionalities are not apparent in any API - one has to rely on documentation  or read the source code to find out which of the different functionalities is expeceted from the user  of any specific API.

I proppose that we take a leaf out of the io.Reader, io.ReadWriter ... interfaces in the io package and define:

- context.Canceller
- context.Values
- context.Deadline
- context.DeadLineCanceller
- context.ValuesCanceller
- context.ValuesDeadline
- context.Context - all of them for backwards compatibility

API authors  can then specify the correct context and this will document in the code the expected context behaviour.

# Cons:

- Some packages will parse the context and act accordingly and this scheme will not work for them without some modification. For example the azure-sdk-for-go will enact a Timeout if the passed in context has a Timeout attribute - otherwise  it reverts to an internal retry with backoff.
- adopting this for any API will probably cause a major version change.

# From experience

Coding guidelines can dictate that a context contain values for general use such as headers or grpc metadayta. This leads to the decision to mandate that every network call uses a common context without realising that this common context might also contain a deadline which on every call becomes shorter and shorter leading to general flakiness. Fixing this in a large codebase without knowing what is expected of any passed in context is not trivial perhaps.

Hence the recent introduction of context.WithoutCancel().

I would assert that if we had the above subcontexts then WithoutCaancel may not be required.
Repository: node
Issue: Crash during ThreadSafeFunction finalization
Labels: node-api

### Version

v.18.15.0

### Platform

all (Win, MacOs)

### Subsystem

node api

### What steps will reproduce the bug?

[electron_test_tsfn_node_integrated_mode.zip](https://github.com/nodejs/node/files/12336461/electron_test_tsfn_node_integrated_mode.zip)
![electrone_25_crash_tsfn](https://github.com/nodejs/node/assets/35471979/2de23603-d73a-4b88-9d98-4f1b1099cfd1)

Close app window or press "Release" button

### How often does it reproduce? Is there a required condition?

[electron_node.log](https://github.com/nodejs/node/files/12336851/electron_node.log)

[pid 628060, tid: 707296 ] --------------FreeEnvironment start : 000008820120C000 uv_loop: 00007FF740548E28
[pid 628060, tid: 707296 ] --------------FreeEnvironment set_stopping(true): 000008820120C000
[pid 628060, tid: 707296 ] --------------FreeEnvironment before RunCleanup : 000008820120C000
// Here, the released function is being finalized from a foreign context
[pid 628060, tid: 707296 ] ThreadSafeFunction Finalize() f_name: test_tsfn Environment* :0000088200A9C000 Isolate: 0000088200834000 this=0000088200A7D400
[pid 628060, tid: 707296 ] env (param): 0000088200A9C000
env isolate ( env->isolate() ) : 0000088200834000
isolate to env ( Environment::GetCurrent(env->isolate()) ) : 000008820120C000
!!! Critical error Environment::GetCurrent(env->isolate())  not eq to env 0000088200A9C000 != 000008820120C000
.....

### What is the expected behavior? Why is that the expected behavior?

_No response_

### What do you see instead?

Absence of process abort

### Additional information

My quick bug fix:
/main/src/node_api.cc

void Finalize() {
   
    v8::HandleScope scope(env->isolate); 
    // <==  fix
    v8::Context::Scope context_scope(env->context());    
    // => fix
    if (finalize_cb) {
      CallbackScope cb_scope(this);
      env->CallFinalizer<false>(finalize_cb, finalize_data, context);
    }
    EmptyQueueAndDelete();
  }
Repository: godot
Issue: DOF Blur doesn't work when MSAA 3D is enable on the mobile render.
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

4.1.1

### System information

Apple Silicon Mac and iPhone - Godot v4.1.1.stable - Vulkan (Mobile)

### Issue description

When MSAA 3D anti-aliasing is enabled on the mobile render, DOF Blur will not appear at all. Sense it works with the Forward+ render, and as far as I can tell, there's nothing saying it shouldn't work, I'm assuming this is a bug.

**MSAA 3D enabled**
<img width="1680" alt="Screenshot 2023-08-14 at 11 05 09 AM" src="https://github.com/godotengine/godot/assets/131915465/c59763e6-421e-40aa-8116-a0944c507cc8">

**MSAA 3D disabled**
<img width="1680" alt="Screenshot 2023-08-14 at 11 05 41 AM" src="https://github.com/godotengine/godot/assets/131915465/cdd5a2bd-c0f5-4ed2-b664-22d152c53f75">


### Steps to reproduce

1. Switch to the mobile render.
2. Turn on DOF blur.
3. Turn on MSAA 3D anti-aliasing.

### Minimal reproduction project

N/A
Repository: go
Issue: proposal: testing: add TB.SetGOMAXPROCS 
Labels: Proposal

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->

I propose adding a SetGOMAXPROCS. This idea is inspired by TB.Setenv.  

As seen Go source codes, too, if it sets GOMAXPROCS and it unsets this value after cleanup, we must write the following ways.

```go
defer runtime.GOMAXPROCS(runtime.GOMAXPROCS(n))
```

```go
prev := runtime.GOMAXPROCS(n)
defer runtime.GOMAXPROCS(prev)
```

The writing style is general, if you know Go specification. But I think we can provide better way to achieve. 

I submitted a [CL](https://go-review.googlesource.com/c/go/+/519235). If this CL isn't been necessary, I don't mind to close it. Thanks.
Repository: godot
Issue: Rect2 class lacks definitions of `lerp()`/`cubic_interpolation()` and error occurs when interpolating negative values
Labels: bug,topic:core,topic:animation

### Godot version

v4.1.1.stable.flathub [bd6af8e0e]

### System information

Linux pop-os 6.4.6-76060406-generic, RTX3060

### Issue description

When animating texture_scale with cubic mode there is a flood of this error message
``
E 0:00:03:0438   intersects_transformed: Rect2 size is negative, this is not supported. Use Rect2.abs() to get a Rect2 with a positive size.
  <C++ Source>   core/math/rect2.cpp:113 @ intersects_transformed()
``
I assume animation is trying to set the value to something out of range, I would expect that would be handled by the editor and this situation will be prevented in AnimationPlayer or somewhere else.

### Steps to reproduce

1. Create a scene of type PointLight2D
2. add AnimationPlayer
3. Animate texture_scale property from minimal 0.01 in frame 1
4. to 0.2 in next keyframe
5. Set interpolation mode to cubic for this animation track
6. set animation to auto play
7. start the scene

### Minimal reproduction project

[animation_issue.zip](https://github.com/godotengine/godot/files/12337162/animation_issue.zip)
Repository: deno
Issue: JUnit: Capture stdout/stderr
Labels: feat,help wanted,testing

This is some leftover work from #19747. JUnit allows you to attach stdout/stderr output to the test case object. I briefly investigated if I could capture the stdout/stderr but realized that it was far too complex with the current architecture so I decided to punt it to later. We do capture the output, but it's put into a global stream and doesn't allow for us to determine what test/step produced the output. 

I'm not hugely familiar with how we're actually capturing the output, so I'm not sure if we can capture separate outputs for each test/step. If we can, it would be extremely valuable to add this as a capability since debugging without output is pretty hard.
Repository: go
Issue: x/tools/gopls: becomes slow in vscode after creating then deleting the $gopath/src and the vendor folder
Labels: gopls,Tools

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21.0 windows/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\User\AppData\Local\go-build
set GOENV=C:\Users\User\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\User\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\User\go
set GOPRIVATE=
set GOPROXY=https://goproxy.io,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21.0
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\User\AppData\Local\Temp\go-build959162870=/tmp/go-build -gno-record-gcc-switches

</pre></details>

### What did you do?
1. having a .go and .mod file, and the content doesn't matter. open it with vscode. ( at this time "go to def" and "format" functions work normally)
2. using `go vendor` create the vendor folder. ( this requires you to have at least one 3rd party library imported )
3. also copying the content of the vendor folder to $gopath/src. 
4. delete the 2 folders created by step 2 and step 3.
5. "go to def" and "format" respond very slowly it takes about minutes to format once. 

### What did you expect to see?
"go to def" and "format" work normally as always.


### What did you see instead?
"go to def" and "format" respond very slowly or becomes unresponsive.


note: 
1. I didn't test which folder actually causes this issue, but I guess both of them can.
2. the reason for doing step 2 and 3 are for the repl tool yaegi to import 3rd party package to work, but it fails, maybe because of windows according to some comments from its github repo issues that it only tested on linux and not like to support windows.
3. another trivial issue in step 5 is that there's also a popup at right bottom corner says "saving .go *something* configuration". this popup also appeared sometimes before, but the configuration is empty if you click the goto setting url
Repository: vscode
Issue: Set output height limit and scrolling for non-text stream outputs
Labels: feature-request,notebook-output

Sometimes the output from a code cell will be very large, which makes it impractical to display the entire output. According to [this answer](https://stackoverflow.com/a/69516283/9434803), I tried changing the setting "Notebook>Output: Text Line Limit" (`"notebook.output.textLineLimit": 5`). However, this seems to only limit the cell size of a pure text based output, and not outputs such as matrices, dataframes or other spreadsheet-like outputs (e.g. from the `View() function in R.) 

(NOTE: The cell code is written in R, although I wouldn't presume this to be relevant for this particular issue.)

##### Example setting:
###### GUI
[![enter image description here][1]][1]

###### (Alternatively) `settings.json`:

```json
"notebook.output.scrolling": true
"notebook.output.textLineLimit": 5
```

##### Example outputs:
###### Text output
Here the cell is limited to 5 lines, with a vertical scroll bar, as defined in the settings:
[![enter image description here][2]][2]

..but not for matrices, dataframes and spreadsheet-like objects.
###### Dataframe
[![enter image description here][3]][3]
###### Output from `View()`
[![enter image description here][4]][4]

#### My question therefore is:

Is it possible to limit cell height for other outputs than text?

  [1]: https://i.stack.imgur.com/rerWY.png
  [2]: https://i.stack.imgur.com/isbX3.png
  [3]: https://i.stack.imgur.com/W1Dry.png
  [4]: https://i.stack.imgur.com/dDGc1.png

_Originally posted by @pehkawn in https://github.com/microsoft/vscode-jupyter/discussions/14113_
Repository: deno
Issue: JUnit: Improve representation of test steps
Labels: feat,help wanted,testing

For #19747, I decided to represent the test steps using the ["steps" syntax used by Jenkins](https://github.com/testmoapp/junitxml#steps). This was at the time the least bad representation I could come up with because it doesn't break the result counts.

@lucacasonato pointed out that our test framework is inspired by Go's and that we should see how Go tools handle this problem. I looked at [jstemmer/go-junit-report](https://github.com/jstemmer/go-junit-report) and they have three modes for handling Go's subtests:
- [Default](https://github.com/jstemmer/go-junit-report/blob/7933520f1e28509e5ba6e95a6c3157d53c223561/parser/gotest/gotest.go#L72-L73): Treats parent and subtests identically
- [IgnoreParentResults](https://github.com/jstemmer/go-junit-report/blob/7933520f1e28509e5ba6e95a6c3157d53c223561/parser/gotest/gotest.go#L76-L79): Marks parent tests as passed no matter what happens but preserves any output
- [ExcludeParents](https://github.com/jstemmer/go-junit-report/blob/7933520f1e28509e5ba6e95a6c3157d53c223561/parser/gotest/gotest.go#L82-L87): Removes parent tests from the report entirely. This would kick the stdout/stderr of the parent steps to the global output.

I don't really like the default solution cause it breaks the failure counts (any subtest failure will cause one or more duplicate failures to be counted), so I propose that add the other two in addition to the default of using the Jenkins step format
Repository: excalidraw
Issue: stop updating labeled-arrow text's position on updates
Labels: bug,performance ⚡️,Labeled Arrows

Right now we're updating labeled-arrow text's position when we drag the arrow across the canvas. Since we're not relying on text position when rendering the labled-arrow, updating its position is unnecessary and and results in deoptimizations.

- [ ] when the arrow is inside a group and you move the group
- [x] when the arrow is inside a frame and you move the frame
- [x] when dragging plain labeled arrow
Repository: excalidraw
Issue: don't rely on container text position when rendering bound text
Labels: performance ⚡️,Text containers

Currently rendering container's bound text relies on its position, thus on its position being properly updated on updates such as when moving the container across the canvas.

This unnecessarily increases the complexity and prevents easy optimizations such as not trashing the cached canvas of the text element on shape non-destructive operations such as position change.

With labeled text, we're not relying on text position with labeled-arrows already (though [incorrectly still updating the position in some cases](https://github.com/excalidraw/excalidraw/issues/6882)), so we should align with that.
Repository: next.js
Issue: Middleware does not run before cached content is loaded
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.5
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/mgoodenough/nextjs-middleware-caching

### To Reproduce

**Step 1:** From the navigation menu on the Home page, click the Dashboard Link. Prior to page load, the middleware will log the following snippet to the console: pathname => /dashboard

**Step 2:** From the navigation menu on the Dashboard page, click the Home Link. Prior to page load, the middleware will log the following snippet to the console: pathname => /

**Step 3:** From the navigation menu on the Home page, click the Dashboard Link. Prior to page load, the middleware does not run.

### Describe the Bug

When navigating from one page to another in the Next.js app via the `Link` component, middleware will only run on the first visit and will not run on subsequent visits to previously viewed (cached) pages.

### Expected Behavior

When navigating from one page to another in the Next.js app via the `Link` component, middleware will run before cached content and routes are matched.

### Which browser are you using? (if relevant)

Chrome Version 114.0.5735.133

### How are you deploying your application? (if relevant)

_No response_