sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: three.js
Issue: Box3.setFromObject doesn't check if worldMatrix is out of date
Labels: Bug

**Description**
Calls to Box3.setFromObject give an incorrect bounding box when the worldMatrix is out of date. 

**To Reproduce**

Steps to reproduce the behavior:
1. Create parent Object3D and assign non-zero position
2. Add a child Object3D and assign a non-zero position
3. Call `new Box3().setFromObject(child).getCenter(new Vector3())` and the vector returned is the child's position, not the world position. 

***Code***

```js
const parent = new THREE.Object3D();
scene.add(parent);

parent.position.copy(new THREE.Vector3(11, 22, 33));

const box = new THREE.BoxGeometry( 20, 20, 20 );
const mat = new THREE.MeshBasicMaterial( {color: 0x00ffff} );
const cube = new THREE.Mesh( box, mat );
parent.add(cube);

cube.position.copy(new THREE.Vector3(10, 20, 30));

// this gives the wrong result
let center = new THREE.Box3().setFromObject(cube)
    .getCenter(new THREE.Vector3());
console.log("before matrix update", center.toArray());

// this gives the correct result
cube.updateWorldMatrix(true, true);
center = new THREE.Box3().setFromObject(cube)
  .getCenter(new THREE.Vector3());
console.log("after matrix update", center.toArray());
```

***Live example***
https://codepen.io/nbosscher/pen/VwmdVxL?editors=1001

**Expected behavior**
I expected the worldMatrix to be auto-updated if it was out of date.


**Platform:**

 - Device: [Desktop]
 - OS: [MacOS]
 - Browser: [Chrome]
 - Three.js version: [r126]
Repository: rust
Issue: Parallelize rustdoc rendering
Labels: T-rustdoc,E-hard,C-enhancement,I-compiletime,S-blocked

I and others would like to parallelize [rustdoc rendering](https://github.com/rust-lang/rust/blob/6f7673d077add6b9a066e988b1b8b132a8193d6c/src/librustdoc/formats/renderer.rs#L69-L98). It is "embarrassingly parallel" ... except that rustdoc has some technical debt in the form of global mutable state that will have to be dealt with first.

### Steps

- [x] Get rid of `CURRENT_DEPTH` thread-local (#82742)
- [ ] Make `Span` etc. Send and Sync
- [ ] Use `RwLock` instead of `RefCell` for `SharedContext` fields (or make `Context`, and by extension `SharedContext`, Send and Sync some other way)
- [ ] So many more things...
- [ ] Add parallelism via MPSC channels and `rayon`

cc @rylev @jyn514 
cc https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/windows-rs.20perf/near/226957262 (was going to open this issue anyway, but noticed this discussion so thought I'd link to it)
Repository: TypeScript
Issue: Feature request: typescript.suggest.paths also suggests relative path in `new URL("_here_", import.meta.url)`
Labels: Suggestion,Awaiting More Feedback

# Suggestion

```ts
new URL("||", import.meta.url)
```

Provide relative filename completion for the string in the 1st position.

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

new URL import meta

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: flutter run -d chrome using --web-hostname 0.0.0.0 doesn't work on some browsers with different ip
Labels: tool,platform-web,has reproducible steps,P3,c: fatal crash,found in release: 2.0,found in release: 2.1,team-web,triaged-web

## Steps to Reproduce

<!-- Please tell us exactly how to reproduce the problem you are running into. -->

1. `flutter create test`
2. `cd test`
3. `flutter run -d chrome --web-hostname 0.0.0.0`
4. It opens a web browser on the URL `http://0.0.0.0:12345`, and I can open that URL on the same device on another tab.

![image](https://user-images.githubusercontent.com/4969854/109908516-48c90800-7c59-11eb-9169-d1c264260545.png)

Looking online, using the hostname `0.0.0.0` allows the usage of the network IP, such as `192.168.1.*`, allowing it to be opened on another device with the URL `192.168.1.219:12345`.

---

5. However, on the flutter web 2.0 release, if I open that URL `192.168.1.219:12345` on any browser on the same device or different device, or using `ngrok` - trying to access the dev website on any URL other than `0.0.0.0:12345`, will end up in limbo.

![image](https://user-images.githubusercontent.com/4969854/109908897-f3d9c180-7c59-11eb-9013-991b7dcf420c.png)

It's weird because the URL works, the title and favicon loads, all the network calls happen, but there's nothing run in the console, if the URL is hash-based it doesn't get populated with the hash, and it basically looks like the HTML runs but the JS does not.
Repository: rust
Issue: Arm thumbv6m binary size increase with dead code change (or from 1.50 to 1.51)
Labels: O-Arm,I-heavy

I've observed an unexpected increase in binary size in response to a [change](https://github.com/stm32-rs/stm32g0xx-hal/commit/77dace37908f281feb9432fc13874475d9dc0765) in a crate that we use. The change only adds new public methods, which we don't call, so all the changed code is effectively dead code, but still it results in a significant increase in our binary size. My guess is that the presence of this new code causes LLVM to make different inlining decisions, even though the new code isn't actually called anywhere.

This happens on 1.50.0. The increase (for a minimal binary included below) is from 932 bytes to 2164 bytes.

Switching from 1.50 to 1.51 (currently in beta) without the above change causes the same increase from 932 bytes to 2164 bytes.

I was going to mark this as a stable to beta regression, but TBH, I think it's probably a pre-existing issue that just triggers in response to legitimate changes in library code. I expect that whatever changed between 1.50 and 1.51 is similar in nature to the code change above.

I've tarred up a moderately minimal bit of code that reproduces this:

[binary-size-increase.tar.gz](https://github.com/rust-lang/rust/files/6081091/binary-size-increase.tar.gz)

To reproduce, run the `./check-size` script contained within the tarball. You might need to `rustup target install thumbv6m-none-eabi` first.

For me, with current stable 1.50, this shows a change in binary size from 932 bytes to 2164 bytes:

```
Size prior to commit 77dace37908f281feb9432fc13874475d9dc0765
-rwxr-xr-x 1 dml eng 932 Mar  4 16:39 a.bin
Size after commit 77dace37908f281feb9432fc13874475d9dc0765
-rwxr-xr-x 1 dml eng 2164 Mar  4 16:39 b.bin
```

If I adjust the script to use 1.51, then I get 2164 bytes for both.

Looking at the disassembly of each binary, it seems that the larger binary includes `compiler_builtins::int::specialized_div_rem::u64_div_rem`, where the smaller binary doesn't. `u64_div_rem` is called from `__udivmoddi4`, which is called from `__aeabi_uldivmod`. These are also absent from the smaller binary, but present and called from `MicroSecond::cycles` / `Delay::delay` in the larger binary.

Cargo.toml sets opt-level = "s". Similar results are observed with opt-level = "z".

Given that LTO is enabled, I'd have expected that dead code would be removed before inlining decisions were made, so I'm surprised that a change to code that isn't called would have this effect.

If there's anything we can do to help LLVM make more optimal decisions when optimizing for binary size, that'd be awesome, although I'm sure it's a pretty difficult problem.
Repository: godot
Issue: Strange behaviour using a 1x1 transparent pixel in a TextureAtlas 
Labels: bug,confirmed,topic:2d

**Godot version:**
3.2.3

**OS/device including version:**
Win 10

**Issue description:**
If you add a 1x1 transparent pixel to a TextureAtlas and try to use it, you will get strange artefacts. If you use it in a texture rect, the entire texture atlas will be drawn along side the pixel, all be it at as massive scale. Hopefully the video below explains it:

![wY1QMAMGks](https://user-images.githubusercontent.com/45369568/109920495-43e47280-7cb2-11eb-970d-3f184da1cf5d.gif)

In addition, if you attempt to use the 1x1 pixel in a Theme component, it will use the entire atlas as the texture. This may be the same case as above with a different scale factor. It's sufficiently broken that I can't really tell.

It is only limited to transparent images. A 1x1 opaque image is handled correctly.

This is perhaps a niche bug. I wanted to use an empty png to replace some built in UI textures with empty versions (such as the radio buttons in a drop down menu). This can instead be achieved by using empty ImageTextures.

**Steps to reproduce:**
1. Create a TextureAtlas with some content.
2. Add a 1x1 transparent image to the TextureAtlas.
3. Use that 1x1 image in a TextureRect. Depending on your atlas size you may have to zoom out quite a long way to see the bleed.
4. Alternatively try using the 1x1 image as an icon in a theme component.

**Minimal reproduction project:**
[Testing-Atlas1x1.zip](https://github.com/godotengine/godot/files/6081295/Testing-Atlas1x1.zip)
Repository: electron
Issue: [Feature Request]: lockOnDesktop Needed
Labels: enhancement :sparkles:

### Preflight Checklist

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


### Problem Description

I need to make a frame lock on the desktop, just like a widget app:
1. Even though user clicked the "show desktop" button on taskbar, it still shows on desktop.
2. Other window could cover on it, but it never cover on others

### Proposed Solution

new BrowserWindow({ lockOnDesktop: true })

### Alternatives Considered

no

### Additional Information

no
Repository: ant-design
Issue: [Feature Request] Form verticalMargin prop
Labels: 🗣 Discussion,💡 Feature Request,Inactive

```jsx
<Form>
  <Form.Item style={{ marginBottom: 0 }} />
  <Form.Item style={{ marginBottom: 0 }} />
  <Form.Item style={{ marginBottom: 0 }} />
</Form>
```

=>

```jsx
<Form verticalMargin={0}>
  <Form.Item verticalMargin={16} />
  <Form.Item />
  <Form.Item />
</Form>
```

---

`verticalMargin` or `gutterVertical`
Repository: vscode
Issue: Separate the error and warning popups from the documentation popups in Intellisense
Labels: feature-request,under-discussion,editor-hover

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Currently, there are [some](https://code.visualstudio.com/docs/editor/intellisense#_customizing-intellisense) options available for customizing how the intellisense popups behave, including when it should appear, the delay before its appearance and a few more. However, I've not found any option to turn on or off the intellisense error- & warning-popups and the documentation popups separately. (I've searched using Google, Stackoverflow and Github, so if it's already been suggested, then I've not been lucky enough to find them).

Here are also two screenshots to explain it in action:
![2021-03-04_13-21-13](https://user-images.githubusercontent.com/52244768/109947821-fcc8a280-7cee-11eb-8f5b-1c2c6d597c12.png)
![2021-03-04_13-36-27](https://user-images.githubusercontent.com/52244768/109947847-03571a00-7cef-11eb-9b67-3a8cc8f6f30f.png)

Thanks.
Repository: pytorch
Issue: `index_copy_`  test fails on PyTorch/XLA
Labels: module: tests,triaged,module: xla

As detailed in the post by @mruberry in https://github.com/pytorch/pytorch/pull/52203#discussion_r586853734, there is an odd bug where a test for `index_copy_` fails only on XLA, while passing on CPU / GPU.

cc @mruberry @VitalyFedyunin @walterddr @ailzhang @gmagogsfm @JackCaoG
Repository: create-react-app
Issue: Why relative imports outside of src/ are not supported?
Labels: needs triage

Hi there. 

Just wondering what is the reason of this restriction? How this benefit developers.

Why is a bad idea to import my `package.json` to display the version of the App? Or to have a `settings.json` in the root of the project?

Can someone makes me understand what is the motivation of this restriction?
Repository: pytorch
Issue: Inconsistent `out=` behaviour on advanced indexing operations.
Labels: triaged,module: complex,enhancement,module: advanced indexing

Most of the advanced indexing operations (see `aten/src/ATen/native/TensorAdvancedIndexing.cpp`) do not have semantics consistent with those of `out=`. An example of this is the `out=` version of `take`, but also all the other in-place operations. Almost all of these operations require `dst.dtype == src dtype`. This is particularly problematic for complex numbers, when we want to copy/add/... float values onto a complex tensor.

A better way would be to relax this equality condition on types to a `at::native::can_cast` condition. This should apply to all the inplace and `out=` versions of advanced-indexing functions.

cc @ezyang @anjali411 @dylanbespalko @mruberry @aocsa
Repository: godot
Issue: [Bullet] Bullet physics adds the default damping values instead of setting them
Labels: bug,topic:physics,topic:3d

**Godot version:**
3.2.3.stable


**OS/device including version:**
N/A

**Issue description:**

Bullet adds the default linear/angular damping values instead of setting them. This issue doesn't occur when using Godot physics backend.

Bug is probably from here:
https://github.com/godotengine/godot/blob/dd1881ae19c9c00cc1215703dcda36b2c6af33f2/modules/bullet/rigid_body_bullet.cpp#L974-L979

**Steps to reproduce:**

* Create a rigid body and set its linear damping value to 0
* Inside physics process `PhysicsServer.body_get_direct_state(get_rid()).total_linear_damp` is now set to `0.1` (this is the default linear damping set inside project settings)


**Minimal reproduction project:**
[bullet-damping-bug.zip](https://github.com/godotengine/godot/files/6083135/bullet-damping-bug.zip)
Repository: flutter
Issue: Unexpected clip behaviour after upgrading to flutter 2.0
Labels: framework,f: material design,d: api docs,P3,team-design,triaged-design

## Steps to Reproduce

```
class DemoWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: SizedBox(
        width: 100,
        height: 100,
        child: Stack(
          fit: StackFit.expand,
          children: [
            FittedBox(
              fit: BoxFit.cover,
              child: Container(
                height: 300,
                width: 200,
                color: Colors.red,
              ),
            ),
          ],
        ),
      ),
    );
  }
}
```

**Expected results:** 

Since Stack is clipping, I expected the output to be a square.

**Actual results:** 

Not a square, the container is clipping through

This worked differently on the previous release of flutter, where the output was a square. Currently I get the desired result if I wrap Stack in a ClipRect.


<details>

```
[✓] Flutter (Channel stable, 2.0.0, on macOS 11.0.1 20B29 darwin-arm, locale en-EE)
    • Flutter version 2.0.0 at /Users/gertdrui/flutter
    • Framework revision 60bd88df91 (19 hours ago), 2021-03-03 09:13:17 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/gertdrui/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] Connected device (2 available)
    • Pixel 4 (mobile) • 9B011FFAZ0013E • android-arm64  • Android 11 (API 30)
    • Chrome (web)     • chrome         • web-javascript • Google Chrome 88.0.4324.192

• No issues found!
```

</details>
Repository: pytorch
Issue: Dimension argument names in torch.diag_embed/diagonal vs. transpose/transpose_
Labels: module: docs,triaged,module: numpy

## ❓ Questions and Help

Had a look at the issue board and didn't find anything related:

In the current version, there's four methods in `torch.Tensor` taking two dimensions as arguments: `diag_embed, diagonal, transpose, transpose_`. (master branch seems to additionally have `swapaxes, swapdims`).

For `diag_embed` and `diagonal`, the numbering starts at 1 (`dim1` and `dim2`), as opposed to the others where it starts at 0 (`dim0` and `dim1`). Is this naming convention intended?

[Link to torch.Tensor docs (master)](https://pytorch.org/docs/master/tensors.html)
[Link to torch.Tensor docs (stable)](https://pytorch.org/docs/1.7.1/tensors.html)

Keep up the good work, I enjoy using PyTorch!


cc @brianjo @mruberry @jianyuh @nikitaved @pearu @heitorschueroff @walterddr @IvanYashchuk @rgommers
Repository: godot
Issue: (Godot Physics) Rigid-to-Rigid body collisions penetrate each other
Labels: bug,topic:physics


**Godot version:**
3.2.3.stable

**OS/device including version:**
N/A

**Issue description:**
When using Godot physics backend, two rigid bodies that move towards each other at a fix linear velocity end up penetrating each other for multiple frames when they collide (doesn't happen using Bullet).

**Steps to reproduce:**

* Position two rigid bodies that move towards the origin at a fixed linear velocity
* When they arrive at the origin, they end up overlapping for multiple frames

![rigid-rigid-godot-physics](https://user-images.githubusercontent.com/79001820/109972089-a8e7a900-7d42-11eb-8d02-c6c733a20526.png)

**Minimal reproduction project:**
[test-rigid-rigid-godot-physics.zip](https://github.com/godotengine/godot/files/6083975/test-rigid-rigid-godot-physics.zip)
Repository: vscode
Issue: API: Allow extensions to render a table in a view
Labels: feature-request,api-proposal

It would be great for extensions to be able to render a table in a view, instead of a tree.

@IanMatthewHuff says:

> Basically we just wanted to ask if this is a control that would be exposed in the public API in the future? Working with webviews we have a lot of flexibility but there are big trade-offs with having to deal with stuff like theming, accessibility, UI look and feel, webview building and so on. If this table view is something that we could use or be involved with testing we’d be very interested.

And I tend to agree!
Repository: pytorch
Issue: How to load trained . torch from conversion to .mlmodel
Labels: oncall: mobile

Hi , I need in help in converting the .torch to .mlmodel ,, while doing it i faced an error . After researching found no solution for the same and posted for help .
the error:
<img width="1009" alt="Screenshot 2021-03-01 at 10 24 01 PM" src="https://user-images.githubusercontent.com/35099512/109978249-b2154d80-7d23-11eb-8e2f-39497d77051d.png">
the code used :
<img width="843" alt="Screenshot 2021-03-02 at 10 46 58 PM" src="https://user-images.githubusercontent.com/35099512/109978278-b93c5b80-7d23-11eb-8286-43ac2cab72e3.png">
 

cc @mruberry
Repository: go
Issue: x/tools/go/analysis/passes/errorsas: support errors.As provided by other packages
Labels: NeedsDecision,FeatureRequest,Tools,Analysis

`go/analysis/passes/errorsas` works only with the standard package `errors`. So, I believe it is useless for many projects which use very popular `github.com/pkg/errors`. Of course, it's possible to alias `errors` package (for example `stderrors`) and use it, but I think it's better to update the analyzer.

I see 2 options here:

- hard code `github.com/pkg/errors.As`. It's the simplest solution but requires an update for every new package
- pass a list of functions via flags. `go/analysis/passes/printf` uses the similar approach

I think the best solution is to combine these options: use flags with the default functions `errors.As` and `github.com/pkg/errors.As`
Repository: opencv
Issue: OE-XX: Hardware-accelerated Video I/O
Labels: category: videoio,evolution,platform: linux,platform: win32

## Hardware-accelerated Video I/O

* Status: **WIP**
* Platforms: **Linux, Windows**

---

The patch #19460 (thanks to @mikhail-nikolskiy) added properties to control hardware-acceleration of video decoding/encoding tasks. This patch is going to be released with OpenCV 4.5.2.

Support matrix for these properties:

OS | Backend | VideoCapture | VideoWriter
-- | -- | -- | --
Linux | [FFMPEG](https://trac.ffmpeg.org/wiki/HWAccelIntro) | VAAPI, MFX | MFX, VAAPI
  | GStreamer | [VAAPI](https://gstreamer.freedesktop.org/documentation/vaapi/index.html?gi-language=c) (and others HW plugins) | VAAPI (and others HW plugins)
Windows | FFMPEG | D3D11, MFX | MFX
  | MSMF | D3D11 | -

Hardware-acceleration is available in preview mode (disabled by default), so feel free to try it with your HW configurations:

```.cpp
VideoCapture capture(filename, CAP_FFMPEG,
    {
        CAP_PROP_HW_ACCELERATION, VIDEO_ACCELERATION_ANY,
    }
);
```

or run OpenCV Video I/O tests (`opencv_test_videoio`).

In case of observed problems, please create new issue with adding reference to this issue.

---

API documentation page is [here](https://docs.opencv.org/master/db/dc4/group__videoio__hwaccel.html)
Wiki page: https://github.com/opencv/opencv/wiki/Video-IO-hardware-acceleration

---

This is commutative issue for patches and bug reports about hardware-accelerated video decoding/encoding.

:rocket: Noticeable PRs:
- #19460 (feature) - added properties support + enabled generic APIs like D3D11/VAAPI + enabled Intel Integrated Graphics
- #19755 (feature) - cv::UMat output/input in VideoCapture/VideoWriter
- :construction:

:rotating_light: Issues:
- #19694: failed VP9 test cases on Windows + Quadro P2000 (CUDA 11.2)
- #19867: 4.5.2 Videoio breaking change for GPU acceleration
- #25185