WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
The following is a full-screen screenshot of the Documentation website on my screen.

As you see, menu simply doesn't fit there. And because the menu is just hanging there, i can't quite scroll it downwards to see the rest of the content.

Issue 2:
When you display some item that has a lot of subitems, the nav grows so much that it doesn't fit on some resolutions, and some of the items aren't shown.

http://oi43.tinypic.com/2ivjtyv.jpg

On that screenshot, nav items are shown up to badges, missing the remaining. I've tested it on latest Firefox and Chrome at 1366x768.
Issue 1:
In v3.2.0 the behavior of how popovers are placed has changed. I have prepared two fiddles that showcase the difference:

Bootstrap v3.1.1 showing correct placement: http://jsfiddle.net/o89u6kn8/1/

Bootstrap v3.2.0 showing incorrect placement: http://jsfiddle.net/dthxt5ka/1/

Please notice that both fiddles share the same code. Only the Bootstrap version is different.

Issue 2:
See http://jsfiddle.net/hqDF7/ for a minimal example.

The issue appeared with 8534e12.

Those lines use .outerWidth & .outerHeight and override what .getBoundingClientRect was returning. Unfortunately, .outer[Width|Height] always return 0 for SVG elements, while .getBoundingClientRect returns the expected output.

Removing the incriminated lines "fixes" the issue. But of course I guess it creates other issues.

This issue is similar to #5956.
Issue 1:
Chrome for Mac. Taken from the docs.

Open the popovers. Resize. Boom.

Issue 2:
Using Bootstrap in a client project, I had to fix a bug where a Popover was incorrectly positioned. The detail was that the mix of markup and JavaScript on the page created the popover, set the focus to the triggering field (causing the Popover to appear), but then other JavaScript modified the DOM (adding an alert to the top of the page) that shifted down the triggering field ... and the Popover stayed positioned relative to the fields original position.

I also noticed that resizing the browser window also fails to reposition the Popover when, again, the location of the underlying field has changed.

My brief research on DOM events indicates that support for generic DOM tree modification events is spotty and buggy, but handling the window resize event would be sufficient for many people.

My approach to this is a bit of a hack (and has some Apache Tapestry details mixed in).

/** Adds a new operation, "reposition", to Bootstrap's popover that
* re-positions the tooltip/popover if it is currently visible. This is used to handle
* changes to the DOM and window resizing.
*/
jQuery.fn.popover.Constructor.prototype.reposition = function () {
if (this.enabled && this.tip().hasClass("in")) {
this.show();
}
}

... and in the code that creates the Popover:

matches.popover(options);

function doReposition() {
matches.popover("reposition");
}

jQuery(window).resize(_.throttle(doReposition, 250));

// Ideally, there would just be a way to handle this for anything that modifies the DOM.
T5.sub(T5.events.ADD_ALERT, null, doReposition);

This works acceptibly; there's a slighe fade in/fade out animation here that I'd prefer to avoid; it would be nice if the tooltip show() function could be broken up a little, so that the code that determines position could be invoked directly, without all the other stuff that show() does.
Issue 1:
Given the following:

import foo from 'foo';
export { default as bar } from 'bar';

I would have expected foo to be loaded and evaluated before bar, but Babel transpiles this to (somewhat simplified):

exports.bar = undefined;

var _bar = require('bar');

Object.defineProperty(exports, 'bar', {
enumerable: true,
get: function get() {
return _interopRequireDefault(_bar).default;
}
});

require('foo');

Note that foo is required after bar.

The workaround is pretty simple:

import foo from 'foo';
import bar from 'bar';

export { bar }

But surprising nonetheless.

I posted this on the discourse forums before filing here.

Here's the issue reproduced on the Babel site.

Input Code

import foo from 'foo';
export { default as bar } from 'bar';

Babel Configuration

babel-latest

Expected Behavior

The 'foo' module should be loaded and evaluated first.

Current Behavior

The re-exported bar is loaded and evaluated before 'foo', despite the reverse source order.

Context

Trying to import babel-polyfill in an "index" type of file (i.e. a file that is entirely re-exports of other files).

Issue 2:
Issue originally made by @loganfsmyth

Input code

import 'foo';
export {foo} from 'bar';

Description

'use strict';

Object.defineProperty(exports, "__esModule", {
value: true
});
exports.foo = undefined;

var _bar = require('bar');

Object.defineProperty(exports, 'foo', {
enumerable: true,
get: function get() {
return _bar.foo;
}
});

require('foo');

Note that foo loads after bar.
Issue 1:
Not sure if there is already an issue about this

The side of the html preview is hidden behind the code editor, see screenshot above

I would probably be able to fix this?

On Chrome (iMac, El Capitan) - Screen size: 1920 x 1080

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-learn-how-script-tags-and-document-ready-work has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When you use the following it doesnt validate as correct. It needs an extra line between the opening and closing lines.

$(document).ready(function() {

});

Workaround for anyone stuck here, use this:

$(document).ready(function() {

});
Issue 1:
Hi, it looks like with the new version 3.0 I have to set the class names of an image to col-lg-4 col-sm-4 col-4 if the image is part of div with the same class names to make the image responsive with all breakpoints.

In version 2 the images CSS properties inherited by default the parent's div properties.

I would like to know if I am getting this right. Thank you,

Laurent

Issue 2:
the images are not responsive by default I have to add a class to the images.

img {

max-width: 100%;

}
Issue 1:
Allow extensions to specify they are deprecated in their package.json, with an optional alternative extension(s) field. This setting can inform the user of the deprecation in-product, and if specified, potentially update to the new extension automatically without informing of the deprecation?

Related: #3670

Issue 2:
It's getting more common to use YAML for configuration. For example docker-compose.yml or Swagger files are usually written in YAML. The JSON Schema based autocomplete for JSON files is a neat feature, please enable that for YAML files also.
Issue 1:
Documentation

When searching the documentation and clicking on the listed links, the link refers to a specific heading/reference in the generated documentation page. On the new HTML documentation design, the fixed top bar covers up this referenced element:

https://numpy.org/devdocs/reference/generated/numpy.repeat.html?highlight=repeat#numpy.repeat

Image illustrating what is seen when entering the page from a search:

Scrolling slightly down reveals the header of the desired content

Issue 2:
When we took on the new theme, we tweaked it to make the title bar taller. This change means that it overlaps focused headings:

https://numpy.org/devdocs/user/building.html#accelerated-blas-lapack-libraries

We should either remove this customization, or do a more thorough sweep of all the dimensions which assume its old value.

To fix this particular bug, we need to add -30px to the margin for .header-style:before, h1:before, h2:before, h3:before, h4:before, h5:before, h6:before {

cc @mattip
Issue 1:
Example name

with-rematch

Describe the bug

I'm using with-rematch to build my app, and I found my component with withRematch HoC works strangly: componentDidMount was called instead of componentDidUpdate if its prop updated.

To Reproduce

I copied with-rematch in my repo: https://github.com/zsxtoys/PoC-nextjs-with-rematch/

First of all, I added console.log to componentDidMount:

https://github.com/zsxtoys/PoC-nextjs-with-rematch/commit/860ea41818f67f44732858f972280c42f345e33a

Then, I click on Home repeatly, and i found componentDidMount called more than once.

Expected behavior

componentDidMount should be call only once.

System information

OS: macOS

Browser: Chrome

Version of Next.js: 7.0.0

Issue 2:
Hello everyone! I was going to start researching if using Next for our project was a good choice, but I couldn't get the 'hello-world' example working. I've followed exactly as the README says, but it won't work. I've also followed the guide on Next's Readme, but I've got the same results.

Am I doing anything wrong? Perhaps with my environment?

Thanks and sorry if this is duplicated (found similar issues, but didn't help me).

This is the error:

ERROR Failed to compile with 1 errors 15:25:47

error in ./pages?entry

Syntax Error: Unexpected token (3:2)

1 | import Link from 'next/link'
2 | export default () => (
> 3 | <div>Hello World. <Link href='/about'><a>About</a></Link></div>
| ^
4 | )
5 |

@ multi ./pages?entry
Issue 1:
Karthik Gurumurthy opened SPR-6369 and commented

I want to be able to specify the JSR303 validation group when specifying @Valid in @Controller-s.

I don't want the validation to be run against the default group every time.

I guess currently I can inject a javax.validation.Validator reference in the @Controller and handle this programmatically. Would be nice if this can be driven through an annotation as well.

But @Valid doesn't support a "group" attribute though.

What do you guys think?

Affects: 3.0 RC2

Issue Links:

#11039 Support for validation groups in @Valid used by spring MVC ("duplicates")

2 votes, 2 watchers

Issue 2:
Pavla Nováková opened SPR-6373 and commented

It would be useful to be able to use validation groups in spring MVC as specified by JSR-303. With the improvement it should be possible to write something like:

@RequestMapping("/foo", method=RequestMethod.POST)

public void processFoo(@Valid(groups={Default.class, MyValidationGroup.class}) Foo foo) { ... }

Affects: 3.0 RC2

Issue Links:

#11035 Support for 'groups' in addition to @Valid for @MVC Controllers ("is duplicated by")

#11722 Add Group Class support to JSR-303 Validation using @Valid ("is duplicated by")

#12504 ValidationUtils: add support for Validation group interfaces

Referenced from: commits 0013317, 49a2aaf

54 votes, 53 watchers
Issue 1:
Version

2.6.2

Reproduction link

https://codepen.io/anon/pen/ZwXRKJ

Steps to reproduce

Since 2.6.x when using the new v-slot syntax the following will not work:

<template #header>
<my-component></my-component>
</template>

When the component is imported "lazy" like this:

components: {
MyComponent: () => import('./MyComponent'),
},

This worked with the old slot syntax.

Now just nothing is shown. Only if the dom is refreshed (e.g. by some display toggle) the component is shown afterwards. But not on the first load.

Another workaround is not to use lazy imports and directly import the component.

What is expected?

v-slots should work with lazy loaded components like it did with the old slot syntax.

What is actually happening?

It is not shown (until the dom is reloaded)

Unfortunately I could not reproduce this async issue with codepen.

It took me quite a while to figure out it is the lazy import which causes my page is not working correctly anymore after updating to 2.6.2.

Issue 2:
Version

2.6.2

Reproduction link

https://codesandbox.io/s/p530yln9z7

Steps to reproduce

Open the repro, follow the instructions.

What is expected?

Component b should appear

What is actually happening?

Component b does not appear

Using Vue 2.5.22 works, or not async loading the component works as well
Issue 1:
I have a code like this:

var manager = new THREE.LoadingManager, loader = new THREE.ObjectLoader (manager), model;
manager.onLoad = function () {
console.log (model); // log 2
};
loader.load (
'......json',
function (result) { model = result; console.log(result) } // log 1
);

and log 2 randomly happens before log 1 (logging undefined as a result). This never happened with real loaders, what's going on?

Issue 2:
Description of the problem

basically, area lights do not work with npm/node module resolution, see:

simplified: https://codesandbox.io/s/three-fibre-userender-test-rohv5

raw threejs arealight demo: https://codesandbox.io/s/dreamy-platform-3jpim

why

all files under examples/jsm pull from ../../../build/three.module.js instead of three, which is arguably not correct. it will pull threejs two times in bundling systems that do not follow package.json:module (but "main" instead, which leads to build/three.js). it then creates two separate namespaces. uniforms.init() ends up writing to the wrong one.

solution

this is how a typical jsm file should look:

import {
ClampToEdgeWrapping,
DataTexture,
FloatType,
LinearFilter,
NearestFilter,
RGBAFormat,
ShaderLib,
UVMapping,
UniformsLib
} from "three";

that's how any other library works. i have never seen library that relies on a distro file - this has obvious pitfalls. i understand that this was made to make the html demos work, but imo this is a hack, and it now impacts production usage.

Three.js version

r107

Browser

Chrome

OS

macOS
Issue 1:
Is the following behaviour of numpy (v1.13.1) a bug or by design?

>>>import numpy as np
>>>a = np.zeros((1,), dtype=[(('title 1', 'x'), '|i1'), (('title 2', 'y'), '>f4')])

>>>a.dtype.descr
[(('title 1', 'x'), '|i1'), (('title 2', 'y'), '>f4')]

>>>a[['y','x']].dtype.descr
[('y', '>f4'), ('x', '|i1')]

I would have expected the last expression to have returned this instead:

[(('title 2', 'y'), '>f4'), (('title 1', 'x'), '|i1')]

Why are the field-titles missing on a view obtained by indexing?

It is kind of surprising, that some aspects of the structured-array dtype just get dropped.

Issue 2:
Describe the issue:

[I want to begin by first acknowledging that this is a fringe case of a bug appearing only in a VM (I haven't yet been able to reproduce it on real hardware), so please feel free to close this issue right away. However, I felt that I still should at least point it out, in case there is some latent real issue that this might uncover. In any case, hints as to how I can dig deeper into this so that I may report it to the proper channel (be it QEMU, GNU libc, or whatever) would be welcome.]

On a QEMU ppc64le VM, When casting an array of floats to np.intc, a weird truncation seems to happen. This only occurs in the VM; it does not happen onthe real ppc64le hardware I had access to (although that system hat an older 4.19 kernel; I cannot change that).

In the code below, I create arrays of value 1. of length 1 through 10, and then cast them to np.int64 and np.intc for comparison.

This works fine for arrays with length <= 3. If fails for longer ones, and apparently there is a pattern in this failure.

Reproduce the code example:

import numpy as np
for i in range(1, 11):
a = np.full(i, 1.)
print(i, a, a.astype(np.int64), a.astype(np.intc))

Error message:

1 [1.] [1] [1]
2 [1. 1.] [1 1] [1 1]
3 [1. 1. 1.] [1 1 1] [1 1 1]
4 [1. 1. 1. 1.] [1 1 1 1] [0 0 0 0]
5 [1. 1. 1. 1. 1.] [1 1 1 1 1] [0 0 0 0 1]
6 [1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1] [0 0 0 0 1 1]
7 [1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1] [0 0 0 0 1 1 1]
8 [1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0]
9 [1. 1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0 1]
10 [1. 1. 1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0 1 1]

NumPy/Python version information:

1.22.1 3.9.10 (main, Jan 16 2022, 17:12:18)

[GCC 11.2.0]
Issue 1:
From @amb-it-ion on January 5, 2016 14:42

I am not sure why I could not find any mention of this: I am really missing a feature to autocomplete on missing classes, e.g. when using Http from angular2/http, and given that angular2 is on the node_modules default path (or inside my tsconfig files configuration) I would expect the autocompletion to pick this definition up and add the corresponding import statement.

Copied from original issue: microsoft/TypeScript-Sublime-Plugin#425

Issue 2:
Hi,

Visual Studio (2013 Ultimate) provides intellisense for the src attribute for script elements, by reading the file system and displaying available files or folders.

It will be quite useful if similar functionality can be provided for <reference> and import statements:

<reference path="foo/ <--- here

import foo = require('foo/ <--- and here
Issue 1:
Which version of ShardingSphere did you use?

5.0.0-beta

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

Both

Reason analyze (If you can)

duplicated code or missing some other important jdbc property

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

when i read 'HikariJDBCParameterDecorator' class source, i found 'useServerPrepStmts' property was set twice in decorate method. I guess it may be duplicated source code or missing some more important property set??

It should be fixed even if just for clean code. :)

Issue 2:
I use Sharding-Proxy to separate reads and writes from MySQL.

In the real instance library, there is a table called 'block'.

When I access the table through Sharding-Proxy, I get an error:ERROR 10002 (C1000): 2Unknown exception: [null]

It looks like because of the name block!!!

so ....why ？

all the other tables seems like no problem；
Issue 1:
Bug report

Bug summary

DayLocator returning incorrect times around daylights switch over, resulting in duplicate day labels.

Code for reproduction

import datetime

import pylab
import matplotlib.dates as mdates
import pytz

x = [datetime.datetime(2017, 3, 30), datetime.datetime(2017,4,4)]
y = [0, 1]

pylab.plot(x, y)

ax = pylab.gca()

tz = pytz.timezone("Australia/Sydney")
ax.xaxis.set_major_locator(mdates.DayLocator(tz=tz))
ax.xaxis.set_major_formatter(mdates.DateFormatter("%a", tz=tz))

pylab.show()

Actual outcome

The day labels for the day of the daylight switch over are duplicated, see figure below:

Expected outcome

The labels should not be duplicated.

Matplotlib version

Operating System: Kubuntu 17.04

Matplotlib Version: 2.02

Python Version: Python 2.7.13

pytz: 2017.2

Issue 2:
Bug summary

Quiver plot issue matching key label color with arrow color

Code for reproduction

q=plt.quiver([1, 2,], [1, 1], [[49],[49]], [0],
[[(0.6, 0.8, 0.5, 1.0 )],
[(0.3, 0.1, 0.2, 1.0 )]],
angles=[[45],[90]],
)
plt.quiverkey(q, .5, .5, 7, r'vector2', labelcolor=(0.3, 0.1, .2, 1), labelpos='S', coordinates = 'figure')

Actual outcome

Expected outcome

The key label color and a vector are both set to (0.3, 0.1, .2, 1) but their colors are different.

Matplotlib version

Operating system: Ubuntu 18.04

Matplotlib version: 3.0.3

Matplotlib backend: TkAgg

Python version: 3.6

Jupyter version (if applicable):

Other libraries:

pip3 install matplotlib
Issue 1:
Do you want to request a feature or report a bug? bug

What is the current behavior?

When React component is mounted as a descendent of DOM element which stops propagation of change event, onChange event of <select> in React component does not occur.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

HTML structure

<!-- outer div's onchange event contains stopPropagation() -->
<div>
<div id="react-root"></div>
</div>

React Component (only render())

render() {
return(
<select onChange={this.doesNotWork} value={this.state.value}>
<option value=""></option>
<option value="another">another option</option>
</select>
);
}

Reproduction in CodePen

What is the expected behavior?

<select onChange> works well just like <input> or <textarea>

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

This issue occurred with React 16.4.2 (not tested for older React), newest Chrome, Firefox, Edge, IE11 on Windows 10.

Issue 2:
@nathansobo will that help your event perf issues a bit? I'm not familiar with atom's plugin infrastructure, But this'll help if you have <Editor/><Plugin1/> (two renderComponents). Doesn't help if you have <Editor><Plugin1/></Editor> though, but I have some ideas to optimize events a bit more.

This is nonetheless an ok idea, I think.

@spicyj
Issue 1:
I think that Atom should be saving the current session (All open tabs and their contents as well as the tree view) by default. It is important to note that saving the session should be done not only on exit, but every time changes are made to the files (without the user having to save the file) So the work will persist even after Atom crashes.

In Sublime you never have to think about what files are open, if you saved last changes, etc. You also never have to worry what happens to your work after crash, you are guaranteed to have it all intact when you open it again. This is very handy and frees you from thinking about trivial things.

Issue 2:
A feature I love about ST2 and iA Writer, which I'm missing in Atom, is when you quit the app with open windows (including unsaved documents), they all appear again when you reopen.

This has saved me countless times in my workflow to handle having to do a system restart for software update, etc and not have to take time to save all my unsaved docs, etc.

It's also nice because I generally have five or six open projects that I just keep minimized in the editor for ease of access. It would be great to have such a feature in Atom.
Issue 1:
I was wondering if it was possible to render a react component server side without serialising it to a string. It should make it possible to trigger state changes without re-rendering the whole tree.

For example, I'd like to be able to do something like this (pseudo-code):

class Test extends Component {
componentWillMount() {
// this method should only be called once, by `render(Test)`
setTimeout(() => this.setState({ ready: true }), 1000)
}
render() {
const { ready } = this.state
if (ready) {
return (<strong>I am ready</strong>)
}
return (<strong>I am not ready</strong>)
}
}

const tree = render(Test)
renderToString(tree)
// => <strong>I am not ready</strong>
setTimeout(() => renderToString(tree), 2000)
// => <strong>I am ready</strong>

I don't really plan to use timeouts but it was to illustrate the idea.

This would be another way to put it:

let setState
class Test extends Component {
componentWillMount() {
// important: this is called only once
console.log('componentWillMount called')
setState = this.setState.bind(this)
}
render() {
const { ready } = this.state
if (ready) {
return (<strong>I am ready</strong>)
}
return (<strong>I am not ready</strong>)
}
}

const tree = render(Test)
// outputs: componentWillMount called
console.log(renderToString(tree))
// outputs: <strong>I am not ready</strong>
setState({ ready: true })
console.log(renderToString(tree))
// outputs: <strong>I am ready</strong>

If this is not possible currently, would it be difficult to implement?

Issue 2:
It would seriously ease the process of building something isomorphic if componentWillMount could return a promise and that react would delay rendering until that promise is resolved. I have seen attempt of doing something like that in react-router and rrouter, however giving this responsibility to each component instead of a router module would make more sense for me.
Issue 1:
#454

#456

#451

Glide.with(getActivity()).load(Utils.getYoutubeUrl(density, getArguments().getString(VIDEO_ID))).asBitmap().error(R.drawable.ic_error_icon).into(glideImageView);

I wish I could get Exception listener for 404

like if particular url returns 404 then retry with fallback url instead of drawable .

Example Url1 - http://img.youtube.com/vi/watsQDZ3KNw/sddefault.jpg

if Url1 returns 404 then fallback

http://img.youtube.com/vi/watsQDZ3KNw/mddefault.jpg

I am using Youtube Image API , which does always have mddefault.jpg and higher version might not available .

Issue 2: