WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Context

For now I am using the Menu component to render custom context menu on the mouse right click event. And menu should appear relatively to the cursor position. So it would be great to pass some

additional "x, y" props to the Popover that will shift Menu position relatively to the anchorEl. Is that a

good idea? Or maybe there is a better way to perform that functionality? Thanks!

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.17

React
v16.0.0

browser
Google Chrome 61.0.3163.100

etc

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

Expected Behavior

I want to add some custom colors as primary for theme.

Current Behavior

Updating theme with custom color not possible. New object is updated with new color but theme property not get updated.

Steps to Reproduce (for bugs)

I call createMuiTheme method and pass object

const default_theme_obj = {
fontFamily: "Roboto, sans-serif",
palette: {
primary: "#fff"
},
};

but when i pass it as theme={default_theme_obj} to MuiThemeProvider nothing happen, it still have default MUI theme colors. This is exacly how it was worked it v0.19.

Context

I expect that theme is updated with new color set as primary.

My app have several different theme depend on user role. When user is on login page default should be applied with color from DEFAULT_THEME object and when user get access he also get theme from DB which is applied to MUI. It was working really well in v0.19 but when i switch MuiProvider is never updated.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.20

React
16.1.1

browser
all
Issue 1:
Version

2.5.17

Reproduction link

https://codesandbox.io/s/zwm20ozlym

Steps to reproduce

check reproduction url

What is expected?

Duplicate keys detected to be warned

What is actually happening?

Duplicate keys detected not warned

when addVnodes is called, vnodes with same key are not warned

Issue 2:
When a class is set in an dom element which is being initied with Vue and the same class is set in the component root dom element, the final result is a double class. You can see the results here, check with the console the dom and you should see "compClass compClass" instead of just one.

It's not a big deal but doesn't seem the expected behaviour.
Issue 1:
Atom will not responding when viewing a large chunk of minified script, maybe it has to do with the syntax highlighting.

Issue 2:
May be a known issue, but files with large embedded images such as github's public/enterprise/maintenance.html will often cause Atom to freeze (MacVim actually struggles as well).

Seems some of them (github's public/maintenance.html for instance) work fine when in soft wrap mode, or until you move your cursor to the long line when out of soft wrap.
Issue 1:
Problem description

The <Grid container> component receives these props

.MuiGrid-spacing-xs-16-1335 {
width: calc(100% + 16px);
margin: -8px;
}

causing a horizontal scrollbar. See this question for a more accurate example and the (unelegant) fix.

Steps to reproduce

Create an empty project and create one <Grid> with a single item inside. Your page will have a horizontal scroll bar.

Versions

Material-UI: beta 5

React: 15.6.1

Browser: Chrome 60

Proposed solution

Only apply the spacing class and its variants on <Grid> children. I suppose this may be a little inconsistent in the case where you are nesting <Grid> containers, so an alternative could be to just have a prop like applySpacingToContainerOnly={true} (default: false) or something?

Issue 2:
The <Grid container> extends beyond its parent, with half of spacing size.

I have marked the extra width in red, also setting spacing to zero fixes the problem.

Here is a working example: https://codesandbox.io/s/Y8nzGm5W.

Similar code with a zero spacing works as expected: https://codesandbox.io/s/NxvYxvQpL.
Issue 1:
I ran into this when implementing Back button transition in a router. Because the transition is inside a browser popstate event, it gets batched with the low pri update, and the pending state doesn't appear.

I had to do this to work around it but it's unfortunate. We might want to fix this by treating pending state as special. Or maybe a warning — but then we need a first-class official API for opting into user blocking pri.

Issue 2:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

isPending is never set to true when calling startTransition within useEffect, but it does work properly when within a useLayoutEffect.

https://codesandbox.io/s/usetransition-useeffect-issues-p1j9s

Here's the correct behavior (accomplished via useLayoutEffect):

Here's the incorrect behavior (via useEffect):

Note the difference is that the opacity never changes to 0.4 (which is determined based on the isPending state).

What is the expected behavior?

I expect them to both behave the same (at least as far as the user can observe).

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

react@0.0.0-experimental-f6b8d31a7

react-dom@0.0.0-experimental-f6b8d31a7
Issue 1:
Hi,

The new text-left, text-center and text-right classes doesn't work on the table cells. Maybe it would be nice to add an !important hack to force alignment ?

Issue 2:
Bootstrap also defined an extension functions named "tabs" which is same as the one provided by jQuery UI. So referencing to both jQuery UI and bootstrap will cause unexpected behaviors on the tabs. I think this issue is kind of related to issue #171, somehow it's more about styles, but this is about javascript namespace. Maybe limit the scope of bootstrap functions by namespace will be a good idea. Thanks.
Issue 1:
module M1
type T1
y
end
foo(x::Int) = 10
foo(x::T1) = foo(x.y)
end

@show code_typed(M1.foo, (M1.T1,))

gives

code_typed(M1.foo,(M1.T1,)) = Any[:($(Expr(:lambda, Any[:x], Any[Any[],Any[Any[:x,M1.T1,0]],Any[]], :(begin # /home/mlubin/test2.jl, line 8:
return foo((top(getfield))(x::M1.T1,:y))::Int64
end::Int64))))]

on Julia 0.4.

This is incorrect, we can't infer anything about the return type here, since foo could be extended later and x.y doesn't need to be an Int.

Issue 2:
if I define a function d2 before a function d1 which calls d2 then change d2, d1 uses the old definition for d2.

I assume this is because it is all precompiled, but maybe there should be a note warning of this? Or would it be possible to replace the old definition with a longjmp to the new one?

(Mostly important for the REPL, since I don't always do a full load)

julia> function d2()
a
end

julia> function d()
d2()
end

julia> d()
in d: a not defined

julia> function d2()
b=2
end

julia> d()
in d: a not defined

julia> d2
Methods for generic function d2
d2() at prompt:2

julia> function d()
d2()
end

julia> d()
2
Issue 1:
scipy 1.0.1, Anaconda 5, Linux 64 bit

When y is a N-dimensional array, I would expect interp1d to work independently on each series.

When invoked with kind='quadratic' or kind='cubic', however, if any series contains NaNs then the interpolated values of all series will be NaN:

import numpy
from scipy.interpolate import *

x = numpy.arange(0, 8, 1)
y = numpy.stack([numpy.arange(0, 80, 10), numpy.full((8, ), numpy.nan)], axis=1)
print("x =", x)
print("y =", y)

for kind in ('nearest', 'linear', 'zero', 'slinear', 'quadratic', 'cubic'):
print(kind + ' =', interp1d(x, y, axis=0, kind=kind)(4.5))
print("Akima =", Akima1DInterpolator(x, y, axis=0)(4.5))
print("PCHIP =", PchipInterpolator(x, y, axis=0)(4.5))

Output:

x = [0 1 2 3 4 5 6 7]
y = [[ 0. nan]
[10. nan]
[20. nan]
[30. nan]
[40. nan]
[50. nan]
[60. nan]
[70. nan]]
nearest = [40. nan]
linear = [45. nan]
zero = [40. nan]
slinear = [45. nan]
quadratic = [nan nan]
cubic = [nan nan]
Akima = [45. nan]
PCHIP = [45. nan]

Issue 2:
Hi,

I have a request for the following case. Let's say I have a N-Dimensional vector of features for each timestamp in a time-series. So a N+1 dimensional data cube. I want to interpolate each feature, side-by-side in the direction of the time-series (1D interpolation).

Currently the scipy.interpolate.interp1d allows for the side-by-side interpolation of a N-dimensional array in one specific direction, which is great.

However, in case you have missing (NaN) data randomly distributed over the N+1-dimensional time-series, this then doesn't apply anymore but is often the case.

One option is to add the time-series also as a N+1-dimensional array, corresponding to the data values. Currently, this would then be like interpolation with grid data, but that is the multi-dimensional interpolation, It would be good to have this option also for 1D interpolation (single direction)

Another option would be by adding some sort of a mask, or boolean weights to the interp1d function, which would be the same shape as the data array, specifying which data points to actually take into account.

Option number 3 would be to add a value which should be ignored and not taken into account in the interpolation, this seems the easiest.

I would greatly appreciate this, coming as someone in the field of earth-observation, where missing data is very common.

Regards,

Matic
Issue 1:
if you have a parent/child relationship doing a query that contains a has_child will result in error:

curl localhost:9200/_search -d '{
"highlight": {"fields": {"title": {}}},
"query": {
"has_child": {
"query": {"match": {"body": "drip"}},
"type": "answer"
}
}
}'

Error returned:

{
"type":"illegal_state_exception",
"reason":"can't load global ordinals for reader of type: class org.apache.lucene.search.highlight.WeightedSpanTermExtractor$DelegatingLeafReader must be a DirectoryReader"
}

Works fine on 2.0.0, fails on 2.1.0 and later.

Issue 2:
When I was upgraded es from 2.0 to 2.1, highlight feature stop working.

I got this error message:

{
"shard": 0,
"index": "4odevelop_4o",
"node": "XiZaRocLQGuBwZPg58Naqw",
"reason": {
"type": "illegal_state_exception",
"reason": "can't load global ordinals for reader of type: class org.apache.lucene.search.highlight.WeightedSpanTermExtractor$DelegatingLeafReader must be a DirectoryReader"
}
}
Issue 1:
It appears commit 329a5cf has broken _basic_auth_str and it now throws an exception TypeError (see below) when the supplied username and password is None.

Befor this commit, in requests 2.1.1, it was possible to supply None values for username and password when authentication is optional - in this particular case Home Assistant writing to InfluxDB with default configuration.

Exception thrown:

TypeError: sequence item 0: expected a bytes-like object, NoneType found

Issue 2:
Possibly just a previously quirkly behavior that intentionally no longer works.

For requests<2.12.2 having None for username and password still resulted in a BasicAuth authstr being created. Starting in 2.12.2 it will raise an exception.

...
File "/blah/lib/python2.7/site-packages/requests/auth.py", line 38, in _basic_auth_str
b64encode(b':'.join((username, password))).strip()
TypeError: sequence item 0: expected string, NoneType found

here's the change, (which certainly seems desirable), but caused our upstream (python-gitlab) to break.

kennethreitz@329a5cf
Issue 1:
In the autograd tutorial, https://pytorch.org/tutorials/beginner/blitz/autograd_tutorial.html

print(x.grad)

gives output:

tensor([[4.5000, 4.5000],

[4.5000, 4.5000]])

but it hangs afterwards.

pytorch version: 1.5.0

python: 3.7.7

OS: windows 7

cc @ezyang @ssnl @albanD @zou3519 @gqchen @peterjc123 @nbcsm @guyang3532

Issue 2:
Whenever backward() is called to compute gradients the python script never terminates. The backward function is not per se blocking and all lines after it are still executed however the script just does not terminate. This may be related with the operation system which is Windows 7 or with the use of conda. At least there is another (post on Stack Overflow) describing the same problem in the same environment.

To Reproduce

Steps to reproduce the behavior:

install PyTorch on windows 7 via conda (conda create --name grad_test pytorch -c pytorch)

run example code given below taken from the post on Stack Overflow

import torch

x = torch.randn(3, requires_grad=True)
y = x * 2
print(y)

gradients = torch.tensor([0.1, 1.0, 0.0001], dtype=torch.float)
y.backward(gradients)
print(x.grad)

print("all done")

Expected behavior

Script runs and exits after printing "all done".

Environment

PyTorch version: 1.3.0

Is debug build: No

CUDA used to build PyTorch: 10.1

OS: Microsoft Windows 7 Enterprise

CMake version: version 3.9.6

Python version: 3.7

Is CUDA available: Yes

CUDA runtime version: 10.1.243

GPU models and configuration: GPU 0: GeForce GTX 1080

Nvidia driver version: 441.12

cuDNN version: Could not collect

Versions of relevant libraries:

[pip] numpy==1.17.3

[pip] torch==1.3.0

[pip] torchvision==0.4.1

[conda] blas 1.0 mkl anaconda

[conda] libblas 3.8.0 14_mkl conda-forge

[conda] libcblas 3.8.0 14_mkl conda-forge

[conda] liblapack 3.8.0 14_mkl conda-forge

[conda] mkl 2019.4 245

[conda] mkl-service 2.3.0 py37hfa6e2cd_0 conda-forge

[conda] pytorch 1.3.0 py3.7_cuda101_cudnn7_0 pytorch

[conda] torchvision 0.4.1 py37_cu101 pytorch

cc @ezyang @ssnl @albanD @zou3519 @gqchen @peterjc123
Issue 1:
My zookeeper version is 3.5.5，My druid version 0.22.0 ,How can I solve it，thank you .

Issue 2:
Submitting GroupBy queries to the JSON query API returns a 500 when given duplicate output name columns. For example:

{
"context": {"queryId": "010b5fa5-9a45-4614-8c0b-acaa747c2af0"},
"dataSource": "Famous_Duets",
"aggregations": [{
"fieldName": "count",
"name": "count",
"type": "count"
}],
"dataSource": "my_datasource",
"dimensions": [{
"dimension": "Female_Singer",
"outputName": "Singer",
"type": "default"
}, {
"dimension": "Male_Singer",
"outputName": "Singer",
"type": "default"
}],
"granularity": "all",
"intervals": ["2017-06-20T14:51:00Z/2017-06-20T18:27:00Z"],
"queryType": "groupBy"
}

Note that Singer is the outputName for more than one groupBy dimension. The query response is:

{"error":"Unknown exception"}

Obviously, the query is malformed, but returning the error in this response might be helpful. The way I tracked it down was in the logs:

2017-06-20T18:49:09,604 INFO [qtp1665324560-197[groupBy_Famous_Duets_010b5fa5-9a45-4614-8c0b-acaa747c2af0]] io.druid.server.QueryResource - Unknown exception [010b5fa5-9a45-4614-8c0b-acaa747c2af0]

Later in the logs, a log containing:

Dimension[Singer] occurred more than once in InputRow

Tipped me off to what the error was.
Issue 1:
Hello,

While setting up deno in docker I noticed the install.sh script uses unzip and the build will exit with the error unzip is not installed. I believe this is not a default program and tar can be used in place of unzip.

RUN curl -fsSL https://deno.land/x/install/install.sh | sh

https://github.com/denoland/deno_install/blob/master/install.sh#L39

The RUN command that worked for me was

RUN sudo apt-get update && sudo apt-get install unzip -y && \
curl -fsSL https://deno.land/x/install/install.sh | sh && \
sudo mkdir "/usr/local/etc/bash_completion.d" && \
sudo chown "$USER:$USER" "/usr/local/etc/bash_completion.d" && \
sudo "$HOME/.deno/bin/deno" completions bash > "/usr/local/etc/bash_completion.d/deno.bash" && \
sudo apt-get clean && \
sudo rm -rf /var/lib/apt/lists/*

ENV DENO_INSTALL="/$HOME/.deno"
ENV PATH="$DENO_INSTALL/bin:$PATH"

Issue 2:
If unzip is not installed, the install.sh should install it for you
Issue 1:
This is on OSX 10.10.1 with Atom 0.15.0

I had an issue today where I ran out of disk space, and Atom seemed to wipe out a previously saved file.

As in, this file had already been saved, I opened it in Atom, saved, then I quit Atom. Then when I restarted Atom, the file was empty.

I checked with ls, the file was empty and 0 bytes.

I do understand that running out of disk space is certainly not a normal condition, but is there any explanation that would explain how Atom would completely wipe out the contents of the file as a result?

Issue 2:
I have a hard time replicating this issue since it will require me filling up the disk again, but in a nutshell the problem is that when I edit a file in Atom, if the disk space is not enough to save it, I find that the file content is erased.

This happened to me more than once (yeah I need more Gbs of disk space) so I can certify that it is Atom the one causing the issue. The issue appears whenever I edit the file, not when I just open it. The problem is not that Atom is not being able to save the file (that would make sense if there is no disk space available), the problem is that Atom removes all the content, and of course I'm afterwards not able to recover it.

I have no clue of why may this be happening
Issue 1:
Feature request

Is your feature request related to a problem? Please describe.

may be related to #8422.

At the present time , when using next.js with other backend frameworks (isomorphic applications), users have few controls to the logging facility of next.js.

Users can only pass {quiet: true} when instantiate next.js object. But doing these only hide error messages, still can not modify some logging behaviours such as logging level or logging format.

I hope next.js can provide some mechanics for controlling dev logging behaviour.

Describe the solution you'd like

using more advanced logging framework such as winston maybe a good solution.

Describe alternatives you've considered

Additional context

I found next.js do have an abstract layer to handle logging(log.ts), while some code use these abstract APIs to log( such as bundled successfully ), some do not ( such as Compiled successfully )

Maybe with controllable logging is also make next.js avilable to provide more detailed messages for debug using.

Issue 2:
Feature request

Is your feature request related to a problem? Please describe.

Using custom server interferes with other logging in my app.

Describe the solution you'd like

A way to silence next and an interface to tap into ready, recompile, error events.

const app = next({ dev: true, quiet: true })
app.on('ready', myLogger.info);
app.on('recompile', myLogger.trace);
app.on('error', err => myLogger.error('something went wrong', { err }));

const handle = app.getRequestHandler()
// ...
Issue 1:
API Doc update for https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/audio/encode_wav

Correct links? No

Clear Description? No

Usage Example?

Parameters Defined? Yes, not verified against current code

Returns defined? Yes, not verified against current code

Raises listed and defined? No

Visuals, if applicable? No

I will submit a PR, please assign this bug to me.

Part of Issue #28237 & Issue #28236

Issue 2:
API doc update for https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/audio/decode_wav

Correct links? No

Clear Description? No

Usage Example?

Parameters Defined? Yes, not verified against current code

Returns defined? Yes, not verified against current code

Raises listed and defined? No

Visuals, if applicable? No

I will submit a PR, please assign this bug to me.
Issue 1:
react.tsx:

import React from "https://esm.sh/react"

export default function hello(foo: string) {
return <p> Hello {foo}</p>;
}

console.log(hello("world"))

deno run react,tsx:

Check file:///home/luca/testStuff/deno/react.tsx
{
"$$typeof": Symbol(react.element),
type: "p",
key: null,
ref: null,
props: { children: [ " Hello ", "world" ] },
_owner: null
}

deno run - < react.tsx:

deno run - < react.tsx
error: Expected ;, got { at file:///home/luca/testStuff/deno/$deno$stdin.ts:4:21

Issue 2:
I'm trying out deno for scripting (it's been a great experience so far, kudos!).

I'd like to be able to create script files without a .ts extension. If I do this, then the following is interpreted as JS and I get a syntax error on the type annotations:

#!/usr/bin/env -S deno run --allow-run --allow-read --allow-write

// code: language=typescript

function hello(name: string) {
console.log("Hello,", name);
}

hello(Deno.args[0]);

$ ./myscript
error: Uncaught SyntaxError: Unexpected token ':'
function hello(name: string) {
^
at file:///home/joe/tmp/myscript:5:20

I believe the simplest solution would be to add a CLI flag to force script to be interpreted as typescript.

Something like:

--language=[javascript, typescript]

so in the above script the shebang becomes:

#!/usr/bin/env -S deno run --language=typescript --allow-run --allow-read --allow-write
Issue 1:
This is the code that I have put in. When I test the link myself, it does everything the challenge mentions. I am just unable to complete this challenge. Am I missing something?

Challenge adjust-the-hover-state-of-an-anchor-tag has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.

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

<style>
a {
color: #000;
}
a:hover{
color: #00F;
text-decoration: none;
}

</style>
<a href="https://atjonathan.github.io/catphotoapp">CatPhotoApp</a>

Issue 2:
Challenge adjust-the-hover-state-of-an-anchor-tag has an issue.

I think this challenge should be changed, I'll list some reasons:

Right now the challenge shows two new concepts, hover and text-decoration: none, when the overall teaching style is one concept per challenge

Here pseudo-classes are introduced for the first time in the curriculum, I think the description is too concise and could leave a beginner with a lot of doubts.

There is not an example showing how to use :hover with a selector.

My suggestion:

Split the challenge in two, one for hover, one for text-transform: none.

Enhance the description, including a practical example.
Issue 1:
23:07 < balpert> can we add <Namespaced.Things /> to JSX?
23:07 < jwalke> I like that you chose the dot!
23:07 < jwalke> Keep it javascript-first.
23:07 < balpert> yes
23:08 < balpert> translating colon to dot would be absurd
23:08 < balpert> (in my opinion)
23:08 < jwalke> So you could have var MyComponentsPackage = {Typeahead:
R.createClass.. }
23:08 < jwalke> <MyComponentsPackage.Typeahead />
23:08 < jwalke> I like it.
23:08 < jwalke> Make an issue!

Issue 2:
I came up with a rather crude (but I think promising) way to autogen component rendering tests. I'm throwing a big list of values at my components' propTypes validators (kind of like using a fuzzer). I use that to construct a set of supposedly-valid values for each prop, and subsequently combine those into supposedly-valid sets of props.

With direct calling of prop validators being deprecated, is there some other way to accomplish this that I'm missing? I think this test generator would be really useful, but given that I'm dependent on a deprecated feature, I'm not clear if it has a future.

fiddle demo: https://jsfiddle.net/6g3r6amb/1/