sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: TypeError: Error.stack getter called with an invalid receiver, js engine: hermes
Labels: Needs: Triage :mag:

### Description

After upgrading the version of react native to 0.17.3 whenever I moved through the tap navigation the following error message shown.

![Screenshot 2024-03-24 194437](https://github.com/facebook/react-native/assets/138590130/08bb327a-afe9-4403-a670-14587ab500b3)

In the Visual Studio Code the following path contains the code 
node_modules\react-native\Libraries\promiseRejectionTrackingOptions.js

![Screenshot 2024-03-24 194636](https://github.com/facebook/react-native/assets/138590130/8aa418aa-41dd-4b3b-ae48-91ea5978fb8c)


After replacing the rejection. stack with the rejection of all work fine.


### Steps to reproduce

1. Upgrade the existing React native version to 0.73.6.
2. Run the application.
3. Everything works fine but when the screen.

### React Native Version

0.73.6

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: Windows 11 10.0.22631
  CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
  Memory: 6.78 GB / 15.88 GB
Binaries:
  Node:
    version: 18.17.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 1.22.19
    path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
  npm:
    version: 9.6.7
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-231.9392.1.2311.11330709
  Visual Studio:
    - 17.8.34322.80 (Visual Studio Community 2022)
Languages:
  Java:
    version: 17.0.10
    path: C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
TypeError: Error.stack getter called with an invalid receiver, js engine: hermes
```


### Reproducer

https://github.com/MTalhaAC/EnlightenAppv0.0.1

### Screenshots and Videos

![Screenshot 2024-03-24 194437](https://github.com/facebook/react-native/assets/138590130/96878e10-4c44-4e89-afa1-b7f1d4297ca4)
![Screenshot 2024-03-24 194636](https://github.com/facebook/react-native/assets/138590130/e685cbb7-6435-4bd5-9487-af29669f488e)
Repository: deno
Issue: Bug: ESM module in `@stencil/core` incorrectly detected as CJS
Labels: triage required 👀

Steps to reproduce:

1. Run this snippet:
  ```ts
  import Bookmarks from "npm:@arcgis/core@4.29/widgets/Bookmarks.js";
  console.log(Bookmarks);
```

Error:

```sh
error: 'import', and 'export' cannot be used outside of module code at file:///Users/marvinhagemeister/Library/Caches/deno/npm/registry.npmjs.org/@stencil/core/4.9.0/internal/client/index.js:24:1

  import { BUILD, NAMESPACE } from '@stencil/core/internal/app-data';
  ~~~~~~
```

Version: Deno 1.41.3
Repository: java-design-patterns
Issue: Timeout pattern
Labels: epic: pattern,type: feature

**Description:**
The Timeout design pattern is crucial in a microservices architecture to handle latency and prevent cascading failures. By setting a timeout, we can avoid long waits for responses from dependent services, improving overall system resilience and performance. This pattern helps in defining a period within which a service call must complete, otherwise, it gets aborted and a fallback mechanism is triggered. This implementation is particularly important for maintaining the robustness of the system under heavy load or when some services are down or slow to respond.

**Main Elements of the Pattern:**
- **Timeout Duration:** Defines the maximum time a service call is allowed to take.
- **Fallback Mechanism:** Provides a default response or alternative workflow if a service call times out.
- **Configuration:** Ability to configure different timeouts for different services based on their response times.
- **Logging and Monitoring:** Capture timeout events for monitoring and debugging purposes.
- **Circuit Breaker Integration:** Work in conjunction with the Circuit Breaker pattern to prevent repeated calls to failing services.

**References:**
1. [Microservices Patterns](https://microservices.io/patterns/reliability/timeout.html)
2. [Resilience4j - TimeLimiter](https://resilience4j.readme.io/docs/timelimiter)
3. [Project Contribution Guidelines](https://github.com/iluwatar/java-design-patterns/wiki)
4. [Timeout pattern](https://www.vinsguru.com/timeout-pattern/)

**Acceptance Criteria:**
- Implement a configurable timeout for service calls.
- Provide a fallback mechanism for timed-out calls.
- Ensure the timeout duration can be configured per service.
- Log timeout events for further analysis and monitoring.
- Demonstrate the pattern with a practical example within the existing microservices.
- Ensure the implementation follows the project's contribution guidelines and coding standards.
Repository: java-design-patterns
Issue: Implement Fallback design pattern
Labels: epic: pattern,type: feature

**Description:**
The Fallback design pattern is a resiliency pattern used in microservices architecture to handle failures gracefully. It ensures that when a service is unavailable or fails, the system can continue to operate by providing an alternative response or executing a predefined fallback mechanism. This pattern enhances the robustness and reliability of microservices by preventing cascading failures and improving the overall user experience.

**Main Elements of the Pattern:**
- **Service Degradation:** Provides a simplified version of the service or a cached response to maintain functionality.
- **Fallback Handlers:** Defines alternative methods or responses when the primary service call fails.
- **Circuit Breaker Integration:** Often used in conjunction with the Circuit Breaker pattern to monitor service health and redirect to fallback handlers when necessary.
- **Timeout Management:** Configures timeouts for service calls to ensure quick fallback execution.
- **Resilience and Fault Tolerance:** Enhances the system's ability to withstand failures without significant disruption.

**References:**
1. [Microservices Patterns - Fallback](https://microservices.io/patterns/reliability/fallback.html)
2. [Spring Cloud Netflix - Hystrix Fallback](https://cloud.spring.io/spring-cloud-netflix/multi/multi_spring-cloud-hystrix.html)
3. [Resilient Microservices with Spring Boot and Hystrix](https://dzone.com/articles/spring-boot-microservice-with-hystrix-fallback)
4. [Java Design Patterns - Contribution Guidelines](https://github.com/iluwatar/java-design-patterns/wiki)
5. [Fallback pattern](https://badia-kharroubi.gitbooks.io/microservices-architecture/content/patterns/communication-patterns/fallback-pattern.html)

**Acceptance Criteria:**
1. Implement a Fallback design pattern in the existing microservices architecture.
2. Ensure the primary service call and fallback handlers are properly defined and integrated.
3. Use a Circuit Breaker pattern to monitor the health of the primary service.
4. Configure timeouts for service calls to trigger fallback mechanisms promptly.
5. Provide unit and integration tests to validate the fallback functionality.
6. Document the implementation details and usage instructions in the project’s README file.
Repository: godot
Issue: VSync Mailbox causes 100% GPU usage
Labels: discussion,topic:rendering,documentation,performance

### Tested versions

v4.3.dev5.mono.official [89f70e98d]

### System information

Windows 11 - Vulkan and DirectX 12 - Forward+ and Mobile

### Issue description

The project was having extremely horrible jitter of frames (constantly switching back to old frames randomly, causing disorienting blur and horrible artifacts), so I tried every VSync mode. Mailbox completely fixed the issue I was facing, but instead of using less than 15% of my GPU on other modes, Mailbox mode instantly forces my GPU to 100% regardless of rendering complexity. It will remain at 100% (never dipping lower) until the game is closed.

Note that my horrible rendering issue only appears in Forward+ and Mobile. Vsync Enabled in Compatibility does not have the issue I was facing.

### Steps to reproduce

1. Use VSync Mailbox mode in Forward+ or Mobile rendering mode
2. Presumably render something. In my case, I have a simple grid of lines rendering in 2d.
3. Open Task Manager and view the Performance tab

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: Recompiles and cache_size_limit from detectron2 CycleBatchNormList
Labels: triaged,oncall: pt2,module: dynamo,dynamo-triage-june2024

Running
```
./benchmarks/dynamo/torchbench.py --inference --performance --only detectron2_fcos_r_50_fpn --stats --dynamic-shapes
```
I am seeing
```py
WARNING:torch._dynamo.convert_frame:torch._dynamo hit config.cache_size_limit (8)
   function: 'forward' (/home/jansel/conda/envs/pytorch/lib/python3.11/site-packages/detectron2/layers/batch_norm.py:318)
   last reason: L['self']._pos == 0      
```

The root cause is this class (slightly minified by hand):
```py
class CycleBatchNormList(nn.ModuleList):
    def __init__(self, length: int, bn_class=nn.BatchNorm2d, **kwargs):
        super().__init__([bn_class(**kwargs, affine=False) for k in range(length)])
        self._pos = 0

    def forward(self, x):
        ret = self[self._pos](x)
        self._pos = (self._pos + 1) % len(self)
        return ret
```

TorchDynamo is correctly detecting the mutation of `self._pos` and mapping the class to `UnspecializedNNModuleVariable`, however the `self[self._pos]` is causing issues because it results in different weights being used each iteration.

This is a particularly tricky case to handle, since it is hard to prove that all values of `self._pos` will result in the same graph.  We also do not support indirect guards, so it is not possible to have a guard on `self[self._pos].blah`.

As a concrete action item, I think we should detect this type of pattern and graph break on it.  This would be a lot better than recompiling and hitting the cache limit, since it would allow us to optimize other parts of the model.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng
Repository: PowerToys
Issue: [Color Picker] Tablet pen input is ignored
Labels: Issue-Bug,Needs-Triage,Product-Color Picker,Needs-Team-Response

### Microsoft PowerToys version

0.78.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

ColorPicker

### Steps to reproduce

I am an artist and I use the color picker a lot; I really like this functionality and would love to use it with my pen too instead of having to switch to the mouse.

Use tablet pen input (I'm using a Wacom) and try to have any interaction with the Color Editor window (even the "title" bar or the close button).

![immagine](https://github.com/microsoft/PowerToys/assets/35636532/15088854-c132-4a0d-ba7d-7965460b9cc3)

### ✔️ Expected Behavior

Tablet pen to work like any other window in the OS.

### ❌ Actual Behavior

Ignores any input from the tablet pen.

### Other Software

Not sure if it is relevant, but my Wacom driver version is 6.4.4-3 (for DTK-2420)
Repository: godot
Issue: Unexpected/wrong behavior in Joint3D when one part is frozen.
Labels: bug,topic:physics,topic:3d

### Tested versions

Tested in v4.2.stable.mono.official [46dc27791], v4.3.dev4.mono.official [df78c0636]

### System information

Windows 10 - v4.2.stable - Vulkan API 1.3.242 - Forward+

### Issue description

If two RigidBody3D Nodes are connected by any Joint3D Node, where one Body has the `Freeze = true` property set, the other has `Freeze = false`; In certain configurations, it is possible for the non-Freeze Body to remain stuck in place as it if was frozen.

When this is the case, toggling the `ExcludeNodesFromCollision` property in the Joint itself causes the non-Freeze body to become active. A more detailed showcase of this problem can be found inside the Bug.cs file in the attached project.

### Steps to reproduce

Download and open the attached project folder, make sure to Build first, as the "Script" Node makes use of [Export]'s a property to the inspector.

A more detailed description for the issue is located inside of Bug.cs, specifically `void Correct()` and `void Issue()`.

### Minimal reproduction project (MRP)

[Bug.zip](https://github.com/godotengine/godot/files/14736202/Bug.zip)
Repository: hello-algo
Issue: 繁體中文版勘誤（Help Wanted）
Labels: translation

We have converted the book from Simplified Chinese(简体中文) to Traditional Chinese(繁體中文) with the [glossary](https://www.hello-algo.com/chapter_appendix/terminology/).

> [!IMPORTANT]
> The Traditional Chinese version is available at https://www.hello-algo.com/zh-hant/, which should still have some bugs. 
>
> We seek help from native Traditional Chinese speakers to improve the Traditional Chinese version by dropping comments here or submitting PRs.
Repository: yt-dlp
Issue: zstd content-encoding
Labels: enhancement,core:networking,low-priority

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

chromium M123 (latest stable) [introduces zstd content-encoding](https://chromestatus.com/feature/6186023867908096). this provides opportunity for faster http transfers, as support within websites will be rolling out

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: go
Issue: proposal: cmd/covdata: support computing total coverage over all packages
Labels: Proposal

### Proposal Details

Currently go coverage computes coverage per package. You can use `-coverpkg` to get coverage to also include cross-package calls, but reported coverage is still per package.

I would suggest to add a flag like `-total` to `tool covdata percent` to compute coverage across all packages (potentially still restricted using `-pkg`). Literally, "number of lines of code called during tests across all packages" / "number of lines of code across all packages".
Repository: go
Issue: cmd/covdata: percent does not support ./... for the -pkg pattern
Labels: NeedsInvestigation,compiler/runtime

### Go version

go version go1.22.1 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.1'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
GOMOD='/code/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1985924870=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I ran:

```
GOCOVERDIR=coverage go test -timeout 10m -cover -covermode atomic -args -test.gocoverdir=coverage ./...
```

to collect coverage data into `coverage` dir and then I ran:

```
go tool covdata percent -i=coverage -pkg=./...
```

### What did you see happen?

No output was made.

### What did you expect to see?

To get the coverage matching the `./...` package(s). Same as what was reported during a test run.

The use case here is that I have also some additional e2e main programs calling into the library I am testing and I want those to not be reported. But to report everything under the `./...` pattern.

Note, help text says:

```
  -pkg string
    	Restrict output to package(s) matching specified package pattern.
```

Which makes me think that `./...` should already be supported.
Repository: rust
Issue: Tracking Issue for __rust_no_alloc_shim_is_unstable
Labels: A-linkage,A-allocators,T-lang,C-tracking-issue

### 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

- [x] Implement (done in https://github.com/rust-lang/rust/pull/86844)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] 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

### Unresolved Questions

* Do we want to commit to allowing linking default output (rlib) format with arbitrary linkers? (see https://github.com/rust-lang/rust/pull/86844#issuecomment-1291008533)
* TODO, maybe more. Maybe we want some formal RFC etc. before stabilizing this.

### Implementation history

* https://github.com/rust-lang/rust/pull/86844
  *  default_alloc_error_handler became stable in https://github.com/rust-lang/rust/pull/102318
Repository: TypeScript
Issue: [ServerErrors][TypeScript] 5.5.0-dev.20240324
Labels: Bug

The following errors were reported by 5.5.0-dev.20240324
[Pipeline that generated this bug](https://typescript.visualstudio.com/TypeScript/_build?definitionId=48)
[Logs for the pipeline run](https://typescript.visualstudio.com/TypeScript/_build/results?buildId=160708)
[File that generated the pipeline](https://github.com/microsoft/typescript-error-deltas/blob/main/azure-pipelines-gitTests.yml)

This run considered 300 popular TS repos from GH (after skipping the top 0).

<details>
<summary>Successfully analyzed 248 of 262 visited repos (:warning: expected 300)</summary>

| Outcome | Count |
|---------|-------|
| Detected interesting changes | 7 |
| Detected no interesting changes | 241 |
| Git clone failed | 4 |
| Language service disabled in new TS | 1 |
| Unknown failure | 9 |

</details>

## Investigation Status
| Repo | Errors | Outcome |
|------|--------|---------|
|0a115876af642a53b8c799d402567b21|1| |
|4a5e4d3c7102d2b84158ac32f4b859be|1| |
|4d1e9523611c332e3d65272363b0fd7c|1| |
|97499a2994ec4fa6c51c969170248ffa|1| |
|a73aba22c3d2ec5cb4237d5649f8ba9a|1| |
|c165c5ce5ae767a657ff0096f558c385|1| |
|d15d17b3edceafb856e67369d0a1c3fc|1| |
Repository: stable-diffusion-webui
Issue: [Feature Request]: Toggle for extra networks/checkpoints tabs to only show files/cards at a given directory level
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 ?

Personally I use the tree view to navigate directories but this would work for the directory type as well:
Not having all of the cards for the entire subdirectory tree displayed all at once at a given level, like every other typical file browser, it only shows the cards present at that level. 

This would probably also help with the initial ui loading/display as when you first click the loras tab it is trying to parse every single item. Currently it makes sorting into folders somewhat less useful without a 'miscallaneous' as if not everything is in a leaf subdirectory then you get not only everything in the current level, but every other level in that directory.

The only time you should be showing everything under a given directory is when you explicitly want it to, Primarily for searches, but I could envision some browsing scenarios as well. So when you actually are using the search box for a search you would either search everything, or have the option to search under the current directory (it should probably be a toggle as I can see why you would want to do either or routinely). This should not be a setting in the settings tab, but a toggle to be switched on and off as needed while using it.

### Proposed workflow

1. Go to Lora/Checkpoint tab
2. Press on a directory, either in the tree view or the directory view
3. Files would only show at that selected level unless a subdirectories toggle is enabled
4. If the user uses the search box, then search everything
5. If a toggle 'search at current directory level only' is checked, then that search will only search at that directory level and its subdirectories


### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Option to have Extra Networks Tree View not show files
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 ?

Probably a settings option as people probably do use it like this, but I would prefer it if the tree view was only for directories, and not making it more onerous to scroll when the directory itself has tons of files under that level. 

Currently I am able to replicate how I would like this to look using a CSS display modifier, but it is almost definitely wasting time processing all of the file leaves under the tree only for me to hide them post-action with CSS. The custom override CSS I use to achieve the same effect is:
_li.tree-list-item.tree-list-item--subitem[data-tree-entry-type="file"] {display:none;}_

### Proposed workflow

1. Go to one of the extra networks tabs (Lora or Checkpoint,etc)
2. Click on a directory in the tree list
3. If there are directories under a given directory selection, display the further subdirectories
4. If there are only files under a given directory selection, then no additional items should be displayed underneath the selection in the tree


### Additional information

_No response_