sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Segmentation fault with connected components with large images (37564 x 73862 pxl)
Labels: bug,category: imgproc

### System Information

master: 073c2d9964dcd3bd6316f55571f04e7d00070d37
ubuntu 22.04
gcc 11.4.0

### Detailed description

connected components crashes with segmentation fault for large images (37564 x 73862) and works for small :
```
cv::Mat labelImage(img.size(), CV_32S, (uint8_t) 0 );
cv::Mat u8_image(img.size(), CV_8U, (uint8_t) 0);
int nLabels = cv::connectedComponents(bw, labelImage, 8);
```

visual studio code call stack in debugger when it happens:
```
libopencv_imgproc.so.409!cv::connectedcomponents::LabelingBolelli4CParallel<int, unsigned char, cv::connectedcomponents::NoOp>::FirstScan::operator()(cv::Range const&) const (Unknown Source:0)
libopencv_core.so.409!cv::(anonymous namespace)::ParallelLoopBodyWrapper::operator()(cv::Range const&) const (Unknown Source:0)
libopencv_core.so.409!cv::parallel_for_cb(int, int, void*) (Unknown Source:0)
libopencv_core.so.409!tbb::detail::d1::start_for<tbb::detail::d1::blocked_range<int>, cv::parallel::tbb::ParallelForBackend::CallbackProxy, tbb::detail::d1::auto_partitioner const>::execute(tbb::detail::d1::execution_data&) (Unknown Source:0)
libtbb.so.12![Unknown/Just-In-Time compiled code] (Unknown Source:0)
libc.so.6!start_thread(void * arg) (pthread_create.c:442)
libc.so.6!clone3() (clone3.S:81)
```

Is there some way i can make this work for large images (I'd rather not tile them)?

### Steps to reproduce

see above

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [x] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Cannot read properties of null (reading 'scheme')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of null (reading 'scheme')
at l.from in src/vs/base/common/uri.ts:339:15
at <anonymous> in src/vs/workbench/browser/parts/editor/editorCommands.ts:622:80
at fn in src/vs/platform/instantiation/common/instantiationService.ts:68:11
at k.n in src/vs/workbench/services/commands/common/commandService.ts:95:46
at k.executeCommand in src/vs/workbench/services/commands/common/commandService.ts:60:17
at Tt.sc in src/vs/workbench/contrib/scm/browser/scmViewPane.ts:2856:31
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at ce.j in src/vs/platform/list/browser/listService.ts:778:19
at ce.h in src/vs/platform/list/browser/listService.ts:770:8
at a.value in src/vs/platform/list/browser/listService.ts:706:112
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at a.value in src/vs/base/common/event.ts:118:84
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at a.value in src/vs/base/common/event.ts:152:97
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at a.value in src/vs/base/common/event.ts:118:84
at o.y in src/vs/base/common/event.ts:1127:13
at o.z in src/vs/base/common/event.ts:1138:9
at o.fire in src/vs/base/common/event.ts:1162:9
at a.value in src/vs/base/common/event.ts:118:84
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at HTMLDivElement.y in src/vs/base/browser/event.ts:40:41
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=31c37ee8f63491495ac49e43b8544550fbae4533&bH=8904089c-dd84-3d55-b6f8-3baed0c155a4)
Repository: vscode
Issue: Cannot read properties of null (reading 'isEmpty')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of null (reading 'isEmpty')
at I.readSelectionFromMarkers in src/vs/editor/common/cursor/oneCursor.ts:68:53
at <anonymous> in src/vs/editor/common/cursor/cursorCollection.ts:64:34
at Array.map (<anonymous>)
at v.readSelectionFromMarkers in src/vs/editor/common/cursor/cursorCollection.ts:64:23
at c.onModelContentChanged in src/vs/editor/common/cursor/cursor.ts:258:50
at <anonymous> in src/vs/editor/common/viewModel/viewModelImpl.ts:409:18
at listener in src/vs/editor/common/model/textModel.ts:235:38
at o.y in src/vs/base/common/event.ts:1127:13
at o.fire in src/vs/base/common/event.ts:1158:9
at J.endDeferredEmit in src/vs/editor/common/model/textModel.ts:2504:23
at U.wb in src/vs/editor/common/model/textModel.ts:1404:23
at U._applyUndo in src/vs/editor/common/model/textModel.ts:1377:8
at w.undo in src/vs/editor/common/model/editStack.ts:219:14
at <anonymous> in src/vs/platform/undoRedo/common/undoRedoService.ts:1028:67
at invoke in src/vs/platform/undoRedo/common/undoRedoService.ts:745:13
at <anonymous> in src/vs/platform/undoRedo/common/undoRedoService.ts:1028:16
at callback in src/vs/platform/undoRedo/common/undoRedoService.ts:788:11
at r.x in src/vs/platform/undoRedo/common/undoRedoService.ts:1026:15
at r.A in src/vs/platform/undoRedo/common/undoRedoService.ts:1109:17
at r.undo in src/vs/platform/undoRedo/common/undoRedoService.ts:1076:15
at U.undo in src/vs/editor/common/model/textModel.ts:1550:32
at g.runEditorCommand in src/vs/editor/browser/coreCommands.ts:2101:29
at g._runEditorCommand in src/vs/editor/browser/coreCommands.ts:340:23
at Object.implementation in src/vs/editor/browser/coreCommands.ts:311:17
at s.runCommand in src/vs/editor/browser/editorExtensions.ts:229:24
at handler in src/vs/editor/browser/editorExtensions.ts:155:38
at fn in src/vs/platform/instantiation/common/instantiationService.ts:68:11
at k.n in src/vs/workbench/services/commands/common/commandService.ts:95:46
at k.executeCommand in src/vs/workbench/services/commands/common/commandService.ts:60:17
at x.M in src/vs/platform/keybinding/common/abstractKeybindingService.ts:370:29
at x.J in src/vs/platform/keybinding/common/abstractKeybindingService.ts:225:15
at <anonymous> in src/vs/workbench/services/keybinding/browser/keybindingService.ts:281:38
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=31c37ee8f63491495ac49e43b8544550fbae4533&bH=087e8736-2db5-0696-093e-835233c65f24)
Repository: storybook
Issue: [Bug]: Storybook Public Instance: Sensitive Data Disclosure in Error Messages (ASVS 6.2.1, 7.2.1)
Labels: security

### Describe the bug

Storybook exposes potential security vulnerabilities when deployed publicly due to unsanitized user-controlled input displayed in error messages. This violates ASVS recommendations 6.2.1 and 7.2.1 concerning information disclosure and input sanitization.

**Impact:**

- Attackers exploiting this vulnerability could:
   - Identify potential vulnerabilities based on error messages revealing internal implementation details.
   - Craft phishing attacks by injecting malicious content into error messages displayed to users.
- This poses a significant security risk, exposing confidential information and potentially undermining user trust.

**Steps to Reproduce:**

1. Access a publicly hosted Storybook instance.
2. Enter arbitrary text (e.g., sensitive information, malicious script) as part of the URL query string.
3. Trigger an error (e.g., incorrect URL path, invalid data).
4. Observe the unsanitized input displayed within the error message.

**Expected Behavior:**

- Error messages should not contain any user-controlled input to mitigate information disclosure and prevent potential phishing attacks.

**Proposed Solution:**

1. **Built-in sanitization:** Implement robust input sanitization mechanisms within Storybook to securely handle user-controlled data displayed in error messages. This ensures compliance with ASVS recommendations and protects sensitive information.
2. **Configuration options**: Offer configurable options for developers to:
   - Define a whitelist of permissible characters for URL parameters.
   - Implement custom sanitization functions based on their specific security requirements.
   
**Alternatively:**

- Provide clear documentation and best practices for secure error handling in publicly deployed Storybook instances.
- Guide developers on custom error page implementations with proper input sanitization.

**Additional Notes:**

- Address the complexity and maintainability concerns raised in the original report regarding modifying Storybook's source code.
- Offer to collaborate with the Storybook team to find an effective solution that addresses these security vulnerabilities.

**References:**

- ASVS Requirement 6.2.1
- ASVS Requirement 7.2.1

**Screenshot:**
![image](https://github.com/storybookjs/storybook/assets/42003122/2da22c79-b6b7-4a77-86ff-1f272223716f)


### To Reproduce

https://master--5ccbc373887ca40020446347.chromatic.com/iframe.html?args=&id=main%27.%0APlease%20report%20it%20to%20www.MyWebSideErrors.com%0A%0APHISHING+TEXT%0D

### System

```bash
all the environments
```


### Additional context

Text Injection (facilitates phishing) (ASVS: 6.2.1; 7.2.1)
Repository: godot
Issue: Can't undo changes made with preview sun and environment in a 3d scene
Labels: bug,enhancement,topic:editor,usability,topic:3d

### Tested versions

- Reproducible in 4.2.stable

### System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Ti Laptop GPU (NVIDIA; 31.0.15.3645) - 12th Gen Intel(R) Core(TM) i9-12900H (20 Threads)

### Issue description

Ctrl+z won't work when colors or other float properties are change in preview sun and preview environment windows. This would be a big inconvenience for an environment artist uses it to test it. Color pickers could be the one of the features where undoing and redoing used a lot.

### Steps to reproduce

- Open a 3d scene
- Open preview window by clicking to three dots next to Transform button
- Change any color 
- Use undo shortcut (ctrl+z) and it won't recover the previous color or check History tab where changes are not added

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Activitybar border missing in Light HC theme
Labels: themes,accessibility

The 2px wide blue border for the active View is missing in the Light HC theme.

<img width="66" alt="image" src="https://github.com/microsoft/vscode/assets/103326/435b0c11-25fe-433f-9cf7-ca36ccb721a7">
Repository: PowerToys
Issue: Remapping bluetooth headphone buttons cause win, shift, ctrl etc keys to stick / lock
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

1. Remap Play/Pause Media key to Win + R (Run shortcut)
2. Click the button on BT headset to trigger Play/Pause. It will successfully execute the shortcut and Run dialog will appear.
3. Now the Win key is stuck, pressing E will trigger Win + E and launch explorer. The Win key will remain locked/stuck till the Win key is pressed on keyboard. 

I have verified this behaviour on two different machines on both run as admin and user mode and this is happening on both.

### ✔️ Expected Behavior

On Play/Pause event just the Run dialog should appear and then pressing any key on keyboard should work.

### ❌ Actual Behavior

Win key got stuck/locked and now pressing any key on keyboard will trigger combo Win + The Pressed Key (Ex. Pressing E will trigger Win + E and will launch the explorer)

### Other Software

_No response_
Repository: next.js
Issue: [NextJS 14.1.0] TypeError: Cannot read properties of undefined (reading 'call')
Labels: bug,Navigation,Lazy Loading,Runtime,Pages Router,Module Resolution

### Link to the code that reproduces this issue

https://github.com/dashawk/nextjs-14-bugger

### To Reproduce

- Clone the provided repository
- Run `yarn install && yarn dev`
- Browse to [http://localhost:3000](http://localhost:3000)

### Current vs. Expected behavior

After doing all the reproduction steps, you will see the **error**. As you can see, I have already applied the suggested fix for `canary@14.1.1-canary.51`
![image](https://github.com/vercel/next.js/assets/1437205/43964f5f-19cc-4ed0-8f2c-f9601845490a)


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Data fetching (gS(S)P, getInitialProps), Dynamic imports (next/dynamic), Metadata (metadata, generateMetadata, next/head), Middleware / Edge (API routes, runtime), Module resolution (CJS / ESM, module resolving), Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I have encountered this issue only in NextJS@14.1.0 which is giving me a headache.

_

> Upgrading might not be a very good habit.

_
Repository: react-native
Issue: eslint-config/eslint-plugin: Support "Flat Config" (ESLint 9)
Labels: Good first issue,Help Wanted :octocat:,Never gets stale

### Description

👋 Coming over from https://github.com/eslint/eslint/issues/18093: ESLint is migrating to a [new "flat config" format](https://eslint.org/docs/latest/use/configure/configuration-files-new) that will be the default in ESLint v9.

It doesn't look like `@react-native-community/eslint-plugin` has support yet. I'm posting this issue here as a reference & cross-linking it to the table in https://github.com/eslint/eslint/issues/18093. If there's anything technical blocking the extension from supporting flat configs, please let us know - we'd be happy to try to help! 💜 

Additional resources:
* [Configuration Migration Guide](https://eslint.org/docs/latest/use/configure/migration-guide)
* _(edit)_ [Plugin Migration Guide](https://eslint.org/docs/latest/extend/plugin-migration-flat-config)
* Blog posts on the new config system: [Part 1: Background](https://eslint.org/blog/2022/08/new-config-system-part-1), [Part 2: Introduction to flat config](https://eslint.org/blog/2022/08/new-config-system-part-2)

_(sorry for not using the issue template properly - I wasn't sure how best to report this)_

### Steps to reproduce

1. Have an `eslint.config.js` (flat config)
2. See setup instructions https://www.npmjs.com/package/@react-native-community/eslint-plugin
3. Note the missing mention of flat config

### React Native Version

n/a

### Affected Platforms

Other (please specify)

### Output of `npx react-native info`

```text
n/a
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

n/a

### Screenshots and Videos

_No response_
Repository: PowerToys
Issue: Host file editor: consider commented lines
Labels: Idea-Enhancement,Needs-Triage,Product-Hosts File Editor

### Description of the new feature / enhancement

as of now, if I have

```
1.2.3.4 myhost.mylan.com
# 5.6.7.8 myhost.mylan.com
```

the host file editor will consider both entries valid and alert me of duplicated entry:
![image](https://github.com/microsoft/PowerToys/assets/2546966/c108b387-15de-4c9a-96f7-4bb082b7d83c)

I think that taking into account commented lines (at least ignoring them like they are in practice) or even better considering comments as such would be interesting.

### Scenario when this would be used?

leaving ready made lines in hosts file

### Supporting information

_No response_
Repository: ollama
Issue: Request to add  leo-hessianai to ollama
Labels: help wanted

Hi guys, 
I tried to use the leo-hessianai-7B model on Ollama. I use the GGUF file (Q4_K_M.gguf from here https://huggingface.co/TheBloke/leo-hessianai-7B-GGUF/tree/main) and followed the instructions from Ollama (https://github.com/ollama/ollama/blob/main/docs/import.md). I already managed to generate answers with the model, but they are extremely wrong and hallucinating (you can say crazy). Unfortunately, I don't know what I'm doing wrong. I assume that the parameters or the template (in the Modelfile you have to create for Ollama) are incorrect.
Hope you can help me out 🙂

I tried the following Modelfiles:

```
FROM ./leo-hessianai-7b.Q4_K_M.gguf
TEMPLATE """{{- if .System }}

system {{ .System }}

{{- end }}

user
{{ .Prompt }}


assistant
"""

SYSTEM """"""

PARAMETER stop 

PARAMETER stop 

```

```
FROM ./leo-hessianai-7b.Q4_K_M.gguf
TEMPLATE "
 {{ .Prompt }} 
"
```

(The same problem occurred when I used the safetensors from this repo and used the ollama tools to convert and quantize the model.)

--> So it would be great if `leo-hessianai-7B`, `leo-hessianai-13B`, and `leo-hessianai-70B` could be added to ollama - find the models at https://huggingface.co/LeoLM
Repository: angular
Issue: `valueChanges` is slow to initiate
Labels: area: forms

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

When working with controls, `valueChanges` stream is initially `null`. That goes kind of against the RxJS paradigm. When working with streams you expect to code regardless of time of execution and streams are specifically there to fix situation where you are dependent on value that is not there for the time being. 

What makes it worse is it works differently for `ngModel` and `formControl`. Consider this directive:
```ts
@Directive({
  standalone: true,
  selector: '[valueChanges]',
})
export class ValueChangesDirective {
  private readonly control = inject(NgControl);

  @Output()
  readonly valueChanges = defer(() => this.control.valueChanges!);
}
```
By the time somebody subscribes to `(valueChanges)` output in the template, `ngModel` versions is ready, while `FormControl` version is not. This makes it impossible to reliably chain control value changes to directive outputs.

I realize these streams are recreated in `ngOnChanges` because `FormControl` is passed as input, rather than created internally as in `ngModel`, but it would be nice if those streams would exist since the beginning as subjects and controls would feed values to them, instead of recreating them.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/value-changes-issue

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular 17
```


### Anything else?

_No response_
Repository: vscode
Issue: Diff Editor: Hide Renames
Labels: feature-request,diff-editor

This would make https://github.com/microsoft/vscode/pull/205019 reviewable.

The idea would be to find consistent word-renames and skip them.
Repository: pytorch
Issue: 17 Dynamo test are failing with "Failed running call_function <function embedding_bag at 0xDEADBEEF".
Labels: low priority,triaged,oncall: pt2,module: dynamo

17 Dynamo test are failing with "Failed running call_function <function embedding_bag at 0xDEADBEEF".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest nn/test_embedding.py -v -k test_embedding_bag_device_cpu_int32_int32_bfloat16`

You will need to remove the skip or expectedFailure before running the repro command.
This may be just removing a line in
[dynamo_test_failures.py](https://github.com/pytorch/pytorch/blob/main/torch/testing/_internal/dynamo_test_failures.py)

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int32_bfloat16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int32_float16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int32_float32
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int32_float64
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int64_bfloat16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int64_float16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int64_float32
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int32_int64_float64
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int32_bfloat16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int32_float16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int32_float32
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int32_float64
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int64_bfloat16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int64_float16
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int64_float32
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_device_cpu_int64_int64_float64
nn/test_embedding.py::TestEmbeddingNNDeviceTypeCPU.test_embedding_bag_dimension_errors_cpu
```
</details>

cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov
Repository: pytorch
Issue: 10 Dynamo test are failing with "GetAttrVariable(NumpyVariable(), __name__) is not a constant". 
Labels: low priority,triaged,oncall: pt2,module: dynamo

10 Dynamo test are failing with "GetAttrVariable(NumpyVariable(), __name__) is not a constant".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest torch_np/numpy_tests/core/test_numerictypes.py -v -k test_names_reflect_attributes_t0`

You will need to remove the skip or expectedFailure before running the repro command.
This may be just removing a line in
[dynamo_test_failures.py](https://github.com/pytorch/pytorch/blob/main/torch/testing/_internal/dynamo_test_failures.py)

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t0
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t1
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t2
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t3
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t4
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t5
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t6
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t7
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t8
torch_np/numpy_tests/core/test_numerictypes.py::TestScalarTypeNames.test_names_reflect_attributes_t9
```
</details>


cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov