WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Since Lucene 4.4 release enable_position_increment settings on token filters cannot be set to false which results in underscores appearing for filtered tokens in shingle filters.

Issue 2:
In very rare cases, it is possible to have two snapshots of the same name exist in a repository, one found in the cluster state as a snapshot in progress, and the other found in the repository. This can happen when a snapshot (lets call it snap) exists in the repository, and we try to create another snapshot with the same name snap. When trying to create the second snap, SnapshotsService#createSnapshot first updates the cluster state to include the second 'snap' snapshot as a snapshot in progress, and then calls SnapshotsService#beginSnapshot, which checks if a snapshot by the same name already exists. If a snapshot by the same name does exist, an exception is thrown, which results in calling SnapshotsService#removeSnapshotFromClusterState. However, this call to remove the snapshot from the cluster state simply submits a cluster state update task for the cluster service to execute in its own update thread, and so there is a tiny window when the cluster state could have a snapshot in progress with the name snap and the repository could have the original snapshot named 'snap' in its storage.

This affects the SnapshotsService#deleteSnapshot call, which looks through both the current snapshots and the snapshots in the repository storage, and it also affects TransportGetSnapshotsAction and TransportSnapshotsStatusAction, which have a very tiny window of time in which its possible to return two snapshots of the same name, or to return the current (soon-to-be-removed from the cluster state) snapshot when the snapshot in the repository storage is what was meant.

For those wondering why we don't check if the snapshot name already exists before adding the new snapshot to the cluster state's snapshots in progress, the reason is because it can present race conditions of its own. If two requests arrive to create a snapshot of the same name at the same time, because neither has yet to be added to the cluster state, it is possible that both pass the check and subsequently both eventually get created by the snapshots service.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

All rows should have the same border color

Current Behavior

When I use colSpan for combine many columns borders have different colors

Steps to Reproduce (for bugs)

You may see this on example

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.1.1

browser
Chrome 62.0.3202.94

os
Windows 10

Issue 2:
Hello, after commints on Feb 4 2018 all multiline inputs stopped to resize properly.

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

Expected Behavior

When user adds a new row to multiline field it resizes it's height to fit the text and cursor moves to the new row.

Current Behavior

When user adds a new row the text field resizes it's height as needed, but the cursor still remains on the first line and text goes outside the upper bounds of the textfield.

Steps to Reproduce (for bugs)

Create simple multiline text field

Enter multiline text

Your Environment

Tech
Version

Material-UI
1.0.0-beta.32

React
16.2.0

browser
firefox
Issue 1:
If the minifier doesn't eliminate constant expressions (like Uglify does), with the way our flat bundles currently work you would ship two bundles.

We should warn prominently in this case, as you would effectively ship a double bundle to production.

Issue 2:
This is task list issue.

"Blocks" fixture app which made by built-in API, 'react-fetch', Server Component combination that useful to play new features v18 later.

But current one is broken because importing removed older Cache API module.

And difficult to notice that regression because there are no tests.

So I planning these task for Blocks working fine again and write regression tests.

[Blocks Fixture] fix broken fixture ServerComponent app #22151

Write regression tests with Cypress

Consider better implementation at some @todo comments, where should we invoke cache refresh() function etc...
Issue 1:
I've had the zones reset to their default almost every time I upgrade the application to a new version.

More annoyingly, on the latest version (v0.23.0) they also get reset every reboot.

Please make sure these settings survive a reboot as well as an application upgrade.

Even better, store them per monitor (some unique ID) so that the settings are remembered for different monitors. For instance when using a laptop which is sometimes connected to monitor A (at home) and sometimes to monitor B (at work). So you can set the zones up differently for each monitor.

Please let me know if there is any additional information needed to troubleshoot this issue.

P.S. I'm running Win10 (v2004, build 19041.508) on a desktop with 2 monitors permanently connected.

Issue 2:
ℹ Computer information

PowerToys version: 0..23.0

PowerToy Utility: FanzyZones

Running PowerToys as Admin: Yes

Windows build number: 2004 (19041.508)

📝 Provide detailed reproduction steps (if any)

Apply custom layout

Reboot computer (I think, it's only happened after turning in on for the day...)

✔️ Expected result

My custom layout will remain unchanged between restarts

❌ Actual result

Custom layout is reset to the default 3 Priority Grid each restart

📷 Screenshots

This is the default it returns to:

This is the custom I expect it to return to (note the layout and the Show space around zones both return to default)
Issue 1:
The code blow returns NotImplementedError: sparse rule for xor.

import jax.numpy as jnp
from jax.experimental import sparse
indices = [[0, 1], [1, 2]]
X = sparse.BCOO(([1 for _ in range(len(indices))], indices), shape=(3, 4))
y = jnp.ones(3, dtype=bool)

@sparse.sparsify
def xor(X, y):
return y[:, None] ^ X

xor(X, y)

Please: add support for XOR operation over sparse matrices.

Check for duplicate requests.

Describe your goal, and if possible provide a code snippet with a motivating example.

Issue 2:
tl;dr: Please implement np.eig in JAX, in particular its forward-mode differentiation

I am working on a quantum project that is currently written in TensorFlow but would greatly benefit from JAX. The main roadblock is that the np.eig function does not have its forward-mode differentiation rule implemented in JAX.

Thanks a lot!
Issue 1:
Describe the workflow you want to enable

SimpleImputer.strategy = 'random' will randomly choose a non-NaN value.

Describe your proposed solution

Find a list of non-NaN indices. Randomly pick one index for each NaN.

Describe alternatives you've considered, if relevant

Pandas:

# Impute missing NaN values by randomly selecting a non-NaN value
for column in df.columns:
nan_indexes = df[df[column].isna()].index
non_nan_values = df[column].dropna().tolist()
imputed_values = [random.choice(non_nan_values) for _ in range(len(nan_indexes))]
df.loc[nan_indexes, column] = imputed_values

Additional context

Let's say you're in the following setting:

GOAL: Iteratively tighten a hyperparameter grid.

You have a broad hyperparameter grid

Some hyperparameter choices disable (i.e. make NaN) other hyperparameter choices.

You do random selection of grid points and get the loss.

You make _isnan a value, true or false, for params that can be NaN.

You impute the missing values for NaNs.

You use decision tree regression to figure out what hyperparameter choices are best.

You tighten your grid iteratively using the above.

However, one downside is that some of the splits will be misleading, if they involved imputed NaNs. (The split on this hyperparameter value could suggest a particular threshold OR that the governing hyperparameter that created this NaN is important.) A way to reduce this confusion is using random choice when imputing.

Issue 2:
The purpose would be to provide an unbiased, stochastic, univariate imputer. The imputer would replace missing values by values sampled uniformly at random from the non-missing values of the sample column.

This would require to add additional random_state constructor parameter to the class.

As for #11208 this strategy should work both on numerical and non-numerical dtypes.
Issue 1:
From @wangjild on 2016-10-18T08:58:54Z

ISSUE TYPE

Bug Report

COMPONENT NAME

git

ANSIBLE VERSION

2.2.0

CONFIGURATION

OS / ENVIRONMENT

debian:8.0 jessie

SUMMARY

If local git repository has modification, an update attempt of always fails with Local modifications exist, even if force=yes was given.

STEPS TO REPRODUCE

tasks:
- name: update project dependency
git: dest={{item.location|quote}} repo={{item.scm_url|quote}} version={{item.scm_revision|quote}} force=yes refspec={{item.scm_refspec}} accept_hostkey=yes
with_items: "{{ deps }}"

EXPECTED RESULTS

ACTUAL RESULTS

failed: [127.0.0.1] => {
"failed": true,
"invocation": {
"module_name": "git"
},
"item": {
"location": "/opt/tiger/neihan/conf",
"name": "neihan/conf",
"scm_refspec": "refs/heads/master",
"scm_revision": "master",
"scm_url": "ssh://*********/neihan/conf"
},
"module_stderr": "Shared connection to 127.0.0.1 closed.\r\n",
"module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_U00Fwd/ansible_module_git.py\", line 1023, in <module>\r\n main()\r\n File \"/tmp/ansible_U00Fwd/ansible_module_git.py\", line 974, in main\r\n result.update(changed=True, after=remote_head, msg='Local modifications exist')\r\nUnboundLocalError: local variable 'remote_head' referenced before assignment\r\n",
"msg": "MODULE FAILURE"
}

Copied from original issue: ansible/ansible-modules-core#5292

Issue 2:
ISSUE TYPE

Documentation Report

SUMMARY

The 1.6.7 release mentions CVE-2014-4967 and CVE-2014-4966.

Both of them are still in the **RESERVED** state:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4966

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4967

Any reason for not setting them free after all these years? :)
Issue 1:
I tried using the @types/xxxx package and had problems.

@types/whatwg-fetch 0.0.33 version has failed with error " node_modules/@types/whatwg-fetch/index.d.ts(32,44): error TS2304: Cannot find name 'ReadableStream'."

I added @types/whatwg-streams to the package.json dev dependencies, but still the failure exists.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I am on version 2.1.6. Trying now with 2.5.2 which is the latest stable version of tsc. Will update the issue once installation and verification is done.

Got new set of errors on tsc 2.5.2

node_modules/@types/react/index.d.ts(165,11): error TS2559: Type 'Component<P, S>' has no properties in common with type 'ComponentLifecycle<P, S>'.

node_modules/@types/whatwg-fetch/index.d.ts(11,13): error TS2451: Cannot redeclare block-scoped variable 'fetch'.

node_modules/@types/whatwg-fetch/index.d.ts(13,14): error TS2300: Duplicate identifier 'HeadersInit'.

FYI, a lot of my react-native project also errored out with tsc 2.5.2. It would be great if you could resolve the the issue for tsc 2.1.6

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Yes

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @ryan-codingintrigue

Issue 2:
Hi everybody,

Iam new in using Typescript and angular. First of all i want to use moment.js and jquery i made a reference path in my bootstrap.v3.datetimepicker.d.ts and in my personal ts file. Linked to jquery and moment, and included the node_module scripts in the index.html. But it keeps giving me the error in my terminal that 'moment' namespace cannot be found. I think i am missing something but i do not know what...

Thanks in advance everybody
Issue 1:
🐛 Bug

Description

Image Type:

I use the torch.utils.data.Dataloader to wrap my dataset class , but the Error message shows that the image tensor was Torch.HalfTensor, but it was float64, Wha should I do to fix it?

(0, (3, 1280, 704), (1280, 704, 3), <class 'torch.Tensor'>, tensor(-0.4490, dtype=torch.float64))

(1, (3, 1280, 704), (1280, 704, 3), <class 'torch.Tensor'>, tensor(-0.4490, dtype=torch.float64))

dataloader_train = DataLoader(train_dataset, batch_size=1,

shuffle=True, pin_memory=True, num_workers=4)

dataloader_valid = DataLoader(test_dataset, batch_size=1,

shuffle=True, pin_memory=True, num_workers=4)

PyTorch Version (0.4.0):

OS (Linux):

How you installed PyTorch (conda):

Additional context

Issue 2:
Issue Description

It seems that stacking is currently (PyTorch 0.4) is not supported for tensors of type HalfTensor; see code example.

I don't know if this is intentional for some reason (hence I didn't label this issue as a bug), but I couldn't find any issue or documentation pointing to that. Since some methods, like torch.utils.data.DataLoader, depend on torch.stack() (in this case implicitly through the default_collate() method), it would be great if either stacking for HalfTensors could get implemented, or the documentation could be updated to contain some kind of hint.

Code Example

Python 3.6.5 (default, Mar 30 2018, 06:41:49)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.3.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import torch

In [2]: torch.__version__
Out[2]: '0.4.0'

In [3]: tensor_1_float = torch.tensor([1, 2, 3], dtype=torch.float)

In [4]: tensor_2_float = torch.tensor([4, 5, 6], dtype=torch.float)

In [5]: torch.stack([tensor_1_float, tensor_2_float])
Out[5]:
tensor([[ 1., 2., 3.],
[ 4., 5., 6.]])

In [6]: tensor_1_half = torch.tensor([1, 2, 3], dtype=torch.half)

In [7]: tensor_2_half = torch.tensor([4, 5, 6], dtype=torch.half)

In [8]: torch.stack([tensor_1_half, tensor_2_half])
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call last)
<ipython-input-8-10f49aa85ea5> in <module>()
----> 1 torch.stack([tensor_1_half, tensor_2_half])

RuntimeError: _cat is not implemented for type torch.HalfTensor

On PyTorch 0.3.1, one gets basically the same error when one tries to do the same thing:

TypeError: Type torch.HalfTensor doesn't implement stateless method cat
Issue 1:
Do you want to request a feature or report a bug?

I think it bug

What is the current behavior?

webpack uglify already minified file (.min.js)

If the current behavior is a bug, please provide the steps to reproduce.

install some dependency with minified build

npm i -s three

write alias to minidied file in config

extensions: [ '.ts' ],
alias: {
three: 'three/build/three.min.js', // <-----------------------
}
},

run webpack in production mode

part in three.min.js

THREE.PointsMaterial.");return new Ha(a)};l.ParticleBasicMaterial=function(a){console.warn("THREE.ParticleBasicMaterial has

after uglify two time:

same part in vendor.min.js

THREE.PointsMaterial."),new ue(t)},t.ParticleBasicMaterial=function(t){return console.warn("THREE.ParticleBasicMaterial has

What is the expected behavior?

no auto minify already minidied files, parse alias from config and add entries with (min.js) extension to black list before run uglify, when run uglife check this black list.

Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.

package.json

"@types/three": "0.89.11",
"clean-webpack-plugin": "0.1.18",
"copy-webpack-plugin": "4.4.2",
"html-loader": "0.5.5",
"html-webpack-plugin": "webpack-contrib/html-webpack-plugin",
"three": "0.90.0",
"ts-keycode-enum": "1.0.4",
"ts-loader": "4.0.0",
"typescript": "2.7.2",
"webpack": "4.0.1",
"webpack-cli": "2.0.9",
"webpack-dev-server": "3.1.0",
"webpack-split-chunks": "^0.2.1"

Issue 2:
When using the UglifyJsPlugin within my webpack build I get a large list of errors from my bower_components dependencies. It looks to me (from here: https://github.com/webpack/webpack/blob/master/lib/optimize/UglifyJsPlugin.js#L43) that I should be able to use something like this

new webpack.optimize.UglifyJsPlugin({
exclude: [
/bower_components\//
]
})

which continues to throw out a massive list of errors, leading me to believe they are still being parsed.
Issue 1:
Challenge add-rounded-corners-with-a-border-radius has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; rv:47.0) Gecko/20100101 Firefox/47.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}

.thick-green-border {
border-color: green;
border-width: 10px;
border-style: solid;
}

.smaller-image {
width: 100px;
border-radius: 10px;
}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<img class="smaller-image thick-green-border" src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back. ">

<p class="red-text">Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>
<p class="red-text">Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>

```

Issue 2:
:lang is code of language i.e: es, fr, ru

:chid is name of challenge as it works currently

/:lang/map should render the map with the names of challenges translated as currently they are in the corresponding file of seeds/challenges (nameLang if it exists or name otherwise to present in english when there is no translation)

/:lang/:chid should render the identified challenge but using the name and description in the target language (as long as it is available as nameLang and descriptionLang in the corresponding seeds/challenges, if it doesnt exist present name and description to present in english challenges that are not translated).

Bonus point: use the library i18next for routes as stated.
Issue 1:
As part of onboarding, if we have helper stuff, that helper stuff needs to be near the feature, not at the bottom.

Issue 2:
The current General settings page could use some improved structure for the various settings as discussed in #2676.

Here's a proposal:

Running as .. (Title)

Always run as administrator..... (Checkbox)

Run at startup (Checkbox)

Restart as admin (Button)

Appearance (Title)

Choose settings color (Radiobutton group)

About PowerToys (Title) (In the side panel)

Version x.xx.x (clickable link to release notes)

Download updates automatically (Checkbox)

Check for updates (Button)

Various links

@htcfreek Please add your proposal of splitting the update section. I like that idea.
Issue 1:
VSCode Version:0.10.11

OS Version:OS X 10.10.5

When I edit a html file with some javascript code, there is no intellisense. But the previous version does have the intellisense. For instance, I typed 'aler', vscode would popup a list to choose. In the latest version html file only intellisense html tags

Issue 2:
I build vscode from the master branch.(0.10.10)

Found that intellisense doesn't work,no auto completion with inline js code in the .html file.

The previous version(0.10.8) support
Issue 1:
React version: 17.0.2

Steps To Reproduce

Use NVDA in Firefox to Navigate through the first code example provided below. (use down arrow keystrokes to navigate the page)

Notice how the graphic elements get announced as clickable.

Link to code example:

<!DOCTYPE html>
<html lang='en'>

<head>
<title>Basic HTML5 document</title>
<meta charset='utf-8'>
</head>

<body>
<div id="root">
<img src="https://picsum.photos/200/300" alt="test text"/>
</div>

<script>
// event delegation
document.querySelector('#root').addEventListener('click', () => { console.log('click') })
</script>
</body>

</html>

From the above minimal example, you can see how events delegated to the root cause NVDA to announce the element as clickable.

If we take this other example:

<!DOCTYPE html>
<html lang='en'>

<head>
<title>Basic HTML5 document</title>
<meta charset='utf-8'>
</head>

<body>
<div id="root">
<img src="https://picsum.photos/200/300" alt="test text"/>
</div>

<script>
// event delegation
document.addEventListener('click', () => { console.log('click') })
</script>
</body>

</html>

The element will not be read as clickable.

Putting handlers on the root is a loss of semantics, and causes the intention of handlers to be no longer communicated well to the assistive technology.

The current behaviour

NVDA reads clickable due to event delegation performed at the root level.

The expected behaviour

NVDA should not read clickable.

Could react provide a way for authors to arbitrarily delegate events to the document node?

Issue 2:
Consider the following:

var MixinNameHere = {

componentDidMount: function() {
// Do some stuff yo!
}
}

var ComponentNameHere = React.createClass({

mixins: [MixinNameHere],

componentDidMount: function() {
// So some stuff here, then (or before) the parent should be called.
}
});

The above will not work because as you can see I have declared the existence of componentDidMount() twice. This would be fair if we didn't have libraries such as underscore or similar libraries that make the use of _.extend which then lets us do:

ClassName.__super__.method.apply(this, arguments);

So my question is, as some one who likes to abstract common logic out and use inheritance (I mix backbone with react) - Why can I not use inheritance to say "did my component mount, yes do this - oh and call the parent
Issue 1:
In React, there is a very common issue of needing the most up-to-date version of state from inside a useEffect, timeout, callback, asynchronous function, etc. It seems the easiest solution is to use a ref, as encouraged by React's own documentation here:

If you intentionally want to read the latest state from some asynchronous callback, you could keep it in a ref, mutate it, and read from it.

Typically, the pattern I use for this is as follows:

const [value, setValue] = useState('some-initial-value');
const valueRef = useRef(value);
valueRef.current = value;

This ensure that on every render we update the ref to contain the latest version of the value state. This works fine, but it's messy - 3 lines of code instead of 1 for every state we need the latest version of. For components with a lot of useState calls this gets really ugly really fast for something that's remarkably simple and doesn't affect performance.

My feature request is this: can we just get a ref that points back to the most recent value of state as part of the useState call? I'd love to be able to do this:

const [value, setValue, valueRef] = useState('some-initial-value');

And then just reference valueRef.current from within effects, timeouts, intervals, event listener functions, etc. The amount of times I have to use the messy ref workaround is frustrating, and this looks like something React would be able to do so easily just by sticking the latest value in the ref on every render. People could then use it if they want it or continue to call useState() as normal otherwise.

Would certainly clean up my company's codebase markedly. Are there any potential downsides to providing this optional ref that I am missing?

Issue 2:
I am using react0.14.7 and webpack for my project. It works perfectly fine.

However, when I try to upgrade to react15, I pops up such an error:

addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component\'s render method, or you have multiple copies of React loaded.

This is a very classic issue (https://gist.github.com/jimfb/4faa6cbfb1ef476bd105).

Why it works in react0.14.7 but fails for react15?

Could any one answer?