WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Perhaps this is a right click option within the console itself, or a setting to save and export on exit/closing tab.

But the option to save/export the console output and input into a txt file

Issue 2:
Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): Version: 0.4.2382.0

Any other software?

Steps to reproduce

Highlight text in Windows PowerShell, in Windows Terminal.

Press CTRL+C and watch as a new line is generated but realize the selected text is both no longer selected and not on the clipboard.

Expected behavior

CTRL+C should continue to work for copying text out of Windows PowerShell.

Actual behavior

CTRL+C is instead just the typical cancel and new line.
Issue 1:
I am still experiencing issue #7318. This is using the latest Firefox, v22. I do not experience the issue with the latest Chrome.

Bootstrap is version 2.3.1.

Issue 2:
I posted this issue earlier, but the example that was posted was not fully representative what I was trying to do and I couldn't recreate the error.

So I created my own JSBin and I have recreated the error where the textarea is not passing via AJAX because there must be some conflict somewhere with vanilla JS, JQUERY or Bootstrap 3.

It will pass data that is hard-coded into the textarea form, but if you type into the form, it will not pass what you type.

To duplicate:

Update: I ran this again and actually saw some of the replies get passed but it is not consistent.

run this JSBin http://jsbin.com/lovahaxu/1/edit?html,js,output (you should see styled output)

Hit reply with one of the responses

You will see some default text, type more text into the form and hit send.

You will receive an alert that displays all the data that is being passed.

Observe the "message=" variable and notice the text you typed is not sent.

Repeat with other replies because I have seen this work a couple of times, but it's not consistent.

I fully admit that my js might be wrong, but I have used this without Bootstrap without problems.
Issue 1:
A number of examples spread across various documentation pages still speak of replication controllers where they should instead say replica sets. Many of these are of an introductory nature and thus tend to confuse Kubernetes newcomers in particular (as determined anecdotally by the number of Slack questions I personally see getting posted in this regard). One particular use case is the application of the kubectl run command which is often accompanied by telling the reader to run kubectl get rc to see the created replication controllers afterwards where instead it should be kubectl get rs these days to list replica sets.

All such occurrences should be updated accordingly. Specifically, I came across

http://kubernetes.io/docs/user-guide/simple-nginx/

http://kubernetes.io/docs/user-guide/pods/multi-container/

http://kubernetes.io/docs/user-guide/walkthrough/k8s201/

There may be additional pages though that I'm not aware of.

I'd be happy to provide a PR to update the pages above and any others people point out.

Thanks.

Issue 2:
After creating a simple pod on an empty cluster I wan't able to delete it.

Way to reproduce:

kubectl run example --image=nginx
kubectl get rc
# empty
kubectl get pods
NAME READY STATUS RESTARTS AGE
example-1934187764-swmqv 1/1 Running 0 38s
kubectl delete pod example-1934187764-swmqv

kubectl get pods
NAME READY STATUS RESTARTS AGE
example-1934187764-l36b7 0/1 ContainerCreating 0 2s
example-1934187764-swmqv 1/1 Terminating 0 57s
kubectl get pods
NAME READY STATUS RESTARTS AGE
example-1934187764-l36b7 1/1 Running 0 6s

Tested with GKE 1.2 and local vagrant (Mac) 1.2.
Issue 1:
Intl.Segmenter is available at runtime, but usage creates a compiler error in Deno v1.20.4:

example.ts:

const segmenter = new Intl.Segmenter("en", { granularity: "grapheme" });

console.log({ denoVersion: Deno.version.deno, segmenter });

$ deno run example.ts
Check file:///Users/deno/example.ts
error: TS2339 [ERROR]: Property 'Segmenter' does not exist on type 'typeof Intl'.
const segmenter = new Intl.Segmenter("en", { granularity: "grapheme" });
~~~~~~~~~
at file:///Users/deno/example.ts:1:28

$ deno run --no-check example.ts
{ denoVersion: "1.20.4", segmenter: Intl.Segmenter {} }

Issue 2:
What are the interactions between these methods:

Process#close()
Process#kill(signal)
Process#status()

The existing docs or a quick read of the source say that:

calling status() after Process#kill(signal) should still be ok (and is).

calling status() after Process#close() will fail with BadResource: bad resource id. So too will calling close() after close().

Because of 1 and 2, presumably Process#kill doesn't (and shouldn't) implicitly invoke Process#close.

What if Process#close is invoked, and the process is still running? Would we expect this to kill the Process, or not? Currently it doesn't seem to do so, and perhaps that's the right design. Just wanted to make the behavior explicit.

Currently nothing stops us from Process#killing a Process that has already exited. If you're lucky, your OS will complain. If you're unlucky, the pid may have been recycled, and you'll be signaling some unknown new process. Wouldn't it be nicer for Deno to verify that if you call Process#kill, the Process hasn't already exited (either naturally, or because you or someone else killed it)?

One way to do that would be to run the sendAsync(dispatch.OP_RUN_STATUS, {rid}) on every Process right after it's started, and have the resulting Promise set a flag, which blocks Process#kill. If that seems too resource-intensive to do across the board, perhaps there's a way to make sure it's at least been done first, in those cases the user requests to kill the Process (or queries its status)?

Next, what are the interactions of the above methods with these:

Process#output()
Process#stderrOutput()
Process#stdin|stdout|stderr.close()

The docs say that calling output() and stderrOutput() schedule a stdout.close() and stderr.close(), respectively, after the pipes have been read.

What if Process#close is invoked, the Process has piped stdio, but output() and stderrOutput() haven't been invoked, and perhaps never will be? Do the stdio pipes get closed? If so, when: only when they're garbage collected?

In general, what is appropriate clean-up for a Process? Should one always explicitly close() it? (I expect it will be closed() automatically when GC'd; though that doesn't mean we shouldn't close it ourselves when we know we're done with it.) If it has open stdio pipes that we haven't read --- perhaps because we killed the Process --- do we need to explicitly close() them before closing the Process?
Issue 1:
see discussion here:

https://groups.google.com/group/symfony-devs/browse_thread/thread/92ae24eafd13e29e?hl=en

Issue 2:
Is there a reason why Request class doesn't have a setUrl method? I really wish to do this:

$request = Request::createFromGlobals();
$request->setUrl("http://www.yahoo.com");

but I can't without creating another instance of Request and copying all of its data minus the URL into the new.
Issue 1:
The drawer doesn't slide back into its original position when closed, it just disappears (unmounts?) instead

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The drawer should slide back into the hidden position

Current Behavior

The slider just unmounts / gets hidden without any animation

Steps to Reproduce (for bugs)

Go to https://material-ui.com/demos/drawers/ click on open left, then click anywhere to dismiss it.

Your Environment

Tech
Version

Material-UI
latest beta

React
16

browser
Chrome 63

etc
TS 2.6.2

Issue 2:
To reproduce:

Open your browser to full width. This is to cause the responsive styling to leave the left nav panel open after clicking on something.

Open https://material-ui.com/.

Click on hamburger at top left.

Click on "Component Demos".

Scroll to bottom.

Click on (Component Demos/) "Tooltips".

Bad behavior: the left nav panel scrolls to top, hiding the currently selected item.

This is particularly annoying in the "Component Demos", since one is likely to try to walk through them sequentially to see what's there.

I have searched the issues of this repository and believe that this is not a duplicate.

I'm on latest Chrome on OSX.
Issue 1:
In type.less, I've found it would be useful for the unstyled and inline to be mixins, rather than developers having to reimplement such things when using LESS.

For example, I'm styling a horizontal navigation bar but I have to reimplement the stylings of ul.inline from type.less into my LESS file, which could easily be replaced with a mixin.

Issue 2:
I originally opened this as a question on SO, but I've since found several other instance in the wild where this happens, so it's not specific to my site. Wondering if it's a bug in Bootstrap, though interestingly I can't replicate this on the carousel example on getbootstrap.com.

From the SO post:

We're doing some final testing on a responsive design and we've discovered an issue on our homepage carousel, but it's only happening on Firefox for Android - not Chrome for Android, not Firefox desktop (not even in responsive design mode), and not on any iOS devices.

Anytime the carousel rotates, either automatically or manually, a black box flashes across the middle after the new slide appears. It is only there for less then a second, then it disappears.

I know it's occurring at some point in the Carousel.prototype.slide function (somewhere between line 144 and line 164 in the source on Github), but I have no idea what element it's occurring on or what specific line is triggering it. I've tried stepping through it in Firefox's remote debugger to no avail.

FWIW, the black box does not occur when viewing the stock Bootstrap carousel demo in Firefox for Android.

We are using the latest version of Bootstrap (3.2.0).

Example 1: https://dl.dropboxusercontent.com/u/9530717/firefox-android-black-box/index.html

Example 2: http://www.tutorialrepublic.com/codelab.php?topic=bootstrap&file=carousel (you can only see it if you click the button that opens the output in a new window)

Example 3: http://www.bootply.com/render/ErniW7HVND

Example 4: http://jsfiddle.net/mattdlockyer/gjPVJ/4/embedded/result/
Issue 1:
Description of the problem

Currently, ObjectLoader doesn't load the specified background texture or environment of a scene's JSON object.

I've outlined a solution below that would import a CubeTexture or Texture for the scene background, and a CubeTexture for environment (since that's the only type of texture environment supports). This involved passing textures into parseObject() and then added them to the scene object.

I could make a PR if looks good, but I'm also not sure if this conflicts with some of the plans outlined in existing issue #17420. Either way this seems like a desirable feature of ObjectLoader.

parseObject: function ( data, geometries, materials, textures ) {

var object;

...

function getTexture( name ) {

if ( textures[ name ] === undefined ) {

console.warn( 'THREE.ObjectLoader: Undefined texture', name );

}

return textures[ name ];

}

switch ( data.type ) {

case 'Scene':

object = new Scene();

if ( data.background !== undefined ) {

if ( Number.isInteger( data.background ) ) {

object.background = new Color( data.background );

} else {

object.background = getTexture( data.background );

}

}

if ( data.environment !== undefined ) {

var texture = getTexture ( data.environment );

if ( texture instanceof CubeTexture ) {

object.environment = texture;

}

}

if ( data.fog !== undefined ) {

if ( data.fog.type === 'Fog' ) {

object.fog = new Fog( data.fog.color, data.fog.near, data.fog.far );

} else if ( data.fog.type === 'FogExp2' ) {

object.fog = new FogExp2( data.fog.color, data.fog.density );

}

}

break;
...

Three.js version

Dev

r113

Browser

All of them

OS

All of them

Issue 2:
Description of the problem

When loading a scene, the background of the editor is not set to the background of the scene. This causes an issue when exporting because the scene's background will be overwritten to the Editor's default gray.

Three.js version

Dev

r103

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS
Issue 1:
📝 Target only a specific keyboard-model with the remappings.

Use case

I have not been able to find a keyboard with a Windows keyboard-layout having the same (or better) mechanical feel as the Apple keyboard (USB with numeric keys) , hence I thought I could "just" remap the keys and re-label the Apple keyboard resulting in (EG ALT->WIN, CMD-> ALT etc).

For my labtop usage I only need the remapping when I am using the PC in my docking station (with the Apple keyboard attached), when I am using the built-in keyboard I need the not-remapped functionality, thus I need a method to differentiate between the different keyboards attached to the PC.

I have read all the current opened issues and am not able to see this request

NB.: Using PT v0.20.1

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Environment

Windows build number: [Version 10.0.18363.778]
PowerToys version: 0.17.0
PowerToy module for which you are reporting the bug (if applicable): Fancy Zones

Steps to reproduce

There's no specific trigger for this issue. Fancy Zones will work as intended and I will randomly move windows around the zones and the zones do not appear.

Expected behavior

I use the shift+mouse to move a window into a zone. I have 3 zones on my monitor that appear as choices

Actual behavior

I hold shift, move the window around and my zone options do not appear. I need to restart PowerToys for the functionality to return. Fancy Zones will stop working again several minutes later.

This started when I upgraded to 0.17.0

Screenshots
Issue 1:
When using tf.identity() it seems like a proper implementation to pass through the input tensor without copying. However, when the input is the value of a variable it might change later, leading to surprising behavior:

var = tf.Variable(1)
old = tf.identity(var.value())
with tf.control_dependencies([old]):
with tf.control_dependencies([var.assign_add(1)]):
new = tf.identity(var.value())

sess = tf.Session()
sess.run(tf.global_variables_initializer())
print(sess.run([old, new])) # Unexpected: [2, 2]

I would think this code should be equivalent to the following workaround that uses a second variable to remember the previous value:

var = tf.Variable(1)
old = tf.Variable(var.initialized_value())
with tf.control_dependencies([old.assign(var.value())]):
with tf.control_dependencies([var.assign_add(1)]):
new = tf.identity(var.value())

sess = tf.Session()
sess.run(tf.global_variables_initializer())
print(sess.run([old, new])) # Expected: [1, 2]

Can we make tf.identity() aware of whether its input is static or varying, to always return the value from the time it's executed?

Issue 2:
I'm running Tensorflow 0.10.

The following code

import tensorflow as tf

x = tf.Variable(0, dtype=tf.int32)

old_val = tf.identity(x)
with tf.control_dependencies([old_val]):
new_val = tf.assign(x, x + 1)

with tf.Session() as sess:
sess.run(tf.initialize_all_variables())

for i in xrange(3):
print sess.run([old_val, new_val, x])

outputs

[1, 1, 1]
[2, 2, 2]
[3, 3, 3]

From reading the docs on control_dependencies and identity as well as StackOverflow, I expected output

[0, 1, ?]
[1, 2, ?]
[2, 3, ?]

where ? indicates that the variable value is unspecified.

Is this a bug? If this is not a bug, what is the correct way to refer to the value of variable before and after assignment in a single graph?
Issue 1:
Vue.js version

2.1.6

Reproduction Link

https://jsfiddle.net/xzhwbb1o/2/

What is Expected?

I want to get the component item up component choice, but when functional , the parent is the #app, remove the functional is choice, is the default of this? I have read the document render, but did not find the relevant tips.

Issue 2:
Let's say I have the following template:

<div id="app">
<parent-component>
<functional-child-component />
<normal-child-component />
</ parent-component>
</div>

If I use this.$parent inside the normal-child-component I get access to the parent-component, as expected.

If I use the same logic inside a functional child component, however, the behavior is different. context.parent gives me access to the root instance, similar to if I was using this.$root in a normal component. Is this the intended behavior? If it is, how can I get access to actual $parent instance inside a functional child component?
Issue 1:
Ok, this is a new one as not sure I've seen it in another product but it is a good alternative to just pure scoring and pushing docs to the top.

When searching, I should be able to ask that I get back a "variety" of results by type, or a field value and a min/max count of each. So for example, I get the best ranked results but I want 5 books, 5 pictures, 5 songs, and 5 movies total rather than 15 books, 5 songs eating up my first page. NOTE: I am not asking that they be grouped together, but that there is a limit to how many of each can make that response to avoiding flooding out the other docs of various types (this is a perfect job for a VarietyConstrainedHitCollector which I'm sure doesn't exist).

Basically a variety constraint on what is returned.

You can implement this client-side but it would be more efficient down in the server. And doing multiple queries by types is wasteful as well and doesn't allow them to be scored together by relevancy.

I'm not sure yet what to do about paging or scrolling or even if those would be supported. This is more of a first-page type of feature, but if you CAN solve paging and scrolling it would be interesting. I'm thinking on those more now but recording this before I forget.

It's also similar to some searches we built in the past that show a summary page of the first 10 and last 10 of the sort order (show me the least and most expensive of matching items) which is a similar variety constraint and more efficiently done in the engine while it has things in memory; rather than doing follow-on queries.

Issue 2:
Ability to collapse on a field. For example, I want the most relevant result from all different report types. Or similarly, the most recent result of each report type. Or maybe, I want to de-dup on headline.

So, the sort order would dictate which one from the group is returned. Similar to what is discussed here:

http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/

From my understanding, it seems that in order for field collapsing to be efficient, the result set must be relatively small.

This is also referred to as "Combine" on some other search products.
Issue 1:
🐛 Bug

Our autodiff infrastructure have bugs on double backward for early expiration of grad_accumulator for some formulas (i.e. layer_norm, linear).

It gives error like below

File "test/test_jit.py", line 659, in checkTrace
grads2_ge = torch.autograd.grad(l2_ge, flattened_recording_inputs, allow_unused=allow_unused)
File "/scratch/wanchaol/local/pytorch/torch/autograd/__init__.py", line 149, in grad
inputs, allow_unused)
RuntimeError: No grad accumulator for a saved leaf!

This is happening on master now, the bug is kinda complicated to trigger: when we add an non-trivial AD formula, sometimes non-trivial models will throw the above error, while in pure Autograd mode it runs fine.

To Reproduce

I noticed this problem appears in #20284 , after I added an AD formula for linear in #20039.

git fetch origin; git checkout gh/wanchaol/5/origin

python setup.py develop

python test/test_jit.py TestEndToEndHybridFrontendModels.test_vae

Expected behavior

The test will test in autograd mode and in JIT Autodiff mode, the autograd mode works fine, but the JIT autodiff second derivative gives the above error, which I think it related to our autodiff infrastructure early release one of the leaf Variable

Issue 2:
🚀 Feature

Hello,

This feature is related to a thread from discuss forum

I would like to propose mechanism of saving _forward_pre_hooks and _forward_hooks while model is preparing for quantization.

Motivation

There are cases that depend on such functionality. Here I duplicate what I said about it in the forum

Have a look at this example of pre forward hook run. Here’s EfficientNet implementation that assumes it can be integrated as backbone to FPN (https://github.com/rwightman/pytorch-image-models/blob/master/timm/models/efficientnet.py#L471)

So here we can see that during forward blocks are called sequentially than we collect input features from specific layers.

Pitch

We can add several lines here https://github.com/pytorch/pytorch/blob/master/torch/quantization/quantize.py#L337

to preserve mod's hooks in new_mod

Additional context

Additionally it is needed to discuss the possibilities of preserving hooks while fusing modules

cc @jerryzh168 @jianyuh @dzhulgakov @raghuramank100 @jamesr66a
Issue 1:
Environment

Windows Version: Windows 10 Education 1903
OS Build: 18362.10005
Windows Terminal version: 0.3.2142.0

Any other software?

Steps to reproduce

Opening more than certain tabs breaks the tab management. There are several issues faced:

Multiple tabs become hidden and there is no way to know how many tabs are open and way to access them.

Tab text/label is partially hidden along with the close button for each tab after the first tab.

Unless the window is maximized, there is no way to even find the new tabs opened. The configuration used is default.

To reproduce:

Open Windows Terminal

Open many tabs

The following GIF demonstrates the issue:

Expected behavior

Tab text/label and close button is not hidden

There is a way to know the number of tabs open and a way to access each one

Actual behavior

Multiple tabs become hidden and there is no way to know how many tabs are open and way to access them.

Tab text/label is partially hidden along with the close button for each tab after the first tab.

GIF image above showcases the bug.

Issue 2:
Description of the new feature/enhancement

When watching logs, or build processes, similar lines being shown repeatedly can often make it hard to determine if anythings happening (as each new page of data looks the same as the previous one)

Smooth scrolling would help this.