WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
The typescript typings support a property "openImmediately" in SelectField which is supposed to be passed to the DropDownMenu child. But the actual SelectField implementation doesn't support it, it's not passed down to DropDownMenu, there's a console error instead:

warning.js:33 Warning: React does not recognize the openImmediately prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase openimmediately instead. If you accidentally passed it from a parent component, remove it from the DOM element.

in div (created by TextField)

in TextField (created by SelectField)

in SelectField (created by LoginScreen)

in div (created by LoginScreen)

in LoginScreen (created by Connect(LoginScreen))

in Connect(LoginScreen) (created by Main)

in div (created by Main)

in Main (created by Connect(Main))

in Connect(Main) (created by MainSelector)

in div (created by MainSelector)

in MainSelector (created by Connect(MainSelector))

in Connect(MainSelector)

in Router (created by ConnectedRouter)

in ConnectedRouter

in div (created by StyleRoot)

in StyleRoot

in Provider

in AppContainer

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

Expected Behavior

A SelectField with openImmediately=true should be displayed open without click. There should be no error on the console if the property openImmediately is used on a SelectField.

Current Behavior

A SelectField with openImmediately=true is not opened automatically. There is and error on the console if this prop is set.

Steps to Reproduce (for bugs)

Use this in your react app to reproduce:

<SelectField openImmediately={true}/>

Your Environment

Tech
Version

Material-UI
0.20.0

React
16.2.0

browser
Chrome 63

Issue 2:
Problem description

Safari has issues with rendering the CircularProgress component. The CPU load rises rapidly and the page freezes. Moreover, the circle looks odd since it is shown in a fully closed fashion.

Link to minimal working code that reproduces the issue

<CircularProgress size={80}/>

Versions

Material-UI: v1.0.0-alpha.21

React: 15.6.1

Browser: Safari (tested on macOS 10.12.6 and iOS 10.3.3)
Issue 1:
This not happens outside terminal = using powershell directly.

Steps to reproduce

start type anything

press space

Expected behavior

the left space or character on the left of command do not delete

Actual behavior

any character on left was deleted and the command characters go to left

Issue 2:
Environment

Windows build number: 0.3.2171.0
Windows Terminal version (if applicable): 0.3.2171.0

Any other software?

Steps to reproduce

Open Windows Terminal

Change to any of the Vietnamese input methods and type

Expected behavior

Vietnamese texts being entered

Actual behavior

For the Vietnamese keyboard layout, only the keys 2, 3, 4 work and produce âêô. A few diacritic keys work but produce the separate diacritics instead of combining them into the base letter. The remaining keys failed to work and produce ? or the letters with diacritics removed

For the Vietnamese number based and Telex input methods, nothing works

I've already search several times and the only related issue is #2213 but I don't think it's a duplicate, as Vietnamese uses Latin characters and no pre-edit textboxes are used like CJK languages
Issue 1:
Hello, I think standard for url array params is ?arr1[]=1&arr2[]=2, am I missing something? Router parses the object into: ?delivery=1&delivery=24

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

Expected Behavior

Expected at least nested objects be supported and parsed correctly from query

Current Behavior

It takes the whole thing as a key, instead of creating an nested object

Doesn't matter the format, none of them works

/?nested[key]=value

or

/?nested.key=value

Steps to Reproduce (for bugs)

Open the page with the pattern above

Print the this.props.url.query in top level page component

Does not work

Context

I can't pass nested object over arbitrarily if I am not using <Link /> component, actually I'm not sure if <Link /> would work with nested object since it is using npm 'url' which does not supported nested object parsing...

Btw, I'm currently using https://github.com/ljharb/qs for parsing atm, I hope this saves you all time if you are looking for alternatives.

Your Environment

Tech
Version

next
2.4.6

node
8.1.3

OS
macOS Sierra

browser
chrome

etc
Issue 1:
Heya,

Currently, @types/angular has a dependency on an earlier version of itself as can be seen in https://npmcdn.com/@types/angular@1.5.5-alpha/package.json.

This cause a duplicate definition error when compiling a project that uses it:

kamik@T460p MINGW64 /D/sandbox/typescript-types-bug (master)
$ npm run tsc

> typescript-types-bug@1.0.0 tsc D:\sandbox\typescript-types-bug
> tsc

node_modules/@types/angular/index.d.ts(17,21): error TS2300: Duplicate identifier 'angular'.
node_modules/@types/angular/index.d.ts(18,21): error TS2300: Duplicate identifier 'ng'.
node_modules/@types/angular/node_modules/@types/angular/index.d.ts(17,21): error TS2300: Duplicate identifier 'angular'.
node_modules/@types/angular/node_modules/@types/angular/index.d.ts(18,21): error TS2300: Duplicate identifier 'ng'.

(...)
kamik@T460p MINGW64 /D/sandbox/typescript-types-bug (master)
$ npm ls
typescript-types-bug@1.0.0 D:\sandbox\typescript-types-bug
+-- @types/angular@1.5.5-alpha
| +-- UNMET DEPENDENCY @types/angular@1.5.4-alpha
| `-- @types/jquery@1.10.26-alpha
`-- typescript@2.0.0

npm ERR! missing: @types/angular@1.5.4-alpha, required by @types/angular@1.5.5-alpha

I've tried looking at https://github.com/DefinitelyTyped/DefinitelyTyped/tree/types-2.0/angular but there is no package.json there. Any way I can contribute a fix?

Issue 2:
I tried using the @types/xxxx package and had problems.

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

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

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

Hi @tkrotoff

Problem:

After React 16 update many related typings just stopped working for anyone still on react 15. A similar error was reported before in #18708 but never resolved and later closed because the person creating the issue updated to react 16 and stopped having the issue.

This are the typings affected that I'm aware of:

@types/react-dom

@types/rc-slider

@types/react-addons-update

@types/react-addons-shallow-compare

@types/react-router

My investigation showed that types for @types/react-select and @types/react-boostrap work fine because although they also reference @types/react to the latest version they pick up the version installed in the project and don't come with their own node_modules folder that will try to use the latest version for react.

Is there anything I can do in a PR to make these libraries work as react-select and react-bootstrap? I digging out the type definitions in here I can't figure out the difference, when do the type modules come with node_modules and when do they not? Can someone assist me in creating a PR to fix this ASAP?

This is a total blocker for anyone still on React 15
Issue 1:
After I upgraded the React version of the project from 16.14.0 to 18.2.0, the console reported the following warning after the project started

Warning: Internal React error: Expected static flag was missing. Please notify the React team.

I don't know the specific cause of the bug

Issue 2:
Describe what you were doing when the bug occurred:

Record a profile

Click on one of the stack frames

The error came up

I'll struggle to reproduce as the first time I did a profile against the same site this didn't happen and the code is not publishable

Please do not remove the text below this line

DevTools version: 4.10.1-f160547f47

Call stack: at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19605:9)

at ProfilingCache_ProfilingCache.getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:20115:11)

at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:34161:33)

at Hh (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:12807:7)

at qi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:13457:7)

at mk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16074:86)

at lk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15459:11)

at kk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15451:23)

at ck (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15435:5)

at Uj (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15142:118)

Component stack: at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:34144:50)

at div

at div

at div

at SettingsModalContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28206:3)

at Profiler_Profiler (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:35772:50)

at ErrorBoundary_ErrorBoundary (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29219:5)

at PortaledContent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29336:32)

at div

at div

at ProfilerContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32934:3)

at TreeContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24322:3)

at SettingsContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24811:3)

at ModalDialogContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29404:3)

at DevTools_DevTools (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:36207:3)
Issue 1:
I find that I'm often having a hard time tracking the source of various React warnings. Would it be an idea to have a setting to throw the warnings so we can at least have a stack trace?

Issue 2:
Seeing something like:

Warning: Any use of a keyed object should be wrapped in React.addons.createFragment(object) before being passed as a child.

Is really useful but... not so much if you don't know where the offending code is. A trace call would really help narrow down where in an application the problematic code is.

This would also obliviate the need for the (pointless) try/catch below that needs to be edited to even work (it catches the error it throws).
Issue 1:
I am trying to define optional externals in an es6 project.

The feature exists - #339 , but there is no flag that I can set in the (externals) configuration to make a dependency optional. Digging into the code I found that optional is a flag checking for reasons, and if every reason's dependency is marked as optional. But I can't seem to find where it is defined.

What would be the best way to define an external dependency optional? Have I missed something and it is possible doing it using configuration?

Issue 2:
I npm installed bootstrap version 3.3.6 and imported it into vendor.ts. Everything seems to be working except the glyphicons, specifically .glyphicon-search is only working in safari, but not showing up in Chrome and Firefox. In Chrome in dev tools, I can see it finds the source.

I have these errors in my console:

Failed to decode downloaded font: http://localhost:8080/

OTS parsing error: invalid version tag

Also trying to import font-awesome 4.5.0. Getting:

Uncaught Error: Cannot find module "../fonts/fontawesome-webfont.eot?v=4.5.0"

and

.//font-awesome/fonts/fontawesome-webfont.eot?v=4.5.0

Module parse failed: /Users/bryantluu/Projects/Work/fe-client/node_modules/font-awesome/fonts/fontawesome-webfont.eot?v=4.5.0 Line 1: Unexpected token ILLEGAL

You may need an appropriate loader to handle this file type.

(Source code omitted for this binary file)

@ .//css-loader?sourceMap!.//postcss-loader!.//font-awesome/css/font-awesome.css 6:304-355

for all font types. Maybe something wrong with the font loaders?
Issue 1:
What / Why

For switching different Node.js version, we use symlink for global node_modules.

$ ls -ld /usr/local/lib/node_modules
/usr/local/lib/node_modules -> /var/packages/Node.js_v16/var/node_modules

The global module directory and npm itself is removed after installing global module.

$ npm install -g pino-pretty
npm WARN reify Removing non-directory /usr/local/lib/node_modules

The behavior have been changed from npm/arborist@f2b0cee.

How

Current Behavior

$ npm install -g pino-pretty
npm WARN reify Removing non-directory /usr/local/lib/node_modules

Steps to Reproduce

Make global node_modules be symlink.

Run npm install -g <any module>

The global node_modules is removed.

Expected Behavior

Allow global node_modules be symlink.

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

If I have a symlink called node_modules to a different directory, then npm will remove this symlink and create a real folder. This has been introduced in npm/arborist@f2b0cee as a safety feature, but as it doesn't disable it as specified when using --force option.

Other people have similar problems too:

#3669

#4274

Expected Behavior

It should work as intended in npm/arborist@f2b0cee (don't remove symlink if --force).

I really needed this thing to work, so I had to downgrade npm to an older version.

Steps To Reproduce

Create an empty folder

Create a second folder inside the first one

Run npm init -y

Run ln -s your_folder_name node_modules

Run npm install --force <any package name>

node_modules no longer points to your_folder_name

Environment

npm: v8.3.1

Node.js: v17.4.0

OS Name: MacOS Catalina

System Model Name: iMac

npm config:

; this only showed comments and registry auth token "(protected)"
Issue 1:
It'd be nice if there was an upgrade function for the plugin binary to save having to uninstall and then install when a new version of a plugin is released.

Even if it was just a download and overwrite to begin with, it could be expanded from there.

Issue 2:
To update a plugin, we need to remove it first otherwise, elasticsearch will complain that it's already installed:

sudo bin/plugin -install mobz/elasticsearch-head

-> Installing mobz/elasticsearch-head...
Failed to install mobz/elasticsearch-head, reason: plugin directory /usr/share/elasticsearch/plugins/head already exists. To update the plugin, uninstall it first using -remove mobz/elasticsearch-head command

I propose that we provide an update switch:

sudo bin/plugin -update mobz/elasticsearch-head

This should be some sugar that runs the following:

sudo bin/plugin -remove mobz/elasticsearch-head
sudo bin/plugin -install mobz/elasticsearch-head
Issue 1:
gotype $GOROOT/src/pkg/net

leads to several error messages due to unresolvable 'import "C"'.

go/types could be more tolerant with invalid operands and types to avoid follow-up
errors.

(For instance, conversions of the form T(x) could always succeed even if x is invalid.
Other operations should not report an error if an operand is already invalid.)

Issue 2:
by skinner.david:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What does 'go version' print? go version go1.2 linux/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1. http://play.golang.org/p/ylDzrxpUTC

What happened?
signal: segmentation fault before 'main.main'

What should have happened instead?
no errors.

Please provide any additional information below.
requires you to
go get azul3d.org/v0
play is not duplicating the error.
Issue 1:
System information (version)

OpenCV => 3.4.3

Detailed description

the bindings generator seems not to respect the HAVE_OPENCV_* defines.

Steps to reproduce

in cmake set:

BUILD_LIST=features2d,python3

you will get a compile error like

opencv/build/modules/python_bindings_generator/pyopencv_generated_types.h:710:46: error: ‘FlannBasedMatcher’ is not a member of ‘cv’
template<> PyObject* pyopencv_from(const Ptr<cv::FlannBasedMatcher>& r)

as the generator still picks up code guarded by

#if defined(HAVE_OPENCV_FLANN)

Issue 2:
System information (version)

OpenCV => 3.3.1

Operating System / Platform => Ubuntu 16.04

Compiler => /usr/bin/c++ (ver 5.4.0)

Detailed description

FlannBasedMatcher has two methods, constructor FlannBasedMatcher and create() that can't be wrapped without optional flann module but CV_WRAP ignores #ifdef HAVE_OPENCV_FLANN.

Steps to reproduce

cmake -DBUILD_LIST=features2d,python2 .. && make -j8
Issue 1:
The compiler should allow shebangs to pass through.

http://stackoverflow.com/questions/23298295/how-to-make-a-shell-executable-node-file-using-typescript

Issue 2:
TypeScript Version:

1.7.5 / 1.8.0-beta / nightly (1.9.0-dev.20160217)

Code

// A self-contained demonstration of the problem follows...

Expected behavior:

Actual behavior:
Issue 1:
Challenge http://freecodecamp.com/challenges/waypoint-use-responsive-design-with-bootstrap-fluid-containers has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When instructed to wrap all html elements in div this Waypoint gives you credit prematurely (by simply creating a div) not necessarily wrapping all the elements.

It logical for me since I am very familiar with HTML but maybe for new html user it would not be obvious that you have to move closing tag to below all other tags since exercise validates without that action...

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-use-responsive-design-with-bootstrap-fluid-containers has an issue.

We need to put all of our html codes in a div with a class container-fluid, but it doesn't matter where you put your code ...div class="container-fluid"></div... challange accept it everytime.

For example :
Issue 1:
Lately I have been playing with fonts with ligatures like PragmataPro, Fira Code, Hasklig, etc...

The only way I have found to make Atom to actually render any ligature is by adding text-rendering: optimizeLegibility to my style config. Anyways, this completely breaks pretty much the entire editor. Cursor position stops working correctly (a single ligature requires 2 or 3 left/right arrow clicks for the cursor to move back/forwards), the delete key acts really funny, etc...

Even more, after commenting text-rendering: optimizeLegibility, Atom keeps doing funny stuff until I restart it.

Those type of fonts are getting more and more common; it would be really nice if Atom could handle them correctly.

Btw, PragmataPro works just fine in Chrome, test it here: http://typecast.com/preview/myfonts/113975 (be sure to add text-rendering: optimizeLegibility to the textbox you'll be testing.

Issue 2:
I'm using the Atom for Windows Alpha from the Atom website (not Chocolatey), version 0.136.0 (as viewed in the Help menu and with --version in the command line, the version file in the Atom folder says v0.17.1; it was downloaded around 12:30AM US Eastern on October 14, 2014 if that helps) on Windows 8.1. I set text-rendering: optimizeLegibility; for .editor in styles.less (because otherwise the ligatures aren't in effect and I get each individual character). This happens regardless of whether hardware acceleration is enabled. It also happens in --safe mode, and the developer tools console shows no errors.

(<*>)::Functor f=>(a->b)->(f a->f b)
fmap::Functor f=>(a->b)->(f a->f b)

in Hasklig, which has ligatures for <*>, ::, =>, and ->.

fifififififififififi

in Calibri, using the ligature for fi. The cursor is at the end of the line, and the misspell underline only leads up to that point as well. The ligature for ff in Calibri has the opposite effect; the cursor and underline extend farther than text on the screen if you put enough f's on a line.

I can provide more details if you need them.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/bonfire-return-largest-numbers-in-arrays has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

It doesn't matter what code you write, your get the same error:

Cannot read property 'eql' of undefined

Even chopping the function call to a straight text string gives the same error.

Issue 2:
Challenge Build a Tic Tac Toe Game has an issue.

User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36.

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

If you select 'x', let the game place an 'o' in spot [2,2]. Then place an 'x' in [2,1]. The game then places an 'o' in [2,0]. If you place an 'x' in [1,0], the game will freeze. I did this several times.
Issue 1:
I just stumbled across this in the minified version of Bootstrap 1.3.0. On line 4 we have:

ol,ul{list-style:none;}

and on line 88 we have:

ul,ol{margin:0 0 18px 25px;}

. Obviously they could be written as one rule:

ul,ol{margin:0 0 18px 25px;list-style:none;}

I'm not sure this is bug in less or wherever, but I guess you could save some bandwidth fixing this minor bug!

Issue 2:
I've noticed that Bootstrap doesn't change it font sizes between layouts. Why is that? For example, the H1 font size is 36px. This seems fine on a desktop but is WAY too big on a mobile layout. What was the reasoning behind not making the font sizes responsive?

And if I wanted to make them responsive, is that easy to do without modifying the Bootstrap source? It seems like I would have to rewrite a lot of code in my main.scss in my own media queries in order to do this. A related part of the problem is that, for example, the H1, H2, H3, etc font sizes are defined as calculated pixels:

$font-size-h1: floor(($font-size-base * 2.6)) !default; // ~36px
$font-size-h2: floor(($font-size-base * 2.15)) !default; // ~30px
$font-size-h3: ceil(($font-size-base * 1.7)) !default; // ~24px
$font-size-h4: ceil(($font-size-base * 1.25)) !default; // ~18px
$font-size-h5: $font-size-base !default;
$font-size-h6: ceil(($font-size-base * 0.85)) !default; // ~12px

If Bootstrap was using rems then you could simply change the base font size in each media query and all headers (in this example) would automatically change size accordingly.

Anyways, just trying to figure out the best approach here and also am wondering why in the world font sizes would not be setup to be responsive...
Issue 1:
pull request for the code - #16589 (review)

Issue 2:
This is the same problem as described in #14440 but with Timestamp, and the fix should be similar.

Probable source of error:

pandas/pandas/tslib.pyx

Line 438
in
093aa82

result = Timestamp(unit * rounder(value / float(unit)), unit='ns')

A small, complete example of the issue

In [1] import pandas as pd
In [2]: ts=pd.Timestamp('2016-03-06 18:43:45.950000')
In [3]: ts.floor('10L')
Out [3]: Timestamp('2016-03-06 18:43:45.950000128')

Expected Output

Timestamp('2016-03-06 18:43:45.950000')

Output of pd.show_versions()

INSTALLED VERSIONS

commit: 093aa82

python: 2.7.6.final.0

python-bits: 64

OS: Linux

OS-release: 3.16.0-46-generic

machine: x86_64

processor: x86_64

byteorder: little

LC_ALL: None

LANG: en_US.UTF-8

LOCALE: None.None

pandas: 0.19.0+63.g093aa82

nose: 1.3.7

pip: 9.0.0

setuptools: 28.7.1

Cython: 0.25.1

numpy: 1.11.2

scipy: None

statsmodels: None

xarray: None

IPython: 5.1.0

sphinx: None

patsy: None

dateutil: 2.5.3

pytz: 2016.7

blosc: None

bottleneck: None

tables: None

numexpr: None

matplotlib: None

openpyxl: None

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: None

httplib2: None

apiclient: None

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: None

boto: None

pandas_datareader: None