sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: TestScript/gotoolchain_local failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/gotoolchain_local"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8753431724635905841)):

    === RUN   TestScript/gotoolchain_local
    === PAUSE TestScript/gotoolchain_local
    === CONT  TestScript/gotoolchain_local
        script_test.go:136: 2024-03-15T03:48:08Z
        script_test.go:138: $WORK=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-737770916/tmpdir1671365449/gotoolchain_local1631686399
        script_test.go:160: 
            PATH=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-737770916/tmpdir1671365449/testbin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/cache/tools/bin:/Users/swarming/.swarming/w/ir/bbagent_utility_packages:/Users/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages:/Users/swarming/.swarming/w/ir/cipd_bin_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/Users/swarming/.swarming/w/ir/cache/cipd_client:/Users/swarming/.swarming/w/ir/cache/cipd_client/bin:/Users/swarming/.swarming/cipd_cache/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            # go install m@v should handle queries (0.036s)
            > ! go install rsc.io/fortune/nonexist@v0.0
            [stderr]
            go: rsc.io/fortune@v0.0.1 requires go >= 1.21rc999; switching to go1.22.9
            [signal: illegal instruction]
            > stderr '^go: rsc.io/fortune@v0.0.1 requires go >= 1.21rc999; switching to go1.22.9$'
            matched: go: rsc.io/fortune@v0.0.1 requires go >= 1.21rc999; switching to go1.22.9
            > stderr '^go: rsc.io/fortune/nonexist@v0.0: module rsc.io/fortune@v0.0 found \(v0.0.1\), but does not contain package rsc.io/fortune/nonexist'
        script_test.go:160: FAIL: testdata/script/gotoolchain_local.txt:238: stderr '^go: rsc.io/fortune/nonexist@v0.0: module rsc.io/fortune@v0.0 found \(v0.0.1\), but does not contain package rsc.io/fortune/nonexist': no match for `(?m)^go: rsc.io/fortune/nonexist@v0.0: module rsc.io/fortune@v0.0 found \(v0.0.1\), but does not contain package rsc.io/fortune/nonexist` in stderr
    --- FAIL: TestScript/gotoolchain_local (4.71s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: When will the ChatGLM model be supported？
Labels: model request

### What model would you like?

When will the ChatGLM model be supported
Repository: PowerToys
Issue: [Mouse without borders] Cursor jumps
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.79.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1. activate feature
2. Use feature

### ✔️ Expected Behavior

smooth transition between screens, with no acceleration of cursor

### ❌ Actual Behavior

cursor shoots from eadge of screen into the center of the other machine's screen

### Other Software

_No response_
Repository: kubernetes
Issue: [Flaking Test] ci-kubernetes-integration-master TestSelectableFields
Labels: sig/api-machinery,kind/flake,triage/accepted

### Which jobs are flaking?

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-integration-master/1768366435643428864

### Which tests are flaking?

k8s.io/apiextensions-apiserver/test: integration

TestSelectableFields

### Since when has it been flaking?

15/3/2024

### Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#integration-master

### Reason for failure (if possible)

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-integration-master/1768366435643428864#1:build-log.txt%3A27112

```
panic: conversion webhook for tests.example.com/v1, Kind=Shirt failed: Post "https://127.0.0.1:45105/convert?timeout=30s": EOF
goroutine 57030 [running]:
k8s.io/apiserver/pkg/storage/etcd3.decodeObj({0x2cd4dc0?, 0xc0005d7360?}, {0x2ce45c0, 0x43049a0}, {0xc000727680?, 0x1e0?, 0xc000951f30?}, 0x503c)
	/home/prow/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/etcd3/watcher.go:612 +0x1c6
k8s.io/apiserver/pkg/storage/etcd3.(*watchChan).prepareObjs(0xc0007ede10, 0xc0012ddef0)
	/home/prow/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/etcd3/watcher.go:580 +0xe5
k8s.io/apiserver/pkg/storage/etcd3.(*watchChan).transform(0xc0007ede10, 0xc0012ddef0)
	/home/prow/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/etcd3/watcher.go:469 +0x3b
k8s.io/apiserver/pkg/storage/etcd3.(*watchChan).processEvent(0xc0007ede10, 0x2c7d7b3a22737574?)
	/home/prow/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/etcd3/watcher.go:434 +0x125
created by k8s.io/apiserver/pkg/storage/etcd3.(*watchChan).run in goroutine 57028
	/home/prow/go/src/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/etcd3/watcher.go:234 +0x129
```

### Anything else we need to know?

Test was introduced in https://github.com/kubernetes/kubernetes/pull/122717

### Relevant SIG(s)

/sig api-machinery
Repository: vscode
Issue: Cannot place multiple cursors between a space and ASCII letter
Labels: bug,editor-core


Type: <b>Bug</b>

1. start holding alt
2. place some cursors between u+0020 and an ascii letter
3. stop holding alt

Results: The cursors disappear (maybe lose focus?) until VSCode is restarted.

Expected: The cursors do not disappear

VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22621
Modes:

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

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)|
|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|
|Load (avg)|undefined|
|Memory (System)|15.74GB (5.85GB free)|
|Process Argv|--crash-reporter-id 6cc89dd3-0ce0-4d8a-8f50-322857abf052|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (30)</summary>

Extension|Author (truncated)|Version
---|---|---
surround-with-tag|Bal|1.0.0
insert-unicode|bru|0.15.1
altx|Dig|0.0.3
sort-json-array|fvc|3.1.0
vscode-pull-request-github|Git|0.82.0
vscode-markdown-footnote|hou|1.0.0
latex-workshop|Jam|9.19.1
diff-tool|jin|0.0.1
vscode-filesize|mkx|3.1.0
debugpy|ms-|2024.2.0
python|ms-|2024.2.1
cpptools|ms-|1.19.8
vsliveshare|ms-|1.0.5918
typst-lsp|nva|0.12.1
latex-sympy-calculator|Ora|1.6.0
java|red|1.28.1
remove-tabs-on-save|red|1.2.4
LiveServer|rit|5.7.9
xcompose|Rub|1.1.1
rust-analyzer|rus|0.3.1877
sort-lines|Tyr|1.11.0
errorlens|use|3.16.0
vscode-lldb|vad|1.10.0
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.3.1
vscode-java-debug|vsc|0.56.2
vscode-java-dependency|vsc|0.23.5
vscode-java-pack|vsc|0.25.15
vscode-java-test|vsc|0.40.1
vscode-maven|vsc|0.44.0


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

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:30979542
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp1r6:30958156
dsvsc020:30976470

```

</details>

<!-- generated by issue reporter -->
Repository: ollama
Issue: Possibility to remove max retries exceeded when downloading models from a slow connection
Labels: feature request

### What are you trying to do?

I'm trying to download Mixtral (26Gb), but every 120 mb an error pops up stating:
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/e9/e9e56e8bb5f0fcd4860675e6837a8f6a94e659f5fa7dce6a1076279336320f2b/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%!F(MISSING)20240315%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240315T063326Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=d14a2deeadcc4f625c71535f456b49a6f8915521ddc7352f2f81aa0f4635bb47": net/http: TLS handshake timeout

### How should we solve this?

Wouldn't it be possible to add a feature disabling or setting a higher number of retries for the user? 


### What is the impact of not solving this?

I understand most people have fast internet, but with my max 500 Kb/s (hopefully cable internet is on the way) all models are a pain. Mistral I can babysit through the download since it takes a couple of hours, but I can't babysit and relaunch Mixtral over 2 days...

### Anything else?

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: feature that would allow for the storage/reuse of frequently/recently used prompts within the prompt/negative prompt fields.
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 ?

**recently used prompts to be stored** in some form of a _scrollable format_ (such as, google search recent example attached below), so that when a user wants to continue modifying the same prompts or add certain tweaks without losing the prompt altogether when we close the `webui.bat` file. I personally maintain a separate text file for all my prompts which is quite tedious. 
the main proposal is just adding a scrollable recent prompts section which will appear below the prompts input field when we click on the `prompts/negative prompt` input field. I would like to assist in implementation of this feature. This enhancement would greatly benefit users who regularly utilize these functions.

### Proposed workflow

1. Go to webui.bat
2.  once webui loads 
3. click on the prompt/negative prompt
4. a scrollable list of all the previously used/most used prompts appear
5. user can choose which prompt from the previously used/mostly used prompt is relevant according to his present needs.


### Additional information

![Screenshot 2024-03-15 115219](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/113274453/ef1693b3-6f0d-4b87-9d42-3764dbd3c8a0)
Repository: vscode
Issue: settings files.exclude does not recognize .vscode folder
Labels: bug,config,confirmation-pending

Type: <b>Bug</b>

- open project/.vscode/settings.json in a separate text editor
- add this setting  "files.exclude": { "\*.\*": true, ".vscode": true, "dist": false, node_modules":true }
- .vscode and node_modules will be hidden in exporer, dist will be visible
- change setting to  "files.exclude": { "\*.\*": true, ".vscode": false, "dist": false, node_modules":true }
- .vscode will still be hidden in explorer

Removing the "\*.\*": true entry mitigates the issue, so it seems like the search pattern \*.\* is greedily including folders with the '.' prefix?


VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz (4 x 3100)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: unavailable_off<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: unavailable_off<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.93GB (7.91GB free)|
|Process Argv|--crash-reporter-id 13072b5e-4a26-43e2-b55d-5eb7771846ef|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30986170
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:30979542
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30958157
dsvsc020:30976470
666c4381:30973075
gee8j676:30988843

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: `derive` generates incorrect bounds for associated types
Labels: A-macros,T-compiler,C-bug,S-has-mcve

I think there's a bug causing incorrect `derive` behaviour for a field whose type is an associated type extracted from a generic parameter.

```rust
trait AssociatedWithDefaultable {
    type Defaultable: Default;  // (1) `Defaultable` implements `Default`.
}

// (2) Expectation: `StoreAssociatedDefaultable` implements `Default` due to (3).
#[derive(Default)]
struct StoreAssociatedDefaultable<AWC: AssociatedWithDefaultable> {
    defaultable: AWC::Defaultable,  // (3) `Defaultable` implements `Default` due to (1).
}

fn get_default<A: AssociatedWithDefaultable>() -> StoreAssociatedDefaultable<A> {
    Default::default()
}
```

```plaintext
error[E0277]: the trait bound `A: Default` is not satisfied
  --> src/main.rs:12:5
   |
12 |     Default::default()
   |     ^^^^^^^^^^^^^^^^^^ the trait `Default` is not implemented for `A`, which is required by `StoreAssociatedDefaultable<A>: Default`
   |
note: required for `StoreAssociatedDefaultable<A>` to implement `Default`
  --> src/main.rs:6:10
   |
6  | #[derive(Default)]
   |          ^^^^^^^ unsatisfied trait bound introduced in this `derive` macro
   = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider further restricting this bound
   |
11 | fn get_default<A: AssociatedWithDefaultable + std::default::Default>() -> StoreAssociatedDefaultable<A> {
   |                                             +++++++++++++++++++++++


```

The macro expansion makes the problem clearer.

```rust
struct StoreAssociatedDefaultable<AWC: AssociatedWithDefaultable> {
    defaultable: AWC::Defaultable,
}
#[automatically_derived]
impl<AWC: ::core::default::Default + AssociatedWithDefaultable> ::core::default::Default
//        ^^^^^^^^^^^^^^^^^^^^^^^^ incorrect
for StoreAssociatedDefaultable<AWC>
where
    AWC::Defaultable: ::core::default::Default,
//                    ^^^^^^^^^^^^^^^^^^^^^^^^ correct but unnecessary
{
    #[inline]
    fn default() -> StoreAssociatedDefaultable<AWC> {
        StoreAssociatedDefaultable {
            defaultable: ::core::default::Default::default(),
        }
    }
}
```

It seems to confuse the associated type with the generic that carries it, causing it to add the bound  `AWC: ::core::default::Default` unexpectedly.

It also adds `AWC::Defaultable: ::core::default::Default`, which is consistent but superfluous.


[Link to playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=7659f9d8c7fdbd3589e5156a747a2304)

```
> rustc --version --verbose
rustc 1.78.0-nightly (3246e7951 2024-02-19)
binary: rustc
commit-hash: 3246e79513cb89ddbfc0f21cb5a877e5b321dcc5
commit-date: 2024-02-19
host: aarch64-apple-darwin
release: 1.78.0-nightly
LLVM version: 18.1.0
```
Repository: rust
Issue: Tracking Issue for perma-unstable `wasm-c-abi` flag
Labels: C-tracking-issue

This is a tracking issue for the MCP "perma-unstable `wasm-c-abi` flag" (https://github.com/rust-lang/compiler-team/issues/703).

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the MCP (cc @rust-lang/compiler -- can anyone write up mentoring
      instructions?)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- ~~Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])~~
- ~~Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])~~

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Implementation history

- https://github.com/rust-lang/rust/pull/117919
- https://github.com/rust-lang/rust/pull/117918

### Related issues
- https://github.com/rust-lang/rust/issues/115666
Repository: ui
Issue: Preventing overlay of sheet component
Labels: bug

### Describe the bug

Hi guys, I am building a drag and drop functionality. So normally, as you can see in the first example, when the blue card is dragged to the waiting list, it will be added to the list since the drag recognizes that it has been dragged to the list. However, when I use the sheet component, it doesn't work because it can't recognize that there is a sheet since it's an overlay. I even tried to remove the z-index from the list and give a higher one to the blue card, but that's not working. Can somebody help?

### Affected component/components

Sheet

### How to reproduce


https://github.com/shadcn-ui/ui/assets/137432044/80c96730-f447-42b1-b7a2-f562fc1d855f



### Codesandbox/StackBlitz link

.

### Logs

```bash
.
```


### System Info

```bash
.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Numerical error when using torch.nn.functional.pad with a large array on MPS device
Labels: module: nn,triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

When padding a long array that is on a MPS device there seems to be an error for long array as reported in https://github.com/Lightning-AI/torchmetrics/issues/1727

This is a minimal snippet to reproduce:
```python
import torch
import torch.nn.functional as F

vec_cpu = F.pad(torch.arange(2**15, device="cpu"), [0, 1], value=2)
print(vec_cpu)
# tensor([    0,     1,     2,  ..., 32766, 32767,     2])

vec_mps = F.pad(torch.arange(2**15, device="mps"), [0, 1], value=2)
print(vec_mps)
# tensor([    0,     1,     2,  ..., 32766, 32767,     2], device='mps:0')

vec_cpu_large = F.pad(torch.arange(2**17, device="cpu"), [0, 1], value=2)
print(vec_cpu_large)
# tensor([     0,      1,      2,  ..., 131070, 131071,      2])

vec_mps_large = F.pad(torch.arange(2**17, device="mps"), [0, 1], value=2)
print(vec_mps_large)
# tensor([2, 0, 0,  ..., 0, 0, 0], device='mps:0')
```

I tried on `torch==2.1.1` and `2.2.1` as well and could reproduce the error with both versions.

### Versions

PyTorch version: 2.1.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.4 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.3.9.4)
CMake version: Could not collect
Libc version: N/A

Python version: 3.10.13 (main, Mar  4 2024, 14:06:47) [Clang 15.0.0 (clang-1500.1.0.2.5)] (64-bit runtime)
Python platform: macOS-14.4-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M3 Pro

Versions of relevant libraries:
[pip3] flake8==7.0.0
[pip3] hs-infrastructure-flake8-plugins==0.2.0
[pip3] mypy==1.9.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] onnx==1.15.0
[pip3] onnxruntime==1.17.1
[pip3] pytorch-ranger==0.1.1
[pip3] torch==2.1.1
[pip3] torch-optimizer==0.3.0
[pip3] torchaudio==2.1.1
[pip3] torchmetrics==1.0.3
[pip3] torchvision==0.16.1
[conda] Could not collect

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @kulinseth @malfet @DenisVieriu97 @jhavukainen @razarmehr