sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Add documentation on how to fix corrupt UIDs in a project (workaround inside)
Labels: discussion,topic:editor

### Godot version

4.0 dev

### System information

all

### Issue description

In some projects and others people are reporting this issue:
```bash
WARNING: res://object.tscn:4 - ext_resource, invalid UUID: uid://somebrokenuid- using text path instead: res://assets/models/somepath.tres
     at: load (scene/resources/resource_format_text.cpp:448)
```

I believe it's a bug between our alpha and beta godot version, we should fix it, as it appears to not just be The Mirror that has the bug.

### A workaround I found I would like to share

I found a working fix for this which can resolve the problem for an entire project, its quite slow to do, but it has worked in our case to clear up all our UID issues. (this goes without saying but I'll say it: MAKE BACKUPS before you do this)

1. Use a regex find and replace (in my case I used CLion with the regex box checked) to remove all the UIDs with a space at the start of uid:// (ENSURE you keep the space at the start of uid= regex pattern)
``` 
 uid=\"uid://.*?\"
```

2. Then use this pattern without the space to nuke it from all the other places its used (ensure no space at start of regex pattern)
```
uid=\"uid://.*?\"
```

3. Open the engine with your project.
4. Set message queue to a very large size (required for large projects) - I used 819200kb because memory is cheap.
![image](https://user-images.githubusercontent.com/748770/201741800-c0ed96ab-e24e-4d08-892e-759c3c0642d6.png)
5. Reboot editor and project
6. File -> Quick Open -> Select all scenes with shift select the top and bottom for all scenes.
7. Wait about 5 minutes until all the scenes open.
8. File -> Save all scenes
9. You're not done yet.
10. Open the file browser -> Search for all .tres files
11. Click each .tres individually and click the save icon individually for each file (this took me ages but it worked)
12. Now it's important, repeat step 8 again
13. You should have a bunch of changes to .import/.tres reboot your editor and check for any UID errors in the console they should be gone.




### Steps to reproduce

Unsure how the bad UIDs were introduced but they seem to disappear by doing my workaround.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Add smoke-tests for CPP extensions compilations
Labels: high priority,module: cpp-extensions,triaged,module: regression

### 🐛 Describe the bug

Followup for https://github.com/pytorch/pytorch/issues/88290

We should add CI/smoke tests for that by using something like the following:
https://github.com/pytorch/pytorch/pull/87615#issuecomment-1289539357

### Versions

CI

cc @ezyang @gchanan @zou3519
Repository: TypeScript
Issue: Experiment with tracking which entities actually may be narrowed
Labels: Suggestion,Domain: Performance,Experimentation Needed,Fix Available,Rescheduled

In Pyright, narrowing can be avoided by keeping track of which entities actually get narrowed within a given scope. This could save a good amount of time by avoiding redundant walks up the control flow graph just to discover nothing interesting a given variable or property.

I'm not sure if Pyright also tracks the first location at which an entity may be narrowed, but that information could also be used to signal when a narrowing walk needs to stop.

This would come at the cost of some memory overhead, but we'd need to experiment to see what the trade-offs are.
Repository: TypeScript
Issue: Display narrowed type of properties in `completionEntryDetails`
Labels: Suggestion,In Discussion,Domain: Type Display

```ts
interface Palette {
    red?: Color;
    green?: Color;
    blue?: Color;
}

type Color = string | [number, number, number];

function checkOrange(p: Palette) {
    if (typeof p === "object" && "orange" in p && typeof p.orange === "number") {
        p./**/
    }
}
```

Request completions at `/**/` and select the option for `orange`.

<details>
<summary><span>Today, we show

```
(property) orange: unknown
```

</span>

![image](https://user-images.githubusercontent.com/972891/201755666-933e990e-3c27-450a-82c7-682a36dfa346.png)

</summary>

```json5
[
    {
        "name": "orange",
        "kindModifiers": "",
        "kind": "property",
        "displayParts": [
            {
                "text": "(",
                "kind": "punctuation"
            },
            {
                "text": "property",
                "kind": "text"
            },
            {
                "text": ")",
                "kind": "punctuation"
            },
            {
                "text": " ",
                "kind": "space"
            },
            {
                "text": "orange",
                "kind": "propertyName"
            },
            {
                "text": ":",
                "kind": "punctuation"
            },
            {
                "text": " ",
                "kind": "space"
            },
            {
                "text": "unknown",
                "kind": "keyword"
            }
        ],
        "documentation": [],
        "tags": []
    }
]
```

</details>

This has to do with how we decide to display properties - we simply request the type of what `p` is narrowed to, not the type of individual properties. This is actually part of another weirder distinction, where narrowing a property doesn't also narrow the containing value's type.

Recently there's been some discussion around whether we could do that; however, I am a bit skeptical here. Short of that, it would be nice to show users the actual type they're using.

This could get a little bit expensive; but narrowing in general should get cheaper. In theory, #51525 could avoid much of the work, and make the overhead here very low.
Repository: node
Issue: Error building nodeJS + FIPS (static linking) on Windows 10
Labels: windows,build

### Version

18.12.0

### Platform

Microsoft Windows NT 10.0.19044.0 x64

### Subsystem

_No response_

### What steps will reproduce the bug?

Install windows prerequisites as defined in BUILDING.md: https://github.com/nodejs/node/blob/v18.x/BUILDING.md#windows

Run:
python configure.py --openssl-is-fips
.\vcbuild.bat

### How often does it reproduce? Is there a required condition?

Reproduced every time, no required conditions.

### What is the expected behavior?

The build should pass and node should run in FIPS mode

### What do you see instead?

The build runs for about 30-40 minutes and fails with the below error trace:

```
...
...
     Creating library ..\..\out\Release\mksnapshot.lib and object ..\..\out\Release\mksnapshot.exp
  mksnapshot.vcxproj -> ..\..\out\Release\\mksnapshot.exe
  generating: "..\..\out\Release\obj\v8_snapshot\/snapshot.cc" "..\..\out\Release\obj\v8_snapshot\/embedded.S"
  Assembling ..\..\out\Release\obj\v8_snapshot\\embedded.S...
  setup-isolate-deserialize.cc
  snapshot.cc
  v8_snapshot.vcxproj -> ..\..\out\Release\lib\v8_snapshot.lib
  node_pch.cc
  node_snapshot_stub.cc
  node_mksnapshot.cc
     Creating library out\Release\node_mksnapshot.lib and object out\Release\node_mksnapshot.exp
  node_mksnapshot.vcxproj -> out\Release\\node_mksnapshot.exe
  node_mksnapshot
  fipsinstall, and also copy_fips_module
  Can't open "out\Release\obj.target/deps/openssl/libopenssl-fipsmodule.so" for reading, No such file or directory
```


### Additional information

_No response_
Repository: angular
Issue: Types from split classes/interfaces do not get checked in templates
Labels: area: compiler,P4,compiler: template type-checking

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

Don't known / other

### Is this a regression?

No

### Description

If I declare a class component in a types.d.ts to distribute in a library like so:

```typescript
export declare class MyExampleComponent {
    propName1: boolean;
    propName2: string;
    propName3: number;
    static ɵfac: ɵngcc0.ɵɵFactoryDeclaration<MyExampleComponent, never>;
    static ɵcmp: ɵngcc0.ɵɵComponentDeclaration<MyExampleComponent, "my-example", never, { "propName1": "propName1"; "propName2": "propName2"; "propName2": "propName2"; }, {}, never, never, false>;
}
```

I can enable strict type checking within angular templates to make sure that the value passed into `propName1` is a boolean (same for the other props).

However, if I split the type declaration like so:

```typescript
export declare interface MyExampleComponent {
    propName1: boolean;
    propName2: string;
    propName3: number;
}
export declare class MyExampleComponent {
    static ɵfac: ɵngcc0.ɵɵFactoryDeclaration<MyExampleComponent, never>;
    static ɵcmp: ɵngcc0.ɵɵComponentDeclaration<MyExampleComponent, "my-example", never, { "propName1": "propName1"; "propName2": "propName2"; "propName2": "propName2"; }, {}, never, never, false>;
}
```

Then it stops checking the types of the properties. It can recognize if the prop is misspelled, but it would not give any error if I passed a string into propName1 or anything else like that.

According to typescript rules, the interface's typings should get merged with the class's typings.

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

_No response_

### Please provide the exception or error you saw

_No response_

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

```true
Angular CLI: 14.2.6
Node: 16.18.0
Package Manager: npm 8.19.2
OS: win32 x64

Angular: 14.2.7
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1402.6
@angular-devkit/build-angular   14.2.6
@angular-devkit/core            14.2.6
@angular-devkit/schematics      14.2.6
@angular/cdk                    14.2.5
@angular/cli                    14.2.6
@schematics/angular             14.2.6
rxjs                            6.5.5
typescript                      4.8.4
```


### Anything else?

_No response_
Repository: bitcoin
Issue: Balance calculation and coin selection should arrive at the same conclusions
Labels: Feature

Currently balance calculation and coin selection operate completely independently of each other, and have slightly different criteria for determining what outputs should be included in their respective calculations. This results in their conclusions differing from each other in various edge cases which can be very confusing to users. They should probably be unified so that computed balances match the available utxos that coin selection may choose from.

A possible solution is to have the wallet actually track its (U)TXOs and compute the balance and available coins from that, rather than each having to iterate all txs in the wallet and try to figure out what's relevant.
Repository: TypeScript
Issue: Allow use of const enums in value space when preserveConstEnums=true
Labels: Suggestion,In Discussion

## Background

The TypeScript compiler uses const enums for the performance benefit of inlining, but then enables `preserveConstEnums` and modifies the output d.ts files to "lie" to API consumers and say that the enum is not const. This, and "just don't export const enums" are the recommended methods for library authors; the emitted code for const vs non-const enums is identical with the flag enabled.

Internally, however, we use the enum values at runtime for Debug helpers. In order to make this work, we must write code like:

```ts
export function formatSyntaxKind(kind: SyntaxKind | undefined): string {
    return formatEnum(kind, (ts as any).SyntaxKind, /*isFlags*/ false);
}
```

But, we cannot write:

```ts
export function formatSyntaxKind(kind: SyntaxKind | undefined): string {
    return formatEnum(kind, SyntaxKind, /*isFlags*/ false);
}
// or
export function formatSyntaxKind(kind: SyntaxKind | undefined): string {
    return formatEnum(kind, (SyntaxKind as any), /*isFlags*/ false);
}
```

Without using `// @ts-ignore-error` to silence:

> 'const' enums can only be used in property or index access expressions or the right hand side of an import declaration or export assignment or type query

## Proposal

Don't issue the above error when `preserveConstEnums=true`.

I believe that this change should be safe because this flag explicitly forces tsc to emit enums as though they had been written as non-const; not issuing the error lets you use it as a value.

## Motivation

In the codebase pre-modules, `ts` was the namespace and was sometimes used intentionally, but now, this `ts as any` pattern is one of the only reasons why our codebase internally needs to refer to the namespace barrels and can't direct import everything everywhere.

If this error were disabled when `preserveConstEnums=true`, however, we could just use the enums directly and not have to jump through hoops (and potentially pull enum formatting out and drop the helpers, removing a cycle between debug and types).

## Alternative considered

Another alternative to this (for the TS compiler itself) is to just not use const enums. This works because our current outputs are produced by esbuild, which doesn't care at all about whether or not enums are const; it will inline them if it can, and it will produce a non-const enum object if the enum itself is needed in value space. But, if we do _any_ other kind of build that isn't "esbuild on src" (e.g. change bundlers, run the bundler on tsc outputs, etc), using non-const enums would cause a performance regression. I also have no idea if there are behaviors one can have in const enums and not in regular enums, though I suspect there aren't any.

## Related

- #31353
- #37282 (in that this proposal would effectively declare we won't do it, and will stick to the current behavior)
- Probably some other issue I didn't find
Repository: flutter
Issue: Skwasm unit tests are flaky on Safari
Labels: a: tests,platform-web,P2,team-web,triaged-web

For some reason, the Skwasm unit test suite (that currently has a single unit test in it) is flaky and sometimes leads to the following error on CI:

```
  [31mFailed to load "test/skwasm/smoke_test.dart":[0m SessionNotCreatedException (500): Could not create a session: The session timed out while connecting to a Safari instance.
```

The test itself is not very high-value, so I'm just going to disable it on Safari for now.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Explore NVIDIA/TransformerEngine for speed/efficiency
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 ?

- https://github.com/NVIDIA/TransformerEngine
  - > A library for accelerating Transformer models on NVIDIA GPUs, including using 8-bit floating point (FP8) precision on Hopper GPUs, to provide better performance with lower memory utilization in both training and inference.

### Proposed workflow

N/A

### Additional information

Crossposted on:

- https://github.com/huggingface/diffusers/issues/1288

Other issues related to potential performance improvements:

- https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/1625
- https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/4096
- https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/4606
Repository: flutter
Issue: Create accessibility tests for all default framework widgets
Labels: a: tests,team,framework,a: accessibility,P2,team-framework,triaged-framework

The entire Flutter SDK's widget catalog should be run against an accessibility test suite to verify they meet the minimum guidelines. Currently, there are Google tests that are run very late in the CI lifecycle that detect these breakages, but it would be good to catch it on GitHub.

For example, a select all semantics node was added in a widget, but it was too small to meet Android's accessibility guidelines for tappable nodes in https://github.com/flutter/flutter/pull/107193

Googlers, see b/258829761 for internal context, and references to the existing tests. We may able to port some of these externally to benefit the community.
Repository: flutter
Issue: M1 macs require special arguments in order to build the "host" targets natively
Labels: team,engine,platform-mac,P2,platform-host-arm,team-engine,triaged-engine

By default on a Mac the "host" targets will include an x64 build but you can override that with `--mac-cpu arm64`. Note that this produces an output directory that includes the suffix `_arm64` which means that the local work flow must acknowledge it across the board. Without this, all development on an M1 mac will produce x64 targets by default and use rosetta for local testing.

Perhaps the default CPU option should be determined from the local host machine and the suffixes should only be used when the CPU target is manually specified. In other words:

`% gn --unoptimized` will produce targets for the local CPU type in `out/host_debug_unopt`
`% gn --unoptimized --mac-cpu arm64` will produce targets for arm CPUs in `out/host_debug_unopt_arm64`
`% gn --unoptimized --mac-cpu x64` will produce targets for Intel CPUs in `out/host_debug_unopt_x64`

For building our targets for deployment, we'll have to manually specify a build for all architectures and then deploy multiple suffixed directories - perhaps with a symlink for `host_foo_<local cpu type> -> host_foo`
Repository: godot
Issue: Resources saved to file from an imported scene do not save with consistent UIDs
Labels: bug,topic:core,topic:editor,confirmed

### Godot version

v4.0.beta.custom_build [98e0d5995]

### System information

Fedora 36

### Issue description

If "save to file" is enabled for meshes or animations in an imported scene, the saved resources are given a random UID if the file doesn't already exist.
This is annoying if you've `.gitignore`d these files, which makes sense to do since they're auto-generated from glTF files. For example, I did so for the vehicle meshes in the [Truck Town](https://github.com/godotengine/godot-demo-projects/tree/4.0-dev/3d/truck_town) demo. If you clone this repo right now, opening any of the vehicle scenes gives multiple invalid UID errors because when the mesh `.res` files are generated they don't get the same UIDs.

I don't know how UIDs work, but I assume the way to fix this would be to remember what UID the resources are saved to in the glTF's `.import` file? That way it would be generated with the same UID every time.

### Steps to reproduce

1. Save a mesh or animation resource from a scene to a file using the advanced import options
2. Reference that resource in a scene and save it
3. Delete the resource and reimport the scene to regenerate it
4. Open the scene referencing the resource, notice the invalid UID error

### Minimal reproduction project

https://github.com/godotengine/godot-demo-projects/tree/4.0-dev/3d/truck_town
Repository: opencv
Issue: Reading pointcloud is not thread safe
Labels: bug,category: viz

### System Information

OpenCV version: 4.6.0
Operating System / Platform: Ubuntu 22.04
Compiler & compiler version: GCC 11.3.0

### Detailed description

I get the following error when attempting to read two different pointclouds from two different threads.
```
OpenCV Version 4.6.0
Warning: In ./IO/PLY/vtkPLYReader.cxx, line 124
vtkPLYReader (0x7ffb74000b70): Could not open PLY file

ERROR: In ./Common/ExecutionModel/vtkExecutive.cxx, line 781
vtkCompositeDataPipeline (0x7ffb74001890): Algorithm vtkPLYReader(0x7ffb74000b70) returned failure for request: vtkInformation (0x7ffb74005970)
  Debug: Off
  Modified Time: 839
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  ALGORITHM_AFTER_FORWARD: 1
  FROM_OUTPUT_PORT: 0
  FORWARD_DIRECTION: 0
```

### Steps to reproduce

```cpp
#include <thread>
#include <opencv2/opencv.hpp>
#include <opencv2/viz.hpp>

using namespace std::literals;

int main()
{
    std::cout << "OpenCV Version " << cv::getVersionString() << std::endl;
    // Make a cube of points
    int w = 100;
    cv::Mat cube(1, w * w * w, CV_32FC3);
    for (int x = 0, i = 0; x < w; ++x)
        for (int y = 0; y < w; ++y)
            for (int z = 0; z < w; ++z, ++i)
                cube.at<cv::Vec3f>(i) = cv::Vec3f(x, y, z);

    // Write cube to two different ply files
    cv::viz::writeCloud("../cube1.ply", cube);
    cv::viz::writeCloud("../cube2.ply", cube);

    // Try to read ply files from threads
    std::thread t1 = std::thread(
        [&cube]()
        {
            cv::Mat cube1 = cv::viz::readCloud("../cube1.ply");
        });

    // std::this_thread::sleep_for(1s);

    // Error here
    std::thread t2 = std::thread(
        [&cube]()
        {
            cv::Mat cube2 = cv::viz::readCloud("../cube2.ply");
        });

    t1.join();
    t2.join();

    return 0;
}
```

### 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: pytorch
Issue: [PT][1.13] torch .numpy() fn broke for some scenario
Labels: module: cpu,triaged,module: numpy,module: regression,actionable,ZeroTensor

### 🐛 Describe the bug

when backward tensor of sng operator is converted from torch tensor to numpy then output is not correct. 
it was expected that output should be 0's as torch tensor has filled with 0's but we get random output after performing .numpy() 
this happens only in 1.13 release, 1.12 works fine. Also if tensor is cloned then it works fine
```
import torch
torch.__version__ # 1.13.0a0 
x = torch.randn(20, dtype=torch.float32, requires_grad=True)
res = torch.sgn(x)
res_bwd = res.grad_fn(torch.ones(res.shape))
res_bwd
# tensor([0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])
np_res = res_bwd.detach().numpy()
np_res
```

```
output = array([5.3426861e-35, 0.0000000e+00, 0.0000000e+00, 0.0000000e+00,
       1.4012985e-45, 0.0000000e+00, 7.6396113e-35, 0.0000000e+00,
       1.7767014e+09, 4.5693540e-41, 7.6396113e-35, 0.0000000e+00,
       9.1476764e-41, 0.0000000e+00, 1.1210388e-43, 0.0000000e+00,
       3.5873241e-43, 0.0000000e+00, 1.8342932e+09, 4.5693540e-41],
      dtype=float32
```

### Versions

torch.__version__ # 1.13.0a0 

cc @VitalyFedyunin @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @mruberry @rgommers
Repository: ant-design
Issue: 能否增加一个 transfer穿梭框组件 能够隐藏 全选下拉框 而不隐藏全选框的api
Labels: Inactive

### What problem does this feature solve?

某些场景下只需要全选框而不需要下拉框

### What does the proposed API look like?

增加一个 隐藏全选下拉框而不隐藏全选框的api，就像antd3的transfer穿梭框一样的样式

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->