sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Diagnostic does not fire on marker trait that requires static
Labels: A-diagnostics,T-compiler,D-diagnostic-infra

### Code

```rust
#[diagnostic::on_unimplemented(
    message = "Arguments to embassy tasks must be 'static",
    label = "Not 'static",
    note = "See https://embassy.dev/... for more details on sharing",
)]
trait SecretStatic {
}

// // Option A
impl<T: 'static> SecretStatic for T {
    
}
// //

// Option B
// impl SecretStatic for i8
// {
// }

// impl SecretStatic for u16
// {
// }

// impl SecretStatic for u32
// {
// }
//

fn expanded_func<T, U, V>(t: T, u: U, v: V)
where
    T: SecretStatic,
    U: SecretStatic,
    V: SecretStatic,
{
    todo!()
}

struct Example {
    x: u32,
}

fn main() {
    expanded_func(1i8, 2u16, 3u32);
    let x = Example { x: 123 };
    expanded_func::<&Example, u16, u32>(&x, 2u16, 3u32);
}
```

### Current output

```
error[E0597]: `x` does not live long enough
  --> src/main.rs:45:41
   |
44 |     let x = Example { x: 123 };
   |         - binding `x` declared here
45 |     expanded_func::<&Example, u16, u32>(&x, 2u16, 3u32);
   |     ------------------------------------^^-------------
   |     |                                   |
   |     |                                   borrowed value does not live long enough
   |     argument requires that `x` is borrowed for `'static`
46 | }
   | - `x` dropped here while still borrowed

For more information about this error, try `rustc --explain E0597`.
```

### Desired output

```
error[E0277]: Arguments to embassy tasks must be 'static
  --> src/main.rs:45:21
   |
45 |     expanded_func::<&Example, u16, u32>(&x, 2u16, 3u32);
   |                     ^^^^^^^^ Not 'static
   |
   = help: the trait `SecretStatic` is not implemented for `&Example`
   = note: See https://embassy.dev/... for more details on sharing
   = help: the following other types implement trait `SecretStatic`:
             i8
             u16
             u32
note: required by a bound in `expanded_func`
  --> src/main.rs:31:8
   |
29 | fn expanded_func<T, U, V>(t: T, u: U, v: V)
   |    ------------- required by a bound in this function
30 | where
31 |     T: SecretStatic,
   |        ^^^^^^^^^^^^ required by this bound in `expanded_func`
```

### Rationale and extra context

We want to use a marker trait in macro expanded code for the embassy executor so that all arguments to tasks are 'static. This is a limitation of the executor, and is a common stumbling block for users.

We wanted to use diagnostics for this to reduce the amount of work required in a proc macro to get good spans and errors, but noticed that diagnostics did not fire at all. They DO fire when we manually add impls for the type instead of using a blanket impl (this is not practical to support for arbitrary user types

### Other cases

_No response_

### Rust Version

Tested with 1.81.0 stable and 1.82.0-beta.6, same output

### Anything else?

_No response_
Repository: Python
Issue: Adding Elliptic Curve Cryptography in Blockchain Directory
Labels: enhancement

### Feature description

## Objective:
Add a Python module named elliptic_curve_cryptography.py to the Blockchain directory, implementing the core principles of Elliptic Curve Cryptography (ECC) for securing blockchain transactions.

## Details:

- The module will include functions for generating ECC key pairs (public and private keys).
- It will demonstrate how ECC can be used to sign and verify transactions within the blockchain.
- Provide examples of using ECC for encryption and decryption processes.
- Ensure compatibility with other cryptographic mechanisms already present in the blockchain project.

## Benefits:

- Strengthens the security of blockchain transactions using lightweight cryptography.
- Enhances the ability to integrate with other blockchain features like digital signatures and smart contracts.
- This feature will help optimize security with less computational overhead compared to other cryptographic methods.


Can you assign it to me under the `hacktoberfest-accepted` label?
I would like to work on this any many other blockchain related techs which I know about!
Repository: material-ui
Issue: Grid component not working for JoyUI
Labels: on hold,component: Grid,package: joy-ui

### Steps to reproduce

Link to live example: (required)
https://codesandbox.io/embed/f4kt4q?module=/src/Demo.tsx&fontsize=12

Steps:
1. Go to https://mui.com/joy-ui/react-grid/#basics
2. Open the code in CodeSandbox: https://cloud.pivonka.io/BbCvPyXM
3. See the Grid not working for JoyUI


### Current behavior

The Grid is not working as expected for the JoyUI. The Grid component adds only padding around each child grid component, without any other sizing.

### Expected behavior

JoyUIs Grid component should work like the MaterialUI component does, i.e. here: https://codesandbox.io/embed/9xswhw?module=/src/Demo.tsx&fontsize=12

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: Linux 6.10 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
Binaries:
    Node: 22.9.0 - /usr/local/bin/node
    npm: 10.8.3 - /usr/local/bin/npm
    pnpm: Not Found
Browsers:
    Chrome: Not Found
npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3 
    @emotion/styled: ^11.13.0 => 11.13.0 
    @mui/base:  5.0.0-beta.40 
    @mui/core-downloads-tracker:  5.16.7 
    @mui/icons-material: ^6.1.0 => 6.1.2 
    @mui/joy: 5.0.0-beta.48 
    @mui/material: ^5.3.1 => 5.16.7 
    @mui/material-nextjs: ^6.1.0 => 6.1.2 
    @mui/private-theming:  5.16.6 
    @mui/styled-engine:  5.16.6 
    @mui/system:  5.16.7 
    @mui/types:  7.2.17 
    @mui/utils:  5.16.6 
    @types/react: ^18.3.5 => 18.3.5 
    react: ^18.3.1 => 18.3.1 
    react-dom: ^18.3.1 => 18.3.1 
    typescript: ^5.1.6 => 5.1.6 
```
</details>


**Search keywords**: grid, joy
Repository: vscode
Issue: Folders in explorer disappear when clicked
Labels: bug,file-explorer


Type: <b>Bug</b>

1. Clone FRRouting master branch: https://github.com/FRRouting/frr (d1433ee9a8fa374ee653dcf1fe6e852481b17119)

2. Try to open directories like bgpd, bfdd etc.

VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Darwin arm64 24.0.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M1 Max (10 x 2400)|
|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>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|3, 5, 5|
|Memory (System)|32.00GB (1.17GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (34)</summary>

Extension|Author (truncated)|Version
---|---|---
markdown-preview-github-styles|bie|2.1.0
ruff|cha|2024.50.0
gitlens|eam|15.6.0
EditorConfig|Edi|0.16.4
prettier-vscode|esb|11.0.0
dependi|fil|0.7.10
remotehub|Git|0.64.0
vscode-github-actions|git|0.27.0
vscode-pull-request-github|Git|0.98.0
go|gol|0.42.1
fluent-icons|mig|0.0.18
symbols|mig|0.0.20
vscode-docker|ms-|1.29.3
debugpy|ms-|2024.10.0
python|ms-|2024.16.1
vscode-pylance|ms-|2024.10.1
jupyter|ms-|2024.9.1
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.19
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-containers|ms-|0.388.0
remote-ssh|ms-|0.115.0
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.4
vscode-remote-extensionpack|ms-|0.25.0
azure-repos|ms-|0.40.0
live-server|ms-|0.4.15
remote-explorer|ms-|0.4.3
remote-repositories|ms-|0.42.0
remote-server|ms-|1.5.2
rust-analyzer|rus|0.3.2146
jinjahtml|sam|0.20.0
even-better-toml|tam|0.19.2

(1 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: three.js
Issue: MaterialX: TextureNode does not have nodeType set
Labels: Nodes

### Description

When using the MaterialXLoader with TiledImage MaterialX nodes, three creates TextureNodes, however I do not see the output type of the TiledImage as the nodeType of the TextureNode as I'd expect. Typically there is a ConvertNode parenting the TextureNode with the correct type, however I've encountered a situation where the TextureNode is parented by a MathNode in which in1 has type color3 but the TextureNode should export a float type, here it's impossible to know which type should be used. This is an issue when exporting three nodes

### Solution

When reading the tiledImage node from the MaterialX file, put the output type as the nodeType on the TextureNode

### Alternatives

If there is some reason for this, or if I'm totally missing where this type can be found, please let me know!

### Additional context

StackBlitz : https://stackblitz.com/edit/three-mtlx-ptdcen?file=main.js,mtlx%2Fbrick.mtlx&terminal=dev

![Screenshot 2024-10-14 at 11 57 32](https://github.com/user-attachments/assets/e875bad9-0c88-4b98-8a9f-b581bab5fbcf)


_No response_
Repository: PowerToys
Issue: Hosts File Editor: when deleting an entry, the editor should not jump to the top of the screen (e.g. scroll up automatically), but remember its context
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Hosts File Editor

### Steps to reproduce

Scroll down Delete an entry a couple of screens down and delete the entry.

### ✔️ Expected Behavior

Edit stays in the same (scrolled down) position.

Usage case for the expected behaviour: 
If you want to delete multiple entries, it is very cumbersome to (once you are scrolled down to the section that contains the deletion candidates), to scroll down after every deletion, and finding the location that you were at. 

### ❌ Actual Behavior

Editor jumps / scrolls to the top of the screen.

### Other Software

_No response_
Repository: godot
Issue: Some meshes in scene file do not get updated when changing source file - other meshes do
Labels: bug,topic:editor,needs testing,topic:import

### Tested versions

- Reproducable in Godot v4.3.stable.official [77dcf97d8]

### System information

Windows 11 - Godot v4.3.stable.official

### Issue description

Godot is not updating prefabs correctly.
The intended update architecture is:
.blend (raw meshes) -> .tscn (set up scene) -> .tscn (scene variant)

When editing a bodyshape of a 3d model the set up scene updates and SOME of the scene variants. Some just keep the old mesh shape.
I even tried to add a cube to the blendfile which appeared in ALL the scenes. The bodyshape however was still only updated in some scenes.

<img width="707" alt="godot_prefab_problem" src="https://github.com/user-attachments/assets/8cbe8c4d-76aa-4501-abf4-3388121a8665">


### Steps to reproduce

There are files for a giraffe and a racoon with different variants.
The racoon should have a clearer half-moon-shaped head.
The giraffe should have a thicker tongue.

The screenshot shows the folder structure and the variants that do get updated an the ones that don't.
Updating other objects like accessoires works however. It seems to be the body object only.

![godot_prefab_problem_folder_structure](https://github.com/user-attachments/assets/73ff0ed0-57d2-4a6b-9033-d0ae96311427)


### Minimal reproduction project (MRP)

[prefab_bug_project.zip](https://github.com/user-attachments/files/17365371/prefab_bug_project.zip)
Repository: flutter
Issue: regression in worst frame raster time on iOS for tiles_scroll_perf_ios__timeline_summary
Labels: P2,team-engine,triaged-engine

On the engine roll here https://github.com/flutter/engine/compare/20369c5d2b93...66d397dff87a

https://flutter-flutter-perf.skia.org/e/?begin=1726190651&end=1728888985&keys=X84a0007b39fb2fa1be1fc8a84f115bd1&requestType=0&selected=commit%3D42806%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Dworst_frame_rasterizer_time_millis%252Ctest%253Dtiles_scroll_perf_ios__timeline_summary%252C&xbaroffset=42806
Repository: godot
Issue: Alpha to coverage doesn't work in Compatibility Renderer
Labels: topic:rendering,documentation,topic:3d

### Tested versions

Tested in Godot 4.3 Stable (arch linux)

### System information

Godot v4.3.stable unknown - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Thu Oct 10 19:03:24 UTC 2024 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3060 (nvidia; 560.35.03) - Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz (6 Threads)

### Issue description

When enabling the alpha anti-aliasing settings in a standard material or custom shader with MSAA enabled, no change shows when in the compatibility renderer, bumping up to the mobile renderer shows proper alpha anti-aliasing with alpha to coverage or alpha to coverage and 1

This is extremely unfortunate as the compatibility renderer is currently preferred for standalone XR use cases (inlcuding webXR) and heavy aliasing caused by alpha test materials is visually distracting and intrusive in VR. 
Ideally the alpha to coverage could be properly supported in the compatibility renderer so that it could be used for these cases. Even better would be to make sure it works for WebXR as well (where performance targets are even tighter and the use of textured alpha planes is vital to making anything that will look good and perform at a decent level)

### Steps to reproduce

enable 4x MSAA for 2d and 3d in project settings
set to compatibility renderer
create multiple intersecting planes with a material with transparency as such 
![image](https://github.com/user-attachments/assets/2b6caee0-1426-4678-bda1-6fb253985b9f)
set editor to half resolution to better see anti-aliasing effects
notice that there is heavy aliasing

switch to mobile renderer
notice aliasing is now solved properly through alpha to coverage

### Minimal reproduction project (MRP)

see above. If you are unable to reproduce I can trim down my project and include here.
Repository: ui
Issue: [bug]:  ⨯ ./node_modules/@tiptap/extension-bullet-list/dist/index.js:3:1 Module not found: Can't resolve '@tiptap/extension-text-style'
Labels: bug

### Describe the bug

I was trying to run the editor and I know well that I installed tiptap very well

### Affected component/components

Button

### How to reproduce

Go to "..."

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Nothing about browsers, everything is going well
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Closing a view while dragging border makes the editor view unresponsive to mouse interaction
Labels: bug,workbench-editor-grid,splitview-widget


Type: <b>Bug</b>

1. Split view
2. While dragging the border between views, press Ctrl+W (closing the current view)

Now VSCode is completely unreactive to mouse interaction in the areas of the two views. Mouse interaction still works in the rest (the sidebar, terminal, top menu).

Curiously, closing more files or opening new files does not fix the issue. Splitting the view makes the new split responsive, but leaves the old split unfixed. 

VS Code version: Code 1.93.1 (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40, 2024-09-11T17:20:05.685Z)
OS version: Linux x64 6.8.0-107045-tuxedo
Modes:

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

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (16 x 4502)|
|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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off<br>webnn: disabled_off|
|Load (avg)|2, 1, 1|
|Memory (System)|60.62GB (47.92GB free)|
|Process Argv|--crash-reporter-id cbeb708d-b159-4344-9cd6-2cc641c7864d|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|wayland|
</details><details><summary>Extensions (24)</summary>

Extension|Author (truncated)|Version
---|---|---
language-x86-64-assembly|13x|3.1.4
copilot|Git|1.238.0
copilot-chat|Git|0.20.3
solidity|Jua|0.0.179
nim|kos|0.6.6
vscoq|max|2.2.1
git-graph|mhu|1.30.0
vscode-docker|ms-|1.29.3
csharp|ms-|2.50.25
vscode-dotnet-runtime|ms-|2.2.0
debugpy|ms-|2024.10.0
python|ms-|2024.14.1
vscode-pylance|ms-|2024.10.1
remote-ssh|ms-|0.115.0
remote-ssh-edit|ms-|0.87.0
cmake-tools|ms-|1.19.52
cpptools|ms-|1.21.6
makefile-tools|ms-|0.11.13
remote-explorer|ms-|0.4.3
vscode-xml|red|0.27.1
swift-lang|ssw|1.11.3
pdf|tom|1.2.2
cmake|twx|0.0.17
vscode-lldb|vad|1.11.0


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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
f3je6385:31013174
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31156134
notype1cf:31157160
5fd0e150:31155592

```

</details>

<!-- generated by issue reporter -->
Repository: electron
Issue: [Bug]: "zoomIn" accelerators do no work on Windows or Linux
Labels: platform/windows,platform/linux,bug :beetle:,status/confirmed,has-repro-gist,32-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

32.2.0

### What operating system(s) are you using?

Windows, Ubuntu

### Operating System Version

Ubuntu 24.04.1, Windows 10 22H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Pressing `Ctrl` plus the key that `+` is on should zoom in just as pressing `Ctrl` plus the key that `-` is on zooms out correctly in the latest version of electron.

### Actual Behavior

Pressing `Ctrl` plus the key that `+` is on does not trigger the zoom in. Currently on `Ctrl` plus `Shift` plus `+` works to trigger zoom in. This is not consistent with the zoom out behavior.

### Testcase Gist URL

https://gist.github.com/jwetzell/5dd9488bc291da575ac3beff1442a641

### Additional Information

The auto-closed issue #40674 has a basic example to reproduce and more thorough detail of the problem.
Repository: vscode
Issue: Custom HISTFILE not being honored
Labels: bug,terminal-shell-zsh

> I believe this has been fixed. Pls let me know if you can still reproduce in a more recent version

_Originally posted by @meganrogge in https://github.com/microsoft/vscode-remote-release/issues/7083#issuecomment-1373878654_

This issue is happening again with VSCode 1.94.0 and Remote - SSH v0.115.0 (I just installed this extension, don't know if it broke recently).

I have my HISTFILE defined in ~/.zshenv and when I connect to the machine via this extension, ~/.zsh_history gets recreated. (XDG_DATA_HOME is also defined in that file and it gets correctly used by the "Server Install Path" settings)

edit: Disabling shell integration in VSCode (as suggested in the original issue) seems to be a workaround for this issue.
Repository: tensorflow
Issue: tf.math.is_strictly_increasing's behavior is not clear on a (2,2) matrix
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.17.0

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When receiving this input:
```
x = tf.constant([[1,2],[2,3]])
```
`tf.math.is_strictly_increasing` outputs `False` instead of `True`.
Also, for a tensor with shape (1,3,3):
```
x = tf.constant([[[-0.3188535,  -1.6029806,  -1.5352179],
  [-0.5704009,  -0.2167283,   0.2548743 ],
  [-0.14944994,  2.0107825,  -0.09678416]]])
```
It's output is still `False` instead of `True` even when x's first dimension only has one element.
Based on the description "Elements of x are compared in row-major order.", it seems that elements in x are compared along row (i.e., the first dimension).
Therefore, to my understanding, if the first dimension contains only one element (such as 1x3x3 shape tensor), the output should be True. If the input is [[1,2],[3,4]], the output should also be `True` since the value in the first dimension is increasing (from `[1,2]` to `[3,4]`)


### Standalone code to reproduce the issue

```shell
import tensorflow as tf
x = tf.constant([[1,2],[2,3]])
print(tf.math.is_strictly_increasing(x))  # False
x = tf.constant([[[-0.3188535,  -1.6029806,  -1.5352179],
  [-0.5704009,  -0.2167283,   0.2548743 ],
  [-0.14944994,  2.0107825,  -0.09678416]]])
print(tf.math.is_strictly_increasing(x))  # False
```
```


### Relevant log output

_No response_