id
int64 393k
2.82B
| repo
stringclasses 68
values | title
stringlengths 1
936
| body
stringlengths 0
256k
⌀ | labels
stringlengths 2
508
| priority
stringclasses 3
values | severity
stringclasses 3
values |
|---|---|---|---|---|---|---|
516,001,413 | pytorch | RuntimeError: !t.is_cuda() INTERNAL ASSERT FAILED at /pytorch/aten/src/ATen/native/sparse/SparseTensorMath.cpp:591 | ## 🐛 Bug
RuntimeError: !t.is_cuda() INTERNAL ASSERT FAILED at /pytorch/aten/src/ATen/native/sparse/SparseTensorMath.cpp:591
## To Reproduce
File "/home/jinzhu/pro/UIL/GraphMatch/layers.py", line 42, in forward
output = torch.spmm(adj, support)
RuntimeError: !t.is_cuda() INTERNAL ASSERT FAILED at /pytorch/aten/src/ATen/native/sparse/SparseTensorMath.cpp:591, please report a bug to PyTorch.
cc @vincentqb | module: sparse,triaged,module: assert failure | low | Critical |
516,010,604 | TypeScript | Provide a code action to replace a string with a template string | ## Suggestion
Provide a code action on a string to replace the string with a template string.
## Use Cases
Often you start with a normal string and notice that it should better be a template string. See the example below. When the cursor is inside the string, there should be code action provided 'Replace with template string'
<img width="300" alt="image" src="https://user-images.githubusercontent.com/172399/68016015-db3b4f00-fc93-11e9-88aa-b5677dc813fb.png">
The code action replace the string with a template string
<img width="300" alt="image" src="https://user-images.githubusercontent.com/172399/68016231-661c4980-fc94-11e9-9193-ca9737abe81c.png">
## Checklist
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, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
| Suggestion,Experience Enhancement | low | Minor |
516,024,783 | youtube-dl | Unsupported URL: tvzavr.ru | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.10.29. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.10.29**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- Single video: https://www.tvzavr.ru/film/rok1/
- Single video: https://www.tvzavr.ru/film/odin-den/
- Single video: https://www.tvzavr.ru/film/11-hd/
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
All video examples above plays fine in Google Chrome browser.
| site-support-request,geo-restricted | low | Critical |
516,039,993 | youtube-dl | Unsupported URL: ntvplus.tv | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.10.29. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.10.29**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- LiveTV stream: https://ntvplus.tv/channel/match-hd-336
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
LiveTV stream above plays fine in Google Chrome browser.
| site-support-request,geo-restricted | low | Critical |
516,044,883 | go | proposal: spec: anonymous struct literals | Currently it is not possible to write a struct literal without mentioning its type (with the exception of struct literals in map and slice composite literals). This can make it extraordinarily hard to write literals for some types. As an extreme example, consider writing a literal initializer for the [sarama.Config](https://godoc.org/github.com/Shopify/sarama#Config) type. All the unnamed struct types need to be written out explicitly, leading to a highly redundant expression 100s of lines long, and also fragile because any fields that are added will cause breakage.
I propose that Go adds a way of writing an anonymous struct literal - a struct literal that has no explicit type - by using the blank identifier (`_`) as a type name in a composite literal.
For example:
_{
Name: "Bob",
Age: 12,
}
Unlike other composite literals, it would require all members to be qualified with field names (no non-keyed elements).
Any field values in the literal that are const will remain const. If all fields in the literal are const, the entire literal is also considered considered const too, forming a *struct constant*.
For example:
const Bob = _{
Name: "Bob",
Age: 12,
}
const BobAge = Bob.Age
Like other constants, an untyped struct constant has a default type, which is the anonymous struct type with all fields converted to their default type.
So, for example, the default type of `_{}` is `struct{}`; the default type of `_{Name: "Bob", Age: 12}` is `struct{Name string, Age int}`.
An anonymous struct literal can be assigned to any struct type that contains a superset of the fields in the literal. Any const fields are treated with the usual const assignment rules. Fields that are not mentioned will be zero.
So, for example:
type Person struct {
Name string
Age uint32
}
var alice Person = _{
Name: "Alice",
Age: 32,
}
Unlike other struct literals, it would not be possible to use the `&` operator, so:
&_{Name: "Bob"}
would be invalid. There might be an argument for allowing assignment of an anonymous struct literal to a pointer type, so:
var P *Person = _{Name: "Bob"}
would be the same as:
var P *Person
var P1 Person = _{Name: "Bob"}
P = &P1
This would fit with the way that literal elements in map and slice literals work.
| LanguageChange,Proposal,dotdotdot,LanguageChangeReview | high | Critical |
516,080,655 | flutter | [in_app_purchase] Provide Documentation on "How to verify subscriptions status" | Is it possible to have some docs or guide about how to verify subscriptions status? Thanks in advance (in_app_purchase) | c: new feature,d: api docs,customer: crowd,p: in_app_purchase,package,team-ecosystem,P3,triaged-ecosystem | low | Major |
516,082,030 | material-ui | [Select] Consistency with Autocomplete | <!-- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
<!-- Describe how it should work. -->
Equivalent to [react-select](https://react-select.com/props#select-props)'s `isSearchable={false}`.
Disables the search functionality, but is still consistently styled.
## Examples 🌈
<!--
Provide a link to the Material design specification, other implementations,
or screenshots of the expected behavior.
-->
## Motivation 🔦
Having consistent styling of searchable and non-searchable selects is a requirement we're currently facing.
This workaround works: [https://codesandbox.io/s/material-demo-ok1kg](https://codesandbox.io/s/material-demo-ok1kg), but it's not exactly pretty.
<!--
What are you trying to accomplish? How has the lack of this feature affected you?
Providing context helps us come up with a solution that is most useful in the real world.
-->
EDIT:
Updated workaround with `readOnly` prop on input suggested by @cooperjones: https://codesandbox.io/s/material-demo-vh5lx | design: material,component: select,component: autocomplete | low | Major |
516,097,751 | youtube-dl | Unsupported URL: uma.media | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.10.29. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.10.29**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- LiveTV stream: https://uma.media/play/embed/636ffab27c5a4a9cd5f9a40b2e70ea88
- LiveTV stream: https://uma.media/play/embed/4ca525c601cc011f61348465fc6c09da
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
LiveTV streams above plays fine in Google Chrome browser. | site-support-request,geo-restricted | low | Critical |
516,120,555 | pytorch | Inconsistent documentation for in-place functions at https://pytorch.org/docs/stable/torch.html | ## 📚 Documentation
In-place functions are documented inconsistently. For example functions that generate samples from a distribution have a section called "In-place random sampling", however there is no other documentation for other in-place functions.
For example `pow_()` and `log_()` are not documented anywhere. Other in-place functions like `fill_()` are referenced in example code but not mentioned.
It would be good to document all in-place functions that are first-class citizens. Or tag functions in some way that have an in-place variant.
| module: docs,triaged | low | Major |
516,142,914 | vscode | [css] support css-variable completion in calc | Issue Type: <b>Bug</b>
The css variable doesn't auto complete in the calc function in the form of var(--css-variable), rather it just stay like this calc(--css-variable), but it is supposed to be like this calc(var(--css-variable)).
Thanks!
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18362
<details><summary>Extensions (19)</summary>
Extension|Author (truncated)|Version
---|---|---
ng-template|Ang|0.802.3
EditorConfig|Edi|0.14.2
vscode-npm-script|eg2|0.3.9
prettier-vscode|esb|2.3.0
php-intellisense|fel|2.3.12
auto-rename-tag|for|0.1.1
angular-essentials|joh|0.6.3
Angular2|joh|8.1.1
vscode-peacock|joh|3.1.6
vscode-language-babel|mgm|0.0.25
vscode-typescript-tslint-plugin|ms-|1.2.2
debugger-for-chrome|msj|4.12.1
angular2-inline|nat|0.0.17
incrementor|nms|0.1.0
angular-console|nrw|8.1.2
material-icon-theme|PKi|3.9.1
live-sass|rit|3.0.0
LiveServer|rit|5.6.1
JavaScriptSnippets|xab|1.7.2
(2 theme extensions excluded)
</details>
<!-- generated by issue reporter --> | feature-request,css-less-scss | low | Critical |
516,146,079 | godot | Integer underflows, overflows and lossy conversions between types | **Godot version:**
3.2.alpha.custom_build. 99cee9038
**OS/device including version:**
Ubuntu 19.10
**Issue description:**
When I compile Godot with all Undefinied Sanitizer options, then I see a lot of errors.
To see errors you need to compile Godot with sanitizers support and special ubsan arguments(integrated into this repository - https://github.com/qarmin/godot/tree/bb) and use LLVM(doesn't work on Windows and it is a little unstable(crashes a lot))
```
scons p=x11 -j6 use_lsan=yes use_asan=yes use_ubsan=yes use_llvm=yes
```
If you don't want to compile godot, then this is compiled version with support of ubsan sanitizer(Linux )
https://www.easypaste.org/file/s3PqQiaT/godot.x11.tools.64.llvms.tar.gz (size ~180MB, Github doesn't allow to host so big files and it will only be active some time)
Issues
```
core/class_db.cpp:440:29: runtime error: implicit conversion from type 'int' of value -1 (32-bit, signed) to type 'uint64_t' (aka 'unsigned long') changed the value to 18446744073709551615 (64-bit, unsigned)
core/command_queue_mt.h:331:48: runtime error: implicit conversion from type 'int' of value -8 (32-bit, signed) to type 'unsigned long' changed the value to 18446744073709551608 (64-bit, unsigned)
core/command_queue_mt.h:373:41: runtime error: implicit conversion from type 'int' of value -8 (32-bit, signed) to type 'unsigned long' changed the value to 18446744073709551608 (64-bit, unsigned)
core/command_queue_mt.h:431:42: runtime error: implicit conversion from type 'int' of value -2 (32-bit, signed) to type 'unsigned int' changed the value to 4294967294 (32-bit, unsigned)
core/hashfuncs.h:102:24: runtime error: unsigned integer overflow: 3419404768 + 3596517327 cannot be represented in type 'unsigned int'
core/hashfuncs.h:119:24: runtime error: unsigned integer overflow: 12770922021182837856 + 14810610120747550883 cannot be represented in type 'unsigned long'
core/hashfuncs.h:57:23: runtime error: unsigned integer overflow: 2402952384 + 2088358182 cannot be represented in type 'unsigned int'
core/hashfuncs.h:74:34: runtime error: unsigned integer overflow: 5863209 + 4294966197 cannot be represented in type 'unsigned int'
core/hashfuncs.h:79:11: runtime error: unsigned integer overflow: 13854873893642593893 + 7378697629483925504 cannot be represented in type 'unsigned long'
core/hashfuncs.h:79:11: runtime error: unsigned integer overflow: 18446744073709551613 + 524288 cannot be represented in type 'unsigned long'
core/hashfuncs.h:81:8: runtime error: unsigned integer overflow: 13839561648464986112 * 21 cannot be represented in type 'unsigned long'
core/hashfuncs.h:81:8: runtime error: unsigned integer overflow: 9547524425524499183 * 21 cannot be represented in type 'unsigned long'
core/hashfuncs.h:83:8: runtime error: unsigned integer overflow: 13931839403097828352 + 6194006260202536960 cannot be represented in type 'unsigned long'
core/hashfuncs.h:83:8: runtime error: unsigned integer overflow: 16024871226882627506 + 11020834466462821504 cannot be represented in type 'unsigned long'
core/hashfuncs.h:85:9: runtime error: implicit conversion from type 'int' of value -251287892 (32-bit, signed) to type 'uint32_t' (aka 'unsigned int') changed the value to 4043679404 (32-bit, unsigned)
core/hashfuncs.h:85:9: runtime error: implicit conversion from type 'int' of value -399682699 (32-bit, signed) to type 'uint32_t' (aka 'unsigned int') changed the value to 3895284597 (32-bit, unsigned)
core/image.cpp:1287:15: runtime error: unsigned integer overflow: 0 - 1 cannot be represented in type 'uint32_t' (aka 'unsigned int')
core/image.cpp:658:40: runtime error: unsigned integer overflow: 37376 - 37632 cannot be represented in type 'unsigned int'
core/image.cpp:659:42: runtime error: unsigned integer overflow: 37376 - 37632 cannot be represented in type 'unsigned int'
core/image.cpp:660:51: runtime error: unsigned integer overflow: 18688 - 35072 cannot be represented in type 'unsigned int'
core/io/resource_loader.h:135:94: runtime error: unsigned integer overflow: 3661741246 + 715307540 cannot be represented in type 'unsigned int'
core/io/resource_loader.h:135:94: runtime error: unsigned integer overflow: 4017695364 + 715307540 cannot be represented in type 'unsigned int'
core/io/resource_loader.h:135:94: runtime error: unsigned integer overflow: 4107908486 + 715307540 cannot be represented in type 'unsigned int'
core/io/resource_loader.h:135:94: runtime error: unsigned integer overflow: 4216973687 + 715307540 cannot be represented in type 'unsigned int'
core/math/random_pcg.cpp:42:45: runtime error: unsigned integer overflow: 2832489 * 12114003972236794897 cannot be represented in type 'unsigned long'
core/math/random_pcg.cpp:42:45: runtime error: unsigned integer overflow: 2905591 * 12114003972236794897 cannot be represented in type 'unsigned long'
core/math/random_pcg.cpp:42:57: runtime error: unsigned integer overflow: 17405449380241845078 + 1442695040888963407 cannot be represented in type 'unsigned long long'
core/method_bind.gen.inc:681:17: runtime error: implicit conversion from type 'VisualShaderNodeCubeMap::Source' of value 3200171710 (32-bit, unsigned) to type 'int' changed the value to -1094795586 (32-bit, signed)
core/oa_hash_map.h:77:17: runtime error: unsigned integer overflow: 0 - 61 cannot be represented in type 'unsigned int'
core/oa_hash_map.h:77:32: runtime error: unsigned integer overflow: 4294967235 + 64 cannot be represented in type 'unsigned int'
core/typedefs.h:177:2: runtime error: unsigned integer overflow: 0 - 1 cannot be represented in type 'unsigned int'
core/typedefs.h:184:9: runtime error: unsigned integer overflow: 4294967295 + 1 cannot be represented in type 'unsigned int'
core/ustring.cpp:1409:17: runtime error: implicit conversion from type 'char' of value -60 (8-bit, signed) to type 'uint8_t' (aka 'unsigned char') changed the value to 196 (8-bit, unsigned)
core/ustring.cpp:2205:25: runtime error: unsigned integer overflow: 2459999264 + 2090140897 cannot be represented in type 'unsigned int'
core/ustring.cpp:2248:25: runtime error: unsigned integer overflow: 2434698624 + 2089350252 cannot be represented in type 'unsigned int'
core/variant.cpp:1189:20: runtime error: implicit conversion from type 'int64_t' (aka 'long') of value -1 (64-bit, signed) to type 'unsigned int' changed the value to 4294967295 (32-bit, unsigned)
core/variant.cpp:2162:15: runtime error: implicit conversion from type 'uint64_t' (aka 'unsigned long') of value 12047754176567800795 (64-bit, unsigned) to type 'int64_t' (aka 'long') changed the value to -6398989897141750821 (64-bit, signed)
core/variant.cpp:2690:11: runtime error: implicit conversion from type 'int64_t' (aka 'long') of value -1 (64-bit, signed) to type 'uint32_t' (aka 'unsigned int') changed the value to 4294967295 (32-bit, unsigned)
core/variant.cpp:2808:11: runtime error: implicit conversion from type 'uint64_t' (aka 'unsigned long') of value 107271114928693 (64-bit, unsigned) to type 'uint32_t' (aka 'unsigned int') changed the value to 11743797 (32-bit, unsigned)
drivers/gles2/rasterizer_storage_gles2.cpp:540:14: runtime error: implicit conversion from type 'int' of value -2 (32-bit, signed) to type 'unsigned int' changed the value to 4294967294 (32-bit, unsigned)
drivers/gles2/shader_gles2.cpp:186:48: runtime error: implicit conversion from type 'int' of value -2147483648 (32-bit, signed) to type 'unsigned int' changed the value to 2147483648 (32-bit, unsigned)
drivers/gles2/shader_gles2.h:262:38: runtime error: implicit conversion from type 'int' of value -2147483648 (32-bit, signed) to type 'unsigned int' changed the value to 2147483648 (32-bit, unsigned)
drivers/gles2/shader_gles2.h:264:38: runtime error: implicit conversion from type 'int' of value -17 (32-bit, signed) to type 'unsigned int' changed the value to 4294967279 (32-bit, unsigned)
drivers/gles3/rasterizer_scene_gles3.cpp:2434:57: runtime error: unsigned integer overflow: 18446744073709551489 + 128 cannot be represented in type 'unsigned long'
drivers/gles3/rasterizer_storage_gles3.cpp:627:14: runtime error: implicit conversion from type 'int' of value -2 (32-bit, signed) to type 'unsigned int' changed the value to 4294967294 (32-bit, unsigned)
drivers/gles3/shader_gles3.cpp:535:15: runtime error: implicit conversion from type 'GLuint' (aka 'unsigned int') of value 4294967295 (32-bit, unsigned) to type 'GLint' (aka 'int') changed the value to -1 (32-bit, signed)
drivers/gles3/shader_gles3.h:389:38: runtime error: implicit conversion from type 'int' of value -5 (32-bit, signed) to type 'unsigned int' changed the value to 4294967291 (32-bit, unsigned)
drivers/png/image_loader_png.cpp:67:51: runtime error: implicit conversion from type 'int' of value -1 (32-bit, signed) to type 'size_t' (aka 'unsigned long') changed the value to 18446744073709551615 (64-bit, unsigned)
drivers/unix/net_socket_posix.cpp:689:9: runtime error: implicit conversion from type 'unsigned long' of value 140484085286312 (64-bit, unsigned) to type 'int' changed the value to 1448 (32-bit, signed)
editor/editor_sectioned_inspector.cpp:311:7: runtime error: implicit conversion from type 'int' of value -1 (32-bit, signed) to type 'ObjectID' (aka 'unsigned long') changed the value to 18446744073709551615 (64-bit, unsigned)
main/main.cpp:1352:43: runtime error: implicit conversion from type 'uint64_t' (aka 'unsigned long') of value 16189665037908562130 (64-bit, unsigned) to type 'int64_t' (aka 'long') changed the value to -2257079035800989486 (64-bit, signed)
modules/csg/csg.h:136:26: runtime error: implicit conversion from type 'int32_t' (aka 'int') of value -99 (32-bit, signed) to type 'uint32_t' (aka 'unsigned int') changed the value to 4294967197 (32-bit, unsigned)
modules/gridmap/grid_map_editor_plugin.cpp:43:16: runtime error: upcast of misaligned address 0xbebebebebebebebe for type 'GridMap', which requires 8 byte alignment
modules/visual_script/visual_script.cpp:1290:24: runtime error: load of value 190, which is not a valid value for type 'bool'
platform/x11/os_x11.cpp:1807:28: runtime error: implicit conversion from type 'int' of value -2 (32-bit, signed) to type 'unsigned int' changed the value to 4294967294 (32-bit, unsigned)
platform/x11/os_x11.cpp:1808:28: runtime error: implicit conversion from type 'int' of value -5 (32-bit, signed) to type 'unsigned int' changed the value to 4294967291 (32-bit, unsigned)
scene/2d/tile_map.cpp:1236:15: runtime error: implicit conversion from type 'uint16_t' (aka 'unsigned short') of value 65535 (16-bit, unsigned) to type 'int16_t' (aka 'short') changed the value to -1 (16-bit, signed)
scene/2d/tile_map.cpp:1241:24: runtime error: implicit conversion from type 'int' of value -2147483648 (32-bit, signed) to type 'unsigned int' changed the value to 2147483648 (32-bit, unsigned)
scene/resources/audio_stream_sample.cpp:98:15: runtime error: unsigned integer overflow: 0 - 1 cannot be represented in type 'uint32_t' (aka 'unsigned int')
scene/resources/ray_shape.cpp:48:24: runtime error: load of value 190, which is not a valid value for type 'bool'
scene/resources/visual_shader_nodes.cpp:850:9: runtime error: load of value 3200171710, which is not a valid value for type 'VisualShaderNodeCubeMap::Source'
servers/physics_2d/broad_phase_2d_hash_grid.h:144:10: runtime error: unsigned integer overflow: 18437737054752470420 + 17870294860456355072 cannot be represented in type 'unsigned long'
servers/physics_2d/broad_phase_2d_hash_grid.h:146:11: runtime error: implicit conversion from type 'uint64_t' (aka 'unsigned long') of value 9216652941687007833 (64-bit, unsigned) to type 'uint32_t' (aka 'unsigned int') changed the value to 3209701977 (32-bit, unsigned)
servers/visual_server.cpp:1013:27: runtime error: implicit conversion from type 'int' of value -262145 (32-bit, signed) to type 'unsigned int' changed the value to 4294705151 (32-bit, unsigned)
```
**Minimal reproduction project:**
Any project
| bug,topic:buildsystem | low | Critical |
516,158,688 | pytorch | Move allgather_coalesced functionality to comm.cpp. | ## 🚀 Feature
Move allgather_coalesced functionality to comm.cpp.
## Motivation
allgather_coalesced does not rely on any backend specific functionality as it just uses process group's allgather. Therefore, by moving it to some more generic place we can get all supported usecases of allgather to be supported for allgather_coalesced
## Additional context
This was requested as a part of review of PR 28857 https://github.com/pytorch/pytorch/pull/28857
cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 | oncall: distributed,triaged | low | Minor |
516,241,219 | pytorch | Support clang+cuda builds | ## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
This feature request is to officially support building CUDA code with clang and include this build in CI.
This build is not officially supported. (https://github.com/pytorch/pytorch/issues/28417#issuecomment-546501812). There has also been related bug reports (e.g. https://github.com/pytorch/pytorch/issues/28417).
## Motivation
Due to the lack of C API and the instability of C++ ABI, compiling PyTroch / libtorch from source is often needed to integrate PyTorch runtime in a C++ code base. If the C++ code base is built by clang (including CUDA), the same tool chain needs to work with PyTorch as well.
## Pitch
Support building CUDA code with clang and include this build in CI.
## Alternatives
The alternative is to have an official C API so that we have stable ABI for a pre-built libtorch library..
## Additional context
<!-- Add any other context or screenshots about the feature request here. -->
| module: build,triaged,enhancement | low | Critical |
516,257,035 | pytorch | Add Wishart and inverse-Wishart distributions | ## 🚀 Feature
Implement the positive-definite-matrix-valued Wishart and inverse-Wishart distributions, currently missing from `torch.distributions`.
## Motivation
These distributions often pop up in Bayesian analysis as the conjugate priors for the covariance or precision matrix of the multivariate Gaussian. It would be great to have an official, GPU-accelerated, `torch.distributions`-compatible implementation available to everyone. This feature already exists in [TensorFlow Probability](https://www.tensorflow.org/probability/api_docs/python/tfp/distributions/Wishart), for example.
<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
## Pitch
I already have a working implementation I wrote for a personal project (involving Bayesian mixture models), extending [`ExponentialFamily`](https://pytorch.org/docs/stable/distributions.html#exponentialfamily). Other than the basic methods, it currently includes:
- reparametrised sampling (`rsample`), based on some background research (some refs. below);
- efficient computations using Cholesky factors;
- unit tests for output shapes, for different combinations of batch and sample shapes;
- unit tests for correctness of `log_prob` and `entropy` vs. [`scipy.stats.wishart`](https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.wishart.html);
- statistical tests show sample statistics (e.g. means, determinants) are indistinguishable vs. [`scipy.stats.wishart`](https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.wishart.html).
Would there be any interest in integrating this into the `torch.distributions` codebase? I'd be happy to make the necessary changes to harmonise style, documentation, and unit-test format.
<!-- A clear and concise description of what you want to happen. -->
## Alternatives
Currently the way to use Wishart distributions in a PyTorch project would be to go through NumPy and use [`scipy.stats.wishart`](https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.wishart.html). This has a couple of big limitations:
- need to copy data between CPU and GPU;
- no support for batched parameters or arguments (e.g. to `wishart.logpdf()`).
<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->
## References
- Sawyer, S. (2007). Wishart Distributions and Inverse-Wishart Sampling. https://www.math.wustl.edu/~sawyer/hmhandouts/Wishart.pdf
- Anderson, T. W. (2003). An Introduction to Multivariate Statistical Analysis (3rd ed.). John Wiley & Sons, Inc.
- Odell, P. L. & Feiveson, A. H. (1966). A Numerical Procedure to Generate a Sample Covariance Matrix. Journal of the American Statistical Association, 61(313):199-203.
- Ku, Y.-C. & Blomfield, P. (2010). Generating Random Wishart Matrices with Fractional Degrees of Freedom in OX.
cc `torch.distribution` maintainers @fritzo @neerajprad @alicanb @vishwakftw
cc @vincentqb @fritzo @neerajprad @alicanb @vishwakftw | module: distributions,feature,triaged | medium | Major |
516,271,923 | go | proposal: crypto/tls: add support for delegated credentials | This proposal is to add support to the `crypto/tls` package for the new cryptographic protocol, [delegated credentials](https://tools.ietf.org/html/draft-ietf-tls-subcerts-02), which will be an extension to TLS. It's currently in the process of being adopted as a standard by the IETF.
Some benefits:
Key protection: rather than deploying the actual private key associated with the certificate that was issued to you by the CA to each server that fronts TLS, one can instead create and issue a delegated credential. This credential can have a much shorter life span than that of the original certificate and one does not need to contact the CA to have it provisioned each time. The client can still verify the chain of trust as the delegated credential is still signed by the certificate obtained by the CA.
Experimentation for new PK algorithms: in addition to the security benefits it provides to protecting keys, it enables for servers to experiment rolling out support for new authentication mechanisms which are tied to the certificate being served. Essentially, the server can try out a new authentication type without altering the certificate the was issued to them by the CA.
Concerns:
- I am not sure about Go's policy for adding support of draft RFC's to the standard library, although this one seems promising in that it will land? Thoughts?
---
_Cc: @FiloSottile_ | Proposal,Proposal-Hold,Proposal-Crypto | low | Major |
516,307,155 | pytorch | Docker issue for Pytorch 1.3 | The issue is related to the issues:
https://github.com/NVIDIA/apex/issues/486
https://github.com/NVIDIA/apex/pull/490
When I try to compline mmdetection with pytorch 1.3 docker I get an error that can be fixed by defining a few environmental variables. It would be nice to be able to perform a compilation without doing these extra steps:
Works with pytorch 1.2
```
ARG PYTORCH="1.1.0"
ARG CUDA="10.0"
ARG CUDNN="7.5"
FROM pytorch/pytorch:${PYTORCH}-cuda${CUDA}-cudnn${CUDNN}-devel
RUN apt-get update && apt-get install -y libglib2.0-0 libsm6 libxrender-dev libxext6 \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
# Install mmdetection
RUN conda install cython -y && conda clean --all
RUN git clone https://github.com/open-mmlab/mmdetection.git /mmdetection
WORKDIR /mmdetection
RUN pip install --no-cache-dir -e .
```
After changing to
```
ARG PYTORCH="1.3"
ARG CUDA="10.1"
ARG CUDNN="7"
```
the build breaks.
And it can be fixed only by defining new environment variables.
```
ENV TORCH_CUDA_ARCH_LIST="6.0 6.1 7.0+PTX"
ENV TORCH_NVCC_FLAGS="-Xfatbin -compress-all"
ENV CMAKE_PREFIX_PATH="$(dirname $(which conda))/../"
```
cc @ezyang | module: binaries,module: build,triaged,module: docker | low | Critical |
516,315,320 | rust | Supplying an &&str when an &str is expected missing a suggestion | ```
let a = std::collections::HashMap::<String,String>::new();
let s = "hello";
let _b = a[&s];
^ & not needed, this is already a reference
```
[playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=5683da2c27bfe291e8f6c2ba766ea07b)
But the error we currently get is:
```
error[E0277]: the trait bound `std::string::String: std::borrow::Borrow<&str>` is not satisfied
--> src/main.rs:4:14
|
4 | let _b = a[&s];
| ^^^^^ the trait `std::borrow::Borrow<&str>` is not implemented for `std::string::String`
|
= help: the following implementations were found:
<std::string::String as std::borrow::Borrow<str>>
= note: required because of the requirements on the impl of `std::ops::Index<&&str>` for `std::collections::HashMap<std::string::String, std::string::String>`
```
Adding one too many layers of indirection is fairly common in rust especially with String / &str so it would be excellent if Rust could hint to the user how to fix this. | C-enhancement,A-diagnostics,T-compiler,A-suggestion-diagnostics,D-papercut | low | Critical |
516,325,885 | TypeScript | Using the "in" operator should make bracket access safe on an object | ## Search Terms
object in keyof bracket operator in
## Suggestion
Checking a key with the "in" operator on an object should make it safe to to use in brackets
## Use Cases
Useful when writing functions that process input JSON/doesn't have a concrete type.
## Examples
```
// Ideally this uses TypeScripts control flow logic to allow the bracket access.
function getPropFailsToCompile(data: object, key: string): any {
if (!(key in data)) {
throw new Error("Data is malformed")
}
return data[key]
}
// Compiles but keyof object has type 'never' in Typescript
function getPropCompilesButNotReasonable(data: object, key: keyof object): any {
if (!(key in data)) {
throw new Error("Data is malformed")
}
return data[key]
}
// Best way I've gotten this to work.
function getPropWorks(data: object, key: string): any {
if (!(key in data)) {
throw new Error("Data is malformed")
}
return (<any>data)[key]
}
```
## Checklist
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, etc.)
* [ x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
| Suggestion,Awaiting More Feedback | low | Critical |
516,353,958 | flutter | Navigator should notify when a Screen regains focus/reappears | I'm working on a implementation of React Portals for flutter, For now, the way it works is that everytime a portalcontainer is built , it updates a portalplaceholder in another part of the widget tree . I can safely update and implement this when Navigating forward , since it triggers initState , but when navigating backwards i can't use the dispose method, at least i can't when there is nested navigators , wich my app implements.
So it would be nice if the Navigator called a method like initState and dispose when the app navigated back to that previous route. I know is as easy as calling route.willGainFocus() , and then overriding that in the Widget. So it's just an idea that i would like to suggest | c: new feature,framework,d: api docs,f: routes,P2,team-framework,triaged-framework | low | Minor |
516,354,009 | pytorch | Trace of torch.tensor is impressively convoluted | ```
def test_trace_modern_ctor(self):
class MyModule(nn.Module):
def forward(self, x):
return torch.tensor([0.0])
# Shouldn't fail sanity checks
traced_rec = torch.jit.trace(MyModule(), torch.randn(2, 2))
print(traced_rec.graph)
```
gives the trace
```
graph(%self : ClassType<Module>,
%1 : Double(2, 2)):
%2 : Double(1) = prim::Constant[value={0}](), scope: MyModule # test/test_jit.py:321:0
%3 : Device = prim::Constant[value="cpu"](), scope: MyModule # test/test_jit.py:321:0
%4 : int = prim::Constant[value=7](), scope: MyModule # test/test_jit.py:321:0
%5 : bool = prim::Constant[value=0](), scope: MyModule # test/test_jit.py:321:0
%6 : bool = prim::Constant[value=0](), scope: MyModule # test/test_jit.py:321:0
%7 : None = prim::Constant(), scope: MyModule
%8 : Double(1) = aten::to(%2, %3, %4, %5, %6, %7), scope: MyModule # test/test_jit.py:321:0
%9 : Double(1) = aten::detach(%8), scope: MyModule # test/test_jit.py:321:0
return (%9)
```
This is way more nodes than I expected to see.
cc @suo | oncall: jit,triaged | low | Minor |
516,374,583 | flutter | Implement textWidthBasis on the Web | We are failing some of our `text_test.dart` tests because we do not respect `textWidthBasis`.
/cc @mdebbar | a: tests,framework,f: material design,a: fidelity,platform-web,P2,c: parity,team: skip-test,team-web,triaged-web | low | Minor |
516,386,462 | rust | Struct with allow(dead_code) on an associated function doesn't provoke a warning when unused | https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=200a3cd3b522382da55883b4b12d3872
```rust
#[warn(dead_code)]
struct U(u64);
impl U {
#[allow(dead_code)]
pub fn foo() {}
}
fn main() {
}
```
In this example, whether there is or not `warn(dead_code)`, there's no warning when the struct is unused. | A-lints,T-compiler,L-dead_code | low | Critical |
516,390,013 | rust | Chain iterator adaptor shold drop exhausted subiterator | Consider the following program:
```rust
use std::sync::mpsc::channel;
fn main() {
let (sender, reciever) = channel();
let source = (1..10).map(move |i| {sender.send(i).unwrap(); i});
let sink = reciever;
let iter = source.chain(sink);
for x in iter {
println!("{}", x);
}
println!("done");
}
```
Currently, it deadlocks. It can be argued, however, that this program should finish, given that "equivalent" program without chain finishes:
```rust
use std::sync::mpsc::channel;
fn main() {
let (sender, reciever) = channel();
let source = (1..10).map(move |i| {sender.send(i).unwrap(); i});
let sink = reciever;
for x in source {
println!("{}", x)
}
for x in sink {
println!("{}", x);
}
println!("done");
}
```
I think this can be achieved by changing the `Chain` definition from
```rust
struct Chain<A, B> {
left: A,
right: B,
state: State,
}
enum State { Left, Right, Both }
```
to
```rust
struct Chain<A, B> {
state: State<A, B>,
}
enum State<A, B> { Left(A), Right(B), Both(A, B) }
```
this will require some unsafe code to flip from `Both` to `Left`, using only `&mut Both`, but should be doable.
Context: I've discovered similarly-shaped code when trying to simplify [this code](https://github.com/async-rs/async-std/pull/419/files#diff-c497dc8de6d1e1471ddca482854b7634R137). Basically, this is an event loop, which works on the stream of events, and some events can feed new events back into the loop. The goal is to make sure the loop is cleanly exhausted.
Not sure if this actually worth it, given super-obscure use-case and potential complications during implementation...
cc @bluss | C-enhancement,T-libs-api,A-iterators | low | Minor |
516,390,400 | flutter | Improve fidelity of multi-pointer tap and long press gestures | The current implementation of `PrimaryPointerGestureRecognizer` does not precisely reflect the OEM behavior, which affects tap and long press.
Take tap as an example. Consider a button being tapped by 2 pointers (fingers) in the following sequence:
> down1, down2, up1, up2
The OEM behavior is different on different platforms:
- On Android, the `onTapUp` is triggered on `up2`
- On iOS, the `onTapUp` is triggered on `up1`
Currently Flutter's behaves the same way as iOS.
This issue also affects long press, except that it's the timing of `onLongPress` that is different.
- Flutter version: 93ab9e64e71d8296f3130f8a445e9facdeb2590d | platform-android,framework,a: fidelity,f: gestures,P3,team-android,triaged-android | low | Minor |
516,392,639 | TypeScript | Report candidates on closing list terminators | From @robpalme: https://twitter.com/robpalmer2/status/1190383568612184064
```ts
function base_init() {
{
}
function me() {
}
```
https://www.typescriptlang.org/play/?ssl=8&ssc=1&pln=9&pc=1#code/GYVwdgxgLglg9mABAIwIYGcCmB9GYZQAUAlIgN4BQliNiFAvhRbYqJLAogLaYnnO0GFIA
# Motivation
When an ending curly brace (or similar) is missing, we can give some better hints to the user.
In some cases, this might be because a stray `}` throws parsing off.
# Suggestion
It would be very cool to explain a possible reason that the user is getting a `'}' expected` error:
> ```
> }
> ~
> This '}' occurs at the same indentation level, but corresponds to a different brace.
> ```
| Effort: Difficult,Domain: Error Messages,Experience Enhancement | low | Critical |
516,419,984 | flutter | Use unified logging instead of syslog on iOS 13+ | ## Proposal
syslog stopped working on iOS 13. Use os_log unified logging instead of syslog or ASL. | platform-ios,engine,P2,team-ios,triaged-ios | low | Minor |
516,486,743 | flutter | Machine readable output from "flutter build" | Make output from "flutter build" consistent and machine readable. This is related to #8351 (the consistency part), but has different use cases.
## Use case
1. There are automation tools out in the wild, such as [fastlane](https://fastlane.tools/) which help us sign and publish artifacts to Play Store, App Store (iTunes) etc.
These tools benefit from knowing Application ID (aka Bundle ID) and path to flutter-built artifacts. Manually specifying these parameters for every developed application is tedious and prone to errors, which are often discovered late, once the publish process is already broken on CI.
1. Another use case is automated artifact upload, which needs to know output binary file paths.
## Proposal
Make "flutter build" output [optionally] machine-readable, printing the list of outputs (e.g. when building split APK) and Application ID / Bundle ID (which is available via `ApplicationPackage.id`), e.g. in JSON or other parse-able format:
```shell
$ flutter build apk --split-per-abi --debug --machine
< verbose output logged to stderr >
[{
"apk": "./build/outputs/app.apk",
"id": "com.example.application",
"abi": "armv7"
},
{
"apk": "./build/outputs/app.apk",
"id": "com.example.application",
"abi": "x86"
}]
```
or
```shell
$ flutter build apk --debug
< verbose output logged to stderr >
Built ./build/outputs/app.apk (com.example.application).
```
| c: new feature,tool,P3,team-tool,triaged-tool | low | Critical |
516,492,735 | rust | Improve error message when an operator is only implemented for references of a given type | If an operator (for example `std::ops::Sub`) is only implemented for references of a given type and you try to subtract two instances of that type directly, the error message doesn't give a clue that an implementation for references exists.
```rust
use std::ops::Sub;
struct Foo {}
impl Sub<&Foo> for &Foo {
type Output = Foo;
fn sub(self, other: &Foo) -> Self::Output {
Foo {}
}
}
fn main() {
let a = Foo {};
let b = Foo {};
let c = a - b; // correctly fails, because `Sub` is only implemented for references
// let c = &a - &b; works
}
```
```
error[E0369]: binary operation `-` cannot be applied to type `Foo`
--> src/main.rs:17:15
|
17 | let c = a - b;
| - ^ - Foo
| |
| Foo
|
= note: an implementation of `std::ops::Sub` might be missing for `Foo`
```
It would be nice if the error message said something like:
```
= note: an implementation of `std::ops::Sub` might be missing for `Foo`
= note: an implementation of `std::ops::Sub` exists for `&Foo`
```
… or even suggested to try `&a - &b` instead.
---
I came across this when trying to subtract two `IndexSet`s (from the `indexmap` crate). I saw in the documentation that there was `Sub` implemented, but the compiler complained that subtracting was not possible. It took me a while to figure out that i had to add two `&`s. | C-enhancement,A-diagnostics,A-trait-system,T-compiler,A-suggestion-diagnostics,D-papercut,D-terse | low | Critical |
516,545,983 | flutter | Add more control over RenderSliverMultiBoxAdaptor | ## Use case
I want to create my own `RenderSliver` which would subclassing `RenderSliverMultiBoxAdaptor`. In my custom `RenderSliver`, I want to be able to create or destroy child in any order. To do that I would need to use `_createOrObtainChild` and `_destroyOrCacheChild`. These methods are private to the library thus, I cannot use them.
## Proposal
Rename `_createOrObtainChild` and `_destroyOrCacheChild` to `createOrObtainChild` and `destroyOrCacheChild` and annotate them with `@protected`.
What do you think about that? Does it seem reasonable?
| c: new feature,framework,f: scrolling,P3,team-framework,triaged-framework | low | Minor |
516,563,176 | react | React DevTools w/ Electron: Profiler "Reload and start profiling" doesn't work due to XMLHttpRequest 'null' origin | **Do you want to request a *feature* or report a *bug*?**
An error gets thrown when using DevTools Profiler on **Electron** with the "**Reload and start profiling**" feature that leaves Profiler in an unexpected state - the profiling session does not end.
I initially opened [the issue over at Electron](https://github.com/electron/electron/issues/20915), but [got asked to get your opinion first](https://github.com/electron/electron/issues/20915#issuecomment-548996868).
**What is the current behavior?**
- Open React DevTools Profiler in **Electron**
- Click "Reload and start profiling"
- Await reload
- Do actions
- Click "Stop profiling" - does not work
- Because there are errors in console (actually thrown immediately after reload, don't have to do any extra actions):
```
Access to XMLHttpRequest at 'chrome-extension://react-developer-tools/build/renderer.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, https.
```
```
Uncaught DOMException: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'chrome-extension://react-developer-tools/build/renderer.js'.
```
**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**
You'll have to use [Electron Fiddle](https://github.com/electron/fiddle) for this one with this gist: https://gist.github.com/joltmode/82574cab4970def210dac0c68d4c34b8
**What is the expected behavior?**
- Open React DevTools Profiler
- Click "Reload and start profiling"
- Await reload
- Do actions
- Click "Stop profiling"
- See profiler results
**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
- React 16.11.0
- Latest version of DevTools
- Electron 6.1.2 | Type: Discussion,Component: Developer Tools | medium | Critical |
516,570,781 | go | cmd/cgo: inject preamble before other include directives | ### What version of Go are you using (`go version`)?
<pre>go version go1.13.3 linux/amd64</pre>
### Does this issue reproduce with the latest release?
Yes
### What did you see?
The cgo generated file `_cgo_export.c` includes `stdlib.h` before anything else (see [here](https://github.com/golang/go/blob/8de0bb77ebc3408a586ad96a3c9ae9c231fd15a3/src/cmd/cgo/out.go#L811)). It precludes the possibility to use some "include first" headers without errors or warnings, such as Python.
From the Python docs:
```Since Python may define some pre-processor definitions which affect the standard headers on some systems, you must include Python.h before any standard headers are included.```
Cgo should allow to inject a C preamble before any other include directive. | help wanted,NeedsInvestigation,FeatureRequest,compiler/runtime | medium | Critical |
516,611,913 | flutter | Flutter SDK hangs while building pub.dart.snapshot on ArchLinux Docker when there are missing system dependencies | Building the following Dockerfile:
```Dockerfile
FROM archlinux/base
RUN pacman -Sy bash curl git unzip --noconfirm
RUN git clone -b "stable" https://github.com/flutter/flutter.git "$HOME/flutter"
RUN "$HOME/flutter/bin/flutter" channel "stable"
RUN "$HOME/flutter/bin/flutter" doctor
```
hangs while building a snapshot:
```
$ docker build -f flutter_archlinux.Dockerfile .
Sending build context to Docker daemon 646.7kB
Step 1/5 : FROM archlinux/base
---> c767d90efdb9
Step 2/5 : RUN pacman -Sy bash curl git unzip --noconfirm
---> Using cache
---> 09d34d647279
Step 3/5 : RUN git clone -b "stable" https://github.com/flutter/flutter.git "$HOME/flutter"
---> Using cache
---> a2e793e6ff79
Step 4/5 : RUN "$HOME/flutter/bin/flutter" channel "stable"
---> Running in 758d6340502a
Downloading Dart SDK from Flutter engine b863200c37df4ed378042de11c4e9ff34e4e58c9...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 264M 100 264M 0 0 6923k 0 0:00:39 0:00:39 --:--:-- 8369k
Building flutter tool...
```
(From another shell on the same container):
```
# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 7208 3596 ? Ss 14:05 0:00 bash /root/flutter/bin/flutter --verbose channel stable
root 12 0.0 0.0 7340 1916 ? S 14:05 0:00 bash /root/flutter/bin/flutter --verbose channel stable
root 118 0.0 0.0 7340 1864 ? S 14:06 0:00 bash /root/flutter/bin/flutter --verbose channel stable
root 119 177 1.3 1555424 219396 ? Sl 14:06 31:08 /root/flutter/bin/cache/dart-sdk/bin/dart /root/flutter/bin/cache/dart-sdk/bin/snapshots/pub.dart.snapshot upgrade --verbosity
root 148 0.0 0.0 7472 4216 pts/0 Ss 14:06 0:00 bash
root 386 0.0 0.0 12848 3172 pts/0 R+ 14:23 0:00 ps aux
```
On the other hand, building the following Docker image succeeds:
```Dockerfile
FROM archlinux/base
RUN pacman -Sy bash curl git tar unzip which xz --noconfirm
RUN git clone -b "stable" https://github.com/flutter/flutter.git "$HOME/flutter"
RUN "$HOME/flutter/bin/flutter" --verbose channel "stable"
RUN "$HOME/flutter/bin/flutter" doctor
```
| c: crash,tool,dependency: dart,platform-linux,e: OS-version specific,P2,team-tool,triaged-tool | low | Minor |
516,628,338 | pytorch | [FR] script returns subclass of the original module class | ## 🚀 Feature
I would love `jit.script`ed modules to be subclasses of the original ones. Currently, the returned modules are of the same `RecursiveScriptModule` type, making them unusable with `isinstance` calls. While one can get the original name of the module, there is no general way to make the same function work for a regular module and a `RecursiveScriptModule`.
E.g., the following extremely common pattern is not doable with a `RecursiveScriptModule`. And in fact can silently cause correctness issues unless one manually asserts that `m` is of a known type.
```py
def init(m):
if isinstance(m, (nn.Linear, nn.Conv2d):
nn.init.orthogonal_(m.weight)
if getattr(m, 'bias', None) is not None:
nn.init.zeros_(m.bias)
net.apply(init)
```
cc @gmagogsfm @suo | triage review,oncall: jit,triaged,TSUsability,TSRootCause:ModuleInheritance | low | Minor |
516,637,991 | TypeScript | Automatic Brace Insertion (ABI) is undesirable | **TypeScript Version:** 3.7-beta
**Search Terms:** automatic brace insertion ABI syntax error
**Code:**
```ts
function a() {
"Automatic Brace Insertion! (ABI)";
```
**Expected behavior:**
The input is syntactically invalid, so emit should fail regardless of the state of `noEmitOnError`. Other forms of un-parsable input already do this, e.g. [`function a(`](https://www.typescriptlang.org/play/?alwaysStrict=false&ssl=3&ssc=2&pln=1&pc=1#code/GYVwdgxgLglg9mABAQwBSIN4ChG8QIgFUwoBTAJwFsYxkyATRAB2XNJIAtSBnHxCOOTbQANgE9EbUL26IocRKWpR+ceqQB0+ANxYAvkA)
**Actual behavior:**
A closing brace is inserted in the emitted JS code.
```js
function a() {
"Automatic Brace Insertion! (ABI)";
}
```
This means that users who are not using `noEmitOnError` are silently having invalid code transformed into valid code. I can confirm this actually happened to someone shipping something to production.
**Playground Link:** [ABI Playground Link](https://www.typescriptlang.org/play/?alwaysStrict=false&ssl=1&ssc=1&pln=2&pc=40#code/GYVwdgxgLglg9mABAQwBQEpEG8BQj+IBEAgiFHALbKwSIBCATshAKaICSYAziw7AgEJEqYnXbpCAbhw4gA)
**Related Issues:** https://github.com/microsoft/TypeScript/issues/34870 , https://github.com/microsoft/TypeScript/issues/34871 , [Lazy Twitter report](https://twitter.com/robpalmer2/status/1190383568612184064)
I would suggest this bug deserves to be fixed based on [Design Goal 7](https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals#goals) (_Preserve runtime behavior of all JavaScript code_) and [Design Non-Goal 7](https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals#non-goals) (_Introduce behaviour that is likely to surprise users_).
**Tagline:** _If the braces don't fit, you must not emit._ | Suggestion,Awaiting More Feedback | low | Critical |
516,689,868 | youtube-dl | Extractor Error KeyError('vid') | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.10.29. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that all URLs and arguments with special characters are properly quoted or escaped as explained in http://yt-dl.org/escape.
- Search the bugtracker for similar issues: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Read bugs section in FAQ: http://yt-dl.org/reporting
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a broken site support issue
- [x] I've verified that I'm running youtube-dl version **2019.10.29**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [x] I've searched the bugtracker for similar bug reports including closed ones
- [x] I've read bugs section in FAQ
## Verbose log
<!--
Provide the complete verbose output of youtube-dl that clearly demonstrates the problem.
Add the `-v` flag to your command line you run youtube-dl with (`youtube-dl -v <your command line>`), copy the WHOLE output and insert it below. It should look similar to this:
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2019.10.29
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
<more lines>
-->
```
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--username', 'PRIVATE', '--password', 'PRIVATE', '--write-thumbnail', '--embed-thumbnail', '--add-metadata', '--write-sub', '--sub-lang', 'en_US', '--embed-subs', '-k', '-v', 'https://www.vlive.tv/video/152198?channelCode=E832DF']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dl version 2019.10.29
[debug] Python version 3.7.4 (CPython) - Windows-10-10.0.18362-SP0
[debug] exe versions: ffmpeg N-95171-g6ca3d34ff8, ffprobe N-95171-g6ca3d34ff8
[debug] Proxy map: {}
[vlive] Downloading login cookies
[vlive] Logging in
[vlive] Downloading login info
[vlive] 152198: Downloading webpage
[vlive] 152198: Downloading live webpage
ERROR: An extractor error has occurred. (caused by KeyError('vid')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\common.py", line 530, in extract
ie_result = self._real_extract(url)
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\vlive.py", line 124, in _real_extract
return self._replay(video_id, webpage, long_video_id, key)
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\vlive.py", line 188, in _replay
long_video_id, key = video_info['vid'], video_info['inkey']
KeyError: 'vid'
Traceback (most recent call last):
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\common.py", line 530, in extract
ie_result = self._real_extract(url)
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\vlive.py", line 124, in _real_extract
return self._replay(video_id, webpage, long_video_id, key)
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\vlive.py", line 188, in _replay
long_video_id, key = video_info['vid'], video_info['inkey']
KeyError: 'vid'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\YoutubeDL.py", line 796, in extract_info
ie_result = ie.extract(url)
File "c:\users\joshj\appdata\local\programs\python\python37-32\lib\site-packages\youtube_dl\extractor\common.py", line 543, in extract
raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('vid')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
```
## Description
<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
Trying to download this video https://www.vlive.tv/video/152198?channelCode=E832DF throws an error. It's a channel+ video so you need an account. You can use mine but I don't know how to provide the credentials without others seeing it. This is the only channel+ video I'm having trouble downloading other videos such as https://www.vlive.tv/video/67590?channelCode=E832DF and https://www.vlive.tv/video/31799?channelCode=E832DF download without a problem.
| account-needed | low | Critical |
516,695,285 | godot | 3D objects get jagged edges in GLES2 (due to low Z-buffer precision on AMD GPUs) | 3.2.alpha3 (same issue existed in previous versions, including 3.1.1 iirc -- and still existed a day or two ago in build `af4fd9de9`)
Windows 7 / ATI Radeon HD 4870
**This happens in GLES2 only** (at least in my case). In GLES3 all seems fine.
I get these weird glitches where the edges of **large** 3D objects are all jagged. This cube is 20x20x20, and the plane is 200x200:
Doesn't matter if the size of the objects comes from scaling the MeshInstance or by adjusting the size of the Mesh itself.
I never noticed this until I bumped up the size of some assets by 10x, to try to fix a potential issue with physics. With the smaller ones everything seemed fine.
While materials don't solve the issue, setting one of the flags `Transparent`, `Unshaded` or `No Depth-Test`, makes the object render correctly, as is the case in the image below. Blue cube has transparency on, red cube doesn't. (Everything else in the materials is default.)
Amusingly, though, when I select the red cube, it suddenly renders perfectly fine. When I deselect it, it suddenly no longer does.
My first assumption is that it's related to depth testing. However, [in another issue](https://github.com/godotengine/godot/issues/32764#issuecomment-542140637) someone was suggesting tinkering with camera's `z-near`, and as I started bumping it up in small steps, the glitches started happening farther away from the camera (I had to zoom out further each time to make them happen). For the size of those cubes, setting it to something between 1.0 and 5.0 seems to "move" the glitches far away enough that they are unnoticeable. So in a way that kinda "fixes" it.
(In the gif above I was using `z-far` 10000, but it didn't seem to me that `z-far` made any difference in this. I only made it big to zoom out at will. I noticed the issue when using z-near 0.1 and z-far 500, which are default values, if I'm not mistaken.)
**Steps to reproduce:**
Create a project, add a plane mesh and one or more cube meshes, and make their sizes somewhat big. As far as I could tell, the bigger, the more noticeable the glitches. Also, the more zoomed out, the more noticeable.
Sometimes the glitches don't start happening until I zoom out quite a bit and zoom back in.
**Minimal reproduction project:**
[Jagged-Edges-Test.zip](https://github.com/godotengine/godot/files/3800855/Jagged-Edges-Test.zip)
| bug,topic:rendering | low | Major |
516,695,526 | pytorch | error: 'SO_REUSEPORT' was not declared in this scope | ## 🐛 Bug
When building from master, the error in the title appears.
## To Reproduce
Steps to reproduce the behavior:
1. checkout master
1. build
## Expected behavior
Build works
## Environment
- PyTorch Version: 1.4 master
- OS (e.g., Linux): Fedora Linux
- How you installed PyTorch (`conda`, `pip`, source): source
- Build command you used (if compiling from source): `python setup.py develop`
- Python version: 3.7.4
- CUDA/cuDNN version: irrelevant
- GPU models and configuration: irrelevant
- Any other relevant information: irrelevant
## Additional context
Problem is with nccl, as described here: https://github.com/NVIDIA/nccl/issues/244
The patch described there seems to be working but a workaround would be nice.
| module: build,triaged,module: third_party | medium | Critical |
516,712,643 | pytorch | "Unknown type constructor" error in TorchScript | ## 🐛 Bug
Scripting functions and classes with initialisation of List, Dict, Tuple fails, if `import typing` is used instead of `from typing import...`: Error "RuntimeError: Unknown type constructor typing.List"
## To Reproduce
Code 1
```
import torch
from typing import List
@torch.jit.script
def MyFunc():
my_list: List[float] = []
return my_list
```
- works normally
Code 2 - fails:
```
import torch
import typing
@torch.jit.script
def MyFunc():
my_list: typing.List[float] = []
return my_list
```
- fails with error
```
RuntimeError:
Unknown type constructor typing.List:
at D:/Programming/Braille/MyCode/qwe.py:6:13
@torch.jit.script
def MyFunc():
my_list: typing.List[float] = []
~~~~~~~~~~~~~~~~~ <--- HERE
return my_list
```
The same trouble with Dict, Tuple. And with scripting classes.
## Expected behavior
Code 2 works like Code 1
## Environment
Connected to pydev debugger (build 183.5912.18)
Collecting environment information...
PyTorch version: 1.3.0a0+de394b6
Is debug build: No
CUDA used to build PyTorch: 10.0
OS: Microsoft Windows 10 Pro
GCC version: Could not collect
CMake version: version 3.12.2
Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 10.0.130
GPU models and configuration: GPU 0: GeForce GTX 1080 Ti
Nvidia driver version: 411.31
cuDNN version: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.0\bin\cudnn64_7.dll
Versions of relevant libraries:
[pip3] numpy==1.17.2
[pip3] pytorch-ignite==0.2.0
[pip3] pytorch-toolbelt==0.2.1
[pip3] segmentation-models-pytorch==0.0.2
[pip3] torch==1.3.0a0+de394b6
[pip3] torchvision==0.4.1a0+d94043a
[conda] blas 1.0 mkl
[conda] cuda92 1.0 0 pytorch
[conda] mkl 2019.0 <pip>
[conda] mkl 2019.0 118
[conda] mkl-include 2019.0 <pip>
[conda] mkl-include 2019.0 118
[conda] mkl_fft 1.0.6 py36hdbbee80_0
[conda] mkl_random 1.0.1 py36h9258bd6_0
[conda] pytorch-ignite 0.2.0 <pip>
[conda] pytorch-toolbelt 0.2.1 <pip>
[conda] segmentation-models-pytorch 0.0.2 <pip>
[conda] torch 1.3.0a0+de394b6 <pip>
[conda] torchvision 0.4.0 <pip>
[conda] torchvision 0.4.1a0+d94043a <pip>
cc @suo | oncall: jit,triaged,jit-backlog | low | Critical |
516,769,753 | PowerToys | [FrancyZones] "Move newly created windows to their last known zone" support for PWAs installed from Chromium Edge | # Summary of the new feature/enhancement
Please support those PWAs installed by Chromium Edge which are opened in individual windows on the "Move newly created windows to their last known zone" function, for now they are opened up in a very strange position (mostly out of the screen)
<!--
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
--> | Idea-Enhancement,Product-FancyZones,Area-App Compat | low | Major |
516,789,023 | kubernetes | Break the circular dependency in kubelet | This is a pre-requisite issue for https://github.com/kubernetes/kubernetes/issues/84473
## Overview
+ [ ] Break the circular dependency between configMapManager, secretManager and kubelet
+ [ ] Refactor kubelet with node status plugin and registry #85672
+ [ ] Add node getter package instead of kubelet gets node
### Circular dependencies
+ ServerCertificateManager https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L763-L775
+ secretManager, configMapManager https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L552-L571
+ resourceAnalyzer https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L618
+ KubeGenericRuntimeManager https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L671-L691
+ PluginManager https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L794-L797
+ VolumeManager https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L810-L824
+ PodWorkers https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L828
+ criticalPodAdmissionHandler and PredicateAdmitHandler https://github.com/kubernetes/kubernetes/blob/a8220072eca6f7ae9972340422dfb46a57fa777b/pkg/kubelet/kubelet.go#L867-L872
/sig node
/kind cleanup
/area code-organization
/area kubelet
/cc @tallclair
/assign | priority/backlog,area/kubelet,kind/cleanup,sig/node,kind/feature,lifecycle/frozen | low | Major |
516,813,260 | go | runtime: support GOFLAGS=-race everywhere | I'd like to set GOFLAGS=-race on a CI builder. However, some tests invoke the go tool to build for GOOS=js where -race is not supported, leading to this error:
$ GOFLAGS=-race GOOS=js GOARCH=wasm go build std
go build: -race is only supported on linux/amd64, linux/ppc64le, linux/arm64, freebsd/amd64, netbsd/amd64, darwin/amd64 and windows/amd64
I believe unsupported flags should be ignored (unlike unknown flags).
| NeedsDecision,compiler/runtime | low | Critical |
516,825,548 | scrcpy | Could not listen on port 27183 | debain10 安装后启动
```js
2019/11/03 20:47:17.095543 cmd_run.go:880: WARNING: cannot start document portal: read unix @->/run/user/1000/bus: EOF
INFO: scrcpy 1.10 <https://github.com/Genymobile/scrcpy>
/usr/local/share/scrcpy/scrcpy-server.jar: 1 file pushed. 3.0 MB/s (22546 bytes in 0.007s)
listen: Operation not permitted
ERROR: Could not listen on port 27183
``` | snap | low | Critical |
516,828,691 | godot | Problem releasing game to appstore | I'm developing a game with this awesome game engine and I want to release my game to appstore. My game uses FB SDK and AdMob and I managed to compile the Godot source for iOS. The game runs fine on simulator and device, But when I archived it in xcode and send it to appstore there is some problems that should be fixed. This is the app store connect error email:
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSBluetoothPeripheralUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data.
And Same for NSCameraUsageDescription and NSBluetoothAlwaysUsageDescription. My game doesn't use camera or bluetooth at all and i think it's for arkit usage in my app. I removed the privacy strings from info.plist but it didn't fix it. How can i disable using bluetooth and camera for my iOS game? | platform:ios,topic:porting | low | Critical |
516,838,853 | svelte | Component Unmount: Allow non-duration based outro animations | I am struggling to use a spring-based animation for component outros (unmounting the DOM element). As far as I can tell, the only way to defer/delay the unmount/outro of a component is to use the `transition` or `out` [directive](https://svelte.dev/docs#in_fn_out_fn) and return an transition object with a specified duration:
``` js
{
duration: 400,
easing: ...
}
```
This works great for easing functions, but I cannot use Svelte's `spring()` function for the outro transition, because it has no fixed duration.
---
## Proposal/Potential solution
My proposed solution is for the `transition`, `in` and `out` directives to accept a function that optionally returns a Promise instead of a Transition object. Once the Promise fulfills (or rejects), Svelte can remove the element from the DOM.
Example REPL for illustration:
https://svelte.dev/repl/cc1467f851284051a11ca0325c2efd97?version=3.12.1
## Alternative I have considered
One alternative I've considered, is pre-calculating a duration for the spring and using that as the duration value in the transition object. This approach has one disadvantage: springs are inherently dynamic, so the animation distance changes how long the spring takes to finish (its duration), which makes a static pre-calculation (i.e. one pre-calculated duration per spring-config) of the spring not possible.
It may be be possible to predict the duration relatively accurately based on the spring config (damping, stiffness, mass, ...) and the travel distance, but that is a considerable amount of work for something which Just Works™ when using normal easing transitions.
## Additional context
Svelte puts a lot of focus into "making UI interactions and animations as easy as possible". For that matter, Svelte even provides its own Spring-based animation API. So it would make sense to allow to use Svelte's `spring()` function (or third-party ones) for outro transitions.
If this addition is feasible and wanted, it may also make sense to revisit some of the built in animation functions like `fade` and `slide` to make it possible to use them also with a spring.
**How important is this feature to me?**
Right now, I am trying to evaluate to port an existing project to Svelte. This existing project has spring-based outro animations in a few places (pages, menus). It's not a dealbreaker, but seems like an unfortunate limitation.
In my opinion, spring interactions and animations are superior to fixed (duration based) easings and feel more intuitive.
**Similar "defered unmount" discussion over at React**: https://github.com/reactjs/rfcs/issues/128
**Potential drawback**: One drawback of the Promise based approach as I proposed it above is, that the author has to handle the animation themselves. I.e. I have to get a reference to the DOM element and do stuff with it, instead of letting Svelte handle it. But this may be necessary nontheless when the author wants to use a third-party library, such as [Popmotion](https://popmotion.io/pure/).
**What about _Intro_ transitions**: In general, my proposal is also about intro animations. But it is not such a big of a problem, because you _can_ roll your own intro animation logic within an `onMount()` handler. In the case of the outro animation, there is no real workaround that I am aware of, which is why I primarily focused on that.
| feature request,stale-bot,temp-stale | low | Major |
516,859,510 | TypeScript | Please document compiler APIs | Would it be possible to get some documentation on the compiler APIs?
I am working on some TypeScript tooling, and I am using `ts.createSourceFile()` to get the AST for a TypeScript source file. However, the tree in `SourceFile.statements` is missing some information. For example, I need to know the type of an `Expression` when a `PropertyDeclaration` only has an `initializer` but no declared `type`. I have tried `TypeChecker.getContextualType()` but it always returns `undefined`; also the implementation doesn't look right. There are internal methods like `TypeChecker.getTypeOfExpression()` that look promising, but they are not visible. Also I read some mention of 'bindings', but I haven't found a way to get them.
Another example is type resolution: When I encounter a `TypeNode` or something similar within the AST, I usually need to know about its declaration: Where does it come from? Is it local? Where is it imported from? Of course I can write that myself with some effort, but surely such logic already exists within the compiler, I just don't know where. | Docs | low | Major |
516,861,527 | rust | Request: mark all integer platform intrinsics as `const` | The platform intrinsics for _floating point_ suffer the standard floating point problems of not being fully deterministic at all times, which is a requirement for const.
However, the platform intrinsics for _integer_ data do not suffer these problems at all. They are plain integer math operations and you can deterministically know exactly what bit pattern you'll get out for any bit pattern you send in. This means that they are eligible for becoming `const`. At compile time we could even emulate the operations if necessary.
So, we should make all of these `const`. | T-lang,T-libs-api,C-feature-request,A-const-eval | low | Minor |
516,863,909 | angular | ExpressionChangedAfterItHasBeenCheckedError is thrown by ngModel.control.disable() been called | # 🐞 bug report
### Affected Package
The issue is caused by package `@angular/forms`
### Is this a regression?
No.
### Description
I want to disable a form field with NgModel (template-driven form) dynamically with `ngModel.control.disabled()` method call in the `ngAfterViewInit()` hook. It will throw ExpressionChangedAfterItHasBeenCheckedError exception.
## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-forms-ngmodel-expressionchangedafterithasbeencheckederr?file=src/app/app.component.ts
## 🔥 Exception or Error
<pre><code>
ERROR
Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'ng-valid: true'. Current value: 'ng-valid: false'.
</code></pre>
## 🌍 Your Environment
**Angular Version:**
<pre><code>
Angular CLI: 8.3.17
Node: 10.16.3
OS: win32 x64
Angular: 8.2.13
... common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.803.17
@angular-devkit/build-angular 0.803.17
@angular-devkit/build-optimizer 0.803.17
@angular-devkit/build-webpack 0.803.17
@angular-devkit/core 8.3.17
@angular-devkit/schematics 8.3.17
@angular/cli 8.3.17
@ngtools/webpack 8.3.17
@schematics/angular 8.3.17
@schematics/update 0.803.17
rxjs 6.5.3
typescript 3.5.3
webpack 4.39.2
</code></pre>
**Anything else relevant?**
This problem also exists in `Angular 9.0.0-rc.0`. | type: bug/fix,workaround1: obvious,area: forms,state: confirmed,forms: template-driven,forms: disabling controls,forms: ngModel,forms: change detection,P4 | low | Critical |
516,866,033 | godot | Shift and CRTL+A group selection does not work on the AnimationPlayer Copy Tracks pop up | **Godot version:**
_3.2 alpha 3_
**OS/device including version:**
All
**Issue description:**
When you hold the Shift key and click the bottom track and then the top track or vica versa, and just those tracks are selected rather than all of the tracks which are inbetween those two.
In addition, CTRL+A does not work either and rather should have just the sellect all functionality as already coded in for the Sellect All/None button.
**Steps to reproduce:**
Create AnimationPlayer, create animation, create at least 3 tracks, press Edit, press Copy Tracks, hold the Shift key and click on the bottom track, then the top track, or vica versa.
 | enhancement,topic:editor,usability | low | Minor |
516,873,798 | godot | When debugging, hovering a variable containing a lot of text makes its tooltip cover the entire screen with white | Godot 3.2 alpha3
When debugging, I hovered some `text` variable in my script which was containing a lot of text (hundreds of lines with some of them having hundreds of characters). Godot tried to show a tooltip with the value inside but that resulted in the tooltip covering the entire editor, curiously without any text visible in it.
I think we need to limit the size of that tooltip, or enhance debugging tooltips in general (see how Rider or Visual Studio tooltips do). | bug,topic:editor,confirmed | low | Critical |
516,875,564 | go | cmd/trace: Mininum mutator utilization plot window durations range is not consistent across Include options | <!-- Please answer these questions before submitting your issue. Thanks! -->
### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.13.4 linux/amd64
</pre>
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/eg/.cache/go-build"
GOENV="/home/eg/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/eg/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/eg/go/src/bitbucket.org/triangleteam/resource-manager/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build569889623=/tmp/go-build -gno-record-gcc-switches"
</pre></details>
### What did you do?
<details><summary>I wrote a simple code to check built in golang tracing:</summary><br>
```go
package main
import (
"os"
"runtime"
"runtime/trace"
"sync"
"time"
)
func main() {
f, err := os.Create("trace.out")
if err != nil {
panic(err)
}
trace.Start(f)
defer func() {
trace.Stop()
_ = f.Close()
}()
wg := sync.WaitGroup{}
for g := 0; g < runtime.NumCPU(); g++ {
wg.Add(1)
go func() {
for i := 0; i < 40; i++ {
bs := make([]byte, 1024*1024)
for k := range bs {
bs[k] = byte(k % 8)
}
time.Sleep(50 * time.Millisecond)
}
wg.Done()
}()
}
wg.Wait()
}
```
</details>
After running this program and getting `trace.out` file as an output I do `$ go tool trace trace.out`, open `http://127.0.0.1:32935/mmu` in the browser and look at the plots with and without **STW** checkbox set.
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
### What did you expect to see?
I expect that X-axis range (min and max *Window duration* for which MMU function is evaluated) is the same with **STW** set and not set.
### What did you see instead?
I see that with **STW** checkbox set the window duration range is `[1ms, ~10s]`, and when checkbox is unset range is `[1ns, 1ms]`.
To conclude: if I get everything correctly, such behavior makes it harder to understand how GC affects the utilization. Should we make the window duration range consistent across any set of checked options? Or maybe we should make it possible for user to configure the range.
| NeedsInvestigation,compiler/runtime | low | Critical |
516,882,164 | godot | Selecting multiple nodes adds empty RefCounted section in the inspector | **Godot version:**
3.2 alpha3
**Steps to reproduce:**
1. Create 2 nodes (best observable with Node)
2. Select both of them
3. This appears at the bottom of the inspector
I guess it shouldn't be there. | bug,topic:editor,confirmed | low | Minor |
516,894,230 | rust | Unhelpful error message constructing re-exported tuple struct with private fields | If a public tuple struct with private fields is declared in a public module, then instantiated elsewhere, the error message is helpful. For example, the code
```rust
// src/lib.rs
pub mod a {
pub struct Triplet(usize, usize, f64);
}
```
```rust
// src/main.rs
use triplets::a::Triplet;
fn main() {
let mut triplets = Vec::new();
triplets.push(Triplet(0, 0, 1.0));
}
```
causes the compiler to give the following useful error message:
```
error[E0423]: expected function, tuple struct or tuple variant, found struct `Triplet`
--> src/main.rs:5:19
|
5 | triplets.push(Triplet(0, 0, 1.0));
| ^^^^^^^
| |
| constructor is not visible here due to private fields
| help: a local variable with a similar name exists: `triplets`
error: aborting due to previous error
```
This tells us exactly what the problem is - that we cannot construct `Triplet` because its fields are private.
However, if the tuple struct is in a private module, but re-exported as public, the error message isn't helpful (it's even confusing). For example,
```rust
// src/lib.rs
mod a {
pub struct Triplet(usize, usize, f64);
}
pub use a::Triplet;
```
```rust
// src/main.rs
use triplets::Triplet;
fn main() {
let mut triplets = Vec::new();
triplets.push(Triplet(0, 0, 1.0));
}
```
gives the compiler error
```
error[E0423]: expected function, tuple struct or tuple variant, found struct `Triplet`
--> src/main.rs:5:19
|
5 | triplets.push(Triplet(0, 0, 1.0));
| ^^^^^^^
| |
| did you mean `Triplet { /* fields */ }`?
| help: a local variable with a similar name exists: `triplets`
error: aborting due to previous error
```
which confusingly suggests initialising the tuple with braces, instead of reporting that the fields are private.
Unsurprisingly, both versions work fine if the fields of `Triplet` are made public. | C-enhancement,A-diagnostics,A-visibility,T-compiler,D-confusing,D-papercut,D-incorrect | low | Critical |
516,897,051 | godot | Opening a scene when an empty scene tab is open should replace the tab | **Godot version:**
3.2 alpha3
**Issue description:**
When you have an empty scene open (no root, no filename assigned) and open another scene, it should replace the empty tab with that scene. You can observe such behavior e.g. in Google Chrome. | enhancement,topic:editor,usability | low | Minor |
516,904,161 | react | "NotFoundError: Failed to execute 'removeChild' on 'Node'" when using React.Fragment <></> with Chrome extension which does not modify the DOM tree below the root div of the React app | This has already been discussed before (#14740), but there wasn't a reproducing example for this kind of issue and I think that my use case is also a bit different.
**Do you want to request a *feature* or report a *bug*?**
I believe this can be considered a bug.
**What is the current behavior?**
In order to reproduce this issue using Chrome, you will need to install the following Chrome extension called TransOver:
https://chrome.google.com/webstore/detail/transover/aggiiclaiamajehmlfpkjmlbadmkledi?hl=en
I use it to translate text on hover.
The only thing that this extension does is appending a tooltip with the translated text to the `body` HTML element when you hover an element with text (it doesn't seem it appends stuff below the React's root `div` element).
I have created two code sandboxes to show you better and explain the problem.
It is a minimal example of a movie app like the one Dan showed at JSConf 2018 in Iceland, though not as beautiful as his and without all that cool Suspense stuff, but at least it uses hooks :) .
- https://codesandbox.io/s/heuristic-lake-exxvu
- https://codesandbox.io/s/magical-grass-016kc
The two code sandboxes are essentially identical, the only difference is that the first one (`heuristic-lake-exxvu`) uses a `div` element for `MovieApp`, whereas the second (`magical-grass-016kc`) uses a `React.Fragment` (`<></>`) component:
`heuristic-lake-exxvu`'s `MovieApp`:
```
const MovieApp = () => {
const [currentMovie, setCurrentMovie] = useState(initialCurrentMovieState);
const { isLoading, id: currentMovieId, movieDetails } = currentMovie;
...
return (
<div> // <======================= Uses a `div`
{isLoading ? (
"Loading..."
) : (
...
```
`magical-grass-016kc`'s `MovieApp`:
```
const MovieApp = () => {
const [currentMovie, setCurrentMovie] = useState(initialCurrentMovieState);
const { isLoading, id: currentMovieId, movieDetails } = currentMovie;
...
return (
<> // <======================= Uses a fragment
{isLoading ? (
"Loading..."
) : (
...
```
Now, if you open `heuristic-lake-exxvu` and click on the `Show movie info` button of any movie in the list, you will see the `Loading...` text before the promise with the data of the movie resolves, and the `Movie` component is rendered.
Before the promise resolves, try hovering on the `Loading...` text with the `TransOver` extension enabled, you should see:
The world makes sense here, no errors, no warnings, everything works.
Now try to do the same thing on `magical-grass-016kc`, as soon as you hover `Loading...`, you will see the `NotFoundError: Failed to execute 'removeChild' on 'Node'` error logged in the browser's console:
Here is a streamable video showing this same error:
https://streamable.com/4gxua
**What is the expected behavior?**
In `heuristic-lake-exxvu` (uses a `div` instead of React fragment), everything worked.
The TransOver extension appends to `body` and does not modify the React's root `div` neither does it append stuff below it, so I would expect the code in the React fragment example (`magical-grass-016kc`) to behave the same and work as in `heuristic-lake-exxvu`.
Chrome is plenty of useful extensions like this one and they should not really interfere with React, I think that users using React applications may also install other extensions which modify the DOM which they find useful.
If an extension appends to body like TransOver does, I wouldn't expect React to have problems with it and cause undesirable effects and application errors like this one.
This is my opinion, I would be very glad to hear what you think about it, and if you think I have spotted a bug of React fragments (I think it's a bug because, again, it works when using a `div` in `heuristic-lake-exxvu`).
**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
Browser: Chrome
React v16.11.0
React DOM v16.11.0
| Type: Needs Investigation | high | Critical |
516,908,024 | godot | preload doesn't list as dependency when in build-in script | **Godot version:**
3.2 alpha3
**Issue description:**
When you preload a resource in a script, it will become a dependency of this script, so e.g. when you try to delete the resource, you get a warning about that. However it's not the case with built-in scripts. They should probably add the dependency to the scene. | bug,topic:editor,confirmed | low | Minor |
516,911,234 | TypeScript | Bad `.d.ts` emit for class expression on `module.exports | ## Repro
```js
module.exports.answer = class C {
foo = 10;
bar;
}
```
## Instructions
```sh
tsc --declaration --allowJS --outDir lib ./src/foo.js
```
## Current
```ts
declare class C {
foo: number;
bar: any;
}
export {};
```
## Expected
```ts
declare class C {
foo: number;
bar: any;
}
export { C as answer };
```
or
```ts
declare class C {
foo: number;
bar: any;
}
export var answer: typeof C;
``` | Bug,Domain: Declaration Emit,Domain: JavaScript | low | Minor |
516,931,822 | rust | Incorrect trace for Item-level syntax errors in modules included by macro-generated code | Using Rust nightly 2019-11-04.
Consider a macro that generates a `mod` statement:
```rust
#[proc_macro]
pub fn generate(_: proc_macro::TokenStream) -> proc_macro::TokenStream {
quote::quote!(mod foo;).into()
}
```
Call this in the src/main.rs in another crate:
```rust
codegen::generate!();
fn main() {
foo::bar();
}
```
In src/foo.rs, we have the following code:
```rust
#{inline}
pub fn bar() {
println!("Hello world");
}
```
Note the intentional syntax error `#{inline}` instead of `#[inline]` in src/foo.rs.
Compiling this setup (reproducible example in
[upload.tar.gz](https://github.com/rust-lang/rust/files/3802516/upload.tar.gz))
with `cargo check`,
we have the following error message:
```
error: expected `[`, found `{`
--> src\main.rs:1:1
|
1 | codegen::generate!();
| ^^^^^^^^^^^^^^^^^^^^^
error[E0433]: failed to resolve: use of undeclared type or module `foo`
--> src\main.rs:4:5
|
4 | foo::bar();
| ^^^ use of undeclared type or module `foo`
```
The second error is an indirect consequence of the first error.
But where did the "found `{`" error message come from?
Obviously, there is nothing wrong with the `codegen::generate!()` macro
(we can verify this by fixing the intentional syntax error in src/foo.rs).
So let's try manually expanding the macro call, i.e. we now replace src/main.rs:1 with
```rust
mod foo;
```
And we have the following correct error message:
```
error: expected `[`, found `{`
--> src\foo.rs:1:2
|
1 | #{inline}
| ^ expected `[`
error: aborting due to previous error
```
So this error is caused by incorrect error span detection.
I am unable to locate the exact set of syntax errors affected,
because this does not happen with every syntax error.
For example, if I replace src/foo.rs with
```rust
#[inline] // correct syntax here
pub fn bar() {
let a = 1 // missing semicolon here
println!("Hello world");
}
```
The resultant error message is correct:
```
error: expected `;`, found ``println``
--> src\foo.rs:3:14
|
3 | let a = 1
| ^ help: add `;` here
4 | println!("Hello world");
| ------- unexpected token
```
| A-diagnostics,A-macros,T-compiler,C-bug | low | Critical |
516,934,947 | flutter | Google Map: Support for "Hollow" Polygons | According to the Google Maps API, most libraries have support for "Hollow" Polygons. However, I could not find any such support for the Dart API.
Does anyone know if such support is already on its way? If not I would like to make it a feature request as my current project requires this functionality.
Below I've included a link to the documentation I am referring to.
https://developers.google.com/maps/documentation/android-sdk/shapes#create_a_hollow_polygon
Thanks!
| c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem | low | Minor |
516,946,620 | flutter | Suggestion: When installing Flutter, ask which parts to install | Hello! I have two workstations. One is a MacBook Air and the other one is a Windows/Linux desktop. I am developing using Flutter on both and I find it a waste of space to download all of the Android stuff on my Mac when I develop on Android on my Windows installation. Would it be possible to add a question related to the installation of the Android stuff?
 | c: new feature,tool,P3,team-tool,triaged-tool | low | Minor |
516,980,607 | pytorch | a retrained and saved jit module could not be reload. | I'm try to retain a JIT module from pytorch using c++ based on Libtorch libtorch-win-shared-with-deps-1.3.0 _cpu, and save retrained module for next usage.
the save and reload process will be like the following , but get erro while try reload.
```cpp
torch::serialize::OutputArchive output_archive;
auto presavedModule = torch::jit::load("D:/localshare/data/model/model.pt");
presavedModule.save("D:/localshare/data/model/testmodel.pt");
auto savedModule = torch::jit::load("D:/localshare/data/model/testmodel.pt");
savedModule.dump(true, true, true);
```
reported error:
```
Caught
expected newline but found 'number' here:
at code/__torch__/modelv2.py:75:51
import __torch__.modelv2.features.16.conv.1
import __torch__.modelv2.features.17
import __torch__.modelv2.features.17.conv
import __torch__.modelv2.features.17.conv.0
import __torch__.modelv2.features.17.conv.1
import __torch__.modelv2.features.18
class features(Module):
__parameters__ = []
__annotations__ = []
__annotations__["0"] = __torch__.modelv2.features.0
~~ <--- HERE
__annotations__["1"] = __torch__.modelv2.features.1
__annotations__["2"] = __torch__.modelv2.features.2
__annotations__["3"] = __torch__.modelv2.features.3
__annotations__["4"] = __torch__.modelv2.features.4
__annotations__["5"] = __torch__.modelv2.features.5
__annotations__["6"] = __torch__.modelv2.features.6
__annotations__["7"] = __torch__.modelv2.features.7
__annotations__["8"] = __torch__.modelv2.features.8
__annotations__["9"] = __torch__.modelv2.features.9
Compiled from code
Type class std::runtime_error
```
Is there any sugesstion:
cc @ezyang @gchanan @zou3519 @jerryzh168 @suo | oncall: jit,triaged | low | Critical |
517,031,484 | youtube-dl | Dplay (Discovery Network) Plus not downloading anymore | Hi, videos that requires authentication not downloading anymore. Tryed both with auth cookie and --username and Password. It says 403 Forbidden. Here below the verbose output:
C:\Users\User\Downloads>youtube-dl.exe --cookies cookie.txt https://it.dplay.com/discovery-channel/una-famiglia-fuori-dal-mondo/stagione-4-episodio-17-gli-amici/ --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--cookies', 'cookie.txt', 'https://it.dplay.com/discovery-channel/una-famiglia-fuori-dal-mondo/stagione-4-episodio-17-gli-amici/', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2019.10.29
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg 3.4.1
[debug] Proxy map: {}
[debug] Using fake IP 79.62.172.157 (IT) as X-Forwarded-For.
[DPlay] una-famiglia-fuori-dal-mondo/stagione-4-episodio-17-gli-amici: Downloading token
[DPlay] una-famiglia-fuori-dal-mondo/stagione-4-episodio-17-gli-amici: Downloading JSON metadata
[DPlay] una-famiglia-fuori-dal-mondo/stagione-4-episodio-17-gli-amici: Downloading JSON metadata
ERROR: This video is only available for registered users. Use --username and --password or --netrc to provide account credentials.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 627, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\YoutubeDL.py", line 2237, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\dplay.py", line 158, in _get_disco_api_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 892, in _download_json
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 870, in _download_json_handle
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 660, in _download_webpage_handle
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 645, in _request_webpage
youtube_dl.utils.ExtractorError: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type youtube-dl -U to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 627, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\YoutubeDL.py", line 2237, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
urllib.error.HTTPError: HTTP Error 403: Forbidden
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\dplay.py", line 158, in _get_disco_api_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 892, in _download_json
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 870, in _download_json_handle
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 660, in _download_webpage_handle
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 645, in _request_webpage
youtube_dl.utils.ExtractorError: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type youtube-dl -U to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\YoutubeDL.py", line 796, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 530, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\dplay.py", line 243, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\dplay.py", line 167, in _get_disco_api_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmps7501na1\build\youtube_dl\extractor\common.py", line 936, in raise_login_required
youtube_dl.utils.ExtractorError: This video is only available for registered users. Use --username and --password or --netrc to provide account credentials. | account-needed | low | Critical |
517,052,363 | pytorch | First element in data passed to `torch.*Tensor` constructors cannot be a tensor | ## 🐛 Bug
`torch.*Tensor` constructors can accept something like `torch.LongTensor([list, tensor])` but not `torch.LongTensor([tensor, tensor])` or `torch.LongTensor([tensor, list])`.
**Exception message:**
> ValueError: only one element tensors can be converted to Python scalars
## To Reproduce
Steps to reproduce the behavior:
```py
import torch as T
x = [1, 2, 3]
y = T.tensor([4, 5, 6])
T.tensor([x, x]) # fine
T.tensor([x, y]) # fine
T.tensor([y, x]) # NOT fine
T.tensor([y, y]) # NOT fine
```
## Expected behavior
Not sure.
## Environment
- PyTorch Version (e.g., 1.0): 1.3.0
- OS (e.g., Linux): Windows 10 64bit
- How you installed PyTorch (`conda`, `pip`, source): Conda
- Build command you used (if compiling from source): N/A
- Python version: 3.7.3
- CUDA/cuDNN version:
- GPU models and configuration:
- Any other relevant information:
cc @cpuhrsch | triaged,module: nestedtensor | low | Critical |
517,071,686 | flutter | Allow TextField label fixed size | The UI design I need to implement has fixed sizes for all text field states, focused, empty, etc. AFAIK there is no way to implement this in Flutter - the label becomes larger when the text field is empty and not focused.
See 'Notes' and 'Hourly Rate' on the screenshots below.
I can work around this with a Column/Text/TextField for now but I think it makes sense to fix this on the InputDecorator level.
```
TextField(
controller: _controller,
decoration: InputDecoration(
labelText: labelText,
),
);
```
| a: text input,c: new feature,framework,f: material design,P3,workaround available,team-text-input,triaged-text-input | low | Minor |
517,076,722 | youtube-dl | Support for stripchat.com | <!--
######################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################
-->
## Checklist
<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.10.29. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->
- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.10.29**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones
## Example URLs
<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- Single video: https://stripchat.com/DaLie
## Description
<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
It is similar to chaturbate.
| site-support-request | low | Critical |
517,086,777 | rust | Tracking issue for `#![register_tool]` | A part of https://github.com/rust-lang/rust/issues/44690.
Some tools (`rustfmt` and `clippy`) used in tool attributes are hardcoded in the compiler.
We need some way to introduce them without hardcoding as well.
https://github.com/rust-lang/rust/pull/66070 introduced a way to do it with a crate level attribute:
```rust
#![register_tool(my_tool)]
#[my_tool::anything] // OK
fn main() {}
```
The previous attempt to introduce them through command line (https://github.com/rust-lang/rust/pull/57921) met some resistance.
This probably needs to go through an RFC before stabilization. | A-attributes,T-lang,B-unstable,T-dev-tools,C-tracking-issue,needs-fcp,S-tracking-design-concerns | high | Critical |
517,146,822 | every-programmer-should-know | A Mindmap to organize the content | I think it'd be awesome if we had a big mindmap to organize all the topics and subtopics.
| Needs some ❤️ | low | Minor |
517,164,087 | pytorch | crash when call dist.new_group(ranks=local_ranks, backend='gloo') | ## 🐛 Bug
<!-- A clear and concise description of what the bug is. -->
process crash when call dist.new_group(ranks=local_ranks, backend='gloo')
## To Reproduce
Steps to reproduce the behavior:
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
```python
dist.init_process_group(backend='gloo', init_method=args.dist_url, world_size=args.world_size, rank=args.rank)
local_group = dist.new_group(ranks=local_ranks, backend='gloo')
```
```
Process 3 terminated with the following error:
Traceback (most recent call last):
File "/opt/conda/lib/python3.6/site-packages/torch/multiprocessing/spawn.py", line 19, in _wrap
fn(i, *args)
File "/opt/CAT/egs/swbd/swbd_recog_h_adpsgd.py", line 249, in speech_recognition_wsj
local_group = dist.new_group(ranks=local_ranks, backend='gloo')
File "/opt/conda/lib/python3.6/site-packages/torch/distributed/distributed_c10d.py", line 1490, in new_group
timeout=timeout)
File "/opt/conda/lib/python3.6/site-packages/torch/distributed/distributed_c10d.py", line 478, in _new_process_group_helper
timeout=timeout)
RuntimeError: [enforce fail at ../third_party/gloo/gloo/transport/tcp/address.cc:29] sizeof(ss_) == bytes.size(). 128 vs 42
```
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
## Environment
Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).
You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```
- PyTorch Version (e.g., 1.3):
- OS (e.g., Linux):
- How you installed PyTorch (`conda`, `pip`, source):
- Build command you used (if compiling from source):
- Python version:
- CUDA/cuDNN version: 10.0.130
- GPU models and configuration:
- Any other relevant information:
## Additional context
<!-- Add any other context about the problem here. -->
cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 | oncall: distributed,triaged | low | Critical |
517,167,422 | TypeScript | NonNullablePartial type - Partial that doesn't allow explicit null/undefined values | <!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.
Please help us by doing the following steps before logging an issue:
* Search: https://github.com/Microsoft/TypeScript/search?type=Issues
* Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ
-->
## Search Terms
<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
partial, nonnullable, required, undefined
## Suggestion
<!-- A summary of what you'd like to see added or changed -->
This might seem as a duplicate of #13195, but this issue is different in that it doesn't require a possibly breaking change to the TS engine.
It instead gets advantage of a special generic Partial type that doesn't allow explicitly setting null/undefined.
```ts
// these of course sadly don't work
type NonNullablePartial<T> = {
[P in keyof T]?: NonNullable<T[P]>;
};
type NonNullablePartial<T> = {
[P in keyof T]?: T[P] extends null | undefined | infer R ? R : T[P];
};
```
My suggestion adds type safety by guarding against what would likely be an error, which isn't yet possible with current implementation of Partial.
## Use Cases
<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->
The reason for this issue is the fact that explicit `null` / `undefined` prevent the application of a "default" parameter with these patterns
```ts
/* In this example
* default config = { message: 'message' }
* user config = { message: undefined }
*/
Object.assign({}, { message: 'message' }, { message: undefined }) // { message: undefined }
const obj = { // obj = { message: undefined }
... { message: 'message' },
... { message: undefined }
}
```
This pattern does not suffer from that and an explicitly set `undefined` is reassigned with a default param. Though, this pattern is impractical for a large set of config variables.
```ts
function f({ message = 'message' } = {}) {
console.log(message)
}
f({ message: undefined }); // message - correct!
f({ message: null }); // null - this makes sense, though not what I am looking for
```
To put it in other words:
I am using a default config object, which I then need to merge with user config object. I need to prevent the user from possibly mistakenly assigning `null`/`undefined` values to parameters which would effectively replace and remove the "default" value.
## Examples
<!-- Show how this would be used and what the behavior would be -->
```ts
export interface ResponseErrorTemplate {
code: string;
status: number;
message: string;
errorConstructor: typeof ApolloError;
}
export interface ResponseErrorTemplateInput {
message: string;
errorConstructor: typeof ApolloError;
}
export type ResponseErrorTemplateGetter = (
config?: Partial<ResponseErrorTemplateInput> // Here, keep Partial, but prevent null/undefined
) => ResponseErrorTemplate;
const defaultConfig: ResponseErrorTemplateInput = {
message: 'Not found',
errorConstructor: ApolloError,
};
export const getNotFoundTemplate: ResponseErrorTemplateGetter = config => ({
...defaultConfig,
...config, // if user defines message: undefined here, they replace the default 'Not found'
status: 404,
code: 'NOT_FOUND',
});
```
## Checklist
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, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
| Suggestion,Awaiting More Feedback | low | Critical |
517,184,299 | pytorch | torch.masked_fill missing out argument | Following up on https://github.com/pytorch/pytorch/issues/29028#issuecomment-548968891, there exists `torch.masked_fill_` but cannot be accessed through `out` argument, which makes writing generic (inplace / out-of-place) code less straighforward
This is just one example, it would be nice to make a summary table for all ops and see if they are consistent about out-argument (allows for generic code) and underscore-suffixed variants (nice semantics, but leads to method signature duplication)
It would be nice to have clear guidelines wrt inplace / out-variants across all PyTorch: tensor instance methods, functions, nn.functional functions, nn.Module classes. | feature,triaged,module: ux | low | Minor |
517,258,628 | pytorch | _compared_saved_loaded doesn't work with torch.tensor constants | Steps to reproduce:
1. Add this test to `test_jit.py`:
```python
def test_trace_modern_ctor(self):
class MyModule(nn.Module):
def forward(self, x):
return (x + 1, torch.tensor([0.0]))
# Shouldn't fail sanity checks
traced_rec = torch.jit.trace(MyModule(), torch.randn(2, 2))
```
2. Run test:
```
Traceback (most recent call last):
File "test/test_jit.py", line 324, in test_trace_modern_ctor
traced_rec = torch.jit.trace(MyModule(), torch.randn(2, 2))
File "/scratch/ezyang/pytorch-tmp/torch/jit/__init__.py", line 880, in trace
check_tolerance, _force_outplace, _module_class)
File "/scratch/ezyang/pytorch-tmp/torch/jit/__init__.py", line 1020, in trace_module
module._c._create_method_from_trace(method_name, func, example_inputs, var_lookup_fn, _force_outplace)
File "/scratch/ezyang/pytorch-tmp/test/jit_utils.py", line 178, in emitModuleHook
self._compared_saved_loaded(module)
File "/scratch/ezyang/pytorch-tmp/test/jit_utils.py", line 164, in _compared_saved_loaded
self.assertMultiLineEqual(a, b)
AssertionError: 'op_v[210 chars]NTS.c1, torch.device("cpu"), 7, False, False, [84 chars]_1\n' != 'op_v[210 chars]NTS.c0, t
orch.device("cpu"), 7, False, False, [84 chars]_1\n'
op_version_set = 1
class Module(Module):
__parameters__ = []
training : bool
def forward(self: __torch__.torch.nn.modules.module.Module,
x: Tensor) -> Tuple[Tensor, Tensor]:
- _0 = torch.to(CONSTANTS.c1, torch.device("cpu"), 7, False, False, None)
? ^
+ _0 = torch.to(CONSTANTS.c0, torch.device("cpu"), 7, False, False, None)
? ^
- _1 = (torch.add(x, CONSTANTS.c0, alpha=1), torch.detach(_0))
? ^
+ _1 = (torch.add(x, CONSTANTS.c1, alpha=1), torch.detach(_0))
? ^
return _1
```
Seems like there's something wrong where we are not resetting constant numbering second time around.
cc @ezyang @gchanan @zou3519 @jerryzh168 @suo | triage review,oncall: jit,triaged | low | Critical |
517,273,823 | pytorch | JIT should respect SKIP_PYTHON_BINDINGS and SKIP_PYTHON_BINDINGS_SIGNATURES | The eager python frontend does not bind specific operators to python, either via SKIP_PYTHON_BINDINGS or SKIP_PYTHON_BIDNINGS_SIGNATURES:
https://github.com/pytorch/pytorch/blob/41e42c34d65f7dce5f526cdb059e860bbe4d0f36/tools/autograd/gen_python_functions.py#L19-L49
The JIT does not respect these lists, however, which means we can end up serializing operator calls that aren't considered part of the public API. This makes BC concerns more complicated, because we need to decide if breaking those serialized formats is supported or not.
This also leads to confusion in PRs. For example: https://github.com/pytorch/pytorch/pull/26332/. There is a fair amount of talking-past-one-another in that PR, because the JIT-focused reviewers are concerned with getting the autograd semantics correct and the eager-focused reviewers see this as a C++-frontend only change. The end result isn't great either: the JIT now calls the C++ frontend function, even though that's not at all what the python frontend does. That may or may not have the correct semantics, but no one checked.
What I think needs to happen here:
1) Clearly document _why_ the functions above are skipped.
2) Move these lists to a form that is easily consumed by eager and the JIT (maybe in native_functions.yaml? But we need to _not_ bind TH and THNN functions in a clear way)
3) If these are bindable today, bind them (i.e. there may have been limitations in the past that prevented us from binding them, but some of these should be bindable now. See https://github.com/pytorch/pytorch/pull/27629 as an example).
4) Get the JIT to work through these lists and either stop binding them or ensure that the binding is correct. Also deal with the BC issues.
This is related to some work that @bhosmer expressed interest in: all of these special bindings are a potential source of bugs across the eager/JIT boundary.
CC @suo @bhosmer @pbelevich @bwasti
cc @suo | triage review,oncall: jit,triaged | low | Critical |
517,289,692 | TypeScript | No autocompletion/intellisense for local commonJS modules | *TS template added by @mjbvz*
**TypeScript Versions**: 3.8.0-dev.20191102
**Search terms:**
- commonjs
- auto complete
*Original report below*
---
I would expect that suggestions commonJS modules written in a similar style to ES6 modules would also be nicely autocompleted as one types, but this seems not to be the case. Any local exports are only suggested if they are ES6 modules.
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.39.2
- OS Version: W10 Pro
Steps to Reproduce:
1. clone [https://github.com/kasvtv/vscode-node-autocomplete](https://github.com/kasvtv/vscode-node-autocomplete)
2. open with VScode
3. start typing `myFunc` in `index.js`
3. no suggestions for commonJS modules
Does this issue occur when all extensions are disabled?: Yes
| Bug,Domain: Auto-import | low | Minor |
517,306,665 | godot | Editor crashes when saving scene with tool script | On Godot_v3.1.1-stable_x11.64 on Arch Linux, the editor crashes when saving a scene with the following script:
```
tool
extends Spatial
export(NodePath) var path
# Called when the node enters the scene tree for the first time.
func _ready():
path = get_node(path)
```
The editor will crash upon saving as long as `path` is unset.
Taking out the line with `tool` will prevent the editor from crashing while saving. Strangely, adding `tool` back in to the script and then saving will not crash the editor, but next time the project is loaded the editor will crash upon saving again.
I do not know if this script crashes the game upon running because the editor will crash when saving whenever I try to run the project.
The workaround for this is to not do the above action in a script. Simply doing `var node = get_node(path)` instead of `path = get_node(path)` will prevent the crash from occurring.
Steps for reproducing:
1. Create a new project
2. Make a scene with a Spatial node (I have yet to try other nodes) that has the above script
3. Close the editor and re-open it
4. Save the project | bug,topic:editor,confirmed,crash | low | Critical |
517,310,689 | flutter | accessibility test meetsGuideline(textContrastGuideline) throws on web | This issues surfaced in a pre-submit test: https://cirrus-ci.com/task/4889346271870976
### Repro code:
`flutter test --platform=chrome test/cupertino/button_test.dart`
```dart
await tester.pumpWidget(
CupertinoApp(
theme: const CupertinoThemeData(brightness: Brightness.dark),
home: CupertinoPageScaffold(
child: CupertinoButton.filled(
child: const Text('Button'),
onPressed: () {},
),
)
),
);
await expectLater(tester, meetsGuideline(textContrastGuideline));
```
### Stacktrace
```
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════ [85/1869]
The following _Exception was thrown while running async test code:
Exception: Incorrect sequence of push/pop operations while building scene surfaces. After building
the scene the persisted surface stack must contain a single element which corresponds to the scene
itself (_PersistedScene). All other surfaces should have been popped off the stack. Found the
following surfaces in the stack:
PersistedScene, PersistedTransform
When the exception was thrown, this was the stack:
package:dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 194:49 throw_
package:build_web_compilers/lib/_engine/engine/surface/scene_builder.dart 26:9 <fn>
package:build_web_compilers/lib/_engine/engine/surface/scene_builder.dart 33:14 get [_persistedScene]
package:build_web_compilers/lib/_engine/engine/surface/scene_builder.dart 464:21 build
package:flutter/src/rendering/layer.dart 767:35 buildScene
package:flutter/src/rendering/layer.dart 1196:28 toImage
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54 runBody
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:12 _async
package:flutter/src/rendering/layer.dart 1185:27 toImage
package:flutter_test/src/accessibility.dart 204:26 <fn>
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54 runBody
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:12 _async
package:flutter_test/src/accessibility.dart 201:71 <fn>
package:flutter_test/src/binding.dart 923:10 <fn>
package:dart-sdk/lib/async/zone.dart 1124:13 _rootRun
package:dart-sdk/lib/async/zone.dart 1021:19 run
package:flutter_test/src/binding.dart 913:25 runAsync
package:flutter_test/src/accessibility.dart 201:43 evaluate
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54 runBody
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:12 _async
package:flutter_test/src/accessibility.dart 196:30 evaluate
package:flutter_test/src/matchers.dart 1973:47 matchAsync
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54 runBody
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:12 _async
package:flutter_test/src/matchers.dart 1972:28 matchAsync
package:test_api/src/frontend/expect.dart 116:25 _expect
package:test_api/src/frontend/expect.dart 75:5 expectLater
package:flutter_test/src/widget_tester.dart 269:13 expectLater
button_test.dart 100:13 <fn>
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50 onValue
package:stack_trace/src/stack_zone_specification.dart 129:26 <fn>
package:stack_trace/src/stack_zone_specification.dart 209:15 [_run]
package:stack_trace/src/stack_zone_specification.dart 129:14 <fn>
package:dart-sdk/lib/async/zone.dart 1132:38 _rootRunUnary
package:dart-sdk/lib/async/zone.dart 1029:19 runUnary
package:dart-sdk/lib/async/future_impl.dart 137:18 handleValue
package:dart-sdk/lib/async/future_impl.dart 678:44 handleValueCallback
package:dart-sdk/lib/async/future_impl.dart 707:32 _propagateToListeners
package:dart-sdk/lib/async/future_impl.dart 522:5 [_completeWithValue]
package:dart-sdk/lib/async/future_impl.dart 552:7 <fn>
package:dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 324:14 _checkAndCall
package:dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 329:39 dcall
package:quiver/testing/src/async/fake_async.dart 268:32 [_drainMicrotasks]
package:quiver/testing/src/async/fake_async.dart 164:5 flushMicrotasks
package:flutter_test/src/binding.dart 1067:16 <fn>
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54 runBody
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 123:12 _async
package:flutter_test/src/binding.dart 1055:35 <fn>
package:dart-sdk/lib/async/future.dart 200:37 <fn>
package:stack_trace/src/stack_zone_specification.dart 209:15 [_run]
package:stack_trace/src/stack_zone_specification.dart 119:48 <fn>
package:dart-sdk/lib/async/zone.dart 1120:38 _rootRun
package:dart-sdk/lib/async/zone.dart 1021:19 run
package:dart-sdk/lib/async/zone.dart 923:7 runGuarded
package:dart-sdk/lib/async/zone.dart 963:23 <fn>
package:stack_trace/src/stack_zone_specification.dart 209:15 [_run]
package:stack_trace/src/stack_zone_specification.dart 119:48 <fn>
package:dart-sdk/lib/async/zone.dart 1124:13 _rootRun
package:dart-sdk/lib/async/zone.dart 1021:19 run
package:dart-sdk/lib/async/zone.dart 923:7 runGuarded
package:dart-sdk/lib/async/zone.dart 963:23 callback
package:dart-sdk/lib/async/schedule_microtask.dart 41:11 _microtaskLoop
package:dart-sdk/lib/async/schedule_microtask.dart 50:5 _startMicrotaskLoop
package:dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15 <fn>
```
### Version
```
[✓] Flutter (Channel unknown, v1.10.7-pre.107, on Linux, locale en_US.UTF-8)
• Flutter version 1.10.7-pre.107
• Framework revision 2affe5ba7c (3 days ago), 2019-11-01 16:07:20 -0700
• Engine revision 8ea19b1c76
• Dart version 2.6.0 (build 2.6.0-dev.8.2 bbe2ac28c9)
``` | a: tests,framework,a: accessibility,platform-web,P2,c: parity,c: tech-debt,team: skip-test,team-web,triaged-web | low | Critical |
517,318,310 | flutter | Get pixel color of Canvas (CustomPaint) | Hello everyone!
We're creating an application using the CustomPaint widget to create some drawing stuffs.
All operations look good, but we miss the possibility of getting a pixel color from the current Canvas to do operations with them, like: custom filters, flood fill, etc.
Is it possible to add this? | c: new feature,framework,a: images,c: proposal,P3,team-framework,triaged-framework | low | Major |
517,330,141 | pytorch | torch.sum(tensor, dim=()) is different from np.sum(arr, axis=()) | ## 🐛 Bug
`torch.sum(tensor, dim=())` performs a full reduce, while `np.sum(arr, axis=())` performs no reduce.
## To Reproduce
Steps to reproduce the behavior:
```
import torch
import numpy as np
arr = np.array([1, 2, 3])
tensor = torch.from_numpy(arr)
tensor.sum(()) # gives tensor(6)
arr.sum(()) # gives np.array([1, 2, 3])
```
## Expected behavior
These should probably be the same. Also, I don't think it makes sense for `tensor.sum(dim=())` to do a full reduce. This special casing caused the bug at https://github.com/pytorch/pytorch/issues/28993 and I suspect the gradient for things like torch.var may be incorrect right now.
## Environment
Pytorch master
## Additional context
Some people who have been involved in multidim support who may be interested: @t-vi, @SsnL, @umanwizard @gchanan. Please let me know your opinions on this subject.
cc @ezyang @gchanan @zou3519 @jerryzh168 @SsnL | high priority,module: bc-breaking,triaged,module: numpy,module: TensorIterator,module: deprecation,module: reductions | medium | Critical |
517,332,740 | flutter | [Cupertino] on iPad, modals are shown in a popover, no way to show Cupertino style modals on iPad | <!-- Thank you for using Flutter!
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
* https://flutter.dev/
* https://api.flutter.dev/
* https://stackoverflow.com/questions/tagged/flutter?sort=frequent
If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->
The showCupertinoModalPopup shows a modal at the bottom of the screen. On iPad modals such as action sheets are shown via a popover.
<!--
Please tell us the problem you are running into that led to you wanting
a new feature.
Is your feature request related to a problem? Please give a clear and
concise description of what the problem is.
Describe alternative solutions you've considered. Is there a package
on pub.dev/flutter that already solves this?
-->
Currently there is no way to show Cupertino style modals on iPad.
<!--
Briefly but precisely describe what you would like Flutter to be able to do.
Consider attaching images showing what you are imagining.
Does this have to be provided by Flutter directly, or can it be provided
by a package on pub.dev/flutter? If so, maybe consider implementing and
publishing such a package rather than filing a bug.
-->
Example:
| e: device-specific,platform-ios,framework,a: tablet,a: fidelity,f: cupertino,a: quality,customer: crowd,P2,team-design,triaged-design | low | Critical |
517,340,826 | godot | [TRACKER] inst2dict and dict2inst related issues | **Godot version:**
3.2, 4.0+
**Issue description:**
There are quite a bunch of old issues present with `inst2dict` and `dict2inst` that it's worth to add a tracker for it. I'm currently working on some of them.
```[tasklist]
## Issues
- [ ] #6533
- [x] #26188
- [ ] #30077
- [ ] #30572
- [x] #31045
- [x] #33015
```
### Other issues
Orphan issues or which need more discussion.
* A class de-serialised with `dict2inst` fails if the class has moved it's path: https://github.com/godotengine/godot/issues/33348#issuecomment-549735838.
* `docs`: Fix the accessibility of the online API docs: https://github.com/godotengine/godot/issues/33348#issuecomment-549640679.
## Fixes
I think it would be best if these fixes could be reviewed in order so that smaller fixes can be rebased on top of bigger ones more easily if deemed satisfactory:
- [x] #33137
- [x] #33018
- [x] #32534
- [x] #33360
They could as well be targeted for 4.0 but see for yourself.
CC @vnen @bojidar-bg. | bug,topic:core,tracker | low | Minor |
517,381,045 | godot | Oversized 'X' in search fields when using a custom editor theme | **Godot version:**
3.1
**OS/device including version:**
Windows 10
Resolution 2560 x 1440p / UI Scaling 100%
**Issue description:**
The 'x' icon used to clear the search fields in the Godot editor interface appears to be too large, likely a retain/scaling issue.
| bug,topic:editor,confirmed | low | Minor |
517,386,614 | godot | Viewport Update Mode Once does not Reset | **Godot version:**
3.2 Alpha 3
**OS/device including version:**
OS: Xubuntu 19.10
CPU/GPU: Intel Atom z3735D
**Issue description:**
A viewport with render_target_update_mode = Viewport.UPDATE_ONCE does not reset the value for render_target_update_mode to Viewport.UPDATE_DISABLED after it has rendered. Likewise a viewport with render_target_clear_mode = Viewport.CLEAR_MODE_ONLY_NEXT_FRAME will always report a render_target_clear_mode of Viewport.CLEAR_MODE_ONLY_NEXT_FRAME even after that frame has passed.
The functionality works, the viewport will only be rendered once or cleared once, but you cannot poll the values of these variables to correctly determine the viewport's render and clear states.
**Steps to reproduce:**
Create a viewport, set render_target_clear_mode to Viewport.UPDATE_ONCE and check said viewport's render_target_clear_mode variable after it has updated.
**Minimal reproduction project:**
[ViewportBug.zip](https://github.com/godotengine/godot/files/3805970/ViewportBug.zip)
| discussion,topic:rendering | low | Critical |
517,387,313 | opencv | G-API feature proposal: endless loops detection for GAPI_TRANSFORM-related logic | ### Introduction
Recently I have been thinking about endless loops detection logic in `GCompiler` with regards to introduced graph transformations support. I have come up with an idea how we should be able to detect all (?) sorts of endless loops at the time of `GCompiler` constructor call by applying somewhat standard ideas.
I suggest this issue to be a discussion point for my idea where we could also share general thoughts on this feature's design.
related to #15313
**Disclaimer**: This is more of a feature request/design proposal for existing functionality rather than a bug or anything of the kind. Not finding any better place to discuss the idea, I decided to create this issue
### Problem statement
Having transformation logic in G-API graphs can introduce potential problem of looping endlessly applying graph transformations defined with `GAPI_TRANSFORM`: mainly, due to the fact that some transformations can "recurse" into each other.
Simple example:
```cpp
GAPI_TRANSFORM(EndlessLoopTransform, <cv::GMat(cv::GMat)>, "pattern in substitute")
{
static cv::GMat pattern(const cv::GMat& in)
{
return cv::gapi::resize(in, cv::Size(100, 100), 0, 0, cv::INTER_LINEAR);
}
static cv::GMat substitute(const cv::GMat& in)
{
cv::GMat b, g, r;
std::tie(b, g, r) = cv::gapi::split3(in);
auto resize = std::bind(&cv::gapi::resize,
std::placeholders::_1, cv::Size(100, 100), 0, 0, cv::INTER_LINEAR);
cv::GMat out = cv::gapi::merge3(resize(b), resize(g), resize(r));
return out;
}
};
```
Needless to say, in the presence of the example transformation, applying transformations for "as long as it is possible" can cause us serious troubles. The problem is, however, that there are more complex, non-straightforward transformation dependencies that can cause similar issues but are much harder to detect.
### Solution
In this section potential solution (algorithm) is proposed to address the problem stated.
#### Idea
Looking at patterns and substitutes and how they're handled within `GCompiler` reminds me of function calls:
- Imagine the following: compiler finds pattern `p_1` in original graph and substitutes it with `s_1`. Now, on the next iteration, pattern `p_2` is discovered being a part of newly substituted piece `s_1`
- In a sense, we can symbolically write this logic as `p_1 => s_1 => p_2 => s_2 => ...` sequence
- We don't really need to know about substitutes (`s_1`, `s_2`), but we do want to know about `p_1` and `p_2` and how they relate to each other. If the relation exists (as shown above), let's say that `p_1` "calls" `p_2`: so we end up having `p_1 => p_2 => ...` sequence
- For each pattern `p_i` within transformation `t_i`, we would love to know which patterns { `p_j` | `j = 0,...,transforms_num` } are "called" by `p_i` directly
- Well, now this resembles a concept of a call graph
- **It seems that finding loops in a call graph of `p_i` would automatically find loops in transformations with regards to `t_i`**
#### Algorithm
Input: array of transformations (with patterns and substitutes), length N
Output: exception throw/return "false" if loop detected, nothing/return "true" otherwise
```
// 1. Call graph construction phase
call_graph - map<pattern*, vector<pattern*>>;
* - pattern is uniquely identified by an _index_ in an array of transformations,
so we can simply use indices instead of actual patterns as key/values for call_graph
for (i in transformations)
create new call_graph element: {pattern_i, {}}
for (j in transformations)
if (pattern_j is found in substitute_i)
add new entry: call_graph[pattern_i].add(pattern_j)
// 2. Searching for loops
// we now have at most N graph components
for (i in range(0, N))
traverse the graph starting from call_graph[i]:
call_graph[i].key - "parent" node
call_graph[i].value - "child" nodes
at each iteration remember visited node
__if "children" contain visited node, we have found a loop__
```
### Concerns
- The algorithm is really a draft, I think it should work in principle but it might have some hidden flaws. Also it seems reasonable to think about some optimizations along to reduce the number of overall iterations
- Unsure if all possible loops are covered by such approach but it feels like that
- There were some concerns about __the order__ of how transformations are applied. Unfortunately, I do not remember the details, but I think that anything concerning the order might be addressed at phase 1 - "call graph construction"
| RFC,category: g-api / gapi | low | Critical |
517,401,981 | opencv | watershed giving not stable results | I keep getting not consistent results with watershed segmentation (providing the python test code below). I'm not sure if this is just weakness of the implemented algorithm or a bug. However when testing on the same data with scikit-image watershed I get correct results. My opencv version is 4.1.2
**dataset1** from opencv:
slice = [2,0,2,2,1,4,3,0,**0**]
```
image:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 4 0 0 0 0]
1 [ 0 2 0 2 2 1 4 3 0 0 0]
2 [ 0 2 0 2 2 1 4 3 0 0 0]
3 [ 0 2 0 2 2 1 4 3 0 0 0]
4 [ 0 0 0 0 0 0 4 0 0 0 0]
markers:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 0 0 0 0 0]
1 [ 0 0 0 0 0 0 0 0 0 0 0]
2 [ 0 0 2 0 0 0 0 0 0 4 0]
3 [ 0 0 0 0 0 0 0 0 0 0 0]
4 [ 0 0 0 0 0 0 0 0 0 0 0]
watershed:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
1 [ -1 2 2 2 2 2 -1 4 4 4 -1]
2 [ -1 2 2 2 2 2 -1 4 4 4 -1]
3 [ -1 2 2 2 2 2 -1 4 4 4 -1]
4 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
```
**dataset2** from opencv:
slice = [2,0,2,2,1,4,3,0,**2**]
```
image:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 4 0 0 0 0]
1 [ 0 2 0 2 2 1 4 3 0 2 0]
2 [ 0 2 0 2 2 1 4 3 0 2 0]
3 [ 0 2 0 2 2 1 4 3 0 2 0]
4 [ 0 0 0 0 0 0 4 0 0 0 0]
markers:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 0 0 0 0 0]
1 [ 0 0 0 0 0 0 0 0 0 0 0]
2 [ 0 0 2 0 0 0 0 0 0 4 0]
3 [ 0 0 0 0 0 0 0 0 0 0 0]
4 [ 0 0 0 0 0 0 0 0 0 0 0]
watershed:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
1 [ -1 2 2 2 2 2 2 -1 4 4 -1]
2 [ -1 2 2 2 2 2 2 -1 4 4 -1]
3 [ -1 2 2 2 2 2 2 -1 4 4 -1]
4 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
```
**dataset3** from opencv:
slice = [2,0,2,2,1,4,3,**2,1**]
```
image:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 4 0 0 0 0]
1 [ 0 2 0 2 2 1 4 3 2 1 0]
2 [ 0 2 0 2 2 1 4 3 2 1 0]
3 [ 0 2 0 2 2 1 4 3 2 1 0]
4 [ 0 0 0 0 0 0 4 0 0 0 0]
markers:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 0 0 0 0 0 0 0 0 0 0 0]
1 [ 0 0 0 0 0 0 0 0 0 0 0]
2 [ 0 0 2 0 0 0 0 0 0 4 0]
3 [ 0 0 0 0 0 0 0 0 0 0 0]
4 [ 0 0 0 0 0 0 0 0 0 0 0]
watershed:
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
1 [ -1 2 2 2 2 -1 4 4 4 4 -1]
2 [ -1 2 2 2 2 -1 4 4 4 4 -1]
3 [ -1 2 2 2 2 -1 4 4 4 4 -1]
4 [ -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1]
```
On the other hand scikit-image watershed in all cases gives correct result:
watershed:
```
[ c0 c1 c2 c3 c4 c5 c6 c7 c8 c9 c10 ]
0 [ 2 2 2 2 2 2 2 4 4 4 4]
1 [ 2 2 2 2 2 2 2 4 4 4 4]
2 [ 2 2 2 2 2 2 2 4 4 4 4]
3 [ 2 2 2 2 2 2 2 4 4 4 4]
4 [ 2 2 2 2 2 2 2 4 4 4 4]
```
python code for testing:
```
import numpy as np
import cv2
# from skimage.morphology import watershed
print(cv2.__version__)
def printer(mat):
row_labels = range(mat.shape[0])
col_labels = range(mat.shape[1])
print(' [ %s ]' % (' '.join(' c%s' % i for i in col_labels)))
for (row_label, row) in zip(row_labels, mat):
print('%s [%s]' % (row_label, ' '.join('%03s' % i for i in row)))
slice = [2,0,2,2,1,4,3,2,1]
gray = np.zeros((5,11), np.uint8)
gray[1,1:-1] = slice
gray[2,1:-1] = slice
gray[3,1:-1] = slice
gray[0,6] = 4
gray[-1,6] = 4
print('image:')
print(printer(gray))
# color = cv2.cvtColor(tab, cv2.COLOR_GRAY2BGR)
color = np.dstack((gray, gray, gray))
markers = np.zeros((5,11), np.int32)
markers[2,-2] = 4
markers[2, 2] = 2
print('markers:')
print(printer(markers))
# markers = watershed(gray, markers)
markers = cv2.watershed(color, markers)
print('watershed:')
print(printer(markers))
```
| category: imgproc | low | Critical |
517,409,146 | flutter | Always highlight the selected widget on the device | Currently you have to call
`ext.flutter.inspector.show` to enable the inspector before selected widgets can be highlighted on the device.
enabling the on device inspector is conflated with inspector select mode.
Suggested solution:
`add ext.flutter.inspector.selectMode` extension that toggles whether clicking on the device should select widgets
and
`ext.flutter.inspector.enable` extension that enables the on device inspector but does not enter select mode.
Clients can call
`ext.flutter.inspector.enable` any time they will use the on device inspector.
the existing `ext.flutter.inspector.show` extension will be left for ~6 months for backwards compatibility with existing IDE plugins. The `show` extension will continue to both enable the inspector and enter select mode.
| c: new feature,framework,f: inspector,d: devtools,P3,team-framework,triaged-framework | low | Minor |
517,430,214 | rust | Fix: mark relevant spans (ex: ident.span) with macro expansion context | In #65830 it was discovered that `hir::Item.ident.span` isn't marked `with_ctxt` of being part of a macro expansion. This had two effects that we saw there:
- error messages don't include the "in this macro invocation" hints
- cases where the dead_code error was suppressed because of foreign macros were no longer suppressed
To solve that there, we're going to just use the old behavior when we're in the middle of a macro expansion already, so we don't use the un-marked span. As @estebank suggested, we should probably clean this up in a separate change. | C-cleanup,A-macros,T-compiler | low | Critical |
517,451,368 | TypeScript | Find all references doesn't find all results and crashes tsserver if `type S = import().S` syntax is used | <!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:** 3.9.0-dev.20200223, 3.8.2
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** Find all references crash tsserver reexport
**Code**
[Reproduction repo](https://github.com/InExtremaRes/find-references-ts-bug/tree/bug1)
file1.ts
```ts
export class Foo {}
export class Bar {}
```
file2.ts
```ts
import * as f1 from './file1';
export class Container {
readonly classes = f1;
}
declare const c: Container;
c.classes.Foo;
// Uncommenting this line make 'Find all references' work again
// export { f1 };
```
file3.ts
```ts
import { Container } from './file2';
declare const c: Container;
// 'Go to definition' works from here but 'Find all references' doesn't show this line
c.classes.Foo;
```
**Expected behavior:**
All three references to `Foo` are shown, in `file1.ts`, `file2.ts` and `file3.ts`.
**Actual behavior:**
Reference in `file3.ts` is not shown.
**Workaround?:**
Uncommenting `// export { f1 };` in `file2.ts` makes all references to be found, even if no other file imports `f1`.
---
<details>
<summary> EDITED (2020-02-23): I tested this section with TS 3.8.2 and doesn't crash tsserver anymore</summary>
In the same repo, but [another branch](https://github.com/InExtremaRes/find-references-ts-bug/tree/bug2) it is shown that with a new file:
file4.ts
```ts
type S = import('./file3').S;
```
find all references on `Foo` crashes tsserver. Changing file4 to:
```ts
import { S } from './file3';
```
avoid the crash. The [tsserver.log](https://github.com/InExtremaRes/find-references-ts-bug/blob/bug2/tsserver.log) shows:
```plain
{"seq":11,"type":"request","command":"references","arguments":{"file":"/tmp/find-references-ts-bug/file3.ts","line":5,"offset":12}}
Err 109 [19:9:26.28] Exception on executing command {"seq":11,"type":"request","command":"references","arguments":{"file":"/tmp/find-references-ts-bug/file3.ts","line":5,"offset":12}}:
Debug Failure. False expression.
Error: Debug Failure. False expression.
at getSourceFileLikeForImportDeclaration (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:109406:22)
at addIndirectUsers (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108990:42)
at addIndirectUsers (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108990:25)
at handleNamespaceImport (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108964:25)
at handleDirectImports (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108929:37)
at getImportersForExport (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108878:13)
at State.importTracker (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:108854:26)
at State.getImportSearches (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110199:33)
at searchForImportsOfExport (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110248:32)
at getImportOrExportReferences (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110672:21)
at getReferencesAtLocation (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110592:17)
at getReferencesInContainer (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110536:21)
at getReferencesInContainerOrFiles (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110095:21)
at getReferencedSymbolsForSymbol (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:110086:21)
at Object.getReferencedSymbolsForNode (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:109889:34)
at Object.findReferencedSymbols (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:109567:60)
at Proxy.findReferences (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:130935:41)
at /tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139099:68
at callbackProjectAndLocation (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139180:13)
at /tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139127:24
at forEachProjectInProjects (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139109:17)
at combineProjectOutputWorker (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139124:13)
at combineProjectOutputForReferences (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139080:13)
at IOSession.Session.getReferences (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:140208:34)
at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:139339:61)
at /tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:140942:88
at IOSession.Session.executeWithRequestId (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:140933:28)
at IOSession.Session.executeCommand (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:140942:33)
at IOSession.Session.onMessage (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:140965:35)
at Interface.<anonymous> (/tmp/find-references-ts-bug/node_modules/typescript/lib/tsserver.js:142280:27)
at Interface.emit (events.js:182:13)
at Interface._onLine (readline.js:290:10)
at Interface._normalWrite (readline.js:433:12)
at Socket.ondata (readline.js:149:10)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
File text of /tmp/find-references-ts-bug/file3.ts:
import { Container } from './file2';
declare const c: Container;
// 'Go to definition' works from here but 'Find all references' doesn't
c.classes.Foo;
export type S = {};
```
</details>
**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Maybe #28680 | Domain: Symbol Navigation | low | Critical |
517,463,248 | flutter | Perform device to host texture transfer on the IO thread. | Capturing a snapshot of a scene is extremely expensive (multiple frame intervals worth of time) and needs to happen on the GPU thread within a frame workload. Because of this, operations like Scene.toImage and Picture.toImage can potentially cause extreme amounts of jank in a Flutter application.
The sequence of operations that need to be performed to realize a host snapshot allocation are as follows:
* The application on the UI thread calls Scene.toImage or Picture.toImage. The scene first needs to be converted into a device image before moving the device image allocation to the host.
* Since the scene itself may reference other device images, the realization of the device image for the snapshot can only happen on a thread with a GPU context. The UI threads does not have such a context. It must therefore be submitted to either the GPU or IO threads. The GPU and IO thread contexts are in the same sharegroup and OpenGL image handles can be shared between the same. However, Skia maintains state along with the handle that is not safe to access from multiple threads concurrently. The restriction means that while texture backed Skia images can be used on either the GPU or IO thread contexts, the images may not be used simultaneously on both. While the engine would ideally like to realize the device image for the snapshot on the IO thread, it cannot do so because the GPU thread may be using that image to render the same onscreen. So, the engine is forced to do this step on the GPU task runner.
* While having to realize device image for the snapshot on the GPU thread is unfortunate, it is nowhere near the bottleneck when it comes to the total time taken on the CPU. That step is the device to host transfer. Ideally, the texture used as the color attachment of the framebuffer could be stolen as a Skia image and sent to IO thread where the device to host transfer can happen. However, the only available API for the creation of a snapshot from a surface (the Skia abstraction for a render target / framebuffer) returns a regular SkImage (SkSurface::makeImageSnapshot). Only images created using SkImage::MakeCrossContextFromPixmap may be shared between contexts. This makes the resulting image unsuitable for cross context sharing for purposes of device to host transfer. The engine also cannot steal the GrBackendRender target from the SkSurface and create a cross context image from the same because the only constructor for the creation of a cross context image is a pixmap. The entire point of the dance is to get a pixmap. Out of options, the engine uses the SkSurface::makeImageSnapshot call on the GPU followed immediately by the SkImage::makeRasterImage call to perform the device to host transfer. All frames rendered by the Flutter application are now susceptible to jank.
To fix the performance issues mentioned above, the entire series of operations were moved to the IO thread. This was because the concurrent use restrictions was not apparent to engine authors. Once issues related to this violation were surfaced in https://github.com/flutter/flutter/issues/43085, the patch was reverted in https://github.com/flutter/engine/pull/13467.
To get back the performance improvements while maintaining threading correctness, one of the following API enhancements from Skia would be necessary:
* The ability to create cross context images from backend textures or backend render targets. The engine can then steal the color attachment of the framebuffer and use that to create a cross context texture on the GPU thread. The image can then be sent to the IO thread for device to host transfer.
* Make the SkSurface::makeImageSnapshot return a cross context image directly.
* Internally, Skia fences access to the data structures so that concurrent read access to the texture is possible.
| c: new feature,engine,c: performance,dependency: skia,P2,team-engine,triaged-engine | low | Major |
517,504,893 | pytorch | Modules without copying in multiprocess | I tried to use a multi-process inference model,but the following occurred:
process number ==1: GPU Memory-usage: 1933mib。
process number ==2: GPU Memory-usage: 3028mib。
......
process number ==10: GPU Memory-usage: 11310mib。
code:
| module: multiprocessing,triaged | low | Minor |
517,522,049 | pytorch | [FR] trace_module traces both eval and train graph | The current `jit.trace_module` returns a `ScriptModule` that behaves the same in `eval` and `train` mode, i.e., always executing the graph that is equivalent to the module at tracing time. This makes it hard to trace a Module's train and eval graph, and combine them together in a single returned `ScriptModule`
cc @suo | oncall: jit,triaged,enhancement | low | Minor |
517,530,450 | electron | Proposal for new module: shortcuts | Right now, we have the `globalShortcuts` module for registering shortcuts that apply to the entire system even when the Electron app is not focused.
I'd like to propose a new `shortcuts` module and deprecating the existing `globalShortcuts` module. The API would look like so:
```js
const { shortcut } = require('electron');
let alreadyRegistered = shortcut.register('normal', 'CmdOrCtrl+L', () => {
// Normal priority shortcut, handled after web content. Web content may preventDefault().
});
let alreadyRegistered = shortcut.register('high', 'CmdOrCtrl+L', () => {
// High priority shortcut, handled before web content.
});
let alreadyRegistered = shortcut.register('global', 'CmdOrCtrl+L', () => {
// Similar to existing globalShortcuts.register(), handled before web content.
});
let registed = shortcut.isRegistered('CmdOrCtrl+L');
shortcut.unregister('CmdOrCtrl+L');
```
There is clear demand for this feature, see #1334 and https://github.com/parro-it/electron-localshortcut
Implementing this within Electron would be much better because the accelerators would be parsed and handled like we already handle `Menu` accelerators. Properly processing the accelerators is tricky and error-prone - `electron-localshortcut` has several bugs and we have had multiple bugs in our own custom implementation as well.
I'm happy to implement this, but I wanted to hear your thoughts first!
cc @electron/wg-api | enhancement :sparkles: | low | Critical |
517,530,511 | react | Is it possible to share contexts between renderers? | **What is the current behavior?**
Hey 👋 I maintain [react-pdf](https://github.com/diegomura/react-pdf). Thanks for your awesome work and making `react-reconciler` for us to use!
I've got many issues lately regarding context not working on my library and when doing tests I found out that context values aren't shared between renderers. This makes it impossible to share state such as themes, i18n, redux and more. As a bit of context, React-pdf is not a primary renderer, and as such, when used in the browser it runs on top of react-dom.
I found the `isPrimaryRenderer` reconciler option that's supposed to be used for "multiple renderers concurrently render using the same context objects" but still any access of the context inside react-pdf components get's just the initial value (even if the context was updated with other value). The same happens for `react-art` that also set `isPrimaryRenderer=false`.
**Minimal demo**
I prepared a quick demo using react-art so you can see how it currently works:
https://codesandbox.io/s/pedantic-hill-54kid?fontsize=14
**What is the expected behavior?**
Share contexts between renderers when using `isPrimaryRenderer` config. Is there a way of achieving this? Am I missing something?
**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
React: 16.11.0
React-dom: 16.11.0
| Type: Enhancement,Component: Reconciler | medium | Critical |
517,537,830 | go | x/build/cmd/coordinator: add timeout to make.bash | It seems the build coordinator doesn't have a timeout on the make.bash phase?
This Mac builder is stuck in make.bash for over 4 hours:
```
darwin-amd64-10_14 rev 2566e21f; running; http://macstadium_host07b reverse peer macstadium_host07b/207.254.3.58:60202 for host type host-darwin-10_14, 4h48m28s ago
2019-11-04T23:20:00Z checking_for_snapshot
2019-11-04T23:20:01Z finish_checking_for_snapshot after 377.4ms
2019-11-04T23:20:01Z get_buildlet
2019-11-04T23:20:01Z wait_static_builder host-darwin-10_14
2019-11-04T23:20:01Z finish_wait_static_builder after 0s; host-darwin-10_14
2019-11-04T23:20:01Z clean_buildlet http://macstadium_host07b reverse peer macstadium_host07b/207.254.3.58:60202 for host type host-darwin-10_14
2019-11-04T23:20:01Z finish_clean_buildlet after 32.1ms; http://macstadium_host07b reverse peer macstadium_host07b/207.254.3.58:60202 for host type host-darwin-10_14
2019-11-04T23:20:01Z finish_get_buildlet after 276.1ms
2019-11-04T23:20:01Z using_buildlet macstadium_host07b
2019-11-04T23:20:01Z write_version_tar
2019-11-04T23:20:01Z get_source
2019-11-04T23:20:05Z finish_get_source after 3.9s
2019-11-04T23:20:05Z write_go_src_tar
2019-11-04T23:20:11Z finish_write_go_src_tar after 6.16s
2019-11-04T23:20:11Z make_and_test
2019-11-04T23:20:11Z make src/make.bash
+17297.4s (now)
```
| help wanted,NeedsInvestigation | low | Minor |
517,549,861 | godot | Computer freezes due to searching in the inspector | **Godot version:**
Godot 3.2 alpha-3 mono
**OS/device including version:**
ArcoLinux
**Issue description:**
When searching the inspector while inspecting a theme (with the editor template, hence tons of properties to search through), Godot will sometimes freeze up and start eating up all of the computer's memory. "Object was deleted while awaiting a callback" is spammed into the console while memory usage skyrockets, until the PC becomes unresponsive. It's necessary to force shut down the computer to get things back to normal.
**Steps to reproduce:**
Not sure, since it doesn't happen all the time. Try creating a blank editor template theme and start editing bits of it and searching through its properties. Eventually the editor should freeze up along with the console spam after some random search. | bug,topic:editor | low | Minor |
517,673,177 | pytorch | How to run two different jit models in two GPUs respectively in one scrip? | I have an encoder-decoder model. After converted encoder and decoder model into jit models, I want to load encoder on GPU:0 and the encoder outputs **Keys** and **Value**. Then I move the **Keys** and **Values** to GPU:1 since the decoder is loaded on GPU:1.
encoder = torch.jit.load(feat_model).cuda(0)
gru_decoder = torch.jit.load(gru_model, map_location=torch.device("cpu")).cuda(1)
loader = getLoader(data_path, batch_size)
for data in loader:
audio, label = data
batch_size = audio.size(0)
k, v = encoder(audio.type("torch.FloatTensor").cuda(0))
k = k.cuda(1)
v = v.cuda(1)
hidden = torch.zeros(1, batch_size, 512).type("torch.FloatTensor").cuda(1)
target = torch.tensor(sos_id).repeat(batch_size).cuda(1)
for step in range(k.size(1)):
probs, hidden = gru_decoder(target, hidden, k, v)
target = torch.argmax(probs, dim=-1)
I have checked that target, hidden, k, v are on GPU:1. However, an error occurs:
arguments are located on different GPUs at /pytorch/aten/src/THC/generic/THCTensorIndex.cu:519:
operation failed in interpreter:
op_version_set = 0
def forward(self,
target: Tensor,
hx: Tensor,
keys: Tensor,
values: Tensor) -> Tuple[Tensor, Tensor]:
input_1 = torch.to(target, dtype=4, layout=0, device=torch.device("cuda"), non_blocking=False, copy=False)
_0 = torch.embedding(self.classifier.embedding.weight, input_1, -1, False, False)
~~~~~~~~~~~~~~~ <--- HERE
input_2 = torch.unsqueeze(_0, 1)
_1 = [self.classifier.rnn.weight_ih_l0, self.classifier.rnn.weight_hh_l0, self.classifier.rnn.bias_ih_l0, self.classifier.rnn.bias_hh_l0]
querys, _2 = torch.gru(input_2, hx, _1, True, 1, 0., False, False, True)
_3 = torch.matmul(keys, torch.permute(querys, [0, 2, 1]))
input_3 = torch.div(_3, CONSTANTS.c0)
attn_w = torch.softmax(input_3, 1)
sums = torch.matmul(torch.permute(attn_w, [0, 2, 1]), values)
input_4 = torch.view(torch.add(querys, sums, alpha=1), [-1, 512])
input = torch.addmm(self.classifier.h.bias, input_4, torch.t(self.classifier.h.weight), beta=1, alpha=1)
It seems that the embedding layer in decoder is on GPU:0. But I have already set decoder on CUDA:1.
Does anyone have any solutions or ideas? Thanks a lot.
cc @suo | oncall: jit,triaged | low | Critical |
517,697,216 | flutter | Allow control over TextField labelText spacing | I need to implement a design where text field labels are farther up from the text field top.
I don't see any way Flutter allows this.
The closest thing is labelStyle height but it breaks label completely when it needs to wrap horizontally. | a: text input,c: new feature,framework,f: material design,a: typography,P3,team-text-input,triaged-text-input | low | Minor |
517,698,422 | flutter | decodeImageFromList shows error when convert YUV420 to ui.Image | <!-- Thank you for using Flutter!
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
* https://flutter.dev/
* https://api.flutter.dev/
* https://stackoverflow.com/questions/tagged/flutter?sort=frequent
If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->
## Steps to Reproduce
Hi Team ,
I'm trying to make a real-time image filter based on CameraController widget. But when I tried to convert controller.planes to Uint8List and convert it from YUV420 to ui.Image, it always show error
**### "Exception has occurred.
_Exception (Exception: Could not instantiate image codec.)"**
step to implement a real-time image filter (what I've thought):
1. get image from CameraController.startImageStream(image)
2. convert CameraImage to ui.Image so I can use canvas to draw it on screen.
3. for canvas there is a way to use colorFilter to make a colorFilter matrix(4 X 5 )
4.finally I'll use a canvas to replace the CameraPreviewer to show the processed cameraImage
Problems here:
Flutter may be not having a convenient solution for matrix operation (like numpy in python, or just I haven't found) and it will take a long time to process the image and cannot achieve a 60fps animation based on my solution.( or any other solution suggested? Thanks in advanced)
When tried to convert YUV420 to ui.Image, I found another interesting "problem"
The Image size is width:720 height:1280, the length of bytes in cameraImage.planes[0] (Y channel ) is 921600.
Based on the description from Wiki or any other website, the U and V channel should be half of Y channel, but in Flutter, the length for U and V is 1 byte less.
Y---921,600
U---460,799
V---460,799
Is this the root cause when failed to convert YUV420 or why it's 1 bytes less then half of Y channel?
### code FYI
controller.startImageStream((CameraImage image) async {
if (!ifProcess && mounted) {
ifProcess = true;
.......
List<int> bytes=List<int>();
image.planes.forEach((plane){
plane.bytes.toList().forEach((byte){
bytes.add(byte);
});
});
img = await decodeImageFromList(
Uint8List.fromList(bytes),
);
.......
} else {
return;
}
}).catchError((e) {
ifProcess = false;
});
This could not run on simulator as it requires to use camera.
**Target Platform:** Android
**Target OS version/browser:** 9.1.0.226
**Devices:** real device
## Logs
### flutter run
[ +65 ms] I/GRALLOC (19935): LockFlexLayout: baseFormat: 11, yStride: 1280, ySize: 921600,
uOffset: 921600, uStride: 1280
[ +67 ms] I/GRALLOC (19935): LockFlexLayout: baseFormat: 11, yStride: 1280, ySize: 921600,
uOffset: 921600, uStride: 1280
[ +49 ms] I/GRALLOC (19935): LockFlexLayout: baseFormat: 11, yStride: 1280, ySize: 921600,
uOffset: 921600, uStride: 1280
[ +62 ms] I/GRALLOC (19935): LockFlexLayout: baseFormat: 11, yStride: 1280, ySize: 921600,
uOffset: 921600, uStride: 1280
### flutter analyze
Analyzing realtime_camera...
info • Unused import: 'package:vector_math/vector_math_64.dart' • lib/main.dart:9:8 •
unused_import
info • Unused import: 'package:linalg/matrix.dart' • lib/main.dart:11:8 • unused_import
info • The value of the local variable 'u' isn't used • lib/main.dart:83:11 •
unused_local_variable
info • The value of the local variable 'v' isn't used • lib/main.dart:84:11 •
unused_local_variable
info • The value of the local variable 'r' isn't used • lib/main.dart:85:15 •
unused_local_variable
info • The value of the local variable 'g' isn't used • lib/main.dart:86:15 •
unused_local_variable
info • The value of the local variable 'b' isn't used • lib/main.dart:87:15 •
unused_local_variable
info • The value of the local variable 'matrix' isn't used • lib/main.dart:194:17 •
unused_local_variable
info • The value of the local variable 'rightY' isn't used • lib/main.dart:298:14 •
unused_local_variable
No issue, just not used of local variable.
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15 19A583, locale zh-Hans-CN)
• Flutter version 1.9.1+hotfix.6 at /Users/geyan/development/flutter
• Framework revision 68587a0916 (7 weeks ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/geyan/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.0, Build version 11A420a
• CocoaPods version 1.8.3
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 39.0.3
• Dart plugin version 191.8423
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.39.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.6.0
[✓] Connected device (1 available)
• ELE AL00 • 8KE0219323014086 • android-arm64 • Android 9 (API 28)
• No issues found!
| c: crash,a: quality,p: camera,package,team-ecosystem,P3,triaged-ecosystem | low | Critical |
517,706,402 | flutter | [web] SelectableText doesn't show toolbar | ## Problem
> Flutter 1.10.14 • channel dev
- flutter for web
Want to copy String_data in the flutter for web.
- clipboard
When trying clipboard in the flutter web , cant copy the text.
```
import 'package:flutter/services.dart';
Clipboard.setData(ClipboardData(text: 'data'));
```
- SelectableText
When tap it, do not appear toolbar.
```
SelectableText(
'SelectableText',
showCursor: true,
enableInteractiveSelection: true,
toolbarOptions: ToolbarOptions(copy: true),
style: TextStyle(height: 2),
),
```
| platform-ios,framework,f: material design,a: quality,a: typography,platform-web,has reproducible steps,P2,found in release: 3.3,found in release: 3.5,team-design,triaged-design | low | Major |
517,739,860 | rust | Mark Result::{ok,err} as #[must_use] | In a discussion in our Rust group, someone incorrectly uses `ok()` without checking its return value, causing confusing issue. As `Result::{is_ok, is_err}` are already marked `#[must_use]` in #59610, I don't see any reason `Result::{ok, err}` shouldn't be.
cc #48926 | T-libs-api,C-feature-request | low | Major |
517,745,995 | opencv | CV_OCL_RUN_ (the default implementation) should not swallow exceptions | ##### System information (version)
- OpenCV => master branch
##### Detailed description
CV_OCL_RUN_ should not swallow exceptions. It gets called when running OpenCL kernels, so when doing GPU acceleration (I was using BackgroundSubtractorMOG2). This is how it is now implemented by default:
```.cpp
#define CV_OCL_RUN_(condition, func, ...) \
try \
{ \
if (cv::ocl::isOpenCLActivated() && (condition) && func) \
{ \
CV_IMPL_ADD(CV_IMPL_OCL); \
return __VA_ARGS__; \
} \
} \
catch (const cv::Exception& e) \
{ \
CV_UNUSED(e); /* TODO: Add some logging here */ \
}
```
From: https://github.com/opencv/opencv/blob/5dd46b54c10b4d18041598eb0f96d062cc8420fe/modules/core/include/opencv2/core/opencl/ocl_defs.hpp
There are some guilty feelings already, expressed in the todo ;-) Imo, it should not catch exceptions at all, let them roll upwards instead and let the caller handle it. | category: ocl,RFC | low | Minor |
517,759,916 | flutter | Expose Skia Paint.getFillPath | Please expose Skia Paint getFillPath
https://skia.org/user/api/SkPaint_Reference#SkPaint_getFillPath
## Use case
Multiple, we can draw the stroke path outline, check point on path
| c: new feature,engine,c: proposal,P3,team-engine,triaged-engine | low | Minor |
517,762,587 | rust | rustc generates invalid DWARF when LTO is enabled | When combining `lto = true` with `debug = true` in Cargo.toml, the compiler generates invalid DWARF, according to [Gimli](https://github.com/gimli-rs/gimli.git).
I've created a minimal example here: https://github.com/hannobraun/dwarf-test
If you follow the instructions in the example's README, you should see something like this:
```
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13d1b to 0x492
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13d30 to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13d4a to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13d59 to 0x5e2
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13d91 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13da6 to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13dce to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13de2 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13dfb to 0x2b31
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e10 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e25 to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e4d to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e61 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e87 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13e9c to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13ec4 to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13ed8 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13ef1 to 0x2b31
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13f06 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13f1b to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13f43 to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13f57 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13fb5 to 0x4ac
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13fca to 0x49f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13fdf to 0x492b
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x13ff4 to 0x523c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14009 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14022 to 0x4893
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1402f to 0x4880
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14049 to 0x4b9
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14056 to 0x5ef
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14063 to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14085 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1409c to 0x5fc
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x140b1 to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x140db to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x140f2 to 0x609
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14107 to 0x616
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1411c to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14146 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1415d to 0x609
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14172 to 0x616
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14187 to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x141b1 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x141c8 to 0x609
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x141dd to 0x616
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x141f7 to 0x4e0
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1420c to 0x62d
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14221 to 0x4d3
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14236 to 0x4945
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1424b to 0x4938
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14279 to 0x492
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1428e to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x142a8 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x142b7 to 0x5e2
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x142c5 to 0x492
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x142da to 0x491e
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x142f4 to 0x522f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14303 to 0x5e2
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14326 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1433b to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14363 to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14377 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14390 to 0x2b31
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x143a5 to 0x4857
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x143ba to 0x536c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x143e2 to 0xf5
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x143f6 to 0xe8
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x144ea to 0x3e22
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14528 to 0x4531
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14551 to 0x4ed
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14582 to 0x453d
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14d39 to 0x4100
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14dcb to 0x3e38
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14e10 to 0x412c
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14e29 to 0x3e4b
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x14e3e to 0x4b11
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x174a6 to 0x6cf
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x17532 to 0x6cf
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x175be to 0x6cf
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x17652 to 0x6cf
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x1770d to 0x7ac
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x178c3 to 0x816
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x178d8 to 0x36f
DWARF error in ../dwarf-test/target/debug/dwarf-test: Invalid intra-unit reference in unit 0x102 from DIE 0x17903 to 0x37c
```
I've seen this first in a larger project. There, the combination of `lto = true` and `debug = true` also causes GDB to freeze when reading the symbols from the binary. I wasn't able to reproduce this in my minimal example, but in the larger project, all binaries that caused GDB to freeze produced these DWARF errors, while I didn't see these errors in the binaries that worked normally.
So while I'm not 100% sure that these DWARF errors are a real problem, I suspect that they're the cause of the GDB freezes I was seeing. | A-LLVM,A-debuginfo,E-needs-test,T-compiler,C-bug | medium | Critical |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.