sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Consensus and media for translation partners
Labels: discussion,topic:editor,documentation

I put it here and not in the documentation because this problem affects the editor's translations.

Recently there was a problem between translation collaborators in which a new user without knowing the translation conventions we have been following began to make changes without prior notice, this caused quite a lot of work reversing changes and not little discussion trying to make the user understand that this type of problems should be consulted before doing it on their own, but this problem left something else patent and is that we need a means to agree between translation collaborators:

- There is already a Discord channel in Spanish, but it is general, if there is a debate about translations, it is often lost among other topics of conversation outside the subject and the same thing I imagine will happen with the other languages; we could make consensus directly in GitHub but this medium I see more oriented to programming issues, problems of the editor and so on, so each language needs a means to bring together all the collaborators and be able to make translation consensus more easily.

- Another issue is that in Weblate to be open precisely is difficult to control when a new user enters and without consulting very drastic changes, I do not know if you can put a level of permissions but regardless of this each language would need between 1 and 2 moderators for those who focus on Spanish translations (for example) moderate translations in the language in which you are collaborating and not have people who do not know the language trying to mediate in a language they do not know.

Greetings and thank you for your attention.
Repository: vscode
Issue: Add vscode.workspace.fs.createWriteStream().
Labels: feature-request,api,file-io,api-proposal

(see #84175)

For the Python extension, we currently use node's fs.createWriteStream() for a variety of purposes:

1. downloading multi-MB files (and tracking progress)
   * calling into a third-party library that expects an `fs.WriteStream`
2. writing generated data out to a file a chunk at a time
3. writing log data out to a file, one entry at a time

For example:
* https://github.com/microsoft/vscode-python/blob/master/src/client/debugger/extension/adapter/logging.ts#L55
* https://github.com/microsoft/vscode-python/blob/master/src/client/common/net/fileDownloader.ts#L39

@jrieken
Repository: TypeScript
Issue: Drop emit of last semicolon in single-line object literal types
Labels: Suggestion

Tracking follow-up to #33402

When synthetic object literal type nodes are printed on a single line, they come out like

```ts
type X = { a: string; b: string; };
```

While working on semicolon formatting features, I briefly had the formatter remove the semicolon after `b: string;`. The result was well-received but I ultimately decided the logic didn’t belong in the formatter; if this was going to be the canonical formatting of single-line object type literals, they should simply come out of the emitter that way.
Repository: flutter
Issue: Refactor the Animation / section organizer demo in Flutter Gallery to use LinkedScrollView-like logic
Labels: team,framework,f: material design,f: scrolling,P2,c: tech-debt,team-design,triaged-design

The Animation / section organizer demo is the last place using the deprecated jumpToWithoutSettling. It's using it as a workaround to the way it was designed. It currently uses scroll notification listeners to force two unrelated lists to share a scroll position. A better solution would be to have them share a scroll position, in a similar way to how the LinkedScrollView test does its thing.

(I'm trying to remove jumpToWithoutSettling, since it's been deprecated since forever.)
Repository: TypeScript
Issue: Suggestion: Config files authored in JS should automatically have intellisense support
Labels: Suggestion

Some libraries (e.g. Babel, Webpack, ESLint) use JS files for their config files.

We don't automatically provide IntelliSense support for these - however, the existing definitions (at least for Babel and Webpack) do provide types that describe the module shape of the files, so they can be manually set up today with a JSDoc comment.

It may be possible to provide a mechanism for associating these config files with their @types packages, and allowing those packages to specify that a given type expresses the module shape of the config file.

Courtesy of @uniqueiniquity 

First suggested here: https://developercommunity.visualstudio.com/content/idea/385119/better-webpack-support.html
Repository: vscode
Issue: breadcrumb menu doesn't need to start in disclosed state on go files
Labels: under-discussion,breadcrumbs

Go can only have one package in a file so it's unnecessary (pointless) to force another click on the disclosure triangle to show the rest of the menu to see the functions you wanted to see to begin with.

<img width="459" alt="Screen Shot 2019-11-11 at 4 42 48 PM" src="https://user-images.githubusercontent.com/20665/68627465-6b06a780-04a3-11ea-90ab-5be34b5e5fa9.png">
Repository: pytorch
Issue: [jit] Script class attributes aren't automatically added
Labels: oncall: jit,triaged

See https://discuss.pytorch.org/t/jit-scripted-attributes-inside-module/60645

cc @suo
Repository: go
Issue: math/big: apply simplification suggested in CL 73231 (or abandon)
Labels: NeedsDecision

Reminder issue: Decide whether to apply https://go-review.googlesource.com/c/go/+/73231 for Go 1.15 (early) or abandon.

Specifically: The change must be applied to the new function lehmerSimulate. Also, need to verify that there's no performance regression.
Repository: go
Issue: cmd/compile: infinite loop in -m=2
Labels: NeedsFix

This compilation unit goes into an infinite loop when compiled with `-m=2`:

```
package x

type Node struct {
	Orig *Node
}

func (n *Node) copy() *Node {
	x := *n
	x.Orig = &x
	return &x
}

func f(n0 *Node) {
	n1 := n0.copy()
	n2 := n1.copy()
	sink = n2
}

var sink *Node
```

Distilled from cmd/compile/internal/gc, pointed out by @dr2chase .
Repository: go
Issue: x/tools/gopls: improve error message when using wrong go command with Go source distribution
Labels: gopls,Tools

#### What did you do?
From the [go/src/cmd](https://github.com/golang/go/tree/master/src/cmd) dir:
```
gopls -rpc.trace -v check compile/main.go
```

#### What did you expect to see?
The command succeeds.


#### What did you see instead?
The command times out after 30s. Output: [gopls.txt](https://github.com/golang/go/files/3833678/gopls.txt)


#### Build info

```
golang.org/x/tools/gopls 0.2.0
    golang.org/x/tools/gopls@v0.2.0 h1:ddCHfScTYOG6auAcEKXCFN5iSeKSAnYcPv+7zVJBd+U=
    github.com/BurntSushi/toml@v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
    github.com/sergi/go-diff@v1.0.0 h1:Kpca3qRNrduNnOQeazBd0ysaKrUJiIuISHxogkT9RPQ=
    golang.org/x/sync@v0.0.0-20190423024810-112230192c58 h1:8gQV6CLnAEikrhgkHFbMAEhagSSnXWGV915qUMm9mrU=
    golang.org/x/tools@v0.0.0-20191108194844-46f05828f2fe h1:FNzasIzfY1IIdyTs/+o3Qv1b7YdffPbBXyjZ5VJJdIA=
    golang.org/x/xerrors@v0.0.0-20190717185122-a985d3407aa7 h1:9zdDQZ7Thm29KFXgAX/+yaf3eVbP7djjWp/dXAppNCc=
    honnef.co/go/tools@v0.0.1-2019.2.3 h1:3JgtbtFHMiCmsznwGVTUWbgGov+pVqnlf1dEJTNAXeM=
```

#### Go info

```
go version go1.13.4 darwin/amd64

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/russell/Library/Caches/go-build"
GOENV="/Users/russell/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/russell/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.13.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.13.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/russell/dev/go/go/src/cmd/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 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bk/1vdjn7vd19x41x0ztsbvmw400000gq/T/go-build918707310=/tmp/go-build -gno-record-gcc-switches -fno-common"
```
Repository: godot
Issue: Modifying a bone's transform will freeze the pose
Labels: bug,discussion,topic:animation

**Godot version:**
3.2 Beta 1

**OS/device including version:**
Windows 10

**Issue description:**
Afaik there was a breaking change in `Skeleton` where the function `set_bone_global_pose` has been renamed to `set_bone_global_pose_override `with two additional arguments `(amount, persistent)`

My understanding is, that `get_bone_global_pose` and `set_bone_global_pose` complemented each other. So that you could actually get a bone's transform by using `get_bone_global_pose`, modify for example the rotation and put it back to the skeleton's transforms by using `set_bone_global_pose`, like stated here in thise reddit topic: https://www.reddit.com/r/godot/comments/b1aqdq/how_to_set_global_y_rotation_of_a_3d_bone/

@fire recently pointed out, that for deprecation purposes, the old method will internally call the new `set_bone_global_pose_override` with arguments `amount = 1.0` and `persistent = true`.
https://github.com/godotengine/godot/issues/32637#issuecomment-539591516

**So here starts the problem / bug I'm facing:**
When I'm using the easiest setup, getting a bone's global pose, do no changes on it and then set it  by using the new method, the bone will then stand still. (I'm using AnimationTrees)
If you want to "unfreeze" bones, you explicitly must call `set_bone_global_pose_override` with `persistent = false` then it will start moving again. If that is the purpose of the persistent argument, it kinda makes sense to me, but actually no (when I consider that set_bone_global_override should replace the old function by 1:1.

What I would expect here is, that at least the "normal" animation should be shown. This happens whether running in `_process` or `_physics_process`

**Steps to reproduce:**
Create a simple scene and add an animated character to it. Use one bone for transformation tests.

These lines of code should be enough to show the issue.
```gdscript
var bone_index = 0
var bone_transform:Transform = skeleton.get_bone_global_pose(bone_index)
skeleton.set_bone_global_pose_override(bone_index, bone_transform, 1.0, true)
```

My first guess is, that `get_bone_global_pose` should always get the global pose like it is without the overridden pose.

**Minimal reproduction project:**
[bone_bug.zip](https://github.com/godotengine/godot/files/3833706/bone_bug.zip)
Here a video showing the issue:
https://youtu.be/VfGeCb2KK6g

btw: Is this really a bug, or is the usage of the override different? Maybe I first need to substract any other transforms? But then fire's comment would be falsly? I'm really unsecure about this.
Repository: create-react-app
Issue: Proposal: more advanced Service Worker support
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Currently, the Service Worker support is very limited because the `service-worker.js` is generated by CRA and users can't customize it.

It's bad cause Service Workers can do much more than we currently use today, and by their inherent design, *should* allow app-specific logic.

### Describe the solution you'd like

We're using `workbox-webpack-plugin` go generate service worker via it's `GenerateSW`.

Instead, we could switch to `InjectManifest`, and add a sample service worker file `src/service-worker.js` to all the app templates. Therefore users will be able to customize the behavior of the Service Worker by editing the `src/service-worker.js` file, and we can preserve the existing runtime defaults by putting the same logic at the `src/service-worker.js` template that `GenerateSW` generates by default.

Regarding TypeScript support, we should be able to transpile that service worker file too!

Additionally, we can benefit from this approach by disabling service worker generation logic if the `src/service-worker.js` is removed. This way we can solve long outstanding request to disable service worker generation.

### Describe alternatives you've considered

I've looked into issues #5369 and #5359. They both essentially propose providing more flexibility by allowing webpack config customization. I think that would be a more generic solution, but it has some significant downsides:

1. We'd have to support unbound set of build configurations. My proposal allows flexibility while only having a single configuration. This can be arguably a strong point, and I've seen it a lot in the decision making of this project before. Yet, personally, I don't think it's that problematic.

2. We can provide better support using this proposal than by allowing webpack build configuration. By this, I mean that we can integrate the `InjectManifest` better if we only have that, in contrary to supporting both `InjectManifest` and `GenerateSW`, or even allowing users to provide an arbitrary plugin there. We can add the logic to disable service worker generation naturally, TypeScript support and possibly other built-time service worker injectors if we ever need to.

3. This proposal will also simplify bug fixing cause there will be less possible configuration states that the user can put the build system into. This kind of repeats the first point (1).

The #7866 might provide flexible webpack build process configuration, and relieve the pain points with the current service workers support. However, this proposal is focusing on more advanced support for Service Worker - not just solving the current pain points - and, in my opinion, has value independently of whether #7866 (or similar) is accepted or not.

### Additional context

I'll be able to submit a PR if this proposal is accepted.
Repository: TypeScript
Issue: Expose emitted module specifiers on AMD outfile emit
Labels: Suggestion,In Discussion

## Search Terms

amd outfile module specifier

## Suggestion

Currently when utilising the compiler APIs to emit as AMD to a single outfile, the emitted module specifier in the outfile is not exposed, but does not match the source file `SourceFile.fileName` or any other attribute.

It appears that there are internals of the TypeScript emitter which determine the module specifier that is included output.  For example, if given `/foo/bar/baz.ts` and `/foo/qat/qux.ts` being part of the same program, when emitted as AMD in a single bundle the module specifier, the outfile will `define()` a module named `bar/baz` and `qat/qux`.  It appears that the algorithm used looks for the common root and removes the extension to determine the module specifier.

## Use Cases

When loading the bundle with an AMD loader, knowing what a module specifier is in the outfile is needed to be able to specify a module to load in a `require()` statement.  So if we were automating a custom build, outputting a "bundle" and determining which module to `require()` to bootstrap the application, we have to "guess" and hope that the emitter doesn't change its algorithm of determining the module specifiers.

## Examples

I'm not totally sure, but a public API that would take a `SourceFile[]` and provide back a `string[]` array of module specifiers.  This could be used in `Host.writeFile()` to determine what module specifiers are contained in the written file.

## 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).
Repository: flutter
Issue: Consider implementing support for Android granularity movement API for navigating text in accessibility nodes
Labels: framework,a: accessibility,c: proposal,dependency: android,P3,team-framework,triaged-framework

Currently, Flutter for Android supports granularity movements for edit fields only.
It is important, however, that a screen reader user is able to navigate by characters, words, lines, etc, whenever a node contains text, including content descriptions.

/CC @darrenaustin
Repository: pytorch
Issue: Compiled functions can't take variable number of arguments
Labels: oncall: jit,feature,triaged

```
torch.jit.frontend.NotSupportedError: Compiled functions can't take variable number of arguments or use keyword-only arguments with defaults:
at /usr/local/lib/python3.6/dist-packages/torch/nn/parallel/data_parallel.py:138:32
    def forward(self, *inputs, **kwargs):
                                ~~~~~~~ <--- HERE
        if not self.device_ids:
            return self.module(*inputs, **kwargs)

        for t in chain(self.module.parameters(), self.module.buffers()):
            if t.device != self.src_device_obj:
                raise RuntimeError("module must have its parameters and buffers "
                                   "on device {} (device_ids[0]) but found one of "
                                   "them on device: {}".format(self.src_device_obj, t.device))
```
As you can see,this varargs is in torch lib itself:
`/usr/local/lib/python3.6/dist-packages/torch/nn/parallel/data_parallel.py:138:32`

cc @suo
Repository: flutter
Issue: iOS a11y bridge should respect `hasImplicitScrolling`
Labels: platform-ios,engine,a: accessibility,P3,team-ios,triaged-ios

Android does this - right now, per @goderbauer, iOS exclusively looks at cacheExtent instead of also respecting hasImplicitScrolling.

It should be possible to set a cache extent on something but also set `hasImplicitScrolling` to false and have the iOS bridge respect that.
Repository: go
Issue: cmd/compile: export non-integer constants to debug info
Labels: NeedsInvestigation,Debugging,compiler/runtime

### What version of Go are you using (`go version`)?
go1.13.4

### Does this issue reproduce with the latest release?
I haven't tried with Go 1.14 yet

### What operating system and processor architecture are you using (`go env`)?
windows/amd64

### What did you do?
- use the code at https://github.com/dlsniper/democonstdbg
- use the latest Delve version from master
- place a breakpoint on line 23
- evaluate the following expression:
```
ot == AnotherConst
```

### What did you expect to see?
A boolean result

### What did you see instead?
```
could not find symbol value for AnotherConst
```
Repository: flutter
Issue: Prevent soft keyboard to show when physical keyboard is used
Labels: a: text input,framework,c: proposal,a: desktop,P3,team-text-input,triaged-text-input

Hi,

I have a custom keyboard in my app and I have successfully prevented the default soft input panel (SIP) to show when I focus my text field. This is accomplished using two methods:

1. Using a custom focus node for the text field that has `@override bool consumeKeyboardToken() { return false; }`
2. Overriding the `void requestKeyboard()` in the text field state and hiding the keyboard.
See more here: https://github.com/flutter/flutter/issues/16863

This works as expected but the soft input panel is displayed as soon as I press a key on my physical keyboard (either my PC keyboard in the emulator or a bluetooth connected keyboard to my physical device).

Overriding a RawKeyBoardListener and hiding the keyboard using `SystemChannels.textInput.invokeMethod('TextInput.hide');` makes it popup and then dissapear, causing a very irritating "flicker" and the entire layout of the application shifts around for a split second.

Hiding the keyboard per default when a physical keyboard is connected would be a great feature to add, I guess it's not implemented as it's asked here without response the last 7 months: https://stackoverflow.com/questions/55754646/detect-if-a-physical-keyboard-is-connected-in-flutter
Repository: pytorch
Issue: error: ‘struct torch::jit::RegisterOperators’ has no member named ‘op’
Labels: oncall: jit,triaged

```
static auto registry =
  torch::jit::RegisterOperators()
    .op("maskrcnn_benchmark::nms", &nms)
    .op("maskrcnn_benchmark::roi_align_forward(Tensor input, Tensor rois, float spatial_scale, int pooled_height, int pooled_width, int sampling_ratio) -> Tensor", &ROIAlign_forward)
    // .op("maskrcnn_benchmark::add_annotations", &add_annotations)
    .op("maskrcnn_benchmark::upsample_bilinear", &upsample_bilinear);
```

these code no longer compatible with pytorch 1.4, how to resolve it?

cc @suo
Repository: opencv
Issue: Drawing into a numpy view with a negative step in the channel dimension doesn't work
Labels: feature,category: python bindings



##### System information (version)

- OpenCV => opencv-contrib-python-headless==4.1.1.26
- Operating System / Platform => OS X


##### Detailed description

I create three 3-channel images and draw a circle into them. In the second case I use the step trick `A[:, :, ::-1]` to flip the R and B channels in the image, emulating `cv.cvtColor` with `COLOR_BGR2RGB`. I then try to draw into that array. The result, as seen in the screenshot, is that nothing gets drawn. In the third case I explicitly make a copy of the channel-flipped array (which is actually a view) before drawing, and it works.

![image](https://user-images.githubusercontent.com/730130/68665520-7a88fd80-0542-11ea-8cab-531c56921bc8.png)

Expected is that cv.circle works in all three cases.

##### Steps to reproduce

```python
import cv2 as cv

image1 = np.zeros((100, 100, 3), dtype='uint8')
cv.circle(image1, (50, 50), 10, (255, 255, 255), -1)

image2 = np.zeros((100, 100, 3), dtype='uint8')
image2 = image2[:, :, ::-1]
cv.circle(image2, (50, 50), 10, (255, 255, 255), -1)

image3 = np.zeros((100, 100, 3), dtype='uint8')
image3 = np.array(image3[:, :, ::-1])
cv.circle(image3, (50, 50), 10, (255, 255, 255), -1)

imshow(image1, image2, image3)
```
Repository: flutter
Issue: Video Player Plugin - Change to diffirent Url dynamically
Labels: c: new feature,p: video_player,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

It would be great to be able to change to another Video file or Url without calling a new instance of the video player.
Now, if you call it just feels the memory. You need to call new activity or a hacky way to dispose previous controller.