WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
% babel --optional es7.asyncFunctions example.js !10039

/usr/local/lib/node_modules/babel/node_modules/babel-core/lib/babel/helpers/parse.js:70
throw err;
^
AssertionError: foo.js: undefined does not match type Pattern
at Type.Tp.assert (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/types.js:53:16)
at addPattern (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:220:24)
at recursiveScanScope (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:167:9)
at recursiveScanChild (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:214:9)
at NodePath.<anonymous> (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:150:13)
at NodePath.each (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/path.js:96:22)
at recursiveScanScope (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:149:14)
at recursiveScanChild (/usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:214:9)
at /usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/scope.js:176:13
at /usr/local/lib/node_modules/babel/node_modules/babel-core/node_modules/ast-types/lib/types.js:627:18

where:

// example.js
import f from 'f';

f(async function(assert) { });
// ^ this function is imported

± % babel --v
5.0.9

± % npm version
{ 'ember-jobs': '0.0.0',
npm: '2.7.4',
http_parser: '2.3',
modules: '14',
node: '0.12.2',
openssl: '1.0.1m',
uv: '1.4.2-node1',
v8: '3.28.73',
zlib: '1.2.8' }

Issue 2:
import foo from 'bar';
(function* () {});

Compiling this raises AssertionError: test.js: undefined does not match type Pattern
Issue 1:
The following code on the current nightly produces an ICE:

#![feature(associated_consts)]

struct Test {
_x: [u32; Test::ARRAY_SIZE]
}

impl Test {
const ARRAY_SIZE: usize = 4;
}

fn main() {}

The compiler outputs the following:

error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'path not fully resolved: PathResolution { base_def: DefTy(DefId { krate: 0, node: 4 }, false), last_private: LastMod(AllPublic), depth: 1 }', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/librustc/middle/def.rs:81

Issue 2:
I tried this code:

#![feature(associated_consts)]

struct S;

impl S {
const N: usize = 3;
}

static STUFF: [u8; S::N] = [0; S::N];

// NOTE: This works OK:
// static STUFF: [u8; 3] = [0; S::N];

fn main() {
// NOTE: This works OK:
// let stuff: [u8; S::N] = [0; S::N];
}

I get the error:

thread 'rustc' panicked at 'path not fully resolved: PathResolution { base_def: DefTy(DefId { krate: 0, node: 4 }, false), last_private: LastMod(AllPublic), depth: 1 }', /Users/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-mac/build/src/librustc/middle/def.rs:81

Meta

rustc --version --verbose:

rustc 1.1.0-nightly (7bd7163 2015-05-06) (built 2015-05-05)

binary: rustc

commit-hash: 7bd7163

commit-date: 2015-05-06

build-date: 2015-05-05

host: x86_64-apple-darwin

release: 1.1.0-nightly

Stack backtrace:

1: 0x10eb86f5f - sys::backtrace::write::hc8a4ac867687625dies
2: 0x10eb8fa50 - panicking::on_panic::h8a20ee230368976dxuw
3: 0x10eb49b45 - rt::unwind::begin_unwind_inner::hdec022e876757f01gcw
4: 0x10eb4a96c - rt::unwind::begin_unwind_fmt::h6ffe61c334a81630mbw
5: 0x10bd00e38 - middle::const_eval::eval_const_expr_partial::h814207524cef7390Tii
6: 0x10b9c0aed - astconv::ast_ty_to_ty::h9119a591013371dfrSv
7: 0x10ba41933 - collect::type_scheme_of_item::h3901b884cf3c707cdny
8: 0x10ba39a2c - collect::convert_typed_item::h12a84069945ba57eQry
9: 0x10ba211ad - collect::convert_item::hcb1eaa0733f02657eBx
10: 0x10ba67b56 - check_crate::closure.38613
11: 0x10ba65ada - check_crate::h71ec2befa9b49c1f5CC
12: 0x10b2cff27 - driver::phase_3_run_analysis_passes::hcfdd4de2213fe030tGa
13: 0x10b2b1c2c - driver::compile_input::h93cb3a50ed1b3f97Qba
14: 0x10b370c93 - run_compiler::h7ca7d41460963b3165b
15: 0x10b36e3fa - boxed::F.FnBox<A>::call_box::h5883147459539851824
16: 0x10b36d957 - rt::unwind::try::try_fn::h498179752253104642
17: 0x10ec12028 - rust_try_inner
18: 0x10ec12015 - rust_try
19: 0x10b36dc2d - boxed::F.FnBox<A>::call_box::h5554344682679983399
20: 0x10eb8e44d - sys::thread::Thread::new::thread_start::h71342e3350e45779fxv
21: 0x7fff921d0267 - _pthread_body
22: 0x7fff921d01e4 - _pthread_start
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): gobindata

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version):

1.4.0

Environment:

Cloud provider or hardware configuration: N/A

OS (e.g. from /etc/os-release): OSX / Linux

Kernel (e.g. uname -a): N/A

Install tools: N/A

Others:

What happened:

Run make all WHAT=cmd/kubectl GOFLAGS=-v

and get:

+++ [1004 17:24:34] Generating bindata:
/Users/andy/Downloads/kubernetes-1.4.0/test/e2e/framework/gobindata_util.go
Cannot find go-bindata. Install with
go get -u github.com/jteeuwen/go-bindata/go-bindata
../../../../../../test/e2e/framework/gobindata_util.go:19: running "../../../hack/update-bindata.sh": exit status 5
make[1]: *** [_output/bin/deepcopy-gen] Error 1
make: *** [generated_files] Error 2

What you expected to happen:

It should build without asking for an external dependency.

How to reproduce it (as minimally and precisely as possible):

Execute make all WHAT=cmd/kubectl GOFLAGS=-v from the root dir of the untar of kubernetes-1.4.0.tar.gz.

Anything else do we need to know:

This is causing an issue with homebrew that was addressed with a hack:

Homebrew/homebrew-core#5558

If you run rm "./test/e2e/framework/gobindata_util.go" first, you're able to build (see the code in the PR).
Issue 1:
Context:

Playwright Version: 1.1.1

Operating System: N/A

Node version: N/A

Browser: N/A

Extra: N/A

Describe the bug

Looking at playwright's dependency graph I noticed that it's relying on an outdated https-proxy-agent version. Because of this, there are two versions of debug installed per every install of playwright. Luckily, it's your only duplicate.

While seemingly minor, you're still relying on outdated deps.

https-proxy-agent@5.x exists – it still supports Node >= 10 and shares your debug link

Issue 2:
Only one of the "stdout" file is shown. I can not see the other stdout/stderr. They are only links like http://localhost:9323/data/xxxxxx.bin.

System info

Playwright Version: [v1.35.1]

Operating System: [All, Ubuntu 20]

Browser: [All, Chromium]

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

Link to the GitHub repository with the repro

My playwright config:

https://github.com/vitejs/vite-plugin-react-pages/blob/fix/md-hmr/test-setup/playwright.config.ts

Steps

Download the test report chromium-ubuntu-20.04-playwright-report in https://github.com/vitejs/vite-plugin-react-pages/actions/runs/5435572598

Open the report locally

Go to the first error test. Checkout its Attachments tab. You can't see stdout/stderr.

Expected

I want to view all stdout/stderr in the report's Attachments tab.

Actual

stdout/stderr is not shown in the report's Attachments tab.
Issue 1:
This isn't always reproducible, but for the last couple of weeks (on fedora 14) I've sometimes gotten messages like:

assemble [llvm]: test/run-pass/arith-0-boot.s
test/run-pass/arith-0-boot.s: Assembler messages:
test/run-pass/arith-0-boot.s:672: Fatal error: duplicate .debug_line sections
test/run-pass/native-mod-boot.s: Assembler messages:
test/run-pass/native-mod-boot.s:1244: Fatal error: duplicate .debug_line sections
test/run-pass/native-boot.s: Assembler messages:
test/run-pass/native-boot.s:938: Fatal error: duplicate .debug_line sections

Sadly, there really are duplicate .debug_info sections:

$ make <...> test/run-pass/arith-0-boot.s
[...]
$ fgrep -n .debug_info test/run-pass/arith-0-boot.s
241: .section .debug_info,"",@progbits
508: .section .debug_info,"",@progbits

Issue 2:
The following code doesn't work (even though I suspect it's correct):

trait Foo {
fn foo(@self) { bar(self); }
}

fn bar(_b: @Foo) { }

The following error is returned:

<anon>:2:24: 2:29 error: mismatched types: expected `@Foo` but found `@Self` (expected trait Foo but found @-ptr)
<anon>:2 fn foo(@self) { bar(self); }
^~~~~
error: aborting due to previous error
Issue 1:
Summary of the new feature/enhancement

Currently it is only possible to drag the terminal window by clicking on the (small) empty space between the + sign and the minimize/maximize buttons.

This is a bit confusing and I find myself trying to drag the window by clicking on the huge white space between the last tab and the + button:

Proposed technical implementation details

It would be nice if the Terminal window would behave like Edge or Chrome where the + button is right near the last tab and you can drag the window by clicking on the empty space between the + symbol and the minimize button:

Edge:

Chrome:

Issue 2:
Default Profile for Common Profile Settings

Allow settings which the user would like applied to all profiles to be specified in a profile with a well-known name, such as "name" : "_default". All settings in this profile will be applied before they are overridden from individual profiles. This would be helpful to allow all profiles to have acrylic applied with a certain opacity where those settings are not specified.

[snip]
{
"name" : "_default",
"useAcrylic" : true,
"acrylicOpacity" : 0.5,
"closeOnExit" : true,
"colorScheme" : "Campbell",
"cursorColor" : "#FFFFFF",
"cursorShape" : "bar",
"fontFace" : "Consolas",
"fontSize" : 10,
"historySize" : 9001,
"padding" : "0, 0, 0, 0",
"snapOnInput" : true,
"startingDirectory" : "%USERPROFILE%"
},
{
"name" : "PowerShell Core",
"commandline" : "C:\\Program Files\\PowerShell\\6\\pwsh.exe",
"guid" : "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
"icon" : "ms-appx:///ProfileIcons/{574e775e-4f2a-5b96-ac1e-a2962a402336}.png",
},
{
"name" : "cmd",
"commandline" : "cmd.exe",
"guid" : "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
"icon" : "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.png",
"useAcrylic" : false
},
[snip]
Issue 1:
Some package still needs an older version of gulp-sourcemaps

npm --prefix superset/assets install
npm WARN deprecated feature-filter@2.2.0: This package has been merged into the 'mapbox-gl-style-spec' package
npm WARN deprecated point-geometry@0.0.0: This module has moved: please install @mapbox/point-geometry instead
npm WARN deprecated shelf-pack@1.1.0: This module is now under the @mapbox namespace: install @mapbox/shelf-pack instead
npm WARN deprecated unitbezier@0.0.0: This module has moved: switch to @mapbox/unitbezier
npm WARN deprecated vector-tile@1.3.0: This module has moved: please install @mapbox/vector-tile instead
npm WARN deprecated whoots-js@2.1.0: This module is now under the @mapbox namespace: install @mapbox/whoots-js instead
npm WARN deprecated geojson-area@0.1.0: This module is now under the @mapbox namespace: install @mapbox/geojson-area inste
ad
npm WARN deprecated object-keys@0.2.0: Please update to the latest object-keys
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm ERR! code E404
npm ERR! 404 Not Found: gulp-sourcemaps@https://registry.npmjs.org/gulp-sourcemaps/-/gulp-sourcemaps-1.7.0.tgz

npm ERR! A complete log of this run can be found in:
npm ERR! /home/maxiq/.npm/_logs/2017-08-03T13_15_30_539Z-debug.log

Unfortunately this is not available in the npm registry (reference: https://registry.npmjs.org/gulp-sourcemaps/). I am unable to build the npm components. Please help.

Issue 2:
When user is only granted schema access, preview query is generated in from of SCHEMA_NAME.TABLE_NAME which failed the query.

Expected results

Preview query success when user only have schema access.

Actual results

Preview query failed

Screenshots

How to reproduce the bug

Grant only schema access to user

Go to SQLLab

Choose the DB and the granted schema

Choose any table.

See the error.

Environment

(please complete the following information):

superset version: > 1.1 (current master) (<1.1 should also have this problem)

python version: 3.7

Checklist

Make sure to follow these steps before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are any.

I have reproduced the issue with at least the latest released version of superset.

I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.
Issue 1:
Expected Behavior

I don't have a concrete example yet, but Werkzeug today released a v1.0.0, and flask only specifies Werkzeug>=0.15 as the dependency, that means any backware incompatible changes made to v1.0.0 of werkzeug could potentially break things here.

Actual Behavior

Things could be breaking

Environment

Python version: 3.6.9

Flask version: 1.1.1

Werkzeug version: 1.0.0

If this is alright, then feel free to close this issue

Issue 2:
Any fresh installs/updates to flask as of the last few hours crash with an import error

ImportError: cannot import name 'url_encode' from 'werkzeug' (/Users/me/env/lib/python3.7/site-packages/werkzeug/init.py)

due to a major version change in werkzeug (from 0.16.1 to 1.0.0), as per pallets/werkzeug#1714
Issue 1:
I chatted about this with @bebraw on gitter, and he said to bring it here as a feature request.

The problem is that async chunks are given non-descriptive names by default, with no way to override, except by using the old CJS-based require.ensure code splitting api.

What would be ideal would be a way to let the developer come up with his or her own unique names for each async chunk. Something like

output: {
createAsyncChunkName: modulesContained => name
}

Where webpack would pass all the modules in an async chunk to the provided function, which would be responsible for generating a unique name. I assume if the generated names are ever duplicated, webpack would just error out.

The use case boils down to being able to analyze build results. My plan is to eventually get webpack in use at work, where we literally have hundreds of async split points. I imagine there'd be value in having a feasible way to quickly identify which split point is in which chunk.

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

bug

What is the current behavior?

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

What is the expected behavior?

I am using an ui-lib which uses react, in the app that has the business logic I have react as well. I am using CommonsChunkPlugin but I see the react 2 times in the vendors bundle.

entry: {
app: ['babel-polyfill', path.join(__dirname, './../src/App.js')],
vendor: ['react', 'react-dom', 'd3'],
},

new webpack.optimize.CommonsChunkPlugin({
name: 'vendor',
filename: 'vendorbundle.js',
chunks: ['vendor', 'app'],
minChunks: 2,
}),

What is the best way to exclude it? Is that a normal behavior?

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

Webpack version 3
Issue 1:
I encounter a problem using the nct.cdf function in scipy.stats!

nct.cdf is the t-Student cumulative distribution function, with shape parameters df (degrees of freedom), nc (non central parameter).

Curiously enough, this function works well for nc<= 65535

YET FOR nc>=65536

You will notice that for any x, and for any nc>=65536:

nct.cdf(x,df,nc)=1.0 which is completely absurd!

For instance:

from scipy.stats import nct

nct.cdf(45,9,65536) gives 1.0 ????? (It should normally be close to 0)

Would any one have a solution to this problem?

Is it a limitation of the algorithm or a fortran type overflow?

Thank you by advance.

Issue 2:
From stackoverflow:

"""

I encounter a problem using the nct.cdf function in scipy.stats!

nct.cdf is the t-Student cumulative distribution function, with shape parameters df (degrees of freedom), nc (non central parameter).

Curiously enough, this function works well for nc<= 65535

YET FOR nc>=65536

You will notice that for any x, and for any nc>=65536:

nct.cdf(x,df,nc)=1.0 which is completely absurd!

For instance:

from scipy.stats import nct
nct.cdf(45,9,65536) # gives 1.0 ????? (It should normally be close to 0)

"""
Issue 1:
Original ticket http://projects.scipy.org/scipy/ticket/647 on 2008-04-20 by trac user bow_der_kleine, assigned to unknown.

Now I use scipy.signal intensively for my research. And I miss some functions, which are necessary for my research. Hence I coded it myself. I use these functions to observe attributes of digital filters, which I designed. Therefore I saved them in a file and called it designtools.py. I tried to code it in scipy-style and tested it for many types of filter. Following is the list of functions

find, rem (I copied from matplotlib), phase, phasejumb, firtype, zerophase, groupdelay, smithdelay, sphakdelay, cplxpair, cplxreal, zpk2sos, tf2sos, sos2zpk, sos2tf

For more information see also documentation in the code.

Issue 2:
Original ticket http://projects.scipy.org/scipy/ticket/648 on 2008-04-20 by trac user bow_der_kleine, assigned to @cournape.

Now I use scipy.signal intensively for my research. And I miss some functions, which are necessary for my research. Hence I coded it myself. I use these functions to observe attributes of digital filters, which I designed. Therefore I saved them in a file and called it designtools.py. I tried to code it in scipy-style and tested it for many types of filter. Following is the list of functions

find, rem (I copied from matplotlib), phase, phasejumb, firtype, zerophase, groupdelay, smithdelay, sphakdelay, cplxpair, cplxreal, zpk2sos, tf2sos, sos2zpk, sos2tf

For more information see also documentation in the code. Because I can't attach a file here, you can find my code under

[http://www.biolawcom.de/files/member/1/designtools.py]
Issue 1:
Environment

Windows build number: Version 10.0.18362.356
Windows Terminal version (if applicable): dev build on 0691c21876229dc573a18473ca04bfc78c0d6803

Any other software?

Steps to reproduce

Open several cmatrix tabs and see what it looks like. Some color attribute are displayed as 32m. Now open a new tab and quickly type things, the buffer are likely to be messed up.

Expected behavior

Rendering is correct.

Actual behavior

Not really.

Analysis

As a follow-up of #1311, in which other people also noticed this problem. It seems like one tab is affecting another when under heavy load. I've explored the code a little bit and found that it was not the case.

When under heavy load, contty is lagged and compressed several sequential key event as one. For example, if I quickly typed aaaaaaslkd, the received buffer in StateMachine::ProcessString (link) looks like this:

"\x1b[93m\x1b[15;22Haaaaaa\x1b[?25h\x1b[m\x1b[?25l\x1b[93m\x1b[15;22Haaaaaas\x1b[?25h\x1b[m\x1b[?25l\x1b[93m\x1b[15;22Haaaaaasl\x1b[?25h\x1b[m\x1b[?25l\x1b[93m\x1b[15;22Haaaaaaslk\x1b[?25h\x1b[m\x1b[?25l\x1b[93m\x1b[15;22Haaaaaaslkd\x1b[?25h\x1b[m\x1b[?25l\x1b[93m\x1b[15;22Haaaaaas...

If we break it up, it wiil be:

\x1b[93m\x1b[15;22Haaaaaa\x1b[?25h\x1b[m\x1b[?25l
\x1b[93m\x1b[15;22Haaaaaas\x1b[?25h\x1b[m\x1b[?25l
\x1b[93m\x1b[15;22Haaaaaasl\x1b[?25h\x1b[m\x1b[?25l
\x1b[93m\x1b[15;22Haaaaaaslk\x1b[?25h\x1b[m\x1b[?25l
\x1b[93m\x1b[15;22Haaaaaaslkd\x1b[?25h\x1b[m\x1b[?25l
\x1b[93m\x1b[15;22Haaaaaas...

This seems reasonable. But StateMachine::ProcessString seems to be wrongly handling this and print control string like \x1b[?25h into the screen buffer.

I've look to hear you guys opinion on this one, especially @zadjii-msft who left a comment in #1311.

Issue 2:
Description of the new feature/enhancement

Add additional app execution aliases in addition to wt

Proposed technical implementation details (optional)

I am used to pressing Win-R then "cmd" to open up a command prompt, can you provide an option for adding bash and cmd as additional aliases (which are disabled by default). Also detect that they are being used and start up the appropriate shell.
Issue 1:
Is there a reason that there's alot of duplicate code in the css source file?

SEE BELOW:

.container:before,

.container:after {

display: table;

content: " ";

}

.container:after {

clear: both;

}

.row:before,.row:after {

display: table;

content: " ";

}

.row:after {

clear: both;

}

.form-horizontal .form-group:before,

.form-horizontal .form-group:after {

display: table;

content: " ";

}

.form-horizontal .form-group:after {

clear: both;

}

.nav:before,

.nav:after {

display: table;

content: " ";

}

.nav:after {

clear: both;

}

.tabbable:before,

.tabbable:after {

display: table;

content: " ";

}

.tabbable:after {

clear: both;

}

.navbar:before,

.navbar:after {

display: table;

content: " ";

}

.navbar:after {

clear: both;

}

.navbar-collapse:before,

.navbar-collapse:after {

display: table;

content: " ";

}

.navbar-collapse:after {

clear: both;

}

.btn-toolbar:before,

.btn-toolbar:after {

display: table;

content: " ";

}

.btn-toolbar:after {

clear: both;

}

.pager:before,

.pager:after {

display: table;

content: " ";

}

.pager:after {

clear: both;

}

.modal-footer:before,

.modal-footer:after {

display: table;

content: " ";

}

.modal-footer:after {

clear: both;

}

Issue 2:
show on bootstrap.css

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L581

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L723

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L743

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2023

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2433

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2617

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2637

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3032

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3296

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3453